Question: I
tried an alter database open and got the following ORA-16-38
error:
SQL> alter database
open:
ORA-16038: log one sequence 1234 cannot
be archived
ORA-19809: limit exceeded for recovery files
ORA-00312 online log 1 thread 1
Answer: The oerr utility shows this for the
ORA-16038 error:
ORA-16038:
Log string
sequence# string cannot be archived
Cause: An attempt was made to archive the named
file, but the file could not be archived.
Examine the secondary error
messages to determine the cause of the error.
Action: No action is required.
The cause notes that the most common solution fix for
this ORA-16038 and ORA-19809 error is to increase the size
of the archived redo log file directory. You should
also increase the value of your
db_recovery_file_dest_size parameter and bounce the
instance See my notes on the related
ORA-19809 error.
|
|
|
Oracle Training from Don Burleson
The best on site
"Oracle
training classes" are just a phone call away! You can get personalized Oracle training by Donald Burleson, right at your shop!
|
|
|
|
|
Burleson is the American Team
Note:
This Oracle
documentation was created as a support and Oracle training reference for use by our
DBA performance tuning consulting professionals.
Feel free to ask questions on our
Oracle forum.
Verify
experience!
Anyone
considering using the services of an Oracle support expert should
independently investigate their credentials and experience, and not rely on
advertisements and self-proclaimed expertise. All legitimate Oracle experts
publish
their Oracle
qualifications.
Errata?
Oracle technology is changing and we
strive to update our BC Oracle support information. If you find an error
or have a suggestion for improving our content, we would appreciate your
feedback. Just
e-mail:
and include the URL for the page.
Copyright © 1996 - 2020
All rights reserved by
Burleson
Oracle ®
is the registered trademark of Oracle Corporation.
|
|