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 Problems with Oracle Content DB Protocols

• 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
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.
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.
Users cannot access Properties dialog boxes or other dialog boxes in the Oracle Content DB or Oracle Records DB Web clients.	Pop-up blockers are blocking these application dialog boxes.	Users must disable pop-up blockers to access some features of the Oracle Content DB and Oracle Records DB Web clients. Users should 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.
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.
Cannot log in as cn=orcladmin.	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.	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 comamnd, 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
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 OracleAS Single Sign-On and log in as orcladmin. Run the odisrvreg 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.
Need to determine the domain display name for Oracle Content DB.	If you have multiple Oracle Content DB databases registered with Oracle Internet Directory, you may be unsure of the value for the domain display name.	If you have only one Oracle Content DB database registered with Oracle Internet Directory, then the Oracle Content DB domain display name is Content. If you have multiple Oracle Content DB databases registered with Oracle Internet Directory, you can use Oracle Directory Manager to determine the correct domain display name, as follows: Open Oracle Directory Manager and connect to Oracle Internet Directory as the cn=orcladmin user. Under Entry Management, navigate through the tree to the following entry: cn=IFS,cn=Products,cn=OracleContext Under this entry, there are mutliple entries of the following format: orclApplicationCommonName=domain_display_name Select each entry and note the value of the seealso property, which appears in the following format: orclReferenceName=database_service_name,cn=DatabaseInstances,cn=IFS,cn=Products,cn=OracleContext The orclApplicationCommonName entry whose seealso property includes the service name of your database is the entry that shows the correct domain display name. Alternatively, you can find the domain display name using the following ldapsearch command on the OracleAS Infrastructure computer: $ORACLE_HOME/bin/ldapsearch -h fully_qualified_infra_host_name -p Oracle_Internet_Directory_Port -D cn=orcladmin -w password_for_cn=orcladmin_user -b "cn=IFS,cn=Products,cn=OracleContext" -s one "objectclass=orclApplicationEntity" seealso For example: $ORACLE_HOME/bin/ldapsearch -h infrahost.company.com -p 389 -D cn=orcladmin -w mypassword -b "cn=IFS,cn=Products,cn=OracleContext" -s one "objectclass=orclApplicationEntity" seealso This command will return one result for each Oracle Content DB repository registered with Oracle Internet Directory. These results will appear similar to the following: orclApplicationCommonName=domain_display_name,cn=IFS,cn=Products,cn=OracleContext seealso=orclreferencename=database_service_name,cn=Database Instances,cn=IFS,cn=Products,cn=OracleContext The domain display name for your Oracle Content DB instance is the domain display name with a seealso value that includes the service name for your database.
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.
On UNIX systems, the regular node does not respond to opmnctl stop or opmnctl restart commands.	The node is hanging and must be stopped manually by the root user.	Because regular nodes run as root, nodes that are hanging must be shut down manually by the root user: kill -9 process-id To find out whether a node is hanging, use the opmnctl status command. Nodes that are hanging will show a status of "Stop." Nodes sometimes hang when the middle tier computer is low on resources, causing the node startup time to exceed 5 minutes.
Cannot log in to a new Site that was added using the Application Server Control.	OC4J_Content was not restarted after the Site was added.	You must restart OC4J_Content after you add a new Site. Restart OC4J_Content from the Content DB Home page in the Application Server Control, or use the following opmnctl command: opmnctl restartproc process-type=OC4J_Content
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.

Solving Problems with Oracle Content DB Protocols

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

Table A-2 Protocol Issues

Problem	Probable Cause	Corrective Action
Problems with outbound FTP on UNIX.	You are using /usr/bin/ftp on UNIX and the default port number in /etc/services is a port other than 21, such as 2100.	Specify the port number explicitly, for example, ftp ifs.us.oracle.com 21, where 21 is the port assigned.
Cannot log in to FTP.	The FTP password has not been set.	Log in to Oracle Content DB with the user account that cannot access FTP and set an FTP password. You can then log in to FTP using the FTP password.
Multibyte file names for files that were uploaded over FTP appear garbled in the Web client.	Protocol command character set was not specified for the FTP client.	When uploading files with multibyte file names over FTP, you must specify a protocol command character set to ensure the file names are properly encoded. This step is only required when the installation locale has a different default character set than the file name you are specifying over FTP. For example, if you want to upload a file with a Japanese file name over FTP, but the installation locale is Spanish, explicitly set the protocol command character set to shift_jis, as follows: FTP> quote setcommandcharacterset shift_jis See "Globalization and the Oracle Content DB Protocols" for more information about protocol command character sets.

Solving Performance Problems

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

Table A-3 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 open_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. For more information about adjusting the parameters in the init.ora file, see Oracle Content Database Installation Guide for your platform.
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.