Hello.
I'm trying to upgrade a primary and physical standby database from 11.2.0.1 to 11.2.0.2 on Linux (64 bit). The databases are on seperate, but identical (in terms of their config) servers. Data Guard is facilitating the synch.
I should add, that I've deviated slightly from the recommended way of upgrading with this configuration (http://docs.oracle.com/cd/E11882_01/server.112/e25608/upgrades.htm), and instead have decided to upgrade the primary first, and make sure it works before synching to the standby. Not my call, but the rationale for this is that it was deemed too risky, so it seemed sensible at the time.
BVCLONE = primary
BVCLONBY = physical standby
The upgraded primary database works fine.
I then installed the db software in a new ORACLE_HOME on the standby server.
Then mounted the physical standby
Then started redo apply on the physical standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
I then made sure that DG was happy:
DGMGRL> show database bvclonby
Database - bvclonby
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: OFF
Instance(s):
bvclonby
Database Status:
SUCCESS
But now I can't open the standby database:
SQL> alter database open read only;
alter database open read only
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Process ID: 20247
Session ID: 11 Serial number: 3
Now, that error message doesn't make sense as it implies running the upgrade scripts on the standby.
and in any case, if I do try and startup in upgrade mode, I get this:
SQL> startup upgrade
ORACLE instance started.
Total System Global Area 4175568896 bytes
Fixed Size 2233088 bytes
Variable Size 1962937600 bytes
Database Buffers 2181038080 bytes
Redo Buffers 29360128 bytes
Database mounted.
ORA-16003: standby database is restricted to read-only access
which I'd expect to see.
I've checked that both databases have the same version number: 11.2.0.2:
standby:
SQL> show parameter db_unique_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_unique_name string BVCLONBY
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
Primary:
SQL> show parameter db_unique_name
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_unique_name string BVCLONE
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
It seems like a no-win scenario. On one hand, you can only open in upgrade mode, on the other, you can only open in read only mode! Of course, I've considered (and am looking into) the possibility that Oracle's error messages are pretty misleading and the problem could be something else completely.
But if anyone has any ideas about what's going on here, I'd be very grateful of you could let me know.
Thanks,
Ray