Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Update 7.3.2 --> 7.3.4

Re: Update 7.3.2 --> 7.3.4

From: Hans-Jürgen Schmitz <hajueschmitz_at_gmx.de>
Date: Tue, 30 Nov 1999 12:09:09 +0100
Message-ID: <3843B055.5A53@gmx.de>


Jonathan Lewis wrote:
>
> This sounds like a software error on the block,
> although it would be useful to have seen the
> actual Oracle error.

It's a ORA 1115.

> Since the corrupted block is in the SOURCE$
> table, there is hope for your database.
>
> Don't do this without consulting your local
> Oracle help desk, but you should be able
> restrict the database to bare minimum activity.
> drop the source$ table and recreate it
> using a bit of code hacked from sql.bsq, and
> then run catalog.sql all over again.
>
> --
>
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> Hans-Jürgen Schmitz wrote in message <38424DCA.C6330246_at_gmx.de>...
> We did an update to 7.3.4 on a Novellserver (3.2) (Y2K).
>
> After that update the last sql catproc.sql failes in several statements.
> There is a block-read error in Block 2048 dbs1.ora (Tablespace system).
>
> A select statement on sys.source$ (which includes Block 2048) raises
> also that error.
>
> This error did not appear before the update (we proceeded it for several
> times).
>
> It is not a disk-error, because with a copy of dbs1.ora happens a
> filecompare. Moving it to another physical position on the disk results
> in the same error on the same Block.
>
> Any ideas?
>
> thank you Hans-Jürgen Schmitz
Received on Tue Nov 30 1999 - 05:09:09 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US