Re: Update 7.3.2 --> 7.3.4

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Mon, 29 Nov 1999 10:29:48 -0000
Message-ID: <943871508.22339.0.nnrp-11.9e984b29@news.demon.co.uk>

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

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 Mon Nov 29 1999 - 04:29:48 CST