Home » RDBMS Server » Backup & Recovery » Checking block corruption, why in alert it is saying Error in trace file (Oracle 10g 10.2.0.1 linux 32 bit)
Checking block corruption, why in alert it is saying Error in trace file [message #319178] Fri, 09 May 2008 04:56 Go to next message
MIFI
Messages: 256
Registered: February 2008
Location: U.K.
Senior Member
Hi,
I wanted to check block corruption using RMAN by following statement

backup validate check logical database;

when i executed the statement, following was the output

Starting backup at 09-MAY-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=91 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/app/oracle/oradata/test/users01.dbf
input datafile fno=00008 name=/u01/app/oracle/oradata/test/workflowuser
input datafile fno=00001 name=/u01/app/oracle/oradata/test/system01.dbf
input datafile fno=00003 name=/u01/app/oracle/oradata/test/sysaux01.dbf
input datafile fno=00010 name=/u01/app/oracle/oradata/test/ifan
input datafile fno=00002 name=/u01/app/oracle/oradata/test/undotbs01.dbf
input datafile fno=00007 name=/u01/app/oracle/oradata/test/taker
input datafile fno=00009 name=/u01/app/oracle/oradata/test/testing1
input datafile fno=00005 name=/u01/app/oracle/oradata/test/brokerdb
input datafile fno=00006 name=/u01/app/oracle/oradata/test/moneio
input datafile fno=00011 name=/u01/app/oracle/oradata/test/web1
input datafile fno=00012 name=/u01/app/oracle/oradata/test/e1
input datafile fno=00013 name=/u01/app/oracle/oradata/test/ind1
channel ORA_DISK_1: backup set complete, elapsed time: 00:06:57
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 09-MAY-08

and when i do the following query

select * from v$database_block_corruption in sqlplus

then there was no row

so it means there is no logical corruption, but when i am looking at alert log file it is giving following lines

Fri May 9 10:14:04 2008
Errors in file /u01/app/oracle/admin/test/udump/test_ora_6606.trc:
Fri May 9 10:14:04 2008
Errors in file /u01/app/oracle/admin/test/udump/test_ora_6606.trc:
Fri May 9 10:14:04 2008
Errors in file /u01/app/oracle/admin/test/udump/test_ora_6606.trc

and in above trace file following contents

/u01/app/oracle/admin/test4/udump/test_ora_6606.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: test
Release: 2.6.18-5-686
Version: #1 SMP Wed Oct 3 00:12:50 UTC 2007
Machine: i686
Instance name: test
Redo thread mounted by this instance: 1
Oracle process number: 61
Unix process pid: 6606, image: oracle@test (TNS V1-V3)

*** 2008-05-09 10:14:04.093
*** ACTION NAME:(0000040 STARTED19) 2008-05-09 10:14:04.071
*** MODULE NAME:(backup full datafile) 2008-05-09 10:14:04.071
*** SERVICE NAME:(SYS$USERS) 2008-05-09 10:14:04.071
*** SESSION ID:(91.40318) 2008-05-09 10:14:04.071

Is it normal, why the in alert file it is saying that Error in.

And it did not create any backupset in folder of flash recovery but in Enterprise manager it is showing last backup on 09-may-2008, why ?

Regards,

Re: Checking block corruption, why in alert it is saying Error in trace file [message #319277 is a reply to message #319178] Fri, 09 May 2008 10:00 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
I assume the error messages correspond with the time you did the VALIDATE? I appears to only be an informational message, however I do not get that message on my 10.2.0.1 on Linux database.

OEM is getting the information from V$BACKUP_SET.
Re: Checking block corruption, why in alert it is saying Error in trace file [message #319282 is a reply to message #319277] Fri, 09 May 2008 10:15 Go to previous messageGo to next message
MIFI
Messages: 256
Registered: February 2008
Location: U.K.
Senior Member
If i am not backing up my database by using RMAN and only using Export utlity to backup the database, how do i be able to get information in v$database_block_corruption view regarding Physical as well as Logical backup.


Re: Checking block corruption, why in alert it is saying Error in trace file [message #319284 is a reply to message #319282] Fri, 09 May 2008 10:17 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
I surely hope you are using more than export to "backup" your database. Export should be used as a supplement to a physical backup of your database.

If corruption exists, v$database_block_corruption will still be populated with the method you used above.
Re: Checking block corruption, why in alert it is saying Error in trace file [message #319288 is a reply to message #319284] Fri, 09 May 2008 10:45 Go to previous messageGo to next message
MIFI
Messages: 256
Registered: February 2008
Location: U.K.
Senior Member
I am not using RMAN because it is my Development database, secondly if i am not using RMAN Backup ,does it automatically check Physical corruption and insert values in v$Database_block_corruption
Re: Checking block corruption, why in alert it is saying Error in trace file [message #319290 is a reply to message #319288] Fri, 09 May 2008 10:58 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
Corruption may still be detected by the database without RMAN. These will be logged to the alert log. However, RMAN provides the ability to check for corruption (physical & logical) on demand and will also populate v$database_block_corruption.
Re: Checking block corruption, why in alert it is saying Error in trace file [message #319293 is a reply to message #319288] Fri, 09 May 2008 11:20 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
You can also use dbv (dbverify) for this.

Regards
Michel
Re: Checking block corruption, why in alert it is saying Error in trace file [message #349307 is a reply to message #319178] Fri, 19 September 2008 16:20 Go to previous message
empee
Messages: 1
Registered: September 2008
Junior Member
I've just hit the same problem and had a look on MetaLink. See note 335731.1

Apparently safe to ignore.

Empee
Previous Topic: Backup current controlfile
Next Topic: Script for Backup
Goto Forum:
  


Current Time: Sat Dec 03 12:13:50 CST 2016

Total time taken to generate the page: 0.09700 seconds