Page 1 of 1
unknown error (To me atleast)
Posted: Fri Jan 09, 2004 1:49 pm
by JDionne
i am getting the following error:
JOCDEVLoadToServer..Into_SQL_Server: OLE DB provider error: The statement has been terminated.
whats that mean?
Jim
Posted: Sun Jan 11, 2004 2:24 am
by roy
Hi,
I guess it means that something about the OLEDB relevance is astray.
but we need to know what is the OLEDB relevance is in your case?
are you simply loading to a regular table using OLEDB stgae or are you trying to populate an OLEDB cube directly?
also, a bit more details on what your doing will help.
if your doing a simple insert via OLEDB stage did you manage to test the OLEDB connectivity successfully? (use the connection wizard)
also double check your sql being sent for annomalies (if my memory serves me there are also befor/after clauses.
IHTH
Posted: Mon Jan 12, 2004 8:56 am
by JDionne
roy wrote:Hi,
I guess it means that something about the OLEDB relevance is astray.
but we need to know what is the OLEDB relevance is in your case?
are you simply loading to a regular table using OLEDB stgae or are you trying to populate an OLEDB cube directly?
also, a bit more details on what your doing will help.
if your doing a simple insert via OLEDB stage did you manage to test the OLEDB connectivity successfully? (use the connection wizard)
also double check your sql being sent for annomalies (if my memory serves me there are also befor/after clauses.
IHTH
I think i found the answer when I tryied to load the file directly through SQL enterprise manager. It was a duplicate key issue.
Thanx
Jim
Posted: Mon Jan 12, 2004 9:39 am
by shawn_ramsey
The OLEDB stage and the SQL Server bulk load stage do not pass pass back the error from the server and will pass back these unusable messages. This problem has been reported to Ascential and there is a case for it. I have found that the best way to find out what is happening is to run the SQL Server profiler tool and trace the errors.
Posted: Mon Jan 12, 2004 9:49 am
by JDionne
shawn_ramsey wrote:The OLEDB stage and the SQL Server bulk load stage do not pass pass back the error from the server and will pass back these unusable messages. This problem has been reported to Ascential and there is a case for it. I have found that the best way to find out what is happening is to run the SQL Server profiler tool and trace the errors.
cool ill do that next time i get crap error msgs.
Jim