Support pack stuck

[Former Member]

Dear Team,

I am using SAPIDES 6.0 on Windows 2003 with Oracle 10.When I am applying Basis Support pack SAPKB70012 in my SAPIDES .Its Stuck in Queue Import and Clock is running MOVE NAMETABS from last 3 Hours.

Thanks

Moni

[Former Member]

since you are applying basis support pack it will not allow you to run any transaction code since base programs and table and datadic are in inactive state

you need to wait till the step is completed

progress can be checked in log under temp directory in \usr\sap\trans\

as you are applying on IDES you will have number of issue

Samrat

[Former Member]

Hi

You can try deleting the entries from PAT01 and PAT03 from OS level.As samrat said it wont resolve your problem,but you can give a try

>sqlplus "/as sysdba"

>delete from <schema id>.PAT01 where PATCH="SAPKB70012";

>commit;

In the same way delete from PAT03 table also

Let me know if needed more informations

Regards

Uday

[Former Member]

Hi

If possible just try bouncing the system once and execute the T-code again

Hope that should work

Regards

Uday

[Former Member]

Hi,

Check for Archive stuck.

Regards,

Sachin Rane.

[Former Member]

Thanks for your reply, I have check my archive . In this 15 GB free space.

Till now clock is running.

Moni

[Former Member]

Hii Monika,

I guess this is a problem with background jobs not running for the import.

Go to SM37,in the job name put R* and user * and in status put scheduled and released

If you find any jobs with the status I have mentioned,just run them,your import will start and do this in 000 client with ddic user

Rohit

[Former Member]

Dont worry about level -12 it will take long time, meanwhile check the action logs for the same.

Regards

Chandra

Edited by: Chandra B. on Mar 25, 2009 3:47 PM

[Former Member]

Now If I Run any Transastion . It give Abap Dump. and I Have check via ST22 . it show 614 Toady abap dump.

Runtime Errors SYNTAX_ERROR

Date and Time 25.03.2009 16:36:56

Short text

Syntax error in program "SAPLKKBL ".

What happened?

Error in the ABAP Application Program

The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be

terminated because it has

come across a statement that unfortunately cannot be executed.

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

" in

line 621:

"The data object "LS_SORT" does not have a component called "COLCOUNT

" "

" "

" "

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

"The data object "LS_SORT" does not have a component called "COLCOUNT"."

" "

" "

" "

Trigger Location of Runtime Error

Program CL_GUI_ALV_GRID===============CP

Include CL_GUI_ALV_GRID===============CM05M

Row 16

Module type (METHOD)

Module Name PUT_PARAMETERS

Error analysis

The following syntax error was found in the program SAPLKKBL :

"The data object "LS_SORT" does not have a component called "COLCOUNT

" "

" "

" "

[sukhdev_kaloor]

check for any updates in tmp directory. There should be some log file getting updated. check messages in that.

[Former Member]

I have Check in D:\usr\sap\trans\log in this below messege is comming.

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

WARNING: System IDE. Warning. 20090325172052 :

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.)

But when I run any transastion ABAP Dump is comming.

Thanks

Moni

[Former Member]

Hi Monika

It is the same issue as I mentioned before,this is related to background jobs not running,you need this job RDDIMPDP to run in the system for patches to be applied

Are you not able to access any T-code

If you are able to access SE38,just go in 000 client and your working client and then run report RDDNEWPP.

Your patches will get applied

Rohit

[Former Member]

When I run T code se38

Abap Dump is comming

Long Test Debugger

Runtime Errors SYNTAX_ERROR

Date and Time 25.03.2009 21:24:39

Short text

Syntax error in program "SAPLSEWORKINGAREA ".

What happened?

Error in the ABAP Application Program

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

come across a statement that unfortunately cannot be executed.

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

"LSEWORKINGAREAU01 " in

line 54:

"The data object "WORK_ITEMS" does not have a component called "JUST_FO"

"R_CHECKING"."

" "

" "

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

"The data object "WORK_ITEMS" does not have a component called "JUST_FO"

"R_CHECKING"."

" "

" "

How I Debug this Program.

Because i am not able to run any T-Code.

Moni

[Former Member]

The fastest and safest way to solve this problem is to raise an OSS-message and let SAP analyze the problem.

You have to apply the queue completely and in the current state (any transaction lead to dumps, rddimpdp is not running and cannot be started manually) this is only possible from os-level by certain tp commands. If someone here is suggesting a tp command and this fails, SAP may refuse further support. So the best chance you have is to raise a message at sap.

Regards,

ulf

[Former Member]

Now I want to clear this support pack from OS level . How I remove from OS level . Because right now i am not able to run any transastion

Thanks

Moni

[Former Member]

Hi Monikaa,

Please check this command at os level

tp showbuffer <SID> pf=\usr\sap\trans\bin\TP_DOMAIN_<SID>.PFL

Cheers

Deepanshu

[former_member204746]

you ar ein a catch 22 situation.

you need RDDIMPDP to be scheduled properly. This can be done by going into SE38 and running program RDDNEWPP. but, you get a short dunp... and TP tool at OS level need RDDIMPDP to continue.

So, you are stuck and only have 2 options:

1. restore from last backup and run RDDNEWPP on all clients including 000, then try SP again

2. open a case with SAP, maybe they will be able to do something without restoring.