Lab128 info in other languages:
|
Lab128. Known bugs.
| 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: |
Will be fixed in the future 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: |
The workaround will be implemented in the future 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.
|
|
