Today I encountered this issue while upgrading the database
Environments: Oracle 11g, ASM, RMAN backup dumps. During RMAN 10g database restoring into 11g database for upgrade, alter database open resetlogs or alter database open resetlogs upgrade command failed as below,
Cause:
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1: '/u404/oradata/DATA/log_3a.rdo'
ORA-00312: online log 3 thread 1: '/u405/oradata/DATA/log_3b.rdo'
Environments: Oracle 11g, ASM, RMAN backup dumps. During RMAN 10g database restoring into 11g database for upgrade, alter database open resetlogs or alter database open resetlogs upgrade command failed as below,
Cause:
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1: '/u404/oradata/DATA/log_3a.rdo'
ORA-00312: online log 3 thread 1: '/u405/oradata/DATA/log_3b.rdo'
SQL> alter database open resetlogs upgrade;
alter database open resetlogs upgrade
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1: '/u404/oradata/DATA/log_3a.rdo'
ORA-00312: online log 3 thread 1: '/u405/oradata/DATA/log_3b.rdo'
Solution:
Clear the logs as below for error log groups,
SQL> alter database clear unarchived logfile group 3;
Database altered.
Now you can proceed with,
SQL> alter database open resetlogs;
or
SQL> alter database open resetlogs upgrade;
alter database open resetlogs upgrade
*
ERROR at line 1:
ORA-00392: log 3 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 3 thread 1: '/u404/oradata/DATA/log_3a.rdo'
ORA-00312: online log 3 thread 1: '/u405/oradata/DATA/log_3b.rdo'
Solution:
Clear the logs as below for error log groups,
SQL> alter database clear unarchived logfile group 3;
Database altered.
Now you can proceed with,
SQL> alter database open resetlogs;
or
SQL> alter database open resetlogs upgrade;
No comments:
Post a Comment