Hi,
We are facing some problem to migrate one Base from 7,2 to 9.8. Does anyone has passed for this and fixed?
The error (om.sag.aris.cip.api.CipException: clan already exists:) are described and showed below:
File Datamigration.log
015-08-10 18:49:33,911|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - Start Migrate Processos XXXX YYYYYY V3 sem versionamento |
databasetype: BASIC | date: Thu Aug 06 10:12:29 BRT 2015 | name: Processos XXXX YYYYYY V3 | schema: aris | version: 25
2015-08-10 18:49:33,911|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - ******************************************** Start options
********************************************
Migration:
- Handle ARIS 7.2 databases
- DTO write number: # 1000
- Log level: 339
- Max size GUID cache: # 100000
- Max size OID cache: # 200000
Optimization:
- ADB size in MB: 0
- Element number per asn: # 5000
- Write number to migration db: # 10000
- Write numbers for tables:
- Table 008: # 2000
- Table 011: # 2000
- Table 012: # 2000
- Table 013: # 2000
- Table 014: # 2000
- Table 015: # 2000
- Table 020: # 2000
- Table 021: # 10000
- Table 022: # 2000
- Table 025: # 2000
- Table 026: # 2000
- Table 027: # 2000
- Table 028: # 2000
- Table 029: # 2000
- Table 030: # 10000
- Table 045: # 2000
******************************************** Finish options ********************************************
2015-08-10 18:49:33,911|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - Cannot read entry _ArchiveSequenceDescriptions
2015-08-10 18:49:33,927|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - ********************************************
********************************************
Exception during migration of optimized database Processos XXXX YYYYYY V3 sem versionamento | clan already exists: Processos XXXX YYYYYY V3 sem versionamento
Cancel optimization and migrate database in normal mode
2015-08-10 18:49:33,927|ERROR|abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - com.sag.aris.cip.api.CipException: clan already exists: Processos
XXXX YYYYYY V3 sem versionamento
at com.sag.aris.cip.impl.hib.HibClanAdministrator.createClan(HibClanAdministrator.java:214)
at com.sag.aris.cip.impl.hib.HibClanAdministrator.createClan(HibClanAdministrator.java:171)
at com.aris.modeling.server.dao.impl.cipbased.ADatabaseDAO.createDatabase(ADatabaseDAO.java:84)
at com.aris.modeling.server.services.datamigration.common.ADataMigrationServiceBase.migrateDBImpl(ADataMigrationServiceBase.java:1149)
at com.aris.modeling.server.services.datamigration.common.ADataMigrationServiceBase.migrateDB(ADataMigrationServiceBase.java:1045)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl.migrateDB(AServerAdminImpl.java:1171)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl._restoreDb(AServerAdminImpl.java:961)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl.restoreDb(AServerAdminImpl.java:939)
at com.aris.modeling.server.bl.components.serveradmin.AServerAdmin$ARestoreAction.run(AServerAdmin.java:801)
at com.aris.modeling.server.common.AServerTaskRunnable.run(AServerTaskRunnable.java:27)
at java.lang.Thread.run(Thread.java:745)
com.sag.aris.cip.api.CipException: clan already exists: Processos XXXX YYYYYY V3 sem versionamento
at com.sag.aris.cip.impl.hib.HibClanAdministrator.createClan(HibClanAdministrator.java:214)
at com.sag.aris.cip.impl.hib.HibClanAdministrator.createClan(HibClanAdministrator.java:171)
at com.aris.modeling.server.dao.impl.cipbased.ADatabaseDAO.createDatabase(ADatabaseDAO.java:84)
at com.aris.modeling.server.services.datamigration.common.ADataMigrationServiceBase.migrateDBImpl(ADataMigrationServiceBase.java:1149)
at com.aris.modeling.server.services.datamigration.common.ADataMigrationServiceBase.migrateDB(ADataMigrationServiceBase.java:1045)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl.migrateDB(AServerAdminImpl.java:1171)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl._restoreDb(AServerAdminImpl.java:961)
at com.aris.modeling.server.bl.admin.logic.AServerAdminImpl.restoreDb(AServerAdminImpl.java:939)
at com.aris.modeling.server.bl.components.serveradmin.AServerAdmin$ARestoreAction.run(AServerAdmin.java:801)
at com.aris.modeling.server.common.AServerTaskRunnable.run(AServerTaskRunnable.java:27)
at java.lang.Thread.run(Thread.java:745)
2015-08-10 18:49:33,927|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - ********************************************
********************************************
2015-08-10 18:49:40,865|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - Start Migrate Processos XXXX YYYYYY V3 sem versionamento |
databasetype: BASIC | date: Thu Aug 06 10:12:29 BRT 2015 | name: Processos XXXX YYYYYY V3 | schema: aris | version: 25
2015-08-10 18:49:40,865|INFO |abs0000000000|default|12gUjqikWd|0000030070|Restore (database: Processos XXXX YYYYYY V3 sem versionamento)|datamigration - ******************************************** Start options
********************************************
Migration:
- Handle ARIS 7.2 databases
- DTO write number: # 1000
- Log level: 339
- Max size GUID cache: # 100000
- Max size OID cache: # 200000
Optimization:
- ADB size in MB: 0
- Element number per asn: # 5000
- Write number to migration db: # 10000
- Write numbers for tables:
- Table 008: # 2000
- Table 011: # 2000
- Table 012: # 2000
- Table 013: # 2000
- Table 014: # 2000
- Table 015: # 2000
- Table 020: # 2000
- Table 021: # 10000
- Table 022: # 2000
- Table 025: # 2000
- Table 026: # 2000
- Table 027: # 2000
- Table 028: # 2000
- Table 029: # 2000
- Table 030: # 10000
- Table 045: # 2000
******************************************** Finish options ********************************************
Hi!
We face the same issue, and I tried the delete command in Admin tool, but got an error message saying 'Error: The system is unable to find the database'. I am able to delete the databases that have status 'visible', but not the ones with status 'migrating'. Is there another command to delete them?
Thanks in advance for any help.
Regards,
Elin