| Oracle® Files Administrator's Guide Release 2 (9.0.4) Part Number B10872-02 |
|
|
View PDF |
| Oracle® Files Administrator's Guide Release 2 (9.0.4) Part Number B10872-02 |
|
|
View PDF |
This chapter provides the following information:
This section contains information to assist with general problems and performance issues. The probable cause and a corrective action are provided for each problem.
Table 11-1 Troubleshooting General Problems
| Problem | Probable Cause | Corrective Action |
|---|---|---|
| An out-of-memory exception is raised when running Oracle Files. | The maximum Java heap size is too low. | Increase the heap size by modifying the -Xmx setting for that node configuration. See the Oracle Files Planning Guide for more information. |
| Server is generally slow for read and write activity. | Probable cause #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 your database's
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 Files server into a two-tier configuration. For more information on adjusting the parameters in the |
Probable cause #2: CTXHX is using 100 percent of your CPU. |
See Appendix A, "Oracle Text Reference". | |
| Server is slow only on read or search activity. | Large volumes of data have been loaded but the CBO statistics weren't updated. | If the Oracle9i Cost-Based Optimizer is using stale statistics data, performance suffers. Run the analyze.sql script located in the $ORACLE_HOME/ifs/files/admin/sql directory to refresh the statistics. |
| Server is slow only on content-based search activity. | Probable cause #1: Oracle Text tablespaces are on the same disk as other database files. | Move the Oracle Text tablespaces to other disks. See the Oracle Collaboration Suite Installation and Configuration Guide and the Oracle9i Database Administrator's Guide for more information on moving tablespaces. |
| Probable cause #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. | Probable cause #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 the Oracle9i 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. |
| Probable cause #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 the Oracle9i Database Administrator's Guide and the Oracle9i Database Performance Tuning Guide and Reference 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 above, 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. |
|
| 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. |
| 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. |
| Problems with NFS on AIX, HP-UX, or Compaq Tru64 platforms. | You are trying to run multiple NFS servers on these platforms. | On AIX, HP-UX, and Compaq Tru64 platforms, the Oracle Files NFS server must use the primary NFS port (2049). Because of this, you cannot run both the native UNIX NFS server and the Oracle Files NFS server on these platforms. |
| Want to reset the Oracle Files system password without knowing what it is. | Have forgotten the Oracle Files system password. | See "Changing the Oracle Files System Password". |
| The administrator has uploaded files and removed them and doesn't 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 Oracle Enterprise Manager Web site to look at the Initial Time of Day and Activation Period entries for the Content Garbage Collection Agent.
Also check the |
| Cannot access Oracle Files from outside the firewall using SMB. | The required port is not open. | Windows clients can only access SMB if it is running on port 139, so you will need to open up port 139 to the external computer. |
| Accessing Oracle Files from outside the firewall using SMB is very slow. | SMB is inherently slow over the Internet. | Because the SMB protocol frequently sends hundreds of network requests for each user operation, using SMB over any network with high latency, such as the Internet, might be too slow for end users. Oracle recommends using SMB only if the end user is within 100 miles of the Oracle Files server. See the Oracle Files Planning Guide for more details. |
| Users fail to be provisioned, or newly provisioned users cannot be added to workspaces. | Required user attributes were not set in Oracle Internet Directory. | The following Oracle Internet Directory user attributes must be non-null for all users: sn, givenName, mail. In addition, all users must have a non-null username.
The username is specified by the |
| "503 Service Unavailable" error message. | The OC4J instance was not restarted after starting the Oracle Files Domain. |
|
| Cannot log in to FTP. | Protocol Access is not enabled for that user. | Log in to Oracle Files with the user account that cannot access FTP and go to the Protocol Access page, where you can set an Oracle Files-specific password. You can then log in to FTP using the Oracle Files-specific password. |
| When using NTFS, nothing gets written into the node log. | The Log Level of the node configuration is not set high enough. | NTFS will not write into the node log unless the Log Level is set to 6. See "Changing a Node Configuration" for information about how to set the Log Level. |
| Oracle Files domain link is not active in the Oracle Enterprise Manager Web site. | Did not restart Oracle Enterprise Manager after Oracle Files configuration. | Restart Oracle Enterprise Manager. See Table 4-1, "Starting and Stopping the Oracle Enterprise Manager Process" for more information. |
| Cannot connect to Oracle Files. | The Oracle Files server may be using DHCP. | If Oracle Files is using DHCP, use the server's current IP address to connect rather than the hostname. All Oracle Files protocols are affected, including HTTP. |
| Oracle Files protocols fail to establish new connections after 10,000+ connects/disconnects. | You are using a 9.0.2x version of Oracle9iAS Infrastructure on a Linux, Windows, or Tru64 platform. | Apply the appropriate ARU patch for your platform and Infrastructure version number. See Note 252888.1 on Oracle MetaLink for a full description of this problem, including the patch IDs. You can access Oracle MetaLink at: |
