Problem whit Logical standby unshyncronized

Hi, i have a logical standby apply from stb redos, and his night, it fails, and the database is not applying redo.
Also there is a process from redo applying whit 99.35 of CPU usage. this is not normal.
Do you have any idea??
thanks for all!

look this shots
SQL> column APPLIED_SCN format 999999999999999999
SQL> column NEWEST_SCN format 999999999999999999
SQL> column READ_SCN format 999999999999999999
SQL> SELECT L.SEQUENCE#, to_char(L.FIRST_TIME,'dd/mm/yyyy hh24:mi:ss'),
2 (CASE WHEN L.NEXT_CHANGE# < P.READ_SCN THEN 'YES'
3 WHEN L.FIRST_CHANGE# < P.APPLIED_SCN THEN 'CURRENT'
4 ELSE 'NO' END) APPLIED
5 FROM DBA_LOGSTDBY_LOG L, DBA_LOGSTDBY_PROGRESS P
6 where l.first_time >= sysdate - 3
7 ORDER BY SEQUENCE#;
SEQUENCE# TO_CHAR(L.FIRST_TIM APPLIED
7816 03/07/2008 23:34:47 CURRENT
7817 04/07/2008 02:46:12 CURRENT
7818 04/07/2008 02:46:48 NO
7819 04/07/2008 08:00:00 NO
7820 04/07/2008 08:49:34 NO
7821 04/07/2008 08:50:17 NO
7822 04/07/2008 09:33:18 NO
7823 04/07/2008 09:59:07 NO
7824 04/07/2008 10:18:36 NO
7825 04/07/2008 10:37:57 NO
10 rows selected.
SQL> !
STATE TIME %WCPU %CPU COMMAND
run 46:29 99.45 99.28 ora_p004_EMP

Similar Messages

  • Problem building logical standby database

    Hi all,
    i am trying to build a logical standby database on platform Sun OS 10/Oracle 10gR2. I am following the Oracle document http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#BEIGHEIA
    I have created a physical standby database and converting it to a logical standby database. I ensured that my physical Standby is in Sync with primary.
    Procedure DBMS_LOGSTDBY.BUILD executes successfully on primary.
    The problem is that the command *'alter database recover to logical standby test;'* DOESN'T END. No error in archive log. I have identified the archived redo log that contains the LogMiner dictionary and the starting SCN and applied that archive log on standby. Still the the above command doesn't end.
    Any Help is appreciated.

    SQL> alter database recover to logical standby m2test;
    This command doesn't return an sql> prompt. Alert log says it is waiting for log sequence 25. The command is running is for more than 5 hours, but still not competed.
    Alertlog:
    Thu Feb 5 22:14:25 2009
    alter database recover to logical standby m2test
    Thu Feb 5 22:14:25 2009
    Media Recovery Start: Managed Standby Recovery (mtest)
    Thu Feb 5 22:14:25 2009
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 2 processes
    Media Recovery Waiting for thread 1 sequence 25
    Document says :-
    If a dictionary build is not successfully performed on the primary database, this command will never complete.
    But the dictionary build on primary is successful.
    SQL> execute dbms_logstdby.build;
    PL/SQL procedure successfully completed.
    I used the following queries and to find which archive log contains dictionary build and made sure that the log archive sequence 22 is applied on standby.
    SQL> SELECT NAME FROM V$ARCHIVED_LOG
    WHERE (SEQUENCE#=(SELECT MAX(SEQUENCE#)
    FROM V$ARCHIVED_LOG
    WHERE DICTIONARY_BEGIN = 'YES' AND STANDBY_DEST='NO')); 2 3 4
    NAME
    /oradata/mtest/archive/mtest_1_22_677975686.arc
    SQL> SELECT MAX(FIRST_CHANGE#) FROM V$ARCHIVED_LOG
    WHERE DICTIONARY_BEGIN='YES'; 2
    MAX(FIRST_CHANGE#)
    177407
    SQL>
    Edited by: user592715 on Feb 6, 2009 3:22 PM

  • Problem whit physical standby

    Hi!
    2 days ago the disk cabinet of the standbys machine failed, the people of HP/UX resolved the fail in the same day, and the stb worked correctly since then.
    Now, the standby creates a new archivelog whenever it sincronizes, and this is not normal. The stb works correctly but the disadvantage of the archive log is worrying.
    How can i solve it??
    thanks of all and sorry my english :-D

    What step and how did you open the Standby database after the disk was resolved? What start mode is it and is it applying logs at the moment? Did you at some point switch it to Primary and started it?
    I expect that you will have achivelog Gaps between the down time and startup of the Standby. Has this Gaps been resolved ?
    If it comes to the worst and the Gaps cannot be filled, you can always recreate your standby from Physical to be in sync again

  • Logical standby | archive log deleted | how to remove gap ???

    hi gurus...
    i have problem on logical standby
    by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
    ON STANDBY
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
    228 674847 674872 YES
    229 674872 674973 CURRENT
    230 674973 674997 NO
    231 674997 675023 NO
    232 675023 675048 NO
    233 675048 675109 NO
    234 675109 675135 NO
    235 675135 675160 NO
    236 675160 675183 NO
    237 675183 675208 NO
    238 675208 675232 NO
    239 675232 675257 NO
    240 675257 675282 NO
    241 675282 675382 NO
    242 675382 675383 NO
    243 675383 675650 NO
    244 675650 675652 NO
    245 675652 675670 NO
    246 675670 675688 NO
    247 675688 675791 NO
    248 675791 678524 NO
    archive log are shipping to standby location also and getting registered
    ALERT LOG OF STANDBY
    Fri May 7 12:25:36 2010
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
    Fri May 7 12:25:37 2010
    RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
    but i dont have standby log after 229 sequence ...
    ON PRIMARY
    SYS@TEST AS SYSDBA> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
    Next log sequence to archive 249
    Current log sequence 249
    what to do next to apply sequences and bring both in sync.
    please help me ,,,,
    Edited by: user12281508 on May 7, 2010 9:45 AM

    thanks for response.
    no its pure logical standby
    i have tried to ftp the archive logs of primary to standby and applied manually
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    any other way ????

  • SQL apply is very slow on Logical Standby..!!

    Hello all,
    We are having Data Guard setup in our environment where we are having Primary, Physical Standby as well as logical standby databases..
    DB Version : 10.2.0.1 in all databases (Pri, Phy and Logical)
    OS : RHEL4
    Only Oracle is running on this Box..
    Since last month we are facing problems in Logical Standby database where it seems SQL apply has become very slow..
    Archive log files are successfully transferring from Primary but since SQL apply has become slow logical standby is lagging behind primary by two days..
    How do i speed up this SQL apply..?? Any ideas and suggestions are most welcome..
    I checked TOP command to find out which oracle processes are consuming maximum CPU and i have found ora_p000_oracle, ora_p001_oracle, ora_p002_oracle, ora_p003_oracle, ora_p004_oracle, ora_p005_oracle, etc processes are consuming highest CPU and Load Average has always been above 1..
    Any help would be greatly appreciated..
    Thanks - HP

    Hello;
    These Oracle notes might help :
    Slow Performance In Logical Standby Database Due To Lots Of Activity On Sys.Aud$ [ID 862173.1]
    Oracle10g Data Guard SQL Apply Troubleshooting [ID 312434.1]
    Developer and DBA Tips to Optimize SQL Apply [ID 603361.1]
    Best Regards
    mseberg

  • Logical Standby - 9iR2

    Hi, i have a litle problem with Logical Standby database a few second the start apply the redo the view V$LOGSTDBY_STATS is empty.
    SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    Database altered.
    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY;
    Database altered.
    SQL> SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME = 'coordinator state';
    NAME VALUE
    coordinator state APPLYING
    SQL> SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME = 'coordinator state';
    no rows selected

    Is the coordinator state process up and running for your Data Guard 9iR2 logical standby environment?
    Here is how to check:
    COLUMN LID FORMAT 9999
    COLUMN SERIAL# FORMAT 9999
    COLUMN SID FORMAT 9999
    SELECT SID, SERIAL#, LOGSTDBY_ID AS LID, SPID, TYPE, HIGH_SCN FROM V$LOGSTDBY_PROCESS;
    You should see processes similar to the following if things are setup correctly:
    SID SERIAL# LID SPID TYPE HIGH_SCN
    48 6 -1 11074 COORDINATOR 7178242899
    56 56 0 10858 READER 7178243497
    46 1 1 10860 BUILDER 7178242901
    45 1 2 10862 PREPARER 7178243295
    37 1 3 10864 ANALYZER 7178241034
    36 1 4 10866 APPLIER 7178239467
    35 3 5 10868 APPLIER 7178239463
    34 7 6 10870 APPLIER 7178239461
    33 1 7 10872 APPLIER 7178239472
    9 rows selected.
    I would review my setup and configuration steps for your Data Guard 9i Logical Standby environment.
    For more tips on monitoring see here:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ls.htm#CHDEFEFC
    And do review your setup and configuration. The steps are covered in the Oracle 9i Data Guard Concepts Guide. See here:
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/toc.htm
    In particular, please review your setup per the guidelines in Chapter 4 of the guide.
    Regards,
    Ben Prusinski
    http://oracle-magician.blogspot.com/

  • Logical Standby Problem

    My environment is Primary database is 11.1.0.7 64bit on Windows 2003 Enterprise 64bit. Logical is on the same platform and oracle version but a different server. I created a physical standby first and it applied the logs quickly without any issues. I received no errors when I changed it over to a Logical standby database. The problem that is happening is as soon as I issue the command "alter database start logical standby apply;" the CPU usage goes to 100% and the SQL apply takes a long time to apply a log. When I was doing this on 10G I never ran into this, as soon as the log was received, it was applied within a couple of minutes. I don't think it could be a memory issue since there is plenty on the Logical standby server. I just can't figure out why the SQL apply is so slow and the CPU usage skyrockets. I went through all of the steps in the guide "Managing a Logical Standby Database" from Oracle and I don't see anything wrong. The only difference between the two databases is that on the Primary I have Large Page support enabled, I don't on the Logical. Any help would be greatly appreciated, I need to use this Logical to report off of.

    Thanks for the responses. I have found what is causing the problem. I kept noticing that the statements it was slowing down on were the ones where data was being written to the SYS.AUD$ table in the System tablespace on the Logical Standby database. A quick count of the records showed that I had almost 6 million records in that table. After I decided to truncate SYS.AUD$ on the Logical, the archive logs started to apply normally. I wonder why the Logical has a problem with this table and the Primary doesn't. I didn't even know auditing was turned on on the Primary database, it must be enabled by default. Now I know why my System table space has grown from 1gb to 2gb since November.
    Now that I fixed it for now, I am unsure what to do to keep this from happening. Can I turn off Auditing on the Logical and keep it on for the Primary? Would this stop data from being written to the SYS.AUD$ table on the Logical? It doesn't appear that there is any kind of cleanup on this table that is offered by Oracle, I guess I can just clean out this table occasionally but that is just another thing to add to the list of maintenance tasks. I notice that you can also write this audit data to a file on the OS. Has anyone here done that?

  • Logical Standby Creation Problems "Create STatus Unknown"

    We are using Grid Control 10.2.0.3 on Oracle 10.2..0.3 databases, Windows 2003 sp2 machines.
    We have a primary and fsfo physical standby working properly. We went to create a logical standby on a separate server and had problems. it turned out that the listener on the server was not discovered on the target. we fixed that problem and finished the creation of the logical standby and it seems to be functioning properly now.
    However, the status on the data guard page for the logical standby shows Create Status Unknown and we are unable to proceed on to create an additional standby database for other purposes. We have tried removing the logical standby target and re-discovering it but status still shows Create Status Unknown.
    Is there any way to clear this status without having to drop the logical standby and completely recreate it.

    The status on the agent shows it uploading successfully.
    We resolved the issue by removing the logical standby from the configuration and selecting to retain the log apply. We then re-added the standby selecting to manage an existing standby database and the status went to normal.

  • Problem when switching over to a Logical Standby - RESOLVED

    I used GRID to create a logical standby. The primary and standby servers have the same OS's and are both 64-bit. I am using Oracle 10gR3 on both, and the same patches have been applied to both servers. Prior to doing the switchover, I queried switchover_status on the primary database and received a state of SESSIONS ACTIVE. I then issued the command ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY on the primary, and ALTER DATABASE PREPARE TO SWITCHOVER TO PRIMARY on the logical. The problem is that they are now both stuck in the PREPARING TO SWITCHOVER state and I cannot to anything to budge them from that state. As far as GRID is concerned, they are both in a NORMAL state, but the SQL queries prove differently. The APPLIED_SCN and NEWEST_SCN on the current standby do not match.
    Any ideas?
    Cheers
    Message was edited by:
    user458496

    Hi,
    APPLIED_SCN means that the newest SCN at which all changes have been applied. The values in the APPLIED_SCN and NEWEST_SCN columns will match if all available redo log data has been processed.
    NEWEST_SCN means that the most recent SCN available on the standby system. If no more logs are being shipped, then changes could be applied to this SCN. The values in the APPLIED_SCN and NEWEST_SCN columns will match if all available redo log data has been processed.
    http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14237/statviews_3250.htm
    Hope this helps.
    Adith

  • RMAN script problem to create logical standby database !

    Dear Friends ,
    I am using Oracle10g database . I want to create a logical standby database . I create two database :
    Primary : orcl
    standby : orclsby1
    Every steps I followed successfully , but when I am going to create "standby database" from "primary database" using rman then I found the following error :
    The script is below which I have to run in Primary (orcl) database :
    Script :
    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 'orcl','orclsby1'
    set db_unique_name='orclsby1'
    set db_file_name_convert='/orcl/','/orclsby1/'
    set log_file_name_convert='/orcl/','/orclsby1/'
    set control_files='/u01/app/oracle/oradata/orclsby1.ctl'
    set log_archive_max_processes='5'
    set fal_client='orclsby1'
    set fal_server='orcl'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(orcl,orclsby1)'
    set log_archive_dest_1='service=orcl ASYNC
    valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=orcl'
    Problem which I got :
    [oracle@localhost DG]$ rman target sys/sys123@orcl auxiliary sys/sys123@orclsby1
    Recovery Manager: Release 10.2.0.1.0 - Production on Mon Oct 19 15:58:17 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: ORCL (DBID=1227832857)
    connected to auxiliary database: ORCLSBY1 (not mounted)
    RMAN> @cr_phys_sby1.txt
    RMAN> run {
    2> allocate channel prmy1 type disk;
    3> allocate channel prmy2 type disk;
    4> allocate channel prmy3 type disk;
    5> allocate channel prmy4 type disk;
    6> allocate auxiliary channel stby type disk;
    7> duplicate target database for standby from
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "from": expecting one of: "dorecover, db_file_name_convert, nofilenamecheck, ;"
    RMAN-01007: at line 7 column 39 file: cr_phys_sby1.txt
    I try to edit the above script using 'nofilenamecheck' 'dorecover' etc. , but cannot resolve the problem . Would u plz help me .... where the problem is .
    Both databases are running on Oracle10g platform .
    Waiting for ur kind reply .. ...

    You need to:
    - create a SPFILE manually for standby database
    - use the RMAN command: DUPLICATE TARGET DATABASE FOR STANDBY
    - remove all SPFILE statements from RMAN script.

  • Logical standby problem on primary DB updates

    Hi all!
    I am quite new to standby databases, but I managed to sucessfully setup logical standby (11g on linux).
    However, I got some problem - when I try to insert some data into Primary DB using simple JDBC statements, I sometimes get exception:
    java.sql.SQLException: ORA-16224: Database Guard is enabled
    And this happens not all the time - sometimes I can insert and commit, but sometimes I get exception.
    This never happens when I am trying to insert data directly from sqlplus or TOAD.
    looks to me like java application sometimes is connecting to standby database.
    any suggestions?
    Thanks

    Check for example, whether both DBs present the same service and whether you have an oracle net configuration like
    myservice =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = host_A)(PORT = 1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST = host_B)(PORT = 1521))
          (LOAD_BALANCE = yes)
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = myservice)
      )You should make sure that the productive service is only presented by the primary database. See this explanation:
    http://prutser.files.wordpress.com/2008/12/client_connectivity.pdf
    Kind regards
    Uwe
    http://uhesse.wordpress.com

  • Logical standby database problem

    i have setup logical standby database on my pc . Everything was working fine . Logs were applied.
    But i tried testing few things on standby and issued few commands on that.
    After that the logs were not applied. i tried to restart that also dint work.
    what should i do so that things r back to normal or i need to create the standby again .
    Thanks

    The output is as follows .
    SQL> SELECT APPLIED_SCN, NEWEST_SCN, READ_SCN, NEWEST_SCN-APPLIED_SCN FROM DBA_LOGSTDBY_PROGRESS;
    APPLIED_SCN NEWEST_SCN READ_SCN NEWEST_SCN-APPLIED_SCN
    179493 194423 179497 14930
    SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
    no rows selected
    SQL> select operation, options, object_name, cost
    2 from v$sql_plan, v$session, v$logstdby
    3 where v$sql_plan.hash_value = v$session.sql_hash_value
    4 and v$session.serial# = v$logstdby.serial#
    5 and v$logstdby.status_code=16113;
    no rows selected

  • Logical STANDBY creating problem in 9.2

    Hi,
    i've a Physical standby db which is runnig quite well. i just tried to convert it to LOGICAL standby db. but it was asking for recovery. actually i had provided all the logs needed .but still was giving error.
    as i had synchronised physical standby i just changed its control file to normal control file from primary db( alter database backup control file to 'c:\lglstdby.ctl' ) (just created).
    i just paste the steps i did.
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Apr 12 08:01:09 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    SQL> conn sys@standby as sysdba
    Enter password: ******
    Connected.
    SQL> shut immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount pfile=E:\oracle\oradata\pfile\init.ora
    ORACLE instance started.
    Total System Global Area  312024024 bytes
    Fixed Size                   453592 bytes
    Variable Size             159383552 bytes
    Database Buffers          150994944 bytes
    Redo Buffers                1191936 bytes
    Database mounted.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-12571: TNS:packet writer failure
    SQL> /
    alter database open resetlogs
    ERROR at line 1:
    ORA-03114: not connected to ORACLE
    SQL> conn sys@standby as sysdba
    Enter password: ******
    Connected.
    SQL> /
    alter database open resetlogs
    ERROR at line 1:
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF'
    SQL> recover database using backupcontrol file;
    ORA-01906: BACKUP keyword expected
    SQL>  recover database using backup controlfile;
    ORA-00279: change 567900150 generated at 04/12/2008 07:57:01 needed for thread
    1
    ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43090.DBF
    ORA-00280: change 567900150 for thread 1 is in sequence #43090
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel;
    ORA-00308: cannot open archived log 'cancel;'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log 'E:\ORACLE\ORA92\RDBMS\1_43090.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-00308: cannot open archived log 'E:\ORACLE\ORA92\RDBMS\1_43090.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    SQL> recover database using backup controlfile;
    ORA-00279: change 567900150 generated at 04/12/2008 07:57:01 needed for thread
    1
    ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43090.DBF
    ORA-00280: change 567900150 for thread 1 is in sequence #43090
    --here i gave what it needed,but it asks for more...
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    E:\oracle\oradata\Archive\1_43090.DBF
    ORA-00279: change 567900630 generated at 04/12/2008 08:07:30 needed for thread
    1
    ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43091.DBF
    ORA-00280: change 567900630 for thread 1 is in sequence #43091
    ORA-00278: log file 'E:\oracle\oradata\Archive\1_43090.DBF' no longer needed
    for this recovery
    ---- it asks for next log as it hasn't generated yet.
    even if cancel recovery it says  file 1 needs media recovery ('E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF' )
    SQL> recover database using backup controlfile;
    ORA-00279: change 567900630 generated at 04/12/2008 08:07:30 needed for thread
    1
    ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43091.DBF
    ORA-00280: change 567900630 for thread 1 is in sequence #43091
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF'Why this is happening dont know ?
    any ideas?
    Thanks & regards!
    Oracle 9.2
    Win 2K Server

    Hi all,
    i managed to open STANDBY DB,but in a different way...
    i had to recreate controlfile .
    SQL> startup nomount pfile=e:\oracle\oradata\pfile\init.ora
    ORACLE instance started.
    Total System Global Area  312024024 bytes
    Fixed Size                   453592 bytes
    Variable Size             159383552 bytes
    Database Buffers          150994944 bytes
    Redo Buffers                1191936 bytes
    SQL> ed
    Wrote file afiedt.buf
      1  CREATE CONTROLFILE REUSE DATABASE "IRCS" RESETLOGS  ARCHIVELOG
      2  --  SET STANDBY TO MAXIMIZE PERFORMANCE
      3      MAXLOGFILES 6
      4      MAXLOGMEMBERS 3
      5      MAXDATAFILES 100
      6      MAXINSTANCES 1
      7      MAXLOGHISTORY 1134
      8  LOGFILE
      9    GROUP 1 (
    10      'E:\ORACLE\ORADATA\REDO\REDO011.LOG',
    11      'D:\ORACLE\ORADATA\REDO\REDO012.LOG'
    12    ) SIZE 4M,
    13    GROUP 2 (
    14      'E:\ORACLE\ORADATA\REDO\REDO021.LOG',
    15      'D:\ORACLE\ORADATA\REDO\REDO022.LOG'
    16    ) SIZE 4M,
    17    GROUP 3 (
    18      'E:\ORACLE\ORADATA\REDO\REDO031.LOG',
    19      'D:\ORACLE\ORADATA\REDO\REDO032.LOG'
    20    ) SIZE 4M,
    21    GROUP 4 (
    22      'E:\ORACLE\ORADATA\REDO\REDO041.LOG',
    23      'D:\ORACLE\ORADATA\REDO\REDO042.LOG'
    24    ) SIZE 4M,
    25    GROUP 5 (
    26      'E:\ORACLE\ORADATA\REDO\REDO51.LOG',
    27      'D:\ORACLE\ORADATA\REDO\REDO52.LOG'
    28    ) SIZE 4M,
    29    GROUP 6 (
    30      'E:\ORACLE\ORADATA\REDO\REDO61.LOG',
    31      'D:\ORACLE\ORADATA\REDO\REDO62.LOG'
    32    ) SIZE 4M
    33  -- STANDBY LOGFILE
    34  DATAFILE
    35    'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF',
    36    'E:\ORACLE\ORADATA\DATA\UNDOTBS01.DBF',
    37    'E:\ORACLE\ORADATA\DATA\DRSYS.DBF',
    38    'E:\ORACLE\ORADATA\DATA\FIN_DATA.DBF',
    39    'D:\ORACLE\ORADATA\DATA\FIN_IDX.DBF',
    40    'E:\ORACLE\ORADATA\DATA\INDX01.DBF',
    41    'D:\ORACLE\ORADATA\DATA\INV_DATA.DBF',
    42    'E:\ORACLE\ORADATA\DATA\INV_IDX.DBF',
    43    'E:\ORACLE\ORADATA\DATA2\OTHER_DATA.DBF',
    44    'D:\ORACLE\ORADATA\DATA\OTHER_IDX.DBF',
    45    'E:\ORACLE\ORADATA\DATA\PAY_DATA.DBF',
    46    'D:\ORACLE\ORADATA\DATA\PAY_IDX.DBF',
    47    'D:\ORACLE\ORADATA\DATA\SALE_DATA1.DBF',
    48    'D:\ORACLE\ORADATA\DATA\SALE_DATA2.DBF',
    49    'E:\ORACLE\ORADATA\DATA\SALE_IDX.DBF',
    50    'E:\ORACLE\ORADATA\DATA\USER_DATA.DBF',
    51    'E:\ORACLE\ORADATA\DATA\XDB01.DBF'
    52* CHARACTER SET WE8MSWIN1252
    SQL> /
    Control file created.
    SQL> alter database open resetlogs;
    Database altered.actually my db was very much consistent. it was asking for not generated logs.. i tried to make incomplete recovery but was erroring with system file not consistent. so i did recreate controlfile but my purpose to create logical was not solved here as when i opened DB with newly created contrlfile database was errorring like
    SCN not matching with primary database (i forgot to copy the exact error words)
    in alert log it was like
    RFS: Destination database mount ID mismatch [0x821cc13b:0x821e318f]
    can't it then synchronise with primary as physical does with fetching previous logs?
    so stopped that to further process..then again tried open my normal physical standby db with physical standby controlfile...but with physical it gave me a error of wrong pasword file and not able mount standby database.
    ERROR at line 1:
    ORA-01991: invalid password file 'E:\oracle\ora92\DATABASE\PWDircs.ORA'
    can't understandb !!....is this die to i tried to mount a open DB? but when creating a physical standby db we do take consistent back(optinal). so that time it doesn't give such type of error of pwd files....
    can't understand this behavoir?
    Any ideas?
    Regards!

  • Problem while mining archivelog in Logical Standby Database

    I have configure Data Guard with one Primary database, one physical standby and one logical standby database; redo are applied correcly on the physical standby database but on the logical standby database when logminer begin mining logfile it encounter this errors :
    ORA-00600 internal error code, arguments : [kpotcgah-7],[64],[X4],[],[],[],[],[]
    ORA-12801 error signaled in parallel query server P003
    ORA-07445
    ORA-12805 parallel query server died unexpectedly

    Unfortunately ORA-00600 errors are beyond the scope ot this forum, as they require tools and source code available only at Oracle Support. The only directions you most probably will get here is to issue a Service Request. Oracle support will, among other things, ask you if you are at the latest available patch for your platform.
    Good luck.

  • Dataguard Problem(logical standby database)

    Hi,
    I have successfully created logical standby database, and everything is working fine, all of the SQL is applying and archiving is also shipping.
    Until I create a new tablespace for e.g. pay in the primary database, and suddenly SQL applying is stopped, but the archive is shipping.
    I am using Windows XP SP2 and Oracle 10gRel2.
    The contents of AlertLog file are as
    Wed Jul 23 22:52:19 2008
    Thread 1 cannot allocate new log, sequence 133
    Checkpoint not complete
    Current log# 3 seq# 132 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
    Wed Jul 23 22:52:23 2008
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    Wed Jul 23 22:52:23 2008
    Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
    Wed Jul 23 22:52:23 2008
    Thread 1 advanced to log sequence 133 (LGWR switch)
    Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
    Thread 1 cannot allocate new log, sequence 134
    Checkpoint not complete
    Current log# 1 seq# 133 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO01.LOG
    Wed Jul 23 22:52:29 2008
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    Wed Jul 23 22:52:29 2008
    Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
    Wed Jul 23 22:52:29 2008
    Thread 1 advanced to log sequence 134 (LGWR switch)
    Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
    Wed Jul 23 22:55:49 2008
    Thread 1 cannot allocate new log, sequence 135
    Checkpoint not complete
    Current log# 2 seq# 134 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO02.LOG
    Wed Jul 23 22:55:54 2008
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    Wed Jul 23 22:55:54 2008
    Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
    Wed Jul 23 22:55:54 2008
    Thread 1 advanced to log sequence 135 (LGWR switch)
    Current log# 3 seq# 135 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\IMRAN\REDO03.LOG
    When i use this command, the SQL Apply starts again but the tablespace is not created on Logical standby database.
    kindly give me a solution.
    Thanks in advanced.

    In Standy database also you need to add TB details for it to recognise Primary DB new TB .
    try adding it and retry your operation .

Maybe you are looking for