warning message: DSD.BCIPut call to SQLExecute failed.
Moderators: chulett, rschirm, roy
warning message: DSD.BCIPut call to SQLExecute failed.
HI ALL,
I have a simple server job, plain simple source to target mapping with no transformations in transformer. every time i run the job, am getting the following WARNING MESSAGES FOR ALL THE ROWS. majority of the rows are getting transferred to the reject with a few being written to the target table. can someone reflect and help me with it.
ABC..FormatContractMix.LoadTdmContractMix: DSD.BCIPut call to SQLExecute failed.
SQL statement:UPDATE dm_ABC SET current_ind = ?, load_job_name = ?, load_date = convert(smalldatetime, ?) WHERE (contract_type = ? AND sale_type = ? AND sale_source_type = ? AND sale_source = ?)
16 Rows affected.
contract_type = "XXX"
sale_type = "YYY"
sale_source_type = "ABX"
sale_source = "DFG"
current_ind = "Y"
load_job_name = "ABC"
load_date = "YYYY-MM-DD"
I have a simple server job, plain simple source to target mapping with no transformations in transformer. every time i run the job, am getting the following WARNING MESSAGES FOR ALL THE ROWS. majority of the rows are getting transferred to the reject with a few being written to the target table. can someone reflect and help me with it.
ABC..FormatContractMix.LoadTdmContractMix: DSD.BCIPut call to SQLExecute failed.
SQL statement:UPDATE dm_ABC SET current_ind = ?, load_job_name = ?, load_date = convert(smalldatetime, ?) WHERE (contract_type = ? AND sale_type = ? AND sale_source_type = ? AND sale_source = ?)
16 Rows affected.
contract_type = "XXX"
sale_type = "YYY"
sale_source_type = "ABX"
sale_source = "DFG"
current_ind = "Y"
load_job_name = "ABC"
load_date = "YYYY-MM-DD"
The key piece of information is the 16 Rows affected part, which is an extra informational message the database is returning and which causes DataStage to generate the warning. What database is this? Are you purposefully trying to update multiple records at a time?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
am using sql server 2008 for both source and target..using update and then insert for the loading methodology...chulett wrote:The key piece of information is the 16 Rows affected part, which is an extra informational message the database is returning and which causes DataStage to generate the warning. What database is this? Are you purposefully trying to update multiple records at a time?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
OK, then I'll concur with Craig, because DataStage expects the database server (or ODBC driver) to be silent on request but yours is returning informational content. So DataStage alerts you to the fact that unexpected output has been received.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
alright, so what exactly am I to do, to get rid of those warning messages, and how will it effect the whole process...ray.wurlod wrote:OK, then I'll concur with Craig, because DataStage expects the database server (or ODBC driver) to be silent on request but yours is returning informational content. So DataStage alerts you to the fact that unexpected output has been received.
sorry to ask such novice questions, but I am one
![Smile :)](./images/smilies/icon_smile.gif)
Call it what you like, I'm trying to assertain if you are updating 16 rows in the one update you posted on purpose (i.e. it was expected) or by accident and it was an unexpected result. The former you may have to take up with your DBA while the latter could be because (for example) your key choice wasn't precise enough. That answer will help drive how to resolve this.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
it certainly was an unexpected result..i didnt intend to do sochulett wrote:Call it what you like, I'm trying to assertain if you are updating 16 rows in the one update you posted on purpose (i.e. it was expected) or by accident and it was an unexpected result. The former you may have to take up with your DBA while the latter could be because (for example) your key choice wasn't precise enough. That answer will help drive how to resolve this.