SAINT/SPAM UPDATE takes longer time more than 12hours

[Former Member]

Hi everyone,

I am doing SAINT/SPAM UPDATE version 33 on NW70 systems running on windows 2003 x64 servers with oracle 10g database. The update is running for more than 12 hours and has not finished yet.

Normally SAINT/SPAM update wud take 15 to 20mins. But this is very unusual.

Has anyone faced similar problems before ?

Please suggest solutions if any

thanks

Moses

[Former Member]

hiii

it seems that your background jobs for transports are not running

Rohit

[Former Member]

Hai,

Please check the RDD* jobs are running or not, schedule RDDNEWPP as user DDIC in client 000.

Check whether your sapevt, R3trans and tp are to the latest.

Regards,

Yoganand.V

[Former Member]

Hi Gents,

Im running into the same issue. But logs show no errors ...

wierd problem... Moses did u fix it?

Seelan

[Former Member]

Hi there,

Please check the corresponding log under /usr/sap/trans/log and /usr/sap/trans/tmp for updates.

I am pretty sure that something is wrong. Although not a standard procedure, I'd usually restart the patch application or worse, the app server itself.

regards, Sean.

[Former Member]

hi

Please ensure below items

- Loging using DDIC

- ensure 000 client you login

- ensure your active login session on CI instance (in case multiple instances)

- ensure to shutdown/stop all other instances (Dialog Distances) running on other hosts

Thanks

Sekhar

[JPReyes]

Check the import monitor and the tp system log to check the status of the patch... please post here any errors found.

Loging using DDIC 
ensure 000 client you login 
ensure your active login session on CI instance (in case multiple instances) 
ensure to shutdown/stop all other instances (Dialog Distances) running on other hosts 

This information is inacurate and missleading... You don't need to logon with DDIC you can use any user with the right authorizations, also you don't need to shutdown any instances.

Regards

Juan

[Former Member]

Dear Moses,

Did you try opening a new session and check out sm50, so as to zero in on what is causing the delay?

Did you check the CPU utilization? and HDD utilization?

Regards,

Veera