cancel
Showing results for 
Search instead for 
Did you mean: 

SPAM/SAINT Update error

Former Member
0 Kudos

Dear Guru's,

After completing the installation of solman 7.0, started the post-installation and we planned update the support package level to current level, so we started to apply the support packages, in the beginning itself if ask for SPAM update and we copied the SPAM/SAINT (SAPKD70038) update file to EPS/in. Now its throwing an error message.

====================================================================================================

- Error in phase: CHECK_REQUIREMENTS

- Reason for error: QUEUE_NOT_EMPTY

- Return code:

- Error message:

Notes on phase CHECK_REQUIREMENTS

QUEUE_NOT_EMPTY: The transport buffer still contains OCS requests

that were not completely processed. To display these requests, use

the following tp command:

tp SHOWBUFFER <SID> -DSOURCESYSTEMS= TAG=SPAM

====================================================================================================

while executing the above command, its showing that trans directory was not set.

====================================================================================================

solccp01:sm1adm 23> tp SHOWBUFFER SM1 -DSOURCESYSTEMS= TAG=SPAM

This is tp version 372.04.70 (release 700, unicode enabled)

E-TPSETTINGS could not be opened.

EXIT

Error in TPSETTINGS: transdir not set.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0208

tp finished with return code: 208

meaning:

error in transportprofil (param missing, unknown,...)

====================================================================================================

While executing tp connect

====================================================================================================

solccp01:sm1adm 25> tp connect SM1 pf=./TP_DOMAIN_SM1.PFL

This is tp version 372.04.70 (release 700, unicode enabled)

Connection to Database of SM1 was successful.

This is R3trans version 6.14 (release 700 - 12.06.09 - 15:20:00).

unicode enabled version

R3trans finished (0000).

tp finished with return code: 0

meaning:

Everything OK

solccp01:sm1adm 26>

====================================================================================================

We running the solman 7.0 on AIX 5.3 with DB2 9.5

Could anyone guide on this.

regards,

Guna

Accepted Solutions (0)

Answers (2)

Answers (2)

markus_doehr2
Active Contributor
0 Kudos

> After completing the installation of solman 7.0, started the post-installation and we planned update the support package level to current level, so we started to apply the support packages, in the beginning itself if ask for SPAM update and we copied the SPAM/SAINT (SAPKD70038) update file to EPS/in.

Start STMS and delete the current queue. Then start SPAM again and apply the SPAM update.

Markus

Former Member
0 Kudos

Dear Markus,

As per your message, I tried by deleting the queue and started the spam update again, now its throwing different error.

Reason for error: CANNOT_DETERMINE_EPS_PARCEL

saying that it doesn't have anything in the EPS Parcel.

regards,

Guna

markus_doehr2
Active Contributor
0 Kudos

- Stop SPAM (leave transaction)

- step on OS level to /usr/sap/trans/buffer

- rename the current <SID> file to e. g. <SID>.old

- start SPAM

Markus

Former Member
0 Kudos

Dear Markus,

Renamed that file and started the SPAM, still its getting the same issue.

regards,

Guna

Former Member
0 Kudos

Dear Markus,

Downloaded the same file and copied to EPS/in, after that the issue has been fixed.

regards,

Guna

Former Member
0 Kudos

You should run transaction STMS once.

This will ensure you have a transport domain.

Without one you can't update any packages.

p.s. SPAM/SAINT should be updated to 39.

Former Member
0 Kudos

Hi David,

Thanks for your information.

Already we did this, trans dir also mentioned there. still we are facing the issue.

regards,

Guna

Former Member
0 Kudos

I faced that same issue only 2 days ago, but when I ran STMS again it solved.

You could try deleting your stms configuration and creating a new one.

Former Member
0 Kudos

Dear David,

Tried with re-configuring the STMS, still same issue only.

regards,

Guna