DSXchange

Hi.
I am getting the following error for the first time when running a job that is simply loading data from a staging table to the target table...this job has been running for months in dev and we received this error for the first time this morning.
Thanks - - John

Project:PRS (NJROS1BVA0301)
Job name:Load_SAV_Mast_Acct_Bal
Event #:458
Timestamp:11/19/2007 11:51:09 AM
Event type:Fatal
User:PRUDENTIAL\X090842
Message:
Load_SAV_Mast_Acct_Bal..xfm.outSAVMast: DSD.BCIPut call to SQLExecute failed.
SQL statement:INSERT INTO PRFW.FISERV_ACCT_BAL(ACCT_NUM, BAL_DT, PORTF_NUM, NM_LN_PNTR, INSTTN_NUM, CURR_BAL, CURR_ACCRUED_INT, CYTD_FED_WTHHLDG, CYTD_STE_WTHHLDG, LAST_ACTY_OPER_ID, LAST_ACTY_DTM) VALUES (?,?,?,?,?,?,?,?,?,?,?)
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289
SQLSTATE=S1000, DBMS.CODE=-289
[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]Unknown error: SQLCODE -289

Have you checked if it is a space issue in your target database?

Thank You!!! that was it...I ended teh tablespaces and we are back in business!!