Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

thrd__cur_declare failed

2 views
Skip to first unread message

Jim R

unread,
Nov 20, 2008, 4:51:19 PM11/20/08
to
I'm getting an error in my log and there's nothing before it in the log that seems to be an issue. The only lines after the startup stuff is:
 
osw_test2: DEBUG: spid 12: Processing CS_CURSOR_DECLARE
osw_test2: DEBUG: spid 12: thrd__cur_declare: Allocated cmd 0x1bdb420
osw_test2: DEBUG: spid 12: thrd__cur_drop: dropping cmd 0x1bdb420
osw_test2: DEBUG: spid 12: CS_CUR_STATUS == CS_CURSTAT_NONE
osw_test2: ERROR: spid 12: thrd__cur_declare: thrd__results() failed
osw_test2: ERROR: spid 12: thrd_cursor_passthru: thrd__cur_declare failed
osw_test2: ERROR: spid 12: event_cursor: srv_cursor_props(CS_GET) failed
 
 
my version info:
 
osw_test2: INFO: Sybase OpenSwitch/15.1/P/PC Intel/0/OPT/Thu Nov 15 21:48:29 2007
osw_test2: INFO: OpenSwitch using Open Server version: Sybase Server-Library/15.
0/P-EBF14421-14416 ESD #8/PC Intel/BUILD1500-096/OPT/Thu Mar 01 18:47:51 2007
 
osw_test2: INFO: OpenSwitch using Open Client version: Sybase Client-Library/15.
0/P-EBF14416 ESD #8/PC Intel/BUILD1500-096/OPT/Thu Mar 01 18:47:51 2007
 
Do you know what is causing the error and is it something I should be concerned about?
 
Thanks
JR
 

Neal Stack [Sybase]

unread,
Nov 20, 2008, 6:07:58 PM11/20/08
to
Hello,

Basically, that message means that OpenSwitch received a request
from a client application to declare a cursor. When OpenSwitch
attempted to decalre it (see ct_cursor(CS_CURSOR_DECLARE)), the
call failed:
http://infocenter.sybase.com/help/topic/com.sybase.dc32840_1500/html/ctref/CHDGACJF.htm

Is it something you should be concerned about? If a tree falls
in the forest and no one is around to hear it, does it make a sound?
Is one of your client application support groups complaining about it?

I can't tell why the declare failed. It could be a Sybase bug but
it could also be a bug in the client application code. Without
further investigation, it would be hard to say which.

Do you know which client application caused OpenSwitch to raise this error?

Does it happen frequently?

If I had a better understanding of the circumstances, I could make
some recommendations for further debugging if you are interested.

Regards,
Neal

0 new messages