|Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86-64
Part Number E14770-21
This chapter describes issues associated with Oracle Universal Content Management (Oracle UCM). It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
When the DMS page is open for an extended period of time (at least 35 minutes), Enterprise Manager crashes. The DMS page is opened by first selecting UCM, then Monitoring, then Performance. The crash happens when the page is open for 35 minutes or more, there are lots of services being called on the server, and Adobe Flash is installed as a browser plug-in.
If you use the Safari web browser to download content into a simple folio where one or more content IDs include multibyte characters, then these multibyte content IDs are displayed as '------'. To avoid this, you can either use Internet Explorer or Firefox, or avoid using multibyte characters in content IDs.
Oracle Site Studio does not support multibyte characters in any value that will be used in URLs, including site IDs, directory names, and page names.
Oracle Site Studio Publisher does not support multibyte characters.
Some operations that require a Desktop Integration Suite user to log in to Oracle Content Server are blocked if that user has a login name that contains multibyte characters. There are no issues if the login name contains only ASCII characters.
If you transfer folder archives between two Oracle Content Server instances using the Archiver utility, then this will fail if these servers have different system locales. No folder will be created on the target server, and no items under that folder will be imported. To avoid this, make sure that the system locales of both content servers match.
If you export a folder archive from the Folder Configuration page in Oracle Content Server and the user locale during export does not match the server system locale, then you will not be able to import that folder archive to the same or a different content server, even if the user and system locales on that server do match. To avoid this, make sure that the user and system locales match during the folder archive export.
There are various issues when converting files with content IDs containing non-ASCII characters using Dynamic Converter in Linux environments with native encoding. To avoid these issues, use only ASCII characters in content IDs. Please note that these issues do not occur in Linux environments with UTF-8 encoding.
Users cannot change their time zone in their user profile page on Oracle Content Server to Kolkata (GMT +05.30), Kathmandu (GMT + 05.45), or Almaty (GMT +06.00).
If both the Folios and AppAdapterCore features are enabled, and the user language is set to either French or Italian, the New Folio page does not allow you to select a template and create a new folio.
UCM servers are supported on IPv4/IPv6 dual-stack hosts, but not on"IPv6-only" hosts. The following topologies are supported:
Oracle Database on IPv4 hosts
Oracle UCM, Oracle URM, Oracle IBR on IPv4/IPv6 dual-stack hosts
Client (browser) on either IPv4 or IPv6 hosts
Large file checkins often time out due to the amount of I/O that occurs. Database locks are held while the large file is written and this blocks subsequent checkins. The IdcServerThreadQueryTimeout configuration setting can be used to lengthen the checkout time. The setting is expressed in seconds; to make the timeout 5 minutes, set
The Content Categorizer-specific execution trace log settings are discontinued. Use the Content Server System Audit Information facility instead. To enable Content Categorizer execution trace, enter
contentcategorizer in the Active Sections control of the Tracing Sections Information section of the Admin System Audit Information page.
When UCM is used with OAM in a Single Sign-on environment, an entry to the config.cfg file must have the following lines added:
This section describes configuration issues and their workarounds. It includes the following topics:
The Oracle Text Search component that is part of Oracle UCM 11gR1 requires a JDBC driver version of 10.2.0.4 or higher. The component will not work with older JDBC driver versions.
There are no known issues at this time.