QRWTSRVR job in "waiting for save-while-active checkpoint" status - IBM AS400

This is a discussion on QRWTSRVR job in "waiting for save-while-active checkpoint" status - IBM AS400 ; Some Oracle processes connect to our iSeries DB2 database through ODBC. They seem to run through QRWTSRVR jobs. All of these jobs currently are showing "waiting for save-while-active checkpoint" status. The jobs all specify an isolation level of READ COMMITTED ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: QRWTSRVR job in "waiting for save-while-active checkpoint" status

  1. QRWTSRVR job in "waiting for save-while-active checkpoint" status

    Some Oracle processes connect to our iSeries DB2 database through ODBC.
    They seem to run through QRWTSRVR jobs. All of these jobs currently
    are showing "waiting for save-while-active checkpoint" status. The
    jobs all specify an isolation level of READ COMMITTED
    ("CURSOR_STABILITY" in the ODBC configuration.) One of the jobs has an
    exclusive update lock on a row in a table, preventing another Oracle
    job from reading the row.

    I can't find any save function running on the system, so I'm at a loss
    to understand why these server jobs are showing the status they show.


  2. Re: QRWTSRVR job in "waiting for save-while-active checkpoint" status

    Jonathan Ball wrote:
    > Some Oracle processes connect to our iSeries DB2 database through ODBC.
    > They seem to run through QRWTSRVR jobs. All of these jobs currently
    > are showing "waiting for save-while-active checkpoint" status. The
    > jobs all specify an isolation level of READ COMMITTED
    > ("CURSOR_STABILITY" in the ODBC configuration.) One of the jobs has an
    > exclusive update lock on a row in a table, preventing another Oracle
    > job from reading the row.
    >
    > I can't find any save function running on the system, so I'm at a loss
    > to understand why these server jobs are showing the status they show.
    >


    Jonathan- Don't know if you're still seeing this, but I asked a System i
    DRDA expert about it and he said he's never seen anything like it
    either. Your best bet is probably working with your IBM service
    provider to investigate, if it happens again.

    --
    Karl Hanson

+ Reply to Thread