Why process 'timestenrepd' on the standby database keep consuming 600% CPU?

Hi all, I have just created a empty active standby pair where there are 14 regular AWT cache groups.
After call of ttRepStart on the standby database, it takes 600% CPU(24 cores CPU) all the time.
There is no data in the cache groups and I found the error logs in the tterrors.log file:
14:01:28.32 Warn: : 27703: 27710/0xf83c50: Recovery started
14:01:31.62 Warn: : 27703: 27710/(nil): Another checkpoint is in progress. The final checkpoint will continue when the other checkpoint finishes.
14:01:44.96 Warn: REP: 25580: [139865850070784, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'FAILOVER' (context 0x7f2f580008c0) starting
14:01:44.97 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPLISTENER' (context 0x7f2f600008c0) starting
14:01:44.97 Warn: REP: 25580: [139865846920960, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'XLA_PARENT' (context 0x7f2f680008c0) starting
14:01:44.97 Warn: REP: 25580: [139865853220608, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'REPHOLD' (context 0x7f35040008c0) starting
14:01:45.04 Warn: REP: 25580: [139865840621312, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'LOGFORCE' (context 0x7f3500000c50) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f540008c0) starting
14:01:45.04 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 0 got repSlave object 0x5406d9a0
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(M)' (context 0x7f2f500008c0) starting
14:01:45.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 0 got repSlave object 0x5006d9a0
14:01:45.05 Warn: REP: 25580: [139865834321664, 0, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.12 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:45.13 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:45.13 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f400008c0) starting
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 1 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841657100032, 1, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f3c0008c0) starting
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 15530743840010091109, track id 2 got repSlave object 0x5406d9a0
14:01:45.76 Warn: REP: 25580: [139841660249856, 2, noAwt] EPPDB:transmitter.c(1434): TT16999: Transmitter connecting to receiver
14:01:46.15 Err : REP: 25580: [139841666549504, 0, noAwt] EPPDB:meta.c(3134): TT16999: receiver slot alloc: 16289484001462337649 15530743840010091109
14:01:46.15 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:46.46 Warn: : 27703: 25580/0x7f2f400008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:46.83 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:46.83 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f340008c0) starting
14:01:46.83 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:47.04 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600888.3 with prev as 0 hdr.firstCTN 1354600888.2expectedCTN=1354600888.2
14:01:47.05 Warn: : 27703: 25580/0x7f2f540008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:47.43 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:47.43 Warn: REP: 25580: [139840591431424, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f200008c0) starting
14:01:47.43 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.46 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. select() timed out isAwt (false) parallelism (3) trackId (0) socket (17)
14:01:48.46 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 0) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (1) socket (19)
14:01:48.66 Warn: REP: 25580: [139840591431424, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 1) set to 1
14:01:48.66 Err : REP: 25580: [139841522874112, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841522874112, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139840591431424, 1, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(3112): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:receiver.c(3113): TT16060: Failed to read data from the network. TimesTen replication receivers are stopping isAwt (false) parallelism (3) trackId (2) socket (23)
14:01:48.66 Warn: REP: 25580: [139841526023936, -1, notKnown] EPPDB:receiver.c(1829): TT16999: stopRcvrThreads (track 2) set to 1
14:01:48.66 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(1870): TT16999: stopRcvrThreads (track 0) set to 0
14:01:48.66 Err : REP: 25580: [139840594581248, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Err : REP: 25580: [139841663399680, 0, noAwt] EPPDB:receiver.c(1657): TT16275: RECEIVER network helper thread terminating due to certain error already recorded in the system log
14:01:48.66 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841526023936, 2, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:48.66 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1276): TT16999: Receiver exiting isAwt (false)
14:01:49.05 Warn: REP: 25580: [139865837471488, 0, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:49.05 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:49.05 Warn: REP: 25580: [139841666549504, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f480008c0) starting
14:01:49.06 Warn: REP: 25580: [139841526023936, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context 0x7f2f00000000) starting
14:01:49.22 Warn: : 27703: 25580/0x7f2f3c0008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:01:50.17 Warn: REP: 25580: [139841666549504, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:53.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:53.54 Warn: REP: 25580: [139841663399680, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2f440008c0) starting
14:01:53.54 Warn: REP: 25580: [139840594581248, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f200008c0) starting
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 2 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139840591431424, 2, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.20 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'TRANSMITTER(S)' (context 0x7f2f180008c0) starting
14:01:54.20 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1112): TT16285: Replication transmitter with local store id 16289484001462337649, remote store id 2679021640115572251, track id 1 got repSlave object 0x5006d9a0
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f080008c0) starting
14:01:54.20 Warn: REP: 25580: [139841533159168, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #4 started
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef40008c0) starting
14:01:54.20 Warn: REP: 25580: [139841405417216, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #1 started
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2efc0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841530009344, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #3 started
14:01:54.21 Warn: REP: 25580: [139841522874112, 1, noAwt] EPPDB:transmitter.c(1425): TT16999: Awt transmitter connecting to receiver
14:01:54.21 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2ef80008c0) starting
14:01:54.21 Warn: REP: 25580: [139841402267392, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #0 started
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f040008c0) starting
14:01:54.21 Warn: REP: 25580: [139841536308992, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #5 started
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_SORTER' (context 0x7f2f0c0008c0) starting
14:01:54.21 Warn: REP: 25580: [139841539458816, 0, Awt] EPPDB:awt.c(144): TT16999: Parallel AWT Sorter started
14:01:54.21 Warn: REP: 25580: [139841399117568, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2eec0008c0) starting
14:01:54.22 Warn: REP: 25580: [139841392817920, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841395967744, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ef00008c0) starting
14:01:54.22 Warn: REP: 25580: [139841389668096, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:repagent.c(1227): TT16025: Thread 'AWT_APPLIER' (context 0x7f2f000008c0) starting
14:01:54.22 Warn: REP: 25580: [139841408567040, 0, Awt] EPPDB:awt.c(210): TT16999: Parallel AWT Applier #2 started
14:01:55.87 Warn: REP: 25580: [139841663399680, -1, notKnown] EPPDB:receiver.c(4350): TT16999: stopRcvrThreads (track 0) set to 0
14:01:56.54 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:56.55 Warn: REP: 25580: [139841182365440, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ed80008c0) starting
14:01:56.55 Warn: REP: 25580: [139841179215616, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600759.70 with prev as 63 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600888.2 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:01:56.89 Warn: : 27703: 25580/0x7f2f180008c0: XXX:1st CTN for track 1 was 1354600894.2 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
14:01:57.26 Warn: REP: 25580: [139865843771136, 0, noAwt] EPPDB:receiver.c(2263): TT16999: RepListner succesfully done spawning a receiver
14:01:57.27 Warn: REP: 25580: [139841176065792, 0, noAwt] EPPDB:repagent.c(1227): TT16025: Thread 'RECEIVER' (context 0x7f2ecc0008c0) starting
14:01:57.27 Warn: REP: 25580: [139841172915968, 0, noAwt] EPPDB:repagent.c(1231): TT16025: Thread 'RECEIVERNET' (context (nil)) starting
14:01:57.90 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600759.71 with prev as 68 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600759.69 with prev as 64 hdr.firstCTN 1354600759.69expectedCTN=1354600759.69
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600888.1 with prev as 4294967295 hdr.firstCTN 1354600888.1expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f200008c0: XXX:1st CTN for track 2 was 1354600894.11 with prev as 4294967295 hdr.firstCTN 1354600894.11expectedCTN=1354600894.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600888.0 with prev as 4294967295 hdr.firstCTN 1354600888.0expectedCTN=1354600888.0
14:02:04.08 Warn: : 27703: 25580/0x7f2f500008c0: XXX:1st CTN for track 0 was 1354600894.0 with prev as 4294967295 hdr.firstCTN 1354600894.0expectedCTN=1354600894.0
Please note that this is a newly active standby pair where there is no data or workload while the problem occurs, it makes me very depressed.

Ok, Chirs, here are my steps to set up the active stnadby pair:
1.steps on the active database:
% ttIsql eppdb;
command> @init_user_grant.sql
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
command> call ttCacheUidPwdSet('cacheuser','oracle');
command> call ttGridCreate('myGrid');
command> call ttGridNameSet('myGrid');
command> call ttCacheStart;
command> @create_all_cache_groups.sql
command>
CREATE ACTIVE STANDBY PAIR eppdb ON "baal", eppdb ON "diablo"
RETURN TWOSAFE
STORE eppdb ON "baal" DISABLE RETURN ALL 5 RESUME RETURN 20
STORE eppdb ON "diablo" DISABLE RETURN ALL 5 RESUME RETURN 20;
command>call ttRepStart;
command>call ttRepStateSet('active');
command>@load_cache_groups.sql
command>exit
2.steps on the standby database:
% ttRepAdmin -duplicate -from eppdb -host "baal" -uid cacheuser -pwd timesten -cacheuid cacheuser -cachepwd oracle -keepCG eppdb
% ttIsql "DSN=eppdb;UID=cacheuser;PWD=timesten;OraclePWD=oracle"
Command> CALL ttCacheUidPwdSet('cacheuser','oracle');
Command> CALL ttCacheStart;
Command> CALL ttRepStart;
After the replication agent is started on the standby database, issuing a 'top' command in the bash on the standby database server,
I can see the process 'timestenrepd' consumes 600%+ CPU all the time except for stopping the replication agent.

Similar Messages

Client process (uniengd) on the Calendar server is consuming 100% CPU usage

The Calendar client bits in the Communicator 4.5 release (Calendar Build 981008)
are suspect of hanging the Calendar server when the end user uses the off-line
feature. The behavior seen will be that a cpu will start climbing and could
reach 80-100% of usage, which will cause the response time for all other end
users to be extremely slow and may not even accept any new logins.

The patch for these bits is available via the Smart Update (Windows and Mac) web
site:

http://home.netscape.com/smartupdate/su1_40.html
 Or you can download the complete version from
http://home.netscape.com/download/selectplatform_1_361.html

For Unix platforms, you will need to download the compressed tar file
(available from http://help/filelib.html#nscal)
and reinstall it.
NOTE: To verify that you are executing a patched version, in the
Calendar client:
Windows platform
 Help menu pulldown, About Netscape Calendar, make sure it has Build
981104 or higher.
 Mac platform
 Select the file from your desktop
 File menu pulldown, Get Info. Make sure has a date of 121698, version
4.51 or later.
 Unix platform
 Help menu pulldown, About Netscape Calendar, make sure it has is Version
4.51 or higher

The procedure for determining which user of Calendar is causing the server's cpu
hang is as follows:
<OL>
<LI>Using your favorite monitoring tool on the server, note the PID
 (process ID) of the uniengd process that is consuming
80 - 100% cpu activity.
<LI>Change directory to /users/unision/db/tmp/PID#
<LI>Execute the command "strings" on all the files in the directory
 (there are usually not very many):

 # strings *

 Near the end of the output, you will see the user's name.
<LI>You can now kill the uniengd process on the server:

 # kill PID# (note: do not use the kill -9 unless absolutely
 necessary!)

<LI>Contact the name of the user whose process you looked up and determine
 what version of Calendar client they are using. Immediately inform
 them of your procedure on upgrading to the correct version.
</OL>

Hi TrondWH,
Thanks for contacting Microsoft.
Currently, would you please try cleaning boot the server and test how the issue goes. Cleaning boot can exclude some third-party application affect. Following are the detailed steps about clean boot:
Log on to the computer by using an account that has administrator rights.
Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the
 System Configuration Utility.
On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
Click OK, Choose Don’t show this message again and then click Restart.
Please check if the issue is still the same.
Please let me know the result.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Bounce the standby database

Hello,
I am using oracle10g with standby database. Here is the database version.
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for Linux: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - Production
Now i want to increase the number of process in primary database. Primary needs downtime. But in this circumstances, should i bounce the standby?
Let me put all my questions here.
1. Should i bounce the standby at this scenario?
2. Here are the commands and sequence of steps to shutdown and start the database. Please correct me if i am wrong....
2a) shutdown the standby database first. (run this command in secondary)
connect / as sysdba
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL>shutdown immediate
2b) shutdown the primary(run this command in primary)
SQL> ALTER SYSTEM SET PROCESS=999 SOPE=spfile;
SQL> SHUTDOWN IMMEDIATE
2c) startup the primary
SQL> STARTUP
2d) Start the secondary database
connect / as sysdba
startup nomount
ALTER DATABASE MOUNT STANDBY DATABASE;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
3) After start the database, how do i ensure, primary is shipping the archivelog to secondary?
Any help is highly appreciated...

+1. Should i bounce the standby at this scenario?+
Not required.
+2. Here are the commands and sequence of steps to shutdown and start the database. Please correct me if i am wrong....+
+2a) shutdown the standby database first. (run this command in secondary)+
connect / as sysdba
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL>shutdown immediate
+2b) shutdown the primary(run this command in primary)+
SQL> ALTER SYSTEM SET PROCESS=999 SOPE=spfile;
SQL> SHUTDOWN IMMEDIATE
+2c) startup the primary+
SQL> STARTUP
+2d) Start the secondary database+
connect / as sysdba
startup nomount
ALTER DATABASE MOUNT STANDBY DATABASE;------------------------------------------------------------------------------
You can just mount
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
+3) After start the database, how do i ensure, primary is shipping the archivelog to secondary?+
Check the alert log on the standby.
Instead you need not shut down the standby at all.
Edited by: user13403205 on Aug 31, 2010 9:04 AM

Recover the standby database

Hi, I have both primary and standby database in ASM and I need to recover the standby database as it's falling behind for too long. The steps I did are:
1. backup full database on primary
2. create a standby controlfile and copy to /tmp on the standby
3. on the standby, RMAN>restore standby controlfile from '/tmp/std.ctl';
4. RMAN>restore database;
5. SQL>recover managed standby database disconnect;
However, the recovery always shuts down and I get the error:
ORA-01110: data file 1: '+W08_DATA_DG/w08p/datafile/system.295.662256331'
What's wrong with my steps?
Your suggestion is greatly appreciated!

the directory structures are the same. The standby was working before. It's just falling behind so I want to restore it from the new backup. Here is the init.ora
*.audit_file_dest='/opt/app/oracle/admin/W08P/adump'
*.background_dump_dest='/opt/app/oracle/admin/W08P/bdump'
*.cluster_database_instances=2
*.cluster_database=false
*.compatible='10.2.0.3.0'
*.control_files='+W08_DATA_DG/w08p/control01.ctl','+W08_RECOVERY_DG/w08p/control02.ctl','+W08_DATA_DG/w08p/control03.ctl'
*.core_dump_dest='/opt/app/oracle/admin/W08P/cdump'
*.db_block_size=8192
*.db_create_file_dest='+W08_DATA_DG'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='W08P'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=W08PXDB)'
*.event='10298 trace name context forever, level 32'
*.job_queue_processes=10
*.log_archive_dest_1='LOCATION=+W08_RECOVERY_DG/W08P/'
*.log_archive_format='%t_%s_%r.arc'
*.log_archive_max_processes=6
*.open_cursors=1000
*.optimizer_index_caching=70
*.optimizer_index_cost_adj=30
*.pga_aggregate_target=1459617792
*.processes=300
*.remote_login_passwordfile='exclusive'
*.sessions=1000
*.sga_target=1610612736
*.undo_management='AUTO'
*.undo_retention=26000
W08P.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/opt/app/oracle/admin/W08P/udump'
standby_archive_dest='LOCATION=+W08_RECOVERY_DG/W08P'
CONTROL_FILE_RECORD_KEEP_TIME=0
standby_file_management=auto
fal_server=w08p
fal_client=w08p_stby
control_file_record_keep_time=90
~

How to monitor the successful archive log shipment to the standby database

Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.

watson2011 wrote:
Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.You can troubleshoot standby by views as
v$managed_standby (standby)
v$dataguard_status
v$dataguard_stats
Some of the new views are introduced from 11g, check below link too
http://docs.oracle.com/cd/B28359_01/server.111/b28294/views.htm#i79129

Add a new datafile to the standby database

Hi,
i have a standby database in recovery managed mode.
Now i must add a new datafile on the production database and i would like
to know how i realized adding the new datafile on the stanby database.
is it right when i do the follow steps?
Before i add a datafile to the primary database,
cancel the recovery on the standby database.
-> add the new datafile on the primary database
after all archived redo logs have been applied, cancel managed recovery:
alter database recover managed standby database cancel;
startup nomount
alter database mount standby database;than
ALTER DATABASE CREATE DATAFILE '/oracle/DB1/db1_9/data9' as '/oracle/DB1/db1_9/data9';
alter database recover managed standby database disconnect;Thanks

8.4.1.1 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to AUTO
The following example shows the steps required to add a new datafile to the primary and standby databases when the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Archive the current redo log so it will get copied to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Verify that the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/t_db1.dbf
/disk1/oracle/dbs/t_db2.dbf
Verify that the new datafile was added to the standby database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/s2t_db1.dbf
/disk1/oracle/dbs/s2t_db2.dbf
8.4.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Verify that the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/t_db1.dbf
/disk1/oracle/dbs/t_db2.dbf
Perform the following steps to copy the tablespace to a remote standby location:
Place the new tablespace offline:
SQL> ALTER TABLESPACE new_ts OFFLINE;
Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time that the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
% cp t_db2.dbf s2t_db2.dbf
Place the new tablespace back online:
SQL> ALTER TABLESPACE new_ts ONLINE;
Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
%rcp s2t_db2.dbf standby_location
Archive the current redo log on the primary database so it will get copied to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Use the following query to make sure that managed recovery is running. If the MRP or MRP0 process is returned, managed recovery is being performed.
SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
Verify that the datafile was added to the standby database after the redo log was applied to the standby database.
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/s2t_db1.dbf
/disk1/oracle/dbs/s2t_db2.dbf
From Oracle Docs...

Apply all ArchiveLogs manually to the Standby Database

Hi,
we can create a Physical Standby Database on Standard Edition, but we have to transfer and apply all ArchiveLogs manually to the Standby Database. How can we do this ?
many thanks

Thank you, but I opened a SR and asked :
1-can we install DATAGUARD (Primary and Standby) with STANDARD edition ?
many thanks.
they answered :
DataGuard is not available with Standard Edition. You need to have the Enterprise Edition in
stalled on the Primary and Standby Host. The Standard Edition only provides basi
c Standby Database without Log Transport and Log Apply Services. So you can create a Physical Standby Database on Standard Edition, but you have to transfer and apply all ArchiveLogs manually to the Standby Database.
that's why I asked you the question.
What is the exact synatx for recover database using backup control file please ?
Thanks again.

Issue in creating the standby database from Active database using RMAN

Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.

Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN

Problem with the standby database?

i am working on 10gr2 on rhel4.
i am creating a standby database on the same servr machine.
i have taken a cold backup of the primary database and edited the parameter files for the primary as well as the standby database.
the only problem is that i am unable to open the standby database in the read only mode. following is the problem:
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/data02/logical_stdby/prdbs02sb/oradata/system01.dbf
thanks

if i issue this command on the primary database, i get
SQL> select status, error from v$archive_Dest where dest_id=2;
STATUS ERROR
ERROR ORA-01031: insufficient privileges
what is the reason, my logs are not propagating to the standby.
also some entries from the primary alert log file is as below:
Thu Oct 4 15:19:26 2007
Errors in file /opt/db/oracle/admin/prdbs02/bdump/prdbs02_arc1_17509.trc:
ORA-01031: insufficient privileges
PING[ARC1]: Heartbeat failed to connect to standby 'PRDBS02SB'. Error is 1031.
what is the reason??? please let me know if anything else is required for troublshooting

How to find the timestamp and SCN in the standby database?

Hai,
I have Oracle 9.2.0.4 RAC with 2 nodes in the production. The logs generated at these servers will be manully moved to my standby database and will be applied. To know what isthe maximum log files applied in the standby database, i am using the below mentioned query in the standby database,
Select thread#,max(sequence#) from v$log_history group by thread#
In general i am using "recover standby database until cancel" command and then checking the database with the above mentioned query whether all the logs are applied or not.
If i use time based or scn based recovery in standby database i.e., "recover standby database until time <time>" or "recover standby database until change <scn number>" , after completion of the recovery, apart from the message "Media recovery complete" or by seeing the alert log, is there any way to query the standby database, so that i can identify the time or scn upto which the archived redo log files got applied.

Hi Sridhar,
There should be some view which will have applied_scn information. There is one more option i can suggest, you can create a heart beat table in production with 2 column like scn and timestamp. Update this table every minute. From standby db you can query this table and get fair idea on applied_scn and timestamp.
While exporting you can export using flashback_scn by taking the value from heartbeat table of standby.
This heartbeat table is used very common in streams environment. Just see if this helps you.
hth,
http://borndba.com

I got the above error while i restore the standby database using RMAN backu

Dear All,
RMAN> crosscheck archivelog all;
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
Help need.i take the backup without catalog database.
regards,
DB

rman> list backup;
it shows lengthier but i showed only the corresponding
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3479    Full    17G        DISK        01:29:42     09-FEB-13
        BP Key: 3479   Status: AVAILABLE   Tag: 09FEB13_FULL_ESMSRV1_DB
        Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3479
File LV Type Ckp SCN    Ckp Time Name
1       Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
2       Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3       Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4       Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5       Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
6       Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7       Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8       Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9       Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
10      Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23      Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39      Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3480    Full    17G        DISK        01:21:30     09-FEB-13
        BP Key: 3480   Status: EXPIRED   Tag: TAG20130209T200021
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3480
File LV Type Ckp SCN    Ckp Time Name
1       Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
2       Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3       Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4       Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5       Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
6       Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7       Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8       Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9       Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
10      Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23      Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39      Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3481    Full    4M         DISK        00:00:03     09-FEB-13
        BP Key: 3481   Status: AVAILABLE   Tag: TAG20130209T212205
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
Controlfile Included: Ckp SCN: 1759462488   Ckp time: 09-FEB-13
BS Key Type LV Size       Device Type Elapsed Time Completion Time
3482    Full    0          DISK        00:00:01     09-FEB-13
        BP Key: 3482   Status: AVAILABLE   Tag: TAG20130209T212212
        Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
SPFILE Included: Modification time: 08-FEB-13
ls -l /oradatabkp
root@drsrv1#ls -l /oradatabkp
total 1108672
drwxr-xr-x   2 ovsd       dba             96 Sep 27 2009 alert_bkp
-rw-r--r--   1 oracle     dba            195 Mar 15 2007 create.sql
drwxr-xr-x   2 oracle     dba           8192 Aug 7 2009 ctrl_bkp
-rw-r--r--   1 root       sys        565114880 Apr 24 2007 drsrv1.tar
drwxrwxrwx   2 root       sys             96 Jun 17 2011 drsrv2-ignitebkp
drwxr-xr-x   4 root       sys             96 Apr 24 2007 esmsrv1
-rw-r-----   1 root       sys        1613824 Feb 22 2007 esmsrv1stby.ctl
-rw-r--r--   1 esmsrv1    dba           5120 Dec 31 2009 esmtables.dmp
-rw-r--r--   1 esmsrv1    dba            538 Dec 31 2009 esmtables.log
drwxrwxrwx   4 root       sys           8192 Mar 10 2009 export
drwxr-xr-x   8 root       sys           8192 Apr 24 2007 finalbackup
-rw-r--r--   1 oracle     dba           3820 Sep 5 2008 invalid.sql
-rw-r--r--   1 esmsrv1    dba         303104 Dec 31 2009 kirdevports.dmp
-rw-r--r--   1 esmsrv1    dba            591 Dec 31 2009 kirdevports.log
drwxr-xr-x   2 root       root            96 Feb 12 2007 lost+found
-rw-r--r--   1 oracle     dba          24954 Aug 9 2009 ovcontrol-090909.ctl
drwxr-xr-x 22 root       sys           8192 Apr 24 2007 ovpi
drwxr-xr-x   2 oracle     dba           8192 Aug 7 2009 pfile_bkp
drwxrw-rw-   4 oracle     dba           8192 Feb 10 15:25 rman
drwxr-xr-x 28 root       sys           8192 Feb 1 17:15 schedbkp
drwxr-xr-x   2 oracle     dba           8192 Jul 11 2011 sdnnm
-rw-r--r--   1 esmsrv1    dba           2196 Dec 31 2009 srirdevports.log
drwxr-xr-x   2 oracle     dba             96 Mar 13 2009 statsreport
-rw-r--r--   1 oracle     dba            966 Mar 15 2007 tbs.sql
drwxr-xr-x   5 oracle     dba             96 Mar 16 2007 testov
drwxr-xr-x   2 root       sys         442368 Mar 11 2009 trendadm_files
root@drsrv1#ls -l /oradatabkp/rman
total 37244448
drwxr-xr-x   2 oracle     dba           8192 Feb 10 15:25 esmsrv1
-rw-r-----   1 oracle     dba        19068198912 Feb 9 14:21 esmsrv1_full_db_09feb13
drwxrw-rw-   2 oracle     dba           8192 Feb 9 21:36 openview
-rw-r--r--   1 oracle     dba         920442 Feb 9 21:37 rmanbkp-all.log

Standby redologs in the standby database

Hi All,
I am preparing the standby database using RMAN creation steps. I am confusing in one area. I have standby redologs in the Primary server. When we issue the duplicate target database for standby dorecover nofilenamecheck command, is it create the standby redologs in the standby database or not ?
please cofirm
Thanks
Shiju

Hi,
no, you must to create standby redo logs manually.
This script may help you
select 'alter database add standby logfile '''||
regexp_substr(MEMBER,'/.+/')||'stdby_'||
regexp_replace(member,regexp_substr(MEMBER,'/.+/'),'')||
''' size '||bytes||';' "Create Standby redo"
from v$logfile lf , v$log l
where l.group# = lf.group#
union all
select 'alter database add standby logfile '''||
regexp_substr(MEMBER,'/.+/')||'stdby_redo0'||(select max(group#)+1 from v$log)||'.rdo'||
''' size '||bytes||';' "Create Standby redo"
from v$logfile lf , v$log l
where l.group# = lf.group#
and rownum <=2
Create Standby redo
alter database add standby logfile '/oracle/redo/prod1/stdby_redo03a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo03b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo02a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo02b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo01a.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo01b.rdo' size 52428800;
alter database add standby logfile '/oracle/redo/prod1/stdby_redo04.rdo' size 52428800;
more
http://www.pythian.com/news/581/oracle-standby-redo-logs
Regards,
Tom
http://asktom.cz

Should the STANDBY database be in NOMOUNT Mode?

Hi There,
Just setup DataGuard and want to monitor the primary and standby databases via the grid. However, I can not configure the standby database because the standby database is in NOMOUNT mode. Was I suppose to mount it? If not, how do I configure the standby database with the enterprise manager in NOMOUNT.
Thanks.
J

Jennifer;
Yes the standby should be in MOUNT mode before apply starts. Or No, to NOMOUNT if you prefer.
Oracle 11g Data Guard: Grid Control Management
http://www.databasejournal.com/features/oracle/article.php/3826706/Oracle-11g-Data-Guard-Grid-Control-Management.htm
Install DataGuard using Oracle Enterprise Manager 10g grid control
http://dbatips.wordpress.com/2007/02/17/install-dataguard-using-oracle-enterprise-manager-10g-grid-control/
Manage Your Existing Data Guards with Enterprise Manager Cloud Control
http://www.gokhanatil.com/2012/04/manage-your-existing-data-guards-with.html
oracle dataguard setup using enterprise manager grid control 11g
http://oracleinstall.wordpress.com/2011/08/21/1250/
Super Good
http://gavinsoorma.com/2011/03/creating-a-11g-data-guard-physical-standby-database-using-enterprise-manager-grid-control-10-2-0-5-2/
The oracle document Data Guard Broker 10g Release 1 (10.1) Part Number B10822-01 cover this in detail
http://docs.oracle.com/cd/B14117_01/server.101/b10822/gui.htm
OR for 11
http://docs.oracle.com/cd/B28359_01/server.111/b28295/title.htm
http://docs.oracle.com/cd/B28359_01/server.111/b28295/toc.htm
See Starting Up and Shutting Down a Physical Standby Database in the Data Guard Concepts and Administration
Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
Best Regards
mseberg
Edited by: mseberg on Apr 27, 2012 3:22 PM

The password file is getting corrupted after rebooting the standby database

Hi,
The password file is getting corrupted after rebooting the standby database.
Since the databases are not in sync, I had to copy the pwfile from primary to standby to make 'em sync.
(BUT.... the pwfile is not getting corrupted every time I reboot the standby by)
Could somebody please explain the reason for the pwfile on the standby database getting corrupted while rebooting ?
Env: Oracle 11g on Windows 7
Thanks in advance

Moderator Action:
This thread was originally posted to the Oracle/Sun Servers HARDWARE forum.
This is definitely not an issue related to any hardware components.
... it's now moved to Database General Questions, hopefully for closer topic alignment.

How to sync the standby database with the primary?

Hi..We have dataguard setup for our production databases(10.2.0.3).
I need one clarification regarding the standby database sync with primary.We identified one of our databases is not in sync with the primary and for longtime the archives are not getting applied at the secondary.
We decided to take the incremental (from SCN)backup from primary and use that at the standby to resolve the gap as described in the book "Oracle dataguard concepts and administration".
But, before doing that,we observed couple of structural changes were not applied at the standby(ex:some tablespaces were not created in secondary where as they were there in primary).
How to apply these changes at the secondary as the standby is in mount state.(Can I open this database and create those tablespaces ?? or do you suggest any other way.
Thanks for your reply.

This points to a setup problem. Something missing, a parameter set wrong etc.
While your question is asking something different - How to correct, I would consider how to prevent. Unless you have a gap or logs not applied you have a deeper issue.
If you have a gap or logs not applied then correct it and check to see if the missing object are present.
The key parameters for Oracle 10 are :
FAL_SERVER=STANDBY
FAL_CLIENT=PRIMARY
STANDBY_FILE_MANAGEMENT=AUTO
DB_FILE_NAME_CONVERT='STANDBY','PRIMARY'
LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
log_archive_dest_1='LOCATION=/u01/app/oracle/oradata/PRIMARY/archive VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_MAX_PROCESSES=30
Check them on both sides for issues.
If your standby is really trashed consider using RMAN to duplicate it. You might end up saving time. I have Oracle 11 short notes on this but it will work on Oracle 10 too.
http://www.visi.com/~mseberg/duprman.html
Otherwise use statements like this to resolve you gap.
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_20_716110538.arc';
ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/oradata/STANDBY/archive/PRIMARY_1_21_716110538.arc';See Section 5.8 Managing Archive Gaps of oracle document B14239-05
Best Regards
mseberg
CKPT is correct, sorry I missed the Welcome to OTN!
Edited by: mseberg on Jul 5, 2011 10:34 AM

Why process 'timestenrepd' on the standby database keep consuming 600% CPU?

Similar Messages

Maybe you are looking for