Yep, agreed.
Try using a different drive that has plenty of free space and do the tests
that I've outlined before...
eg:
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'F:\DBA\SNAPCF_XE.F';
And take an spfile backup - this should genereate a new snapshot
controlfile:
RMAN> backup current controlfile;
I'd also get the sysadmin to do hardware/os/firmware check of the server in
case this is just the tip of the iceberg... is there corruption in the
underlying hardware/storage/firmware etc.
And check the alert.log - have you got other issues as well?
Cheers,
Leng Burgess.
On Fri, Aug 17, 2018 at 8:38 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
wrote:
You may simply be out of space.
Sent from my iPad
On Aug 16, 2018, at 17:35, Jeff Chirco <backseatdba@xxxxxxxxx> wrote:
Yes I have 3 control files but this is not a control file, its the
snapshot control file. I have deleted this snapshot file and it recreates
it as corrupt. I am wondering which control file could be corrupt.
On Thu, Aug 16, 2018 at 1:19 PM Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
On 08/15/2018 07:21 PM, Jeff Chirco wrote:
I have an 10g XE database that is failing during rman backup.
ORA-19624: operation failed, retry possible
ORA-19599: block number 10014 is corrupt in control file
C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\SNCFXE.ORA
I am not sure what SNCFXE.ORA is but I believe it is some snapshot
control file backup. Anybody know how to recover for this? Do I need
to do a full recovery from controlfile trace?
Hopefully, you have more than one control file? If you do, please copy
the correct one over the corrupt
C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\SNCFXE.ORA file.
Check your control_files parameter in the instance. If you don't have
more than one, try dumping it to trace (ALTER DATABASE BACKUP
CONTROLFILE TO TRACE AS 'C:\temp\ctlfile.sql' NORESETLOGS) then shutting
down the instance and re-creating the control file.
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
//www.freelists.org/webpage/oracle-l
