Re: drop database ... something I would have never thought I'd use

Mary,

there was widespread block corruption in several datafiles as well in the current redo log.
(I don't usually multiplex redo logs until after completing import/loads). it was a test run of a migration to 10g and was easier to drop and re-create the database.
well, attempt to re-create the database. as the RAID volumes went offline even during reformatting the filesystems ... no new database was created. I've done what I can do with the box as far as firmware/driver updates and running diagnostics. The issue will be escalated to a service call on Monday with the hardware vendor.

Had the database been worth salvaging, yes, a new undo tablespace would have been the way to go.

Paul

On Sat, 19 Feb 2005 04:54:40 -0800, Mary Bahrami <mbahrami_at_seattletimes.com> wrote:
> Would it have worked to create another undo TS, alter system set undo TS=x?, drop old one?
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Paul Drake
> Sent: Friday, February 18, 2005 5:25 PM
> To: oracle-l
> Subject: drop database ... something I would have never thought I'd use
>
> A failure of a hardware RAID controller (driver, perhaps) caused this
> (along with GBs of trace files):
>
> Fri Feb 18 20:15:45 2005
> Running with 1 strand for Non-Enterprise Edition
> Running without dynamic strand for Non-Enterprise Edition
> Fri Feb 18 20:15:45 2005
> Starting ORACLE instance (normal)
> Fri Feb 18 20:15:46 2005
> ORACLE Instance easdev (pid = 7) - Error 1578 encountered while
> recovering transaction (4, 2).
> Fri Feb 18 20:15:46 2005
> Errors in file d:\oracle\admin\easdev\bdump\easdev_smon_3400.trc:
> ORA-01578: ORACLE data block corrupted (file # 2, block # 20551)
> ORA-01110: data file 2: 'K:\ORACLE\ORADATA\FODDER\UNDOTBS01.DBF'
>
> Here is a fix for block corruption:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\ora-dba>d:
>
> D:\>set oracle_sid=fodder
>
> D:\>sqlplus /nolog
>
> SQL*Plus: Release 10.1.0.3.0 - Production on Fri Feb 18 20:15:26 2005
>
> Copyright (c) 1982, 2004, Oracle. All rights reserved.
>
> SQL> connect / as sysdba
> Connected to an idle instance.
> SQL> shutdown abort;
> ORACLE instance shut down.
> SQL> startup nomount;
> ORACLE instance started.
>
> Total System Global Area 612368384 bytes
> Fixed Size 790352 bytes
> Variable Size 174321840 bytes
> Database Buffers 436207616 bytes
> Redo Buffers 1048576 bytes
>
> SQL> alter database mount exclusive;
>
> Database altered.
>
> SQL> alter system enable restricted session;
>
> System altered.
>
> SQL> drop database;
>
> Database dropped.
>
> Disconnected from Oracle Database 10g Release 10.1.0.3.0 - Production
> SQL> quit
>
> Its quite amazing that a database, healthy or otherwise, can be
> dropped in under a minute."Gone in 60 seconds ..."
>
> I knew about the feature, I just thought that I would never use it.
> Obviously, this is not a production system.
> It is useful for testing backups, though.
>
> Paul
>
> --
> #/etc/init.d/init.cssd stop
> # f=ma, divide by 1, convert to moles.
> --
> http://www.freelists.org/webpage/oracle-l
>

-- 
#/etc/init.d/init.cssd stop
# f=ma, divide by 1, convert to moles.
--
http://www.freelists.org/webpage/oracle-l