I installed the NT version of Datastage, and then exported my project from the Unix version and imported it to the NT version.
The release notes of Datastage says that if you are using Redbrick, you must add the line DISABLE_INFO=YES to the rbodbc32.ini file, if you want to suppress informational messages.
Before I did this all my jobs aborted with info and warning messages. After I added this line, all my jobs work fine accept one, which is still doing exactly the same as before. The jobs are all very similar and I cant see what is causing this.
Has anyone dealt with this issue before ?
Dirk Moolman
Database Administrator
Reach Technologies
South Africa
www.thefuelgroup.co.za
"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit." -Helen Keller
==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================
Bug ?
Something else that makes me wonder -
normally when I get an error on an update or an insert, there is only one update / insert statement and 1 record (result set) in the error.
In the case below I get 2 records in the error.
OPLoadCustomer.Load_Customer.Customer_update: DSD.BCIPut call to SQLExecute failed. SQL statement:UPDATE CUSTOMER SET ACCOUNT_CODE = ?, ACCOUNT_NAME = ?, BRANCH_CODE = ?, CUSTOMER_CAT_TYPE = ?, ACCOUNT_OPEN = ?, STANDARD_VOLUME = ?, CONTRACT_EXPIRY = ?, DUE_DATE = ?, NEW_CONTRACT_REC = ?, CURRENCY_CODE1 = ?, CURRENCY_CODE2 = ?, AGG_LEVEL = ? WHERE (OLD_ACCOUNT = ?) 0 Rows affected.
ACCOUNT_CODE = "69"
normally when I get an error on an update or an insert, there is only one update / insert statement and 1 record (result set) in the error.
In the case below I get 2 records in the error.
OPLoadCustomer.Load_Customer.Customer_update: DSD.BCIPut call to SQLExecute failed. SQL statement:UPDATE CUSTOMER SET ACCOUNT_CODE = ?, ACCOUNT_NAME = ?, BRANCH_CODE = ?, CUSTOMER_CAT_TYPE = ?, ACCOUNT_OPEN = ?, STANDARD_VOLUME = ?, CONTRACT_EXPIRY = ?, DUE_DATE = ?, NEW_CONTRACT_REC = ?, CURRENCY_CODE1 = ?, CURRENCY_CODE2 = ?, AGG_LEVEL = ? WHERE (OLD_ACCOUNT = ?) 0 Rows affected.
ACCOUNT_CODE = "69"
I logged a case with Tech Support for this - cant figure it out.
I add the line "DISABLE_INFO=YES" to the rbodbc32.ini file, and all jobs are fine accept one. When I remove this line, all jobs abort with too many warnings being displayed. The funny thing is that the warnings arent errors, just messages sent back from Redbrick.
Beginning to think its a bug in the software.
Dirk
-----Original Message-----
From: Dirk Moolman [mailto:dirkm@reach.co.za]
Sent: Tuesday, November 06, 2001 3:27 PM
To: Datastage List
Subject: Bug ?
I installed the NT version of Datastage, and then exported my project from the Unix version and imported it to the NT version.
The release notes of Datastage says that if you are using Redbrick, you must add the line DISABLE_INFO=YES to the rbodbc32.ini file, if you want to suppress informational messages.
Before I did this all my jobs aborted with info and warning messages. After I added this line, all my jobs work fine accept one, which is still doing exactly the same as before. The jobs are all very similar and I cant see what is causing this.
Has anyone dealt with this issue before ?
Dirk Moolman
Database Administrator
Reach Technologies
South Africa
www.thefuelgroup.co.za
"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit." -Helen Keller
==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================
I add the line "DISABLE_INFO=YES" to the rbodbc32.ini file, and all jobs are fine accept one. When I remove this line, all jobs abort with too many warnings being displayed. The funny thing is that the warnings arent errors, just messages sent back from Redbrick.
Beginning to think its a bug in the software.
Dirk
-----Original Message-----
From: Dirk Moolman [mailto:dirkm@reach.co.za]
Sent: Tuesday, November 06, 2001 3:27 PM
To: Datastage List
Subject: Bug ?
I installed the NT version of Datastage, and then exported my project from the Unix version and imported it to the NT version.
The release notes of Datastage says that if you are using Redbrick, you must add the line DISABLE_INFO=YES to the rbodbc32.ini file, if you want to suppress informational messages.
Before I did this all my jobs aborted with info and warning messages. After I added this line, all my jobs work fine accept one, which is still doing exactly the same as before. The jobs are all very similar and I cant see what is causing this.
Has anyone dealt with this issue before ?
Dirk Moolman
Database Administrator
Reach Technologies
South Africa
www.thefuelgroup.co.za
"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit." -Helen Keller
==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================