User, Role, Profile Synchronization – Incremental

[Former Member]

Hello experts, I am currently doing a nightly incremental sync on Users, Roles, and Profiles and am experiencing the following error I’ve never seen before:

Apr 2, 2012 10:25:43 PM com.virsa.cscext.dao.CSCDAO execSQL

WARNING: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.61.65

1. com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.61.65

                at com.ibm.db2.jcc.am.ed.a(ed.java:679)

Any ideas out there?

Kyle

[hugo_amo]

Hi Kyle,

This warning message is a result of running out of space in the

transaction log.

Regards,

Hugo Amo.

[Former Member]

Thanks Hugo,

Any suggestions on fixes? Is there a particular table we can clear? Any ideas if that will have adverse affects?

Kyle

[hugo_amo]

Hi Kyle,

If you have a look at:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

Here it is said:

"Execute a COMMIT or ROLLBACK on receipt of this message (SQLCODE) or retry the operation.

If the database is being updated by concurrent applications, retry the operation. Log space may be freed up when another application finishes a transaction.

Issue more frequent commit operations. If your transactions are not committed, log space may be freed up when the transactions are committed. When designing an application, consider when to commit the update transactions to prevent a log full condition.

If deadlocks are occurring, check for them more frequently. This can be done by decreasing the database configuration parameter DLCHKTIME. This will cause deadlocks to be detected and resolved sooner (by ROLLBACK) which will then free log space.

If the condition occurs often, increase the database configuration parameter to allow a larger log file. A larger log file requires more space but reduces the need for applications to retry the operation. Transaction configuration parameters which may need to be adjusted are LOGFILSIZ, LOGPRIMARY, LOGSECOND. For more information about the transaction log search the DB2 Information Center using phrases such as "transaction log".

If installing the sample database, drop it and install the sample database again.

sqlcode: -964

sqlstate: 57011

"

Hope this helps.

Regards,

Hugo