Skip to Content
0
Former Member
Mar 26, 2009 at 03:52 AM

Reg:ABAP dump:TYPELOAD_NEW_VERSION

1576 Views

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