Archives are not transorting to standby database

Hi Experts,
DB version: 10.2.0.4
OS Version: Windows 2003
Here i have one issue, unable to transfer the archives from Primary to standby database.
I have no errors found in primary and also in standby database, I can able to ping both primary & standby database from both locations, I unable to trace the issue,
Take as high importance.Can any one help. Appriciated for your help.
Completed: alter database recover managed standby database cancel
Fri Jan 28 22:36:49 2011
alter database recover managed standby database disconnect from session
MRP0 started with pid=24, OS id=2164
Managed Standby Recovery not using Real Time ApplyMedia Recovery Waiting for thread 1 sequence 84857
Fri Jan 28 22:36:55 2011
Completed: alter database recover managed standby database disconnect from session

Post the values of the following parameters from your standby database: fal_client and fal_server, SQL> show parameter falNAME TYPE VALUE
fal_client string STBY
fal_server string SYS
also post the last 100 lines from the alert log of your production database.
Thread 1 advanced to log sequence 84895
Current log# 1 seq# 84895 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84895 mem# 1: F:\ORA_DATA\REDO01A.LOG
Fri Jan 28 22:00:10 2011
Thread 1 advanced to log sequence 84896
Current log# 3 seq# 84896 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84896 mem# 1: F:\ORA_DATA\REDO03A.LOG
Thread 1 advanced to log sequence 84897
Current log# 2 seq# 84897 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84897 mem# 1: F:\ORA_DATA\REDO02A.LOG
Fri Jan 28 22:00:34 2011
Thread 1 advanced to log sequence 84898
Current log# 1 seq# 84898 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84898 mem# 1: F:\ORA_DATA\REDO01A.LOG
Fri Jan 28 22:02:13 2011
Thread 1 advanced to log sequence 84899
Current log# 3 seq# 84899 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84899 mem# 1: F:\ORA_DATA\REDO03A.LOG
Fri Jan 28 23:37:21 2011
ALTER SYSTEM SET log_archive_dest_state_2='enable' SCOPE=BOTH;
Fri Jan 28 23:46:36 2011
ALTER SYSTEM SET log_archive_max_processes=12 SCOPE=BOTH;
Sat Jan 29 00:01:32 2011
alter database add standby logfile thread 1
group 4 size 50m,
group 5 size 50m
Sat Jan 29 00:01:35 2011
Starting control autobackup
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Control autobackup written to DISK device
handle 'J:\ORACLE\RECO\SYS\AUTOBACKUP\2011_01_29\O1_MF_S_741657695_6N77SKJM_.BKP'
Sat Jan 29 00:09:32 2011
Thread 1 advanced to log sequence 84900
Current log# 2 seq# 84900 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84900 mem# 1: F:\ORA_DATA\REDO02A.LOG
Sat Jan 29 00:10:04 2011
Thread 1 advanced to log sequence 84901
Current log# 1 seq# 84901 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84901 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 cannot allocate new log, sequence 84902
Checkpoint not complete
Current log# 1 seq# 84901 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84901 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 advanced to log sequence 84902
Current log# 3 seq# 84902 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84902 mem# 1: F:\ORA_DATA\REDO03A.LOG
Thread 1 cannot allocate new log, sequence 84903
Checkpoint not complete
Current log# 3 seq# 84902 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84902 mem# 1: F:\ORA_DATA\REDO03A.LOG
Sat Jan 29 00:10:18 2011
Thread 1 advanced to log sequence 84903
Current log# 2 seq# 84903 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84903 mem# 1: F:\ORA_DATA\REDO02A.LOG
Thread 1 advanced to log sequence 84904
Current log# 1 seq# 84904 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84904 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 cannot allocate new log, sequence 84905
Checkpoint not complete
Current log# 1 seq# 84904 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84904 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 advanced to log sequence 84905
Current log# 3 seq# 84905 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84905 mem# 1: F:\ORA_DATA\REDO03A.LOG

Similar Messages

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

Archives are not being able to ship to standby

Dear Friends
i have installed oracle 9i on linux 4
i have made primary and standby behavior
both database's listeners are up
primary database is running in read right while standby is in mounted state.
both servers are pinging to each other's services (tnsping primary& standby)
but archives are not shipping to standby
please help me out

What is the error showing in the log file
Or post it here
just asking,did run the command at standby
alter database recover managed standby database disconnect from session;
Shaan
Edited by: Shaan_dmp on Mar 11, 2010 7:54 PM

Archives are not applying on 2nd standby

Hi,
i have one primary and two standby DBs in different servers.
archives are applying to one standby only,not appling to another.
what are the things i need to check? please guide me

Hi,
archives are not applying that are received from primary
on standby DB:
SQL>select SEQUENCE#,APPLIED from v$archived_log;
UENCE# APP
393 NO
387 NO
388 NO
389 NO
on standby ihaven't seen MRP process,but i have given sql comd like
SQL> alter database recover managed standby database disconnect from session;
on standby it's displying
SQL> select PROCESS,STATUS from v$managed_standby;
PROCESS STATUS
ARCH CLOSING
ARCH CLOSING
RFS WRITING
RFS RECEIVING
RFS RECEIVING
here there is no MRP process,plz tell me where is the mistake.

EMERGENCY: List of files in Recovery Area not managed by the database

Hi,
this is an emergency request....
I have this data guard set up. And i accidently dropped online redo logs, standby logs and the archive log except the current online redolog.
i actually ran to cleanup the whole directory which included the controlfile and the datafiles (was on the wrong location on ASM)
but the controlfile and the datafiles did not get deleted. i can still see them on the ASM.
and now when i am trying to restore the archive logs, but i keep getting error as shown below...
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
so when i did the below i was getting error as:
RMAN> CATALOG RECOVERY AREA;
using target database control file instead of recovery catalog
searching for all files in the recovery area
no files found to be unknown to the database
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
number of files not managed by recovery area is 82, totaling 168.10GB
But i do see those data files that RMAN is complaining as shown above in the ASM.
I HOPE I DID NOT MESS UP THE CONTROLFILE and the DATFILES
CAN SOMEONE HELP ME FIX THIS MISTAKE THAT I DID.
Right now the data guard is running fine, the logs are getting shipped from primary and the getting applied at the DG.
And i am able to see all the redo logs got deleted.
But not sure how the deleted redo logs got created in the ASM (i did not create them manually)
Thanks.
Philip.
Edited by: user8898644 on May 5, 2010 8:52 AM
Edited by: user8898644 on May 5, 2010 9:16 AM
Edited by: user8898644 on May 5, 2010 11:43 AM

Yes this happened on the standby database.
I had to restore the archive logs because i deleted all the archive logs which got shipped from the primary.
I did re-create the standby logs. But when i checked back the redo logs that i deleted came back again.
I have no idea how they can back again. is it a feature of ASM where a mirrored copy of the files are stored on ASM and they re-create them when accidently dropped.
Can you help me understand how the redologs got created again automatically.
Right now the data guard is running fine but i do see the error
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
and when i do the following
RMAN> catalog recovery area;
i do see errors as below...
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/onlinelog/group_2.372.718194833
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/system.596.715610261
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/undotbs1.571.715603525
number of files not managed by recovery area is 82, totaling 168.10GB
we do have the db_create_file_dest and db_recovery_file_dest pointing to the same location as +DATA
How do i fix the above error?
Thanks in advance.

Archive log not shipped to standby.

Dear Experts,
We have are using oracle 10.2.0.4.0 on AIX.
And we have configured physical standby database which was working fine till date.
suddenly i found that the MRP process is waiting for gap.
i have all the archive logs on the primary system and all the logs are getting shipped to standby database expect one file.
/oracle/PRD/saparch/PRDarch1_46811_755493268.dbf only this file is not getting shipped to standby database....due to which the standby is waiting for this log.
log applied till 46810
other logs are getting shipped.
However i tried to manually copy this log to standby but it didnt start applying this log.
and i heard that if i copy the log file manually then i need to register it...please let me know how to register it if it is the correct method.
Please help to overcome this issue....
Thanks,
Shankar.
Edited by: Shankar Viji on Jun 19, 2012 10:34 PM

Shankar Viji wrote:
Dear Mesberg,
Is there any way to over come this bug.
Bug 6851669 - ORA-308 / ORA-27037 from Dataguard GAP resolution [ID 6851669.8]
if not i am planing to take offline backup of my primary and restore it on standby and start the DR again.
Please suggest is that the correct way to do it r not.
Thanks,
Shankar.
Edited by: Shankar Viji on Jun 21, 2012 10:51 PMHi,
It looks for me that archive unable to read, it may be because of any header verification or corrupted blocks.
Now do you have backup of archives ?
If so restore it and retry again.
If not, I suggest you to go with incremental scn for standby instead of recreation whole DR.
Check this link http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/

Export and Import are not supported on 10g databases for users logged

Hi
I having the below written error, when i want to export or import my database. I having Standalone system using windows xp.
Role Error - Export and Import are not supported on 10g databases for users logged in with the SYSDBA role. Logout and login using a different role before trying again.

Actually i ma new to EM...
When I want to Import any thing He is asking abt the HOST CREDENTIALS
I can't undrstatnd wht he is asking????
Host Credentials
* Username
* Password
          Save as Preferred Credential
It Genrate the below error
Error - ERROR: Wrong password for user

Archived log file are not shifted to standby side and applied

Hi Guru's,
DB
My OS Version:Windows Server 2003
DB Version:11.2.0.1.0
I am trying to create Physical Standby DB on my test machine after setting all the parameters and start standby db in mount mode when i do the verification of archived log files that need to be shift from pri site to standby site i am getting:
no rows selected.
I am following the below mentioned doc for reference
http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#i63561
Can anyone from your side can help me to sort out this problem.
Thanks in advance

vk82 wrote:
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
39
SQL> select process,status,sequence# from v$managed_standby;
PROCESS STATUS SEQUENCE#
ARCH CLOSING 38
ARCH CLOSING 36
ARCH CONNECTED 0
ARCH CLOSING 37
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
39
Yes the max sequence generated on primary is same as the max sequence applied on standby.
And what is MRP and why it is important can you please let me know abt thisWhenever you created standby database, Make a habit of tail to alert log file to monitor whats happening on the standby database, Besides MRP is an Media Recovery Process , which applies archies/redo on standby database.
MRP can apply based on the redo transport, If you are using real-time apply then Redo will be writtened to the standby redo log files at the same time recovery will be performed by MRP process, If you are not using Real-Time apply then whenever a archive generated on primary that archive will be transported to the standby and applied on the standby database.
It is recommended to use Realtime apply, so that you can avoid much data lost.
However you are in 11gR2, You can use below query to monitor
SQL> SELECT * FROM V$STANDBY_EVENT_HISTOGRAM WHERE NAME = 'apply lag' AND COUNT > 0;
NAME             TIME UNIT                  COUNT LAST_TIME_UPDATED
apply lag           0 seconds                 431 08/05/2012 22:14:21
apply lag           1 seconds                   7 08/05/2012 22:13:31
SQL>Edited by: CKPT on Nov 6, 2012 6:49 PM

Archive logs are not transferred to STDBY database

Hi,
I have create a STDBY database (I am running the release 9.2.0.7.0).
I see that the archivelogs are not correctly transferred into STDBY server.
From Primary alert log, I see the following error:
ARC1: Evaluating archive log 1 thread 1 sequence 16734
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
ARC1: Beginning to archive log 1 thread 1 sequence 16734
Creating archive destination LOG_ARCHIVE_DEST_1: '/backup/archivelogs/log1_16734.arc'
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 16734 host STDBY_PROD
ARC1: Completed archiving log 1 thread 1 sequence 16734
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 14:54:42 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 14:54:42 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
ARC0: Begin FAL archive (thread 1 sequence 16483 destination STDBY_PROD)
Creating archive destination LOG_ARCHIVE_DEST_2: 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
LGWR: I/O error 3114 archiving log 2 to 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_lgwr_5265.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 15:10:08 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
I see that both archiving destinations are VALID:
SQL> select dest_id, dest_name, status from v$archive_dest_status where status != 'INACTIVE';
DEST_ID ---------- DEST_NAME -------------------------------------------------------------------------------- STATUS
1 LOG_ARCHIVE_DEST_1 VALID
2 LOG_ARCHIVE_DEST_2 VALID
SQL>
TNSPING works properly in both directions, e.g. from PROD -> STDBY:
$tnsping STDBY_PROD
TNS Ping Utility for Linux: Version 9.2.0.7.0 - Production on 17-NOV-2011 16:56:40
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:
/mnt/orclEBS/oracle/proddb/9.2.0/network/admin/PROD_ebslive/sqlnet_ifile.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp) (HOST=EBSSTDBY) (PORT=1521)) (CONNECT_DATA=(SID=PROD)))
OK (10 msec)
Please help me to solve this issue.
Thank you.

A few notes :
Troubleshooting Tips For Dataguard Switchover (9i and 10gR1) [ID 298986.1]
Although it is about Switchover, it does mandate a password file exclusive. If the switchover requires the password file, shouldn't ARCH shipping require it ?
Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
also covers 9i with specific mentions of 9i differences from 10g. Passwordfile is not mentioned as different in 9i from 10g.
Data Guard 9i - Net8 Configuration for a 2-node database environment. [ID 175122.1
has log_archive_dest_2='SERVICE=NODE2STDBY.ACME.COM' so it connects to the service
*However* the document "Introduction to Oracle 9i Data Guard Manager" from
Data Guard 9i Introduction to Data Guard Manager GUI [ID 150217.1]
page 59 has this : "The creation process will attempt to create a remote login password file for the standby database to
enable remote connections to the database. (Note: A remote login password file is not necessary for
Data Guard operation; it is only needed to allow remote connections to the database from clients,
such as other Enterprise Manager tools.)"
Similarly the section "3.2.6 Set Initialization Parameters on a Physical Standby Database"
in the 9i DataGuard manual at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm#62941
only has
remote_archive_enable=TRUE
(this is an instance parameter)
Similarly the section "5.8.2.1 Primary Database Initialization Parameters"
at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/log_transport.htm#1067609
explains
The last parameter, REMOTE_ARCHIVE_ENABLE=SEND, allows the primary database to send redo data to the standby database, but prevents the primary database from receiving redo data from another system.
with REMOTE_ARCHIVE_ENABLE=RECEIVE on the Standby
to Receive and archive the incoming redo data from the primary database, but only while the database is running in the standby role
So, I guess that REMOTE_ARCHIVE_ENABLE is the important one. Not REMOTE_LOGIN_PASSWORDFILE.
In 9i : http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1174.htm#1023087
In 10g it is deprecated : http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams176.htm#sthref541 so that LOG_ARCHIVE_CONFIG is used.
(and no longer appears in the 11.2 Reference)
Hemant K Chitale

Archive logs not applied on standby!!

Hi Guys,
I am trying to set up physical standby on windows 2003 server. I am using oracle 10.2.0.4.0. I get the following error in my alert file on standby
Failed to request gap sequence
Following is the results of some queries :
SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MR(fg) WAIT_FOR_GAP 1 10004 0 0
SQL> select * from v$archive_gap;
no rows selected
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
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
ARC0: Becoming the 'no FAL' ARCH
MESSAGE
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
FAL[client]: All defined FAL servers have been attempted.
MESSAGE
MRP0: Background Media Recovery cancelled with status 16037
MRP0: Background Media Recovery process shutdown
Managed Standby Recovery Canceled
Media Recovery Start: Managed Standby Recovery
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
FAL[client]: All defined FAL servers have been attempted.
SQL>SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
where applied= 'YES'
no rows selected
##Modification to primary##
*.log_archive_dest_2='SERVICE=STANDBY'
*.fal_client='STUTEST'
*.fal_server='STUSTANDBY'
*.log_archive_config='DG_CONFIG=(STUTEST,STUSTANDBY)'
##Modification to standby##
*.db_unique_name='STANDBY'
*.log_archive_dest_2='SERVICE=STANDBY'
*.log_archive_dest_state_2='ENABLE'
*.Fal_server=STUTEST
*.Fal_client=STUSTANDBY
*.db_file_name_convert='H:\ORACLE\ORADATA\STUTEST\','I:\ORACLE\ORADATA\STUTEST\s_'
*.log_file_name_convert='D:\oracle\oradata\STUTEST\','D:\oracle\oradata\STUTEST\s_'
Nore: I used RMAN to create the standby database. The following are brief steps
Below are the steps to accomplish the task :
Step 1: Backup the database that includes backup of datafiles, archivelogs and controlfile for standby
backup current controlfile for standby;
Step 2: Move the backups to the standby server and restore control file from backup
Step 3: Make changes in the parameter files of both primary and standby database
Step 4: Do the restore and recover on standby database
Step 5: Put the standby database in recover managed mode
Thanks for help guys!!!!!

Hi sb92075
Alert log on standby
alter database mount standby database
Mon Jul 26 14:10:40 2010
Setting recovery target incarnation to 1
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=21, OS id=6708
ARC1 started with pid=22, OS id=3892
ARC2 started with pid=23, OS id=4380
ARC3 started with pid=24, OS id=4896
ARC4 started with pid=25, OS id=6348
ARC5 started with pid=26, OS id=5868
ARC6 started with pid=27, OS id=6904
ARC7 started with pid=28, OS id=4428
ARC8 started with pid=29, OS id=5008
Mon Jul 26 14:10:40 2010
ARC0: Archival started
ARC9 started with pid=30, OS id=5804
Mon Jul 26 14:10:41 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 Jul 26 14:10:41 2010
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
Mon Jul 26 14:10:41 2010
Successful mount of redo thread 1, with mount id 2477113436
Mon Jul 26 14:10:41 2010
Physical Standby Database mounted.
Mon Jul 26 14:10:42 2010
ARC1: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon Jul 26 14:10:42 2010
Errors in file c:\oracle\admin\stustandby\udump\stustandby_ora_6604.trc:
Mon Jul 26 14:11:41 2010
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=3696
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Mon Jul 26 14:11:46 2010
Waiting for all non-current ORLs to be archived...
Media Recovery Waiting for thread 1 sequence 10004
Fetching gap sequence in thread 1, gap sequence 10004-10017
Mon Jul 26 14:11:47 2010
Completed: alter database recover managed standby database disconnect from session
Mon Jul 26 14:12:16 2010
*FAL[client]: Failed to request gap sequence*
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
*FAL[client]: All defined FAL servers have been attempted.*
Alert log on primary
Mon Jul 26 13:50:11 2010
db_recovery_file_dest_size of 40960 MB is 49.73% 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 Jul 26 13:50:12 2010
Successfully onlined Undo Tablespace 19.
Mon Jul 26 13:50:12 2010
SMON: enabling tx recovery
Mon Jul 26 13:50:12 2010
Database Characterset is WE8ISO8859P1
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=38, OS id=3776
Mon Jul 26 13:50:14 2010
Completed: ALTER DATABASE OPEN
Mon Jul 26 13:51:10 2010
Shutting down archive processes
Mon Jul 26 13:51:15 2010
ARCH shutting down
ARCa: Archival stopped
Mon Jul 26 14:11:47 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
*FAL[server]: DGID from FAL client not in Data Guard configuration*
*FAL[server]: FAL request for destination STUSTANDBY was:*
GAP - thread 1 sequence 10004-10017
DBID 2422302575 branch 670594799
Mon Jul 26 15:04:10 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
*FAL[server]: DGID from FAL client not in Data Guard configuration*
*FAL[server]: FAL request for destination STUSTANDBY was:*
GAP - thread 1 sequence 10004-10017 DBID 2422302575 branch 670594799

All logs received but not applied | Physical Standby Database

All,
Need your help....
We have physical standby database setup as below
Primary : 2 node RAC
Stdby : Standalone physical standby database.
When I verify the stdby database status, I could see all the logs are received from primary but still not applied many.. Could any one please help me what is the issue and how to resolve it ...?
Primary :
=====
SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1 2 3 4 ;
Thread Last Sequence Generated
1 8073
1 8073
2 4521
2 4521
stdby:
====
SQL> SELECT ARCH.THREAD# "Thread",
2 ARCH.SEQUENCE# "Last Sequence Received",
3 APPL.SEQUENCE# "Last Sequence Applied",
4 (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
5 FROM
6 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
7 (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
8 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
(SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
9 10 WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
Thread Last Sequence Received Last Sequence Applied Difference
1 8073 8055 18
2 4521 4510 11
--Below are tailed messages from standby alert log:
Fri Nov 04 10:45:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:50:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 10:50:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 10:55:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:00:15 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:00:15 2011
Archiver process freed from errors. No longer stopped
Fri Nov 04 11:05:16 2011
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance BWFCCSTD - Archival Error
ORA-16014: log 6 sequence# 8058 not archived, no available destinations
ORA-00312: online log 6 thread 1: '+ASM_DATA01/bwfccstd/onlinelog/group_6.418.766235259'
ORA-00312: online log 6 thread 1: '+ASM_FRA01/bwfccstd/onlinelog/group_6.307.766235263'
Fri Nov 04 11:05:16 2011
Archiver process freed from errors. No longer stopped

Primary:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +ASM_FRA01
Oldest online log sequence 8073
Next log sequence to archive 8074
Current log sequence 8074
SQL>
Stdby:
=====
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination ?/dbs/arch
Oldest online log sequence 8074
Next log sequence to archive 0
Current log sequence 8074
Enough space is available :
=================
SQL> set lines 180 pages 50000;
SQL> set lines 100
col name format a60
select name
, floor(space_limit / 1024 / 1024) "Size MB"
, ceil(space_used / 1024 / 1024) "Used MB"
from v$recovery_file_dest
order by nameSQL> SQL> 2 3 4 5 ;
NAME Size MB Used MB
+ASM_FRA01 70000 531
Edited by: 889828 on 2011/11/04 2:26 AM

Log Files are not shipping to standby.

Hi,
I am getting the below error. My log files are not getting shipped from primary to standby. Below is the error msg from alert log file. Help needed.
Thu Jan 10 17:27:17 2013
Error 1031 received logging on to the standby
Errors in file d:\app\sesa241915\diag\rdbms\orcl\orcl\trace\orcl_arc2_2944.trc:
ORA-01031: insufficient privileges
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
Thanks in advance.

Please find the content of trace file.
*** 2013-01-11 10:16:41.389
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:16:41.404 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:16:41.404 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:16:41.420 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:16:41.420 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:17:41.482
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:17:41.795 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:17:41.795 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:17:41.795 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:17:41.795 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:18:41.857
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:18:42.154 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:18:42.154 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:18:42.154 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:18:42.154 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:19:42.185
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:19:42.467 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:19:42.467 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:19:42.467 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:19:42.467 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:20:42.545
Redo shipping client performing standby login
*** 2013-01-11 10:20:42.639
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:20:42.810 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:20:42.810 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:20:42.810 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:20:42.810 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:21:42.889
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:21:43.217 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:21:43.217 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:21:43.217 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:21:43.217 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:22:43.295
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:22:43.639 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:22:43.639 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:22:43.639 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:22:43.639 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:23:43.701
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:23:44.045 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:23:44.045 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:23:44.045 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:23:44.045 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:24:44.123
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:24:44.451 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:24:44.451 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:24:44.451 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:24:44.451 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:25:44.514
Redo shipping client performing standby login
*** 2013-01-11 10:25:44.639
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:25:44.951 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:25:44.951 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:25:44.951 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:25:44.951 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:26:45.014
Redo shipping client performing standby login
*** 2013-01-11 10:26:45.170
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:26:45.373 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:26:45.373 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:26:45.389 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:26:45.389 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:27:45.435
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
*** 2013-01-11 10:27:45.779
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:27:45.951 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:27:45.951 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:27:45.967 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:27:45.967 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:28:46.029
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
*** 2013-01-11 10:28:46.326
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:28:46.435 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:28:46.435 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:28:46.435 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:28:46.435 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:29:46.482
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:29:46.889 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:29:46.889 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:29:46.904
*** 2013-01-11 10:29:46.904 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:29:46.904 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
Redo shipping client performing standby login
*** 2013-01-11 10:30:47.140
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:30:47.297 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:30:47.297 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:30:47.312 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:30:47.312 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:31:47.378
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:31:47.691 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:31:47.691 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:31:47.691 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:31:47.691 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:32:47.772
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:32:48.069 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:32:48.069 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:32:48.069 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:32:48.069 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
*** 2013-01-11 10:33:48.135
Redo shipping client performing standby login
*** 2013-01-11 10:34:09.261
OCIServerAttach failed -1
.. Detailed OCI error val is 12170 and errmsg is 'ORA-12170: TNS:Connect timeout occurred
*** 2013-01-11 10:34:45.873
OCIServerAttach failed -1
.. Detailed OCI error val is 12170 and errmsg is 'ORA-12170: TNS:Connect timeout occurred
*** 2013-01-11 10:35:06.984
OCIServerAttach failed -1
.. Detailed OCI error val is 12170 and errmsg is 'ORA-12170: TNS:Connect timeout occurred
*** 2013-01-11 10:35:06.984 4132 krsh.c
Error 12170 received logging on to the standby
*** 2013-01-11 10:35:06.984 869 krsu.c
Error 12170 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 12170 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-12170: TNS:Connect timeout occurred
*** 2013-01-11 10:35:06.999 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 12170.
*** 2013-01-11 10:35:06.999 2747 krsi.c
krsi_dst_fail: dest:2 err:12170 force:0 blast:1
*** 2013-01-11 10:36:07.063
Redo shipping client performing standby login
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1017 and errmsg is 'ORA-01017: invalid username/password; logon denied
OCISessionBegin failed. Error -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2013-01-11 10:36:07.267 4132 krsh.c
Error 1031 received logging on to the standby
*** 2013-01-11 10:36:07.267 869 krsu.c
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl'
ORA-01031: insufficient privileges
*** 2013-01-11 10:36:07.267 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'orcl'. Error is 1031.
*** 2013-01-11 10:36:07.267 2747 krsi.c
krsi_dst_fail: dest:2 err:1031 force:0 blast:1
2. Please find the query results.
From Primary:
SQL> set lines 200
SQL> set numwidth 15
SQL> column ID format 99
SQL> column "SRLs" format 99
SQL> column active format 99
SQL> col type format a4
SQL> select ds.dest_id id
2 , ad.status
3 , ds.database_mode db_mode
4 , ad.archiver type
5 , ds.recovery_mode
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
11 , v$archive_dest ad
12 where ds.dest_id = ad.dest_id
13 and ad.status != 'INACTIVE'
14 order by
15 ds.dest_id
16 /
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 72
2 ERROR UNKNOWN LGWR IDLE MAXIMUM PERFORMANCE 0 0 0
From Standby:
SQL> set lines 200
SQL> set numwidth 15
SQL> column ID format 99
SQL> column "SRLs" format 99
SQL> column active format 99
SQL> col type format a4
SQL> select ds.dest_id id
2 , ad.status
3 , ds.database_mode db_mode
4 , ad.archiver type
5 , ds.recovery_mode
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
11 , v$archive_dest ad
12 where ds.dest_id = ad.dest_id
13 and ad.status != 'INACTIVE'
14 order by
15 ds.dest_id
16 /
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 72
2 ERROR UNKNOWN LGWR IDLE MAXIMUM PERFORMANCE 0 0 0
Regards
Srinivasan R

Archive logs not applied on logical database.

I have 10.2.04 oracle logical dataguard on windows:
The logs are trasported smoothly from primary to stanby;
But they are not applied to the logical standby;
There are no GAPS.
This is the message i got from DG broker wehn i ran verify configuration
Initializing
Connected to instance I-AG1101:tito
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
hclistg: ASYNC
hclidg: ASYNC
Checking standby redo log files.....OK
Checking Data Guard status
hclistg : Normal
hclidg : Normal
Checking Inconsistent Properties
Checking agent status
hclistg ... OK
hclidg ... WARNING: No credentials available for target. I-SAG1151
Attempting agent ping ... OK
Switching log file 420.Done
Checking applied log on hclidg.......WARNING:
Timed out after 60 seconds waiting for log to be applied.
Processing completed.
This is the results of query: SELECT SEQUENCE#, FIRST_TIME, APPLIED
FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;
SEQUENCE#|FIRST_TIME|APPLIED
391|3/31/2010 1:08:27 PM|CURRENT
392|3/31/2010 3:10:19 PM|NO
393|3/31/2010 3:47:05 PM|NO
394|3/31/2010 3:47:13 PM|NO
395|3/31/2010 3:47:40 PM|NO
396|3/31/2010 3:47:46 PM|NO
397|3/31/2010 3:50:14 PM|NO
398|3/31/2010 3:50:20 PM|NO
399|3/31/2010 3:54:01 PM|NO
400|3/31/2010 3:54:36 PM|NO
401|3/31/2010 3:54:43 PM|NO
402|3/31/2010 3:56:24 PM|NO
403|3/31/2010 3:56:30 PM|NO
404|3/31/2010 4:00:46 PM|NO
405|3/31/2010 4:34:03 PM|NO
406|3/31/2010 4:35:31 PM|NO
407|3/31/2010 5:38:57 PM|NO
408|4/1/2010 7:30:25 AM|NO
409|4/1/2010 11:45:23 AM|NO
410|4/1/2010 11:47:06 AM|NO
411|4/1/2010 2:26:25 PM|NO
412|4/1/2010 2:26:43 PM|NO
413|4/1/2010 2:26:44 PM|NO
414|4/1/2010 2:28:13 PM|NO
415|4/1/2010 5:08:12 PM|NO
416|4/1/2010 5:08:19 PM|NO
417|4/1/2010 5:08:52 PM|NO
418|4/2/2010 10:31:19 AM|NO
419|4/2/2010 10:35:06 AM|NO
420|4/2/2010 11:24:27 AM|NO
Please help,,,

i am getting this error when i run alter database mount standby database
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 1610612736 bytes
Fixed Size 1299288 bytes
Variable Size 545262760 bytes
Database Buffers 1056964608 bytes
Redo Buffers 7086080 bytes
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01665: control file is not a standby control file
I configured my logical DG using Grid control

How to monitor the successful archive log shipment to the standby database

Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.

watson2011 wrote:
Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.You can troubleshoot standby by views as
v$managed_standby (standby)
v$dataguard_status
v$dataguard_stats
Some of the new views are introduced from 11g, check below link too
http://docs.oracle.com/cd/B28359_01/server.111/b28294/views.htm#i79129

Logs not applying on Standby Database

I am afraid I am back.
I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid=29, OS id=23272
MRP0: Background Managed Standby Recovery process started (SAPDS)
started logmerger process
Fri Jun 29 15:03:45 2012
Managed Standby Recovery not using Real Time Apply
Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
Rereading datafile 2 header failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
Recovery Slave PR00 previously exited with exception 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
MRP0: Background Media Recovery process shutdown (SAPDS)
Completed: alter database recover managed standby database disconnect from session
My question therefore is how can I get out of this and get my logs to apply on standby?

Hello again;
Do you think if I tried to repeat the duplicate?
Yes I think you should do this.
Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
I always cleanup the standby before trying another dup
OVERVIEW
Step 1 - Password file fro standby - Copy from primary and rename
Step 2 - Directory Structure on the remote server - Make sure noting is missing
Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
Step 6 - Initialization Parameter File for the Auxiliary Instance
Step 7 - Set SID for Auxiliary Instance
Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
Step 10 - Start RMAN and run the DUPLICATE Command
SID_LIST_LISTENER Example from mine
SID_LIST_LISTENER =
   (SID_LIST =
       (SID_DESC =
       (SID_NAME = PLSExtProc)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (PROGRAM = extproc)
       (SID_DESC =
       (global_dbname = CLONE.hostname)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (sid_name = CLONE)
Prevent Timeouts
Add these to both servers
To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120
To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
RMAN
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
Connect should return something like this
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
INIT Extras
To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
Best Regards
mseberg
Edited by: mseberg on Jun 29, 2012 11:12 AM

Archives are not transorting to standby database

Similar Messages

Maybe you are looking for