Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2002
    Location
    linz, austria
    Posts
    3

    Question Unanswered: error msg via php

    dopes anybody know why i get this message - all of a sudden

    3 weeks ago the system worked flawlessly
    now no way..

    i can connect , but every select statement gives me that error:
    [IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "UPDATABLE WORKFILE", type of resource: "100", and resource name: "TEMP DATABASE ". SQLSTATE=57011

    select statements via command line work fine.

    thanks for every hint

    paul

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: error msg via php

    One of your databases is not available ....



    Originally posted by db2_php_user
    dopes anybody know why i get this message - all of a sudden

    3 weeks ago the system worked flawlessly
    now no way..

    i can connect , but every select statement gives me that error:
    [IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "UPDATABLE WORKFILE", type of resource: "100", and resource name: "TEMP DATABASE ". SQLSTATE=57011

    select statements via command line work fine.

    thanks for every hint

    paul

  3. #3
    Join Date
    Feb 2003
    Location
    Germany
    Posts
    1

    Re: error msg via php

    Hi,

    since a DB2 OS/390 V7.1.1 update I have the same problem.
    You found any solution.
    Thanks
    Sebastian


    Originally posted by db2_php_user
    dopes anybody know why i get this message - all of a sudden

    3 weeks ago the system worked flawlessly
    now no way..

    i can connect , but every select statement gives me that error:
    [IBM][CLI Driver][DB2] SQL0904N Unsuccessful execution caused by an unavailable resource. Reason code: "UPDATABLE WORKFILE", type of resource: "100", and resource name: "TEMP DATABASE ". SQLSTATE=57011

    select statements via command line work fine.

    thanks for every hint
    paul

  4. #4
    Join Date
    Sep 2002
    Location
    linz, austria
    Posts
    3

    Lightbulb Re: error msg via php

    Betreff:
    PMR 82832 : SQLCODE904 bei ODBC seit Host DB2 V7
    Von:
    "Peter Urthaler" <peter_urthaler@at.ibm.com>
    Datum:
    Mon, 30 Sep 2002 09:46:53 +0200
    An:
    wa@jku.at

    Lieber Herr Astleitner,

    hier die Information unseres Labors:

    :::+++:::

    The problem is caused by the new server-side scrollable cursor support
    for OS/390 with version 7.

    Since scrollable cursor support is new, some ODBC applications that were
    working with previous releases of UDB for OS/390 or UDB for Unix,
    Windows, and OS/2 may encounter behavioral or performance changes. This
    occurs because before scrollable cursors were supported, applications
    that requested a scrollable cursor would receive a forward-only cursor.

    To restore an application's previous behavior before scrollable cursor
    support, set the following configuration keywords in the db2cli.ini
    file:

    PATCH2=6
    DisableKeysetCursor=1
    UseServerKeysetCursor=0

    :::+++:::

    Testen Sie bitte mit den genannten Parametern.


    Mit freundlichen Grüßen / Best regards

    Peter Urthaler
    SSC Salzburg 65/672 Phone: +43-662-8388/9410
    IBM Austria Fax: +43-662-8388/9330



    Originally posted by seschmid
    Hi,

    since a DB2 OS/390 V7.1.1 update I have the same problem.
    You found any solution.
    Thanks
    Sebastian

  5. #5
    Join Date
    May 2003
    Posts
    1

    Re: error msg via php

    The reason code of updatable workfile means that a TEMP database and tablespaces needs to be created in order to enable scrollable cursor support on the system. TEMP database is not to be confused with the DSNDB07 database. CREATE DATABASE AS TEMP ....
    If data sharing is used, each data sharing member needs it's own temp database, CREATE DATABASE AS TEMP FOR memberssid....
    These TEMP DATABASES are also needed for temporary tables. Scrollable cursor support uses internal temporary tables and this is why they need the TEMP database.
    APAR PQ73794 has now been changed to include the UPDATABLE WORKFILE reason code as one of the symptoms. This apar is going to correct the reason code and document the TEMP database info. IBM is also going to be updating the install info bucket for DB2 V7 to include this info to warn those that are using ini file settings that are inadvertently requesting scrollable cursors.

    SO the solution to the problem is to either make the db2cli.ini setting changes to not request scrollable cursors or define the TEMP database and tablespace.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •