Synchronize Undo and Redo Files

[Fabão]

Friends, I administer a Banco Oracle 9.2.0.1.0. and the server that the same is turned off with the seat in the air. Now I'm having the error message when I try to open the bank:

Select all

Tue Jul 25 10:11:36 2006 
Recovery of Online Redo Log: Thread 1 Group 1 Seq 199 Reading mem 0 
Tue Jul 25 10:11:36 2006 
  Mem# 0 errs 0: G:\ORACLE\ORADATA\DBAND01\REDO01.LOG 
Recovery of Online Redo Log: Thread 1 Group 1 Seq 199 Reading mem 0 
  Mem# 0 errs 0: G:\ORACLE\ORADATA\DBAND01\REDO01.LOG 
Tue Jul 25 10:11:37 2006 
Errors in file g:\oracle\admin\dband01\udump\dband01_ora_4264.trc: 
ORA-00607: Internal error occurred while making a change to a data block 
ORA-00600: internal error code, arguments: [4193], [2235], [2272], [], [], [], [], []

so I got to understand, the Redo file is not synchronized with the UNDO. Would you like to know if someone has passed through this and if there is any way to force the synchronism between them? If I have said any nonsense, please correct me !!

vlw

[erthal]

Fabão,

Let us go to some important questions:

1. Was the bank in Archivelog mode?
2. Is it a production bank?
3. Have you put your resume on job offer sites? (joking)

ABS,
Gustavo.

[Fabão]

And Gustavo, the not good for all the answers !! This actually occurred in a development bank and I am taking advantage to try to recover to learn !! If you can help, I thank !!!

vlw

[erthal]

Fabão,

then the problem is lower. So you can start the bank with:

Select all

Startup Mount 
Alter Database Open ResetLogs

This will clear the contents of the redo files.

UNDO tablespace is not related to this error, since, as the name says, it is to undo (undo), and the redo files are to redo.

To exemplify the UNDO tablespace, it follows a practical example of this is when we use DML (INSERT, UPDATE, DELETE commands, for example).

When we make an Update or Delete, Oracle writes the old information on the Undo Tablespace. The new information is recorded in the Oracle blocks in their respective tables / segments / eRacle blocks. If we make a commit, Oracle will simply release the segments of Undo Tablespace, which will be taken advantage of in other transactions.

In the case of Insert, Oracle picks up the number of blocks in which the new information will be stored, and inserts the new information. After the Commit, the operation repeats and the Undo segments are released.

But instead of using the Commit, typing rollback, all the information stored in the Undo segments will be recorded on the new information.

is for what serves Undo Tablespace.

Redolog Files serve to redo a transaction as well as backup.

ABS,
Gustavo.
PS: A good consultation source is the address http://tahiti.oracle.com

[Fabão]

Vlw by tip, but it did not work, he returned the following message:

Select all

SQL> startup mount 
ORACLE instance started. 
 
Total System Global Area  135338868 bytes 
Fixed Size                   453492 bytes 
Variable Size             109051904 bytes 
Database Buffers           25165824 bytes 
Redo Buffers                 667648 bytes 
Database mounted. 
SQL> alter database open resetlogs 
  2  ; 
alter database open resetlogs 
* 
ERROR at line 1: 
ORA-01139: RESETLOGS option only valid after an incomplete database recovery

If you have another tip, send aí !!!

vlw

[erthal]

There,

What is the contents of the file

Select all

g:\oracle\admin\dband01\udump\dband01_ora_4264.trc?

if it is large, send a copy to gantal@commitconsultores.com.br

ABS,
Gustavo.