From: Josh C. <na...@gm...> - 2004-08-05 09:41:21
|
I got a log from the sybase module and it is being cancelled by sybase..... ct_con_alloc(ctx0, &conn) -> CS_SUCCEED, conn0 ct_con_props(conn0, CS_SET, CS_USERNAME, "myUser", CS_NULLTERM, NULL) -> CS_SUCCEED ct_con_props(conn0, CS_SET, CS_PASSWORD, "myPass", CS_NULLTERM, NULL) -> CS_SUCCEED servermsg_cb servermsg_cb ct_connect(conn0, "myServer", CS_NULLTERM) -> CS_SUCCEED ct_options(conn0, CS_SET, CS_OPT_CHAINXACTS, 1, CS_UNUSED, NULL) -> CS_SUCCEED ct_cmd_alloc(conn0, &cmd) -> CS_SUCCEED, cmd0 ct_command(cmd0, CS_LANG_CMD, "use myDatabase", CS_NULLTERM, CS_UNUSED) -> CS_SUCCEED ct_send(cmd0) -> CS_SUCCEED servermsg_cb ct_results(cmd0, &result) -> CS_SUCCEED, CS_CMD_SUCCEED ct_results(cmd0, &result) -> CS_SUCCEED, CS_CMD_DONE ct_results(cmd0, &result) -> CS_END_RESULTS, CS_FALSE ct_cmd_drop(cmd0) -> CS_SUCCEED Cursor.execute _lock: count -> 1 ct_cmd_alloc(conn0, &cmd) -> CS_SUCCEED, cmd1 _lock: count -> 2 _set_state: _LAZY_IDLE _unlock: count -> 1 ct_command(cmd1, CS_LANG_CMD, "query goes here; ", CS_NULLTERM, CS_UNUSED) -> CS_SUCCEED ct_send(cmd1) -> CS_SUCCEED _start_results ct_results(cmd1, &result) -> CS_SUCCEED, CS_STATUS_RESULT ct_res_info(cmd1, CS_NUMDATA, &value, CS_UNUSED, NULL) -> CS_SUCCEED, 1 ct_describe(cmd1, 1, &fmt) -> CS_SUCCEED, datafmt0=[name:"" type:CS_INT_TYPE status:CS_FALSE format:CS_FMT_UNUSED count:1 maxlength:4 scale:0 precision:0] ct_bind(cmd1, 1, &datafmt0->fmt=[name:"" type:CS_INT_TYPE status:CS_FALSE format:CS_FMT_UNUSED count:1 maxlength:4 scale:0 precision:0], databuf0->buff, databuf0->copied, databuf0->indicator) -> CS_SUCCEED, databuf0 _set_state: _LAZY_FETCHING ct_cancel(conn0, NULL, CS_CANCEL_ALL) -> CS_SUCCEED _unlock: count -> 0 ct_cmd_drop(cmd1) -> CS_SUCCEED ct_con_props(conn0, CS_GET, CS_CON_STATUS, &value, CS_UNUSED, NULL) -> CS_SUCCEED, CS_CONSTAT_CONNECTED ct_close(conn0, CS_OPT_STATS_IO) -> CS_SUCCEED ct_con_drop(conn0) -> CS_SUCCEED Why would this happen? I'd really not like to have to requery every time that happens. -Josh On Wed, 4 Aug 2004 09:38:23 -0500, Josh Close <na...@gm...> wrote: > I am using sybase with mssql and freetds. When I execute a query I > will get 0 results most of the time when first ran. I will run it > again 1 second later and it will work just fine. > > Could this be a sybase error? Or possibly a freetds error? > > I did 'export TDSDUMP=/var/log/freetds.log' to see what freetds was > doing and got this > > 09:30:53.204554 tds_process_end: more_results = 0 > was_cancelled = 1 > error = 0 > done_count_valid = 0 > 09:30:53.204584 tds_process_end() state set to TDS_IDLE > 09:30:53.204852 ct_cmd_drop() > 09:30:53.204909 ct_con_props() action = CS_GET property = 26 > 09:30:53.204939 ct_close() > 09:30:53.205109 ct_con_drop() > > Does that mean that tds was cancelled at some point by sybase? > > Any help would be great. > > -Josh > |