Fetch Out of sequence

Hi,

I'm getting the error 'Fetch Out of Sequence' in QA and Production servers but not in development server. Our QA and production servers are under AIX OS.

The particular module was working fine in production server till our previous release, but in the last release it is not working though we haven't done any code change.

Please help me in getting the solution for fixing this issue.

Thanks in advance.

[442 byte] By [lalia] at [2007-11-27 4:25:51]
# 1
I bet you are using indexing by name (column name) rather than by integer.
jschella at 2007-7-12 9:34:08 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 2
No, we are indexing by number. Please note that this is working fine in our development environment. But in production enviroment it is not working.
lalia at 2007-7-12 9:34:08 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 3
Probably help to know what database.Googling suggests any number of reasons for this. Likely your last update changed code that is encountering one of these.
jschella at 2007-7-12 9:34:08 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 4

> No, we are indexing by number. Please note that this

> is working fine in our development environment. But

> in production enviroment it is not working.

This actually makes things worse IMO.

The problem is one of the following and all of these should be investigated.

1) Differences between platforms in development and production regarding database vendor and/or version, driver vendor and/or version. It's possible you have a development environment that supports an out of order fetch while in the production you don't.

Hopefully it's (1) because the next two are worse.

2) There are unaccounted for changes in the structure of tables between your development and production environments. These are far more likely to be the source of the problem if you are doing something silly like SELECT *

3) You have a threading problem of some sort. This one would be the nastiest but is certainly a possibility and often the kind of problem one encounters when one did not test properly and then has problems taking working code from a development environment to a production environment.

cotton.ma at 2007-7-12 9:34:08 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 5
Hi,We are using oracle 8.1.7 database in development and in production.One more thing to be noted here is that if we connect to the production database from the development environment, it works fine.Thanks
lalia at 2007-7-12 9:34:08 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...