How to solve the problem of error reporting ORA-16038 in SQL
This article mainly explains "how to solve the problem of error reporting ORA-16038 in SQL". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to solve the problem of error reporting ORA-16038 in SQL".
# problem description: start error report
SQL > startup
ORACLE instance started.
Total System Global Area 1787138048 bytes
Fixed Size 2254104 bytes
Variable Size 956304104 bytes
Database Buffers 822083584 bytes
Redo Buffers 6496256 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 32429
Session ID: 1137 Serial number: 5
# View alarm log
[oracle@ora2] $tail-f / u01/oracle/diag/rdbms/orcl/orcl/trace/alert_orcl.log
.
Errors in file / u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_32429.trc:
ORA-16038: log 3 sequence# 510 cannot be archived
ORA-19502: write error on file "", block number (block size=)
ORA-00312: online log 3 thread 1:'/ u01 Universe oracle.oradataUnip orclapace redo03.log'
USER (ospid: 32429): terminating the instance due to error 16038
.
# View trace file
More / u01/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_32429.trc
.
Executing ASYNC actions
-END DDE Actions Dump (total 0 csec)-
ORA-16038: log 3 sequence# 510 cannot be archived
ORA-19502: write error on file "", block number (block size=)
ORA-00312: online log 3 thread 1:'/ u01 Universe oracle.oradataUnip orclapace redo03.log'
Kjzduptcctx: Notifying DIAG for crash event
.
# solution
SQL > conn / as sysdba
Connected to an idle instance.
SQL > startup mount
ORACLE instance started.
Total System Global Area 1787138048 bytes
Fixed Size 2254104 bytes
Variable Size 956304104 bytes
Database Buffers 822083584 bytes
Redo Buffers 6496256 bytes
Database mounted.
SQL > alter database clear unarchived logfile group 3
Database altered.
SQL > alter database open
Database altered.
SQL >
Thank you for your reading, the above is the content of "how to solve the problem of error reporting ORA-16038 in SQL". After the study of this article, I believe you have a deeper understanding of how to solve the problem of error reporting ORA-16038 in SQL, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
