| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1.1) for Windows Part Number B12240-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes Release 2 (9.0.4.1.1) for Windows Part Number B12240-02 |
|
|
View PDF |
This chapter summarizes release note issues associated with Oracle Files.
The following sections are included in the chapter:
The following features are new for Oracle Files Release 2 (9.0.4.3).
|
Note: Oracle Files Release 2 (9.0.4.3) is part of the Oracle Collaboration Suite Release 2 (9.0.4.1.1). |
The Oracle Workflow configuration process for adding additional languages has been simplified.
In addition to the nine new languages supported by Oracle Collaboration Suite for Release 2, the Oracle Files Web user interface and the Oracle FileSync user interface have been translated into Russian.
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.
Also new for this release, you can now define an action to be performed when a workflow process is approved, such as moving or copying files to a specified location, versioning the files, or deleting the files.
|
See Also: Oracle Files Administrator's Guide for information on how to design and register custom workflows for use in Oracle Files |
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
|
See Also: Oracle Files Administrator's Guide for more information on custom branding |
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):
If the primary database listener in a RAC configuration failed.
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 supports Transparent Application Failover (TAF).
To handle the second problem, you can now migrate the domain controller to another middle-tier host.
|
See Also: Oracle Files Administrator's Guide for more information on migrating the domain controller |
In Oracle Files Release 1 (9.0.3.2), 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 through the Web user interface.
In Oracle Files 9.0.4.3, the default service configurations have been changed from allowing an 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 OC4J_iFS_files.default_island.1 or in application.log.
Due to this change, you may now see the following errors:
Oracle Files Web UI: "The maximum number of concurrent sessions has been reached. Please try your request again later."
OC4J_iFS_files.default_island.1 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 create your own customer Service Configuration, you must adjust your -Xmx setting.
If you see any java.lang.OutOfMemory errors in your OC4J_iFS_files.default_island.1 or application.log files, then you also need to adjust your -Xmx setting.
Table 5-1 provides details on why the -Xmx setting may need to be changed.
|
Note: The term PCCU refers to 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. |
Table 5-1 Xmx Settings
| Service Configuration | Setting for IFS.SERVICE.Maximum ConcurrentSessions | Expected PCCU | 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 |
|
See Also: Oracle Files Planning Guide and the Oracle Files Administrator's Guide for additional information about sizing and performance tuning |
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)
The Xmx setting cannot exceed 4GB. Oracle Corporation recommends that the Xmx setting should not exceed 2GB for Oracle Files.
To change the Xmx setting for an Oracle Files HTTP node:
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
Log in using the ias_admin username and password.
At the Oracle9iAS Home page, click OC4J_iFS_files.
Click Server Properties.
Update Java Options to be the new -Xmx setting. For example, enter -Xmx430m to specify 430MB of memory for the Java heap.
Click Apply to save the change.
Restart OC4J_iFS_files from the Oracle9iAS Home page.
To change the Xmx setting for an Oracle Files regular node:
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
Log in using the ias_admin username and password.
At the Oracle9iAS Home page, click the Oracle Files domain target link.
At the Oracle Files Home page, click Node Configurations under the Configuration section.
At the Node Configurations page, click the name of the node you want to change.
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.
Click OK to save the change.
Restart the node.
Once your peak concurrent connected users (PCCU) exceed 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.
Oracle Files requires one of the following Oracle database versions:
Oracle Collaboration Suite Release 2 Information Storage database, with 9.2.0.4 (or later) database patch set
External 9.2.0.4 (or later) version of the Oracle database
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.
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
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 2000
Microsoft Excel 2000
Microsoft PowerPoint 2000
Microsoft FrontPage 2000
Microsoft Visio 2000, 2002
Microsoft Project 2000, 2002
Adobe Acrobat 5.0
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 2000
Microsoft Excel 2000
Microsoft PowerPoint 2000
Microsoft FrontPage 2000
Microsoft Office 2003 Professional, including:
Microsoft Word 2003
Microsoft Excel 2003
Microsoft PowerPoint 2003
Microsoft FrontPage 2003
Microsoft Visio 2000, 2002, 2003
Microsoft Project 2000, 2002, 2003
Adobe Acrobat 5.0
Microsoft Windows
Netscape Communicator 7.x
Microsoft Internet Explorer 5.5 Service Pack 2
Microsoft Internet Explorer 6.02 Service Pack 1
Mozilla 1.2.1, 1.1
Macintosh
Microsoft Internet Explorer 5.1, 5.2
Linux
Netscape Communicator 7.x
Mozilla 1.2.1, 1.1
UNIX
Mozilla 1.2.1, 1.1
Microsoft Windows
OnNet FTP 4.0
WS_FTP Pro 7.6
Cute FTP Pro 3.0
Hummingbird 7.0
UNIX
Command line ftp Solaris 2.8, 2.9
Macintosh OS X.2
Transmit 2.5.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
Microsoft Windows
Hummingbird NFS Maestro 6.0 (Windows NT)
Hummingbird NFS Maestro 7.0 (Windows NT/2000)
OnNet 7.0 (Windows 2000 only)
UNIX
Solaris 2.8 and 2.9
Linux Advanced Server 2.1, Kernel 2.4.9-e.16
Linux Red Hat 8.0
Microsoft 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 with:
Microsoft Word 2002
Microsoft Excel 2002
Microsoft PowerPoint 2002
Microsoft Visio 2002
Microsoft Project 2002
Adobe Acrobat 5.0
Microsoft Office 2003 Professional, with Microsoft Internet Explorer 6.02 Service Pack 1 and MSDAIPP.DLL version 11.0.5510.0 with:
Microsoft Word 2003
Microsoft Excel 2003
Microsoft PowerPoint 2003
Microsoft Visio 2003
Microsoft Project 2003
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 2002
Microsoft Excel 2002
Microsoft PowerPoint 2002
Microsoft Visio 2002
Microsoft Project 2002
Adobe Acrobat 5.0
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 2002
Microsoft Excel 2002
Microsoft PowerPoint 2002
Microsoft FrontPage 2002
Here are some general operations and administration issues you should be aware of before using Oracle Files. The bugs referred to are described in more detail in Section 5.10, "Known Bugs".
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.
When creating a Web Folders mapping in Windows XP, you must specify the port explicitly, even if you are using port 80. For example:
http://foo.acme.com:80/files/content
If you do not specify a port number, Windows XP may use the File System Redirector, which is not supported for use with the Oracle Files WebDAV server.
If you open an HTML file from the Oracle Files Web UI using Internet Explorer, and then choose File > Save As to download the content, the file will be saved as type Web Page, complete by default. If you save the file as this file type, any relative links in the HTML file will be re-written as absolute links due to the default behavior of Internet Explorer.
If you do not want to see this behavior, choose another file type (such as Web Page, HTML only) from the Save As dialog box before saving. Alternatively, if you right-click the file from the Browse Files page and choose Save Target As..., you will not see this behavior.
Here are some issues related to configuring Oracle Files.
This section discusses configuration issues with Oracle Workflow.
In order to build custom workflows, you need to use Oracle Workflow Builder on a Windows NT, 2000, or XP system. You can download Oracle Workflow Builder from the Oracle Technology Network (OTN). To do this, follow these steps:
Point a Web browser at http://otn.oracle.com.
Click the Downloads icon in the upper right corner of the page.
Click Oracle Collaboration Suite.
Follow the instructions on this page to download Oracle Workflow Builder. The version you want is the Oracle Workflow Embedded Release 2.6.2 for Microsoft Windows 98/NT/2000/XP.
|
See Also:
|
After you have created a custom workflow, you need to make it available to Oracle Files by loading the custom workflow into the Workflow schema. To do this, save the custom workflow as a .wft file, copy it to the middle tier machine where the workflow schema resides, and load the .wft file using wfload:
%ORACLE_HOME%\bin\wfload -u workflow_schema_name/workflow_schema_password@database _URL workflow_file_location/workflow_file_name
For example:
%ORACLE_HOME%\bin\wfload -u OWF_MGR/MY_PASSWORD@qa8-sun.us.oracle.com/private /oracle/MyCustomWorkflow.wft
|
See Also: Oracle Files Administrator's Guide for information about registering a custom workflow with Oracle Files |
If you are using an external Oracle 9.2.0.3 database other than the Oracle Collaboration Suite Information Store, you need to confirm that the Catalog for the LDAP PL/SQL API has been loaded in this database.
To confirm the presence or absence of the Catalog, run the following SQL*Plus command as the SYS user on the database tier:
DESC DBMS_LDAP
If no such package exists, run the catldap.sql script that is present in %ORACLE_HOME%\rdbms\admin as the SYS user on the database tier. This creates the catalog in the database.
|
Caution: Make sure that you runcatldap.sql in the Oracle home of the database; do not run the script from the middle tier or infrastructure Oracle homes. |
You cannot use the same Oracle Workflow schema to support two different Oracle Files domains. If you have multiple Oracle Files domains being used by the same database instance, you must have different Oracle Workflow schemas (as is the case with Oracle Files schemas).
During configuration, you may want to choose an Oracle Workflow schema name different from the default value of OWF_MGR to ensure that you are not reusing an existing Oracle Workflow schema.
As new Oracle Files users are created in Oracle Internet Directory, run the following SQL*Plus commands to provision the new users into Oracle Workflow:
set serveroutput on size 1000000
declare
ret_code boolean;
begin
ret_code := wf_ldap.synch_changes();
if (ret_code) then
dbms_output.put_line('WF_LDAP.Synch_Changes successful');
else
dbms_output.put_line('WF_LDAP.Synch_Changes failed. Please try again');
end if;
exception
when others then
dbms_output.put_line('Exception encountered : ' || sqlerrm);
end;
/
|
Note: It is recommended that you create aDBMS_JOB that will automatically run wf_ldap.synch_changes() at regular intervals. |
This section covers Oracle Internet Directory issues specific to Oracle Files.
|
See Also: Oracle Internet Directory Release Notes athttp://otn.oracle.com/documentation, for complete information on all known issues. |
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 Also: Oracle Internet Directory Administrator's Guide for more information on viewing theorclCommonNicknameAttribute |
Here are some issues relevant to Oracle Files Globalization Support, formerly known as National Language Support (NLS).
When using the Save As command in Internet Explorer to save documents with multibyte filenames, the filename in the Save As dialog appears corrupted.
To fix this, enable the Always send URLs as UTF-8 option in Internet Explorer:
Select Tools > Internet Options.
Select the Advanced tab.
Check the Always send URLs as UTF-8 option.
Click OK.
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.
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.
This section covers issues relating to Oracle Files documentation.
The Oracle Files Administrator's Guide provides instructions on how to change font characteristics in the Oracle Files Web UI on page 7-2. To do this, administrators need to edit an XML style sheet called custom.xss.
As part of this process, administrators also need to copy text from another XML style sheet called blaf.xss. The following additional information is available to help administrators perform this step.
To change font characteristics in the Oracle Files Web UI:
Make a backup copy of custom.xss on each of your middle tiers. The custom.xss file is located in the following directory:
%ORACLE_HOME%\j2ee\OC4J_iFS_files\applications\files\files\cabo\styles
Open blaf.xss, located in the following directory:
%ORACLE_HOME%\j2ee\OC4J_iFS_files\applications\files\files\cabo\styles\blaf.xss
Copy the following entries from blaf.xss:
<!-- The default font family --> <style name="DefaultFontFamily"> <property name="font-family">Arial,Helvetica,Geneva,sans-serif</property> </style> <!-- The default font --> <style name="DefaultFont"> <includeStyle name="DefaultFontFamily"/> <property name="font-size">10pt</property> </style>
Be careful not to edit this file.
Open the live copy of custom.xss and paste in the text from step 3.
Modify the two entries as you choose. For example, you could change the entries to the following:
<!-- The default font family --> <style name="DefaultFontFamily"> <property name="font-family"> Times New Roman,Arial,sans-serif </property> </style> <!-- The default font --> <style name="DefaultFont"> <includeStyle name="DefaultFontFamily"/> <property name="font-size"> 9pt </property> </style>
Save your changes to custom.xss on each of your middle tiers.
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
| Bug No. | 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 | Arabic is not available in Oracle Workflow.
In this version, Oracle Workflow does not package Arabic in the Workflow product. This is an Oracle Workflow limitation. |
None. |
| 2851941 | The 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. |
| 2960519 | Re-use of the Oracle Files schema configured and set up with the same middle tier will cause problems with Agents.
If you run the Oracle Files Configuration Assistant more than once in the same Oracle home, against the same Oracle Files domain and schema, the Agents in the local node will become deactivated if the following are true:
|
You may see this problem if you need to run the Oracle Files Configuration Assistant a second time due to failures during the post-upgrade process.
You can avoid this behavior by not selecting the Run Agents checkbox in the Node Configuration screen of the Oracle Files Configuration Assistant. Alternatively, if you have already run the Oracle Files Configuration Assistant more than once and your Agents have become deactivated, you can solve the problem by going to the Oracle Enterprise Manager Web site and setting all the Agents to "Active" for the affected node. You must activate each Agent individually. |
| 2520112 | 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. |
|
| 2391425 | NLS: IFSCONFIG fails in Japanese environment on AL32UTF8 database.
Oracle Text does not support Japanese lexer on AL32UTF8 databases; hence Oracle Files does not support AL32UTF8 databases for Asian languages. |
Use UTF8 for the database instead of AL32UTF8. |
| 3124801 | Oracle Files Release 2 (9.0.4.3) installs an extra documentation directory.
Oracle Files shipped with the following outdated directory: %ORACLE_HOME%\ifs\files\doc\ The information in this directory is old and is not meant to be used. |
Do not refer to the documents under this directory. Instead, refer to the documents on the Oracle Collaboration Suite Documentation CD. |
| 3214142 | Java Command for regular nodes needs to be changed.
The current Java Command for Oracle Files regular nodes includes the following argument: -XX:+OverrideDefaultLibthread This argument should be removed. Retaining this argument can cause problems. |
Perform the following steps:
See Also: Oracle Files Administrator's Guide for more information about changing node configurations and restarting regular nodes. Caution: Make sure that any new node configuration you create does not include this argument. |
| 2522186 | Oracle Files Configuration Assistant cannot establish a connection to a RAC database with the thin driver.
The Oracle Files Configuration Assistant attempts to make a connection to a RAC database as SYS 'AS SYSDBA' using the thin JDBC driver, which fails. |
|
| 3016906 | Oracle Files configuration against Windows 64-bit Oracle9i Database Server 9.2 database fails.
The database is missing the |
There are two possible solutions:
|
| 3313333 | Oracle Workflow help is not configured by default.
For Oracle Workflow Release 2.6.2 and earlier, the help must be manually configured. |
First, unzip the help files:
Next, configure the
|
Table 5-3 Administration Bugs
| Bug No. | Description | Action |
|---|---|---|
| 2867479 | User authentication occasionally fails when accessing Oracle Files.
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. |
| 2408925 | Oracle Enterprise Manager allows illegal characters for service name.
Service Configuration objects that have ';' embedded in their names will cause problems. |
Do not use ';' in service names. |
| 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 |
Restart the domain, and delete the old default subscriber from Oracle Files after changing the default Subscriber in Oracle Internet Directory. |
| 3200712 | Oracle Enterprise Manager node statistics page reports that the OS is Windows 2000 instead of Windows 2003.
For an Oracle Files node running in JDK 1.3.1 on Windows 2003 server, the Node Performance and Statistics page in Oracle Enterprise Manager Web site displays the node's operating system name as Windows 2000 instead of Windows 2003. |
None. This is a JDK 1.3.1 limitation. |
| 2573630 | Windows network/domain user with admin privileges cannot start the domain controller or nodes on Oracle Enterprise Manager Web site.
This is a limitation of Oracle Enterprise Manager for this release. |
Set up a local user with "logon as batch job" privileges and use that local user to start the domain controller and nodes from Oracle Enterprise Manager Web site.
Alternatively, you can use the network user to start the domain controller and nodes from the command line via |
| 3231664 | Cannot close the command window used to run ifsctl.bat.
Due to Windows limitations, you cannot close the command window from which you are running |
Do not close the command window from which you are running ifsctl.bat.
Alternatively, you can use the Oracle Enterprise Manager Web site as a local user to manage the domain and nodes. |
Table 5-4 Generic Oracle Files Bugs
| Bug No. | Description | Action |
|---|---|---|
| 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. |
| 3200325 | Oracle Collaboration Suite Search only supports exact matches on User Name for Oracle Files content.
Oracle Collaboration Suite Search for Oracle Files ignores the content of the User Name field if the value provided does not match a valid Oracle Files user. |
Provide an exact match in the Oracle Collaboration Suite Search User Name field when searching Oracle Files content. Do not use wildcards. |
| 2518871 | Files with multibyte file names that were zipped with the Oracle Files Zip feature must be unzipped with a utility that supports UTF8.
If you use the Zip feature in the Oracle Files Web user interface to zip a file or set of files that have multibyte file names, you cannot use WinZip to unzip the file because WinZip does not support UTF8. |
Unzip the file using either the Unzip feature in the Oracle Files Web user interface, or use the JAR utility to unzip the file locally. |
| 3078486 | Users with punctuation in their passwords may have problems.
If Oracle Files users have punctuation in their passwords (for example, ';' '%' '#'), these users may not be able to enable protocol access in Oracle Files. In addition, these users may be unable to change their SSO passwords using the Oracle Files Web UI. |
To solve this problem, choose one of the following options:
Option 1
Option 2 If you want to use case-sensitive authentication, you should not permit users to include punctuation in their passwords. Use Oracle Internet Directory tools to change the passwords of existing users that have punctuation in their passwords. |
Table 5-5 HTTP/WebDAV Bugs
| Bug No. | Description | Action |
|---|---|---|
| 2393968, 2386806, 2337719 | URLS with '#,' '%,' or ';' in them do not work.
URLs that have these characters embedded will cause problems. |
Do not use '#,' '%,' or ';' in URLs. |
| 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:
|
| 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.
See Also: Oracle9i Application Server Administrator's Guide for detailed information on how changes in hostname and port affect Oracle9iAS, and specifically how |
| 2697262 | WebDAV drag-and-drop download can result in 0-byte file.
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. This appears to be caused by |
Upgrade Internet Explorer to the latest Service Pack.
Ensure the client environment conforms to the supported configuration listed in Client Certifications for WebDAV: Web Folders. |
| 3006494 | Cannot create multiple Web Folder mappings that use different user credentials on the same client computer.
Because of a Web Folders limitation, Oracle Files does not support logging in to Web Folders as different users from the same Windows client. Web Folders caches user credentials, so if you first create a Web Folders mapping as user1, and then create a second mapping as user2, after user1's connection is disconnected, user2 will be able to access user1's content. |
Do not create Web Folder mappings that use different user accounts from the same client computer.
Alternatively, you can restart the Windows client. |
Table 5-6 NFS Bugs
| Bug No. | Description | Action |
|---|---|---|
| 1749601 | Unable to chgrp in Oracle Files NFS.
A |
None. The security model is different and this has no impact. |
| 1749621 | Unable to chmod in Oracle Files NFS.
A |
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. |
Table 5-7 AFP Bugs
| Bug No. | 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. |
| 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. |
| 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. |
Table 5-8 NTFS Bugs
| Bug No. | Description | Action |
|---|---|---|
| 1289569 | Delete appears to work on some files that a user should not be able to delete.
No error messages are given when a user tries to delete a document that the user does not have permission to delete, or when a user tries to delete special objects, such as the inbox folder, which cannot be deleted. |
Although no error message appears, the document or folder is not deleted. Selecting Refresh in the Windows Explorer will cause the Windows Explorer to refresh the display and the document or folder will reappear. |
| 1113581 | Cannot delete or rename versioned files in NTFS.
Attempts to delete or rename a versioned file in NTFS 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 NTFS server does not allow deletion or renaming of versioned files. |
Use the Web interface to delete the file. |
| 1412048 | In Windows NT with Service Pack 6, some .txt documents cannot be modified and saved in Wordpad.
When editing a document with the Read Only attribute with Wordpad on NT 4.0 with Service Pack 6, you will not be able to save the document to a different name using the Save As dialog box. When trying to save the document under a different name you will receive an error stating that the document cannot be accessed because it is in use by another application. |
Remove the Read Only attribute before editing the document with Wordpad, or use another editor, such as Notepad. |
| 1846693 | Cannot start NTFS protocol server from terminal services client session.
Attempting to start NTFS protocol server from a terminal services session results in the following error message:
The NTFS protocol server cannot be started from within a Windows terminal services client session. |
Start Oracle Files from the Windows server console rather than trying to start it from a terminal services client session. Windows terminal services client sessions can only access devices that are already defined at the time the terminal session starts. |
| 1937209 | Cannot drag mail from Outlook 2000 to a drive mapped to Oracle Files.
Using drag and drop to move mail from Outlook 2000 to a drive mapped to Oracle Files results in an error message stating that the file cannot be dropped to this location, and a zero length file is created on the mapped drive. This error occurs when using Outlook 2000 on Windows NT. The error does not occur on Windows 2000 or when using Outlook Express. |
Drag and drop mail from Outlook to a local hard drive, then move the file from the local hard drive to the drive mapped to Oracle Files. |
Table 5-9 Oracle FileSync Bugs
| Bug No. | 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. |
Do not use '%' in folder names if you want to use Oracle FileSync for file synchronization. |
| 3037418 | There is no Arabic selection available in the list of installation languages for Oracle FileSync.
Oracle FileSync can be installed on an Arabic machine and will function in Arabic. However, the installation process will not display Arabic. |
Install Oracle FileSync in another language, then switch the locale to Arabic. |
