stale cursor???

[Oliver Stratmann]

Hello All!

We have a cursor in an application which fetches some data out of a DB2-DB.
Normally it all works kind of well.
We inserted a routine at certain places in order to do some
perfomance-monitoring .
Now we got the problem, that the cursor closes at some point although not
all the data has been fetched and then next fetch of the application causes
an error.
Is there a way to force the cursor to stay open?

Thanks for your hints or help in advance!

Bye!

Oli

[Sean McKeough]

If this is cli or jdbc, you should check your auto-commit on in your
sp/udf (that's what you mean by routine, right)?

The cursor will stay open until a tx boundary...if you need to commit,
and leave the cursor open, you can create the cursor 'with hold' but if
the commit/rollback is happening accidentally, then you need to find out
where/why.

Oliver Stratmann wrote:

Hello All!

We have a cursor in an application which fetches some data out of a DB2-DB.
Normally it all works kind of well.
We inserted a routine at certain places in order to do some
perfomance-monitoring .
Now we got the problem, that the cursor closes at some point although not
all the data has been fetched and then next fetch of the application causes
an error.
Is there a way to force the cursor to stay open?

Thanks for your hints or help in advance!

Bye!

Oli

[Oliver Stratmann]

Sadly this seems not to be the cause of the error.
The cursor only reads data and performs no commit or rollback.
The routine/program which was inserted into the code, sends time-based
information to a programoutside our application which holds these
information for later analysis. We think that a kind of timeout is performed
on the cursor.
We tried the Hold-option which did not solve the problem.

Thanks for your hint, Sean!
Have a nice Weekend!

Bye!
Oli
"Sean McKeough" <mc******@nospam.ca.ibm.com> schrieb im Newsbeitrag
news:bm**********@hanover.torolab.ibm.com...

If this is cli or jdbc, you should check your auto-commit on in your
sp/udf (that's what you mean by routine, right)?

The cursor will stay open until a tx boundary...if you need to commit,
and leave the cursor open, you can create the cursor 'with hold' but if
the commit/rollback is happening accidentally, then you need to find out
where/why.

Oliver Stratmann wrote:

Hello All!

We have a cursor in an application which fetches some data out of a DB2-DB. Normally it all works kind of well.
We inserted a routine at certain places in order to do some
perfomance-monitoring .
Now we got the problem, that the cursor closes at some point although not all the data has been fetched and then next fetch of the application causes an error.
Is there a way to force the cursor to stay open?

Thanks for your hints or help in advance!

Bye!

Oli

[Sean McKeough]

There's no concept of a cursor timeout...I'd suggest using a statement
event monitor to see what's being done for that application id (what
happens after the open, and before the -501 error).

Oliver Stratmann wrote:

Sadly this seems not to be the cause of the error.
The cursor only reads data and performs no commit or rollback.
The routine/program which was inserted into the code, sends time-based
information to a programoutside our application which holds these
information for later analysis. We think that a kind of timeout is performed
on the cursor.
We tried the Hold-option which did not solve the problem.

Thanks for your hint, Sean!
Have a nice Weekend!

Bye!
Oli
"Sean McKeough" <mc******@nospam.ca.ibm.com> schrieb im Newsbeitrag
news:bm**********@hanover.torolab.ibm.com...

If this is cli or jdbc, you should check your auto-commit on in your
sp/udf (that's what you mean by routine, right)?

The cursor will stay open until a tx boundary...if you need to commit,
and leave the cursor open, you can create the cursor 'with hold' but if
the commit/rollback is happening accidentally, then you need to find out
where/why.

Oliver Stratmann wrote:

Hello All!

We have a cursor in an application which fetches some data out of a
DB2-DB.
Normally it all works kind of well.
We inserted a routine at certain places in order to do some
perfomance-monitoring .
Now we got the problem, that the cursor closes at some point although
not
all the data has been fetched and then next fetch of the application
causes
an error.
Is there a way to force the cursor to stay open?

Thanks for your hints or help in advance!

Bye!

Oli

[Bernard Dhooghe]

"Oliver Stratmann" <st*****@gmx.de> wrote in message news:<bm************@ID-180535.news.uni-berlin.de>...

Hello All!

We have a cursor in an application which fetches some data out of a DB2-DB.
Normally it all works kind of well.
We inserted a routine at certain places in order to do some
perfomance-monitoring .
Now we got the problem, that the cursor closes at some point although not
all the data has been fetched and then next fetch of the application causes
an error.
Is there a way to force the cursor to stay open?

Thanks for your hints or help in advance!

Bye!

Oli

Is the error -501?

When a cursor is openened, it is valid for the package
schema.packageid is was openened in (as can be seen by testing, I do
not know if this behavior is documented): DB2 UDB LUW when processing
the fetch, will look at controlinfo in the package addressed at time
of the fetch. So if a set current packageset has been issued between 2
fetches, and the schema has changed, the fetch will not find his
control info he expects to find in <schema at open cursor
time><packageid> and will return -501 (assuming newschema.packageid
exists, otherwise it will return -805). This is one occurence I know
where a -501 can be returned.

Bernard Dhooghe