Re: Oracle DB Took a HIT

From: <asprusch_at_my-dejanews.com>
Date: Thu, 30 Jul 1998 11:00:09 GMT
Message-ID: <6ppjnq$faq$1@nnrp1.dejanews.com>

Try the command
alter session set events '10231 trace name context forever, level 10' This probably allows you to export your current data.

Hope this will help,
Andreas Prusch

In article <6pl272$fac$1_at_mawar.singnet.com.sg>, "Leonis" <chong01_at_singnet.com.sg> wrote:
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0020_01BDBA91.593F8040
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> 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.=20
> Stan Novinsky wrote in message <35B87543.98A68225_at_jhuapl.edu>...
> We are running Oracle 7.1 on an Alpha 8400 running OpenVMS 6.2.=20
> Two days ago, we took a power hit. Although the computer did not =
> crash, the DB took a hit.=20
> 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:=20
> =20
> _____=20
> =20
> PL/S=20
> Parallel server mode inactive=20
> Proc: 0x224 BATCH_1 User: [350,000] ORACLE7 Term:=20
> Image: APL1SD$DRA4:[ORACLE.V715.RDBMS]SQLDBA.EXE;9=20
> Enqueue Quota: 4000=20
> vsnsql=3Da vsnxtr=3D3=20
> cpu ALPH 80000000 vms V6.2 not clustered with 0 nodes=20
> scsnd: APL1SD , ndname: APL1SD, sys$node APL1SD::=20
> cpuid 80 rev 044C0000000000000000000C archflg 3C000=20
> hwmdl: 1100 hwnm: AlphaServer 8400 Model 5/300 cpus: FFFFFFFF cpush: =
> 0 active: 2, av=20
> locktbl size 30000 max 65535 resource hash size 2048=20
> 31-DEC-1999 21:55:51.35:=20
> =20
> *** SESSION ID:(6.1)=20
> =20
> ***=20
> Corrupt block=3D70252ac file=3D7. blocknum=3D152236. found during =
> media/instance recovery=20
> on disk type=3D6. ver=3D1. dba=3D70252ac inc=3D1f9 seq=3D601 =
> incseq=3D1f905fc=20
> =20
> ***=20
> Corrupt block=3D6026e5f file=3D6. blocknum=3D159327. found during =
> media/instance recovery=20
> on disk type=3D6. ver=3D1. dba=3D6026e5f inc=3D3b8 seq=3Dac =
> incseq=3D3b800ab=20
> =20
> ____________=20
> =20
> 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.=20
> =20
> Thanks=20
> =20
> Stan_Novinsky_at_JHUAPL.EDU=20
> =20
> =20
> =20
> =20
>
> ------=_NextPart_000_0020_01BDBA91.593F8040
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
> <HTML>
> <HEAD>
>
> <META content=3Dtext/html;charset=3Diso-8859-1 =
> http-equiv=3DContent-Type>
> <META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV>Hi, </DIV>
> <DIV> size=3D2> </DIV>
> <DIV>You don't have to recreate the =
> instance.</DIV>
> <DIV> </DIV>
> <DIV>Have you check for any  invalid =
> db objects=20
> ? Try to analyze the table and =
> indexes.</DIV>
> <DIV> </DIV>
> <DIV>you can also turn the =
> DB_BLOCK_CHECKSUM on and=20
> from the ora-01578 errors </DIV>
> <DIV>in the trace file to access the amount of =
> data/object=20
> corruption.</DIV>
> <DIV> </DIV>
> <DIV>If your can sacrifice the data =
> created/<FONT=20
> color=3D#000000>modified after the recovery. Then =
> just</DIV>
> <DIV>
> <DIV>Drop the affected data files and =
> recreate.=20
> Re-import using the backup before failure.</DIV>
> <DIV> </DIV>
> <DIV>Since your instance is not running =
> in archive=20
> log mode, that's the most you can do. </DIV></DIV>
> <BLOCKQUOTE=20
> style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
> 5px">
> <DIV>Stan Novinsky<STAN_NOVINSKY_at_JHUAPL.EDU> wrote in message <<A =
>
> =
> href=3D"mailto:35B87543.98A68225_at_jhuapl.edu">35B87543.98A68225_at_jhuapl.edu=
> </A>>...</DIV>We=20
> are running Oracle 7.1 on an Alpha 8400 running OpenVMS 6.2. Two =
> days=20
> ago, we took a power hit.   Although the computer did not =
> crash,=20
> the DB took a hit.=20
> The DB came up but slow.  It is operational and running =
> without a=20
> problem except taht we found an error in one of log files pertaining =
> to a=20
> corrupt block.  I checked the .TRC files and found the =
> following:=20
> _____   <FONT=20
> size=3D-1>PL/S <FONT=20
> size=3D-1>Parallel server mode inactive <FONT=20
> face=3DArial,Helvetica>Proc: 0x224 BATCH_1 User: =
> [350,000]=20
> ORACLE7      Term: <FONT=20
> face=3DArial,Helvetica>Image:=20
> APL1SD$DRA4:[ORACLE.V715.RDBMS]SQLDBA.EXE;9 <FONT=20
> face=3DArial,Helvetica>Enqueue Quota: =
> 4000=20
> vsnsql=3Da =
> vsnxtr=3D3=20
> cpu ALPH 80000000 =
> vms=20
> V6.2     not clustered with 0 =
> nodes=20
> scsnd: APL1SD  =
> , ndname:=20
> APL1SD, sys$node APL1SD:: face=3DArial,Helvetica><FONT=20
> size=3D-1>cpuid 80 rev 044C0000000000000000000C archflg =
> 3C000=20
> hwmdl: 1100 hwnm: =
> AlphaServer=20
> 8400 Model 5/300 cpus: FFFFFFFF cpush: 0 active: 2, av =
>
> locktbl size 30000 =
> max 65535=20
> resource hash size 2048 face=3DArial,Helvetica><FONT=20
> size=3D-1>31-DEC-1999 21:55:51.35:<FONT=20
> face=3DArial,Helvetica>=20
> *** SESSION=20
> ID:(6.1)<FONT=20
> size=3D-1>=20
> *** =
> <FONT=20
> face=3DArial,Helvetica>Corrupt block=3D70252ac =
> file=3D7.=20
> blocknum=3D152236. found during media/instance =
> recovery=20
> on disk type=3D6. =
> ver=3D1.=20
> dba=3D70252ac inc=3D1f9 seq=3D601 =
> incseq=3D1f905fc<FONT=20
> face=3DArial,Helvetica>=20
> *** =
> <FONT=20
> face=3DArial,Helvetica>Corrupt block=3D6026e5f =
> file=3D6.=20
> blocknum=3D159327. found during media/instance =
> recovery=20
> on disk type=3D6. =
> ver=3D1.=20
> dba=3D6026e5f inc=3D3b8 seq=3Dac incseq=3D3b800ab
> face=3DArial,Helvetica>=20
> size=3D-1>____________<FONT=20
> face=3DArial,Helvetica>=20
> Is there a way to repair or remove the are with the corrupt block =
> other=20
> than rebuilding the DB.  We are not running archive mode.=20
> Thanks=20
> Stan_Novinsky_at_JHUAPL.EDU <FONT=20
> size=3D-1> =20
>   </BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_0020_01BDBA91.593F8040--
>
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Thu Jul 30 1998 - 06:00:09 CDT