UC_OBJECTS_NOT_CONVERTIBLE DSO request activation issue

[arun_purohit]

Hi BW Experts,

We have installed a standard BI content flow of a DSO.

I have loaded data till PSA & then loaded DSO DTP.... went fine...

but while activating DSO request, getting error & short dump...

Following is the dump-

****

Category               ABAP Programming Error

Runtime Errors         UC_OBJECTS_NOT_CONVERTIBLE

ABAP Program           CL_RSDMD_UPDATE_MASTER_DATA===CP

Application Component  BW-WHM-DBA

****

......

****

Error analysis

    The statement

       "MOVE src TO dst"

    requires that the operands "dst" and "src" are convertible.

    Since this statement is in a Unicode program, the special conversion

    rules for Unicode programs apply.

    In this case, these rules were violated.

How to correct the error

    Use only convertible operands "dst" and "src" for the statement

       "MOVE src TO dst"

    Probably the only way to eliminate the error is to correct the program.

    -

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

    "UC_OBJECTS_NOT_CONVERTIBLE" " "

    "CL_RSDMD_UPDATE_MASTER_DATA===CP" or "CL_RSDMD_UPDATE_MASTER_DATA===CM00T"

    "_CREATE_XY_IMAGES"

    If you cannot solve the problem yourself and want to send an error

**************************

There is not customization in BI content flow.... all codes are standard.... Activation log indicates SID generation error.....

data looks fine (nothing junk in data)....

Activation went fine when we removed SID generation.....

Any idea what went wrong & what could be the probable solution......

Initially we though, since activation went fine without SID... if might b DB issue, as in DB03, PSATEMP space is 100% utilized......

I looked up in scn for threads with similar dump, found some threads with similar dump but no applicable solution for our case...

Please help with this.....

Thanks

Arun Purohit

[dinesh_smhdr · Accepted solution]

Sometimes SID activation error generates due to no. of processes running in the background.

You can check this in RZ04. You can select the request in the DSO , reduce the no of PARALLEL ACTIVATION  and PARRELISM SID from 3 to 1 anc check.

[arun_purohit · Accepted solution]

Hi Dinesh,

We have enough background processes, I checked. Activation issue is with respect to one particular infoobject ABC & other infoobjects which are having ABC as reference infoobject.

I tried removing those infoobjects & activation went fine.

That object is giving error in RSRV for all Master data tests related to SID... Tried repairing them but no luck.....

Basis Developer View of Short dump says-

The internal operation just processed is "MOVE".

Internal mode was started at *******.

The operand "dst" has the type "G_S_ASI" of the length 124,

the operand "src" has the type "I" of the length 4.

[former_member182470 · Accepted solution]

Try to repair your SID generation with this FM: RRSI_VAL_SID_SINGLE_CONVERT

Execute this in SE37.

[arun_purohit · Accepted solution]

Hi Suman,

Will adjusting SID tables of that object in SE14 help??

[former_member182470 · Accepted solution]

Yeah, you have to repair the SID inconsistency for that infoobject. Have you run the function module which I gave you?

[arun_purohit · Accepted solution]

I didn't try that FM yet...

http://www.consolut.com/en/s/sap-ides-access/d/s/doc/F-RRSI_VAL_SID_SINGLE_CONVERT

looks like, I need to pass characteristic values for repairing SID's...

if that not b the case... how shall I proceed with that FM...

[former_member182470 · Accepted solution]

Yeah, you need to pass the infoobject name and try to execute. If it doesn't , then try to pass other parameters.

[arun_purohit · Accepted solution]

Hi Suman,

I tried using that function module, but no luck with it...

It just displays SID value for the particular value of infoobject.

But our issue got resolved partly. Steps-

1) We removed one attribute of our infoobject, apparently it was the cause

2) reactivated the infoobject, adjust p table in SE14

Following above two steps, we didn't get any short dump but DSO request activation, but DSO activation job got failed.

I did RSRV again, this time get fewer errors. Error says, no entry in x table for corresponding p table entries....

I checked X table, it was with zero records.....

Hence, issue was related to master data only... base tables...

Please provide you inputs if required.

Thanks.

[former_member182470 · Accepted solution]

What made you to remove the attribute? Anyways, your issue got resolved. Please close the thread..

[arun_purohit · Accepted solution]

I will close this thread by EOD tomorrow, after 100% resolution.

I need to check removal of that attribute & .....

Will close the thread mostly by tomorrow EOD.

Thanks for your prompt support.

[arun_purohit · Accepted solution]

Hi Suman,

few queries-

1) in that master data object-

we have huge volume of data in Ptable, but somehow data in SID X table is zero.

Is there any approach of re-generating SID's, without having to reload all the master data?

2) as I told u we removed an attribute in that infoobject. Could it be a risk? Is there any chance that when we move that object to BW Production, master data already in BW Prod for that object get corrupted?

Becasue we suspect that in Dev SID table data got deleted due to some transports we made to BW Dev from some other system.

[former_member182470 · Accepted solution]

Hi,

1) Without loading master data it is not possible to fill whole SID table. If any inconsistencies in SID table, then you can repair it with RSRV or with FM. But to load whole SID, you have to load master data again. P -table means Time Independent Display Attr table

2) Is that attribute is not going to be used in your reports? If no, then you can transport the infoobject to prod. You have to reload the master data again in prod to ensure no data inconsistency in SID tables

Regards,

Suman

[former_member182470]

Hi,

You should have run RSRV test for your DSO when the error occurred. It would have shown you about the inconsistency in SID generation. You can repair here itself.

You can do database inconsistency checks also in RSRV

Regards,

Suman

[arun_purohit]

Hi Suman,

Tried that already.... All is fine in RSRV.....

any chance is it a upgrade related issue for 3.5 To 7.3..

Please let me know if more info from job log or dump is required...

[former_member182470]

We can suspect about the upgrade too. I suggest you to report to SAP and wait for their observations.