Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

switchover problem after upgrade from 11.2.0.1 to 11.2.0.2

karol.napiorkowskiJan 19 2011 — edited Jan 21 2011
Hello

I succesfull upgraded my database from 11.2.0.1 to 11.2.0.2 on my test enviroment.
My enviroment works with dataguard configuration.
Data Guard management is dgmgrl.
OS is Linux Redhat x86_64

I have problem with switchover operation:

During switchover operation (with dgmgrl) new primary database is switched succesfull but problem is with new standby database, I have message:
ORA-10458: standby database requires recovery
ORA-01194: datafile 1, needs more recovery to be consistent
ORA-01110: datafile 1: '/u01/app/oracle/oradata/DB1/system01.dbf'

To end switchover operation I should start new standby instance. But if i try startup It i have:
ORA-00845: MEMORY_TARGET not supported on this system

In alert log new standby database I have:
.
.
Completed: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN
Wed Jan 19 08:15:00 2011
Performing implicit shutdown abort due to switchover to physical standby
Shutting down instance (abort)
License high water mark = 20
USER (ospid: 13290): terminating the instance
Instance terminated by USER, pid = 13290
Wed Jan 19 08:15:02 2011
Instance shutdown complete
ORA-1092 : opitsk aborting process
Wed Jan 19 08:15:06 2011
Starting ORACLE instance (normal)
.
.
WARNING! Recovering data file 1 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 2 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 3 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 4 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command..
.
.
ARC9: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Media Recovery Log /u01/app/oracle/redologs2/archiveredolog/DB1/1_194_739556401.dbf
Identified End-Of-Redo for thread 1 sequence 194
Wed Jan 19 08:15:20 2011
Using STANDBY_ARCHIVE_DEST parameter default value as /u01/app/oracle/oradata/DB1/archivelog/
RFS[1]: Assigned to RFS process 13553
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 3536
Starting Data Guard Broker (DMON)
Wed Jan 19 08:15:21 2011
INSV started with pid=32, OS id=13555
RFS[1]: Selected log 4 for thread 1 sequence 197 dbid 1279411810 branch 739556401
Archived Log entry 44349 added for thread 1 sequence 197 ID 0x4f8d3d29 dest 1:
Archived Log entry 44350 added for thread 1 sequence 197 ID 0x4f8d3d29 dest 2:
Archived Log entry 44351 added for thread 1 sequence 197 ID 0x4f8d3d29 dest 3:
Wed Jan 19 08:15:24 2011
Resetting standby activation ID 0 (0x0)
Media Recovery End-Of-Redo indicator encountered
Media Recovery Applied until change 972405267
Completed standby crash recovery.
Errors in file /u01/app/oracle/diag/rdbms/tdb1nod1/DB1/trace/DB1_ora_13451.trc:
ORA-10458: standby database requires recovery
ORA-01194: plik 1, aby byl spojny, wymaga dalszego przywracania
ORA-01110: plik danych 1: '/u01/app/oracle/oradata/DB1/system01.dbf'
ORA-10458 signalled during: alter database open...
Wed Jan 19 08:15:25 2011
RFS[2]: Assigned to RFS process 13603
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 3532
Wed Jan 19 08:15:26 2011
RFS[3]: Assigned to RFS process 13619
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 3536
RFS[3]: Opened log for thread 1 sequence 196 dbid 1279411810 branch 739556401
Wed Jan 19 08:15:26 2011
RFS[4]: Assigned to RFS process 13617
RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 3534
Archived Log entry 44352 added for thread 1 sequence 196 rlc 739556401 ID 0x4f8d3d29 dest 4:
RFS[4]: Opened log for thread 1 sequence 195 dbid 1279411810 branch 739556401
Archived Log entry 44353 added for thread 1 sequence 195 rlc 739556401 ID 0x4f8d3d29 dest 4:
Wed Jan 19 08:15:29 2011
RFS[5]: Assigned to RFS process 13643
RFS[5]: Identified database type as 'physical standby': Client is LGWR ASYNC pid 7251
Primary database is in MAXIMUM PERFORMANCE mode
RFS[5]: Selected log 4 for thread 1 sequence 199 dbid 1279411810 branch 739556401
Wed Jan 19 08:15:30 2011
RFS[6]: Assigned to RFS process 13645
RFS[6]: Identified database type as 'physical standby': Client is ARCH pid 3536
RFS[6]: Selected log 5 for thread 1 sequence 198 dbid 1279411810 branch 739556401
Wed Jan 19 08:15:31 2011
Archived Log entry 44354 added for thread 1 sequence 198 ID 0x4f8d3d29 dest 1:
Archived Log entry 44355 added for thread 1 sequence 198 ID 0x4f8d3d29 dest 2:
Archived Log entry 44356 added for thread 1 sequence 198 ID 0x4f8d3d29 dest 3:
Wed Jan 19 08:15:45 2011
RFS[7]: Assigned to RFS process 13699
RFS[7]: Identified database type as 'physical standby': Client is ARCH pid 3532
Wed Jan 19 08:16:47 2011
RFS[7]: Assigned to RFS process 13699
RFS[7]: Identified database type as 'physical standby': Client is ARCH pid 3532
Wed Jan 19 08:16:47 2011
Starting ORACLE instance (normal)
WARNING: You are trying to use the MEMORY_TARGET feature. This feature requires the /dev/shm file system to be mounted for at least 2147483648 bytes. /dev/shm is either not mounted or is mounted with available space less than this size. Please fix this so that MEMORY_TARGET can work as expected. Current available is 1586806784 and used is 3781902336 bytes. Ensure that the mount point is /dev/shm for this directory.
memory_target needs larger /dev/shm
Wed Jan 19 08:30:17 2011
db_recovery_file_dest_size of 102400 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

It is look like the instance proseses was not shutdown during operation shutdown abort.
If I connect to instance with sqlplus i have message:
Connected with idle instance

Proceses are still active.
Output linux statement ps -aux | grep oracle:
root 13032 0.0 0.0 88060 3248 ? Ss 08:13 0:00 sshd: oracle [priv]
oracle 13039 0.0 0.0 88060 1860 ? S 08:13 0:00 sshd: oracle@pts/1
oracle 13040 0.0 0.0 68248 1676 pts/1 Ss 08:13 0:00 -bash
oracle 13402 0.0 0.3 2328080 22220 ? Ss 08:15 0:00 ora_pmon_DB1
oracle 13404 0.0 0.2 2325832 15536 ? Ss 08:15 0:00 ora_vktm_DB1
oracle 13408 0.0 0.2 2325832 15584 ? Ss 08:15 0:00 ora_gen0_DB1
oracle 13412 0.0 0.2 2325832 15468 ? Ss 08:15 0:00 ora_diag_DB1
oracle 13414 0.0 0.2 2325832 15584 ? Ss 08:15 0:00 ora_dbrm_DB1
oracle 13416 0.0 0.2 2325832 15680 ? Ss 08:15 0:00 ora_psp0_DB1
oracle 13419 0.1 0.4 2327368 25688 ? Ss 08:15 0:08 ora_dia0_DB1
oracle 13422 0.0 0.8 2325832 49152 ? Ss 08:15 0:02 ora_mman_DB1
oracle 13425 0.0 0.4 2332100 27344 ? Ss 08:15 0:00 ora_dbw0_DB1
oracle 13427 0.0 0.2 2325832 16648 ? Ss 08:15 0:00 ora_lgwr_DB1
oracle 13432 0.0 0.3 2325832 21524 ? Ss 08:15 0:00 ora_ckpt_DB1
oracle 13434 0.0 0.2 2325832 17600 ? Ss 08:15 0:00 ora_smon_DB1
oracle 13436 0.0 0.2 2325832 15604 ? Ss 08:15 0:00 ora_reco_DB1
oracle 13438 0.0 0.4 2326468 27976 ? Ss 08:15 0:00 ora_mmon_DB1
oracle 13440 0.0 0.3 2325832 22120 ? Ss 08:15 0:00 ora_mmnl_DB1
oracle 13442 0.0 0.2 2331932 15764 ? Ss 08:15 0:00 ora_d000_DB1
oracle 13444 0.0 0.2 2326896 14784 ? Ss 08:15 0:00 ora_s000_DB1
oracle 13447 0.0 0.2 2325852 16628 ? Ss 08:15 0:00 ora_dmon_DB1
oracle 13527 0.0 0.8 2357896 48984 ? Ss 08:15 0:00 ora_arc0_DB1
oracle 13530 0.0 0.5 2341496 31832 ? Ss 08:15 0:00 ora_arc1_DB1
oracle 13532 0.0 0.8 2359596 50968 ? Ss 08:15 0:00 ora_arc2_DB1
oracle 13534 0.0 0.7 2357896 48844 ? Ss 08:15 0:00 ora_arc3_DB1
oracle 13536 0.0 0.8 2357896 48860 ? Ss 08:15 0:00 ora_arc4_DB1
oracle 13538 0.0 0.5 2341384 31524 ? Ss 08:15 0:00 ora_arc5_DB1
oracle 13540 0.0 0.5 2341384 31536 ? Ss 08:15 0:00 ora_arc6_DB1
oracle 13542 0.0 0.5 2341384 31536 ? Ss 08:15 0:00 ora_arc7_DB1
oracle 13545 0.0 0.5 2341384 31536 ? Ss 08:15 0:00 ora_arc8_DB1
oracle 13547 0.0 0.5 2341384 31536 ? Ss 08:15 0:00 ora_arc9_DB1
oracle 13555 0.0 0.2 2325852 16168 ? Ss 08:15 0:00 ora_insv_DB1
root 18288 0.0 0.0 88060 3240 ? Ss 08:30 0:00 sshd: oracle [priv]
oracle 18290 0.0 0.0 88200 2012 ? S 08:30 0:00 sshd: oracle@notty
oracle 18291 0.0 0.0 54004 2232 ? Ss 08:30 0:00 /usr/libexec/openssh/sftp-server
oracle 18336 0.0 0.2 87132 13336 ? Ssl 08:41 0:00 /u01/app/oracle/product/11.2.0/db_2/bin/tnslsnr LISTENER -inherit
oracle 18607 0.1 0.6 2350168 39972 ? Ss 09:37 0:00 oracleDB1 (LOCAL=NO)
oracle 18609 0.1 1.4 2395944 85880 ? Ss 09:37 0:00 oracleDB1 (LOCAL=NO)
oracle 18611 0.0 0.5 2346216 36100 ? Ss 09:37 0:00 oracleDB1 (LOCAL=NO)
oracle 18615 0.1 0.2 2331228 18136 ? Ss 09:38 0:00 oracleDB1 (LOCAL=NO)
oracle 18617 0.1 0.3 2332184 21508 ? Ss 09:38 0:00 oracleDB1 (LOCAL=NO)
oracle 18619 0.0 0.0 65556 940 pts/1 R+ 09:38 0:00 ps -aux
oracle 18620 0.0 0.0 61160 736 pts/1 S+ 09:38 0:00 grep oracle

Shared memory is still allocated for instance:
df -h /dev/shm

System plików rozm. użyte dost. %uż. zamont. na
tmpfs 5,0G 2,0G 3,1G 39% /dev/shm

Please for help.
Regards
Karol

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Feb 18 2011
Added on Jan 19 2011
7 comments
529 views