SAP Knowledge Base Article - Preview

1984448 - Stack trace when trying to alter server from ASEJDBC to ASEODBC - SAP IQ


Upgrading from SAP IQ 15.x to SAP IQ 16.x

**  Command status when error occurred:  NO COMMAND OR CURSOR ACTIVE    **

Parser command text:
alter server "XXXX" class 'ASEODBC'
Dump all thread stacks at stcxtlib/st_server.cxx: for PID:

stack trace included:
void dbi_alterserver
a_cursor*DoExecuteBodyLocal(Connection*,a_stmt*,a_statement*,a_stmt_identifier*,bool,unsigned,unsigned short
void DoExecuteStmt(Connection*,a_stmt*,a_statement*,a_stmt_identifier*,unsigned short,unsigned)
void db__execute(Connection*,an_sqlpres_receive*)
void RequestProcedure::call()
void Context::call(Procedure*,Context**)
void Worker::call_on_stack(Procedure*)
void TopProcedure::call()
int Worker::spawn(Procedure*)
void EngStream::handle_ind(unsigned char,unsigned)
unsigned RQBaseItem::do_work(Worker*)
void RequestQueue::worker_body()
void request_task(void*)



  • SAP IQ 15.x
  • SAP IQ 16.0
  • SAP IQ 16.1


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP IQ 16.0 ; SAP IQ 16.1 ; SAP Sybase IQ 15.4


sybase, dbi_alterserver, ASEJDBC, ASEODBC, 758579, CR758579, CR#758579, CR 758579, alter server , KBA , BC-SYB-IQ , Sybase IQ , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.