problems upgrading from SC4 to SC5

[marchg]

problems encountered during testing. Peregrine suggested that I re-run the conflict resolution. Could you please indicate what steps need to be followed when doing the conflict resolution.

Is there any docs as the manual merely indicates what reports need to be run.

[sjensen]

What problem did you get? or most important where in the upgrade process did it go wrong for you? We have done our test upgrade using the upgrade utility from SC 3.0 SP10 A9901 to SC 5.1.2.4 SC 5.1 Application (we are using AIX 5.2) and let me be honest with you, depending on how your system has been configured/modified you need to do additional tasks. We made our own task-list inluding the upgrade it self, and we landed at 85 task to complete all the stuff.

In week 31 we are going to do it again with our production system.

//Steen

[marchg]

Hi,

Thanks for the reply. The problem I am having is during the conflict resolution. I have printed the exception report and the changes that I need to make are for the status of Renamed. I have changed the Object, Process & datadict object and left some of the format & links as they can be changed later according to our system modifications. When I ran the create upgrade, I received errors with the load transfer.
Error - sqlExec error: CREATE TABLE /*P4[TEMPupgradestatus; m1; sqlserver2k; {{}, {}, {}, {}}; Tot recs: 2; Tot bytes: 128]*/ upgradestatusm1 /* Tconstraints */
(/*P4[descriptor; 0; m1; 1]*/ descriptorprgn image null,
/*P4[version; 1; m1; 0]*/ version varchar(30) null , constraint upgradestatusm1_P UNIQUE (version)
)

(apm.upgrade.sqlsys.sub,create.new)
sqlExec error: errcode=2714 errortext=SQLSERVER error# 2714 severity 16: There is already an object named 'upgradestatusm1' in the database. (apm.upgrade.sqlsys.sub,create.new)
Unrecoverable error in application: apm.upgrade.sqlsys.sub on panel create.new
Unrecoverable error in application: apm.upgrade.sqlsys on panel decide.exit
Unrecoverable error in application: apm.upgrade.load.transfer on panel decide.
The error during changing the dbdict is: Invalid number of parameters (dbdict.sql.changes,call.sql.changes)

I need to know what to change during the conflict resolution and if possible, steps that I need to look at. What exactly needs to be done during conflict resolution besided looking at the Renamed status files.

Thanks

[fid509]

Maybe you may set the sqldrop:1 parameter in sc.ini.
This will drop any existing table prior to conversion.

[marchg]

Thanks for the reply. Forgot about that option.

When I do a create upgrade, I get the following error:
Record number = 795563 (apm.upgrade.build.simple,save.object)
Duplicate key value is: (fileupgradeobjects) keyobject.name=erddef, deviceairconditioning{\"logical.name\"}{\"logical. name\"})) (apm.upgrade.build.simple,save.object)
fileupgradeobjects) keyobject.name=erddef, deviceairconditioning{\"logical.name\"}{\"logical. name\"}) (apm.upgrade.build.simple,save.object)
The record being added contains a duplicate key (apm.upgrade.build.simple,save.object)

Do I need to delete the upgrade objects before doing the create upgrade? Secondly, during my conflict resolution, I change the fields that are displayed in the exception report. How do I re-run the exception report to display only the objects that have not changed. Hope this makes sense as I think that my problem may be in the conflict resolution phase. I might be missing a few steps.