Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Question 1: What happens when an error occurs during the migration process?

Answer 1: When an error occurs during the migration process, an error message will be displayed in the Migration Utility console window. This message will provide a brief description of the issue.

Question 2: Where can I find more detailed information about the error?

Answer 2: For more detailed information regarding the error, you should refer to the migration.log file. This log file contains comprehensive details about the errors encountered and is located at:

\AdeptiaServer\ServerKernel\MigrationUtility\migration.log

Question 3: How do I access the migration.log file?

Answer 3: To access the migration.log file, navigate to the following directory on your system:

...AdeptiaServer\ServerKernel\MigrationUtility

Locate the migration.log file within this directory and open it using a text editor or a log viewer application.

Question 4: What information is available in the migration.log file?

Answer 4: The migration.log file contains detailed information about the migration process, including:

  • Time and date of the migration attempt

  • Detailed error messages and codes

  • Specific steps or actions that failed during migration

  • Any relevant stack traces or debug information

Question 5: What should I do if I cannot understand the error message in the migration.log file?

Answer 5: If you are unable to understand the error message or need further assistance, consider the following steps:

  1. Check the documentation: Refer to the official migration utility documentation for guidance on common errors and troubleshooting steps.

  2. Contact support: If the documentation does not resolve your issue, contact Adeptia support for further assistance. Provide them with the relevant error messages and the migration.log file for quicker resolution.

Question 6: How can I prevent errors during the migration process?

Answer 6: To minimize the risk of errors during migration, ensure the following:

  • Compatibility: Verify that the source and target systems are compatible and meet all prerequisites for migration.

  • Backup: Always create a backup of your data and configurations before starting the migration process.

  • Follow guidelines: Adhere to the guidelines and best practices provided in the migration utility documentation.

  • Test environment: Perform a test migration in a staging or test environment to identify potential issues before executing the migration in the production environment.

Question 7: Can I perform multiple migrations simultaneously?

Answer 7: It is generally recommended to avoid performing multiple migrations simultaneously to prevent potential conflicts and ensure each migration process receives adequate resources. If multiple migrations are necessary, ensure they are executed in a controlled and sequential manner.

Question 8: What should I do if the migration process is interrupted?

Answer 8: If the migration process is interrupted:

  1. Check the console: Look for any immediate error messages in the Migration Utility console window.

  2. Review the log: Examine the migration.log file for detailed information on where and why the interruption occurred.

  3. Resolve issues: Address any issues indicated in the log before attempting to restart the migration process.

  4. Restart migration: Once issues are resolved, restart the migration process from the beginning or from a safe checkpoint if supported.

Question 9: Can a user extract an object from a higher version and deploy it on a lower version?

Answer 9: No, the migration process only allows objects to be migrated from a lower version to a higher version. For example, objects extracted from AC4.X cannot be deployed to AC3.X.

Question 10: During the AIS to AC migration process, can a user deploy the client's objects to any version of AIS?

Answer 10: No, as part of the migration process, the user needs to install AIS and upgrade it to the latest version available before deploying the client's objects.

Question 11: Can the DBCleaner utility create tables in all databases, such as MySQL, SQL, and Oracle?

Answer 11: The DBCleaner utility can create tables only for MySQL and SQL databases. It does not support table creation for Oracle databases.

Question 12: If the DBCleaner utility does not work for Oracle database creation, what should be done?

Answer 12: For creating databases for Oracle, you need to create the backend and log databases for both AIS and AC in RDS (Relational Database Service).

Question 13: Should the aistoacverification utility be run for both AIS and AC in the AIS to AC migration process?

Answer 13: Yes, the aistoacverification utility should be run to correct the objects' data provided by the client before extracting the final corrected objects from AIS.

Question 14: What should be done if the admin's password changes after deploying an object, and you cannot log in?

Answer 14: It is possible that the SysAdmin has modified the password for the admin user. To obtain the updated password:

  1. Go to the backend database.

  2. Locate the au_user table.

  3. Right-click to extract the table by selecting 1000 rows.

  4. Go to the table column au_entityname and find Admin.

  5. Scroll right in the table to locate the au_password column.

  6. Copy the encrypted admin password.

  7. Decrypt the password to obtain the new admin password.

  • No labels