Oracle® Developer Suite Release Notes
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX
Part No. B10668-05
This chapter discusses issues and workarounds for Oracle Discoverer Desktop (Discoverer Desktop). The chapter includes the following topics:
This section describes general issues and their workarounds for Oracle Discoverer Desktop.
If you install Oracle Discoverer Desktop 9.0.4 on the same computer as Oracle Discoverer Desktop 9.0.2, the following error message will be displayed if you attempt to start Discoverer Desktop 9.0.2 from the Windows Start menu:
Cannot find a required file : dcmresus.msb.
The message is displayed because of a problem loading certain libraries on a computer with multiple Oracle homes. The same message will also be displayed if you attempt to start Discoverer Desktop 9.0.2 by double-clicking on
dis51usr.exe in Windows Explorer.
To work around this problem, do one of the following:
Workaround 1: Run Discoverer Desktop 9.0.2 from the Windows command line, as follows:
From the Windows Start menu, choose Command Prompt to display the Command Prompt window.
Enter the following at the command prompt:
where 902_ORACLE_HOME is the directory in which Discoverer Desktop 9.0.2 was installed.
Workaround 2: Run Discoverer Desktop 9.0.2 from a batch file, as follows:
Open a new file in a text editor (for example, Notepad).
Enter the following in the new text file:
Save the file in the directory
\discoverer902\bin, and give the file a
.bat suffix (for example,
To start Discoverer Desktop 9.0.2, you can do either or both of the following:
Double click the new
.bat file in Windows Explorer.
Replace the existing shortcut to Discoverer Desktop 9.0.2 in the Programs menu with a shortcut to the new
Note:The above workarounds assume the user has already used the Oracle Home Selector (typically required for any computer with multiple Oracle homes).
This section describes useful information for Oracle Discoverer Desktop.
Do NOT manually edit the End User Layer (EUL) tables or contents (for example, by using SQL*Plus), unless specifically directed to do so by Oracle Support or Development. Manual editing of the EUL tables is not supported and any manual changes can result in a corrupt EUL.
For end users who are only able to run scheduled workbooks, note that the Refresh button in the Scheduling Manager dialog will not re-run the query from the base tables, but from the table that stores the scheduled workbook results. This is also the case for the "Run query automatically" option on the General tab of the Options dialog.
Previous versions of Oracle Discoverer shipped with the files
Memo.doc, which were used to demonstrate "drill out" functionality. To reduce disk space requirements and installation time, these files and instructions for their use will be made available from the Oracle Technology Network (
The following Oracle Discoverer registry variables are available, in addition to those documented in the Oracle Discoverer Administrator Administration Guide and the Oracle Application Server Discoverer Configuration Guide:
|Category||Discoverer registry variable||Description||Default||Valid Values|
|Database||DefaultPreserve DisplayProperty ForRefresh||When refreshing, specifies whether an updated item description is discarded and replaced with the original description, or whether the updated description is retained||0||
|Database||EnableTriggers||Specifies whether database triggers are disabled.
For example, Discoverer attempts to make a database call for every new column found during a refresh. If this value is set to 0, Discoverer will not make the database call.
|Database||ExportJoinFrom Master||When exporting a business area, specifies whether joins from the master folder are also exported.||0||
|Database||SetNULLItem HeadingOnBulk Load||When performing a bulk load, specifies whether item headings are set to the same value as item display names, or set to null.||0||
Oracle Discoverer's support for Transparent Application Failover (TAF) on a Real Application Cluster (RAC) computer requires a failover mode of "select", as shown in the example
tnsnames.ora entry below:
NAME = (DESCRIPTION= (ADDRESS= (PROTOCOL=tcp) (HOST=servername) (PORT=1521)) (CONNECT_DATA= (SERVICE_NAME= NAME) (FAILOVER_MODE= (TYPE=select) (METHOD=basic) (RETRIES=4) (DELAY=15))))
Oracle Corporation recommends that you should initially set RETRIES and DELAY to the values given in the example above (that is, 4 and 15 respectively). However, you may need to increase these values for your own computer.
In certain rare scenarios, end users may see an error message if failover occurs. When they acknowledge the error message, their sessions will continue as normal. A fix for these scenarios is planned for release as a patch to the 9.0.4 release.