Page 1 of 1

Windows 2003

Posted: Thu 14 Sep 2006 17:15
by alvinr
I have two issues:
1)Can Oradirect.net 3.5 trial work correctly in Windows 2003 sp1? It is installed but when I pick oradirect as a provider in VS 2005 Reporting services or Integration services , it does nothing. I have tried x86.
2) When I install oradirect in x64 I don't see Oradirect as a provider.

Posted: Tue 19 Sep 2006 05:59
by Alexey
We are investigating OraDirect .NET compatibility with Windows 2003 and x64 architecture. You'll be notified on results as soon as possible.

Posted: Sun 01 Oct 2006 17:06
by alvinr
Any word on the Windows 2003 x86/x64 testing?
Thanks

Posted: Mon 02 Oct 2006 06:20
by Alexey
Please check whether you have two machine.config files:
first under [Windows\Microsoft.NET\Framework\v2.#.#####\Config\] and second under [Windows\Microsoft.NET\Framework64\...].
Then check whether appropriate DBProviderFactories entry exists in the first machine.config file. If not copy it from the second one and reboot.

This is the new error I am getting now in Windows 2003 x64

Posted: Wed 04 Oct 2006 22:19
by alvinr
I can see the Oradirect Provider in the .Net Provider List and also I can test a connection but when I try to use it I get this error: This works properly in Windows 2003 x86.

[DataReader Source 1 [2266]] Error: System.OverflowException: Arithmetic operation resulted in an overflow. at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)

Posted: Thu 05 Oct 2006 06:02
by Alexey
When exactly the error occurs?

Posted: Thu 05 Oct 2006 10:13
by alvinr
This happens when I execute the package. If I pick another provider it works.
This error is in SSIS. I would like to use Oradirect provider to transfer data.

Posted: Thu 05 Oct 2006 10:38
by Alexey
Could you please describe in detail what steps you perform for error to appear. Provide us with detailed scenario.

Posted: Thu 05 Oct 2006 13:50
by alvinr
I just add a DataReader Source task and pick an OraDirect connection as its source. When I try to run it, I get the error. I don't get the error when I use direct mode.

Posted: Fri 06 Oct 2006 07:13
by Alexey
I can't reproduce any error. I've just successfully transferred data from Oracle database table to a text file using non-direct mode of OraDirect.
Either specify a detailed scenario to reproduce error or send us test project if possible.
This works properly in Windows 2003 x86.
Where do you get the errror?

Posted: Fri 06 Oct 2006 13:16
by alvinr
The error is happening in Windows 2003 x64

Posted: Mon 09 Oct 2006 11:55
by Alexey
This problem may have something to do with known "brackets problem" in Oracle client. If you have brackets in a path, Oracle client won't parse it properly.
Could you try to use ODP.NET provider and inform us about results?

Getting error on 2003 64x machine with OCI mode.

Posted: Sat 14 Oct 2006 07:23
by hardik
alvinr wrote:The error is happening in Windows 2003 x64

Hi, I'm getting following error on 2003 64x machine with OCI mode.


***********************************************************************
Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for 64-bit Windows: Version 10.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.1.0 - Production
Time: 14-OCT-2006 10:04:13
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 60
nt OS err code: 0
Client address:

***********************************************************************

Posted: Mon 16 Oct 2006 09:26
by Alexey
Please describe the problem in detail.
Send us small test project if possible to reproduce the problem; it is
desirable to use 'scott' schema objects, otherwise include definition of
your own database objects. Use e-mail address provided in the Readme file. Do not use third party components.
If it is impossible for you to create test project please send us a piece of
your code where the error occurs.