Skip Headers

Oracle Internet File System Setup and Administration Guide
Release 9.0.2

Part Number A95995-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

10
Oracle 9iFS Troubleshooting and Performance Information

This chapter provides information on troubleshooting and configuration logs. The following topics are included:

Troubleshooting General Problems and Performance Issues

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 -mx setting for that node configuration file. See Appendix D, "Process Configuration Files".

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 init.ora file:

  • 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 9iFS server into a two-tier configuration.

For more information on adjusting the parameters in the init.ora file, see the Oracle Internet File System Installation and Configuration Guide.

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 analyze.sql script located in the <ORACLE_HOME>\9ifs\admin\sql directory.

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 IFS_TEXT. For more information, see the Appendix E, "Working with Oracle Text".

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 ORACE_HOME/rdbms/<sid>/bdump directory for the latest logs which indicate the frequency of Redo log switching.

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 /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.

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:

  1. Start/Restart the Oracle9i Intelligent Agents on all the hosts of the Oracle 9iFS domain (you need to define ORACLE_SID in the environment when you start or restart IAs).

    agentctl stop
    agentctl start

    Check it with "echo $ORACLE_SID".

  2. Check whether the IAs have discovered the Oracle 9iFS targets. Check $ORACLE_HOME/network/agent/services.ora. You should find the entry for the Oracle 9iFS Domain Controller if you configured an Oracle 9iFS Domain Controller on that host and the entries for all the Oracle 9iFS nodes (except HttpNode) that you configured on that host. You should see entries for oracle_sysman_ifs and oracle_sysman_ifs_node in the services.ora file.

  3. Check to see that these files exist:

    $OH/network/agent/config/ifs.ora
    $OH/network/agent/config/ifs.tcl
    

    Check to see if $OH/sysman/config/OEMClient.properties contains entries for ifs. If missing, run the ifsoemsetup script as the oracle user.

    You can also try running $OH/9ifs/bin/ifsoemappsetup as oracle user.

  4. Open the Oracle9i Enterprise Manager Console.

    oemapp console
    

    Use the Discovery Wizard to discover or refresh all the hosts of the Oracle 9iFS domain.

Troubleshooting Administrative Problems

Troubleshooting Client Problems

Table 10-2 Troubleshooting Client Problems
Problem Probable Cause Corrective Action

After installing Oracle 9iFS, you are unable to access the Web interface.

The Oracle HTTP Server has not been started.

Make sure you restart the Oracle HTTP Server. Run the ifsJservctl -start script from %ORACLE_HOME%\9ifs\bin. If it still doesn't work, take a look at ifsjserv.log found under %ORACLE_HOME%\Apache\Jserv\logs.

When using the Web interface, problems occur when using drag and drop in the Web interface to upload files to the server.

A web proxy is being used for FTP.

Users may need to edit their web browser preferences so that they do not use a proxy for FTP.

In Word95: "Word cannot open the document".

In other Windows application: "Unable to open F:\home\jdoe\ifs10949.doc. There are too many files already open".

In Netscape: "F:\home\jdoe\ifs10949.doc. Too many files are open. Quit one or more programs or files, and try again."

In Internet Explorer: "Action canceled. Internet Explorer was unable to link to the Web page you requested. The page might be temporarily unavailable."

The parameter "MaxAllOpenFiles" in the SmbServer.def is too low.

(These error messages are examples of what the user may see if this problem occurs.)

Adjust MaxAllOpenFiles in Smb.Server.def higher.

Use Analyze to Optimize Performance

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 ifssys

Note 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.

Troubleshooting E-mail Problems

Table 10-3, "Troubleshooting E-mail Problems" contains solutions to common e-mail configuration and operation problems.

Table 10-3 Troubleshooting E-mail Problems

Problem Probable Cause Corrective Action

Incoming e-mail hangs.

Oracle 9iFS SMTP server is not running.

Uninstall e-mail using this script:

#!/bin/sh
# To uninstall smtp from 9iFS, run this 
script as root.
/usr/bin/ex /etc/sendmail.cf <<EOF
g/doCheck/p
g/doCheck/s/^/#/
w
q
EOF

Troubleshooting Oracle Text Problems with Internet File System

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

Problem Probable Cause Corrective Action

Cannot search on document contents of any documents.

Oracle Text server is not running

See Appendix E, "Working with Oracle Text".

Using search in the WebUI returns error "IFS-22012:Search Failed. Invalid query may have been specified", or returns no results when user searches in WebUI Help.

Database character set is not supported by the Oracle Text Multi-Lexer.

Reinstall or upgrade your database to have the NLS_CHARACTERSET of UTF8 or one of the other ones supported by the Oracle Text Multi-Lexer for the language you are using.

For more information, see the section on "Multi_Lexer" in the Oracle9i Text Reference Guide.

Cannot search on document contents after upgrading the Oracle Internet File System schema from version 1.0 or version 1.1 to version 0.0.1.

Oracle Text index was not re-populated.

See Chapter 4, "Upgrading from a Previous Version of Oracle 9iFS" of the Oracle Internet File System Installation and Configuration Guide for more information.

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 Internet File System Installation and Configuration Guide. See the Oracle9i Administrator's Guide for more information on moving tablespaces.

Server is slow only on content-based search activity.

Probable cause #2: Oracle Text indexes have become fragmented.

Regularly optimize the text Oracle index INDEXEDLOB_I (for upgraded schemas), or GLOBALINDEXEDBLOB_I (for new schemas). For more information, see the Appendix E, "Working with Oracle Text".

Problem Probable Cause Corrective Action

Searching on the contents of new documents stops working.

A recent document has caused Oracle Text server to fail.

  1. Log into sqlplus as ifssys/<schema-pwd>, and issue
    select count(*) from ctx_user_pending;

  2. If there are any rows in that view and the rows are not changing, then a recent document has caused Oracle Text to stop indexing. See the problem "Oracle 9iFS rows show up in the ctx_user_pending view" to determine which Oracle 9iFS documents these rows refer to.

  3. Still in sqlplus, issue
    select * from ctx_user_index_errors;
    to see if there are any recent errors. Resolve any of these errors. See the problem "Oracle 9iFS rows show up in the ctx_user_index_errors view" to determine which Oracle 9iFS documents these rows refer to.

  4. Check again to see if there are any rows in ctx_user_pending and, if so, that the rows are changing.

  5. If this does not resolve the issue, contact your Oracle Support representative for further assistance.

Oracle 9iFS rows never get processed and never leave the Oracle Text view ctx_user_pending.

Oracle 9iFS documents are corrupt or do not have the correct extension.

  1. Follow the steps in "Oracle 9iFS rows show up in the Oracle Text view ctx_user_index_errors" to determine which Oracle 9iFS documents are being referred to, substituting ctx_user_pending for ctx_user_index_errors and pnd_rowid for err_textkey.

  2. Examine this document, looking for these problems:

    • Is the file damaged in any way?

    • Is the file name extension correct for this document?

    • Is the character set of the document correct?

  3. If no obvious problems are found, send the document to your Oracle Support Representative for further diagnosis.

  4. Delete the document from Oracle 9iFS.

Oracle 9iFS rows show up in the Oracle Text view ctx_user_index_errors.

Oracle 9iFS documents are corrupt or do not have the correct extension.

  1. Determine which Oracle 9iFS document is being referred to.

    sqlplus ifssys/ifssys
    select du.uniquename, vd.name, 
    co.contentsize, cs.id, vd.id
    from odmv_document vd, odm_ contentobject co, odmm_contentstore cs, odm_document od,
    odm_directoryuser du
    where vd.id = od.id
    and od.contentobject = co.id
    and co.content = cs.id
    and du.id = vd.owner
    and cs.id in
    (
    select distinct od.id
    from ctx_user_index_errors cp, odmm_ contentstore od
    where od.rowid = err_textkey
    )
    order by cs.id;
  2. $ORACLE_HOME/9ifs/bin/ifsshell

  3. @ login system/<password>

  4. showallpaths -id <vd.id>
    replacing <vd.id> with the vd.id returned from the Select statement above. This command will display the absolute path of the document.

  5. Examine this document, looking for these problems:

    Is the file damaged in any way?

    Is the file name extension correct for this document?

    Is the character set of the document correct?

  6. If no obvious problems are found, send the document to your Oracle Support Representative for further diagnosis.

Using the Configuration Log Files

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

$ORACLE_HOME/9ifs/log

Windows NT

%ORACLE_HOME%\9ifs\log

IfsConfigOut.log

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.

IfsConfigSql.log

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.

Common Errors Found in the IfsConfigOut.log and IfsConfigSql.log Files

The following list displays the common errors found and a resolution:

The WCP Server Log File

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.

General Notes About the WCP Server Log

The following list describes some general information about the WCP server log.

The Oracle 9iFS Windows Utilities Log Files

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:\.

There are three types of log files, all located in the "log" subdirectory under the directory where the Windows interface is installed.

Globalization Support Troubleshooting

The following information describes troubleshooting information to assist with general problems with Globalization Support.

Possible Problem: FTP Client

Unable to ls and put filenames and folders with non-ASCII characters from the MS-DOS FTP client.

Possible Solution

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.

Possible Solution for Microsoft Windows 95, 98, 2000, NT

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:

  1. Access the Properties/Font tab.

  2. Start up your FTP session in this same command prompt 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
Caveats

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.

MS-DOS Code Pages

The following tables lists some MS-DOS code pages and their corresponding language.

MS-DOS Code Page Language

437

United States

850

Multilingual (Latin I)

852

Slavic (Latin II)

855

Cyrillic (Russian)

857

Turkish

860

Portuguese

861

Icelandic

863

Canadian-French

865

Nordic

866

Russian

869

Modern Greek

Windows ANSI Code Pages

The following table lists Windows ANSI code pages and their language/font.

Windows ANSI Code Page Language/Font

1250

Central European

1251

Eastern European using Cyrillic letters

1252

Western European using Roman letters

1253

Greek

1254

Turkish

1255

Hebrew

1256

Arabic

1257

Baltic

1258

Vietnamese

Possible Problem: Filenames Truncated or Corrupted

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.

Possible Solution

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.

Possible Problem: Unable to Drag and Drop Files Through the Web Interface

Unable to drag and drop files through the Web interface using a multibyte operating system.

Possible Solution

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.

Possible Problem: Unable to Insert Files Through FTP

Unable to insert files correctly through FTP even if the default character set of the FTP server is the same as the client OS.

Possible Solution

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.

Possible Problem: Unable to Perform Context Searches on Multilingual Content

Unable to context search multilingual content in a document after inserting a document into the repository through FTP.

Possible Solution

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>


Go to previous page Go to next page
Oracle
Copyright © 1999, 2002 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Contents
Go To Index
Index