SAP DB Release Information (7.3.00.41 to 7.3.00.48) Kernel: ======= PTS: 1128313 since: 7.3.00.48 Fixed Problem: appearance: Crash in catalog cache Preconditions and circumstances: Kernel-version 7.3.00.47 + select on a complex view, which was defined with sqlmode <> oracle, for the select oracle-mode and select-fetch-optmization are used. Workaround: None for R/3, otherwise the select-fetch-optimization should be avoided Solution: The handling of the systemview-record has to be changed. PTS: 1127011 since: 7.3.00.47 Fixed Problem: appearance: A recovery of a complete or incremental backup returns the error, that the backup-device is already attached. Also the label cannot be read. Preconditions and circumstances: Complete or Incremental recovery fails during a precheck, which determins the correctness of the used backup. Afterwards the device is not alway detached. Workaround: restart the database Solution: code correction PTS: 1126918 since: 7.3.00.47 Fixed Problem: appearance: Functions like decode and some other comparsions accept the datatype-compatibility of boolean and string_literals/user/usergroup or the like. Preconditions and circumstances: none Workaround: none Solution: The check of compatibility has to be extended for string_literals/user/usergoup and the like. PTS: 1126791 since: 7.3.00.47 Fixed Problem: appearance: Alter table ... drop primary key may result in a corrupt catalog. Preconditions and circumstances: The key of the table contains a column having a length > 254 bytes. Workaround: Don't drop the key via alter table statement. Copy the table instead. PTS: 1126676 since: 7.3.00.47 Fixed Problem: appearance: Error -3008 at select on complex view with date or time function in sqlmode oracle Preconditions and circumstances: Kernel version 7.3.0.29 Workaround: no PTS: 1126644 since: 7.3.00.47 Fixed Problem: appearance: A LogBackup is recovered with recover_replace and returns an incorrect returncode -3004 (invalid log backup) Preconditions and circumstances: A multi-cpu hardware is used and the servertasks are configured in a way, that allows servertasks to be run in different UKTs. By this the tape-read-task and the devspace-write-tasks (aka Log_Reader) are running complete asynchronous. Workaround: Reconfigure the taskcluster that way, that all servertasks are running in one UKT Solution: code correction PTS: 1126606 since: 7.3.00.47 Fixed Problem: appearance: The kernel crashed. Preconditions and circumstances: A complex view select has been used in a db-procedure definition, where a table in a subselect is unknown. Workaround: Correct the statement in the db-procedure. Solution: Missing check of the returncode har been introduced. PTS: 1126520 since: 7.3.00.47 Fixed Problem: appearance: The datatype-check in ODBC on VARCHAR UNICODE-columns does not return the info VARCHAR, only UNICODE Preconditions and circumstances: no special ones Workaround: none Solution: the kernel has to check for internal VARCHAR-flag and return the datatype accordingly PTS: 1126199 since: 7.3.00.47 New Feature: Feature description: The command "check table catalog" now also checks the correctness of the stackentries for columns with a definition length >= 255 because in earlier releases there were some bugs. PTS: 1126133 since: 7.3.00.47 Fixed Problem: appearance: - error -8006 during insert - error -3019 during select Preconditions and circumstances: - (-3006) LONG BYTE defined with DEFAULT, the default had to be used in this insert, parse/execute used separately - (-3019) command used a one-value-subquery whose number-value filled the calculated number length (the decimals minus the fractional part), as the constant 1 does (fixed (1,0) Workaround: - use the DEFAULT-value explicitely - use a function or some superfluous arithmetic around the subquery-value to increase the calculated number of digits. PTS: 1126039 since: 7.3.00.47 Fixed Problem: appearance: core with trace back a93swap_to_application a93_sending a93_user_commands +0x0170 (a small number of bytes behind start of user_commands) ak91run_sql_process Preconditions and circumstances: in knldiag it can be seen: started server, then 'malloc,....Not enough space' Client with different swap-kind than server tries to connect Solution: Assure that the needed memory for the server is available and that no malloc-error will be caused during start-up of the server. PTS: 1125797 since: 7.3.00.47 Fixed Problem: appearance: trigonometric function does not return expected value; its 16-th digit differs Preconditions and circumstances: none Workaround: Rounding to 15 digits may help PTS: 1125590 since: 7.3.00.47 Fixed Problem: appearance: knldiag[.err] shows funny (not initialized) character behind system error - info Preconditions and circumstances: unicode-environment Workaround: none Solution: end of variable to be output has to be initialized in unicode-environment PTS: 1125474 since: 7.3.00.47 Fixed Problem: appearance: -8006 during create dbproc Preconditions and circumstances: dbproc includes - a recursive select - with a subquery in the final select and - has some parameter in this recursive select Workaround: Get rid of the subquery in the final select by changing it to a join or use two selects, one for reuse, so the result can be used in the second's select from-part Solution: So far the server forgots the parameter information of those recursive select-parts not being the final one. Now they are not overwritten any more by the parameter information of the final select. PTS: 1125464 since: 7.3.00.47 New Feature: Feature description: MAPCHAR resp. ALPHA now add some output-bytes internally to allow even MAPCHAR ('Ä') without used-defined-output-length PTS: 1125416 since: 7.3.00.47 Fixed Problem: Appearance: Corrupted b*tree index after a synchronization problem in the data cache, which became visible as an error -9001 "BD Invalid Root" in the knldiag and in the application log. Preconditions and circumstances: This could happen if root pageNo's of indexes are stored and used after the corresponding index is re-created or dropped. Additional the root pageNo has to be the root of a new b*tree and at the same time two tasks should access the root pageNo in the data cache, whereby one tasks has the old view and one the new onto the root. Workaround: Do not drop and re-create indexes without updating the pase information of the applications. This could mean, that SAP work processes has to be restarted, which forces a new parse phase. PTS: 1125299 since: 7.3.00.47 Fixed Problem: Appearance: Kernel returns -9044, if an index access was execute with an old parse info containing an old file root. Preconditions and circumstances: Index has to be dropped and recreated and the old root has to be the root of a new b*tree. Workaround: invalidate parse info; restart application PTS: 1125276 since: 7.3.00.47 Fixed Problem: Appearance: Error "-8028 UNION columns must be compatible:DATE" at union select with mixed column types of date, time or timestamp and char unicode columns. Preconditions and circumstances: Database runs as unicode instance Workaround: Usage of chr() function for explicite transformation of date/time/timestamp columns to character columns. PTS: 1125275 since: 7.3.00.47 Fixed Problem: appearance: -7016 during parsing resp. -3016 during execution Preconditions and circumstances: A statement where the datatype and length of a parameter can not defined by the kernel as with SELECT * FROM DUAL respectively a bound application-variable resulting in a description of its datatype and length sent to the kernel which does not fulfill the needs of the kernel for this parameter as a char-variable does for fixed-column + ?. Workaround: The bound application-variable should be of the correct datatype. PTS: 1125116 since: 7.3.00.47 Fixed Problem: appearance: An insert into a table x returns error -4004, even though the table exists. Preconditions and circumstances: The insert has been blocked by another transaction. This transaction then drops and recreates the table. When the first transaction continues, error -4004 is returned until the catalog cache is purged. Workaround: Execute a rollback statement to purge the catalog cache. PTS: 1125035 since: 7.3.00.47 Fixed Problem: appearance: There are more resultrows returned than specified using a ROWNO/ROWNUM-clause. Preconditions and circumstances: SELECT with ROWNO/ROWNUM + correlation used Workaround: None within one SQL statement. And with more statements the ROWNO would be in the last one usually resulting in the full resultset in the (last-1) th statement, therefore the last one is useless. PTS: 1125018 since: 7.3.00.47 Fixed Problem: appearance: Drop index fails with error -9205. Preconditions and circumstances: The index has 16 columns and the index name is longer than 18 bytes. Workaround: None. PTS: 1125000 since: 7.3.00.47 Fixed Problem: appearance: Crash of kernel without traceback because of stack overflow Preconditions and circumstances: Linux, 64bit, SQL-command with really many arithmetic operations in one expression resp. really many AND/OR-terms resp. unusual number of subqueries included. No specific values can be given because it depends on the given userstack. Workaround: Separate the statement into at least two. PTS: 1124981 since: 7.3.00.47 New Feature: Feature description: To reduce the wait time for index updaters, index readers will look after every processed index leaf page if an exclusive index request exist. If so the index scan is interrupted and the exclusive request is executed. After the exclusive lock the read access goes on. PTS: 1124816 since: 7.3.00.47 Fixed Problem: Appearence: more than one outer join Preconditions and circumstances: access path (index, key) to right outer join table Workaround: delete access path to right outer join table not R/3 relevant PTS: 1124802 since: 7.3.00.47 Fixed Problem: appearance: Error -3019, -3048 or the like (those checking input-values) Preconditions and circumstances: call of a dbproc including a declare cursor whose cursorname is given as parameter and which includes a join and the isolation level differes between creation of dbproc and current isolation level Workaround: No join in the select, no parameter name used for the cursorname --> use two selects, one with the join, second with no join and the cursorname resp. do the join in the from-part of the final select PTS: 1124732 since: 7.3.00.47 New Feature: Feature description: New option EXTENDED for CHECK TABLE and VERIFY command to check the structure of the data base. In contrast to the default behaviour of check table and verify the extended mode checks the ascending order of the keys in the primary (table) and secondary (indexes) data pages. Note that the new checks will increase the CPU consumption of the participated task and therefore the total runtime will increase too. Syntax: CHECK TABLE [EXTENDED] VERIFY [EXTENDED] PTS: 1124726 since: 7.3.00.47 Fixed Problem: Appearance: Error -9205 at alter table add/drop primary key on temp tables Workaround: Define primary key at creation time or use create table as select to copy the temp table PTS: 1124643 since: 7.3.00.47 Fixed Problem: 1) Preconditions and circumstances SELECT .. FROM DOMAIN.COLUMNS for a non-updatable joinview returns values <> NULL in the keypos column. This is wrong since these view don't have a key. 2) Is it internal or external visible ? Both. 3) Propability that the error occurs High. 4) Is there a WorkAround and how does this work ? No. PTS: 1124479 since: 7.3.00.47 Fixed Problem: miscellaneous Appearance possible, not seen so far: -9206 System error: AK Duplicate catalog information Preconditions and circumstances currently a new table/view is created, leading to the error mentioned above after a create table...as select was done, which resulted internally to an old fileversion, was therefore retried, succeeded, but used an arbitrary surrogate, which now should be used (again) or the create table..as select tries to 'reuse' that surrogate (identification) because of its missing surrogate-initialization Workaround none PTS: 1124396 since: 7.3.00.47 Fixed Problem: Precondition: join select with "not exists" predicate Appearance: wrong result Workaround: no PTS: 1124386 since: 7.3.00.47 Fixed Problem: miscellaneous Appearance Error -4003 unknown user Preconditions and circumstances ALTER PASSWORD + is given as special identifier (with "...") Workaround If possible, avoid " in that case, otherwise, there is no workaround PTS: 1124328 since: 7.3.00.47 Fixed Problem: 1) Appearance (short description of the problem and how it can be realized) Kernel crash during SQL Connect via DBM, if the data base has no free pageNos. 2) Preconditions and circumstances Data base has to be full. See knldiag for DB Full messages0 3) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) no PTS: 1124149 since: 7.3.00.47 Fixed Problem: Appearence: "dbmcli util_execute suspend logwriter" returns only a couple of '*' as sequence number Workaround: no PTS: 1124114 since: 7.3.00.47 Fixed Problem: wrong results, miscellaneous Appearance Error -3016, -3019 we saw, but others are possible Preconditions and circumstances Update * of a LONG-column + * another non-key-column, whose value is not specified using a literal or ? or :parameter, but with something that has to be calculated (+1, or function around or something like that) Workaround Separate the update of the two columns into two updates PTS: 1124104 since: 7.3.00.47 Fixed Problem: RowShareRequests are not satisfied if SysShareLocks exist because TabRequests are preferred satisfied and if a SysShareLock was removed RowRequests were not satisfied. Such waiting RowRequests are only removed by the timeout. This can only happen if ALTER commands are used. PTS: 1124034 since: 7.3.00.47 Fixed Problem: Appearance: "SET TO READ ONLY" messages within knldiag for table SYSUPDSTATWANTED. This messages have no further consequences. Precondition: kernel version >= 7.3.0.36 (see pts 1121915) Workaround: no PTS: 1124014 since: 7.3.00.47 New Feature: Feature Description: For better error diagnostics in case of lock collisions on pages the pageNo is visible in the console output after the suspend reason. Additional the pageNo is visible in the systemtable domain.sysmon_active_task in the column WATING4ROOT. PTS: 1123959 since: 7.3.00.47 Fixed Problem: system error Appearance Error -9210 kb stack op illegal Preconditions and circumstances in case of an EXISTS in the select_list (for example as part of a case-function) Workaround Change the SQL-statement, for example do a from-select with COUNT(*) (perhaps with ROWNO <=..) and use a CASE/DECODE for the count-result as with SELECT DECODE (cnt, 0, 'nothing', 'some'),... FROM (SELECT COUNT(*) cnt FROM ...) cnttab, ... PTS: 1123002 since: 7.3.00.47 Fixed Problem: FETCH PREV might not find all records. The workaround only can be a FETCH NEXT. PTS: 1122524 since: 7.3.00.47 Fixed Problem: Precondition: Only index select with min/max function and min/max operand is also a function. Appearance: Wrong result Workaround: Avoid only index strategy by selecting a non index column or dropping the index PTS: 1122272 since: 7.3.00.47 Fixed Problem: Precondition: Join select with equal condition between a coulmn and a constant and constan length is greater than column length. Appearance: error -2010 Workaround: No PTS: 1118630 since: 7.3.00.47 Fixed Problem: Appearance: Emergency shutdown because of error code -9013 or -9014. Preconditions and circumstances: The b*tree structure could corrupt, if an error occur during an update operation on the b*tree and a savepoint takes place before the emergency shutdown - caused by the error - is executed. Workaround: no gotten to enter the solution> PTS: 1117174 since: 7.3.00.47 Fixed Problem: a call of a db-procedure containing 2 catalog selects may crash the kernel. This problem has been solved. PTS: 1125186 since: 7.3.00.45 Fixed Problem: appearance: Unpredictable errors may occur due to an internal state of the catalog cache, for example see http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1124950 Preconditions and circumstances: Unpredictable. Workaround: None PTS: 1124953 since: 7.3.00.45 Fixed Problem: Core appearance: ak562do_select_insert a562_select_insert ak35call_semantik Preconditions and circumstances: INSERT...SELECT for table having SYSKEY Workaround: Some DDL (create index, drop index) before trying again. Then problem should never occur again PTS: 1124871 since: 7.3.00.45 Fixed Problem: Appearence: A call of a db-procedure returns error -9205, catalog information not found. Preconditions and circumstances: The execution of a sql statement inside the db-procedure fails with -8 and the db-procedure has been dropped in the meantime.. Workaround: None. PTS: 1124489 since: 7.3.00.45 Fixed Problem: crash (in slowknl), system error, miscellaneous Appearance core-trace-back: sql__setrang g03dfchange_format_date g03dchange_format_date ak48date_time_analyze a48get_view_def_string a508get_definition_text -8 datatype NULL Preconditions and circumstances core: when select .. from viewdefs is called and the viewdefinition includes a date(internal)-value, the current sqlmode is oracle or the date_and_time_format <> internal -8 : SELECT .. FROM DBTIMES datatype : SELECT .. FROM COLUMNS WHERE tablename = 'DBTIMES' Workaround none PTS: 1124244 since: 7.3.00.45 Fixed Problem: 1) Appearance (short description of the problem and how it can be realized) Kernel will crash during select comands with an illegal page no access. The knldiag contains something like this "DATACACH Illegal Pno 4711" and a stack back trace containing the procedures bd50count_records, bd50eval etc. 2) Preconditions and circumstances This could happen if the internal base table evaluation during join processing is executed with counting the records in a given key range. Additional the given start key has to be nearly at the right edge of the b*tree. 3) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) no PTS: 1123935 since: 7.3.00.45 Fixed Problem: appearance: Error -9211 System error: KB Stack type illegal at outer join selects with order by on constant expressions. Workaround: Rewrite the statement to a from select with order by clause where the inner select is the outer join, e.g. select 4 as prio from t1, t2 where t1.x = t2.y (+) order by prio => select prio from (select 4 as prio from t1, t2 where t1.x = t2.y (+)) order by prio PTS: 1123890 since: 7.3.00.45 Fixed Problem: appearance: After recovery of a data backup on a unix system the error "no converter entry" occurs. What means that not all pages are restored although the recovery result was OK. The used tape media has no upper limit and is written until the device driver signals "end of tape reached". Preconditions and circumstances: On unix systems it is allowed to write less then the given blocks. Returned is not an error but the real amount of blocks which could be written. On NT systems an error signals the "end of tape". The backup and recovery code assumes that an error is set if not all could be written or read. Workaround: You must specify an upper limit (COUNT) for the tape media. Solution: After calling vasynio not only the return code must be check but the written or read blocksize too. The io result is now analyzed correctly. PTS: 1123055 since: 7.3.00.45 Fixed Problem: Precondition: diagnose monitor parseid was enabled and then switched off Appearance: system view running_commands shows outdated entries Workaround: No PTS: 1121195 since: 7.3.00.45 Fixed Problem: 1) Appearance (short description of the problem and how it can be realized) Completely wrong estimated optimizer statistics after short run time. 2) Preconditions and circumstances Update statistics will estimates completely wrong results, if the given table contains a couple of GB. 3) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) You can set the sample rate to 100%. This will increase the runtime, because the entire table will be examined. Do not forget to set it back to its default once you have installed a database version fixing this bug. PTS: 1123808 since: 7.3.00.43 Fixed Problem: wrong results Appearance Float-value truncated to fixed-value Preconditions and circumstances Function having more than one numeric parameter, which have to be of equal datatype/length as in LEAST, GREATEST, DECODE (but not SUBSTR, where some numeric parameters are in) + the first parameter is a fixed-point-number and one of the others is a floating-point-number. Workaround Try to change sequence of values resp. do some arithmetic (division) to force the first parameter to be float (in case of decode, where sometime sequence-change is not possible) PTS: 1123779 since: 7.3.00.43 Fixed Problem: SQL commands, system error Appearance Error -8 Preconditions and circumstances - unicode-catalog - statement-length 4006 (ascii) resp. 8012 (unicode) - create table or explain Workaround Add at least 2 blanks somewhere in the middle of the statement. PTS: 1123749 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance The first part or the whole transaction is rollbacked, although not rollbacked by the user/application. Preconditions and circumstances ROLLBACK TO which resulted in -7065 SUBTRANS COMMIT/ROLLBACK not allowed without SUBTRANS BEGIN Everything in this transaction before this ROLLBACK TO is rollbacked. Workaround Check savepoint_names three times before using them in ROLLBACK TO. PTS: 1123729 since: 7.3.00.43 Fixed Problem: wrong results, miscellaneous Appearance Long-columns are empty/blank although string-literal was inserted to it. Preconditions and circumstances Insert was done using an updatable joinview. Workaround Insert using the primary tables, not the joinview. PTS: 1123717 since: 7.3.00.43 Fixed Problem: SQL commands Appearance ERROR -7032 SQL statement not allowed for column of data type LONG Preconditions and circumstances using WHERE long_col IS [NOT] NULL + using DISTINCT or being in from-select or in subquery Workaround Two statements have to be build out of this one PTS: 1123693 since: 7.3.00.43 Fixed Problem: wrong results Appearance digits (123000) results in '000123' Workaround in many cases function CHR will help PTS: 1123666 since: 7.3.00.43 Fixed Problem: crash, SQL commands Appearance Core vak05.p', Line: (around 17000), dereferenced pointer is nil with trace back a05password_get ak21_alter_create_user_semantic Preconditions and circumstances unicode-database + CREATE USER/ALTER USER with no password specified. Workaround Correct the statement and do not forget to write the password. PTS: 1123618 since: 7.3.00.43 Fixed Problem: internal only PTS: 1123563 since: 7.3.00.43 Fixed Problem: 1) category: Performance 2) appearance: explain with predefined join sequence shows a cheaper cost value as a computed sequence 3) precondition: join sequence search level = 9 4) workaround: none PTS: 1123554 since: 7.3.00.43 Fixed Problem: system error Appearance -9205 System error: AK Catalog information not found: xxxxxxxxxxxxxxxx0060 (x being any hex-digit), other errors are possible, too Preconditions and circumstances FETCH or SELECT on LONG-column, LONG-column-surrogate ending with hexadecimal '00' Workaround none PTS: 1123509 since: 7.3.00.43 New Feature: STOP ON ERROR stops even switch-output PTS: 1123505 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance we saw -2027, but other errors (not convertable numbers, -2000 row to long) possible Preconditions and circumstances select ... longcol union all select ... null from + order by or another union all behind Workaround create a dumm-table, with exactly one column with the corresponding long-datatype, fill it with one row and the null-value, add that new table to the join and change null to the column from the dummy-table PTS: 1123488 since: 7.3.00.43 Fixed Problem: migration, restart, system error, crash, system tables Appearance error -9404 vak00, 1 resp. core with traceback of ak361NamedIndexRecord a361migrate Preconditions and circumstances Migration from 6.2 --> 7.2/7.3, first restart with 7.2/7.3, the catalog migration is done at that time Workaround Sometimes an increasing/decreasing of _CAT_CACHE_MINSIZE (combined with a decreasing of MAXUSERTASKS) will help. PTS: 1123394 since: 7.3.00.43 Fixed Problem: crash Appearance Crash in kernel, no correct stackback trace given. Preconditions and circumstances create dbproc or create trigger + a create table (or some other long statement resulting in an internal structure with several hundred levels) with around 1000 columns Workaround Increase installation parameter _MAXTASK_STACK PTS: 1123346 since: 7.3.00.43 Fixed Problem: 1) Appearance (short description of the problem and how it can be realized) Select * from TABLESTATISTICS returns with -9000, not implemented. 2) Preconditions and circumstances This could happen if the table has a long column and the kernel internal description of the long column within the filedirectory says that this long column is a 'special' one. 3) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) Do not select the tablestatistics. BTW select tablestatistics is a very cost intensive call, because all pages of the tree will be read and the tree is blocked as long as the operation takes place. PTS: 1123323 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance Error -8004 although the qualification looks correctly. Preconditions and circumstances Superfluous bracket + qualification with NOT + more than one qualification behind that bracket, example a AND (NOT c AND NOT d) AND e AND f (each small letter being a comparison) Workaround Avoid superfluous brackets. PTS: 1123231 since: 7.3.00.43 Fixed Problem: 1) Appearance (short description of the problem and how it can be realized) Database kernel should not executes an emergency shutdown after check table, verify respl. verify cold terminates with the error code -9003. 2) Preconditions and circumstances You need at least one corrupted record, which causes the fatal error illegal_entry_length (-9003). 3) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) no PTS: 1123112 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances The 'no reference' option of the create/drop view statement introduced for BW does not prevent from reference locks completly. This results in deadlocks in the BW application. 2) Is it internal or external visible ? external. 3) Propability that the error occurs middle. 4) Is there a WorkAround and how does this work ? no. PTS: 1123087 since: 7.3.00.43 Fixed Problem: Precondition: Join select with IN clause on index or key field Appearance: Bad performance because of wrong join sequence Workaround: Try to optimize command with create or drop index PTS: 1123052 since: 7.3.00.43 Fixed Problem: wrong results, system error Appearance Error row not found or wrong rows inserted Preconditions and circumstances - insert...select ... where... (select date/timecol...) - current date_and_time_format <> INTERNAL Workaround The problem can be avoided by using function CHAR (.. , ..) in the upper select and in the subquery PTS: 1123009 since: 7.3.00.43 Fixed Problem: system error Appearance Error -9111/-602 with knldiag-entry VAK05.4: []->1[8192000] len: and m-1+x > n during preparation of a statement Preconditions and circumstances A unicode-database + an ascii-interface + a long statement, exceeding half of the available size in the input packet Workaround Increase installation-parameter _PACKET_SIZE and/or shorten the statement PTS: 1122940 since: 7.3.00.43 Fixed Problem: Precondition: Unicode database and the DBM user has a password with more then 9 characters Appearance: Error -4008 at utility connect with the DBM user Workaround: Change DBM password with dbmcli command user_put PTS: 1122894 since: 7.3.00.43 Fixed Problem: SQL commands Appearance Error -8017 for select-statement Preconditions and circumstances Select-statement has HAVING-clause with IS [NOT] NULL in. Workaround If the expression checked against NULL is of datatype number, it can be changed to ... > ; with character-expressions something like <> 'somestupidstring' may help PTS: 1122884 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances If the last field of a foreign key is of datatype unicode and the delete rule is 'on delete set default', the trailing blanks of the last field are not removed when storing the default foreign key in the catalog. If the default foreign key is then inserted into the foreign key table and the foreign key does not exist as key of the referenced table, the insert fails wrongly. 2) Is it internal or external visible ? both 3) Propability that the error occurs low 4) Is there a WorkAround and how does this work ? no PTS: 1122858 since: 7.3.00.43 Fixed Problem: wrong results, corrupted data Appearance different errors possible showing that data in some records does not correspond to table definition Preconditions and circumstances ALTER TABLE .. MODIFY a column which was stored with fixed length, some records had the NULL-value in that column and the new length for storing that column is smaller than the old one. Workaround Data in that records is corrupted. One can try to see as much data as possible by calling hex(...) for all columns for those records, deleting them and inserting them again. If number-data is included, one will need some help of support to'read' the data. PTS: 1122804 since: 7.3.00.43 Fixed Problem: wrong results Appearance Row not found resp. resultrow found which is part of the resultset, but not the resultrow wanted at that time (the wrong resultrow-number). Preconditions and circumstances If Arrayfetch is used (implicitly) for FETCH FIRST and no FETCH (NEXT) afterwards, FETCH ABSOLUTE/RELATIVE/PREV will result in the wrong resultrow/row not found. Workaround FETCH (NEXT) will clean that situation PTS: 1122782 since: 7.3.00.43 Fixed Problem: category: SQL commands message while 'FETCH SAME': ERROR -2010 Assignment impossible, char value too long appearance: 'FETCH SAME' on fetch result set and an 'index only' strategy PTS: 1122768 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance Error -2010 for a NULL-value Preconditions and circumstances If the length of the input-parameter will be checked for some functions like chr (..., maxlength) then NULL-value may, but need not result in that error Workaround Surround the column which includes the NULL-value with a dummy-function, like SUBSTR (...., 1) PTS: 1122742 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance Error -2010 when calling a dbproc/a trigger, even if no character data is used. Preconditions and circumstances Dbproc/Trigger uses local variable of datatype float(n) n > 20. This variable is filled with something of more than 20 digits. Workaround Define the local variable with n <= 20. PTS: 1122685 since: 7.3.00.43 Fixed Problem: crash Appearance Trace-Back ak13modify_default ak13modify Preconditions and circumstances ALTER TABLE .. MODIFY for a column of datatype TIMESTAMP/BOOLEAN and default TIMESTAMP/TRUE/FALSE Workaround Try to drop the default before modifying the column PTS: 1122680 since: 7.3.00.43 New Feature: For sqlmodes <> Oracle the optional keyword AS is now allowed between table_name and reference_name in a table_spec. PTS: 1122666 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances If a table has a serial column and an alter table statement for that table requires a table copy, the current serial value is not copied into the catalog. This results in duplicate serial values causing error 200, duplicate key. 2) Is it internal or external visible ? external. 3) Propability that the error occurs middle. 4) Is there a WorkAround and how does this work ? no. PTS: 1122612 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances crash because of using 'monitor init' command 2) Is it internal or external visible ? both 3) Propability that the error occurs unknown, depending on use of monitoring. 4) Is there a WorkAround and how does this work ? Don't use 'monitor init' command PTS: 1122532 since: 7.3.00.43 Fixed Problem: category: wrong result set/count precondition: MIN/MAX aggregate function with first index column in output list and 'GROUP BY' clause workaround: none PTS: 1122518 since: 7.3.00.43 New Feature: preventing kernel from crashing if internal system error occur PTS: 1122483 since: 7.3.00.43 Fixed Problem: system error Appearance -9409 AK system error VAK00 1 Preconditions and circumstances The detailed circumstances are unknown. But some internal severe error occured, the errornumber was saved, some additional work done, the original errorno restored. But the errorpos (holding the info where the error occured) is neither saved nor restored, at least in one situation explicitly set to 1 resulting in the output given above. Workaround none PTS: 1122453 since: 7.3.00.43 Fixed Problem: category: SQL commands, error appearance: "-2001 key too long" precondition: cartesian product and local outer join predicates instance: SELECT B FROM T2,T1 WHERE 3(+) = B PTS: 1122444 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance error -8 remaining temporary table locks error -3048 Preconditions and circumstances Union with correlation in from-select select.. from xyz isolation level 0 after select on same table with same cursorname and isolation level 20 correlatied Subquery without any parameter, but with date/time/timestamp in Workaround change select-statement close cursor explicitly before reusing it use a dummy-param PTS: 1122409 since: 7.3.00.43 New Feature: Earlier releases only evaluates OR strategies if the strategy of the upper AND terms have a bigger ratio of pages read/all pages then 0.001. For big tables this threshold is not suitable because the amount of pages which have to be read could be very great. Now the threshold is removed and all possible OR strategies are evaluated. PTS: 1122369 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance error -9000 during an insert Preconditions and circumstances - a unicode-database + - an insert into a non-unicode LONG-column using a string_literal + - specifying more than (a little bit less than) 4000 character, which can be specified without problem if a non-unicode-database is used. Workaround usage of host-variables and using parameter in the insert PTS: 1122346 since: 7.3.00.43 Fixed Problem: miscellaneous Appearance The column-definition RAW is accepted, although has to be disallowed together with RAW; RAW only allowed in sqlmode Oracle Workaround none needed, a normal RAW-column is created PTS: 1122318 since: 7.3.00.43 New Feature: connection Appearance different possible errors, noone found so far, but possible Preconditions and circumstances A client with no unicode-functionality is connected to a unicode-database Workaround Use a newer client PTS: 1122307 since: 7.3.00.43 Fixed Problem: Preconditions and circumstances A deadlock is detected but it relates to another deadlock which can only be resolved by the request timeout. Example: All transactions work with the same record. T1 set row share T2 set row share T3 req row exclusive => wait T2 req row exclusive => wait T1 req row exclusive => DEADLOCK, work rollbacked, -600 => T1 is termintated, T2 and T3 are waiting. PTS: 1122297 since: 7.3.00.43 New Feature: Avoid crashing af database kernel, if inconsistent strategy data appear PTS: 1122281 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances If a db-procedure having inout parameters of type date, time, timestamp is called from a unicode client, wrong result values may be returned. 2) Is it internal or external visible ? Internal. 3) Propability that the error occurs low 4) Is there a WorkAround and how does this work ? Don't use inout parameter, use in and out parameters instead. PTS: 1122264 since: 7.3.00.43 Fixed Problem: crash, wrong results Appearance Values for UTCDATE, UTCDIFF, TRANSACTION and TIMEZONE does not show the current value, but an older one resp. a core with an case-checking-error (no otherwise part) in vak54 around line 14400 Preconditions and circumstances At least one of those functions is used in a (not in a normal insert) resp. UTCDATE or UTCDATE is part of a view which is selected now. Workaround none PTS: 1122244 since: 7.3.00.43 Fixed Problem: Precondition: Usage of prepared statements joined with drop and create of temp tables. Appearance: Wrong result at select on temp table. Workaround: reparse select after drop and create of temp table PTS: 1122238 since: 7.3.00.43 Fixed Problem: system error / core Appearance move error -9111 with info vak542, 9 in knldiag resp. core if tried to reproduce with slow kernel Preconditions and circumstances Select exceeding 8000 bytes having a complex view in the from-clause Workaround Try to shorten the select or select * from complex view and then do a select .. from PTS: 1122227 since: 7.3.00.43 Fixed Problem: system error Appearance -9211 kb_stack_type_illegal on DEC OSF/1 Preconditions and circumstances ALTER TABLE..ADD PRIMARY KEY ... and those column(s) specified to become PRIMARY KEY have a UNIQUE INDEX Workaround Drop that index before the ALTER TABLE PTS: 1122193 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances If a table contains case sensitive columns names (special identifiers), it is not possible to use those columns as parameters of a trigger, because the parameter syntax does not accept quotes. 2) Is it internal or external visible ? Both. 3) Propability that the error occurs Middle 4) Is there a WorkAround and how does this work ? Don't use special identifiers as column names. PTS: 1122186 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances If a column is indexed and becomes key of a table via 'ALTER TABLE ... ADD PRIMARY KEY', the index has not been dropped. 2) Is it internal or external visible ? both. 3) Propability that the error occurs middle. 4) Is there a WorkAround and how does this work ? Drop the index by hand before execution of the alter table statement. PTS: 1122164 since: 7.3.00.43 Fixed Problem: not relevant for support and customers PTS: 1122156 since: 7.3.00.43 Fixed Problem: category: wrong result precondition: several subselects with outer join workaround: none PTS: 1122143 since: 7.3.00.43 Fixed Problem: endless loop Appearance CPU used 100 % Preconditions and circumstances select called with no set_function used in the select_list, but group by used with the select_list-columns + order by used with set_function Workaround put the set_function in the select_list, too PTS: 1122104 since: 7.3.00.43 Fixed Problem: wrong results (destroyed permanent data) Appearance values seeming to be in the wrong column and/or conversion problems of numbers/date-and-time-values and so on Preconditions and circumstances An update .. SET (col1, col2...) = (SELECT...) was done with at least 2 columns to be updated and a CORRELATED subquery in the SET-part Workaround One subquery per column to be updated in case there is a correlation involved in the update PTS: 1122042 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances A correlated update on a table having an update trigger produces error 200, if more than about 32 rows are affected. 2) Is it internal or external visible ? Both. 3) Propability that the error occurs low. 4) Is there a WorkAround and how does this work ? Do single row updtaes only (select for update, update where current of): PTS: 1122041 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances A select from all system views using sysdd.locks may produce -9111, move error. 2) Is it internal or external visible ? both. 3) Propability that the error occurs Middle, there must be a catalog lock on any table or view while the select is running. 4) Is there a WorkAround and how does this work ? No. PTS: 1121921 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances Under certain conditions alter table modify allows to reduce the length of a column, even though column values with greater length exist. This is true, if the table has not to be copied internally. 2) Is it internal or external visible ? external 3) Propability that the error occurs middle 4) Is there a WorkAround and how does this work ? verify the data via a select statement first. PTS: 1121654 since: 7.3.00.43 Fixed Problem: If a restore log is aborted a savepoint is written. If this is done in a batch job there is a high chance that a followup restore log will terminate with -9209 (logpage not found). A workaround is to repeat the complete recovery with data and then log. PTS: 1119005 since: 7.3.00.43 Fixed Problem: Precondition: subquery in join selects Appearance: Wrong result Workaround: No PTS: 1118641 since: 7.3.00.43 Fixed Problem: system error Appearance -9005 System error: BD Illegal key Preconditions and circumstances (DISTINCT ) where the internal length of (the maximum definition-length+1) is > 1024 Workaround (DISTINCT SUBSTR(,1,1023)) in case of a ascii/byte-column, (DISTINCT SUBSTR(,1,511)) in case of a unicode-column PTS: 1123292 since: 7.3.00.41 Fixed Problem: system error, wrong results Appearance Error -9806, a number-representation includes one byte X'FE'. Preconditions and circumstances SELECT with set-function (MIN/MAX/...) + GROUP BY plus the byte X'FE' at a special position (different for different selects) in the data handled Workaround none System Tables: ============== PTS: 1124798 since: 7.3.00.45 Fixed Problem: appearence: Sucessful backup actions are displayed as defective in the R/3 planning calendar (transaction DB13), and no action logs could be found for the backup actions in transaction DB13 and DB12. Reason: since dbmcli command "load_r3tab" yields an error, the file dbm.utl could no longer be loaded into the systemtable CNREPRT. Preconditions and circumstances: Occurs always since version 7.3.00.43. Workaround: Eliminate the line DATE 'MM DD' from CNR3DATA.ins in \env\ Solution: With this patch this error does not occur anymore. Installation: ============= PTS: 1125952 since: 7.3.00.47 Fixed Problem: appearance: The installation parameter DEFAULTCODE=internal results in EBCDIC-columns Workaround: use CHAR (..) ASCII resp. UNICODE or specify a user-dependant defaultcode (in releases, where this is possible) Solution: The installation will not allow INTERNAL any more PTS: 1125583 since: 7.3.00.47 Fixed Problem: aappearance: after installation/update of Server its impossible to start/stop x_server (permission denied) Preconditions and circumstances: x_server with update feature is running during installation niserver and vserver images have no sbits Workaround: chmod 550 /pgm/vserver /pgm/niserver Solution: use SDBINST/SDBUPD > 7.3.00.35 C Precompiler: ============== PTS: 1126190 since: 7.3.00.47 Fixed Problem: appearance: The precompiler returns -817 'Incompatible datatypes' for LONG UNICODE columns Preconditions and circumstances: You use an UNICODE enabled database and static SQL with LONG UNICODE columns Workaround: Use the -Hnocheck option of the precompiler Solution: A software update is necessary PTS: 1119643 since: 7.3.00.47 Fixed Problem: The hostvariable of type TCHAR was always mapped to a char type on windows platforms, also for unicode applications. This bug is fixed Precompiler Runtime: ==================== PTS: 1127063 since: 7.3.00.47 Fixed Problem: appearance: Trace file name is 'T.pct' when trace is enabled via shared memory at begining, and does not respect compiled-in setting of name. Preconditions and circumstances: Always if the trace is enabled via shared memory at begining. Workaround: do not enabling trace via shared memory before the program is running Solution: precompiler update PTS: 1126998 since: 7.3.00.47 Fixed Problem: appearance: EXEC SQL DESCRIBE INTO DESCRIPTOR sometimes returns a wrong column length for unicode columns if you run in oracle mode Preconditions and circumstances: orcalce mode using an oracle sqlda data structure Workaround: none Solution: precompiler update PTS: 1126588 since: 7.3.00.47 Fixed Problem: appearance: Blanks are cut off from UCS2 data when retrieving data using hostvariables of type SQL_ORA_UCS2, SQL_ORA_UTF16 or SQL_ORA_TCHAR together with oracel or sapr3 mode. Preconditions and circumstances: Data is stored into UCS2 columns and retrieved using hostvariables of above mentioned types. Workaround: Use other host variable types. Solution: Use new precompiler runtime library. PTS: 1126485 since: 7.3.00.47 Fixed Problem: appearance: No error code is delivered into sqlca.sqlcode after failed PUTVAL/GETVAL statements, if request/receive communication with database kernel produces the error. Preconditions and circumstances: Kernel communication error while request/receive. Workaround: None. Solution: Use new precompiler runtime library. PTS: 1126184 since: 7.3.00.47 Fixed Problem: appearance: If UCS2 long columns are read into ASCII hostvariables by the use of GETVAL statements, the application may crash. It is also possible that the application fails with error "-777 Conversion from UNICODE impossible". Preconditions and circumstances: Use of UCS2 long columns in the database and ASCII hostvariables in the application. Workaround: None. Solution: Use a new precompiler runtime library. PTS: 1126082 since: 7.3.00.47 Fixed Problem: appearance: SELECT ... INTO command is send as mass command to database kernel if internal mode is used. This can lead to an error "-5015 Missing keyword: FROM". Preconditions and circumstances: SELECT ... INTO is used. Workaround: Don't use internal mode for SELECT ... INTO command. Solution: Use new precompiler runtime library. PTS: 1126054 since: 7.3.00.47 Fixed Problem: appearance: Error "Invalid VDN Number" durring floating point number conversion. Preconditions and circumstances: A conversion error occurs while converting some special floating point values into the internal number format Workaround: none Solution: a precompiler update is needed PTS: 1125878 since: 7.3.00.47 Fixed Problem: Appearance: Errror -883 in CONNECT. Preconditions and circumstances: The username or password is specified as TCHAR variable, and the source is precompiled with Unicode option. Workaround: Use a character data type of explicit width, i.e. SQLUCS2, or char. Solution: The handling of the TCHAR data type was added to the connect handling. PTS: 1125871 since: 7.3.00.47 Fixed Problem: Appearance: Error -778 appears on a prepare from an Unicode host variable. Preconditions and circumstances: A command FETCH USING DESCRIPTOR is prepared from an Unicode host variable in a precompiler program in internal mode. Workaround: None, a software update (precompiler runtime) is necessary. Solution: The case of the unnamed result set is now handled properly in the precompiler runtime. PTS: 1125770 since: 7.3.00.47 Fixed Problem: Appearance: Error -778 when preparing a FETCH from a host variable. Preconditions and circumstances: When a host variable is defined as UCS2 (SQLUCS2 or TCHAR in Unicode mode), an it is used to contain a FETCH command using a descriptor, e.g. the command FETCH CURSORNAME USING DESCRIPTOR and a precompiler command EXEC SQL PREPARE FCOMMAND FROM :HOSTVAR is executed, always an error -778 is returned. Workaround: None, a software update is necessary. Solution: xxx PTS: 1125642 since: 7.3.00.47 Fixed Problem: appearance: When inserting UCS2 long data into a LONG UNICODE column the error "(-3989):Invalid long column length" can occur. Preconditions and circumstances: UCS2 host variable, LONG UNICODE column, and long UCS2 data to insert exceeds packet size of database. Workaround: Increase packet size of database. Solution: A new precompiler runtime library must be installed. PTS: 1125312 since: 7.3.00.47 Fixed Problem: appearance: The R/3 application server is blocked if an signal 8 is reviece. The stackbacktrace ended within a sqlrealloc, sqlalloc or sqlfree call. Preconditions and circumstances: If an signal is recieved by the disp+work process the signalhandler calls an dbsl_break funktion. The dbsl_break or any of their called functions (EXEC SQL CANCEL) allocates new memory for the execution of the cancel call. Since memory allocation function are not allowed within a signalhandler the proces may be deadlocked by this mallc call. Solution to the problem A Softwareupdate is necessary Workaround: None PTS: 1124644 since: 7.3.00.47 New Feature: Feature description: The performance of the precompiler runtime was significantly improved by using a hash based data structure for the internal data container PTS: 1124575 since: 7.3.00.47 Fixed Problem: 1) Preconditions and circumstances The application returns the errormessage -4012 'Unknown parseid after a serverdb crash/shutdown or reconnect 2) Solution to the problem A Softwareupdate is necessary 3) Probability that the error occurs Only if the database transaction before the crash was uncommitted. 4) Workaround One of these action would help: - Restart your database twice - Connect to the database with a different application before reconnection your program/appserver. - Restart your program/appserver. PTS: 1121986 since: 7.3.00.47 Fixed Problem: 1) Preconditions and circumstances Several long data conversions from/to unicode missing. The kind of conversion is depending on wether ASCII or UCS2 order packets are used. 2) Solution to the problem An update of the precompiler runtime library is necessary. 3) Probability that the error occurs Always if not-supported conversion is used. 4) Workaround None. PTS: 1125255 since: 7.3.00.46 New Feature: Feature description: For security enhancement the memory mapped file for enabling the precompiler trace is now located in $HOME/.sdb/ The irtrace tool updates the file irtrace.shm in this directory PTS: 1124299 since: 7.3.00.44 Fixed Problem: 1) Preconditions and circumstances Indicator variables in SQLDA structure are not well aligned. 2) Solution to the problem An update of the precompiler runtime library is necessary. 3) Probability that the error occurs Could occur if not-well aligned memory is used. 4) Workaround Use well-aligned memory for index variables in the SQLDA. PTS: 1124291 since: 7.3.00.44 Fixed Problem: Error messages in diagnostic files: none diagnostic file: precompiler trace Error message: none (illeagal content in character values) Appearance: Character arrays are not padded with blanks if the kernel column is a unicode column. Preconditions and circumstances If the hostvariable size is longer than the corresponding kernel column and the kernel column is a unicode column then the hostvariable will not be padded with blanks. Probability that the error occurs always, but usually the hostvariables used by R/3 are not longer than the kernel column Workaround none, update of the precompiler runtime is needed. Further documentation none PTS: 1123575 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances The application returns to few values on the second call to an SELECT COUNT(*) 2) Solution to the problem A Softwareupdate is necessary 3) Probability that the error occurs Always 4) Workaround Do not EXEC SQL CLOSE CURSOR. Closes the cursor implicite during a reopen instead PTS: 1123179 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances - The application runs under R/3 and SAPDB is the central instance. - R/3 without SAPDB but with a liveCache instance are not affected. - A long running or deadlocked connection is killed with x_cons - The errorcode 800 is show in the prcompiler trace - The stackbacktrace shows follwong entries p03cpacketinit pr03PacketInit pr01ConNewCont pr03onConnect 2) Solution to the problem A Softwareupdate is necessary 3) Probability that the error occurs Always 4) Workaround Do not kill the task with x_cons PTS: 1122883 since: 7.3.00.43 New Feature: Number values returned from the database and converted into a string representation will get a nicer format. If the buffer size is to small the digits behind the point will be truncated. This leads to a lost of the precision, but it avoids the exponend represenation of the number values which cannot be handled by R/3. PTS: 1122359 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances A memory access error could cause a precompiler application to crash if parseinfo cache is enabled. 2) Solution to the problem An update of the precompiler runtime library is necessary. 3) Probability that the error occurs Depending on the parseinfo cache entries and machine depending memory allocation functions. 4) Workaround Disable parseinfo cache. PTS: 1122208 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances In case of ASCII database, if a precompiler program uses connect with KEY DEFAULT and the xuser data is empty, the wrong error message "-4025 Errortext corrupted (SourceExhausted)" is printed instead of the correct one "-4008 Unknown user name/password combination". 2) Solution to the problem An update of the precompiler runtime library is necessary. 3) Probability that the error occurs If a ASCII database is used. 4) Workaround None. PTS: 1122187 since: 7.3.00.43 Fixed Problem: Error messages in diagnostic files: diagnostic file: none Error message: none (after register a precompiler runtime, no appropriated runtime will be find) Appearance: Registering a new precompiler runtime remove all registered runtimes with the same version and key. Preconditions and circumstances The error occures only on windows platforms. The runtime which will be register has the same version and same key like a registerd runtime, but they differs in the case of the letters of path. Probability that the error occurs see Preconditions and circumstances Workaround none, update of irconf is needed. Further documentation none PTS: 1120678 since: 7.3.00.43 Fixed Problem: Error messages in diagnostic files: diagnostic file: precompiler trace Error message: -75 Too many SQL statements (work rolled back) Appearance: If a lot of "SET ISOLATION LEVEL" commands will be send as a precompiler command (EXEC SQL SET ISOLATION LEVEL ) an error -75 Too many SQL statements (work rolled back) will occur. The reason for that error is a kernel bug that the internal command counter within the database kernel will overflow. But the precompiler should avoid running into this bug by changing its behaviour for sending the command "SET ISOLATION LEVEL". Preconditions and circumstances The error occures if a lot of "SET ISOLATION LEVEL" commands will be send in the same session. Probability that the error occurs Applications that sends a lot of "SET ISOLATION LEVEL" commands via the precompiler interface can run into this error with a high probability. Workaround none, an update of the precompiler runtime or a newer kernel (>= 7.3.00 Build 33) will be needed. Further documentation none PTS: 1120414 since: 7.3.00.43 Fixed Problem: Error messages in diagnostic files diagnostic file: precompiler trace Error message: no error message, have a look to the insert value of the float column and compare it with the original value Appearance (short description of the problem and how it can be realized) A rounding error occurs converting double values to kernel float columns. For example the number 81 will be converted into 80.999999999999999. Preconditions and circumstances A lot of double values (for example 8.1e+01) will be badly rounded by converting them into a VDN number. Unfortunately this is the reason for that a comparsion of the inserted double values and the original double values will fail. Probability that the error occurs A complete list of affected numbers cannot be given, but a lot of numbers without values after the decimal point are affected. Workaround Avoid using float columns as key Further documentation In general the precision of a double value conversion into a VDN-number is guaranteed only for the first 15 numbers of the mantissa. The 16th number of the mantissa will be rounded. So it's always not a good idea using float columns as key columns JDBC: ===== PTS: 1126777 since: 7.3.00.47 Fixed Problem: appearance: Content of long column is corrupted after executing an insert or an update if more than one long column will be inserted and the first long column is of type long unicode and the second long column is of type long byte. Preconditions and circumstances: more than one long column within a statement Workaround: none Solution: new JDBC driver is needed PTS: 1126653 since: 7.3.00.47 Fixed Problem: Appearance: Selecting strings from VARCHAR columns that contain only a few characters uses an unexpected high amount of memory in the Java Virtual Machine. Preconditions and circumstances: For any VARCHAR(n) column in a result set, a getString() returns a string instance having an internal buffer with n chars. A lot of space is thus waisted if the string is kept. Workaround: Use 'new String(getString(colindex))' in places where appropriate (check for NULL values if necessary/applicable). Solution: Iternally a new String instance is created in case of trimming, which results in the use of a shorter buffer by the JVM. (The larger buffer is then garbage-collected). PTS: 1126510 since: 7.3.00.47 Fixed Problem: Appearance: ResultSet.getDouble() returns inexact values (e.g. 5.22500000000005 instead of 5.225). Preconditions and circumstances: The data type must be a FLOAT or a FIXED having less than 19 digits. Workaround: Use at least a FLOAT(20) for floating-point numbers in the data definition. Solution: A wrong old conversion method was used. PTS: 1125447 since: 7.3.00.47 Fixed Problem: Appearance: Using IBM JDK 1.3.1 Win32 build cn131-20021107, a ClassDefNotFoundError is thrown when trying to use the XA Connection or the Pooled Connection. Preconditions and circumstances: Using IBM JDK 1.3.1 Win32 build cn131-20021107, a ClassDefNotFoundError is thrown when trying to use the XA Connection or the Pooled Connection. Workaround: None. A software update is necessary. Solution: The wrapper method for hiding JDBC 3.0 features (java.sql.Savepoint) was added for the rollback and releaseSavepoint methods of the connection wrapper of the XA/pooled connection implementation. PTS: 1125089 since: 7.3.00.45 Fixed Problem: Appearance: When selecting negative FIXED values that are shorter than 19 digits, an exception may be raised that the conversion is impossible. Preconditions and circumstances: The data value must have less significant (not equal to 0) digits after the decimal point, than the precision of the FIXED data type that was defined, i.e. the number must end in a '0', and have a precision greater than 0. Workaround: None, a software update is necessary. PTS: 1123770 since: 7.3.00.43 Fixed Problem: Error messages in diagnostic files: diagnostic file: none Error message: -709 Appearance: Reconnect fails with error -709 Preconditions and circumstances The reconnect within the JDBC driver fails if the xserver uses a different port than the standard port 7210. Probability that the error occurs Always if the xserver uses a other than the default port number. Workaround none, update of the JDBC driver needed. Further documentation none PTS: 1120133 since: 7.3.00.43 Fixed Problem: An exception - type ArithmeticException - occurs, if the method getBigDecimal(int Column) tries to read from a column of type float which contains a value lower than 1E-38 or bigger than 1E+38. This bug was fixed. ODBC: ===== PTS: 1127862 since: 7.3.00.47 Fixed Problem: 1) Preconditions and circumstances The ODBC-driver can crash due to a memory leak if connect handles are often reused for SQLConnect/SQLDisconnect. 2) Solution to the problem Install a new ODBC-driver (libsqlod[w].[a|so]) 3) Probability that the error occurs Applications which reuse ODBC connect handles can suffer from this problem. Applications which have only a fixed number of connections are not concerned. 4) Workaround Actually there are two leaks. The bigger one can be avoided if a connect handle is not reused but freed (SQLFreeHandle). PTS: 1125844 since: 7.3.00.47 Fixed Problem: appearance: If packet encoding UCS2 is used, the SQLGetData() function may return invalid long data. Preconditions and circumstances: Use of UCS2 packet encoding. Workaround: None. Solution: Use new ODBC lib. PTS: 1124459 since: 7.3.00.47 Fixed Problem: 1) Preconditions and circumstances The ODBC driver crashes (e.g. under Solaris 5.6). The crash happens within SQLAllocHandle. 2) Solution to the problem Install a new ODBC-driver (libsqlod.[a|so]) 3) Probability that the error occurs Other systems than Solaris 5.6 do not seem to suffer from this bug. 4) Workaround none PTS: 1125081 since: 7.3.00.45 Fixed Problem: 1) Preconditions and circumstances After a session timeout reparsing a statement results in an error. E.g. in sqlmode oracle an error can occur by execution of a prepared statement. 2) Solution to the problem Install a new ODBC-driver (sqlod32.dll, libsqlod.[a|so]) 3) Probability that the error occurs Only if another sqlmode than internal is used and a timeout happened between preparing and execution of a statement. 4) Workaround increase session timeout PTS: 1122823 since: 7.3.00.43 Fixed Problem: 1) Preconditions and circumstances Using ADO-upatable resultsets it is not possible to update to a NULL value 2) Solution to the problem Install a new ODBC-driver (sqlod32[w].dll, libsqlod.[a|so]) 3) Probability that the error occurs only if NULL values are processed 4) Workaround none Interface Runtime: ================== PTS: 1126716 since: 7.3.00.47 Fixed Problem: Appearance: The loader hangs when extracting into data files that are encoded in UTF8. Preconditions and circumstances: The code specifier of the output data stream has to be UTF8. There must be some character in the data that is represented by more than one byte in UTF8 encoding. Workaround: None. A software update is necessary. Solution: An internal routine copied as much data as possible and did not check for the boundaries of characters in UTF8 and UCS2 encoding, leading to incomplete characters copied. This was corrected. DBMClient: ========== PTS: 1123848 since: 7.3.00.43 New Feature: All features and patches from higher releases now also in this release available. DBMGUI: ======= PTS: 1127724 since: 7.3.00.47 Fixed Problem: Appearance: DBM Server crashes during recover_replace. Preconditions and circumstances: No recover was running before or a previous running restore was already finished completely at the time the recover_replace is called. Workaround: Do not call recover_replace without an unfinished restore. Solution: Use this patch. DBMServer: ========== PTS: 1127873 since: 7.3.00.47 Fixed Problem: Appearance: backup_cancel and backup_ignore repeat the answer of the previous backup_start or backup_replace command and the external backup log and the external backup protocol files contain partially duplicated output of the previous backup_start or backup_replace. Preconditions and circumstances: An external backup tool was used during the previous backup_start or backup_replace. Workaround: Ignore the unexpected command output and the unexpected output in the files external backup log (dbm.ebl) and external backup protocol (dbm.ebp). Solution: Use this patch. PTS: 1127767 since: 7.3.00.47 New Feature: Feature description: Faster end of backup and end of recovery detection for backups and recoveries using external backup tools. PTS: 1127426 since: 7.3.00.47 Fixed Problem: appearance: The DBMServer answers a recover_ignore with the Return Code -8020 and the Recovery Wizard of DBMGUI can not finish a restore after a reinitialization of a database successfully. Preconditions and circumstances: An external backup tool was used during the previous restore. Workaround: Ignore the unexpected -8020 and kill the Recovery Wizard if necessary. Solution: Use this patch. PTS: 1127304 since: 7.3.00.47 Fixed Problem: appearance: The backup history can not be opened with DBMCLI or viewed in DBMGUI. Preconditions and circumstances: No backup of the database was ever created. Workaround: Make a backup of the database Solution: Use this patch. PTS: 1127300 since: 7.3.00.47 New Feature: Feature description: The DBMServer command "db_cons" allows now full access to the "x_cons" tool including the up to now not available subcommand "show". The DBMServer command show allows now only access to these subcommands which the DBMServer returns on the show_list command. PTS: 1127161 since: 7.3.00.47 Fixed Problem: Appearance: Crash of the Backint for SAP DB/MaxDB implementation supplied with SAP DB/MaxDB. Preconditions and circumstances: You tried to restore files with Backint for SAP DB/MaxDB. Workaround: Call Backint for Oracle instead of Backint for SAPDB/MaxDB. Solution: Use this patch. PTS: 1125442 since: 7.3.00.47 Fixed Problem: Appearance: Message "Did not find any stage files." in dbm.ebp and dbm.ebl despite existing stage files in the staging area. Preconditions and circumstances: The database is running on a UNIX. Workaround: One could try to use very short names for the log backup files, e.g. just one character plus the automatically added version number. This workaround however depends on the alignment and the size of the dirent structure on the machine, therefore it depends on the used compiler and it may not work on all platforms. Solution: Install a patch containing this bug fix. PTS: 1125264 since: 7.3.00.47 Fixed Problem: appearance: The DBMServer command sql_recreateindex sends invalid SQL commands to the database instance. Another symptom is a crash if the DBMServer (dbmsrv executable) while executing sql_recreateindex. Preconditions and circumstances: The database instance works in unicode mode and sql_recreateindex was called with a index specification. Workaround: Use drop index and create index via native SQL. Solution: This patch solves the problem. PTS: 1125059 since: 7.3.00.47 Fixed Problem: Appearance: Error "-4 received a garbled packet." during archive_stage_repeat. Preconditions and circumstances: The command archive_stage_repeat is called without any prior archive_stage. Workaround: Always use archive_stage_repeat only after a archive_stage in the same DBMServer session. PTS: 1110339 since: 7.3.00.47 New Feature: 1) Description The return code of a backup in the backup history does now also take the results of a used external backup tool into account. That means, if a backup was successfully finished by the database kernel and the external backup tool failed after that, the DBMServer return code representing a failed backup tool will be shown as return code of the backup by the backup_history_* commands of the DBMServer. 2) Advantages The column RESULT of the backup history in the DBMGUI does no longer represent only the success of a backup from the database kernels point of view. 3) Disadvantages The content of the file dbm.knl may not longer be representing the backup history shown by DBMCLI and DBMGUI, if external backup tools were used. 4) Further documentation None PTS: 1125295 since: 7.3.00.45 New Feature: With new security behavior of our software a database instance checks always its upc file on startup. The special service instance had not have a upc file up to now. This feature implements the creation of a upc file for the service instance during the DBMServer command inst_reg. The database manager operator of a service instance is always service,service. The existence of a upc file allows now also a remote access directly to the service instance. PTS: 1123190 since: 7.3.00.43 New Feature: 1) Feature description New parameter "-inverted" for the DBMServer function backup_history_list. If used, the backup history is listed in reversed order, latest backup listed first. 2) Advantages and disadvantages of the feature. What has to be considered, if the feature is used? The interesting part of the backup history is listed first. No disadvantages known. 3) Further documentation None PTS: 1122434 since: 7.3.00.43 Fixed Problem: The log filling level is not shown correctly. The 100% value cannot be reached. The behaviour is corrected with this patch. PTS: 1122403 since: 7.3.00.43 New Feature: Problem Description The database configuration does not require a value for the confirguration parameter INSTANCE_TYPE. Most SAP DB components and applications assume in this case the INSTANCE_TYPE OLTP. But some components and application would not work properly without INSTANCE_TYPE. Also the values BW and CS will cause some trouble. A BW or CS configuration has no other dieferences to a OLTP configuration. Solution After a upgrade to this SAP DB version a empty INSTANCE_TYPE or a INSTANCE_TYPE with the values CS or BW will automaticly changed to OLTP. PTS: 1122211 since: 7.3.00.43 New Feature: 1) Description The new DBMServer Command autorecover allows the automatic recovery of a database if the backup history is available. 2) Advantages and disadvantages of the feature. The backup history must be available and the recover strategy choosen by the DBMServer must be feasibly without any manual media change (e.g. without a change of a tape). Otherwise the recovery will fail. 3) Further documentation Will be documented in the next version of "Database Manager CLI: SAP DB 7.4" PTS: 1121365 since: 7.3.00.43 Fixed Problem: 1) Category: backup 2) Error messages in diagnostic files: none 3) Appearance (short description of the problem and how it can be realized): A database backup with NetWorker and a file system backup with NetWorker happen at the same time. The file system backup backs up a part the database backup pipe and destroys the database backup. 4) Preconditions and circumstances: NetWorker is used under UNIX 5) Probability that the error occurs: 100% 6) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?) Avoid file system backups during backups of the database or exclude the pipe directory from file system backups. 7) Further documentation None PTS: 1120180 since: 7.3.00.43 Fixed Problem: 1) Category: Backup 2) Error messages in diagnostic files: none 3) Appearance (short description of the problem and how it can be realized): A parameter to a backup function is enclosed in double quotes. The resulting behaviour is undefined. 4) Preconditions and circumstances: A parameter to a backup function is enclosed in double quotes. 5) Probability that the error occurs: Very low, not seen in real life so far. 6) Workaround (What can I do or what have I to do, if I use an older version and the problem occurred?): Avoid the double quoted parameters to backup functions if possible, e.g. rename backup medium 7) Further documentation: None PTS: 1120176 since: 7.3.00.43 New Feature: Feature In case of reinstall util_activate is now available without sysdba. It will use the current sysdba from the upc file. PTS: 1111132 since: 7.3.00.43 New Feature: 1) Feature description: If the DBMServer command backup_history_open is called without -e and backup_history_list with -e, the External Backup ID's are now displayed. Thier availability status however is marked as UNKNOWN. 2) Advantages and disadvantages of the feature. What has to be considered, if the feature is used? Nothing 3) Further documentation None Loader: ======= PTS: 1126498 since: 7.3.00.47 Fixed Problem: appearance: Replication Manager may crash running TABLELOAD TABLE command if the table to load does not exist and is created by Replication Manager and that table has columns with user defined default values. PTS: 1124605 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATALOAD command: Running a command like DATALOAD TABLE tab col1 1-10 DEFAULT NULL col2 12-20 INFILE '' FORMATTED NULL ' ' with blanks as NULL representation the Replication Manager could stop processing with the following error message: // M Error at record in infile. // E -25302: This value is not a valid number: PTS: 1124537 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATALOAD command: Replication Manager crashed if DATALOADing data into keyed table with LONG columns in case the data to insert contains duplicate keys and MAXERRORCOUNT was set to a value > 1. PTS: 1124407 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATALOAD command Running DATALOAD commands with data files in format RECORDS on a table that has LONG columns the Replication Manager would crash. PTS: 1124216 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATAEXTRACT FOR DATALOAD commands: DATAEXTRACTing FOR DATALOAD LONG values into numbered/single LONGFILEs failed if the data file format was FORMATTED and the long file name exceeded the length of 21 characters. Running the command DATAEXTRACT FOR DATALOAD TABLE testtab OUTFILE 'testtab.dat' LONGFILE longcol 'longfilename_longcol.dat######' Replication Manager stopped with the following error message where the given minimumlength corresponds to the long file name length: // E -25344: Incorrect field length for column 'LONGCOL', minimum length 30. PTS: 1124151 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATAEXTRACT command: DATAEXTRACTing a table with LONG values into numbered/single LONGFILEs the Replication Manager saved the LONG values of first table record to long file with wrong file name. The name still contains the placeholder #. Thus only ( - 1) numbered LONG files were created during extract. PTS: 1121822 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATALOAD and DATAUPDATE commands: Loading arbitrary constants with DATALOAD failed. Running the command DATALOAD TABLE 'HANS' INFILE the Replication Manager stopped processing with the following error message: // E -25317: Constant must be compatible with column type and length (column: ''). PTS: 1120767 since: 7.3.00.47 Fixed Problem: Fixed bug in processing DATALOAD command: Running DATALOAD TABLE 1 NULL IF POS 1 = '' INFILE '' the Replication Manager did not insert NULLs into even if the empty string was found in data file. The Replication Manger returned an error depending on the data type of the column to be filled expressing that the found values is invalid data for the column to be filled. PTS: 1122582 since: 7.3.00.43 Fixed Problem: Fixed bug in handling of free date/time/timestamp mask: Parsing free date/time/timestamp masks the RepMan did not check return values. Thus unexpected errors upon inserting respective date/time/timestamp values could have occured. Example: Running a command like DATALOAD TABLE tstest INSTREAM FILE '' TIMESTAMP 'YYYY.HH:MM:SS' with "1999.13:10:51" as content of the data file the RepMan would stop with the following error message: // E -25301: Invalid input for date or time column: 1999.13:10:51 The problem is that during parsing the mask the error message pointing that the date mask is incomplete was ignored by RepMan. PTS: 1122548 since: 7.3.00.43 Fixed Problem: Fixed bugs in processing DATAEXTRACT command: DATAEXTRACTing data to files with format FORMATTED BINARY the data could not be loaded again if the table extracted had numerical columns; error message upon loading: // E -25302: This value is not a valid number: Running DATAEXTRACT FOR DATALOAD ... OUTFILE FORMATTED BINARY the Replication Manager created the partially wrong DATALOAD command where it mixes binary and ascii format like this: DATALOAD TABLE
INSTREAM FILE '' FORMATTED BINARY ASCII SQLCLI: ======= PTS: 1117560 since: 7.3.00.47 Fixed Problem: appearance: xsql now can display timestamps. Furthermore, date and time are printed correctly. Preconditions and circumstances: select statement with date/time/timestamp columns Workaround: None. Solution: Use new xsql. WebAgent: ========= PTS: 1126044 since: 7.3.00.47 Fixed Problem: appearance: webagent73.ini contains wrong paths to library and other directories Preconditions and circumstances: Workaround: correct the paths manually Solution: apply the patch PTS: 1125778 since: 7.3.00.47 Fixed Problem: appearance: Using WebServer on DEC 64 Bit and HP 64 bit platformes Preconditions and circumstances: shared libraries could not be found Workaround: DEC: edit WebAgent73.ini that way that all paths to libraries containing .../lib/lib64/... are changed to .../lib/... HP: replace file extensions .so with .sl Solution: apply the patch Runtime Environment: ==================== PTS: 1127782 since: 7.3.00.47 Fixed Problem: appearance: the dbmcli produdes a garbled error message "DBM-Api Error -4"..., followed by non-ASCII characters, when the connection to the dbmsrv is broken. Preconditions and circumstances: the dbmsrv terminates unexpectedly Workaround: just ignore the non-ASCII characters Solution: initialize the character array used for the error message PTS: 1127566 since: 7.3.00.47 New Feature: Feature description: The message output was improved if a task awakes from a wrong event. PTS: 1127073 since: 7.3.00.47 Fixed Problem: appearance: kernel crash. Preconditions and circumstances: a huge amount of connects are made to the database in parallel Workaround: none Solution: There was a non-synchronized access to a global queue. This has been eliminated. PTS: 1125562 since: 7.3.00.47 Fixed Problem: appearance: During local connection attempt, the error Error -8888: SERVERDB not accessible, cannot create communication semaphore is shown. Preconditions and circumstances: The database name is not given in all uppercase letters and a local connection is attempted. Workaround: Use only UPPERCASE database names. Solution: An automatic uppercase mapping in the routines, that establish the connection. PTS: 1125477 since: 7.3.00.47 Fixed Problem: appearance: Database may chrash if the X_CONS command 'SHOW QUEUES' (also included in 'SHOW ALL') is excecuted. Preconditions and circumstances: This effect is enforced if load balancing is activated for the database. Workaround: No workaround available Solution: Update to version including this patch. PTS: 1120368 since: 7.3.00.47 Fixed Problem: 0) Releases UNIX only 1) Preconditions and circumstances A client program could abnormaly terminate while holding a communication segment lock. The cause for that abnormal termination can be i.e. a user abort via a signal. The kernel does not check if client is still alive while trying to acquire the communication lock. This leads to a endless loop, that locks not only the task that tries to communicate, but all tasks within that UKT. Typical stack backtrace shows the routines sql32_lock_comseg e75_release_connection 2) Probability that the error occurs very small... 3) Solution to the problem The kernel already uses a timer thread to check for died applications. The communication state is now checked if the lock cannot be acquiered and if the communication is already aborted, the lock is reinitialized. 4) Visibility high 5) Workaround None, you have to restart the kernel to release the locked tasks. PTS: 1124096 since: 7.3.00.46 Fixed Problem: SECURITY 1) Preconditions and circumstances This is a security fix. It protects against potential buffer overflow using a specialized 'intrusion' program, that could execute code an behalf of the owner of 'niserver' or 'x_server'. The possible attack position is inside common used code shared between all platforms. 2) Probability that the error occurs low (no such program was ever known off, but the code would allow to write it...). If such a program was written: 100% 3) Solution to the problem The copy routines is modified to check the string for being correctly terminated by a zero byte. If not the connection packet is rejected. 4) Visibility it depends on the action taken by the intruders coding... 5) Workaround none PTS: 1125119 since: 7.3.00.45 Fixed Problem: appearance: database instance is not able to remove client semphore from IPC directory us:dbname. The database cannot be started. To reenable start of database, the directory '/usr/spool/sql/ipc/us:dbname' and all its content must be removed. Preconditions and circumstances: A local communication using client application crashes or keeps connections open during database shutdown. This only happens if the user, that started the application is not owner of the database and is using a local shared memory communication. Workaround: Do not use local communication, if you are not owner of the database. PTS: 1124851 since: 7.3.00.45 Fixed Problem: Appearence: x_cons show state always reports "offline" Preconditions and circumstances: x_cons is running as a different OS user as the database kernel Workaround: Run x_cons as the same user as the database kernel PTS: 1124591 since: 7.3.00.45 Fixed Problem: Appearence: Bringing a database from state online to state admin fails. The dbm reports an error message "database already started", but a state check gives state offline Preconditions and circumstances: May happen under unix only. When the dbm is told to bring a database from state online to state admin, it first stops the database, waits until it has reached state offline and then restarts it. The messages occured because the dbm incorrectly regarded the database as already offline while the watchdog process was still busy removing the ipc resources. The dbm - attempting to restart the database - also tried to remove the ipc resources. Workaround: As this is a timing problem, it does not occur always. To completely avoid it: If the database is in state online, bring it to state offline first by using the dbm command "db_offline" before bringing it to state admin. PTS: 1123446 since: 7.3.00.43 Fixed Problem: when kernel crashed on a unix system without removing the ipc resources, the console command show state still reported state admin or online, while the dbmcli command db_state reported offline. Now the console command show state also reports offline. PTS: 1123419 since: 7.3.00.43 Fixed Problem: Reading UNICODE files encoded (UCS2), the loader sometimes produced an error message like "Error during execution -->-25302 This value is not a valid number: 0" This happened because of an incorrect cr/lf handling. PTS: 1123162 since: 7.3.00.43 Fixed Problem: 0) Releases All 1) Preconditions and circumstances A task statistic is requested. The result is ok, but the entry for task detail receive reply time is incorrect. This leads to unexpected results in the calculated time needed for OMS call. 2) Probability that the error occurs 100% 3) Solution to the problem The correct value is set. 4) Visibility high 5) Workaround none PTS: 1123046 since: 7.3.00.43 Fixed Problem: Because of the limitation of the server string to 64 bytes it is not possible to connect to a database with an "NI Connect String" which is often longer than 64 bytes. This limitation was installed unintended to Version 7.4.2.21. As a result the application gets the following error: "server node name too long" This limitation was removed again. PTS: 1122912 since: 7.3.00.43 Fixed Problem: Under some circumstances (no kernel process running but ipc tag files and parts of ipc resources still existing), the dbmcli command db_state returned incorrect results instead of "OFFLINE". This has been fixed by checking if the processes mentioned in the pid files are alive PTS: 1122575 since: 7.3.00.43 Fixed Problem: SAPDB_sprintf did not process negative floating point values correctly. Either the result string contained a random character instead of the minus sign or it was empty. It seems that negative floating point values are not used in SAPDB, as this error occurred only during internal testing. Nevertheless, it was fixed. PTS: 1122426 since: 7.3.00.43 Fixed Problem: If a client application such as SQL Studio connects with a server nodename longer than 64 Bytes the application crushes with an access violation. Correction: Connects with nodenames longer than 64 Bytes are not supported . The client application gets the error message 'server node name to long'. PTS: 1122046 since: 7.3.00.43 Fixed Problem: In certain cases, the dbm command "recover config" deleted a parameter file just written. XSERVER: ======== PTS: 1125787 since: 7.3.00.47 Fixed Problem: appearance: During software update DBMGUI/dbmcli is able to connect from a remote host. Since it can happen in any state of update process the behavour is completely undefined. One appearance is the update process fails since dbmsrv is busy. Preconditions and circumstances: x_server is running Workaround: Only by policy: Do not try to use software while it is updating. Do not connect a DBMGUI/dbmcli while update process is running. Solution: The x_server checks if the installation is registered. Since the software update first deregisters the installation, no futher dbmsrv connection will be establishable. PTS: 1124305 since: 7.3.00.47 Fixed Problem: 0) Releases UNIX only 1) Preconditions and circumstances Each user gets a umask during login. If the umask of the user, that starts the x_server is set to 022, the group write access to the x_server logger pipe and the update pipe is user only. Another user may stop the x_server, but cannot start it again even if in the same group. 2) Probability that the error occurs 50% 3) Solution to the problem The umask is internally set to 007 now, prohibiting only world access. 4) Visibility high 5) Workaround Start the x_server after check you umask. Set umask to 002 before starting x_server.