Package in a standby database

Hi,
How to know that all objects like sequences and packages in the standby database are updated even if there is a change in the primary database.
Is the query ALTER DATABASE OPEN READ ONLY;
can query the standby database and do not affect the primary database and how to leave this read only mode
Tovohery

Check this out.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/manage_ps.htm#1017113

Similar Messages

  • Creating new tables in Logical Standby database

    Hi
    I have a requirement to create new tables in logical standby database. These tables will not be present on primary database. Is it possible to do this ?
    I have a new schema already created which has the privilege to CREATE new table.
    I have stopped the logical standby apply.
    When I am now trying to create a new table but it is failing with error : insufficient privileges.
    When I am trying to run below statement on new schema it is also failing with error of insufficient privileges.
    alter session disable dataguard;
    Please help.

    user8819121 wrote:
    Thanks Mahir,
    I was able to create the table after logging in as sysdba.
    But I need my user on that table to execute DML statements. My user has privileges to insert,delete and update any table.
    I tried the following statements to disable the guard but it is sill not working
    ALTER DATABASE GUARD STANDBY.
    Do I need to skip the tables created using dbms_logstdby package to not making it part of SQL Apply ? I guess not since the table is not in primary database.
    Amit
    You can skip only on primary, your created schema on Standby is not in primary.
    Then you must change Status of data guard to NONE. NONE is means is not any security on your data.
    In Guard status NONE can change all schema data.
    Please check link: http://docs.oracle.com/cd/E11882_01/server.112/e10700/manage_ls.htm#CHDGFGHG
    Following tests on user created before guard status is change from ALL to STANDBY.
    C:\Users\Administrator>sqlplus / as sysdba
    SQL> conn test/test
    Connected.
    SQL> select table_name from user_tables;
    TABLE_NAME
    T
    SQL> insert into t values(22);
    insert into t values(22)
    ERROR at line 1:
    ORA-16224: Database Guard is enabled
    SQL> conn / as sysdba
    Connected.
    SQL> select guard_Status from  v$database;
    GUARD_S
    ALL
    SQL> alter  database guard standby;
    Database altered.
    SQL> conn test/test
    Connected.
    SQL> insert into t values(1);
    insert into t values(1)
    ERROR at line 1:
    ORA-16224: Database Guard is enabled
    SQL> conn / as sysdba
    Connected.
    SQL> select guard_Status from  v$database;
    GUARD_S
    STANDBY
    SQL> alter  database guard none;
    Database altered.
    SQL> select guard_Status from  v$database;
    GUARD_S
    NONE
    SQL> conn test/test
    Connected.
    SQL> insert into t values(1);
    1 row created.
    SQL> commit;
    Commit complete.And Now I want share with you new tests :)
    Now user creating when after guard status change
    SQL> drop  user test cascade;
    User dropped.
    SQL> select guard_status from v$database;
    GUARD_S
    STANDBY
    SQL> create user test identified by test;
    User created.
    SQL> grant create session,  resource, create table to test;
    Grant succeeded.
    SQL> conn test/test
    Connected.
    SQL> create table t (n number);
    Table created.
    SQL> insert into t values(1);
    1 row created.
    SQL> commit;
    Commit complete.
    SQL>It means when guard status is ALL then all of user created guarding.
    When you changed status to STANDBY then Logical Standby guard only primary schema and created schema before change.
    NONE is not guard any schema. it means you can delete standby schema data too.
    Regards
    Mahir M. Quluzade
    Edited by: Mahir M. Quluzade on Apr 19, 2013 4:07 PM

  • Data Guard - Steps to install Physical standby database in an RHEL 5.6 x86

    HI Team,
    I need to install Physical standby database in a OS installed from factory with most basic packages. Please find the info in detail
    Standby Server :
    Database Version : 10g Release 2
    Operating System : Red Hat Enterprise Linux Server release 5.6 (Tikanga) , RHEL 5.6 x86_64
    swartis.dc$ free -m
    total used free shared buffers cached
    Mem: 34158 33847 311 0 558 28367
    -/+ buffers/cache: 4921 29237
    Swap: 10001 63 9937
    - Things i need to validate in the PROD server. Eg : Are the prod db version & standby db version should be the same, Do the OS need to be same ............ETC
    - Basic Linux rpm required for standby server & any other pre-requisites required at standby server
    - Verify connectivity speed btw servers to decide log file size
    - Please give me more detailed steps , where i need to start the steps in installation of Physical standby database.
    Thanks in advance.
    -- Rakesh
    Edited by: Rakesh on Jan 10, 2012 8:23 AM

    Hello again;
    Sorry for the Delay.
    To this question "Do i need to install 10.2.0.2.0 ORACLE_HOME & on top of it apply 10.2.0.3.0 patchset.?"
    Yes.
    All my Oracle 10 installs started with 10.2.0.1 and then I patched up from there. If I remember correctly 10.2.0.1 may bark on Red Hat 5.
    You can work around this by reviewing this file :
    /etc/redhat-releaseSave whatever is in there somewhere and replace it with :
    redhat-3After the install put back what was there and get rid of the "redhat-3".
    I extra RPM's I used were :
    rpm -ivh kernel-headers-2.6.18-164.el5.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh elfutils-libelf-devel*.x86_64.rpm glibc-devel-2* gcc-4*.x86_64.rpm gcc-c++-4*.x86_64.rpm libstdc++-devel-4*.x86_64.rpm glibc-headers*.x86_64.rpm libgomp*.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh sysstat*I searched my Red Hat Disks before hand and ran the RPM commands as shown. Adjust as needed.
    To verify that the required packages have been installed on your system, run the following command :
    pm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" binutils \
    compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc \
    glibc-common glibc-devel-2.5 libaio libaio-devel libgcc libstdc++ libstdc++-devel \
    make sysstatThis document is for Oracle 11, but the OS part should be the same.
    http://www.visi.com/~mseberg/installing_oracle_11g_r2_64.html
    Currently I have 3 servers running both Oracle 10 and 11 ( In different homes ) using this OS.
    I have used Oracle 11 document with Oracle 10 also : ( Better once you are setup and a great standby recovery document )
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Creation of Standby Database through Rman.

    Hi Everybody,
    Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    Os: Windows Xp
    I am trying to create a standby database with the help of Rman..
    but when i am trying to invoke the Rman Executable and connect to the primary and auxillary database ie:standby
    it's giving me the following error...........
    C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 09:28:08 2008
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: PRIMARY (DBID=1503515402)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04006: error from auxiliary database: ORA-12541: TNS:no listenerI have restarted my listener service but still getting the error...
    here is my Listener.ora entries...........
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1525))
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PRIMARY)
          (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    standby=
    (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1526))
    SID_LIST_standby =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = standby)
          (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
      )any help appreciated
    Regards,
    Prosenjit Mukherjee

    Hi Hemant,
    It worked...when I i issued the command as mentioned by you it started the Listener..
    lsnrctl start standby
    Now I am able to connect to both the Database using Rman..
    C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 10:55:08 2008
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: PRIMARY (DBID=1503515402)
    connected to auxiliary database: STANDBY (not mounted)
    RMAN>Thanks for the Input...
    Is there any way by which i can start both the Listener with "lsnrctl start"...........instead of manually starting individual listener's
    Regards,
    Prosenjit Mukherjee
    Edited by: Prosenjit on Oct 2, 2008 11:01 AM

  • Standby Database fails to read dictionary from redo log

    hi,
    I am attempting to create a Logical standby database on same machine as the primary database. I have executed the steps outlined in Oracle Documentation several times, but end up with the same error. Detailes of setup and error are provided below. Please help. Thanks.
    ==========
    OS: REdhat 8 (2.4.18-14)
    RDBMS: Oracle EE Server 9.2.0.3.0
    primary db init details:
    *.log_archive_dest_1='LOCATION=/usr3/oracle/admin/lbsp/archive/ MANDATORY'
    *.log_archive_dest_2='SERVICE=STDBY'
    standby db init details:
    log_archive_dest_1='LOCATION=/usr3/oracle/admin/stdby/archive/'
    standby_archive_dest='/usr3/oracle/admin/lbsp/archive_pdb/'
    Standby alert log file (tail)
    LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
    Sun Jul 13 11:37:20 2003
    Errors in file /usr3/oracle/admin/stdby/bdump/stdby_lsp0_13691.trc:
    ORA-01332: internal Logminer Dictionary error
    LSP process trace file:
    Instance name: stdby
    Redo thread mounted by this instance: 1
    Oracle process number: 18
    Unix process pid: 13691, image: oracle@prabhu (LSP0)
    *** 2003-07-13 11:37:19.972
    *** SESSION ID:(12.165) 2003-07-13 11:37:19.970
    <krvrd.c:krvrdfdm>: DDL or Dict mine error exit. 384<krvrd.c:krvrdids>: Failed to mine dictionary. flgs 180
    knahcapplymain: encountered error=1332
    *** 2003-07-13 11:37:20.217
    ksedmp: internal or fatal error
    . (memory dump)
    KNACDMP: Unassigned txns = { }
    KNACDMP: *******************************************************
    error 1332 detected in background process
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-01332: internal Logminer Dictionary error
    another trace file created by error is: stdby_p001_13695.trc
    Instance name: stdby
    Redo thread mounted by this instance: 1
    Oracle process number: 20
    Unix process pid: 13695, image: oracle@prabhu (P001)
    *** 2003-07-13 11:37:19.961
    *** SESSION ID:(22.8) 2003-07-13 11:37:19.908
    krvxmrs: Leaving by exception: 604
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01031: insufficient privileges
    ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
    ORA-06512: at line 1
    there are no errors anywhere during the creation, mounting or opening of standby database. After the initial log register, any log switch on primary is communicated to standby and visible in DBA_LOGSTDBY_LOG. Also, archived logs from primary are successfuly copied by system to directory pointed by standby db's standby_archive_dest parameter.
    I noticed, somehow everytime I issue "ALTER DATABASE START LOGICAL STANDBY APPLY" command the procedures and packages related to logmnr get invalid. I compile them and again after "APPLY" they become invalid.
    Invalid object list:
    OBJECT_TYPE OBJECT_NAME
    VIEW DBA_LOGSTDBY_PROGRESS
    PACKAGE BODY DBMS_INTERNAL_LOGSTDBY
    PACKAGE BODY DBMS_STREAMS_ADM_UTL
    VIEW LOGMNR_DICT
    PACKAGE BODY LOGMNR_DICT_CACHE
    PROCEDURE LOGMNR_GTLO3
    PROCEDURE LOGMNR_KRVRDA_TEST_APPLY
    Anybody point out what I am doing wrong. Thanks for the help

    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
    post from standby:-
    SQL> select name, state From v$asm_diskgroup;
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privilegesPost from primary & standby
    SQL> select * from v$pwfile_users;
    User Profile for 919131
    919131     
    Handle:     919131  
    Status Level:     Newbie
    Registered:     Mar 6, 2012
    Total Posts:     16
    Total Questions:     8 (8 unresolved)
    OTN failed 100% to help you, then why you posted another question?
    First close all your old answered threads and then better continue your updates in your thread.
    Edited by: CKPT on Jul 9, 2012 11:45 AM

  • ORA-01403: no data found on LOGICAL STANDBY database

    Hi ,
    Logical Standby issue :
    Oracle 10.2.0.2 enterprise edition .
    M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
    I m getting countinuously no data foud errror on logical standby database .
    I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
    exec dbms_logstdby.instantiate_table (.......................................
    but when i start apply process on logical standby it again give no data found for new table :
    Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
    As much as i known abt the error that is :
    table1
    id
    10
    20
    30
    Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
    update table1 set id=100 where id=50;
    above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
    Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
    watingggg guyssss/......

    Troubleshooting ORA-1403 errors with Flashback Transaction
    In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
    ORA-1403: No Data Found
    Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
    When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
    The initial error
    When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
    LOGSTDBY stmt: update "SCOTT"."MASTER"
    set
    "NAME" = 'john'
    where
    "PK" = 1 and
    "NAME" = 'andrew' and
    ROWID = 'AAAAAAAAEAAAAAPAAA'
    LOGSTDBY status: ORA-01403: no data found
    LOGSTDBY PID 1006, oracle@staco03 (P004)
    LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
    The Investigation
    The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
    SQL> select versions_xid
    , versions_startscn
    , versions_endscn
    , versions_operation
    , pk
    , name
    from scott.master
    versions between scn minvalue and maxvalue
    where pk = 1
    order by nvl(versions_startscn,0);
    VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
    03001900EE070000 3492279 3492290 I 1 andrew
    02000D00E4070000 3492290 D 1 andrew
    Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
    From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
    SQL> select operation
    , undo_sql
    from flashback_transaction_query
    where xid = hextoraw('02000D00E4070000');
    OPERATION UNDO_SQL
    DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
    ('1','andrew');
    BEGIN
    Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
    SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
    SQL> commit;
    The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
    SQL> alter database start logical standby apply;

  • Monitoring Physical standby database through OEM

    HI ,
    We are monitoring Physical standby database through OEM and we monitor from console using SYS user
    As per our company policy we change our sys password every month so after change it we need to change SYS password from console also
    so is any way we can change SYS password on console using command line utility? if yes then please give us the command
    Thanks

    we monitor from console using SYS userYou have to monitor it using a SYSDBA user not necessarily SYS. So you can create a user e.g. SYS_MONITOR which has different policy than SYS. Although it is best to change that password on regular bases too, maybe every 3 months.
    so is any way we can change SYS password on console using command line utility?I don't get your question. Are you asking if it is possible to change the monitoring username/password using some command line utility? If so, I haven't heard of such tool. But there could be a package like MGMT_TARGET which you can manipulate the credentials if you know how to use it.

  • Standby database upgrade process

    Hi
    I have a 11gR1 database with dataguard setup.I have successfully upgraded the primary database to 11gR2 using dbua.
    Although 11gR2 software is installed on standby server,I realized archivelogs were not shipped to standby server during the database upgrade.
    When I switch logfile in primary, I see below errors in standby alertlog:
    RFS: 'Attach' request version mismatchWhat is the best way to sort out standby database regarding database upgrade ?
    Do I need to manually add oratab entry, new pfile, etc in standby server ?
    or
    Do I have to rebuild DR ?

    Both primary and standby compatible parameter is 11.1.0.0.0
    However, rman is giving this error:
    rman target sys/sys@orcl auxiliary sys/sys@orcl_std
    Recovery Manager: Release 11.2.0.3.0 - Production on Sun Dec 11 08:53:34 2011
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ORCL (DBID=1297219823)
    Recovery Manager incompatible with AUXILIARY database: RMAN 8.0.4.0 to 11.1.0.7 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: AUXILIARY database is not compatible with this version of RMANLike I said, after the database upgrade pirmary became 11.2.0.3, standby is still 11.1
    I upgraded primary with dbua.
    Do I need to mount standby from new 11.2 home , copy pwd file, add oratab entry etc ?
    These were done automatically on primary via dbua

  • Standby Database(TNS no listener)

    The following error is encountering when I connect from standy database for recreating standby database
    Rman-00554 initilization internal recovery manager package failed
    Rman-04005 error from target database
    ORA-12541 TNS no listener
    Any help would be highly appreciated

    Oracle version number (to four decimal places)?
    Logical or physical standby?
    Connect using what connection string?
    Making a wild guess at what you are trying to do since you included almost no information here's what you may be trying to do:
    SQL> startup nomount;
    $ rman target sys/oracle1@proda auxiliary /
    RMAN> duplicate target database for standby nofilenamecheck;
    RMAN> exit;obviously using a real password and instance name.
    If not then you need to do a far more complete job of explaining what you are doing.

  • Creating a new schema in a Logical Standby Database

    Hi All,
    I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
    I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
    However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
    Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
    SYS@UATDR> connect / as sysdba
    Connected.
    SYS@UATDR>
    SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
    2 from v$database
    3 /
    NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
    UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
    SYS@UATDR>
    SYS@UATDR> create tablespace ts_new
    2 /
    Tablespace created.
    SYS@UATDR>
    SYS@UATDR> create user new
    2 identified by new
    3 default tablespace ts_new
    4 temporary tablespace temp
    5 quota unlimited on ts_new
    6 /
    User created.
    SYS@UATDR>
    SYS@UATDR> grant connect, resource to new
    2 /
    Grant succeeded.
    SYS@UATDR> grant unlimited tablespace, create table, create any table to new
    2 /
    Grant succeeded.
    SYS@UATDR>
    SYS@UATDR> -- show privs given to new
    SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
    2 /
    GRANTEE PRIVILEGE ADM
    NEW CREATE ANY TABLE NO
    NEW CREATE TABLE NO
    NEW UNLIMITED TABLESPACE NO
    SYS@UATDR>
    SYS@UATDR> -- create objects in schema
    SYS@UATDR> connect new/new
    Connected.
    NEW@UATDR>
    NEW@UATDR> -- prove ability to create tables
    NEW@UATDR> create table new
    2 (col1 number not null)
    3 tablespace ts_new
    4 /
    create table new
    ERROR at line 1:
    ORA-01031: insufficient privileges
    NEW@UATDR>
    NEW@UATDR>

    HI Daniel,
    I appreciate your quick response.
    My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
    SYS@UATDR> connect / as sysdba
    Connected.
    SYS@UATDR>
    SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
    2 from v$database
    3 /
    NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
    UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
    SYS@UATDR>
    SYS@UATDR> create tablespace ts_gav
    2 /
    Tablespace created.
    SYS@UATDR>
    SYS@UATDR> create user gav
    2 identified by gav
    3 default tablespace ts_gav
    4 temporary tablespace temp
    5 quota unlimited on ts_gav
    6 /
    User created.
    SYS@UATDR>
    SYS@UATDR> grant connect, resource to gav
    2 /
    Grant succeeded.
    SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
    2 /
    Grant succeeded.
    SYS@UATDR>
    SYS@UATDR> -- show privs given to gav
    SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
    2 /
    GRANTEE PRIVILEGE ADM
    GAV CREATE TABLE NO
    GAV CREATE ANY TABLE NO
    GAV UNLIMITED TABLESPACE NO
    SYS@UATDR>
    SYS@UATDR> -- create objects in schema
    SYS@UATDR> connect gav/gav
    Connected.
    GAV@UATDR>
    GAV@UATDR> -- prove ability to create tables
    GAV@UATDR> create table gav
    2 (col1 number not null)
    3 tablespace ts_gav
    4 /
    create table gav
    ERROR at line 1:
    ORA-01031: insufficient privileges
    GAV@UATDR>

  • Issue in configuring Standby Database from Active database in 11g by RMAN

    POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
    Hi All,
    I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
    Version of Database:11g(11.2.0.1.0)
    Operating System:Linux 5
    Error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Primary Database Entries:
    Tnsentry:
    SONYPRD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)(UR=A)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listner Entry:
    SID_LIST_SONYPRD =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtproc)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = SONYPRD)
    (GLOBAL_DBNAME = SONYPRD)
    Auxiliary Details:
    Tns Entry:
    SONYPRD =
    (DESCRIPTION =
    # (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listener Entry in auxiliary:
    SID_LIST_SONYPRDSTBY =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = SONYPRDSTBY)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = SONYPRDSTBY)
    TNSPING from Primary DB:
    [oracle@oracle11g ~]$ tnsping sonyprdstby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
    OK (0 msec)
    TNSPING from Auxuliary server
    [oracle@oracle11gstby ~]$ tnsping sonyprd
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
    OK (10 msec)
    Script Used for duplicate:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'sonyprd','sonyprdstby'
    set db_unique_name='sonyprdstby'
    set db_file_name_convert='/sonyprd/','/sonyprdstby/'
    set log_file_name_convert='/sonyprd/','/sonyprdstby/'
    set control_files='/u01/app/oracle/oradata/control01.ctl'
    set log_archive_max_processes='5'
    set fal_client='sonyprdstby'
    set fal_server='sonyprd'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
    set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
    Tried the script from both Primary and auxiliary but no luck
    [oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: SONYPRD (DBID=3131093559)
    connected to auxiliary database: SONYPRD (not mounted)
    Listener Status from primary:
    [oracle@oracle11g ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-DEC-2012 17:42:17
    Uptime 1 days 0 hr. 26 min. 41 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
    Services Summary...
    Service "sonyprd.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    Service "sonyprdXDB.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Listener Status from Standby when database bring to Nomount state:
    [oracle@oracle11gstby admin]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 21-DEC-2012 16:13:47
    Uptime 0 days 1 hr. 58 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
    Services Summary...
    Service "sonyprdstby" has 1 instance(s).
    Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
    The command completed successfully
    Please provide any work arounds to proceed further in creating the standby database.
    Thanks,
    Ram.
    Edited by: 895188 on Dec 21, 2012 5:50 PM
    Edited by: 895188 on Dec 21, 2012 6:09 PM
    Edited by: 895188 on Dec 21, 2012 6:22 PM

    Hello;
    Script has to be run from auxiliary.
    Great details, but what I don't see is how you connect in RMAN.
    Example
    Start RMAN
    $ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
    Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: RECOVER2 (DBID=3806912436)
    connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
    Generally for active duplication I start the future standby on a pfile NOMOUNT.
    Auxiliary Instance Initialization Parameters Needed :
    DB_NAME
    CONTROL_FILES
    DB_BLOCK_SIZE
    ( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
    Then start RMAN and finally run a single line duplication command.
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
    mseberg

  • Issue in creating the standby database from Active database using RMAN

    Hi All,
    I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
    Version of Database:11g(11.2.0.1.0)
    Operating System:Linux 5
    Error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Primary Database Entries:
    Tnsentry:
    SONYPRD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)(UR=A)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listner Entry:
    SID_LIST_SONYPRD =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtproc)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = SONYPRD)
    (GLOBAL_DBNAME = SONYPRD)
    Auxiliary Details:
    Tns Entry:
    SONYPRD =
    (DESCRIPTION =
    # (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listener Entry in auxiliary:
    SID_LIST_SONYPRDSTBY =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = SONYPRDSTBY)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = SONYPRDSTBY)
    TNSPING from Primary DB:
    [oracle@oracle11g ~]$ tnsping sonyprdstby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
    OK (0 msec)
    TNSPING from Auxuliary server
    [oracle@oracle11gstby ~]$ tnsping sonyprd
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
    OK (10 msec)
    Script Used for duplicate:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'sonyprd','sonyprdstby'
    set db_unique_name='sonyprdstby'
    set db_file_name_convert='/sonyprd/','/sonyprdstby/'
    set log_file_name_convert='/sonyprd/','/sonyprdstby/'
    set control_files='/u01/app/oracle/oradata/control01.ctl'
    set log_archive_max_processes='5'
    set fal_client='sonyprdstby'
    set fal_server='sonyprd'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
    set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
    Tried the script from both Primary and auxiliary but no luck
    [oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: SONYPRD (DBID=3131093559)
    connected to auxiliary database: SONYPRD (not mounted)
    Listener Status from primary:
    [oracle@oracle11g ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-DEC-2012 17:42:17
    Uptime 1 days 0 hr. 26 min. 41 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
    Services Summary...
    Service "sonyprd.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    Service "sonyprdXDB.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Listener Status from Standby when database bring to Nomount state:
    [oracle@oracle11gstby admin]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 21-DEC-2012 16:13:47
    Uptime 0 days 1 hr. 58 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
    Services Summary...
    Service "sonyprdstby" has 1 instance(s).
    Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
    The command completed successfully
    Please provide any work arounds to proceed further in creating the standby database.
    Thanks,
    Ram.

    Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN

  • Logical Standby Database in NOARCHIVE Mode

    Hi,
    I have configured a Logical Standby Database for Reporting purposes. A Physical Standby Database is running for MAA. i.e. in case of Role Transition (switch/Failover) the Physical Stdby Db will get the role of the Primary.
    The logical standby database is creating a lot of Archive Redologs files, nearly every minute. Redolog files are 50MB and there is no work done in db during the time. I'm NOT using Standby Redolog files.
    Is there a need for logical standby database to be in NOARCHIVELOG mode? The Primary is definatley in ARCHIVELOG mode.
    Thanks for any responses.
    regards
    Sahba

    hi,
    well there are two things to the above:-
    1. there was an archive file nearly every minute:
    this is due to a db recovery. for some reason, the db was in inconsistent state, after a sudden shutdownof the OS. I was on a test environment, on windows vista, unfortunately. unimportant ... a reboot solved it.
    2. Logical standby db in NOARCHIVE MODE when setup for the purpose of Reporting.
    As long as the MAA configured for the primary db, such as physical standby db, and a second, the logical standby db setup purely for the purpose of reporting, which then can run with NOARCHIVELOG mode, after converting the physical standby db to logical.
    logical standby db uses Streams architecture, so this method brings cost, time and performance advantages to the customer.
    regards
    Sahba

  • Logs are not getting applied in the standby database

    Hello,
    I have created a physical standby database and in it the logs are not getting applied..
    following is an extract of the standby alert log
    Wed Sep 05 07:53:59 2012
    Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
    Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
    Attempting refetch
    Media Recovery Waiting for thread 1 sequence 37638
    Fetching gap sequence in thread 1, gap sequence 37638-37643
    Wed Sep 05 07:53:59 2012
    RFS[46]: Assigned to RFS process 3081
    RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
    RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
    Wed Sep 05 07:55:34 2012
    RFS[42]: Possible network disconnect with primary database
    However, the archived files are getting copied to the standby server.
    I tried registering and recovering the logs but it also failed..
    Follows some of the information,
    Primary
    Oralce 11R2 EE
    SQL> select max(sequence#) from v$log where archived='YES';
    MAX(SEQUENCE#)
    37668
    SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
    DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
    LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
    Standby
    Oralce 11R2 EE
    SQL> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    37637
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select open_mode, database_role from v$database;
    OPEN_MODE DATABASE_ROLE
    READ ONLY WITH APPLY PHYSICAL STANDBY
    Please help me to troubleshoot this and get the standby in sync..
    Thanks a lot..

    the results are as follows..
    SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
    PROCESS STATUS GROUP# THREAD# SEQUENCE#
    ARCH CLOSING 1 1 37644
    ARCH CLOSING 1 1 37659
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    MRP0 WAIT_FOR_GAP N/A 1 37638
    RFS IDLE N/A 0 0
    RFS IDLE N/A 0 0
    RFS IDLE N/A 0 0
    RFS RECEIVING N/A 1 37638
    RFS RECEIVING N/A 1 37639
    RFS RECEIVING N/A 1 37640
    RFS RECEIVING N/A 1 37641
    RFS RECEIVING N/A 1 37642
    RFS RECEIVING N/A 1 37655
    RFS RECEIVING N/A 1 37673
    RFS RECEIVING N/A 1 37675
    42 rows selected.
    SQL>
    SQL> select name,value, time_computed from v$dataguard_stats;
    NAME VALUE TIME_COMPUTED
    transport lag +00 02:44:33 09/05/2012 09:25:58
    apply lag +00 03:14:30 09/05/2012 09:25:58
    apply finish time +00 00:01:09.974 09/05/2012 09:25:58
    estimated startup time 12 09/05/2012 09:25:58
    SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
    TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
    05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
    05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
    05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
    05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
    05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
    05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
    05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
    05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
    05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
    05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
    05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
    05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
    05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
    05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
    05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
    05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
    05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
    05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
    05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
    05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
    05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
    05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
    05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
    05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
    05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
    05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
    05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
    05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
    05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
    05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
    05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
    05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
    05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
    05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
    05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
    05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
    05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
    05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
    05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
    05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
    05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database

  • Error while trying to open physical standby database - (DATA GUARD)

    Hi Everyone,
    I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
    Primary Database spec: (2 Node Rac on ASM)
    Oracle Version : 10.2.0.3.0
    O/s : HP-UX B.11.23
    Standby Database spec: (Single Node)
    Oracle Version : 10.2.0.3.0
    O/s: HP-UX db01 B.11.23
    Error:
    alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database open
    2 ;
    alter database open
    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: '+DATA/dprod/datafile/system01.dbf'
    Parameters :
    log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
    FOR=(ONLINELOGFILES,PRIMARY_
    ROLE) DB_UNIQUE_NAME=PROD
    remote_archive_enable string true
    fal_client string DPROD
    fal_server string PROD1, PROD2
    Steps tried so far:
    Changed log_archive_dest_2 = DEFER on both the primary nodes
    Standby :
    startup nomount
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    alter database recover managed standby database cancel;
    alter database open/readonly (tried both)
    Same error.
    On Primary:
    SQL> select max(sequence#) from v$log_history;
    MAX(SEQUENCE#)
    55702
    on Standby:
    MAX(SEQUENCE#)
    33289
    Primary Database:
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    55700 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55702 13-JUN-11 13-JUN-11
    60824 rows selected.
    Standby Database:
    SEQUENCE# FIRST_TIME NEXT_TIME
    55698 13-JUN-11 13-JUN-11
    55699 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    15206 rows selected.
    Additional Information :
    There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
    Any help will be highly appreciated. Thanks in advance
    Sadiq

    Hi,
    Primary Database:
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    STATUS CHECKPOINT_COUNT
    ONLINE 57717
    ONLINE 57717
    57 rows selected.
    Standby Database;
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    STATUS CHECKPOINT_COUNT
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    STATUS CHECKPOINT_COUNT
    ONLINE 30723
    ONLINE 30723
    57 rows selected.
    Archieve log list :
    Primary database:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 49111
    Current log sequence 49111
    Standby Database:
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 0
    Current log sequence 49111
    I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

Maybe you are looking for