Archive log gap is created is standby when ever audit trail is set to DB

Hi
I am a new dba. I am facing a problem at production server that whenever audit_trail parameter is set to db , archive log gap is created at the standby site.
My database version is 10.2.0.4
Os is windows 2003 R2
Audit_trail parameter is set to db only in primary site, after setting the parameter as db when I bounced the database and switched the logfile , archive log gap is created in the standby..I am using LGWR mode of log transport.
Is there any relation beteen audit_trail and log transport ?
Please note that my archive log location of both the sites has sufficient disk space and the drive is working fine.Also my primary and standby is in WAN.
Please help me in this.Any help will be highly appreciated.
Here a trace file which may be helpful to give any opinion.
Dump file d:\oracle\admin\sbiofac\bdump\sbiofac_lns1_6480.trc
Tue Jun 05 13:46:02 2012
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:16504M/18420M, Ph+PgF:41103M/45775M, VA:311M/2047M
Instance name: sbiofac
Redo thread mounted by this instance: 1
Oracle process number: 21
Windows thread id: 6480, image: ORACLE.EXE (LNS1)
*** SERVICE NAME:() 2012-06-05 13:46:02.703
*** SESSION ID:(534.1) 2012-06-05 13:46:02.703
*** 2012-06-05 13:46:02.703 58902 kcrr.c
LNS1: initializing for LGWR communication
LNS1: connecting to KSR channel
Success
LNS1: subscribing to KSR channel
Success
*** 2012-06-05 13:46:02.750 58955 kcrr.c
LNS1: initialized successfully ASYNC=1
Destination is specified with ASYNC=61440
*** 2012-06-05 13:46:02.875 73045 kcrr.c
Sending online log thread 1 seq 2217 [logfile 1] to standby
Redo shipping client performing standby login
*** 2012-06-05 13:46:03.656 66535 kcrr.c
Logged on to standby successfully
Client logon and security negotiation successful!
Archiving to destination sbiofacdr ASYNC blocks=20480
Allocate ASYNC blocks: Previous blocks=0 New blocks=20480
Log file opened [logno 1]
*** 2012-06-05 13:46:44.046
Error 272 writing standby archive log file at host 'sbiofacdr'
ORA-00272: error writing archive log
*** 2012-06-05 13:46:44.078 62692 kcrr.c
LGWR: I/O error 272 archiving log 1 to 'sbiofacdr'
*** 2012-06-05 13:46:44.078 60970 kcrr.c
kcrrfail: dest:2 err:272 force:0 blast:1
*** 2012-06-05 13:47:37.031
*** 2012-06-05 13:47:37.031 73045 kcrr.c
Sending online log thread 1 seq 2218 [logfile 2] to standby
*** 2012-06-05 13:47:37.046 73221 kcrr.c
Shutting down [due to no more ASYNC destination]
Redo Push Server: Freeing ASYNC PGA buffer
LNS1: Doing a channel reset for next time around...

OK
Great details thanks!!
Are The SDU/TDU settings are configured in the Oracle Net files on both primary and standby ? I will see if I have an example.
The parameters appear fine.
There was an Oracle document 386417.1 on this, I have not double checked if its still available. ( CHECK - Oracle 9 but worth a galance )
Will Check and post here.
I have these listed too. ( Will check all three and see if they still exist )
When to modify, when not to modify the Session data unit (SDU) [ID 99715.1] ( CHECK - still there but very old )
SQL*Net Packet Sizes (SDU & TDU Parameters) [ID 44694.1] ( CHECK - Best by far WOULD REVIEW FIRST )
Any chance your firewall limit the Packet size?
Best Regards
mseberg
Edited by: mseberg on Jun 6, 2012 12:36 PM
Edited by: mseberg on Jun 6, 2012 12:43 PM
Additional document
The relation between MTU (Maximum Transmission Unit) and SDU (Session Data Unit) [ID 274483.1]
Edited by: mseberg on Jun 6, 2012 12:50 PM
Still later
Not sure if this helps but I played around will this on Oracle 11 a little, here that example:
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = yourdomain.com)(PORT = 1521))
SID_LIST_LISTENER = (SID_LIST =(SID_DESC =(SID_NAME = STANDBY)
                      (ORACLE_HOME = /u01/app/oracle/product/11.2.0)
                      (SDU=32767)
                      (GLOBAL_DBNAME = STANDBY_DGMGRL.yourdomain.com)))
ADR_BASE_LISTENER = /u01/app/oracle
INBOUND_CONNECT_TIMEOUT_LISTENER=120Edited by: mseberg on Jun 6, 2012 12:57 PM
Also of interest
Redo is transporting in 10gR2 versions.
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-dataguardnetworkbestpr-134557.pdf
Edited by: mseberg on Jun 6, 2012 1:11 PM

Similar Messages

Physycal Standby archive log gap....

Archive log gap caused... The reason being before the logs can be shipped to standby location where deleted by rman backup... So restored the archives on primary database site back again... These old logs from the gap are not getting shipped to the standby site, but the new ones generated currently are getting shipped.
Can some one help what action do I have to take to resolve the gap? And how to know what's causing and not letting this shipping happen?
Or shall I manually ship these gap archive logs to the standby site?

1) Yep running 9i.. But still its not shipping...Are FAL_CLIENT & FAL_SERVER parameters are defined at standby level?
If not, define them at standby level. Those parameter will help to get missing (gap) archives from primary database.
2) If so shipped manually do have to register the archive logs? Just copy from primary to standby and don't need to register any gap, that was in 8i and when there was no background process MRP (media recovery process). If the standby database is in auto media recovery, then, it will automatically applies all the archived logs.
Jaffar

Archive Log Gap between Disaster recovery server & Production Server

Hi
Can anybody provide me the script to find out the archive log missing on Production Server means that archive log backed up & deleted from the production server & rest of the Archive logs has been shipped on to the DR server. Means it will shot the gap between production server & DR server until that log which has been deleted from the production server , but next logs has been shipped to the DR server. But rest of the logs only be applied when delete log be restored on the production server & shipped on the DR server.
thanks.
Regards
Ravi Kant Arya

Ravi,
The question is how are you getting the archive logs shipped over to your standby database? If you are doing it via FTP or scripts, then you may want to look at configuring DataGuard to do it for you. Look at "Setting Up Oracle Dataguard for SAP" at:
http://www.oracle.com/us/solutions/sap/wp-ora4sap-dataguard11g-303811.pdf
Good Luck.
Mike Kennedy

Archive log shipping error in Logical standby database

Hi,
We have Primay and logical database configuration both in RAC in Production. both database are in 10.2.0.4.
Everyday we having issue of some archivelog not transfered to logical server around 2AM. I am having good exposure in Logical/Log minor/Goldgendate and can say fal server/client server configuration is correct.
Can you guys please give some input of what can cause this.
Yes we take RMAN backup of both database around 1:30 using control file instead of recovery catalog and I doubt this put lock on control file and cause this issue.
I would be glad of you could help me out in this.
Thanks a lot!
Pradeep
Below is the configuration of archive/fal on both database.
PIP1REP2 is logical database(instance 2) where apply process is running/configured.
Primary server configuration on (PIP11) (same are on other instances).
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP2
fal_server string PIP11
SQL> sho parameter archive
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=+ARCH01
log_archive_dest_2 string SERVICE=pip1rep2 lgwr async
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string ENABLE
llog_archive_local_first boolean TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
Logical server configuration
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP
fal_server string pip11, pip12, pip13, pip14, pi
p15
SQL> sho parameter archive
NAME TYPE VALUE
alog_archive_dest_1 string LOCATION=+ARCH01/PIP1REP valid
for=(onlinelogfiles, all_rol
es) db_unique_name=pip1rep
log_archive_dest_2 string LOCATION=+ARCH01/PIP1REP/ARCH_
DEST2_STANDBY_LOGS VALID_FOR=(
STANDBY_LOGFILES,STANDBY_ROLE)
db_unique_name=pip1rep
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string enable
log_archive_local_first boolean TRUE
log_archive_max_processes integer 20
log_archive_min_succeed_dest integer 1
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string +ARCH01

Do you think creating recovery catalog will resolve it?
Yes, I do. (But I do not know for sure)
If it helps when I got to this part I decided to backup either the Primary or the Standby, but not both.
I decided Primary only and documented how to recreate my standby without downtime.
I hope this helps.
regards.

How to set a user status (complete) when ever system status is set complete

Experts,
We have configured status profile and few user status (say open, pre-release, complete) and assigned the status profile to the item category(zxxx).
The problem we have is if we have a service order that is created with the item (item category zxxx) -- Say the header status is open and the item status is pre-release. Now end user comes and sets the header status to completed - then the item status is still set pre-release. It is not changing to complete as expected.
Yes, the Item system status is set to completed but not the user status. How do I configure to set a complete user status when the header and item system status are set to completed.
Thank you
Edited by: ram on May 4, 2010 8:51 PM

I am not sure if this can be "reverse engineered" in Status profile.
But here is some hint. You can use the BAdI CRM_ORDER_STATUS mehtod AFTER_CHANGE and actually break when the Header status is changed, and set the item status as desired.

Best way of deleting archive logs on standby when backup taken on primary

Hello,
I have a 11gr2 dataguard configuration without the broker.
main problem in my particular situation arises from my FRA size on primary much more than on standby (90Gb vs 30Gb) and in some situations I'm constrained with FRA space on standby.... I'm going to align the FRAs but in the mean time....
can anyone confirm that if I have configuration as in subject with maximum performance mode and I'm not using the broker I should consider a sort of "external" way for archive log deletion on the physical standby?
In fact I'm setting on primary
- retention policy = redundancy 1
- archivelog deletion = applied on standby (without using any "backed up...." option)
Considering the standby it seems from docs that:
- retention policy always wins over deletion policy (so no archive eligible for deletion is deleted if retention is not satisfied)
- I can set on standby archivelog deletion = applied on standby (without using any "backed up...." option)
But it is not clear to me the effect of this config in case this is a standby itself and without any other cascade standby databases
The manual says this has to be met:
1) The archived redo log files have been applied to the required standby databases.
---> what does this mean in case the db is a standby.. met or not met as I have no other cascade standby dependant on this one?
2) The logs are not needed by the BACKED UP ... TIMES TO DEVICE TYPE deletion policy. If the BACKED UP policy is not set, then this condition is always met.
---> I should be ok
So the last question for standby is
- what to set retention policy to?
I have not understood if I set it to "NONE", this means no retention at all or retention for ever....
sometimes I read that there is no policy; in other examples that files will be retained forever (because no file considered as obsolete).... or at least so I understood...
I would like to have a sort of policy on standby where the archive logs can be deleted as soon as they are applied during the continuous media recovery phase...
It seems I can't find a self contained set of configurations across the dataguard....
Thanks in advance.
Gianluca

I agree with you.... It is a temporary contingency....
I already stressed the fact that sizes between sites must be quite identical...
we are going towards a production dataguard, migrating from a windows config (without it) to a Linux based config....
but this contingency made me think about these considerations regarding policies and automatic dataguard operations
I also stressed on equal size grow capability for both sites file systems, also for data tablespaces, so that for example in case of high fragmentation we have to avoid a limit situation where
1) a file system full for DR datafiles causes abend of automatic media recovery
2) this generates FRA growth in DR because archive logs are shipped but not applied any more
3) FRA goes 100% in DR and primary cannot ship any more
4) archive logs cannot be automatically deleted on primary because not already shipped
5) FRA full on primary and DB hangs....
Thanks anyway for input

Archive log can not ship to GAP logfiles to standby DB automatically

we have a non-real time standby database, which will receive the archive file from the primary database server most of the time, and will apply the logfiles only at one point of time daily.
Some times, we need to shutdown the Standby DB server for a while ( 3-4 hours).
The missed logfiles will catch up during the standby down time later.
But since last week we had an storage incident, the primary DB server stops to catch up the missed logfiles, and saw this message at the archvie trace file:
ABC: tkrsf_al_read: No mirror copies to re-read data
Current, we found the archive log gaps on the standby server, and have to manually copy those logfiles over and register them.
Saw some tips on the internet to change the parameter "log_archive_max_processes", but no help for us at all.
Here is the parameter on the Primary DB server:
log_archive_dest_2 = SERVICE=Standby_server reopen=300

which will receive the archive file from the primary database server most of the timeMost times from primary. Then remaining times? so you Copy manually and register?
Then it's dataguard not an manual standby.
Error 1034 received logging on to the standby
Errors in file /******/***arc210536.trc:
ORA-01034: ORACLE not available
FAL[server, ARC2]: FAL archive failed, see trace file.these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate ,
When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
Once you enable check what are the errors in primary alert log file.
How is your network band width speed? Is it capable to hold that much archive data?
May be it will take some time when you pause & start.
Also use LGWR in log_archive_dest_2 for real time apply after creatin standby redo logs.
So post the alert log information once you enable standby database.

Archived log missed in standby database

Hi,
OS; Windows 2003 server
Oracle: 10.2.0.4
Data Guard: Max Performance
Dataguard missed some of the archivelog files and but latest log files are applying. standby database is not in sync with primary.
SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
I queried above command and I found some files are missed in standby.
select status, type, database_mode, recovery_mode,protection_mode, srl, synchronization_status,synchronized from V$ARCHIVE_DEST_STATUS where dest_id=2;
STATUS TYPE DATABASE_MODE RECOVERY_MODE PROTECTION_MODE SRL SYNCHRONIZATION_STATUS SYN
VALID PHYSICAL MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE NO CHECK CONFIGURATION NO
Anyone can tell me how to apply those missed archive log files.
Thanks in advacne

Deccan Charger wrote:
I got below error.
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 activeYou need to essentially do the following.
1) Stop managed recovery on the standby.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;2) Resolve the archive log gap - if you have configured FAL_SERVER and FAL_CLIENT Oracle should do this when you follow step 3 below, as you've manually copied the missed logs you should be OK
3) restart managed recovery using the command shown above.
You can monitor archive log catchup using the alert.log or your original query.
Niall Litchfield
http://www.orawin.info/
Edited by: Niall Litchfield on May 4, 2010 2:29 PM
missed tag

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Delete archive log files on physical standby

I want to delete the archive log files on the phsical standby database when they were applied. The archive log files are in the flash recovery area. So i used
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
in rman.
My question:
Does rman delete the archive log files immediately when they are applied or when the disk space becomes scarce?

Hi,
They're marked as reclaimable when applied, so they're still on the disk but when the flah recovery area will become full they'll be deleted to give space to the new one, and so...
Loïc

Problem in Archive log sync with Passive Node to Standby

Hi,
I have configured Active-Passive Oracle Database using Fail Safe between Active and Passive Node. Also successfully configured Data Guard between Active Node to Standby Node.
Versions:
1. Oracle Database Version: Oracle 11g R2
2. Oracle Fail Safe: 3.4.2
3. OS: Windows Server 2008 R2
Problem:
Now after fail over the database to Passive node, to check whether the DR is functioning or not, archive logs are not transferring to Standby node. In the Passive Node aler log file error is showing:
"ORA-01031: insufficient privileges
PING[ARC2]: heartbeat failed to connect to standby órcldr´. Error is 1031
Could anyone please let me know the possible reason for this and the resolution.

Hello;
I'm thinking password file. It needs to be the same copy on all instances.
Did you copy and rename it as needed?
And you need to restart using the correct copy of the password file too.
So a Standby for example must startup on the correct copy of the password file or you will still get the error.
Best Regards
mseberg
Edited by: mseberg on Nov 14, 2012 9:46 AM

Archive logs to standby showing odd behavior.

10.2.0.2
HP 11.23
I'm monitoring the archive log transfer of files, and it appeared a little odd...as if the the files are not being applied.
So log into the system manually, and ran:
recover managed standby database cancel;
returned with recovery complete.
THen I issued:
recover managed standby database until cancel;
It asked for the files. I ran AUTO....it did it's thing, each one individually responding that
ORA-00279: change 7313758876671 generated at 04/24/2009 18:54:51 needed for
thread 1
ORA-00289: suggestion : /oraarch/swesc/peregrine_1_21380_640853326.arc
ORA-00280: change 7313758876671 for thread 1 is in sequence #21380
ORA-00278: log file '/oraarch/swesc/peregrine_1_21379_640853326.arc' no longer
needed for this recovery
Showing that it was successfully going through each archive file, applying it.
It did this until it looked for the next file that didn't exist.
This leaving the final log as 21393.
Then I issue an archive log list...
it shows 21357!
What is going ON?!

I ran archive log list on both systems to get that information.
after applying all the archive logs from the primary, the standby still showed the same sequence as it did to prior to recovery.
The recovery completed successfully, but archive log list doesn't show any change.
Meaning that before the recovery was run, it was 21357, after recovery was finished, it SHOULD have ready 23193, but it still read 21357.
Edited by: WillyB on May 6, 2009 11:07 AM

Data Guard Archive Log Latency Between Primary and Physical Standby

How can I get the time it takes (latency) for the primary instance to get an archive log over to the physical standby instance and get it "archived" and "applied". I have been looking at the V$ARCHIVED_LOG view on each side but the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY" and no timestamp. I thought the DATE datatype include data and time. Any ideas on how I can get the latency info I'm looking for?
Thanks
Steve

the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY"
and no timestamp. Did you try using TO_CHAR ? e.g.
to_char(completion_time,'dd/mm/yyyy hh24:mi:ss')

How to create uniform size archive logs?

DB version 11.2.0.3
OS solaris.
i have 6 online redo log groups.
i want that my archive logs file always create of uniform size of 50MB each?

Asad99 wrote:
DB version 11.2.0.3
OS solaris.
i have 6 online redo log groups.
i want that my archive logs file always create of uniform size of 50MB each?Why do you care about the size of an individual archivelog? What problem does that solve?
Archivelogs are simply "backup" copies of the online redologs. So in general, an archivelog will be the same size as the online redolog that it is archiving. It may happen to be be smaller in some circumstances that cause a log switch before an online redo log is full.

Archive Logs NOT APPLIED but transferred

Hi Gurus,
I have configured Primary & Standby databases in same Oracle Home. OS version is OEL 5. Database version is 10.2.0.1. I could get the archive logs in the standby site but they are not getting applied in the standby database. I don't have OLAP installed in my database version. Would this create this issue? However I attached my primary alert log details below for your reference:
Thu Aug 30 23:55:37 2012
Starting ORACLE instance (normal)
Cannot determine all dependent dynamic libraries for /proc/self/exe
Unable to find dynamic library libocr10.so in search paths
RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
LD_LIBRARY_PATH is not set!
The default library directories are /lib and /usr/lib
Unable to find dynamic library libocrb10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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.1.0.
System parameters with non-default values:
processes = 150
sga_target = 289406976
control_files = /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control01.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control02.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control03.ctl
db_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim
log_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWSTAND/onlinelog, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWPRIM/onlinelog
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(newprim,newstand)
log_archive_dest_1 = LOCATION=/home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=newprim
log_archive_dest_2 = SERVICE=newstand LGWR ASYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=newstand
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
log_archive_max_processes= 30
log_archive_format = %t_%s_%r.dbf
fal_client = newprim
fal_server = newstand
db_file_multiblock_read_count= 16
db_recovery_file_dest = /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area
db_recovery_file_dest_size= 2147483648
standby_file_management = AUTO
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=newprimXDB)
job_queue_processes = 10
background_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump
user_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump
core_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/cdump
audit_file_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/adump
db_name = newprim
db_unique_name = newprim
open_cursors = 300
pga_aggregate_target = 95420416
PMON started with pid=2, OS id=28091
PSP0 started with pid=3, OS id=28093
MMAN started with pid=4, OS id=28095
DBW0 started with pid=5, OS id=28097
LGWR started with pid=6, OS id=28100
CKPT started with pid=7, OS id=28102
SMON started with pid=8, OS id=28104
RECO started with pid=9, OS id=28106
CJQ0 started with pid=10, OS id=28108
MMON started with pid=11, OS id=28110
MMNL started with pid=12, OS id=28112
Thu Aug 30 23:55:38 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Thu Aug 30 23:55:38 2012
ALTER DATABASE MOUNT
Thu Aug 30 23:55:42 2012
Setting recovery target incarnation to 2
Thu Aug 30 23:55:43 2012
Successful mount of redo thread 1, with mount id 1090395834
Thu Aug 30 23:55:43 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Aug 30 23:55:43 2012
ALTER DATABASE OPEN
Thu Aug 30 23:55:43 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=28122
ARC1 started with pid=17, OS id=28124
ARC2 started with pid=18, OS id=28126
ARC3 started with pid=19, OS id=28128
ARC4 started with pid=20, OS id=28133
ARC5 started with pid=21, OS id=28135
ARC6 started with pid=22, OS id=28137
ARC7 started with pid=23, OS id=28139
ARC8 started with pid=24, OS id=28141
ARC9 started with pid=25, OS id=28143
ARCa started with pid=26, OS id=28145
ARCb started with pid=27, OS id=28147
ARCc started with pid=28, OS id=28149
ARCd started with pid=29, OS id=28151
ARCe started with pid=30, OS id=28153
ARCf started with pid=31, OS id=28155
ARCg started with pid=32, OS id=28157
ARCh started with pid=33, OS id=28159
ARCi started with pid=34, OS id=28161
ARCj started with pid=35, OS id=28163
ARCk started with pid=36, OS id=28165
ARCl started with pid=37, OS id=28167
ARCm started with pid=38, OS id=28169
ARCn started with pid=39, OS id=28171
ARCo started with pid=40, OS id=28173
ARCp started with pid=41, OS id=28175
ARCq started with pid=42, OS id=28177
ARCr started with pid=43, OS id=28179
ARCs started with pid=44, OS id=28181
Thu Aug 30 23:55:44 2012
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
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARCt started with pid=45, OS id=28183
LNS1 started with pid=46, OS id=28185
Thu Aug 30 23:55:48 2012
Thread 1 advanced to log sequence 68
Thu Aug 30 23:55:48 2012
ARCo: Becoming the 'no FAL' ARCH
ARCo: Becoming the 'no SRL' ARCH
Thu Aug 30 23:55:48 2012
ARCp: Becoming the heartbeat ARCH
Thu Aug 30 23:55:48 2012
Thread 1 opened at log sequence 68
Current log# 1 seq# 68 mem# 0: /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/redo01.log
Successful open of redo thread 1
Thu Aug 30 23:55:48 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Aug 30 23:55:48 2012
SMON: enabling cache recovery
Thu Aug 30 23:55:48 2012
Successfully onlined Undo Tablespace 1.
Thu Aug 30 23:55:48 2012
SMON: enabling tx recovery
Thu Aug 30 23:55:49 2012
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=47, OS id=28205
Thu Aug 30 23:55:49 2012
Error 1034 received logging on to the standby
Thu Aug 30 23:55:49 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
ORA-01034: ORACLE not available
FAL[server, ARC1]: Error 1034 creating remote archivelog file 'newstand'
FAL[server, ARC1]: FAL archive failed, see trace file.
Thu Aug 30 23:55:49 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Thu Aug 30 23:55:49 2012
ORACLE Instance newprim - Archival Error. Archiver continuing.
Thu Aug 30 23:55:49 2012
db_recovery_file_dest_size of 2048 MB is 9.77% 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.
Thu Aug 30 23:55:50 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump/newprim_ora_28120.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Thu Aug 30 23:55:50 2012
Completed: ALTER DATABASE OPEN
Thu Aug 30 23:56:33 2012
FAL[server]: Fail to queue the whole FAL gap
GAP - thread 1 sequence 1-33
DBID 1090398314 branch 792689455
Kindly, guide me please..
-Vimal.

CKPT: The trace file details are added below for your reference;
/home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning and Data Mining options
ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
System name:     Linux
Node name:     localhost.localdomain
Release:     2.6.18-8.el5PAE
Version:     #1 SMP Tue Jun 5 23:39:57 EDT 2007
Machine:     i686
Instance name: newprim
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 28124, image: [email protected] (ARC1)
*** SERVICE NAME:() 2012-08-30 23:55:48.314
*** SESSION ID:(155.1) 2012-08-30 23:55:48.314
kcrrwkx: nothing to do (start)
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
*** 2012-08-30 23:55:49.723 60679 kcrr.c
Error 1034 received logging on to the standby
Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
ORA-01034: ORACLE not available
*** 2012-08-30 23:55:49.723 58941 kcrr.c
kcrrfail: dest:2 err:1034 force:0 blast:1
kcrrwkx: unknown error:1034
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
ARCH: Connecting to console port...
kcrrwkx: nothing to do (end)
*** 2012-08-31 00:00:43.417
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:05:43.348
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:10:43.280
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:15:43.217
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:20:43.160
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:25:43.092
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:30:43.031
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:35:42.961
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:40:42.890
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:45:42.820
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:50:42.755
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:55:42.686
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:00:42.631
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:05:42.565
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:10:42.496
kcrrwkx: nothing to do (start)
Mahir: Yes I have my 4 standby redo logs!
I created the standby manually without using RMAN.
Hemant: if it asks for even first thread, then obviously it shows nothing is applied on Standby. By the way so it is not called a 'GAP', I think..!
Thanks.

Archive log gap is created is standby when ever audit trail is set to DB

Similar Messages

Maybe you are looking for