ai-center
2023.10
true
- Release Notes
- Before you begin
- Getting started
- Installing AI Center
- Migration and upgrade
- Projects
- Datasets
- Data Labeling
- ML packages
- Out of the box packages
- Pipelines
- ML Skills
- ML Logs
- Document UnderstandingTM in AI Center
- AI Center API
- How to
- Licensing
- Basic Troubleshooting Guide
Troubleshooting
AI Center User Guide
Last updated Oct 22, 2024
Troubleshooting
The tenant needs to be created in the Automation Suite environment before running the migration script.
The migration script is meant to migrate datasets and ML packages only once. On rare
occasions, there are some extra datasets or ML packages added in the source environment post
migration is complete then in this case the migration needs to be re-run. Run the following
commands in the destination database before re-running the
migration:
delete from [ai_pkgmanager].[ml_package_versions_temp];
delete from [ai_pkgmanager].[projects] where tenant_id in ('T1','T2',...);
delete from [ai_pkgmanager].[ml_packages] where tenant_id in ('T1','T2',...);
delete from [ai_pkgmanager].[ml_package_versions] where tenant_id in ('T1','T2',...);
delete from [ai_trainer].[datasets] where tenant_id in ('T1','T2',...);
delete from [ai_pkgmanager].[ml_package_versions_temp];
delete from [ai_pkgmanager].[projects] where tenant_id in ('T1','T2',...);
delete from [ai_pkgmanager].[ml_packages] where tenant_id in ('T1','T2',...);
delete from [ai_pkgmanager].[ml_package_versions] where tenant_id in ('T1','T2',...);
delete from [ai_trainer].[datasets] where tenant_id in ('T1','T2',...);
Note:
`T1`
, `T2`
, … in the query above are the tenant UUIDs
in the destination environment. These are the DESTINATION_TENANT_ID
as
mentioned in the input.json
file passed while running the migration script
./mastermigrationscript.sh input.json
.
You can re-run the migration
using the following
commands:
cd ~/migration/ai-customer-scripts/platform/sfmigration/
./mastermigrationscript.sh input.json
cd ~/migration/ai-customer-scripts/platform/sfmigration/
./mastermigrationscript.sh input.json
After the migration, cloned ML Packages present in the source environment will be marked as
VALIDATION_FAILED
in the Automation Suite environment. These packages
need to be cloned again in the destination environment once the migration is complete.
Note: In this case, cloned packages refers to the
packages from UiPath® and Open-Source
Packages.