Adding a physical standby using GridControl failed

Hi
I am trying to add a physical standby DB to a 10.2.0.4 database.
It failed at the end on the 'Step: Create Standby Database'
This is the log for this step ( step #79 ) - after backing up and restoring and after the recoverDatabase step
Output log :
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:13:44 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected.
SQL> SQL> SQL> ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:04 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected to an idle instance.
SQL> SQL> ORACLE instance started.
Total System Global Area 3221225472 bytes
Fixed Size          2044072 bytes
Variable Size          2315259736 bytes
Database Buffers     889192448 bytes
Redo Buffers          14729216 bytes
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:08 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> Connected.
SQL> SQL> 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
PL/SQL procedure successfully completed.
SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:08 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected.
SQL> SQL> SQL> ORA-01507: database not mounted
ORACLE instance shut down.
SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:14 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected to an idle instance.
SQL> SQL> ORACLE instance started.
Total System Global Area 3221225472 bytes
Fixed Size          2044072 bytes
Variable Size          2315259736 bytes
Database Buffers     889192448 bytes
Redo Buffers          14729216 bytes
Database mounted.
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:22 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected.
SQL> SQL> SQL> ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:39 2009
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> SQL> Connected to an idle instance.
SQL> SQL> ORACLE instance started.
Total System Global Area 3221225472 bytes
Fixed Size          2044072 bytes
Variable Size          2315259736 bytes
Database Buffers     889192448 bytes
Redo Buffers          14729216 bytes
Database mounted.
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/system011.dbf' to '/dg2/u04/oradata/dg2/system011.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/system011.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/undotbs011.dbf' to '/dg2/u04/oradata/dg2/undotbs011.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/undotbs011.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/sysaux011.dbf' to '/dg2/u04/oradata/dg2/sysaux011.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/sysaux011.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/users011.dbf' to '/dg2/u04/oradata/dg2/users011.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/users011.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/netrac_data01.dbf' to '/dg2/u04/oradata/dg2/netrac_data01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/netrac_data01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iview.dbf' to '/dg2/u04/oradata/dg2/iview.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iview.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/VCADMIN01.dbf' to '/dg2/u04/oradata/dg2/VCADMIN01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/VCADMIN01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/virt_cent_admin.dbf' to '/dg2/u04/oradata/dg2/virt_cent_admin.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/virt_cent_admin.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/testdir01.dbf' to '/dg2/u04/oradata/dg2/testdir01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/testdir01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/sunopsis.dbf' to '/dg2/u04/oradata/dg2/sunopsis.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/sunopsis.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/xpedio02.dbf' to '/dg2/u04/oradata/dg2/xpedio02.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/xpedio02.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/xpedio01.dbf' to '/dg2/u04/oradata/dg2/xpedio01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/xpedio01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/otis02.dbf' to '/dg2/u04/oradata/dg2/otis02.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/otis02.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/otis_data01.dbf' to '/dg2/u04/oradata/dg2/otis_data01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/otis_data01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ne_data.dbf' to '/dg2/u04/oradata/dg2/ne_data.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ne_data.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt2.dbf' to '/dg2/u04/oradata/dg2/iboss_dt2.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt2.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt1.dbf' to '/dg2/u04/oradata/dg2/iboss_dt1.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt1.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt.dbf' to '/dg2/u04/oradata/dg2/iboss_dt.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM3.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM3.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM3.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM2.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM2.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM2.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM1.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM1.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM1.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/users01.dbf' to '/dg2/u04/oradata/dg2/users01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/users01.dbf'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo01.log' to '/dg2/u04/oradata/dg2/redo01.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo02.log' to '/dg2/u04/oradata/dg2/redo02.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo03.log' to '/dg2/u04/oradata/dg2/redo03.log'
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
dgcreate.DGrecoverStby: SELECT FILE#, NAME from v$tempfile
dgcreate.DGrecoverStby: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/temp01.dbf' to '/tmp/temp16000'
dgcreate.DGrecoverStby: ALTER DATABASE TEMPFILE 3 DROP
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '/dg2/u01/arch/dg2' STANDBY DATABASE UNTIL CHANGE 9210711497140
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
dgcreate.DGcreateSpfile: CREATE SPFILE FROM PFILE='/dg2/u01/app/oracle/product/10.2/dbs/initdg2.ora'
dgcreate.DGaddTempfiles: ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-16000: database open for read-only access
ORA-06512: at line 26 (DBD ERROR: OCIStmtExecute)
the last line in the alert log were :
ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
Completed: ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
INSV started with pid=13, OS id=16351
and the tempfile was created successfully
Any ideas ?
How to debug ?
Orna

Hi
Just a follow up :
the problem was with a DDL database trigger, that is not sensitive to the read only mode of the standby database
disabling the DDL trigger solved my problem
Orna

Similar Messages

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

  • Physical standby using rman

    Step By Step Guide To Create Physical Standby Database Using RMAN
         Doc ID:     Note:469493.1
    says: Step 2: Move the backups to the standby server
    I'm a rman novice. What does that move look like? Do I copy the various files mentioned in the backup output, like /u01/oracle/product/ora10g/flash_recovery_area/ORA10G/backupset/2007_12_09/o1_mf_annnn_TAG20071209T145731_3oqf84xl_.bkp or is there some other glue that has to be performed to make the standby system see the backup correctly.
    Could I just tar up the FRA?

    Hi,
    You can place your backup whatever you find it appropriate and catalog it on the target server using catalog rman command.
    Your FRA can be large and it can take time to copy all content of FRA to target server.
    The best way to use backup ... format '<path_to_backup location>/bkp_%U'; Then copy backup piece(s) to target server and register with catalog start with '<path_to_backup location on target server';
    Best Regards,
    Alex

  • DG - creating physical standby using clone VMbox

    Hi,
    I have a VMbox 11.2.0.2 database prebuilt from "Oracle Developer Days".
    Then I clone it as "Oracle Developer Days Clone".
    Since they are now identical, How can I make the clone as my standby DB?
    Can I mount it as standby?
    Thanks,
    Petra-K

    Add to listerner.ora
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PLSExtProc)
          (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_2)
          (PROGRAM = extproc)
        (SID_DESC =
          (GLOBAL_DBNAME = orcl_stby)
          (ORACLE_HOME =/u01/app/oracle/product/11.2.0/dbhome_2)
          (SID_NAME = orcl_stby)
    GLOBAL_DBNAME will service name of standby database.
    Regards
    Mahir M. Quluzade

  • 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

  • Physical standby database fail-over

    Hi,
    I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
    I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
    Primary:
    alter system set log_archive_dest_state_2='DEFER';
    alter system switch logfile;
    Standby:
    alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
    Standby:
    alter database activate physical standby database;
    alter database open;
    shutdown immediate;
    startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
    RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
    RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
    1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
    2) Are all the old backups marked unusable after a fail-over is performed?
    FYI... flashback database was not used in this case as it did not server our purpose.
    Any information or documentation links would be greatly appreciated.
    Thanks,
    Harris.

    Thanks for the reply.
    The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
    Anyhow, we got the issue resolved. Below is the resolution path.
    1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
    Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
    If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
    So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
    After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
    Thanks,
    Harris.
    Edited by: user11971589 on Nov 18, 2010 2:55 PM

  • Unable to open the physical standby in read only  (10g)

    Hi,
    I m trying to create physical standby using RMAN to another server . But at the last step when trying to test Real Time Apply i m unable to open the standby in read only mode.Can Anyone please let me know whats the issue and how to resolve it
    SQL> select status from v$instance;
    STATUS
    MOUNTED
    SQL> alter database recover managed standby database using current logfile disconnect from session;
    Database altered.
    SQL>  alter database recover managed standby database cancel;
    Database altered.
    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:
    '/u01/app/oracle/product/10.2.0/oradata/test1/system.dbf'

    Hi,
    This is a newly created standby. I created just now. Below the o/p requested
    In Primary
    SQL> set line 200                                                                                                             
    SQL> set pagesize 200
    SQL> col message format a90
    SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message from v$dataguard_status where dest_id=2;
    SEVERITY      ERROR_CODE TO_CHAR(TIMESTAMP,'D MESSAGE
    Error              12541 04-MAR-2012 11:55:05 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
    Error              12541 04-MAR-2012 12:00:12 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
    Error               1034 04-MAR-2012 12:06:25 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
    Warning             3113 04-MAR-2012 13:21:24 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
    Warning             3113 04-MAR-2012 13:21:24 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error               3113 04-MAR-2012 13:21:24 PING[ARC1]: Error 3113 when pinging standby test1.
    Warning             3113 04-MAR-2012 13:33:29 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
    Warning             3113 04-MAR-2012 13:33:29 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error               3113 04-MAR-2012 13:33:29 PING[ARC1]: Error 3113 when pinging standby test1.
    Error               1034 04-MAR-2012 13:39:50 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
    Error               1034 04-MAR-2012 13:45:29 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
    Warning             3113 04-MAR-2012 13:57:56 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
    Warning             3113 04-MAR-2012 13:57:56 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error               3113 04-MAR-2012 13:57:56 PING[ARC1]: Error 3113 when pinging standby test1.
    14 rows selected.
    SQL> select     ds.dest_id id
    ,       ad.status
    ,       ds.database_mode db_mode
    ,       ad.archiver type
    ,       ds.recovery_mode
    ,       ds.protection_mode
    ,       ds.standby_logfile_count "SRLs"
    ,       ds.standby_logfile_active active
    ,       ds.archived_seq#
    from    v$archive_dest_status   ds
    ,       v$archive_dest          ad
    where   ds.dest_id = ad.dest_id
    and     ad.status != 'INACTIVE'
    order by
            ds.dest_id
    /   2    3    4    5    6    7    8    9   10   11   12   13   14   15   16 
            ID STATUS    DB_MODE         TYPE       RECOVERY_MODE           PROTECTION_MODE            SRLs     ACTIVE ARCHIVED_SEQ#
             1 VALID     OPEN            ARCH       IDLE                    MAXIMUM PERFORMANCE           0          0            64
             2 VALID     UNKNOWN         ARCH       UNKNOWN                 MAXIMUM PERFORMANCE           3          0            64In standby
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
       THREAD# MAX(SEQUENCE#)
             1             64
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;                    
       THREAD# MAX(SEQUENCE#)
             1             64
    SQL> select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    ARC0: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery starting Real Time Apply
    Media Recovery Waiting for thread 1 sequence 63
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    MESSAGE
    RFS[1]: Assigned to RFS process 9880
    RFS[1]: Identified database type as 'physical standby'
    Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_63_776981781.arc
    Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_64_776981781.arc
    Media Recovery Waiting for thread 1 sequence 65
    16 rows selected.

  • Data Guard - Physical Standby Setup by RMAN

    I am trying to set up a physical standby using RMAN. After I brought up the standby db, I failed to turn on redo apply. I found out that the standby redo log files were not copied over to the standby.
    The back up script I use is as follows.
    run {
    allocate channel ch2 type disk;
    backup current controlfile for standby format '/backups/sitv/cf_%d_t%t_s%s_p%p';
    backup format '/backups/sitv/%U.bkup' database;
    sql 'alter system archive log current';
    backup format '/backups/sitv/al_t%t_s%s_p%p.bkup' archivelog all;
    release channel ch2;
    What command should I use to be able to make a backup of the standby log files as well?
    Thanks.

    Hi Sybrand,
    Thank for the reply. Let me give a little bit more detailed information on what I did.
    I followed the documentation as follows to set up the physical standby
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
    I created the standby log files per section 3.1.3 on the primary db before the standby is created.
    I used the following command to restore the standby on a different server.
    run {
    allocate auxiliary channel ch1 device type disk;
    duplicate target database for standby dorecover nofilenamecheck;}
    My question is the standby log files did not show up on the standby server. However, the log files showed in the v$logfile table. After I tured on the redo apply, the changes I made in primary db did not happen in the standby db.
    Any idea on how to fix it?
    Thanks.

  • Data Guard Physical Standby Failover

    I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
    "During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
    vice
    "After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
    Much thanks.

    In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
    TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
    You can achieve this using FLASHBACK DATABASE option:
    From the documentation:
    After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
    Read the following documents:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
    In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
    "After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
    TRUE. If you enable Fast-Start Failover:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
    Cheers!

  • Physical Standby and Primary Hangs after Role Reversal

    Created Physical Standby using two machines.(10.2.0.2)
    Plugged it into Grid Control(R3)
    Tried to switch over. This was carried out successfully but then hanged while updateing the configuration. This is what I am getting in the drcMITDG.log on
    Primary:
    DG 2007-10-05-09:02:33 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:02:34 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:02:34 0 2 635079900 DMON: ENUM_DRC: success. (len = 987)
    DG 2007-10-05-09:02:34 0 2 635079900 DMON: ENUM_DRC operation completed
    DG 2007-10-05-09:02:47 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:02:47 0 2 635079901 DMON: ENUM_DRC: success. (len = 987)
    DG 2007-10-05-09:02:47 0 2 635079901 DMON: ENUM_DRC operation completed
    DG 2007-10-05-09:02:48 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:03:03 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:03:18 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:03:28 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:03:28 0 2 635079902 DMON: ENUM_DRC: success. (len = 987)
    DG 2007-10-05-09:03:28 0 2 635079902 DMON: ENUM_DRC operation completed
    DG 2007-10-05-09:03:33 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:03:48 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    DG 2007-10-05-09:04:03 0 2 0 DMON: Entered rfm_get_chief_lock() for CTL_SWITCH, reason 0
    SECONDARY:
    DG 2007-10-04-14:04:51 0 2 0 DMON: Health check master lock conversion successful
    DG 2007-10-04-14:04:51 0 2 0 DMON: a process acquired the healthcheck master lock
    DG 2007-10-04-14:04:51 0 2 0 DMON: posting primary instances for SWITCHOVER phase 5
    DG 2007-10-04-14:04:51 0 2 0 DMON: SWITCHOVER Completed with errors
    DG 2007-10-04-14:04:51 0 2 0 INSV: Received message for inter-instance publication
    DG 2007-10-04-14:04:51 0 2 0 Primary Site is named: MITDG_BACKREST
    DG 2007-10-04-14:04:51 0 2 0 req_id 0.0.0, opcode CTL_SWITCH, phase END, flags 5
    DG 2007-10-04-14:04:51 0 2 0 error = ORA-16509
    DG 2007-10-04-14:04:51 0 2 0 DMON: dispersing message to standbys for SWITCHOVER phase 5
    DG 2007-10-04-14:04:51 0 2 0 INSV: All instances have replied for message
    DG 2007-10-04-14:04:51 0 2 0 DMON: site 02001000, instance 00000001 queuing healthcheck lock re
    quest
    DG 2007-10-04-14:04:51 0 2 0 req_id 0.0.0, opcode CTL_SWITCH, phase END
    DG 2007-10-04-14:04:51 0 2 0 DMON: Releasing healthcheck master lock
    DG 2007-10-04-14:04:51 0 2 0 DMON: Health check master lock conversion successful
    DG 2007-10-04-14:04:51 0 2 0 DMON: a process acquired the healthcheck master lock
    DG 2007-10-05-08:48:42 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    DG 2007-10-05-08:48:52 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    DG 2007-10-05-08:49:07 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    DG 2007-10-05-08:49:22 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    DG 2007-10-05-08:49:37 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    DG 2007-10-05-08:49:52 1000 2 635079894 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason
    0
    Any idea what is going on..
    Thanks

    Hi, you must upraise a iTAR to Oracle Support for resolve this problem, because this behaviour is irregular and you will lost much time for analyze and resolve this problem.
    Regards.

  • Physical Standby -- Automate Startup under Windows

    I've created a physical standby using 9i on Win2003. It's working fine, but it won't come up automatically when the machine reboots. I've used ORADIM to create the service, and I can see in the registry that ORA_<sid>_AUTOSTART is set to TRUE, but after the machine reboots I have to manually:
    SQL> alter database mount standby database;
    SQL> alter database recover managed standby database disconnect;
    Apparently the problem is that the service is trying to open the database normally, not realizing that special commands need to be run to start a physical standby.
    I want the whole standby site to come up and run properly when the machine reboots. How can I set this up?

    Hi,
    You may try the following:
    modify the oracle service using oradim -edit starttype=service
    place your sql commands in a sql file, wrap it with a batch file and ask your NT administrator to run(prepare a script) the batch file immediately after startup.
    You sql file :
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    your batch file :
    set oracle_sid=<sid_here>
    sqlplus sys/pwd @SQLScript.sql
    HTH
    Regards,
    Badri

  • RMAN question concerning Physical Standby

    We have a database in a two-server Dataguard environment. We use RMAN to backup up the Primary database (on the server CORE), but we do not backup the Physical Standby (this was recommended by our vendor).
    Once a month, I switchover the Primary database (on the server CORE) over to the Physical Standby database (which is on the server DG). I apply Linux patches to the CORE server and reboot. I then bring up the database as Physical Standby (using "startup nomount", followed by "alter database mount standby database" and then "alter database recover managed standby database disconnect from session"), and then I do a switchover and make it the Primary again.
    My question is, after I bring up the database on the server CORE as a Physical Standby, and before I do a switchover to make it the Primary again, can I use RMAN to run a "restore database validate" to see if my backups are currently valid, or would this not give me the expected results since I am the Physical Standby?
    Thanks in advance.

    You should have any problem. What you're doing is similar to a a "rolling upgrade". When your physical to production environment make sure put the dest_2 in defer. Is your current physical standby works now? If so, there's problem.

  • 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

  • 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

Maybe you are looking for