SPAM/SAINT update error

[#1]

Hi Everyone,

While updating SPAM from Version 7.02/0037 to Version 7.02/0045 I am getting following runtime error.

Help me in resolving CALL_FUNCTION_PARM_UNKNOWN runtime error.

[gururaj_srinivasa]

Hi Rajashree,

Normally such error occours during SPAM/SAINT upgrade, exit the transaction and rerun SPAM, that should work. If that does not resolve, check and upgrade kernel to latest patch.

Hope this helps.

Guru

[Former Member]

I assume you are running unix flavor system,

first trace if any error happened in import process, since you cannot open spam then go to OS level

/usr/sap/trans/tmp and /usr/sap/trans/log

find latest modified file there( during your import session).

check for error or clues there.

/$sync --> this command is to flush buffer

you can do it in another way.

open SE38

display this program SAPMSPAM

press ctrl + F2 or check button

if check passed successfully

then press activate or ctrl + F3

if it run successfully then

run SPAM T-code again in new session.

If you meet any error during above steps please paste your error here.

raise OSS if you need urgent resolution.

[Former Member]

Dear Rajashree,

Please check the version of tp and r3trans and also kernal of your system. Please update both of them to the latest available at market place.

Regards,

Sachin

[Former Member]

Please restart SPAM/SAINT.

[former_member509286]

When ever I am using SPAM/SAINT transaction getting the same error as mentioned above.

How to restart SPAM/SAINT.

[Former Member]

try tcode "/$sync" first and then run SPAM.

[Former Member]

HI,

Update TP and R3trans

Restart SPAM  and again import SPAM/SAINT update

Let me know your results

Sid

[Former Member]

Simply run SPAM update again. For more info see Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP

"

1. SPAM/SAINT updates

• Symptom: When you import the SPAM/SAINT update, a range of different runtime errors may occur:
  • LOAD_PROGRAM_LOST
  • LOAD_PROGRAM_CLASS_MISMATCH
  • LOAD_TEXTPOOL_LOST
  • SAPSQL_SELECT_WA_TOO_SMALL
  • SAPSQL_SELECT_TAB_TOO_SMALL
  • SAPSQL_WA_TOO_SMALL
  • DDIC_STRUCLENG_INCONSISTENT
  • RUNT_ILLEGAL_SWITCH
  • CALL_FUNCTION_PARM_UNKNOWN

           These errors occur because the source code of the Support Package Manager is modified by the import during the run. CALL_FUNCTION_PARM_UNKNOWN, LOAD_PROGRAM_LOST, LOAD_PROGRAM_CLASS_MISMATCH, and LOAD_TEXTPOOL_LOST occur if the ABAP load or text elements are to be loaded back into the local buffer, and there is a different version in the database.
However, SAPSQL_SELECT_WA_TOO_SMALL, SAPSQL_SELECT_TAB_TOO_SMALL, SAPSQL_WA_TOO_SMALL, DDIC_STRUCLENG_INCONSISTENT and RUNT_ILLEGAL_SWITCH occur if changes are made on the SPAM/SAINT data structures with the SPAM/SAINT update.

Solution: None of these errors will occur again if you restart the Support Package Manager (transaction SPAM) and continue to import the SPAM/SAINT update.

"

Regards

Roman

[former_member509286]

I tried restarting SPAM after trying "/$sync".

But still I am getting same error.