Page 1 of 1

Surrogate Key Error

Posted: Mon Aug 23, 2010 11:54 pm
by nmacolin
Hi all. Any help would be appreciated.

I have the following scenario.

Surrogate_Key_Stage requesting Sequence numbers from a DB2 DB residing on z/OS.

I have the following properties set in the Surrogate Key Gen:

Database Type = Db2
Database Name = #DBNAME#
password = #PWSD#
ServerName = #SERVERNAME#
use default database = FALSE
use default server = FALSE
username = #USERNAME#
Generated Output Column Name = SEQ_VALUE_KEY
source Name = #SCHEMA#.SQ_PROJECT_COMPNT_KEY
source Type = Database Sequence

The sequence has been defined in the Database as

CREATE SEQUENCE DBDDMGR.SQ_PROJECT_COMPNT_KEY
START WITH 1
INCREMENT BY 1
NO MAXVALUE
NO CYCLE
CACHE 20;

I get the following Errors :
(1)
Surrogate_Key_Generator_7,1: Error Idx = 1;
DB2Driver Embedded SQL message: SQL0551N "ISDMG03" does not have the privilege to perform operation "CREATE
IN" on object "DB2T.DSADM.DB2ESQL8.()". SQLSTATE=42501
;
sqlcode = -551;
sqlstate = 42501



(2)
Surrogate_Key_Generator_7,0: Program not bound to database
Attempting to bind /opt/IBM/InformationServer/Server/DSComponents/bin/db2esql80.bnd to the database DB2T ....failed


Any insite is appreciated. DBA is not aware of any permission issues. So at this point I don't know if it's the IIS server 8.1 that needs to be looked into or the Database.

I did find a reference to a patch, but our Admin suggests that is for Enterprise Stage ??

http://www-01.ibm.com/support/docview.w ... wg1JR32038

So lost and confused. Can someone who has an indepth knowledge please let me know where to from here.

Regards
Nick

Posted: Tue Aug 24, 2010 4:59 am
by ray.wurlod
Run this message text by your DBA.
"ISDMG03" does not have the privilege to perform operation "CREATE IN" on object "DB2T.DSADM.DB2ESQL8.()".
Get your DBA to show you the privileges that "ISDMG03" has.

Not sure about the second message; it appears to state that a bind command has failed (could be bind19 or bind20). Yet is seems odd that the program can get through to DB2 if this is the case. Again, your DBA should be able to advise. But, as always, fix the first error first.