SQLSever - SQLSTATE = 42000, fNativeError = 2754

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Aquilis
Participant
Posts: 204
Joined: Thu Apr 05, 2007 4:54 am
Location: Bangalore
Contact:

SQLSever - SQLSTATE = 42000, fNativeError = 2754

Post by Aquilis »

hi all,

Trying to Invoke a SQL-Server Stored procedure from DataStage. Am encountering below Fatal error.
a. Unfortunately same stored procedure is invoked in different job with same input parameter and is working fine.
b. Also, same job is working fine in other enviroments.
c. Stored procedure is workign fine, if I execute it directly in database.
d. Verified the privielges on stored procedure and everything seems fine.

Missing something. Am not able to figure out what's hapepning around with it.

Code: Select all

Warning: SQLSTATE = 42000, fNativeError = 2754
Fatal Error: Fatal: [IBM(DataDirect OEM)][ODBC SQL Server Driver][SQL Server]Error severity levels greater than 18 can only be specified by members of the sysadmin role, using the WITH LOG option.
Aquilis
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is the user who is invoking from Datastage a member of sysadmin role?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Aquilis
Participant
Posts: 204
Joined: Thu Apr 05, 2007 4:54 am
Location: Bangalore
Contact:

Post by Aquilis »

All other jobs are working with same user and more over same procedure being triggered from different jobs with different hardcoded value.

I feel it's related to database, SQL server.
Aquilis
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: SQLSever - SQLSTATE = 42000, fNativeError = 2754

Post by SURA »

Aquilis wrote:a. Unfortunately same stored procedure is invoked in different job with same input parameter and is working fine.
b. Also, same job is working fine in other enviroments.
I do noticed ( not the same issue) sometimes Datastage behaves bit strange! That too, these kind of issues will come to the jobs ( not all ) which was modified & recompiled !

Datastage may fails to overwrite the behind the screen files properly could be the reason I guess ( Gurus please correct me if my thought is wrong )

1) Fine , you said working fine in other env? The other is Dev/ ?

2) Delete the job where it is not working and import the job from other env where it is working fine!

Let us know the outcome .
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Post Reply