text: <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>Table 18 - 5 Information to collect for DB2</td><td>File</td></tr></thead><tbody><tr><td>Description</td><td>db2d1 ag. 1og</td></tr><tr><td>This file is the DB2 diagnosis file. It is in the 5H0ME / sq11 b / dizdunp directory, where 5H0WE is the home directory of the DB2 instance.</td><td>CLI trace ( Open Database Connectivity ( ODBC ))</td></tr><tr><td>This file contains the call - level interface ( CLI ) trace file for diagnosing SQL statements. The CU trace option must be turned on to collect the file. ( See ‘ Setting the CLI trace for DBZ ’ on page 392.)</td><td>Text summary</td></tr><tr><td>Collect a text summary of the application group and folder with the database problem by logging on to the Content Manager OnDemand server through the Content Manager OnDemand Administrator Client.</td><td>Content Manager OnDemand system log</td></tr><tr><td>Gather the Content Manager OnlDemand system log messages10 minutes before and after the database problem.</td><td>SQLCODE error message</td></tr><tr><td>If the SQLCODE error message is available, collect this information to determine whether the problem is from Content Manager OnDemand or the database.</td><td>DB2 configuration report of the Content Manager OnDemand instance</td></tr><tr><td>This report is generated by the dbZ command : dbZ get : db cfg for - 1nstance_nane</td><td>ars. 1n1</td></tr><tr><td>If you cannot determine the database engine, check the path of the ars. In I file. In UNIX System Services, run set × / teg / set. txt and send a binary copy of the ars. In i file to IEM Support.</td><td>ars. cfg</td></tr><tr><td>Send a binary copy of the ars. cfg file to IBM Support.</td><td>c11.1n1</td></tr><tr><td>Verify the contents of the c11. in : file. Verify that MYSDEFAULTSS1D - vs xx points to the correct DB2 Subsystem ( O. Also, check whether the value can be set within your installation by a BSAK03K3B3B statement in JCL or as a hierarchical fili</td><td>On Windows and other platforms</td></tr><tr><td>For Windows, collect the Content Manager Ordemand server configuration settings : WLT : __0CA__98013NC1 ; SOTTVAMC1 ; LBM ; lockeound For all other platforms, collect the arrs.. 1r1, arrs. c1g, irrs. cache, and arrs. df ' s filleles.</td><td>Application group report</td></tr><tr><td>The application group ID is the name of the related DB2 tables.</td></tr><tr></tr></tbody>
          </table> </body> </html>