Re: Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Stephane Faroult
Kevin Bass wrote: > > I have attempted a full export and received the following message: > > [/u03] $ exp system/ full=y rows=y file=full.dmp > > Export: Release 8.0.5.0.0 - Production on Mon Dec 3 15:3:21 2001 > > (c) Copyright 1998 Oracle Corporation. All rights reserved. > > Connected to:

RE: Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Koivu, Lisa
Title: RE: Corrupted data blocks in tablespace SYSTEM Kevin, Try exporting your schema owners (code, tables, etc.) as a CYA.  When you recreate the db, you can import each schema separately.  A pain, but it will save you. Lisa -Original Message- From:   Kevin Bass [SMTP:[EMAIL

RE: Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Kevin Bass
I have attempted a full export and received the following message: [/u03] $ exp system/ full=y rows=y file=full.dmp Export: Release 8.0.5.0.0 - Production on Mon Dec 3 15:3:21 2001 (c) Copyright 1998 Oracle Corporation. All rights reserved. Connected to: Oracle8 Release 8.0.5.0.0 - Productio

Re: Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Stephane Faroult
> Kevin Bass wrote: > > I have just started a project and have encountered a database problem. > The previous DBA did not create any backup scripts or backup and > recovery plans. Is there a way to get around this problem without > re-creating the database? > > > When executing my script to get

Re: Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Riyaj_Shamsudeen
respond to ORACLE-L                 To:        Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>         cc:                 Subject:        Corrupted data blocks in tablespace SYSTEM I have just started a project and have encountered a database problem. The previous DBA did not create

Corrupted data blocks in tablespace SYSTEM

2001-12-03 Thread Kevin Bass
I have just started a project and have encountered a database problem. The previous DBA did not create any backup scripts or backup and recovery plans. Is there a way to get around this problem without re-creating the database?     When executing my script to get corrupted data block inform