|
-
I don't think you are going to be able to open the database in the current scenario. Your second "recover database" -issued after space issue, most certainly iniitated the recovery of the offending datafiles hence, big troubles.
I can't see any scenario other than starting from scratch.
Also, if you are planning to drop the unwanted tablespaces on target database you may want to use the FOREVER option on "skip tablespace" command.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote