Redo log mining.

Hello,
We've a database on which auditing having been activated. Some fraudulous acctivities have been operated on that database. The database was not running in archivelog mode. Now management wants information about those activities to be retrieved. The database is 9iR2.
1- Is it possible to get the trace of those fraudulous activities given the situation I described?
2- Some people suggest we exploit the content of the redos. Can anyone explain/tell the techniques that we can use to mine the redo log?
Thanks in advance.

Damorga,Erka, thanks for your replies. The team that was managing the databases wasn't a team of DBAs. They were rather System/network Administrators and we cannot blame them.
New structural chages are being made and the new team of DBAs was set up about 2 months ago. It's only at that moment that we realized the sinning I described above. We turned auditing and archiving on. The problem which brought me to post here happened long before we were hired. That means the content of the redos were flushed everytime they were full, but management is putting pressure on us to try and get a trace of those activities. I wanted to confirm that we cannot get those trace in the situation I presented.
Now I would like to know, how far in the past can logminer go? I mean, I know it works best in archivelog mode but if we apply logminer on archives that are like 4 months or more old, can we have significant information about everything that happended during that period?
Edited by: [email protected] on 7 févr. 2009 02:41

Similar Messages

Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

Recover database without controlfile and redo logs

Hi guys,
I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
-All controlfiles are missing
-All redo logs are missing
-I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
-The database is in archivelog mode
-The database was created with OMF (Oracle Managed Files)
So I have done this steps:
1) When the database was opened I rename all controlfiles and all redo logs
2) Shutdown Abort
3) I run the bkp_controlfile.sql, here I have a problem...
The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1:
'/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
Any suggestion to help me?
Thanks a lot.

Excelent! Thanks for your answers Markus and Hemant.
In conclusion...
- If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
- if we haven´t all redo logs availables, there are 2 situations:
1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
With all this I close this thread. Was very good experience.
If anyone would add something will be welcome.
Thanks for all
I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
ALL IN ONE SESSION*
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size                  1315224 bytes
Variable Size             377491048 bytes
Database Buffers          247463936 bytes
Redo Buffers                5644288 bytes
Database mounted.
Database opened.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> @/home/oracle/bkp_controlfile.sql
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size                  1315224 bytes
Variable Size             377491048 bytes
Database Buffers          247463936 bytes
Redo Buffers                5644288 bytes
Control file created.
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
ORA-00289: suggestion :
/u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
ORA-00280: change 398764 for thread 1 is in sequence #40
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> ALTER DATABASE OPEN RESETLOGS;
Database altered.
SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
Tablespace altered.
SQL>
ALL IN DIFERENT SESSIONS*
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
Database altered.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 631914496 bytes
Fixed Size                  1315224 bytes
Variable Size             377491048 bytes
Database Buffers          247463936 bytes
Redo Buffers                5644288 bytes
Database mounted.
SQL> ALTER DATABASE ARCHIVELOG;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> ALTER SYSTEM SWITCH LOGFILE;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> SHUTDOWN IMMEDIATE
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3

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?

Database not starting,REDO log file error?

My DB was working fine uptill last evening, when i restarted it for some DB task it showed me an error ..
ORA-00333: redo log read error block 57346 count 8192
I studied the alert log file & related trace file .... but could not conclude what to do ?? Can any one suggest me what could be the solution...
ORACLE 10g R2
Windows 2003 Server
Database in NOARCHIVELOG mode.
I don't have the recent backup.The one i have is 20 days old.
Alert Log file contents : -
Wed Jun 02 20:22:19 2010
Aborting crash recovery due to error 333
Wed Jun 02 20:22:19 2010
Errors in file e:\oracle\product\10.2.0\admin\ora10g\udump\ora10g_ora_140.trc:
ORA-00333: redo log read error block 57346 count 8192
ORA-333 signalled during: ALTER DATABASE OPEN...
Wed Jun 02 20:37:15 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Jun 02 20:43:53 2010
Shutting down instance: further logons disabled
Wed Jun 02 20:43:53 2010
Stopping background process CJQ0
Wed Jun 02 20:43:54 2010
Stopping background process MMNL
Wed Jun 02 20:43:55 2010
Stopping background process MMON
Wed Jun 02 20:43:56 2010
Shutting down instance (immediate)
License high water mark = 3
Wed Jun 02 20:43:56 2010
Stopping Job queue slave processes
Wed Jun 02 20:43:56 2010
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Wed Jun 02 20:43:58 2010
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Wed Jun 02 20:43:58 2010
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Trace file to read ora10g_ora_140.trc:-
Dump file e:\oracle\product\10.2.0\admin\ora10g\udump\ora10g_ora_140.trc
Wed Jun 02 20:22:18 2010
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 1
CPU                 : 2 - type 586, 1 Physical Cores
Process Affinity    : 0x00000000
Memory (Avail/Total): Ph:3527M/4094M, Ph+PgF:4386M/5973M, VA:800M/2047M
Instance name: ora10g
Redo thread mounted by this instance: 1
Oracle process number: 15
Windows thread id: 140, image: ORACLE.EXE (SHAD)
*** SERVICE NAME:() 2010-06-02 20:22:18.406
*** SESSION ID:(159.3) 2010-06-02 20:22:18.406
Successfully allocated 2 recovery slaves
Using 545 overflow buffers per recovery slave
Thread 1 checkpoint: logseq 14261, block 2, scn 86974094
cache-low rba: logseq 14260, block 4023
    on-disk rba: logseq 14262, block 3758, scn 86978396
start recovery at logseq 14261, block 2, scn 86974094
ORA-00333: redo log read error block 57346 count 8192
ORA-00312: online log 2 thread 1: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00333: redo log read error block 57346 count 8192
ORA-00312: online log 2 thread 1: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G\REDO02.LOG'
ORA-27091: unable to queue I/O
ORA-27070: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00333: redo log read error block 57346 count 8192
*** 2010-06-02 20:43:58.812
*** 2010-06-02 20:43:58.812 60680 kcrr.c
ARCH: Archival disabled due to shutdown: 1089
*** 2010-06-02 20:43:59.812 60680 kcrr.c
ARCH: Archival disabled due to shutdown: 1089

Hi,Aman this(following) may is not good way for opening database,but OP can try and open own database:
@ DBA4 you will see from following example how you can open your database.In your online log files was corrupted,therefore you have to do following step by step then you database will open.
SQL> alter database clear unarchived logfile group 2;
alter database clear unarchived logfile group 2
ERROR at line 1:
ORA-01624: log 2 needed for crash recovery of instance p (thread 1)
ORA-00312: online log 2 thread 1:
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\REDO02.LOG'
SQL> alter database backup controlfile to trace as 'D:\oracle\product\10.2.0\ora
data\P\c.txt';
Database altered.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 125829120 bytes
Fixed Size                  1288100 bytes
Variable Size              75499612 bytes
Database Buffers           41943040 bytes
Redo Buffers                7098368 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "P" RESETLOGS   ARCHIVELOG
2      MAXLOGFILES 16
3      MAXLOGMEMBERS 3
4      MAXDATAFILES 100
5      MAXINSTANCES 8
6      MAXLOGHISTORY 292
7 LOGFILE
8    GROUP 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\REDO01.LOG' SIZE 50M,
9    GROUP 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\REDO02.LOG' SIZE 50M,
10    GROUP 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\REDO03.LOG' SIZE 50M
11 DATAFILE
12    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\SYSTEM01.DBF',
13    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\UNDOTBS01.DBF',
14    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\SYSAUX01.DBF',
15    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\USERS01.DBF',
16    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\TS_TEST.ORA',
17    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\TEST.ORA',
18    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\TEST1.ORA'
19 CHARACTER SET WE8MSWIN1252;
Control file created.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\SYSTEM01.DBF'
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 2032832 generated at 06/03/2010 12:42:29 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\P\ARCHIVELOG\2010_06_03\O1_MF_1_87_
%U_.ARC
ORA-00280: change 2032832 for thread 1 is in sequence #87
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\SYSTEM01.DBF'
ORA-01112: media recovery not started
then add *_allow_resetlogs_corruption=true* in pfile then startup database with pfile as
SQL> startup mount pfile=D:\oracle\product\10.2.0\admin\P\pfile\init.ora.pr
ORACLE instance started.
Total System Global Area 125829120 bytes
Fixed Size                  1288100 bytes
Variable Size              62916700 bytes
Database Buffers           54525952 bytes
Redo Buffers                7098368 bytes
Database mounted.
SQL> recover;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 2032832 generated at 06/03/2010 12:42:29 needed for thread 1
ORA-00289: suggestion :
D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\P\ARCHIVELOG\2010_06_03\O1_MF_1_87_
%U_.ARC
ORA-00280: change 2032832 for thread 1 is in sequence #87
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\P\SYSTEM01.DBF'
ORA-01112: media recovery not started
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL>finally remove allowresetlogs_corruption=true parameter from pfile.

Redo Log Files - more than 12 per hour

Hello @all,
I have a problem with my redo log files. I get more than 12 switches per Hour. I have 3 Files with 5oM size. I increased the sitz to 15o M, but
I still have 12 switches per hour.
Do anyone know, what I did wrong?
Database:
Oracle 9i
Thanks
Martin

user9528362 wrote:
Hello @all,
yes I know, that 3 switches per hour are perfekt, but I had increased the Size from 5o M to 15oM already and the amount from switches, are not reduced.
So there must be something else, that causes the log switches.Martin,
As I said somewhere above too, 150meg is a tiny size if you are managing a production db. I have already mentioned that make your log file size to at least 500meg and than check. As for the high redo activity, only you can confirm that whether this has been started from now only or was happening before too? In anycase, for an active oltp, 500 to 1gb of redo log file size should be okay.
For the extra redo generation, you have been given link for mining log files using logminer. Try using it to see what is causing extra redo.
HTH
Aman....

Redo Log Resize

Hi Experts
i need to resize my online redo log size. at present its size 100Mb. can you plz guide me and give me the steps how i can accomplish this activity successfully
my DB Version is 10g(10.2.0.3) and O/S is RHEL AS 4.6
regards,

To changing size of online logfiles you need drop that and create with new size.But there you can not drop current and active log group.To avoiding this you can use alter system switch logfile and alter system checkpoint .Following example you will see that.
C:\Documents and Settings\Administrator>set ORACLE_SID=TEST
C:\Documents and Settings\Administrator>sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jul 29 16:42:04 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> select group||' - '||member from v$logfile;
select group||' - '||member from v$logfile
ERROR at line 1:
ORA-00936: missing expression
SQL> select group#||' - '||member from v$logfile;
GROUP#||'-'||MEMBER
1 - D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\REDO01.LOG
3 - D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\REDO03.LOG
2 - D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\REDO02.LOG
SQL> desc v$log;
Name                                      Null?    Type
GROUP#                                             NUMBER
THREAD#                                            NUMBER
SEQUENCE#                                          NUMBER
BYTES                                              NUMBER
MEMBERS                                            NUMBER
ARCHIVED                                           VARCHAR2(3)
STATUS                                             VARCHAR2(16)
FIRST_CHANGE#                                      NUMBER
FIRST_TIME                                         DATE
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
1 - INACTIVE
2 - INACTIVE
3 - CURRENT
SQL> alter database drop logfile group 1;
Database altered.
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
2 - INACTIVE
3 - CURRENT
SQL> alter database add logfile group 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\R
EDO_01.LOG' size 50M;
Database altered.
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
1 - UNUSED
2 - INACTIVE
3 - CURRENT
SQL> alter database drop logfile group 2;
Database altered.
SQL> alter database add logfile group 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\R
EDO_02.LOG' size 50M;
Database altered.
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
1 - UNUSED
2 - UNUSED
3 - CURRENT
SQL> alter system switch logfile;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
1 - ACTIVE
2 - CURRENT
3 - ACTIVE
SQL> alter system checkpoint;
System altered.
SQL> select group#||' - '||status from v$log;
GROUP#||'-'||STATUS
1 - INACTIVE
2 - CURRENT
3 - INACTIVE
SQL> alter database drop logfile group 3;
Database altered.
SQL> alter database add logfile group 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\R
EDO_03.LOG' size 50M;
Database altered.
SQL>

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

Select from .. as of - using archived redo logs - 10g

Hi,
I was under the impression I could issue a "Select from .. as of" statement back in time if I have the archived redo logs.
I've been searching for a while and cant find an answer.
My undo_management=AUTO, database is 10.2.0.1, the retention is the default of 900 seconds as I've never changed it.
I want to query a table as of 24 hours ago so I have all the archived redo logs from the last 48 hours in the correct directory
When is issue the following query
select * from supplier_codes AS OF TIMESTAMP
TO_TIMESTAMP('2009-08-11 10:01:00', 'YYYY-MM-DD HH24:MI:SS')
I get a snapshot to old ORA-01555 error. I guess that is because my retention is only 900 seconds but I thought the database should query the archive redo logs or have I got that totally wrong?!
My undo tablespace is set to AUTOEXTEND ON and MAXSIZE UNLIMITED so there should be no space issues
Any help would be greatly appreciated!
Thanks
Robert

If you want to go back 24 hours, you need to undo the changes...
See e.g. the app dev guide - fundamentals, chapter on Flashback features: [doc search|http://www.oracle.com/pls/db102/ranked?word=flashback&remark=federated_search].

How to disable write to redo log file in oracle7.3.4

in oracle 8, alter table no logged in redo log file like: alter table tablename nologging;
how to do this in oracle 7.3.4?
thanks.

user652965 wrote:
Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving.

Is There a Way to Run a Redo log for a Single Tablespace?

I'm still fairly new to Oracle. I've been reading up on the architecture and I am getting the hang of it. Actually, I have 2 questions.
1) My first question is..."Is there a way to run the redo log file...but to specify something so that it only applies to a single tablespace and it's related files?"
So, in a situation where, for some reason, only a single dbf file has become corrupted, I only have to worry about replaying the log for those transactions that affect the tablespace associated with that file.
2) Also, I would like to know if there is a query I can run from iSQLPlus that would allow me to view the datafiles that are associated with a tablespace.
Thanks

1) My first question is..."Is there a way to run the
redo log file...but to specify something so that it
only applies to a single tablespace and it's related
files?"
No You can't specify a redolog file to record the transaction entries for a particular tablespace.
In cas if a file gets corrupted.you need to apply all the archivelogs since the last backup plus the redologs to bring back the DB to consistent state.
>
2) Also, I would like to know if there is a query I
can run from iSQLPlus that would allow me to view the
datafiles that are associated with a tablespace.Select file_name,tablespace_name from dba_data_files will give you the
The above will give you the number of datafiles that a tablespace is made of.
In your case you have created the tablespace iwth one datafile.
Message was edited by:
Maran.E

Problem in creating database -Missing Redo log file

I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
My alert log file is
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:27 2013
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:38 2013
Setting recovery target incarnation to 2
Wed Nov 06 10:07:38 2013
Assigning activation ID 1876274518 (0x6fd5ad56)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
Successful open of redo thread 1
Wed Nov 06 10:07:38 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Nov 06 10:07:38 2013
SMON: enabling cache recovery
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc (incident=1345):
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
Wed Nov 06 10:07:46 2013
Trace dumping is performing id=[cdmp_20131106100746]
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Error 600 happened during db open, shutting down database
USER (ospid: 5424): terminating the instance due to error 600
Instance terminated by USER, pid = 5424
ORA-1092 signalled during: alter database "oracl" open resetlogs...
ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
Wed Nov 06 10:07:47 2013
ORA-1092 : opitsk aborting process
251,1 95%

>I am try to create a new database using DBCA
>Please help me to resolve this issue.My redo log file was missing
DROP and recreate the database. It is a *new* database without any data.
Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
Hemant K Chitale

Best way to move redo log from one disk group to another in ASM?

Hi All,
Our db is 10.2.0.3 RAC db. And database servers are window 2003 server.
We need to move more than 50 redo logs (some are regular and some are standby) which are not redundant from one disk group to another. Say we need to move from disk group 1 to 2. Here are the options we are thinking about but not sure which one is the best from easiness and safety prospective.
Thank you very much for your help in advance.
Shirley
Option 1:
1)     shutdown immediate
2)     copy log files from disk group 1 to disk group2 using RMAN (need to research on this)
3)     startup mount
4)     alter database rename file ….
5)     Open database open
6)     delete the redo files from disk group 1 in ASM (how?)
Option 2:
1)     create a set of redo log groups in disk group 2
2)     drop the redo log groups in disk group 1 when they are inactive and have been archived
3)     delete the redo files associated with those dropped groups from disk group 1 (how?) (According to Oracle menu: when you drop the redo log group the operating system files are not deleted and you need to manually delete those files)
Option 3:
1)     create a set of redo members in disk group 2 for each redo log group in disk group 1
2)     drop the redo log memebers in disk group 1
3)     delete the redo files from disk group 1 associated with the dropped members

Absolutely not, they are not even remotely similar concepts.
OMF: Oracle Managed Files. It is an RDMBS feature, no matter what your storage technology is, Oracle will take care of file naming and location, you only have to define the size of a file, and in the case of a tablespace on an OMF DB Configuration you only need to issue a command similar to this:
CREATE TABLESPACE <TSName>; So the OMF environment creates an autoextensible datafile at the predefined location with 100M by default as its initial size.
On ASM it should only be required to specify '+DGroupName' as the datafile or redo log file argument so it can be fully managed by ASM.
EMC. http://www.emc.com No further commens on it.
~ Madrid
http://hrivera99.blogspot.com

How to remove a redo log file

Hi Experts,
I want to remove a wrong redo log file from 10G R2 database in window.
how to do that without loss data?
my steps as
1. alter system switch logfile;
2. select * from v$log;
which ARC and sataus do I can drop redo log file based on above SQL
no archive and active status?
ALso Which account should I do above action?
fExamp, system account added redo log file, i only
can drop by system? how about sys?
Thanks help in detail steps
Jim
Edited by: user589812 on Dec 23, 2008 4:35 PM

Jim,
Check this link out for how to drop a redo log file
Make sure a redo log group is archived (if archiving is enabled) before dropping it. To see whether this has happened, use the V$LOG view.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#i1006489
SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
   GROUP# ARC STATUS
        1 YES ACTIVE
        2 NO CURRENT
        3 YES INACTIVE
        4 YES INACTIVE
Drop a redo log group with the SQL statement ALTER DATABASE with the DROP LOGFILE clause.
The following statement drops redo log group number 3:
ALTER DATABASE DROP LOGFILE GROUP 3;

What is a redo log file? can anyone explain in simple terms

I am confused between redo log file and physical datafile can anyone explain in simple terms
Thank u
Regards,
Vijay

See Overview of Physical Database Structures

Redo log mining.

Similar Messages

Maybe you are looking for