Standby database ALERTLOG displays WARNING in Readonly mode

Hi,
I have configured Standby database through RMAN and open it in read only mode after opening Alertlog file display below warning every 4/5 minutes, if some one knows plz let me know. Thanks
***Warning - Executing transaction without active Undo Tablespace
Tue Jul 12 07:44:38 2005
Restarting dead background process QMN0
QMN0 started with pid=9

Hi,
configuration of undo tablespace are.
NAME VALUE
undo_management AUTO
BDC> show parameter undo_tablespace
NAME VALUE
undo_tablespace UNDOTBS2
From DBA_TABLESPACE
STATUS TABLESPACE_NAME
ONLINE UNDOTBS1
ONLINE UNDOTBS2
why undo tablespace is not Active as ALERTLOG says, Waiting for reply, and PAUL how can I check METALINK as it requires registration, Thanks
KHAWAR

Similar Messages

  • Logical standby database keeps displaying ORA-16768

    I have a logical standby database setup on a remote host to accept cascaded logs from a physical standby. Everything was working fine until yesterday when I get the above error and log apply services stopped. When I go into Grid Control to Data Guard I see the error and it displays the failed SQL statement which is a create index statement. I have the option of clicking the SKIP button. When I click SKIP it appears to have processed it as the error goes away but then a few minutes later the error comes back, log apply stops and the failed SQL statement is the same create index statement. I guess the Skip doesn't mean Skip, it means Retry... My question is how do I get past this? Logs have been piling up.

    Hi,
    Ok I applied :
    SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    Database altered.
    SQL> alter database start logical standby apply immediate;
    Database altered.
    SQL>
    And now I received this :
    ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
    Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
    Action: Check the StatusReport monitorable property of the database specified.
    What does it mean to check the status report.....
    I found this about monitorable status report !!
    DGMGRL> show database 'M3RPT' 'StatusReport';
    STATUS REPORT
    INSTANCE_NAME SEVERITY ERROR_TEXT
    * WARNING ORA-16821: logical standby database dictionary not yet loaded
    DGMGRL>
    What can I do ?
    Thanks a lot
    oldschool
    Edited by: oldschool on Jun 4, 2009 2:37 AM

  • Test physical standby database in dataguard

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

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

  • Create StandBy Database

    Can anyone help me in creating StandBy Database.
    I am using oracle 10g.
    Thanks in advance

    I am trying to Create Standby Database.the log_mode is in NonARCHIVELOG
    Mode.. i want to make it as ARCHIVELOG ..
    So i tried wid
    sql>shutdown immediate;
    sql>startup mount;
    sql>alter database archivelog;
    sql>alter database open;
    am getting error as invalid sql statement

  • Starting Physically Standby Database in Mount Mode

    Hi All
    I have configured Data Guard using Oracle 10g 10.2.0.4.0 (64 bits) on Windows 2008 Server (64 bits) Release 2 Enterprise.
    Data guard configuration was OK as the message from "Enable Configuration DG1" was "SUCCESS" for both
    Primary and Standby Database. I have also set both Databases and TNS to start Automatically whenever Windows Starts.
    The Problem is as long as the Standby Server is running, there is No issue.
    But when we Restarts the Backup Server, Physically Standby Database is Started and TNS is also Started,
    but Archives  are not received until I physically do the following steps so that it can received the Archives.
    SQL> startup nomount;                                                                                                                
    SQL> alter database mount standby database;                                                                 
    SQL> alter database recover managed standby database disconnect from session;
    Is there a way to start Physically Standby Database in Mount mode when windows started.
    Regards
    Thunder2777

    Hi Mihael
    I have created 2 files. 1 Bat file 2nd sql file which contains all commands as written above.
    When I execute start.bat file
    1. set ORACLE_HOME=C:\oracle\product\10.2.0\db_1
    2. set ORACLE_SID=UMISBK
    3. sqlplus / [email protected]
    1 & 2 executed properly. At 3 it just display SQL help for login as shown below.
    SQL*Plus: Release 10.2.0.4.0 - Production
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Usage 1: sqlplus -H | -V
        -H             Displays the SQL*Plus version and the usage help.
        -V             Displays the SQL*Plus version.
    Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
      <option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
    It Did Not execute start.sql file to excute sql commands.
    Regards
    Thunder2777

  • 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

  • Error: 1013231 Unable to update database while in readonly mode for backup

    Hi all,
    Wen im deleting the members for dimendsion , its giving error (hyperion 11.1 aso)
    Error: 1013231 Unable to update database while in readonly mode for backup , how can i solve this problem ,plz can any one help on this
    Thanks

    Has somebody set the database ready for archiving, maybe some maxl has been run and the db has not been returned from read only mode.
    Try running the following Maxl (change app.db to match your app/db)
    alter database app.db end archive;
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Standby Database (Archive Log Mode)

    I'm going to be setting up a standby database.
    I understand that the primary database must be in archive log mode.
    Is there any reason for the standby database to be in archivelog mode?

    Since your primary Db is in archive log mode, so will be your standby, when it is made primary.But. you can use STANDBY REDO LOGS from 9i version, where these Standby Redo Logs then store the information received from the Primary Database.
    As per metalink:-
    >
    Standby Redo Logs are only supported for the Physical Standby Database in Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs are only used if you have the LGWR activated for archival to the Remote Standby Database.If you have Standby Redo Logs, the RFS process will write into the Standby RedoLog as mentioned above and when a log switch occurs, the Archiver Process of the Standby Database will archive this Standby Redo Log to an Archived Redo Log, while the MRP process applies the information to the Standby Database. In a Failover situation, you will also have access to the information already written in the Standby Redo Logs, so the information will not be lost.
    >
    Check metalink Doc ID: Note:219344.1
    Regards,
    Anand

  • Running a physical standby database in noarchivelog mode

    Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
    Standby Database: single instance 11.2.0.2
    OS: AIX 7.1
    Hello,
    I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
    Thanks

    Hello again;
    If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
    For this :
    b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
    And for this :
    resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
    --- Will post a detailed example here in a moment.
    Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
    all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
    I did another switchover and it was done. I used TAF and none of the users even noticed.
    Best Regards
    mseberg

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

  • Should the STANDBY database be in NOMOUNT Mode?

    Hi There,
    Just setup DataGuard and want to monitor the primary and standby databases via the grid. However, I can not configure the standby database because the standby database is in NOMOUNT mode. Was I suppose to mount it? If not, how do I configure the standby database with the enterprise manager in NOMOUNT.
    Thanks.
    J

    Jennifer;
    Yes the standby should be in MOUNT mode before apply starts. Or No, to NOMOUNT if you prefer.
    Oracle 11g Data Guard: Grid Control Management
    http://www.databasejournal.com/features/oracle/article.php/3826706/Oracle-11g-Data-Guard-Grid-Control-Management.htm
    Install DataGuard using Oracle Enterprise Manager 10g grid control
    http://dbatips.wordpress.com/2007/02/17/install-dataguard-using-oracle-enterprise-manager-10g-grid-control/
    Manage Your Existing Data Guards with Enterprise Manager Cloud Control
    http://www.gokhanatil.com/2012/04/manage-your-existing-data-guards-with.html
    oracle dataguard setup using enterprise manager grid control 11g
    http://oracleinstall.wordpress.com/2011/08/21/1250/
    Super Good
    http://gavinsoorma.com/2011/03/creating-a-11g-data-guard-physical-standby-database-using-enterprise-manager-grid-control-10-2-0-5-2/
    The oracle document Data Guard Broker 10g Release 1 (10.1) Part Number B10822-01 cover this in detail
    http://docs.oracle.com/cd/B14117_01/server.101/b10822/gui.htm
    OR for 11
    http://docs.oracle.com/cd/B28359_01/server.111/b28295/title.htm
    http://docs.oracle.com/cd/B28359_01/server.111/b28295/toc.htm
    See Starting Up and Shutting Down a Physical Standby Database in the Data Guard Concepts and Administration
    Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
    Best Regards
    mseberg
    Edited by: mseberg on Apr 27, 2012 3:22 PM

  • ORA-01578 about standby database in read only mode

    Hi,
    I have an ORA-05178 (data block corrupted) about a standby database which in read-only mode. About production database, there is no problem.
    After analyze, this is an index segment :
    SELECT segment_name , segment_type , owner , tablespace_name
    FROM sys.dba_extents
    WHERE file_id = 58
    AND 218173 BETWEEN block_id and block_id + blocks -1
    SEGMENT_NAME SEGMENT_TYPE OWNER TABLESPACE_NAME
    SICINHIS01 INDEX MOWIN IDX_DATA01
    There is no constraint.
    How can I repair this problem ?
    Nicolas

    Hi,
    I have an ORA-05178 (data block corrupted) about a standby database which in read-only mode. About production database, there is no problem.
    After analyze, this is an index segment :
    SELECT segment_name , segment_type , owner , tablespace_name
    FROM sys.dba_extents
    WHERE file_id = 58
    AND 218173 BETWEEN block_id and block_id + blocks -1
    SEGMENT_NAME SEGMENT_TYPE OWNER TABLESPACE_NAME
    SICINHIS01 INDEX MOWIN IDX_DATA01
    There is no constraint.
    How can I repair this problem ?
    Nicolas

  • Do I need to use standby database in begin backup mode to take the backup?

    Hi All,
    I have a 10g(10.2.0.4) primary database with standby on a solaris platform. I need to create another standby database for the same primary.
    I have stopped the recovery on existing standby database and started copying(os copy) the files from existing standby to 2nd standby server. However I haven't kept the existing standby database(mounted) in begin backup mode. Is it okay?
    Thanks,
    Arun

    Backup mode for a mounted database?
    orclz>
    orclz> startup mount
    ORACLE instance started.
    Total System Global Area  788529152 bytes
    Fixed Size                  3050600 bytes
    Variable Size            373293976 bytes
    Database Buffers          406847488 bytes
    Redo Buffers                5337088 bytes
    Database mounted.
    orclz>
    orclz> alter database begin backup;
    alter database begin backup
    ERROR at line 1:
    ORA-01109: database not open
    orclz>

  • Physical Standby Database (Protection Mode)?!!

    Hi,
    I have configured a physical standby database to use Real-time Apply, but i noticed that the protection mode of the database has been changed from "Maximum Performance" to ''Maximum Availability"..
    log_archive_dest_3='service=phystby OPTIONAL LGWR SYNC AFFIRM reopen=120 valid_for=(online_logfiles,primary_role) db_unique_name=phystby'
    Any body to explaine??
    Regards,

    LGWR SYNC AFFIRM
    These are the options are used in maximum protection  mode ,in which oracle will write the information in both the server(primary and standby) and this write occurs at same time.
    oracle write the information in online redo logfile of both the server simultaneously.
    and this option ensure no data loss will occurs if primary will fail.
    SYNC related with Network transmission mode.
    AFFIRM related with disk write option.
    LGWR describe Redo archival process.
    Thanks
    Kuljeet                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Standby database mode...

    how can i find whether standby database is in recovery mode or not?
    Regards,
    BK.

    query v$database
    SQL> desc v$database
    Name                            Null?    Type
    DBID                                  NUMBER
    NAME                                  VARCHAR2(9)
    CREATED                             DATE
    RESETLOGS_CHANGE#                        NUMBER
    RESETLOGS_TIME                         DATE
    PRIOR_RESETLOGS_CHANGE#                   NUMBER
    PRIOR_RESETLOGS_TIME                        DATE
    LOG_MODE                             VARCHAR2(12)
    CHECKPOINT_CHANGE#                        NUMBER
    ARCHIVE_CHANGE#                        NUMBER
    CONTROLFILE_TYPE                        VARCHAR2(7)
    CONTROLFILE_CREATED                        DATE
    CONTROLFILE_SEQUENCE#                        NUMBER
    CONTROLFILE_CHANGE#                        NUMBER
    CONTROLFILE_TIME                        DATE
    OPEN_RESETLOGS                         VARCHAR2(11)
    VERSION_TIME                             DATE
    OPEN_MODE                             VARCHAR2(20)
    PROTECTION_MODE                        VARCHAR2(20)
    PROTECTION_LEVEL                        VARCHAR2(20)
    REMOTE_ARCHIVE                         VARCHAR2(8)
    ACTIVATION#                             NUMBER
    SWITCHOVER#                             NUMBER
    DATABASE_ROLE                             VARCHAR2(16)
    ARCHIVELOG_CHANGE#                        NUMBER
    ARCHIVELOG_COMPRESSION                    VARCHAR2(8)
    SWITCHOVER_STATUS                        VARCHAR2(20)
    DATAGUARD_BROKER                        VARCHAR2(8)
    GUARD_STATUS                             VARCHAR2(7)
    SUPPLEMENTAL_LOG_DATA_MIN                   VARCHAR2(8)
    SUPPLEMENTAL_LOG_DATA_PK                   VARCHAR2(3)
    SUPPLEMENTAL_LOG_DATA_UI                   VARCHAR2(3)
    FORCE_LOGGING                             VARCHAR2(3)
    PLATFORM_ID                             NUMBER
    PLATFORM_NAME                             VARCHAR2(101)
    RECOVERY_TARGET_INCARNATION#                   NUMBER
    LAST_OPEN_INCARNATION#                    NUMBER
    CURRENT_SCN                             NUMBER
    FLASHBACK_ON                             VARCHAR2(18)
    SUPPLEMENTAL_LOG_DATA_FK                   VARCHAR2(3)
    SUPPLEMENTAL_LOG_DATA_ALL                   VARCHAR2(3)
    DB_UNIQUE_NAME                         VARCHAR2(30)
    STANDBY_BECAME_PRIMARY_SCN                   NUMBER
    FS_FAILOVER_STATUS                        VARCHAR2(22)
    FS_FAILOVER_CURRENT_TARGET                   VARCHAR2(30)
    FS_FAILOVER_THRESHOLD                        NUMBER
    FS_FAILOVER_OBSERVER_PRESENT                   VARCHAR2(7)
    FS_FAILOVER_OBSERVER_HOST                   VARCHAR2(512)
    CONTROLFILE_CONVERTED                        VARCHAR2(3)
    PRIMARY_DB_UNIQUE_NAME                    VARCHAR2(30)
    SUPPLEMENTAL_LOG_DATA_PL                   VARCHAR2(3)
    MIN_REQUIRED_CAPTURE_CHANGE#                   NUMBER

Maybe you are looking for