Problem with BI file 
Author Message
 Problem with BI file

Hello!
I have a problem: we have two environments on our aix-system. 1 a 6.3f
and 1 a 7.3, what has happened is that a deveoper started the
6-database with version 7, discoverd what he'd done, deleted a .lk
file and restarted the 6-database with version 6. Now months later, we
stopped the system for maintenance and when tried to restart the
6-database we're unpleasantly surpised with the message that the .bi
file refers to a database last used on the day that the above error
was executed. Is the a way to fool the bi image file to refer to the
current database? Otherwise we lose a whole day's production.

I hope I have described the problem clearly as I'm not the
administrator!!
thanks for any input (even bad news!!)

Chris



Tue, 25 Sep 2001 03:00:00 GMT
 Problem with BI file


says...

Quote:
> Hello!
> I have a problem: we have two environments on our aix-system. 1 a 6.3f
> and 1 a 7.3, what has happened is that a deveoper started the
> 6-database with version 7, discoverd what he'd done, deleted a .lk
> file and restarted the 6-database with version 6. Now months later, we
> stopped the system for maintenance and when tried to restart the
> 6-database we're unpleasantly surpised with the message that the .bi
> file refers to a database last used on the day that the above error
> was executed. Is the a way to fool the bi image file to refer to the
> current database? Otherwise we lose a whole day's production.

> I hope I have described the problem clearly as I'm not the
> administrator!!
> thanks for any input (even bad news!!)

You're in trouble.

You can do a "mock index rebuild" to recover from the obvious symptoms
but you will lose data.  The problem is that you have no way to know what
data...  Your best option is to restore from backup.

Trust me, that really is the best thing to do.

If you don't trust me then use the -F option to force access to the
database (if you're lucky you'll only spend months cleaning up relational
integrity issues as they pop up out of the blue...) and then use proutil
to do an index rebuild.  When proutil asks you what indexes just use "!"
to say that you're all done without actually selecting any.  It'll run
through a few steps and then quit after clearing the "tainted" flag.

You will lose data.  You won't know what data until you trip across it.

BTW, if that 7.3 release isn't 7.3e you should patch it immediately.  
7.3a and 7.3c01 in particular are very, very {*filter*} releases to be
trusting production data too...  And 6.3 is obviously prehistoric...



Tue, 25 Sep 2001 03:00:00 GMT
 Problem with BI file

Quote:

> Hello!
> I have a problem: we have two environments on our aix-system. 1 a 6.3f
> and 1 a 7.3, what has happened is that a deveoper started the
> 6-database with version 7, discoverd what he'd done, deleted a .lk
> file and restarted the 6-database with version 6. Now months later, we
> stopped the system for maintenance and when tried to restart the
> 6-database we're unpleasantly surpised with the message that the .bi
> file refers to a database last used on the day that the above error
> was executed. Is the a way to fool the bi image file to refer to the
> current database? Otherwise we lose a whole day's production.

There is a fair cbance that the database is corrupted beyond repair. You
could try to dump the data using the -F option and load it into a new
database, but there is no guarantee that you'll be able to recover all
the data that way.

----
Niels Diepeveen
Endea automatisering



Tue, 25 Sep 2001 03:00:00 GMT
 Problem with BI file
We restored from tape and re-entered yesterday's production. All
appears to be well again. Thanks for your tips and advice !!

Chris

On Fri, 09 Apr 1999 14:09:21 +0200, Niels Diepeveen

Quote:


>> Hello!
>> I have a problem: we have two environments on our aix-system. 1 a 6.3f
>> and 1 a 7.3, what has happened is that a deveoper started the
>> 6-database with version 7, discoverd what he'd done, deleted a .lk
>> file and restarted the 6-database with version 6. Now months later, we
>> stopped the system for maintenance and when tried to restart the
>> 6-database we're unpleasantly surpised with the message that the .bi
>> file refers to a database last used on the day that the above error
>> was executed. Is the a way to fool the bi image file to refer to the
>> current database? Otherwise we lose a whole day's production.

>There is a fair cbance that the database is corrupted beyond repair. You
>could try to dump the data using the -F option and load it into a new
>database, but there is no guarantee that you'll be able to recover all
>the data that way.

>----
>Niels Diepeveen
>Endea automatisering



Tue, 25 Sep 2001 03:00:00 GMT
 Problem with BI file

Quote:

>Hello!
>I have a problem: we have two environments on our aix-system. 1 a 6.3f
>and 1 a 7.3, what has happened is that a deveoper started the
>6-database with version 7, discoverd what he'd done, deleted a .lk
>file and restarted the 6-database with version 6. Now months later, we
>stopped the system for maintenance and when tried to restart the
>6-database we're unpleasantly surpised with the message that the .bi
>file refers to a database last used on the day that the above error
>was executed. Is the a way to fool the bi image file to refer to the
>current database? Otherwise we lose a whole day's production.

>I hope I have described the problem clearly as I'm not the
>administrator!!
>thanks for any input (even bad news!!)

>Chris

I have not worked with this for quite a while, but I imagine that you use
the -F (Force) to go into the database.
If you still can't get in, delete the BI file and try again.
If this also fails, restore an old BI file and try again.

Once you are inside, do a dump and reload.



Fri, 28 Sep 2001 03:00:00 GMT
 Problem with BI file
Be aware that a dump & load does NOT guarentee your DB is integer again.
If you loose your BI your can (and will) loose transaction data.

Backup can be a better option in stead of going into a repair spiral.

Peter


Quote:


>>Hello!
>>I have a problem: we have two environments on our aix-system. 1 a 6.3f
>>and 1 a 7.3, what has happened is that a deveoper started the
>>6-database with version 7, discoverd what he'd done, deleted a .lk
>>file and restarted the 6-database with version 6. Now months later, we
>>stopped the system for maintenance and when tried to restart the
>>6-database we're unpleasantly surpised with the message that the .bi
>>file refers to a database last used on the day that the above error
>>was executed. Is the a way to fool the bi image file to refer to the
>>current database? Otherwise we lose a whole day's production.

>>I hope I have described the problem clearly as I'm not the
>>administrator!!
>>thanks for any input (even bad news!!)

>>Chris

>I have not worked with this for quite a while, but I imagine that you use
>the -F (Force) to go into the database.
>If you still can't get in, delete the BI file and try again.
>If this also fails, restore an old BI file and try again.

>Once you are inside, do a dump and reload.



Fri, 12 Oct 2001 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. BI File vs LBI File

2. BI Accelerator: flat files, clustering and local cubes

3. Multi-volumd database - BI file overflow extent size

4. RE-CREATING .BI FILE!!!

5. .bi file truncation

6. bi file size

7. bi file has wrong cluster size

8. move bi file

9. How to look at the BI file?

10. BI file too short???

11. Bi file on raid 0+1

12. Truncating BI file - 24/7 Backup Strategy


 
Powered by phpBB® Forum Software