PKG with Attunity Connector fails with JobAgent

  • Hi,

    I am using Attunity 64 bit connector to load data from Sql server to Oracle database. It works perfectly when I am executing it manually in VS2008 R2. Yesterday I tried using Job Agent to schedule a package which has attunity connector it gave below error. I tried scheduling a package with no attunity connector, this got successfully ran.

    I am working on 64 bit machine.

    I have installed 64 bit oracle client.

    Have this also "ODTwithODAC112021".

    No 32 bit Oracle client. (Still I am able to work on BIDS and Execute the packages).

    I didnot do any kind of Z_SSIS regedit.

    Error:

    "Executed as user: 123. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.

    Started: 6:12:20 PM Error: 2011-09-22 18:12:21.60 Code: 0x000002C0 Source: PKG_Customer_Load Connection manager "Conn_ORA" Description: OCI error encouneterd. ORA-01005: null password given; logon denied End Error

    Error: 2011-09-22 18:12:21.60 Code: 0x0000020F Source: DFT_Order_Load Tgt_Order [1558] Description: The AcquireConnection method call to the connection manager Conn_ORA failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC0047017 Source: DFT_Order_Load SSIS.Pipeline Description: component "Tgt_Order" (1558) failed validation and returned error code 0x80004005. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC004700C Source: DFT_Order_Load SSIS.Pipeline Description: One or more component failed validation. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC0024107 Source: DFT_Order Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 6:12:20 PM Finished: 6:12:21 PM Elapsed: 0.797 seconds. The package execution failed. The step failed."

    I have not found any kind of solution on the internet.

    Please let me know if you require any more information.

    Thanks for your help,

    NAW.

  • Error:

    "Executed as user: 123. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.

    Started: 6:12:20 PM Error: 2011-09-22 18:12:21.60 Code: 0x000002C0 Source: PKG_Customer_Load Connection manager "Conn_ORA" Description: OCI error encouneterd. ORA-01005: null password given; logon denied End Error

    Error: 2011-09-22 18:12:21.60 Code: 0x0000020F Source: DFT_Order_Load Tgt_Order [1558] Description: The AcquireConnection method call to the connection manager Conn_ORA failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC0047017 Source: DFT_Order_Load SSIS.Pipeline Description: component "Tgt_Order" (1558) failed validation and returned error code 0x80004005. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC004700C Source: DFT_Order_Load SSIS.Pipeline Description: One or more component failed validation. End Error

    Error: 2011-09-22 18:12:21.60 Code: 0xC0024107 Source: DFT_Order Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 6:12:20 PM Finished: 6:12:21 PM Elapsed: 0.797 seconds. The package execution failed. The step failed."

    Hi,

    The problem is not with the Attunity connector. If you read the error message carefully, it says that there was a logon error.

    A couple of things I would recommend:

    1. Set the "Delay Validation" property of the connection to False. Otherwise SSIS may attempt to logon before your config file(s) has been applied.

    2. If you have set your package's Protection Level to DontSaveSensitive, no passwords will be saved (even if you checked the "Remember Password" box). You have to set passwords with a config file or some other means when the package is scheduled and executed.

    Hope this helps.

    Martin.

  • Wow.. Its working. Thanks Martin... you the best.

  • naresh.elugala (9/23/2011)


    Wow.. Its working. Thanks Martin... you the best.

    Sure...no problem. I'm sure you could tell I've been bitten by that way too many times before 😛

  • Thank you!! I had the same problem and the solution works.

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

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