| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5081.1 | Restore of area without recovery? | bouvs.us.oracle.com::OAKEY | I'll take Clueless for $500, Alex | Wed Feb 26 1997 17:16 | 14 |
| >> <<< Note 5081.0 by NOMAHS::SECRIST "Rdb WWS; [email protected]" >>>
>> -< What things set 'inconsistent' flag in RMU/DUMP/HEAD ? >-
>> What are all of the things that can set the flag in the "database
>> recovery" section of an RMU/DUMP/HEADER that makes RMU/DUMP report
>> "Database is inconsistent and has been modified" ?
Right off hand the operation that comes to mind is restoring an area
without following that by a recover. If you restore an area, the area is
marked inconsistent and will be marked as consistent as soon as you recover
from the AIJ.
Do they have corrupt pages in the CPT? Did they restore an area?
|
| 5081.2 | Things that make you go "Hmmmmmm" | NOMAHS::SECRIST | Rdb WWS; [email protected] | Wed Feb 26 1997 18:04 | 16 |
|
Hmmm. That's what came to mind for me too, but they swear they
haven't restored anything out of synch or used RMU/ALTER, etc.
The database came from an EXPORT/IMPORT they did some moons ago
to overcome file fragmentation, and they're command procedure
does an online VERIFY/NOROOT and full AIJ backup daily with
either full or incremental RMU backups and everything is clean
in the logs. They're going to scour the logs, but then I
couldn't figure out any other way this would have been set.
They have got to be missing something or have a late-night
hacker nobody knows about ;-)
Thanks,
rcs
|
| 5081.3 | | m5.us.oracle.com::LWILCOX | Chocolate in January!! | Thu Feb 27 1997 11:14 | 6 |
| I do remember several reports some time ago where customers would export
\import and then end up with this flag on. Never did figure out why or
how and it did not seem to cause trouble...I think there might be some
old notes about this.
Liz
|
| 5081.4 | | NOVA::SMITHI | Don't understate or underestimate Rdb! | Thu Feb 27 1997 11:38 | 9 |
| ~I do remember several reports some time ago where customers would export
~\import and then end up with this flag on. Never did figure out why or
~how and it did not seem to cause trouble...I think there might be some
~old notes about this.
Seems unlikely, that would mean this was possible after a CREATE DATABASE
(which is all IMPORT does).
ian
|
| 5081.5 | | m5.us.oracle.com::LWILCOX | Chocolate in January!! | Thu Feb 27 1997 13:31 | 8 |
| <<< Note 5081.4 by NOVA::SMITHI "Don't understate or underestimate Rdb!" >>>
>>Seems unlikely, that would mean this was possible after a CREATE DATABASE
>>(which is all IMPORT does).
You bet it seems unlikely. Note 1486 in 5.0 notesfile was the one I
remembered.
|