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 Sybinit - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 83640 Most sybinit tests are blocked becuase the current directory name is truncated. Hence, master device & krg files cannot be found. The errorlog always shows a "No such file or directory" message whenever an attempt is made to access a file in current dir. 83641 In sybinit/siupgd[1-5], error in up001b.out:SERVER ERROR: Error in upgrade check: version is 'flag, th', expected '11.0 '.The version string is different on other platforms but the error is same. 84899 There are syntax in sjis versions of locales files, due to use of '&' as the escape character. 86448 If sybinit is invoked with "-l japanese -c eucjis" option and typed "?" to display help message at "sybsystemprocs configuration" and "audit configuration" screen, core dumped. 86788 german/iso_1 sybinit.loc file in generic cougar codeline is broken. A ':' has replaced a ';' comment character on the SCCS id line, causing sybinit -l german to abort language load with "INTERNAL ERROR: Format error in localization file". 87473 If 'rs_init' finds a 'sql.ini' entry which references a driver not found in 'libtcl.cfg', 'rs_init' should ask if the user wants to add the driver to 'libtcl.cfg'. If the user does not want to add it, 'rs_init' should read the rest of the 'sql.ini' file. 78012 1 During upgrade to 11.x, sybinit does not copy the backupserver's runserver file from 10.x release directory to the 11.x directory. 79706 1 error and info msgs are formatted by inserting line-breaks where spaces occur in the locales-file version of the msg. This doesn't work well in Japanese because spaces rarely occur in Japanese. 79714 1 Some sybinit error messages are composed of multiple pieces of text from the locales file. This doesn't work well when the messages are translated to foreign languages. 81350 1 Not able to rerun 'remapping database' from sybinit menu option after remap failed during upgrade from 4.9.2 to 11.0. 81899 1 When the interfaces file for an old release being upgraded has a single entry and its IP address is invalid, and this entry is selected during the upgrade (as it must be), upgrade fails. 81910 1 Upgrade an old server, providing an interfaces file in the new release directory which has an entry with an invalid IP address before the entry for the old server. For every service for every such invalid entry, an interactive user will have to dismiss 3 Sybase Confidential Page: 1 System Problem Report SYBASE 11.0.1 Sybinit - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 83111 1 setting errorlog name to existing directory name will not raise any error message from sybinit. server configuration will fail but there's no message explaining what was the reason of the failure. 71803 2 In formatting help screens, sybinit breaks lines where spaces occur. But Japanese does not use spaces. Japanese help-screen messages have long sequences of characters with no spaces. And sybinit does not check for a "word" that's longer than a line. 74605 2 "BACKUP SERVER CONFIGURATION" screen shows "5. Backup Server tape configuration file: /oldreldirs/testinstall/backup_tape. fg". Note the missing "c" in "backup_tape". Looks like a formatting problem. Also, after the server was installed, I could not 74716 2 Sybinit: When raw device is specified for sybsecurity, sybinit determines device size automatically, but refuses to accept floating -point size value (instead of integer). 74982 2 When upgrading from 100x to 11.0, the SQL SERVER UPGRADE SCREEN should not display menu #3(sybsystemprocs db configuration), since the sybsystemprocs is already created in 100x and the server knows the configuration 74984 2 After logging into sybinit, when we select "configure a server product", the time stamp for "Date Installed" for the SQL Server doesnt seem to reflect the dataserver binary date or the sql server product installation date. 75496 2 "Existing sybsystemprocs database is too small ('15' mega): the minimum size permitted is '0.00' megabytes." on sybinit upgrade test from 10.00 or 10.01 to 11.0, on siupgd1, 2, 3, 4, 5 75954 2 The sybinit menu for configuring a SQL server can incorrectly handle a selection that is out of range. 75958 2 Sybinit reinstalls system stored procedures when installing a new character set even though the default character set/sort order is not being changed. 76005 2 c2 security NOT correctly installed while canon says "c2 security correctly installed 78361 2 During upgrade from 4.92 to 11.0 - the upgrade appears to use SYB_BACKUP as the backup server name during the 4.92 to 10.0 phase. 80114 2 Invoke sybinit to perform upgrade from 49x/10.0x-> 11.0: set sybinit.release_directory to {OLD_RELDIR}, select existing {SERVERNAME}, accept default user=sa, then Ctrl-a gets "CONNECTIVITY ERROR: DB-Library error: 'Interface file: unexpected end-of-line.' Sybase Confidential Page: 2 System Problem Report SYBASE 11.0.1 Sybinit - Mar 10 1996 Sun Solaris SVR4 2.4 SPR No. Pri Description ------- --- ------------------------------------------------------------------- 81564 2 When entering a port number for the interfaces file, the following s equence of values is correctly rejected as out-of-range: 1, 1024, 65536, 65535. Thereafter, all values (even valid ones) are rejected as out of range. 71729 3 rs_init only supports the 8 character sets that it knows about. 75007 3 When we are upgrading to 11.0 using sybinit and for some reason the sybinit gives an INTERNAL ERROR, the sybinit log file says "check the log @ .." and refers to itself. this is kind of misleading for the customer. i can understand the reference 75087 3 After upgrade has succeeded to 11.0, the sybinit is returning back to the SQL SERVER UPGRADE SCREEN. if we select upgrade again, sybinit is doing something eventhough the server is upgraded. i think, at this point, the sybinit doesnt check the version 84559 3 Menus allow attempts to install chinese and japanese at the same time. Chinese should exclude all other languages. Japanese should exclude all other languages. 85481 3 547, 548 message number not able to find in $SYBASE/locales/us_english/iso_1/sybinit/sqlsrv.loc file. 86452 3 sybinit Japanese help message displaed unreabale character. Japnese GPG staff correct some localization file already. But, It was not bind to production media.