Archive log info

Hi,
I am using oracle 10g on RHEL 5. How do i know following:
1.Upto this SCN to this SCN redo data is in X archive log file.
2.A particular archive log file say name X.arc is having redo data from this SCN to this SCN.
Above i am saying for SCN, if it is possible by from - upto time then will also useful to me.
Is there any dictionary view, DBMS package by which i may get above information please.
Regrads
Nisha

I am getting following output:
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# ARC S NAME
276 7148748 7156900 YES A ORACLE/PRODUCT/10.2.0/FLASH_RECOVERY_
AREA/ORCL/LOG1_276_673265555.ARC
277 7156900 7164223 YES A ORACLE/PRODUCT/10.2.0/FLASH_RECOVERY_
AREA/ORCL/LOG1_277_673265555.ARC
Here this SCN 7156900 data is in which arc file because it is showing in both the files? And what does it mean by sequence# column?

Similar Messages

Request info on Archive log mode Best Practices

Hi,
Could anyone from their personal experience share with me the Best Practices for maintaining Archiving on any version of oracle. Please tell me
1) Whether to place archives and log files on same disks?
2) How many lgwr processes to use.
3) checkpoint frequency.
4) How to maintain speed of the server being run in archivelog mode.
5) Errors to look.
Thanks,

1. Use separate mount point for archive logs like /archv
2. Start using with 1 and check the performance.
3. This is depends upon the redo log file size. Create your redo log file such that hourly maximum 5-8 log switch will happen. Try to make it less than 5 log switch per hour.
4. Check the redo log file size.
5. Check for archive log mount point space allocation. Take the backup of archive by RMAN and deleted the backed up archive logs from the archived destination.
Regards
Asif Kabir

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

ORA-19571: archived-log recid 118360 stamp not found in control file - help

Hi
Every backup I do I am getting an error like below at the bottom :, every backup I do, it's complaaining about DIFFERENT archive log.
ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file.
I have set keep control file info to 14 days, my retention is 7 days in RMAN, so I don't know why it's complaining, below is the full log.
It seeems to be having problems with archive logs that have just been generated while it's doing the backup I think??
channel d3: specifying archive log(s) in backup set
input archive log thread=1 sequence=705 recid=124248 stamp=707103829
input archive log thread=1 sequence=706 recid=124249 stamp=707103830
input archive log thread=1 sequence=707 recid=124250 stamp=707103831
input archive log thread=1 sequence=708 recid=124251 stamp=707103831
input archive log thread=1 sequence=709 recid=124252 stamp=707103832
input archive log thread=1 sequence=710 recid=124253 stamp=707103832
input archive log thread=1 sequence=711 recid=124254 stamp=707103833
input archive log thread=1 sequence=712 recid=124255 stamp=707103833
input archive log thread=1 sequence=713 recid=124256 stamp=707103834
input archive log thread=1 sequence=714 recid=124257 stamp=707103835
input archive log thread=1 sequence=715 recid=124258 stamp=707103835
input archive log thread=1 sequence=716 recid=124259 stamp=707103836
input archive log thread=1 sequence=717 recid=124260 stamp=707103836
input archive log thread=1 sequence=718 recid=124261 stamp=707103837
input archive log thread=1 sequence=719 recid=124262 stamp=707103837
input archive log thread=1 sequence=720 recid=124263 stamp=707103838
input archive log thread=1 sequence=721 recid=124264 stamp=707103838
input archive log thread=1 sequence=722 recid=124265 stamp=707103839
input archive log thread=1 sequence=723 recid=124266 stamp=707103840
input archive log thread=1 sequence=724 recid=124267 stamp=707103840
input archive log thread=1 sequence=725 recid=124268 stamp=707103841
input archive log thread=1 sequence=726 recid=124269 stamp=707103841
RMAN-03009: failure of backup command on d3 channel at 01/01/2010 02:11:33
ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file
continuing other job steps, job failed will not be re-run
channel d6: starting compressed archive log backupset
channel d6: specifying archive log(s) in backup set
input archive log thread=1 sequence=641 recid=124034 stamp=707077994
input archive log thread=1 sequence=642 recid=124035 stamp=707077994
...

It's a rac, so shall I restart one instance at a time?? Or the whole thing? I am using an recovery catalog, so should I be connected to the recovery catalog Or control file to do a cross check backup, also when it's doing the backup do u recon it can't fing archivelog in controlfile file as it's not done a resync, should I force it to do a resync after a backup then backup the archive logs??? I really don't want to bounce the db as it's 24/7

Disabling Log_Archive_Start in Archive Log Mode

Guys,
I have a Database running in Archive Log mode.
I have a situation where in I have to do bunch of bulk updates for which I dont want any logs generated.
sO I was thinking to set the intialization parameter log_archive_start to false before I run the DML updates
ALTER SYSTEM SET log_archive_start = false
after the DML is run I will turn it back on
ALTER SYSTEM SET log_archive_start = True
Do you think if this is the right to go about or would I have to switch from Archive Log Mode to No Archive Log Mode
run the DML update and then switch back to Archive Log Mode
Any comments/suggestions/inputs woo

Hello,
I would use some other way to get a full nologing behaviour.
First, ensure your tablespace is in force logging mode.
ALTER TABLESPACE data FORCE LOGGING NOLOGGING;
ALTER TABLESPACE index FORCE LOGGING NOLOGGING;
This will ensure that you're usually logging.
Set all tables/indexes to be nologging
BEGIN
FOR vRes IN (SELECT OWNER,TABLE_NAME FROM DBA_TABLES WHERE TABLESPACE_NAME='data')
LOOP
EXECUTE IMMEDIATE 'ALTER TABLE ' || vRes.OWNER || '.' || vRes.TABLE_NAME ' NOLOGGING';
END LOOP;
END;
Do even for indexes.
From now on, when you want to do your huge amount of updates/... targetting objects in tablespaces data and index, jou just have to:
ALTER TABLESPACE data NO FORCE LOGGING;
ALTER TABLESPACE indexes NO FORCE LOGGING;
- Your DML
ALTER TABLESPACE data FORCE LOGGING;
ALTER TABLESPACE indexes FORCE LOGGING.
4 commands to disable logging for every object in the tablespace.
Beware, when in NOLOGGING mode, you won't be able to "RECOVER" any of the tables. Thiis is not crash-friendly, but you'll have no redo info generated, which is what you require.
Regards,
Yoann.

Two copies archive logs with only one defined

Hi,
On a 11g database, I have only got flash_recovery_area defined. When switched into archive log mode, I have expected only one copy of archive logs produced in the defined USE_DB_RECOVERY_FILE_DEST location, but there is another copy generated as well under $ORACLE_HOME/dbs directory. How to explain that? and how to DISABLE the second copy to be produced?
Thanks for any help
Zhuang Li
PS: more info
In spfile:
orcl.__java_pool_size=50331648
orcl.__large_pool_size=16777216
orcl.__oracle_base='/usr/oracle11g'#ORACLE_BASE set from environment
orcl.__pga_aggregate_target=1828716544
orcl.__sga_target=1056964608
orcl.__shared_io_pool_size=0
orcl.__shared_pool_size=654311424
orcl.__streams_pool_size=0
*.audit_file_dest='/usr/oracle11g/admin/orcl/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_file_record_keep_time=30
*.control_files='/db/orcl1/control0^@^@C^AC"^@^@^@^@^@^C^@^@^@^@^@^@^A^D{^S^@^@1.ctl','/db/orcl1/control02.ctl',
'/db/orcl1/control03.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='orcl'
*.db_recovery_file_dest='/usr/oracle11g/flash_recovery_area'
*.db_recovery_file_dest_size=6442450944
*.diagnostic_dest='/usr/oracle11g'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.job_queue_processes=5
*.open_cursors=300
*.pga_aggregate_target=1824522240
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=1258291200#internally adjusted
*.sga_target^@^@C^AC"^@^@^@^@^@^D^@^@^@^@^@^@^A^DCS^@^@=1056964608
*.undo_tablespace='UNDOTBS1'
==============================
SQL> select destination from V$ARCHIVE_DEST;
DESTINATION
/usr/oracle11g/R1/dbs/arch
USE_DB_RECOVERY_FILE_DEST
10 rows selected.
SQL> SQL> archive log lis
SP2-0718: illegal ARCHIVE LOG option
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 2549
Next log sequence to archive 2551
Current log sequence 2551
SQL>
===================
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
standby_archive_dest string ?/dbs/arch

This is the way 11g install sets up the archive destination intially after creating the database using DBA.
What you can do is to go to the Recovery Settings in Enterprise Manager. You would notice that Archive Log Destination number 1 is set to usr/oracle11g/R1/dbs/arch while number 10 is set to USE_DB_RECOVERY_FILE_DEST
Remove the entry for Number 1 (leave it blank). Apply the settings. This will force Oracle to only log to flash_recovery_area.
<br>
Oracle Database FAQs
</br>

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')

RMAN copies of archived logs view

When I backup the archivelogs with this statement:
backup as copy archivelog all;
Why are these copies not shown in the RC_BACKUP_ARCHIVELOG_DETAILS view?
The Description says:
BTYPE      CHAR(9)      The backup type container, which can be BACKUPSET, IMAGECOPY or PROXYCOPY.
In which view or table are this files represented?
Thanks!
Edited by: 916796 on 24.02.2012 04:15
Edited by: 916796 on 24.02.2012 06:29

OK
I think V$BACKUP_REDOLOG is the one.
http://docs.oracle.com/cd/E11882_01/server.112/e25513/dynviews_1060.htm#REFRN30024
SELECT * FROM V$BACKUP_REDOLOG ;
set linesize 200
SELECT THREAD#, SEQUENCE#, FIRST_TIME, NEXT_CHANGE#, NEXT_TIME, BLOCKS FROM V$BACKUP_REDOLOG;
-- archive logs backed up
select
THREAD#,
   MAX(SEQUENCE#)
FROM
V$BACKUP_REDOLOG
GROUP BY
THREAD#;Best Regards
mseberg
Edited by: mseberg on Feb 24, 2012 7:37 AM
Later
I did a test on one of my test databases
SQL> SELECT DBID FROM V$DATABASE;
      DBID
1612176986And then
SELECT
DB_KEY
FROM
RMANCAT.RC_DATABASE
WHERE
DBID = 1612176986; Once I have this I can query the "RC" tables
SELECT
FROM
RMANCAT.RC_ARCHIVED_LOG
WHERE DB_KEY = 2511344 ;   -- 72It returns 72 rows so I did a log switch and ran the query again, the count remained 72.
Next I tried this :
SELECT
FROM
RMANCAT.RC_BACKUP_ARCHIVELOG_DETAILS
    WHERE DB_KEY = 2511344; I expected another 72, but got 66. I did another log switch and it remained 66.
So I think you are right about the RC_ tables. And they seem to only hold backup info.
RC_ARCHIVED_LOG shows the most promise. The query should probably include a AND IS_STANDBY = 'NO'
Having a difficult time finding exactly what you want.
Edited by: mseberg on Feb 24, 2012 2:46 PM

Any 3rd party Database Activity Monitoring products that read Archive Logs?

I've been doing lots of research to find auditing-related 3rd party software products that read Oracle's archive log files. Many products are available for 'log' monitoring for security etc., but so far I've not found any that read the actual archive log files themselves. LogMiner is useful, but need to know if other products exist.
Any info is appreciated! Thanks.....

Thanks for your reply, Satish

Goldengate extracting from Archive log

Dear All,
We are conducting a replication of Oracle Database. Due to high load on Production server, the client is providing us a near DR database server for extraction. This database server is using Oracle Data Guard to be in Sync with Production server. Hence we will be using Archive logs shipped from Production to DR to Extract changed data. I have searched on the Net and read manuals, but I am unable to understand the how to configure OGG for this scenario. I understand that we can used Tranlogoptions parameter to extract data from Archive logs, but since the near DR database is in Mount state, how can we Log in the database using userid /password in extract process. Also we need to have Select any dictionary privileges on the database, but database is in mount state, so how to work on it??
Awaiting eagerly for the reply.l

For a physical standby, you can configure GG to read the archived standby logs in archive log only (ALO) mode.
ARCHIVEDLOGONLY causes Extract to read from the archived logs exclusively, without querying or validating the logs from system views such as v$log and v$archived_log. This parameter puts Extract into Archived Log Only mode (ALO). For more information, see the Oracle GoldenGate Oracle Installation and Setup Guide.
You can configure the Extract process to read exclusively from the archived logs. This is
known as Archived Log Only (ALO) mode. In this mode, Extract only reads from archived
logs that are stored in a specified location. ALO mode allows Oracle GoldenGate to use
production logs that are shipped over to a secondary database (such as a standby) as the
data source for Oracle GoldenGate. The online logs will not be used. Oracle GoldenGate
will connect to the secondary database to get metadata and other required data as needed.
As an alternative, ALO mode is supported on the production system.
Extract automatically operates in ALO mode if it detects that the database is a physical standby.
Lots of other info in the Oracle install guide.

When to delete Archive Log files ? and is safe to delete ?

Hi all,
I have a question, my DB is running in Archive Log mode and is growing day by day, so should I delete archive log files and where i find that my which files are old and how to delete theses files, for info I also take full RMAN and export backup regularly .
abbas

Well, if you're not comfortable with Backup and Recovery principles, i'd advise you to first read TFM: Backup and Recovery Concept(click) for you data safety's sake.
Anyway, just to give you a glance at what could happen, immagine suche a situation where your database is made of 5 different datafiles (whatever they are - SYSTEM, SYSAUX, UNDO, ...), controlfiles and online redo logs. If, for example your backup is done in a timeline such as:T0 : Backup datafile F1 and F2
T1 : Backup datafile F2 and controlfile
T2 : Backup datafile F3, F4
T3 : Backup datafile F5
T0' : Backup datafile F1 and F2
T1' : Backup datafile F2 and controlfile
T2' : Backup datafile F3, F4
T3' : Backup datafile F5
...If your server crashes (for example is thrown though the 5th floor window..) in order to make a full recovery, you could proceed multiple ways.
. Restore files from Tx' backups. Then you'd need every archived redo logs created from T0' to now in order to be able to do a full recovery.
. Restore files from backups; T3, T0', T2' and rectreate controlfile. Then you'd need every archived redo log created from T3 (inclusive).
. Restore Tx backup, ...
. Restore ...
and so on.
What's important is that you're at least able to resynch a full-set backup. What I mean is: if you restored "T3, T0', T2' and rectreate controlfile", in order to open the database you'll absolutely need every archived redo log created between T3 and T2' inclusive. If one is missions, you won't be able to open it.
That is the principle. Read the concept book I linked to get more infos.
Regards,
Yoann.

Too many Archive Log

Hi,
I have a problem on a production server: our support partner told me that we are creating too many Archive Log files. They are not sure at all of what is happening.
Please, do you know if there is any System View which we could obtain more information about Archive Logs usage?
Thanks in advance.
Best Regards,
Joan Padilla

Hi Joan,
The sensible number of archive logs is determined by your backup and recovery strategy. You can delete them, once you have back-upped the database and the archivelogs. Further info in the Backup and Recovery Concepts manual.
You can find information on them in v$archived_log.
If you decide to delete them without having read the aforementioned manual, I will pray for you you don't suffer a hard disk crash.
You may want to review the relationship with your support partner too.
Their advice is not exactly professional.
Sybrand Bakker
Senior Oracle DBA

Restore archive log which were not backed up

Hi experts,
as per understandings, after the creation of database the scn will starts from 1 and it grows sequentially,
1)i have not taken any backup until today.
2) i deleted all the archivelogs, but i have database alive
3) taken a full backup.
so i tried to restore from scn 100 to 200.
restore archivelog from scn 100 until scn 200;error:
RMAN-20242: specification does not match any archivelog in recovery cataloag
now my scn is 504575
is it possible to restore archive log from 100 scn to 200 scn?
Thanks & Best Regards.
appriciated for the right answers.

784585 wrote:
Hi,
iam not using any STANDBY database..But earlier you said "see if any case accidently missed archives are deleted, those archives need to apply in standby, so what can we do?"
So of course people thought you were trying to sync up a standby ...
i want to generate all the archives from the scratch of the database..
my question is , database SCN will start from 1, so all the database has information from 1 to end...so why cant we take backup again as archives from database?This is pretty basic. You cannot recover from a backup you do not have. You've already said
1)i have not taken any backup until today.
2) i deleted all the archivelogs, but i have database aliveSo with no backup and no archive log, what would expect to recover from?
OK, here's how it works.
As changes are made to the database, a record of the change is written to a memory (not disk) structure called the "redo log buffer". When a transaction is committed the redo log buffer is written to the online redo log file. You must have a minimum of two online redo log files. This online redo log file is of fixed size. When it is full, the process of writing to it switched to the other (or next, if you have more than two). When an online redo log file is filled, and writing of redo info is switched to the next file, the filled file is copied to a NEW archived log file. After going through all the online redo logs in this round-robin fashion, it will come back to the first and start overwriting its previous contents. The archived log files are given unique names so that they are not over written but instead generate a constant stream of new archivelogs. It is these archive log files that contain all of your redo info that pre-dates the oldest info remaining in the online redo logs.
In a recovery operation, the following happens
first, the database files are restored from backup, starting with the newest full backup that meets your recovery needs, then following with all incremental backups after that. You said you have no backups prior to today.
Second, after the files are restored from backups (which you said you don't have) additional redo information is applied to get the changes since the most recent full or incremental backup that was restored. This additional info comes from the archivelog files, which you said you didn't back up and apparently you deleted.
So, you've said you have no database backup and no archivlogs either backed up or original. So from where do you expect to be able to recover this information?

Automatic archive log

I am learning Oracle on 9i, try to set database as automatic archive log but always failed. pls help.
Thanks
Init.ora:
# Redo Log and Recovery
log_archive_start = true
log_archive_dest = %ORACLE_HOME%\database\%%ORACLE_SID%%\archive
log_archive_format = "%%ORACLE_SID%%%T%TS%S.ARC"
here the info:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Disabled
Archive destination D:\oracle\ora90\RDBMS
Oldest online log sequence 12
Next log sequence to archive 14
Current log sequence 14

I am learning Oracle on 9i, try to set database as automatic archive log but always failed. pls help.
Thanks
Init.ora:
# Redo Log and Recovery
log_archive_start = true
log_archive_dest = %ORACLE_HOME%\database\%%ORACLE_SID%%\archive
log_archive_format = "%%ORACLE_SID%%%T%TS%S.ARC"
here the info:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Disabled
Archive destination D:\oracle\ora90\RDBMS
Oldest online log sequence 12
Next log sequence to archive 14
Current log sequence 14 I think you're close to getting it working, you have all of the init.ora parameters set. If you do the following in SQL Plus it should work:
SHUTDOWN IMMEDIATE
STARTUP MOUNT <SID> EXCLUSIVE
ALTER DATABASE <SID> ARCHIVELOG
SHUTDOWN IMMEDIATE
STARTUP
Then run ARCHIVE LOG LIST to verify it worked.

Extract is abended and looking 8 days old archive log.

I was doing some maintenance and I stop all the extracts and replicats. Couple of my extracts are stopped and looking for 8 days old archive logs. Please tell me how can I recover from that situation. I dont have that archive any more we only keep 5days arch.
GGSCI (ggastdb01.infra.mms) 5> info e_it860t
EXTRACT E_IT860T Initialized 2011-02-08 16:04 Status STOPPED
Checkpoint Lag 00:10:05 (updated 04:34:30 ago)
Log Read Checkpoint Oracle Redo Logs
2011-02-24 09:53:04 Seqno 15721, RBA 103192
Report file Error:
2011-02-24 14:34:04 ERROR OGG-00446 Could not find archived log for sequence 15494 thread 1 under alternative or default destinations. SQL <SELECT name FROM v$archived_log WHERE sequence# = :ora_seq_no AND thread# = :ora_thread AND resetlogs_id = :ora_resetlog_id AND archived = 'YES' AND deleted = 'NO>. Last alternative log tried /u10/oradata/PPMTST10/arch/1_15494_721133148.arc, error retrieving redo file name for sequence 15494, archived = 1, use_alternate = 0Not able to establish initial position for sequence 15494, rba 68728848.
2011-02-24 14:34:04 ERROR OGG-01668 PROCESS ABENDING.

If you don't have the log file(s) in question, then you need to:
re-sync the databases/schema/tables, or
advance the CSN to a point in time where you do have log files and deal with missing data separately
Is an archived transaction log missing?
● Extract reads the archived logs when an online log is not available. If you started
Extract after it was stopped for a long time, the records it needs to process might
already be archived away.
● Restore the archive log that is specified in the error message in the report file, and also
restore all subsequent logs.
NOTE Extract should not be stopped for a long time. If you must stop Extract, make
certain that archives are available all the way back to the time that you stopped
Extract. If Extract remains stopped for an exceptionally long time, it might be more
practical to resynchronize the table(s) rather than wait for Extract to go through the
archives and catch up.

Archive log info

Similar Messages

Maybe you are looking for