cancel
Showing results for 
Search instead for 
Did you mean: 

SPAM Problem....

Former Member
0 Kudos

Hi,

I am applying SAP_BASIS Support pack 10 in my NW04s system. Unfortunately at import phase due to power failure my serever wents down.

After that I up the server & restart applying the SP10 using SAPM. It runs for long time & hangs at MOVE NAMETAB.

I check at OS level only TP.EXE is running & no R3TRANS.EXE. I checked the log & found

START imp all BWT 20080813185631 ADMIN BWTRAINING 20080813185631

INFO: event SAP_IMPORT_START triggered successfully

INFO TBATG CONVERSION OF BWT N not needed ADMIN BWTRAINING 20080813185631

START tp_getprots BWT P 20080813185631 ADMIN BWTRAINING 20080813185631

WARNING: System BWT. Warning. 20080813185713 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System BWT. Warning. 20080813190121 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System BWT. Warning. 20080813190213 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

WARNING: System BWT. Warning. 20080813190713 :

WARNING: Background job RDDIMPDP could not be started or terminated abnormally.

Please check that the R/3 system is running.

Please check the system. Use transactions SM21, SM37, SM50.

WARNING: (This warning is harmless if no further warnings follow.)

I restarted the SPAM again but the problem is same only TP.EXE is running.

It shows that RDDIMPDP is terminated.

Please suggest

Thanks,

Shambo

Edited by: Shambo on Aug 13, 2008 3:40 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Shambo,

Please check whether you could access transaction 'STMS' and see if you find the support packages in the import queue, if yes, I would request you to please import it from there, by selecting the support package > request>Import, I think it should resolve your problem

If it doesn't work, then you goto SE38 and schedule the background job 'RDDIMPDP' using program 'RDDNEWPP' as your log shows there was an issue with the background job.

Hope it helps.

Thanks,

Naga

Former Member
0 Kudos

Hi

I tried this also. But stil receiving the DUMPS while running the report through SE38.

I tried to restart the import using STMS that time also this is giving the dump.

Now I restart the import using SPAM but it hangs in IMP ALL step & only TP.exe is running. In logs the error is same.

Please suggest.

Thanks & Regards,

Shambo

Former Member
0 Kudos

Do you have a contingency plan in place and at your fingertips right now?

You may have to restore the DB to a point in time prior to the SP install and start the process over.

This is one reason it is recommended to not do productive work in the system while performing SP updates.

markus_doehr2
Active Contributor
0 Kudos

There are possibilities of "resurrecting" the system.

If it's a time critical thing I suggest you open an OSS call (BC-UPG-OCS) and explain what happened. There is a possibility to start the import "manually" from command line, however, this should be checked by the support people which state which part of the package is already implemented.

If the system is not so critical and you have a backup step backwards to the state before the update.

Markus

markus_doehr2
Active Contributor
0 Kudos

- Logon to client 000

- start transaction SE38 and execute program "RDDNEWPP"

- start transaction SE37

- select all jobs that are active

- use the menu to "Job - check status"

Markus

Former Member
0 Kudos

Hi Markus,

I am reciving below dump.after running the RDDNEWPP program in SE38

Short text

Syntax error in program "SAPICP__ ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPICP__ " in include "ICPFORMS

" in

line 2656:

"The type "BSKEYWORD" is unknown."

" "

" "

" "

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 SAPICP__ :

"The type "BSKEYWORD" is unknown."

" "

" "

" "