If you encounter a problem that you cannot resolve using the manuals, ask the designated person at your site to contact Sybase Technical Support. Gather the following information prior to calling Technical Support to help resolve your problem more quickly.
If a problem occurs while you are trying to access remote data, execute the same script against a local table. If the problem does not exist on the local table, it is specific to Component Integration Services and you should continue through this list.
Find out what version of Component Integration Services you are using:
Note the SQL script that reproduces the problem. Include the script that was used to create the tables.
Find the processing plan for your query. This is generated using set showplan. An example of this is:
set showplan, noexec on go select au_lname, au_fname from authors where au_id = ‘A1374065371’ go
The output for this query will look like this:
STEP1 The type of query is SELECT. FROM TABLE authors Nested iteration Using Clustered Index
The noexec option compiles the query, but does not execute it. No subsequent commands are executed until noexec is turned off.
Obtain the event logging when executing the query by turning on trace flags 11201 – 11205. These trace flags log the following:
11201 – Client connect, disconnect, and attention events
11202 – Client language, cursor declare, dynamic prepare, and dynamic execute-immediate text
11203 – Client rpc events
11204 – Messages routed to client
11205 – Interaction with remote servers
After executing the script with the trace flags turned on, the logging is found in the error log in the $SYBASE/install directory. For example:
dbcc traceon (11201,11202,11203,11204,11205) go select au_lname, au_fname from authors where au_id = 'A1374065371' go dbcc traceoff (11201,11202,11203,11204,11205) go
The error log output is as follows (the timestamps printed at the beginning of each entry have been removed to improve legibility):
server LANGUAGE, spid 1: command text: select au_lname, au_fname from authors where au_id = 'A1374065371' server SIGDISABLE, spid 1: signals disabled on endpoint 10 server RMT_CONNECT, spid 1: connected to server 'SYBASE', using language/charset 'us_english.iso_1', packet size 512 server SYB_TSCN, spid 1, server SYBASE: SELECT au_id, au_lname, au_fname FROM pubs2.dbo.authors WHERE au_id = "A1374065371" server OMNIENDS, spid 1: closing cursor 'O1_16' server OMNICLOS, spid 1: deallocating cursor 'O1_16', type CONNECTION.
This tracing is global, so once the trace flags are turned on, any query that is executed will be logged; therefore, turn tracing off once you have your log. Also, clean out the error log periodically by bringing the server down, renaming the error log, and restarting the server. This creates a new error log.