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 |
The D:\Orant\Rdbms80\Trace\creoALRT.LOG file (Prinergy 1.1) or D:\Ora816\Rdbms\Trace\creoALRT.log file (Prinergy 2.0) shows an error similar to this: (the data file number and name may be different) ORA-00604: error occurred at recursive SQL level 1 ORA-00376: file 4 cannot be read at this time ORA-01110: data file 4: 'G:\ORANT\ORACLE\DATA\RBS1CREO.ORA' |
|
|
|
||
Symptoms |
The RAID drive containing the Oracle database has run out of disk space or the RAID was shut off during operation and Oracle errors are appearing in the Prinergy diagnostics logs and Oracle ALERT log. |
|
|
|
||
Cause |
The data file (in the example above, data file 4 - Rbs1creo.ora) was taken offline due to some problem accessing the data file such as the RAID being turned off during operation, or possibly the RAID running out of disk space when Oracle tried to expand the data file. When the data file is taken offline, its status changes from 'ONLINE' to 'RECOVER' or 'OFFLINE'. If the datafile has the status of RECOVER, to put the data file back online, it must be recovered, then manually placed online. If the datafile is OFFLINE, you can put the datafile back ONLINE without recovering. Note: The archived log files may be required to bring the datafiles back online. If a database backup occurs after the datafiles were taken offline, you may not be able to recover the database. |
|
|
|
||
Solution |
Recover the data file and put it online: First identify which datafile is in recovery: 1) Start the Oracle Server Manager - SVRMGR30 (Prinergy 1.1) or SVRMGRL (Prinergy2.0): EXAMPLE: * D:\> SVRMGR30 2) Connect as the user 'Internal': * SVRMGR> connect internal/creo 3) Display the status of each datafile: * SVRMGR> select status, name from v$datafile; EXAMPLE (Prinergy 1.1): * SVRMGR> select status, name from v$datafile; * STATUS NAME * ---------- ----------------------------------------- * SYSTEM G:\ORANT\ORACLE\DATA\SYSCREO.ORA * ONLINE G:\ORANT\ORACLE\SORTSPACE\TMP1CREO.ORA * ONLINE G:\ORANT\ORACLE\DATA\USR1CREO.ORA * RECOVER G:\ORANT\ORACLE\DATA\RBS1CREO.ORA * 4 rows selected.
To recover the datafile(s) do the following: 4) Recover the data file: * SVRMGR> recover datafile 'G:\Orant\Oracle\Data\Rbs1creo.ora'; ** Note: ** Replace the data file name 'G:\Orant\Oracle\Data\Rbs1creo.ora' with the data file that requires recovery. 5) If this prompt appears: Specify log: {<RET>=suggested | filename | AUTO | CANCEL}' Press RETURN until it says 'Media recovery complete' 6) Put the data file online: * SVRMGR> alter database datafile 'G:\Orant\Oracle\Data\Rbs1creo.ora' online; ** Note: ** Replace the data file name 'G:\Orant\Oracle\Data\Rbs1creo.ora' with the data file that requires recovery. If the datafile that required recovery was RBS1CREO.ORA, then the rollback segments may have to be put online: 7) Check the rollback segment status: * SVRMGR> select status, segment_name from dba_rollback_segs; EXAMPLE: * SVRMGR> select status,segment_name from dba_rollback_segs; * STATUS SEGMENT_NAME * ---------------- ------------------------------ * ONLINE SYSTEM * OFFLINE USRRBS1 * OFFLINE USRRBS2 * OFFLINE USRRBS3 * OFFLINE USRRBS4 * 5 rows selected. 8) Put the rollback segments online (if necessary): * SVRMGR> alter rollback segment USRRBS1 online; * Statement processed. * SVRMGR> alter rollback segment USRRBS2 online; * Statement processed. * SVRMGR> alter rollback segment USRRBS3 online; * Statement processed. * SVRMGR> alter rollback segment USRRBS4 online; * Statement processed. 9) Exit from Server Manager: * SVRMGR> exit Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
||