[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbms

Title:VAX DBMS
Notice:THIS NOTESFILE IS NOT A FORMAL SUPPORT CHANNEL
Moderator:SCARY::CHARLAND
Created:Thu Feb 20 1986
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2642
Total number of notes:11044

2625.0. "ALS bugcheck w/AIJTUL$ABORT" by m5.us.oracle.com::LWILCOX (How about Fireworks?) Tue May 06 1997 18:41

T.RTitleUserPersonal
Name
DateLines
2625.1m5.us.oracle.com::LWILCOXHow about Fireworks?Tue May 06 1997 18:427
One other tidbit I forgot to mention is she tried to use ROTATE and this
command appeared to hang.  She also mentioned at one time she noted a stall
message along the lines of "waiting for AIJ submission".

Thanks.

Liz
2625.2NOVA::R_ANDERSONOracle Corporation (603) 881-1935Wed May 07 1997 00:3815
    For the benefit of other readers, I'll provide a synopsis of what I
    sent Liz offline.
    
    The ALS switch-over operation failed because 1 (or more) of 3 events
    occurred:
    1.  The switch-over timed out (not likely).
    2.  The switch-over was being performed by DBR (impossible :-)
    3.  A DBR was invoked after ALS was unable to locate a valid journal
    for over-writing (most likely).
    
    I'm not sure given the available information why the journals could not
    be over-written (especially because fast-commit is disabled so there
    are no checkpoint requirements), so further analysis is required.
    
    Rick
2625.3ACE *might* be the problem?M5::LWILCOXHow about Fireworks?Wed May 21 1997 18:128
After turning off the AIJ on electronic cache feature the database has not
had any problem with this.  I think I remember seeing something about that
somewhere, but can't come up with it.  Anyone else have any kind of similar
experience (bugchecks so long as ACE was on)?

Thanks.

Liz
2625.4More occurrencesM5::DMACKENZWed May 28 1997 15:5728
    This problem has occurred two more times.  Today's incident was when
    AIJ cache was disabled and DBMS is 6.1-11.  Bugchecks are on their way; 
    I expect to have more information soon.
    
    The first bugcheck occurred on May 4th, DBMS 6.1-1, AIJ cache enabled.
    No exception in the bugcheck.  The AIJ_STATUS is 1 (filaccerr right?)
    Following is noteworthy information about each AIJ file:
    o Current:   Activated May 4th, modified, inaccessible, never backed up,
                 AIJ_STATUS=5
    o Last Used: Activated May 4th, modified, 99% full, backup in progress,
                 never backed up, AIJ_STATUS=0
    o Oldest:    Activated April 28th, modified, 99% full, backup in
                 progress, last backed up April 28th, next to be backed up,
                 AIJ_STATUS=0
    
    I've requested operator notification be enabled since it is not at this
    point.
    
    The problem was corrected (disable AIJs, drop AIJs, create AIJs, BU
    database) before today's problem was reported.  Would there by any
    clues remaining as to the cause for the AIJ being marked inaccessible
    and the reason the AIJ backups are not completing?  What does an
    AIJ_STATUS of 5 mean?  Any other insights?
    
    Thanks,
    
    Diane
                           
2625.5AIJ backups not completingM5::DMACKENZWed May 28 1997 17:5512
    I received the ALS bugcheck from May 22nd and took a look at it.  DBMS 
    is 6.1-11 and AIJ caching is disabled.  Again no exception.  Two AIJ
    files are in the process of being backed up and the third is current
    and marked full and inaccessible.
    
    It appears to me that the current AIJ file is being marked inaccessible
    because it is full and there are no AIJ files available to write to,
    since the other two are in the process of being backed up.  I'll be
    looking for clues as to why the backups aren't completing.  Would there
    be any left behind?
    
    Diane