/SAPAPO/OM_LC_DOWNLOAD_UPLOAD section C grayed out

Question

I have recently completed an unicode conversion of our SCM 7.0 system. On the source I ran sections A and B, then did the unicode conversion. On the target I did a fresh install of liveCache and made it the same build. I followed the info in note 632357
I have then tried this process two ways, but the first way which I thought was what I needed to do caused many issues.
The first process.
I used the commands below to get the parameters set in the target install the same as they were in the source.
$ dbmcli -u control,#####  -d APT 
$ db_drop
$ dbmcli db_create APT control,######
$ dbmcli -u control,###### -d APT
dbmcli on APT> medium_put APT_BACKUP /tmp/APTinst/APT.backup FILE DATA 0 8 YES
dbmcli on APT> service_connect
dbmcli on APT> recover_config APT_BACKUP
dbmcli on APT> service_release
The parameters seemed to work, but the problem I had was trying to get the datafiles created. The source had 16 datafiles so I was trying to create the targets 16 datafiles. I ran the below command for that and it said ok, but never actually created them.
dbmcli on APT> param_addvolume 1 DATA  /sapdb/APT/sapdata1/DISKD0001 F 262144
dbmcli on APT> param_addvolume 2 DATA  /sapdb/APT/sapdata1/DISKD0002 F 262144
dbmcli on APT> param_addvolume 3 DATA  /sapdb/APT/sapdata1/DISKD0003 F 262144
dbmcli on APT> param_addvolume 4 DATA  /sapdb/APT/sapdata1/DISKD0004 F 262144
dbmcli on APT> param_addvolume 5 DATA  /sapdb/APT/sapdata1/DISKD0005 F 262144
dbmcli on APT> param_addvolume 6 DATA  /sapdb/APT/sapdata1/DISKD0006 F 262144
dbmcli on APT> param_addvolume 7 DATA  /sapdb/APT/sapdata1/DISKD0007 F 262144
dbmcli on APT> param_addvolume 8 DATA  /sapdb/APT/sapdata1/DISKD0008 F 262144
dbmcli on APT> param_addvolume 9 DATA  /sapdb/APT/sapdata1/DISKD0009 F 262144
dbmcli on APT> param_addvolume 10 DATA /sapdb/APT/sapdata1/DISKD0010 F 262144
dbmcli on APT> param_addvolume 11 DATA /sapdb/APT/sapdata1/DISKD0011 F 262144
dbmcli on APT> param_addvolume 12 DATA /sapdb/APT/sapdata1/DISKD0012 F 262144
dbmcli on APT> param_addvolume 13 DATA /sapdb/APT/sapdata1/DISKD0013 F 262144
dbmcli on APT> param_addvolume 14 DATA /sapdb/APT/sapdata1/DISKD0014 F 262144
dbmcli on APT> param_addvolume 15 DATA /sapdb/APT/sapdata1/DISKD0015 F 262144
dbmcli on APT> param_addvolume 16 DATA /sapdb/APT/sapdata1/DISKD0016 F 262144
I then went back into se38 and ran /SAPAPO/OM_LC_DOWNLOAD_UPLOAD, but the buttons for section C are all grayed out.
The second process was to use what the fresh target install created with no parameter changes, but I then went back into se38 and ran /SAPAPO/OM_LC_DOWNLOAD_UPLOAD, but the buttons for section C were still all grayed out.
Thanks

Answer 1

Hello Natalia,
I have an issue with step C4-loading LiveCache transactional data in section C.
We are in the process of upgrading our SCM5.0 system to release SCM7.0. Our source livecache version is 7.6.03.12 and target livecache version we are upgrading to is 7.7.04.29. We are in the downtime phase of the upgrade, executing the post LiveCache upgrade C1-C11 steps in Section C.
During step C4 when uploading LiveCache transaction data, we are running into an error CONNE_IMPORT_WRONG_COMP_TYPE. The dump says that "when importing the object 'OT_ORDERS", the component no. 5 in the dataset has a different type from the corresponding component of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL". The data type is "P" in the dataset, but "C in the program"
We are running AIX5.3 and Oracle 10.2.0.2.0.
I would appreciate if you can provide some help or pointers on how this issue can be addressed. Thank you!
Please see below for some information from the ST22 dump
Error analysis                                                                                |
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "GET_DB" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When importing the object "OT_ORDERS", the component no. 5 in the
dataset has a different type from the corresponding component
of the target object in the program "/SAPAPO/SAPLOM_UPGR_PARALLEL".
The data type is "P" in the dataset, but "C" in the program.
Information on where terminated
Termination occurred in the ABAP program "/SAPAPO/SAPLOM_UPGR_PARALLEL" - in
"GET_DB".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 3222
of the (Include) program "/SAPAPO/OM_UPG_CLASS_IMPCLUT".
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "GET_DB" "(METHOD)", but it was neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/SAPAPO/SAPLOM_UPGR_PARALLEL "; its source code
begins in line
|    3221 of the (Include program "/SAPAPO/OM_UPG_CLASS_IMPCLUT ".