I did, from 3.6 to 4 .1.1 with the migration - script
In general it was succesfull.
Some points need attention.
f.i.: my customer used "/" as a character in the model names like "-" is used (stupid...).
That doesent' work with the migration routine. Correct it in 3.6.
And:
Don't rename the Name and the Login of the Admin! must be "Admin" !!!! in AC3.6.
For the '/' in the source database, this is only for Sybase and SqlAnywhere RDBMS. In this case, you have to check there is no '/' in the fields that are mapped to a fullname. Here is the list of fields concerned:
amSoftware: Publisher, Name, VersionLevel
amProduct: Brand, Model
amContract: Ref
amPOrdLine: ItemNo
amAdjustment:ItemNo
amItemListVal (where Identifier='amBrand'): Value
amFamily: Name, Brand
amAsset (Category.bHardware=1): ComputerName, AssetTag
amInvoice: InvoiceNumber
amCompany: Code
Check the migration.xml file you have with peregrine support. They update it often and your pb have been fixe for oracle, mssql and db2. Maybe your file is not up to date.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.