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 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.
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.

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 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.

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.

Symptoms

HCL Z Asset Optimizer operational jobs for Inquisitor or Usage import are failing.

When running Inquisitor Import or Usage import batch jobs, multiple users using the Analyzer to access the Repository database can lead to timeouts or deadlocks. These batch jobs require exclusive accesses to the data in the tables. SQLCODE -904 error occurs with reason code 00C90083 or reason code 00C9008E.

Causes

When running Inquisitor Import or Usage import batch jobs, multiple users using the Analyzer to access the Repository database can lead to timeouts or deadlocks. These batch jobs require exclusive accesses to the data in the tables. SQLCODE -904 error occurs with reason code 00C90083 or reason code 00C9008E

Diganosing the problem

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

DSNT501I  - DSNIDBET RESOURCE UNAVAILABLE  656  
            CORRELATION-ID=AAAAAA  
            CONNECTION-ID=DB2CALL  
            LUW-ID=NETA.GGGGGG.UUUUD99=81188  
            REASON 00C90083  
            TYPE 00000200  
            NAME XXXXXX.YYYYY
                
DSNT501I  - DSNIDBET RESOURCE UNAVAILABLE  656  
            CORRELATION-ID=BBBBB  
            CONNECTION-ID=DB2CALL  
            LUW-ID=NETA.GGGGGG.IIIII222=81188  
            REASON 00C9008E  
            TYPE 00000200  
            NAME XXXXXX.YYYYY

Resolving the problem

You can perform one or more of the following changes to resolve the issue:

Run these jobs during off-peak periods.
Reduce the number of users that need to use the Analyzer during peak periods.
Reduce the value of the COMMIT=1000 attribute to COMMIT=500 in PARMLIB members HZASIQP1 and HZASUIP1.
Define the DSNACLI plan and the dependent packages to use uncommitted reads.
- Modify all packages and plan in db2.SDSNSAMP(DSNTIJCL) to have ISOLATION(UR) and then run the job.
- When you change the settings for DSNACLI, ensure that this plan is not used by other applications or create the plan with a different name.
- By setting ISOLATION(UR), when you run Analyzer reports, it is likely that the correct or latest information is not be displayed due to concurrency issues in Db2®.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.