Standby Database with Recovery Manager

Logical standby database resides on another server. some archive log files are not synced with standby database
I want to recreate standby database with rman
Any step by step documentation ?

Before you recreate all and everything, try the troubleshoot hints in the document mentioned in the previous post.
Werner

Similar Messages

Logical Standby Database with 10g+ASM on both sides??

Hi out there,
is there a known way to establish a logical standby database on 10g, if both
sides are running with an ASM setup?
I've tried to create one out of a physical standby database (which is set up
and running w/o any problems), like a book suggested me to do.
The procedure was:
1. switch on supplemental logging
2. prepare initiation parameters (for archive logging etc.) on both sides for
logical stb.
3. shut down the phyiscal standby
4. alter database create logical standby controlfile as '<path>'; on the
primary, transfer the controlfile to the standby db. Here I had to use RMAN
to copy the controlfile into the ASM System, and modify the initfile/spfile
in order to use the controlfile. No problem so far.
5. mount the standby database, alter database recover managed standby database
disconnect; -> At this point, the alert log complained about non-available
datafiles.
6. alter database activate standby database; --> fails ("needs recovery") due
to last point.
The trouble is, the controlfile created at point 4 cointains wrong paths to
the datafiles. Since I can not have the same disk group name on the standby
system, and since ASM renames the stored datafiles by its own, the complaints
of point 5 are comprehensible, but nevertheless annoying.
I tried to backup a controlfile to trace and change the paths, but at after
mounting the standby with this controlfile and proceeding at point 5, the
system says "<path> is not a standby controlfile"
Is there a different way of creating a "Logical Standby Database with 10g+ASM
on both sides"? Metalink said nothing about LogStby and ASM.
Best regards and thanks in advance,
Martin

I'm not sure if this will work but try:
1. create trace control file (you did it)
2. change paths (you did it)
3. recrate control file (you did it)
... there was error occured during mount before
so mount database (not as standby)
4. create standby control file (from recreated control file)
5. shutdown instance, replace control file with new standby control file or replace the control filename in parameter file.
6. mount as standby
What happend?
Update: Tested on my side and it has worked fine... How about you?
Message was edited by:
Ivan Kartik

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

SQL exception during creation of a physical standby database with EM

Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
=============
2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
=========
I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

Can you please tell me how can i see data gaurd on EM..
I have oracle 11gR1..i have implemmented primary as well standby database..
I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
You got error that means u did it using EM..how can i do it on EM

ORA-10458: standby database requires recovery

hi
kindly help me... i got error when standby open in read only mode
SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 5344731136 bytes
Fixed Size 2237776 bytes
Variable Size 1275071152 bytes
Database Buffers 4060086272 bytes
Redo Buffers 7335936 bytes
Database mounted.
SQL> Alter Database Recover Managed Standby Database Disconnect;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'

hi CKPT
I executed the action plan as you recommend and got below information;
SQL> recover standby database;
ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
thread 1
ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'/archive/PROD_1_750568044_45400.ARC'
ORA-00310: archived log contains sequence 45400; sequence 45027 required
ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01666: control file is for a standby database
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
---------------------------------- and some other activity but still not found any solution-------------
RMAN> recover database until sequence
2> 45026;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:47
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
RMAN> recover database until sequence 45027;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:59
RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
RMAN> recover database until sequence 45025;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:43:09
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
ORA-01666: control file is for a standby database

Creating a Standby Database with the Same Directory Structure

Hello gurus,
I am self-learning the feature Oracle Data Guard, so I am testing it on Oracle 10g R2.
At Oracle documentation there is a section F.4.: Creating a Standby Database with the Same Directory Structure*, that explains how to create a standby database with RMAN but there is something that I don´t understand:
In the standby server, I created a database with the SID equal to production database* with the objetive to have the same directory structure, but when I try to startup nomount the standby database with pfile appear this expected error:
ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
So my question is: Is possible have the Same Directory Structure on both: Production and StandBy server?
Thanks in advanced.

Uwe and mseberg: thanks for your quick answers
I have a doubt: How can you have the same directory structure if you have differents SIDs?, for example if you follow the OFA suggestions you would must have:
On Production server: */u01/app/oracle/oradata/PRIMARY/system.dbf*
On StandBy server: */u01/app/oracle/oradata/STANDBY/system.dbf*
Or you created the directory structure manually on StandBy server? For example replacing the string STANDBY* to PRIMARY* before create the database using dbca.
Do you understand my doubt? Excuse me for my english.
Thanks.

Standby database with different directory structure

Hi,
sorry to say that we are in desupported version due to some constraint.
oracle version : 8.1.7.0.0.
os:sun 5.9
I need to create physical standby database with different directory structure:
i have created standby database with same directory structure of primary, now i have requirement to create with different directory structure.
in oracle 8i we can not give multiple parameter for db_file_name_convert(ORA-01678: parameter db_file_name_convert must be two strings, a pattern and a replacement) and i do have partitions in primary as follows:
bash-2.05$ df -h
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c1t0d0s0       20G    14G   5.6G    72%    /
/proc                    0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
fd                       0K     0K     0K     0%    /dev/fd
swap                    11G    40K    11G     1%    /var/run
dmpfs                   11G     0K    11G     0%    /dev/vx/dmp
dmpfs                   11G     0K    11G     0%    /dev/vx/rdmp
swap                    11G   656K    11G     1%    /tmp
/dev/dsk/c1t0d0s3       25G    18G   6.8G    72%    /oracle
/dev/vx/dsk/suportaldg/oracle1
                        12G    11G   1.1G    91%    /oracle1
/dev/vx/dsk/suportaldg/oracle2
                        12G   8.1G   3.7G    69%    /oracle2
/dev/vx/dsk/suportaldg/orapurge
                       200G   182G    17G    92%    /orapurge
/dev/vx/dsk/suportaldg/oracle3
                        12G    10G   1.9G    85%    /oracle3
/dev/vx/dsk/suportaldg/oracle4
                        12G    12G    58M   100%    /oracle4
/dev/vx/dsk/suportaldg/oracle5
                       7.0G   5.9G   1.0G    86%    /oracle5
/dev/vx/dsk/suportaldg/oracle6
                       7.0G   6.4G   564M    93%    /oracle6
/dev/vx/dsk/suportaldg/oracle7
                        23G    23G   358M    99%    /oracle7
/dev/vx/dsk/suportaldg/oracle8
                        13G    13G   165M    99%    /oracle8
/dev/vx/dsk/suportaldg/oracle9
                        23G    22G   1.4G    94%    /oracle9
/dev/vx/dsk/suportaldg/oracle10
                        12G 10.0G   1.9G    85%    /oracle10
/dev/vx/dsk/suportaldg/oracle11
                        39G    36G   2.1G    95%    /oracle11
/dev/vx/dsk/suportaldg/oracle12
                        39G    38G   1.1G    98%    /oracle12
/dev/vx/dsk/suportaldg/oracle13
                        68G    65G   2.6G    97%    /oracle13
/dev/vx/dsk/suportaldg/oracle14
                       200G   199G   1.3G   100%    /oracle14
/dev/vx/dsk/suportaldg/oracle15
                       200G   196G   3.6G    99%    /oracle15
/dev/vx/dsk/suportaldg/oracle16
                        70G    64G   5.5G    93%    /oracle16
/dev/vx/dsk/suportaldg/oracle20
                       7.0G   6.4G   609M    92%    /oracle20
/dev/vx/dsk/suportaldg/oracle50
                        28G    26G   2.0G    93%    /oracle50
/dev/vx/dsk/suportaldg/oratranslog
                       185G   165G    19G    90%    /oratranslogso how i can create standby database with different directory structure, help is appreciated.
Thanks
Edited by: prakashdba on Mar 5, 2009 11:04 PM

Looks like very difficult and inform you mgmt about the drawbacks of running olderv ersions
may be you can try something like this but i dont know whether it is supported or not
db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle3','/dev/vx/dsk/suportaldg/STDBY/oracle3']
db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle4','/dev/vx/dsk/suportaldg/STDBY/oracle4']
db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle5','/dev/vx/dsk/suportaldg/STDBY/oracle5']

What are the differences of creating a physical standby database with ASM?

I want to create a physical standby database for my 10g(10.2.0.1) database. But it is using ASM. Is it possible to create a standby database for a database using ASM?
What are the differences of creating a physical standby database with ASM?

tell us what your research shows and we'll try to
validate it. I am simulating Oracle ASM on a PC and I want to try
DataGuard on it now. So I am trying to create DataGuard
on an ASM system. The purpose is only learning and test.That's telling us how you are researching, not what you have observed.
Your research could have included looking at the documetation, and you might have found http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#sthref1642
which discusses exactly what you are looking for.
Message was edited by:
Hans Forbrich

Maintain standby database with DG

Good day,
I have primary and ph.standby databases.
I'd like to maintain standby database with DG(Data Guard), but DB_UNIQUE_NAME and SERVICE_NAME are the same for primary and ph.standby.
Is it possible to adjust DG broker?

CompHead wrote:
Good day,
I have primary and ph.standby databases.
I'd like to maintain standby database with DG(Data Guard), but DB_UNIQUE_NAME and SERVICE_NAME are the same for primary and ph.standby.
Is it possible to adjust DG broker?http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/install.htm#BABECEJC
>
To enable DGMGRL to restart instances during the course of broker operations, a service with a specific name must be statically registered with the local listener of each instance. The value for the GLOBAL_DBNAME attribute must be set to a concatenation of db_unique_name_DGMGRL.db_domain. For example, in the LISTENER.ORA file:
LISTENER = (DESCRIPTION =
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=host_name)
(PORT=port_num))))
SID_LIST_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=sid_name)
(GLOBAL_DBNAME=*db_unique_name*DGMGRL.dbdomain)
(ORACLE_HOME=oracle_home))
>
Logically, it should not work.

DBUA Failed at "Configuring Database with Enterprise Manager"

Hi All,
We upgraded our production database and we have configured OEM in that, while upgrading from 10.2.0.3 to 10.2.0.5, it failed at the stage "Configuring Database with Enterprise Manager". Could anyone suggest how to upgrad OEM to 10.2.0.5.

I don't think you will find logging regarding failed jobs on the system. But you can create a "view only" user, see MOS: How To Create Administrator Accounts (Super Admin, Admin, View Only, etc) In Grid Control [ID 377310.1]
Eric

To find SCN number in standby database with Oracle 9i.

Hi all,
1.how to find SCN number in standby database with Oracle 9i.
note:
1.it is in mount stage.
2.oracle 9i.
regards,
Jayaprakash.

Hello;
I have no Data Guard 9 to review. However I might try this :
select * from "_DBA_APPLY_PROGRESS";
OR
select time_mp,time_dp, scn_wrp, scn_bas, scn from smon_scn_time;Also found this: ( almost certainly NOT a physical Standby )
SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;Best Regards
mseberg
Not worth another post but I think v$database on Oracle 9 has these columns only :
v$database on Oracle 9
DBID
NAME
CREATED
RESETLOGS_CHANGE#
RESETLOGS_TIME
PRIOR_RESETLOGS_CHANGE#
PRIOR_RESETLOGS_TIME
LOG_MODE
CHECKPOINT_CHANGE#
ARCHIVE_CHANGE#
CONTROLFILE_TYPE
CONTROLFILE_CREATED
CONTROLFILE_SEQUENCE#
CONTROLFILE_CHANGE#
CONTROLFILE_TIME
OPEN_RESETLOGS
VERSION_TIME
OPEN_MODE
PROTECTION_MODE
PROTECTION_LEVEL
REMOTE_ARCHIVE
ACTIVATION#
DATABASE_ROLE
ARCHIVELOG_CHANGE#
SWITCHOVER_STATUS
DATAGUARD_BROKER
GUARD_STATUS
SUPPLEMENTAL_LOG_DATA_MIN
SUPPLEMENTAL_LOG_DATA_PK
SUPPLEMENTAL_LOG_DATA_UI
FORCE_LOGGING              ."_DBA_REGISTERED_ARCHIVED_LOG" has a "NEXT_SCN"
Edited by: mseberg on Dec 19, 2011 10:03 AM
Edited by: mseberg on Dec 19, 2011 10:29 AM
Much later
Also found this :
select dbms_flashback.get_system_change_number scn from dual;
Edited by: mseberg on Dec 19, 2011 11:06 AM

Creating Standby database with Oracle 10gR2 SE (no dataguard). Procedure

Hello,
I have problems in creating a standby database without Dataguard (Oracle Standard Edition)
-Oracle 10gR2 SE (No DataGuard !!!!)
- SUSE Enterprise 10.
Both primary and standby databases are running in Virtual machines (lab).
I will describe the exact steps I followed :
1.---------------------------------------------------
Both primary and standby databases have exactly the same file / folder structure
2.---------------------------------------------------
I enabled archive log mode with a new destination : /opt/oracle/oradata/orcl/archive_logs.
Also : SQL> alter database force logging;
3.---------------------------------------------------
I shut down the primary database (shutdown immediate)
4.---------------------------------------------------
I created a standby controlfile on the primary database:
SQL> startup mount
SQL> alter database create standby controlfile as '/tmp/standby.ctl'
SQL> shutdown immediate
5.---------------------------------------------------
I did a cold backup from the primary db to the standby db
(I copied all the db files, control files, redo log)
6.---------------------------------------------------
I copied from the primary db to the standby db the standby control file
(from primary /tmp/standby.ctl)
7.---------------------------------------------------
I copied from the primary db to the standby db the standby control file
(from primary /tmp/standby.ctl)
8.---------------------------------------------------
I created on the standby database a pfile from the spfile :
SQL> create pfile from spfile;
9.---------------------------------------------------
I edited the pfile and changed the controlfile location (with the standby controlfile created in step 4)
>>>>> *.control_files='/opt/oracle/oradata/orcl/standby.ctl'
10.--------------------------------------------------
I started the standby db
SQL> startup mount pfile='/opt/oracle/product/10.2/db_1/dbs/initorcl.ora'
SQL> alter database recover managed standby database disconnect from session;
SQL> quit
11.--------------------------------------------------
I made some changes on the primary db on user scott
SQL> update table set .......
12.--------------------------------------------------
I switched logfile on the primary db
SQL> alter system switch logfile;
13.--------------------------------------------------
I manually copied the new archivelog to the standby db
And then nothing !!!
The db changes are not applied.
Please help me fix the procedure !!!
Thanks

Hi
Ref to your Oracle SE Standby issue, we were in similar situation couple of years ago to build an Automated Standby for our disaster recovery on Oracle SE. We finally got a solution provider Anbul Technologies , they have a one of their solutions based on Oracle SE which provided fully automated Standby in Oracle SE.
We are successfully running that solution in our prod env for many years. You can visit their site www.anbultechnologies.co.uk or contact them for further details. They are Uk based but provides support and services all over Europe.
Cheers

11g standby database media recovery failed due to ora-600

hi friends,
DB: 11g 11.1.0.6
OS: Windows server 2003 ent
I've setup datagaurd using 11g. but for last 2 days, not able to start media recovey on standby database.
here's my alertlog file
alter database recover managed standby database using current logfile disconnect from session
Sat Jan 03 11:23:04 2009
MRP0 started with pid=18, OS id=648
Fast Parallel Media Recovery enabled
Managed Standby Recovery starting Real Time Apply
Media Recovery apply datafile 5 offline range
parallel recovery started with 2 processes
Waiting for all non-current ORLs to be archived...
Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\BACKUP\O1_MF_1_297_4ON23Q00_.ARC
Completed: alter database recover managed standby database using current logfile disconnect from session
Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc (incident=544158):
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
Incident details in: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_544158\gold_mrp0_648_i544158.trc
Errors with log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
MRP0: Background Media Recovery terminated with error 600
Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
Managed Standby Recovery not using Real Time Apply
Shutting down recovery slaves due to error 600
Recovery interrupted!
Sat Jan 03 11:23:15 2009
Trace dumping is performing id=[cdmp_20090103112315]
Sat Jan 03 11:23:16 2009
Recovered data files to a consistent state at change 92419435
Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
Sat Jan 03 11:23:17 2009
Sweep Incident[544158]: completed
MRP TRACE FILE
** 2009-01-03 11:05:36.140 1095 krsh.c
MRP0: Background Managed Standby Recovery process started
*** 2009-01-03 11:05:41.140
*** 2009-01-03 11:05:41.140 1295 krsm.c
Managed Recovery: Initialization posted.
Started 11g Parallel Media Recovery
Fast Parallel Media Recovery enabled
*** 2009-01-03 11:05:41.156 1095 krsh.c
Managed Standby Recovery starting Real Time Apply
*** 2009-01-03 11:05:41.671
Recovery target incarnation = 5, activation ID = 0
Influx buffer limit = 31623 (50% x 63246)
Successfully allocated 2 recovery slaves
Start recovery at thread 1 ckpt scn 92413878 logseq 297 block 2
*** 2009-01-03 11:05:43.281
Media Recovery add redo thread 1
*** 2009-01-03 11:05:43.296 1295 krsm.c
Managed Recovery: Active posted.
*** 2009-01-03 11:05:43.500
Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\O1_MF_1_297_4ON1Y6NZ_.ARC
*** 2009-01-03 11:05:44.093
Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\O1_MF_1_298_4ON74ROZ_.ARC
*** 2009-01-03 11:05:44.906
Incident 520220 created, dump file: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_520220\gold_mrp0_4044_i520220.trc
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
*** 2009-01-03 11:05:45.687 1095 krsh.c
MRP0: Background Media Recovery terminated with error 600
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
*** 2009-01-03 11:05:45.687 1095 krsh.c
Managed Standby Recovery not using Real Time Apply
kcrrgaptime: no snapshot information available
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 21376Kb in 2.55s => 8.19 Mb/sec
Total redo bytes: 23424Kb Longest record: 14Kb, moves: 17/62299 moved: 0Mb (0%)
Longest LWN: 804Kb, reads: 2357
Last redo scn: 0x0000.05823f03 (92421891)
Change vector header moves = 8621/118937 (7%)
*** 2009-01-03 11:05:45.828
Media Recovery drop redo thread 1
Completed 11g Parallel Media Recovery
Starting in-flux buffer recovery from SCN 0.92413878 to SCN (non-inclusive) 0.92419435
*** 2009-01-03 11:05:46.265
Influx Media Recovery add redo thread 1
*** 2009-01-03 11:05:47.531
*** 2009-01-03 11:05:47.531 1295 krsm.c
Managed Recovery: Not Active posted.
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
error 473 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
could you help on this...?
waiting for your favorable reply,
thanks in advance..
Regards

Hi;
This error occurs when you have run a switchover/ failover, you may have two parallel standby's but when you pass the command for switchover the one standby is not aware of what you have done.
The point is that all standby should know who is your primary & standby's should also be aware of each other in their "pfiles" now, you should either recreate the standby or open with reset logs.
ora-600 occurs due to different incarnation.
Hope this will help you
if you switch multiple logfiles in primary, & run >>
alter database recover managed standby database disconnect;
your standby will start syncing.
Hope this will help you

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Physical Standby Database with slight complication

Hello Database experts,
Primary is a multi-node RAC instance , primarily two distinct schemas (for simplicity sake schema A on tablespace A1/A2 and schema B on tablespace B1/B2). There is a proposed physical standby database. Now primary is Enterprise Data warehouse with millions of updates per minute. Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.
Any workaround possible?
Assume that Hot backup of primary database backup has to be done so we can not perform nologging operations on schema A and Logical standby is not a option.
Kind Regards,
Sunil

***Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.***
Yes. but not in physical standby. While bypassing the objects to physical standby the recovery cannot be enabled at the time. So data loss may occur. Try to configure logical standby database. you can get what you expect.
thanks

Standby Database with Recovery Manager

Similar Messages

Maybe you are looking for