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 4.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
While you are using Oraclebackupmanager to restore database, a DOS window appears on the server, reporting "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 six 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. To trigger the error message, 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 number of database updates, you will see the error message. The message does not necessarily indicate a major problem, but it could be an indication of a full disk or some other problem that is preventing the log files from being archived. |
|
|
|
||
Solution |
Check the C: or D:\Oracle\10.2.0\Rdbms\Trace\alert_ARAXI.log file for error messages. If there are no actual errors, you can safely ignore the message. 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 v$logfile status, in sqlplus> select * from v$logfile; If any log file has a STALE status, you may want to run "alter system switch logfile" six times to roll over the log. Check the status of the database backups using OracleBackupManager (use the Show command). Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Amy Chan |
|
Submitted by |
Amy Chan |
|
Date submitted |
02 Nov 2006 |
|