Post reply

SSIS package generating TONS of OraOLEDB errors

  • August 21, 2017 at 2:14 pm

    #338809

    I'm not new to SSIS, but I built a package that takes data from a SQL instance and inserts it into an Oracle database. The package runs successfully (it takes longer than expected) but generates upwards of 100 OraOLEDB errors. Below is a clip of the execution utility output window:

    Ordinarily, I'd assume it's something to do w/the Oracle connector, but why does it still run successfully? Is it trying to make a connection each time this error is thrown? Is there a way to prevent that (or at the very least suppress the error?)

    Thanks in advance!

  • August 21, 2017 at 4:33 pm

    #1956071

    It looks like on one of those errors, there might be some more text after the word description? Is that the case? If so are there any differences between the different messages? Any others or anywhere with more description or further errors?
    The error number itself can come up for various reasons - the connector as you said, permissions on temp folder, how it's being run (command line, job, etc) and the security context.. And then other things indicated by additional descriptions in the messages.

    Sue

  • August 22, 2017 at 5:59 am

    #1956134

    No, text. Sorry. Just computer puke. The only thing I can think of is I think I remember setting the package to always use the default code page because I was getting warnings on it. Other than that, I've never seen a package do this.

Viewing 3 posts - 1 through 2 (of 2 total)

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