1 2 Previous Next 16 Replies Latest reply: Feb 2, 2011 3:18 AM by 688970 RSS

    archive logs not shipped !!

    user106161
      Hi Guys,

      I am using oracle 10.2.0.4.0 on windows 2003 server. I created a standby database using RMAN duplicate command. I also re created password file on primary database as follows
      C:\oracle\10.2.0\database>orapwd file=orapw$ORACLE_SID password=XXXX force=y
      and copied it across to standby. My standby database was successfully created but my archive logs are not shipped to standby. I also did tnsping and it looks okie. I fired the following query on standby :

      SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
      2 order by SEQUENCE#
      3 ;

      no rows selected

      Any idea where I am going wrong. Would appreciate your help :)

      Thanks in advance!!!

      Regards
        • 1. Re: archive logs not shipped !!
          728006
          Hi

          Can you please give me the output of archive log list from both primary and standby and output of log_archive_dest from primary


          KK

          Edited by: user12061936 on Nov 9, 2010 11:14 AM
          • 2. Re: archive logs not shipped !!
            744052
            You primary database execute the following

            SQL> ALTER SYSTEM SWITCH LOGFILE;

            and then check the V$ARCHIVED_LOG on the standby database.

            Thanks.
            • 3. Re: archive logs not shipped !!
              Dan A
              User:

              On the standby, try this:

              select max (sequence#), applied from v$archived_log where applied = 'YES' group by applied;


              DA.
              • 4. Re: archive logs not shipped !!
                user106161
                Hi,

                Primary

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 12518.
                Thu Oct 28 13:40:09 2010
                Error 12170 received logging on to the standby
                Thu Oct 28 13:40:09 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-12170: Message 12170 not found; No message file for product=RDBMS, facility=ORA

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 1034.
                Thu Oct 28 14:20:10 2010
                Error 1034 received logging on to the standby
                Thu Oct 28 14:20:10 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-01034: Message 1034 not found; No message file for product=RDBMS, facility=ORA

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 1034.
                Thu Oct 28 14:21:44 2010
                ALTER SYSTEM ARCHIVE LOG
                Thu Oct 28 14:21:44 2010
                Thread 1 advanced to log sequence 12452 (LGWR switch)
                Current log# 2 seq# 12452 mem# 0: D:\ORACLE\ORADATA\STUTEST\REDO02A.LOG
                Current log# 2 seq# 12452 mem# 1: E:\ORACLE\ORADATA\STUTEST\REDO02B.LOG
                Thu Oct 28 14:25:10 2010
                Error 1031 received logging on to the standby
                Thu Oct 28 14:25:10 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-01031: Message 1031 not found; No message file for product=RDBMS, facility=ORA

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 1031.
                Thu Oct 28 14:29:33 2010
                ALTER SYSTEM ARCHIVE LOG
                Thu Oct 28 14:29:33 2010
                Thread 1 advanced to log sequence 12453 (LGWR switch)
                Current log# 3 seq# 12453 mem# 0: D:\ORACLE\ORADATA\STUTEST\REDO03A.LOG
                Current log# 3 seq# 12453 mem# 1: E:\ORACLE\ORADATA\STUTEST\REDO03B.LOG
                Thu Oct 28 14:30:11 2010
                Error 1031 received logging on to the standby
                Thu Oct 28 14:30:11 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-01031: Message 1031 not found; No message file for product=RDBMS, facility=ORA

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 1031.
                Thu Oct 28 14:32:07 2010
                Clearing standby activation ID 2482107584 (0x93f1f4c0)
                The primary database controlfile was created using the
                'MAXLOGFILES 16' clause.
                There is space for up to 13 standby redo logfiles
                Use the following SQL commands on the standby database to create
                standby redo logfiles that match the primary database:
                ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 104857600;
                ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 104857600;
                ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 104857600;
                ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 104857600;
                WARNING: OMF is enabled on this database. Creating a physical
                standby controlfile, when OMF is enabled on the primary
                database, requires manual RMAN intervention to resolve OMF
                datafile pathnames.
                NOTE: Please refer to the RMAN documentation for procedures
                describing how to manually resolve OMF datafile pathnames.
                Starting control autobackup
                Control autobackup written to DISK device
                     handle 'G:\ORACLE\FLASH_RECOVERY_AREA\STUTEST\AUTOBACKUP\2010_10_28\O1_MF_S_733588328_6DLYTTS7_.BKP'
                Thu Oct 28 14:35:11 2010
                Error 1031 received logging on to the standby
                Thu Oct 28 14:35:11 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-01031: Message 1031 not found; No message file for product=RDBMS, facility=ORA

                PING[ARC4]: Heartbeat failed to connect to standby 'STUSTDBY'. Error is 1031.
                Thu Oct 28 14:55:11 2010
                Error 1031 received logging on to the standby
                Thu Oct 28 14:55:11 2010
                Errors in file c:\oracle\admin\stutest\bdump\stutest_arc4_11568.trc:
                ORA-01031: Message 1031 not found; No message file for product=RDBMS, facility=ORA

                Standby:

                Dump file c:\oracle\admin\stustdby\bdump\alert_stustdby.log
                Mon Nov 08 13:44:01 2010
                ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
                vsnsql=14 vsnxtr=3
                Windows Server 2003 Version V5.2 Service Pack 2
                CPU : 8 - type 8664, 2 Physical Cores
                Process Affinity : 0x0000000000000000
                Memory (Avail/Total): Ph:15165M/16378M, Ph+PgF:17124M/17814M
                Mon Nov 08 13:44:01 2010
                Starting ORACLE instance (normal)
                LICENSE_MAX_SESSION = 0
                LICENSE_SESSIONS_WARNING = 0
                Picked latch-free SCN scheme 3
                Autotune of undo retention is turned on.
                IMODE=BR
                ILAT =24
                LICENSE_MAX_USERS = 0
                SYS auditing is disabled
                ksdpec: called for event 13740 prior to event group initialization
                Starting up ORACLE RDBMS Version: 10.2.0.4.0.
                System parameters with non-default values:
                processes = 200
                sessions = 225
                sga_max_size = 7230980096
                nls_language = ENGLISH
                nls_territory = UNITED KINGDOM
                resource_manager_plan =
                sga_target = 5133828096
                db_file_name_convert = H:\ORACLE\ORADATA\STUTEST\, H:\ORACLE\ORADATA\STUTEST\std_, I:\ORACLE\ORADATA\STUTEST\, I:\ORACLE\ORADATA\STUTEST\std_, F:\ORACLE\ORADATA\STUTEST\, F:\ORACLE\ORADATA\STUTEST\std_, E:\ORACLE\ORADATA\STUTEST\, E:\ORACLE\ORADATA\STUTEST\std_
                log_file_name_convert = D:\oracle\oradata\STUTEST\, D:\oracle\oradata\STUTEST\std_, E:\oracle\oradata\STUTEST\, E:\oracle\oradata\STUTEST\std_
                db_block_size = 8192
                compatible = 10.2.0.1.0
                log_archive_config = DG_CONFIG=(STUTEST,STUSTDBY)
                log_archive_dest_1 = LOCATION=H:\oracle\oradata\stutest\ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STUSTDBY
                log_archive_dest_2 = SERVICE=STUTEST LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STUTEST
                log_archive_dest_state_1 = ENABLE
                log_archive_dest_state_2 = ENABLE
                log_archive_max_processes= 10
                log_archive_min_succeed_dest= 1
                standby_archive_dest = H:\oracle\oradata\stutest\ARCH
                log_archive_trace = 0
                fal_client = STUSTDBY
                fal_server = STUTEST
                archive_lag_target = 0
                db_file_multiblock_read_count= 32
                db_recovery_file_dest = G:\oracle\flash_recovery_area
                db_recovery_file_dest_size= 42949672960
                standby_file_management = AUTO
                undo_management = AUTO
                undo_tablespace = UNDOTBS2
                undo_retention = 900
                remote_login_passwordfile= EXCLUSIVE
                db_domain =
                service_names = STUTEST
                dispatchers = (PROTOCOL=TCP) (SERVICE=STUTESTXDB)
                shared_servers = 4
                remote_dependencies_mode = SIGNATURE
                job_queue_processes = 10
                cursor_sharing = SIMILAR
                audit_file_dest = C:\ORACLE\ADMIN\STUSTDBY\ADUMP
                background_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\BDUMP
                user_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\UDUMP
                core_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\CDUMP
                db_name = STUTEST
                db_unique_name = STUSTDBY
                open_cursors = 300
                pga_aggregate_target = 1572864000
                PMON started with pid=2, OS id=744
                MMAN started with pid=4, OS id=5652
                DBW0 started with pid=5, OS id=4468
                LGWR started with pid=6, OS id=2636
                CKPT started with pid=7, OS id=3620
                SMON started with pid=8, OS id=580
                RECO started with pid=9, OS id=4516
                PSP0 started with pid=3, OS id=1844
                Mon Nov 08 13:44:06 2010
                starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
                Mon Nov 08 13:44:06 2010
                starting up 4 shared server(s) ...
                MMON started with pid=11, OS id=4616
                CJQ0 started with pid=10, OS id=5144
                MMNL started with pid=12, OS id=4952
                Mon Nov 08 13:44:36 2010
                Shutting down instance: further logons disabled
                Mon Nov 08 13:44:36 2010
                Stopping background process CJQ0
                Mon Nov 08 13:44:37 2010
                Stopping background process MMNL
                Mon Nov 08 13:44:38 2010
                Stopping background process MMON
                Mon Nov 08 13:44:38 2010
                Shutting down instance (immediate)
                License high water mark = 1
                Mon Nov 08 13:44:38 2010
                Stopping Job queue slave processes, flags = 7
                Mon Nov 08 13:44:38 2010
                Job queue slave processes stopped
                Waiting for dispatcher 'D000' to shutdown
                All dispatchers and shared servers shutdown
                Mon Nov 08 13:44:40 2010
                ALTER DATABASE CLOSE NORMAL
                ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
                ARCH: Archival disabled due to shutdown: 1089
                Shutting down archive processes
                Archiving is disabled
                Archive process shutdown avoided: 0 active
                ARCH: Archival disabled due to shutdown: 1089
                Shutting down archive processes
                Archiving is disabled
                Archive process shutdown avoided: 0 active
                Mon Nov 08 13:44:57 2010
                Starting ORACLE instance (normal)
                LICENSE_MAX_SESSION = 0
                LICENSE_SESSIONS_WARNING = 0
                Picked latch-free SCN scheme 3
                Autotune of undo retention is turned on.
                IMODE=BR
                ILAT =24
                LICENSE_MAX_USERS = 0
                SYS auditing is disabled
                ksdpec: called for event 13740 prior to event group initialization
                Starting up ORACLE RDBMS Version: 10.2.0.4.0.
                System parameters with non-default values:
                processes = 200
                sessions = 225
                sga_max_size = 7230980096
                nls_language = ENGLISH
                nls_territory = UNITED KINGDOM
                resource_manager_plan =
                sga_target = 5133828096
                db_file_name_convert = H:\ORACLE\ORADATA\STUTEST\, H:\ORACLE\ORADATA\STUTEST\std_, I:\ORACLE\ORADATA\STUTEST\, I:\ORACLE\ORADATA\STUTEST\std_, F:\ORACLE\ORADATA\STUTEST\, F:\ORACLE\ORADATA\STUTEST\std_, E:\ORACLE\ORADATA\STUTEST\, E:\ORACLE\ORADATA\STUTEST\std_
                log_file_name_convert = D:\oracle\oradata\STUTEST\, D:\oracle\oradata\STUTEST\std_, E:\oracle\oradata\STUTEST\, E:\oracle\oradata\STUTEST\std_
                db_block_size = 8192
                compatible = 10.2.0.1.0
                log_archive_config = DG_CONFIG=(STUTEST,STUSTDBY)
                log_archive_dest_1 = LOCATION=H:\oracle\oradata\stutest\ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STUSTDBY
                log_archive_dest_2 = SERVICE=STUTEST LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STUTEST
                log_archive_dest_state_1 = ENABLE
                log_archive_dest_state_2 = ENABLE
                log_archive_max_processes= 10
                log_archive_min_succeed_dest= 1
                standby_archive_dest = H:\oracle\oradata\stutest\ARCH
                log_archive_trace = 0
                fal_client = STUSTDBY
                fal_server = STUTEST
                archive_lag_target = 0
                db_file_multiblock_read_count= 32
                db_recovery_file_dest = G:\oracle\flash_recovery_area
                db_recovery_file_dest_size= 42949672960
                standby_file_management = AUTO
                undo_management = AUTO
                undo_tablespace = UNDOTBS2
                undo_retention = 900
                remote_login_passwordfile= EXCLUSIVE
                db_domain =
                service_names = STUTEST
                dispatchers = (PROTOCOL=TCP) (SERVICE=STUTESTXDB)
                shared_servers = 4
                remote_dependencies_mode = SIGNATURE
                job_queue_processes = 10
                cursor_sharing = SIMILAR
                audit_file_dest = C:\ORACLE\ADMIN\STUSTDBY\ADUMP
                background_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\BDUMP
                user_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\UDUMP
                core_dump_dest = C:\ORACLE\ADMIN\STUSTDBY\CDUMP
                db_name = STUTEST
                db_unique_name = STUSTDBY
                open_cursors = 300
                pga_aggregate_target = 1572864000
                PMON started with pid=2, OS id=3728
                PSP0 started with pid=3, OS id=4568
                MMAN started with pid=4, OS id=5136
                DBW0 started with pid=5, OS id=5696
                CKPT started with pid=7, OS id=5084
                SMON started with pid=8, OS id=5592
                RECO started with pid=9, OS id=1088
                CJQ0 started with pid=10, OS id=5668
                MMON started with pid=11, OS id=5736
                Mon Nov 08 13:44:58 2010
                starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
                Mon Nov 08 13:44:58 2010
                starting up 4 shared server(s) ...
                LGWR started with pid=6, OS id=5848
                MMNL started with pid=12, OS id=5560
                Mon Nov 08 13:49:11 2010
                The input backup piece G:\ORACLE\FLASH_RECOVERY_AREA\STUTEST\BACKUPSET\2010_11_08\O1_MF_NCNNF_TAG20101108T130958_6FHXO6G1_.BKP is in compressed format.
                Mon Nov 08 13:49:13 2010
                alter database mount standby database
                Mon Nov 08 13:49:17 2010
                Setting recovery target incarnation to 1
                ARCH: STARTING ARCH PROCESSES
                ARC0 started with pid=22, OS id=5556
                ARC1 started with pid=23, OS id=2744
                ARC2 started with pid=24, OS id=784
                ARC3 started with pid=25, OS id=5772
                ARC4 started with pid=26, OS id=5096
                ARC5 started with pid=27, OS id=6028
                ARC6 started with pid=28, OS id=3960
                ARC7 started with pid=29, OS id=5676
                ARC8 started with pid=30, OS id=6000
                Mon Nov 08 13:49:17 2010
                ARC0: Archival started
                Mon Nov 08 13:49:17 2010
                ARC1: Archival started
                ARC2: Archival started
                ARC3: Archival started
                ARC4: Archival started
                ARC5: Archival started
                ARC6: Archival started
                ARC7: Archival started
                ARC8: Archival started
                ARC9: Archival started
                ARCH: STARTING ARCH PROCESSES COMPLETE
                Mon Nov 08 13:49:17 2010
                ARC1: Becoming the 'no FAL' ARCH
                ARC1: Becoming the 'no SRL' ARCH
                Mon Nov 08 13:49:17 2010
                ARC0: Becoming the heartbeat ARCH
                Mon Nov 08 13:49:17 2010
                ARC0: Thread not mounted
                Mon Nov 08 13:49:17 2010
                Successful mount of redo thread 1, with mount id 2486280025
                Mon Nov 08 13:49:17 2010
                Physical Standby Database mounted.
                Completed: alter database mount standby database
                ARC9 started with pid=31, OS id=1532
                Mon Nov 08 13:49:18 2010
                ARC3: Thread not mounted
                Mon Nov 08 13:49:19 2010
                ARC7: Thread not mounted
                Mon Nov 08 13:49:20 2010
                ARC5: Thread not mounted
                Mon Nov 08 13:49:21 2010
                ARC6: Thread not mounted
                Mon Nov 08 13:49:22 2010
                The input backup piece G:\ORACLE\FLASH_RECOVERY_AREA\STUTEST\BACKUPSET\2010_11_08\O1_MF_NNNDF_FULL_BACKUP_20101108_6FHPV3M6_.BKP is in compressed format.
                Mon Nov 08 13:49:22 2010
                ARC8: Thread not mounted
                Mon Nov 08 13:49:23 2010
                ARC2: Thread not mounted
                Mon Nov 08 13:49:24 2010
                ARC4: Thread not mounted
                Mon Nov 08 13:49:25 2010
                ARC1: Thread not mounted
                Mon Nov 08 13:56:25 2010
                Full restore complete of datafile 21 F:\ORACLE\ORADATA\STUTEST\STD_TS_BIGIX02.DBF. Elapsed time: 0:07:02
                checkpoint is 1086212221
                last deallocation scn is 1050615953
                Mon Nov 08 13:57:32 2010
                Full restore complete of datafile 9 F:\ORACLE\ORADATA\STUTEST\STD_TS_BIGIX01.DBF. Elapsed time: 0:08:10
                checkpoint is 1086212221
                last deallocation scn is 1050615956
                Mon Nov 08 13:57:44 2010
                Full restore complete of datafile 7 H:\ORACLE\ORADATA\STUTEST\STD_TOOLS01.DBF. Elapsed time: 0:00:12
                checkpoint is 1086212221
                last deallocation scn is 723726110
                Mon Nov 08 13:59:09 2010
                Full restore complete of datafile 19 I:\ORACLE\ORADATA\STUTEST\STD_TS_FES02.DBF. Elapsed time: 0:09:47
                checkpoint is 1086212221
                last deallocation scn is 1050668295
                Mon Nov 08 14:00:01 2010
                db_recovery_file_dest_size of 40960 MB is 0.02% used. This is a
                user-specified limit on the amount of space that will be used by this
                database for recovery-related files, and does not reflect the amount of
                space available in the underlying filesystem or ASM diskgroup.
                Mon Nov 08 14:01:58 2010
                Full restore complete of datafile 13 F:\ORACLE\ORADATA\STUTEST\STD_TS_FESIX01.DBF. Elapsed time: 0:04:14
                checkpoint is 1086212221
                last deallocation scn is 1050667841


                Clearing online redo logfile 2 D:\ORACLE\ORADATA\STUTEST\STD_REDO02A.LOG
                Clearing online log 2 of thread 1 sequence number 12653
                Mon Nov 08 14:12:18 2010
                Errors in file c:\oracle\admin\stustdby\bdump\stustdby_mrp0_4244.trc:
                ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [2] [1]
                ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [2] [1] [E:\ORACLE\ORADATA\STUTEST\STD_REDO02B.LOG]
                ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
                OSD-04002: unable to open file
                O/S-Error: (OS 2) The system cannot find the file specified.
                ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [2] [1] [D:\ORACLE\ORADATA\STUTEST\STD_REDO02A.LOG]
                ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
                OSD-04002: unable to open file
                O/S-Error: (OS 2) The system cannot find the file specified.

                Clearing online redo logfile 2 complete
                Mon Nov 08 14:12:20 2010
                Errors in file c:\oracle\admin\stustdby\bdump\stustdby_mrp0_4244.trc:
                ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [3] [1]
                ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [3] [1] [E:\ORACLE\ORADATA\STUTEST\STD_REDO03B.LOG]
                ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
                OSD-04002: unable to open file
                O/S-Error: (OS 2) The system cannot find the file specified.
                ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [3] [1] [D:\ORACLE\ORADATA\STUTEST\STD_REDO03A.LOG]
                ORA-27041: Message 27041 not found; No message file for product=RDBMS, facility=ORA
                OSD-04002: unable to open file
                O/S-Error: (OS 2) The system cannot find the file specified.

                Mon Nov 08 14:13:22 2010
                Error 1017 received logging on to the standby
                ------------------------------------------------------------
                Check that the primary and standby are using a password file
                and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
                and that the SYS password is same in the password files.
                returning error ORA-16191
                ------------------------------------------------------------
                FAL[client, MRP0]: Error 16191 connecting to STUTEST for fetching gap sequence
                Mon Nov 08 14:13:22 2010
                Errors in file c:\oracle\admin\stustdby\bdump\stustdby_mrp0_4244.trc:
                ORA-16191: Message 16191 not found; No message file for product=RDBMS, facility=ORA

                Mon Nov 08 14:13:52 2010
                Errors in file c:\oracle\admin\stustdby\bdump\stustdby_mrp0_4244.trc:
                ORA-01017: Message 1017 not found; No message file for product=RDBMS, facility=ORA

                Edited by: user12951692 on 09-Nov-2010 04:38
                • 5. Re: archive logs not shipped !!
                  user106161
                  Yes I did that, it doesnot work
                  • 6. Re: archive logs not shipped !!
                    user106161
                    Hi Dan,

                    SQL> select max (sequence#), applied from v$archived_log where applied = 'YES' group by applied;

                    no rows selected

                    Thank
                    • 7. Re: archive logs not shipped !!
                      user106161
                      Any help GUYS!!!
                      • 8. Re: archive logs not shipped !!
                        728006
                        Hi

                        Check the log file wht you have posted there is lot of error is there and is ur rman duplicate is completed successfully of failed with some errors?

                        From Primary

                        sqlplus

                        conn sys/pwd@stby as sysdba -->can you paste the output...


                        KK

                        Edited by: user12061936 on Nov 9, 2010 2:32 PM
                        • 9. Re: archive logs not shipped !!
                          user106161
                          Thanks for ur reply KK

                          Yes My rman duplication worked fine and gave no errors


                          On primary

                          C:\oracle\10.2.0\database>sqlplus sys/XXXXX@stustdby as sysdba

                          SQL*Plus: Release 10.2.0.4.0 - Production on Tue Nov 9 14:43:43 2010

                          Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

                          ERROR:
                          ORA-01031: insufficient privileges



                          C:\>tnsping stustdby

                          TNS Ping Utility for 64-bit Windows: Version 10.2.0.4.0 - Production on 09-NOV-2010 14:44:52

                          Copyright (c) 1997, 2007, Oracle. All rights reserved.

                          Used parameter files:
                          C:\oracle\10.2.0\network\admin\sqlnet.ora


                          Used TNSNAMES adapter to resolve the alias
                          Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = mledbstandby.colchester.ac.uk)(P
                          ORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = STUSTDBY)))
                          OK (20 msec)
                          • 10. Re: archive logs not shipped !!
                            728006
                            Hi

                            see the error that is the reason why it is not able to ship the logs to standby, check the password file or the service name...or drop and create the password file with the same password on both primary and standby.

                            if the below command is working then i believe your logs is going to ship to standby.

                            sqlplus sys/XXXXX@stustdby as sysdba

                            KK

                            Edited by: user12061936 on Nov 9, 2010 3:32 PM
                            • 11. Re: archive logs not shipped !!
                              user106161
                              Hi KK,

                              I understood your point. I checked my listerner file and tnnames file. I recreated my password file on primary and transported it to my standby database. It still gives me same error.
                              • 12. Re: archive logs not shipped !!
                                688970
                                Check whether your OS user is part of ORA_DBA group. You can find this group by going to start>RUN>compmgmt.msc (type it). Click OK. Click Local Users and Groups and then double click Groups. Again double click ora_dba. Find if the user is the member of this group. If not add user in the format domainname\username. Click apply and OK.

                                KK is right. If you cannot do the following from primary
                                sqlplus sys/yyyy@standby
                                then your logs will not be shipped to standby.

                                Also create password file for standby seperately ( I mean create at standby server) rather than creating at primary and taking it across to standby, of course you can use the same password..

                                Hope it works

                                Edited by: jazz81 on 10-Nov-2010 16:31
                                • 13. Re: archive logs not shipped !!
                                  714611
                                  Hello.

                                  Are you have a standby redolog files on standby database?
                                  • 14. Re: archive logs not shipped !!
                                    user106161
                                    Hi

                                    My redo logs are not shipped from primary to standby

                                    Thanks
                                    1 2 Previous Next