Support pack produced syntex error

[Former Member]

Hello,

Facing Systex Error problem during Patch upgrade, i am applying following support packages

SAP_BASIS 7.0 & SAP_ABA 7.0 - 13 TO 18

SAP_BW - 20

BI-CONT 7.3 - 1 TO 10

I have applied support packages upto SP12, i have defined new queue as mentioned above. during the some phase i am getting sytex error in lots of program. kindly check following details which i am facing

I have highlighted some of the program and its attribute, where attribute is same in all program.

Waiting for your response.

Runtime Errors SYNTAX_ERROR

Date and Time 26.06.2009 09:09:42

Short text

Syntax error in program "SAPLBTCH ".

What happened?

Error in the ABAP Application Program

The current ABAP program "????????????????????????????????????????" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLBTCH " in include

"CL_GUI_ALV_GRID===============CU " in

line 127:

"Type "IF_ALV_PRINT_PARAMETER_PROXY" 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 "????????????????????????????????????????" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program SAPLBTCH :

"Type "IF_ALV_PRINT_PARAMETER_PROXY" is unknown"

" "

" "

" "

Runtime Errors SYNTAX_ERROR

Date and Time 26.06.2009 09:06:36

Short text

Syntax error in program "CL_WB_PGEDITOR_INITIAL_SCREEN=CP ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program

"CL_WB_PGEDITOR_INITIAL_SCREEN=CP " in include

"CL_GUI_ALV_GRID===============CU " in

line 127:

"Type "IF_ALV_PRINT_PARAMETER_PROXY" 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 "RSABAPPROGRAM" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program

CL_WB_PGEDITOR_INITIAL_SCREEN=CP :

"Type "IF_ALV_PRINT_PARAMETER_PROXY" is unknown"

" "

" "

" "

Runtime Errors SYNTAX_ERROR

Date and Time 26.06.2009 09:19:51

Short text

Syntax error in program "SAPLSUNI ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSUNI " in include

"CL_GUI_ALV_GRID===============CU " in

line 127:

"Type "IF_ALV_PRINT_PARAMETER_PROXY" 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 "SAPMSPAM" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program SAPLSUNI :

"Type "IF_ALV_PRINT_PARAMETER_PROXY" is unknown"

" "

" "

" "

Trigger Location of Runtime Error

Program SAPMSPAM

Include MSPAMO01

Row 780

Module type (MODULE PBO)

Runtime Errors SYNTAX_ERROR

Date and Time 26.06.2009 09:20:35

Short text

Syntax error in program "SAPLSLVC_FULLSCREEN ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSLVC_FULLSCREEN " in

include "CL_GUI_ALV_GRID===============CU " in

line 127:

"Type "IF_ALV_PRINT_PARAMETER_PROXY" 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 "RSMON000_ALV" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program SAPLSLVC_FULLSCREEN :

"Type "IF_ALV_PRINT_PARAMETER_PROXY" is unknown"

" "

" "

" "

Best Regards,

V.Singh

[Former Member · Accepted solution]

Hi

Prerequesite to apply Support package in Live system

You can check

-->Take full offline backup of your system,

-->Table space available on Database.

--> Your SPAM/SAINT version is updated.

--> Your Kernel patch is updated.

-->Your Buisness Client is locked

-->Workprocess and Memory is available.

-->Space available at OS level

-->Check all prerequisites means spam status patch levels etc.

-->lock all users except the user with which you want to apply(DDIC or equalent).

-->check the tablespaces and os file system sizes.

-->Check the tp version if required apply latest(n-1 kernel).

-->Take ABAPer presence at the time of applying.

-->Deschedule all Batch jobs

Even i have faced the same problem when i was applying patches couldn't log on to system so i was just monitoring the logs and given sufficient time for patches to finish

Regards

Uday

[markus_doehr2 · Accepted solution]

> Even i have faced the same problem when i was applying patches couldn't log on to system so i was just monitoring the logs and given sufficient time for patches to finish

I haven't faced that problem in the last 13 years in Basis administration.

Of course, it's possible, that you can't logon in another client/new mode since programs are actually patched, however, that is expected and is nothing unusual. One would just need to wait some time until all programs are consistent again.

Markus

[Former Member · Accepted solution]

Thanks a lot to all for suggestions.

But is there any otherway to carryfowarwd again patches. Except restore / recovery.

Best Regards,

V.Singh

[former_member302557]

Notes 1281321 and 1465387 helped me to solve.

[former_member302557]

Hi,

I tried these steps of doing through the tp.exe command, but its halfway through. After imported with warnings and restarting hte instances, some tcodes are working now, like SU01/SM51 etc, but SPAM/SAINT are giving the same error.

I tried the activation through tcode SE18, but when I click on activate the programs throw the same error.

Any idea?

Srinivasan K

[Former Member]

Thanks for Update, will be helpful for others who come across this error

Regards

Uday

[Former Member]

Restored the full offline backup, that was the only solution, Thanks for support

[Former Member]

this kind of problem is happening in SP17 of Basis and you can fix it by following notes.

sapnote_0000998004.pdf

sapnote_0001274493.pdf

sapnote_0001288862.pdf

sapnote_0001332780.pdf

Regards,

V.Singh

[Former Member]

Hi

If you are able to login to system and execute the tcode SPAM and continue the patch upgrade then its fine but if you are unable due to SYNTAX_ERROR then there is no other option.

I have a commond through will we can apply support packs but iam not sure SAP recommands to do so

SP can be applied by following cmd from OS level

E:\usr\sap\<SID>\SYS\exe\uc\NTI386>tp import <SAPKB70013> <SID> pf=\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

Regards

Uday

[Former Member]

Hi

Check the SLOG,ULOG and see is any update going on

usr/sap/trans/log

Regards

Uday

[Former Member]

Right now i stopped my system,

so can i check my offline log inside mentioned directory.

Regards,

V,singh

[markus_doehr2]

> so can i check my offline log inside mentioned directory.

that was not a good idea.

If you install support packages you have to stop all production work on the system, means, all users need to be logged off and all batch jobs need to be stopped.

Of course you get syntax errors because parts of the program may be patched and others not.

Since you now stopped the system it's possible that you're even unable to logon because of syntax errors. I hope you have a good backup.

Again: it's normal and expected that you get syntax errors before the update is not complete because you patch a running system.

Markus

[Former Member]

Is there any way or change to restart patching anyway

Best Regards,

V.singh

[Former Member]

Hello markus,

this happend with me second time, before this i faced same sitution in newly installed system, then i did new installation again, you can check my previous same kind of thread.

Thread: Logon failuer after apply support packages, SYNTAX_ERROR in SAPLSDOC

I cannot understand where it is problem,

Its really very strange for me to identify what is the problem and in which support pack has problem?

is other ppls faced this problem or my stars are not good while doing this.

I dont want to reinstall or recover system this time.

Suggestions will be highly appreciable.

Best Regards

V.Singh

[markus_doehr2]

It seems you don't understand how patching works (no offense).

If you install a support package there are various phases (which you might have seen).

A first step install/update the tables/views/structure, a second step imports the code changes and a third step activates those changes.

As long as not all three steps are completed you might face syntax errors. If e. g. step one is in process and a program refers to a table structure that is not consistent with the code (because stage 2 and 3 are not done yet) it will dump. This is a normal and expected.

Support packages installation is (usually) done in downtime (not system shut down but downtime in sense of no one logged on but you with SPAM), that means, you logon to client 000 with one mode, start the patch application and leave the system alone until the patch process is finished. If the patch application takes several hours then you might get syntax errors for those several hours until it's finished.

Markus

[markus_doehr2]

> I have applied support packages upto SP12, i have defined new queue as mentioned above. during the some phase i am getting sytex error in lots of program. kindly check following details which i am facing

Did you stop the batch processes?

It's normal that syntax errors are occuring during the patch application because it takes some time until all programs are consistently updated.

Markus

[Former Member]

Thanks Markus,

I have applied SPs upto 12 seprately, then defined new queue.

I havnt stopped any Batch jobs.

One thing i would like to tell you that i started patch deployment in background instead of dialog mode.

Suddenly i started to get syntex error while running SPAM,SAint,sm32,sm50,se38, etc

Regards,

V.singh