BIG problem apply Supprt Pack in Solution Manager 4.0

[Former Member]

I was applying BASIS 700 SP9 with all the pre-requisite in Solution Manager 4.0. The process seems hang, no process can be seen in SM66. Therefore I terminated it and the next moment I know, i can't go to any txn, including SPAM(after exiting the screen). The txn just throw short dumps. This is very sad~~~ Luckily it is a sandbox.

Can anyone advise if it is possible to reverse? Or do I have to perform a reinstall of Solution Manager? What is the next step?

Thanks in advance

[raguraman_c · Accepted solution]

Hi,

Provide the short dump details. How come we know the error if you have not provided?

Did you take any offline backup? May be you can restore it.

Feel free to revert back.

--Ragu

[Former Member · Accepted solution]

Ok, here is the dump when I execute ST22. Different dumps messages for different txns, however, the point that it stops seems to be happening at "CALL FUNCTION" or "CALL METHOD" statement.

Runtime Errors SYNTAX_ERROR

Date and Time 17.05.2007 18:01:27

Short text

Syntax error in program "SAPLSCP2 ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSCP2 " in include "LSCP2U09

" in

line 66:

"The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"

" the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"

"S"."

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SAP "

Error analysis

The following syntax error was found in the program SAPLSCP2 :

"The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field with"

" the similar name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"

"S"."

Trigger Location of Runtime Error

Program SAPLOLEA

Include LOLEAU13

Row 71

Module type (FUNCTION)

Module Name AC_CALL_METHOD

Source Code Extract

Line SourceCde

41 DATA AC_GLOBAL_FLUSH_MODE TYPE C.

42 DATA MAXLINES TYPE I.

43 DATA URL(255) TYPE C.

44 DATA LEN TYPE I.

45 DATA FLDTYPE TYPE C.

46 DATA DOLPARAM TYPE C.

47 DATA NCOMPS TYPE I.

48 DATA I TYPE I.

49 DATA N(2) TYPE N.

50 DATA SIZE TYPE I.

51 DATA SVARS_WA LIKE svars_record.

52

53 FIELD-SYMBOLS: <F>, <AC_X1> TYPE X, <AC_X2> TYPE X,

54 <EXPORTS_WA> TYPE OLE2_METH_PARMS.

55

56 For the call to CL_ABAP_CHAR_UTILITIES=>charsize......................

57 CLASS CL_ABAP_CHAR_UTILITIES DEFINITION LOAD .

58 " "

59

60 * Initialisation

61 CLEAR: EXPORTSINDEX, PARAMS, MESSAGE_NR, MESSAGE_TEXT.

62

63 * check and set the AC_FRONTEND_RUNS_IN_UTF8 parameter.

64 * if the AC_FRONTEND_RUNS_IN_UTF8 parameter is set, multiply the strin

65 * to avoid parameters being truncated in the frontend.

66 IF AC_FRONTEND_RUNS_IN_UTF8 <> ABAP_TRUE.

67

68 DATA : gui_uses_utf8 TYPE rststype-sel_ok.

69

70 " ask Matthias whether SAPGUI uses the length critical codepage UT

>>>> CALL FUNCTION 'SCP_GUI_USES_UTF8'

72 IMPORTING

73 gui_uses_utf8 = gui_uses_utf8.

74

75 IF gui_uses_utf8 IS NOT INITIAL.

76 AC_IS_FRONTEND_UTF8 = abap_true.

77 ENDIF.

78

79 AC_FRONTEND_RUNS_IN_UTF8 = abap_true. "set to true to avoid multi

80 ENDIF.

81

82

83 * If there are entries in IMPORTS set the RETURN_VALUES_EXIST for

84 * smart flushing. So if RETURN_VALUES_EXIST = ' ' a flush can be

85 * postponed in AC_FLUSH_CALL

86 IF NOT IMPORTS[] IS INITIAL.

87 RETURN_VALUES_EXIST = 'X'.

88 ENDIF.

89

90 * determine size of exports table

[raguraman_c · Accepted solution]

Hi,

Is your system is unicode system? You said errors happening in different programs, is ita all related to languages? try to restore from backup otherwise, raise an OSS message.

Please post any further findings, improvements, you may get idea from others.

Feel free to revert back.

--Ragu

[Former Member · Accepted solution]

No, our system is not on unicode. It recovered itself today, not too sure what cures it. I rerun the import and looking at the action log now. It is really kind of stuck.

START MAIN IMPORT SOL I 20070518101742 ANNK PGAPCSM01 20070518101728

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (10), I'm waiting 4 sec (20070518101810). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (20), I'm waiting 1 sec (20070518101834). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (30), I'm waiting 4 sec (20070518101858). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (40), I'm waiting 2 sec (20070518101930). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (50), I'm waiting 2 sec (20070518102005). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (60), I'm waiting 1 sec (20070518102041). My name: pid 8140

WARNING:
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL is already in use (70), I'm waiting 4 sec (20070518102103). My name: pid 8140

[raguraman_c · Accepted solution]

Hi,

Don't stop transaction. Keep patience. Check your virtual memory. Is it to recommended size? Check your master guide. Once you are done with SP. Try to investigate. I guess the time it takes might be because of virtual memory problem.

Feel free to revert back.

--Ragu

[Former Member · Accepted solution]

Thank Ragu. This is a sandbox Solution Manager 4.0 so sizing might be an issue. I will give it more time. Apparantly, I managed to solve a "stuck" stage that is caused by unknown data type BADI_NUMBER_GET_NEXT in Program SAPLSNR3. This can be solved by activating Enhancement Sport: BADI_NUMBER_GET_NEXT in txn SE18. Info can be found in OSS note 980194.

More to fix.....

[yuezhi_zhao · Accepted solution]

Hello Annie,

Please do not just wait. The hanging problem is becuase there's one 'lock file' existing and TP is thinking there's another TP running for SAPKW70009.

The solution is very simple. Please rename or remove the file
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL to somthing else. The TP will go on and the lock file will be created again.

Regards,

Joe

[Former Member · Accepted solution]

Hi, I am back on this case. I restarted the Solution Manager server and perform Queue IMPORT again. Yuezhi, you are right, there is a SOL file in the /usr/sap/trans/tmp directory. However, I am unable to delete it at this moment. Looks like the process is hang and keeps retrying.

1 ED0314 DD: Execution of Database Operations

1 ED0314

1 ED0302 =========================================================================

1 ED0327 Process..................: "PGAPCSM01_8"

1 ED0303 User.....................: "DDIC"

1 ED0305 Date, time...............: "08.06.2007", "16:21:22"

1 ED0307 Platform.................: "CUSTOMER"-"SOL"("700")/"ORACLE/WindowsNT/PGAPCSM01"

1 ED0311 Tool.....................: "BATCH"/"RADBAT01"

1 ED0315 Log......................: "F", "
pgapcsm01\sapmnt\trans\tmp\N070518.SOL"

1 ED0314

1 ED0316 Program parameters:

1 ED0314 Process cat..............: sequential

1 ED0302 =========================================================================

1 ED0320XStart phase "001" **********************************************************

1 ED0306 "Preprocessing of TBATG"

1 ED0301 *************************************************************************

1 ED0301X*************************************************************************

1 ED0306 "Preprocessing of TBATG"

1 ED0322 End phase "001" ***********************************************************

1AETR012XProgram terminated (job: "RDDGEN0L", no.: "16212201")

1 ED0317XProgram start============================================================

1 ED0314

1 ED0314 DD: Execution of Database Operations

1 ED0314

1 ED0302 =========================================================================

1 ED0327 Process..................: "PGAPCSM01_8"

1 ED0303 User.....................: "DDIC"

1 ED0305 Date, time...............: "08.06.2007", "16:31:55"

1 ED0307 Platform.................: "CUSTOMER"-"SOL"("700")/"ORACLE/WindowsNT/PGAPCSM01"

1 ED0311 Tool.....................: "BATCH"/"RADBAT01"

1 ED0315 Log......................: "F", "
pgapcsm01\sapmnt\trans\tmp\N070518.SOL"

1 ED0314

1 ED0316 Program parameters:

1 ED0314 Process cat..............: sequential

1 ED0302 =========================================================================

1 ED0320XStart phase "001" **********************************************************

1 ED0306 "Preprocessing of TBATG"

1 ED0301 *************************************************************************

1 ED0301X*************************************************************************

1 ED0306 "Preprocessing of TBATG"

1 ED0322 End phase "001" ***********************************************************

[Former Member · Accepted solution]

ST22 Dump

Runtime Errors RAISE_EXCEPTION

Date and Time 08.06.2007 16:31:24

Short text

Exception condition "DESTINATION_NOT_OPEN" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

A RAISE statement in the program "SAPLCRFC" raised the exception

condition "DESTINATION_NOT_OPEN".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

Specified destination is not open.

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"RAISE_EXCEPTION" " "

"SAPLCRFC" or "LCRFCU20"

"RFC_CONNECTION_CLOSE"

or

"SAPLCRFC" "DESTINATION_NOT_OPEN"

or

"RADBAT01 " "DESTINATION_NOT_OPEN"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

[Former Member · Accepted solution]

Delete the log file
pgapcsm01\sapmnt\trans\tmp\SAPKKW70009.SOL and start, it works

[Former Member · Accepted solution]

Delete the logs in tmp folder, and start again. It works fine.

[Former Member]

Hi all.

My experience related with this issue is that RDDGEN0L job begin cancel systematically meanwhile I was updating SPAM.

The log of RDDGEN0L refers to a file like this /usr/sap/trans/tmp/N

The solution is to delete such file and execute RDDNEWPP from client 000 with user DDIC.

Both times I've suffered this problem there were running transports (STMS) meanwhile I was updating SPAM.

Regards.

Enrique José Marcos

[Former Member]

Hello,

We have the same Pb. Did you find any solution ?

Thank you.

[Former Member]

Pascal,

I am in Perform Adjustment stage now, my IMPORT phase is completed. It took about 72000 sec to complete. My solution:

1. Stop the current import phase as it could be hang due to low value in rdisp/max_wprun_time

2. Set rdisp/max_wprun_time=14400 in Instance Profile thru RZ10

3. Restart your SAP Solution Manager server to clear the locks and outstanding processes

4. In SPAM, perform the import again

DESTINATION_NOT_OPEN is not the actual problem, the TIME_OUT is the problem. You can read the report name from TIME_OUT dump that stop the whole process as it requires more than 600 sec(default) to run online.

All the best~

[Former Member]

Hi Annie,

But my problem is like the first one , after installing SP09 on Solution Manager 4.0, I could not start any transaction and I have short dump with the following extract :

"Short text

Syntax error in program "SAPLSCP2 ".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLOLEA" had to be terminated because it

has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSCP2 " in

include "LSCP2U09

" in

line 66:

"The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field

with"

" the similar

name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"

"S"."

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SAP "

Error analysis

The following syntax error was found in the program SAPLSCP2 :

"The field "ZCSA_SYSTEM_LANGUAGE" is unknown, but there is a field

with"

" the similar

name "ZCSA_INSTALLED_LANGUAGES". "ZCSA_INSTALLED_LANGUAGE"

"S"."

" "

Trigger Location of Runtime Error

Program SAPLOLEA

Include LOLEAU13

Row 71

Module type (FUNCTION)

Module Name AC_CALL_METHOD

Source Code Extract"

We could not do any thing on the system.

[Former Member]

Pascal,

My solution manager recovered itself the next day so I suspect it is the night DDIC batch jobs that recovered it. I am not too sure which one, these two are the ones that I think it could be after backtracking the jobs:

1. RDDIMPDP

Job Start After Event SAP_TRIGGER_RDDIMPDP

Event periodic

Find SAP_TRIGGER_RDDIMPDP in this document, it displays how to trigger SAP_TRIGGER_RDDIMPDP (I didn't use this so pls try at your own risk)

http://searchsap.techtarget.com/searchSAP/downloads/chapter-march_searchSAP.pdf

2. RDDMNTAB

Hope this helps.