UCM: Troubleshooting Cached Pages

When working with metadata, profiles and rules your browser may cache option list values and configurations.  You may experience making changes but not seeing those changes reflected in the page.  Follow these steps to attempt to resolve this.  The steps assume the use of Chrome as the browser.

1. Open the Developer Tools (Press Ctrl+Shift+J)
2. Select the tab labeled Network
3. Right click in the white space
4. Click Clear Browser Cache
5. Click OK
6. Close the Developer Tools

UCM: Troubleshooting Performance Issues

The most important tracing options that will help initially identify the problem are

system,systemdatabase,requestaudit,searchquery

Standard Weblogic UCM server logs in 11g are stored in the locations below:

D:\Oracle\user_projects\domains\ecm_domain\servers\UCM_server\logs\UCM_server.log
D:\Oracle\user_projects\domains\ecm_domain\servers\UCM_server\logs\UCM_server-diagnostic.log

Daily content server log files are stored in:

D:\Oracle\user_projects\domains\ecm_domain\ucm\cs\weblayout\groups\secure\logs\*.htm

Location of system audit information logs

D:\Oracle\user_projects\domains\ecm_domain\ucm\cs\data\trace \*.log

This value is set in the configuration variable TraceDirectory .

Environment Packages:
1. Login to UCM.
2. Go to Administration -> Environment Packager.
3. Click "Start packaging." This creates a zip file for uploading. Once the zip is created, it will go to the following directory:
$MW_HOME/user_projects/domains/<domain>/ucm/cs/weblayout/groups/secure/logs/env

UCM: !csJdbcGenericError

As the error name indicates, this is a general exception related to database access (JDBC stands for Java Database Connectivity). To get more data about the underlying error, try the following:

1. In the Administration menu, choose System Audit and enable systemdatabase tracing. Click the Full Verbose checkbox for maximum detail, and the Save checkbox to preserve this change across server restarts.
2. Edit your config.cfg file and set SecureDataAllowedIntoStatusMessage=true. Reboot the server. 

Repeat the operation that causes the error, and review the trace and UCM diagnostic logs to get more information on the error.


NOTE: First check the trace to find the issue. Use "requestaudit, searchquery, indexer, systemdatabase".
If not resolved, then update the config file with above configuration, and then update the parameters in the trace with "searchquery, systemdatabase".