Secondary index creation on infocube is faililng with ABAP Short dump ORA 60

[former_member558460]

Hi All,

Secondary index creation on infocube is getting failed with the below short dump:

Short text

    SQL error in the database when accessing a table.

What can you do?

    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator

    .

    You can use the ABAP dump analysis transaction ST22 to view and manage

    termination messages, in particular for long term reference.

How to correct the error

    Database error text........: "ORA-00060: deadlock detected while waiting for

     resource"

    Internal call code.........: "[RSQL/INSR//BIC/FZETTDC01 ]"

    Please check the entries in the system log (Transaction SM21).

    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:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"GP87BJ6EJY8VN3ITXZSPTIBJNUY" or "GP87BJ6EJY8VN3ITXZSPTIBJNUY"

"WRITE_ICFACT"

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

notification to SAP, include the following information:

1. The description of the current problem (short dump)

    To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

    Display the system log by calling transaction SM21.

    Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

    In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

Information on where terminated

    Termination occurred in the ABAP program "GP87BJ6EJY8VN3ITXZSPTIBJNUY" - in

     "WRITE_ICFACT".

    The main program was "RSBATCH_EXECUTE_PROZESS ".

    In the source code you have the termination point in line 6031

    of the (Include) program "GP87BJ6EJY8VN3ITXZSPTIBJNUY".

    The program "GP87BJ6EJY8VN3ITXZSPTIBJNUY" was started as a background job.

    Job Name....... "BIDTPR_9006861_1"

    Job Initiator.. "ALEREMOTE"

    Job Number..... 21323400

    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

    procedure "WRITE_ICFACT" "(FORM)", but it was neither handled locally nor

     declared

    in the RAISING clause of its signature.

    The procedure is in program "GP87BJ6EJY8VN3ITXZSPTIBJNUY "; its source code

     begins in line

    5994 of the (Include program "GP87BJ6EJY8VN3ITXZSPTIBJNUY ".

6001     l_s_delta_pkg    TYPE rsdd_delta_pkg,

6002     l_lines          TYPE i,

6003     l_facttab     TYPE rsd_tablnm.      " KFL01: local fact table

6004

6005   FIELD-SYMBOLS:

6006     <l_s_u>       TYPE /BIC/FZETTDC01.

6007

6008   l_facttab  = '/BIC/FZETTDC01'.

6009

6010   CALL FUNCTION 'RSDU_DB_COMMIT'. "Commit falls duprec bei insert!

6011   c_lines = 0.

6012

6013   SORT g_t_u BY

6014   KEY_ZETTDDC01P

6015   KEY_ZETTDC01T

6016   KEY_ZETTDC01U

6017   KEY_ZETTD011

6018   KEY_ZETTD012

6019   KEY_ZETTDC013

6020   KEY_ZETTDC014

6021   KEY_ZETTD015

6022   KEY_ZETTDC016

6023   KEY_ZETTDC017

6024   KEY_ZETTDC018

6025   KEY_ZETTDC019

6026   KEY_ZETTDC01A

6027   KEY_ZETTDC01B

6028   KEY_ZETTDC01C

6029   .

6030

>>>>> INSERT (l_facttab) FROM TABLE g_t_u.

6032 c_lines  = sy-dbcnt.

6033

6034

6035 ***** Check requid if no inconsistency is happened********************

6036 CALL FUNCTION 'RSM_INFOCUBE_WRITE_CHECK'

6037   EXPORTING

6038     i_infocube        = 'ZETTDDC01'

6039     i_rnsid           = i_req_sid

6040   EXCEPTIONS

6041     write_not_allowed = 1

6042     OTHERS            = 2.

6043 **** shortdump if write is not allowed in the current state *********

6044 **** If no entry in the table RSMDATASTATE ===> no abort    *********

6045 IF sy-subrc = 1.

6046   MESSAGE x299(brain)

6047   WITH sy-repid i_req_sid.

6048 ENDIF.

6049 ENDFORM.                    "WRITE_ICFACT

6050

Please Advice,

Asim.

[former_member183519]

Hi Asmin,

pls refer link:

Fail when create index | SCN

Regards,

Hitesh

[former_member558460]

Hi All,

I tried RSRV but still its not working.

@Jyothi: Report performance its slow, thats the reason we need secondary index.

Regards,

Asim.

[RamanKorrapati]

Hi asim,

Please try to delete created secondary index.

Lets try activate your cube and do the RSRV tests.

once your cube was fine then you can create index on your cube thru process chain.

delete index before loading and created index after dtp load to cube.

to increase report performance you can create aggregates on your cube.

Thanks

[Former Member]

Hi Asim,

if your query had too many restricted key figures and calculated key figure and many characteristics in rows and free chars, also degrade the query performance..

revise your query definition again , compress cube data if there are many request.. and create an aggregates with the objects that are used in query

[Former Member]

Hi Asim,

dimensional table in info cube are already indexed, why do you need secondary index?

[RamanKorrapati]

Hi Asim,

please check with your Oracle DB/basis team.

its  DB level issue.

Lets try to  activate info cube and check it.

try to do RSRV tests on cube.

Thanks