Problem in standby database

Hi,
Logs which are shipping to standby database are not been registered automatically..
I need to register them manual....
Can you please help me in finding the problem behind this.

Aman wrote:
Hi,
Logs which are shipping to standby database are not been registered automatically..
I need to register them manual....
Can you please help me in finding the problem behind this.Firstly that is not possible which log actually shipped to standby database but not registered.But you can manually register log using ALTER DATABASE REGISTER LOGFILE clause or just transfer archive log to LOG_ARCHIVE_DEST_1 destination on standby side and this will enough.When recovering process these logs will be apply.
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/original_export.htm

Similar Messages

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.

Dataguard Problem(logical standby database)

Hi,
I have successfully created logical standby database, and everything is working fine, all of the SQL is applying and archiving is also shipping.
Until I create a new tablespace for e.g. pay in the primary database, and suddenly SQL applying is stopped, but the archive is shipping.
I am using Windows XP SP2 and Oracle 10gRel2.
The contents of AlertLog file are as
Wed Jul 23 22:52:19 2008
Thread 1 cannot allocate new log, sequence 133
Checkpoint not complete
Current log# 3 seq# 132 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
Wed Jul 23 22:52:23 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:52:23 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:52:23 2008
Thread 1 advanced to log sequence 133 (LGWR switch)
Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
Thread 1 cannot allocate new log, sequence 134
Checkpoint not complete
Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
Wed Jul 23 22:52:29 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:52:29 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:52:29 2008
Thread 1 advanced to log sequence 134 (LGWR switch)
Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
Wed Jul 23 22:55:49 2008
Thread 1 cannot allocate new log, sequence 135
Checkpoint not complete
Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
Wed Jul 23 22:55:54 2008
Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
Wed Jul 23 22:55:54 2008
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Wed Jul 23 22:55:54 2008
Thread 1 advanced to log sequence 135 (LGWR switch)
Current log# 3 seq# 135 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
When i use this command, the SQL Apply starts again but the tablespace is not created on Logical standby database.
kindly give me a solution.
Thanks in advanced.

In Standy database also you need to add TB details for it to recognise Primary DB new TB .
try adding it and retry your operation .

Problem creating standby database using RMAN

I am preparing standby database on Windows environment. For the same..
1. I have taken full database,archivelog and standby control file backup on primary database.
2.Backup pieces have been moved to standby server.
3.TNS configured on both the servers.
4.connected to target as well as auxiliary database and trying to create the standby database using the below command...
duplicate target database for standby;
But I am getting the below error........
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
ORA-19870: error reading backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
ORA-19504: failed to create file "E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM\CONTROL01.CTL"
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/01/2009 10:35:48
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
Please provide me the solution for the same...
Thanks in Advance.....
Sukanta

channel ORA_AUX_DISK_1: reading from backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
ORA-19870: error reading backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
ORA-19504: failed to create file "E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM\CONTROL01.CTL"
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
failover to previous backup
Can you please confirm if the directory E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM is existing on standby box and rman can write to that location (free space & permissions)
If the issue is still present provide us the control_files parameter from standby..
- Ravi.M

Issue on physical standby database

Hi
I've a problem on standby database.
I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
I get following message in my alert log
WARNING! Recovering data file 88 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
how can I fix this now.
We keep physical standby database 2 day behind, and apply logs manually.
Physical standby database is maintained manually.
Could someone help me in getting out of this problem.
Oracle 9.2.0.7
solaris

Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
Note:
If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
Specifying a Time Delay
You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
Canceling a Time Delay
You can cancel a specified delay interval as follows:
For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
For logical standby databases, specify the following SQL statement:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
Section 12.8, "Using a Physical Standby Database with a Time Lag"
Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

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

Problem in recover physical standby database(Data Guard) by rman

Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS
would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PM

hi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks

Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

Problem building logical standby database

Hi all,
i am trying to build a logical standby database on platform Sun OS 10/Oracle 10gR2. I am following the Oracle document http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#BEIGHEIA
I have created a physical standby database and converting it to a logical standby database. I ensured that my physical Standby is in Sync with primary.
Procedure DBMS_LOGSTDBY.BUILD executes successfully on primary.
The problem is that the command *'alter database recover to logical standby test;'* DOESN'T END. No error in archive log. I have identified the archived redo log that contains the LogMiner dictionary and the starting SCN and applied that archive log on standby. Still the the above command doesn't end.
Any Help is appreciated.

SQL> alter database recover to logical standby m2test;
This command doesn't return an sql> prompt. Alert log says it is waiting for log sequence 25. The command is running is for more than 5 hours, but still not competed.
Alertlog:
Thu Feb 5 22:14:25 2009
alter database recover to logical standby m2test
Thu Feb 5 22:14:25 2009
Media Recovery Start: Managed Standby Recovery (mtest)
Thu Feb 5 22:14:25 2009
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 2 processes
Media Recovery Waiting for thread 1 sequence 25
Document says :-
If a dictionary build is not successfully performed on the primary database, this command will never complete.
But the dictionary build on primary is successful.
SQL> execute dbms_logstdby.build;
PL/SQL procedure successfully completed.
I used the following queries and to find which archive log contains dictionary build and made sure that the log archive sequence 22 is applied on standby.
SQL> SELECT NAME FROM V$ARCHIVED_LOG
WHERE (SEQUENCE#=(SELECT MAX(SEQUENCE#)
FROM V$ARCHIVED_LOG
WHERE DICTIONARY_BEGIN = 'YES' AND STANDBY_DEST='NO')); 2 3 4
NAME
/oradata/mtest/archive/mtest_1_22_677975686.arc
SQL> SELECT MAX(FIRST_CHANGE#) FROM V$ARCHIVED_LOG
WHERE DICTIONARY_BEGIN='YES'; 2
MAX(FIRST_CHANGE#)
177407
SQL>
Edited by: user592715 on Feb 6, 2009 3:22 PM

RMAN script problem to create logical standby database !

Dear Friends ,
I am using Oracle10g database . I want to create a logical standby database . I create two database :
Primary : orcl
standby : orclsby1
Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
The script is below which I have to run in Primary (orcl) database :
Script :
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 'orcl','orclsby1'
set db_unique_name='orclsby1'
set db_file_name_convert='/orcl/','/orclsby1/'
set log_file_name_convert='/orcl/','/orclsby1/'
set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
set log_archive_max_processes='5'
set fal_client='orclsby1'
set fal_server='orcl'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(orcl,orclsby1)'
set log_archive_dest_1='service=orcl ASYNC
valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
Problem which I got :
[oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1227832857)
connected to auxiliary database: ORCLSBY1 (not mounted)
RMAN> @cr_phys_sby1.txt
RMAN> run {
2> allocate channel prmy1 type disk;
3> allocate channel prmy2 type disk;
4> allocate channel prmy3 type disk;
5> allocate channel prmy4 type disk;
6> allocate auxiliary channel stby type disk;
7> duplicate target database for standby from
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
Both databases are running on Oracle10g platform .
Waiting for ur kind reply .. ...

You need to:
- create a SPFILE manually for standby database
- use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
- remove all SPFILE statements from RMAN script.

Problem when create standby database

hello,
I have two server(NT4.0,SP6) installed Oracle 8i(8.1.6 Enterprise) at the same directory.I want one as the primary database,another one as the standby database.
The two database have the same SID,use SQL*Plus it can access each other.
My operating steps as below:
1.on primary server:
1)connect internal;
2)shutdown immediate;
3)copy all datafiles(*.DBF) to a backup directory;
4)startup
5)alter database create standby controlfile as 'd:\oracle\ora81\ILLDB\standby.ctl'
6)alter system archive log current
2.on standby server:
1)copy all backuped datafile,standby.ctl,all redo log files from primary server to standby server,overwrite all same name files;
2)modify the init.ora,add this parameter:
"standby_archive_dest = "location=D:\Oracle\oradata\ILLDB\archive" ";
3)statup oracle service in Service control manel;
4)run svrmgrl.exe;
5)startup nomount;
6)alter database mount standby database;
then a error message appear:
"ORA-01665 controlfile is not a standby controlfile".
I don't know which step is mistake.Please tell me correct steps.
Thanks

I did face the similar problem while trying to create and startup a clone database for Point in Time Recovery (PITR). The error message is
ORA-01696 controlfile is not a clone controlfile
Are you folks have any idea how do I resolve this problem?? Is there any way to create clone control file??

Standby database problem

Hi Guys,
Happy New Year....
I have a problem with the standby database was down for few days and back online. After I brought it up the logs from the primary database are applied and then it fails to apply the real-time logs.
Database version is 10g running with Non-Cluster mode.
I found the following in dgmon log
DG 2007-01-02-19:32:18 0 2 610825807 DMON: ENUM_DRC: success. (len = 653)
DG 2007-01-02-19:32:18 0 2 610825807 DMON: ENUM_DRC operation completed
DG 2007-01-02-19:32:22 0 2 610825808 DMON: ENUM_DRC: success. (len = 653)
DG 2007-01-02-19:32:22 0 2 610825808 DMON: ENUM_DRC operation completed
DG 2007-01-02-19:32:22 1000 2 610825809 DMON: MON_PROPERTY operation completed
DG 2007-01-02-19:32:22 1000 2 610825810 DMON: MON_VERIFY forwarded to site PrimaryDB for processing
DG 2007-01-02-19:39:10 0 2 0 NSV0: Failed to connect to remote database PrimaryDB. Error is ORA-12154
DG 2007-01-02-19:39:10 0 2 0 NSV0: Message is dropped.
DG 2007-01-02-19:39:10 1000 2 610825810 DMON: Database PrimaryDB returned ORA-12154
DG 2007-01-02-19:39:10 1000 2 610825810 for opcode = MON_VERIFY, phase = NULL, req_id = 2.1.610825810
DG 2007-01-02-19:39:10 1000 2 610825810 DMON: MON_VERIFY operation completed
DG 2007-01-02-19:39:10 1000 2 610825811 DMON: CTL_GET_STATUS forwarded to site PrimaryDB for processing
DG 2007-01-02-19:45:57 0 2 0 NSV0: Failed to connect to remote database PrimaryDB. Error is ORA-12154
DG 2007-01-02-19:45:57 0 2 0 NSV0: Message is dropped.
DG 2007-01-02-19:45:57 1000 2 610825811 DMON: Database PrimaryDB returned ORA-12154
DG 2007-01-02-19:45:57 1000 2 610825811 for opcode = CTL_GET_STATUS, phase = NULL, req_id = 2.1.610825811
DG 2007-01-02-19:45:57 0 2 0 DMON: Failed to publish large message. Error is 0xffffff81
DG 2007-01-02-19:45:57 0 2 0 Message packet header dump:
DG 2007-01-02-19:45:57 0 2 0 Request ID = 2.1.610825811
DG 2007-01-02-19:45:57 0 2 0 Sender ID = 0
DG 2007-01-02-19:45:57 0 2 0 Requesting Site = 00001000
DG 2007-01-02-19:45:57 0 2 0 Requesting Instance ID = 0
DG 2007-01-02-19:45:57 0 2 0 Root Resource Handle = 00000000
DG 2007-01-02-19:45:57 0 2 0 Opcode = 00000000
DG 2007-01-02-19:45:57 0 2 0 Phase = 0
DG 2007-01-02-19:45:57 0 2 0 Status = ORA-00000
DG 2007-01-02-19:45:57 0 2 0 Target Instance = 0
DG 2007-01-02-19:45:57 0 2 0 Severity = ORA-00000
DG 2007-01-02-19:45:57 0 2 0 Flags = 1
DG 2007-01-02-19:45:57 1000 2 610825811 Unable to post result to client, status = ORA-16531
DG 2007-01-02-19:45:57 1000 2 610825811 DMON: CTL_GET_STATUS operation completed
Standby DB & Primary DB tnsnames.ora file content
StandbyDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = StandbyDB.qsvl.mobilearia.com)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = StandbyDB)
PrimaryDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = PrimaryDB.qsvl.mobilearia.com)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = PrimaryDB)
Appreciated your response and thank you in advance.
Regards,
~cs

ORA-16531 is an internal error. Open an iTAR.

ORA-00235 Standby Database Controlfile problem

Dear fellow dbas,
I am just starting to become acquainted with high availability and have to solve following problem.
We have a RAC database with a standby database that is out of sync. In fact the standby database is running in async mode but archived redo logs are not applied.
They are successfully forwarded from the primary instance to the standby db though. Looking at the alert.log I discovered an ORA-00235 error - control file fixed table inconsistent due to concurrent update.
As a result of this I have a huge gap between the primary and standby database.
Can you please give me a step to step tutorial, how I can resolve this issue?
Any help is appreciated!
Many thanks,
Sebastian

Hello Anand,
I am using 11.1.0.7.0.
My standby database is a cluster database as well. I shut both instances down using srvctl and created a standby controlfile from my primary instance, which I copied to the respective locations referred to in the spfile of my dataguard database. Afterwards I started up and issued a ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
The database does not open and the alert.log states ORA-01124 "cannot recover datafile 1 - file is in use or recovery".
Next, the background media recovery process was shut down.
What should I do, to get my standby back running?
Should I place the primary database in backup mode and copy the datafiles to my standby db?
Afterwards I would create a standby controlfile again and overwrite the standby ones.
Maybe you assist in pointing at the next steps.
Many thanks,
Sebastian

Problem creating a new spfile on a standby database.

I'm running an oracle 9.2.0.8 physical standby where I've changed some parameters creating a new pfile. The instance is working fine with this pfile, but I want to use an spfile. To do this, I've cancelled recovery, created a new spfile from the current pfile and shutdown the instance. Then the problem appears when I mount the instance. I check the parameters I've changed in the pfile and these changes are not present on my "new" spfile. If I take a look to spfile parameter...., my instance is running with old one! Do you have any suggestion about how to fix this?
Thanks in advance.

>
Did You restarted instance in order to use a new changed pfile?
And only after that created spfile?
>
Yes, I've restarted the instance to use the new pfile, and also after create the new spfile.
>
What You mean with "take a look to spfile parameter"?
You checked out and saw that database is still using pfile?
>
I've executed the following sentence:
"show parameter spfile"
and the output shows me that the file in use was the old one.
>
If you don't specify on startup what file to use spfile or pfile then oracle automaticaly looks into $ORACLE_HOME/dbs and search in this order:
* spfileSID.ora
* spfile.ora
* initSID.ora
* init.ora
Do you have under $ORACLE_HOME/dbs spfileSID.ora or spfile.ora?
>
I've the following files under $ORACLE_HOME/dbs:
* spfileSID.ora (that's the new spfile)
* initSID.ora (that's the old spfile)
* initxxxxx.ora (that's my custom pfile)
I've created the new spfile with my standby database on mount state, with the following sentence:
"create spfile from pfile"
When I restart the instance and try to mount it (using the new spfile), I get an ORA-00214 error.
So, I'm still running with my custom pfile.

The Critical Problems for Creating Standby Database

The Critical Problems for Creating Standby Database:(I want to create a physical standby database on the same system of the primary database)
1. Should I copy all the backup datafiles, standby controlfile and password file to a same directory before the first time to mount the standby database?
2. Before mounting the standby database, Should I change the datafile's name to a new one in the standby controlfile? How to change them?
3. When issuing the command to mount the standby database, should I specify the controlfile's name.(using which controlfile to mount)
These problems are not clearly secified in Oracle documentations.

Can you point us to the Windows specific documentation you refer to?
The parameter DB_FILE_NAME_CONVERT should take care of the new mapping for your datafiles (and LOG_FILE_NAME_CONVERT for logs), so you should be able to put them where you want and use the parameter to point Oracle to the correct location. You should not need to change the name in the controlfile.
Place your standby controlfiles where you have the control files defined in your parameter file and Oracle should recofgnise that it is a standby db. You should not need to specify which controlfiles to use (if this is even possible), your CONTROL_FILES init parameter points to them.
Not sure about the password file....my instances are on separate boxes and the password file has the same name on both primary and standby.

Problem in standby database

Similar Messages

Maybe you are looking for