List of changes for portingset: 8.3a.01 MaintCage: # 33197 (BDNT25269): Graphics Server problem in BW Date: Tue, 14 Nov 2006 12:25:53 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Sessions like cprmp2701m000, cprmp3701m000 and cprrp0731m000 create charts and are using files from the graphics server (3rd party software). However, regularly cases have been logged, in the past and still now, that an error message is given related to the Graphics Server, usually like: "Failed to open Graphics Server" and/or "Create window failed for widget "DsCgraph" of widget class "TsGraphWidgetClassRec"" Workaround Make sure c:\winnt\baan\bin is in the PATH environment variable. Test Procedure See problem description. Start the mentioned session with a PATH variable withoud the c:\winnt\baan\bin directorry. Start the session from Worktop. Affected Executables bw.exe Motive source SDIS:ERP-00000-12499 MaintCage: # 33189 (BDUX25277): Fix problem in bclm.getproductidfromobject Date: Mon, 13 Nov 2006 16:49:09 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) both bclm.getproductidfromobject and bic_info cannot handle full pathnames to determine product id based on secu files Test Procedure bic_info6.2 -S ottaad2500 and bic_info6.2 -S `explode6.2 ottaad2500` should return the same product id. Affected Executables bshell6.2 bic_info6.2 MaintCage: # 33180 (BDUX25088): Errno 32 (Broken pipe) bdb_errno 0 Date: Mon, 13 Nov 2006 11:29:39 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Error when session has no authority for table Workaround N/A Test Procedure Tested the database server with 3GL script function main() { select whinh310.rcno from whinh310, tccom100, tcmcs003 where whinh310._index1 = {:whinh312.rcno} and whinh310.cwar refers to tcmcs003 path whwmd200.cwar as set with 1 rows selectdo endselect } Motive source SDIS:TECH-00000-01536 MaintCage: # 33110 (BDNT24746): Could not login on w2k3 server with SSPI authentication Date: Mon, 6 Nov 2006 15:36:59 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) SSPI logon did not work anymore from remote system since 8.3a Test Procedure Try to logon to baan from remote system to baan server, using SSPI protocol (see BW configuration). Affected Executables all client binaries using SSPI protocol, mainly BW. MaintCage: # 33107 (BDUX25138): SQL: Better native support for Informix IDS Date: Mon, 6 Nov 2006 15:12:32 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) The SQL processor does not fully exploit the functionality offered by the underlying database. Especially when it is used for the Cognos/ODBC solution, then performance is far from optimal, if one of the following constructions is used: - general expressions in the SELECT clause - derived tables (a.k.a. "inline views" or "subselects") - full support of left and right outer joins - simple or searched case function (in a filter) - trim function (in a filter) - cast specification - coalesce - extract Performance would improve dramatically when the capabilities of the underlying database were used to support these constructions. This is what is implemented in this project. Note: optimizations already applied when using the Cognos/ODBC solution and when the underlying database is Oracle, Microsoft SQL server, DB2 UDB or MySQL. Now these optimisation also apply for Informix IDS (with the ODBC solution). Test Procedure Execute a query with any of the constructions mentioned above. Either use the Cognos/ODBC solution or add the -p16 flag to bsql6.2. Set DBSLOG=01570 and observe that the construction is pushed to the database. For example, executing the following query: bsql6.2 -p16 -q "select salary + bonus from ( select * from dbtst120 ) dt" results in the following query on Oracle: SELECT (t0.t$salary+t0.t$bonus) FROM b61a.tdbtst120000 t0 (Note that the optimizer of the SQL processor eliminated the redundant derived table.) Note that certain constructions simply cannot be pushed to the database, because the database does not support them. For instance, MSQL does not support the TRIM function with any character other than a space. Affected Executables bsql jbdb inf_srv6.2 MaintCage: # 33086 (BDNT25116): reconfigured parameters not used by Informix database Date: Fri, 3 Nov 2006 13:34:32 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Baan installation takes very long (days) on Windows systems when installation wizard is used. Workaround - manual database instance setup - install application Test Procedure do Baan installation in one step (portingset and application) Affected Executables inf_adm MaintCage: # 33044 (BDUX24986): SQL: Informix, MSQL and MySQL sort NULLs before any other data (wrong result for UNION with ORDER BY) Date: Tue, 31 Oct 2006 10:41:14 +0100 (CET) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Informix, Microsoft and MySQL sort NULL values before any other data. If a query contains a UNION and an ORDER BY that sorts NULL values as well as 'normal' data, then the result of the query could be incorrect. Test Procedure With a debugable database driver, set the environment variable BAAN_SQL_NO_UNION_OPTIM=1 and execute the following query: select a.empno, b.firstnme as str from dbtst190 a left join dbtst120 b on a.empno = b.empno where a.empno in ( 10, 100, 100000 ) union select a.empno, b.projno as str from dbtst190 a left join dbtst180 b on a.empno = b.empno where a.empno in ( 50, 100, 100000 ) order by str, empno (Note that some rows in dbtst190 have no match in dbtst120 and dbtst180, so NULLs are generated) Observe that no duplicate rows are returned. Affected Executables bshell bsql all database drivers MaintCage: # 32998 (BDNT25077): Not able to user BwPrint as user Administrator Date: Thu, 26 Oct 2006 10:51:34 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) BwPrint cannot be started as user Administrator due to an extra check on long usernames. When the username is longer than 8 characters an application event is logged and the application will not start. Workaround Use a username with a maximum of 8 characters Test Procedure Right click on bwprint.exe. Choose 'Run as...'. Choose for user Administrator and enter the correct password. When BwPrint does not start look in the eventviewer and check the events for bwprint. Affected Executables BwPrint.exe Motive source SDIS:TECH-00000-01583 MaintCage: # 32991 (BDUX25090): utc.add error when DST border is crossed Date: Wed, 25 Oct 2006 13:52:48 +0200 (CEST) Created on: DevChopin Type: bugfix Problem Description (Customer terms) Hours can not be registered in bptmm1120m000. Test Procedure function main () { long ret_val long today today = date.to.utc(2006, 10, 23, 8, 0, 0) ret_val = utc.add( today, 0, 0, 7, 0, 0, 0, today) } Affected Executables bshell Motive source TCS:800-155185 MaintCage: # 32947 (BDNT25049): Baanman not running with Administrator account Date: Mon, 23 Oct 2006 11:49:55 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Because of a new check on username (max length 8 characters) baanman does not run anymore when user is 'Administrator'. Workaround Run as Baan user, not as administrator Test Procedure Start baanman.msc, which uses baanman.dll. Use 'Run as....' to choose user 'Administrator'. The SSE ES Service Manager should start. Affected Executables baanman.dll Motive source SDIS:TECH-00000-01517 MaintCage: # 32943 (BDUX25047): JVMI: missing dir in LD_LIBRARY_PATH Date: Mon, 23 Oct 2006 09:48:11 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) bshell hangs when JRE 1.3 is used on DEC/OSF Workaround add to $BSE/lib/bse_vars: LD_LIBRARY_PATH=/lib/alpha:/lib/alpha/classic:/lib/alpha/native_threads where is the directory of the installed JRE most times this is /usr/opt/java131 Test Procedure OW on DEC/OSF with JRE 1.3 Affected Executables bshell bjvmi.jar MaintCage: # 32816 (BDUX24911): new zoneinfo files Date: Fri, 13 Oct 2006 16:16:23 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The DST switch had been moved from 15 okt to 5 nov in Brazil Workaround change the files manualli or download the files. Then compile with the zic compiler (Fill this in) Test Procedure install portingset, check if new files are there, new rule for brazil for 2006 and 2007 Affected Executables zonerule files, Motive source SDIS:tech-00000-01519 MaintCage: # 32706 (BDUX24742): SQL: UPPER and LOWER implementation Date: Fri, 6 Oct 2006 15:33:24 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Added the UPPER and LOWER functions to the query language. Test Procedure sample query: select upper('abc') from dbtst120 where empno=10 this should return ABC MaintCage: # 32653 (BDNT24781): Drag and drop in edit box not correct Date: Thu, 5 Oct 2006 07:36:20 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Open a single-occ session. Select text in an edit field. Drag the selected text using the mouse to another edit field in a single-occ session. Now the dragged text is visually removed from the first edit field. However this change in the first field is not saved. Workaround Use copy/paste using the keyboard. Test Procedure See problem description. Affected Executables bw.exe Motive source SDIS:TECH-00000-01449 MaintCage: # 32631 (BDUX24674): Audit trail sometimes incomplete Date: Wed, 4 Oct 2006 10:07:35 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Audit trail sometimes incomplete when mixing delayed inserts with actions that explicitly request an error condition. Test Procedure .../tests/bshell_integration/audit/004 Affected Executables bshell Motive source TCS:800-154786 MaintCage: # 32601 (BDUX24743): JVMI: core dump within debug logging Date: Tue, 3 Oct 2006 12:00:13 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) bshell crashes on Solaris when JVMI logging is enabled with -dbgjvmi Test Procedure start tmboaserver 2.7 on Solaris with enabled logging Affected Executables bshell libjvm2bvm MaintCage: # 32582 (BDNT24728): SQL Support UNION Date: Fri, 29 Sep 2006 16:26:30 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Our SQL language did not support UNION; only UNION ALL. Workaround ? Test Procedure Run the test scripts in: \db\lib\sql\Test\tests\ansi92\union_distinct Affected Executables QP MaintCage: # 32572 (BDUX24709): Problem in sort with unicode Date: Fri, 29 Sep 2006 12:16:01 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Sorting of a BOM doesn't work Test Procedure cat <s1.u 10|1|1 |1 10|1|.2 |2 10|1|.2 |3 10|1|1 |4 10|1|1 |5 EOF sort6.2 -t'|' +0 -1 +1n -2 +3n -4 s1.u -o s1.snu should not change the file. Affected Executables sort6.2 Motive source SDIS:ERP-00000-10112 MaintCage: # 32571 (BDUX24672): SQL: disable new keywords (COALESCE, CHAR, INT, ...) in non-ANSI mode Date: Fri, 29 Sep 2006 12:15:37 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) The addition of new key words may give unwanted side effects for existing installations that perform a porting set upgrade. The following key words are now only available in ANSI mode (e.g. through the ODBC solution): - char - character - coalesce - day - extract - hour - int - integer - interval - minute - month - second - substring - varchar - varcharacter - year Consequently, certain SQL features are now available in ANSI mode only: - coalesce - extract - cast as char/character/int/varchar/varcharacter - substring - interval literals Workaround Use a different name for an alias that is now a keyword, or qualify the column name. For example: select int from dbtst107 may be rewritten as: select dbtst107.int from dbtst107 And select hiredate - birthdate as interval from dbtst120 may be rewritten as: select hiredate - birthdate as an_interval Test Procedure Execute the following command: bsql6.2 -c0 -q"select clan as int from ttaad110" This should work fine. Execute the following command: bsql6.2 -p16 -c0 -q"select clan as int from ttaad110" This should give the error: SqlState=42I00, 'Unexpected token 'int'', NativeError=302, Line=1 (The option -p16 switched the SQL parser to ANSI mode) In the same fashion, try some or all of the keywords listed above. Affected Executables bshell bsql MaintCage: # 32543 (BDUX24653): SQL implement EXTRACT Date: Thu, 28 Sep 2006 16:37:08 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Added the EXTRACT function to the SQL language. Syntax: EXTRACT( FROM ) datetimeField can be: YEAR, MONTH, DAY, HOUR, MINUTE or SECOND datetime expression can be a TIMESTAMP or a DATE The result is an INTEGER. Test Procedure bsql -p 16 -q "select extract(year from current_timestamp) from dual" Affected Executables jbdb, all db drivers MaintCage: # 32489 (BDUX24649): Blocking audit_srv when shared memory is full Date: Tue, 26 Sep 2006 16:08:35 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Audit_srv blocking when shared memory is full. Affected Executables audit_srv MaintCage: # 32477 (BDUX24634): SHM improved logging Date: Tue, 26 Sep 2006 10:31:20 +0200 (CEST) Created on: MaintCage Type: porting specific change Problem Description (Customer terms) Better error message if no SHM available. DevCage: # 32466 (BDUX24207): Blogind keeps file descriptors open after startup Date: Mon, 25 Sep 2006 16:48:24 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Blogin (and ASM) daemon on Unix does not close file descriptors stdin/out/err. This may cause problems to close the shell which started blogind. Problem was found on Linux. Test Procedure on Linux: - start a shell (as user root) - be sure that env. var USER is not set (unset USER) - as root: start blogind6.x - as root: run lsof | grep blogind -> check that file descriptors 0, 1, 2 have been mapped to /dev/null instead of stdin/err/out Affected Executables blogind/asm_srv Motive source SDIS:TECH-00000-00949 MaintCage: # 32462 (BDUX24623): QP: Error 201 on float values that are not according to diga Date: Mon, 25 Sep 2006 15:59:18 +0200 (CEST) Created on: MaintSchoenberg Type: bugfix Problem Description (Customer terms) When using the 8.2b porting set on Corelli applications, error 201 is given. The problem occurs due to FLOAT values in the database that are not according to the domain definition (in particular the "diga" constraint: the number of digits after the decimal point) Test Procedure A script like the following can be used to reproduce the problem: table tdbtst120 function set.up() { select * from dbtst120 for update where empno = 10 selectdo endselect dbtst120.bonus=46.316399 db.update(tdbtst120,db.retry) commit.transaction() } function tear.down() { select * from dbtst120 for update where empno = 10 selectdo endselect dbtst120.bonus=1000 db.update(tdbtst120,db.retry) commit.transaction() } function main() { set.up() select * from dbtst120 for update where empno = 10 selectdo endselect dbtst120.salary=100000 db.update(tdbtst120,db.retry) db.flush() tear.down() } Affected Executables bshell MaintCage: # 32445 (BDUX24607): suppress No Table error message in refint Date: Mon, 25 Sep 2006 11:03:35 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) I do get the following errors in log.aad4225 after reorganizing the tables. After installing ERPln with DB2 and portingset 7.6b.01 I find the following errors like. ttadv176050 R [0] SQLState QP999: Table does not exist (error 506) Workaround Ignore messages. Test Procedure reorganize tables Affected Executables refint Motive source TCS:800-149108 TCS:800-149271 TCS:800-152263 MaintCage: # 32437 (BDUX24555): SQL: Better native support for Db2 and MySQL Date: Mon, 25 Sep 2006 08:44:19 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) The SQL processor does not fully exploit the functionality offered by the underlying database. Especially when it is used for the Cognos/ODBC solution, then performance is far from optimal, if one of the following constructions is used: - general expressions in the SELECT clause - derived tables (a.k.a. "inline views" or "subselects") - full support of left and right outer joins - simple or searched case function (in a filter) - trim function (in a filter) - cast specification - coalesce Performance would improve dramatically when the capabilities of the underlying database were used to support these constructions. This is what is implemented in this project. Note: optimizations already applied when using the Cognos/ODBC solution and when the underlying database is Oracle, Microsoft SQL server. Now these optimisation also apply for DB2 UDB and for MySQL (with the ODBC solution). Test Procedure Execute a query with any of the constructions mentioned above. Either use the Cognos/ODBC solution or add the -p16 flag to bsql6.2. Set DBSLOG=01570 and observe that the construction is pushed to the database. For example, executing the following query: bsql6.2 -p16 -q "select salary + bonus from ( select * from dbtst120 ) dt" results in the following query on Oracle: SELECT (t0.t$salary+t0.t$bonus) FROM b61a.tdbtst120000 t0 (Note that the optimizer of the SQL processor eliminated the redundant derived table.) Note that certain constructions simply cannot be pushed to the database, because the database does not support them. For instance, MSQL does not support the TRIM function with any character other than a space. Affected Executables bsql jbdb db2v5_srv6.2 mysql_srv6.2 MaintCage: # 32434 (BDUX24591): AIX use default type for enum Date: Mon, 25 Sep 2006 08:36:08 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Unknown Server Mode was reported during ERP LN 6.1 installation on AIX. Workaround n/a Test Procedure install portingset on AIX. Affected Executables inf_adm6.x MaintCage: # 32410 (BDNT24585): MSQL Unicode: performance problem on type mismatch Date: Thu, 21 Sep 2006 16:34:40 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Unicode MSQL only: Performance problems SQLserver is using 100% cpu while the bshell/msq7_srv is doing almost nothing Test Procedure full install Affected Executables msql7_srv MaintCage: # 32408 (BDNT24583): SHM manager fails to start if username is 8 characters Date: Thu, 21 Sep 2006 16:24:15 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) SHM service on windows did not start if username length is exactly 8 characters. Username field of SHM properties becomes empty, if username of 8 characters is filled in. Workaround use shorter username as baan user under which SHM service runs on windows. Test Procedure 1. modify shm properties (via baan management snapin): fill in a user name of 8 characters 2. try to start SHM (assuming filled in user is a valid baan user). Affected Executables shmserv.exe/shmcfg.dll MaintCage: # 32396 (BDNT24487): SQL SUM() on intervals Date: Wed, 20 Sep 2006 15:57:16 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) The SQL processor did not support SUM(). E.g.: select sum(endtime-startime) from dbtst206 From now on this construct can be used in SQL. Test Procedure Execute a query like this one: select sum(endtime-startime) from dbtst206 Affected Executables QP MaintCage: # 32316 (BDUX24480): Unicode: PLEN not valid after function call Date: Fri, 15 Sep 2006 12:25:38 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Unicode: error 205 (generated by the database driver) on INSERT or UPDATE because strings are passed to the database driver that are longer than the defined column length. The problem popped up on the assignment of a longer MB domain to a shorter one in combination with return values of 3GL function calls. Test Procedure See demo source above. Without the fix, the ASSERTs on line 19 and line 21 fail. Affected Executables bshell Motive source SDIS:ERP-00000-10235 Inq:411840 MaintCage: # 32292 (BDNT24459): Long user names: better error message Date: Wed, 13 Sep 2006 17:06:05 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Installation wizard failed, when logged on with long user name (during installation on a Unix tyarget system) Workaround NA Test Procedure Run compress -? or bpack -? when logged on with long user name. No error should occur and no message in the eventviewer regarding the length of user name. Affected Executables bpack,compress,shm manager (last one is win32 specific) MaintCage: # 32281 (BDUX24450): Core dump in database drivers when started by bdbpost in an almost full shm context Date: Wed, 13 Sep 2006 13:37:03 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Database drivers crash when the shared memory is full. The SIGSEGV occurs in the function creat_hash_tbl() on a NULL pointer dereference. Affected Executables all database drivers Motive source TCS:800-154556 MaintCage: # 32269 (BDNT24437): Too strict checks when no real BSE is available. ERP installer stopped unexpected Date: Tue, 12 Sep 2006 15:59:58 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) Too strict length check (of 8 characters) on user names, causing the ERP installer to stop MaintCage: # 32260 (BDUX24432): SQL: searched CASE and COALESCE Date: Tue, 12 Sep 2006 11:39:49 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) The ERP LN SQL language lacks support for both the SEARCHED CASE and the COALESCE expression. Workaround -- Test Procedure Try, for example the following commands: bsql6.2 -q "select case when salary > 25000 then 'Fairly high' when salary > 15000 then 'Moderate' else 'Well...' end from dbtst120" Or, bsql6.2 -q "select coalesce( b.empno, a.empno ) from dbtst190 a left join dbtst120 b on a.empno = b.empno" Affected Executables bshell bsql jbdb library (ODBC) MaintCage: # 32228 (BDNT24386): MSQL Unicode: right truncation errors Date: Fri, 8 Sep 2006 14:26:00 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) MSQL Unicode mode only: Right truncation errors in the application event log Test Procedure full FP3 install Affected Executables msql_srv MaintCage: # 32177 (BDNT24360): Unicode: MSQL error 205 during reconfiguration Date: Wed, 6 Sep 2006 16:24:46 +0200 (CEST) Created on: MaintCage Type: bugfix Problem Description (Customer terms) MSQL Unicode only: error 205 during upgrade to ERP LN FP3 Test Procedure FP3 upgrade Affected Executables msql7_srv Motive source TCS:800-154665 DevCage: # 32162 (BDNT24234): Default changed in msql_driver_param file Date: Tue, 5 Sep 2006 11:31:26 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) The installation wizard consumed a lot of times. Database is in LEVEL 2 mode but I see in $BSE/lib/msql/msql_driver_param that query optimization is 011. Workaround n/a Test Procedure install ERP LN. Affected Executables msql7_adm.exe Motive source SDIS:TECH-00000-01296 DevCage: # 32112 (BDUX24307): SQL NQP extension for timezone conversions Date: Thu, 31 Aug 2006 16:05:23 +0200 (CEST) Created on: DevCage Type: enhancement Problem Description (Customer terms) Extend the SQL language with timezone conversion function. Test Procedure Execute the following query (to convert a time from UTC to MET timezone): SELECT CONVERT_TZ(TIMESTAMP '2006-08-31 12:00:00', 'UTC', 'MET') FROM Result must be: 2006-08-31 14:00:00 Affected Executables All DevCage: # 32095 (BDUX24229): TCS 800-150128 (std_gen: errors are reported twice) Date: Thu, 31 Aug 2006 12:03:56 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Not all std_gen compile errors were found. Some seemed to be reported twice. Workaround Not applicable Test Procedure script: field.xyz: when.field.changes script: display.all before.program: long y script: long x long y string z(10) z = x + y before.program: display.all() script: declaration: long a group.1: after.choice: Affected Executables std_gen Motive source TCS:800-150128 DevCage: # 31980 (BDUX24086): PAM is not working correctly on Linux and Solaris Date: Fri, 25 Aug 2006 14:03:16 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) PAM doesn't work correctly on Linux and Solaris Affected Executables badmin6.2 bshell6.2 Motive source TCS800-154420 DevCage: # 31946 (BDUX24164): SHM attach may fail on SUN Date: Thu, 24 Aug 2006 10:04:04 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) SHM was not always accessible for database driver and/or bshell on SUN Test Procedure Run shmmanager, and then bshell, or bsql or qptool. Check that bsql/qptool/bshell can attach to SHM. Affected Executables shmmanager6.x DevCage: # 31842 (BDUX24047): Manual merge of BDUX24009 (Only root login allowed) Date: Wed, 16 Aug 2006 10:15:39 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Users cannot logon if blogind protocol was used on AIX/DEC Workaround Be sure that USER env. var is not set when starting blogind/rexecd.exe Test Procedure Try to login with blogin protocol. Logon should succeed (if password was ok). DevCage: # 31833 (BDUX23946): Make bdbvalidate pick up the -H flag, and do not skip fields-to-be-checked Date: Tue, 15 Aug 2006 17:24:58 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) (1) "bdbvalidate6.2" did not pick up the -H flag if HIGH_ASCII_TOLERANCE was set in the environment. (No remark or defect.) (2) "bdbvalidate6.2", with option -H or resource high_ascii_tolerance=0 or environment variable HIGH_ASCII_TOLERANCE=0, did not check single-byte fields for high ASCII characters, if that field had no explicit domain constraints. (No remark or defect, found by Jan Blankenburgh.) (3) "bdbvalidate6.2" did not check multi-byte fields for a possibly incorrect 'plen', if that field had no explicit domain constraints. (No remark or defect; introduced in BDUX23192 for TCS defect 800-152880.) Workaround n/a Test Procedure See problem description (customer terms). Affected Executables bdbvalidate6.2 DevCage: # 31788 (BDUX23985): Always interpret idxopt value in /baan/b61a/bse/lib//_driver_param in octal Date: Mon, 14 Aug 2006 11:56:33 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Performance problems at several customer sites on queries that do an index scan. Workaround Be aware that the idxopt value in $BSE/lib//_driver_param file needs a leading 0, so specify "014" instead of "14". Test Procedure Test for oracle driver (for others you can setup compareable tests, but you have the figure out the right values) Specify idxopt value "14" im the ora_driver_param file. DBSLOG=01400 bsql6.2 -c 0 -q "SELECT tfgld482.* FROM tfgld482 WHERE tfgld482._index2 < { 1,'x','y' } ORDER BY tfgld482._index2 desc as set with 1 rows" Note that this test will generate error 506 as the tf table does not exist in company 0, but that does not matter here. The generate Oracle-SQL in the dbs.log file will use the FILTER technique when using the old porting set, and the ITERATIVE approach when using the new one. Affected Executables all database drivers Motive source Spin off of Inquiries 348821 and 338108 DevCage: # 31758 (BDUX23939): non licensed objects in SHM do not run Date: Tue, 8 Aug 2006 17:13:31 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Cannot run unlicensed objects when in SHM Test Procedure load ottstpcalc in shm and try to run it Affected Executables bshell6.2 DevCage: # 31731 (BDNT23845): Unicode: MSQL bind parameter problem Date: Thu, 3 Aug 2006 14:19:39 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) MSQL Unicode: tss bind value not converted to utf-16 causing installation problems Test Procedure Unicode full install Affected Executables msql_srv Motive source TCS 800-153937