Create Physical Standby fails

It looks like a script that runs, Exits in the middle.
I am able to test a disk dump and execute host commands on both the source and destination server.
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:49 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
set echo off>Connected. GridTest>GridTest>GridTest>GridTest>GridTest> 2 3 4 5 6 7 8 9 10 11 12 13 Row count
: 1 Start printing spfile value: spfile# G:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SPFILEGridTest.ORA PL/SQL procedure successfully completed.
GridTest>Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL*Plus
: Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:50 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
CONNECT sys/#GridTest# AS SYSDBA;>ORA-01012: not logged on CONNECT sys/#GridTest# AS SYSDBA;>

Sounds like you are loosing the network connection between your OMS and
the standby target? Check the network.
Regards,
Porus.

Similar Messages

Create physical standby failed at destination preparation step

I have tried several times to create a physical standby using Grid Control. Everytime, the job failed at the step "Destination Preparation". The log file indicated the following error message:
PLS-00553: character set name is not recognized.
This is because an extra word "PuTTY" was inserted into the spfile as shown in the following spfile, therefore, the instance cannot be started. In addition, everytime when issuing the command "cat spfilermslag.ora", the word "PuTTY" will automatically appear in the command line after the "cat spfilermslag.ora" command.
$ cat spfilermslag.ora
gé ú&PuTTYrmslag.__db_cache_size=150994944
rmslag.__large_pool_size=4194304
rmslag.__shared_pool_size=71303168
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/rmslag/udump'
[oracle@wppnode2 dbs]$ PuTTY
What is going on here? How can I fix the problem?
Thanks!

You can still carefully use the corrupted spfile to create a pfile and start your database with teh pfile, then create spfile from the pfile.
Make a copy of the spfilermslag.ora sand save it as initrmslag.ora. Open the spfile with notepad, carefully remove all the wrong characters at the begining and end of the file. Use the init file to startup the database
SQL>connect sys as sysdba
SQL>startup spfile=$ORACLE_HOME/dbs/initrmslag.ora
SQL>create spfile from pfile;
SQL>shutdown immediate
SQL>startup

Error while creating physical standby database using Oracle Grid 10.2.0.5

Hi All,
I am setting up data guard using oracle grid.
Primary database version: - 10.2.0.4
Standby database version: - 10.2.0.4
Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
Fatal NI connect error 12533, connecting to:
(DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 10.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 17-AUG-2010 02:40:07
Tracing not turned on.
Tns error struct:
    ns main err code: 12533
    TNS-12533: TNS:illegal ADDRESS parameters
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0As we can see, address_list is empty.
Can anyone suggest what could be the reason behind this?

Dear user13295317,
Here is the error explanation;
Oracle Error :: TNS-12533
TNS:illegal ADDRESS parameters
Cause
An illegal set of protocol adapter parameters was specified.
In some cases, this error is returned when a connection cannot be made to the protocol transport.
Action
Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA.
Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
Ogan

Problem creating physical Standby database with RMAN

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

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

Problem in identifying control file when creating physical standby

hi there,
(database version: 10.2.0.4
plateform linux)
I'm using the command as below to create physical standby database from backup:
rman target / auxiliary sys/tiger@paceview
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PACEVIEW (DBID=2092349485)
connected to auxiliary database: PACEVIEW (not mounted)
run {
allocate auxiliary channel c1 device type DISK;
set until sequence 38;
duplicate target database for standby dorecover nofilenamecheck;
released channel: ORA_DISK_1
allocated channel: c1
channel c1: sid=35 devtype=DISK
allocated channel: c2
channel c2: sid=36 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 04-SEP-12
contents of Memory Script:
   set until scn 138180211934;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 04-SEP-12
channel c1: restoring control file
ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/backup/rman/paceview/DEL1_standby.ctl)
ORA-19601: output file is control file (/PGHProdDB/oradata/paceview/control1.ctl)
failover to previous backup
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
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 restorei have already tried crosscheck but still giving same error
thanks

Hello;
So this is what I would do :
Backup Primary ( change to your directory as need )
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Move the backup and duplicate like this :
rman target sys/password@PRIMARY auxiliary /
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}For complete details of this method see :
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

Problem While Creating Physical Standby Using RMAN

Hi Guru's
May be this incidence you all face while creating physical standby DB. I try to create Physical standby database Using RMAN Duplicate Command from one server
(pri machine) to Standby Machine.
The steps i followed to create the above are as follows:
Step 1:- Enable Forced Logging
SQL> ALTER DATABASE FORCE LOGGING;
Step 2:- Configure a Standby Redo Log
SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
Step 3:- Set Primary Database Initialization Parameters
SQL> create pfile='?/dbs/pfileorcl.ora' from spfile;
Edit the pfile to add the standby parameters, here shown:
db_unique_name='orcl'
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,orcldr)'
LOG_ARCHIVE_DEST_2='SERVICE=orcldr LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcldr'
*.fal_server=orcldr
*.fal_client=orcl
*.standby_file_management=auto
Step 4:- Enable Archiving
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE OPEN;
Step 5:- Setup tnsnames for standby database
This should be done on primary database by altering tnsnames.ora or using NetCA command, and create it by the name orcldr
orcldr =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = standby-svr)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcldr)
Step 6:- Backup database and copy it to standby
This backup script should be run on primary and copied to standby on the same mount point, running this scripts using RMAN, all files under /rman_backup should be copied to /rman_backup on standby server.
$rman target /
RMAN> run
allocate channel c1 type disk;
allocate channel c2 type disk;
backup database format '/rman_backup/%U';
backup archivelog all format '/rman_backup /%U';
backup current controlfile for standby format '/rman_backup/%U';
Step 7:- Standby Database Steps
Installing Oracle Software
This should be same release and patchset with exactly same ORACLE_HOME mount point.
Setting Up listener
Create and start a listener on standby database using NetCA, or creating listener.ora in $ORACLE_HOME/network/admin
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby-svr)(PORT = 1521))
Step 8:- Set Standby Database Initialization Parameters
Copying the pfile created in primary database and renames it to initorcldr.ora, and changes these parameters:
db_unique_name='orcldr'
LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcldr,orcl)'
LOG_ARCHIVE_DEST_2='SERVICE=orcl LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl'
*.fal_server=orcl
*.fal_client=orcldr
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
Step 9:- Setup tnsnames for primary database
This should be done on standby database by altering tnsnames.ora or using NetCA command, and create it by the name orcl
orcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = primary-svr)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
Step 10:- Copy a Password File
A password file must be created on the Primary and copied over to the Standby site. The sys password must be identical on both sites. Copy orapworcl to $ORACLE_HOME/dbs and rename file to orapworcldr
Step 11:- Create mount points for Oracle
Mount point should be created on standby server with the same convention used in primary, this includes the location for controlfiles, redo logs, datafiles, archive log destination and alert logs.
$ mkdir -p /u01/app/oracle/oradata/orcl/
$ mkdir -p /u01/app/oracle/flash_recovery_area/
$ mkdir -p /u01/app/oracle/admin/orcl/adump
$ mkdir -p /u01/app/oracle/admin/orcl/bdump
$ mkdir -p /u01/app/oracle/admin/orcl/cdump
$ mkdir -p /u01/app/oracle/admin/orcl/udump
Step 12:- Use RMAN to restore backup and setup standby
Connect to RMAN and execute the following command to create standby database, this should be performed on standby server after copying backup and setting tnsnames.
$ export ORACLE_SID=orcldr
$ rman target sys/tiger@orcl auxiliary sys/tiger@orcldr
RMAN> duplicate target database for standby dorecover;
Here i am getting problem as :
While trying to connect to traget database and auxiliary database i notice that when RMAN is connect to both databases it shows
orcl ( DBID xyz)
orcl (not mounted)
Here in my view the second database must be standby database name or auxiiary db name is standby db name which in my case is orcldr
after this issue i am facing the second issues as :
in command
duplicate target database for standby dorecover;
After modifying the command to
RMAN> duplicate target database to "standby";
rman-05520 database name mismatch
Can u please let me know where i am mistaking

ok for pri:
db_name=orcl
db_unique_name=orcl
for standby:
db_name=orcl
db_unique_name=sbyorcl ( i change orcldr to sbyorcl later)for new testing
but now what i am getting on
Verify connectivity
On Primary Server:
C:\> lsnrctl stop LISTENERI (working fine)
C:\> lsnrctl start LISTENER (working fine)
C:\> tnsping orcl (working fine)
C:\> tnsping sbyorcl (working fine)
C:\> sqlplus sys/xxxxx@orcl (working fine)
C:\> sqlplus sys/xxxxx@sbyorcl (not working fine)
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
On Standby Server:
C:\>lsnrctl stop LISTENER
C:\> lsnrctl start LISTENER
C:\> tnsping orcl
C:\> tnsping sbyorcl
C:\> sqlplus sys/xxxxx@orcl
C:\> sqlplus sys/xxxxx@sbyorcl
My listner file for pri :-
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = orcl)
      (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
      (SID_NAME = ORCL)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
tnsnames.ora file on pri is:
sbyorcl =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = sbyorcl)
ORCL =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = orcl)
and listener file on standby :
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = PLSExtProc)
      (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
      (PROGRAM = extproc)
    (SID_DESC =
      (GLOBAL_DBNAME = orcl)
      (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
      (SID_NAME = orcl)
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
and tnsnames.ora file on standby:
ORCL =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = orcl)
sbyorcl =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
(CONNECT_DATA =
       SERVICE_NAME = sbyorcl)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (CONNECT_DATA =
      (SID = PLSExtProc)
      (PRESENTATION = RO)
Kinldy guide me where i am mistaking it's urgent

How to create physical standby database without dataguard

Hi,
Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
Please find the specifications of my server :
Database : Oracle 10.2.0.1(Standard Edition)
Server : Linux 4.0(32 bit machine)
As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
Thanks in advance.
Regards,
Farooq

Hello,
I hope this link helps you out...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA
Edited by: Pratik.L on Dec 31, 2009 12:03 PM

Creating physical standby databases with DG Broker & OEM

Hi guys,
I manage 8i, 9i & 10g databases through OEM 10.2.0.2.
Today, I would like to create physical standby db for the most important applications. Because I'm a lazy guy, I'd like to do it the easiest way, with GUI and wizzards provided by OEM.
1. Do you know any tutorial on the Internet that would help to do it easily ? My only source up to now is the official DB broker documentation (http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/toc.htm), which is 300 pages long like every Oracle doc. I'd appreciate any tutorial that could lead me straight to the essential. I've heard that is not so tricky to create a physical standby db
2. Is the procedure really different to create (and then manage) a physical standby database on Oracle 8i, 9i and 10g ? Is it possible to do it through DB Broker and OEM for every version ?
thank you for your help
Antoine

Antionio,
Oracle Documentation is the best source of configuring any Oracle component.
But, If you do not want to read the entire doc, and want to configure Dataguard Broker (without OEM), then here is the Link.
http://www.oracledba.org/10g/dr/10gR2_dataguard_RAC_to_RAC.html#Configure_Dataguard_Broker:

Switchover to physical standby failed

Hi gurus,
Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
SQL> alter database commit to switchover to physical standby;
alter database commit to switchover to physical standby
ERROR at line 1:
ORA-16014: log 1 sequence# 91775 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
Please advice
regards,
shaan

Hi,
There is already a thread which you opened Up you can reply back in that..
switchover to physical standby failed
- Pavan Kumar N

Creating physical standby database on same machine with dataguard

hi every one
i m new in oracle databases,
i read documentation to create physical standby databases,
now i install virtual machine (vmware) on my system,
i install windows xp on this vm and oracle 9i
now i want to create standby database on the same machine in some other drive configured with datagurd
virtual machine
OS windows xp
database oracle 9i
plz reply me how i do this
explain clearly step by step.
plz reply me in detail

When you need to have the standby database on the same server as the master, use lock_name_space in the init.ora.
This parameter permits this to occur without having to worry about changing the db_name.
http://www.oug-ottawa.org/pls/htmldb/f?p=103:21:729607614317189728::::P21_TIP_NUM:821

Creating physical standby through Cloud Control 12C fails

Hi,
I have a SR with MOS on physical standby setup through Cloud Control 12C. My setup is two Exadata Quarter RAC X2-2 installations and i'm setting up primary standby/between those two installations. Lets call them exa1db01(primary) and exa2db01(standby).
I'm using Cloud version 12.1.0.2 and agents on the latest version and patch. We just upgraded before Christmas. When i try to create a physical standby it fails on the transfer stage with below error:
"Uncaught exception in command fileTransfer: unable to instantive value javax.xml.bind.JAXBE1ement@46dd1e39 for attribute actualException"
At the moment its sent to developement so i have to wait for a fix. The reason for posting here is that i cant believe that this is not working on Cloud Control 12.1.0.2. This is basic functionality and i'm amazed that this is a bug. Our Exadata installation is running on 11.2.0.3 BP10 so it should be fairly fresh.
I truly believe the problems needs to be somewhere in our installation or the connectivity between our Exadata environments. Do any of you have any experience with DG through Cloud on that participial version ?
Cheers

Hello again;
Check the solution in this: ( and note the multiple versions of oracle it covers )
UNABLE TO FIND GRID INFRASTRUCTURE LISTENER (Doc ID 1483234.1)
Best Regards
mseberg

Creating physical standby using rman fails with ORA-19558: error de-allocat

Dear All,
We are creating physical stadnby database from 2 node RAC ( 2 node RAC to standalone physical standby).
While in the rman duplicate process we are getting below error, we were not able to sorted out..
No third party storage has been used ....
DB version : 11gR2 and the OS is RHEL5
Appreciate if any one hepl us to resolve this issue ...
Thanks in advance ...
RMAN-03009: failure of backup command on prmy1 channel at 10/05/2011 17:59:26
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03113: end-of-file on communication channel
Edited by: 889828 on 2011/10/06 2:17 AM

The problem is well decribed in your alert log.....you are using Oracle Managed File names which means you will not be able to duplicate the database as RMAN won't be able to automatically generate new names for the files using the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters.
Youll have to use the SET NEWNAME command to specify the names of the database files. Done this a few times , and I don't recommend using OMF specifically beacuse of this hassle.
WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.
Problem handling is described in
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)
Part Number B14194-03

Problem while creating Physical standby database on remote Server

Hi
I try to create a physical standby datbaase using OEM 10gr2, it is working when I create on same server. No issue but when I try to create same on remote server it is giving below warning and process failing. Please let me know what needs to be down in this senario...
It is showing redo log information in v$log and v$log_file but not creating physically on PHYSICAL Standby instance..
I appriciate your help and ur time too..
These messages are from PRIMARY database alert*.log file
There is space for up to 12 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;
WARNING: OMF is enabled on this database. Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames.
Thanks and Regards,
RK

Well, it is simply warning that "Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames"
For instance, the path for the logfile name in "ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800" may need to be changed manually. It is advisable to check the mentioned documentation.

Create physical standby database via grid control Errror

Hi
I wonder if anyone has seen the following problem
I am creating a standby database using EM Grid Control wizard. It all configures fine and starts the job goes through all steps including copying datafiles etc. but when it hits the step CREATE STANDBY DATABASE it fails with no explanation. In the oms log all it says is an error about cant find the sid name
EM Grid COntrol is 10.2.0.5 version
Windows Primary is Windows 2003 server 10.2.0.4 db
Trying to create on windows 2003 server with same oracle version
Thanks
D

Did you search the same on Metalink ?
please also cehck
EM: Creation process for a physical standby DB failed with SQL Exception
Regards
Rajesh

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 Physical Standby fails

Similar Messages

Maybe you are looking for