Sybase数据库技术，数据库恢复专家

Resolution: Reviewed Sep 2002. Presently not targeted for any future release of the product as changes between dblib and ctlib based isql are expected. This is documented in the 11.1 'Release Bulletin Open Client/Server' manual, section on 'Standalone Utilities'.

There are several differences between dblib and ctlib based isql. A change so late in the game could cause a regression to scripts at other customer sites.

sendResults (SrvSession, SrvDataFormat [], Object [][]) method.

Clients wishing to send widetable results with the sendResults method should pass in an array of SrvRowDataFormat2 objects to the newly created

sendResults (SrvSession, DataFormat [], Object [][]) method.

Status: Reviewed Sep 2002. Pending further investigation by Engineering.

an acknowledgement of the TDS attention packet. The problem occurs while putting

together confidential data packets to determine if the ack has arrived.

The DISABLE_UNPROCESSED_PARAM_WARNINGS connection property can be set to true in order to stop jConnect from creating these SQLWarnings.

Resolution:

This CR was reviewed Sep 2002 and a decision was made to not implement this request.

Both Sybase and Datadirect have considered this request and feel that if an unwary customer starts to fiddle with the switches, they could potentially create a bigger problem than when they started.

A better option is to edit the registry by creating scripts for example, with the required switches after confirming in development/QA that these switches work.

1. The correct MQ Series classes for the client platform must be installed - ma88. This can be downloaded from ibm for free.

2. Some WebSphere jars must be copied over to the client platform: websphere.jar, utils.jar, ujc.jar, ras.jar, ns.jar, jca.jar, j2ee.jar, iwsorb.jar, ibmorb.jar. All these jar files must be in the JMS_SES_JVM_CLASSPATH property, as well as the JMS ot driver dbt26jmsjni.jar, in your nnsyreg.dat file.

3. You must use a WebSphere VM (and it must be the same version vm as the one the WebSphere app server is using!). In the WebSphere install, you can unselect everything, but the developer tools. This will install the vm for you. You can also copy the vm over from the app server, if it is on the same platform as the client. I'm not sure if you can download from IBM just the vm.

It would be much easier for the customer to use the MQSeries ot driver with WebSphere, but JMS does work.

updated to reflect the correct location for the file objectid.dat:$SYBASE/config.

Note that the SQLWarning messages will be displayed in the fashion that the user has select from the options jisql menu. By default, the Warnings are displayed in the message box at the bottom of the jisq connection window.

In OC 11.1.1 and 12.0 (prior to OC 12.0 EBF#15, see

CR 291708) when using isql with "-wXX" parameter, data

that was greater than XX did not wrap. This configuration

option reverts the behavior to the old (and incorrect)

behavior exhibited in OC 11.1.1 and OC 12.0 prior to EBF

#15.

OpenSwitch.

For more information, see the javadocs for com.sybase.jdbcx.Connection.

Typically, jConnect will send unichar/univarchar parameter data when the following conditions are met:

1. The server is ASE, and the version is 12.5 or higher

2. The server is using utf-8 as its default character set

3. The client has specified a value of 6 for the JCONNECT_VERSION connection property.

Using unichar/univarchar data can sometimes lead to a performance degradation at the server, so if a client wishes to enable widetable functionality (which requires a JCONNECT_VERSION of 6), but wishes to disable unichar, they can set the new property value to true.

Reviewed Dec 2002. This issue is being tracked under ASE CR 228419 and is targeted (but not committed) for the ASE 15.0 release.

server name resolution, providing a lookup for hostname and port number for connectivity.

To utilize this feature just bypass adding the Network Address in the DSN configuration. Go to the section in the General Tab titled "Use Interface File for Connection Information (Optional)". Enter the full path and filename of the SQL.INI interfaces file for the field labeled "Interfaces File", like "C:\SYBASE\INI\SQL.INI". Enter the ASE Server name as found in the SQL.INI file in the field for "Server Name". When you attempt to connect, the ODBC Driver will get the Hostname and Port number for the ASE Server, and use that information to make the connection.

for the ASE Server, and use that information to make the connection. The attribute names to use when you are using a connection string in your application are "Interfaces File" and "Interfaces File Server Name".

work around: Set NNOT_TIL_GET_BLOCKING_TIMEOUT in each transport to infinite (-1) and the problem does not occur.

with error: blk_rowxfer():internal BLK-Library error: No value or

default available and NULL not allowed.

Tested with:

HP UX: OC 12.5 EBF 10665

Sun Solaris: OC 12.5 EBF 10659

WinNT 4.0 SP6: OC 12.5 EBF 10679

Important: Works ok with SQLAdvantage 12.5 and JISQL

A good rule of thumb is that clients who want to send streaming data to the server should make sure to set the JCONNECT_VERSION connection property to 4 or higher (this is the default in jConnect 5.x), and they should call the PreparedStatement.set*Stream methods to set the parameter.

For clients using widetable-enabled ASE servers (version 12.5 and higher), and who are interested in sending values to large (> 255 byte) varchar and varbinary columns and stored proc params, the client should use the setString and setBytes methods. This will help clients avoid getting errors from the server saying that explicit CONVERTs are needed.

if (! Connection.getAutoCommit())

{

Connection.setAutoCommit(true);

}

without getting an Exception from the database.

With the new behavior, a client will still be able to specify a HOSTNAME using the connection property. But, if the client does not specify one, jConnect will attempt to learn the host machine's name, and will send that to the server at login time.

1. An EOLEException with message "Errors Occurred" is raised when inserting Chinese characters.

2. An EOLEException with message "Parameter data overflow for small money at ordinal 6" is raised when inserting numeric data greater than 99999, eventhough in delphi the data type is ftBCD.

Reference.get("REPEAT_READ").getContent();

the following error...ERROR: spid 230: SRVLIB: NUM=16315 SEV=15 ST=0: srv__read_packet:

Protocol error occurred: length in header (3338) more than packet size(512)

To setup jConnect to utilize failover (without using an LDAP server), clients should do the following:

1. Set the REQUEST_HA_SESSION connection property to true (note that clients must do this when using an LDAP server as well)

2. Set the new SECONDARY_SERVER_HOSTPORT property to the hostname and port number of the failover server. For example, if the failover server was on host machine foo, and the server was listening on port 4000, you might use the following lines of code:

Properties props = new Properties();

props.put("REQUEST_HA_SESSION", "true");

props.put("SECONDARY_SERVER_HOSTPORT", "foo:4000");

Note that a colon is placed between the hostname and the port number, just as in a typical JDBC URL.

Con_comres and con_ihandle field in the surrogate conhandle need to be updated when the surrogate conhandle is built to point to the correct EIB and IHANDLE's This will cauise OC4's when Tran Iso is turn on an a transaction tries to wirte to the SYTDLOG1, and there may be other problems that are not documented.

ASE 12.5 cannot handle a 4.6 tds stream in a mixed mode program the ctx handle from OSC is used and the TDS version is hardcoded to version 4.6.

thrd__ct_close: Connection busy, ct_close(CS_UNUSED) failed

thrd__ct_con_drop: ct_con_drop() failed

This issue would show up when a client used a command such as 'set statistics io, time on', which results in query-processing statistics being sent to the client as SQLWarning messages.

with error code: 114, pc=0, call=1, seg=0

114 Attempt to access item beyond bounds of memory (Signal 10)

'The Instruction at "0x100403de" feferenced memory at "0x000001ec". The memory could not be "read".' This has been fixed in version 02.70.0016

It returned CS_CMD_SUCCEED when it should have returned CS_CMD_FAILED.

for HPUX 11.11 and PHNE_28538 for 11.00.

Syntax error at token 'ON', line 1 offset 46.

This fix is a workaround for a java bug described in the following location:

http://developer.java.sun.com/developer/bugParade/bugs/4623303.html

For more information on canonical charset names, see this document:

http://java.sun.com/products/jdk/1.2/docs/guide/internat/encoding.doc.html

1. Client has not set the HOSTNAME connection property and the host computer's name (retrieved through java.net.InetAddress.getLocalHost().getHostName()) is longer than 30 bytes. jConnect will now truncate any hostname longer than 30 bytes to a max of 30 bytes.

With this CR, we also added a performance enhancement to Connection.commit() and Connection.rollback().

Finally, we added a fix to properly report the datatype in metadata when the server sends back LONGCHAR data.

The context allocation routine failed.

The following problem caused the failure:

Invalid context version.

Now, this build of the Sybase ASE ODBC Driver, ctlib based, requires you to use OCS 12.0 ONLY. If you want to use OCS 12.5 you must use EBF 11081 (12.5.0/P-EBF11081 ESD#11/04.10.0000).

ct_poll can generate a SEGV.

Tested and reproduced with Sybase ASE ODBC Driver 4.10.0000 and 4.10.0049.

Works fine with old "Sybase System 11" ODBC Driver 3.11.0000

Also works fine when using ADO, instead of RDO, with any ODBC driver version.

The workaround is to include rdoEngine.rdoDefaultCursorDriver = rdUseOdbc in coding.

To request unichar/univarchar support, a client must set the JCONNECT_VERSION connection property to 6. Furthermore, a client must set the DISABLE_UNICHAR_SENDING property to false (we have changed this property so that it now defaults to true).

When unichar/univarchar is properly enabled, jConnect will send unichar/univarchar parameter data only if the characters cannot be converted to the negotatiated character set of the Connection.

For example, if the server has iso_1 as the default character set, and the client tries to send a unichar representation of the euro character (and unichar is enabled), jConnect will send the String to the server as unichar/univarchar.

both SNA and TCP/IP protocols

when called with many paramters multiple times.

written to log file (such as with DEBUG=a) in stress-test mode.

Workaround: Use DEBUG=a only for debugging purposes when there is a problem.

Otherwise, DEBUG=e is recommended.

Message number: LAYER = (0) ORIGIN = (0) SEVERITY = (0) NUMBER = (0)

Message String: blk_init(): blk layer: internal BLK-Library error: Failed when CT_Lib routine ct_fetch(BLK_IN_GET_FMT) called.

Workaround is to use ODBC Driver 4.20 instead.

This property is used in conjunction with the SELECT_OPENS_CURSOR property. When SELECT_OPENS_CURSOR is set to true, *and* this property is set to any positive value, select statements executed by the client will open a cursor. The cursor will have a fetch size of the value set with this property.

Note that when this property is set, jConnect changes the way it normally interprets the SELECT_OPENS_CURSOR property; normally SELECT_OPENS_CURSOR will open a cursor only if the SQL contains a 'FOR UPDATE' clause. When IMPLICIT_CURSOR_FETCH_SIZE is set to some non-zero value, jConnect will open a cursor for every select, with or without a FOR UPDATE.

is called twice for the same PoolConnection object (which will implicitly close

the connection open by the first call). JDBC spec says that this should not happen.

Customer finds srv_props(CS_SET,SRV_S_IFILE) regression moving from

12.0 openserver to 12.5 openserver.

char intf[255] = {"\0"};

strcpy(intf, "./interfaces");

retcode = srv_props(ctos_ctx->cx_context, CS_SET, SRV_S_IFILE, intf, CS

_SIZEOF(intf), (CS_INT *) NULL);

This change should result in better performance for some customer applications. It will not hurt performance.

resulting in reduced performance.

This behavior can be useful, for example, in a case where the timeout is caused by a deadlock situation.

1. set DYNAMIC_PREPARE connection property to true

2. create a batch of PreparedStatements

3. call setFetchSize()

4. executeBatch()

jConnect will still properly execute the batch. Before this fix, jConnect would become confused by the setFetchSize(), which would create a cursor to process results (even though a cursor makes no sense in the context of executing a batch of statements).

to start displaying these errors.

jConnect should be altered to code around the current ASE behavior to provide the proper JDBC behavior which is to limit the ResultSet to the setRowMax() number of rows whether a cursor is used or not.

"-2147217887 : Multiple-step operation generated errors. Check each status value." To prevent this from happening, a new connection option is required, ReportUnknownForUpdatable, which is False (0) by default. When set to TRUE (1), this option will always return SQL_ATTR_READWRITE_UNKNOWN for the SQL_DESC_UPDATABLE field of the result column descriptors. This will only apply to stored procedure result sets.

(french) accented characters, defncopy is adding extra spaces to the text of the

procedure when the client configured with iso_1.

analyze functionality check for mismatched configuration

options in the rcm.cfg and the OpenSwitch.cfg files.

http://sybooks.sybase.com/onlinebooks/group-or/orp1250e/osconins/@Generic__BookView?DwebQuery=SSID

column without -E option specified.

swedish etc. receives a com.sybase.jdbc2.tds.TdsDataOutputStream exception when the

length is around 255 characters.

Connection String name for SybaseWorkArounds

Long Name: SybaseWorkArounds

Short Name: SWA

Possible Values of SybaseWorkArounds for RaiseError:

0 RaiseError as Warning, the default

1 RaiseError as Error

Pls note that the RDO/PPT definitions supplied in the Installation JCL are corrected as of 12.50.01 (see CR 274424)

CCSID=850,CHARTYPE=A,CHARSIZE=1,PAD=20,

Full example listed below:

SYGWMCXL TYPE=INITIAL

SYGWMCXL TYPE=ENTRY,CHARSET=cp850,CHARSETBYTES=S, *

CCSID=850,CHARTYPE=A,CHARSIZE=1,PAD=20, *

A2E=(21=5A,5B=BA,5D=BB,5E=B0,7C=4F,AA=5F,BD=4A), *

E2A=(5A=21,BA=5B,BB=5D,B0=5E,4F=7C,5F=AA,4A=BD)

The following modules are new in OSC and OCC 12.5 for IMS/MVS and must be preloaded under MVS before the IMS region is started:

+ LU62IMS, CPICIMS and TCPIMS

This now needs to be documented in the newer install Guides there is no mention in the 12.5 guides.

They cannot be passed as zero, otherwise ct_cursor() call will fail.

Both the primary and redundant RCMs respond to the same login

request after they reestablish connectivity to primary OpenSwitch.

Customer would like the ability to format the footer divisions and spaces between values for the compute clause in isql.

Eliminate the need to activate the tracing programmatically in the jconn2d.jar

of concurrent connections, OpenSwitch will report error:

OpenSwitch error cfg_read: Unable to open 'OpenSwitch.cfg': Too many open files

select from a table that contains a column that is of type date or of type time.

Tested and reproduced with:

cobpre 12.5 EBF 11508 (NT) and 11510 (AIX)

cobpre 12.0 EBF 11240 (NT) and 11235 (AIX)

cobpre 12.5.1 EBF 11410 (NT)

Like Open Cleint on the lan customer would like High Availabilty.

Would like CTBCONNECT using SYGWHOST lib to be able to failover to a backup server if the connection to the first server fails.

the current transaction status which is included in every TDS_DONE/

TDS_DONEPROC/TDS_DONEINPROC packet. jConnect already allows this for

SybExceptions and SybWarnings and further; CT-Lib provides access to

this information via the API call "ct_res_info(...TRAN_STATE...) "

This is causing a problem for customer that stay connect all day running requests.

At Logoff SYGWCTXH does a TDFREE and cleans up the chained 4K ESDSA Parm Desc, since there is many of them SUGWCTXH is in a tight loop cleaning up the descriptors and causes CICS to abend the TASK with a AICA.

NPTL threads libraries of RH AS 3.0. Note: at the time of this investigative CR filing. The NPTL libraries are not certified but this symptom was observed.

because the application code has requested to retrieve a registered

output parameter prior to reading the result set.

In other word customer would like the same region ID to have muliply TCP SSIDs.

So we need a way to Ingnore the SSID if is not valid on that LPAR, and bring up the correct REGION with the TCP/IP SSID that is up for that LPAR.

Workaround: None

the name of the driver is invalid as follows:"Sybase Sybase ASE OLE DB

Provider". The string should be: "Sybase ASE OLE DB Provider".

ADO connection string sample: "Provider=Sybase.ASEOLEDBProvider;Use Sybase LDAP=1;Sybase LDAP URL=ldap://aseHost:389/dc=sybase,dc=com;Sybase Server Name=ase1252;Initial Catalog=odbc;"

Properties:

Use Sybase LDAP=1 (this indicates to Provider to use LDAP scheme)

Sybase LDAP URL=ldap://ldapHost:389/dc=sybase,dc=com (Site specific ldap url)

Sybase Server Name=ase1252 (ase server name as defined on LDAP server)

Workaround: Do not use comments in sql you want to execute

being put back in the pool. If a connection is idle for more than the time specified in idle timeout, it should be automatically closed.

When the advanced option "Print Statement" is set to "MS Compatible" in the OLE DB Data Source, each print statement is treated as a separate result set.

But any sproc containing a print statement called through the Sybase ASE OLE DB Provider

would fire the following error at ADODB.RecordSet.Open :

Runtime error '-214767259 (80004005)'

[Native Print code: 0]

[Datadirect ADO Sybase Provider] This is my message from sproc

This has been fixed.

client application declares them in a different order than

when they were declared in the stored procedure residing

on ASE.

Workaround: Use AseDbType instead of creating new enumerations

Workaround: None

Workaround: None

Workaround: None

A connection string property NoErrorIfRSPending has been added to the provider to support this behavior.

This causes the connection to fail.

Tested and reproduced with:

jConnect 5.5 ESD#13 (EBF 11937)

Oracle 9.0.2

Workaround: None

When the advanced option "Print Statement" is to "MS Compatible" in the OLE DB Data Source, each print statement is treated as a separate result set.

But any sproc containing a print statement called through the Sybase ASE OLE DB Provider

would fire the following error at ADODB.RecordSet.Open :

Runtime error '-214767259 (80004005)'

[Native Print code: 0]

[Datadirect ADO Sybase Provider] This is my message from sproc

This has been fixed.

Workaround: None

The code below has reduced the Recevie Timeout from 30 Secs to 1. The issue is now that 1 sec is to short for some companies. We are suppling a ZAP for customers to configure this to what ever time will work for them. We need a way to configure this such as a parameter on the listener....

Workaround: Use SQLFetch() instead of SQLGetData()

Workaround: Use separate variables for the length indicator.

configuration parameter is set too low. Customer wants a way to

timeout if the network/host goes down but not timeout active, long

running queries.

Workaround: Use the appropriate 'C' type

RSP8C shows an example of how to transmit variable text. See Appendix E, "RSP8C variable text sample RSP" for a reproduction of the sample.

> support bigint

> support unsigned datatypes ( unsigned smallint, unsigned int, unsigned bigint)

3> Support Server Side packet Size

Driver does support -1 as a valid setting but defers to ASE to decide the optimal packet size

This CR would limit the number of SQLWarnings chained off a connection object under the assumption that the use does not care about the warnings but does not want to suffer lost memory thru the chained SQLWarnings. Suggest default number of queued SQLWarnngs equal to 5.

(QTS 366986 fixes TCP/IP Resets)

"timeout" period expires. The "timeout" being the smallest of the "tcp_ip_abort_interval"

on the operating system or the RESPONSE_TIMEOUT from the OpenSwitch.cfg file.

"DB-Library error: Err 20004, Sev 2 - Cannot perform more than one read"

call to OpenSwitch.

Currently if the header files have both C++ and C syntax in them, esql/c will not handle the parsing properly. Standard OS header files routinely include both C++ and C typedefs.

>SYBASE 10:05:57 TRANID SYLB TSKNO 69206 EXCEPTION SOCKET NOT FOUND

>SYBASE 10:05:57 TRANID SYLB TSKNO 69206 EXCEPTION SOCKET NOT FOUND

> ...

1900/01/00 00:00:00: 0xb00ca,00000001: [xalog_open_file/165]

it was set unavailable one.

even though it was able to copy all of the rows into the database.

SYBASE 14:40:58 TRANID SYLB TSKNO 00043 TRANSACTION START FAILED WITH RESP=00000045 RESP2=00000008

SYBASE 14:40:58 TRANID SYLB TSKNO 00043 35039 TRAN START ERROR: TRANSACTION SYGH NOT DEFINED IN THE PCT OR IS DISABLED.

cursor pre-fetch buffer size (CS_CURSOR_ROWS), the application would return less rows than

expected and could fail unpredictably.

Added support for BigInt for use with ASE15.0

Workaround: 1. Shortcut key 'CTRL+SHIFT+B' is used to set a breakpoint quickly. This feature may meet the first requirement. 2. Set an individual RulerContextMenuId for SQL Scrapbook, and create a popupMenu "Add Bookmark...". UI changes: a. Added "Bookmarks" view as one of "Database Development" perspective default views. b. Added "Bookmarks" view shortcut.

token stream to ASE causing a server error message. No invalid data is inserted.

Includes a registered procedure "rp_refresh_interfaces" which allows the user

to refresh the interfaces file at will.

(1) For version 15.0

SDK 15.0 ESD #3 (or later) and Sybase DBLib Kerberos Authentication Option 15.

(2) For veresion 12.5.1

SDK 12.5.1 ESD #12 (or later) and Sybase DBLib Kerberos Authentication Option 12.5.

The Customers may not be familiar with CICS Executive Interface Block Function (EIBFN), thus, would not be able to decipher the cryptic error message in the CICS log and diagnose that the root cause, namely: having MFC OSC configured with trace options enabled (see below)without enabling CICS AUXILLLARY Trace config parameters in the CICS System Initiatilisation Table (SIT).

MFC OSC Trace options:

DEBUGSW=Y (in source module "SYOSCUST")

TRACE=ON (in source module "SYLSCFG")

<Hints & Tips on enabling CICS AUX Trace:

In order for Sybase to write out to the CICS Aux Trace Facility these CICS System Initialization(SIT) Parameters must be on

+ INTTR=ON

Code this parameter to specify whether the internal CICS trace destination is to be activated at system initialization.

+ SYSTR=ON

Code this parameter to control the master system trace flag.

+ USERTR=ON

Code this parameter to set the master user trace flag on or off. If this Parameter is set to off, then the EXEC CICS ENTER TRACENUM command will receive an INVREQ condition if EXCEPTION is not specified. If the program does not handle this condition the transaction will abend with a AEIP.>

from ct_cancel().

ASE returns the correct value, but ODBC delivers a huge number.

servers on Linux IBM pSeries.

When set, isql exits whenever a server error is encountered with a severity >= 11. With this option, when a 'real' server error is received, isql will return '2' to the calling program (shell/command prompt) and write 'Msg[tab][server error nbr.]' to stderr.

isql -Uusername -Sservername -P

SERVERNAME:(1)>

SERVERNAME:(2)>

"33607..SYBASE..CATRPC.REQUESTED MODULE NOT LOADED"

if the data file to be copied in does not contain data for the timestamp column.

manual_action: Executing manual.sh (server=sosw, reason=1006)

pool_set_prop_atomic: Failed to preset pool status in companion.

coord_suspend: Cannot change status of pool POOL1 to SUSPENDED

manual_action: Suspending OpenSwitch failed.

do__useraction: Failed to execute the manual script for CMP_FAIL_ACTION. Check the error messages above for reasons of failure.

All future changes to the server/pool configuration are prohibited.

Operating-system error:

Bad file number

35039,' TRAN START ERROR: TRANSACTION %s NOT DEFINED IN THE PCT OR IS DISABLED.'

Needs to change.

Repserver memory leak.

Msg 5702, Level 10, State 1: ASE is terminating this process.

CTLIB Message: - L0/O0/S0/N0/0/0:

blk_init(): blk layer: CT library error: Failed when CT_Lib routine ct_results() called.

$ isql_r -V -SREGTEST15

CT-LIBRARY error:

ct_con_props(SET): security service layer: internal security control layer error: error string not available

CEEXOPT STORAGE=((00,NONE,00,0K),OVR) The third Pamater is the issue "dsa_alloc_value"

MSG13 DC CL50'SYBTP13 - CONNECTION FROM UNKNOWN HOST'

This message has customers confused on what is going on.

Would like the message to be more specfic like " A non Sybase client try to connect"

the load library.

Details:

Temp table wizard considers any object name prefixed with '#' as a temp table. For example, with the following statement referencing a stored procedure 'pbcatcol', temp table wizard still popped up:

create index #abc on pbcatcol (pbcatcol.pbc_case)

Problem Details:

The user failed setting a breakpoint in an ASE stored procedure with long name, the breakpoint would not be adjusted to the nearest valid SQL statement, stack tracke were displayed in ASE's error log file, and the user will not able to debug any ASE stored procedures from that point on until they perform the following steps:

1. Delete all the breakpoints from the Breakpoint view of SQL Debugger.

2. Shut down WorkSpace

3. Shut down and reboot ASE Server.

4. Restart WorkSpace

5. Do not set breakpoint in stored procedures or trigger with name longer than ~22 bytes.

The problem is caused by a debugging related ASE server problem.

Solutions:

1. Database Development Tooling adds a safeguard mechanism that prevents the user from setting breakpoint for ASE long-named procedural object (SPs and triggers). In additon, there's a new debugger preference for the user to turn off the safeguard so that when the user installed ASE debugger patches in the future, we don't need to take out the safeguard mechanism, and the user only need to disable the safeguard from the preference page.

2. The user is advised to install ASE patch 12.5.3 ESD #7 to fix the root cause.

Programmer's Supplement Open Client and Open Server 12.5.1 for Microsoft Windows explains that Sybase has certified Microsoft's Visual C++ Version 5.0.

But it should be Visual C++ Version 6.0.

To see the correct information, please read Release Bulletin.

in the file. OpenSSL gets an error with these certificates. For example, the command "openssl pkcs8 < server1.crt" will return the following error message:"Error reading key

24292:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:642:Expecting:

ENCRYPTED PRIVATE KEY". This error is not seen with certicom.

When using an ASE that uses OpenSSL, you may get the following error message:

"Sybase CSI Error Message: Error reading the private key. The specified buffer content

is not in the expected format."

If this error is encountered, the corrective action would be to regenerate

certificate/private key using the new tools.

By doing a regsvr32 sybdrvoledb.dll and put the directory in the path.

This seems not to be possible with our Organic drivers.

Resolution: This performance issue has been fixed.

Resolution: This performance issue has been fixed.

Resolution: This performance issue has been fixed.

Change of login,password,database should be allowed.

The content assist in SQL Editor gives the user the incorrect syntax when typing in "create index index_name on table_name (". The content assist gives table_name.column_name, which doesn't fit the ASE index. If user select one column from content assist and try to save, error will occur.

Resolution: This issue has been fixed.

Resolution: This issue has been fixed.

Resolution: This issue has been fixed.

Resolution: This performance issue has been fixed.

Resolution: This issue has been fixed.

Resolution: This issue has been fixed.

Resolution/Workaround: Change the default value of univarchar to ' ' (space).

Remaining issues:

If the user clicks on 'Null' checkbox in the Configure Parameters dialog, the stored procedure will be running forever.

Workaround:

User should avoid clicking check box 'Null' for univarchar in the Configure Parameters dialog, otherwise the stored procedure will be running forever; but the user can still click on the Terminate button to terminate the running stored procedure in SQL Results view.

message about the link to an Attachment Site Parms

not available.

[Sybase][ODBC Driver][Adaptive Server Enterprise]

Can't specify a length or scale on type 'longsysname'

Also, the DDL gen wizard should not use the Debug API to retrieve procedural object definitions for ASA/IQ.

Resolution: This issue has been fixed.

followings in the CICS log:

> EZY1261I 22/11/06 08:21:08 EZACIC03 ATTACH SUCCESSFUL, TCB ADDRESS=00895988 TERM=

TRAN=AMD2 TASK=0001965

> EZY1278I 22/11/06 08:21:08 EZACIC03 DETACH SUCCESSFUL TCB ADDRESS=00895988 TRAN=AMD2

TASK=0001965

when doing update with a varchar parameter without specifying "Size" property,

and the actual parameter value is a string including simplified chinese chars and

the size of actual string parameter is more than 255 bytes,

exception "Data Overflow ......" would happened.

WorkSpace crashes when executing a stored procedure with a huge number (5000) of result sets.

Solutions:

1. Added Eclipse preference under 'Sybase, Inc.-->Database Development-->SQL Results view' to limit the number of result sets can be displayed in the SQL Results view in Multiple window display mode and Single window/Grid display mode. When the limit is reached, a proper warning message will be displayed as a tab in the SQL Results view.

2. If the user wants to examine a large number of SQL result sets after a stored procedure execution, the user can use the SQL Results view context menu "Save All Results' to save the result sets into a text file.

3. All procedural object execution are now put in a separate job, and a progress monitor will be displayed to allow the user to cancel or put in the background.

When using 'Save' or 'Save As' context menu in Database Explorer perspective to save the exported table syntax to a SQL file, the charset was not set automatically to UTF-16, which is the default charset used when exporting table syntax, hence the user need to manually set the SQL file 'charset' property to UTF-16 to be able to read the SQL file.

Solutions:

Database Explorer perspective will set the SQL File charset to UTF-16 automatically when saving the exported table syntax.

Database Explorer uses incorrect terminator for ASE when exporting table syntax.

Solution:

In Workspace 1.7, Database Explorer uses "go" as the statement terminator for ASE when exporting table syntax or logging activity.

When using MSDTC with Sybase ADO.NET Pooling feature to connect to ASE, Pooling is not working. In ASE, we will see all physical connections instead, which may lead ASE to exceed maximum number of connections.

with bittype on commit statement.

When the user creates a single trigger with all 3 activation types, i.e., insert, delete and update, and creates another trigger with either insert or update,

and then user modifies and saves the aforementioned 'all' trigger, where the SQL Editor drops the 'all trigger' and recreates it, as in ASE, there is no ALTER TRIGGER command. Thus, in this process ASE server deletes the insert or update trigger as user is re-creating the all action trigger.

In this situation, when we have breakpoint in a trigger in the now deleted 'insert' (or 'update') trigger, ASE servers will get a stack trace during trigger debugging, as there is a breakpoint but the object does not exist any more.

Please refer to the 'Trigger Restrictions' below.

(http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.docset.ase_15.0/title.htm)

-----------------------------------------------

Trigger Restrictions

Adaptive Server imposes the following limitations on triggers:

A table can have a maximum of three triggers: one update trigger, one insert trigger, and one delete trigger.

Each trigger can apply to only one table. However, a single trigger can apply to all three user actions: update, insert, and delete.

Workaround:

The user will need to remove all the breakpoints for the trigger that got deleted, in this case, remove all the breakpoints for the trigger_INS or any trigger that does not exist any more (deleted by the ASE server), only then user can start using the debugger as before.

During trigger debugging using SQL Debugger in the Database Development Tooling, if the tigger contains SQL statements that reference views that are derived from the trigger table, the end user will not be able to see the contents of the view in the Referenced Tables View during debugging, but the debugging session is not affected.

In an ASE 15 database, create a new user. Do not have this user as the DBO.

Create a new stored procedure, and give ownership to the new user.

In the Enterprise Explorer, create a connection to that database using the sa or DBO information

Browse to the database --> new user schema --> expand the Procedures

You should now see the error

Disconnect the DB session, and modify the properties such that you are logging in as the new user

In the Enterprise Explorer, log in to the database again (as the new user)

Browse to the database --> new user schema --> expand the Procedures

You are now able to see the stored procedure.

You may also now expand the DBO procudures, and see the list available there as well.

Problem Description:

Some users have experienced that for some ASE procedural objects-- stored procedures and triggers in database other than 'master', the debugger breakpoint cannot be set at the correct location.

Problem Resolution:

The workaround is to restart ASE database server

For some ASE procedural objects-- stored procedures and triggers in database other than 'master', the debugger breakpoint cannot be set at the correct location. Usually, those procedural objects contain SQL statements eRxpanded by the ASE server after the definition is modifed and saved. For example, after the following statement in a stored procedrue got saved and expanded by the server, the user will not be able to set the breakpoint on that statement:

"select * from authors", will be expanded to

"--Adaptive Server has expanded all '*' elements in the following statement

select authors.au_id, authors.au_lname, authors.au_fname, authors.phone, authors.address, authors.city, authors.state, authors.country, authors.postalcode from authors",

and when the user tries to set breakpoint at the 'select authors...' statement, the breakpoint will be off.

This problem is caused by an ASE bug, CR463870.

Problem Description:

In WorkSpace2.0, if you use Visual SQL, the Query editor, or the DataWindow editor with a particular connection profile and database, then make a change to the tables/columns of that database (eg, add/delete a table or column), you will not see those changes the next time you use Visual SQL, the Query editor, or the DataWindow editor;

Problem Resolution:

Disconnect and connect to the database server again.

Version: Sybase DB-Library/12.5.1/P-EBF14280 ESD #17/PCIntel/BUILD1251-048/OPT/Tue Jan 23 01:47:19 2007 (we kept this same version in client side when testing all servers below)

When running C application that calls xp_server, the following error message appears:

Returns error:

Msg 8015, Level 0, State 1

Server 'ase1254', Procedure 'xp_cmdshell', Line 2

Adaptive Server has truncated parameter number 1 passed to rpc '08sybsyespxp_cmdshell' on server 'ASE1254_XP'. The remote server does not support character or binary data wider than 255 bytes.

Issue happens with dblib applications only. Ctlib applications work fine.

Microsoft Data Link utility fails with "Catastrophic failure" when creating MS Data Link 64bit entry with OLEDB provider. Works fine in 32-bit environment only.

Sideinfo: When using AsaDataReader from IAnywhere Ado.Net driver it works fine.

contents of variables and dump the first x number

of rows in the referenced tables at each

breakpoint.

Resolution: Added a context menu to allow

the user to invoke the Dump Variable & Table Data

wizard during a SQL debug session to save the

variable values and selected table rows to a log

file specified by the user.

unrecognized"

a.) ITransactionJoin Interface as being implemented in

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc00075_1500/html/oledb/Supported_interfaces_oledb.htm

b.) The MS DTC registry entries for the OLEDB and ODBC dlls had to be entered manually.

(http://support.microsoft.com/kb/817066/en-us) amd tp configure the MS DTC

(http://support.microsoft.com/?scid=kb%3Ben-us%3B839279&x=14&y=9).

when the Sybase Environment Variables are incorrectly set.

In ASE 15, proxy table mapped to external directory/file sometimes can't be opened.

Problem 1 Resolution:

Restart ASE 15 server.

Problem 2 Decription:

Proxy table can't be updated/inserted/deleted when proxy table have datetime datatype column,and the proxy table mapped to the remoted table in Chinese language ASE server.

Problem 2 Resolution:

This is ASE server issue, it will be fixed in the later version.

Resolution: Added Placements and Fragmentation read-only pages in the IQ Index Editor.

isql -Uusername -Sservername -P

SERVERNAME:(1)>

SERVERNAME:(2)>

- Organic ODBC Driver 15.0.0.162 (03.51) 64-bit

- SQL Server 2005 64 bit

- Windows 2003 Server 64-bit

- Adaptive Server Enterprise/12.5.1/EBF 11662 ESD#2 on HP-UX 64-bit box

- Visual Studio 2005

When running an SQL Server Integration Services (SSIS) package from within SQL Server 2005 64 bit by using Organic ODBC Driver 15.0 64-bits, the following conversion errors occur when international characters are present in rows data (�, �, � etc.):

For string values:

Data conversion failed while converting column "di_descripcion" (1817) to column "di_descripcion" (239). The conversion returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page."

For integer values:

4495 OnError carga CC_CTACTE 2007-07-23 14:48:03.000 SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "component "DataReader Source" (1)" failed because error code 0x80004002 occurred, and the error row disposition on "output column "cc_protestos" (145)" specifies failure on error. An error occurre

When there are no international characters involved in rows data, the SSIS package works fine.

In 32-bit environment Windows 2003 (using SQL Server 2005 32-bits, Organic ODBC Driver 15.0 32-bit), the same SSIS package always runs fine, including when there are international characters involved in rows data.

Resolution: For ASA and IQ, there are two ways to retrieve the definition of procedural objects, one is via the debug API, the other is using system tables, but the source retrieved are different. Originally, the procedural object editor was using the ASA/IQ debug API to retrieve the source. Now it is fixed by adding a read-only Debug page in the ASA/IQ procedural object editor which still uses the debug API, but the original Source page is now using the system tables to retrieve the correct definition.

- SDK 15.0 ESD#9 for Linux

- ASE 15.0.2 EBF 14328 for Sun Solaris

When selecting data via Linux SDK 15.0 isql, the columns display with double of the original size defined in datatype.

Resolution: Added a context menu in the SQL Results view on the root node of a group of results so that the user can save all sql statements at the same time.

Resolution: Enhanced the usability of the Connection Info. Field in the SQL Scrapbook/File Editor.

Resolution: Added search context menu to allow the user to search a text string in the SQL Results view in text mode.

Resolution: Added context menu Show Schema and Show Owner in Enterprise Explorer to give the user the choice to turn on/off the schema folder grouping and see the owner name along with the object name.

When he tried to use SDK 15 ODBC (sybdrvodb.dll), he received error messages

> SYBASE 08:22:41 TRANID SYLB TSKNO 00027This transaction is already active (in CSML)

> You cannot cancel a transaction that is not active (in SYCM screen)

Resolution: Fixed, with the exception of for some ASE system stored procedures that require database name (qualified name).

Resolution:

Fixed

Makes it easier to get the version number of the server.

Resolution: Now the user can manually type in create index and insert statements in the ASE Temp table creation wizard and proper SQL annotation will be generated. With the annotation in place, indexes will be created and rows will be inserted at stored procedure execution/debug time.

implicitly. At this point it's unknown if this requires some new status from ASE/DTM to client, or if this is even within the XA specification. This request comes up because of the ASE behavior to implicitly end an XA transaction when a trigger command fails, such as in duplicate insert, foreign key constraint error, explicit rollback commadn, etc.

Please, add the following important recompilation information into EBF readme files for customer's orientation on how to proceed with his ctlib applications after applying latest EBFs:

- If the CTlib application is using the OCS shared libraries then there is no need to recompile or relink. Just overlay the ESD and the application should work.

- If the application is statically linked with the OCS static libaries then it needs to be relinked with the ESD OCS libs to use the ESD fixes.

- If the application is modified to use the new features introduced in the ESDs, then it needs to be recompiled and relinked

Resolution: Make Go a keyword so that it will be treated as a statement terminator. But notice that the go cannot be used as an alias.

2. Event Handler cheatsheet: Using this cheatsheet the user creates an event, completes the edit, and adds the query. If the user then attempts to add another query by using 'Click to redo,' the contents in the editor removes the header and the contents become as follows:

begin

print 'Replace this print line with your SQL statements'

end

instead of:

CREATE EVENT test34

ENABLE

AT ALL

HANDLER

begin

print 'Replace this print line with your SQL statements';

insert into T1 (c1)

values(9)

end

In addition, items edited before were not saved and are gone. It appear that the reason this problem occurs is that the editor is being reloaded every time 'Click to edit' or 'Click to redo' is selected in the cheatsheat.

For "eventhandlers", when the editor is loaded the code must be retrieved from the point of the header, which is before the begin statement.

The error is raised when trying to call a stored procedure with a binary parameter through ADO.NET

Resolution: Added annotation in the generated DDL script to warn the user to set the quoted identifier preference correctly.

2. Not recognise no result set as a valid syntax.

it will be truncated at the first space.

OpenSwitch may crash in thrd_lock() or mtx_lock() functions.

When customer uses ct_init and ct_exit and executes application as asynchronous mode, a memory leak happens.

We need to remove ct_init and ct_exit to get the memory stablized.

2. Do some modification to the SQL file.

3. Save and close the SQL file.

4. Reopen the SQL file.

sql editor, the name of the connection profile is lost.

keyword "AS", all parameters were reported as being SQL_PARAM_INPUT

when calling SQLProcedureColumns, even when some were defined as

output or input_output.

Using a SqlDataSource bound to a GridView with parameters in the data source gives AseException "COUNT field incorrect"

permission page, switches to another page, saves, takes no further action, and

closes the editor, no warning dialog appears for saving the dirty editor. If the

user switches to another editor and switches back, the revert action is disabled

for the dirty editor.

Database Development perspective opens and should show the cheat sheet view with

'Getting Started w/ Database Development.'

ODBC driver. ODBC Driver fails when SQLMoreResults is called after SQLPrepare.

times leaves connection open in CLOSEWAIT state and memory

allocated. Occasionally ISQL may hang.

to a permission error on HKLM\SOFTWARE\Sybase\OLEDB Provider

Full control is needed but a regular user by default only has Read access.

Secondly the application sybdrvadm.exe doesn't properly maintain system and user datasources.

Resolution: This has been fixed.

(1) Use TDS 4.6 or earlier versions;

(2) Connect to an Open Server application;

(3) Use different character sets between the client and the Open Server.

"Translate to a file" and "Display translation in a window" in

Menue File -> Preferences.

had tab characters in the parameter declaration.

"AS" two or more times, all parameters were reported as being

SQL_PARAM_INPUT when calling SQLProcedureColumns, even though some

were defined as output or input_output.

the comments contained the keyword "AS" two or more times, all

parameters were reported as being SQL_PARAM_INPUT when calling

SQLProcedureColumns, even though some were defined as output

or input_output.

http://sybooks.sybase.com/nav/detail.do?docset=1065

It can be found at

http://manuals.sybase.com/onlinebooks/group-cnarc/cng1110e/ocerrors/

link should be moved to Open Client/Server 11.1.1 (Archive)as well

the CM is disconnected from the network and COORD_MODE=avail.

Resolution: This has been fixed.

Resolution: This has been fixed.

Resolution: This has been fixed.

From a Micosoft SQL Server 2005 Linked Server connection a query on a table having

a nullable CHAR column gives error:

Msg 7356, Level 16, State 1, Line 1

The OLE DB provider "MSDASQL" for linked server "LINKED_SERVER" supplied inconsistent metadata for a

column.

The column "COLUMN" (compile-time ordinal 3) of object "DATABASE.dbo.TABLE" was reported to have

a "DBCOLUMNFLAGS_ISFIXEDLENGTH" of 16 at compile time and 0 at run time.

Similar query with the OLEDB Provider succeeds.

When replicating a table parameterized with a table having a combination of datatypes an error occurs:

[ASEOLEDB]Data overflow. Increase specified column size or buffer size (Source: MSSQLServer, Error number: 30128)

failing with 12.5.1 The DBlib application no longer can connect.

If the customer rolls back to the base version of 12.5.1 it works fine.

All versions of 15.0 and ESD are working fine the defect is only in the 12.5.1 ESD#;s

Error message is unbale to connect to servername and the applicaiton will stop

ERROR: 1028 Unable to open connection to server: MIC_DET_SQL06.

ERROR: 1024 DB-Library error: 20003 SQL Server connection timed out.

with Open Client CTlib 12.5.1 and ESD#22

If you involke a time out value on a conenction object the time out will be never happen

the command object will continue to pool for the server after five min of so you will

get a connection time out even thou the connection should of timed out in 15 sec for example.

/*

**

** Description

** -----------

** This is the example program that is printed in Chapter 1 of the

** Client-Library Programmer's Guide. It connects to a server,

** sends a select query, prints the rows, disconnects, and exits.

**

** Inputs

** ------

** None.

**

** Server Tables

** -------------

** This program requires the pubs2 database.

*/

/*

** Language Query Example Program.

*/

#include <stdio.h>

#include <stdlib.h>

#include <string.h>

#include <ctpublic.h>

#include "example.h"

#define MAXCOLUMNS 2

#define MAXSTRING 40

#define ERR_CH stderr

#define OUT_CH stdout

/*

** Username and password are defined in example.h

*/

CS_CHAR *Ex_username = EX_USERNAME;

CS_CHAR *Ex_password = EX_PASSWORD;

/*

** Define a macro that exits if a function return code indicates

** failure.

*/

#define EXIT_ON_FAIL(context, ret, str) \

if (ret != CS_SUCCEED) \

{ \

fprintf(ERR_CH, "Fatal error: %s\n", str); \

if (context != (CS_CONTEXT *) NULL) \

{ \

(CS_VOID) ct_exit(context, CS_FORCE_EXIT); \

(CS_VOID) cs_ctx_drop(context); \

} \

exit(EX_EXIT_FAIL); \

}

/*

** Callback routines for library errors and server messages.

*/

CS_RETCODE CS_PUBLIC csmsg_callback PROTOTYPE((

CS_CONTEXT *context,

CS_CLIENTMSG *clientmsg ));

CS_RETCODE CS_PUBLIC clientmsg_callback PROTOTYPE((

CS_CONTEXT *context,

CS_CONNECTION *connection,

CS_CLIENTMSG *clientmsg ));

CS_RETCODE CS_PUBLIC servermsg_callback PROTOTYPE((

CS_CONTEXT *context,

CS_CONNECTION *connection,

CS_SERVERMSG *servermsg ));

/*

** Main entry point for the program.

*/

int

main(int argc, char *argv[])

{

CS_CONTEXT *context; /* Context structure */

CS_CONNECTION *connection; /* Connection structure. */

CS_COMMAND *cmd;/* Command structure. */

/* Data format structures for column descriptions: */

CS_DATAFMT columns[MAXCOLUMNS];

CS_INT datalength[MAXCOLUMNS];

CS_SMALLINT indicator[MAXCOLUMNS];

CS_INT count;

CS_RETCODE ret;

CS_RETCODE results_ret;

CS_INT result_type;

CS_CHAR name[MAXSTRING];

CS_CHAR city[MAXSTRING];

CS_INT timeval =15; //<---- set the time out value

EX_SCREEN_INIT();

/*

** Step 1: Initialize the application.

*/

/*

** First allocate a context structure.

*/

context = (CS_CONTEXT *)NULL;

ret = cs_ctx_alloc(EX_CTLIB_VERSION, &context);

EXIT_ON_FAIL(context, ret, "cs_ctx_alloc failed");

/*

** Initialize Client-Library.

*/

ret = ct_init(context, EX_CTLIB_VERSION);

EXIT_ON_FAIL(context, ret, "ct_init failed");

ret = ct_config(context, CS_SET, CS_TIMEOUT, &tmOut, CS_UNUSED, NULL);//< involking it here,.

EXIT_ON_FAIL(context, ret, "error setting timeout");

/*

** Step 2: Set up the error handling. Install callback handlers

** for: - CS-Library errors - Client-Library errors - Server

** messages.

*/

/*

** Install a callback function to handle CS-Library errors.

*/

ret = cs_config(context, CS_SET, CS_MESSAGE_CB,

(CS_VOID *)csmsg_callback,

CS_UNUSED, NULL);

EXIT_ON_FAIL(context, ret,

"cs_config(CS_MESSAGE_CB) failed");

/*

** Install a callback function to handle Client-Library errors.

**

** The client message callback receives error or informational

** messages discovered by Client-Library.

*/

ret = ct_callback(context, NULL, CS_SET, CS_CLIENTMSG_CB,

(CS_VOID *)clientmsg_callback);

EXIT_ON_FAIL(context, ret,

"ct_callback for client messages failed");

/*

** The server message callback receives server messages sent by

** the server. These are error or inforamational messages.

*/

ret = ct_callback(context, NULL, CS_SET, CS_SERVERMSG_CB,

(CS_VOID *)servermsg_callback);

EXIT_ON_FAIL(context, ret,

"ct_callback for server messages failed");

/*

** Step 3: Connect to the server. We must: - Allocate a connection

** structure. - Set user name and password. - Create the

** connection.

*/

/*

** First, allocate a connection structure.

*/

ret = ct_con_alloc(context, &connection);

EXIT_ON_FAIL(context, ret, "ct_con_alloc() failed");

/*

** These two calls set the user credentials (username and

** password) for opening the connection.

*/

ret = ct_con_props(connection, CS_SET, CS_USERNAME,

Ex_username, CS_NULLTERM, NULL);

EXIT_ON_FAIL(context, ret, "Could not set user name");

ret = ct_con_props(connection, CS_SET, CS_PASSWORD,

Ex_password, CS_NULLTERM, NULL);

EXIT_ON_FAIL(context, ret, "Could not set password");

/*

** Create the connection.

*/

if(EX_SERVER==NULL)

ret = ct_connect(connection, (CS_CHAR *)NULL, 0);

else

ret = ct_connect(connection, (CS_CHAR *)EX_SERVER, strlen(EX_SERVER));

EXIT_ON_FAIL(context, ret, "Could not connect!");

/*

** Step 4: Send a command to the server, as follows: - Allocate a

** CS_COMMAND structure - Build the command to be sent with