UDM on physical standby database in grid control 11.1

I am getting
Test Results
ORA-06550: line 70, column 5: PLS-00201: identifier 'RAISE_APPLICATION_ERROR' must be declared ORA-06550: line 70, column 5: PL/SQL: Statement ignored
While creating UDM on physical standby database in grid control 11.1. Please help me how to resolve this. I am able to create UDM on normal or primary databases.

What credential is defined?
Fairly certain only a sysdba connection will work unless the recovery is stopped and switched to read-only. Or when it becomes primary ...

Similar Messages

  • 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 standby database through Grid Control.

    Hi,
    I want to know if source database which we term as primary database goes down during Db creation process when given option of "Perform a live backup of primary database" during Add standby wizard in Grid Control. Please let me know if people have already tested it in their environments.
    I appreciate you all for looking into my forum.
    Regards,
    Gaurav

    No, one of the options for performing this task is to create from a Live db.
    A couple of things to note here:
    You must be using spfile
    If you are not using the default port of 1521 then you must also have the local_listener parm set
    I recommend using the "db_unique_name" option to make it easier to manager in OEM (for the target name)
    Hope this helps,
    Landon

  • Error while setting up Standby database using Grid Control

    I am getting this on grid control 10.2 on windows env while creating standby database using EM. I have checked this folder and it does exists.
    any ideas?
    C:\oracle\ora10.1\network\admin\listener.ora: java.io.IOException: The system cannot find the path specified

    There is no problem tnsnames.ora & listener.ora since I am getting the same error for just standby backup also.
    this is error on emoms.trc file
    2007-07-18 13:19:37,318 [EMUI_13_19_37_/console/database/instance/sitemap] ERROR perf.sitemap setMaintenancePage.1812 - java.sql.SQLException: ORA-00933: SQL command not properly ended
    ORA-06512: at "SYSMAN.ECM_UTIL", line 509
    ORA-06512: at line 1
    java.sql.SQLException: ORA-00933: SQL command not properly ended
    ORA-06512: at "SYSMAN.ECM_UTIL", line 509
    ORA-06512: at line 1
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
         at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
         at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:180)
         at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:869)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1153)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2932)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3023)
         at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4132)
         at oracle.sysman.util.jdbc.PreparedStatementWrapper.execute(PreparedStatementWrapper.java:173)
         at oracle.sysman.util.jdbc.CallableStatementWrapper.execute(CallableStatementWrapper.java:135)
         at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.getClonableHomes(CloneHomeSql.java:449)
         at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.getClonableHomes(CloneHomeSql.java:561)
         at oracle.sysman.eml.ecm.cloneHome.repaccess.CloneHomeSql.isHomeClonable(CloneHomeSql.java:363)
         at oracle.sysman.db.adm.inst.SitemapController.setMaintenancePage(SitemapController.java:1807)
         at oracle.sysman.db.adm.inst.SitemapController.setRequestAttributes(SitemapController.java:1385)
         at oracle.sysman.db.adm.BaseController.handleEvent(BaseController.java:1154)
         at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:577)
         at oracle.sysman.db.adm.RootController.handleRequest(RootController.java:174)
         at oracle.sysman.db.adm.DBControllerResolver.handleRequest(DBControllerResolver.java:114)
         at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:781)
         at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:337)
         at oracle.sysman.eml.app.Console.doGet(Console.java:318)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:88)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
         at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
         at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:20)
         at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:336)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
         at java.lang.Thread.run(Thread.java:534)
    2007-07-18 13:19:42,505 [EMUI_13_19_42_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
    2007-07-18 13:19:44,224 [EMUI_13_19_44_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
    2007-07-18 13:19:46,052 [EMUI_13_19_44_/console/database/dataguard/create] ERROR em.dataguard mapHelpPage.2002 - StandbyUtil.mapHelpPage: dghelp for database/dataguard/createSchedule not mapped to any help ID.. Defaulting to oemdba_consens_data_guard_page
    2007-07-18 13:19:47,130 [EMUI_13_19_47_/console/database/dataguard/create] ERROR em.dataguard validate.1118 - CreateBean: ClassNotFoundException: null
    2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone createTemplate.379 - TemplateManager.createTemplate(): Exception: java.io.IOException: The system cannot find the path specified
    2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone submitJobPreparation.3013 - DBCloneObject.submitJobPreparation(): Exception: java.io.IOException: The system cannot find the path specified
    2007-07-18 13:19:53,052 [Thread-85] ERROR jobs.dbclone submitDBCloneJob.3228 - DBCloneObject.submitDBCloneJob(): Exception: The system cannot find the path specified
    2007-07-18 13:19:58,006 [EMUI_13_19_58_/console/database/dataguard/create] ERROR em.dataguard onEvent.1038 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: The system cannot find the path specified

  • Creating physical standby db through grid control 11g fails with "default listener is not running"

    On step 4/6, i am getting error like below
    ErrorExamine and correct the following error(s), then re-try the operation.Default Listener in Grid Infrastructure - The default listener in the grid infrastucture is not running.
    I have the listener running on grid user and grid home, 11.2 in both primary and standby.
    During these steps till 4, its no where asked for grid user password.
    Not sure how it will detect the grid home listener.
    Listener is running with default port 1521 on both the servers primary and standby
    On the step 4 screen the other option for default listener is non-default listener and its pointing to db home and not grid home.
    So i guess oracle is looking for the listener to be up on the db home and not on grid home causing the issues,
    if so how to fix this ?
    I am using role separation, separate user for grid and oracle homes grid and oracle user and all are on 11.2.0.1 db + grid

    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

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

  • 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

  • Cannot Clear Critical Alert for Physical Standby Databases

    10.2.0.4.0 Grid Control monitoring 10.2.0.4.0 databases and standby databases with 10.2.0.4.0 agents.
    The standby databases are running on Xen guests. The O/S is Red Hat 4 Advanced Server.
    I had a failure of Xen guest on Saturday that caused me to have to rebuild the standby servers. EM Grid Control successfully verifies the configurations and the status is normal for both physical standby databases. (A rebuilt logical standby database shows no alerts.)
    Grid Control database targets page shows a single critical alert for each physical standby database. The alert is for "number of missing media files is 4". The metric graph shows the count as 0 since before the rebuilds. I cannot clear the alerts from the Critical Alerts page. Grid Control reports "The selected alert(s) cannot be manually cleared. They will clear automatically once the metric is no longer in a critical or warning state.".
    Any suggestions?
    Thanks,
    Ray Westphal

    Thanks for the reply Anthony.
    The result of the query on both standby databases is '0'. The metric graph also shows the value at '0' since before rebuilds.
    And the OMS db and agents have been reset several times since I posted this.
    Ray Westphal.

  • Standby Database for GRID instance

    Hi All,
    I have a requirement from a client to provide a Standby database (Physical or Logical) for the GRID control instance. Baffled by this, I tried to explain that the GRID instance is very small and may not require a standby. The client is adamant.
    So, has anyone had any experience (experimental or otherwise) of configuration of a standby for GRID?. If so, how? and which would be a feasible option, Physical or Logical?
    Any feedback is appreciated.
    Regards,
    Timothy.

    The search function on here isn't great, it took me longer than I care to admit to find you this:
    OMS question on Physical Standby database
    If you need clarification on anything, shout. Like I said, its a pain to do.

  • Oracle Configuration Manager 10.2.7  on physical standby database

    Hi
    Did anybody succeed to install and get running OCM on physical standby-database? When starting collection configuration script, i get
    an known error ORA-01219.
    Any help any tipps?
    Felice

    Hi Tom
    Thank you for the information. I think it is the right place to install OCM - not standalone installation - software installed with Oracle Database Enterprise Edition. The problem is only that installCCRSQL.sh can't handle Mounted Database (Standby-Database).
    We got similar problems with Grid Control Management Agents, when doing health checks.
    Mayby there is as workaround/patch (Opatch).
    Regards
    Felice

  • OEM for physical standby database

    Hello All,
    I am using Oracle 11.2.0.3. My enterprise manager is db console 11.2
    I have Oracle Enterprise manager dbcnsole for my RAC primary database  and I have created through sqlplus command line a physical standby database.
    My questions
    Can I use the RAC primary dbconsole to monitor my physical standby database? if yes what the steps?
    Is it mandatory to use grid control in that case? if yes, what steps are needed to implement grid control ?
    Regards,

    Hi,
    It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control.  This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
    If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
    Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality).  In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
    Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
    Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
    Using EM cloud control 12c is best available option to monitor your standby databases
    For install docs refer to
    http://docs.oracle.com/cd/E24628_01/install.121/e22624/toc.htm
    For Software download link
    http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
    Regards,
    Rahul

  • 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

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

  • Issue with physical standby database not in sync with primary

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

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

  • Problem discovering 9.2.0 physical standby database in 10GR1 OEM

    We have a Dataguard test setup in our company which was done using 9.2.0 OEM consisting of two 9.2.0 databases(one primary and another physical standby).
    I could get the 10GR1 agent discover the primary database properly, but couldnot discover the physical standby database? The 10GR1 agent on the remote host is running fine, but just not discovers the database that is in physical standby mode and running fine.
    Any suggestions???

    Have you tried manually adding the standby?
    Note that in grid, in the monitoring configuation screen, use the sys as sysdba account, dbsnmp doesn't have enough privileges.
    Bazza

Maybe you are looking for