Oracle® Internet File System

Release Notes

Release 1.1 for Windows NT/2000

November 2000

Part No. A85287_02

Overview

These release notes accompany the Oracle Internet File System Release 1.1 for Windows NT/2000.

This document contains these topics:

Client Certifications

The following client software versions have been tested and certified for Oracle Oracle iFS:

Netscape:
- Netscape Communicator 4.72 production release (for FTP, IMAP4, SMTP, HTTP, and the Web interface)
Microsoft:
- Microsoft Internet Explorer 5.0 and 5.5 with Outlook Express (for FTP, IMAP4, SMTP, HTTP, and the Web interface)
- Microsoft Windows NT 4.0 Workstation, or NT Server, Service Pack 6, and higher (for Windows access with SMB and the Windows interface)
- Microsoft Windows 95
- Microsoft Windows 98
- Microsoft Windows 2000 Professional
Eudora 4.3 for IMAP, SMTP

Known Issues

Web Proxies for FTP Drag and Drop

Users may need to edit their web browser preferences so that they do not use a proxy for FTP. Using a web proxy may cause problems when using drag and drop in the Web interface to upload files to the server.

Apache Setup

Chapter 9 of the Oracle Internet File System Setup and Administration Guide accompanying this release indicates that a script needs to be run in order to set up Oracle Apache Server. In fact, the Configuration Assistant performs this Apache setup function automatically, therefore the script is not included.

The same section provides incorrect information on accessing Oracle iFS for Oracle Apache Server. The correct path to access Oracle iFS is as follow:

http://<servername>:<port_number>/ifs/files

Mapping Oracle iFS Network Drives

Because mapping a network drive to an NT/2000 server is controlled by Windows, independent of Oracle iFS, the user must first be authenticated by Windows for access to that NT/2000 server.

If users are having difficulty mapping an Oracle iFS drive, the NT/2000 administrator should create a shared drive on the NT/2000 server independent of Oracle iFS, and have the users try to map to it. If this fails, see your Windows NT/2000 documentation for more information on Windows authentication.

Instructions for end users::

When mapping a network drive to Oracle iFS running on an NT/2000 server, specify a Windows user id and password valid for that NT/2000 server. (Without valid Windows user id and password on the NT/2000 server, you will be unable to map to Oracle iFS.) If this user id does not also exist in Oracle iFS, you will be logged in with Oracle iFS user id "guest" automatically. You may not connect to Oracle iFS through NTFS without a valid Windows user id and password. (To connect to Oracle iFS running on a Windows NT/2000 server without a valid Windows user id and password, use the Web Interface.)

NOTE: Mapping a drive on Windows NT/2000 server that is in a domain you are not authenticated against may require supplying the user id in the following syntax: <domainname>\<userid>, for example, MyDomain\gking. Oracle iFS ignores the domain prefix and only looks at the user id.

Warning: In mapping an Oracle iFS drive to an NT/2000 server, the user does not need to provide a valid Oracle iFS password, since the user has been authenticated by Windows. Therefore, the NT/2000 administrator must be trusted not to create NT/2000 user accounts with the same name as an Oracle iFS user for the purpose of fraudulently accessing that Oracle iFS user's data.

When mapping a network drive to Oracle iFS running on a UNIX server, an Oracle iFS user id and password is sufficient. If the user name you provide is not a valid Oracle iFS user on this UNIX server, you will be logged in as "guest" automatically, assuming the administrator has not disabled this option.

Instructions for System Administrators::

Each Oracle iFS user requires a Windows NT/2000 account with the same user id. If the server is in a Windows domain, Oracle recommends the user account be created at the domain level. Otherwise, the user account can be local to the Windows NT/2000 server.

Access Control Lists (ACLs)

Access Control on Created Objects

The ACL associated with any created object is determined by the user's default ACL as specified in the Primary User Profile. A non-admin-enabled user's default ACL is set to PUBLISHED, except for MailBox, MailDocument, MailFolder, and Message, which are PRIVATE. An admin-enabled user's default ACL is set to PRIVATE, except for the following classes, which are set to PUBLISHED:

VersionSeries
VersionDescription
AccessControlList
PropertyBundle
DirectoryObject

To change the default ACL applied to a document, access Oracle iFS from the Web Interface or the Windows Interface.

Modifying System ACLs

A system administrator has the privilege to modify System ACLs (PUBLIC, PUBLISHED, PROTECTED). The administrator can mistakenly modify a system ACL in a manner that renders it useless by deleting the WORLD Access Control Entry (ACE). Care should be taken when modifying any system ACLs.

For more information on setting system ACLs, consult the Oracle Internet File System Setup and Administration Guide.

Known Bugs

The following bugs are known to exist in the Oracle iFS 1.1 release. Workarounds are given when appropriate. The known bugs are grouped by process or component:

Generic Oracle iFS Bugs

Bug 1106093 (also listed as 1263638, 1252587)	Recursively deleting a large folder tree fails. (Complex searches fail with the exception, IFS-21000: Session is not connected or has timed-out.)
Description:	When executing tasks that require a long time to complete, such as complex searches, searches over a very large data set, or deleting a large folder tree, the connection times out and fails.
Action:	Shut down the service and increase the SessionTimeoutPeriod parameter in the properties file. The default value is 10 minutes. Restart the service. Modifying this parameter affects all services started using this new property file.
Bug 1115247	Folder items are sorted uppercase first, then lowercase.
Description:	When listing the items in a folder, the items are sorted case-sensitively, by name.
Action:	None.
Bug 1244817	Inconsistent usage of prompts in Oracle ifs Manager and Oracle iFS Server Manager.
Description:	The prompts in Server Manager and iFS Manager are different, yet some of the values entered are the same. This may be confusing.
Action:	Below is the explanation of the prompts. Ifs Manager Username: Oracle iFS administrator's login Password: Oracle iFS administrator's password iFS Schema Password: Schema password for the Oracle iFS installation The following fields are read-only. The displayed information is specified in the corresponding Oracle iFS Service properties file. To change any of the information below, you must first have a properties file containing the desired information. Then select the "Change iFS Service" button and enter the new iFS Service name. The fields will then be refreshed from the information in the new properties file. iFS Service: The Oracle iFS service name that corresponds to the properties file which has service-specific information such as the schema name, caching, and connection pool parameters. Database Service: The `tnsnames.ora` entry for the database. If blank, iFS Manager will connect to the local database running on the same machine. iFS Schema: The schema name for the Oracle iFS installation. Server Manager iFS user name: Oracle iFS administrator's login. iFS user password: Oracle iFS administrator's password. iFS service name: Oracle iFS service name that corresponds to the desired properties file. iFS database password: Schema password for Oracle iFS installation.
Bug 1369729 (also listed as 1389141)	Cannot see an object to which the user has been granted access. (When a user tries to access the attribute of an object to which the user's access been revoked, an IfsException occurs.)
Description:	If the ACL of an object is changed by one user so that object becomes discoverable by a different user, the object may not be discoverable until the user disconnects from Oracle iFS and reconnects. For example, if user A changes the ACL of an item in a folder from "Private" to "Public," user B might not see that item in the folder until user B disconnects and reconnects to Oracle iFS. Conversely, if user B has discovered an object whose ACL is subsequently changed by user A, causing that object to no longer be discoverable by user B, user B may continue to see that object until disconnecting and reconnecting to Oracle iFS. However, if user B performs an operation on that object, such as getting its name, that operation might fail and throw an IfsException, indicating the user does not have permission to perform that operation.
Action:	Disconnect and reconnect your session.
Bug 1379386	System stops indexing after Chinese files are inserted.
Description:	Binary files containing Chinese characters can stop the queue of files being indexed by interMedia Text. If this happens, you can still insert and update files, but no files in the system will be indexed until you address this problem.
Action:	Delete the file and restart interMedia Text indexing. For more information, see the Oracle8i interMedia Text Reference.

Command Line Utilities Bugs

Bug 1237269	The date format string is not validated when set, but only when it is used.
Description:	Setting the ifsmod date format string with an invalid format will not return an error. An invalid date format error is returned on the command that actually uses the date format.
Action:	After setting a date format string, use the format immediately. If a string error is returned, reset the date format to a valid date format.

XML Bugs

Bug 1246851	Subclassing through XML to create a ClassObject with an invalid name causes an obscure error.
Description:	When creating a subclass, the table name created in the database is set to the name of the ClassObject. If the ClassObject name is an invalid tablename, (tablename cannot be a reserved SQL word, nor can it contain spaces or illegal characters) the following exception is thrown: `IFS-30002: Unable to create new LibraryObject.`
Action:	Edit the XML file and change the name of the ClassObject.
Bug 1255889	Using XML to create a value domain fails.
Description:	Trying to create a value domain using XML results in an XML parsing error.
Action:	Create the value domain through Oracle iFS Manager.

NTFS Bugs

Bug 1289569	Delete appears to work on some un-deleteable files.
Description:	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.
Action:	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.
Bug 1391358	Cannot move a rendered XML document.
Description:	A document without any explicit content cannot be moved to another folder. Documents without any explicit content are generally created using XML and the contents are rendered.
Action:	The document must be deleted and then recreated in the new folder.
Bug 1412048	In Windows NT with Service Pack 6, .txt documents cannot be modified and saved in Wordpad.
Description:	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.
Action:	Remove the Read Only attribute before editing the document with Wordpad, or use another editor such as Notepad.
Bug 1417572	Cannot delete a locked folder.
Description:	The NTFS Server does not support locking or unlocking a folder, therefore a folder that has been locked using another interface cannot be unlocked using NTFS. Locked folders cannot be deleted.
Action:	Use a different user interface, such as the Web Interface, or the Windows User Interface to unlock the folder before deleting it.
Bug 1454964	Access violation in the NTFS Server.
Description:	After running for an extended period of time, the NTFS Server may terminate, displaying the following error message: access violation in ifsproxy.dll
Action:	Restart the NTFS Server.

Windows Interface Bugs

Bug 1246484	Cannot cancel a check out in the Windows interface.
Description:	The Cancel Checkout option is not available. If you check out a file and decide not to create a new version (e.g., check in the file), there is no way to cancel the checkout.
Action:	Use the Cancel Checkout function in the Web interface. NOTE: If you check in a versioned file that has not changed since being checked out, Oracle iFS will not create a new version of this file.
Bug 1246456	Potential loss of service on starting multiple WCP servers against the same databases.
Description:	In a three-tier model, multiple installations of Oracle iFS can point to the same database. If multiple Windows Client Protocol (WCP) servers are started against the same database, the WCP server started last takes over servicing all Window interface requests. All the other WCP servers, however, do not display any errors, but do not service any Windows interface requests. So, if the last WCP server is shut down, none of the remaining servers will service any Windows interface requests.
Action:	For this release, only one WCP protocol server is supported.
Bug 1252913	Find returns documents which the user cannot locate with a path.
Description:	The Find dialog returns documents for which the user has discovery privileges, even if the user does not have privileges on the folder containing the document. For example, if a user creates a document as Published in his/her home directory, another user will be able to find the document using the Oracle iFS Find dialog even though this user cannot access the document because s/he does not have permission on the first user's home directory. The Find results show the document name and 'In Folder' as "drive:". Double-clicking the document gives an error "Cannot open document (o:\new.txt) ErrorCode 2".
Action:	Relax the permissions in the first user's home directory or have the first user place published documents in accessible directories.

Web Interface Bugs

Bug 1104090	In Netscape, uploading a folder using drag and drop fails.
Description:	Using drag and drop in Netscape, uploading a folder and its contents will fail. This is a Netscape browser bug.
Action:	You have several options: If the folder's contents are not other folders, first create the folder in Oracle iFS, then upload the folder's contents using drag and drop. Upload using browse rather than drag and drop. Use Internet Explorer.
Bug 1235607	If quota is exceeded, attempting to upload over an existing file will fail.
Description:	If quotas are being used, and you are currently near or over your quota, you may not be able to upload any files, even if you are attempting to replace an existing file.
Action:	Delete the file you are replacing before attempting the upload.
Bug 1244053	After entering username and password, pressing Enter causes login screen to beep.
Description:	On the login.jsp, after entering the login and password, pressing the Enter key causes a BEEP.
Action:	Press the Tab key to select the Login button before pressing Enter.
Bug 1248003	The text in the column heading disappears after the window is resized.
Description:	After resizing the window, the headings on the File List disappear. You will see boxes filled with black.
Action:	This is a style sheet/browser issue. Reload the File List by clicking the current folder in the Directory Tree.
Bug 1252587 (also listed as 1106093, 1263638)	Library Session times out during long uploads.
Description:	See Description of Bug 1106093 in "Generic Oracle iFS Bugs" on page 6.
Action:	See Action for Bug 1106093 in "Generic Oracle iFS Bugs" on page 6.
Bug 1258791	Cannot apply ACLs to more than 100 items in the Web interface at one time.
Description:	A design issue in the Web interface limits the number of items you can have selected when you choose Apply ACL from the Edit menu.
Action:	Select fewer than 100 items when you are applying ACLs.
Bug 1370141	Upload and check-in/check-out menus overlap if the system uses small fonts.
Description:	If you set the Windows NT display parameters to use small fonts, the menu options in the Upload and Check-In/Check-Out menus overlap one another. This problem only occurs in Netscape browsers, not in Internet Explorer.
Action:	If you are a Netscape user, change the font settings in the Display section of the Windows control panel to use large fonts.
Bug 1372615	Using Internet Explorer, uploading a document with non-ASCII document name via drag and drop fails.
Description:	Using Internet Explorer 5.0 or 5.5 to upload a file with a non-ASCII file name via drag and drop results in an error message that the file already exists. Choosing to overwrite the non-existent file causes the filename to be truncated when the file is stored in Oracle iFS.
Action:	This is a known NLS bug with the FTP window in Internet Explorer 5.0 or 5.5. Either use upload via browse, or use a different protocol server to upload the file.
Bug 1374498	Non-ASCII file name is displayed as string of rectangles while viewing its parents.
Description:	For a file with a non-ASCII name: If you open the View Parents window to see all the folders in which a file appears, the file name appears as a series of rectangles.
Action:	Set your browser to ignore typefaces. For example, in Netscape, select `Edit -> Preferences -> Appearance` and set Fonts option to "Use My Default Fonts."
Bug 1384904 (also listed as 1379837, 1374374)	Using Netscape, cannot upload a file with non-ASCII characters in filename.
Description:	Using Netscape to upload (via browse) a document that has a non-ASCII filename, the upload fails.
Action:	Use Internet Explorer or a different protocol to upload the file, such as FTP or SMB.
Bug 1385640 (also listed as 1373077)	Using the Japanese version of Netscape, uploading a file via drag and drop fails.
Description:	If you try to drag and drop a file through the Japanese version of Netscape, the upload fails. Note that this problem only occurs if the character set used for the filename does not match the character set of the Oracle iFS FTP server. Unfortunately, the user has no way to determine the server character set.
Action:	Use a different protocol to upload the file, such as FTP or SMB.
Bug 1387938	Drag and drop upload may fail.
Description:	Using FTP to drag and drop from the Web Interface, the upload fails if the path to the server is not fully qualified.
Action:	Either fully qualify the path to the server (for example, myserver.mycompany.com:2100) or use a different protocol server to upload the file.
Bug 1399626	Uploading a file via drag & drop into a folder with a period in its name causes the file to open in Internet Explorer.
Description:	Attempting to upload a document into a folder with a period in its name causes the upload to fail. Instead of being uploaded, the file displays in Internet Explorer.
Action:	Navigating one level up from the folder (the folder with a period in its name), then back down into the folder will enable the upload to work.
Bug 1399646	Folder with an apostrophe in its name cannot be opened from Web Interface.
Description:	If a folder name contains an apostrophe, you cannot open that folder in the Web Interface.
Action:	Remove the apostrophe from the folder name.

FTP Bugs

Bug 1107309	Cannot publish website with FrontPage 2000 if folder name has a space.
Description:	Cannot publish website with FrontPage 2000 through FTP if the folder name includes a space.
Action:	Remove spaces from the names of all folders (and all parent folders).
Bug 1233338	Renaming a file or folder to an existing folder name moves the item under that folder.
Description:	When a user renames a file or folder to a name of an already existing folder, the item is moved into that folder, rather than returning an error that an item already exists of that name.
Action:	Renaming to an existing folder should not be allowed; however, there is no loss of data. The user can open the existing folder, locate the file or folder, and rename and/or move it to its correct location and name.

E-mail Bugs

Bug 1106173	Outbox fails to bounce undeliverable messages.
Description:	The Oracle iFS Outbox agent will retry to send the message repeatedly at increasing intervals of time. The message will then be purged after seven days.
Action:	Monitor the outbox at least weekly to identify undeliverable e-mails.
Bug 1197079	Deleting and expunging multiple messages in Netscape Messenger 4.7 may cause the client to fail.
Description:	Occasionally, trying to delete several messages and expunge them all at once using Netscape Messenger 4.7 causes the client to fail.
Action:	Retry the same operation. If the error recurs, restart the client and delete messages in smaller groups.
Bug 1254452	Cannot use the FTP delete/mdelete command to delete an e-mail message.
Description:	If you use the FTP delete/mdelete command to delete an e-mail message, the following exception is thrown: `550 <e-mail message name> is a folder, use rmdir.`
Action:	Use the Web interface, SMB, or your IMAP client to delete e-mail messages.
Bug 1246882	Creating folders recursively using Netscape Messenger 4.7 does not subscribe all folders.
Description:	Netscape Messenger allows you to create IMAP folders recursively. However the top-level folders do not get subscribed. For example, if you create d01/d011/d0111, the folders d01 and d011 do not get subscribed automatically. These folders are not be visible on your IMAP client if options are set to view only subscribed folders.
Action:	Subscribe the unsubscribed folders explicitly.
Bug 1248657	Mail sent from a machine that uses XFN instead of DNS does not always work.
Description:	XFN is a federated naming service used instead of DNS. Oracle iFS e-mail only supports DNS.
Action:	DNS is required for Oracle iFS.
Bug 1379886	Cannot delete non-ASCII-named folder with EUDORA 4.3.2.
Description:	It is not possible to remove folders named with non-ASCII characters using EUDORA 4.3.2.
Action:	Use any other e-mail client, SMB, or the Web Interface to remove the folder.
Bug 1380015	Unable to login into an IMAP account with a non-ASCII character in the name.
Description:	If user name has non-ASCII characters, logging into the IMAP server may fail. This happens if the server character set is not set correctly.
Action:	Set the Oracle iFS server default character set to ISO8859-1 or the appropriate multibyte character set.
Bug 1386666	Certain Oracle iFS e-mails not viewable in PINE.
Description:	Multipart e-mail messages that have not been delivered from Oracle iFS cause PINE to crash.
Action:	Use any other e-mail client or SMB to view the e-mail.
Bug 1387952	E-mails sent from PINE cannot be opened in the Web Interface.
Description:	An e-mail that originated from a PINE client is not viewable in the Oracle iFS 1.1 Web UI. The body of the e-mail will not be displayed. Instead, a "404 Document not found" error is reported.
Action:	The e-mail can be viewed using any standard e-mail client suitably configured, and through Windows Explorer using Oracle iFS SMB.

HTTP Bugs

Bug 1167713	JLU inheritance is valid for only one level.
Description:	The JSP Lookup (JLU) inheritance does not descend to more than one level in the class hierarchy. For example, in the hierarchy: `A` `+ -- B` `+ -- C` a Java Server Page associated with B will be invoked when a document of class C is accessed. However a JSP associated with A will not be invoked when a document of class C is accessed. In the case of a type C descending from type B which in turn descends from type A, C will not see any JSP mapped to type A.
Action:	Add another entry to the JLUs, wherein type B is mapped to the same JSP as type A.
Bug 1387888	Web Folders displays an e-mail as a folder.
Description:	The Web Folders-based interface to Oracle iFS does not handle the rendering of Oracle iFS emails as one entity. The e-mails appear as a folder and the constituents as parts of separate documents.
Action:	Use an IMAP client to view the e-mail.
Bug 1387909	DAV servlet default charset encoding is not in Oracle iFS Service Properties.
Description:	The default character set value for the DAV Servlet is stored in `IfsDavServletParameters` file instead of the `IfsService.properties` file.
Action:	In the IfsDavServletParameters.properties file, change the ifs.dav.webfolders.charencoding parameter to 8-bit and multibyte folders. The file is in the following directory: $ORACLE_HOME/ifs<version>/settings/oracle /ifs/protocols/dav/impl/properties.
Bug 1393110	Folder names in top level Oracle iFS directory are restricted.
Description:	In an Apache environment, servlet names exactly matching one or more of the first characters of the name of a top-level directory will cause the Web UI to fail. For example, if the name of the servlet is `ifsservlet`, the presence of a folder called `ifsservlet_files` will cause the Web UI to fail.
Action:	Do not create any top-level folder on Oracle iFS with the same first set of characters as the servlet name.

Oracle iFS Manager Bugs

Bug 1167418	There is no provision for changing the ACL of a User Object itself.
Description:	The ACLs of DirectoryUsers cannot be changed in the Oracle iFS Manager.
Action:	Go to the Web Interface and select the user in the Users list. Click Edit->Apply ACL to update the ACL.
Bug 1388097	Cannot rename an ACL or User.
Description:	ACLs or users cannot be renamed in Oracle iFS Manager.
Action:	To rename an ACL, go to the Web Interface, select the ACL in the ACL list and click Edit->Rename. Renaming a DirectoryUser requires a Java utility that can update the NAME attribute of the DirectoryUser.
Bug 1401400	All operations after exception IFS-10653 are not saved.
Description:	If you do an illegal operation in Oracle iFS Manager you may get the exception "IFS-10653: Unable to abort transaction". After this exception is displayed, all operations are invalid and will not be committed to the database.
Action:	Exit Oracle iFS Manager. Restart Oracle iFS Manager and continue working.