1 2 Previous Next 19 Replies Latest reply: Oct 19, 2012 9:38 AM by mseberg RSS

    Problem with current scn on standby database..

    Ecimen
      Hello ;

      one day ago i switched over our primary database to standby database, everything went fine. but today when i checked current scn for both database i saw both were different. and current scn was not changing on standby database. What reason can cause this problem?

      here some outputs when i tried to find out problem..

      on primary database ;

      SQL> select thread#, max(sequence#) from v$archived_log group by thread#;       
         THREAD# MAX(SEQUENCE#)
      ---------- --------------
               1            156 
      on standby database;
      SQL> select thread#, max(sequence#) from v$archived_log  where applied='YES' group by thread#;
      
         THREAD# MAX(SEQUENCE#)
      ---------- --------------
               1            156 
      on standby
      SQL> select LAST_CHANGE#, STATUS from V$STANDBY_LOG;
      
      LAST_CHANGE# STATUS
      ------------ ----------
           2927636 ACTIVE
                 0 UNASSIGNED
                 0 UNASSIGNED
                 0 UNASSIGNED 
      on standby
      SQL> select current_scn from v$database;
      
      CURRENT_SCN
      -----------
          2916773 
      on primary
      SQL> select current_scn from v$database;
      
      CURRENT_SCN
      -----------
          2927809
      Edited by: Ecimen on 18.Eki.2012 01:36

      Edited by: Ecimen on 18.Eki.2012 01:47
        • 1. Re: Problem with current scn on standby database..
          dataseven
          hi,

          could you have a look at this thread

          SCN number difference in primary and standby databases

          regards,
          • 2. Re: Problem with current scn on standby database..
            teits
            Ecimen wrote:
            Hello ;

            one day ago i switched over our primary database to standby database, everything went fine. but today when i checked current scn for both database i saw both were different. and current scn was not changing on standby database. What reason can cause this problem?
            http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm#i77231

            is there an error in your alertlog? if any paste
            are you using USING CURRENT LOGFILE for your redo apply?
            execute on standby.
            also: SELECT name, value, datum_time, time_computed FROM V$DATAGUARD_STATS;



            HTH
            Tobi
            • 3. Re: Problem with current scn on standby database..
              abdul:
              hello,
              what i do first is check :

              [on both side]
              select switchover_status from v$database
              and also verify the output of:

              >
              SELECT to_char(COMPLETION_TIME,'dd-mon-yyyy hh24:mi:ss') FROM V$ARCHIVED_LOG WHERE APPLIED='YES';>

              select timestamp, facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp;
              select     ds.dest_id id
              ,     ad.status
              ,     ds.database_mode db_mode
              ,     ad.archiver type
              ,     ds.recovery_mode
              ,     ds.protection_mode
              ,     ds.standby_logfile_count "SRLs"
              ,     ds.standby_logfile_active active
              ,     ds.archived_seq#
              from     v$archive_dest_status     ds
              ,     v$archive_dest          ad
              where     ds.dest_id = ad.dest_id
              and     ad.status != 'INACTIVE'
              order by
                   ds.dest_id
              /
              [on both side]

              select scn_to_timestamp(<your's db current_scn) from dual;

              Edited by: abdul: on Oct 18, 2012 2:44 PM
              • 4. Re: Problem with current scn on standby database..
                mseberg
                Hello;

                I would double check my Standby Redo Logs and make sure they are the correct size and you have the correct number. But a small lag in SCN between the Primary and the Standby can be expected in general.

                Do a log switch and then try this query :

                http://www.visi.com/~mseberg/monitor_data_guard_transport.html

                Best Regards

                mseberg
                • 5. Re: Problem with current scn on standby database..
                  Ecimen
                  Hello teits
                  SQL> SELECT name, value, datum_time, time_computed FROM V$DATAGUARD_STATS;
                  
                  NAME
                  --------------------------------
                  VALUE
                  ----------------------------------------------------------------
                  DATUM_TIME                     TIME_COMPUTED
                  ------------------------------ ------------------------------
                  transport lag
                  +00 00:00:00
                  10/18/2012 13:12:56            10/18/2012 13:12:57
                  
                  apply lag
                  +00 00:00:00
                  10/18/2012 13:12:56            10/18/2012 13:12:57
                  
                  NAME
                  --------------------------------
                  VALUE
                  ----------------------------------------------------------------
                  DATUM_TIME                     TIME_COMPUTED
                  ------------------------------ ------------------------------
                  
                  apply finish time
                  +00 00:00:00.000
                                                 10/18/2012 13:12:57
                  
                  estimated startup time
                  205
                  
                  NAME
                  --------------------------------
                  VALUE
                  ----------------------------------------------------------------
                  DATUM_TIME                     TIME_COMPUTED
                  ------------------------------ ------------------------------
                                                 10/18/2012 13:12:57
                  Hello abdul
                  on standby
                  SQL> select switchover_status from v$database
                    2  ;
                  
                  SWITCHOVER_STATUS
                  --------------------
                  NOT ALLOWED
                  on primary
                  SQL> select switchover_status from v$database;
                  
                  SWITCHOVER_STATUS
                  --------------------
                  TO STANDBY
                  SQL> select     ds.dest_id id
                  ,       ad.status
                    2    3  ,     ds.database_mode db_mode
                    4  ,  ad.archiver type
                  ,       ds.recovery_mode
                    5    6  ,     ds.protection_mode
                    7  ,  ds.standby_logfile_count "SRLs"
                    8  ,  ds.standby_logfile_active active
                    9  ,  ds.archived_seq#
                   10  from       v$archive_dest_status   ds
                  ,       v$archive_dest          ad
                   11  where      ds.dest_id = ad.dest_id
                   12   13  and   ad.status != 'INACTIVE'
                   14  order by
                          ds.dest_id 15  ;
                  
                          ID STATUS    DB_MODE         TYPE       RECOVERY_MODE
                  ---------- --------- --------------- ---------- -----------------------
                  PROTECTION_MODE            SRLs     ACTIVE ARCHIVED_SEQ#
                  -------------------- ---------- ---------- -------------
                           1 VALID     MOUNTED-STANDBY ARCH       MANAGED REAL TIME APPLY
                  MAXIMUM PERFORMANCE           0          0           159
                  
                          32 VALID     UNKNOWN         ARCH       IDLE
                  MAXIMUM PERFORMANCE           0          0           159
                  output of these queries is too long.
                  SELECT to_char(COMPLETION_TIME,'dd-mon-yyyy hh24:mi:ss') FROM V$ARCHIVED_LOG WHERE APPLIED='YES';
                  select timestamp, facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp;
                  Hello mseberg

                  After i ran "alter system switch logfile;" on primary database , current scn on standby database has changed , shouldnt current scn on standby be same with primary database instantly when online redo log getting applied on primary database?
                  DB_NAME    HOSTNAME       LOG_ARCHIVED LOG_APPLIED APPLIED_TIME   LOG_GAP
                  ---------- -------------- ------------ ----------- -------------- -------
                  PRIMARYD   LOCALHOST               159         159 18-OCT/11:35         0
                  Edited by: Ecimen on 18.Eki.2012 03:26

                  Edited by: Ecimen on 18.Eki.2012 03:42
                  • 6. Re: Problem with current scn on standby database..
                    abdul:
                    hi,
                    After i ran "alter system switch logfile;" on primary database , current scn on standby database has changed , shouldnt current scn on standby be same with primary database instantly when online redo log getting applied on primary database?
                    donot have to worry your database is fine and its not necessarily happen that the both side of current_scn has same .

                    -------------------EDITING-----------------

                    excuse me,

                    run this command
                    [on standby]
                    alter database recover managed standby database cancel;
                    shut immediate;
                    startup mount
                    alter database recover managed standby database disconnect from session;
                    Edited by: abdul: on Oct 18, 2012 4:12 PM
                    • 7. Re: Problem with current scn on standby database..
                      mseberg
                      Hello again;

                      Take a look at :
                      select * from v$recovery_progress;
                      The applied_scn column will give a mechanism of determining how far your standby is lagging behind your primary. If you have any load at at the Standby will always be behind the primary.

                      You cannot transport and apply everything the very instant it occurs on the primary.

                      Best Regards

                      mseberg
                      • 8. Re: Problem with current scn on standby database..
                        Ecimen
                        Hello abdul;
                        SQL> alter database recover managed standby database disconnect from session;
                        alter database recover managed standby database disconnect from session
                        *
                        ERROR at line 1:
                        ORA-01153: an incompatible media recovery is active 
                        hello mseberg

                        on primary
                        SQL> select * from v$recovery_progress;
                        
                        START_TIM TYPE                                                             ITEM                             UNITS                                 SOFAR      TOTAL TIMESTAMP COMMENTS
                        --------- ---------------------------------------------------------------- -------------------------------- -------------------------------- ---------- ---------- --------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                        17-OCT-12 Media Recovery                                                   Log Files                        Files                                     5          5
                        17-OCT-12 Media Recovery                                                   Active Apply Rate                KB/sec                                    4          4
                        17-OCT-12 Media Recovery                                                   Average Apply Rate               KB/sec                                    2          2
                        17-OCT-12 Media Recovery                                                   Maximum Apply Rate               KB/sec                                    4          4
                        17-OCT-12 Media Recovery                                                   Redo Applied                     Megabytes                                 1          1
                        17-OCT-12 Media Recovery                                                   Last Applied Redo                SCN+Time                                  0          0 17-OCT-12 SCN: 02825490
                        17-OCT-12 Media Recovery                                                   Active Time                      Seconds                                   3          3
                        17-OCT-12 Media Recovery                                                   Apply Time per Log               Seconds                                   1          1
                        17-OCT-12 Media Recovery                                                   Elapsed Time                     Seconds                                 387        387
                        
                        9 rows selected.
                        • 9. Re: Problem with current scn on standby database..
                          abdul:
                          SQL> alter database recover managed standby database disconnect from session;
                          alter database recover managed standby database disconnect from session
                          *
                          ERROR at line 1:
                          ORA-01153: an incompatible media recovery is active
                          >


                          Most likely you had missed the logfiles from standby site; you can verify it by issue "select max(SEQUENCE#) from v$loghist". Most likely the old logfiles did not yet shipped to standby site from primary site. Another simple way you can do is tio shutdown standby db, then start it as mount mode if you have 11gR2 db that should be enough. Oracle will automatically in sync between primary and standby for you. If you can not wait, you could start the mount mode for standby db, then issue the command " recover standby database until cancel;
                          • 10. Re: Problem with current scn on standby database..
                            Ecimen
                            Output is the same for both database;
                            SQL> select max(SEQUENCE#) from v$loghist
                              2  ;
                            
                            MAX(SEQUENCE#)
                            --------------
                                       160
                            when i run the command "recover standby database until cancel;" on standby database i still get the same error
                            SQL>  recover standby database until cancel;
                            ORA-01153: an incompatible media recovery is active
                            • 11. Re: Problem with current scn on standby database..
                              teits
                              Ecimen wrote:
                              SQL>  recover standby database until cancel;
                              ORA-01153: an incompatible media recovery is active
                              can you re-check this : on standby
                               SELECT to_char(COMPLETION_TIME,'dd-mon-yyyy hh24:mi:ss'),name,sequence#,applied,creator FROM V$ARCHIVED_LOG a WHERE APPLIED!='YES';  
                              have you ever used "KEEP" option in your rman command?

                              please grep your alertlog file for error...paste error related to HA.
                              e.g
                               $cat alert_sid.log |grep -i ora-|grep -v TNS:no  
                              • 12. Re: Problem with current scn on standby database..
                                Ecimen
                                on standby
                                TO_CHAR(COMPLETION_T
                                --------------------
                                NAME
                                ------------------------------
                                 SEQUENCE# APPLIED   CREATOR
                                ---------- --------- -------
                                17-oct-2012 17:19:05
                                secondarydb
                                       145 NO        ARCH
                                
                                17-oct-2012 17:19:09
                                secondarydb
                                       146 NO        FGRD
                                
                                17-oct-2012 17:19:13
                                secondarydb
                                       147 NO        FGRD
                                no i didnt use keep option.

                                here output of $cat alert_sid.log |grep -i ora-|grep -v TNS:no on standby database;
                                ORA-03135: connection lost contact
                                ORA-03135: connection lost contact
                                ORA-03135: connection lost contact
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-16058: standby database instance is not mounted
                                ORA-1109 signalled during: alter database CLOSE NORMAL...
                                ksuapc : ORA-1033 foreground process starts before PMON
                                ORA-01034: ORACLE not available
                                ORA-01034: ORACLE not available
                                ORA-1093 signalled during: alter database recover if needed
                                ORA-1093 signalled during: alter database recover if needed
                                ORA-16136 signalled during: alter database recover managed standby database cancel...
                                ORA-01034: ORACLE not available
                                ORA-01034: ORACLE not available
                                ORA-16055: FAL request rejected
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-16058: standby database instance is not mounted
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1665 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE...
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-1109 signalled during: alter database CLOSE NORMAL...
                                ORA-12537: TNS:connection closed
                                ORA-12537: TNS:connection closed
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1665 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1665 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE...
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-1665 signalled during: alter database recover managed standby database using current logfile disconnect...
                                ORA-1109 signalled during: alter database CLOSE NORMAL...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1665 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE...
                                ORA-1100 signalled during: ALTER DATABASE MOUNT...
                                ORA-1665 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE...
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-16047: DGID mismatch between destination setting and target database
                                ORA-1109 signalled during: alter database CLOSE NORMAL...
                                ORA-00235: control file read without a lock inconsistent due to concurrent update
                                ORA-16037: user requested cancel of managed recovery operation
                                ORA-16037: user requested cancel of managed recovery operation
                                ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
                                ORA-1153 signalled during: alter database recover managed standby database disconnect from session...
                                ORA-1153 signalled during: ALTER DATABASE RECOVER  standby database until cancel  ...
                                and also theres an error related to tns in alert.log
                                ***********************************************************************
                                
                                Fatal NI connect error 12514, connecting to:
                                 (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.150.30.162)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=second_DGB)(CID=(PROGRAM=oracle)(HOST=primarydb)(USER=oracle))))
                                
                                  VERSION INFORMATION:
                                        TNS for Linux: Version 11.2.0.1.0 - Production
                                        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
                                  Time: 18-OCT-2012 14:08:46
                                  Tracing not turned on.
                                  Tns error struct:
                                    ns main err code: 12564
                                
                                TNS-12564: TNS:connection refused
                                    ns secondary err code: 0
                                    nt main err code: 0
                                    nt secondary err code: 0
                                    nt OS err code: 0
                                maybe its normal getting this error since our primary database is now standby database?

                                Edited by: Ecimen on 18.Eki.2012 06:15
                                • 13. Re: Problem with current scn on standby database..
                                  expressoteam
                                  Ecimen wrote:
                                  ORA-16047: DGID mismatch between destination setting and target database
                                  fyi: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter matches the DB_UNIQUE_NAME parameter defined at the destination.

                                  >
                                  and also theres an error related to tns in alert.log
                                  ***********************************************************************
                                  
                                  Fatal NI connect error 12514, connecting to:
                                  (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.150.30.162)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=second_DGB)(CID=(PROGRAM=oracle)(HOST=primarydb)(USER=oracle))))
                                  
                                  VERSION INFORMATION:
                                  TNS for Linux: Version 11.2.0.1.0 - Production
                                  TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
                                  Time: 18-OCT-2012 14:08:46
                                  Tracing not turned on.
                                  Tns error struct:
                                  ns main err code: 12564
                                  
                                  TNS-12564: TNS:connection refused
                                  ns secondary err code: 0
                                  nt main err code: 0
                                  nt secondary err code: 0
                                  nt OS err code: 0
                                  maybe its normal getting this error since our primary database is now standby database?
                                  you should not get tns error because of switchover

                                  Tobi
                                  • 14. Re: Problem with current scn on standby database..
                                    Ecimen
                                    Well trying to fix this problem since 2 days with no luck.. everything seems ok but i dont know why tns gives error..

                                    i am sure archive logs are transfering to standby database but online redo logs not getting applied instantly on standby database ..and also getting "ORA-01153: an incompatible media recovery is active" when i try to run "recover standby database until cancel;" on standby database due to missing logs (no idea why i am getting this error maybe related to tns error thats why..)

                                    here alert.log on standby database;
                                     Fatal NI connect error 12514, connecting to:
                                     (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.150.30.162)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=second_DGB)(CID=(PROGRAM=oracle)(HOST=primarydb)(USER=oracle))))
                                    
                                      VERSION INFORMATION:
                                            TNS for Linux: Version 11.2.0.1.0 - Production
                                            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
                                      Time: 19-OCT-2012 14:12:54
                                      Tracing not turned on.
                                      Tns error struct:
                                        ns main err code: 12564
                                    
                                    TNS-12564: TNS:connection refused
                                        ns secondary err code: 0
                                        nt main err code: 0
                                        nt secondary err code: 0
                                        nt OS err code: 0
                                    Fri Oct 19 14:12:57 2012
                                    RSM0 started with pid=30, OS id=18868
                                    ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='primarydb';
                                    ALTER SYSTEM SET log_archive_format='%t_%s_%r.dbf' SCOPE=SPFILE SID='primarydb';
                                    Fri Oct 19 14:18:08 2012
                                    Media Recovery Waiting for thread 1 sequence 174
                                    Fri Oct 19 14:18:13 2012
                                    RFS[3]: Selected log 4 for thread 1 sequence 174 dbid 151255635 branch 795784662
                                    Fri Oct 19 14:18:22 2012
                                    Recovery of Online Redo Log: Thread 1 Group 4 Seq 174 Reading mem 0
                                      Mem# 0: +DATA/primarydb/onlinelog/group_4.266.795859605
                                    Fri Oct 19 14:18:43 2012
                                    Archived Log entry 231 added for thread 1 sequence 173 ID 0x9163e06 dest 1:
                                    Fri Oct 19 14:35:15 2012
                                    ALTER DATABASE RECOVER  standby database until cancel
                                    ORA-1153 signalled during: ALTER DATABASE RECOVER  standby database until cancel  ...
                                    here is the status of listeners on primary and standby databases after i switched over....

                                    listener status on standby database;
                                    [oracle@primarydb ~]$ lsnrctl status
                                    
                                    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 19-OCT-2012 14:38:39
                                    
                                    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
                                    
                                    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.150.30.113)(PORT=1521)))
                                    STATUS of the LISTENER
                                    ------------------------
                                    Alias                     LISTENER
                                    Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
                                    Start Date                19-OCT-2012 11:35:53
                                    Uptime                    0 days 3 hr. 2 min. 45 sec
                                    Trace Level               off
                                    Security                  ON: Local OS Authentication
                                    SNMP                      OFF
                                    Listener Parameter File   /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
                                    Listener Log File         /u01/app/oracle/diag/tnslsnr/primarydb/listener/alert/log.xml
                                    Listening Endpoints Summary...
                                      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
                                      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.150.30.113)(PORT=1521)))
                                    Services Summary...
                                    Service "+ASM" has 1 instance(s).
                                      Instance "+ASM", status READY, has 1 handler(s) for this service...
                                    Service "PLSExtProc" has 1 instance(s).
                                      Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
                                    Service "primary" has 1 instance(s).
                                      Instance "primarydb", status READY, has 1 handler(s) for this service...
                                    Service "primary_DGB" has 1 instance(s).
                                      Instance "primarydb", status READY, has 1 handler(s) for this service...
                                    Service "primarydb" has 1 instance(s).
                                      Instance "primarydb", status UNKNOWN, has 2 handler(s) for this service...
                                    The command completed successfully 
                                    listener status on primary database
                                    [oracle@secondarydb admin]$ lsnrctl status
                                    
                                    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 19-OCT-2012 14:39:27
                                    
                                    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
                                    
                                    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=secondarydb)(PORT=1521))
                                    STATUS of the LISTENER
                                    ------------------------
                                    Alias                     LISTENER
                                    Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
                                    Start Date                19-OCT-2012 09:10:27
                                    Uptime                    0 days 5 hr. 29 min. 0 sec
                                    Trace Level               off
                                    Security                  ON: Local OS Authentication
                                    SNMP                      OFF
                                    Listener Parameter File   /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
                                    Listener Log File         /u01/app/oracle/diag/tnslsnr/secondarydb/listener/alert/log.xml
                                    Listening Endpoints Summary...
                                      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.150.30.162)(PORT=1521)))
                                      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))
                                    Services Summary...
                                    Service "PLSExtProc" has 1 instance(s).
                                      Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
                                    Service "second_DGMGRL" has 1 instance(s).
                                      Instance "secondarydb", status UNKNOWN, has 1 handler(s) for this service...
                                    Service "secondarydb" has 1 instance(s).
                                      Instance "secondarydb", status UNKNOWN, has 1 handler(s) for this service...
                                    The command completed successfully
                                    by the way no idea why second_DGB service is not up on primary database..maybe because of this we are having problem?

                                    Edited by: Ecimen on 19.Eki.2012 04:56
                                    1 2 Previous Next