Backing up a Standby Database

Is it possible to shutdown a 9i physical standby
database and take a cold backup that can then be
restored on the primary server and brought up as the
primary db? The backup would not be an RMAN backup,
but instead just an OS file system backup.yes it's possible, but you have to recreate the controlfile to get it working. the controlfiles of standby and primary are different.
-ap

Similar Messages

Implementation of ORACLE9i RMAN physical standby database`

Sir's,
How to implement RMAN in the physical standby database

Hi Ashu Goel,
Can u let me know any thing abot the prerequistw of implementation with the configuration settings of the above said.If I understand you correctly you want to use rman to backup an already existing dataguard setup.
Doing this would be very similar as a normal rman backup with the limitation you have to stop the recovery during the backup window and run the backup in mount mode.
To make a consistent backup of the standby database, make sure that the last shutdown of the standby database was clean and that it was not placed in recovery mode after that time, and then mount the control file. For example:
sqlplus SYS/oracle@sbdb1 <<EOF
SHUTDOWN IMMEDIATE
STARTUP NOMMOUNT PFILE=initSTANDBY.ora
ALTER DATABASE MOUNT STANDBY DATABASE;
EOF
You can back up the standby database when it is in any other mode, but the backups will be inconsistent.
Start RMAN and connect to the standby database with the TARGET keyword (not the AUXILIARY keyword) and the recovery catalog database. You must be connected to the recovery catalog. For example, enter:
% rman TARGET SYS/oracle@sbdb1 CATALOG rman/cat@catdb
If do not have automatic channels configured, then manually allocate one or more channels of type DISK or sbt. Note that you are connected to the standby host, so the backups are made by server sessions on the standby (not the primary) host.
This example backs up all the standby datafiles as well as the control file and archived logs by using automatic channels:
BACKUP DATABASE PLUS ARCHIVELOG;
Regards,
Tycho

Standby database is not Sync with primary DB

Hi,
One week back I configured standby database and It was running fine.
But 2 days back(Saturday) somebody had down my standby database. Today when I mounted my database; I saw this is not sync with primary database.
Database Name :- pcs
Primary db_unique_name :- pcs
standby db_unique_name :- pcstd
Present scanerio is...
Status of Standby Database is...
SQL> startup mount;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2063792 bytes
Variable Size 301990480 bytes
Database Buffers 763363328 bytes
Redo Buffers 6324224 bytes
Database mounted.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
SQL> recover managed standby database disconnect from session;
Media recovery complete.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
N/A 130 0 WAIT_FOR_LOG
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /backup/bkpcs/
Oldest online log sequence 121
Next log sequence to archive 0
Current log sequence 126
Status of Primary database is..
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /data/pcs10g/archive/
Oldest online log sequence 129
Next log sequence to archive 131
Current log sequence 131
SQL>
Somebody can help me to resolve the following issues
(1). Why archive log list not showing exact log sequence number on Standby Database.
(2). How can I configure automatic archive logs apply from Live to Standby again.
Regards,

Problem has been resolved.

Restore standby database 10gR2 after crash

The RMAN do a full backup of the physical standby of the DataGuard 10gR2 everyday.
If the standby was dead, disks corrupted, and replaced with a new server.
Can we restore the standby from the RMAN backup, apply the archivelogs or we have re-create the standby db from the primary ?
If possible to restore the standby from the RMAN backup, what are the procedure exactly ?
Is it like this:
     RMAN>     Startup force nomount;
     RMAN>     Restore spfile;
     RMAN>     Restore controlfile;
     RMAN>     Shutdown
     RMAN>     Startup mount
     RMAN>     Restore database
     SQL> Recover standby database until cancel;
## to start Redo Apply
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

user565394 wrote:
The RMAN backup of the standby db is not obsolete and the archivelogs are still available for the last 30 dayson the RMAN backup.
I believe there is no need to re-create the standby db from the primary because the RMAN backup is still valid so it's must be possible to get the standby db back from the RMAN. If anyone who has experience and could confirm this with the procedure. That would be great.Why not test it by your own? Create a standby database and practice. You can check my video tutorial on creating standby database:
http://kamranagayev.wordpress.com/2010/06/25/rman-video-tutorial-series-creating-duplicate-and-standby-database-using-rman/
Moreover, read the "Backing Up a Standby Database with RMAN" of the following documentation:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmbackp.htm#445993
Use the RMAN BACKUP command to back up the standby database. A backup of the standby database is exactly the same as a backup of the primary database, except that the backup takes place on the standby site. The primary database has no influence on the backup of the standby database. Note that when you connect to the standby database to perform the backup, you connect using the TARGET keyword and not the AUXILIARY keyword.
Whether the standby database backup is consistent or inconsistent depends on the state of the standby database when the backup is made. Only a consistent backup can be restored without performing media recovery.

What is command to bring back the standby database to primary database?

what is command to bring back the standby database to primary database?
Please reply soon....

Mariappan wrote:
no i am not using dgbroker...Please don't make me drag everything out of you. If you only answer one question at a time, this is going to take much longer and I'm going to find better things to do with my time.
One more time: Have you read the documentation - http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/role_management.htm#1033701

How to delete the foreign archivelogs in a Logical Standby database

How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?

OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923

Switching between Primary and Standby database

Hi,
I managed to setup a standby database that is updated by the primary db either when doing a log file switch or when changing the role of the primary db to standby.
Now I want to put the standby database (that was in primary role for a short period) back into its standby role. I entered
"Alter database commit to switchover to physical standby with session shutdown;"
The archived redo logs as well as the control file are updated on the primary database (which was in standby role for the same short period). When I enter
"Alter database commit to switchover to primary" I am receiving the following error message:
SQL> alter database commit to switchover to primary;
alter database commit to switchover to primary
ERROR at line 1:
ORA-16139: media recovery required
After issuing the recovery statement I get this message:
SQL> recover database
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
At the same time this log entry is written into the alert log:
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:962365 archive SCN:0:977340
Switchover: Media recovery required - standby not in limbo
ORA-16139 signalled during: alter database commit to switchover to primary...
But when I try to use the BACKUP CONTROLFILE statement during recovery I get this error message:
SQL> recover database using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01666: control file is for a standby database
Although being quite a newbie it's obvious that the primary database (which was standby for a short period) is worried that there are older archived redo logs than online logs. I guess this happens because of the log_archive_dest definition on the standby database :
*.LOG_ARCHIVE_DEST_3='SERVICE=ORAMPPRD REOPEN=60 MAX_FAILURE=3 LGWR SYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAMPPRD'
Changes are applied immediately and only written to the archive.
But how can it be managed that the online redo logs on the primary system are also updated when switching back from standby ???
Thanks,
Philipp.

Thanks, it's working now.
I think it's important to explizitely follow the steps to switchover standby and primary for it to work. I maybe shutdown the standby to early.
Cheers,
Philipp.

Restored standby database from primary; now no logs are shipped

Hi
We recently had a major network/SAN issue and had to restore our standby database from a backup of the primary. To do this, we restored the database to the standby, created a standby controlfile on the primary, copied this across to the control file locations and started in standby recover and applied the logs manually/registered to get it back up to speed.
However, no new logs are being shipped across from the primary.
Have we missed a step somewhere?
One thing we've noticed is that there is no RFS process running on the standby:
SQL> SELECT PROCESS, CLIENT_PROCESS, SEQUENCE#, STATUS FROM V$MANAGED_STANDBY;
PROCESS CLIENT_P SEQUENCE# STATUS
ARCH ARCH 0 CONNECTED
ARCH ARCH 0 CONNECTED
MRP0 N/A 100057 WAIT_FOR_LOG
How do we start this? Or will it only show if the arc1 process on the primary is sending files?
The arc1 process is showing at OS level on the primary but I'm wondering if its faulty somehow?
There are NO errors in the alert logs in the primary or the standby. There's not even the normal FAL gap sequence type error - in the standby it's just saying 'waiting for log' and a number from ages ago. It's like the primary isn't even talking to the standby. The listener is up and running ok though...
What else can we check/do?
If we manually copy across files and do an 'alter database register' then they are applied to the standby without issue; there's just no automatic log shipping going on...
Thanks
Ross

Hi all
Many thanks for all the responses.
The database is 10.2.0.2.0, on AIX 6.
I believe the password files are ok; we've had issues previously and this is always flagged in the alert log on the primary - not the case here.
Not set to DEFER on primary; log_archive_dest_2 is set to service="STBY_PHP" optional delay=720 reopen=30 and log_archive_dest_state_2 is set to ENABLE.
I ran those troubleshooting scripts, info from standby:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_PHP
fal_server PHP
local_listener
log_archive_config
log_archive_dest_2 service=STBY_PHP optional delay=30 reopen=30
log_archive_dest_state_2 DEFER
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE
PHP PHP MAXIMUM PERFORM PHYSICAL S MOUNTED
ANCE TANDBY
THREAD# MAX(SEQUENCE#)
1 100149
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
MRP0 WAIT_FOR_LOG 1 100150
NAME VALUE UNIT TIME_COMPUTED
apply finish time day(2) to second(1) interval
apply lag day(2) to second(0) interval
estimated startup time 8 second
standby has been open N
transport lag day(2) to second(0) interval
NAME Size MB Used MB
0 0
On the primary, the script has froze!! How long should it take? Got as far as this:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_R1P
fal_server R1P
local_listener
log_archive_config
log_archive_dest_2 service="STBY_PHP" optional delay=720 reopen=30
log_archive_dest_state_2 ENABLE
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS
PHP PHP MAXIMUM PERFORMANCE PRIMARY READ WRITE SESSIONS ACTIVE
THREAD# MAX(SEQUENCE#)
1 100206
NOW - before you say it - :) - yes, I'm aware that fal_client as STBY_R1P and fal_server as R1P are incorrect - should be PHP - but it looks like it's always been this way! Well, as least for the last 4 years where it's worked fine, as I found an old SP file and it still has R1P set in there...?!?
Any ideas?
Ross

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

Creating physical standby database from another physical standby database

hi,
We have one production database and one physical standby of the production. Now we have situation where we need to create one database from either production or from standby. As production is loaded we can not do it using active database option. Now we have the only option to copy the database from standby.
As of now we open the standby and copy it using rman duplicate database and again we put it back to standby mode.
Is it possible to create standby database from standby database only?
Oracle version : 11.1.0.7.0
I have seen procedure allowing to do the same in version 11.2.0.3. I have tried searching for the difference but didn't find when this feature was introduced.
Thanks,
Ketul Patel

Hello;
Active duplicate should work when connected to Standby as source Database. However there's a bug 11715084 which is not fixed until version 11.2.0.4.
If patch 11715084 is available for your version it may work, but all the 11.1.0 are gone so I have no way to test.
RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET [ID 1343515.1]
Understanding ORA-01671 error during controlfile creation / backup [ID 461121.1]
Best Regards
mseberg
Edited by: mseberg on Feb 13, 2013 8:59 AM

Create ONLINE logfile in physical standby database

We have created a physical standby database with rman duplicate command on a remote server
"duplicate target database for standby dorecover nofilenamecheck"
When I see the standby server...Online logfiles are not created however its relevant entries are there in V$LOG and V$LOGFILE views.
I guess it is the default behaviour of duplicate command in RMAN and we can not specify LOGFILE clause when we create standby database.
Now the problem is we could not drop the online logfile on standby database since it's status is "CURRENT", "ACTIVE".
Since the ONLINE LOGFILE are not actually created , "ALTER DATABASE CLEAR LOGFILE GROUP " command returns with error as it could not find the file in the server.
So How we can drop the current/active online logfile and add new ones in standby db?

I'm assuming you have physical standby. Here are step I did in the past.
1) create a backup control file
2) bring the database back using the "recreate control file" it the trace file BUT you need to remove or comment out the line that has the corrupt or missing redo log file. And don't forget to add the tempfile after you recreate the controlfile
example:
alter database backup controlfile to trace;
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/oracledata/orcl/redo01.log' SIZE 200M,
GROUP 2 '/oracledata/orcl/redo02.log' SIZE 200M,
GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M,
# GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M
-- STANDBY LOGFILE
-- GROUP 10 '/oracledata/orcl/redostdby04.log' SIZE 200M,
-- GROUP 11 '/oracledata/orcl/redostdby05.log' SIZE 200M
DATAFILE
'/oracledata/orcl/system01.dbf',
'/oracledata/orcl/undotbs01.dbf',
'/oracledata/orcl/sysaux01.dbf',
'/oracledata/orcl/users01.dbf'
CHARACTER SET WE8ISO8859P1
If you just want to add the standby redo log then using this command.
alter database add standby logfile
'/<your_path>/redostdby01.log' size 200M reuse,

Problem Converting standby database from snapshot to physical

Any help willl be greatly appreciated...
I am trying to convert a standby database that is in "snapshot" mode back to "physical" standby and I am encountering problems in the process from the "DGMGRL" command line.
Both instances are on the same physical machine. Everything was working fine untill I tried to change the db from snapshot to physical. The DGMGRL starts the conversion process and is able to shutdown but when trying to restart the instance is fails and reports that the service is not defined.
Here is the issue I am facing:
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1 <======= the primary database
C:\app\MMJ\product\11.1.0\db_1\BIN>dgmgrl
DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/password@i11g1sb <===== the standby database currently in snapshot mode
Connected.
DGMGRL> connect sys/password@i11g1 <==== the primary database
Connected.
DGMGRL> convert database 'i11g1sb' to physical standby;
Converting database "i11g1sb" to a Physical Standby database, please wait...
Operation requires shutdown of instance "i11g1sb" on database "i11g1sb"
Shutting down instance "i11g1sb"...
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "i11g1sb" on database "i11g1sb"
Starting instance "i11g1sb"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "i11g1sb"
You must start instance "i11g1sb" manually
Failed to convert database "i11g1sb"
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database (disabled)
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
SUCCESS
DGMGRL> exit
C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1SB
C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:40:16 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 426852352 bytes
Fixed Size 1333648 bytes
Variable Size 369100400 bytes
Database Buffers 50331648 bytes
Redo Buffers 6086656 bytes
Database mounted.
Database opened.
==============>>>> as you can see I can start the standby database without any problems and even query the table in which I made some changes. I had added the record with "Region_ID"=30. I have
SQL> select * from hr.regions;
REGION_ID REGION_NAME
30 JAPAC
1 Europe
2 Americas
3 Asia
4 Middle East and Africa
SQL>
The same table on the primary database has the following records in the same table:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\MMJ>set ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
C:\Documents and Settings\MMJ>set ORACLE_SID=i11g1
C:\Documents and Settings\MMJ>
C:\Documents and Settings\MMJ>cd %ORACLE_HOME%
C:\app\MMJ\product\11.1.0\db_1>cd bin
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:43:10 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL>
SQL> select * from hr.regions;
REGION_ID REGION_NAME
1 Europe
2 Americas
3 Asia
4 Middle East and Africa
20 JAPAC
40 JAPAC
6 rows selected.
SQL>
=======> The TNSPING works fine against both the databases.
C:\app\MMJ\product\11.1.0\db_1\BIN>set O
ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
ORACLE_SID=I11G1SB
OS=Windows_NT
C:\app\MMJ\product\11.1.0\db_1\BIN>
C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1sb
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:42
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
E = I11G1SB)))
OK (230 msec)
C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1
TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:47
Copyright (c) 1997, 2007, Oracle. All rights reserved.
Used parameter files:
c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
E = I11G1)))
OK (30 msec)
C:\app\MMJ\product\11.1.0\db_1\BIN>lsnrctl
LSNRCTL for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:57:01
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Welcome to LSNRCTL, type "help" for information.
LSNRCTL> set current_listener i11g1
Current Listener is i11g1
LSNRCTL> services
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MHost)(PORT=1523)))
Services Summary...
Service "I11G1" has 1 instance(s).
Instance "I11G1", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1 refused:0
LOCAL SERVER
Service "I11G1SB" has 1 instance(s).
Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:55 refused:1
LOCAL SERVER
Service "I11G1SB_DGMGRL" has 1 instance(s).
Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "i11g1.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1XDB.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: MHost, pid: 3944>
(ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1430))
Service "i11g1_DGB.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1_XPT.mhost" has 1 instance(s).
Instance "i11g1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:6 refused:0 state:ready
LOCAL SERVER
Service "i11g1sb.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "i11g1sbXDB.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: MHost, pid: 7336>
(ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1931))
Service "i11g1sb_DGB.MHost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "i11g1sb_XPT.mhost" has 1 instance(s).
Instance "i11g1sb", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
LSNRCTL>

Thanks for the response.
So, here is the status now....with a little background...
After my original post, I started to read the manuals and I found the sql command to convert the database back from snapshot to physical standby (sb).
That worked fine and I had my snapshot sb back to physical sb.
So when you posted the suggestion, I already had my db in physical sb mode. I said no problem, I will convert it back to snapshot and then back again using dgmgrl instead of sql+
Well here is how my listener is configured now.
SID_LIST_I11G1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = I11G1.MHOST)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1)
(SID_DESC =
(GLOBAL_DBNAME = I11G1SB.MHOST)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1SB)
(SID_DESC =
(GLOBAL_DBNAME = I11G1SB_DGMGRL)
(ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
(SID_NAME = I11G1SB)
Then using dgmgrl I tried to change the db from p-sb to s-sb and the results are not good....
"i11g1 >"dgmgrl
DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL>
DGMGRL> connect sys/[email protected]
Connected.
DGMGRL>
DGMGRL>
DGMGRL> convert database 'i11g1sb' to snapshot standby;
Converting database "i11g1sb" to a Snapshot Standby database, please wait...
Database "i11g1sb" converted successfully
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show configuration
Configuration
Name: DGConfig1
Enabled: YES
Protection Mode: MaxPerformance
Databases:
i11g1 - Primary database
i11g1sb - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "DGConfig1":
Warning: ORA-16607: one or more databases have failed
DGMGRL> show database 'i11g1sb';
Database
Name: i11g1sb
Role: SNAPSHOT STANDBY
Enabled: YES
Intended State: APPLY-OFF
Instance(s):
i11g1sb
Current status for "i11g1sb":
SUCCESS
DGMGRL> show database 'i11g1';
Database
Name: i11g1
Role: PRIMARY
Enabled: YES
Intended State: TRANSPORT-ON
Instance(s):
i11g1
Current status for "i11g1":
Error: ORA-16778: redo transport error for one or more databases
DGMGRL> exit
Not sure if the following (notice the typo in the service name) in the parameter (log_archive_dest_2) definition on the standby d/b has anything to do with this. I did not get this error when I initially converted to s-sb.
also I checked all my session notes, I did not type the command to set this parameter on the standby d/b and so it was not a typo on my part. However, it seems to have come from the rman script supplied with the obe. This script is supposed to clone the primary d/b to a standby db and in the process replace the string /i11g1/ with /i11g1sb/.
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string service=i11g1sbsb async valid_
for=(online_logfile,primary_ro
le) db_unique_name=i11g1sb
SQL>
SQL>
SQL> select instance_name from v$instance;
INSTANCE_NAME
i11g1sb
SQL>
Given all this, the archive logs seem to be shipping correctly to the sby d/b.
"i11g1sb >"cd C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
"i11g1sb >"dir
Volume in drive C is Local Disk
Volume Serial Number is 3189-6472
Directory of C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
30/03/2009 09:05 PM <DIR> .
30/03/2009 09:05 PM <DIR> ..
30/03/2009 05:41 PM 35,627,008 O1_MF_1_137_4X2H4JJM_.ARC
30/03/2009 05:41 PM 1,910,784 O1_MF_1_138_4X2H4LVC_.ARC
30/03/2009 09:04 PM 10,447,360 O1_MF_1_139_4X2V03RW_.ARC
30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V3BWB_.ARC
4 File(s) 56,640,000 bytes
2 Dir(s) 39,716,225,024 bytes free
"i11g1sb >"
"i11g1 >"dir
Volume in drive C is Local Disk
Volume Serial Number is 3189-6472
Directory of C:\app\MMJ\flash_recovery_area\I11G1\ARCHIVELOG\2009_03_30
30/03/2009 09:05 PM <DIR> .
30/03/2009 09:05 PM <DIR> ..
30/03/2009 04:09 PM 35,627,008 O1_MF_1_137_4X29QHTV_.ARC
30/03/2009 04:24 PM 1,910,784 O1_MF_1_138_4X2BMOC7_.ARC
30/03/2009 06:32 PM 10,447,360 O1_MF_1_139_4X2L4J3X_.ARC
30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V37KL_.ARC
4 File(s) 56,640,000 bytes
2 Dir(s) 39,716,229,120 bytes free
I am tempted to start all over again, but I'd rather use this opportunity to debug this issue (as a learning exercise). I can always start from scratch. That brings up another Q: What do I need to do to blow away all traces of the stand by database (including all the archive logs etc...) keeping my primary intact. I'd also like to blow away all snapshot and archive logs for the primary as well.

Cannot Convert standby database from snapshot to physical

Hello all,
I am using Oracle Entreprise version 11gR1 and had made the followings configuration:
- ANAISMD2 : primary database+_+
- ANAISMD3 : physical standby datbase. Created via RMAN
Both are located on the same host running a RH 4.
ANAISMD3 is maintained successfully with the primary.
I can make a fail-over between the both: it works fine.
I can convert ANAISMD3 from physical to snapshot via DGMGRL: it works fine
But I cannot convert back ANAISMD3 to physical, got an error ORA-12514
I had checked also the listener service for both ANAISMD2/ANAISMD3 before launching the conversion:
- the services shown on ANAISMD3 seems correct e.g. ANAISMD2 is seen as a remote server.
- but on ANAISMD2, ANAISMD3 seems incorrect e.g. ANAISMD3 is seen as a local server.
I had attached some screen shots of dg/lsnrctl results;
What are the mistakes
Thank in advance for support
==> Before I made the conversion , DGMGRL shows correct primary/standby status:
DGMGRL for Linux: Version 11.1.0.6.0 - Production
Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@ANAISMD2
Connected.
DGMGRL> show configuration
Configuration
Name: ANAIS
Enabled: YES
Protection Mode: MaxPerformance
Databases:
ANAISMD2 - Primary database
ANAISMD3 - Snapshot standby database
Fast-Start Failover: DISABLED
Current status for "ANAIS":
SUCCESS
==> When I want to convert back ANAISMD3 to physical, I got the following errors from the listener:_
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@ANAISMD2
Connected.
DGMGRL> convert database 'ANAISMD3' to physical standby;
Converting database "ANAISMD3" to a Physical Standby database, please wait...
Operation requires shutdown of instance "ANAISMD3" on database "ANAISMD3"
Shutting down instance "ANAISMD3"...
Database closed.
Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "ANAISMD3" on database "ANAISMD3"
Starting instance "ANAISMD3"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
You are no longer connected to ORACLE
Please connect again.
Unable to start instance "ANAISMD3"
You must start instance "ANAISMD3" manually
Failed to convert database "ANAISMD3"
DGMGRL>
==> Here ist he listener.ora_ (I put the same for both ANAISMD2/ANAISMD3 with port 1541/1551). Note: DGB is the accepted extension for dgmgrl service (instead of DGMGRL as mentionned in documentation).
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL=TCP) (HOST=rh4-2a) (PORT=1541))
TRACE_LEVEL_LISTENER = ADMIN
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = ANAISMD2)
(GLOBAL_DBNAME = ANAISMD2.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD2)
(GLOBAL_DBNAME = ANAISMD2_DGB.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD3)
(GLOBAL_DBNAME = ANAISMD3_DGB.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
(SID_DESC =
(SID_NAME = ANAISMD3)
(GLOBAL_DBNAME = ANAISMD3.world)
(ORACLE_HOME=/home/oracle/product/11.1.0)
==> Here is the tnsnames.ora (I put the same for both ANAISMD2/ANAISMD3 with port 1541/1551).
ANAISMD2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rh4-2a)(PORT = 1541))
(CONNECT_DATA =
(SERVICE_NAME = ANAISMD2_DGB.world)
ANAISMD3.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rh4-2a)(PORT = 1551))
(CONNECT_DATA =
(SERVICE_NAME = ANAISMD3_DGB.world)
==> Here is the sqlnet.ora (same on both):
TRACE_LEVEL_CLIENT = OFF
DIAG_ADR_ENABLED=FALSE
DIAG_DDE_ENABLED=FALSE
DIAG_SIGHANDLER_ENABLED=FALSE
names.directory_path = (TNSNAMES)
names.default_domain = world
name.default_zone = world
==>
==> List of services provided by the listener of ANAISMD2:
LSNRCTL for Linux: Version 11.1.0.6.0 - Production on 10-AUG-2009 16:39:36
Copyright (c) 1991, 2007, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2a)(PORT=1541)))
Services Summary...
Service "ANAISMD2.world" has 1 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "ANAISMD2_DGB.world" has 1 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:3 refused:0+
LOCAL SERVER
Service "ANAISMD3.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "ANAISMD3_DGB.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
+"DEDICATED" established:0 refused:0+
LOCAL SERVER
The command completed successfully
==> List of services provided by the listener of ANAISMD3:
Services Summary...
Service "ANAISMD2.world" has 2 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD2_DGB.world" has 2 instance(s).
Instance "ANAISMD2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD2_XPT.world" has 1 instance(s).
Instance "ANAISMD2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=rh4-2)(PORT=1521))
Service "ANAISMD3.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "ANAISMD3_DGB.world" has 1 instance(s).
Instance "ANAISMD3", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
The command completed successfully

You need to have static service registered with listener in this way. This is must because as you know when it converts db that time it shutsdown dbs also so all dynamic services are lost and dgmgrl is not ale to connect to db hence conversion fails.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORACLE_SID)
(GLOBAL_DBNAME=db_unique_name_DGMGRL.db_domain)
(ORACLE_HOME = /apps/oracle/product/11.1.0)
Plus with this make a entry in tnsnames.ora using service name from above or check from lsnrctl status look for service "db_unique_name_DGMGRL.db_domain"
e.g. this is my best practice how i give the names to tns entry
db_unique_name_DGMGRL =
(DESCRIPTION =
(SDU = 32767)
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = port))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = db_unique_name_DGMGRL.db_domain)
Define same way in both primary and standby db.
Now use these tns entries to create configuration.
e.g.
create configuration prim_db as primary database is db_unique_name connect identifier is "db_unique_name_DGMGRL";
-- db_unique_name_DGMGRL from primary tns entry
add database stdby_db as connect identifier is "db_unique_name_DGMGRL" MAINTAINED AS PHYSICAL;
-- db_unique_name_DGMGRL from standby db tns entry
hope this will help

Issue with physical standby database not in sync with primary

Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
Rakesh

HI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL>

Logical standby database problem

i have setup logical standby database on my pc . Everything was working fine . Logs were applied.
But i tried testing few things on standby and issued few commands on that.
After that the logs were not applied. i tried to restart that also dint work.
what should i do so that things r back to normal or i need to create the standby again .
Thanks

The output is as follows .
SQL> SELECT APPLIED_SCN, NEWEST_SCN, READ_SCN, NEWEST_SCN-APPLIED_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN READ_SCN NEWEST_SCN-APPLIED_SCN
179493 194423 179497 14930
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
no rows selected
SQL> select operation, options, object_name, cost
2 from v$sql_plan, v$session, v$logstdby
3 where v$sql_plan.hash_value = v$session.sql_hash_value
4 and v$session.serial# = v$logstdby.serial#
5 and v$logstdby.status_code=16113;
no rows selected

Backing up a Standby Database

Similar Messages

Maybe you are looking for