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:
Section 50.1.4, "Site Studio Publisher Does Not Support Multibyte Characters"
Section 50.1.10, "Some Asian Time Zones Cannot Be Set on User Profile Page"
Section 50.1.12, "New Folio Page Does Not Work in French and Italian Languages"
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.
Characters entered in the Web Layout Editor that are not part of the content server's operating system character set will be corrupted (displayed as '?') after the Update Portal feature is used. To avoid this, use characters that are native to the operating system character set of the content server.
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 Kolkota (GMT +05.30), Kathmandu (GMT + 05.45), or Almaty (GMT +06.00).
Please note the following considerations when working with the download applet in Oracle Content Server:
The option to check out a native file when downloading it from a search results page does not work.
When downloading native files from a search results page, you must manually enter the target file name for the first item you are downloading.
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
This section describes configuration issues and their workarounds. It includes the following topics:
Section 50.2.1, "Minimum JDBC Driver Version Required for Oracle Text Search Component"
Section 50.2.3, "Using Standalone Admin Applications with DB2 or SQL Server System Database"
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.
Searches on Oracle Content Server may fail in instances where the UseCollaboration configuration flag is set to 'true' and the search index used is Oracle Text Search. If this is the case, modify Oracle Content Server's config.cfg file to include the following configuration flag:
ZonedSecurityFields=xClbraUserList,xClbraAliasList
If this flag already exists, append the two new fields to the list.
The config.cfg file can be modified from Admin Server, by selecting General Configuration, and then adding the information to the Additional Configuration Variables box. You must restart the content sever for the changes to take effect.
For the standalone administration applications to work, JDBC connection information for the system database must be provided. You can enter this information most easily in the System Properties application, in the Database tab. How much information you need to provide depends on what type of database and JDBC driver you are using; you always need to provide at least a connection string, username, and password. If Oracle Content Server is using a DB2 or SQL Server database, then select "Other JDBC Driver" and modify Oracle Content Server's intradoc.cfg file (located at Domain_Dir/ucm/cs/bin/intradoc.cfg) to include the following two lines, exactly as shown:
IDC_WL_LIB_DIR=${AppServerHome}/server/lib
IDC_WL_MODULES_DIR=$IDC_MW_HOME/modules
Then the driver name and classpath will be calculated by Content Server, and do not need to be entered in System Properties. You must still enter the connection string, username, and password.The JDBC connection string for DB2 should be as follows:
jdbc:weblogic:db2://database_hostname:database_port_number;databaseName=database_name
The JDBC connection string for SQL Server should be as follows:
jdbc:weblogic:sqlserver://database_hostname:database_port_number;databaseName=database_name
There are no known issues at this time.