DB2/UDB Enterprise connectivity prob

ankita · Post by **ankita** » Tue May 20, 2008 4:18 am

Hi All,

We are facing connectivity errors while using DB2/UDB Enterprise stage to connect from a parallel job as below,

DB2_UDB_Enterprise_58,0: Error Idx = 1;
DB2Driver Embedded SQL message: SQL30082N Security processing failed with reason "3" ("PASSWORD MISSING").
SQLSTATE=08001
;
sqlcode = -30082;
sqlstate = 08001

After searching the forum we have tried below options,
- Able to connect to DB2 from command line of ETL box
- All values are hardcoded, didn't use parameter or env var for below properties:
1. Use Defualt Database = False
1.2. Database = <database>
2. Use default server = False
2.1. Server = <DB2 instance name for the table, same as $DB2INSTANCE >
3. Client Instance name = <DB2 client instance name >
3.1. User = <User name>
3.2. Password = <Password>

But still not able to resolve the issue. ODBC stage is working, so uid/pwd are correct. Could you please suggest any help ?

Thanks !
Ankita

ArndW · Post by **ArndW** » Tue May 20, 2008 6:51 am

Is this a runtime error or do you get it when doing "view data"? If this is a write stage, what method are you using?

ankita · Post by **ankita** » Tue May 20, 2008 6:59 am

It's runtime error while trying to load data to DB2 table using DB2/UDB Enterprise stage.

ArndW · Post by **ArndW** » Tue May 20, 2008 7:07 am

Do you get the same error when using an update/insert method instead of load? For LOAD you need additional permissions to the table, I am fairly certain that they are documented in the installation guide.

ankita · Post by **ankita** » Tue May 20, 2008 7:07 am

Sorry I missed your 2nd question, we have used Append -> Write mode to insert all records. No record qualifies for update.

ankita · Post by **ankita** » Tue May 20, 2008 7:14 am

ArndW, Thanks for your suggestion ! I just tried with upsert (with same set of input) , but failing with similar problem.

ArndW · Post by **ArndW** » Tue May 20, 2008 7:18 am

Can you try using the "load" method to see if the error message is the same? Sometimes you can examine the generated load scripts to see what values DataStage is using.