When I started my database today, I found that the database can only be mounted and cannot be opened. The following error message is displayed:
SQL> select open_mode from v $ database;
OPEN_MODE
----------
MOUNTED
SQL> alter database open;
Alter database open
*
Row 3 has an error:
ORA-16014: log 2 serial number 66 Unarchived, no available destination
ORA-00312: Online log 2 thread 1:
F: OraclePRODUCT10.2.0ORADATAORCLREDO02. LOG
It turns out that there is a log problem, which is better solved. Check the log status.
SQL> select * from v $ log;
GROUP # THREAD # SEQUENCE # BYTES MEMBERS ARC STATUS
---------------------------------------------------------------------
FIRST_CHANGE # FIRST_TIME
---------------------------
1 1 68 52428800 1 NO INACTIVE
September 1949257-07
3 1 69 52428800 1 NO CURRENT
1959968--07
2 1 66 52428800 1 NO INACTIVE
September 1918631-07
If this log is inactive, clear the log.
SQL> alter database clear logfile group 2;
Alter database clear logfile group 2
*
Row 3 has an error:
ORA-00350: log 2 (instance orcl log, thread 1) needs to be archived
ORA-00312: Online log 2 thread 1:
F: ORACLEPRODUCT10.2.0ORADATAORCLREDO02. LOG
SQL> alter database clear unarchived logfile group 2;
The database has been changed.
At this point, the log is cleared. This time it should be okay. Start the database.
SQL> alter database open;
The database has been changed.
SQL>
OK, problem solving
Summary: status of the log file group
Current: Working Group currently in use
Inactive: inactive group
Active: archiving is not completed yet
Unused: Not used yet. Generally, This is the status of the newly created group.
Working Groups in active and current status cannot be deleted. It is only available after switching logs.
SQL> select open_mode from v $ database;
OPEN_MODE
----------
MOUNTED
SQL> alter database open;
Alter database open
*
Row 3 has an error:
ORA-16014: log 2 serial number 66 Unarchived, no available destination
ORA-00312: Online log 2 thread 1:
F: ORACLEPRODUCT10.2.0ORADATAORCLREDO02. LOG
It turns out that there is a log problem, which is better solved. Check the log status.
SQL> select * from v $ log;
GROUP # THREAD # SEQUENCE # BYTES MEMBERS ARC STATUS
---------------------------------------------------------------------
FIRST_CHANGE # FIRST_TIME
---------------------------
1 1 68 52428800 1 NO INACTIVE
September 1949257-07
3 1 69 52428800 1 NO CURRENT
1959968--07
2 1 66 52428800 1 NO INACTIVE
September 1918631-07
If this log is inactive, clear the log.
SQL> alter database clear logfile group 2;
Alter database clear logfile group 2
*
Row 3 has an error:
ORA-00350: log 2 (instance orcl log, thread 1) needs to be archived
ORA-00312: Online log 2 thread 1:
F: ORACLEPRODUCT10.2.0ORADATAORCLREDO02. LOG
SQL> alter database clear unarchived logfile group 2;
The database has been changed.
At this point, the log is cleared. This time it should be okay. Start the database.
SQL> alter database open;
The database has been changed.
SQL>
OK, problem solving
Summary: status of the log file group
Current: Working Group currently in use
Inactive: inactive group
Active: archiving is not completed yet
Unused: Not used yet. Generally, This is the status of the newly created group.
Working Groups in active and current status cannot be deleted. It is only available after switching logs.