Patching the Standby DB

Hi All,
I need to patch my standby database with a few bug fix patches.
The primary (prod) database has already been patched.
The following are the steps that i am planning to implement. Please advice if any change is needed.
1. Backup the oracle binaries
2. Disable log shipping from primary to Standby
SQL>alter system set log_archive_dest_state_3=defer ;
3. Stop the Managed recovery on the standby database.
SQL> alter database recover managed standby database cancel;
4. Shutdown database
SQL> Shutdown immediate;
5. Apply patches (opatch apply)
6. Startup nomount
SQL> startup nomount;
7. Mount the standby database
SQL> alter database mount standby database;
8. Start the Managed recovery on the standby database.
SQL> Alter database recover managed standby database using current logfile disconnect from session;
Please let me know if the steps are all fine or if any changes are needed.
TIA
KVYou've not specified the patchset. I assume you're trying to apply some CPU, there are two parts of patching:
1. Patch the oracle software
2. Patch the existing database (e.g. ?\rdbms\admin\catcpu.sql)
Your steps seem fine, but you're skipping the second part of patching (refer to the readme of the patch as the step may defer for different CPU patches) and that is essential part. My plan of action will be similar to following:
After backing up binaries and database
1. Stop all the oracle services/processes
2. Verify the appropriate opatch version (refer readme)
3. patch the oracle S/W using opatch
4. Verify that the CPU is applied successfully (opatch lsinventory)
5. Patch the database (refer the readme for specific steps)
6. check for invalid objects and compile them if necessary
7. check whether the patch is applied successfully on database or not (using registry$history)
8. Similarly patch the S/W of standby server (No need to patch the database)
N.B. If you've already applied CPU on primary, then your POA is ok.
Regards,
S.K.

Similar Messages

SECURITY PATCH ON STANDBY DATABASE AND PRIMARY DATABASE

I have a question on applying CPU on standby and primary database
I have a standby database on machine2 and primary on machine1
I applied a CPU patch on the Oracle Home of Standby database and
did not run the catcpu.sql as standbydatabase is in mount state.
Now i am going to apply the CPU patch on primary database.
What i need to confirm is that after i apply the patch on primary database oracle home
and run the cat cpu.sql on that do i have to do anything on the standby database
for instance rebuilding it or something or the change would be shipped to the standby
server automatically.
The purpose is to have the primary and standby database on the same patch level
in case of a failover
Please let me know asap

Any one has any idea on this. Any ideas would be appreciated

After patching primary database, can I do not patch phsical standby db?

If I patch the primary from 10.2.4.0 to 10.2.0.5 in RAC db,
Do I must patch phsical standby to the same version or can afford to leave it alone (still 10.2.0.4)?
Thank you.

You must apply the same patchs to the standby site.
Because in case of a failover, when the standby become primary, you do not want to find a bug resolved in the patch already applied to the failed database.
That is why the docs for patching this scenario always describe the steps to patch both sites, production and standby.
For example, Note ID 187242. "Applying Patch Sets / Interim Patches with Physical Standby Database in Place".
Regards.

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

Error 1017 received logging on to the standby

Hi anyone,
Please help me...
i have database running on Oracle 10gR1 EE (10.1.0.4.0) on Linux Red Hat. and this server is replicate to DR server for backup. we change 'SYS' password about a week ago and nothing occur until today, the database is not connecting to DR server. here is the error obtain from the alert_log file. is there i 've missed anything when changing SYS password?
somebody please help me.. im in horror now.
thanks in advance.
-Nonie

forgot to paste the error.
Mon Jan 21 14:54:20 2008
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
It may be necessary to define the DB_ALLOWED_LOGON_VERSION
initialization parameter to the value "10". Check the
manual for information on this initialization parameter.
-Nonie

Logs are not getting applied in the standby database

Hello,
I have created a physical standby database and in it the logs are not getting applied..
following is an extract of the standby alert log
Wed Sep 05 07:53:59 2012
Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Attempting refetch
Media Recovery Waiting for thread 1 sequence 37638
Fetching gap sequence in thread 1, gap sequence 37638-37643
Wed Sep 05 07:53:59 2012
RFS[46]: Assigned to RFS process 3081
RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
Wed Sep 05 07:55:34 2012
RFS[42]: Possible network disconnect with primary database
However, the archived files are getting copied to the standby server.
I tried registering and recovering the logs but it also failed..
Follows some of the information,
Primary
Oralce 11R2 EE
SQL> select max(sequence#) from v$log where archived='YES';
MAX(SEQUENCE#)
37668
SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
Standby
Oralce 11R2 EE
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
37637
SQL> select * from v$archive_gap;
no rows selected
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ ONLY WITH APPLY PHYSICAL STANDBY
Please help me to troubleshoot this and get the standby in sync..
Thanks a lot..

the results are as follows..
SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
PROCESS STATUS GROUP# THREAD# SEQUENCE#
ARCH CLOSING 1 1 37644
ARCH CLOSING 1 1 37659
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
MRP0 WAIT_FOR_GAP N/A 1 37638
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS RECEIVING N/A 1 37638
RFS RECEIVING N/A 1 37639
RFS RECEIVING N/A 1 37640
RFS RECEIVING N/A 1 37641
RFS RECEIVING N/A 1 37642
RFS RECEIVING N/A 1 37655
RFS RECEIVING N/A 1 37673
RFS RECEIVING N/A 1 37675
42 rows selected.
SQL>
SQL> select name,value, time_computed from v$dataguard_stats;
NAME VALUE TIME_COMPUTED
transport lag +00 02:44:33 09/05/2012 09:25:58
apply lag +00 03:14:30 09/05/2012 09:25:58
apply finish time +00 00:01:09.974 09/05/2012 09:25:58
estimated startup time 12 09/05/2012 09:25:58
SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database

*HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY*

HOW TO DELETE THE ARCHIVE LOGS ON THE STANDBY
I have set the RMAN CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY; on my physical standby server.
My archivelog files are not deleted on standby.
I have set the CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default on the Primary server.
I've checked the archivelogs with the FRA and they are not beign deleted on the STANDBY. Do I have to do something for the configuation to take effect? Like run a RMAN backup?
I've done a lot ofresearch and i'm getting mixed answers. Please help. Thanks in advanced.
J

Setting the Policy will not delete the Archive logs on the Standby. ( I found a thread where the Data Guard product manager says "The deletion policy on both sides will do what you want" ). However I still
like to clean them off with RMAN.
I would use RMAN to delete them so that it can use that Policy are you are protected in case of Gap, transport issue etc.
There are many ways to do this. You can simply run RMAN and have it clean out the Archive.
Example :
#!/bin/bash
# Name: db_rman_arch_standby.sh
# Purpose: Database rman backup
# Usage : db_rman_arch_standby <DBNAME>
if [ "$1" ]
then DBNAME=$1
else
echo "basename $0 : Syntax error : use . db_rman_full <DBNAME> "
exit 1
fi
. /u01/app/oracle/dba_tool/env/${DBNAME}.env
echo ${DBNAME}
MAILHEADER="Archive_cleanup_on_STANDBY_${DBNAME}"
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
exit
EOF
echo `date`
echo
echo 'End of archive cleanup on STANDBY'
mailx -s ${MAILHEADER} $MAILTO < /tmp/rmandbarchstandby.out
# End of ScriptThis uses ( calls an ENV) so the crontab has an environment.
Example ( STANDBY.env )
ORACLE_BASE=/u01/app/oracle
ULIMIT=unlimited
ORACLE_SID=STANDBY
ORACLE_HOME=$ORACLE_BASE/product/11.2.0.2
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
LIBPATH=$LD_LIBRARY_PATH:/usr/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
#export TERM=linux=80x25 wrong wrong wrong wrong wrong
export TERM=vt100
export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
export ORACLE_HOME
export LIBPATH LD_LIBRARY_PATH ORA_NLS33
export TNS_ADMIN
export PATH
export MAILTO=?? your email hereNote use the env command in Unix to get you settings.
There are probably ten other/better ways to do this, but this works.
other options ( you decide )
Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
http://www.oracle.com/technetwork/database/features/availability/rman-dataguard-10g-wp-1-129486.pdf
Maintenance Of Archivelogs On Standby Databases [ID 464668.1]
Tip I don't care myself but in some of the other forums people seem to mind if you use all caps in the subject. They say it shouting. My take is if somebody is shouting at me I'm probably going to just move away.
Best Regards
mseberg
Edited by: mseberg on May 8, 2012 11:53 AM
Edited by: mseberg on May 8, 2012 11:56 AM

[SOLVED]How to patch the kernel? And other questions

Like the same user who started this thread I'm suffering from hibernation resuming troubles using kernel 2.6.38. In that thread was posted a soluttion that involves patching the kernel.
The patch to apply is this:
http://git.kernel.org/?p=linux/kernel/g … e3e9fc8684
Waiting for the bug to be corrected and a new version supplied is not an option, because this laptop is my main computer and I heavly rely on hibernation.
Here's my trouble now. I don't know if it is possible to patch without recompiling the whole kernel, or it has to be compiled with that patch applied. I have seen the archlinux's wiki guide about compiling the kernel, but found nothing about applying patches (maybe I didn't searched with enought depth).
In case there is needed a full compilation, should I use the vanilla kernel, the Arch Linux one or any of the AUR ones (I said AUR because they're the first that came to my mind)? Should i expect a performance gain with this (apart from fixing the hibernation bug)?
Maybe i'm just doing a bunch of dumb questions, and the only thing I need is to search deeply on the wiki. In that case, please tell me. If not, I rather get some answers around kernel patching and / or compiling questions.
Edit: In addittion, it is possible that all this questions are just newbie ones, I don't know, but as I am willing to learn from this I will appreciate any info or documentation about it.
Thank you.
Last edited by ethail (2011-04-12 06:30:48)

From the source tree (/usr/src/linux-whatever) execute
patch -p1 < /path/to/fix.patch
then recompile kernel from the source tree.
Basically that consists of executing the following commands from the source tree:
make menuconfig
make
make modules_install
cp -v System.map /boot/System.map-CUSTOM
cp -v arch/x86/boot/bzImage /boot/vmlinuz-CUSTOM
mkinitcpio -k 2.6.38-CUSTOM -g /boot/kernel-CUSTOM.img
and you need to add menu entry in /boot/grub/menu.lst
-k 2.6.38-CUSTOM should corespond to /lib/modules/2.6.38-CUSTOM (replace 2.6.38-CUSTOM with the name of your module directory, name depends on the kernel version and suffix that you gave in menuconfig). Regarding kernel configuration in menuconfig - I can't help you, you could use arch stock kernel config (zcat /proc/config.gz > /usr/src/linux-whatever/.config)
I do these kind of things this way - maybe someone else have a more elegant solution.

Listener not working in one of the servers of the Standby site

Hello,
The system is a RAC with two servers working as Primary site, and two servers working as Standby site.
Both servers of the Primary site are sending redo logs to one of the servers of the Standby site. The other server of the Standby site is not receiving any redo log.
I have checked the listener.ora and the tnsnames.ora files of the server that is not receiving and it is well configured comparing it with the server that is receiving the redo logs.
If I check the status of the listener: lsnrctl status listener_<node name>
Both of the Standby servers look fine.
But if I connect directly to the database...
In the 1st server of the Standby, the IP appears:
SQL> show parameter listener
NAME TYPE VALUE
local_listener string (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.xxx)(PORT = xxxx))
remote_listener string LISTENERS_DB
Nevertheless, in the second server of the Standby site, the one that is not receiving the redo logs, the IP does not appear:
SQL> show parameter listener
NAME TYPE VALUE
local_listener string (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = xxxx))
remote_listener string LISTENERS_DB
I have found the following to reload the listener:
Oracle# lsnrctl reload listener_`hostname`
Oracle# lsnrctl reload listener_standby
Has anyone tried this? Did it work? It can be run without affecting the sytem, Dataguard, replication..., right?
If you have another idea to fix this, let me know please.
Thank you ;)
Edited by: user11281526 on 29-oct-2009 4:35
Edited by: user11281526 on 30-oct-2009 7:36
Edited by: user11281526 on 31-oct-2009 4:11

If I see the status of the listener_standby in the second server of the Standby site, the one that it is not receiving redo logs, it looks like it is fine. Why?
#lsnrctl status listener_standby
LSNRCTL for Solaris: Version 10.1.0.4.0 - Production on dd-mm-yyyy hh:mm:ss
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=IP_second_server_standby)(PORT=xxxx)))
STATUS of the LISTENER
Alias listener_standby
Version TNSLSNR for Solaris: Version 10.1.0.4.0 - Production
Start Date dd-mm-yyyy hh:mm:ss
Uptime xx days yy hr. zz min.
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/10.1.0/db_1/network/admin/listener.ora
Listener Log File /opt/oracle/product/10.1.0/db_1/network/log/listener_standby.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=IP_second_server_standby)(PORT=xxxx)))
Services Summary...
Service "DB1" has 1 instance(s).
Instance "DB1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Edited by: user11281526 on 29-oct-2009 6:41
Edited by: user11281526 on 29-oct-2009 6:42
Edited by: user11281526 on 29-oct-2009 6:43

Problem with the standby database?

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

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

Bounce the standby database

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

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

Recover the standby database

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

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

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

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

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

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

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

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

Standby redologs in the standby database

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

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

Patching the Standby DB

Similar Messages

Maybe you are looking for