Re: Cannot delete a database instance

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:<403cb566$0$10341$ed9e5944_at_reading.news.pipex.net>...
> "Edwinah63" <edwinah_at_customercare.com.au> wrote in message
> news:d714e824.0402242117.73dcfcb6_at_posting.google.com...
> > Hi everyone,
> >
> > i am trying to delete a database 'Assist'. i have:
> >
> > * oracle 9i
> > * win 2k
>
> > what do i need to check? how can i delete this bl**dy database?
>
> Thanks for the kind words. It is a bit invidious to name folk as there are a
> *lot* of helpful people here.
>
> To delete a database on win2k you should only need to
>
> stop the service
> run oradim -delete -sid <sid>
> delete all the files from disk.
>
> You might wish first to delete the database from listener.ora and restart
> the listener and tnsnames.ora as well. This will stop people from connecting
> to the database. to delete from OEM I *think* that you have to delete the
> node, carry out the database delete and the deletes from the listener, and
> rediscover the node. I suspect that there might be an easier way, but I am
> not familiar with it if so. If you have jobs and events registered against
> targets on the node you would need to deregister them first so it does
> become somewhat complex getting the order right.
>
> hope this helps

Regarding the OEM bit. The database is only listed in OEM because the Intelligent Agent "discovered" it. To discover it, it consults the Listener for details of what has been statically-declared in the SID_LIST section of the listener.ora. If the naughty database is removed from there, and the Listener is re-started, and if the Intelligent Agent is then re-started, too, you should be able to check the contents of ORACLE_HOME\network\agent\services.ora and find that the database has been quietly forgotten. It then requires only the Node - Refresh to have the contents of OEM itself fixed.

Niall however is correct that the existence of registered jobs or events might pose a problem, but I think you'll find that deleting all the ".q" files in the network\agent directory will sort that out.

Regards
HJR Received on Wed Feb 25 2004 - 17:58:32 CST