5
Oracle Files

This chapter summarizes release note issues associated with Oracle Files.

The following sections are included in the chapter:

• What's New in This Release?
• Service Configurations and Java Memory Sizing
• Certification and System Requirements
• General Issues
• Configuration Issues
• Oracle Internet Directory Issues
• Globalization Support Issues
• Documentation Issues
• Known Bugs

5.1 What's New in This Release?

The following features are new for Oracle Files Release 2 (9.0.4.1).

5.1.1 Creating Custom Workflows

Oracle Files comes with a default workflow process. Additionally, with this release you can now define a custom workflow process in Oracle Workflow, then register it with Oracle Files. You can design and register any number of custom workflow processes.

For information on how to design and register custom workflows for use in Oracle Files, see the Oracle Files Administrator's Guide, Chapter 7, "Customizing Oracle Files."

5.1.2 Branding the Oracle Files User Interface

Some organizations have "look and feel" standards, such as the requirement to use a particular company logo or color scheme. The Oracle Files Web User Interface can be customized to match those standards.

System Administrators can make the following customizations to the Oracle Files Web UI:

• Oracle Files Web UI colors can be altered.
• Oracle Files Web UI fonts can be changed.
• Particular Oracle Files Web UI images (such as the Oracle Files logo) can be modified or replaced.
• The title bar for the Oracle Files Web UI can be altered.

For more information on custom branding, see the Oracle Files Administrator's Guide, Chapter 7, "Customizing Oracle Files."

5.1.3 Improved Domain Controller Reliability After Machine Failure

The domain controller is an important component of the Oracle Files domain.

In Oracle Collaboration Suite Release 1, the domain could not be easily shut down, started, monitored, or configured in the following situations (although the domain would continue to run):

1. If the primary database listener in a RAC configuration failed.
2. If the machine on which the domain controller was running failed.

The first problem was due to the domain controller using a derived JDBC thin driver URL for communication between the domain controller and the database. To handle this problem, you can now specify a database URL in the registry.xml file. This can then be used to specify a JDBC thick driver URL, which will support Transparent Application Failover (TAF).

To handle the second problem, you can now migrate the domain controller to another middle-tier host. For more information on migrating the domain controller, see the Oracle Files Administrator's Guide, Chapter 5, "Administrative Operations in Oracle Enterprise Manager."

5.1.4 Automatic User Provisioning

In Oracle Files Release 1 (9.0.3.1), users created in Oracle Internet Directory were automatically provisioned in Oracle Files every 24 hours. Shortening this interval required a series of manual steps.

For the current release, the interval has been reduced to 15 minutes. Additionally, users created in Oracle Internet Directory are automatically provisioned in Oracle Files when they log in to Oracle Files for the first time.

5.2 Service Configurations and Java Memory Sizing

In Oracle Files 9.0.4.1, the default service configurations have been changed from allowing unlimited number of sessions to now specifying a maximum number of sessions which can connect to the service. This was done to reduce the likelihood of experiencing java.lang.OutOfMemory errors in the oc4j_opmn.log or application.log.

Due to this change, you may now see the errors:

• Oracle Files Web UI: "The maximum number of concurrent sessions has been reached. Please try your request again later."
• oc4j_opmn.log or application.log: "IFS-20127: Service too busy (maximum concurrent sessions)"

If you see either of these errors, change the Service Configuration from Small to Medium or from Medium to Large, or create your own custom Service Configuration. If you use the Large Service Configuration, or if you make your own customer Service Configuration, you will also need to adjust your Xmx setting.

If you see any java.lang.OutOfMemory errors in your oc4j_opmn.log or application.log files, then you also need to adjust your Xmx setting.

See the following table for more details on why the Xmx setting may need to be changed.

Table 5-1  Xmx Settings

Service Configuration	Setting for IFS.SERVICE.Maximum ConcurrentSessions	Expected number of peak concurrent connected users (PCCUFoot 1)	Recommended size for Xmx (Java maximum memory)	Need to change the default Xmx setting of 256MB?
Small	40	25	64 MB	No
Medium	70	45	162 MB	No
Large	200	125	430 MB	Yes

1 Peak concurrent connected users (PCCU) is the number of users who are logged into Oracle Files and have performed an operation during the peak hour of the day. If you do not know how many that is likely to be, assume 10% of your entire Oracle Files named user population.

See the Oracle Files Planning Guide and the Oracle Files Administrator's Guide for additional information about sizing and performance tuning.

5.2.1 Calculating Xmx Settings

A general guideline for calculating the Xmx setting is:

Xmx = PCCU * 2.8MB

or more exactly,

Xmx = (PCCU * 1.6 sessions per PCCU * 1MB per session) + (DATACACHE.Size * 3KB per data cache object).

Note that the Xmx cannot exceed 4GB. Oracle recommends the Xmx should not exceed 2GB for Oracle Files.

5.2.2 Changing Xmx Settings

To change the Xmx setting for an Oracle Files HTTP node:

1. Edit the file $ORACLE_HOME/opmn/conf/opmn.xml
2. Change the "-Xmx256m" to the appropriate value in the OC4J instance. Here is an example to change the java maximum heap size to be 430MB of memory:

   <oc4j instanceName="OC4J_iFS_files" gid="OC4J_iFS_files">
       <config-file path="/private/9iASHome/j2ee/OC4J_iFS_files/config/server.xml"/>
       <java-option value="-Xmx430m"/>
       <oc4j-option value="-properties"/>
       <port ajp="3001-3100" rmi="3101-3200" jms="3201-3300"/>
       <environment>
         <prop name="LIBPATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/>
         <prop name="DISPLAY" value=":0.0"/>
         <prop name="NLS_LANG" value=".UTF8"/>
         <prop name="LD_LIBRARY_PATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/>
         <prop name="SHLIB_PATH" value="/private/9iASHome/lib32:/private/9iASHome/lib"/>
       </environment>
   </oc4j>
   
   

3. Save the change
4. Restart the OC4J process to have OC4J use the new setting.

To change the Xmx setting for an Oracle Files regular node:

1. Go to the Oracle Enterprise Manager Web site on the host where the Oracle Files node is configured. For example:

   http://myserver.mycompany.com:1810
   
   

2. Log in using the ias_admin username and password.
3. At the Oracle9iAS Home page, click the Oracle Files domain target link.
4. At the Oracle Files Home page, click Node Configurations under the Configuration section.
5. At the Node Configurations page, click the name of the Node you want to change.
6. At the Edit Node page, update Java Command to be the new -Xmx setting. For example, enter "-Xmx430m" to specify 430MB of memory for the Java heap.
7. Click OK to save the change.
8. Restart the node.

5.2.3 Adjusting Service Configuration Settings

Once your peak concurrent connected users (PCCU) exceeds 125, general guidelines for adjusting the IFS.SERVICE settings in the Service Configurations are:

MaximumConcurrentSessions = 1.6 * PCCU

DATACACHE.Size = 400 * PCCU

DATACACHE.EmergencyTrigger = 0.80 * DATACACHE.Size

DATACACHE.UrgentTrigger = 0.75 * DATACACHE.Size

DATACACHE.NormalTrigger = 0.65 * DATACACHE.Size

DATACACHE.PurgeTarget = 0.55 * DATACACHE.Size

 

CONNECTIONPOOL.WRITEABLE.MaximumSize = 0.05 * PCCU

CONNECTIONPOOL.WRITEABLE.TargetSize = 0.04 * PCCU

CONNECTIONPOOL.WRITEABLE.MinimumSize = 5

 

CONNECTIONPOOL.READONLY.MaximumSize = 0.05 * PCCU

CONNECTIONPOOL.READONLY.TargetSize = 0.04 * PCCU

CONNECTIONPOOL.READONLY.MinimumSize = 5

The other settings in the Service Configuration do not generally need to be adjusted.

5.3 Certification and System Requirements

Oracle Files requires either the Oracle Collaboration Suite Release 2 Information Storage database or an external 9.2.0.3 version of the Oracle database. If you are using an external database, you should upgrade to the 9.2.0.3 release of the database if you have not done so already.

5.3.1 Client Certifications

The following client software has been tested and certified for the various protocol servers offered by Oracle Files. Higher operating system and application service pack and minor version number releases are supported.

5.3.1.1 SMB

1. Microsoft Windows NT 4.0 Workstation Service Pack 6a with:
   • Microsoft Office 2000 Service Pack 3, including:
     • Microsoft Word 2000
     • Microsoft Excel 2000
     • Microsoft PowerPoint 2000
     • Microsoft FrontPage 2000
2. Microsoft Windows 2000 Professional Service Pack 3 with:
   • Microsoft Office 2000 Service Pack 3, including:
     • Microsoft Word 2000
     • Microsoft Excel 2000
     • Microsoft PowerPoint 2000
     • Microsoft FrontPage 2000
   • Microsoft Office XP Service Pack 2, including:
     • Microsoft Word 2002
     • Microsoft Excel 2002
     • Microsoft PowerPoint 2002
     • Microsoft FrontPage 2002
   • Microsoft Visio 2000, 2002
   • Microsoft Project 2000, 2002
   • Adobe Acrobat 5.0
3. Microsoft Windows XP Professional Service Pack 1 with:
   • Microsoft Office 2000 Service Release 1, including:
     • Microsoft Word 2000
     • Microsoft Excel 2000
     • Microsoft PowerPoint 2000
     • Microsoft FrontPage 2000
   • Microsoft Office XP Service Pack 2, including:
     • Microsoft Word 2002
     • Microsoft Excel 2002
     • Microsoft PowerPoint 2002
     • Microsoft FrontPage 2002
   • Microsoft Visio 2000, 2002
   • Microsoft Project 2000, 2002
   • Adobe Acrobat 5.0

5.3.1.2 Web Browsers (for URLs, Web User Interface, Enterprise Manager Web Site for Managing Files)

1. Microsoft Windows
   • Netscape Communicator 7.0x
   • Microsoft Internet Explorer 5.5 Service Pack 2
   • Microsoft Internet Explorer 6.02 Service Pack 1
   • Mozilla 1.2.1
2. Macintosh
   • Microsoft Internet Explorer 5.2
3. Linux
   • Netscape Communicator 7.0x
   • Mozilla 1.2.1
4. UNIX
   • Mozilla 1.2.1

5.3.1.3 FTP Clients

1. Windows
   • OnNet FTP 4.0
   • WS_FTP Pro 7.6
   • Cute FTP XP 5.0
   • Cute FTP Pro 3.0 (Windows XP only)
   • Hummingbird 7.0
2. UNIX
   • Command line ftp Solaris 2.7, 2.8, 2.9
3. Macintosh OS X.2
   • Transmit 2.5.1

5.3.1.4 AFP

1. Mac OS X.2 with Microsoft Office Mac X, including:
   • Microsoft Word for Mac OS X
   • Microsoft Excel for Mac OS X
   • Microsoft PowerPoint for Mac OS X

5.3.1.5 NFS Client Support

1. Microsoft Windows
   • Hummingbird NFS Maestro 6.0 (Windows 98, NT)
   • Hummingbird NFS Maestro 7.0 (Windows NT/2000)
   • OnNet 7.0 (Windows 2000 only)
2. UNIX
   • Solaris 2.8 and 2.9
   • Linux Advanced Server 2.1, Kernel 2.4.9-e.16
   • Linux Red Hat 8.0

5.3.1.6 WebDAV: Web Folders

1. Windows XP Professional Service Pack 1
   • Microsoft Office XP Service Pack 2, with Microsoft Internet Explorer 6.02 Service Pack 1 and MSDAIPP.DLL version 10.145.3914.17 with:
     • Microsoft Word 2002
     • Microsoft Excel 2002
     • Microsoft PowerPoint 2002
     • Microsoft FrontPage 2002
     • Microsoft Visio 2002
     • Microsoft Project 2002
     • Adobe Acrobat 5.0
   • Microsoft Office 2000 Service Release 1, with Microsoft Internet Explorer 6.02 Service Pack 1 and MSDAIPP.DLL version 8.103.5219.0
     • Microsoft Word 2000
     • Microsoft Excel 2000
     • Microsoft PowerPoint 2000
     • Microsoft Visio 2000
     • Microsoft Project 2000
     • Adobe Acrobat 5.0
2. Microsoft Windows 2000 Professional Service Pack 3
   • Microsoft Office XP Service Pack 2, with Microsoft Internet Explorer 6.02 Service Pack 1 and MSDAIPP.DLL version 10.145.3914.17 with:
     • Microsoft Word 2002
     • Microsoft Excel 2002
     • Microsoft PowerPoint 2002
     • Microsoft FrontPage 2002
     • Microsoft Visio 2002
     • Microsoft Project 2002
     • Adobe Acrobat 5.0
   • Microsoft Office 2000 Service Pack 3, with Microsoft Internet Explorer 5.5 Service pack 2 and MSDAIPP.DLL version 8.103.3521.0 with:
     • Microsoft Word 2000
     • Microsoft Excel 2000
     • Microsoft PowerPoint 2000
     • Microsoft Visio 2000
     • Microsoft Project 2000
     • Adobe Acrobat 5.0
3. Microsoft Windows NT 4.0 Workstation Service Pack 6a with:

• Microsoft Office 2000 Service Pack 3, with Microsoft Internet Explorer 5.5 Service pack 2 and MSDAIPP.DLL version 8.103.3521.0 with:
  • Microsoft Word 2000
  • Microsoft Excel 2000
  • Microsoft PowerPoint 2000
  • Microsoft FrontPage 2000

5.3.1.7 WebDAV: Oracle FileSync client

1. Windows XP Professional Service Pack 1
2. Windows 2000 Professional Service Pack 3
3. Windows NT Workstation Service Pack 6
4. Windows 98

5.4 General Issues

If a valid SMTP server is not specified during Oracle Files configuration, or a user has a null or invalid e-mail address, any Oracle Files operation that involves an e-mail notification will fail, including Workspace creation.

Since the Subscriber Administrator's password is sent to the Subscriber Administrator by e-mail, the Subscriber Administrator will not be able to perform any administrative tasks if a valid SMTP server is not specified during configuration. For example, the Subscriber Administrator will not be able to manage users, quota, or categories, specify Subscriber settings, or restore files.

See bug 2520112 for more information about this issue.

5.5 HP-UX and Linux: Files Component Issue

Before running $ORACLE_HOME/ifs/files/ifswfsetup, perform the following two tasks:

1. Load the DBMS_LDAP package into information storage database, as follows:
   1. Go to the Oracle home directory of the information storage database and set the ORACLE_HOME and PATH environment variables as follows:

      $ export ORACLE_HOME=<oracle_home path>
      $ export PATH=$ORACLE_HOME/bin:$PATH 
      

   2. Change directory to $ORACLE_HOME/rdbms/admin
   3. Connect to SQL*Plus:

      $ sqlplus system/<system_password> 
      
      

   4. Enter the following SQL commands:

      SQL> spool catldap.log 
      SQL> @catldap.sql 
      SQL> exit 
      
      

2. Add the JDK directory to the PATH environment variable on the mid tier:

   $ export PATH=$ORACLE_HOME/jdk/bin:$PATH
   

5.6 Configuration Issues

If Oracle9iAS Web Cache is enabled, Netscape or Mozilla browsers may not be able to access Oracle Files. See bug 2960325 and bug 2615650 for information on how to resolve this issue.

In addition, using Oracle9iAS Web Cache to cache any content located under /files/content is prevented due to a variety of security issues.

5.7 Oracle Internet Directory Issues

See the Oracle Internet Directory Release Notes for complete information on all known issues. This section covers only those issues specific to Oracle Files.

5.7.1 User Provisioning Failure

Sometimes, users created in Oracle Internet Directory fail to be provisioned in Oracle Files, or you may be unable to add newly provisioned users to Oracle Files Workspaces.

If these problems occur, they are likely due to a failure to set required user attributes in Oracle Internet Directory. The following Oracle Internet Directory user attributes must be non-null for all users:

• sn
• givenName
• mail
• username

The username attribute is specified by the orclCommonNicknameAttribute in the Subscriber's OracleContext. See the Oracle Internet Directory Administrator's Guide for more information on viewing the orclCommonNicknameAttribute.

5.8 Globalization Support Issues

Here are some issues relevant to Oracle Files Globalization Support, formerly known as National Language Support (NLS).

5.8.1 Jagged Bold/Italic Fonts

When running in Japanese, Simplified Chinese, Traditional Chinese, and Korean environments, bold or italicized fonts in the Configuration Assistants appear jagged, and are difficult to read.

This issue is caused by problems in the 1.3.1_02b version of the JDK, and can be resolved by moving to JDK 1.3.1_04. This problem will be fixed in future releases of Oracle Files.

See bug 2377003 and base bug 2220343 for more information.

5.8.2 Character Set Limitations

Oracle Files does not support AL32UTF-8 databases for Asian languages, because Oracle Text does not support Chinese, Japanese, and Korean lexers on AL32UTF-8 databases. On such databases, Chinese, Japanese, and Korean documents will not be indexed or searchable. UTF-8 is the recommended character set for Unicode-based file systems. See also bug 2391425.

5.9 Documentation Issues

This section covers issues relating to Oracle Files or Oracle Collaboration Suite documentation.

5.9.1 Installation Guide Issues

The Oracle Collaboration Suite Installation and Configuration Guide includes a section called "Making Oracle Files Searchable" on page 11-7. You do not need to perform the steps listed in this section because the Oracle Files Configuration Assistant sets up the job to perform indexing automatically.

5.9.2 Administrator's Guide Issues

The Oracle Files Administrator's Guide provides instructions on how to set up the Oracle Workflow Notification Mailer on page 7-10. These instructions only apply to administrators who are creating and registering custom workflows for use in Oracle Files.

Step 1 of these instructions asks administrators to make sure that UNIX Sendmail is configured on the middle-tier host where Oracle Workflow is installed. The following additional information is available to help administrators perform this step.

To determine if Sendmail is running:

1. Log on to the middle-tier host where Oracle Workflow is installed as the "workflow" user.
2. Enter the following command in a UNIX shell prompt:

   $ ps -ef | grep sendmail
   
   

   If Sendmail is running, it will return a valid Sendmail process.

To start Sendmail if it is not running:

1. Type the following command to start Sendmail:

   $ /usr/sbin/sendmail -bd -q15m
   
   

   Note: The location of the Sendmail binary may vary depending on your operating system configuration.

To test if Sendmail is configured correctly:

1. Enter the following commands:

   telnet localhost 25
   helo localhost
   mail from : <>
   
   

   You must get a response of "Sender OK."

2. Next, enter the following:

   rcpt to : <email address of recipient>
   
   

   You must get a response of "Recipient OK."

3. Next, type the following:

   data
   subject : xxx
   yyy
   zzz
   .
   quit
   
   

   Note: You must type a period to mark the end of the e-mail body.

4. Check whether the recipient receives the e-mail. If the recipient receives the e-mail, then Sendmail is configured correctly.

5.10 Known Bugs

The following bugs are known to exist in this Oracle Files release. Workarounds are given when appropriate. The known bugs are grouped in tables by the following processes or components:

• Table 5-2, " Configuration Bugs"
• Table 5-3, " Administration Bugs"
• Table 5-4, " NFS Bugs"
• Table 5-5, " AFP Bugs"
• Table 5-6, " Generic Oracle Files Bugs"
• Table 5-7, " HTTP/WebDAV Bugs"
• Table 5-8, " Windows / SMB / Print Services Bugs"
• Table 5-9, " Oracle FileSync Bugs"
• Table 5-10, " E-mail Bugs"

  Table 5-2  Configuration Bugs

  Bug #	Description	Action
  2944440	Oracle Workflow does not use SSL-enabled Oracle Internet Directory. Although Oracle Files can work with an SSL-enabled Oracle Internet Directory instance, Oracle Workflow will only work with the non-SSL port.	Irrespective of whether Oracle Files is configured to work with the SSL-enabled Oracle Internet Directory port, Oracle Workflow must be configured to work with the non-SSL Oracle Internet Directory port.
  2961091	Workflow does not support Arabic. In this version, Oracle Workflow does not package Arabic in the Workflow product. This is a Workflow limitation.	None.
  2851941	Oracle Files Configuration Assistant cannot be run against a load-balanced multi-node RAC DB. The Oracle Files Configuration Assistant will not work if you are using a multi-node RAC Database and are using a load-balanced port.	During RAC configuration, set up a database server port that is not load balanced. Then, run the Oracle Files Configuration Assistant against this port.
  2960325, 2615650	Set up a workaround to use the Oracle9iAS Web Cache port instead of the HTTP or HTTPS port for Netscape or Mozilla. Users will get the following error when trying to access a page in Oracle Files using Netscape or Mozilla: "Oracle SSO Warning - Unable to process request. Either the requested URL was not specified in terms of a fully-qualified hostname or OHS single sign-on is incorrectly configured. Please notify your administrator." This is caused by the fact the browser is unable to determine the port number for Web Cache. This happens only when you are using Netscape or Mozilla; Microsoft Internet Explorer works as desired.	Explicitly set the Web Cache URLs in the list of Partner applications: As the orcladmin user, log in to the SSO Server at http://<hostname>: <port>/pls/orasso/orasso.home where <hostname> refers to the hostname of the Infrastructure machine and <port> corresponds to the Oracle HTTP Server Port. Click on SSO Server Administration. Choose Administer Partner Applications. Click Add Partner Application to add the instance, or click the pencil icon corresponding to the middle-tier instance to edit an existing one. Enter or change the entries for Home URL, Success URL, and Logout URL. For standard HTTP access: Home URL: http://<mid-tier hostname>:<Web Cache HTTP Listen port> Success: http://<mid-tier hostname>:<Web Cache HTTP Listen port>/osso_login_success Logout: http://<mid-tier hostname>:<Web Cache HTTP Listen port>/osso_logout_success For HTTPS access: Home: https://<mid-tier hostname>:<Web Cache HTTP Listen (SSL) port> Success: https://<mid-tier hostname>:<Web Cache HTTP Listen (SSL) port>/osso_login_ success Logout: https://<mid-tier hostname>:<Web Cache HTTP Listen (SSL) port >/osso_logout_ success Click Apply and then Ok to save the changes.

  Table 5-3  Administration Bugs

  Bug #	Description	Action
  2408925	Oracle Enterprise Manager allows illegal characters for service name. Service Configuration objects that have ';' embedded in their names will cause problems.	None. This bug stems from a problem in the underlying OC4J layer of the software.
  2867479	Users occasionally receive an "Unable to Get User" error. This error message occurs in configurations that use a load balancer for multiple Oracle Internet Directory servers. The error occurs when a user tries to log in to the domain after a certain period (equal to the connection timeout period on the load balancer) of inactivity on the middle tier against the Oracle Internet Directory server. The problem is more likely to happen if there are very few users on the system. The greater the number of active users, the less likely the problem will occur, because the level of interaction between the middle tiers and Oracle Internet Directory automatically increases, which ensures that the connection between the middle tier and Oracle Internet Directory does not time out.	The user can retry the operation, which should generally work. Alternatively, increase the connection timeout period on the load balancer that is used to connect to the Oracle Internet Directory servers.
  2746006	Cannot stop the Oracle Files domain if the Oracle Files schema password is changed. The schema password for Oracle Files is required in order to be able to start or stop a domain.	Do not change the schema password for a running Oracle Files instance.
  2852809	Need to restart the Oracle Files domain any time the default Subscriber is changed on the LDAP server. If the default Subscriber is changed in Oracle Internet Directory after the Oracle Files domain has been started, users in the new default Subscriber will be created with usernames of the format username@subscribername.	Restart the domain, and delete the old default subscriber from Oracle Files after changing the default Subscriber in Oracle Internet Directory.

  Table 5-4  NFS Bugs

  Bug #	Description	Action
  1749601	Unable to chgrp in Oracle Files NFS. A chgrp does not have any effect on mode for a file.	None. The security model is different and this has no impact.
  1749621	Unable to chmod in Oracle Files NFS. A chmod does not have any effect on mode for a file.	None. The security model is different and this has no impact.
  1750049	Mode attributes cannot be set. Cannot change the permission mode bits through Oracle Files NFS.	None. The security model is different and this has no impact.
  1749778	Links cannot be created using Oracle Files NFS. No links (symbolic, soft, or hard) can be created in Oracle Files NFS.	None. The security model is different and this has no impact.
  2333774	Cannot copy files or folders where a non-standard ASCII character is the first character in the name. Folders and files that have non-standard ASCII characters as the first character cannot be copied using NFS Maestro.	Use other NFS clients; this problem appears to be a Maestro limitation
  2480035	The Oracle Files NFS server cannot be used after instance failover in RAC database. After an Oracle instance failover, the Oracle Files NFS server cannot be used. Any operation, including copy, upload, etc. generates an I/O Error being prompted to the user.	Restart the Oracle Files NFS Server from the Oracle Enterprise Manager Web site if the server is rendered unusable after the content cache shutdown.

  Table 5-5  AFP Bugs

  Bug #	Description	Action
  1990453	File Encrypt fails when using Mac OS Finder to encrypt files on Oracle Files (mounted as AFP volume). The Mac OS File-->Encrypt utility creates temporary files containing * in their names. However, Oracle Files does not allow filenames to contain an asterisk.	Do not try to encrypt a file from a Mac. Instead, encrypt the file locally, on the Mac, and then copy the encrypted file to Oracle Files through AFP.
  2380571	Size of Mac file does not take into account size of resource fork. The resource fork is not being included in size computations; thus, the size of the document may not be accurate.	None.
  2463376	Finder does not refresh folder listing. When the contents of a folder is updated by adding, removing, or modifying files, the AFP finder does not refresh the folder listing.	Log out and log back in to work around this problem.
  2994830	Making a file non-versioned in the Oracle Files Web interface can cause the file to vanish. Documents in the Oracle Files application can be versioned using the Web interface. If a Macintosh user is logged in using AFP and viewing a folder with a versioned file, the file is visible but read-only. If a user logs in to the Web interface and changes this file so that it is now NOT versioned (by deleting all saved versions), the file viewed by the AFP user may vanish from the Macintosh client folder listing.	The workaround is for the Macintosh user to logout and log back in to AFP. This will refresh the folder listing.
  2719007	The default protocol character set logic is applied globally. The AFP server protocol (or, "command") encoding is a constant value that is applied globally for the server. Every user session that connects to the AFP server uses the same encoding; there is no way to override this encoding on a per-user or per-session basis. If there are AFP clients (Macintosh clients) that need to connect to the AFP server with a different encoding, they will not be able to do so unless the AFP server encoding is changed accordingly.	The workaround so that multiple clients with differing encodings can use the AFP server together is to run multiple AFP servers. To do this, use multiple middle-tier machines, each running an AFP server with the desired encoding. The AFP server encoding is specified in the property IFS.SERVER.PROTOCOL.AFP.Encoding.
  2994813	Cannot open documents under or upload into AllPublic/Users/... The AFP server for the Oracle Files application allows Macintosh clients to mount either the "user's home directory" or the "AllPublic" directory as network volumes. The AllPublic volume has a limitation where files under the "Users" folder inside the AllPublic volume cannot be opened reliably, and new files cannot be uploaded into the "Users" folder. Files and folders can be listed, however, and files can be copied to the local disk.	To open files, copy them to the local disk first, then open them. To upload files, use the "user's home directory" mountpoint (volume) instead of the AllPublic volume.
  2995643	Microsoft PowerPoint files with long names cannot be saved directly. PowerPoint files with file names longer than 31 characters appear truncated when you try to save using AFP. For example: long_long_long_long_lo?5A0B.ppt The user will be able to open the PowerPoint file and copy it to the local hard disk, just like any other file. Once opened in PowerPoint, however, if the user makes changes to the file and issues a "Save" command, an error will be displayed: "Error accessing file <filename>." The changes will not be saved and the original file that was opened will be deleted (moved to the Trash and renamed "PowerPoint Temp 0" or similar).	If you want to save changes and keep the file, issue a "Save As" command, either by choosing the command from the menu or toolbar, or by clicking "Yes" in the dialog box that is displayed when the file is closed. Choose a different name for the saved file. Once you do so, the new file will be saved correctly.

  Table 5-6  Generic Oracle Files Bugs

  Bug #	Description	Action
  2473166	Sorting in Browse Tables does not work in Netscape 4.7x. Sorting by any column in a browse table in Netscape 4.7x does not sort.	Use IE 5.x and above, or Netscape 7.0, as the browser.
  2414889	Searches don't exclude AFP resource forks. It is possible for Oracle Files Advanced Searches to include AFP resource forks in search results. Any actions performed on these files will result in an error.	Ignore these files in the search results.
  2222609	Oracle Files only supports Oracle Single Sign-On via IE 5.x and above or Netscape 7.0x. Accessing Oracle Files with any other Web client will cause the user to have to always log in.	To use Oracle Single Sign-On so that you only have to log in once, use IE 5.x and above or Netscape 7.0x as your browser.
  2391425	Content searching will not return any documents if using the AL32UTF-8 database character set and searching in Japanese, Chinese, or Korean. Oracle Text currently does not support the Chinese, Japanese, or Korean lexers in a AL32UTF-8 database; therefore, you cannot search on Chinese, Japanese, or Korean documents, since they are not indexed. Depending on your locale setting and the database session language, Oracle Files configuration may fail when the Oracle Text index is created, or the configuration may succeed but content searching on Chinese, Japanese, or Korean documents will always return zero hits.	There are two options: Alter your database character setting from AL32UTF-8 to UTF-8. Install Oracle Files into a different database with a UTF-8 character setting.

  Table 5-7  HTTP/WebDAV Bugs

  Bug #	Description	Action
  2337719	URLS with semi-colons return a 404 error. URLs that have ';' embedded will cause problems.	None. This bug stems from a problem in the underlying OC4J layer of the software.
  2386806	URLs with '%' in them do not work. URLs that have '%' embedded will cause problems.	None. This bug stems from a problem in the underlying OC4J layer of the software.
  2355830	WebDAV locking does not work with Dreamweaver 4. Accessing content on Oracle Files from Dreamweaver 4 via WebDAV does not work properly. The first issue is that Dreamweaver 4 is not supporting the correct XML that is returned from the server. This causes Dreamweaver 4 to improperly display to the user the correct content stored on the server. Due to this problem, implicit locking of documents by Dreamweaver 4 is not supported.	Downloading a patch from Macromedia for Dreamweaver 4 will solve all but the implicit locking issue. The locking issue is still an open issue. However, if you are using Dreamweaver MX, downloading the Dreamweaver MX v6.1 Updater from the Macromedia Web site will fix this problem: http://www.macromedia.com/ support/dreamweaver/ downloads_updaters.html
  2955251	Cannot connect to Oracle Files through WebDAV cookie-less client. If multiple Oracle Files middle tiers are fronted by a load balancer that relies on cookies to load balance requests, WebDAV clients that do not store cookies will not be able to access that Oracle Files instance via the load balancer.	Configure the load balancer to use IP addresses instead of cookies for load balancing.
  2614217	Uploading a document via Netscape returns an Oracle SSO warning error. When the Oracle Collaboration Suite middle tier is configured, it registers with the Single Sign-On server using the Oracle HTTP Server port. It is incorrect to register the HTTP Server port if Oracle9iAS Web Cache is configured.	For mod_osso to work correctly, the Single Sign-On registration for this middle tier must be corrected manually. For detailed information on how changes in hostname and port affect Oracle9iAS, and specifically how mod_osso and Oracle9iAS Single Sign-On Server may be affected, see Chapter 7, "Component Configuration Dependencies" in the Oracle9i Application Server Administrator's Guide.
  2697262	WebDAV drag-and-drop download can result in 0-byte file. On Windows NT using Internet Explorer 5.5, dragging a file from a Web Folder on Oracle Files to the local PC file system can result in a 0-byte file if the file is locked by another user on Oracle Files.	Apply Internet Explorer patch Q299618.

  Table 5-8  Windows / SMB / Print Services Bugs

  Bug #	Description	Action
  1113581	Cannot delete or rename versioned files in SMB. Attempts to delete or rename a versioned file in SMB result in a failure message indicating that all or part of the file may be locked. Certain applications, such as Microsoft Word and Microsoft Excel, save their work by deleting old versions of the document. Because this would cause a loss of data attributes and compromise the versioning features of Oracle Files, the Oracle Files SMB server does not allow deletion or renaming of versioned files.	Use the Oracle Files Web interface to delete the file.
  2472522	Windows generates multiple print jobs. Certain versions of Windows create multiple print jobs in Oracle Files when the user requests to print a single document. These extra print jobs have no content, and will not result in paper use. They will, however, show up in the queue for a short period of time. The correct document will still be printed.	None.
  2344972	Cannot print to printer that is restricted by username and password. When connecting to a printer from Windows NT/2000, the user is not prompted for a username and password. If the share is restricted by a username and password, then the user will not be able to print.	There are two courses of action: Before mounting the printer, map a network drive to a file share on the same server. When the user is prompted for his username and password, enter the same username and password that will subsequently be used for accessing the printer. Before mounting the printer, open a DOS prompt and enter: > net use \\<server-name>\<printer-name> <password> /USER:<username> Then mount the printer, using the exact same name for the printer share.
  2424896	Server property for enabling printing does not appear in SMB Server Configuration. In order to enable printing via SMB, the Oracle Files administrator must set a property to specifically enable the sharing of printers. This property will not be listed automatically as one of the SMB server configuration properties.	The Oracle Files administrator must manually add the IFS.SERVER.PROTOCOL.SMB. EnablePrinting property and set its value to TRUE.
  2890902	Files lose metadata when they are copied between folders using SMB. Copying a file from Windows using a network drive mapped to the Oracle Files SMB server will only copy the contents of the file. Oracle Files metadata, such as categories, will not be copied. This is a limitation of the Windows operating system. The Windows operating system does not handle Oracle Files metadata, and therefore does not copy this metadata when copying a file. Under some circumstances, a file cut and paste operation in Windows Explorer will result in a file move rather than a file copy. Oracle Files metadata is maintained when a file move is performed.	The Oracle Files Web interface should be used to copy files that have metadata. Copying a file using the Oracle Files Web interface will maintain the file's metadata.
  3020371	Cannot list SMB mountpoints with Hummingbird NFS client. When a machine has the Hummingbird NFS client installed, the machine will attempt to use NFS when told to connect to a server that supports both NFS and SMB. When a user clicks Start -> Run and types \\servername, the Hummingbird NFS client will display the NFS mountpoints in the window that comes up. SMB mountpoints and printers will not be displayed.	There are many possible workarounds for this issue: Mount the SMB mountpoints and printers directly, using the Map Network Drive dialog or the Add Printer Wizard. Disable the NFS server on the machine that is running the SMB server. Uninstall the Hummingbird NFS client on the machines that need to list SMB mountpoints on a server.
  2995548	User may need to manually cancel blank jobs after printing. Some Windows clients may add blank print jobs ahead of the actual print job when a user prints to Oracle Files Print Services. These jobs may get "stuck" in the queue.	Users will need to double click on the printer icon and manually cancel the blank print jobs if their document is not getting printed.
  3008391	Users may not be able to add printers through the Add Printer Wizard. When a user adds a printer through the Add Printer Wizard from Windows clients, they may get the error "Printer cannot be found."	Do not use the Add Printer Wizard to add a printer. Instead, click Start -> Run. Then, type \\<servername> and press Enter. In the window that appears, double-click on the printer you wish to add.

  Table 5-9  Oracle FileSync Bugs

  Bug #	Description	Action
  2374879	Server-side folders with the percent (%) character in their names are not synchronized. Folders and files that have '%' embedded in their names will not be synchronized during the sync process.	None. This bug stems from a problem in the underlying OC4J layer of the software.

  Table 5-10  E-mail Bugs

  Bug #	Description	Action
  2520112	Unexpected error occurs on creation of Workspaces when there is a problem in a user's e-mail address. If a valid SMTP server is not specified, or a user has a null or invalid e-mail address, any Oracle Files operation that involves an e-mail notification will fail.	1) Ensure a valid SMTP server is specified in the FilesBaseServerConfiguration parameter: IFS.SERVER.APPLICATION.UIX. SmtpServer 2) Ensure that users have valid non-null e-mail addresses.

  Table 5-11 User Synchronization Bugs

  Bug #	Description	Action
  2971002	Givenname is not sync'ed. FilesOidUserSynchronizationAgent does not synchronize givenname attribute with Oracle Files	Use Web Client or Bulk Administration Tool to change givename attribute in Oracle Files.