Oracle® Developer Suite Release Notes
10g (9.0.4) for Windows, Linux, Solaris, and HP-UX
Part No. B10668-03
This chapter discusses the following Oracle Software Configuration Manager (SCM) topics:
The Oracle Software Configuration Manager development team are committed to producing regular patchsets following the release of Oracle Developer Suite 10g (9.0.4). The latest SCM patch sets are made available on OracleMetaLink (
http://metalink.oracle.com). Go to patches, then enter the patch ID (if known) or alternatively search Product or Family "Oracle Designer - Repository Family". For additional information about availability and compatibility of the latest releases, see Support note:60705.1.
Important: If your repository has been installed or upgraded via the repository administration utility (RAU) that came with Oracle Designer/SCM release 220.127.116.11, you must immediately patch all Oracle Designer 18.104.22.168 clients by applying the Oracle Designer/SCM patchset 22.214.171.124.
Oracle Designer/SCM 126.96.36.199 works against an earlier version of the repository that came with Oracle Designer/SCM 188.8.131.52 and will not work against a later repository from Oracle Designer/SCM release 184.108.40.206. Oracle Designer/SCM patchset 220.127.116.11 (a maintenance release) patches your 18.104.22.168 installation allowing it to connect to the 22.214.171.124 compatible repository.
If your repository is still at a version compatible with Oracle Designer/SCM 126.96.36.199, Oracle Designer/SCM 188.8.131.52 will work with that repository. However, we strongly recommend that you install the Oracle Designer/SCM 184.108.40.206 patchset on your 220.127.116.11 clients and upgrade your repository as soon as possible.
If you wish to create a new repository, then, before doing so, we strongly recommend that you install the Oracle Designer/SCM 18.104.22.168 patchset on your 22.214.171.124 installation. This will prevent you subsequently having to upgrade it via the RAU when you later apply the Oracle Designer/SCM 126.96.36.199 patchset.
There may be product dependencies requiring Oracle Forms Developer and Oracle Reports Developer patch sets. Follow Support Notes for any future updates.
Current certification details can be checked on OracleMetaLink (
http://metalink.oracle.com) by choosing the Certify & Availability option.
The earliest previous release from which Oracle SCM provides upgrade is Oracle Repository 6.0. Users of the older Oracle Designer Release 1.3.2 wishing to upgrade to Oracle SCM will therefore need to upgrade to Oracle Designer 6.0 first. The following alternatives exist for locating the upgrade to Oracle Designer 6.0:
If Oracle Designer 6.0 is installed, the upgrade from Oracle Designer 1.3.2 can be invoked from the Oracle Designer 6.0 Repository Administration Utility.
The Oracle Designer 1.3.2 to 6.0 upgrade can be obtained from OracleMetaLink.
When you install Oracle SCM, you can select a combination of different product languages to install on the same computer. If you select Japanese as one of these languages (for example, a selection of Japanese, Korean and English), you should be aware that the user interface (translations) will be in Japanese, and this cannot be altered by changing the NLS language on the client computer. If you do not select Japanese (for example, if you select Chinese, Korean and English), the user interface will be in English. Therefore, if you do not require the user interface to be in Japanese, then you should not select Japanese as one of the product languages.
Details of compatibility of Oracle Repository 6i and Oracle SCM repositories can be found in support note 60705.1, available on OracleMetaLink.
To read the support note:
Log in to OracleMetaLink (
Enter the note number in the Search field and select Advanced.
Select the DocID option and select Search.
Select the document title.
New feature: Instrumentation Report
RAU->HELP MENU->Instrumentation Report
Intended use by:
Designer/Repository Administrators, other DBAs and Oracle Support
Repository Administration Privileges, connection to the Designer schema instance (established via the RAU). An HTML Browser is required to view the output.
This report is intended to assist with the diagnosis and resolution of common problems. The HTML output produced is mainly server and repository related although some of the client registry settings are also reported.
Typically you may be experiencing a problem as a result of one or more of the following:
Designer schema installation, upgrade or migration setup
Designer schema invalid, missing or disabled schema objects
Tablespace storage issues
Missing system privileges or grants
Invoking import/export or SQL*Plus utilities
If you are experiencing problems in these areas the report may help you to quickly identify and resolve the problem. An Oracle Support representative may also ask you to run the report and supply the output for further analysis.
The RAU will attempt to display the report in an appropriate HTML browser, provided your client is set up to use one. Otherwise the output files can be found in the respective
You may also want to run this report after an installation, upgrade, or as part of your standard maintenance tasks, just to provide a general "health check" status of the schema.
Please refer to the online help for further information on this feature.
Other changes from the previous release of Oracle Repository 6i are bug fixes.
The registration feature (transfer of an existing Oracle schema into the repository) is still available, but has been de-supported.
Log in to OracleMetaLink (
Click the Bugs button on the left of the screen.
In the Bug Database Search dialog:
From the Product list, select Oracle Repository (the bug database uses the old product name).
From the Status list, select one of the "Closed" options (e.g. "Closed, verified by filer").
In the Fixed in Version field, enter a product version number to search (e.g. "9.0.2%").
Enter values in any other fields to restrict the search as required.
Click the Search Bugs button.
The API and Model Reference Guide is available on the Oracle Technology Network (
http://otn.oracle.com). From the navigator frame on the left of the screen, choose Documentation > Oracle SCM (Repository) > Repository API and Model Reference Guide.
This section documents known problems and restrictions for:
ORA-02063: preceding 2 lines from R212', encountered during migration from Designer 6.0 to 6i/9i (bug 2758364)
ORA-02063: preceding 2 lines from R212
RME-02124 Failed to execute SQL statement: begin ck_upgrade_mod.init(:b1, b2);
Note, It is also possible that other similar errors may also occur at different stages of the migration process.
Sometimes the problem can be resolved by clicking on the retry button on the RAU control panel, or restarting the migration at the point of failure after shutting down and restarting the instance, but if this is a persistent problem then it could be related to the fact that the source or target instances may not be setup correctly (see below).
You can verify this by looking in the
init.ora parameter file to see the settings for open_cursors, if one does not exist then the default which is 50 will be used.
Try running the following SQL command from SYS to verify this (8.0.x):
select NAME, VALUE
where upper(NAME) like 'OPEN_CURSORS' /
Name Value ---------- open_cursors 50
Note: it is recommended that you run this SQL as the value in the
init.ora file may differ to that that has been applied to the instance. On 8i or above you need to use the following command:
show parameter open_cursors
NAME TYPE VALUE --------------- open_cursors integer 50
It is worth checking all the
init.ora parameters match or exceed the minimum recommended values in the documentation that came with your product. This is true for both Designer 6.0 (migration source instance) and the SCM (migration target instance).
Skipping insert of Element element_ID because ..... Duplicate Plural Name
This bug is a duplicate of bug 2641774, which is in the process of being fixed.
Command Line Tool
Version History Viewer (VHV)
Version Event Viewer (VEV)
The failure to invoke a Java tool may occur in the following ways:
Problem: Java application does not invoke
This occurs when invoking the Command Line Tool from a short cut or from the Repository Object Navigator.
This occurs when trying to use the 'connect' command from the Command Line Tool.
Problem: java.lang.IllegalArgumentException : ErrorDialog: null message vector
This occurs when running the Dependency Manager (
ckdm61) from the DOS command prompt.
This occurs when invoking the VHV, VEV or Compare Utility from the Repository Object Navigator.
Problem: Connect dialog keeps appearing
This occurs when invoking the Dependency Manager from the Repository Object Navigator or the Oracle Designer Front Panel.
All of these problems stem from the same cause. There is a bug with the thin JDBC driver (bug 2346116) such that connections will fail if the length of the connect string is in the range 184 - 192 characters. See bugs 2181931 and 2346116 for more details.
Note: This happens only when connecting to an Oracle9i server. If connecting to an Oracle 8.1.7 server, all possible variations of
TNSNAMES.ORA entries that work for SQL*Plus and the repository C++ tools will work and allow the Java tools to be invoked.
database instance name
database host name
database host domain
client computer network name
client computer username
name of Oracle home directory for Oracle SCM
Thus there is no simple workaround that will work for all situations. If you encounter this problem with a particular TNS alias, the workaround is to change the length of the alias entry in the
TNSNAMES.ORA file. Increase or decrease the length of the entry, preferably by a minimum of 9 characters. The simplest way to do this when using Oracle Net configuration tools is to add the domain to, or remove the domain from, the hostname, for example:
Use host.domain instead of host if you have not previously specified the domain.
Use host instead of host.domain if you have previously specified the domain.
CKREPINImay fail with the following error:
end-of-file-communication channel ORA-24323: value not allowed Error accessing package DBMS_APPLICATION_INFO ORA-03114: not connect to ORACLE
CKREPINI, which will now succeed.
Files and Folders
If using only files and folders, you might want to turn off the heading "Files" in the Navigator window. To do so, choose Navigator > Show Hide, select Objects in the Show Type Headings field and select the Never option button.
Check In Contents
To check in the contents of a workarea or container, choose Version > List Checkouts, select the sub-context and click OK. In the List Checkouts dialog box, click Select All, then click Check In.
Note that if you purge versions from a workarea, prior versions, or other versions depending on the appropriate workarea compilation rule, will not appear until the workarea is refreshed.
Memory usage when running Java utilities from the Repository Object Navigator
The Compare and Merge utilities, and the Version History Viewer and Version Event Viewer are written in Java. The first time one of these tools is invoked, a Java Virtual Machine (JVM) is started within the Repository Object Navigator process. It will then appear that the Navigator is using a great deal more memory. The JVM is not shut down until the process ends, so this memory usage will not decrease until the Repository Object Navigator is shut down, even though the tool window may have been closed.
The memory parameters used by the JVM at startup can be controlled by registry settings. Memory allocations may need to be increased or adjusted depending on usage and the host environment. You can do this by changing the values of the following Windows registry variables, all of which are shown in bytes under the following registry keys:
(where HOMEn is home number of the home installed into for a multiple Oracle home environment, but is not present where the default Oracle home is being used).
There is also a problem in that the memory used by each invocation of one of these Java tools is not completely freed up. This may result in out-of-memory conditions arising after many invocations. If this happens, shut down and restart the Repository Object Navigator, or invoke the utilities from the Command Line Tool, which runs in its own JVM.
.docextensions, but on Win32 computers these extensions are most likely to be used for MS Word files, which are binary.
CDR-03120 : Internal Error - Problem making a repository connection.
The Command Line Tool will invoke and immediately close down. If you invoke the Command Line Tool directly and try to connect to a repository on the default database of the local computer you will get a Java error.
localhas been set up as an alias or Net8 connect identifier for the local database by Net8 Configuration.
An alternative workaround is to use the Command Line Tool instead of the Repository Object Navigator to invoke the VHV for the configuration. The Command Line Tool will prompt the user to set the workarea context but, once this has been done, the VHV for the configuration will be successfully invoked.
CDR-03100: Diff/Merge internal error: java.lang.IllegalStateException (compare)
CDR-03126: Internal Error - Object Delta retrieval (merge)
The message from the Version History Viewer for either compare or merge is:
A warning dialog box (currently undocumented in the online help) is displayed to inform you that that it is not possible to compare in these circumstances. You should ignore this warning when not comparing versions of a subclassed form in the same workarea or configuration.
Create a string value "SUBCLASS_WARNING" with value "FALSE". Any other value (or the string not existing) results in the warning being displayed.
Any compare of a subclassed form must be carried out on versions that are in different workareas or configurations.
Comparing Oracle Forms
The Compare utility enables you to compare different versions of the same Oracle Form file, but not two different Forms files. When comparing files other than Oracle Forms, two different files can be compared.
Merge Window, clarification on saving changes
After making changes, use File > Save to save your changes. Earlier versions had a Save button' which did this.
This also occurs for any client configured to use a NLS language other than the default "US".
Invoke the RON.
Navigate to the General Settings panel (Options > General Settings).
Type in the default date format that you want to use.
NOTE: You will need to perform this procedure for each client where you intend to use the VEV.
CDR-01062: Compilation leaves file
orphaned. Need to include container
This may have been caused by deletion of a previously imported folder that contained a share of an object, where the original object was not imported and does not exist in the workarea. In this situation, it is the share of the object that is causing this error.
GRANT EXECUTE ON sys.lt_export_pkg TO exp_full_database;
GRANT EXECUTE ON sys.lt_export_pkg TO PUBLIC;
GRANT EXECUTE ON sys.lt_export_pkg TO user;
Import/Export in database format - exported objects may contain dangling references
The repository utilities Export and Import in database format are designed to take advantage of the universal uniqueness property of the Repository Object Internal Identifier. For example an object can be copied from one repository to another using Export and Import without having to change its internal identifier.
This feature is used by the Export and Import utilities to allow new versions of objects to be copied to other repositories even though the logical identifier or user's identifier (e.g. NAME) has changed. It also means that object versions can be exported which have references to other objects not included with the export, i.e. an object version may contain dangling references. This is not a problem so long as a) a subsequent export or import copies in the missing referenced objects, or b) the dangling references are resolved, either by deleting that part of the dangling object's structure which includes the reference, or by nullifying the reference property.
You should always precede an export operation with a check for external references within the set of candidate export objects. For example, a workarea or container may include the definition of a module object which references a language object not included in the workarea or container.
To resolve dangling references automatically at the target repository, select the "Remove dangling references" option on the Advanced Options dialog box in the Import Wizard. This option is highly recommended if the Import is creating 'brand new objects' as it will not be possible to copy new versions or related versions later on.
Import/Export in database format - Import utility may require specific repository privileges or access rights
For a versioned repository, depending on the kind of export performed, the Import utility will execute operations on your behalf which may require certain privileges, for instance:
Manage Workareas - allows user to create a workarea
Compile - allows user to compile or refresh a workarea
Version - allows user to create new versions of objects within a workarea
If an error is returned by any of these operations, check that you have the appropriate repository privileges (assigned via the Repository Administration Utility) and workarea and container access rights (assigned via the Repository Object Navigator).
For a non-versioned repository, none of the above operations apply. The Import Wizard will normally detect this case.
Dependency Analyzer must be run against Pro*C files not the C files generated by the Pro*C compiler
The dependency analyzer should be run on a Pro*C (
.pc) file to extract the dependencies from the SQL embedded in the file. The analyzer will look at both the C and SQL dependencies in the Pro*C file.
If the dependency analyzer is run on a C file generated by the Pro*C compiler, then it is likely that the analyzer will fail. This is because the dialect of C generated by the Pro*C compiler will trigger one or more underlying bugs in the dependency analyzer C parser (e.g. bug 2744718 - DA FAILS TO PARSE SELECT STATEMENT WHEN IT'S CONCATENATED WITH '\'). Analyzing the C file generated by the Pro*C compiler will also fail to extract the SQL dependencies, as there is no special handling for the generated OCI API. If the SQL dependencies are desired, then the Pro*C file itself must be analyzed.
Switching off case matching for object names
The MATCH_CASE session variable can be used to switch on and off the matching of case for names of objects. Switching the MATCH_CASE session variable off, using the command
set match_case off
command, may degrade performance in larger repositories.
The SCM Java based tools, which include:
Version History Viewer
Version Event Viewer
Command Line Utility
all use JDBC thin client as the mechanism to connect to Repository. As a result these tool do not support OS authenticated connections.
Use of public and private synonym access
Public synonym access is recommended only if you have a single Oracle SCM repository on the Oracle instance. If you have more than one such repository, we recommend that you use only private synonym access for each of them. Avoid the case where one repository is using public synonym access and the others are using private synonym access since this may lead to unpredictable behavior.
The message should read
ORA-12514 : TNS:listener could not resolve SERVICE_NAME given in connect descriptor
The error occurs because the SERVICE_NAME in the CONNECT_DATA was not found in the listener's tables.
This error will be returned if the database instance has not registered with the listener; the instance may need to be started.
You will see one of the following two failures:
You will see the following error messages:
ORA-01403: no data found
RME-02124: Failed to execute SQL statement: begin jr_workarea.define_spec(:wa,:spec); :iserror := 0; :sqlcode := 0; exception when others then :iserror := 1; :sqlcode := sqlcode; end;
The workarea update simply does not add the new rule, because if the file is bigger than 30000 bytes, only the first 30000 bytes are read, terminating the later portion.
.RVI files visible on file system
When creating a folder mapping, extra files called
.RVI files are created. The repository uses
.RVI files to store information about which file and folder objects have been updated. Do not delete these
If a repository containing tables with LOB columns is backed up, the tables with LOB columns must be restored to a tablespace with the same name as the original, otherwise the restore fails with the message:
does not exist
If a repository is restored from a backup that contains tables with columns based on types (e.g. SDW_USERS and SDW_ACCESS_RIGHTS) and a type name with the same object identifier (OID) as one being imported already exists anywhere in the target database, neither the types nor the tables are restored. The following error messages are displayed:
IMP-00015: following statement failed because the object already exist: "CREATE TYPE ... " IMP-00061: Warning: Object type "..." already exists with a different identifier IMP-00063: Warning: Skipping table "..." because object type "..." cannot be created or has different identifier
However, if the same type name exists but with a different OID and the IGNORE parameter is set to Y, the types are imported followed by the tables.
Everyone has full access to the global wastebasket (bug 1208420)
This unexpected behavior is not known to cause any problems.
Naming convention for user-defined version labels
If checking in to a default checkin branch using user-defined labelling, the version label becomes user label.
For information about automatic version labelling, refer to the online documentation.
Screen resolution types
Oracle SCM can be run under SVGA (recommended) or VGA.
Oracle recommends that you set the system font size to Small Fonts (Control Panel > Display > Settings > Font Size).
Please note that where you see Copyright 2002 this is also covered by Copyright 2003.
This section documents known restrictions to keyboard controls, and is organized in the following sections:
This section documents general keyboard control restrictions.
When the Dependency Manager is started from the Repository Object Navigator, keyboard focus may be unreliable. Therefore, the Dependency Manager must always be started from the Command Line Tool to make full use of the keyboard controls.
Version Event Viewer
When the Version Event Viewer is started from the Repository Object Navigator, keyboard focus may be unreliable. Therefore, the Version Event Viewer must always be started from the Command Line Tool to make full use of the keyboard controls.
Version History Viewer
When the Version History Viewer is started from the Repository Object Navigator, keyboard focus may be unreliable. Therefore, the Version History Viewer must always be started from the Command Line Tool to make full use of the keyboard controls.
This section documents areas of the user interface for which standard keyboard controls are not implemented and contains the following sections:
This section documents the parts of the Dependency Manager for which non-standard keyboard controls exist, but for which alternative keyboard controls are available.
Build Dependencies Dialog Box
The Build Dependencies dialog box contains a table and a number of controls. To navigate between the cells in the table, use the Tab key. To navigate from the table to the other controls in the dialog box, first navigate to the last cell in the table, then use Ctrl+Tab. To navigate between controls outside of the table, use the Tab key.
Change Workarea Dialog Box
To choose OK from the Change Workarea dialog box, focus must be on the OK button before activating the Enter key. If focus is on the list of workareas field when the Enter key is pressed, the dialog box is canceled without changing the workarea.
Search for Out of Workarea Objects Dialog Box
To navigate between the cells of the Configurations table, use the Tab key. To move focus out of the Configurations table, press Ctrl+Tab.
Selection Drop-Down Lists
A number of selection drop-down lists exist within the Dependency Manager. When using selection drop-down lists, use the following keyboard controls:
Press F4 to open the drop-down list, and navigate to the required entry using the Up and Down arrow keys.
If the selection drop-down list is a column in a table, press F2 first (to select the cell for edit), then F4 to open the drop-down list, and use the Up and Down arrows to navigate to the required entry.
This section documents the parts of the Repository Administration Utility for which non-standard keyboard controls exist.
Main RAU Panel
The Repository Administration Utility (RAU) panel comprises a number of buttons that provide access to administration features. To use the keyboard controls to access a feature from its associated RAU button, first navigate to the appropriate button (using the Tab key) and then press the spacebar.
User Maintenance Screen
On the User Maintenance screen, the options are Add Users, Delete Users, Expand Nodes, Collapse Nodes and View Properties. To use the keyboard to perform these tasks, use the Windows Menu key to display the context menu, then use the Up and Down arrow keys to choose the required option from the menu.
This section documents the parts of the Repository Object Navigator for which non-standard keyboard controls exist.
Each time the Repository Object Navigator is started a Navigator window and a Property Palette are displayed by default. To use keyboard controls to navigate through the Navigator window immediately after the Repository Object Navigator has been started, press F4 to switch context to the Property Palette, then press F3 to return to the Navigator window.
Color Dialog Box
Color can be used to distinguish text items in the Repository Object Navigator, the Property Palette and the TextPad. To use the keyboard to change the color of text, invoke the Color dialog box (as described in the online help system) and use the Up, Down, Left and Right arrow keys to pick the required color.
For some repository elements it is possible to specify reference properties, that is, references to repository elements that already exist. A reference property can be chosen from the Select Objects dialog box. To display the Select Objects dialog box from a Property Palette, position the cursor in the appropriate reference property field and press the Enter key.
To invoke any button in the Configuration Wizard dialogs, first navigate to the button using the Tab key and then use the spacebar to choose that button.
Dialog Boxes with Grid Controls
A number of dialog boxes in the Repository Object Navigator contain grid controls, for example, the Customize Navigator Groups dialog box. When using dialog boxes with grid controls, use the following keyboard controls:
To navigate around a grid, use the Up, Down, Left and Right arrow keys.
To navigate out of a grid to the next control, use Ctrl+Tab. Note that pressing Tab in the last cell of a grid navigates to the next window in the dialog box, if one exists.
Dialog Boxes with Query Windows
A number of dialog boxes in the Repository Object Navigator (for example, the Customize Navigator Views dialog box) contain query windows that contain buttons for actions, such as grouping conditions.
When using dialog boxes with query windows, use the following keyboard controls:
To move a row up the list for sorting purposes, use Ctrl+Up Arrow.
To move a row down the list for sorting purposes, use Ctrl+Down Arrow.
To group selected cells together, use Alt+G.
To undo a grouping for selected cells, use Alt+U.
To duplicate cells, use Alt+D.
To clear a condition, use Alt+C.
To toggle between AND and OR settings, use the spacebar.
To toggle check boxes, use the spacebar.
To navigate to a field with a mnemonic, use Alt + the mnemonic.
If the focus is on a tree, the Enter key opens or closes a branch instead of activating the default button (e.g., closing the dialog box).
If the focus is on a table, the Enter key navigates to the next row instead of activating the default button.
If the focus is in a multi-line text field, the Tab key navigates through the text. Use Ctrl+Tab to navigate to the next field.
If mnemonics are used to navigate to an editable drop-down list field, the field will not be in focus until the Tab key is pressed.
This section documents known problems and workarounds for keyboard controls:
When the Merge window has been invoked from the Command Line Tool, JAWS reads either blank, unavailable or nothing at all when the user navigates through the merge document. However, this problem will not occur if the Merge window is invoked from the Version History Viewer.
Use Alt+Tab to go to another window, then Alt+Tab to return to the Merge window.
Iconify the Merge window, and then de-iconify it.
Open and close any of the menus in the menu bar without selecting a menu item.
One of these workarounds will also need to be applied when the user navigates from the merge document to the toolbar and then back to the merge document.
This problem occurs when properties copied via 'Copy Properties' are being viewed via 'View Copied Properties', and the down arrow key is being used to trigger JAWS to read out the visible information for each property. When more than five properties have been copied, the reading for each property is preceded by a reading of the last property visible in the 'View Copied Properties' dialog.
Issue for JAWS users invoking VEV, VHV or Compare utilities.
When invoking the Version Event Viewer, Version History Viewer or Compare utility from the Repository Object Navigator JAWS will read the name of the dialog window as it is created, but it will then read the text of the Repository Object Navigator main window once the dialog has been established. This may suggest incorrectly that the invoked dialog has failed (and disappeared).
To verify that the dialog has been correctly created: Press the TAB key. This will highlight (focus on) the first control/menu item in the dialog, which JAWS will read.
It may be possible for a user to navigate via the keyboard to disabled tabs that would not be accessible to a user navigating with a mouse.
In order for JAWS to read output from the Command Line Tool correctly, users should download a set of scripts from the Oracle Technology Network (
There are currently no general Linux, Solaris, and HP-UX platform issues.
Broadcast Server - Solaris computers
The broadcast server does not work on Solaris computers (bug 1325598).