DB/2 enterprise access - SQL and TABLE method

ArndW · Post by **ArndW** » Wed Jun 21, 2006 6:00 am

We have an EE configuration that goes to 2 remote DB/2 servers. We have just completed the installation and setup of a new series of machines and have hit an odd problem.
Using the DB/2 Enterprise stage and "user SQL" or "Auto generated SQL" we can view data and run a job. But when the "Table" method is specified we get errors, the first of which is SQL -1390 (which, according to the DOCS, is

SQL1390C The environment variable DB2INSTANCE is not defined or is invalid.

.

Does anyone have an idea why this might be?

DSguru2B · Post by **DSguru2B** » Wed Jun 21, 2006 6:34 am

I personally never ran into a problem like that, but hereswhat i was able to find.
I hope it helps.

ArndW · Post by **ArndW** » Wed Jun 21, 2006 7:12 am

Thanks, we've gone through all that already and know about that part.
It seems that we are now getting connectivity to the main DB/2 coordinator node (since we can connect & read data using the user SQL) but once we parallel and use the TABLE method the connections don't go through and return -1390.

We are still investigating but aren't getting any further in localizing the cause.

ArndW · Post by **ArndW** » Wed Jun 21, 2006 7:22 am

The problem has now been solved.

It turns out that the NFS mounts on the DB/2 machines for PX had different access rights, so PX and server could connect to the main coordinator node and issue "normal" work since the main DB/2 coordinator node then went to all of the actually processing (partition) nodes to work on the SQL. The "TABLE" method switches that so that the job goes to all of the nodes directly from the DataStage. Since one of the nodes didn't have sufficient UNIX access rights the connection wasn't established so DataStage just returned the ubiquitous -1390 error.