Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
You may encounter these errors in Prinergy and Oracle: 1) Prinergy diagnostics logs shows database errors when starting up: 'E 24Jul00 10:25:04.093-PDT [525.407] LINOSERVER ARAXI PChangeJobShare.main iDBIF_ThrowDBException.cpp(101): A general database failure has occured: [SERVERERROR] Error from Server: ORA-01033: ORACLE initialization or shutdown in progress'. 2) Main Directory and Registered File daemons crash when Workshop is started. 3) Oracle database log file: D:\Orant\RDBMS80\Trace\creoALRT.log shows the message: 'ORA-1113 signalled during: alter database open ...'. |
|
|
|
||
Symptoms |
The database was backed up then restored during maintenance performed on the RAID. |
|
|
|
||
Cause |
If the contents of the RAID were moved to another RAID, or the RAID was backed up then subsequently restored, you may encounter a database failure if the Oracle services were not disabled when the RAID was backed up. The database files on the RAID are inconsistent or 'out-of-sync' with the control files and redo log files. After the Oracle files are restored onto the RAID, Oracle detects that the files are not current and require recovery. |
|
|
|
||
Solution |
Follow these steps to recover the database: 1) Stop Oracle services - OracleServiceCreo and OracleStartCreo (Prinergy 1.1) or OracleStarter (Prinergy 2.0). 2) Back up the existing database files (D:\Orant\Oracle\* (Prinergy 1.1), E:\Orant\Oracle\*, G:\Orant\Oracle\* or the Orant folder on the RAID). Back up the files to disk, either onto the E: drive or RAID. 3) Restart the OracleServiceCreo and OracleStartCreo (OracleStarter) services. 4) Open a command prompt window and enter: D:\> svrmgr30 (in Prinergy 2.0, enter SVRMGRL) SVRMGR> connect internal/creo SVRMGR> shutdown immediate; SVRMGR> startup 5) Verify that you have an error similar to the one below. If not, then consult an Oracle expert. ORA-01113: file 3 needs media recovery ORA-01110: data file 3: 'G:\ORANT\ORACLE\DATA\USR1CREO.ORA' The file number and file name may be different, the phrase 'ORA-01113: ... needs media recovery' is the indication that the database file is out of sync. 6) Start up the database in 'mount' mode and recover the database: SVRMGR> shutdown immediate; SVRMGR> startup mount; SVRMGR> recover database; 5) Re-start the database and check for errors: SVRMGR> shutdown immediate; SVRMGR> startup A successful startup will display the message 'Database opened' as shown below: Total System Global Area 18751488 bytes Fixed Size 49152 bytes Variable Size 8388608 bytes Database Buffers 10240000 bytes Redo Buffers 73728 bytes Database mounted. Database opened. If this fails to work, it may be necessary to restore the database from the last backup set using OracleBackupManager. See the workaround SYOA-0000113, "How to restore the database using OracleBackupManager." Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
daemon, oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||