Standby database issue

Hi All,
My Oracle database version is Oracle9i Enterprise Edition Release 9.2.0.8.1 in windows.
My client want to do some verfication on DR database. Users will connect to their application and they should be able to view the DR transaction.Generally our transaction logs come to Production to DR in moring. So they must view all the transaction comes in production to the DR.
phase 2 will be the user submitting the transaction.
overall procedure is :-
1. DBA set the DR in read only mode.
2. User config needs to be changed to point to DR Databse
3. User run the appln to view the transaction.
In this case,we are not going to shutdown the production database.
Now my question is how do I start and what steps do i need to follow? Do i need to disable dataguard from production and open the DR database in read only mode?
Thanks,
Meena

Hello,
If the users need to view the transaction reports on the standby database, then yes, it needs to be opened in Read Only mode.
But, when you open your standby database in read only mode, there would not be any recovery in progress on the standby (no Active Dataguard option for the version you are using).
1. Cancel the MRP on the standby database
SQL>alter database recover managed standby database cancel;
2. Open the standby database in read only mode
SQL>alter database open read only;You can later ask the users to connect to the standby database by providing them its TNS entries. The standby database can be used only for reporting purpose (select operations) when you have opened it with read only option.
Regards,
Shivananda

Similar Messages

Logical standby database issue?

Hi,
I created a logical standby database on the same server as primary database.
then I transited the old primary DB to standby DB,
old standby DB to primary DB.
and "alter system switch logfile" in new Primary DB.
execute sql in new standby DB:
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
0
question:
the redo logs can not be applied to new standby DB,
How to solve it?
thanks
DB release:9i

Hi,
Can you upload the output of:
sqlplus> show parameter arc
from both instances, or post the init.ora parameters from both. I would like to verify your arc related parameters.
Also, did you check the alert log in the primary and standby for errors?
Thanks,
Idan.

Oracle 8.1.7 Standby database issue....

My standby database stop archiving.
Media Recovery Log D:\ORACLE\ADMIN\MYDB\ARCHIVE\LOG3582_1.ARC
Media Recovery Waiting for thread 1 seq# 3583
Mon Apr 18 14:57:04 2005
Media Recovery Log D:\ORACLE\ADMIN\MYDB\ARCHIVE\LOG3583_1.ARC
Media Recovery Waiting for thread 1 seq# 3584
Mon Apr 18 15:32:58 2005
Media Recovery Log D:\ORACLE\ADMIN\MYDB\ARCHIVE\LOG3584_1.ARC
Mon Apr 18 15:33:00 2005
Errors in file D:\oracle\admin\MYDB\udump\ORA02380.TRC:
ORA-00600: internal error code, arguments: [3020], [21008251], [1], [3584], [19946], [16], [], []
Media Recovery failed with error 600
ORA-283 signalled during: ALTER DATABASE RECOVER managed standby database ...
Mon Apr 18 15:34:52 2005
Errors in file D:\oracle\admin\MYDB\udump\ORA02380.TRC
I tried to recover LOG3584_1.ARC but no success.
Is there any way to recover this situation without recreating it.

If I'm not wrong , you are hitting into bug# 3762714.

Standby Database with Standard Edition

Hi All,
I'm attempting to setup a Standby database with Oracle 10g Standard Edition. I must manually copy over the archive logs to my Standby database server because i'm using Standard Edition.
Once my primary database archive logs have been copied over to the standby location shouldn't the database automatically apply those archive logs? I have issued the "alter database recover managed standby database disconnect from session" so my understanding is that it is in recovery mode and shoudl be finding the archive logs to apply. Can anyone confirm that this configuration should work with Standard Edition and perhaps point me in the right direction, which parameters in the init file to check, to get my standby database to apply these archive logs automatically.
Thanks,

To quickly determine the level of synchronization for the standby database, issue the following query on the physical standby database:
SQL> SELECT ARCHIVED_THREAD#, ARCHIVED_SEQ#, APPLIED_THREAD#, APPLIED_SEQ#
2> FROM V$ARCHIVE_DEST_STATUS;
ARCHIVED_THREAD# ARCHIVED_SEQ# APPLIED_THREAD# APPLIED_SEQ#
1 947 1 945

Creating a Physical Standby Database

Hi,
I'm reading Oracle® Data Guard
Concepts and Administration
10g Release 2 (10.2)
B14239-04.
In 3.2 Step-by-Step Instructions for Creating a Physical Standby Database chapter it says :
3.2.1 Create a Backup Copy of the Primary Database Datafiles and recommend RMAN to do that.
And in
3.2.4 Copy Files from the Primary System to the Standby System
Use an operating system copy utility to copy the following binary files from the
primary system to the standby system:
■ Backup datafiles created in Section 3.2.1
Finally

sorry , I did not finish.
I continue
finally,
3.2.6 Start the Physical Standby Database
Step 1 Start the physical standby database.
On the standby database, issue the following SQL statement to start and mount the
database:
SQL> STARTUP MOUNT;
I wonder , how to transform RMAN backup files to data files ? It is not explained or it is not necessary ?
Many thanks.

Conceptual Question-Standby Database

Hi all,
I was just going through this documentation
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm
In the beginning it says
"Log apply services automatically apply redo to standby databases to maintain synchronization with the primary database and allow transactionally consistent access to the data"
I want to know How does process takes redo log and apply to datafile?What is basically happening inside?
Cheers,
Neerav

Dear Neerav999,
If i would know your Oracle database version, i could give you a more detailed explanation but i will give it anyway;
There are options that you can use for the Oracle Data Guard. Data Guard is used for replicating the primary database to the standby database via the archivelogs and/or with the redologs. You may not have a standby redolog for maximized performance protection level and it is not mandatory however you need to have standby redos for maximized availiability and protection, protection levels of the Oracle database.
Starting from 11g, you can able to cancel the recovery process on standby site and open the standby database read only than (magic goes here) you can start the media recovery! The command list as follow for 11g;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL --> This command will cancel the MRP0 process and will stop the continuous media recovery
ALTER DATABASE OPEN READ ONLY
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE [USING CURRENT LOG FILE] DISCONNECT FROM SESSION;
--> Above command will start the media recovery process ON THE READ ONLY DATABASE!You can give it a try that one by creating a dummy table on primary and wait for one or two log switches and check back the standby database. You are going to see the table has been also created there.
So answer to your eternal question! :)
MRP process is there to fetch and request the archivelogs from the primary site. This process can be started with the below command;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;You may have a simple test of cource. Cancel the MRP process and switch some logfiles on primary site. Than rerun above command to restart the MRP process and check v$dataguard_status fixed view. You will see that MRP is going to try to fetch the missing archivelog files and will try to close down the gap between the primary and the standby database. Here let me show you another 11g feature of Data Guard.
On 11g you can compress the redologs! What do you need to compress it? There is maybe the most threatning problem of the Data Guard is the connection itself. It should be fast and reliable. Otherwise the MRP process will fall behind and if you are running on maximum performance mode, it will also decrease the performance of the primary database and will hardly close the gap. You 11g Data Guard does is it compresses the log files in the fetching period. If its done with fetching and closed the gap than the normal transmission without the compression will continue to operate. Here is an example of redo compression parameter;
alter system set log_archive_dest_n = 'service= ORCLSTBY
LGWR ASYNC valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=ORCLSTBY compression=enable'I have checked the link that you have given and its Oracle 10g but i have just written it to understand some real factors between the 10g Data Guard and the 11g Data Guard. There are also other changes but if you can go to the 11g New Features site you will see Arup Nanda's posts about it.
If you are to use the standby redologs and it is called "Real Time Apply" and you can see it on v$dataguard_status fixed view. Here is the information from the online documentation;
6.2.1 Using Real-Time Apply to Apply Redo Data Immediately
If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
Use the ALTER DATABASE statement to enable the real-time apply feature, as follows:
    *For physical standby databases, issue the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE statement.
    *For logical standby databases, issue the ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE statement.
Standby redo log files are required to use real-time apply.Here is a fixed view that you may see the processes;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_1169.htm#REFRN30144
PROCESS      VARCHAR2(9)      Type of process whose information is being reported:
    *RFS - Remote file server
    *MRP0 - Detached recovery server process
    *MR(fg) - Foreground recovery session
    *ARCH - Archiver process
    *FGRD
    *LGWR
    *RFS(FAL)
    *RFS(NEXP)
    *LNS network server processAll above indications are most verbose and your answer to your question resides here but you need to read it carefully to understand how Oracle applies log files.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1009613
Regards.
Ogan

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.

Issue in configuring Standby Database from Active database in 11g by RMAN

POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
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.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PM

Hello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg

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

RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP

First question.
Can primary and standby database have the same SID name?
As I recall it is yes.
I believe they must have different GLOBAL or DB_UNIQUE_NAME?
Anyway, RMAN I believe is telling me it is having problems copying control file on first and dies.
Permissions Issue on STANDBY machine?
RMAN> connect target backup_admin/backup_admin
connected to target database: LABDG (DBID=1973403623)
RMAN> connect auxiliary sys/oracle@STANDBY;
connected to auxiliary database: LABDG (not mounted)
RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE;
Starting Duplicate Db at 18-JUL-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=10 device type=DISK
contents of Memory Script:
backup as copy reuse
targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' auxiliar
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' ;
executing Memory Script
Starting backup at 18-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=151 device type=DISK
Finished backup at 18-JUL-11
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format '/u01/oradat
restore clone controlfile to '/u01/app/oracle/flash_recovery_area/LABDG/cont
'/u01/oradata/LABDG/control01.ctl';
executing Memory Script
Starting backup at 18-JUL-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
copying standby control file
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/18/2011 11:20:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2011 11:20:
ORA-17628: Oracle error 19505 returned by remote Oracle server

Hi,
Permissions Issue on STANDBY machine?First problem I see is the sysdba password must be the same on both sides (target and auxiliary dbs).
From the documentation.
The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can
create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.Check all prereqs for the standby db duplicate here.
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
Rgds,
Tycho

Issue in creating Standby database

hi ALL
I am trying to create a standby database on a different server.
I am creating through RMAN with duplicate database command.
I am stuck with the issue where after backup it is not able to startup auxiliary database with error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/07/2010 13:00:57
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01261: Parameter db_recovery_file_dest destinati
on string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: Unable to access the specified directory or device.
O/S-Error: (OS 3) The system cannot find the path specified.
RMAN> **end-of-file**
My db_recovery_file_dest is different from the default location on primary.
I have created the db_recovery_dest in standby and set the parameter in rman script as well . But it is not working
Please help
thanks in advance

jatinmahajan wrote:
hi ALL
I am trying to create a standby database on a different server.
I am creating through RMAN with duplicate database command.
I am stuck with the issue where after backup it is not able to startup auxiliary database with error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/07/2010 13:00:57
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01261: Parameter db_recovery_file_dest destinati
on string cannot be translated
ORA-01263: Name given for file destination directory is invalid
OSD-04018: Unable to access the specified directory or device.
O/S-Error: (OS 3) The system cannot find the path specified.
Hi, the value of db_recovery_file_dest parameter is invalid,set this properly value(path) for this parameter and try again.

Facing issues in standby database

standby database is in sync but when we say archive log list "Current log sequence " and "Oldest online log sequence" are not geting updated
even though archives are getting applied.
Solution :- We can create new standby controlfile in order to get those archive sync .
Question :- why we are still receiving alert log errors when the standby database is running in Max performance? We have these standby files from so many days but recently we are able to see these errors
Any help regarding this is much appreciate.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /ofa/u001/PRMAN/app/oracle/admin/arch
Oldest online log sequence 179147
Next log sequence to archive 0
Current log sequence 179149
Standby alert log error message:-
Media Recovery Log /ofa/u001/PRMAN/app/oracle/admin/arch/1_189733_608563408.dbf
Clearing online log 6 of thread 0 sequence number 0
Errors in file /ofa/u001/PRMAN/app/oracle/admin/diag/rdbms/prmangfd/PRMAN/trace/PRMAN_ora_18720.trc:
ORA-00367: checksum error in log file header
ORA-00315: log 6 of thread 0, wrong thread # 1 in header
ORA-00312: online log 6 thread 0: '/ofa/u001/PRMAN/oradata/redologs1/stbyredo03.log'
RFS[16]: Opened log for thread 1 sequence 189734 dbid 1005584078 branch 608563408
Media Recovery Waiting for thread 1 sequence 189734 (in transit)
Mon Jul 29 12:06:03 2013
Archived Log entry 13297 adde
Trace file info:-
ORA-00367: checksum error in log file header
ORA-00315: log 6 of thread 0, wrong thread # 1 in header
ORA-00312: online log 6 thread 0: '/ofa/u001/PRMAN/oradata/redologs1/stbyredo03.log'
DDE rules only execution for: ORA 312
Standby sync status:-
DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP
PRMAN GFDHP122 176449 189700 29-JUL/10:29 -13251
Primary:-
DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP
PRMAN NGMHP121 189702 189700 29-JUL/10:41 2
standby redo logs :-
select group#, dbid, thread#, blocksize,used, status, sequence# from v$standby_log
GROUP# DBID THREAD# BLOCKSIZE USED STATUS SEQUENCE#
4 UNASSIGNED 0 1024 0 UNASSIGNED 0
5 UNASSIGNED 0 1024 0 UNASSIGNED 0
6 UNASSIGNED 0 1024 0 UNASSIGNED 0
Members of standby redo log file:-
select * from v$logfile where type='STANDBY'
SQL> /
GROUP# STATUS TYPE MEMBER IS_
4 STANDBY /ofa/u001/PRMAN/oradata/redologs1/stbyredo01.log NO
5 STANDBY /ofa/u001/PRMAN/oradata/redologs1/stbyredo02.log NO
6 STAND
Thanks,
Kumar Dharamoni

Hello;
I think I would try to clear the log :
Example
ALTER DATABASE CLEAR LOGFILE GROUP 3;
Do this for any groups you are having this issue with.
Best Regards
mseberg

Archive apply issue for standby database in Standard Edition.

We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
alter database recover managed standby database disconnect from session;
======================================================================================
This is the status:
SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

The DB version is 10.2.0.5
I can do this to apply at standby DB:
SQL> set autorecovery on
SQL> recover standby database;
Then I tried to run this to leave the session:
alter database recover managed standby database disconnect from session;
Do not seen any apply.
=============================
Here is the last lines of alert log:
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
Clearing online log 1 of thread 1 sequence number 10158
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 10166
Thu Sep 06 15:08:35 EDT 2012
Completed: alter database recover managed standby database disconnect from session
======
We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
Thanks!

Data Guard - MRP stuck issues on a physical standby database

Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?

Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

Next log sequence to archive in Standby Database (RAC Dataguard Issue)

Hi All,
I just had implemented Data Guard in our server. My primary Database is RAC configured, but it is only single node. The other Instance was removed and converted it to Developement Instance. For the reason I kept the primary as RAC is when I will implement dataguard, my Primary Database is RAC with 7 nodes.
The first test is successful, and I was able to "switchover" from my primary to standby. I failed in the 'FAILOVER" test.
I restore my primary server and redo the setup.
BTW, my standby DB is physical standby.
When I try to switchover again and issue archive log list, below is my output.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 0*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
MOUNTED PHYSICAL STANDBY
===============================================
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 38*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ WRITE PRIMARY
In my first attempt to switchover before I failed in "FAILOVER" test, I also issue +archive log list+ in both primary and standby database, and if I remember it right, next log sequence on both should be identical. Am I right on this?
Thanks in Advance.
Jay A

Or Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence?

Standby database issue

Similar Messages

Maybe you are looking for