Lab128. Known bugs.
Version 1.8.12
| Bug ID: | 201705190 - Lab128 can hang. |
| Symptoms: | Lab128 can hang during automatic collection of performance data. |
| Explanation: | The internal deadlock happens. |
| Workaround: | Upgrade to 1.8.13 or later version. |
| Fix: | Fixed in 1.8.13 version. |
Version 1.8.x
| Bug ID: | 201702190 - Dates in the reports use wrong country local formatting. |
| Symptoms: | In the reports dates can use wrong format. |
| Explanation: | The information about Date/Time format was incorrectly read. |
| Workaround: | Upgrade to current version. |
| Fix: | Fixed in 1.8.10 version. |
Version 1.8.8, 1.8.9
| Bug ID: | 201702010 - SSH connection refused to some SSH servers. |
| Symptoms: | An attempt to see the Alert file or Top Processes gives error: Not supported SSH version |
| Explanation: | Recent changes in the SSH code resulted in the removal of support for SSH servers with SSH-1.99 as not supporting SSH version 2, although they do support SSH2. This code has been restored. |
| Workaround: | Upgrade to current version. |
| Fix: | Fixed in 1.8.10 version. |
Version 1.x
| Bug ID: | 201701120 - Wrong positioning of some pop-up windows when using large monitors. |
| Symptoms: | Some pop-up windows position incorrectly when large monitors are used. This effect is almost unnoticeable on smaller screens. |
| Explanation: | The modal windows user absolute positioning coordinates, while relative/application coordinates were used. |
| Workaround: | Upgrade to current version. |
| Fix: | Fixed in 1.8.10 version. |
Version 1.8.x
| Bug ID: | 201701110 - Clusterware Commander appears to hang for about 1 minute during execution of the clusterware commands. |
| Symptoms: | The execution of Instance Start/Stop and other commands could hang CW Commander. |
| Explanation: | The modal window displaying the command can block normal execution of the background activity. |
| Workaround: | Upgrade to current version. |
| Fix: | Fixed in 1.8.10 version. |
Version 1.8.8.0 released on December 26, 2016
| Bug ID: | 201701050 - Hanging on opening of the alert file or other trace files. |
| Symptoms: | In the Alert File Viewer window, the file is not loaded. Similarly, when 10053 Trace Viewer is open, the file is not loaded to the viewer. |
| Explanation: | The bug was introduced in this version. While querying SFTP protocol version, the list of features can be supplied by the server. This list is optional. On some servers the list is empty, but Lab128 is still expecting the list, causing a wait for data which never arrives. So the user observes hanging on some SFTP server implementations. |
| Workaround: | No workaround. |
| Fix: | Fixed in 1.8.9 version. |
Version 1.8.7.0 released on July 20, 2016 (or earlier)
| Bug ID: | 201607300 - Exception on closing Activity Explorer / SQL Explorer / Session History windows. |
| Symptoms: | After switching to Tree tab in ASH section of Activity Explorer / SQL Explorer / Session History, if there is large number of tree lines (1000+), the exception can be thrown. Closing these windows can also produce an exception and then refusing to reopen the window. |
| Explanation: | When building a tree too many Graphic Device Interface (GDI) handles are allocated eventually exceeding the limit. |
| Workaround: |
No workaround. You may never hit this bug, unless selecting very large time interval and choosing the grouping with high cardinality item being first, for example, by Object ID / SQL. These will produce many rows in the tree, leading to the problem. |
| Fix: | Fixed in future versions. Please contact if you need this fix earlier. |
Version 1.7.0.0 released on October 23, 2014
| Bug ID: | 201411050 - Activity Explorer shows zeros in elapsed time and percentages in ASH summary section. |
| Symptoms: | Activity Explorer shows zeros in elapsed time and percentages in ASH summary section. |
| Explanation: | The default time interval between snapshots of active sessions incorrectly propagates into the aggregation engine. |
| Workaround: | There is easy workaround. Open monitor settings: Main Menu | Options | Settings for Monitored Instance; then go to the "Active Session History" section, "Time Between Measurements, sec" edit box and replace "1" with "1.01". Press "Apply and Close" button. Now the aggregation should work OK. |
| Fix: | Will be fixed in future versions. |
Version 1.6.6.0 released on August 2, 2014
| Bug ID: | 201408220 - Lab128 64-bit version hangs after monitored instance restarted. |
| Symptoms: | Lab128 64-bit version can hang after monitored instance restarted. |
| Explanation: | The conversion from double type to integer exceeds 32-bit integer range and causes exception. Lab128 32-bit is not affected, because no exception is generated by 32-bit code. |
| Workaround: | None. Upgrade to 1.6.7 or later. |
| Fix: | Fixed in 1.6.7 version. |
| Bug ID: | 201408221 - Lab128 64-bit version repeatedly reconnects to some databases with non-UTF8 character sets. |
| Symptoms: | After connecting to some databases with WE8ISO8859P1 character sets, Lab128 can reconnect repeatedly. |
| Explanation: | The character conversion from DB character set to UTF-8, which is used by Lab128 internally, was using too small buffer causing memory access fault and termination of the thread responsible for connection to Oracle. |
| Workaround: | None. Upgrade to 1.6.7 or later. |
| Fix: | Fixed in 1.6.7 version. |
Version 1.6.4.0 released on February 4, 2014
| Bug ID: | 201403040 - Reports may be empty when showing data for Oracle object containing pound '#' sign in their names. |
| Symptoms: | Reports shows "no data" for Oracle object names containing pound '#' character. |
| Explanation: | The pound '#' character has a special meaning in internal URL used to identify the reports and parameters. |
| Workaround: | Download 1.6.4.2 technical release lab128_1642.exe, then run this digitally signed exe file or rename it to lab128.exe replacing the existing file. |
| Fix: | Also will be fixed in future versions. |
| Bug ID: | 201402190 - Lab128 gets "ORA-29275: partial multibyte character" when monitoring database with some 2-byte character sets such as Korean KO16MSWIN949. |
| Symptoms: | ORA-29275 error in the log files |
| Explanation: | Some Asian character sets need 3 bytes per character in UTF8 encoding while only 2 bytes were reserved |
| Workaround: | Download 1.6.4.2 technical release lab128_1642.exe, then run this digitally signed exe file or rename it to lab128.exe replacing the existing file. |
| Fix: | Also will be fixed in future versions. |
Version 1.6.2.0 released on August 2, 2013
| Bug ID: | 201308150 - Closing Explain Plan window can produce memory exception. |
| Symptoms: | Closing Explain Plan window can produce memory exception. |
| Explanation: | The memory manager deallocates before all dependent objects deallocate. |
| Workaround: | Download 1.6.2.2 technical release lab128_1622.exe, then run this digitally signed exe file or rename it to lab128.exe replacing the existing file. |
| Fix: | Fixed in 1.6.2.2; 1.6.3.0 versions. |
| Bug ID: | 201308090 - Hostname can be truncated in SSH login window. |
| Symptoms: | When selecting saved connections in SSH login window, the hostname can be truncated. |
| Explanation: | Conversion to UTF8 receives wrong length parameter. |
| Workaround: | Download 1.6.2.2 technical release. Also, the hostname can be manually typed in. Download lab128_1622.exe, then run this digitally signed exe file or rename it to lab128.exe replacing the existing file. |
| Fix: | Fixed in 1.6.2.1, 1.6.3.0 versions. |
| Bug ID: | 201308080 - The editor in SQL Central removes trailing spaces. |
| Symptoms: | The editor in SQL Central removes trailing spaces after 1-2 second pause. |
| Explanation: | The editor configuration is incorrect. |
| Workaround: | Download 1.6.2.2 technical release. Download lab128_1622.exe, then run this digitally signed exe file or rename it to lab128.exe replacing the existing file. |
| Fix: | Fixed in 1.6.2.1, 1.6.3.0 versions. |
Version 1.5.9.12 released on March 8, 2012
| Bug ID: | 201203110 - Lab128 produces memory access fault error. |
| Symptoms: | Stack dump file "send to technical support..." with <Invalid Read at 0xFFFFFFF*> |
| Explanation: | Error in time conversion function. |
| Workaround: | Download 1.5.9.14 version. |
| Fix: | Fixed in 1.5.9.14 version. |
| Bug ID: | 201203120 - Oracle 8i connection problem. |
| Symptoms: | |
| Explanation: | Error in setting workarea_size_policy session parameter which is not available in 8i. |
| Workaround: | Download 1.5.9.14 version. |
| Fix: | Fixed in 1.5.9.14 version. |
Version 1.5.9.10 released on April 28, 2011
| Bug ID: | 201106080 - The Top Processes window may hang when monitoring Oracle on AIX platform. |
| Symptoms: | This is related to AIX platform only. The Top Processes window can freeze. There can be stack dump files generated in the Lab128 working directory. |
| Explanation: | AIX is somewhat different than other Unix-like environment. There is no 'top' command/application implemented in AIX, Lab128 uses 'nmon' command to provide comparable information. This bug is in the module that decodes 'nmon' data. |
| Workaround: | Do not open Top Processes window if Oracle runs on AIX platform or contact technical support for the patch. |
| Fix: | Fixed in 1.5.9.12 version. |
| Bug ID: | 201105170 - After the DB upgrade to Oracle 11.2, the query on v$lock view is very slow and consumes CPU on the server side. |
| Symptoms: | After the upgrade to 11.2, the query on v$lock used by Lab128 takes long time to execute and the query uses a lot of CPU resources on the server side. |
| Explanation: | This is actually an Oracle bug but it affects Lab128. There were multiple reports that after the upgrade to 11.2, queries against v$lock / gv$lock (like this one: select * from v$lock) becomes CPU-intensive and can take minutes to execute. |
| Workaround: | Please contact technical support for the workaround of this Oracle bug. |
| Fix: | Fixed in 1.5.9.12 version. |
Version 1.5.9.8 released on November 9, 2010
| Bug ID: | 201103070 - Lab128 can hang when NLS_LANG on client is set to multibyte character set (AL32UTF8 etc). |
| Symptoms: | When Oracle client is using multibyte character set by having NLS_LANG set in the regisrty or in environment variable, a query on CLOB column can hang. This causes the application to hang. |
| Explanation: | Queries on LOB columns can return into the reserved buffer of fixed size less characters than expected, because some characters take more than 1 byte. The application calls for more characters in the loop with no chance to exit. |
| Workaround: |
Before starting Lab128, set NLS_LANG to a single-byte characterset. For example: NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 You can also change NLS settings on the client by changing the registry key: HKEY_LOCAL_MACHINE/SOFTWARE/Oracle/KEY_*_home*/NLS_LANG Please note that this registry change can affect other applications running on the same workstation. |
| Fix: | Fixed in Lab128 version 1.5.9.10. |
| Bug ID: | 201102140 - Lab128 can hang in the Alert File viewer if the alert file contains other than ASCII 7-bit characters, for example with codes in 0x80-0xFF range. |
| Symptoms: | The application hangs when starting the Alert File viewer if the alert file contains other than ASCII 7-bit characters. |
| Explanation: | The highlighter used by Alert File viewer doesn't expect non-ASCII 7-bit character and produces memory access fault. |
| Workaround: | None. Don't use the Alert File viewer if the alert file is expected to have characters other than ASCII 7-bit characters. |
| Fix: | Fixed in Lab128 version 1.5.9.10. |
| Bug ID: | 20101115 - Lab128 can hang in Activity Explorer for few minutes using local CPU 100%. |
| Symptoms: | Lab128 can hang in Activity Explorer for few minutes using 100% local CPU. |
| Explanation: | This can happen on a single-CPU workstation with a monitored database having large number of database objects (>100,000). The Lab128 user interface thread spins instead of entering sleep mode while wating on a lower priority thread to complete the internal dataset update. On a single-CPU workstation, the lower priority thread becomes starved for CPU time and takes an unusualy long time to complete. |
| Workaround: | None. If you experience this rare problem, please contact technical support for the patch. |
| Fix: | Fixed in Lab128 version 1.5.9.10. |
| Bug ID: | 20101110 - Lab128 doesn't start with Oracle client 8.0.5 or 8.0.6. |
| Symptoms: | When using an old Oracle client (before version 8.1.5), an access memory fault happens. |
| Explanation: | This is caused by the OCIEnvCreate function which is missing in old Oracle clients. |
| Workaround: |
Option 1 - Upgrade Oracle client. Option 2 - put two DLLs from the Instant client into the Lab128 directory, please see more details in this FAQ question. |
| Fix: | Fixed in Lab128 version 1.5.9.10. |