| Oracle Internet File System Setup and Administration Guide Release 9.0.2 Part Number A95995-01 |
|
This chapter provides information on troubleshooting and configuration logs. The following topics are included:
This section contains information to assist with general problems and performance issues.
Table 10-1, "Troubleshooting Administrative Problems" describes common administration problems, what may have caused them, and what you should do to correct the problems.
Table 10-1| Problem | Probable Cause | Corrective Action |
|---|---|---|
|
An out-of-memory exception is raised when running Oracle 9iFS |
The maximum Java heap size is too low. |
Increase the heap size by modifying the |
|
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
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 9iFS server into a two-tier configuration.
For more information on adjusting the parameters in the |
|
Server is generally slow for read and write activity |
Probable cause #2: CTXHX is using 100 percent of your CPU. |
See "Troubleshooting Oracle Text Problems with Internet File System". |
|
Server is slow only on read or search activity |
Large amounts of documents have been loaded or updated and the Oracle9i Cost-Based Optimizer is using old statistics. |
Run the |
|
Server is slow only on content-based search activity |
Oracle Text tablespaces are on the same disk as other database files. |
Move the Oracle Text tablespaces to other disks. See the Oracle Internet File System Installation and Configuration Guide. See the Oracle9i Administrator's Guide for more information on moving tablespaces. |
|
Oracle Text indexes have become fragmented. |
Regularly optimize the Oracle Text Oracle index |
|
|
Server is slow only on write activity |
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 Administrator's Guide for more information. In general, Redo logs should be switching every hour or less frequently. See the |
|
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 Administrator's Guide, the Oracle9i Recovery Manager User's Guide, and the Oracle9i Recovery Manager 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 Sun SPARC Solaris, 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 "Index Maintenance" in Appendix E, "Working with Oracle Text". |
|
If a new folder is created using the Windows interface, an agent is triggered. |
When a folder is created in Windows Explorer, a new file is created (testdir.tmp) and then is deleted. Windows Explorer does this to make sure the right information is available to create information inside the folder. Therefore, the agent is triggered. |
No corrective action, this is the way Windows Explorer is designed to work. |
|
Want to reset the Oracle 9iFS system password without knowing what it is. |
Have forgotten the Oracle 9iFS system password. |
You will need to contact Oracle Support or, if not, you must re-install the database. If you choose to re-install the database, you will need to make sure that you have copied any files stored in the Oracle 9iFS database out to a local hard drive before starting the re-install process. The re-install will result in the loss of all information currently stored in the database. |
|
Problems with outbound FTP on UNIX. |
You are using |
Specify the port number explicitly, for example, |
|
When creating a class object in a language other than English, the following exception is encountered: "Exception IFS-30002 - Unable to create new LibraryObject." |
Class object and attribute names must be in English. |
Names for class objects and attributes must be in English. |
|
The administrator has uploaded LOB 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 ContentGarbageCollection Agent. |
Use Oracle 9iFS Manager to look at 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 getting activated at the periodic intervals. |
|
Cannot discover Oracle 9iFS targets (Oracle 9iFS Domain Controllers and Oracle 9iFS Nodes) in Oracle9i Enterprise Manager Console
|
Oracle Intelligent Agents on the hosts of those Oracle 9iFS targets are not running or didn't discover the targets. Oracle9i Enterprise Manager hasn't refreshed for those hosts.
|
Make sure that Oracle Enterprise Manager Console has been properly setup and configured. After you run the Oracle 9iFS Configuration Assistant, as a post-installation task:
|
Because Oracle 9iFS uses advanced features of Oracle9i, Oracle 9iFS requires use of Oracle's Cost-based Optimizer (CBO) to determine the most efficient way to execute SQL statements. For CBO to work properly, you should run the Analyze command before using Oracle 9iFS, as well as regularly during the use of Oracle 9iFS, especially after users have loaded large numbers of files into Oracle 9iFS or have changed their data in other ways.
On UNIX, perform these steps, replacing password with your password.
cd $ORACLE_HOME/9ifs/admin/sql sqlplus ifssys/password @analyze.sql ifssysNote that the command may take a while to complete, especially when there are large numbers of documents in Oracle 9iFS. In general, the command should be run during periods of reduced load on the system.
For more information about the Cost-based Optimizer and dbms_stats.gather_schema_statistics (used by analyze.sql), consult the Oracle9i database documentation.
Table 10-3, "Troubleshooting E-mail Problems" contains solutions to common e-mail configuration and operation problems.
Table 10-3 Troubleshooting E-mail Problems
This section addresses troubleshooting issues regarding Oracle Text. It includes the problem descriptions, possible causes, and solution descriptions.
Table 10-4 Troubleshooting Oracle Text Problems
During the configuration of Oracle 9iFS, the IfsConfigOut.log and the IfsConfigSql.log files are generated and stored in the following directories:
| Platform | Directory |
|---|---|
|
UNIX |
|
|
Windows NT |
|
The IfsConfigOut.log file is a log of the configuration, starting with saving properties to configuration files, then creating the schema and tablespaces. This log file lists which files are executed, what .adm and .typ files are executed by the AdminManager and CreateClasses.
If an error occurs during the Oracle 9iFS configuration, the problem is reported at the bottom of the log file. Notice a large Java stack trace. The trace is printed twice: once, exactly when the error occurred (by the thread actually executing the operation), and again by the main thread when it is displaying the error. Sometimes the first trace has more information, so be sure to examine both traces.
This log file contains a SQL "dump" of all the SQL statements that were executed directly from the SQL scripts that create the Oracle 9iFS schema, for example, odmmain.sql. This file is always created in "verbose" mode.
The following list displays the common errors found and a resolution:
java.lang "class not found"--A jar or library file is missing from the $ORACLE_HOME/lib or other directory.
java.sql.SQLException: procedure or package not available--A required package has not been installed in the Oracle software that Oracle 9iFS is being installed on top of, notably, the DBMS_OBFUSCATION_PACKAGE, or certain Oracle text packages.
The WCP Server Log is embedded within the log file for the node. It logs the WCP commands received from the Oracle 9iFS Windows Utilities, the intermediate output when commands are processed, and the WCP response sent back to the Oracle 9iFS Windows Utilities.
The following list describes some general information about the WCP server log.
The Oracle 9iFS Windows Utilities also have their own log files. By default, the log files are not generated unless the following Windows registry values are set up. You can customize the path specified for IfsDebug.log, for example, C:\.
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\IFS\Debug\Level=0x64(DWORD)
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\IFS\Debug\Path=<C:\IfsDebug.log>(string)
There are three types of log files, all located in the "log" subdirectory under the directory where the Windows interface is installed.
IfsSockMgr.log--Logs events such as Oracle 9iFS SocketManager starts and exceptions encountered by SocketManager.
IfsWcpSessions?.log--The '?' represents the drive letter to which the Oracle 9iFS (SMB) server is mapped. This file logs any exceptions during the interaction with the WCP server associated to the mapped drive and is normally blank.
IfsDebug.log--Logs the internal commands sent to WCP server.
The following information describes troubleshooting information to assist with general problems with Globalization Support.
Unable to ls and put filenames and folders with non-ASCII characters from the MS-DOS FTP client.
The character encoding of the command prompt window needs to match the character encoding of the FTP session. The character encoding of the FTP session will indicate to the FTP server the character set to use to encode the filename strings. This will ensure proper storage of the filenames in the repository as well as ensure proper display of filenames in the command prompt window.
Windows uses Unicode as its main character set. But for compatibility with MS-DOS, traditional code pages are supported. The MS-DOS command chcp allows viewing and setting the active code-page for the command prompt window.
To display the number of the active console code page, use a command line to enter the following:
C:\>chcp Active code page: 437
437 is the United States code page. For example, if you are using 437, you will not be able to handle German characters, ö and ß, in your FTP session. To handle German characters, the code page 1252 should be used. 1252 is for Western European languages.
To change the active code page to 1252, use a command line to enter the following:
C:\>chcp 1252 Active code page: 1252
Only the code page installed with Windows NT will display correctly in a command prompt window using Raster fonts. Other code pages will display correctly in windows using TrueType fonts or Lucida Console.
To change the fonts for the window:
The character encoding for the session should be set using the quote command, setcharencoding, to the same encoding for the command prompt window. If you change the code page with the chcp command, it is recommended that you use the Lucida Console font as the console font to avoid incorrect glyphs on the screen.
Use the following code to set the character encoding for the session:
ftp> quote setcharencoding <IANA character set name>
For example:
ftp> quote setcharencoding Windows-1252
The German Windows NT 4.0 Operating System has a default active code page of 850 for the command prompt windows. 850 is the multilingual Latin1 code page. The command prompt MS-DOS FTP client does not recognize German characters using 850, so the code page should be changed to 1252, which will work properly.
The following tables lists some MS-DOS code pages and their corresponding language.
The following table lists Windows ANSI code pages and their language/font.
Filenames truncated or corrupted when using the drag and drop feature of the Web interface to upload files named with Western European characters using the Netscape browser.
Netscape uses the Windows code page for its FTP client. If the Oracle database character set is UTF8, the FTP server needs to have the DefaultCharacterSet property in the properties file set to ISO-8859-1 for Western European languages.
Unable to drag and drop files through the Web interface using a multibyte operating system.
The drag and drop feature only supports the character set (or subsets) of the Oracle Internet File System FTP server default character set. Check the value in the properties file.
Unable to insert files correctly through FTP even if the default character set of the FTP server is the same as the client OS.
Be sure to have the NLS_LANG environment variable set to the same character set as the database character set. The OCI driver reads this environment variable and uses for string conversion before inserting into the database. For example, if the database character set is UTF8, then set NLS_LANG=.UTF8. This is only a problem with the OCI drivers, and not JDBC thin drivers.
Unable to context search multilingual content in a document after inserting a document into the repository through FTP.
Be sure to set the language for the current FTP session. Documents inserted via the 'put' command will have its LANGUAGE attribute set to this value.
To view the current language for the FTP session, use the following quote command:
ftp> quote showlanguage 226 Language English
To set the language for the FTP session, use the following quote command:
ftp> quote setlanguage <Oracle language name>
|
|
![]() Copyright © 1999, 2002 Oracle Corporation. All Rights Reserved. |
|