cancel
Showing results for 
Search instead for 
Did you mean: 

Back ground job not stopping (Backup job)

Former Member
0 Kudos

Hi Experts

There is a background job of backup running now, I want to end it.

It is not ending from SM37 when i try to cancel it.

Also, I had earlier scheduled these jobs in DB13, and later deleted it, but still it starts automatically at the specified time.

I dont understand why is it so, and when I try to delete it, it does end.

I dont want to end it from SM50.

Please suggest me a solution.

Thanks

Harikrishna

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

try this on the os level:

Under db2sid do:

db2_all "db2 list applications show detail " |grep Per  (find backup services/agent id's at DB2 level)

then

db2 "force application (NUMBER)"; (number is the agent/process)

Former Member
0 Kudos

Hi Hari,

somtimes it happens , when connection between DB13 and SM37 is broke. then system show job running bt in actual job is not running at backend like workprocess stuck .

Please check at database level whether datafiles are in backup mode i.e.( V$BACKUP table in Oracle) .u can check for DB2 .

If not, that means no job is running . and u jst restart the work process.

Regards

Deepak

Former Member
0 Kudos

Hi Deepak

The job was running, i had checked in the file system also, the back up file size was changing..

paul_power
Active Contributor
0 Kudos

Hello Harikrishna,

What is your database type and release number?

The jobs no longer show as scheduled in DB13?

The ones that are existing are they new ones or the ones from when db13 had scheduled some backups? Is there any sign from the db logs of these backups having failed or are they still in progress?

regards,

Paul

Former Member
0 Kudos

Hi Paul

The database is DB2 and version is 09.01.0007

Yes, the jobs no longer shows in DB13, I have deleted all jobs from DB13 last month.

But suddenly it started since yesterday.

When I try to end it from SM37 it does not end.

DB13 --> double click on the job --> says -->

This action has not been scheduled via DB13.

Therefore parameter settings are not available.

Status - running.

SM21 log error: "Database error -2048 at EXE"

Also, the once that are existing (which I have not deleted) shows some error but gets finished

Error:

Action deleted in SDBAP at 20120915225959

Job cancelled after system exception ERROR_MESSAGE

I dont understand why this is happening.

Former Member
0 Kudos

Hello Hari,

go to SM37, select the job you want to cancel and (don't press Stop) but go to JOB -> Check status (or CTRL+SHIFT+ F12)

And after this refresh a couple of times the window.

Former Member
0 Kudos

Hi Harikrishna

adding to paul,

is your DB team using an externel software like commvault ,for backup purpose?

Former Member
0 Kudos

Hi Vlad,

I did, but still job is running...

it says: 1 jobs were checked and 0 jobs were corrected.

@deepak: they are using emc..

Former Member
0 Kudos

hello,

so in db13 there is no entry in your calendar (with Category : All Actions selected) right?

Can you pasta a part of the job log (the beginning) and also some details about it.

As i understand you don't want to kill the process directly from OS or SM50 with /without core.

Former Member
0 Kudos

yes, no entry in DB13.

DB13 --> double click on the job --> says -->

This action has not been scheduled via DB13.

Therefore parameter settings are not available.

Status - running.

No, not from SM50 or OS, I need to know why this job is not getting canceled from SM37, why is this job running even when I have already canceled it from DB13.

Former Member
0 Kudos

Hello,

have a look at SAP Note 1293321 and 931122.