RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL
Expertise: Intermediate
Sep 21, 2004



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Uploading a Large Number of Records in DB2

When you're carrying out an database-intensive operations, like trying to insert a lot of records in one transaction or opening a bunch of connections at the same time, you run the risk of encountering various database configuration-related issues. Below are some of the frequent problems/exceptions that can occur, and their solutions.
  1. Problem: The error message is SQL0912N. This tell you that the maximum number of lock requests has been reached for the database. Solution Increase the locklist using the following DB2 command:
    db2 update db cfg for <database_name> using LOCKLIST <new_value>
    <new_value> is the value you are assigning to the parameter. The default value for LOCKLIST is 100.
  2. Problem: The error message is SQL0964C. This means the transaction log for the database is full. Solution: Increase the primary and secondary DB2 logs using the following commands:
    DB2 update db cfg for <database_name> using LOGPRIMARY <new_value>
    DB2 update db cfg for <database_name> using LOGSECOND <new_value>
    You might also need to increase the log file size using the following command:
    DB2 update db cfg for <database_name> using LOGFILSIZ <new_value>
Gautham Muthuravichandran
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date