This content has been marked as final. Show 4 replies
I've seen something like this where the OS mounts READ ONLY shutdown the database ( its probably down ) and hard boot and check the OS before attempting to start the standby.
Any chance the compatible parameter is different between the primary and standby?
Given the combination of errors I would probably get oracle support involved early.
All parameters were same as before.
The things that were changed are redo logs.
Before making standby flashback they were not there.
Now I can see them in $logs.
I'll update on this as soon as I'll reach site tomorrow.
Thanks & regards
Just try to open ur standby using open resetlogs
I have the same issue when using sqlplus, probably a bug. But it works fine when using rman:
SQL> SHUTDOWN IMMEDIATE;
ORACLE instance shut down.
SQL> STARTUP MOUNT;
ORACLE instance started.
Total System Global Area 314572800 bytes
Fixed Size 2083696 bytes
Variable Size 142607504 bytes
Database Buffers 163577856 bytes
Redo Buffers 6303744 bytes
SQL> FLASHBACK DATABASE TO SCN 17838032043;
rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Apr 10 14:14:36 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: XXXXXXXX (DBID=1514076400, not open)
RMAN> SQL 'ALTER DATABASE OPEN READ ONLY';
using target database control file instead of recovery catalog
sql statement: ALTER DATABASE OPEN READ ONLY
I found the answer here: