Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Known and Resolved Issues In Release 10.3

This chapter describes known problems in Oracle Enterprise Repository 10.3, as well as issues found in earlier versions that are now resolved in 10.3. Entries include a description of the problem, and a workaround or solution where appropriate.

For instructions on installing Oracle Enterprise Repository, see Oracle Enterprise Repository Installation Guide.

For additional information about the new features and capabilities of Oracle Enterprise Repository, see What’s New in Oracle Enterprise Repository 10.3.

 

Known Issues

The following section describes issues that were found in Oracle Enterprise Repository 10.3. Entries include a description of the issue, and a workaround or solution where appropriate.

Tracking Number
Description and Workaround
CR361307
Oracle Service Bus currently generates WSDLs that incorrectly import XSD using the WSDL import element. This causes a problem in the AquaLogic suite due to the fact that these Oracle Service Bus WSDLs can be parsed and submitted to Oracle Enterprise Repository properly by the AquaLogic common Eclipse tooling; however, the Oracle Registry Repository Exchange Utility is not capable of parsing the WSDLs when migrating them back to Oracle Service Registry.
Workaround or Solution:
For more information, including an example of the proper usage of the XSD import element to import XSD, see the Oracle Enterprise Repository Oracle Registry Repository Exchange Utility manual
CR336712
XSLT parsing does not function correctly in WebSphere installations.
Workaround or Solution:
WebSphere installations require the following additional JVM parameter in the same location as -Xverify:none:

-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault

CR334183
The installer fails during database installation on HP-UX Itanium 11i v2.
Workaround or Solution:
Run the database wizard after installation.
CR333239
The SetOperator of Searchterm in the REX API is not sensitive to case and may return more search values than expected.
Workaround or Solution:
None.
CR337340
Oracle Workshop for WebLogic cannot authenticate to the repository when Oracle Enterprise Repository is configured for J2EE container authentication.
Workaround or Solution:
None.
CR337317
Oracle Workshop for WebLogic cannot authenticate to the repository when Oracle Enterprise Repository is configured for SSO authentication.
Workaround or Solution:
None.
CR338241, CR337545
When Oracle Enterprise Repository is deployed on IBM WebSphere 6.x and if Oracle Enterprise Repository Event Manager is enabled, the embedded Apache ActiveMQ JMS Server cannot be used due to conflicts in the classes used by ActiveMQ and Oracle Enterprise Repository.
Workaround or Solution:
The WebSphere 6.x customers can use the JMS server that comes with IBM WebSphere 6.x.
CR339154
There is a limitation when configuring the embedded ActiveMQ JMS Server to use MS SQL Server since this database is not supported by ActiveMQ.
Workaround or Solution:
Use the file system to store messages or use an external JMS Provider. When Oracle Enterprise Repository is configured in a cluster, it is important to configure ActiveMQ to use a database to store messages, and due to this limitation, MS SQL user must use an external JMS server in a clustered environment.
CR339155
When publishing JMS messages to IBM WebSphere, the Oracle Enterprise Repository Event Manager will not set the JMS Client ID due to J2EE threading restrictions in setting the ClientID within a Web container.
Workaround or Solution:
For more information, see http://www.ibm.com/developerworks/library/j-getmess/
CR338849
When uninstalling the Oracle Enterprise Repository plug-ins for Eclipse, Oracle Workshop for WebLogic will also be removed if Oracle Workshop for WebLogic was installed by the Oracle Enterprise Repository installer. This may not be desirable if other plug-ins were added to Oracle Workshop for WebLogic.
Workaround or Solution:
To avoid uninstalling additional Oracle Workshop for WebLogic plug-ins, deselect the ALER Plug-ins for Eclipse from the list of components to uninstall.
CR338212
The XSLT viewer in the Oracle Enterprise Repository Asset Editor requires the equivalent of a client side JRE version of 1.5.0_09 or later.
CR337596
Project submissions may fail with a Enterprise Repository Connection Busy error when you attempt to re-submit a project within a short time of the initial submission and your submission is in the same Eclipse session and the initial submission is still in progress.
Workaround or Solution:
If the operation fails, close the current Eclipse session and restart. After Eclipse restarts, the operation will succeed.
CR339815
Creating a RAW_SCM with a downloadUri that includes & chars causes the Artifact Store to fail to appear in the list of available stores when creating a new file.
Workaround or Solution:
You must manually 'xml escape' characters. For example, replace & with &
CR339175
Oracle Enterprise Repository creates an Microsoft Excel a spreadsheet for every asset type of an asset being exported. Many Oracle Enterprise Repository asset types use special characters, such as a colon (:) which cause Excel to throw an error message and the Tab name, which should be the asset type name, no longer matches the asset type
Workaround or Solution:
Rename the tabs after the export to Excel so that they match the asset types in Oracle Enterprise Repository.
CR339842
Manually replacing 'xml escape' characters, such as replacing & with &amp prevents downloading of ClearCase ccWeb content. See CR339815.
Workaround or Solution:
Use a RAW_SCM that accesses ClearCase using the Oracle Enterprise Repository file store mechanism.
CR339633
Application server using SUN JDK crashes or throws an out of memory exception.
Workaround or Solution:
Add the following to JAVA_OPTS:
-XX:NewSize=128m -XX:MaxPermSize=128m
CR339336
When an Asset is opened, edited in the Asset Editor, and the Advanced Registration Flow processes the asset in the background, the merge capability is not supported by Oracle Enterprise Repository.
Workaround or Solution:
Revert the changes made within the Asset Editor or lose the changes made by the Advanced Registration Flow.You can reduce the probability of this issue occurring by increasing the Event Manager Sleep time to a large value so that the Events are emitted and processed when the traffic to Oracle Enterprise Repository is low.
CR339632
When an Asset is submitted using the Quick Submit feature, there is an issue in processing that asset by the Advanced Registration Flow when:
  • The Asset is opened in the Asset Editor by a Registrar before the Advanced Registration Flow accepts the asset
  • Advanced Registration Flow accepts the asset
  • Registrar accepts the asset and is not aware that the Advanced Registration Flow has accepted the asset as the Asset page has not refreshed
  • The Asset Editor updates to show that Advanced Registration Flow has accepted the asset
This creates a duplicate asset entry in the Asset Editor tree and the Advanced Registration Flow has issues executing the multi-tier approval process.
Workaround or Solution:
When an asset enters into this condition, manually unaccept and then accept the asset.
CR334366, CR335077
In Oracle Workshop for WebLogic, submitting an assembly model to Oracle Enterprise Repository may prevent users from also performing other operations in parallel, such as performing a search, before the submission is completed.
Workaround or Solution:
Avoid performing multiple operations when submitting assembly models.
CR329907
In Oracle Workshop for WebLogic, you cannot store and retrieve binary artifacts, such Word docs and JPEG files, for assembly models.
Workaround or Solution:
None.
CR348052
When running the java process during the upgrade installation, larger data sets may run into JVM memory constraints.
Workaround or Solution:
If “out of memory” errors occur while running the migrate.sh or migrate.bat process, increase the memory as follows:
  1. Open the r4.bat/r4.sh file.
  2. Increase the memory by increasing the java -mx192m setting (e.g., java -mx1024m).
  3. Save the changes.
  4. Re-run the migrate.sh or migrate.bat process.
CR348053
When upgrading to Oracle Enterprise Repository 10.3, importing larger data sets may cause available memory issues when running the Import/Export tool.
Workaround or Solution:
Save the impexp.jnlp file locally, and then edit it to increase the default max-heap-size amount to better accommodate the size of the data sets being imported. If the machine importing the data sets has enough available memory, set the max-heap-size as follows:
<j2se version="1.5" max-heap-size="1024m"/>
CR377485
When you download Oracle Enterprise Repository assets that were harvested by the Harvester client, any dependent artifacts that are referenced via a remote URL will not be included in the download artifact bundle.
CR376029
Do not delete all of the out-of-the-box Asset Types using the Asset Editor and then attempt to create a new Asset Type.
Workaround or Solution:
At least one Asset Type must exist in the system, or you will not be able to create a new Asset Type in the Asset Editor.
CR376257
Sometimes Visual Studio .NET does not properly reset the toolbars and menu items of a previously installed add in, so it appears that rebranded items have not been rebranded.
Workaround or Solution:
To reset the menu items, run devenv /setup.
Or perform these following steps:
  1. Close all Visual Studio instances.
  2. Open a command line console with Visual Studio settings (for example, a Visual Studio 2005 Command Prompt from the Start menu) and type:

    3. devenv /resetaddin *

If the above does not work, then try the following commands. Note that these commands will delete all customization done to Visual Studio, such as keyboard mappings.
devenv /resetsettings
devenv /resetaddin *
CR377488
Using the getRelationshipTypes() method of the REX Asset object to return every relationship type is not recommended and in a future release may no longer be supported.
Workaround or Solution:
If users want every single relationship type in the system, then they would be better served by calling:
RelationshipTypeCriteria criteria = new RelationshipTypeCriteria();
criteria.setNameCriteria('');
RelationshipType[] mRelationshipTypes =
flashlineRegistry.relationshipTypeQuery(authToken, criteria);
CR380933
When downloading a sample artifact bundle using download to client in Oracle Enterprise Repository, it should treat the XSDs different if they are present in different relative paths in that artifact bundle. But, in Oracle Enterprise Repository 10.3, only one XSD is downloaded and the reference to the other XSD is not resolved. This is not a desired behaviour.
Workaround or Solution:
None.
CR380926
Download bundle of WSDL/BPEL (SOA) assets from Oracle Enterprise Repository is not working consistent across the User Interfaces such as WebUI v/s ALSync(Eclipse Tooling/SB Workspace). For example, the following scenarios will result in unexpected results:
Case 1: When a Harvested Artifact asset has reference to remote or absolute file URLs artifact assets.
Case 2: When a Harvested Artifact asset has reference to same XSD schema multiple times in same WSDL, which is located in diffrent relative paths.
See CR380933.
Workaround or Solution:
None.
CR377226
When the application server and the database are in different timezones, the date fields in the audit log and in the usages window show the time from the database appended with the time zone information from the application server.
Workaround or Solution:
When the servers are in different time zones, user should modify the 'Long Date Format Specification' parameter (cmee.server.date.format.long.default) in the system settings to not include the time zone in the display. This can be accomplished by removing the 'z' at the end of the default setting, which is 'yyyy-MM-dd HH:mm:ss z'.
CR380318
Before logging in to the Oracle Enterprise Repository using any supported browsers (Internet Explorer & FireFox), users should enable the cookies for the Oracle Enterprise Repository application to work correctly.' If cookies are not enabled on the browser, then the login to the Oracle Enterprise Repository application fails.
Workaround or Solution:
    1. In the browser, check the Accept Cookies from Sites option.
    2. Open the Oracle Enterprise Repository URL in the browser.
    3. Log in using the username/password credentials. The Oracle Enterprise Repository Home page opens.

 

Changes and Resolved Issues for 10.3

The following section describes changes and issues that were found in earlier Oracle Enterprise Repository releases and are resolved in release 10.3.

Change Request Number
Description
CR339520
In previous releases, the Advanced Search field Model Producing Product searched over the product name, not the product name and version. When search results were returned, the results table showed both the Name and Version together.
In Oracle Enterprise Repository 10.3, this problem is fixed.
CR377511
In previous releases, there was a bug that enabled users to add a note to a retired asset.
In Oracle Enterprise Repository release 10.3, retired assets are frozen, so that no changes can be made to a retired asset until the asset’s status is changed to Active in the Asset Editor.
CR377941
The Oracle Registry Repository Exchange Utility imports the Endpoint: Web Service asset type. In the import file, the Endpoint is associated with UUID 1b38de40-7048-11dc-b72a-f7dea4420b44. The import bundle is not configured to preserve UUIDs so import will randomly create a new UUID for this asset type for every customer.
The Harvester expects this asset type, which will be delivered in the new SOA/BPM Suite Solution Pack.
The result is that anyone installing the Registry Repository Exchange Utility Solution Pack in the future will ALWAYS duplicate the Endpoint: Web Service asset type and Oracle Registry Repository Exchange Utility endpoints will not live alongside Harvested Endpoints.
The UUID of the Endpoint: Web Service should be 1b38de40-7048-11dc-b72a-f7dea4420b44. The asset type is loaded by importing the Registry Repository Exchange Utility Solution Pack. The Solution Pack was not properly set to preserve the UUID during import so a random UUID will be set for all customers. The PreserveUUIDs=true flag is now set on the Solution Pack.
Customers who already have an Endpoint: Web Service due to an import of the Registry Repository Exchange Utility Solution Pack should sunset that asset type after importing the SOA/BPM Suite Solution Pack.


  Back to Top       Previous  Next