IBM Support

** Troubleshooting ** "SQLCODE=-204, SQLSTATE=-42704" error when using DbConv to create new database

Troubleshooting


Problem

Administrator creates brand new (blank) DB2 database. Administrator logs onto the Controller application server, launches 'Controller Configuration' and creates a new database connection to the database. Administrator clicks 'connect' and then clicks 'Create DB'. An error appears.

Symptom

Depending on the environment the error may appear slightly differently, but it will be similar to:

    ** ERROR: com.ibm.db2.jcc.am.io: DB2 SQL Error:
    SQLCODE=-204, SQLSTATE=-42704, SQLERRMC=CONTRO, DRIVER=3.57.82
    ** ERROR: Invalid datbase, XFRANGO is empty

Cause

There are many potential causes for similar-looking DB2 errors.

  • NOTE: This Technote *only* relates to the scenario where the error contains the codes: SQLCODE=-204, SQLSTATE=-42704

In this scenario, there are several possible causes for the errors:
  • Scenario #1 - DB2 database server is not using 'Oracle Compatibility Mode'.
    • TIP: In this scenario, the error message will typically contain the word 'USER_TABLES'
  • Scenario #2 - DB2 database client (installed on the Controller application server) has "Enable operating system security for DB2 objects" enabled.
  • Scenario #3 - DB2 database has not been created correctly.

Diagnosing The Problem

IMPORTANT: It is vital that you check the exact 'SQLCODE' and 'SQLSTATE' error numbers, to help you troubleshoot the root cause.

  • Make sure that you check the error code reference numbers precisely. If they are different, then search IBM Technotes for different/specific advice for your error code.

Resolving The Problem

Scenario #1
Delete the database. Re-configure the DB2 database server to use 'Oracle Compatibility Mode'. Re-create the DB2 database. Re-try.

  • For more information, see separate IBM Technote #1613531.


Scenario #2
There are two different methods you can choose:
    (1) Uninstall DB2 client (from the Controller application server), and re-install DB2 client.
    • During the installation wizard do NOT enable "Enable operating system security for DB2 objects"
or (2) Add the group "Everyone" to the Windows security local group "DB2USERS" on the Controller application server
    • For more information see separate IBM Technote #1504470

Scenario #3
Delete the 'bad' database, and recreate the DB2 database using the correct settings.
  • TIP: For full details, see separate IBM Technote #1570572

[{"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Controller","Platform":[{"code":"PF033","label":"Windows"}],"Version":"10.1.1;10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 June 2018

UID

swg21681892

Page Feedback