Re: Is this a CAREER-ENDING mistake ? Accidently ran catalog.sql

From: Ana C. Dent <>
Date: Fri, 08 Aug 2008 01:34:58 GMT
Message-ID: <Xns9AF3BC929802Canacedenthotmailcom@>

"Ana C. Dent" <> wrote in news:Xns9AF3B986C264Eanacedenthotmailcom_at_69.16.185.247:

> Richard <> wrote in news:4340ee0a-1fdc-408c-a161-

>> There's no backup except there's an exp ...owner=sys,  can that be
>> used to restore ?  As I understand all system packages are owned by
>> sys, so the export of sys will restore it, I hope ?

> If you dodged this bullet I hope you'll learn a few things from it.
> 1) Objects owned by SYS can not be exported!
> 2) The database needs to be online & operational for import to work.
> Since SYS owns all internal DB objects & the DB needs to be open &
> online for import to function; thinking that you can import objects
> As a learning exercise after this dust settles.
> Take your dump file & invoke the import utility into a fresh,
> empty & disposable instance.
> Please use CUT & PASTE & post the results back here for posterity!

exp / file=sys.dmp log=sys.log owner=sys statistics=none

Export: Release - Production on Thu Aug 7 18:26:57 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

EXP-00056: ORACLE error 1017 encountered ORA-01017: invalid username/password; logon denied Username: / as sysdba

Connected to: Oracle Database 10g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP and Data Mining options Export done in US7ASCII character set and UTF8 NCHAR character set server uses AL32UTF8 character set (possible charset conversion)

About to export specified users ...

. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SYS 
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user SYS 
About to export SYS's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics

Export terminated successfully without warnings.

Where's the beef?
Lots of sizzle, but NO data!

IIRC, I tried this with either V7 or V8 & exp refused to do anything. I'm not sure this behavior is better or worse than earlier versions. It obvisouly is somewhat misleading at best & dangerous at worst.

Managing Oracle should only be done by trained professionals. Well meaning ameteurs can be dangerous; especially with incomplete or incorrect "knowledge".

You can lead some folks to knowledge but you can't always make them think!

HAND! Received on Thu Aug 07 2008 - 20:34:58 CDT

Original text of this message