cancel
Showing results for 
Search instead for 
Did you mean: 

SPAM Error

Former Member
0 Kudos

Hello All,

SPAM /SAINT update running for a long time. I have reset the deployment, updated the tp and r3trans, but same effect. I have restored the DB after the installation and started again the SPAM update, it running again.In the below bar it is showing imp all & clock is moving & moving..We need to update the SPAM from SAPKD70020 to SAPKD70033..SAPKD70033 is giving this above error..

Accepted Solutions (0)

Answers (10)

Answers (10)

Former Member
0 Kudos

Not at all..It was a clustering problem as we were using High availablity system..It has nothing to do with spam..

Former Member
0 Kudos

Hello Scott,

I also have same issue, my system also on a cluster. May i know what needs to be checked

Thanks

Jose

Former Member
0 Kudos

Thanks..

former_member184114
Active Contributor
0 Kudos

Ashley,

Would you mind sharing your solution?

Regards,

Faisal

Former Member
0 Kudos

Hi,

I face the same issue & it runs after running the DB Statistics.

Run DB statistics and try to reimport again.

Regards,

Rajesh

Former Member
0 Kudos

Dear Scott,

Check for File Permissions.

Regards,

Siv

Former Member
0 Kudos

Check STMS configuration. Please check the Import log. Post the error in the Import log (slog).

Thanks,

Sourav Misra

IBM

ashish_mishra2
Contributor
0 Kudos

It use to happen when update process is deacivated from SM13.

Former Member
0 Kudos

hello.

Could be some of the reasons:

1.Check the free space in the imp directories.

2.the necessary background job..are they triggering?

3.Run the tp test to check if it is working fine.

4.When you start the import, check if tp and R3trans are the two main process at the OS-level.

Thanks,

Prasanna

Former Member
0 Kudos

seems that your transport mechanism hangs, check analyze the problem following the Notes

Note 556941 - Transport FAQ: Error scenarios

Note 26966 - Background jobs do not start when transporting

Note 71353 - Transports hang during background steps

JPReyes
Active Contributor
0 Kudos

check the import.log also check the tp system log and the import monitor in STMS, as mention before check that your filesystem is not full, specially the redo logs.

Regards

Juan

Former Member
0 Kudos

hi,

also look for the archive directory ... some time it's get stuck if it is full.

Regards,

Former Member
0 Kudos

Hi,

Please check the logs in tmp directory.

-Srini

Former Member
0 Kudos

You can check work process. Increase your background process.

Thanks

Regards,

Ashish Kumar

SAP Basis Consultant

Former Member
0 Kudos

you can check the logs in the temp directory of your trans directory.Please check that you have space in file system.