Reg:ABAP dump:TYPELOAD_NEW_VERSION

[Former Member]

Hi All,

We are getting the dumps(150),TYPELOAD_NEW_VERSION with only one particular user in one of our production servers,there are a few background jobs scheduled with the same user and all the jobs have got finished successfully.

below pasted is the detailed dump message

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

Data type "MC11VA0ITM" was found in a newer version than required.

What happened?

Runtime error

The current ABAP program, "SAPLMCEX", had to be terminated because one of the

statements could not be executed at runtime.

What can you do?

Try restarting the program.

If the error occurrs several times, consult your SAP administrator.

Choose "Print" to obtain a hard copy of the termination message.

You can use Transaction ST22 to display and manage short dump messages.

It also allows you to retain them beyond their normal deletion date.

Error analysis

The data type "MC11VA0ITM" was reloaded from the database while the program

was running.

However, the system found a version of the type that was newer than

the one required.

How to correct the error

Try to restart the program.

System environment

SAP Release.............. "620"

Application server....... "provpr08"

Network address.......... "10.130.33.98"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00C6C8D04C00"

Character length......... 16 Bits

Pointer length........... 64 Bits

Work process number...... 0

Short dump setting....... "full"

Database server.......... "provpr01"

Database type............ "ORACLE"

Database name............ "VPR"

Database owner........... "SAPERP"

Character set............ "C"

SAP kernel............... "640"

Created on............... "Aug 17 2008 21:27:08"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "247"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

User, transaction...

Client.............. 810

User................ "ADMINJOBS"

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

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

Program............. "SAPLMCEX"

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

Row of screen....... 6

Information about program making the Remote Function Call (RFC):

System.............. "VPR"

Database Release.... 620

Kernel Release...... 640

Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)

Call type: "synchron (imode 1)" (S = Synchronous, a/A = Asynchronous, T =

Transaction)

Client.............. 810

User................ "ADMINJOBS"

Transaction......... " (Program: SAPLV50R_VIEW)"

Function module..... "SHP_VL10_DELIVERY_CREATE_PARA"

Call destination.... "provpr08_VPR_01"

Source server....... "provpr05_VPR_01"

Source IP address... "10.130.33.108"

Additional RFC logon information:

Trusted Relation....." "

Logon return code....0

Trusted return code..0

Note: Prior to Release 4.0, there was less information available on RFC

calling programs.

Information on where terminated

The termination occurred in the ABAP program "SAPLMCEX" in "MCEX_11_QRFC".

The main program was "SAPMSSY4 ".

The termination occurred in line 0 of the source code of the (Include)

program " "

of the source code of program " " (when calling the editor 00).

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

We are on 640 Kernel-AIX ,level-247

I have no clue on how to go about,

can some one pls.look into it nad do the needful.

Thanks in advance

Rgds

Venu

[Former Member]

Venu ,I dont understand one thing

when is the dump coming,since all the background jobs have finished successfully,then there is no issue as such

and since the user is system user he is not doing any dialog transactions,so you need not worry

I guess the issue is when the transports were moving,then these dumps were coming as the background jobs for that user were also running but I guess you will not see these dumps coming now

You only need to run the background jobs that were cancelled.

that is why SAP says suggest that you do transports in production system when no one is being done,particularly in the evening time

Just ignore these dumps as these are quite usual

Rohit

[Former Member]

Hi Rohit,

Thanks once again

I believe that my question has been answered appropriately,I appriciate the your help and support.

I take the liberty to put across one more ABAP dump(80 dumps by a single user),"RABAX_CALLING_RABAX:"

The error text is as below

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

Runtime Error RABAX_CALLING_RABAX

Occurred on 03/24/2009 at 07:25:29

Error "14 431" in error handling.

What happened?

A further error occurred when displaying an error message.

What can you do?

You can display the error message using Transaction ST22. If

no further error is logged there, try to find an appropriate

entry in the SAP system log.

-

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

The T100 error code is "14 431".

The error text reads

Invalid output to terminal from background processing

with this key.

-

---

Last error logged in SAP kernel

-

---

Component............ "Taskhandler"

Place................ "SAP-Server provpr03_VPR_01 on host provpr03 (wp 0)"

Version.............. 1

Error code........... 5

Error text........... "ThAMInsert: no active mode"

Description.......... " "

System call.......... " "

Module............... "thxxhead.c"

Line................. 9893

How to correct the error

In general, it is sufficient to determine the original cause of the

error and to eliminate it. Since the display of the runtime error

has failed, you can only analyze the error by looking at the

system log or the short dump display.

System environment

SAP Release.............. "620"

Application server....... "provpr03"

Network address.......... "10.130.33.106"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00C6C9904C00"

Character length......... 16 Bits

Pointer length........... 64 Bits

Work process number...... 2

Short dump setting....... "full"

Database server.......... "provpr01"

Database type............ "ORACLE"

Database name............ "VPR"

Database owner........... "SAPERP"

Character set............ "C"

SAP kernel............... "640"

Created on............... "Aug 17 2008 21:27:08"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "247"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Client.............. 810

User................ "HJAFFER"

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

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

Program............. "SAPLSGUI"

Screen.............. "SAPMS380 0100"

Row of screen....... 3

Information about program making the Remote Function Call (RFC):

System.............. "VPR"

Database Release.... 620

Kernel Release...... 640

Connection type: 3 (2 = R/2, 3 = R/3, E = External, R = Reg.external)

Call type: "synchron (imode 1)" (S = Synchronous, a/A = Asynchronous, T =

Transaction)

Client.............. 810

User................ "HJAFFER"

Transaction......... "ZSA5E (Program: ZVRV_OPEN_ORDERS_ALV)"

Function module..... "ZVRV_OPEN_ORDERS_ALV_PRL"

Call destination.... "provpr03_VPR_00"

Source server....... "provpr03_VPR_01"

Source IP address... "10.130.33.106"

Additional RFC logon information:

Trusted Relation....." "

Logon return code....0

Trusted return code..0

Note: Prior to Release 4.0, there was less information available on RFC

calling programs.

Information on where terminated

The termination occurred in the ABAP program "SAPLSGUI" in

"SAPGUI_PROGRESS_INDICATOR".

The main program was "SAPMS380 ".

The termination occurred in line 33 of the source code of the (Include)

program "LSGUIU01"

of the source code of program "LSGUIU01" (when calling the editor 330).

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

There are so many logs written in SM21 by the same user as mentioned below

HJAFFER AB0 Run-time error "CALL_FUNCTION_SEND_ERROR" occurred

HJAFFER AB1 > Short dump "090324 072401 provpr03 HJAFFER " generated

HJAFFER D01 Transaction Canceled 14 431 ( )

HJAFFER AB0 Run-time error "RABAX_CALLING_RABAX" occurred

detailed Log...

Details Page 1 Line 17 System Log: Central Analysis 1

Time Instance Ty. Nr Cl. User Tcod MNo Text Date : 24.03.09

07:24:01 provpr03_VPR_00 DIA 01 810 HJAFFER D01 Transaction Canceled 14 431 ( )

Details

Recording at local and central time........................ 03/24/2009 07:24:01

Entry in collective system log at local time............... 03/24/2009 07:25:25

Task................ 55318 . 01 D1 Dialog work process No. 01

User................ HJAFFER

Client.............. 810

Terminal............ TXFRIALP

Session............. 1

Transaction code....

Program name........ SAPMS380

Problem class....... K SAP Web AS Problem

Development class... SDYN

Module name.........

Location............

T100................ 14 431

Parameters..........

Documentation for system log message D0 1 :

The transaction has been terminated. This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction. The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message 14 431

Invalid output to terminal from background processing

No documentation exists for message 14431

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

Pls.look into it and guide me thru as you did in the earlier case

Rgds

Venu

[Former Member]

Hi Venu,

It looks a transport as gone into the system which contains data type MC11VA0ITM and the buffer still contains the old object,thats why there is a conflict and this is causing the dump

try the follwoing things:

1. ask the user to start his program again,the work that he was doing and it should finish sucessfully

2. if it doesnt,reimport the transport(ask the functional team what was the transport related to this that has moved in) and then ask user to start again,the problem will get resloled

Let me know of any questions

Rohit

[Former Member]

Hi Rohit,

Thank you very much for the reply.

The user is a system user and he is running a few scheduled BTC jobs.All the jobs have got finished successfully..in this case,do I need to reschedule all the completed BTC jobs,which are being run by the user

I have noticed that there are several transports moved at the time at which the dumps were started thrown

Pls.can you eloborate on the same.

Thanks once again,

Rgds

Venu