50 Oracle Universal Content Management

This chapter describes issues associated with Oracle Universal Content Management (Oracle UCM). It includes the following topics:

50.1 General Issues and Workarounds

This section describes general issues and workarounds. It includes the following topics:

50.1.1 Enterprise Manager Page Crashes After Extended Time When Using Flash Browser Plug-In

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.

50.1.2 Standalone Oracle Inbound Refinery Application Executables on Windows 7

On Windows 7, the standalone Oracle Inbound Refinery application executables are not automatically copied to the bin directory (Domain_Dir/ucm/ibr/bin). If you need to use standalone applications, you can copy and rename them from Idc_Home/bin. For example, to use System Properties, you should copy Idc_Home/bin/Installer.exe to Domain_Dir/ucm/ibr/bin/SystemProperties.exe.

Please note that Oracle Inbound Refinery is supported on Windows 7 in development environments only.

50.1.3 Folio Items With Content IDs Containing Multibyte Characters Do Not Display Correctly in Safari

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.

50.1.4 Site Studio Does Not Support Multibyte Characters in Site IDs, Directory Names, and Page Names

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.

50.1.5 Site Studio Publisher Does Not Support Multibyte Characters

Oracle Site Studio Publisher does not support multibyte characters.

50.1.6 Desktop Integration Suite Users Cannot Perform Oracle Content Server Operations If Their User Logins Contain 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.

50.1.7 Transferring Folder Archives Between Content Servers Fails If Server System Locales Do Not Match

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.

50.1.8 Importing Folder Archives Fails If User Locale Did Not Match Server System Locale During Export

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.

50.1.9 Issues With Converting Files With Content IDs Containing Non-ASCII Characters Using Dynamic Converter

There are various issues when converting files with content IDs containing non-ASCII characters using Dynamic Converter. To avoid these issues, use only ASCII characters in content IDs.

50.1.10 Some Asian Time Zones Cannot Be Set on User Profile Page

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).

50.1.11 New Folio Page Does Not Work in French and Italian Languages

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.

50.1.12 UCM Servers and IPv6 Support

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

50.1.13 Large File Checkins May Cause Timeouts

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 IdcServerThreadQueryTimeout=300.

50.1.14 Content Categorizer Trace Log Settings Discontinued

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.

50.1.15 Using UCM with OAM Server under Single Sign-on

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:


50.1.16 Extra Lines Displayed Viewing Contribution Folders in IE8

When using Folders in IE8 with default settings, IE8 adds extra lines. This is solved by opening the Compatibility View Settings dialog and unselecting the Display intranet sites in Compatibility View checkbox.

50.1.17 WebDAV Connection Fails After Logout or Restart

In Windows 7 and Windows Vista clients, after logging out and logging back in or after restarting, the Network Place used to access UCM over WebDAV may no longer work. This is solved by deleting and recreating the connection.

50.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

50.2.1 Minimum JDBC Driver Version Required for Oracle Text Search Component

The Oracle Text Search component that is part of Oracle UCM 11gR1 requires a JDBC driver version of or higher. The component will not work with older JDBC driver versions.

50.2.2 Configuring Standalone Applications with Non-Oracle Databases

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. This is the method for setting JDBC information for standalone applications:

In SystemProperties, on the Database tab, select the appropriate driver, and enter the connection string, user name, and password. You do not need to enter a classpath or driver name.

For DB2, you would select the DataDirect DB2 JDBC Driver, and the connection string must then be of this form:


For MS SQLServer, you would select the DataDirect SQL Server JDBC Driver, and the connection string must then be of this form:


50.2.3 Manually Disabling 8.3 File Naming for Oracle Inbound Refinery on Windows 7

When running Oracle Inbound Refinery on Windows platforms, you may see this alert:

"The weblayout directory is on a filesystem with 8dot3 semantics. Legacy 16-bit 8dot3 filenames conflict with revision labels and will cause file loss. Disable 8dot3 semantics by running Installer DisableNtfs8dot3 and then restarting Windows."

On Windows 7, running Installer DisableNtfs8dot3 does not resolve this. You must make the configuration change manually in the Windows registry.

To change the Windows registry, go to the following key:


Then, set the value of the NtfsDisable8dot3NameCreation key to 1. You must restart Windows for the new setting to take effect.

Please note that Oracle Inbound Refinery is supported on Windows 7 in development environments only.

50.3 Documentation Errata

There are no known issues at this time.