August 5, 2008 at 3:08 pm
Hello,
I have a machine with SQL Server 2005 x64 another machine with x32, I use packages SSIS to bring information from Oracle, but these packages doesn't work machine x64. It works only machine x32.
I Have installed both Oracle providers on the machine x64 and I use the sintaxe bellow
dtexec.exec /f "d:\package.dtsx"
What do I need to this works?
Sorry my bad English
August 6, 2008 at 12:35 am
Hi,
Can you provide little bit mroe information like what error message it throws or error number.
August 6, 2008 at 5:42 am
Hi,
I have several erros, but this package works in 32 bits
Started: 08:32:21
Error: 2008-08-06 08:32:54.32
Code: 0xC0016016
Source:
Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this info
rmation. This error occurs when there is a cryptographic error. Verify that the correct key is available.
End Error
Progress: 2008-08-06 08:33:11.00
Source: Data Flow Task
Validating: 0% complete
End Progress
Error: 2008-08-06 08:33:11.23
Code: 0xC0202009
Source: Package Connection manager "BASETESTE.ESA_SILVA"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error
Error: 2008-08-06 08:33:11.25
Code: 0xC020801C
Source: Data Flow Task OLE DB Source [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "BASETESTE.ESA_SILVA" failed with e
rror code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2008-08-06 08:33:11.25
Code: 0xC0047017
Source: Data Flow Task DTS.Pipeline
Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
End Error
Progress: 2008-08-06 08:33:11.25
Source: Data Flow Task
Validating: 50% complete
End Progress
Error: 2008-08-06 08:33:11.25
Code: 0xC004700C
Source: Data Flow Task DTS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2008-08-06 08:33:11.25
Code: 0xC0024107
Source: Data Flow Task
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 08:32:21
Finished: 08:33:11
Elapsed: 49.859 seconds
C:\Documents and Settings\mcsrvbd>
August 7, 2008 at 12:38 pm
Hi friends,
Anybody help-me
tranks
August 8, 2008 at 3:55 am
- First you need to encrypt your login information with a password. The target machine uses an internal key to encrypt sensitive information (properties of the package). Need to redeploy after this.
- Second you need to use 32-Bit drivers in the x64 machine as well, switch the SSIS settings to x86 only. You need to install the 32-Bit Oracle client with probably OLEDB as well instead of x64.
August 8, 2008 at 5:54 am
Hi,
In My package I use a login to conect on ORACLE and another to conect to SQL Server, but I don't use login to encrypt the package. Must I use?
I have both drivers in the machine (x32 and x64)
Should I install only driver x32?
August 8, 2008 at 6:07 am
I'd recommend to use the 32-Bit drivers only. Especially in Oracle the concurrent 32-bit and 64-bit driver installation can be tricky and avoid installation of service packs, etc. Usually the speed is the same as the bottleneck is the network, not your machine.
You MUST use a password to encrypt the login information when you transfer a SSIS package to another machine, otherwise you cannot decrypt the password again. Only exeptions is "no passwords used" or "using NT logins".
August 8, 2008 at 6:30 am
Excuse my insistence, but I am very difiduldade in this process.
I configured a password on packagePassword and in option protectionlevel = EncryptSensitiveWithUserKey
Would be it same?
or in connection managers, how can I decrypt password?
August 8, 2008 at 7:03 am
After you defined to encrypt with a password you need to open each data connection and re-type the login information (especially the password). Test the connection afterwards.
You should do this with EVERY connection in the package(s)
Then re-deploy the package to the target server. When opening (runtime...) you are asked for the new package password and the system then is able to de-crypt the passwords you encrypted by re-typing the passwords before.
In my experience it is NOT POSSIBLE just to add the password as this seems to delete all password information (not sure how this process is working in detail but we needed to re-type all passwords in our systems). The passwords are then saved unless you change the package password.
August 8, 2008 at 7:32 am
Which Oracle clients are you using? I know there are issues with the 10.2.0.1 clients on a 64 bit install of SQL Server. The issue is with the Program Files (x86). It is fixed by patching the Oracle clients to version 10.2.0.3.
Mike
“I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant.”...Robert McCloskey
___________________________________________________________________
August 8, 2008 at 8:02 am
I use exactly the version 10.2.0.1
I will search the version 10.2.0.3 to do test
thank you
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply