Release Notes for Oracle Designer and Oracle SCM |
Section 3 of 4 |
A full list of the bugs that have been fixed in Oracle Designer is available from Oracle Technology Network (otn.oracle.com).
If certain prerequisites are met, performance enhancements will automatically be incorporated into the repository during upgrade. The prerequisites are:
To allow manual installation of the performance enhancements if automatic installation was not possible, a new menu item "Enable Performance Enhancements" has been added to the Options menu in the RAU (repository administration utility). This menu item is enabled only when the prerequisites for performance enhancements are met (as above), and when the performance enhancements are not already installed. Choosing this menu item will install the performance enhancements to the repository. This is an irreversible action.
Associated with this facility, the Check Requirements Utility has been updated to show the new requirement "Execute permission on DBMS_RLS".
Importing a full repository dump file created from a repository with performance enhancements enabled
The use of RLS (row level security) imposes additional constraints on the import and export of data where the name of the repository owner importing the data is different from repository owner exporting the data (bug 3624540). A new file, jrpolicy_reset.sql, has been added which in conjunction with the RAU 'reconcile' facility will reapply the security policies under the name of the new owner of the data. The RAU 'reconcile' must be run twice; the first reconcile establishes the new owner and the second reconcile associates the imported data with that owner.
If you use the RAU to import a full repository dump file and get error messages of the form:
ORA-01918: user 'REPOSD48B9I' does not exist
ORA-06512: at "SYS.DBMS_RLS", line 308
ORA-06512: at line 1
IMP-00017: following statement failed with ORACLE error 1918: "BEGIN DBMS_RLS.ADD_POLICY('REPOSD48B9I', 'SDD_ENTUIE','SDD_ENTUIE','REPOS D48B9I','SDD_SAC_VERSION_POLICY','SELECT,INSERT,UPDATE,DELETE',FALSE,TRUE); END;"
then you are importing the data as a repository owner with a different name than the one used to export the data and must use import directly as detailed below. Whilst doing this, messages of the form "The view was created with compilation warnings" will be displayed. The import will end with a message like "Import completed successfully with warnings". These messages can be safely ignored.
To import a full repository dump:
IMP <newuser>/<password> FROMUSER=<olduser> TOUSER=<newuser> FILE=<repos.dmp>
where
olduser = the repository owner name from which the dump file is extracted
touser = the new repository owner's name
This section documents known problems and restrictions for the following parts of the Oracle Designer and Oracle SCM products:
The Oracle Designer development team is committed to producing regular patchsets following the release of 9.0.4. The latest patchsets are made available via Oracle MetaLink (metalink.oracle.com). To find the latest patchset in MetaLink, click the Patches button, then (in the new Metalink patch search facility) either enter the patch ID (if known) or search by "Product or Family" for "Oracle Designer - Repository Family". The latest iDS patchset is listed in the Release list (drop down box). For additional information about availability and compatibility of the latest releases, see Support note:60705.1.
Current certification details can be checked on OracleMetaLink (at 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 first need to upgrade to Oracle Designer 6.0. You can find the upgrade to Oracle Designer 6.0 in one of the following ways:
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:
There may be product dependencies requiring Oracle Forms Developer and Oracle Reports Developer patch sets. Follow Support Notes for any future updates.
When installing the Oracle Developer Suite software on a client machine, you can select a combination of different product languages (i.e., languages that you would like the products to support, if available). If you include Japanese as one of these languages (for example, if you select Japanese, Korean and English) then, in the Designer product, the user interface text will always be in Japanese. You cannot alter this later by changing the NLS language setting on the client machine. If you do not include Japanese as one of the product languages (for example, if you select Chinese, Korean and English) then the user interface text in Designer will always be in English.
If you do not require the user interface text to be in Japanese, then you must not include Japanese as one of the product languages. If you do require the user interface text to be in Japanese, you should, in addition to selecting Japanese as a product language, also check that a Japanese font has been installed.
If you have a National Language Support (NLS) version of the repository, you can change the display language for the following text:
Current valid display languages are the default (English) or Japanese.
With Oracle Designer, if you also use Generator tools, you can change the display language for Generator preference descriptions and their valid value meanings. Changing the display language for "Valid Preference Names" will also change the display language for the Repository Object Browser (ROB).
The translated text files for the display languages that the repository supports are installed in the directory Oracle_home\REPADM61\NLS if you have an NLS version of the repository.
Note: If you do not have these translated text files in the \NLS directory, you cannot change the display language.
To set up the repository for NLS operation, you need to:
When installing a repository from the Repository Administration Utility (RAU), you may select either "support for Repository (core) objects" or "support for Oracle Designer Objects". If your repository was installed by selecting the "support for Repository (core) objects" option then you must also install support for Oracle Designer Objects before the repository can be used by the Oracle Designer client tools. This is achieved by re-running the RAU and installing the required support. If your repository additionally requires upgrading, then you can either:
Enabling support for Oracle Designer Objects will cause the repository to become non-versioned. Any version history information from the repository will not be visible. To switch the versioning on again, in the Repository Administration Utility choose Options > Enable Version Support. The version history information will then be visible (bug 1419412).
Introduction
Oracle Designer release 9.0.2.4 onwards includes a web based reporting tool for Oracle Designer called Repository Object Browser (ROB). ROB is functionally similar to the Oracle Designer Web Assistant (ODWA) tool, which is developed and shipped as a part of Oracle iDevelopment Accelerator suite. This section is a guide for users of ODWA migrating to ROB.
Installing ROB
ROB will be installed automatically as a part of the repository install/upgrade process, by the Repository Administration utility (RAU). Unlike the ODWA, all the ROB objects will be installed within the REPOWNER schema. Access to all the subordinate users will be automatically created using the previously selected type of synonyms. Installing ROB on a repository having ODWA will not affect the ODWA data but the repository users will no longer be able to access ODWA.
ODWA Data
ODWA operates mainly on the data stored in the repository, although it also maintains some ODWA specific data. These data include details about ODWA Hotspots, ODWA graphic categories and ODWA search library. All the data captured by ODWA are stored in a set of tables in ODWA owner schema. Following is a comprehensive list of all such tables and details about data stored in them.
Table Name |
Description |
---|---|
ODWA_QUERY_LIBRARY | Contains data for all the saved queries |
ODWA_HOTSPOTS | Contains information about all the Hotspots defined for ODWA graphics |
ODWA_GRAPHICS | Contains the information about all ODWA graphic items |
ODWA_GRPH_CATEGORIES | Contains information about the various graphic categories defined in ODWA |
Migration to ROB
All the data contained in the ODWA tables can be migrated to ROB. ROB uses tables in the Repos owner schema with the same name and structure as that of ODWA owner tables to hold the ROB specific data. Hence migration of the hotspots and other saved query libraries from ODWA to ROB is an easier task. This can be accomplished with a simple SQL script that reads the ODWA tables listed above and inserts the data into ROB tables with the same name. For example the ODWA query library can be migrated by executing the following insert statement:
insert into REPOS.ODWA_QUERY_LIBRARY select ID, CATEGORY, LABEL, DESCRIPTION, PUBLISHED, OWNER, LAST_DATE_CHANGED, BASIC, ADVANCED, VERSION, AUDIT_TAB from ODWA.ODWA_QUERY_LIBRARY;
where "REPOS" is the repository owner schema and "ODWA" is the ODWA owner schema.
Only the tables listed in the previous topic need to be migrated in this manner, the other ODWA tables like ODWA_SESSIONS need not be migrated as they do not contain any data that is useful to ROB.
ODWA Preferences
While configuring ODWA, values for various preferences need to be inserted into the ODWA_PREFERENCES table manually, using SQL*Plus. ROB provides an easy-to-use web interface to manage all the preferences. Only Repos owner can change the preferences and this can be done by navigating to the "Manage Preferences" page under "Management facility".
Note: By default ROB does not support CDM objects like business rules, or CDM style reports. To expose these reports in ROB, set the preference "Enable Custom Development Method(CDM) objects" in the preferences page.
Problem
When you download a file whose name includes non-English characters, the file is saved with a name that is different to the original. The difference may include the loss of the file extension.
Workaround
In the download dialog, save the file with a name that comprises entirely English characters, then rename the saved file on the disk.
This section relates to the Process Modeler, Entity Relationship Diagrammer, Function Hierarchy Diagrammer, Dataflow Diagrammer and Design Editor tools.
Problem
If a Windows user that is not a member of the local 'Power Users' group or the 'Administrator' group attempts to invoke the Oracle Designer diagrammers, then an alert box will appear indicating 'failed to update registry'. The error is being raised because the user does not have permissions to allow Oracle Designer to write to the HKEY_CLASSES_ROOT registry key.
Workaround
Initially, press the OK button to dismiss the error message. The workaround is to add the Windows user(s) wishing to use Oracle Designer to the local 'Power Users' group or 'Administrator' group.
To copy a set of objects, keeping references between them, use Extended Copy.
If you copy a container using Edit > Copy, each object within the container is copied as a separate object. If two or more objects within the container refer to each other, the references are not updated to point to the new object in the new container, but still refer to the object in the original container, for example:
Application System ABC
Table DEPT
Table EMP
FK to DEPT
Copy ABC creating new application system XYZ
Application System XYZ
Table DEPT
Table EMP
FK to ABC.DEPT ( not XYZ.DEPT )
If you want to maintain the links (such that in this example the foreign key points to XYZ.DEPT), select all the objects in the container and then choose Utilities > Extended Copy.
Problem
When the syntax checker is run on application logic it may spuriously report errors. Two examples when this can occur are:
- when DECLARE appears before BEGIN. In this case you could remove the word DECLARE (leaving the variable declarations in place).
- when the application logic uses Forms built-ins such as FORMS_MDI_WINDOW or WINDOW_STATE. The syntax checker does not recognize these and states that they must be declared, however the Forms Builder environment does recognize them so the form will run correctly.
Workaround
None. In cases like these the best way to check that the application logic is working correctly is to generate the form and check that it works correctly.
Problem
Requerying application logic does not work. Thus for example, when editing a workarea to include an old version of a table, any application logic associated with the table is not requeried. If you edit the application logic, you may see a message to the effect that the logic is out of date.
Workaround
Do any of the following:
Problem
In the Repository Object Navigator, if you select a module, choose Utilities > Designer > Copy with New Language, select a language and click OK, the message "CDR-00114: Container context has not been set" is displayed.
Workaround
Run the utility from the Design Editor (choose Utilities > Copy with New Language).
Problem
Design capture of a persistent queue and corresponding queue table into a database user that has no queue table implementations may result in a CDA-02186 error during validation.
A database user must have a queue table implementation if a persistent queue implementation references the database user with its 'Queue Table Database User' property. Since these objects are put forward for validation in an undefined order following design capture, the database user may not have a queue table implementation when the persistent queue implementation is validated.
Workaround
Design capture the queue table(s) first then invoke design capture again for the persistent queue(s).
Problem
There are many reported problems using OLE to embed objects in Designer diagrams, or to embed Designer diagrams in other applications.
Note: Some extra exception handling has been added to the diagrammers to handle OLE errors during diagram open. This will enable some diagrams to be partially recovered, which would not have been possible in earlier releases.
Components Affected
CASEDE - Design Editor
CASEDFD - CASE Dataflow Diagrammer
CASEFHD - CASE Function Hierarchy Diagrammer
CASEERD - CASE Entity Relationship Diagrammer
CASEPM - CASE Process Modeler
Workaround
Use OLE sparingly.
Do not embed too many objects in Oracle Designer diagrams.
Use Edit > Paste, rather than Edit > Paste Special or Insert > Object if you wish to include a diagram
in (for example) a Microsoft Word document.
Problem
Descriptions and Labels may overlap when laid out by the Process Modeler.
Component Affected
CASEPM - CASE Process Modeler
Workaround
Manually move the overlapping text, or use shorter text if possible.
Problem
Invoke one of the Utilities under the Version menu.
Invoke a diagrammer if not already open.
Click on the Select Icon.
Drag a selection area over the diagram and you will notice that a horizontal and vertical line appears (as well
as the dotted selection area rectangle) This is common across all of the tools.
Components Affected
CASEDE - Design Editor
CASEDFD - CASE Dataflow Diagrammer
CASEFHD - CASE Function Hierarchy Diagrammer
CASEERD - CASE Entity Relationship Diagrammer
CASEPM - CASE Process Modeler
Workaround
Restart the tool.
Problem
When scaling a diagram on the Print dialog box, the diagram does not always print correctly.
Component Affected
CASEDFD - CASE Dataflow Diagrammer
CASEFHD - CASE Function Hierarchy Diagrammer
CASEERD - CASE Entity Relationship Diagrammer
Workaround
None
Problem
If you capture a large schema and display the results on a diagram, autolayout may be unable to resolve some overlaps.
Component Affected
CASEDE - Design Editor
Workaround
Capture the design without enabling Show Results on new Server Model Diagram (on the Source tab of the Capture Server Model from Database dialog box), then include the server model definitions on the diagram a few at a time.
Problem
You cannot generate Forms Menu Modules with the batch interface.
Component Affected
CASEDE - Design Editor
Workaround
Use the generator from within Design Editor.
Problem
There are a number of reported problems using a plotter (i.e. a vector device) as opposed to raster device (most printers).
Components Affected
CASEERD - CASE Entity Relationship Diagrammer
CASEDE - Design Editor
Workaround
Make sure you have the most up to date driver for your plotter. If the plotter driver supports raster to vector conversion, the results will be better. Avoid using custom colors in your diagram.
Problem
If a module component has two masters, layout can be poor.
Component Affected
CASEDE - Design Editor
Workaround
None.
Problem
Edit > Select All, followed by Best Fit Selection may result in the diagram becoming very small in the center of the current window.
Component Affected
CASEFHD - CASE Function Hierarchy Diagrammer
Workaround
Instead of Edit > Select All, choose Edit>Select and then Select All from within the dialog box. In this case the Best Fit works.
Problem
The Undo layout option is not always enabled until autolayout has been performed a number of times.
Component Affected
CASEDFD - CASE Dataflow Diagrammer
Workaround
None.
If a selected application system contains entities that you have mapped to views, these will be removed when the Database Design Transformer starts. You will be asked to confirm each removal with a dialog box which states that a table entity mapping will be removed.
Problem
Entity relationship diagrams become inaccessible if the Database Design Transformer is opened from the Entity Relationship Diagrammer.
Workaround
Do one of the following:
On generating a Form module, if Canvas/Item properties are inherited from object library even if they were set in Designer, you might encounter bug 3285507 (TAB PAGE CANVAS TOO BIG WHEN SUB COMPONENT WITH TAB STOPS USED). You must install Forms patch 3306045 after you have installed Oracle Forms/Reports patch release 3 (9.0.2.3).
A prerequisite for running generated forms within iDS or iAS is that JInitiator is installed on the client. The JInitiator software is available in your local Oracle Home: <Oracle_Home>\jinit\jinit[nnnn].exe
To run generated forms locally after an iDS installation:
The specified browser will display the form.
To run generated forms locally after an iAS installation:
The generated form will run in the web browser.
It is possible to model an item of type OCX Control or OLE Container, but these types are now generated as a text item. Warning message 39 is issued when such generation is attempted.
For Oracle Forms, restrictions have been added for some triggers. The following are now only permissible at form or block level:
WHEN-CLEAR-BLOCK
WHEN-CREATE-RECORD
WHEN-DATABASE-RECORD
WHEN-NEW-RECORD-INSTANCE
WHEN-REMOVE-RECORD
The following is now only permissible at form-level:
WHEN-NEW-FORM-INSTANCE
Previously it was acceptable to create these triggers additionally at block or item level. Although Designer still supports this at the design stage, you should not use this facility.
Although the number of characters allowed for object names in Oracle Designer is nominally 30, eight of these are required for the prefix that is added during generation. This means that the practical maximum number of characters for an object name is 22.
Menu substitution parameters are no longer supported by Oracle Forms. Because of this, Oracle Designer is unable to support generation of user-defined menu substitution parameters. From Oracle Designer 9i onwards, any user-defined menu parameter (e.g. <XX>) will simply appear in the menu's command line (e.g. :XX), with no run-time support. We recommend that you replace the use of these parameters with other code/methods for achieving the same results.
Generation preserving layout does not work with sub-components.
The Generator requires that the names of tables and their keys be unique within the first 21 characters. The table names are used to create names for program units, which are limited to 30 chars.
The generator prepends the following example text when naming program units to support various areas of functionality:
CGRI$CHK_table_name or CGRI$DEL_table_name
It is not possible to preserve layout when modifications are made because the inclusion and dimensions of one block affect the sequence and dimensions of the others. If a form with Blocks on Tabs is generated in preserve layout mode, it may not run correctly. An alternative is to modify the form by hand, capture the design back to the repository and generate again.
The standard object libraries shipped with Oracle Form Generator have not changed names between releases 6i and 9i/10g. A form generated with release 6i may not compile if compiled with the 9i/10g object library (and vice versa). This may cause confusion if a user has .FMB files generated from both these releases in one area.
The preferences ITMMPW (minimum permitted width) and ITMPPE (permitted percentage expansion) are now applied to block titles, so if they are set at module or module component level they may add extra room to existing titles potentially changing the layout.
During generation, Web PL/SQL Generator makes use of the WSGL PL/SQL library package of procedures, functions and constants. This package has been reconstructed to incorporate the new "Concealed data" display type and must be reinstalled if you want to use this facility.
The package specification file is wsgl.pks and the package body is wsgl.pkb. Both files appear in the CGENW61\CVWETC directory of your Oracle Designer installation and they must be installed on the PL/SQL Toolkit schema. Instructions are contained in the help topic "Setting up the PL/SQL Toolkit schema".
Problem
Error message PLS-00593 ("Default value of parameter P_REFRESH_URL in body must match that of specification") is displayed during the creation of WSG single sign-on packages.
Workaround
Manually change the default value of P_REFRESH_URL in WSGSSO.PKB to WSGSSO_CONSTANTS.G_CANCEL_URL, then rerun WSGSSO.SQL.
Even though the WSGSSO package provides SSO authentication to your WSG applications, the DAD used to access your generated applications should use "Basic Authentication" as its authentication mode.
This is because generated applications using the WSGSSO security package cooperate with the SSO server for authentication, but still use their own set of user and responsibility tables.
Note: For information on how to set up DADs, refer to the Oracle Application Server administration documentation.
When setting up Portal single sign-on (SSO) in an Oracle Application Server environment, you will need to specify a port number. This port number must be the one specified in the virtual hosts section of the HTTP server page of Oracle Enterprise Manager.
This port number will be required for the following:
Additionally, the Portal administrator, after creating the appropriate DAD, has to give the Web Agent URL with the correct port number to the Portal user.
Problem
You cannot generate reports from the batch generation tool if forms are also generated in the same batch.
Workaround
Generate Reports and Forms separately.
Currently there is a restriction imposed by the Report Generator on the module short name and implementation name which means they cannot contain any spaces. This causes generation to fail with the following error :
CGEN-03448 ERROR: Module: Name is not a valid Oracle name; try 'module_name'
where module_name is the name of the module without spaces.
The workaround is to make sure that the module short name and implementation name do not contain spaces.
The design capture tool does not support capturing of ORDER BY sequences where the syntax is based on a number relating to the item order in the select statement, e.g.:
select empno, deptno, job from emp order by 2;
Here the ORDER BY sequence is based on deptno; however it will not be recovered.
If the select statement is in the following syntax the ORDER BY information will be recovered:
select empno, deptno, job from emp order by deptno;
Report Generator includes a tag in a generated program unit to identify the repository element for which the event or named routine was defined. When capturing application logic, Report Generator uses this tag to associate application logic with the correct repository element.
If you modify or remove the tag and attempt to capture the application logic, Report Generator is unable to identify the repository element associated with the captured application logic. Report Generator therefore associates the captured application logic with a repository window definition.
If you intend to capture a generated program unit, do not modify or remove the tag embedded in generated program units.
Hint: If you intend to add user application logic using Report Builder, we recommend that you create a skeletal event code segment or named routine for the appropriate repository element. When you generate the report, Report Generator will generate the code and include a valid tag. You can then use Report Builder to modify the code. During design capture, Report Generator will capture the application logic and use the tag to assign it to the correct Repository element. If you do not define the application logic in the Repository to begin with, a valid tag will not exist and Report Generator will capture the application logic and associate it with the window definition.
You can modify generated application logic in Report Builder. To retain this modified application logic during subsequent generations, you must capture it into the repository. By default, Report Generator does not capture generated application logic unless you indicate that you have modified it.
To indicate that you have modified generated application logic, add one or more alpha-numeric characters (not a space) between the comment symbol (--) and the start of the generated tag.
For example, the line containing the generated tag might appear as follows:
-- CG$PV0001.5642752
To indicate that you have changed this application logic and that it is to be captured, you might change the tag as follows:
-- modified CG$PV0001.5642752
Problem
Up to Designer 2.1.2 you could apply header, body and trailer templates to Reports. However, because of the changed functionality of Oracle Reports 6.0 onwards you can no longer use templates on report headers and trailers.
Workaround
None.
Support for global temporary tables has been added to Oracle Designer. The following model changes have been made to support this feature:
You can find information about how to use this feature in the Oracle Designer online help.
Oracle Designer allows you to model many sophisticated database features. However, not all of these can be implemented in every database type. If you generate a feature that is not supported by your chosen database type, you will see an error message.
Oracle Database does not allow the default value for a column to be derived from a user-defined function. In the Design Editor, if you create a table with such a column, the table is created without any apparent error, but while generating the design to the database, the generator fails, stating that user-defined functions are not allowed as default values.
To connect to Microsoft SQL Server 7.0, use the Microsoft SQL Server ODBC driver that is supplied with the SQL Server 7.0 client software. (Server Generator has been tested with SQLSVR32.DLL version 3.70.06.23).
When specifying the logon details for an IBM DB2/MVS v5 ODBC connection, the username must be entered in uppercase to be able to see any objects for a server model capture. (Bug 1314224 refers.)
When connecting to DB2/MVS v5, use the IBM DB2 ODBC driver to connect. (Bug 1314307 refers.)
Server Generator provides connections to online databases using either ODBC or the Oracle Network layer.
During testing it has been found that using an old driver designed for an earlier version of an RDBMS can produce unpredictable behavior, such as a failure to recognize legitimate types or syntactic constructs introduced with the newer RDBMS.
We recommend that you obtain ODBC drivers for non Oracle databases from either the database provider or a specialist supplier.
A patch from Sybase (ref. EBF 7704) must be applied to Sybase clients before attempting access to Sybase System 11 databases for generation or capture. If this patch is not applied, the Design Editor can terminate unexpectedly.
Problem
Server Generator does not generate synonyms that reference objects across database links. Therefore the Generate Distributed Capability check box on the Database Generator Options dialog box has no effect.
Workaround
None.
Problem
Server Generator does not generate code for Master Replication Groups or Replicated Groups. Therefore the Generate Replication Statements check box on the Generate Database Administration Objects dialog box, and the Assign Objects to Replication Code check box on the Database Generator Options dialog box, have no effect.
Workaround
None.
Problem
The same server diagram can be open any number of times in the server diagrammer in the Design Editor.
Workaround
Open each diagram only once.
The following situations are all resolved by explicitly setting the default date format to 'DD-MON-YYYY'. To do so, choose Options > General Settings in the Design Editor or Repository Object Navigator and enter this value in the Date Format field.
When you try to start the VHV from a matrix diagram the first time, the following error is displayed:
CDR-03103: Attempted Diff/Merge but ran out of memory.
The workaround is to invoke the VHV from elsewhere in Designer.
Using Matrix Diagrammer, you cannot create, update, delete or version containers, workareas or configurations. Also, you cannot create or delete configuration memberships between elements and configurations.
The workaround is to use the Repository Object Navigator to perform these operations.
When the intersection is a foreign key, for example if you select Table Definition vs Relational Definition, the Matrix Diagrammer GPFs. It works correctly when the intersection is not a foreign key.
Oracle Designer supports version 3.7 of the JAWS reading software.
For the Dependency Manager, Version History Viewer and Version Event Viewer to run under JAWS, you must download and use Java Access Bridge version 1.0.3 for Windows.
In Microsoft Windows 2000, mnemonics (the underscores that indicate a shortcut) do not appear in a dialog or menu in Oracle Designer until the ALT key has been pressed. (See also bugs 1522303 and 1962540. )
Problem
There is limited keyboard access to generated navigation action items.
Workaround
Set the focus on action items by using the menu option Block > Next. Then press enter to select.
Problem
When using the Repository Reports navigator, and when the focus is moved between different nodes, JAWS sometimes reads out inappropriate prose.
Workaround
This problem will not occur if the navigator is not accessed using the mouse.
Problem
When using the navigator in the Design Editor, pressing INSERT+UP ARROW sometimes causes JAWS to behave inappropriately.
Workaround
This problem will not occur if the navigator is not accessed using the mouse.
Problem
The following error has been reported during the migration process, during the stage CK_UPGRADE_MOD:
ORA-02063: preceding 2 lines from R212 .. RME-02124 Failed to execute SQL statement: begin ck_upgrade_mod.init(:b1,b2); end;
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 set up correctly (see below).
Workaround
If such an error occurs it may be as a result of insufficient open cursors setting on the source Designer 6.0
instance.
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):
SQL> select NAME, VALUE 2 from V$PARAMETER 3 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:
SQL> show parameter open_cursors NAME TYPE VALUE ------------- ----------- ------- open_cursors integer 50
Please refer to the install guide for your Designer 6.0 instance, chapter 2. Depending on your hardware environment
you must at least be using the minimum recommended settings for open_cursors. For example on a PC, open_cursors=400
is recommended as a minimum. To apply the change you must shutdown and restart the instance. If this does not resolve
the problem please contact Oracle support.
Other parameters and recommended settings:
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 6i/9i (migration
target instance).
Problem
When migrating to a Release 9.0.2 or 9.0.4 repository, an attempt to migrate a user-extended element with a name that is reserved in 9i (e.g. "Project") results in the following warning message:
Skipping insert of Element element_ID because ..... Duplicate Plural Name
Workaround
A workaround is available but please contact your Oracle Support representative for assistance with this.
Problem
When migrating Designer 6.0 data to a later Designer repository on a multibyte database, the text property 'PL/SQL Block' is not migrated correctly for PL/SQL definitions of type PACKAGE. No error message will be displayed but, after migration, any text in the 'PL/SQL Block' property will have been moved into its 'Private Declaration' property.
This bug is a duplicate of bug 2641774, which is in the process of being fixed.
Workaround
None.
Problem
Unable to invoke a SCM Java tool when connected to a repository on an Oracle9i server. This problem can be encountered when trying to invoke any of the SCM Java tools, which are:
The failure to invoke a Java tool may occur in the following ways:
1 | Problem: Java application does not invoke This occurs when invoking the Command Line Tool from a short cut or from the Repository Object Navigator |
2 | Problem: [JDK2] No message error at ...RepositoryConnection.setConnection(RepositoryConnection.java:608) This occurs when trying to use the 'connect' command from the Command Line Tool |
3 | Problem: java.lang.IllegalArgumentException : ErrorDialog: null message vector This occurs when running the Dependency Manager (ckdm61) from the DOS command prompt |
4 | Problem: CDR-03120 : Internal Error - Problem making a Repository Connection This occurs when invoking the VHV, VEV or Compare Utility from the Repository Object Navigator |
5 | 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.
Workaround
Ensure that the connect string passed to the JDBC driver is not in the range 184 - 192 characters. There are many environmental factors that affect the length of this string, for example:
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:
Problem
On Oracle 8.1.7 systems during upgrade, the stage CKREPINI may 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
Workaround
Apply server patch 1408453, taking care to download the patch specific to your database version. Once the server has been patched, run 'Full Reconcile' from the Repository Administration Utility. This will rerun the stage CKREPINI, which will now succeed.
Problem
In previous releases of the Repository Administration Utility, subordinate users were able to perform migration as well as the repository owner. This has now been changed so that, by default, only the repository owner can run the Migration utility. However, some sites may still wish to allow subordinate users to perform migration.
Workaround
In the Repository Administration Utility, the repository owner can explicitly grant a subordinate user access to the Migration utility by enabling the "Migration Utility (RAU)" checkbox on the Repository User Properties dialog for that user.
Problem
In the Repository Administration Utility, no reminder is displayed about performing a full reconcile after remapping an existing user-extended element type.
Workaround
Always perform a full reconcile after remapping a user-extended element type.
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.
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.
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
Key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEn\REPADM61
JVM_NATIVE_STACK_SIZE
JVM_JAVA_STACK_SIZE
Key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEn\REPADM61\DEFAULT_JVM_PARAMS_THIN_JDBC
JVM_MIN_HEAP_SIZE
JVM_MAX_HEAP_SIZE
(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.
Problem
In the Repository Object Navigator, the default rule in the file registry is Text File for files with .DOC or .doc extensions, but on Win32 systems these extensions are most likely to be used for MS Word files, which are binary.
Workaround
From the Utilities menu, choose Edit File Registry and use the Edit Rule option to change the rule to Binary File for files with these extensions.
Problem
If you are using the Repository Object Navigator and are connected to a repository on the default database of the local machine (i.e. connected as repos/manager with no connect identifier specified), you will not be able to invoke the VHV, VEV, Dependency Manager and Compare utilities. The following error will be displayed:
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 machine you will get a Java error.
Workaround
Connect to the repository on the default database of the local machine by specifying a Net8 alias e.g. repos/manager@local, where local has been set up as an alias or Net8 connect identifier for the local database by Net8 Configuration.
Problem
In the Repository Object Navigator, the import of an application system may fail with an error indicating that conflicts have been detected between user extensions exported from the source repository and the target repository, and that these must be resolved before import can proceed.
Workaround
Using the Repository Administration Utility, extract the user extension definitions from the source repository and load them into the target repository. The import of the application system in the Repository Object Navigator should now work.
Problem
When invoking the VHV for a configuration in the Repository Object Navigator, the dialog 'Set Context Workarea' may be displayed and the Repository Object Navigator hangs.
Workaround
Before invoking the VHV for a configuration, invoke the VHV for any other object and then close it. Now, invoking the VHV for a configuration will work.
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.
Problem
If using a repository on an Oracle9i server, attempting to copy an ORACLE_DATABASE Designer element can result in the following error.
PLS-00123: program too large
Workaround
There is currently no workaround for a repository on an Oracle9i server.
Different file handling rules can be set for any particular file type (pattern) depending on the operating system on which the Oracle SCM client is running. (This is done in the RON, by clicking on the menu option "Utilities > Edit File Registry" to invoke the "Edit File Registry" dialog.) For each rule you can set the platform type to "All", "Win32", or "Unix". If you set the platform type to "Unix" for a particular rule then the Windows release of Oracle SCM will ignore this rule and continue scanning the rule set for a matching rule (one that matches both file pattern and platform). If no matching rule is found then the file is assumed to be a binary file and you will not be able to run the diff/merge utility.
For the existing Windows implementation of Oracle SCM it makes no sense to set the platform type to "Unix"; please set the platform type to "All" or "Win32".
The diff/merge utilities running on the Windows platform handle text files (files that match the file pattern and the platform - "All" or "Win32" - and for which the rule has been set to "text") regardless of whether the line terminator is MS-DOS style (Carriage Return and Line Feed) or unix style (Line Feed). Both the file "download" and "map folder to file system" operations have options to enable translation between MS-DOS and UNIX file formats for text files. See also bug 3457436 "Merging converts Unix end-of-line characters <LF> to Windows ones <CR><LF>."
If the Compare Utility fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
If the Compare utility has been invoked from the Command Line Tool, it may hang after a compare of Oracle Forms files.
Workaround
Invoke the Compare utility from the Repository Object Navigator instead of from the Command Line Tool and this problem will not occur.
Problem
When the Compare utility is invoked from the Repository Object Navigator, a program failure can occur if the Compare window is maximized, the window divide bar is moved and then the close button (x) at the top right is pressed.
Workaround
Invoke the Compare utility from the Version History Viewer or the Command Line Tool and this problem does not occur. Alternatively, if invoked from the Repository Object Navigator, do not maximize the Compare window.
Problem
In the Repository Object Navigator or Version History Viewer, an attempt to compare or merge a generated .FMB file that has already been merged may fail. Messages from the Repository Object Navigator are:
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:
java.lang.IllegalStateException
Workaround
None.
Problem
The Compare utility cannot compare versions of a subclassed form that are in the same workarea or configuration. In addition, rather than reporting an error, the utility sometimes appears to have successfully compared the versions of the subclassed form.
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.
This warning can be turned off by adding a string value to the registry key:
HKEY_CURRENT_USER\SOFTWARE\ORACLE\REPOS61\FORMSDM
Create a string value "SUBCLASS_WARNING" with value "FALSE". Any other value (or the string not existing) results in the warning being displayed.
Workaround
Any compare of a subclassed form must be carried out on versions that are in different workareas or configurations.
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.
If Merge fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
If the Merge window has been invoked from the Command Line Tool, it may hang after a merge of Oracle Forms files.
Workaround
Invoke the Merge window from the Repository Object Navigator instead of from the Command Line Tool and this problem will not occur.
After making changes, use File > Save to save your changes. (N.B. Earlier versions had a 'Save' button' which did this).
If the Version History Viewer fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
Date appears as DD-MON-YY, where DD and YY are both corrupted. Occurs only when the Version Event Viewer is called from either the Command Line Tool, or the Design Editor, in a Japanese environment, before the RON has been invoked.
(Also occurs for any client configured to use a NLS language other than the default "US").
Workaround
1.Invoke the RON
2.Navigate to the General Settings panel (Options -> General Settings)
3.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.
If the Version Event Viewer fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
Running the Version Event Viewer with a start date in which the year is set to 99 or earlier causes no event data to be displayed in the viewer window.
Workaround
None.
Problem
Importing into a workarea or refreshing a workarea can fail with the following error:
CDR-01062: Compilation leaves file filename 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.
Workaround
Restore the deleted folder from the Wastebasket. Invoke the Command Line Tool and reattach the shared object from the Lost+Found container. The shared object will now be seen as an original object and can be deleted causing no further problems
Problem
This occurs when exporting from an Oracle9i 9.0.1 database and the user has insufficient privileges. Users with DBA privilege or any of those shown in the given workaround will not encounter this problem. (This is fixed in Oracle9i 9.2.)
Workaround
Grant any of the following:
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;
Problem
When importing a workarea containing versioned objects into the same repository using the option 'Create new version where objects exist in the destination repository, otherwise create new objects', the import will fail if you try and create a new workarea by specifying a new workarea name in the wizard.
Workaround
Create a new workarea with the relevant name before you run the Import Wizard.
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.
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, e.g.
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.
The dependency analyzer should be run on a ProC (.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 ProC file.
If the dependency analyzer is run on a C file generated by the ProC compiler, then it is likely that the analyzer will fail. This is because the dialect of C generated by the ProC 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 ProC 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 ProC file itself must be analyzed.
If the Dependency Manager fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
Running a purge from the Dependency Manager fails because of lack of extents for rollback segment.
Workaround
Force dependency purge to use suitably sized rollback segment; only one rollback segment (of sufficient size) needs to be available. You can achieve this by making all rollback segments offline except for one large rollback segment. See the Oracle SCM Repository Installation Guide for instructions to do this.
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 a
set match_case off
command, may degrade performance in larger repositories.
If the Command Line Tool fails to invoke, this may be as a result of a common problem shared by other SCM Java tools. The full problem description and workaround can be found at the beginning of this section.
Problem
When attempting to exit from a long running command, CTRL-C not only terminates the command that is running but also the Command Line Tool. All outstanding uncommitted changes will be lost.
Workaround
Do not use CTRL-C unless you want to terminate the command line session completely and you are not concerned about any changes that have not been committed.
Problem
Users are unable to import into a new repository.
Workaround
An export needs to be run first on all new repositories so that certain tables will be created to allow an import to complete. Once the initial export is run, the missing tables will be created.
The broadcast server does not work on Solaris systems (bug 1325598).
The API and Model Reference Guide is available on the Oracle Technology Network (OTN) at http://otn.oracle.com. From the navigator frame on the left of the OTN screen, choose Documentation > Oracle9iSCM (Repository) > Repository API and Model Reference Guide.sdsd
In some circumstances message ORA-12514 is displayed without its intended text.
Intended text of message
ORA-12514 : TNS:listener could not resolve SERVICE_NAME given in connect descriptor
Cause
The SERVICE_NAME in the CONNECT_DATA was not found in the listener's tables.
Action
Check to make sure that the SERVICE_NAME specified is correct.
Comment
This error will be returned if the database instance has not registered with the listener; the instance may need to be started.
If you wish to export any repository data, you must install and use the appropriate version of the Oracle 8i Import and Export utilities (IMP & EXP) against your repository. That is, you must use the 8.1.6 utilities for an 8.1.6 database and the 8.1.7 utilities for an 8.1.7 database. These utilities must not be installed into the same Oracle home as Oracle Repository.
In some circumstances, you may not be able to get an instance of the Form Builder tool running from the Design Editor. For example, if you click on the action item list, after generation of a form, and choose the option to run Form Builder, nothing happens, i.e. the Form Builder tool does not open.
In this case, you should change the following entry in the registry file from:
HKEY_CLASSES_ROOT\CLSID\{4271DF00-B54A-11CF-864B-0020AF1D40D7}\LocalServer32 ifbld90.exe /AUTOMATION
to
HKEY_CLASSES_ROOT\CLSID\{4271DF00-B54A-11CF-864B-0020AF1D40D7}\LocalServer32 <ORACLE_HOME>\ifbld90.exe /AUTOMATION
After generating a form in a non-English Oracle Designer environment, you will need to compile and run the form externally using Oracle Developer.
Oracle Designer can be run under SVGA (recommended) or VGA.
We recommend that you set the system font size to Small Fonts (Control Panel > Display > Settings > Font Size).
It is possible to create instances of elements with names that are SQL or PL/SQL reserved words. Users should beware of this where these element names are likely to be used in SQL or PL/SQL statements. Also, if a systems modeling element is created with a name that is a SQL or PL/SQL reserved word, it may not be possible to transform it into a systems design element.
The SCM Java based tools, which include: Version History Viewer; Version Event Viewer; Dependency Manager; and 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.
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 behaviour.
Problem
If you create a configuration based on the current contents of a workarea, the configuration will consist of the entire contents of the workarea, possibly including objects to which you do not have access.
Workaround
Either manually remove the inaccessible objects from the configuration (e.g. Remove Members in the Configuration Wizard) or create the configuration based on the workarea specification rather than the workarea contents (e.g. use "from specification" in the Configuration Wizard rather than "from current contents").
Problem
Creating or updating a workarea will fail if a workarea specification is used, whose text exceeds 30K
i) It may fail with 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;
or
ii) 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.
Workaround
Create a configuration and use it to identify the member versions and then base a workarea on this configuration.
Problem
This applies when building a workarea based only on a configuration and with no check-in branch specified. If you use the workarea to check out and check in an object, the object now exists at the revised version. If you attempt to revert to the original object version by refreshing the workarea, the object disappears from the workarea completely rather than existing at its original version.
Workaround
None.
Problem
It is possible to create multiple identical objects in the same container without raising a uniqueness violation. An object can be created in a container in the context of one workarea and an identical object (e.g. with the same name in the same container) in the context of another workarea. If a workarea is created (or recompiled) which includes both objects (for example by including all objects within the container), the name uniqueness rules are violated without an error being raised.
Workaround
Manually perform name uniqueness check after workarea compilation.
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 .RVI files.
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:
ORA-00959: tablespace 'tablespace_name' 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.
This unexpected behaviour is not known to cause any problems.
Problem
If the database that is hosting the new instance is created with a multi-byte character set and this is different to that of the database hosting the existing 6.0 instance, it is possible that during migration errors will occur because character data has become too big. For example, if the 6.0 repository used a character set of WE8ISO8859P1 but the target database uses UTF8, characters in the range 128-255 will go from requiring 1 byte to 2 bytes to hold them. This would include all the none ASCII characters. If an object in the repository had a name that included such a character, and the name was already the maximum length for the column definition in which it was stored, the migrated data becomes too large and raises an error during migration when it is attempted to be inserted into the new repository.
Workaround
Follow Oracle's recommendations for changing the character set of the 6.0 repository database before attempting to migrate.
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.
|
|
|