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 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
A DOS window appears on the server that reads, "Cannot allocate log, archival required. Press <ENTER> to acknowledge message." |
|
|
|
||
Cause |
This message appears when Oracle cannot copy the Online redo log file to the archived log file before Oracle needs to reuse the online redo log file. There are 6 online redo log files that are used in sequence. Each redo log file is written out to the archived log file folder as soon as Oracle switches to the next redo log file. Thus to get this error message, either the log file cannot be written out due to a full disk or some other problem, or the log file cannot be written out fast enough to keep up with the log file switches. The archived log files are stored in an NT compressed folder. This slows down the writing process so in some cases when the log files are switching rapidly due to a large amount of database updates, you will see this message appear. This message does not necessarily indicate a major problem, but it could also be an indication of a full disk or some other problem that is preventing the log files from being archived. Therefore, you should check the D:\Orant\Rdbms80\Trace\creoALRT file for error messages if the warning message appears. |
|
|
|
||
Solution |
Check the D:\Orant\Rdbms80\Trace\creoALRT file for error message. If there are no errors, then the message can be ignored. If there are errors, more troubleshooting is required. The most likely cause of a failure is a full E: drive (this is typically where the archived log files are stored). You may also want to check if the database is being backed up properly. If the database backups fail, the archived log files will accumulate in the E:\Orant\Oracle\ArchivedLogFiles folder. Check the status of the database backups using OracleBackupManager (use the Show command). Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||