RAISE_EXCEPTION dump

Hi All ,

Let me know if anyone can provide any solution to the dump as attached

oracle db 11.2.3

OS is linux x86 64

Further , SAP note 900376 - Data collection methods CCMS_GEN_TAB_R and CCMS_GEN_TAB_S is not applicable

Regards

Ram

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

Hi Bharatram,

Please provide more information about the dumps what action you have performed so you get this dump and also sm21 log info.

Atul

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hey atul ,

Below is the information in detail::

Runtime Errors RAISE_EXCEPTION

Date and Time 23.07.2014 17:07:53

Short text

Exception condition "INTERNAL_ERROR" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

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

A RAISE statement in the program "SAPLSCSM_DATA_SUPPLIER" raised the exception

condition "INTERNAL_ERROR".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

How to correct the error

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:

"RAISE_EXCEPTION" " "

"SAPLSCSM_DATA_SUPPLIER" or "SCSM_GEN_TAB"

"SETTABLE"

"SAPLSCSM_DATA_SUPPLIER" "INTERNAL_ERROR"

"SAPMSSY8 " "INTERNAL_ERROR"

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.

User and Transaction

Client.............. 000

User................ "SAPSYS"

Language key........ "E"

Transaction......... " "

Transactions ID..... "53CF553C420C4FF0E10000008361B2F6"

Program............. "SAPLSCSM_DATA_SUPPLIER"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

Termination occurred in the ABAP program "SAPLSCSM_DATA_SUPPLIER" - in

"SETTABLE".

The main program was "SAPMSSY8 ".

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

of the (Include) program "SCSM_GEN_TAB".

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

Job Name....... " "

Job Initiator.. " "

Job Number..... " "

Regards

Ram

Check if this note is applicable

1755994 - Data collector CCMS_GEN_TAB_R terminates

1677348 - Table monitoring terminates when started

Also let me know which program or job led to this ABAP Dump.

Hello Ram,

could you please attach screenshots about configuration of the method which terminates in RZ21 --> Methods --> Method Definitions --> Display Overview? Often wrong parameter settings are causing errors with the method. Which method you have used - CCMS_GEN_TAB_R or CCMS_GEN_TAB_G?

Regards,
Alwina

Thanks Alwina Enns ,

Below are the screenshots for CCMS_GEN_TAB_R & CCMS_GEN_TAB_G

Let me know your suggestions or inputs

Regards

Ram

show the values under parameters tabs

Hi Divyanshu Srivastava,

Below are the values under parameter tabs:

Regards

Ram

Hello Ram,

thanks. But this is the default configuration of the both methods. Do these both methods terminate or do you have a copy of these methods to monitor another table? Could you please check open alerts under:

RZ20 --> SAP CCMS Technical Expert Monitors
              --> CCMS Selfmonitoring
                   --> <SID> --> MoniInfra_<instance>
                       --> Tooldispatching (short running tasks)
                             --> Messages

if you see in the alerts which method terminates?

Regards,
Alwina

Therre are many alerts with termination as given above .

Let me know if any solutions can be given?/

Regards

Ram

Hello Ram,

the CCMS_MSS* methods you need only if you have a MSSQL database, if you have another database these methods can be deactivated. Most likely the method Z_CCMS_GEN_TAB_ARFCSSTATE_G creates the raise_exeption dump, could you please attach screenshots about configuration of this method in RZ21?

Regards,
Alwina

Hi Alwina,

Below is the method forZ_CCMS_GEN_TAB_ARFCSSTATE_G in RZ21

Regards

Ram

Hello Ram,

thanks. Some suggestions on the parameters:

For the parameter T100_MESS you should use a message ID which is defined in the transaction SE91.

For the parameter WHERECLAUSE2 could you please remove "space", it should look like ARFCSTATE='SYSFAIL'.

For the parameter RESCANFROMBEGIN please check the note:

1677348 - Table monitoring terminates when started

In this parameter a name of the column in the table should be defined. Does such column (ende) exist in the table, which you need to monitor?

After you have make changes to the parameters and stored the method definition please reset the monitoring segment in 'WARMUP' status and check again the selfmonitoring structure in RZ20 if the method still terminates. You can reset the segment in "RZ21 --> Topology --> Segment Overview --> Display Overview", then "change mode", then select the segment of the instance, where table monitoring MTEs are located, and press the button "Reset Segment in "WARMUP" Status".

Regards,
Alwina

Is that all you have in that dump?

With that info, it's really hard to say anything.

Divyanshu

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Divyanshu

The more detailed error as below ::

Runtime Errors RAISE_EXCEPTION

Date and Time 23.07.2014 17:07:53

Short text

Exception condition "INTERNAL_ERROR" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

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

A RAISE statement in the program "SAPLSCSM_DATA_SUPPLIER" raised the exception

condition "INTERNAL_ERROR".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

How to correct the error

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:

"RAISE_EXCEPTION" " "

"SAPLSCSM_DATA_SUPPLIER" or "SCSM_GEN_TAB"

"SETTABLE"

"SAPLSCSM_DATA_SUPPLIER" "INTERNAL_ERROR"

"SAPMSSY8 " "INTERNAL_ERROR"

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.

User and Transaction

Client.............. 000

User................ "SAPSYS"

Language key........ "E"

Transaction......... " "

Transactions ID..... "53CF553C420C4FF0E10000008361B2F6"

Program............. "SAPLSCSM_DATA_SUPPLIER"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

Termination occurred in the ABAP program "SAPLSCSM_DATA_SUPPLIER" - in

"SETTABLE".

The main program was "SAPMSSY8 ".

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

of the (Include) program "SCSM_GEN_TAB".

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

Job Name....... " "

Job Initiator.. " "

Job Number..... " "

Regards

Ram

Ask a Question

Top Q&A Solution Author

User

Count