[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

06/10/2003 at 07:35AM PDT, ID: 20643126
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.6

alter database force open with _ALLOW_RESETLOGS_CORRUPTION = TRUE

Asked by mojope in Oracle Product Info

Tags: force, open, database, _allow_resetlogs_corruption, alter

This is a two-part question.

I have a partially restored database where I have some new, and some older datafiles.  Together I have them all.  No archivelogs, no anything.  This is the path I must take!

I have to do a force open of the database with _ALLOW_RESETLOGS_CORRUPTION = TRUE

This is ok, and I will have a inconsistent database afterwards.  However, there is not much data added in the database between the datafiles I have, perhaps nothing if I am real lucky.  Is it possible to make this inconsistent database consistent in some way afterwards, and then go through the database and check for concistency errors (added data in some tables and then remove it etc.)

If not, I have to export all tables, rebuild the database, import tables and rebuild indexes.  This is a rather complex database with lots of users/stored procedures/views etc. so the rebuild will take for ages.   Any short-cuts that can be taken here, for instance exporting out the build of the database in script format or something from the corrupt database?

This is urgent as the dabase is a production database and is down for the moment.


Thanks,

Morten
[+][-]06/10/03 09:14 AM, ID: 8692178

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Oracle Product Info
Tags: force, open, database, _allow_resetlogs_corruption, alter
Sign Up Now!
Solution Provided By: SDutta
Participating Experts: 1
Solution Grade: C
 
 
 
Loading Advertisement...
20091028-EE-VQP-85