Corrupt control file? [message #534011] |
Fri, 02 December 2011 02:55 |
|
Rodge
Messages: 6 Registered: December 2011
|
Junior Member |
|
|
Hi all,
I've recently moved jobs and am doing a lot of the normal things getting familiar with my new company's databases.
I was checking through our production backup logs and came across something that looks a little funny. From the last two days backups, I see:
select completion_time, marked_corrupt, media_corrupt, logically_corrupt
from v$backup_datafile
where controlfile_type = 'B'
order by completion_time desc
COMPLETION_TIME MARKED_CORRUPT MEDIA_CORRUPT LOGICALLY_CORRUPT
01/12/2011 11:27:25 2011 1201 2
01/12/2011 11:26:18 0 0 0
01/12/2011 11:25:24 2011 1201 1
01/12/2011 11:15:56 2011 1201 0
01/12/2011 01:40:10 0 0 0
30/11/2011 11:23:48 2011 1130 2
30/11/2011 11:22:44 0 0 0
30/11/2011 11:21:56 2011 1130 1
30/11/2011 11:13:00 2011 1130 0
30/11/2011 01:41:01 0 0 0
The 01:40 record will come from our nightly command:
BACKUP INCREMENTAL LEVEL=0 FILESPERSET=20 FORMAT 'full_%d_%t_%s_%p'
DATABASE INCLUDE CURRENT CONTROLFILE
The 11AM records will come from the command:
BACKUP INCREMENTAL LEVEL=0 FORMAT 'ctl_%t_%s_%p' CURRENT CONTROLFILE;
(I know backups shouldn't still be running at 11am and we don't need level 0 backups every night, that's a seperate issue I'll be addressing! )
I see there's been a similar entry here in v$backup_datafile for all backups that there's records for.
The database is up and running just fine.
There are no unusual errors being reported by the database in OEM or the alert log.
I tried looking at both our control files (yes, should have 3 - something else I've listed to change!) with dbverify which showed no issues - though I'm not sure if this is designed to work with control files.
I'm just wondering whether I need to be concerned here?
If so, how could I confirm whether it's an issue with a specific controlfile (I'm assuming it's not an issue with the backup to tape itself, as it's reporting the same corruption every day)?
I'd obviously like to diagnose this now while the db is up and running, rather than at 4am some morning during a crash and finding out my backup control files are no good!
Thanks in advance for any help or opinions!
[Updated on: Fri, 02 December 2011 03:07] by Moderator Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|