cancel
Showing results for 
Search instead for 
Did you mean: 

SPAM update error

former_member183044
Active Participant
0 Kudos

Hi Experts,

I have came to a critical solution. Please Help.

I have applied the patch (SAPKB73103) upgrade through SPAM for the level upgrade 2 to 3. I put through Background job yesterday evening(18.00). But today morning , when i checked in SM37 the job is still Active.

Is the patch upgrade takes that much time?

Screenshots are attached below.

Awaiting your earliest replies....

Regards

Praveen

Accepted Solutions (1)

Accepted Solutions (1)

former_member183044
Active Participant
0 Kudos

Hi Experts,

After some time, the spam upgrade has been successfully completed. The issue was there beacuse there was no space in device. Then we extended the device space.

After half an hour, the upgrade have been completed.

Thanks to all .

Regards

Praveen

Former Member
0 Kudos

Hey Praveen,

Good to hear that the issue is fixed.

Check my comments of Nov 6th reg OS space and db table space.

Also one more thing : please deactivate archive logs as archives will be high and can fill up your archive directory at os level and if it fille up the complete system will hang with no users to login to system possible

Regards,

Nikhil

former_member183044
Active Participant
0 Kudos

Hi Nikhil,

Thanks for your valuable information.

Can u please tell me how to deactivate archive logs?

Regards

Praveen

Former Member
0 Kudos

This message was moderated.

mohsin_mulani4
Discoverer
0 Kudos

HI Praveen,

login as orasid

sqlplus / as sysdba

Disable archive log mode

archive log list
shu immediate
startup mount
select status from v$instance;
alter database noarchivelog;
alter database open;
select status from v$instance;
archive log list

Regards

Mohsin

former_member183044
Active Participant
0 Kudos

Hello muhsin,

Thanks for the reply...

Regards

Praveen

Answers (8)

Answers (8)

Former Member
0 Kudos

Hi Praveen,

Check both OS space and DB table space. Then check the upgrade logs

Regards,

Nikhil

former_member182657
Active Contributor
0 Kudos

Hi,

Could you please share SLOG,ALOG and ULOG,and check the job status for further details.

Regards,

Gaurav

Reagan
Advisor
Advisor
0 Kudos

The first screen is not an error. It says the job has been scheduled. You should check the job log.

Click on the icon next to the refresh icon and check the status of the job. If it is still active then do a "Check Status" of the job. Select the job and then from the menu  select "Job" - "Check Status"

and see if that changes the status of the job.

former_member185239
Active Contributor
0 Kudos

Hi Praveen,

- Check the job logs

- Check the /usr/sap/trans/tmp folder if any logs file are getting updated or not.

- check the tp and r3trans process on os level.

- check the database , there might be a transaction log might be full.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hello Praveen,

Have you cleared the DB issue which i pointed out in the earlier thread()

regards,

pavan

Syamkriz
Active Participant
0 Kudos

Did your system gone down for any backup or something? check the patch logs, provide sm21 logs. Without posting logs no one can guess what happened

regards,

Syam

Former Member
0 Kudos

Hi Praveen,

Please check the space..

ans also check the logs...?

Regards,

Raj

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi,

Did you check the jobs logs ?

What about other related logs ?

Regards,