A Troubleshooting Oracle Content DB

Use this appendix to troubleshoot problems in your Oracle Content DB installation.

This appendix provides information about the following topics:

Solving General Administration Problems
Solving Performance Problems

Solving General Administration Problems

Table A-1 provides information about how to troubleshoot general Oracle Content DB administration problems.

Table A-1 General Administration Issues

Problem	Probable Cause	Corrective Action
The administrator has uploaded files and removed them, and does not see the space retrieved in the tablespace.	The Initial Time of Day and Activation Period has been set incorrectly for the `Content GarbageCollectionAgent`.	Use the Application Server Control to view the Initial Time of Day and Activation Period entries for the Content Garbage Collection Agent. Also check the node log and see if the Content Garbage Collection Agent is being activated at periodic intervals.
When using Oracle Internet Directory, users fail to be provisioned, or newly provisioned users cannot be added to Libraries.	Required user attributes were not set in Oracle Internet Directory.	The following Oracle Internet Directory user attributes must be nonnull for all users: `sn`, `givenName`, `mail`. In addition, all users must have a nonnull user name. The user name is specified by the `orclCommonNickname Attribute` in the OracleContext of the realm. See Oracle Internet Directory Administrator's Guide for more information about viewing the `orclCommonNicknameAttribute`.
After adding a user to a file-based user repository using the OracleAS JAAS Provider Admintool, the new user cannot log in to Oracle Content DB.	`OC4J_Content` was not restarted after the user was added.	After you add a user to a file-based user repository using the OracleAS JAAS Provider Admintool, you must restart `OC4J_Content` before the user can log in to Oracle Content DB. Alternatively, you can use the Application Server Control to add users. You do not need to restart `OC4J_Content` after adding users with the Application Server Control.
In the Oracle Content DB Web client, in Administration Mode, user administrators can see users who were deleted in the user repository, as well as update the profile information for these users.	The `deleteuser` script was not run after deleting the users in the user repository.	You must run the `deleteuser` script to remove users from Oracle Content DB after you delete users in the user repository. See "Deleting Users in Oracle Content DB" for more information.
Users cannot access Properties dialog boxes or other dialog boxes in the Oracle Content DB Web client.	Pop-up blockers are blocking these application dialog boxes.	Users must disable pop-up blockers to access some features of the Oracle Content DB Web client. Users can hold down the Ctrl key while clicking Launch to bypass most pop-up blockers. In addition, users can refer to the Help for the browser for more information about pop-up settings.
In the user preferences dialog in the Oracle Content DB Web client, the values for First Name, Last Name, and E-mail Address are blank and cannot be updated by users.	The User Administrator has not provided these values.	If you are using a file-based user repository as your Oracle Content DB user repository, there is no way to provide the First Name, Last Name, and E-mail Address user profile values when you create users. To set these values, log in to the Oracle Content DB Web client as a User Administrator and switch to Administration mode. Then, access the user profile for each user you added and set these attributes.
You have added a user to your user repository, but cannot find this user in Oracle Content DB user searches.	The user has not yet logged in to Oracle Content DB.	Because users are not provisioned until they log in for the first time, they may not appear in Oracle Content DB searches, even though they exist in the user repository. You must wait until the user logs in to Oracle Content DB before searching for the user, or attempting to add the user to a Library.
Cannot connect to Oracle Content DB.	The Oracle Content DB server may be using DHCP.	If Oracle Content DB is using DHCP, use the current IP address of the server to connect, rather than the host name. All Oracle Content DB protocols are affected, including HTTP.
In the Application Server Control, the following error message appears for a particular server on the Node page: "This server is configured but not loaded now."	The server may not have been configured correctly, or the server may have an initialization or loading problem. This message also appears when the server has been deleted from the node at run time, but still exists in the node configuration.	Check the node log for information about possible initialization and loading errors for this server.
Cannot log in as `cn=orcladmin` (Oracle Internet Directory user repository only).	You forgot or do not know the `cn=orcladmin` password.	You can reset the password in the Metadata Repository database. The DSE root attribute name is `orclsupassword`. Note: After a certain number of failed attempts to connect, the `cn=orcladmin` account becomes locked. In this case, you must unlock the account.
The `cn=orcladmin` account becomes locked (Oracle Internet Directory user repository only).	The `cn=orcladmin` account becomes locked, by default, after 10 failed attempts to connect. This setting is controlled by the password policy.	If you know the `cn=orcladmin` password, you can unlock the account by running the following command from the OracleAS Infrastructure Oracle home: ORACLE_HOME/bin/oidpasswd connect=db_SID unlock_su_acct=true In the preceding command, `db_SID` is the SID for the database. For example: ORACLE_HOME/bin/oidpasswd connect=orcl unlock_su_acct=true OID DB user password: my_ODS_password OID superuser account unlocked successfully. The command prompts for the password of the ODS schema. By default, the ODS password is the same as for the `cn=orcladmin` account, which was set during OracleAS Infrastructure installation. See Also: Oracle Internet Directory Administrator's Guide for information about changing the password policy for the allowed number of failed attempts to connect
Users are experiencing problems logging in through the Web client after logging out.	The user did not close all browser windows after logging out of Oracle Content DB.	Because of JAZN limitations, to fully log out of Oracle Content DB, users must close all browser windows associated with the browser they used to log in to Oracle Content DB. For example, if users logged in using Microsoft Internet Explorer, they must close all Internet Explorer windows after they log out.
The password for the `cn=orcladmin` account has expired, and you want to change the default password expiration time.	The default password expiration time is 60 days.	To change the default expiration time for the `cn=orcladmin` password: If the `cn=orcladmin` account is locked, you must unlock the account before you can modify the password policy. See the preceding item in this table for more information. Log in to Oracle Directory Manager and go to Password Policy Management. Look for the following two attributes: - The `PasswordExpiryTime` attribute under the `cn=PwdPolicyEntry` (for example, `password_policy_entry,dc=mycompany,dc=com`) - The `pwdmaxage` attribute under Entry Management (for example, `cn=PwdPolicyEntry,cn=common, cn=products,cn=OracleContext,dc=mycompany,dc=com`) Change the `pwdmaxage` attribute in each password policy to an appropriate value. For example: 5184000 = 60 days (default) 7776000 = 90 days 10368000 = 120 days 15552000 = 180 days 31536000 = 1 year Note: It is very important to change this value in both places. Still in Oracle Directory Manager, go to the realm-specific `orcladmin` account. Find the `userpassword` attribute and assign a new value. You can then start any Oracle component that uses Oracle Single Sign-On and log in as `orcladmin`. Run the `oidsrvreg` utility to reset the randomly generated password for Oracle Directory Integration and Provisioning. For example: odisrvreg -D cn=orcladmin -w mypassword -p 3060 Already Registered...Updating DIS password... DIS registration successful. See Also: Oracle Identity Management Integration Guide for more information
An out-of-memory exception occurs when running Oracle Content DB.	The maximum Java heap size is too low.	Increase the heap size by modifying the `-Xmx` setting for that node configuration. See "Modifying Node Configurations" for more information.
Content queries through the Web and Windows return no rows.	Oracle Text indexing of the documents has not occurred.	See "Maintaining the IFS_TEXT Index by Using the Oracle Text PL/SQL Packages" for more information.
In the Application Server Control, cannot view the Oracle Content DB Web services in the Web Services tab of the OC4J_Content page.	The Oracle Content DB Web services do not use the Oracle Application Server Web Services framework	The Oracle Content DB Web services use the Axis framework, not the Oracle Application Server Web Services framework. Because of this, in the Application Server Control, the Oracle Content DB Web services do not appear in the Web Services tab for OC4J_Content.
When using the Search Logs function in the Application Server Control, cannot find OC4J_Content logs.	The log search criteria include message types that do not apply.	On the Search Logs page in the Application Server Control, be sure to select Unknown in the Message Types section. Oracle Content DB logs are not categorized by the other message types listed (Internal Error, Warning, Trace, Error, and Notification).

Solving Performance Problems

Table A-2 provides information about how to troubleshoot problems with Oracle Content DB performance.

Table A-2 Performance Issues

Problem	Probable Cause	Corrective Action
Server is generally slow for read and write activity (case #1).	Server memory is overcommitted. The server is excessively swapping memory blocks to disk.	Run system monitoring tools, such as `vmstat` (UNIX) and look for excessive page swapping to verify the problem. Adjust the following parameters in the `init.ora` file for the database: Reduce `processes.` Reduce o`pen_cursors.` Reduce `db_block_buffers.` Stop unneeded Java VMs or other unneeded processes. You may also need to add memory to your server or, if you are running a single-tier configuration, reconfigure your Oracle Content DB server into a two-tier configuration.
Server is generally slow for read and write activity (case #2).	`CTXHX` is using 100 percent of your CPU.	See Appendix C, "Managing the Oracle Text Index".
Server is slow only on read or search activity.	Large volumes of data have been loaded but the CBO statistics were not updated.	If the Cost-Based Optimizer is using out-of-date statistics data, performance suffers. Run the `analyze.sql` script located in the `ORACLE_HOME/content/admin/sql` directory to refresh the statistics.
Server is slow only on content-based search activity (case #1).	Oracle Text tablespaces are on the same disk as other database files.	Move the Oracle Text tablespaces to other disks. See Oracle Database Administrator's Guide for more information about moving tablespaces.
Server is slow only on content-based search activity (case #2).	Oracle Text indexes have become fragmented.	Regularly optimize the Oracle Text Oracle index `IFS_TEXT`. See "Maintaining the IFS_TEXT Index by Using the Oracle Text PL/SQL Packages" for more information.
Server is slow only on write activity (case #1).	Large amounts of documents are being loaded and the Redo logs are too small.	Add two or more 100 MB or larger Redo logs. See Oracle Database Administrator's Guide for more information. In general, Redo logs should be switching every hour or less frequently. See the `ORACLE_HOME/rdbms/sid/bdump` directory for the latest logs which indicate the frequency of Redo log switching.
Server is slow only on write activity (case #2).	Large amounts of documents are being loaded and the Redo logs are on the same disk as the database files.	Place the Redo logs on a separate disk from the database files. See Oracle Database Administrator's Guide and Oracle Database Performance Tuning Guide for more information. For optimal performance, dedicate one or more disks (and, if possible, a disk controller) exclusively to the Redo logs, and optimize the disks for sequential write activity. For example, on Solaris Operating System (SPARC), you may choose raw partitions or UNIX file systems for the disks. If you choose UNIX file systems on Solaris 2.6 or later, use the "forcedirection" option when mounting the file systems. These options should only be used if the file systems are dedicated exclusively to the Redo logs.