|
-
Was your database in archivelog mode?
Make sure archivelogs are available and in the right location.
Make sure the first line of your control file reads like...
CREATE CONTROLFILE REUSE SET DATABASE "your_db_name" RESETLOGS ARCHIVELOG
sqlplus /nolog
conn sys as sysdba
--hit enter--
STARTUP NOMOUNT
@/your_path/your_control_file.sql
RECOVER DATABASE USING BACKUP CONTROLFILE until cancel
--apply your logs--
alter database open resetlogs;
Once your database is up, bounce it and be sure your alertlog is clean.
Put together a backup strategy.
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