IBM Support

JR32465: FED:CALL FSTP MAKE DB2 CRASH WHEN SHUTDOWN REMOTE ORACLE SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem was detected on cobra when SVT, it exists on v91
    and v95 too. open the defect to fix it.
    env: Cobra n090219 n090219 build
    oracle client/server version: 9i/11g
    The svt test scenario and related db2dump files are put on
    /home/db2inst1/result4defect/shutdownoracle
    @vanguard1.cn.ibm.com
    We create 100 connections to continuously call a very simple
    fstp.
    When we shutdown the remote oracle datasource,the db2 crash in
    one minute. The next log is picked from one of those
    connections.
    BEGIN iteration 18
    Mon Feb 23 14:17:07 CST 2009
    call FSTP.ORA888
      Result set 1
      --------------
      COUNT(*)
      ------------------------
        +1.00000000000000E+003
      1 record(s) selected.
      Return Status = 0
    END iteration 18
    BEGIN iteration 19
    Mon Feb 23 14:17:09 CST 2009
    call FSTP.ORA888
    SQL1476N  The current transaction was rolled back because of
    error "-30080".
    SQLSTATE=40506
    END iteration 19
    BEGIN iteration 20
    Mon Feb 23 14:17:11 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 20
    BEGIN iteration 21
    Mon Feb 23 14:17:13 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 21
    BEGIN iteration 22
    Mon Feb 23 14:17:15 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 22
    BEGIN iteration 23
    Mon Feb 23 14:17:16 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 23
    BEGIN iteration 24
    Mon Feb 23 14:17:20 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 24
    BEGIN iteration 25
    Mon Feb 23 14:17:21 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 25
    BEGIN iteration 26
    Mon Feb 23 14:17:24 CST 2009
    call FSTP.ORA888
    SQL30080N  A communication error "NET8: 12514" occurred
    sending or receiving
    data from the remote database. SQLSTATE=08001
    END iteration 26
    BEGIN iteration 27
    Mon Feb 23 14:17:25 CST 2009
    call FSTP.ORA888
    SQL1224N  The database manager is not able to accept new
    requests, has
    terminated all requests in progress, or has terminated the
    specified request
    because of an error or a forced interrupt.  SQLSTATE=55032
    The call stack from  is as below,
    <StackTrace>
    -------Frame------ ------Function + Offset------
    0x09000000006C3270 pthread_kill + 0xB0
    0x09000000006C2AE8 _p_raise + 0x48
    0x090000000002B56C raise + 0x4C
    0x090000000008E9C4 abort + 0xC4
    0x0900000014A23E2C sqloExitEDU + 0x24C
    0x09000000148D50B0 sqle_panic__Fv + 0x110
    0x0900000015F4236C sqljsTrapResilience__FP14db2UCinterface +
    0x62C
    0x0900000015F42954 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
    0x214
    0x0900000014B07F7C RunEDU__8sqeAgentFv + 0x3BC
    0x0900000014AF7F0C EDUDriver__9sqzEDUObjFv + 0x1AC
    0x0900000014AF821C sqlzRunEDU__FPcUi + 0x3C
    0x0900000014A2C36C sqloEDUEntry + 0x6AC
    </StackTrace>
    Follow the next steps to set up svt test scenario,
    1. create remote and federated store procedures
    SET PASSTHRU ORA1#
    CREATE PROCEDURE "ORA888" (cur1 out SYS_REFCURSOR) as
    BEGIN
        open cur1 for select count(*) from SAKE_FSTP_TABLE101;
    END;#
    SET PASSTHRU RESET#
    CREATE PROCEDURE FSTP.ORA888 SOURCE "BBCS1"."ORA888" FOR
    SERVER ora1 WITH RETURN TO CALLER all #
    2. create 100 connections using clp to continuously call the
    federated sp, just like,
    db2 -v "call FSTP.ORA888"
    3. shutdown datasource on remote oracle server using command of
    "shutdown abort" in sqlplus.
    

Local fix

Problem summary

  • Users affected:
       Users of the DB2 for LUW Homogeneous Federation Feature or
    InfoSphere Federation Server
    Problem description and summary:
       See error description.
    

Problem conclusion

  • Problem was first fixed in Version 9.5 FixPak 5 (s091123 ). This
    fix should be applied on the federation server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR32465

  • Reported component name

    FEDERATED RUNTI

  • Reported component ID

    5724N9703

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-23

  • Closed date

    2009-12-22

  • Last modified date

    2009-12-22

  • APAR is sysrouted FROM one or more of the following:

    JR32464

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    FEDERATED RUNTI

  • Fixed component ID

    5724N9703

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCAVPX","label":"Federated Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
22 December 2009