SQL exception during creation of a physical standby database with EM

Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
=============
2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
=========
I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

Can you please tell me how can i see data gaurd on EM..
I have oracle 11gR1..i have implemmented primary as well standby database..
I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
You got error that means u did it using EM..how can i do it on EM

Similar Messages

  • What are the differences of creating a physical standby database with ASM?

    I want to create a physical standby database for my 10g(10.2.0.1) database. But it is using ASM. Is it possible to create a standby database for a database using ASM?
    What are the differences of creating a physical standby database with ASM?

    tell us what your research shows and we'll try to
    validate it. I am simulating Oracle ASM on a PC and I want to try
    DataGuard on it now. So I am trying to create DataGuard
    on an ASM system. The purpose is only learning and test.That's telling us how you are researching, not what you have observed.
    Your research could have included looking at the documetation, and you might have found http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#sthref1642
    which discusses exactly what you are looking for.
    Message was edited by:
    Hans Forbrich

  • 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

  • Physical Standby Database with slight complication

    Hello Database experts,
    Primary is a multi-node RAC instance , primarily two distinct schemas (for simplicity sake schema A on tablespace A1/A2 and schema B on tablespace B1/B2). There is a proposed physical standby database. Now primary is Enterprise Data warehouse with millions of updates per minute. Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.
    Any workaround possible?
    Assume that Hot backup of primary database backup has to be done so we can not perform nologging operations on schema A and Logical standby is not a option.
    Kind Regards,
    Sunil

    ***Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.***
    Yes. but not in physical standby. While bypassing the objects to physical standby the recovery cannot be enabled at the time. So data loss may occur. Try to configure logical standby database. you can get what you expect.
    thanks

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

  • Oracle Dataguard Question on Physical Standby Database with a Time Lag

    I have a Standby database (PROD_LAG) that has a delay of 24hrs. How do I check to see what Archive have applied, what is current, and what is left to do.
    There is a script but its for a Logical Standby database...
    Thanks you in advance...

    hi,
    ok a little bit more explanation.
    The GUI does work but seems to report incorrect data.
    I have carried out a switchover so the primary database is now 'offsite_emrep' and the standby database is 'office_emrep'
    The GUI how ever still reports that office_emrep is the primary database.
    I cannot add the offsite_emrep database as the host is unknown. I am however running the GUI from the Host.
    I have the following from the agent status
    [oracle@griddg bin]$ ./emctl status agent
    #Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.2.0.3.0
    OMS Version : 10.2.0.3.0
    Protocol Version : 10.2.0.2.0
    Agent Home : /u01/app/oracle/product/10.2.0/agent10g
    Agent binaries : /u01/app/oracle/product/10.2.0/agent10g
    Agent Process ID : 19797
    Parent Process ID : 19780
    Agent URL : https://griddg.domain.net:3872/emd/main/
    Repository URL : https://griddg.domain.net:1159/em/upload
    Started at : 2007-10-01 12:35:02
    Started by user : oracle
    Last Reload : 2007-10-01 12:35:02
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0.00
    Number of XML files pending upload : 116
    Size of XML files pending upload(MB) : 27.67
    Available disk space on upload filesystem : 83.08%
    Last attempted heartbeat to OMS : 2007-10-01 12:38:08
    Last successful heartbeat to OMS : unknown
    Agent is Running and Ready
    any help is appreciated.
    rgds
    alan

  • 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

  • Createing a physical standby database.

    Hi,
    Can we create a physical standby database with in a single system in windows.
    If possible please please help me how to do.
    Thanks and Regards
    Poorna Prasad

    Hi,
    After making changes in the pfile and when i am starting the database in nomount stage with pfile i am getting the following error
    SQL> startup nomount pfile='E:\oracle\product\10.2.0\db_1\database\initoracle.ora'
    ORA-16024: parameter LOG_ARCHIVE_DEST_1 cannot be parsed
    SQL>
    and my parameter file is
    oracle.__db_cache_size=427819008
    oracle.__java_pool_size=4194304
    oracle.__large_pool_size=4194304
    oracle.__shared_pool_size=167772160
    oracle.__streams_pool_size=0
    audit_file_dest='E:\oracle\product\10.2.0/admin/oracle/adump'
    background_dump_dest='E:\oracle\product\10.2.0/admin/oracle/bdump'
    compatible='10.2.0.1.0'
    control_files='E:\oracle\product\10.2.0/oradata/oracle/\control01.ctl','E:\oracle\product\10.2.0/oradata/oracle/\control02.ctl','E:\oracle\product\10.2.0/oradata/oracle/\control03.ctl'
    core_dump_dest='E:\oracle\product\10.2.0/admin/oracle/cdump'
    db_block_size=8192
    db_domain=''
    db_file_multiblock_read_count=16
    db_name='oracle'
    db_recovery_file_dest='E:\oracle\product\10.2.0/flash_recovery_area'
    db_recovery_file_dest_size=2147483648
    dispatchers='(PROTOCOL=TCP) (SERVICE=oracleXDB)'
    job_queue_processes=10
    open_cursors=300
    pga_aggregate_target=202375168
    processes=150
    remote_login_passwordfile='EXCLUSIVE'
    sga_target=609222656
    undo_management='AUTO'
    undo_tablespace='UNDOTBS1'
    user_dump_dest='E:\oracle\product\10.2.0/admin/oracle/udump'
    db_unique_name='oracle'
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(oracle,orap)'
    LOG_ARCHIVE_DEST_1= 'LOCATION=E:\oracle\product\10.2.0\flash_recovery_area\ORACLE\ARCHIVELOG/VALID_FOR=(ALL_LOGFILES,ALL_ROLES)DB_UNIQUE_NAME=oracle'
    LOG_ARCHIVE_DEST_2='SERVICE=orap LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=orap'
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=ENABLE
    LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    LOG_ARCHIVE_MAX_PROCESSES=30
    fal_server=orap
    fal_client=oracle
    standby_file_management=auto
    db_file_name_convert='d:\orap\data\','E:\oracle\product\10.2.0\oradata\oracle'
    log_file_name_convert='d:\orap\data\','E:\oracle\product\10.2.0\oradata\oracle','E:\oracle\product\10.2.0\flash_recovery_area\ORAP\ONLINELOG','E:\oracle\product\10.2.0\flash_recovery_area\ORACLE\ONLINELOG'

  • Create ONLINE logfile in physical standby database

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

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

  • Test physical standby database in dataguard

    Hi all,
    I had a successfull dataguard implementation for oracle 9r2.
    Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
    As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
    Now i want to test physical standby database with applications tier  but don't want to disturb origional primary database.
    as these are the normal switchover steps
    1) at primary db
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
    2) at standby
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
    3) at primary, now this will be the stand by database
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    4) at standby, now this will be the primary database
    SHUTDOWN IMMEDIATE;
    STARTUP
    My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
    Regards,
    Ken

    To avoid touching the primary production DB, you may try to use the following command on your standby database side:
    alter database activate standby database;
    This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
    Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

  • Standby database with different directory structure

    Hi,
    sorry to say that we are in desupported version due to some constraint.
    oracle version : 8.1.7.0.0.
    os:sun 5.9
    I need to create physical standby database with different directory structure:
    i have created standby database with same directory structure of primary, now i have requirement to create with different directory structure.
    in oracle 8i we can not give multiple parameter for db_file_name_convert(ORA-01678: parameter db_file_name_convert must be two strings, a pattern and a replacement) and i do have partitions in primary as follows:
    bash-2.05$ df -h
    Filesystem             size   used  avail capacity  Mounted on
    /dev/dsk/c1t0d0s0       20G    14G   5.6G    72%    /
    /proc                    0K     0K     0K     0%    /proc
    mnttab                   0K     0K     0K     0%    /etc/mnttab
    fd                       0K     0K     0K     0%    /dev/fd
    swap                    11G    40K    11G     1%    /var/run
    dmpfs                   11G     0K    11G     0%    /dev/vx/dmp
    dmpfs                   11G     0K    11G     0%    /dev/vx/rdmp
    swap                    11G   656K    11G     1%    /tmp
    /dev/dsk/c1t0d0s3       25G    18G   6.8G    72%    /oracle
    /dev/vx/dsk/suportaldg/oracle1
                            12G    11G   1.1G    91%    /oracle1
    /dev/vx/dsk/suportaldg/oracle2
                            12G   8.1G   3.7G    69%    /oracle2
    /dev/vx/dsk/suportaldg/orapurge
                           200G   182G    17G    92%    /orapurge
    /dev/vx/dsk/suportaldg/oracle3
                            12G    10G   1.9G    85%    /oracle3
    /dev/vx/dsk/suportaldg/oracle4
                            12G    12G    58M   100%    /oracle4
    /dev/vx/dsk/suportaldg/oracle5
                           7.0G   5.9G   1.0G    86%    /oracle5
    /dev/vx/dsk/suportaldg/oracle6
                           7.0G   6.4G   564M    93%    /oracle6
    /dev/vx/dsk/suportaldg/oracle7
                            23G    23G   358M    99%    /oracle7
    /dev/vx/dsk/suportaldg/oracle8
                            13G    13G   165M    99%    /oracle8
    /dev/vx/dsk/suportaldg/oracle9
                            23G    22G   1.4G    94%    /oracle9
    /dev/vx/dsk/suportaldg/oracle10
                            12G  10.0G   1.9G    85%    /oracle10
    /dev/vx/dsk/suportaldg/oracle11
                            39G    36G   2.1G    95%    /oracle11
    /dev/vx/dsk/suportaldg/oracle12
                            39G    38G   1.1G    98%    /oracle12
    /dev/vx/dsk/suportaldg/oracle13
                            68G    65G   2.6G    97%    /oracle13
    /dev/vx/dsk/suportaldg/oracle14
                           200G   199G   1.3G   100%    /oracle14
    /dev/vx/dsk/suportaldg/oracle15
                           200G   196G   3.6G    99%    /oracle15
    /dev/vx/dsk/suportaldg/oracle16
                            70G    64G   5.5G    93%    /oracle16
    /dev/vx/dsk/suportaldg/oracle20
                           7.0G   6.4G   609M    92%    /oracle20
    /dev/vx/dsk/suportaldg/oracle50
                            28G    26G   2.0G    93%    /oracle50
    /dev/vx/dsk/suportaldg/oratranslog
                           185G   165G    19G    90%    /oratranslogso how i can create standby database with different directory structure, help is appreciated.
    Thanks
    Edited by: prakashdba on Mar 5, 2009 11:04 PM

    Looks like very difficult and inform you mgmt about the drawbacks of running olderv ersions
    may be you can try something like this but i dont know whether it is supported or not
    db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle3','/dev/vx/dsk/suportaldg/STDBY/oracle3']
    db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle4','/dev/vx/dsk/suportaldg/STDBY/oracle4']
    db_file_name_convert=['/dev/vx/dsk/suportaldg/oracle5','/dev/vx/dsk/suportaldg/STDBY/oracle5']

  • Physical standby database Version 11g Creation over grid control 10g

    We are useing oracale 11g enterprise edition and want to create a physical standby database on another machine:
    On primary host we've installed "standard database" and turned on archive log mode over em.
    On the standby host we've installed only oracle without a database and without a listener.
    On a third machine we've installed grid control and registered the primary and standby hosts. Using EM with Data Grid I'm attempting to create a Physical Standby on standby host. Everything is working except for the last part as noted here:
    SQL*Plus: Release 11.1.0.6.0 - Production on Do Apr 3 11:21:17 2008
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    SQL> SQL> Bei einer nicht hochgefahrenen Instance angemeldet.
    SQL> SQL> ORA-32004: obsolete and/or deprecated parameter(s) specified
    ORACLE-Instance hochgefahren.
    Total System Global Area 535662592 bytes
    Fixed Size          1334380 bytes
    Variable Size          167773076 bytes
    Database Buffers     360710144 bytes
    Redo Buffers          5844992 bytes
    SQL>
    Datenbank wurde geändert.
    SQL> Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSTEM01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSAUX01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\UNDOTBS01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\USERS01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\EXAMPLE01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO01.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO01.log'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO02.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO02.log'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO03.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\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: ALTER DATABASE RECOVER AUTOMATIC FROM '%ORACLE_HOME%\RDBMS' STANDBY DATABASE UNTIL CHANGE 1061001
    dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
    dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
    SQL Error: ORA-16004: Sciherungs-Datenbank muss wiederhergestellt werden
    ORA-01152: Backup-Datei zum Wiederherstellen der Datei 1 war nicht alt genug
    ORA-01110: Datendatei 1: 'C:\ORACLE\PRODUCT\11.1.0\DB_1\ORADATA\DG3\SYSTEM01.DBF' (DBD ERROR: OCIStmtExecute)
    What is to do?
    What mean's in this case:
    "ORA-01152 file string was not restored from a sufficiently old backup
    Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
    Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery."

    Thanks for your immediate reply,
    but there's a problem: We don't create the standby database manually. The creation is done by data guard over grid control. And the "automatic" creation stopps at this point.
    Unfortunatly we don't know, wich steps of a manuall standby database creation are done and wich steps are not done at this point.
    The oracle documentation (for release 11g) to create a manuall standby database is "B28294-02". But there's no step 5 "alter database recover managed standby database disconnect from session". Do you mean step 4 of chapter 3.2.6?
    Is there no way, to create a standby database automatically over grid control? Or do we have to do something else before creating the physical standby database? Perhaps we have to create a full backup after switching to archive log mode?

  • Physical Standby Database Creation with RMAN

    Hi,
    I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
    and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
    In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
    In F.1.1 page F-2 it is said :
    See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
    Any way I'm looking for a procedure or clear article to create it.
    Many thanks before.

    Physical Standby Database Creation with RMAN
    Use the DUPLICATE command.
    Check out this metalink doc: Note:374069.1 and Note:118409.1
    Message was edited by:
    STW
    Message was edited by:
    STW

  • RE logical/physical standby database

    1. Why logical standby database is SQL apply, and Physical standby database is redo apply? What ‘s the meaning/objective for that? (pls don’t tell me what is SQL/redo apply)
    2. As we know, a logical standby database can be used for reporting and querying if primary database is down, why we still need a physical standby database (it can’t do that during recovering process, it just a same copy of primary database)? Why not just go ahead to set up only a perfect logical standby database? (just because logical one can’t accommodate all kinds of data type???)
    3. Combined with Real time Apply and maximum protection, we can achieve a zero data loss, but could we achieve a zero downtime? Why or why not?

    Go Through Below link
    >>>Can you convert a Logical standby to a Physical Standby?

  • How to convert logical standby database to Physical Standby Database

    Hi,
    Does anyone know how to convert logical standby database(10.2.0.3) to Physical Standby Database(10.2.0.3)? Is this possible? If so,please give me steps for it.
    Thanks.
    Regards,
    RJ.

    I don't believe this to be possible. One of the steps invloved in the creation of a logical standby is the following:
    ALTER DATABASE OPEN RESETLOGS;
    This makes the logical standby a different incarnation of the db from the primary.
    A physical standby is a binary copy of a primary db, a logical standby is a completely seperate db that just happens to get sql statements applied to it that are generated from a primary db, but is open read/write.
    One avenue, though would be if you had flashback database enabled and you flashed back all the way to when the db was a physical standby and then rolled forward with the archived redo logs.
    It's somewhat unlikely you are in that situation, but that is a possibility.
    Indeed the 11g snapshot standby does this sort of thing:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#sthref740
    jason.
    http://jarneil.wordpress.com

Maybe you are looking for