Oracle Database Discussions

Hi all,

I'm hoping someone can help me out. I'm in the midst of trying to upgrade our performance environment to 11gR2. To mimic production, I have a physical standby setup in the perf environment. I've successfully upgraded clusterware and asm to 11g and was now going to perform the database upgrade. I've followed http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/upgrades.htm#CHDBJAGG which is rather simplistic in nature, but one would hope that's because this is to be a simple process. However, I'm unsure about the steps involved with the physical standby. Am I to install the 11g binaries, repoint the environment to use them and then put the db back into recovery mode, or should I instead install the binaries yet leave them at 10.2x for the duration of the dbua running on the primary and then repoint post upgrade?

The reason I ask is this; upon attempting to repoint to the 11g binaries and mounting the standby database I receive the following in my alert log:

SUCCESS: diskgroup DG1 was mounted
Spfile +DG1/perfrdb/spfileperfrdb.ora is in old pre-11 format and compatible >= 11.0.0; converting to new H.A.R.D. compliant format.
ERROR: failed to establish dependency between database perfrdb and diskgroup resource ora.DG1.dg
Errors in file /opt/oracle/diag/rdbms/perfrdb/perfrdb/trace/perfrdb_mmon_25110.trc (incident=36139):
ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [17505], [], [], [], [], [], [], [], [], [], []
ORA-17505: ksfdrsz:1 Failed to resize file to size 9 blocks
ORA-15061: ASM operation not supported [41]
Incident details in: /opt/oracle/diag/rdbms/perfrdb/perfrdb/incident/incdir_36139/perfrdb_mmon_25110_i36139.trc
Trace dumping is performing id=[cdmp_20100824175159]
Tue Aug 24 17:52:09 2010
alter database mount standby database
Tue Aug 24 17:52:09 2010
Restarting dead background process MMON
Tue Aug 24 17:52:09 2010
MMON started with pid=17, OS id=25136
Tue Aug 24 17:52:09 2010
SUCCESS: diskgroup DGBACK was mounted
Tue Aug 24 17:52:09 2010
ERROR: failed to establish dependency between database perfrdb and diskgroup resource ora.DGBACK.dg
ALERT: Compatibility of the database is changed from 10.2.0.3.0 to 11.1.0.0.0.
Errors in file /opt/oracle/diag/rdbms/perfrdb/perfrdb/trace/perfrdb_ora_25129.trc:
ORA-00202: control file: '+DG1/perfrdb/controlfile/current.271.727826011'
ORA-17505: ksfdrsz:1 Failed to resize file to size 1864 blocks
ORA-15061: ASM operation not supported [41]
Control file section 4 expansion from 1852 blocks to 1864 blocks due to record size increase denied by OS
Backup controlfile written to trace file /opt/oracle/diag/rdbms/perfrdb/perfrdb/trace/perfrdb_ora_25129.trc
ORA-217 signalled during: alter database mount standby database...
Tue Aug 24 17:52:57 2010

I had installed the July PSU for the database, but based on :
ORA-15061 reported while doing a file operation with 11.1 or 11.2 ASM after PSU applied in database home [ID 1070880.1] I rolled it back and applied patch 9778840 to both the grid infrastructure and db homes but with the same result.

I suspect I'm missing something very simple but I'm a bit stumped as to what. Of course if I need to leave the standby at 10g until after the upgrade of the primary that would explain it but somehow I don't think that's it.

Any help would be VERY much appreciated.

Cheers,
Chris