Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2004
    Posts
    24

    Unanswered: DB2 Task Center:LOB locators exceeded?!

    When I try to view task history from the DB2 Task Center I get this error:

    "
    ICM0003N An SQL error occurred while searching for objects.
    IBMCLI DriverDB2/NT SQL0429N The maximum number of
    concurrent LOB locators has been exceeded. SQLSTATE=54028

    Explanation:

    An SQL error occurred while the Information Catalog Manager API
    was performing a search of the IBM DB2 tools catalog.

    User Response:

    Check the Message Reference for more information about this SQL
    error. "
    I have no idea what LOBs have to do with view task history, but either something is wrong with my tools db catalog or I need to adjust its configuration. I searched for how to fix this error, and it usually has something to with changing application code. But since I don't have access to the IBM Task Center's source code, I need find out how to fix this.

    Any help would be appreciated.

    Thanks.

  2. #2
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    LOB locators are used by CLI applications to retrieve LOBs piece-wise. The DB2 Task Center uses LOBs under the covers because some information in the task history is stored in a LOB column, I guess.

    You should try to adjust your CLI configuration and add "PATCH2=50" to your CLI configuration. This will cause LOB locators to be freed within CLI once the next LOB is accessed.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  3. #3
    Join Date
    Feb 2004
    Posts
    24
    Thanks for the reply. Do you know where the cli configuration for the task center is located? I assume it must be some .ini or .conf file.

    Thanks.

  4. #4
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    There is no "CLI configuration for the task center". It is the regular DB2 CLI configuration. Have a look at the UPDATE CLI CONFIGURATION command.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  5. #5
    Join Date
    Feb 2004
    Posts
    24
    I put the setting into the config, but it did not seem to help. Here is the output of my get cli cfg command:


    Section: tstcli1x
    -------------------------------------------------
    uid=userid
    pwd=*****
    autocommit=0
    TableType='TABLE','VIEW','SYSTEM TABLE'

    Section: tstcli2x
    -------------------------------------------------
    SchemaList='OWNER1','OWNER2',CURRENT SQLID

    Section: MyVeryLongDBALIASName
    -------------------------------------------------
    dbalias=dbalias3
    SysSchema=MYSCHEMA

    Section: lobLocator
    -------------------------------------------------
    PATCH2=50

    Do I need to restart the DAS for this to take affect?

Posting Permissions

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