Home
Troubleshooting and support
To isolate and resolve problems with your HCL software, you can use the troubleshooting, messages, and support information. This information contains instructions for using the problem determination resources that are provided with your HCL products.
Troubleshooting a problem
Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.
Problems and solutions
Solution information helps you to understand the causes of an issue with your product and learn what to do to diagnose or resolve the problem.
Insufficient space in the Db2® work file database
When processing large amounts of data, you can encounter insufficient space in the Db2® work file database.

Troubleshooting and support
To isolate and resolve problems with your HCL software, you can use the troubleshooting, messages, and support information. This information contains instructions for using the problem determination resources that are provided with your HCL products.
- Troubleshooting a problem
  Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.
  - Problems and solutions
    Solution information helps you to understand the causes of an issue with your product and learn what to do to diagnose or resolve the problem.
    - Resolving Db2 SQLCODE -805 error for DSNACLI plan
      If you receive a SQLCODE -805 error, operational jobs fail.
    - Insufficient space in the Db2® work file database
      When processing large amounts of data, you can encounter insufficient space in the Db2® work file database.
    - Preventing Db2 timeouts/deadlocks during Inquisitor or Usage imports
      Batch import jobs from the Inquisitor or the Usage Monitor require exclusive access to tables in the Repository database to prevent timeouts or deadlocks.
    - Improving Db2 performance
      For DB2 sites, HCL Z Asset Optimizer operational jobs are usually run during off-peak so it is important that all IQ Import and Usage Import jobs must complete during the batch window.
    - Updating your Global Knowledge Base (GKB) database
      HCL support provides monthly update to the Global Knowledge Base (GKB). so that you can keep your product inventory definitions up-to-date. You can also submit items to HCL support for inclusion in GKB updates.

Insufficient space in the Db2® work file database

When processing large amounts of data, you can encounter insufficient space in the Db2® work file database.

Symptoms

HCL Z Asset Optimizer operational jobs are failing.

Causes

When you run SQL queries that process large amounts of data, including sorts and joins, there is insufficient space in the work file database that is used for temporary storage.

Diagnosing the problem

Check for examples of following messages in the Db2® MSTR address space:

DSNT501I  -DE91 DSNIXWKF RESOURCE UNAVAILABLE  553   
           CORRELATION-ID=XXXXXX                     
           CONNECTION-ID=DB2CALL                     
           LUW-ID=AUIBMQXP.OMU1DEC1.C4729058740C=0   
           REASON 00C900A5                           
           TYPE 00000230                             
           NAME 4K                                   
DSNT501I  -DE91 DSNIWKFL RESOURCE UNAVAILABLE  554   
           CORRELATION-ID=XXXXXX                     
           CONNECTION-ID=DB2CALL                     
           LUW-ID=AUIBMQXP.OMU1DEC1.C4729058740C=0   
           REASON 00C90084                           
           TYPE 00000230                             
           NAME 4K

View and check the sizes and extents of the physical data sets allocated to the table spaces in the work file database.

Resolving the problem

Increase the sizes of the table spaces associated with the work file database. The sample db2.SDSNSAMP(DSNTIJTM) job provides examples of how to increase the sizes of the table spaces.