By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,611 Members | 1,693 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,611 IT Pros & Developers. It's quick & easy.

Function Sequence Error

P: n/a
Hi All:

I use db2 v8.1 AIX 5.2

Today we recieved an error at the use machine (db2 client) while
loggin into one of the applications.

The details of the error message are:

[IBM] [CLI Driver] CLI0125E Function Sequence Error.SLQSTATE=S1010.

Plz advise on what it means and how can it be avoided..

Regards,
Racerx

Feb 6 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Feb 6, 11:44 am, "Racerx" <p.paingan...@gmail.comwrote:
Hi All:

I use db2 v8.1 AIX 5.2

Today we recieved an error at the use machine (db2 client) while
loggin into one of the applications.

The details of the error message are:

[IBM] [CLI Driver] CLI0125E Function Sequence Error.SLQSTATE=S1010.

Plz advise on what it means and how can it be avoided..

Regards,
Racerx
This error means fetching a row after the resultset is closed

Feb 7 '07 #2

P: n/a
Racerx,

In my humble experience, that error masks other errors. (The one it
masks the most in our shop is an ODBC/ADO timeout error.) However, if
you had the error while "logging into one of the applications", it may
be something else. The only way to see the real error is to run a
trace. Does this application connect using the ODBC driver or an
OLEDB driver?

Craig Wahlmeier
Feb 7 '07 #3

P: n/a
On Feb 8, 2:51 am, cwahlme...@data-tronics.com wrote:
Racerx,

In my humble experience, that error masks other errors. (The one it
masks the most in our shop is an ODBC/ADO timeout error.) However, if
you had the error while "logging into one of the applications", it may
be something else. The only way to see the real error is to run a
trace. Does this application connect using the ODBC driver or an
OLEDB driver?

Craig Wahlmeier
It is a OLEDB driver.
When we changed the aduseclient to SERVER ,we did not recieve the
error again.
Can we have some light on this?

Feb 8 '07 #4

P: n/a
Racerx,

Can you see the error in a CLI trace?
Just put
[COMMON]
trace=1
TraceFileName=c:\clitrace.txt
TraceFlush=1

in your DB2CLI.INI file.

Craig

Feb 12 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.