51 Oracle Universal Records Management

This chapter describes issues associated with Oracle Universal Records Management. It includes the following topics:

51.1 General Issues and Workarounds

This section describes general issues and workarounds. It contains the following sections:

51.1.1 Role Report Output is Dependent on User Generating the Report

A role report can be generated by clicking Records then Reports then Role from the Main menu. The output of the report may not show all data for all roles. The output is dependent on the user who is generating the report and the permissions given to that user.

51.1.2 Viewing Frozen Items After Freeze Execution

When a freeze is executed from the Search Results page, the ensuing page does not redirect the customer back to the search results. To view frozen items after a freeze is executed from the Search Results page, execute a new search or refresh the page manually by clicking the Refresh button on the browser.

51.1.3 Items Returned When Using Screening

It should be noted that screening is a retention feature that only returns content items with a life cycle or items that are frozen.

51.1.4 Oracle Text Search and Report Configuration Options

When using Oracle Text Search, an incompatibility existed with the options to exclude report templates and reports in search results. These options appear on the Configure Report Settings Page.

It is now possible to exclude reports in search results by checking the Exclude Reports in Search Results checkbox. However, if the Exclude Report Template in Search Results box is checked, templates are still included in searches. Oracle is aware of this issue and is working to fix it in a future release.

51.2 Configuration Issues and Workarounds

This section contains configuration issues and workarounds. It contains the following sections:

51.2.1 Import FOIA Archive Error Message

Importing the Freedom of Information Act (FOIA) archive from the Setup Checklist page may display a spurious error message stating Archiver is already running, please try again later.

This error may be safely ignored. It is generated because the click to initiate the archive is registered twice. Ignore the warning, wait fifteen minutes and then see if the alert notification for that task is removed. The import of the archive can also be confirmed by opening the Archiver and verifying that the FOIAPrivacyAct archive is present.

51.2.2 Oracle Text Search and Index Rebuilds

When installing the Freedom of Information Act (FOIA) functionality for Oracle Universal Records Management you may not be able to do fast index rebuilds. Uncheck the Fast Index Rebuild option if using the FOIA option.

51.2.3 Restart Required: Performance Monitoring and Reports

After performance monitoring is selected and enabled, the content server must be restarted in order for monitoring to commence. Note that a restart is also required after configuration of Oracle URM in order for all report options to appear on the appropriate menus.

51.3 Documentation Errata

There are no known issues at this time.