+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 17

Row or object SEKVENCE in EXTLOG001 type *FILE in use

  1. Row or object SEKVENCE in EXTLOG001 type *FILE in use

    Can someone tell me what this exception means:
    [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use

    Alan


  2. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  3. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  4. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  5. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  6. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  7. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  8. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  9. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    alan_sec wrote:

    > Can someone tell me what this exception means:
    > [SQL0913] Row or object SEKVENCE in EXTLOG001 type *FILE in use


    Did you have a look at the description of the error? On DB2 LUW, I got:

    $ db2 "? sql0913"

    SQL0913N Unsuccessful execution caused by deadlock or timeout.
    Reason code "".

    Explanation:

    The request issued was involved in an unresolved contention for
    use of an object and the execution failed.

    The reason codes are as follows:

    2 transaction branch failed due to deadlock.

    68 transaction branch failed due to lock timeout.

    72 transaction rolled back due to an error concerning a DB2 Data
    Links Manager involved in the transaction.

    80 statement failed due to timeout.

    User Response:

    o For reason code 80, you can retry the failed statement
    without terminating the application. If the application
    accesses multiple remote databases, it may be better to
    rollback the transaction to avoid the possibility of a global
    deadlock.

    o For other reason codes, issue a request to rollback the
    transaction. The transaction cannot be committed due to the
    failure of the current transaction branch.

    o To help avoid deadlock or lock timeout, issue frequent COMMIT
    operations, if possible, within long-running applications or
    applications requiring data with high concurrent access.


    But it seems that you're on a different platform, so things might not be the
    same there.

    --
    Knut Stolze
    DB2 Information Integration Development
    IBM Germany

  10. Re: Row or object SEKVENCE in EXTLOG001 type *FILE in use

    Alan,

    you got this exception doing what ?
    I suppose it was returned to you by an application ? (and not
    originally by DB2 on a commandline - so being 'pre-processed')

    -913 means deadlock/timeout on zOS as well.

    I'd say, it's a timeout, and the application is even returning you what
    it was waiting for.

    any entry's in the db2diag.log ?


+ Reply to Thread
Page 1 of 2 1 2 LastLast