| Release Notes for Oracle Designer and Oracle Designer Repository |
Section 3 of 4
|
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 existthen 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.
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;"
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
| Installation, Patch Sets and Upgrades | Migration |
To read the support note:
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.
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:
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).
While upgrading the repository, the RAU replaces any ODWA objects in the repository schema with ROB ones (if ODWA is installed into the repository owner schema), but it does not recreate the synonyms created for subordinate users. The synonyms will point to the ODWA objects only.
If ODWA has been installed into the repository owner schema, no action need be taken about the synonyms. If ODWA has been installed in a schema other than the repository owner, the synonyms (public or private) created for ODWA should be dropped before the upgrade process. The list of synonyms created for ODWA can be obtained from the files "privsyn.sql" or "pubsyn.sql" under the "ins" folder in the ODWA installation.
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.
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.
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.
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.
When the syntax checker is run on application logic it may spuriously report errors. Two examples when this can occur are:
Workaround
- 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.
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.
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:
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).
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).
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.
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.
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.
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
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.
You cannot generate Forms Menu Modules with the batch interface.
Component Affected
CASEDE - Design Editor
Workaround
Use the generator from within Design Editor.
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.
If a module component has two masters, layout can be poor.
Component Affected
CASEDE - Design Editor
Workaround
None.
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.
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.
Entity relationship diagrams become inaccessible if the Database Design Transformer is opened from the Entity Relationship Diagrammer.
Workaround
Do one of the following:
To run generated forms locally after an iDS installation:
To run generated forms locally after an iAS installation:
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.
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
Symptoms: Packages WSGL.pks, WSGJSL.pks becomes invalid after installing NLS specific WSGLM<nls>.pks packages e.g.WSGLMNL.pks, WSGLMDK.pks
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 some bug fixes.
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".
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.
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.
This port number will be required for the following:
You cannot generate reports from the batch generation tool if forms are also generated in the same batch.
Workaround
Generate Reports and Forms separately.
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.
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;
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.
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.5642752To 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
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.
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.
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.
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.
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.
CDR-03103: Attempted Diff/Merge but ran out of memory.The workaround is to invoke the VHV from elsewhere in Designer.
The workaround is to use the Repository Object Navigator to perform these operations.
Note:
Java Access Bridge 1.2 cannot read Java components because if a java window is launched by a C application using JNI, then AccessBridge and JAWS cannot work with this window.
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.
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.
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.
The following error has been reported during the migration process, during the stage CK_UPGRADE_MOD:
Note, It is also possible that other similar errors may also occur at different stages of the migration process.ORA-02063: preceding 2 lines from R212 .. RME-02124 Failed to execute SQL statement: begin ck_upgrade_mod.init(:b1,b2); end;
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):
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> select NAME, VALUE 2 from V$PARAMETER 3 where upper(NAME) like 'OPEN_CURSORS' / NAME VALUE ------------ ------- open_cursors 50
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
Oracle Designer Repository 6i/9i (migration target instance).
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 NameWorkaround
A workaround is available but please contact your Oracle Support representative
for assistance with this.
None.
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 ORACLEWorkaround
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.
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.
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.
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_SIZEKey HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEn\REPADM61\DEFAULT_JVM_PARAMS_THIN_JDBC
JVM_JAVA_STACK_SIZE
JVM_MIN_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):
JVM_MAX_HEAP_SIZE
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.
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.
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:
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.CDR-03120 : Internal Error - Problem making a repository connection.
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.
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.
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.
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 largeWorkaround
There is currently no workaround for a repository on an Oracle9i server.
For the existing Windows implementation of Oracle Designer Repository 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>."
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.
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:
The message from the Version History Viewer for either compare or merge is:CDR-03100: Diff/Merge internal error: java.lang.IllegalStateException (compare) CDR-03126: Internal Error - Object Delta retrieval (merge)
Workaroundjava.lang.IllegalStateException
None.
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\FORMSDMCreate 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.
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.
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.
Importing into a workarea or refreshing a workarea can fail with the following error:
CDR-01062: Compilation leaves file filename orphaned. Need to include containerThis 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
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;
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.
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.
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.
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.
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 Designer Repository Installation Guide for instructions to do this.
command, may degrade performance in larger repositories.set match_case off
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.
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.
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.
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
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").
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.
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.
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.
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:ORA-00959: tablespace 'tablespace_name' does not exist
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.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
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.
For information about automatic version labelling, refer to the online documentation.
By default, the network traffic between the Designer client and the Repository is not encrypted. For a fully secure connection, the security features of the Oracle database must be configured appropriately.
|
Copyright © 2007, Oracle. All Rights Reserved. |