Post reply

OLE DB Error

  • October 5, 2004 at 9:53 pm

    #83849

    Hi,

    I need SQL Server experts to throw some light on the below errors:

    1. A job is getting executed daily scheduled for every 1 hr. Sometimes it runs successfully otherwise it ends up showing an error with the following text:

    OLE DB provider 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399) [SQLSTATE 01000] (Error 7312). The step failed.

    2. A DTS package has been created and was scheduled to run as a jon for every 2 hrs. It is giving the following error text from which I am unable to figure out the proper technical information.

    ...   DTSRun:  Executing...   DTSRun OnStart:  DTSStep_DTSExecuteSQLTask_1   DTSRun OnFinish:  DTSStep_DTSExecuteSQLTask_1   DTSRun OnStart:  DTSStep_DTSDataPumpTask_1   DTSRun OnProgress:  DTSStep_DTSDataPumpTask_1; 44 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 44   DTSRun OnFinish:  DTSStep_DTSDataPumpTask_1   DTSRun OnStart:  DTSStep_DTSDataPumpTask_2   DTSRun OnProgress:  DTSStep_DTSDataPumpTask_2; 23 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 23   DTSRun OnFinish:  DTSStep_DTSDataPumpTask_2   DTSRun OnStart:  DTSStep_DTSDataPumpTask_3   DTSRun OnProgress:  DTSStep_DTSDataPumpTask_3; 18 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 18   DTSRun OnFinish:  DTSStep_DTSDataPumpTask_3   DTSRun OnStart:  DTSStep_DTSDataPumpTask_4   DTSRun OnProgress:  DTSStep_DTSDataPumpTask_4; 5 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 5   DTSRun OnFinish...  Process Exit Code 1.  The step failed.

    These are running on the same box with the following details:

    SQL Server 7.0 (7.00.1063) Standard Edition

    Windows NT 4.0 (Build 1381, Service Pack 6)

    Thanks in advance.


    Lucky

  • October 5, 2004 at 11:15 pm

    #525527

    The step that is failing, what does it do?

    Kindest Regards,

  • October 6, 2004 at 6:39 am

    #525563

    Cannot remember if the error number is the same but I sometimes get the dts message and step failed if there is a data conversion problem (ie date). If the details you posted are from the job history it will not give you enough to work with as it only shows the first 1000 (approx) chars.

    Either run the DTS in a dos prompt or change the job to output to a text file. This should then tell you the row and column that is causing the problem if it is a data issue.

    Far away is close at hand in the images of elsewhere.
    Anon.

  • October 6, 2004 at 3:35 pm

    #525667

    Hi,

    there is too few details. OLEDB job can fail for so many reasons. David is right. It could be a certain type of data or length of the field that causes the problem if it is a data import for example. The job can try to access a database that is not acesible for some reason at certain times. The network issues could be a problem at the beginning and the end of the day with the users logging on and off if the connection timeout is set to a low value

    I looked up error 7312

    Invalid use of schema and/or catalog for OLE DB provider '%ls'. A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog and/or schema.

    Is your job running dynamic scripts? This error is unlikely when connecting to the same database and sometimes job runs well

    Yelena

    Regards,Yelena Varsha

  • October 8, 2004 at 12:21 am

    #525884

    Hello,

    Thanks for all your inputs. I will look up into the respective areas mentioned in your replies and will get back.

    Thanks


    Lucky

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply