SQL2019N error while running LOAD in DB2 Control Center

[techtip07]

Hi ,

I am getting the following error while running the SQL
LOAD utility through IBM DB2 Command Editor v8.1.7

"SQL2019N An error occurred while binding the utilities to the database. "

But the same LOAD works fine while executing through the lower version of the Command Editor tool (available on a different machine.)

Looks like something to do with the version.
Could anyone help on this ?

The load script which I am running in Command Editor :
=====================================================
LOAD CLIENT FROM C:\data1.dat
of asc method L
(
001 010,
011 020,
241 241,
242 244,
245 247,
248 250,
251 253,
254 255,
256 257,
258 263,
264 269,
270 275,
276 277,
278 280,
281 282,
283 283,
284 284,
285 287
)
MESSAGES C:\L_data1.txt

REPLACE INTO prodschema.tabname
(
cola,
colb,
col01,
col02,
col03,
col04,
col05,
col06,
col07,
col08,
col09,
col10,
col11,
col12,
col13,
BLANK,
col14,
col15
)
statistics yes with distribution and detailed indexes all
nonrecoverable;

 

[MarcLodge]

From the manual:

Explanation: Because the current level of the utility being executed was not bound to the database, the system attempted to bind all utilities to the database and this binding process failed. Possible causes for the error include:

The system may have run out of disk space.
A system resource problem such as too many files opened.
A missing or invalid list of utility programs to be bound (db2ubind.lst).
A missing or invalid bind file for one of the utilities (db2uxxxx.bnd).
The user does not have the required authorization for binding utilities. The required privileges are:
BIND privilege for the utility programs
SELECT privilege for the system catalogs.
For the RESTORE utility, the database is restored, but at least one utility is not bound to the database. The other utilities stop processing.

User Response: Complete all activities that may be competing for system resources and resubmit the utility command. If the error continues, perform one of the following actions:

Have a user with SYSADM or DBADM authority retry the command.
Reinstall the database manager or reapply any recent updates or do both.
Bind the utility programs (db2uxxxx.bnd files) individually to the database (with no format option) to isolate the problem and, possibly enable some utilities to operate successfully.

I would be inclined to look at authority issues first to see if that's it.

Marc

 

[techtip07]

Marc,

I believe the authority issues are a consequence of the root problem.Because,I am well able to execute the LOAD command with my userid on another machine having a lower version of IBM DB2 Command Editor.
Looks like it couldnt find the entry for the LOAD utility in the .bnd file and hence trying to bind all the available utilities which is resulting in the problem.

I'm not sure whether any fixpacks have come from IBM to solve this issue.

Thanks,

 

[gregsimpson]

techtip07,

there is a specific LOAD privilege, so if your convinved authority is your problem, maybe you have the privilege on one database but not on the other? Some notes below.

To load data into a table You must have one of the following authorities:
SYSADM
DBADM
LOAD authority on the database and:
INSERT privilege on the table if you load data in INSERT mode, TERMINATE mode (to terminate a previous load operation), or RESTART mode (to restart a previous load insert operation)
INSERT and DELETE privilege on the table if you load data in REPLACE mode, TERMINATE mode (to terminate a previous load replace operation), or RESTART mode (to restart a previous load replace operation)
INSERT privilege on the exception table, if one is used during the load operation
Note:
Because all load processes (and all DB2 server processes in general) are owned by the instance owner, and all these processes use the identification of the instance owner to access the required files, the instance owner must have read access to input data files. The input data files must be readable by the instance owner, regardless of who performs the load operation.
To restart a load You must have one of the following authorities:
SYSADM
DBADM
LOAD
See priveleges for loading data into a table for more information.

You should know at what point you want to restart the load process.

To terminate a load You must have one of the following authorities:
SYSADM
DBADM
LOAD
See priveleges for loading data into a table for more information.

You should also try to restart the load before terminating it. Terminate a load only if you try to restart it and an unrecoverable error occurs

Cheers
Greg

 

[techtip07]

Hi ,

I would have thought of privilege issue ,but I am able to do the LOAD (with the same userid) on another machine that has DB2 8.1(which is a lower version to the current one that I am using, DB2 v8.2)

Or I would be happy to know if someone has atleast done a similar kind of above LOAD from a DB2 v8.2 client.

Thanks,