Solution : https://service.sap.com/sap/support/notes/391 (SAP Service marketplace login required)
Summary :
This SAP Note addresses an issue where all database accesses hang and only an hourglass is displayed system-wide in SAP environments using Oracle databases. Error logs indicate inability to allocate logs for archiving, pointing towards full archival locations or permissions issues. Common errors include ORA-00257 (archiver error) and ORA-16038 (log cannot be archived), often accompanied by OS errors such as insufficient disk space. Solutions involve clearing space in archival directories or altering log destination paths temporarily, ensuring proper write permissions, and verifying the archiving process's operation. Using BRARCHIVE 7.00+ is recommended for managing offline redo logs efficiently.
Key words :
archive log <log> thread <thread> sequence <seq_nr>arc0, alter system set log_archive_dest_1 = 'location=<temp_path>', sqlplus usingalter system archive log start, error writing archive log <log>ora-16014, error creating archive log <log>ora-00272, alter system set log_archive_dest=<temp_path>, alter system archive log stop, alter system archive log start, error 19504 creating archive log file, problems accessing secondary archive destinations 6
Related Notes :
932251 | ARCH no longer archives after full file system |
904490 | Automatic enhancement of control files |
863417 | FAQ: Database Archive modes and redo logs |
767414 | FAQ: Oracle latches |
694155 | Error due to corrupt redo logs |
619188 | FAQ: Oracle wait events |
584548 | Unusually high number of redo logs |
546006 | Problems with Oracle due to operating system errors |
541538 | FAQ: Reorganization |
521264 | Hang situations |