Severe error(s) occurred in phase MAIN_INIT/RUN_RSPTBFIL_INIT!

[Former Member]

Hello All,

I am applying EHP3 for CRM system, CRM system is install on cluster server.

During  Preprocessing Phase SUM had stop with:

Severe error(s) occurred in phase MAIN_INIT/RUN_RSPTBFIL_INIT!,

Last error code set: Batchjob 'RSPTBFIL' with id '12405200' aborted

I can see the shaow instance is not becuse of disp+work was stop.

I had added disp+work file ,

I hope some body has tried this issue,

Thanks

Reza

Dev_disp_qc1.txt.zip

[Reagan · Accepted solution]

It appears to me there was an attempt to upgrade the system prior to this execution and you tried to reset the upgrade which was not done correctly. This has caused an inconsistency in the system. Have you checked the log file RSPTBINI.QC1? This could be the reason why the job RSPTBFIL is failing in the main system. You should review ALL the RSPTBINI log files available at S:\SUM\abap\log before you decide to reset the upgrade and start over again, else there is a strong possibility that you will end up in the same situation again.

Reagan

[divyanshu_srivastava3 · Accepted solution]

I do agree..

Regards,

[Former Member · Accepted solution]

Hello Reagan,

Thanks Again for reply,

I had tried to reset the upgrade, but as you told, I am in the same situation, the bach job stop.

I have this to file  RSPTBINI file, I hope There is a sloution for this batch job issue.

Thanks

Reza

RSPTBINI.txt.zip

RSPTBINI-qc1.txt.zip

RSPTBINI_PH-.txt.zip

[hemanth2 · Accepted solution]

Hi Reza,

The error is:
"

2 ETQ373 parameter "JOBENDTIME" = "191244"

2EETQ262 Batchjob "RSPTBFIL" aborted

1EETQ399 Last error code set is: Batchjob 'RSPTBFIL' with id '19124200' aborted

1EETQ204 Upgrade phase "RUN_RSPTBFIL_INIT" aborted with severe errors ("20141119191312")

"
and the R/3 dump:
"

The current ABAP   program "SDB2FMSS" had to be terminated because it has

come across a   statement that unfortunately cannot be executed.

The following syntax   error occurred in program "SAPLSDSB " in include "LSDSBU04

" in

line 149:

"Type   "TY_T_DDXTT" is unknown"   " Have you already done a yntax check on the program. Can you try a quick workaround: Try to repair the function group SDB2 with the option SE37 -> Utilities -> Repair Func groups ? Let me know how this goes. Regards, Hemanth

[Former Member · Accepted solution]

Hello,.

Thanks Again for help,

This is Test system and I can not made this repar.

I think my problem is i had added spdd and spau. transport during upgrade and from SPAU we had some note that was apply in test system by sum. and now we have this problem

Thanks

Again

Reza

[hemanth2 · Accepted solution]

Reza, I am just wondering whether it would be possible to trigger a transportof the program  from a QA or dev server to the affected server and then check. What do you think?

Regards,
Hemanth

[hemanth2]

Before the restart of the SUM, it would be a good idea to execute the 'cleanipc <nr> remove' with the root user to ensure that none of the SHM segments are present.

Regards,
Hemanth

[Former Member]

Hi Heranth.

I have execute the 'cleanipc 02 remove' for central instance and restat server, but still the same

disp+work not start.

Thanks

Reza

Dev_disp_qc1.txt.zip

[hemanth2]

Hi reza,

The new issue is:
"

Wed Nov 19 15:49:11 2014

*** ERROR => DpHdlDeadWp: W0 (pid 7460) died (severity=0, status=0) [dpxxwp.c     1325]

DpWpRecoverMutex: recover resources of W0 (pid = 7460)

"

Are you sure you have applied the latest kernel? This is the same issue as note 1966321 - ABAP application server instance hangs due to mutex deadlocks and  the one described in SAP Note # 1964562.

Please update your kernel to the patch level precised in the note and also set the parameter 'em/use_sema_lock = TRUE'.

# 1964562 - Avoiding deadlock in signal handling on Windows

Can you let me know the complete kernel version?

Regards,
Hemanth

[Reagan]

The new trace is not showing the same error again. Are you able to see the dev_w0 trace file?

If not then what other trace files are available in the shadow instance work directory?

[Former Member]

Hi

Sorry for this, I can see the shadow instance it shold not start now,

The problem is the bach job in central instance get canceled.

Job started

Step 001 started (program RSPTBFIL, variant SAP_INIT, user ID DDIC)

Internal session terminated with a runtime error SYNTAX_ERROR (see ST22)

Job cancelled

  Error in the ABAP Application Program

  The current ABAP program "SDB2FMSS" had to be terminated because it has
  come across a statement that unfortunately cannot be executed.

  The following syntax error occurred in program "SAPLSDSB " in include "LSDSBU04
   " in
  line 149:
  "Type "TY_T_DDXTT" is unknown"
  " "

Thanks

Reza

[hemanth2]

Hi Reza,

Has the server started, I am not able to make out by this reply

:
"

Sorry for this, I can see the shadow instance it shold not start now,

"

The other issue is just a /nST22 dump, I do not think it is that critical..

Regards,
Hemanth

[Former Member]

I can see the problem is the Batchjob 'RSPTBFIL' incentral instance was canceled,

with:

The following syntax error occurred in program "SAPLSDSB " in include "LSDSBU04

   " in

  line 149:

  "Type "TY_T_DDXTT" is unknown"

And I am not sure the shadow should start at the :

phase MAIN_INIT/RUN_RSPTBFIL_INIT

Thanks

Reza

[Former Member]

The Central instance is startet but not the shoadow,

Should shadow was startet in this Phase?

Thanks for help.

Reza

[hemanth2]

HI Reza,

I will need to check this further as to whether the shadow server should start at MAIN_INIT/RUN_RSPTBFIL_INIT . I will give an update asap.

Regards,
Hemanth

[Former Member]

Hi Hemanth.

Thanks  for help.

Reza

[hemanth2]

Hi Reza,

It looks like in the phase MAIN_INIT/RUN_RSPTBFIL_INIT, the table consistency is checked. Did the SUM tool try to start the Shadow instance on its own in this phase?

Regards,
Hemanth

[former_member182657]

Hi Reza,

From log file RSPTBINI-qc1 issue seems with the entry

Table in file but not in PUTTB:" "DDLDEPENDENCY"

Shows inconsistencies with the upgrade.

Regards,

Gaurav

[Former Member]

Hello,

My problem is we had outo transport runing on this system. an Spau transport was transportet to Test server,

I find manye error and syntax error in this system.

Sloution is a new restart.

Thanks for alle helps

Reza

[former_member189797]

I had worked on a similar issue in the past. it was the same reason in that case also.
"Always advised to turn off auto transport during the period of landscape systems upgrade."

These were the steps which had helped me to determine the cause in past case :
-----------------------------------------------------------------------------------------------------------------------

Perform a syntax check on the program and see where it is using the
type TY_T_DDXTT . If you double click in it it should show that it does not exist. So somewhere this is being used but not defined. If you have a similar system, check the same program where TY_T_DDXTT is being used. double click on it and it will open the program where this is defined. Check the version management of

program where this is defined on both system. you should be able to determine how program was changed and take a decision.

------------------------------------------------------------------------------------------------------------------------

when the version management was checked it showed the SPAU request .

Best Regards,
Gaurav Pandey

[hemanth2]

Great news Reza.

I think it would be a good idea to do a DB consistency check once as well, see
SAP Note No. 23345- Consistency check of ORACLE database (and preferably an update DB statistics).

regards,
Hemanth

[Former Member]

Yes I know this now:(

[Former Member]

Thanks

I will do that too

Thanks

Reza

[former_member182657]

Hi Reza,

Now at this stage best would be to open a support ticket with SAP in parallel or last is to opt reset of upgrade.

Regards,

Gaurav

[divyanshu_srivastava3]

Hi Reza,

After taking restart of windows, can you share the latest logs ?

Regards,

[divyanshu_srivastava3]

esp, job logs for "Batchjob 'RSPTBFIL' with id '12405200'" with dev_w0.

[Former Member]

Hello,

I had add dev_w0 -

Thanks Again for help.

Reza

dev_w0.txt.zip

[Former Member]

Hello All,

I tried to reset this SUM and start Again. But reset stop with.

Severe error(s) occurred in phase REV_PREPROC/RUN_RSUPGREV_SHDT!

Last error code set: Batchjob 'RSUPGREV' with id '19252500' aborted

The same problem the job get canceled.

APup broke during phase RUN_RSUPGREV_SHDT in module REV_PREPROC / Reverts the preprocessing module(s) and resets the procedure

Error Message: Batchjob 'RSUPGREV' with id '19252500' aborted

How this can happend?

Thanks for any reply

Reza

sapup.txt.zip

[divyanshu_srivastava3]

Where are the job logs ?

[Former Member]

Hello,

Thanks Again for reply.

The same error:

Error in the ABAP Application Program

The current ABAP program "SDB2FMSS" had to be terminated because it has
come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSDSB " in include "LSD
" in
line 149:
"Type "TY_T_DDXTT" is unknown"
" "
" "
" "

The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program

The current ABAP program "SDB2FMSS" had to be terminated because it has

Thanks again

ST22_qc1.zip.txt.zip

[Sriram2009]

Hi

Could you refer the SAP Note for Dump

1809597 - Syntax error in SAPLSDSB or SAPLSDB2

BR

SS

[Former Member]

Hi,

Thanks for reply.

In transaction ST22, short dumps occur with the error " is

"TY_T_DDXTT" is unknown"

and not from note.

'TY_S_OPER_STRUC'

Du you know it is defferent?

Thanks

Reza

[Sriram2009]

Hi

On the same SAP Note have you check the Symptom 2 ? 1809597

BR

SS

[former_member189797]

Perform a syntax check on the program and see where it is using the
type TY_T_DDXTT . If you double click in it it should show that it does not exist. So somewhere this is being used but not defined. If you have a similar system, check the same program where TY_T_DDXTT is being used. double click on it and it will open the program where this is defined. Check the version management of

program where this is defined on both system. you should be able to determine how program was changed and take a decision.

[former_member182657]

Hi Reza,

Could you please share RSPTBFIL.ELG log file as well.

Regards,

Gaurav

[Former Member]

Hi Gaurav,

There is no RSPTBFIL.ELG log file in

S:\usr\sap\QC1\DVEBMGS02\Work

or

S:\SUM\abap\log

Thanks

Reza

[former_member182657]

Hi Reza,

Could you check with S:\usr\sap\<SID>\SUM\abap\log

Regards,

Gaurav

[Former Member]

Sorrry there is not this file there.

But there are some file : RSPTBINI.

I had add one of them.

RSPTBINI_PH.txt.zip

[former_member182657]

Kindly share these logs to us file would be RSPTBINI.LOG

Regards,

Gaurav

[hemanth2]

Hi Reza,

It looks like the Dump was triggered cause:
"

The termination was   triggered in function "ab_genprog"

of the SAP kernel, in   line 1862 of the module

"//bas/721_REL/src/krn/runt/abgen.c#5".

The internal operation   just processed is "FUNC".

Internal mode was   started at 20141119095741.

Program name.........:   "SAPLSDSB ".

Error message........: "Type   "TY_T_DDXTT" is unknown".

"

Is the stack consistent? This looks like an issue that can occur if an activity like SPAM was not done correctly. Can you please check this?

Regards,

[Former Member]

Hello,

Yes the SPAM was done correctly and is green.

Thanks

[former_member182657]

Hi,

Please share the complete dump from ST22.

Regards,

Gauarv

[Former Member]

Hi,

Here is a st22 dump file.

Thanks

reza

ST22_qc1.zip.txt.zip

[former_member182657]

Hi Reza,

Not able to open the attached log file,could you please re attach as a txt.

Regards,

Gaurav

[Former Member]

Hi Gaurav,

This is a zip file, I had just add .txt for add the zip file  to massage,

Just remove .txt and you can open the zip file

Thanks

Reza

[hemanth2]

Hi Reza,

The startup error is:
"

*** Error 11 while initializing OS dependent part.

*** ERROR => DpEmInit: EmInit failed (1) [dpInit.c     1513]

*** ERROR => DpMemInit: DpEmInit (-1) [dpInit.c     1377]

*** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit

*** DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs
"

Previously we have seen such issues on AIX due to old kernel versions. Please check 1889466 - Memory Management errors on AIX in 7.40 kernel and use lastest patch for kernel.

The below links will help you if there are any queries with the kernel update procedure:

SAP Note No. 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

SAP Note No. 1629598 - SAP Kernel 720 will replace older kernel versions

SAP Note No. 19466 - Downloading SAP kernel patches

Also check:

http://scn.sap.com/docs/DOC-1206

(for Manual Kernel Upgrade)

and

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11219

(for kernel upgrade using JSPM)

____________
Kind Regards,
Hemanth
SAP AGS

[Former Member]

Hi Hemanth,

The Kernel for shadow system is a leatest from Solution manager MOPS. Should I chage the kernel is SUM?

Thanks again

Reza

[Reagan]

*** ERROR => <EsNT> CreateFileMapping name=Global\ES_SEG_03_003 ,size=2044 MB, error=1455 [esnti.c      1278]

Follow this SAP KBA

1997262 - The shadow instance won't start up. System dev_w* trace files highlight error message 1455...

If possible supply the dev_w0 trace file.

Reagan

[Former Member]

Thanks for reply,

There is no dev_w0 trace file. on:

S:\SUM\abap\system\QC1\DVEBMGS03\Work

Thanks Reza

[hemanth2]

Hi Reza,

Great. The latest kernel files should be in:

"../usr/sap/SUM/SUM/abap/<SID>/DVEBMGS<nr>/exe"

and

/usr/sap/SUM/SUM/abap/exe

"

Also add following parameters to the shadow instance profile:

"

ES/SHM_MAX_PRIV_SEGS  = 12

ES/SHM_MAX_SHARED_SEGS = 3

abap/shared_object_size_MB = 20

"

Kind Regards,

Hemanth

[Reagan]

Hello Hemanth,

Are you sure these parameters are valid for the kernel based on Windows? Also cleanipc is not applicable on Windows systems. To clean the shared memory segments on a Windows system you need to restart Windows.

Reagan

[hemanth2]

Sorry I did not read the OS part. Thanks Reagan.
Yes Reza, please do a OS restart the next time you plan on launching SUM. Please hold on the parameter change till then; check the kernel part first.

[Former Member]

Hi Reagan,

I did tried to add PHYS_MEMSIZE = 50% in parameter to the shadow instance profile.

Restart SAP and server. But still the same.

Thanks again