Any known issues with Windows Server 2003?

Any known issues with Windows Server 2003?

Postby Oleksiy Kosenkov » Tue 04 Jul 2006 16:40

Hello dear CoreLabs,
our customer is getting a NullPointerException inside CoreLab.Oracle.OracleDataReader.Read()

The fragment of the stack trace follows:
Code: Select all
System.NullReferenceException: Object reference not set to an instance of an object.
    at OciDynamicType.nativea(HandleRef , HandleRef , Int32 , UInt16 ,  UInt32 )
    at OciDynamicType.a(HandleRef , HandleRef , Int32 , UInt16 , UInt32 )
    at a.a.ar.c(Int32 A_0)
    at CoreLab.Oracle.OracleDataReader.Read()

It looks like it occurs on just one PC running Server 2003 SP1. All other (multiple) PCs running Windows XP Pro and Home never get this error.
This PC however is pretty important for the customer (so re-install the OS or move to another PC is no option).

How would you suggest to approach this problem?
Is there any logging/debugging/tracing facility in OraDirect .NET 3.20 we can use?

Thanks for any hints.
Oleksiy Kosenkov
Oleksiy Kosenkov
 
Posts: 3
Joined: Tue 04 Jul 2006 16:33

Postby Alexey » Wed 05 Jul 2006 08:10

Does this error occur always with that query or sometimes?
It can be caused by the difference of Oracle client. Do you have the same version of Oracle client on all your computers?
Could you 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. Do not use third party components.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Oleksiy Kosenkov » Wed 05 Jul 2006 08:39

Hello Alexey,

Alexey wrote:Does this error occur always with that query or sometimes?
This error occurs always on this PC, and never on other PCs. It's inside our application, so I'm pretty sure it's always called in exactly the same context.

Alexey wrote:It can be caused by the difference of OracleClient. Do you have the same version of OracleClient on all your computers?
Yes, the client is the same, 10.2.0.1

Alexey wrote:Could you send us small test project if possible to reproduce the problem; it is desirable to use 'test' schema objects, otherwise include definition of your own database objects. Do not use third party components.
Hmmm... Unfortunately it's hardly possible, because a) it fails on just one PC, on others it works well; and b) faulty PC is at the customer (the customer of our client) site, so installing development environment in order to try an arbitrary SQL is problematic.

In any case, we may expect you are not able to reproduce this error inhouse, because it works in hundred of cases by us and fails on that one PC only.

Your idea about somehow different Oracle client is reasonable. The point is to find what is different. We took the usual approach - re-installed Oracle client and then re-installed our application which incorporates OraDirect; with no effect unfortunately.
Oleksiy Kosenkov
 
Posts: 3
Joined: Tue 04 Jul 2006 16:33

Postby Alexey » Thu 13 Jul 2006 10:40

Windows 2003 is installed on 32x or 64x PC?
What data do you read using CoreLab.Oracle.OracleDataReader.Read() method?
Why don't you use 3.50 version?
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Oleksiy Kosenkov » Thu 13 Jul 2006 15:36

Hello Alexey,

1) It's 32-bit hardware
2) We are reading the whole row. Columns are of type DATE, VARCHAR2 (up to 2000 char long) and NUMBER
3) Using 3.20 because our application was built when only this version was available. Since the app is already deployed multiple times we unwillingly consider updating data provider.

By the way, there is additional info just arrived.
The customer has re-installed OS on that host, then all components, but the problem stays. Then he installed same OS, same Oracle Client and same CoreLab onto another host, and it works well. So the problem may pretty well reside inside Oracle Client or even deeper.

Knowing a magic way to debug problems with OraDirect would be very beneficial for us nevertheless...
Oleksiy Kosenkov
 
Posts: 3
Joined: Tue 04 Jul 2006 16:33

Postby Alexey » Fri 14 Jul 2006 06:47

You might utilize direct mode to avoid using of Oracle client.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for Oracle