Not abe to open the database after logging in SYS user
Hi Team,
Iam running Oracle 11g r2 database , Iam getting the below error when I try to login into the database. Iam new to Oracle DBA .
I tried logging in as below and run the below command
sqlplus / as sysdba
sql> alter database orcl open;
I get the below error
rror starting at line 1 in command:
alter database orcl open
Error report:
SQL Error: ORA-00355: change numbers out of order
ORA-00353: log corruption near block 9972 change 57969482 time 01/28/2020 17:08:22
ORA-00312: online log 1 thread 1: 'E:\APP\oracomp\ORADATA\OR
00355. 00000 - "change numbers out of order"
*Cause: A change number found in the redo log is lower than a previously
encountered change number. The log is corrupted in some way. The
corruption may be at the earlier change or at this one.
*Action: Do recovery with a good version of the log or do time based
recovery up to the indicated time.
Kindly let me know what is the solution for this error and cause of the error. Any help is really appreciated
Iam running Oracle 11g r2 database , Iam getting the below error when I try to login into the database. Iam new to Oracle DBA .
I tried logging in as below and run the below command
sqlplus / as sysdba
sql> alter database orcl open;
I get the below error
rror starting at line 1 in command:
alter database orcl open
Error report:
SQL Error: ORA-00355: change numbers out of order
ORA-00353: log corruption near block 9972 change 57969482 time 01/28/2020 17:08:22
ORA-00312: online log 1 thread 1: 'E:\APP\oracomp\ORADATA\OR
00355. 00000 - "change numbers out of order"
*Cause: A change number found in the redo log is lower than a previously
encountered change number. The log is corrupted in some way. The
corruption may be at the earlier change or at this one.
*Action: Do recovery with a good version of the log or do time based
recovery up to the indicated time.
Kindly let me know what is the solution for this error and cause of the error. Any help is really appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a lot
Can you tell us what you did, or what you found, to solve this? That may help others who see this question.
Also this error was *NOT* caused by you logging in as SYS. That login simply allowed you to see this error message. The actual error happened earlier. If you want us to be able to help you, you will have to tell us what happened earlier in this system.
Or, if this is a production database, you will likely need to follow Franck’s advice above.