Archive from redo log

1. How can i read the DML's in the redo log?
I need the statements from the redo log like we get through LOGMINOR in SQL_REDO column.
2. How to create the archive log file from Redo logs through a command?
Means i want to clean the Redo log and want to create archive log so that i can use those archive log in LOGMINOR.
Thanks,

Hemant K Chitale wrote:You can find out which row it is and what are the contents of that row currently in your database by querying
Once you get the values, you'd have to work backwards (or forwards) to figure out what values you need to set in the other database.Actually i also have other tables then how i can consider perticular column name and search that?I could have other statements.
update "TEST2" set "LEADCOUNTSTDFAILED" = '234' where "LEADCOUNTSTDFAILED" = '233' and ROWID = 'AAAQDRAAKAAAUSdAAs';
Then how i can get it.
Also that view conists of thousands of DML's.
Thanks,

Similar Messages

Problem while archiving the redo Log

Hi all,
I m having few issues in my server...
I get the following error in the alert log of oracle..
There are many errors
1) No space left on device
2) ARC0: I/O error 19502 archiving log 1 to
'/oracle/admin/SNM/arch/arch_1_393_668727286.arc'
ARCH: Archival stopped, error occurred. Will continue retrying
3) ORA-16014: log 1 sequence# 393 not archive*d, no available destinations*
Also please find the v$log file query
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
1 1 405 1073741824 1 NO CURRENT
60275455 20-OCT-09
2 1 403 1073741824 1 NO INACTIVE
59987366 19-OCT-09
3 1 404 1073741824 1 NO INACTIVE
60125083 20-OCT-09
Also the diskspace is almost 97%.
Can anyone let me know whether archival of redo log files is causing the issue here?
If so if i stop the archival of logs ,will it solve the problem?
Can anyone help me on this?
Mon Oct 19 09:54:39 2009
Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
ORA-19502: write error on file
"/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
577537 (blocksize=512)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
ORA-19502: write error on file
"/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
559105 (blocksize=512)
Mon Oct 19 09:54:39 2009
Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
ORA-19502: write error on file
"/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno
577537 (blocksize=512)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
ORA-19502: write error on file
*"/oracle/admin/SNM/arch/arch_1_393_668727286.arc", blockno*
*559105 (blocksize=512)*
ARC0: I/O error 19502 archiving log 1 to
'/oracle/admin/SNM/arch/arch_1_393_668727286.arc'
ARCH: Archival stopped, error occurred. Will continue retrying
Mon Oct 19 09:54:40 2009
ORACLE Instance SNM - Archival Error
Mon Oct 19 09:54:40 2009
ORA-16038: log 1 sequence# 393 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
Mon Oct 19 09:54:40 2009
Errors in file /oracle/admin/SNM/bdump/snm_arc0_23831.trc:
ORA-16038: log 1 sequence# 393 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
Mon Oct 19 09:54:40 2009
ARCH: Archival stopped, error occurred. Will continue retrying
Mon Oct 19 09:54:40 2009
ORACLE Instance SNM - Archival Error
Mon Oct 19 09:54:40 2009
ORA-16014: log 1 sequence# 393 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
Mon Oct 19 09:54:40 2009
Errors in file /oracle/admin/SNM/bdump/snm_arc1_23833.trc:
ORA-16014: log 1 sequence# 393 not archive*d, no available destinations*
ORA-00312: online log 1 thread 1: '/oracle/oradata/SNM/redo01.log'
Mon Oct 19 10:00:16 2009
ARC0: Encountered disk I/O error 19502
Mon Oct 19 10:00:16 2009
ARC0: Closing local archive destination LOG_ARCHIVE_DEST_1:
'/oracle/admin/SNM/arch/arch_1_393_668727286.arc' (error
19502)
(SNM)

yes it is the production server.
Also the arch folder contains 2 GB file - arc file....
Does disable of archival will solve the issue?
I am try to clear the space or move to some other location..But the thing is my application files is of 3 to 4 GB.remaining thing is of dbf files.
6564 drwxr-x--- 2 oracle oinstall 512 Oct 21 2008 .
6563 drwxr-x--- 3 oracle oinstall 512 Oct 21 2008 ..
6568 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control01.ctl
6569 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control02.ctl
6570 -rw-r----- 1 oracle oinstall 7061504 Sep 30 11:58 control03.ctl
9283 -rw-r----- 1 oracle oinstall 5128192 Sep 30 10:21 mfxpima.dbf
6600 -rw-r----- 1 oracle oinstall 17179877376 Sep 30 11:50 muse0.dbf
6572 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 08:10 redo01.log
6573 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 10:16 redo02.log
6574 -rw-r----- 1 oracle oinstall 1073742336 Sep 30 11:58 redo03.log
6578 -rw-r----- 1 oracle oinstall 19293806592 Sep 30 11:58 sysaux01.dbf
6576 -rw-r----- 1 oracle oinstall 1698701312 Sep 30 11:56 system01.dbf
6579 -rw-r----- 1 oracle oinstall 2147491840 Sep 30 11:04 temp01.dbf
6577 -rw-r----- 1 oracle oinstall 4084211712 Sep 30 11:58 undotbs01.dbf
6580 -rw-r----- 1 oracle oinstall 5251072 Sep 30 10:21 users01.dbf
What as to be done....in this case....
Help me out...
I have no other option ....
SRinivasan

Manual archiving of redo log files....

Hi ,
If the database is running in NOARCHIVELOG mode , is it possible to archive the redo log files manually.... and how..????
Note: I use Oracle 10g v.2
Many thanks,
Simon

Having issued the command , i noticed that the USE_DB_RECOVERY_FILE_DEST is the destination of LOG_ARCHIVE_DEST_10:
SQL> select dest_id,dest_name,status,destination from V$ARCHIVE_DEST;
   DEST_ID DEST_NAME                                                                        STATUS    DESTINATION
         1 LOG_ARCHIVE_DEST_1                                                               VALID     C:\oracle\product\10.2.0\flash_recovery_area\EPESY\ARCHIVELOG\
         2 LOG_ARCHIVE_DEST_2                                                               INACTIVE
         3 LOG_ARCHIVE_DEST_3                                                               INACTIVE
         4 LOG_ARCHIVE_DEST_4                                                               INACTIVE
         5 LOG_ARCHIVE_DEST_5                                                               INACTIVE
         6 LOG_ARCHIVE_DEST_6                                                               INACTIVE
         7 LOG_ARCHIVE_DEST_7                                                               INACTIVE
         8 LOG_ARCHIVE_DEST_8                                                               INACTIVE
         9 LOG_ARCHIVE_DEST_9                                                               INACTIVE
        10 LOG_ARCHIVE_DEST_10                                                              VALID     USE_DB_RECOVERY_FILE_DESTBut... i have set the LOG_ARCHIVE_DEST parameter not ...._10.
How the system will point to the directory i've set in my previous alter system command...- when i use the archive log list???
Many thanks,
Simon

Archiver is unable to archive a redo log because the output device is full

Dear Experts,
When I logged to EM of my DB 11g R2. I found the following:
- Database Instance Status : Down
- Details
The instance has been terminated by a database process because of a fatal internal condition, or a critical background process was killed by the user.
Archiver is unable to archive a redo log because the output device is full or unavailable.
- Agent Connection to Instance
Status: Failed
Details: ORA-01034: ORACLE not available
Thank you in advance for any help you provide
Best Regards

mahmoudrabie wrote:
Thank you 919294
I was root not oracle and when I switch to oracle (which is member of dba group), the I ran
rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Mar 7 13:27:06 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
then as friends suggested
RMAN> backup archivelog all delete input;
Starting backup at 07-MAR-12
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/07/2012 13:28:00
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directorycheck the connection
connected to target database (not started)*so first startup the databaseto mount and then perform the operation
--neeraj

How do I manually archive 1 redo log at a time?

The database is configured in archive mode, but automatic archiving is turned off.
For both Oracle 901 and 920 on Windows, when I try to manually archive a single redo log, the database
archives as many logs as it can up to the log just before the current log:
For example:
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
6 rows selected.
SQL> alter system archive log next;
System altered.
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
See - instead of only 1 log being archive, 4 of them were. Oracle behaves the same way if I use the "sequence" option:
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
6 rows selected.
SQL> alter system archive log next;
System altered.
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
Is there some default system configuration property telling Oracle to archive as many logs as it can?
Thanks,
DGR

Thanks Yoann (and Syed Jaffar Jaffar Hussain too),
but I don't have a problem finding the group to archive or executing the alter system archive log command.
My problem is that Oracle doesn't work as I expect it.
This comes from the Oracle 9.2 online doc:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_23a.htm#2053642
"Specify SEQUENCE to manually archive the online redo log file group identified by the log sequence number integer in the specified thread."
This implies that Oracle will only archive the log group identified by the log sequence number I specify in the alter system archive log sequence statement. However, Oracle is archiving almost all of the log groups (see my first post for an example).
This appears to be a bug, unless there is some other system parameter that is configured (by default) to allow Oracle to archive as many log groups as possible.
As to the reason why - it is an application requirement. The Oracle db must be in archive mode, automatic archiving must be disabled and the application must control online redo log archiving.
DGR

Standby Database fails to read dictionary from redo log

hi,
I am attempting to create a Logical standby database on same machine as the primary database. I have executed the steps outlined in Oracle Documentation several times, but end up with the same error. Detailes of setup and error are provided below. Please help. Thanks.
==========
OS: REdhat 8 (2.4.18-14)
RDBMS: Oracle EE Server 9.2.0.3.0
primary db init details:
*.log_archive_dest_1='LOCATION=/usr3/oracle/admin/lbsp/archive/ MANDATORY'
*.log_archive_dest_2='SERVICE=STDBY'
standby db init details:
log_archive_dest_1='LOCATION=/usr3/oracle/admin/stdby/archive/'
standby_archive_dest='/usr3/oracle/admin/lbsp/archive_pdb/'
Standby alert log file (tail)
LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
Sun Jul 13 11:37:20 2003
Errors in file /usr3/oracle/admin/stdby/bdump/stdby_lsp0_13691.trc:
ORA-01332: internal Logminer Dictionary error
LSP process trace file:
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 18
Unix process pid: 13691, image: oracle@prabhu (LSP0)
*** 2003-07-13 11:37:19.972
*** SESSION ID:(12.165) 2003-07-13 11:37:19.970
<krvrd.c:krvrdfdm>: DDL or Dict mine error exit. 384<krvrd.c:krvrdids>: Failed to mine dictionary. flgs 180
knahcapplymain: encountered error=1332
*** 2003-07-13 11:37:20.217
ksedmp: internal or fatal error
. (memory dump)
KNACDMP: Unassigned txns = { }
KNACDMP: *******************************************************
error 1332 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01332: internal Logminer Dictionary error
another trace file created by error is: stdby_p001_13695.trc
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 20
Unix process pid: 13695, image: oracle@prabhu (P001)
*** 2003-07-13 11:37:19.961
*** SESSION ID:(22.8) 2003-07-13 11:37:19.908
krvxmrs: Leaving by exception: 604
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
ORA-06512: at line 1
there are no errors anywhere during the creation, mounting or opening of standby database. After the initial log register, any log switch on primary is communicated to standby and visible in DBA_LOGSTDBY_LOG. Also, archived logs from primary are successfuly copied by system to directory pointed by standby db's standby_archive_dest parameter.
I noticed, somehow everytime I issue "ALTER DATABASE START LOGICAL STANDBY APPLY" command the procedures and packages related to logmnr get invalid. I compile them and again after "APPLY" they become invalid.
Invalid object list:
OBJECT_TYPE OBJECT_NAME
VIEW DBA_LOGSTDBY_PROGRESS
PACKAGE BODY DBMS_INTERNAL_LOGSTDBY
PACKAGE BODY DBMS_STREAMS_ADM_UTL
VIEW LOGMNR_DICT
PACKAGE BODY LOGMNR_DICT_CACHE
PROCEDURE LOGMNR_GTLO3
PROCEDURE LOGMNR_KRVRDA_TEST_APPLY
Anybody point out what I am doing wrong. Thanks for the help

ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
post from standby:-
SQL> select name, state From v$asm_diskgroup;
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privilegesPost from primary & standby
SQL> select * from v$pwfile_users;
User Profile for 919131
919131
Handle:     919131
Status Level:     Newbie
Registered:     Mar 6, 2012
Total Posts:     16
Total Questions:     8 (8 unresolved)
OTN failed 100% to help you, then why you posted another question?
First close all your old answered threads and then better continue your updates in your thread.
Edited by: CKPT on Jul 9, 2012 11:45 AM

GoldenGate Extract Process will not read from redo log with manual help

Here is my issue.
I have GoldenGate replication successfully setup one-way from 1 Source to Many Targets. There is 1 source extract on the DB and many pumps that push the trail file data to the Targets. Replication does work but after manual help with starting up the Source Extract process.
If I execute the command:
GGSCI> alter extract <source extract name> begin now
GGSCI> view report <source extract name>
The extract starts and reads the source trail file but will not process data, I continually see in the ggserr.log file "OGG-01515: Positioning to begin time MMM DD, YYYY, HH:MM:SS" The date and time are irrevelant for this problem.
When I see this, I SQ*Plus into the database and look in the v$log table for the current log and sequence #.
I return to GGSCI and issue the following command:
GGSCI> alter extract <source extract name> thread 1 extseqno <sequence # from v$log query>
GGSCI> start <source extract name>
It then works as expected. Why is this so? I thought the alter extract <source extract name> begin now would do the same output.
We do use ASM but like I said when I issue the:
GGSCI> alter extract <source extract name> thread 1 extseqno <sequence # from v$log query>
It works like it should.
Very weird.
- Jason

Yes, supplemental logging is enabled on both the source and the targets, but why would supplemental logging on the targets have any affect on why the Source Extract on the source can't read from the source redo log?
This is not a RAC database, rather single-instance with one thread. Also, we are using DBLOGREADER functionality as it is an 11.2.0.3 database.
My issue is simply, when I start the source extract from being down, meaning it isn't running, I issue this command:
alter <source extract> begin now
start <source extract>
view report <source extract>
OGG-01515 Positioning to begin time <today's date and time> ie Mar 4, 2013, 3:26:39 PM. (this is repeated over and over and over)
If I perform a
info <source extract> detail---> I see the following:
Log Read Checkpoint Oracle Redo Logs 2013-03-04 15:26:39 Thread 1, Seqno 0, RBA 0 (why is it showing 0, becuase it can't read the redo, WHY NOT?)
Extract Source BEGIN END
Not Available <today's date> <today's date> (repeat....)
However, if I retreive the Redo Log number and I issue:
alter spe thread 1 extseqno (redo log sequence #)
start spe.
Then it works okay. I have to manually tell it what redo log to begin reading from. Why?
- Jason
Edited by: 924317 on Mar 4, 2013 9:03 AM

Cannot read Redo log

Hi,
We have a site which is used for replication.
At this site we had a capture,propogate and the apply process.
Because of some errors we dropped the capture and propogate process.
We also droppeed the streams queue.
Then we created a new Capture and Propogate process as well as
a new streams queue.
When we start the capture process then the process gets aborted.
When we see the dump file we get the following errors.
It says that you cannot read from redo log
*** 2003-02-07 22:01:23.000
*** SESSION ID:(22.16) 2003-02-07 22:01:23.000
ORA-00333: redo log read error block 131074 count 8192
ORA-00334: archived log: 'E:\ORACLE\ORCL92\RDBMS\ARC00029.001'
ORA-27070: skgfdisp: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
ORA-00333: redo log read error block 131074 count 8192
ORA-00334: archived log: 'E:\ORACLE\ORCL92\RDBMS\ARC00029.001'
ORA-27091: skgfqio: unable to queue I/O
ORA-27070: skgfdisp: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 23) Data error (cyclic redundancy check).

OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 23) Data error (cyclic redundancy check).
These errors indicate that the file is unreadable from the OS point of view.

Logmnr/capure error b'coz of corruption of redo log block

Hi,
We all know that capture process reads the REDO entries from redo log files or archived log files. Therefore we need to ahev db in ARCHIVELOG mode.
In alert log file, I found error saying :
Creating archive destination LOG_ARCHIVE_DEST_1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
ARC0: Log corruption near block 66922 change 0 time ?
ARC0: All Archive destinations made inactive due to error 354
Fri Apr 04 12:57:44 2003
Errors in file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
As a normal practice, we do have multiplexing of redo log files at diff location, but even that second copy of redo log is of no use to recover the redo log. This explains redo log could not be archived, since it can't be read. Same is true even for Logmnr process, it could not read the redo log file and it failed. Now, we have wae to recover from this situation (as far as DB is concern, not Stream Replication), since the shutdown after this error was IMMEDIATE causing checkpoing, and rollback/rollforward is not required during system startup. (No instance recovery) We can make db NOARCHIVELOG mode, drop that particular group, and create new one, and turn db to ARCHIVELOG mode This will certainly serve the purpose as far as consistency of DB is concern.
Here is a catch for Stream Replication. The redo log that got corrupted must be having few transaction which are not being archived, and each will be having corresponding SCN. Now, Capture Process read the info sequentially in order of SCN. Few transaction are now missed, and Capture process can't jump to next SCN skipping few SCN in between. So, we have to re-instantiate the objects on the another system which has no erros, and start working on it. My botheration is what will happen to those missed transaction on the another database. It's absolete loss of the data. In development I can manage that. But in real time Production stage, this is a critical situation. How to recover from this situation to get back the corrupted info from redo log ?
I have not dropped any of the log group yet. B'coz I would like to recover from this situation without LOSS of data.
Thanx, & regards,
Kamlesh Chaudhary
Content of trace files :
Dump file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc
Fri Apr 04 12:57:31 2003
ORACLE V9.2.0.2.1 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.2.0 - Production
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Instance name: trishul
Redo thread mounted by this instance: 1
Oracle process number: 16
Windows thread id: 1724, image: ORACLE.EXE
*** SESSION ID:(13.1) 2003-04-04 12:57:31.000
- Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION02\1_36.ARC'
- Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
*** 2003-04-04 12:57:44.000
ARC0: All Archive destinations made inactive due to error 354
*** 2003-04-04 12:57:44.000
kcrrfail: dest:2 err:354 force:0
*** 2003-04-04 12:57:44.000
kcrrfail: dest:1 err:354 force:0
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
*** 2003-04-04 12:57:44.000
ARC0: Archiving not possible: error count exceeded
ORA-16038: log 2 sequence# 36 cannot be archived
ORA-00354: corrupt redo log block header
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
ORA-16014: log 2 sequence# 36 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG
Dump file e:\oracle\admin\repf\udump\trishul_cp01_2048.trc
Fri Apr 04 12:57:27 2003
ORACLE V9.2.0.2.1 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.2.0 - Production
Windows 2000 Version 5.0 Service Pack 2, CPU type 586
Instance name: trishul
Redo thread mounted by this instance: 1
Oracle process number: 30
Windows thread id: 2048, image: ORACLE.EXE (CP01)
*** 2003-04-04 12:57:28.000
*** SESSION ID:(27.42) 2003-04-04 12:57:27.000
TLCR process death detected. Shutting down TLCR
error 1280 in STREAMS process
ORA-01280: Fatal LogMiner Error.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01280: Fatal LogMiner Error
**********************

I have the similar problem - I am using Steams environment, and have got this
"ORA-00353: log corruption near block" errors in the alert.log file
during capture the changes on the primary database, and Capture
process became aborted after that.
Was that transactions lost, or after i've started the Capture process
again the were captured and send to the target database?
Have anyone solved that problem?
Can you help me with it?

Redo log and Disk Full

hi
all
i'm new oracle DBA. i had one problem is
my Database is in archive mode. now redo log is available but not archive and my disk is full. so i couldn't open my Database what i have to do next step please help me...
Thanks in advance
Dharmesh
null

Take a proper copy of all the archived log files from the archive destination to some backup media like tape(for future recoverability) and delete them off from the disk to avail for space on the disk.
You will then be able to open your DB and proper archiving will take place.
What is happening?
The ARCHiver process is finding no space on the disk to archive the redo log files and thus Oracle stops doing any further action since it is in archive log mode.

RMAN x Online redo logs - doubt

When using RMAN's online hot backup, RMAN does not back up the online redo logs, does it?
Is there a way to do that?

The online redo logs files are never backed up by RMAN or any hot backup method.
The online redo logs files contain the latest data or redo generated by the database.(The data comes from redo log buffer written by LGWR).
The contents of the current redo logs are not archived until a log switch occurs.
This means if all your members in a redo log group fails, you would lose the latest information. So its best practice to invoke log switch before starting archivelog backup.

Polling on a practice for REDO logs

I would like to do a poll on the below security practice because it seemed not commonly deployed. If this practice is done in your company for the core databases, could you please reply to my posting and state your industry, DBA strength and total number of employees? Will collate the results later.
Previous posting 14/4/04:
Can the archive and redo logs be maintained in a way such that no one administrator (sys ad or DBA) will have access to all copies of logs? This is to prevent any disgrunted party to delete the logs and render the point-in-time data recovery impossible. What is the most common way used to achieve this? Thanks for reply:-)
(I am thinking of writing the logs to 2 servers, inwhich one server is fully owned and not accessible to the SysAd)

Are you trying to simultaneously use the Data Guard Broker and issue commands in SQL*Plus?
If so this does not work: Choose one tool and stick with it.

Why not use Redo log for consistent read

Oracle 11.1.0.7:
This might be a stupid question.
As I understand if a select was issued at 7:00 AM and the data that select is going to read has changed at 7:10 AM even then Oracle will return the data that existed at 7:00 AM. And for this Oracle needs the data in Undo segments.
My question is since redo also has past and current information why can't redo logs be used to retreive that information? Why is undo required when redo already has all that information.

user628400 wrote:
Thanks. I get that piece but isn't it the same problem with UNDO? It's written as it expires and there is no guranteee until we specifically ask oracle to gurantee the UNDO retention? I guess I am trying to understand that UNDO was created for effeciency purposes so that there is less performance overhead as compared to reading and writing from redo.And this also you said,
>
If data was changed to 100 to 200 wouldn't both the values be there in redo logs. As I understand:
1. Insert row with value 100 at 7:00 AM and commit. 100 will be writen to redo log
2. update row to 200 at 8:00 AM and commit. 200 will be written to redo log
So in essence 100 and 200 both are there in the redo logs and if select was issued at 7:00 data can be read from redo log too. Please correct me if I am understanding it incorrectly.I guess you didnt understand the explaination that I did. Its not the old data that is kept. Its the changed vector of Undo that is kept which is useful to "recover" it when its gone but not useful as such for a select statement. Whereas in an Undo block, the actual value is kept. You must remember that its still a block only which can contain data just like your normal block which may contain a table like EMP. So its not 100,200 but the change vectors of these things which is useful to recover the transaction based on their SCN numbers and would be read in that order as well. And to read the data from Undo, its quite simple for oracle to do so using an Undo block as the transaction table which holds the entry for the transaction, knows where the old data is kept in the Undo Segment. You may have seen XIDSEQ, XIDUSN, XIDSLOT in the tranaction id which are nothing but the information that where the undo data is kept. And to read it, unlke redo, undo plays a good role.
About the expiry of Undo, you must know that only INACTIVE Undo extents are marked for expiry. The Active Extents which are having an ongoing tranaction records, are never marked for it. You can come back after a lifetime and if undo is there, your old data would be kept safe by oracle since its useful for the multiversioning. Undo Retention is to keep the old data after commit, something which you need not to do if you are on 11g and using Total Recall feature!
HTH
Aman....

Does Redo Log include CLOB Columns Blocks?

Hi All,
Please help me in understanding how oracle handle redo logs on ENABLE IN ROW STORAGE CLOB's. How redo log behave on table with DISABLE IN ROW STORAGE ?
for following table if I update column other than D_CLOB does Redo log stores the D_CLOB column blocks as well. Is there any way to find if D_CLOB column blocks are included/excluded from redo log.
create table T
D_INT INTEGER,
D_CHAR CHAR(30),
D_DATE DATE,
D_CLOB CLOB
I performed following test but give no indication whether blocks of D_Clob Columns is inculded or not ..
SQL> update t
2 set d_char='Testing'
3 where rownum<500;
499 rows updated
SQL> commit;
Commit complete
SQL> select A.name,(b.value)/(1024*1024) MB
2 from v$statname a, v$mystat b
3 where a.statistic#=b.statistic#
4 and a.name='redo size'
5 /
NAME MB
redo size 5.59245300

I found this information for the Oracle Guru "Burleson", maybe that helps : http://www.dba-oracle.com/t_logging_clob_blob_lob.htm

How to damage online redo log for simulation

Dear All,
Kindly please help to inform me, is there any way to damage online redo log from database level (not from OS command like dd) ?
I need to do it for test case to enable db_block_checking and db_block_checksum (set both parameter to TRUE).
Is those parameter will help from redo log corruption ? that's why, i want to prove it.
Thanks
Anthony

user12215770 wrote:
My purpose is i want to verify that the db_block_checking and db_block_checksum can avoid redo corruption (the corruption caused by process in the database).Redo corruption could also occur due to other issues as http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams049.htm#REFRN10030 says:
>
Checksums allow Oracle to detect corruption caused by underlying disks, storage systems, or I/O systems. If set to FULL, DB_BLOCK_CHECKSUM also catches in-memory corruptions and stops them from making it to the disk.
>
You could try to use ORADEBUG POKE command to write directly in the SGA if you know how to find log buffer blocks ... About ORADEBUG please read http://www.juliandyke.com/Diagnostics/Tools/ORADEBUG/ORADEBUG.html.

Archive from redo log

Similar Messages

Maybe you are looking for