I'm tryiing to run a package that transfers data from an Oracle database to a
table in SQL Server 2005. The package runs just fine from the BID.

However, when I deploy it to the server, it fails. It gives a "ORA-01017:
invalid
username/password; logon denied" error when I use the Microsoft OLE DB
Provider for Oracle, and a "ORA-10005: null password; logon denied" error
when I use the Oracle provider for OLE.

Are data connections to Oracle broken or could there be a problem within
deployment?

Can someone provide some good, detailed instructions on how to get this to
work??

Thanks in advance.

Bob Sherman wrote:
I haven't used the Oracle provider, but you may want to look at the
package protection level setting. This uses User Key for encrypting
sensitive information by default, but for deployment I suggest you
change to do not save sensitive. Use configurations to supply passwords
and other sensitive parameters at run-time. I know some provider just
don't seem to save this type of information, and that is no bad thing.
You should be able to workaround this with configurations, and be more
secure as well.

--
Darren
http://www.sqldts.com
http://www.sqlis.com

Thank you Darren - I'll try your suggestions, but it does look data
connections to Oracle are basically BROKEN! There is no excuse for having use
workarounds to accomplish a task that very simple in SQL Server 2000,
especially after Mr. Balmer made such a big deal out 'connectivity' at the
intro on 11/7.

Hopefully they will fix this in the first service pack.

"Darren Green" wrote: