| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.2) Part Number B25493-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.2) Part Number B25493-03 |
|
|
View PDF |
This appendix covers troubleshooting tips and frequently asked questions regarding migration to Oracle Calendar.
The appendix contains the following sections:
This section contains the troubleshooting tips and the frequently asked questions about migrating to Oracle Collaboration Suite from Microsoft Exchange.
Question: Where can I get the latest version of the ExMigrate tool?
The latest version of the ExMigrate tool can be downloaded from Metalink (http://metalink.oracle.com). The following are the steps to locate the ExMigrate tool:
In the Metalink home page, click Patches and Updates.
Click Simple Search.
Enter 3394297 as the patch number and select Microsoft Windows 32 bit (Client) as the platform.
Question: ExMigrate does not provision Calendar accounts. How can I provision accounts for thousands of users?
The unison user account contains a number of scripts in the unison/bin directory that help in account provisioning. Specifically, you can use unidssearch and uniuser to perform this task. unidssearch prints a list of all LDAP accounts that do not have Calendar service. The printed format is the syntax required by uniuser, which adds the Calendar service to an LDAP subscriber. So you can execute the two commands simultaneously. For example,
$ unidssearch > new_users $ uniuser -ex new_users -n nodeid
Where nodeid is the number of your Calendar server node, which you provided during installation. If you have forgotten it, check the unison/misc/unison.ini file in the unison account.
The file new_users will look something like this:
A DID=cn=UserOne,cn=Users,dc=us,dc=oracle,dc=com A DID=cn=UserTwo,cn=Users,dc=us,dc=oracle,dc=com
Question: ExMigrate requires a password value in the users.ini file. How can I retrieve the password?
You can briefly modify the user passwords to a value that is known to you. In this case, you should communicate to the user population that their accounts will be temporarily unavailable while you perform the migration. Then, use an ldapsearch command to retrieve the current password settings, and store the settings in a file. This password value is an MD4 hashed value. However, this should not be a problem because you do not need to know the plain text value.
The following is an example of issuing the ldapsearch command:
$ORACLE_HOME/bin/ldapsearch -h hostname.domain -p 4032 -D cn=orcladmin -w password -b "cn=Users,dc=us,dc=oracle,dc=com" "cn=*" userpassword
The following is the output of the preceding command:
dn: cn=UserOne,cn=Users,dc=us,dc=oracle,dc=com
userpassword: {MD4}DI7mvQ+Wm9WcXrYRdYQYQQ==
dn: cn=UserTwo,cn=Users,dc=us,dc=oracle,dc=com
userpassword: {MD4}DI7mvQ+Wm9WcXrYRdYQYQQ==
First, save these results so you can restore the original password values later. Then, run the following command:
$ORACLE_HOME/bin/ldapmodify -v -r -h hostname.domain -p 4032 -D cn=orcladmin -w password -f umod
Where umod is a file with contents similar to the following:
dn: cn=UserOne,cn=Users,dc=us,dc=oracle,dc=com changetype: modify userpassword: welcome1 dn: cn=UserTwo,cn=Users,dc=us,dc=oracle,dc=com changetype: modify userpassword: welcome1
So now for the period of your migration, you know the passwords of the users and you can build the users.ini file with these values. Once the migration is complete, you can do the reverse by running ldapmodify with a file that has contents similar to the following:
dn: cn=UserOne,cn=Users,dc=us,dc=oracle,dc=com
changetype: modify
userpassword: {MD4}DI7mvQ+Wm9WcXrYRdYQYQQ==
dn: cn=UserTwo,cn=Users,dc=us,dc=oracle,dc=com
changetype: modify
userpassword: {MD4}DI7mvQ+Wm9WcXrYRdYQYQQ==
Question: What will ExMigrate allow me to migrate from Exchange? Will ExMigrate permit me to migrate PST or profile information from Outlook?
The following information can be migrated from an Exchange server:
Calendar
Contacts
Journal
Notes
Tasks
ExMigrate can only be used to migrate accounts and their scheduling information from the Exchange server. Refer to the Readme files which are part of the ExMigrate.zip for limitations and caveats.
Question: How do I know if the Exchange Administrator profile has the correct privileges for running ExMigrate?
Ask the Exchange site administrator. The Administrator account should have an Exchange mailbox, and have permissions to open and read other users' inboxes. Select the Admin role from the list of permissions for this user using the Exchange Management Interface.
Question: How do I know whether my migration setup is correct?
Try populating the [MasterList] section of ExMigrateUsers.ini with users accounts, and then add one of those accounts to the [MigrationSubset] section. This will allow you to test one account, and monitor the logs for the results.
Question: How do I know if a user has been migrated?
User accounts which are successfully migrated are marked as the following in the [MigrationSubset] section of ExMigrateUsers.ini (with a /D prefix):
D=1/E=ExchangeUser1/U=OCSUser1
If a user account is unsuccessfully migrated, it must be cleared and restarted.
Question: I have run a test migration, and all the attendees for a specific meeting have their own copy of the meeting. What happened?
Ensure that the [MasterList] section of the ExmigrateUsers.ini file is filled properly and it contains the complete list of users to be migrated. Although you are only migrating the accounts listed in the [MigrationSubset] section of the same file, the links to the meetings are maintained by consulting the users in the [MasterList] section. Any unresolved names in a meeting will cause this behavior.
Question: I get a message stating that ÒCan't connect to the Exchange serverÓ. What could be causing this?
Verify that the [ExchangeServer] section of the ExMigrateConfig.ini file is correctly filled out. Use the /hint switch with ExMigrate to generate this information. The latest version of ExMigrate supports the switch for both Exchange 5.5 and 2000.
This section contains the troubleshooting tips regarding migrating Calendar data from MeetingMaker.
Issue: Unable to import more than one MeetingMaker export file at once.
Cause: Faulty parameter setting in the unimmimpsrv.ini file.
Action: Make sure to set one timezone per export file in the unimmimpsrv.ini file. For example, if timezone is PST8PDT and the NodeID of the Calendar server is 100, the parameter setting in unimmimpsrv.ini should be:
[100]
mmexportfilelist={mm1.dat, mm2.dat, mm3.dat}
mmtimezonelist={PST8PDT, PST8PDT, PST8PDT}
Issue: unimmimpsrv runs successfully but no data is imported.
Cause: Missing parameter in the unimmimpsrv.ini file.
Action: Verify the unimmimpsrv.ini file. In particular, verify that you have as many mmtimezonelist entries as you have mmexportfilelist entries. In addition, verify that the node identifiers are correct for your deployment.
This section contains the troubleshooting tips regarding migrating Calendar data using iCalendar representation.
Issue: Using the uniical utility for a day event is returning a specific error message:
uniical [error]: Invalid icalendar data.
UID = 20040824T084800Z-Fall-Semester-Begins
Cause: Some iCalendar data in the import file is incorrect. The iCalendar entry can be identified by the UID, when the UID is provided in the iCalendar data.
Action: Verify the iCalendar data for the specified UID. In particular, the date format usually causes issues. The log file at $ORACLE_HOME/ocal/log/uniical.log would be helpful to diagnose the issue.
For example, the following would be valid date formats:
DTSTART:20040824T084800Z DTEND:20040824T094800Z
