cancel
Showing results for 
Search instead for 
Did you mean: 

stuck at SPAU_SPDD_CHECK phase

Former Member
0 Kudos

We are running basis package upgrade in BGD with 'A' priority,but the SPAU_SPDD_CHECK phase takes longer time than usual ,(In my case about >12hrs) background job is running with out any errors in sm37.

Experts please help

i'm in a terrrrrible condition.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Anoop,

Once try to apply this patches from dialogue mode.

When you do it through dialogue mode it will display errors if any.

Based on that we can take actions.

Once do it through dialogue and send the screenshot to me.

Answers (4)

Answers (4)

Former Member
0 Kudos

Here we go...

Former Member
0 Kudos

Check tp process at OS level and also Check Filesystem (like /oracle/<SID>/oraarch and etc) having enough space and then Kill stuck process from SAP and OS Level

retry after reset queue

Regards,

Abhishek

alichtenau
Advisor
Advisor
0 Kudos

Hi Anoop,

I thought this is a sybase machine?
Please attach the work process traces.

And please do not reset the queue again in that way.

Cheers,

Andreas

Former Member
0 Kudos

Hey Andreas,

Of course its Sybase machine,

alichtenau
Advisor
Advisor
0 Kudos

Hi Anoop,

can you please attach the work process trace of the running job?

According to your attachments I can see below error, but I think this doesn't correlate with your issue in SPAM.

M  *****************************************************************************

M  *

M  *  LOCATION    SAP-Gateway on host pamserver / sapgw00

M  *  ERROR       hostname 'iwdfvm2738.wdf.sap.corp' unknown

M  *

M  *  TIME        Wed Nov 19 16:55:50 2014

M  *  RELEASE     721

M  *  COMPONENT   NI (network interface)

M  *  VERSION     40

M  *  RC          -2

M  *  MODULE      nixxhl.cpp

M  *  LINE        193

M  *  DETAIL      NiHLGetNodeAddr: hostname cached as unknown

M  *  COUNTER     111

M  *

M  *****************************************************************************

What's the current status? Is the job running? Do you have any dumps or errors in ST22 or SM21?

Could you please attach the workprocess trace of the current run and/or check this for errors?

Many thanks,
Andreas

Former Member
0 Kudos

Hey Andreas,

My Problems Have been Solved.Thanks for your great  Support.

Once again Thanks & Regards,

Anoop

Former Member
0 Kudos

Hi Anoop,

Yes, It seems OCS_QUEUE_IMPORT has been stuck and You need to kill/clean this process
and then do reset Queue from SPAM or SE37 (Functional Module OCS_QUEUE_RESET)
and then try reload and perform SP Upgrade

Please send latest logs(like SLOG, ALOG ) from /DIR_TRANS/log

Regards,

Abhishek

Former Member
0 Kudos

I did that for countless time ! here im attched logs you asked

former_member185239
Active Contributor
0 Kudos

Hi Anoop,

- Run the transaction SM37 and then check the job status.

- Run SM66 and check whether its showing the process there or not.

- If it is not showing in SM66 , you need to kill the process.

Cancel the job and restart the import and also do paste the job logs

With Regards

Ashutosh Chaurvedi

Former Member
0 Kudos

I have Stopped the background process and restarted my sytem, Now spam status is error stop on SPAU_SPDD_CHECK phase.

former_member182034
Active Contributor
0 Kudos

hi Anoop,

Please share the latest log of this SPs. For meanwhile  have a look at below thread. It might be helpful

Regards,

Former Member
0 Kudos

Hi Mr.Abdul,

We have checked above link.Please note that we have already reset the queue more than 2 times ,but still we are facing above mentioned error.Which log you need ? Log fom the tmp directory with same name of the package ?(SAPKB70103.PCD) actually it have 30MB of size

And Thanks for your reply !

former_member182034
Active Contributor
0 Kudos

anoop,

please share the logs(SLOG, ALOG and ULOG) and status of SM50

Regards,

former_member182034
Active Contributor
0 Kudos

anoop,

right now this function OCS_QUEUE_IMPORT is hanged. Please check SM50 and If there is showing a running job which relates to SPAM then first kill this report if you not able then kill the work process and retry the spam.

did you update the statistics or not? If not then please update the statistics and check again the spam.

Regards,

Message was edited by: M. Abdul Jamil

alichtenau
Advisor
Advisor
0 Kudos

Please do NOT reset the queue in this way .This is not supported by SAP and can cause huge troubles if it is executed in a wrong way!