cancel
Showing results for 
Search instead for 
Did you mean: 

/SAPAPO/OM_LC_DOWNLOAD_UPLOAD section C grayed out

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member229109
Active Contributor
0 Kudos

Hello George,

1) Check the values of the liveCache parameters UNICODE and DEFAULTCODE.

The values should be YES and UNICODE, SAP note 632357.

If you need to change those parameters, please bring the liveCache to offline mode first,

Then set the values as recommended in the note.

Please check that the LCA/LDA/LEA connections are reset in LC10 -> Integration to be pointed

To the target liveCache instance. Restart the application server if the connections were changed

And test connections in /ndb59.

2)

If you still will have the /SAPAPO/OM_LC_DOWNLOAD_UPLOAD buttons for section C all grayed out

=> Please create the SAP message for the BC-DB-LCA component to get SAP support.

Thank you and best regards, Natalia Khlopina

Former Member
0 Kudos

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 ".

former_member229109
Active Contributor
0 Kudos

Hello Sharfuddin Khan,

I recommend you to create the SAP message to the component "BC-DB-LCA" to get SAP support.

We could login to your system & take a look closer on this problem.

Thank you & best regards, Natalia Khlopina

Former Member
0 Kudos

Hello Natalia,

I have already created a message with SAP but a resolution has not been provided yet. The first action recommended to me was to look at some SAP notes, that I had already reviewed and also followed the steps mentioned in the guides.

Is there a way for you to check on this through the ticket I created? The Message number is 305147 / 2010

Thank You!

Sharf Khan