"-1 Rows affected"-SQL Server Call Execute Failed

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
major
Premium Member
Premium Member
Posts: 167
Joined: Mon Nov 26, 2007 12:21 am

"-1 Rows affected"-SQL Server Call Execute Failed

Post by major »

Hi,

After going through different search outputs i am posting this topic,
We recently upgraded from DS7.5 to DS8.1 Server edition and facing the below issue. Data is not getting updated properly in SQL Server DB.

DSD.BCIPut call to SQLExecute failed.
SQL statement:UPDATE IntlHeadCount.dbo.TIFEED_STAGING SET Process_Indicator = ? WHERE (Month_End_Date = ? AND Employee_ID = ? AND Entry_Dt = ?)
-1 Rows affected.

Month_End_Date(TIME_STAMP format) = "2011-07-31 00:00:00.000"
Employee_ID = "6511521"
Entry_Dt(TIME_STAMP format) = "2011-08-11 04:27:12.000"
Process_Indicator = "Y"

When we tried to change the "Transaction Handling" Settings as
Isolation Level - None, Rows per trabsaction 0, Parameter array size 1,
it was updating, still with warnings. We are confused on the ACTUAL CAUSE.

Any inputs / resolution will be appreciated.

Thank you very much!
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Don't recall ever seeing a negative number in this context. Suggest you get your official support provider involved and also make sure (if you haven't already) that you are current on your fixpacks.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Are there earlier errors in the log, particularly from SQLAllocEnv() or SQLConnect() ? Can other jobs connect to this data source?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
major
Premium Member
Premium Member
Posts: 167
Joined: Mon Nov 26, 2007 12:21 am

fixpacks up to date

Post by major »

Hi Chulett,

Thanks for the response, we verified the Fixpacks and all are up to date.
We are trying to contact support directly though, any other leeds in this regard ?

Thank you very much again!
major
Premium Member
Premium Member
Posts: 167
Joined: Mon Nov 26, 2007 12:21 am

Post by major »

Hi Ray,

There isn't any previous errors or other logs for the specific run.
We are able to connect and retrieve from this data source.

Issue occurs during INSERT/UPDATE and while we change the "Transaction Handling" options, the WARNINGS behave differently.
We are still to find a resolution.

Thanks
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Post by SURA »

Is it ODBC Connector stage / ODBC Enterprise stage?

Try it both as well as Dynamic RDBMS

Just a guess.

DS User
Post Reply