![]() ![]() SQL> alter system set log_archive_dest_1='' scope=memory Īnother way is to manually move some archive logs to a new destination. Use RMAN to backup and delete your archive logs and when the incident is resolved, you may undo the change: This depends on LOG_ARCHIVE_MIN_SUCCEED_DEST parameter, which defines the minimum number of destinations that must succeed in order for the online logfile to be available for reuse. SQL> alter system set log_archive_dest_1='LOCATION=/oratest/TESTDB/arch' scope=memory Īrchive destination USE_DB_RECOVERY_FILE_DESTĭatabase will try to put logs on both destinations, but if one of them is full, it will fail and will put it only in the second destination. ![]() You can add one more archive log destination to a filesystem with enough free space: Database froze, due to archive log destination being full and you can only connect as SYSDBA.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |