Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle DB Took a HIT
Hi,
You don't have to recreate the instance.
Have you check for any invalid db objects ? Try to analyze the table = and indexes.
you can also turn the DB_BLOCK_CHECKSUM on and from the ora-01578 errors =
in the trace file to access the amount of data/object corruption.
If your can sacrifice the data created/modified after the recovery. Then =
just
Drop the affected data files and recreate. Re-import using the backup =
before failure.
Since your instance is not running in archive log mode, that's the most =
you can do.
Stan Novinsky wrote in message <35B87543.98A68225_at_jhuapl.edu>...
We are running Oracle 7.1 on an Alpha 8400 running OpenVMS 6.2. Two days ago, we took a power hit. Although the computer did not = crash, the DB took a hit.
The DB came up but slow. It is operational and running without a = problem except taht we found an error in one of log files pertaining to = a corrupt block. I checked the .TRC files and found the following:
PL/S
Parallel server mode inactive
Proc: 0x224 BATCH_1 User: [350,000] ORACLE7 Term:
Image: APL1SD$DRA4:[ORACLE.V715.RDBMS]SQLDBA.EXE;9
Enqueue Quota: 4000
vsnsql=a vsnxtr=3
cpu ALPH 80000000 vms V6.2 not clustered with 0 nodes
scsnd: APL1SD , ndname: APL1SD, sys$node APL1SD::
cpuid 80 rev 044C0000000000000000000C archflg 3C000hwmdl: 1100 hwnm: AlphaServer 8400 Model 5/300 cpus: FFFFFFFF cpush: = 0 active: 2, av
locktbl size 30000 max 65535 resource hash size 2048 31-DEC-1999 21:55:51.35:
on disk type=6. ver=1. dba=70252ac inc=1f9 seq=601 = incseq=1f905fc
***
Corrupt block=6026e5f file=6. blocknum=159327. found during =
media/instance recovery
on disk type=6. ver=1. dba=6026e5f inc=3b8 seq=ac = incseq=3b800ab
Is there a way to repair or remove the are with the corrupt block = other than rebuilding the DB. We are not running archive mode.
Thanks
Stan_Novinsky_at_JHUAPL.EDU Received on Tue Jul 28 1998 - 12:36:46 CDT
![]() |
![]() |