The new parameters include:
[ENG]
usermailmap = O
itemuidmap = P
resourcemailmap = O
usersmscprefmap = OU3
usermobiletypemap = N
usermobilemap = R
- There is no event calendar coexistence between Calendar Server versions. V1 users will only see V1 event calendars and V2 users will only see V2 event calendars.
Unidbfix -c may report "Minor inconsistencies" on a 9.0.4 server when events are created by a 9.0.4 user using Oracle Connector for Outlook 9.0.4 and accepted/declined by a 5.4 user using the Windows Native client 9.0.4. These inconsistencies will not impact the integrity of the database.- V1 users will not generate e-mail messages when using resource scheduling.
- Attachment names may change to "Mime-Encoded-attachment.txt" when using a mix of 9.0.4 users and 5.4 users with Oracle Connector for Outlook. The attachments will still be readable.
- Mac clients (V5.2.3) may not be able to download offline files while connecting to a 9.0.4 Standalone installation.
UIDs
- A User UID may in some cases not be replicated to a remote note. If this is the case, use the
uniuser -mod command to modify a field for this user.
- A UID will be created by the system for a user without an existing UID.
Oracle Connector for Outlook Issues
- Adding an occurrence to an already repeating event (using a desktop client) causes the event to get duplicated in Oracle Connector for Outlook.
- An event deleted with Oracle Connector for Outlook will simply show as declined in a desktop client if you do not send a cancellation.
Designates
- Windows clients cannot list designates of remote resource.
- You cannot enter a Designate Name with a space.
- Users may get an error when creating an event while working as a Designate. However, the event will be properly created.
- The Remote Designate feature only works with the Calendar Web Client.
Various
- Search: Searching with
unigroup -ls on a name that has a dot (for example, group.name) may return no item.
3.1.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Calendar Server.
- You could not transfer an agenda to another user with the Calendar Administrator.
- You could not manage holidays from the Calendar Administrator.
- Mozilla 1.2.1 on Solaris did not display full pages.
- You could not create an event calendar using the Calendar administrator.
- You could not modify resource working hours using the Calendar Administrator.
- You could not start and stop a server/node with the remote client.
- Translated versions of the online Help:
- Setting default reminders is not described. Oracle has assigned bug number 2948693 to track this.
- For ADA versions, in the Display Preferences section under Setting Your Preferences, the Help explains that you can select the hours of the day you want displayed in your Daily View, but this does not apply to ADA mode. This sentence has been removed. Oracle has assigned bug number 2949389 to track this.
3.1.4 Document Errata
The following sections provide information on documentation errors in the Oracle Calendar Server documentation.
3.1.4.1 Oracle Collaboration Suite Installation Guide
In Appendix F of the Installation Guide, under the sub-heading "Installing Oracle Calendar Standalone", step 5 is described as follows:
5. In the Specify File Locations screen, select:
/<SourcePath>/Disk1/calendar_standalone/Disk1/stage/products.jar
This is not correct. Depending on your platform, perform the following:
- For HP-UX:
After you complete step 4, unmount Disk 1, eject Disk 1, and mount Disk 5.
Then, in the Specify File Locations screen, select:
/<SourcePath>/calendar_standalone/stage/products.jar
- For Linux, instead of step 5, substitute:
5. In the Specify File Locations screen, select:
/<SourcePath>/calendar_standalone/stage/products.jar
3.1.4.2 Oracle Calendar Reference Manual
In the Oracle Calendar Reference Manual, Appendix F, "Calendar Server Utilities", the unirestore documentation contains a syntax error.
The correct syntax should be the following:
SYNTAX
unirestore [-u <uid>] [-path <bkpPath>]
[-futureReplies] [-noAddAttendee] [-logAll]
-n <node-ID> [-host <hostname>] [-p <sysOpPsw>]
unirestore -ls [<user>] [-path <bkpPath>]
-n <node-ID> [-host <hostname>] [-p <sysOpPsw>]
unirestore -v
unirestore -h
3.2 Oracle Calendar SDK
This section covers these topics:
3.2.1 What's New in this Release?
This release of the Oracle Calendar SDK includes the following new features:
- Task operations (VTODO objects)
- Contact operations (VCARD objects)
- Corresponding Java classes with JNI (Java native interface)
- Remote designate operations
- Connection pooling
The inclusion of Java classes facilitates Java implementations that were previously implemented by third parties.
Connection pooling adds configuration options for the connection model used by the SDK. This greatly enhances resource usage and efficiency when implementing various applications (especially Web-based and multi-threaded environments), and promotes reuse of existing connections.
Old CAPI event functions have been superseded by newer CSDK functions. Customers already using the CAPI functions need to run the utility unifhconv on the server if they depend on any of the following iCalendar properties:
- X-* (any X- property)
- SEQUENCE
- RESOURCES
- RELATED-TO
- CONTACT
- URL
- ATTENDEE where the attendee is a non-calendar user (e.g. invited only by their e-mail address)
3.2.2 Known Limitations and Workarounds
- The "blocking" behaviour of the connection pool has been disabled. Any attempt to open a new server connection when the maximum number of connections (as set by
max_users) has been reached will return an error instead of waiting until a connection becomes available. Oracle assigned bug number 2989379 to track this.
- Connection pool error codes are incorrectly mapped to the CAPIStatus value
CAPI_STAT_LIBRARY_INTERNAL_COSMICRAY. If this value is returned by calls to CSDK_Connect, CSDK_Authenticate or CSDK_SetIdentity, then it most likely means that the connection pool was unable to provide a connection to the requested server. Oracle assigned bug number 2889348 to track this.
- If a server connection is lost (for example, if the calendar service is stopped while a client is connected), the dead connection may not be released from the connection pool causing subsequent calls to fail. Oracle assigned bug number 2898775 to track this.
- Blank lines in
ocas.conf and ocwc.conf: Blank lines in ocas.conf and ocwc.conf in your R2 installation will be removed by the Upgrade Assistant. To preserve them, replace them with "#" before running the Assistant.
3.3 Oracle Calendar Application System
This section contains release note information on the following products:
3.3.1 Oracle Calendar Web Client
This section covers these topics:
3.3.1.1 What's New in this Release?
This section lists new features of Oracle Calendar Web Client.
- The new Scheduler provides an efficient way to find out when multiple users and Resources are available for Meetings; the resource-scheduling mechanism allows hierarchical searches and automatic workflow for resources requiring designate approval. Users can also view details about people or resources.
- The "Show time as free" feature allows users to accept invitations to meetings while remaining available for other invitations.
- Support for Web Conferencings; users can join and create Web Conferencings from the Web Client.
- New designate functionality, including support for:
- Resource designates
- Event calendar designates
- Remote designates
- Changes made to notification and wireless preferences are applied to calendar desktop clients.
- Ability to set default reminder settings for Meetings, Daily Notes and Day Events.
- Support for 24-hour meetings.
- A link to the Calendar Administrator from the global toolbar (for users with Server Administration rights).
- Ability for users to set the hours displayed in the daily or weekly view.
- Support for Additional Languages, including Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Brazilian Portuguese, Portuguese, Swedish, Spanish, Simplified Chinese, Traditional Chinese and Turkish.
3.3.1.2 Known Limitations and Workarounds
This section describes known limitations and workarounds for Oracle Calendar Web Client.
- File attachments:
- After uploading a file to the server, if the user closes the browser window instead of clicking OK, the file will remain in the server's temporary directory. Oracle assigned bug number 2973763 to track this problem.
- The temporary directory used on the server should be changed to one that is write-accessible, namely,
<ocas>/tmp instead of <ocas>/bin. Oracle assigned bug number 2973833 to track this problem.
- When viewing someone's agenda with full viewing rights and attempting to open an attachment to a meeting, a security violation error message appears. Oracle assigned bug number 2983094 to track this problem.
- Wireless reminder option: In Entry Default preferences, the wireless reminder option is available even when wireless preferences are disabled. Oracle assigned bug number 2975055 to track this problem.
- Show time as: The "Show time as" drop-down menu may appear to be available when it should not be. Specifically, when you are about to reply to a meeting invitation (and your status is still "unconfirmed") the menu should not be available until you have replied. Instead, the menu is available but becomes unavailable after you click it. Oracle assigned bug number 2978497 to track this problem.
- Netscape/Mozilla issues:
- Some error messages may not appear in Netscape or Mozilla after an incorrect action is performed. Also in this case, a reload must be done in order for the buttons and links to work. Oracle assigned bug number 2978866 to track this problem.
- Netscape 6.2: In order to print an agenda properly, the margin size must be set to one inch under Web Client Display Preferences. Oracle assigned bug number 2861543 to track this problem.
- Netscape 6.x: The "Return to Previous" link in some error pages does not work. This is a Netscape issue. Oracle assigned bug number 2981030 to track this problem.
- Mozilla 1.x: Users may experience display problems and erratic behavior. Oracle assigned bug number 2847384 to track this problem.
- Redirect issue: This line (in
$ORACLE_HOME/ocas/conf/ocal.conf) will not redirect the client properly, since Alias only works for the location portion of a URL (up to the question mark):
Alias /calendar \
"/private1/oracle/middletier/ocas/bin/ocas.fcgi?sub=web"
Instead, use the following:
<Location /calendar>
Redirect permanent /calendar \
http://<host>:<port>/ocas-bin/ocas.fcgi?sub=web
</Location>
Oracle assigned bug number 2982922 to track this problem.
- Reminder lead time: When a user tries to set a reminder lead time greater than the server's maximum allowed value, the lead time is automatically reset to the server's maximum value without warning. Oracle assigned bug number 2980094 to track this problem.
- Multiple Installations of the Oracle Calendar Web Client: Each Web Client installation only supports calendar server nodes with common settings. To support a calendar server node with different settings, you must install another instance of the Web client.
- Broken images on UNIX: The Web Client uses Oracle UIX (User Interface XML) technology to generate Web pages. UIX dynamically generates many images (such as buttons and tabs) appearing throughout the UI. Due to limitations in Java 2 Standard Edition (J2SE) prior to version 1.4, UIX requires an X server process in order to generate dynamic images on UNIX platforms. (Note that this limitation does not affect Windows platforms.) To locate the X server, the UIX runtime relies on the value of the DISPLAY environment variable. If the Web Client is running on a UNIX host, and some of the images in the UI appear broken or inconsistent, the problem may be that the value of the DISPLAY environment variable for the Web Client process is set incorrectly. (A common symptom of this problem is that instead of the rounded, beige, Oracle-style buttons, UI pages are rendered using native browser buttons.)
To verify the value of the DISPLAY environment variable for the Web Client process, open the ORACLE_HOME/opmn/conf/opmn.conf file in a text editor, and locate the entry for the instance called \OC4J_Portal\:
<oc4j maxRetry="3" instanceName="OC4J_Portal" gid="OC4J_Portal"
numProcs="1">
<environment>
<prop name="DISPLAY" value="your-host-name:0.0"/>
</environment>
</oc4j>
The value of the DISPLAY property should point to a running X server. Warning: During installation, the Oracle Universal Installer automatically populates the value of the DISPLAY property in opmn.xml using the value of the DISPLAY environment variable detected during the installation session. If you are running OUI remotely (e.g. from a desktop PC with X emulation software such as Hummingbird Exceed), this auto-detected value will be incorrect, as it will point to a remote X server which is not guaranteed to be available. The safest approach is to create an X server on the middle tier host and set the DISPLAY property to point to it. Consult your UNIX documentation on how to start an X server on your platform.
3.3.1.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Calendar Web client.
- When editing or deleting events, e-mail notification was not sent, even if it was set to do so in preferences. Oracle assigned bug number 2907433 to track this problem.
- Resource conflicts were not properly checked when resource designates issued approval, unless resource approval was set up after the Calendar server was installed. Oracle assigned bug number 2906858 to track this problem.
- A resource designate would be asked to sign in after clicking a resource approval link, unless the resource was already signed in. Oracle assigned bug number 2907487 to track this problem.
- "Show time as" functionality was described in the online Help even though it was not implemented in the release. Oracle assigned bug number 2907123 to track this problem.
- The Scheduler page had changes made that were not reflected in the online Help. Oracle assigned bug number 2907159 to track this problem.
- Adding a group to an entry could cause an error if you were acting as a designate, picking a group from a search results list, or adding an LDAP group or group you didn't create. Oracle assigned bug numbers 2852128, 2859436, 2901674, and 2906654 to track this.
- Entering a number followed by a space in a text box where a numerical value is required (such as the "repeat for" text box) could cause an error. A similar thing happened when creating a new group and entering the new name with an extra space -- the group would not be created. Oracle assigned bug numbers 2844834 and 2894371 to track this.
- When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. Oracle assigned bug number 2892157 to track this problem.
- Two or more users with the same name could not sign on, even if they had different passwords. Oracle assigned bug number 2899249 to track this problem.
- Line breaks were not shown in the Details section of Meeting entries.
- When the first instance date of a Repeating entry did not match the default date on the General page, the default date would not be updated to reflect the Repeating date.
- The Calendar Portlet page would return the message, "This service is currently unavailable, please try later," when a user had Daily Notes or Day Events scheduled for the current day and had set the calendar display preferences to not display declined meetings.
- Internet Explorer 5.x Macintosh only: If the default start and/or end time in the Group View was changed and then a search for a group was performed, a "No Response from Application Web Server" page appeared.
- Netscape 7.x only: Margins of one inch had to be set for the Printer-friendly format feature to work correctly.
- The hour set in the "From" and "To" times in the Deliver reminders and notifications field in the Wireless section of the Edit Preferences page had to be greater than or equal to one. For example, using 0hr 00 min would result in an error. This was only an issue when the 24-hour display format is used.
- Edit Access Rights Page: If the
g: or r: prefixes were used when performing a search from the Edit Access Rights page, misleading error messages would appear.
- When 12:00 p.m. was selected from the drop-down box on the Suggest Time page, 12:00 a.m. was set in the General section of the Entry Modification/Creation pages. This was only an issue when using the 12-hour time format for the Web client.
- Internet Explorer 5.1 Macintosh only: When clicking Suggest Time from the Create/Modify Meeting page, the Suggest Time dialog box would open behind the main page.
- When setting values for the Print section of the Preferences page, using a value greater than 3 for the Margin setting would cause the Web client to freeze.
- Creating New Groups: You could only add an existing Group to a new Group by either entering a specific group name in the Search field and clicking Find, or by selecting the Groups radio button and clicking Find.
- You could not upload attachments with titles longer than 41 characters.
- Suggest Time Feature: Entering 24 in the Time between fields of the Suggest Date & Time page resulted in an Internal Server error. This only occurred when using the 24-hour time format.
- Whenever the Oracle Calendar server was restarted, the midtier Oracle HTTP Server had to be restarted as well.
- Internet Explorer 5.x Macintosh only: If the default start and/or end time in the Group View was changed and then a search for a group was performed, a "No Response from Application Web Server" page would appear.
- The Return to Portal link at the bottom of the Web Client pages would not function properly.
3.3.1.4 Document Errata
This section describes known issues in the Oracle Calendar Web client online Help.
Device settings in standalone: When using Web client standalone, you can edit the following device setting preferences, which are not described in the Help:
- Notification of Entries in plain text format or as notes in your calendar display on your mobile phone.
- Mobile device alarm.
- Preferred service center number.
3.3.2 Oracle Calendar Web Services
This section covers these topics:
3.3.2.1 What's New in this Release?
This is the first release of Oracle Calendar Web services, the newest component of Oracle Calendar. Oracle Calendar Web services allows applications to retrieve, through common XML queries, calendar data for display in any portal, client application or backend server. Developers can use the Oracle Calendar Web services toolkit, included with Oracle Calendar, to build Web services applications and create SOAP queries.
3.3.2.2 Known Limitations and Workarounds
The APIs of the Web Conferencing portion of the calendarlet are subject to change. Their functionality is not complete and has not been tested.
3.3.3 Oracle Sync Server
This section contains the following topics:
3.3.3.1 What's New in this Release?
Oracle Sync Server is a new component of Oracle Calendar that allows you to synchronize data with any SyncML-compliant device using a standard Hypertext Transfer Protocol (HTTP) connection. Sync Server uses SyncML, the open standard for synchronization backed by the Open Mobile Alliance. With a SyncML-compliant device and Oracle Sync Server, you can synchronize calendar data, to-do lists, contact information and other relevant data across multiple networks, platforms and devices.
3.3.3.2 Known Limitations and Workarounds
This section describes general issues and their workarounds for Oracle Sync Server 9.0.4.
- Nokia 3650:
- Nokia 3650 and 92xx:
- Changes to an entry's Access Level on the server are not synchronized to the device. However, a new entry's Access Level will be correctly synchronized from the server to the device the first time. Oracle assigned bug number 2839895 to track this problem.
- Unable to synchronize Business and Home addresses from the Oracle Calendar desktop client to the phone device. Oracle assigned bug number 2839242 to track this problem.
- E-mail addresses synchronized from the server to the device get reversed; that is, E-mail address 1 becomes E-mail Address 2, and vice versa. Oracle assigned bug number 2839795 to track this problem.
- Nokia 3650, Nokia 7650, Nokia 92xx, Sony Ericsson T68i: The "completed" property for tasks is not supported. Tasks marked as completed on the server cannot be marked as completed on the device. Oracle assigned bug number 2909625 to track this problem.
- All Nokia Devices, Sony Ericsson P800: These devices do not allow you to change their time zones. If you are travelling across time zones, it is best to avoid synchronizing until you return. However, if you must synchronize, only do so if your account on the Calendar server remains set to the same time zone as your device.
- Nokia 92xx: Unable to synchronize with the Nokia 9290 phone device when
KeepAlive=True (default value set by the Collaboration Suite installation) Oracle assigned bug number 2862018 to track this problem.
- Ericsson T39, T68, R520m: Task synchronization is not supported. Oracle assigned bug number 2909625 to track this problem.
- Ericsson R520m, T39, T68, Sony Ericsson T68i, Siemens S55: When travelling, it is recommended that you set your device to the same time zone as your Calendar account before synchronizing.
- Ericsson R520m, T39, T68, Sony Ericsson T68i:
- Missing Resource Names: When the
attendeesindetails parameter on the server is set to "short," resource names and statuses in event details are not synchronized to a device. This is because truncated resource names are not meaningful to users. Resources are only added to event details when attendeesindetails is set to full.
- Missing Dash in Phone Number: The device does not store formatted phone numbers. All non-numeric characters other than "#" are removed when phone numbers are stored on the device.
- Missing or Modified E-mail Addresses: The device can store one e-mail address for a contact, while the server can store two. If a contact's e-mail address is modified on the device and synchronized to the server, it is possible that the wrong address on the server will be updated. This is because there is no way at this time for the server to detect which address is supposed to be updated.
- Missing Organization Field: The device can store one organization field for a contact, while the server can store two. If a contact's organization field is modified on the device and synchronized to the server, the information in both server fields is discarded in favor of the field synchronized from the device.
- Contact's Full Name Becomes a Last Name: The correct way to enter contact names on the device is "
Lastname, Firstname". Names entered on, or synchronized to, the device without a comma will be stored on the device as last names only.
- Ericsson R520m:
- The Ericsson r520m has a limit of 150 characters in its event details field. Attendee information that exceeds 150 characters is not added to the details field. It is best to use the default server parameter of
AddAttendeesInDetails = short with this phone. Oracle assigned bug number 2862247 to track this problem.
- When you create an untimed event using the device, the Daylight Savings time change can cause it to be displayed as a Meeting with a duration of 1 minute on the Oracle Calendar desktop client. Oracle assigned bug number 2864097 to track this problem.
- Ericsson T68i:
- When a contact's e-mail address is modified using the phone device and contains special characters, it appears to be corrupt on the Oracle Calendar desktop client. This occurs because the phone device does not return the EMAIL vcard property in the appropriate format. Oracle assigned bug number 2844777 to track this problem.
- Siemens S55: Memos created on the Siemens S55 synchronize as Daily Notes on the server. (Other phone devices synchronize Memos as Day Events.) Oracle assigned bug number 2962661 to track this problem.
3.3.3.3 Resolved Limitations in this Release
- Modifying contact information using the phone device resulted in truncated fields on the Oracle Calendar desktop clients because the maximum character length allowed varied depending on the phone device's limitations. Oracle assigned bug number 2844930 to track this problem.
3.4 Oracle Connector for Outlook
This section contains these topics:
3.4.1 What's New in this Release?
This section lists new features of Oracle Connector for Outlook.
- Out of Office Assistant and Server-side e-mail Rules
- View mail server quota usage
- New e-mail, voice mail and wireless preferences
- Ability to recover e-mail deleted from one or more folders for a specified period of time
- Schedule and join Web Conferencing through Microsoft Outlook
- New enhanced resource scheduling functionality
- Prompt for language choices when upgrading from a previous version using the
/Lang command-line switch.
- Assign delegate access to remote node users
- Access to complete (Calendar and non-Calendar) user directory backing Calendar Server
- Ability to resolve names against OiD distribution lists
- Reduction in number of IMAP4 and calendar API commands issued to implement frequently performed Microsoft Outlook operations
- Master Node Configuration to auto-detect Calendar Server Account
- Local Mailbox Caching - ability to use a local copy of IMAP4 e-mail while working on-line
- Ability to configure folder count refreshes
- The ability to control whether the delegate name appears as "on behalf of" the folder's owner when sending messages
- The ability to automatically notify the Calendar owner when a delegate adds a meeting to the owner's Calendar
- Optimizations to the Outlook Advanced Search functionality when looking for e-mail recipients, meeting organizers and attendees
- Support for Additional Languages, including Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Korean, Norwegian, Brazilian Portuguese, Portuguese, Swedish, Spanish, Simplified Chinese, Traditional Chinese and Turkish
3.4.2 Known Limitations and Workarounds
This section describes known limitations and workarounds for Oracle Connector for Outlook.
- IMAP server: When using an IMAP4 server that does not support Simple Authentication and Security Level (SASL) encryption, such as Oracle Email Server, it is recommended that you enforce Secure Sockets Layer (SSL) for all connections to your IMAP4 server to avoid sending passwords in clear text. Consult your e-mail server documentation for more information. For details on setting up an Oracle Connector for Outlook IMAP4 connection with SSL, see the Oracle Connector for Outlook online help.
- Recurring meetings:
- The error message displayed when a user attempts to modify and save an instance of a recurring meeting owned by another user should state that access to the instance is denied, as is the case with non-recurring meetings, rather than reporting an OLE warning. (#01634)
- If you modify a set of recurring meetings while working offline, any modifications you make to individual instances of that meeting before reconnecting to the server will not be saved. (#01567)
- Under some circumstances, changes made to repeating meetings using an Oracle Calendar desktop client or Oracle Calendar Web client may invalidate the recurrence rule created in Outlook. (#00395)
- Oracle Connector for Outlook does not support the creation of monthly recurring meetings on the 29th or 30th day of the month. (#00257)
- Recurring all-day Events cannot be changed to single all-day Events if the change causes resource or scheduling conflicts, and vice-versa. To work around this problem, delete the recurring all-day Event, then create the single all-day Event. (#00265, 00271)
- Forwarded images: When a message with an attached image is forwarded, the image may get duplicated. (#01479)
- Stationery backgrounds: Stationery backgrounds can cause problems when using Pretty Good Privacy (PGP) encryption. (#01400, 01401)
- Outlook 2002: Oracle Connector for Outlook only supports the default Send/Receive Group.
- Folder rules:
- Resetting your
.ost file may cause you to lose folder context information such as your client-side Inbox rules. After resetting your .ost file, verify that your folder rules are intact by opening your Inbox and selecting Tools | Rules Wizard. In the Apply rules in the following order box, verify your folder rules. To modify your rules, click Modify and follow the instructions.
- To specify a person using the Outlook Client-Side Rules Wizard, you must provide both the user's display name and e-mail address separated by a semi-colon in order to have the rules trigger on messages received from that person. (#00520)
- Folders:
- Folder names are case-insensitive. (#00321)
- Public folders cannot be made available for offline use. To work offline with the contents of a public folder, you must copy the contents of a public folder to a private folder, then enable the private folder for offline use. (#00322)
- Custom folder views using the Group By option are not supported. Suggested workaround: Set the Group By field to none. (#00299)
- Meeting invitations:
- All attendees invited to a meeting are invited as Required, even if some were initially invited as Optional.
- Meetings that have been accepted or declined while working offline using the Respond to all by Accepting command will not change color to reflect Busy status. To work around this problem, connect to the server and upload your offline changes. (#00917)
- Unsupported formats/attachments:
- Oracle Connector for Outlook does not support Transport Neutral Encapsulation Format (TNEF) in e-mail messages, or
WINMAIL.DAT attachments sent by Microsoft e-mail clients.
- Oracle Connector for Outlook does not recognize Macintosh attachments containing a resource fork. (#00248)
- Birthdays and anniversaries: Birthdays and anniversaries cannot be added to a contact while working offline. To work around this problem, add the birthday or anniversary to your contact while working online. (#00309)
- Synchronization: Synchronizing the Pocket Outlook 2002 Inbox using ActiveSync 3.5 with Outlook 2000 will result in unresolved items.
- Web Conferencings: Due to an Outlook 2000 limitation (Microsoft Knowledge Base: 272320), Outlook 2000 users require at least Office 2000 Service Pack 3 to correctly display an instance of a recurring Oracle Web Conferencing. Oracle assigned bug number 2927339 to track this.
- Oracle Calendar form: If the Oracle Calendar form becomes unpublished or lost, other Calendar features, such as Attendee Availability, Group Views, Resource Scheduling, Plan A Meeting and Propose New Times will not work properly. To solve this problem, simply re-publish the Oracle Calendar form. Oracle assigned bug number 2770611 to track this.
3.4.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Connector for Outlook.
- Outlook XP only: When right-clicking on an item in the Calendar folder or Inbox representing an instance of a recurring event owned by another user, the menu items in the pop-up menu would be doubled. (#01290)
- Reading an incoming e-mail while it was being moved to another folder by an Inbox rule could result in the message being duplicated in the destination folder. (#00748)
- If an open message was moved immediately after replying, a copy of that message would remain in its original location. (#00266)
- Outlook 2000 on Windows 98 only: When working in another user's Calendar folder, you could not create a new meeting by simply highlighting a time and typing directly in the cells. (#01123)
- When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. Oracle assigned bug number 2892157 to track this.
- Ability to synchronize Notes and Ink Notes with Pocket PC devices.
- Ability to synchronize off-line folders without first visiting them.
- Long delays were experienced after Connector installation took place.
- Upgrading the Connector Version or Purging the off-line folders resulted in PST files getting deleted.
- Meetings created with attachments (Word, Excel) using an Oracle Calendar desktop client did not show the attachments when the same meeting was viewed from Oracle Connector for Outlook XP. The attachments could be seen properly on Microsoft Outlook 2000.
- Recurring Meetings or Show Free/Busy information could not be displayed correctly if user did not have full administration privileges.
- Users with rights to manage Holidays could inadvertently delete Holidays for everyone through Outlook.
- Client-side rule to move ALL e-mail to PST resulted in second empty e-mail.
- Moving an e-mail from the Oracle Connector for Outlook to a target PST folder did not delete the source message.
- Cancelling a move of multiple messages from the Oracle Connector for Outlook to a target PST folder deleted the source messages.
- The time displayed in the Reminder pop-up window on Outlook XP displayed the reminder time instead of the meeting's start time.
3.5 Oracle Calendar Desktop Clients
This section contains release note information on these products:
3.5.1 Oracle Calendar Desktop Client for Windows
This section contains these topics:
3.5.1.1 What's New in this Release?
This section lists new features of Oracle Calendar Desktop Client for Windows.
3.5.1.2 Known Limitations and Workarounds
This section describes known limitations and workarounds for Oracle Calendar Desktop Client for Windows.
- iCalendar import: When attempting to import an iCalendar file to an external calendar product such as Microsoft Outlook, only the first entry in the file is imported correctly. To work around this issue, you should export/import your Agenda data in vCalendar format instead. Oracle assigned bug number 2859449 to track this problem.
- VCS import: Importing
.vcs files from some programs may not work properly. Oracle assigned bug number 2836621 to track this problem.
3.5.1.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Calendar Desktop Client for Windows.
- When attempting to print your Agenda while having a Designate Agenda window open, the system occasionally printed the Designate Agenda rather than your own. Oracle assigned bug number 2836683 to track this.
- When attempting to print your Agenda with the time range set to span 24 hours, the application reverted to the default time range (08:00-17:00) instead. Oracle assigned bug number 2859640 to track this.
- Downloading your agenda to a file after changing your password caused errors. Oracle assigned bug number 2912923 to track this.
- When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. Oracle assigned bug number 2892157 to track this.
- When you have new entries in your offline agenda, selecting Download To Local File did not properly reconcile the agendas. Oracle assigned bug number 2896226 to track this.
3.5.2 Oracle Calendar Desktop Client for Macintosh
This section contains these topics:
3.5.2.1 What's New in this Release?
This section lists new features of Oracle Calendar desktop client for Macintosh.
3.5.2.2 Known Limitations and Workarounds
This section describes general issues and their workarounds for Oracle Calendar desktop client for Macintosh.
- Sign-in:
- After configuring a master-node server for a specific user, the user name displayed in the Sign-in dialog is that of the previously signed-on user instead of the indicated user. Oracle assigned bug number 2864234 to track this.
- Attempting to sign-in to the application with a valid password containing a Euro character will fail. Oracle assigned bug number 2871974 to track this.
- Signing in to your agenda off-line may not always work. For instance, it is known that in the off-line configuration dialog box, if you select a different time zone and then try to sign in, you will simply be returned to the sign-in dialog box. Oracle assigned bug number 2893984 to track this.
- Notifications:
The pop-up notification for new entries feature does not work. Oracle assigned bug number 2872763 to track this.
- Windows: When switching back and forth between Oracle Calendar desktop client for Macintosh and other applications, the Oracle Calendar windows appear in the foreground but remain grayed out as though they were still in the background. Oracle assigned bug number 2893976 to track this.
- Repeating events:
Trying to apply a change in Reply status to all instances of a repeating meeting may not work. Oracle assigned bug number 2884186 to track this.
- Printing: When you click Print from the New Group dialog when there is no default printer set up on your system, a message is displayed asking if you wish to set up a printer. Clicking Cancel yields the following unexpected error: Module: <CST_ManageGroupsDlog.cpp>, Label: 125, Service error: 0x31002 Oracle assigned bug number 2842273 to track this.
- Address Book:
- Address Book categories do not function correctly. Oracle assigned bug numbers 2830426 and 2879849 to track this.
- If you leave your address book open while upgrading, your data may not appear to have been migrated properly. Just click on the address book icon from the toolbar to see your updated entries. Oracle assigned bug number 2911972 to track this.
- Creating a Daily Note from the Address Book while working off-line may not work. Oracle assigned bug number 2921488 to track this.
- Exporting the address book to tab-delimited/comma-delimited text files does not work. Oracle assigned bug number 2924992 to track this.
- Duplicate Meeting: The Duplicate Meeting functionality may cause some unexpected behavior. Oracle assigned bug numbers 2874952 and 2892366 to track this.
- Apply to All: In the event editor, the Apply to All functionality may not work correctly for all selections. Oracle assigned bug numbers 2884158, 2884186, and 2884903 to track this.
- iCalendar import: You cannot import iCal files while off-line. Oracle assigned bug number 2922180 to track this.
3.5.2.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Calendar desktop client for Macintosh.
- Changes to your Address Book's user-defined fields were not saved. Oracle assigned bug number 2832478 to track this.
- In cases where there was no wireless support (such is the case for MDCC), wireless reminder checkboxes were displayed in the Reminder tabs and the Entry Defaults preferences even though they should not have been. Oracle assigned bug number 2893809 to track this.
- When creating a recurring Meeting whereby one instance had a duration long enough to create a conflict with another instance on the following day, the following message was displayed: "Two or more instances have the same date and time". Oracle assigned bug number 2840028 to track this.
- Clicking OK in the Oracle Calendar Preferences dialog and then choosing View | Set Filter could cause the application to terminate unexpectedly. Oracle assigned bug number 2847602 to track this.
- Attempting to create a recurring Meeting that exceeded the maximum number of instances allowed caused the following unexpected error: Module: <CST_Event_Editor.cpp>, Label: 390, Service error: 0x1812b. Oracle assigned bug number 2872041 to track this.
- Attempting to display the Print Preview for an Agenda page that contained a Meeting spanning more than 24 hours could cause the application to terminate unexpectedly. Oracle assigned bug number 2877037 to track this.
- A password that was changed while working off-line to a password not allowed by the server could cause the application to unexpectedly terminate when attempting to reconcile the on-line and off-line passwords. Oracle assigned bug number 2903609 to track this.
- When a remote user was invited to a meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status would be shown as "will confirm later" instead of "will attend". This was a server issue. Oracle assigned bug number 2892157 to track this.
- Making changes to notification preferences produced a blank dialog box. Oracle assigned bug number 2891594 to track this.
- If you expand a repeating event (Meeting, Daily Note, Day Event), select all the instances and try to change your reply status, the program terminated unexpectedly. Oracle assigned bug number 2919825 to track this.
- You could not create a weekly meeting on a Saturday or Sunday. Oracle assigned bug number 2929937 to track this.
- Clicking the Open All Folders button from a recently retrieved Published Address Book yielded the Save dialog. Oracle assigned bug number 2879881 to track this.
- Creating an address book while working off-line (standalone only) caused errors to occur the next time you signed in. Oracle assigned bug number 2871716 to track this.
- Meetings created by Event Calendars that include attendees yielded unexpected errors. Oracle assigned bug number 2880321 to track this.
- If you opened another user's agenda as a designate and then did a refresh, you would get an error message. Oracle assigned bug number 2919085 to track this.
3.5.3 Oracle Calendar Desktop Client for Linux
This section contains these topics:
3.5.3.1 What's New in this Release?
This section lists new features of Oracle Calendar Desktop Client for Linux.
3.5.3.2 Known Limitations and Workarounds
This section describes general issues and workarounds for Oracle Calendar Desktop Client for Linux.
- Address Book Folders: Changes you make to Address Book Folders preferences will remain in effect for the current session only. They are not properly saved. Oracle assigned bug number 2836729 to track this.
- iCalendar export: iCalendar files exported while working off-line contain errors and cannot be imported. Oracle assigned bug number 2847503 to track this.
3.5.3.3 Resolved Limitations in this Release
This section describes resolved limitations of Oracle Calendar Desktop Client for Linux.
- Attempting to create a group containing a user that was an Event Calendar caused the following unexpected error: Module: <CST_ManageGroupsEditorDlog.cpp>, Label: 135, Service error: 0x13209. Oracle assigned bug number 2847208 to track this.
- Meetings created by Event Calendars that included attendees caused unexpected errors. Oracle assigned bug number 2880299 to track this.
- When a remote user was invited to meeting, the meeting owner's status was not correctly displayed to the remote user. The owner's status was shown as "will confirm later" instead of "will attend". This was a server issue. Oracle assigned bug number 2892157 to track this.
- When changing your password while working off-line, choosing a password that was not allowed by the server could cause the application to unexpectedly terminate when you attempted to reconcile your on-line and off-line passwords. Oracle assigned bug number 2903609 to track this.
3.5.4 Oracle Calendar Desktop Client for Solaris
This section describes general issues and workarounds for Oracle Calendar Desktop Client for Solaris.
- Exporting an iCalendar file: If you export an iCalendar file containing a Holiday, delete the Holiday from your Agenda and then re-import the file using a date range, the Holiday will not appear in your Agenda. Suggested workaround: In the Period area of the Import iCalendar file dialog, select "All" instead of "Range".
- Reconciling your Agendas: Selecting "Download Only" from the Reconcile, Cancel, Download Only dialog box will erase any changes you have made in your off-line Agenda. You will not be warned that any changes that you make will be lost.
- Creating a repeating entry: Clicking "Apply to All" in the General tab of a repeating entry may reset your Reminder and Reply options for all instances of the entry.
- Exceed 7.0: You may encounter problems using Exceed 7.0 with Oracle CorporateTime 5.0.2 for Motif.
- Storing off-line files on a remote machine: Storing off-line files on a remote machine (i.e. not the machine on which you are running the application) may cause slow-downs when you perform certain functions such as working off-line or working with an Address Book. Suggested workaround: Store your off-line files on a local disk.
- Running concurrent copies: You should not run concurrent copies of Oracle CorporateTime from one Unix account.
- Resources with many designates: You can exceed the maximum mail distribution number by adding a resource with many designates. Suggested workaround: Avoid adding resources to mail distribution lists if they have many designates.
3.6 Oracle Calendar Sync Clients
This section contains release note information on these products:
3.6.1 Oracle Calendar Sync for Palm for Windows
This section contains these topics:
3.6.1.1 What's New in this Release?
This section lists new features of Oracle Calendar Sync for Palm for Windows.
- Support for Web Conferencing details in events
- Ability to choose whether or not to synchronize refused events to your device
- Ability to choose whether or not events that fall outside your date range are to be deleted from your device (but kept on the server)
- Support for synchronizing and filtering contact categories
- Support for synchronizing attendees and their statuses to the device
- Ability to change your attendance status from the device and synchronize it back to the server
- Enhanced support for recurrence rule on personal events
- Ability to configure which rules to use during a modify conflict on a per data type basis
3.6.1.2 Known Limitations and Workarounds
This section describes general issues and workarounds for Oracle Calendar Sync for Palm for Windows.
- Upgrades: When upgrading from Oracle CorporateSync 3.0.x for Palm, the InstallShield returns random characters when reading an empty value from the registry instead of returning an error. Oracle assigned bug number 2872048 to track this.
- Titles containing "=": Events and contacts may not synchronize correctly when the title specified ends with an "=" character. Oracle assigned bug number 2864229 to track this.
- Modifications on client and server: When modifying the same contact with a desktop client and the Palm device, and the rules setting is set to replace the mobile device item with the calendar server item, some fields may not be synchronized correctly. Oracle assigned bug number 2851814 to track this.
- Daylight Savings: Recurring meetings which span the Daylight Savings time change may not be synchronized correctly. Several instances before or after the time change may have incorrect end times. Oracle assigned bug number 2842124 to track this.
- Information not synchronized to server: Notes, Alarms and Access Levels modified on the device may not get synchronized with the server. If you are using a V5.4 server, Details may not get synchronized either. Oracle assigned bug number 2842611 to track this.
3.6.2 Oracle Calendar Sync for Palm for Macintosh
This section contains these topics:
3.6.2.1 What's New in this Release?
This section lists new features of Oracle Calendar Sync for Palm for Macintosh.
- Support for ACE
- Support for Mac OS X
3.6.2.2 Known Limitations and Workarounds
This section describes general issues and workarounds for Oracle Calendar Sync for Palm for Macintosh.
- Time zones: The Palm organizer does not support different time zones. Make sure the Palm organizer time zone corresponds to the calendar application's.
- Repeating Entries: You cannot synchronize the Palm organizer's Repeating Entries. You can, however, synchronize calendar server Repeating Entries.
- Hand-held overwrites Macintosh: The 'Hand-held overwrites Macintosh" feature is not available.
- Timed/untimed events: If you change a timed Event to an untimed Event, or vice versa, on your Palm organizer, the change will not appear in the calendar application.
- Languages: Oracle Calendar Sync for Palm only fully supports English-language synchronization.
- Duplicate names: Oracle Calendar Sync for Palm does not present a list of possible matches for duplicated names. To avoid this problem, enter as much unique user information as possible (for example, organization unit).
3.6.3 Oracle Calendar Sync for Pocket PC
This section contains these topics:
3.6.3.1 What's New in this Release?
This section lists new features of Oracle Calendar Sync for Pocket PC:
- Support for Web Conferencing details in events
- Ability to choose whether or not to synchronize refused events to your device
- Ability to choose whether or not events that fall outside your date range are to be deleted from your device (but kept on the server)
- Support for synchronizing and filtering contact categories
- Support for synchronizing attendees and their statuses to the device
- Ability to change your attendance status from the device and synchronize it back to the server
- Enhanced support for recurrence rule on personal events
- Ability to configure which rules to use during a modify conflict on a per data type basis
3.6.3.2 Known Limitations and Workarounds
This section describes general issues and workarounds for Oracle Calendar Sync for Pocket PC.
- Upgrades: When upgrading from Oracle CorporateSync 3.0.x for Pocket PC, the InstallShield returns random characters when reading an empty value from the registry instead of returning an error. Oracle assigned bug number 2872048 to track this.
- Titles containing "=": Events and contacts may not synchronize correctly when the title specified ends with an "=" character. Oracle assigned bug number 2864229 to track this.
- Modifications on client and server: When modifying the same contact with a desktop client and the Pocket PC device, and the rules setting is set to replace the mobile device item with the calendar server item, some fields may not be synchronized correctly. Oracle assigned bug number 2851814 to track this.
- Categories containing spaces: The Calendar server does not support Contact Category names that begin or end with one or more spaces. Oracle assigned bug number 2949143 to track this.
- Daylight Savings: Recurring meetings which span the daylight time change may not be synchronized correctly. Several instances before or after the time change may have incorrect end times. Oracle assigned bug number 2842124 to track this.
- Information not synchronized to server: Editing a recurring event from the device does not sync (with V5.4 Server only). Oracle assigned bug number 2891864 to track this.
