Note to Newbies: Know when it's time to call Oracle Support
Whilst I love the forums and think they are a great place to go for help and advice, there are times when they are not the best medium for support and this was one of them.
Forum questions are answered by volunteers, people who have day jobs to do themselves, that are happy to share their experience and help out others with queries. That’s why you will often see people getting flamed for posting subject titles with ‘URGENT’ or ‘PLEASE HELP NOW’.
In this thread there were a lot of people wiling to help, but with the OP seemingly not fully understanding some of the responses and even admitting in one post that they were ‘in a panic’ the confusion led to the problem being made worse.
If you’ve screwed up production and are in a panic, there’s a good chance that you may not have explained the issue clearly. Responses can only be given based on the information that you have provided and if that is not accurate, or you misread some of the instructions, then you could very quickly end up in an even bigger mess.
It’s too easy to say ‘don’t panic’.
I’ll admit that I’ve experienced that awful feeling in the pit of your stomach when you realise you have done something you shouldn’t have done, especially in production. I’m sure many others have too. But panic is generally what makes things worse (this especially applies to my diving as well as DBA work!).
Instead, take a deep breath and put in that call to Oracle Support.
The last post in the thread pretty much sums up the best response:
My first advice would have been:
Shutdown both databases and take a cold backup of everything if you have the time & space for that.
Contact Oracle Support!
Wait patiently for their advice and do not simply everything anybody tells you over the internet !
Unfortunately, the ‘Too late now for that’ also rings true and I just hope that the OP was able to get this resolved.