List of changes for portingset: 9.0c Eyck: # 67299 (BDNT61187): Cannot log in to BW. Date: Wed, 14 Oct 2015 15:04:39 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Misleading error message from BW when environment var �PACKAGE_COMP� is unknown. Test Procedure Start BW with commandbox seting: "-- -set PACKAGE_COMP=unknown" Motive source TCS:800-205146 Eyck: # 67216 (BDUX61388): SQL: Crash on query with aggregate on indexed array column and prepared set Date: Thu, 08 Oct 2015 11:27:18 +0200 Created on: Eyck Type: bugfix Problem Description (Customer terms) The SQL processor may crash if a SELECT statement is executed that meets the following conditions: - aggregate on array indexing expression in the SELECT clause - grouping column in the SELECT clause - AS PREPARED SET clause - the result row set contains more than 71 rows This problem is introduced with porting set 9.0b.01. Workaround Set BAAN_SQL_CACHEROWS to a value that is at least the number of rows returned by the SELECT statement. The default value is 71. Test Procedure Run the Print Reconciliation Data session. Or, execute a SELECT statement that meets all conditions stated above. Affected Executables all database drivers Motive source TCS:800-205963 Eyck: # 66588 (BDUX60533): installer: do not automatically enable row versioning Date: Mon, 03 Aug 2015 13:09:17 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Full installs using the 9.0b porting set automatically set the bdb_use_row_version:1 resource. This resource influences the delayed locking mechanism. Older application versions (before LN 10.4) make wrong assumptions about the layout of the record buffers, causing problems in combination with row versioning, DBCM or record timestamps. As row versioning is enabled for all tables, it is much more sensitive to application bugs than the other features. To avoid problems, the 9.0b.01 porting set will not automatically set bdb_use_row_version:1 anymore. At a later point in time we will enable row versioning for LN 10.4 and higher again. Workaround For full installs using the 9.0b porting set that install application versions up to LN 10.3.x 1. Install the porting set only. 2. Modify $BSE/lib/default/db_resource file: Disable/delete bdb_use_row_version resource. 3. Continue the installation of the Tools & Apps Test Procedure full install and verify that $BSE/lib/defaults/db_resource does not contain bdb_use_row_version:1, except for EDB. Affected Executables installer Eyck: # 66532 (BDUX60466): Bshell: Crash on subquery in SELECT clause returning NULL values Date: Tue, 28 Jul 2015 16:15:22 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) If the SELECT clause of a SELECT statement contains a subquery, and the subquery results in a NULL value on a string column, then the bshell may crash. Test Procedure Write a small 3GL program with a query such as the following. Verify that it runs without problems: function main() { string max_s(20) select ( select max(strcol) from table where 1=0 ):max_s from table selectdo endselect } The program should return empty string in the variable max_s. Affected Executables bshell Eyck: # 66497 (BDUX60443): Oracle 12.1.0.2: create index with advanced compression gives unexpected error Date: Mon, 27 Jul 2015 14:28:21 +0200 Created on: Eyck Type: bugfix Problem Description (Customer terms) Oracle 12.1.0.2 with index compression gives ORA-25195 (bdberrno 26195) on MLE shadow tables. Test Procedure Regression tests on Oracle 12.1.0.2 or later Affected Executables ora_srv Eyck: # 66439 (BDUX60210): Sensitivity Label Not Working for Specific Company. Date: Tue, 21 Jul 2015 15:13:49 +0200 Created on: Eyck Type: bugfix Problem Description (Customer terms) Sensitivity labeling not working for extended company numbers. Workaround N/A Test Procedure ed test script "chk_extended_comp_sensitivity.test" Affected Executables Bshell Motive source InforXtreme:506510 Eyck: # 66355 (BDUX60135): D508448: Running Create Tables for a large range of companies takes hours (and get slower and slower) Date: Thu, 09 Jul 2015 15:51:16 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Running Create Tables or Check Tables for a large range of companies takes hours, and it becomes dramatically slower. Workaround Only check a few companies at a time, and restart the bshell after each check. Alternatively, set up a few batch jobs for this task. Each job must be handled by a fresh bshell. Test Procedure Run the Create Tables and Check Tables sessions for a large number of companies. Observe that the processes keep their pace. Affected Executables bshell all database drivers Motive source InforXtreme:508448 Eyck: # 66345 (BDUX60080): Change Bshell trace destination directory in multi-tenant cloud Date: Thu, 09 Jul 2015 07:49:00 +0200 Created on: Eyck Type: bugfix Problem Description (Customer terms) bshell trace files in tenant mode should appear in $BSE/log and not in $BSE/tmp any more Also hostnames should not appear when %h is specified Affected Executables bshell6.2 Motive source JIRA:LND2-4151 JIRA:LND2-4554 Eyck: # 66314 (BDUX60081): Made combo-driver buffer dynamic Date: Fri, 03 Jul 2015 14:02:50 +0200 Created on: Elgar Type: porting specific change Problem Description (Customer terms) Combo driver raises: Buffer overflow in combined Bshell/driver Workaround use db.flush() or db.commit() more often. The db.flush() does not affect the transaction but just pushes the transaction buffer from the client (bshell) to the database driver and results in a fresh/cleaned up buffer. Test Procedure Transactions in the combo driver are now not limited to a fixed size (1024*4kB) but to the system imposed (memory allocation) limits. Affected Executables bshell and all other database clients. Eyck: # 66285 (BDNT60137): manual merge of BDNT60045, string compare in unicode Date: Wed, 01 Jul 2015 10:35:31 +0200 Created on: Eyck Type: bugfix Problem Description (Customer terms) Compare Issue wth string variables. When doing a compare of 2 strings: string1 < string2 and the stings have values like 01E020268 and 01 then the result is other then expected. when setting a trim function around the strings it's working fine. Workaround set a trim around the string, or declare these as fixed. Test Procedure test with below kind of script. #string compare not working CONFIG include unicode.config /CONFIG BAAN3GL function main() { long ret, ret2 string strabc(3) string strab(3) strabc = "23a" strab = "23" ret = 2 if strabc < strab then ret = 0 endif if trim$(strabc) < trim$(strab) then ret = 1 endif ASSERTSEQ(ret, 2) } /BAAN3GL Affected Executables bshell Motive source InforXtreme:499092 Eyck: # 66235 (BDUX60077): D508448: Running Create Tables for a large range of companies takes hours Date: Fri, 26 Jun 2015 15:30:23 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Using the session Create Tables to create all tables in a number of companies takes too much time, and the process gets slower and slower. The effect is observable from the 2nd company. When more than 10 companies are processed, it becomes evident. Test Procedure Use the Create Tables session to create all tables in a number of companies. The process should keep going at more or less the same rate. Affected Executables All database drivers Motive source DF:508448 Eyck: # 66217 (BDUX59908): bshcmd does not work correctly with combo driver Date: Thu, 25 Jun 2015 13:45:53 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) bshcmd doesn't work on combo drivers Affected Executables bshell, db drivers, bshcmd Motive source JIRA:LND2-3254 Eyck: # 66181 (BDUX59996): Installer: Installation of BaanIV/Corelli fails (row versioning is not supported) Date: Fri, 19 Jun 2015 15:17:57 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) The installation of BaanIV and Corelli fails with the 9.0b porting set. During the installation the following resource is set in the $BSE/lib/defaults/db_resource file: bdb_use_row_version:1 The IVc and Corelli Tools do not support row versioning. Workaround The following work-around can be used: * install the porting set only. * remove the "bdb_use_row_version:1" line from the db_resource filel. * continue the installation. Test Procedure Install IVc or Corelli. The installation should succeed. Verify that the $BSE/lib/defaults/db_resource file does *not* have the following line: bdb_use_row_version:1 Install LN and verify that the $BSE/lib/defaults/db_resource file contains the line above. Affected Executables ora8_adm db2v5_adm msql_adm Eyck: # 66077 (BDUX59767): SQL: SELECT MAX( ) gives bad performance Date: Fri, 12 Jun 2015 09:53:09 +0200 Created on: Elgar Type: enhancement Problem Description (Customer terms) A SQL statement that contains a set function specification (aggregate) on an element of an array column is not handled by the database. The database driver evaluates the grouping, which may result in a severe performance penalty. Test Procedure Set DBSLOG=400 and use bsql to execute a query as the following: select max(phoneno(1)) from dbtst120 Observe that the statement sent to the database contains the MAX() expression. Affected Executables All database drivers Eyck: # 65959 (BDUX59738): handle.report.pool.string.scan returns incorrect field count Date: Wed, 03 Jun 2015 15:20:25 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Message: Error in sort nr fields scanned ... expected ... Affected Executables bshell6.2 Motive source TCS:800-204392 Eyck: # 65929 (BDNT59748): BaanIV username cannot contain high ascii chars anymore. Date: Tue, 02 Jun 2015 14:53:52 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Convergence problem. BaanIV username cannot contain high ascii chars anymore. Workaround N/A Test Procedure Create username that contains a high ascii char. Motive source InforXtreme:485452 Eyck: # 65596 (BDNT59391): Repgen generate wrong 3GL code Date: Fri, 01 May 2015 14:16:37 +0200 Created on: Elgar Type: bugfix Problem Description (Customer terms) Reports complain: Error in reading sort file record: 1 fields scanned, xxyyzz expected Affected Executables repgen6.2 Motive source TCS:800-203891 Eyck: # 65535 (BDUX59267): Adding CDFs to input fields and remove report input field limit Date: Fri, 24 Apr 2015 15:40:24 +0200 Created on: Elgar Type: enhancement Problem Description (Customer terms) CDF fields cannot be added to a report without recompiling the report. Affected Executables bshell6.2 repgen6.2 Motive source JIRA:LND2-3936 JIDA:LND2-1156 Total number of changIDs displayed: 20