Error while infocube repartitioning COPY_TO_SHD_FFACT

[Former Member]

Hi,

While repartitioning infocubes i always get an error on COPY_TO_SHD_FFACT step.

The monitor error is the following:

You tried to work with the name of a table or view that does not exist in the database.

An exception with the type CX_SY_NATIVE_SQL_ERROR occured, but was neither handled locally.

But in SE16 the table well exists.

Our database is oracle and system level is 14.

Could anyone help?

Thanks.

Joris

For information:

In SM21 :

"UNCAUGHT_EXCEPTION"

The dump in ST22 is:

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_RSDU_REPART_EXCEPTION

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_RSDU_REPART_EXCEPTION' was raised, but it was not caught anywhere along the call hierarchy.

Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program 'RSDU_IC_COMP_REPART' has to be terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also keep them for a long time.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_RSDU_REPART_EXCEPTION', was not caught and therefore caused a runtime error.

The reason for the exception is: No text available for this exception

The occurrence of the exception is closely related to the occurrence of a previous exception CX_RSDU_REPART_EXCEPTION", which was raised in the program "CL_RSDU_IC_COMP_REPART========CP", specifically in line 102 of the (include) program "CL_RSDU_IC_COMP_REPART========CM00P".

The cause of the exception was: No text available for this exception

The occurrence of the exception is closely related to the occurrence of a previous exception "CX_SY_NO_HANDLER", which was raised in the program "SAPLRSDU_PART_ORA", specifically in line 10 of the (include) program "LRSDU_PART_ORAF03".

The cause of the exception was:

An exception with the type CX_SY_NATIVE_SQL_ERROR occurred, but was neither handled locally, nor declared in a RAISING clause

The occurrence of the exception is closely related to the occurrence of a previous exception "CX_SY_NATIVE_SQL_ERROR", which was raised in the program "SAPLRSDU_PART_ORA", specifically in line 17 of the (include) program "LRSDU_PART_ORAF03".

The cause of the exception was:

You tried to work with the name of a table or view that does not exist in the database

Source Code Extract

Line SourceCde

1 REPORT rsdu_ic_comp_repart .

2

3 TYPE-POOLS: rsd.

4

5 DATA:

6 l_r_exception TYPE REF TO cx_root.

7

8 PARAMETERS:

9 p_ipro TYPE rsinfoprov.

10

11 TRY.

12

13 *Class cl_rsdu_ic_comp_repart calls DB dependent implementation

14 cl_rsdu_ic_comp_repart=>if_rsdu_repart~run(

15 i_infocube = p_ipro ).

16

17 CATCH cx_root INTO l_r_exception.

18

>>>>> RAISE EXCEPTION TYPE cx_rsdu_repart_exception

20 EXPORTING previous = l_r_exception.

21

22 ENDTRY.

Edited by: Joris GIVONETTI on Dec 1, 2010 6:01 PM

[Former Member]

Problem is solved.

SAP advice me to pass the OSS note 1329869.

Now repartitionning is OK.

Joris