** Troubleshooting ** "DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.59.81 ** ERROR: Invalid datbase, XFRANGO is empty" creating new Controller database
User launches "Controller Configuration" and selects a database connection. User starts the standard (Java-based) "Database Conversion Utility", and chooses "Controller DB". User clicks "Connect" and chooses "Create DB". After a while, an error appears.
Running script: script/db2/trigger_trg_saxipmain_insert.sql
Running script: script/db2/trigger_trg_saxipstand_delete.sql
Running script: script/db2/trigger_trg_saxipstand_insert.sql
** ERROR: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.59.81
** ERROR: Invalid datbase, XFRANGO is empty
Controller database's transaction log settings are too restrictive.
- Specifically, the value for "LOGPRIMARY" is too small (for example it was set to 20).
- For more details on this topic, see separate IBM article "Tivoli Identity Manager Express Version 4.6 - Database update fails with an SQL error".
There are several different possible causes for the log settings being incorrect:
- Scenario #1 - DBA has configured the database to have the wrong (too restrictive) log settings
- Scenario #2 - DBA has configured the database to have the correct settings, but these settings have not yet been activated by the database server.
- See separate IBM Technote 1614478.
Transaction logs keep track of each and every transaction - if anything goes wrong with database/instance it gives the database a chance to roll forward/back these transactions. There are many different potential ways to configure transaction logs, such as:
- In DB2 there are two different ways of taking care of transactions:
- Transaction log file sizes
- Number of log files
The optimal transaction log configuration varies between database usage (for example 'datawarehouses', 'OLTP') and how intense the usage is (for example the number of concurrent active users).
=> Therefore it is impossible to give precise/exact recommendations for transaction log settings.
One tip can be useful is to use the "logsecond" parameter - if 'logprimary' is full a second logfile ('logsecond') is created. This is created "on the fly when needed", and they are freed (over time) when the database manager determines that they are no longer needed. There is a downside to this - there can be some overhead to create a new logfile during a transaction.
- For more information on 'logsecond' see link at the end of this Technote.
Controller 10.1 database hosted on DB2.
Resolving the problem
Increase the value for the DB2 setting "LOGPRIMARY" on the Controller application repository database.
- NOTE: The optimal value for your environment will vary depending on your circumstances. In one real-life example, the original value was "20", and the problem was fixed by increasing the value to 100.
- To see the existing value for "LOGPRIMARY" run the following command script:
get db cfg for <database_name>
Inside the results, there will be a line similar to the following:
Number of primary log files (LOGPRIMARY) = 20
- To modify the value for "LOGPRIMARY" run the following command script:
update db cfg for <database_name> using LOGPRIMARY <newvalue>
TIP: For more details on this, see separate IBM Technote #1298630.
- Delete the database
- Re-create the database (create a new/blank DB2 database)
- Use the 'legacy' (non-JAVA) version of DbConv instead, to create the database
- Afterwards, this same program to raise the database version to a compatible version.
- Afterwards, re-use the JAVA version of DbConv to finish upgrading the database.
- Delete the DB2 database
- Re-create the DB2 database
- Launch Explorer
- Navigate to the "...\c10\legacy" directory. TIP: By default, this is located here: C:\Program Files\ibm\cognos\c10\legacy
- Double-click on the file "DbConv.exe"
- Inside the 'data' section, click on the '...' button
- Browse to the relevant UDL file inside the "DATA" directory (for example C:\Program Files\ibm\cognos\c10\data\production.udl)
- Click "Open"
- Choose a "Group Language" (for example "EN")
- Choose a Local Language" (for example "EN")
- Click "CreateDb". TIP: This will upgrade to database version 300.
- Click "Run Steps". TIP: This will upgrade to database version 833.
- After the processes have completed, click "Close"
- Re-launch "Controller Configuration"
- Open section 'Database Connections'
- Highlight connection name (for example 'production') and clicks the green triangle ("run") button at the top of the screen. This launches DbConv ("Database Conversion Utility")
- Click "Connect". Note how the 'Current version" will be set to a higher number.
- Click on "Upgrade" to upgrade the database to the current Controller version level.
- Finally, click "Close".
TIP: If you get an error "Error 429 (Hex 1AD)..." when using "DbConv.exe" then:
- Launch a command prompt by clicking "Start" - "Run" and then typing in "CMD" <Enter>
- Change directory to the c10\common folder (for example using: cd "C:\Program Files\ibm\cognos\c10\common")
- Register the DLL file using: regsvr32.exe FrCrypto.dll
Ensure that the correct DB2 database settings have been actioned *before* using "Database Conversion Utility".
- See separate IBM Technote 1614478.
1454989 - "Error 429 (Hex 1AD) ActiveX component can't
1298630 - DB2 SQL error: SQLCODE: -964 SQLSTATE: 5701
Tivoli Identity Manager Express Version 4.6 - Database
1614478 - "DB2 SQL Error: SQLCODE=-964 SQLSTATE=57011.
Translate this page: