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.

Similar Messages

How to removed the 300GB old archive logs???

Dear Gurus
Site-A
Our Environment:
Live Production 2-Node RAC Oracle10g r2 10.2.0.4
Data and Archive is stored in Oracle ASM
Operating System: Sun Solaris10 64bit
We have two databases.
==>db-1(Site-A db-1 is Oracle streaming with Site-B db-1,so archive logs should not be deleted which is required for oracle streaming)
==>db-2
Existing Backup and Recovery Strategy:
Daily logical backup of application schema using DATA PUMP.
We have not taken any RMAN Backup still.
Please find the status of Shared Storage.
-bash-3.00$ asmcmd
ASMCMD> lsdg
State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
MOUNTED EXTERN N N 512 4096 1048576 614256 577801 0 577801 0 DATA/
MOUNTED EXTERN N N 512 4096 1048576 298948 38635 0 38635 0 FLASH/
We want to removed the old archive logs?
Please suggest the best way of removed the old archive logs for db-2 and db-1?
Can you Please suggest that how many time and how many space it's required for completed the backup?
Regards
Hitesh Gondalia
Edited by: hitgon on Oct 1, 2011 9:50 PM
Edited by: hitgon on Oct 1, 2011 10:09 PM
Edited by: hitgon on Oct 1, 2011 10:13 PM

You should consider using RMAN for backup/recovery. Logical exports (Data Pump) are useful for some purposes, but are not the preferred way to go for your backup and recovery needs. RMAN will give you better performance and so much more options.
Long-term, a great way to delete archivelog backups is via RMAN “backup archivelog …. delete input” and/or “delete archivelog … “commands.
Please delete archivelogs only after they are already backed up. RMAN will also take into consideration if the backups are needed for Streams and/or Standby.
About the backup space – a full RMAN backup is typically smaller than the size of your DB. You need to run a test to see the exact size. The frequency and type of backup should be based on your SLE for this DB.
Iordan Iotzov
http://iiotzov.wordpress.com/

Golden Gate for mysql5.5 extract is Abended,and not error in the file

Dear All,
golden gate for mysql5.5 to oracle 11g,extract is Abended ,but there didn't have error in the log , And sometimes the successful extraction some records;
extract :
EXTRACT EXT_M1
TRANLOGOPTIONS AltLogDest /mydata/mysqllog/binlog/binlog.index
SOURCEDB [email protected]:16052, USERID mama,PASSWORD mama
sqlexec "set names gbk;"
EXTTRAIL dirdat/m1
Dynamicresolution
TABLE mama.merchants_member_card_customer;
datapump:
EXTRACT DPRD_M1
SOURCEDB [email protected]:16052, USERID mama,PASSWORD mama
RMTHOST 192.168.2.57, MGRPORT 7089, compress --COMPRESSUPDATESETWHERE
RMTTRAIL /home/oracle/goldengate/dirdat/m1
NOPASSTHRU
TABLE mama.merchants_member_card_customer;
GGSCI>>info all
Program     Status      Group       Lag at Chkpt Time Since Chkpt
MANAGER     RUNNING
EXTRACT     RUNNING     DPRD_M1     00:00:00      00:00:01
EXTRACT     ABENDED     EXT_M1      00:11:49      00:01:56
REPORT:
GGSCI>>view report ext_m1
                  Oracle GoldenGate Capture for MySQL
      Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230
Linux, x64, 64bit (optimized), MySQL Enterprise on Apr 23 2012 05:23:34
Copyright (C) 1995, 2012, Oracle and/or its affiliates. All rights reserved.
                    Starting at 2013-09-29 18:38:08
Operating System Version:
Linux
Version #1 SMP Wed Jun 13 18:24:36 EDT 2012, Release 2.6.32-279.el6.x86_64
Node: M46
Machine: x86_64
                         soft limit   hard limit
Address Space Size   :    unlimited    unlimited
Heap Size            :    unlimited    unlimited
File Size            :    unlimited    unlimited
CPU Time             :    unlimited    unlimited
Process id: 6322
Description:
**            Running with the following parameters                  **
2013-09-29 18:38:08 INFO    OGG-03035 Operating system character set identified as UTF-8. Locale: zh_CN, LC_ALL:.
EXTRACT EXT_M1
TRANLOGOPTIONS AltLogDest /mydata/mysqllog/binlog/binlog.index
SOURCEDB [email protected]:16052, USERID mama100,PASSWORD ****************
sqlexec "set names gbk;"
Executing SQL statement...
2013-09-29 18:38:08 INFO    OGG-00893 SQL statement executed successfully.
EXTTRAIL dirdat/m1
Dynamicresolution
TABLE mama100.merchants_member_card_customer;
2013-09-29 18:38:08 INFO    OGG-01815 Virtual Memory Facilities for: COM
    anon alloc: mmap(MAP_ANON) anon free: munmap
    file alloc: mmap(MAP_SHARED) file free: munmap
    target directories:
    /home/goldengate/dirtmp.
CACHEMGR virtual memory values (may have been adjusted)
CACHESIZE:                               64G
CACHEPAGEOUTSIZE (normal):                8M
PROCESS VM AVAIL FROM OS (min):         128G
CACHESIZEMAX (strict force to disk):     96G
Database Version:
MySQL
Server Version: 5.5.24-patch-1.0-log
Client Version: 6.0.0
Host Connection: 192.168.2.46 via TCP/IP
Protocol Version: 10
2013-09-29 18:38:08 INFO    OGG-01056 Recovery initialization completed for target file dirdat/m1000000, at RBA 1295, CSN 000086|000000065228677.
2013-09-29 18:38:08 INFO    OGG-01478 Output file dirdat/m1 is using format RELEASE 11.2.
2013-09-29 18:38:08 INFO    OGG-01026 Rolling over remote file dirdat/m1000000.
2013-09-29 18:38:08 INFO    OGG-00182 VAM API running in single-threaded mode.
2013-09-29 18:38:08 INFO    OGG-01515 Positioning to begin time 2013-9-29 06:26:18.
**                     Run Time Messages                             **
2013-09-29 18:38:08 INFO    OGG-01516 Positioned to Log Number: 86
    Record Offset: 65223906, 2013-9-29 06:26:18.
2013-09-29 18:38:08 INFO    OGG-01517 Position of first record processed Log Number: 86
    Record Offset: 65223906, 2013-9-29 06:26:18.
TABLE resolved (entry mama100.merchants_member_card_customer):
TABLE mama100."merchants_member_card_customer";
Using the following key columns for source table mama100.merchants_member_card_customer: id.
2013-09-29 18:38:08 INFO    OGG-01054 Recovery completed for target file dirdat/m1000001, at RBA 1316, CSN 000086|000000065228677.
2013-09-29 18:38:08 INFO    OGG-01057 Recovery completed for all targets.
ggsevt:
2013-09-29 18:38:08 INFO    OGG-00963 Oracle GoldenGate Manager for MySQL, mgr.prm: Command received from GGSCI on host localhost (START EXTRACT EXT_M1 ).
2013-09-29 18:38:08 INFO    OGG-00975 Oracle GoldenGate Manager for MySQL, mgr.prm: EXTRACT EXT_M1 starting.
2013-09-29 18:38:08 INFO    OGG-00992 Oracle GoldenGate Capture for MySQL, ext_m1.prm: EXTRACT EXT_M1 starting.
2013-09-29 18:38:08 INFO    OGG-03035 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Operating system character set identified as UTF-8. Locale: zh_CN, LC_ALL:.
2013-09-29 18:38:08 INFO    OGG-00893 Oracle GoldenGate Capture for MySQL, ext_m1.prm: SQL statement executed successfully.
2013-09-29 18:38:08 INFO    OGG-01815 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Virtual Memory Facilities for: COM
    anon alloc: mmap(MAP_ANON) anon free: munmap
    file alloc: mmap(MAP_SHARED) file free: munmap
    target directories:
    /home/goldengate/dirtmp.
2013-09-29 18:38:08 INFO    OGG-00993 Oracle GoldenGate Capture for MySQL, ext_m1.prm: EXTRACT EXT_M1 started.
2013-09-29 18:38:08 INFO    OGG-01056 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Recovery initialization completed for target file dirdat/m1000000, at RBA 1295, CSN 000086|000000065228677.
2013-09-29 18:38:08 INFO    OGG-01478 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Output file dirdat/m1 is using format RELEASE 11.2.
2013-09-29 18:38:08 INFO    OGG-01026 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Rolling over remote file dirdat/m1000000.
2013-09-29 18:38:08 INFO    OGG-00182 Oracle GoldenGate Capture for MySQL, ext_m1.prm: VAM API running in single-threaded mode.
2013-09-29 18:38:08 INFO    OGG-01515 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Positioning to begin time 2013-9-29 06:26:18.
2013-09-29 18:38:08 INFO    OGG-01516 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Positioned to Log Number: 86
    Record Offset: 65223906, 2013-9-29 06:26:18.
2013-09-29 18:38:08 INFO    OGG-01517 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Position of first record processed Log Number: 86
    Record Offset: 65223906, 2013-9-29 06:26:18.
2013-09-29 18:38:08 INFO    OGG-01054 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Recovery completed for target file dirdat/m1000001, at RBA 1316, CSN 000086|000000065228677.
2013-09-29 18:38:08 INFO    OGG-01057 Oracle GoldenGate Capture for MySQL, ext_m1.prm: Recovery completed for all targets.
2013-09-29 18:38:09 INFO    OGG-01054 Oracle GoldenGate Capture for MySQL, dprd_m1.prm: Recovery completed for target file /home/oracle/goldengate/dirdat/m1000002, at RBA 1435, CSN 000086|000000055512672.
2013-09-29 18:38:09 INFO    OGG-01057 Oracle GoldenGate Capture for MySQL, dprd_m1.prm: Recovery completed for all targets.

GGSCI>>info ext_m1 showch
EXTRACT    EXT_M1    Last Started 2013-09-29 18:38   Status ABENDED
Checkpoint Lag       00:11:49 (updated 00:12:05 ago)
VAM Read Checkpoint 2013-09-29 18:26:18.665841
Current Checkpoint Detail:
Read Checkpoint #1
VAM External Interface
Startup Checkpoint (starting position in the data source):
    Timestamp: 2013-09-29 18:26:18.665841
Recovery Checkpoint (position of oldest unprocessed transaction in the data source):
    Timestamp: 2013-09-29 18:26:18.665841
Current Checkpoint (position of last record read in the data source):
    Timestamp: 2013-09-29 18:26:18.665841
Write Checkpoint #1
GGS Log Trail
Current Checkpoint (current write position):
    Sequence #: 0
    RBA: 917
    Timestamp: 2013-09-29 18:30:55.655570
    Extract Trail: dirdat/m1
CSN state information:
CRC: 20-82-1D-34
CSN: Not available
Header:
Version = 2
Record Source = A
Type = 8
# Input Checkpoints = 1
# Output Checkpoints = 1
File Information:
Block Size = 2048
Max Blocks = 100
Record Length = 20480
Current Offset = 0
Configuration:
Data Source = 5
Transaction Integrity = 1
Task Type = 0
Status:
Start Time = 2013-09-29 18:38:08
Last Update Time = 2013-09-29 18:38:08
Stop Status = A
Last Result = 0

How to delete old archived logs

hai i am running oracle 9i in archive log mode
my disk is about 90% full
pls tell me how to delete archive logs that are very older

Hi Rajeskm,
First of all, archives should not be deleted, depending your backup policie, you can need them in a recovery. But if you want delete them, do:
find <log_archive_dest>/ -name *.rdo (or extention used by you) mtime +<days ago> -exec rm{}\
Explanation:
Find -- The first, and most obvious, use is find's ability to locate old, big, or unused files, or files that you forgot where they are.
mtime -- The mtime--modify time--is the time when the actual contents of a file was last modified. This is the time displayed in a long directoring listing (ls -l).
rm -- Deletes a file without confirmation (by default).
Regards,
Jonathan Ferreira - Brazil
http://www.ebs11i.com.br

Deleting the old Archive Log Files from the Hard Disk

Hello All,
I want to delete the old archive files of Oracle. These files are very old and consuming very huge disk space.
Is there any way by which I can delete these files from the Hard Disk?
Can I directly delete them using the Operating System Command?
Will it cause any dilfference to the normal functioning of my Database?
If I need to delete these files, do I need to bring the database down?
Please guide me.
I need to do this activity to make some space free on the Hard Disk.
Thanks in advance.
Himanshu

Hi.
Keep archived logs from time of last backup and forward to currenct time on disk together with the backup itself. And keep older archived logs together with older warm/cold backupfiles on tape as long as there is enough capasity or following your recovery strategy. This way you might be able to roll forward a recovery without restoring these files from tape which often the faster.
Older archived logs can be deleted manually, with scheduled OS script or automatically with RMAN.
Good luck
rgds
Kjell Ove

RMAN backup archive logs on tape that has not been backuped yet...

We are using RMAN with catalog on Legato. Oracle 10gR2.
Our archive log backup is taking every 2 hours with scriipt:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
# 0.0840278 = 121 minutes!
backup archivelog FROM TIME = 'sysdate-0.0840278' filesperset 50 format '/arch1_%d_%u/';
release channel t1;
release channel t2;
}In the night we take everyday full backup where we delete all 9 days old archive log which has been backuped on tape at least once. The script is following:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
backup full database filesperset 2 format '/full_%d_%U/';
release channel t1;
release channel t2;
allocate channel d2 type disk;
delete archivelog until time 'trunc(sysdate)-9'
backed up 1 times to device type SBT_TAPE;
release channel d2;
}Problem is that sometimes archive log backup is not performed (Legato head is busy with other backups or some restore that happened in the time when backup is scheduled and later 2hours frame is missing those logs) and then we backup them with some manual script.
We'd like to know how to backup to tape all archive logs in last 5 days that has not been backuped once to tape. I.E:
backup archivelog FROM TIME = 'sysdate-7' filesperset 50 format '/arch1_%d_%u/'
backed up 0 times to device type SBT_TAPE;This part will be included in daily job...which should recollect all missing archive logs from last seven days.
THX

You could try to use the NOT BACKED UP x TIMES clause from BACKUP command.

Cleanup job to remove archive logs automatically through OEM Grid control

Hi All,
I am working on 11gR2 3node RAC database. we have enabled archivelog mode for the databases and don't have any backup processes (like rman) and not using ASM.
Please let me know how to cleanup the old archivelogs automatically through oem Grid control.
I have some idea how to do it in standalone database, but not sure how it works in RAC environment through OEM. Please let me know.
Thanks in advance.

Hari wrote:
Thanks for your reply and The requirement is, put the DB in archive log mode and cleanup the old archive logs which is more than 5days. We are doing this because of space issue and don't have backup for these files and the DB must be in archive log mode.
I have few question here.
1. Is it must to take the backup of the archive log files and before delete them?No, but if you aren't backing up, why create the archivelogs in the first place?
2. If i delete them without backup, what is the negative impact?If you aren't backing up the database in the first place (as you stated in an earlier post) then it really doesn't matter what you do with the archivelogs as they are worthless anyway.
3. What is the recommended process to do it?My recommendation is you first start using rman to backup the database
4. I need to setup this process through OEM grid control.
Please let me know.
Thanks,
HariIt all begs the question which has already been asked and you avoided answering . . . if you are not taking backups, why bother archiving? The archive logs have ZERO VALUE outside of a consistent backup strategy. So how is it you have a 'requirement' to run in archivelog mode but no requirement for backups?
Edited by: EdStevens on Dec 2, 2011 9:30 PM

System I/O and Too Many Archive Logs

Hi all,
This is frustrating me. Our production database began to produce too many archived redo logs instantly --again. This happened before; two months ago our database was producing too many archive logs; just then we began get async i/o errors, we consulted a DBA and he restarted the database server telling us that it was caused by the system(???).
But after this restart the amount of archive logs decreased drastically. I was deleting the logs by hand(350 gb DB 300 gb arch area) and after this the archive logs never exceeded 10% of the 300gb archive area. Right now the logs are increasing 1%(3 GB) per 7-8 mins which is too many.
I checked from Enterprise Manager, System I/O graph is continous and the details show processes like ARC0, ARC1, LGWR(log file sequential read, db file parallel write are the most active ones) . Also Phsycal Reads are very inconsistent and can exceed 30000 KB at times. Undo tablespace is full nearly all of the time causing ORA-01555.
The above symptoms have all began today. The database is closed at 3:00 am to take offline backup and opened at 6:00 am everyday.
Nothing has changed on the database(9.2.0.8), applications(11.5.10.2) or OS(AIX 5.3).
What is the reason of this most senseless behaviour? Please help me.
Thanks in advance.
Regards.
Burak

Selam Burak,
High number of archive logs are being created because you may have massive redo creation on your database. Do you have an application that updates, deletes or inserts into any kind of table?
What is written in the alert.log file?
Do you have the undo tablespace with the guarentee retention option btw?
Have you ever checked the log file switch sequency map?
Please use below SQL to detirme the switch frequency;
SELECT * FROM (
SELECT * FROM (
SELECT TO_CHAR(FIRST_TIME, 'DD/MM') AS "DAY"
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '00', 1, 0)), '999') "00:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '01', 1, 0)), '999') "01:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '02', 1, 0)), '999') "02:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '03', 1, 0)), '999') "03:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '04', 1, 0)), '999') "04:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '05', 1, 0)), '999') "05:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '06', 1, 0)), '999') "06:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '07', 1, 0)), '999') "07:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '08', 1, 0)), '999') "08:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '09', 1, 0)), '999') "09:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '10', 1, 0)), '999') "10:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '11', 1, 0)), '999') "11:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '12', 1, 0)), '999') "12:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '13', 1, 0)), '999') "13:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '14', 1, 0)), '999') "14:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '15', 1, 0)), '999') "15:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '16', 1, 0)), '999') "16:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '17', 1, 0)), '999') "17:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '18', 1, 0)), '999') "18:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '19', 1, 0)), '999') "19:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '20', 1, 0)), '999') "20:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '21', 1, 0)), '999') "21:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '22', 1, 0)), '999') "22:00"+
+, TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '23', 1, 0)), '999') "23:00"+
FROM V$LOG_HISTORY
WHERE extract(year FROM FIRST_TIME) = extract(year FROM sysdate)
GROUP BY TO_CHAR(FIRST_TIME, 'DD/MM')
+) ORDER BY TO_DATE(extract(year FROM sysdate) || DAY, 'YYYY DD/MM') DESC+
+) WHERE ROWNUM < 8+
Ogan

How long should a reasonable person expect their computer screen to last before a pixel drop out line appears? I have been asked to pay for a repair after 1 year and 19 days!!

A thin coloured line appeared on my i-Mac screen and I have been asked to pay £139 to have it repaired. This was reduced by the manager of the Sheffield store from c£300!!
The computer is 1 year and 19 days old but the warranty period is 1 year. I was uanable to bring the machine in earlier but the problem was there 2 weeks ago within the warranty period. Still no joy from the store as I had not reported it before the 12 months!!
What with Time Capsule back-up issues I an beginning to lose faith in Apple.
Surely a reasonable person could expect the machine to be repaired FOC as a goodwill gesture?

opticalted wrote:
Surely a reasonable person could expect the machine to be repaired FOC as a goodwill gesture?
Not after the warranty has expired. Apple has no obligation to do so.

Urgent: Huge diff in total redo log size and archive log size

Dear DBAs
I have a concern regarding size of redo log and archive log generated.
Is the equation below is correct?
total size of redo generated by all sessions = total size of archive log files generated
I am experiencing a situation where when I look at the total size of redo generated by all the sessions and the size of archive logs generated, there is huge difference.
My total all session redo log size is 780MB where my archive log directory size has consumed 23GB.
Before i start measuring i cleared up archive directory and started to monitor from a specific time.
Environment: Oracle 9i Release 2
How I tracked the sizing information is below
logon as SYS user and run the following statements
DROP TABLE REDOSTAT CASCADE CONSTRAINTS;
CREATE TABLE REDOSTAT
AUDSID NUMBER,
SID NUMBER,
SERIAL# NUMBER,
SESSION_ID CHAR(27 BYTE),
STATUS VARCHAR2(8 BYTE),
DB_USERNAME VARCHAR2(30 BYTE),
SCHEMANAME VARCHAR2(30 BYTE),
OSUSER VARCHAR2(30 BYTE),
PROCESS VARCHAR2(12 BYTE),
MACHINE VARCHAR2(64 BYTE),
TERMINAL VARCHAR2(16 BYTE),
PROGRAM VARCHAR2(64 BYTE),
DBCONN_TYPE VARCHAR2(10 BYTE),
LOGON_TIME DATE,
LOGOUT_TIME DATE,
REDO_SIZE NUMBER
TABLESPACE SYSTEM
NOLOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
GRANT SELECT ON REDOSTAT TO PUBLIC;
CREATE OR REPLACE TRIGGER TR_SESS_LOGOFF
BEFORE LOGOFF
ON DATABASE
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
INSERT INTO SYS.REDOSTAT
(AUDSID, SID, SERIAL#, SESSION_ID, STATUS, DB_USERNAME, SCHEMANAME, OSUSER, PROCESS, MACHINE, TERMINAL, PROGRAM, DBCONN_TYPE, LOGON_TIME, LOGOUT_TIME, REDO_SIZE)
SELECT A.AUDSID, A.SID, A.SERIAL#, SYS_CONTEXT ('USERENV', 'SESSIONID'), A.STATUS, USERNAME DB_USERNAME, SCHEMANAME, OSUSER, PROCESS, MACHINE, TERMINAL, PROGRAM, TYPE DBCONN_TYPE,
LOGON_TIME, SYSDATE LOGOUT_TIME, B.VALUE REDO_SIZE
FROM V$SESSION A, V$MYSTAT B, V$STATNAME C
WHERE
A.SID = B.SID
AND
B.STATISTIC# = C.STATISTIC#
AND
C.NAME = 'redo size'
AND
A.AUDSID = sys_context ('USERENV', 'SESSIONID');
COMMIT;
END TR_SESS_LOGOFF;
Now, total sum of REDO_SIZE (B.VALUE) this is far less than archive log size. This at time when no other user is logged in except myself.
Is there anything wrong with query for collecting redo information or there are some hidden process which doesnt provide redo information on session basis.
I have seen the similar implementation as above at many sites.
Kindly provide a mechanism where I can trace which user is generated how much redo (or archive log) on a session basis. I want to track which all user/process are causing high redo to generate.
If I didnt find a solution I would raise a SR with Oracle.
Thanks
[V]

You can query v$sess_io, column block_changes to find out which session generating how much redo.
The following query gives you the session redo statistics:
select a.sid,b.name,sum(a.value) from v$sesstat a,v$statname b
where a.statistic# = b.statistic#
and b.name like '%redo%'
and a.value > 0
group by a.sid,b.name
If you want, you can only look for redo size for all the current sessions.
Jaffar

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.

Extract in abended

HI !
I have add extract in (sqlserver2005 standard sp3 11.2.1.0.2 ogg)
trying to replicate to oracle 11g xe.
ADD EXTRACT finance, TRANLOG, BEGIN NOW
EXTRACT ttext
SOURCEDB osdfsdfdsf,USERID sdfsdfsd, PASSWORD sdfsdfsdf &
AES128, ENCRYPTKEY securekey1
EXTTRAIL /V34016-01/dirdat/lt
TABLE dbo.*;
when i am starting
start extract ttext
it is showing error
can not create process 'extract' ,child process is no longer alive.
warnning 01742: mgr mgr returen with error response.
and info all is showing manager is running
but extract is abended and showing total time in time since chkpt.
yours sincerely
Edited by: 944768 on Sep 12, 2012 7:08 AM

thank u.
After adding exttrail and
TRANLOGOPTIONS MANAGESECONDARYTRUNCATIONPOINT in prameter file it has started
but shwing below error. when using view report <ext>
with status running.
2012-09-12 21:47:58 WARNING OGG-00091 VAM Client Report <[mssqlvam::TruncMgr::
Timer] Unable to execute procedure. The database is not published. Execute the p
rocedure in a database that is published for replication. Error (-2147217900): U
nable to execute procedure. The database is not published. Execute the procedure
in a database that is published for replication.
yours sincerely
Edited by: 944768 on Sep 12, 2012 9:58 PM
Edited by: 944768 on Sep 12, 2012 9:59 PM

How to recover datafile in Oralcle 10g...? No backups and No archive log

All,
I need to recover the datafile 2 which is for undo tablespace and it is in recover state and i need to recover the data files now .
But the bad thing is We dont have backup at all and we dont have archive logs (Archive log disabled in the database)...
In this situation how can i recover the datafile ...?
SQL> select a.file#,a.name,a.status from v$datafile a,v$tablespace b where a.ts#=b.ts#;
FILE# NAME STATUS
1 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/system01.dbf SYSTEM
*2 /export/home/oracle/logs/bw/undotbs01.dbf RECOVER*
3 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/sysaux01.dbf ONLINE
4 /export/home/oracle/datafiles/bw/bwfcc73.dbf ONLINE
5 /export/home/oracle/datafiles/bw/bwfcc73_01.dbf ONLINE
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 4940
Current log sequence 4942

Hi,
First of all you must Open a ticket with oracle Support and explore the options
You can use this note to fix it:
RECOVERING FROM A LOST DATAFILE IN A UNDO TABLESPACE [ID 1013221.6]
If you is Unable to Drop Undo tablespace Since Undo Segment is in Needs Recovery
You can Upload the following trace file while opening the ticket
SQL>Alter session set tracefile_identifier='corrupt';
SQL>Alter system dump undo header "<new of undo segment in recover status>";
Go to udump
ls -lrt *corrupt*
Upload this trace file
Also upload the alert log fileRegards,
Levi Pereira
Edited by: Levi Pereira on Nov 29, 2011 1:58 PM

Archive log mode Turn off

Hi all DBA guys, Have a Nice day all
If i change archive log mode to no archive log mode, internally whats happen my database?.
Is this old archive log backup use for future if again convert no archive to archive log mode?
What's happen flashback if i change archive log mode to no archive log mode?
Regards
S.Azar

azarmohds wrote:
Thanx lot,
why i asked this question means, rightnow you posted, this is feature of 10g i.e flashback database confiured when archive log mode is enabled...,so in this case
What's happen flashback if i change archive log mode to no archive log mode?S.Azar,
You should be clear about things that when you read notes from web, there can be a language mismatch. So the best is that search first over the oracle docs.
Now about your doubt, its a terminology mismatch which is happening here. To enable Flashback Database feature which is more persistent copy of the undo data , stored seperately in a FLB file, you MUST have to have archivelog mode configured in your db. Without this, you can't enable the Flashback Database feature. And you can't switch to noarchive log mode as well if you have Flashback Database mode on.
The other thing ( which I guess Anurag was mentioning ) is the normal Flashback feature which relies on Undo data stored in the undo tablespace. This solely is based on teh undo data and doesn't depend on the archive/nonarchive log mode of the database. But this is limited to that data and to that time period up till which you can store the undo data in your undo tablespace.
HTH
Aman....

Archive Logs in every 15 minutes(Oracle 11g 64 bit EE on Linux RHEL 4

In our production database we have very few transactions may be of few MB's in whole day but it is generating archive logs constantly in every 15 minutes(may be sometime in 14 minutes also) of file size 50 MB each and this way consume 4 GB of space in a day for archive log which is way above than expected.
I have checked archive_lag_target and value of this is 0.
Any clue why it is creating 50 MB archive log file after every 14-15 minutes?

It's easy enough to reduce redo log file size without downtime; just add new smaller redo log files, switch logfile a couple of times and drop the old redo log files.
However, if the redo logs are filling up before they switch, then this will probably only make matters worse.
If the redo logs are switching before they are full then maybe you also need to consider log_checkpoint_interval and log_checkpoint_timeout settings.
If the redo logs are filling up before they switch then use the techniques suggested by a couple of the other posters to track down the guilty SQL.

Extract is abended and looking 8 days old archive log.

Similar Messages

Maybe you are looking for