March 9, 1996 Sybase Customers, The following represents problem reports still open and unresolved against System 11. This report is provided to aid you in identifying known problems, should you encounter any during the operation of this product. The problems reported are ordered by importance (high to low), and then by problem identification. Our development process specifies that System 10 bug fixes be included in System 11 products. There are certain circumstances where this is not possible, specifically when: a) Problem fixes made in System 10 missed the cut-off date for inclusion. That would be problems resolved past the System 10.0.2.4 Rollup date of November 11, 1995; specifically those resolved after January 19, 1996, b) System 11 code implementations made specific problem fixes made in System 10 unnecessary, c) Problem fixes made in System 10 were believed necessary, but presented high risk of destabilization to System 11. Therefore, they weren't included in System 11. At present, there is only one problem that is associated with item c); 61628. Current plans call for these problems to be included in a subsequent System 11 maintenance release. Sybase System 11 Release Team System Problem Report SYBASE 11.0.1 Backup Server - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 79671 IO_EMULDEAD_B multibuffering process died is a poor error message. It is used when pipe I/O fails or if srv_select fails on the pipe file descripter. Make message more meaningful. 81785 get a segmentation fault and core dump when tryingn to dump to a network dump 84955 While the tape auto config does its tests, it blocks other connections into the backup server, and slows concurrent backup sessions. isql into backupserver times out. SYB_BACKUP...sp_who returns only after the config. tests are done. 85664 shutdown SYB_BACKUP with nowait get new error 7212, "Can't close connection on site 'SYB_BACKUP' because it is not active." 87028 When the -D4 trace flag is enabled to trace tape auto config feature, the strategy # displayed is one less than the actual strategy stored in the tape config file. This might cause confusion for tech support engineers/customers who enable this trace flag. 87134 backup API: load database with headeronly on an API device prints 6.32.2.2 (volume not valid)and 1.14.2.3 noise messages on the backup server error log. However, the load with headeronly is succesful from the client side. 87155 backup API: if the DLL is not found, the error message 4.124.2.1 is issued. The message should read 'can't open file: ', rather than ': can't open file'. 87156 backup API: Informational message for the API (4.125.1.1) is not cle ar enough. User tends to mistake them for an error message. Change the message to make it user friendly. 87159 backup API: when a dump is made to an API device which causes syb_open to hang, e.g., waiting for another process to read from a named pipe, then the SQL server message 'Backup server session id is:...' is not printed until syb_open returns. 68259 1 If an error is encountered while closing the archive device for a LOAD operation, then Backupserver reports the close error, but then reports that the LOAD completed successfully. 68564 1 French message not found by backupserver. Prints it in English. See 52833 for a similar problem with the German message. Backup Server: 4.41.1.1: Creating new disk file' is in English instead of French. 69158 1 French message not found by backupserver, English being substituted for "4.41.1.1: Creating new disk file". Translation does exist in locales/{french}/iso_1/bslib.loc Sybase Confidential Page: 1 System Problem Report SYBASE 11.0.1 Backup Server - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 73685 1 See bugid 42381 for description. This bug also occurred in version 10.x. 82063 1 backup server dies attempting to allocate memory on a remote load of a large db. Looks to be running outof swap. Memory allocation for '8' bytes failed in 'srv_poll' for 'NET_POLL array' allocation 83674 1 When customer tries to dump using Backup API on a remote System 11 backupserver, from a system 10 SQL server & backup server the system 11 backup server crashes dumping core. Normal dump/load to tape/disk work fine. 63445 2 If the internal version of a message is more recent than the version retured by the current locale Backup Server should generate a message based on the internal text. Instead the internal format is used with the _old_ message body => strange results. 69996 2 "Backup Server: 5.7.2.11: RPC ('as_pagerun') execution failed. seen while shutdown with nowait during dump. Xref: bugid 45938, 59708, 57549 70872 2 The error messages reported from sybmultbuf need to be improved. 72649 2 It doesn't appear that the bytes written for label IO to tapes is counted and recorded on the tape by backup server. This isn't much of an issue for database dumps, however for transaction dumps could lead to hitting EOT before capacity is reached. 73986 2 A volume handling test doing remote Dump and Load to/from SCSI tape. DUMP/LOAD is terminated by executing sp_volchanged() with an action of 'ABORT' cause message "Backup Server: 5.7.2.11: RPC ('as_pagerun') execution failed." 79533 2 dump to tape one local one remote. make sure both are prompting for volume change. using sp_volchange abort local stripe. the dump is still hung until you abort the remote stripe. 81374 2 issuing SYB_BACKUP...shutdown gives the following stack in errorlog.ucbacktrace->terminate_process->kisignal-> -fini->initquery ->yyparse->sqlpars->+dsrecv_language->conn_hdlr->-coldstart. Backupserver did not shutdwon. 87445 2 after sp_volchanged message an extra message: Backup Server:5.16.2.2: DB-Library error, error number 20018, severit 5: General SQL Server error: Check messages from the SQL Server is coming 61192 3 Assume client1 connected to server1 initiates a dump with the BS. Also assume server1 has locale A. When the dump requires a volchg BS issues request to client1 through server1. The response must be made through client2. Assume client2 is connected to==> Sybase Confidential Page: 2 System Problem Report SYBASE 11.0.1 Backup Server - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 68763 3 The check for a valid volume name label is performed after the check for a valid file name match. The order of these checks are reversed.