Standby Database with RMAN on ASM

Hi,
I am using redhat Linux AS 4 and my database is 10.2.0.1. This database used ASM for storage of data files, control files, online redo logs. Flash recovery area is also configured in the ASM.
I want to create a physical standby database on a different machine by using RMAN. Can someone kindly point me to some easy to follow document? I have scoured the oracle docs, but am more confused than ever.
regards

Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
Note: the examples in this document use regular filesystems but the process is the same regardless, ie, in db_file_name_convert use your diskgroup rather than a filesystem (db_file_name_convert=+DG_SOURCE,+DG_TARGET)
another note to complement the first one:
Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Primary [ID 837102.1]
Edited by: rui_catcuddler on Sep 2, 2010 6:51 AM

Similar Messages

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

Creating standby database using RMAN

When I'm creating standby database with RMAN command
'duplicate for standby' backups for creating standby database
have to be accessible from host where standby database
is created. I can copy the backups to standby host, or use
NFS to share the disk with backups to standby host.
But when I have backups in ASM diskgroup how can
I achieve it would be accessible from standby host?
Thanks a lot for advice,
M.

OK, thanks,
I will create standby using Grid, but I have the following problem:
database instance is running on the host where I want
to create standby database. The running instance is for
testing purposes and has the same db_name, db_unique_name, db_domain
parameters as in primary database.
I will change db_unique_name to be distinct from primary database one,
should I also change instance SID not to be the same in
testing database and standby on the same host, or when creating standby
database I can specify distinct one for 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 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

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

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

Standby database from RMAN backup

I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
Database : Oracle 10G R2
OS : Windows Server 2003
My backup script is
configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
SQL "ALTER SYSTEM SWITCH LOGFILE";
SQL "ALTER SYSTEM SWITCH LOGFILE";
backup database;
SQL "ALTER SYSTEM SWITCH LOGFILE";
SQL "ALTER SYSTEM SWITCH LOGFILE";
backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
For recovery of a standby database,
I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
set ORACLE_SID=NGINPROD
set dbid 820336652
STARTUP NOMOUNT
RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
RESTORE DATABASE;
Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
RMAN> recover database;
Starting recover at 16-AUG-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
starting media recovery
unable to find archive log
archive log thread=1 sequence=253340
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/16/2011 09:31:57
RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
------------------------------------------------------------------------------------------------------------------------------------------------

Here's the standard dcoumentation on the procedure :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
Hemant K Chitale

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

Creation of Standby Database through Rman.

Hi Everybody,
Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
Os: Windows Xp
I am trying to create a standby database with the help of Rman..
but when i am trying to invoke the Rman Executable and connect to the primary and auxillary database ie:standby
it's giving me the following error...........
C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 09:28:08 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY (DBID=1503515402)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12541: TNS:no listenerI have restarted my listener service but still getting the error...
here is my Listener.ora entries...........
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1525))
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = PRIMARY)
      (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
standby=
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1526))
SID_LIST_standby =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = standby)
      (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
)any help appreciated
Regards,
Prosenjit Mukherjee

Hi Hemant,
It worked...when I i issued the command as mentioned by you it started the Listener..
lsnrctl start standby
Now I am able to connect to both the Database using Rman..
C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 10:55:08 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY (DBID=1503515402)
connected to auxiliary database: STANDBY (not mounted)
RMAN>Thanks for the Input...
Is there any way by which i can start both the Listener with "lsnrctl start"...........instead of manually starting individual listener's
Regards,
Prosenjit Mukherjee
Edited by: Prosenjit on Oct 2, 2008 11:01 AM

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

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 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

Trying to restore a database with RMAN in new server

Hello,
Database: Oracle 10gR2
O/S: Windows Server 2003
My RMAN backuppieces are stored in a network drive:
\\old_location\FULL
and
\\old_location\INC
I'm trying to restore a whole database with RMAN in another server from my FULL backup.
For that, I copy all backuppieces files
from: \\old_location\FULL
to new server: D:\new_location\
Also I created the relevant folder hierarchy under <ORACLE_BASE> directory, as follows:
a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>\admin' directory
b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata' directory
c. pfile.ora and controlfile (CTL_MTDPROD_2308_20120401_1.CTL) are backup from original database and they are in D:\new_location\
d. I copied pfile.ora and controlfile to folder: C:\oracle\product\10.2.0\db_1\database\
I started creating an instance in new server from scratch:
C:\>oradim -new -sid MTDPROD -intpwd mtdprod
C:\> SET ORACLE_SID=MTDPROD
C:\> rman
RMAN> connect target sys
RMAN> SET DBID=21692876873
RMAN> STARTUP force nomount PFILE=C:\oracle\product\10.2.0\db_1\database\init_mtdprod.ora
RMAN> restore controlfile from 'C:\oracle\product\10.2.0\db_1\database\CTL_MTDPROD_2308_20120401_1.CTL';
RMAN> alter database mount;
#Since I want to read my backuppieces from D:\new_location and not from \\old_location\FULL then I catalog and restore like:
RMAN> catalog start with 'D:\new_location\';
RMAN> restore database;
Starting recover at 25/04/12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=541 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile copies to recover
recovering datafile copy fno=00003 name=D:\BD_MTDPROD\CONTROLFILES\SYSAUX01.DBF
recovering datafile copy fno=00004 name=D:\BD_MTDPROD\CONTROLFILES\USERS01.DBF
recovering datafile copy fno=00007 name=D:\BD_MTDPROD\DATAFILES_DATA\MSE.ORA
recovering datafile copy fno=00010 name=D:\BD_MTDPROD\DATAFILES_DATA\EXPEDIENTES2.ORA
channel ORA_DISK_1: reading from backup piece \\old_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: failover to piece handle=D:\new_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK tag=TAG20120401T190004
.....(continues)
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\
Please, advice.

user521219 wrote:
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\Is this a cold backup? Did you change the location of control file in your PFILE or is it still pointing to old location?
You may want to check the output of RESTORE DATABASE PREVIEW command, which will just report which backup files it uses without actually restoring thhe DB.

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']

Standby Database with RMAN on ASM

Similar Messages

Maybe you are looking for