| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.1) Part Number B14486-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Migration and Coexistence Guide 10g Release 1 (10.1.1) Part Number B14486-02 |
|
|
View PDF |
This appendix covers issues regarding e-mail migration and tips to troubleshoot these issues. In addition, it covers the some frequently asked questions regarding e-mail migration. The appendix contains the following sections:
Oracle Collaboration Suite 10g Mail Migration Tool: Installation Issues
Oracle Collaboration Suite 10g Mail Migration Tool: Account Migration Issues
Oracle Collaboration Suite 10g Mail Migration Tool: Data Migration Issues
You may encounter issues while installing Oracle Collaboration Suite Email Migration Tool. This section covers some of the common issues and their workarounds.
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/mail/migration/migrate/Migrate
Action: If you encounter this problem, check whether the Oracle home has been set and the esmigration.zip file has been extracted to the correct directory, which is $ORACLE_HOME/oes/migration.
Error occurred during initialization of VM. Could not reserve enough space for object heap
Action: If you encounter this issue, run Oracle Collaboration Suite Email Migration Tool on a computer that has a minimum of 1 GB RAM.
You may encounter errors while migrating user accounts from a source e-mail system to Oracle Collaboration Suite. This section covers some common errors that occur during account migration.
Error: Mandatory Attribute sn is missing for user username
Action: Populate the user's sn attribute on the source e-mail system and retry user provisioning.
Error: javax.naming.NameNotFoundException:[LDAP:error code 32 - No Such Object]; remaining name source_ldap_parent_dn
Cause: The source LDAP DN entered in the Mail Services page of the migration setup wizard is wrong.
Action: Correct the base DN.
Error: User: username. Batch: batch number. Failed to create user. Target userID is an empty string.
Cause: Applying the username generation rule for that user has resulted in an empty target userID.
Action: Perform the following steps:
Modify users.xml to add the unique targetimapuserid attribute to failed users.
Reload the users by clicking File and then click Load Users on the Oracle Collaboration Suite Email Migration Tool main window.
Click Migrate and then click Provision Users to provision the failed users in Oracle Collaboration Suite.
Error: Batch=batchnum Failed to create entry on target LDAP server. [Invalid DN syntax]
Cause: The manager attribute for the user is not a valid DN.
Action: Set the manager attribute mapping in the LDAP schema mapping wizard to No Mapping.
You may encounter errors while migrating user data from a source e-mail system to Oracle Collaboration Suite. This section covers some common errors that occur during data migration.
Error: Base user username does not exist on the target LDAP server.
Cause: Account creation did not happen correctly.
Action: Rerun the account creation process and ignore any 'duplicate entry' errors.
Error: User:username. Batch:batchnumber. Failed to migrate folder foldername
Cause: Folder migration failed during IMAP migration.
Action: Check if the folder is listed as a No-Select Folder. To check this, perform the following steps:
telnet source_imap_host imap_port
login username password
list "" *
Error: User:username. Batch:batchnumber. Plug-in failed to generate MBOX
Cause: The plug-in failed to extract the user's messages and folders.
Action: Check if the administrator profile has the requisite privileges. Refer to Meeting System-Specific Requirements for details on setting privileges on the source system.
Error: User:username. Batch:batchnumber. Failed to route user
Cause: The plug-in failed to set a routing rule.
Action: Check if the administrator profile has the requisite privileges. Refer to Meeting System-Specific Requirements for details on setting privileges on the source system.
Error: User:username. Batch:batchnumber. Failed to migrate user's e-mail data
Cause: One or more folders were not migrated.
Action: Check folder-specific errors in the migration log.
Error: User:username. Batch:batchnumber. Out of memory error. Try increasing heap size
Cause: Oracle Collaboration Suite Email Migration Tool does not have enough memory to operate.
Action: Increase the value of the -Xmx parameter in migrate.sh for Unix or in migrate.cmd for Microsoft Windows. In addition, reduce the number of concurrent users.
Error: User:username. Batch:batchnumber. Failed to send e-mail to user username with subject mailsubject on SMTP server: servername
Cause: The migration notifier could not send a notification message.
Action: Check if the specified SMTP server is running and allowing relay using the Oracle Enterprise Manager console.
This section contains some of the frequently asked questions (FAQ) regarding Oracle Collaboration Suite e-mail migration.
Question 1: I am getting an error that the attribute attributename is not a fully qualified -mail address. What should I do?
Answer: You are getting this because the specified attribute is not an e-mail address. You should provide a suitable e-mail address for the alias, distribution list, or shared folder.
Question 2: What is the disk space required for an MBOX-based data migration on the computer where Oracle Collaboration Suite Email Migration Tool is run?
Answer: The disk space requirement is approximately 300 MB for concurrently migrating 10 users, assuming a quota of 20 MB for each user. Note that the MBOX files are not deleted by the migration tool after the migration. The disk space is calculated using the following formula:
Disk space required = n * q * 1.5
where n is the number of users to be migrated and q is the quota for each user.
Question 3: How do I resolve account name conflicts?
Answer: If Oracle Collaboration Suite Email Migration Tool detects any duplicate target user names (also called name conflicts) when creating accounts in the target Oracle Internet Directory, then the tool logs an error and does not create the duplicate account. Duplicate target user name errors or name conflict errors can only be avoided if username generation rules are used in such a way that unique target user names are generated.
To resolve name conflicts, perform the following steps for all failed users:
Modify users.xml to add the unique targetimapuserid attribute to failed users.
Reload the users by clicking File and then click Load Users on the Oracle Collaboration Suite Email Migration Tool main window.
Click Migrate and then click Provision Users to provision the failed users in Oracle Collaboration Suite.
Question 4: Can I run setup more than once?
Answer: Yes, you can run the migration setup wizard more than once if the users are not already loaded into the migration repository. If you rerun the setup after loading the users, the state of all the users will be lost.
Question 5: Can I load a user list more than once?
Answer: Ideally, you should extract all users for all domain and load them once. However, multiple loading may be required if, for example, IMAP passwords are not entered in users.xml before loading the users. In this case, edit users.xml to enter or modify the required attributes and then reload the users.
