Scheduled Backup Jobs

[tobias_ptz]

Hello everybody,

We are switching some databases from Oracle to Sybase and at the moment I'm on the setup of a Hot Standby Database.

So I use simple configs <sp_config_dump> to dump my databases (<SID>, master, saptools, sybmgmtdb) and the transaction logs.

These scripts are planed via the SOLMAN DBACOCKPIT.

With Oracle we used BRTOOLS and the DB13, which created in SAP backup jobs (SM37).

So, if no SAP instance is up, no backup job is running, even the DB is online.

With Sybase I found out, the jobs are created in the master db itself, so the dumps are always running.

If I now load on my standby system the master db, it runs the dump scripts as the primary db and some transaction logs (e.g. <SID>.TRAN.20141024.113000.000) will override the other one.

Now my question, where in the master db, or in the job scheduler are the jobs planed in?

And what is the best way to disable the jobs?

- The best way is to disable the jobs without deleting the config_dumps in the master db.

Any idea?

Thank you!

Best regards,

Tobias

[former_member3043 · Accepted solution]

Hello Tobias,

the jobs are in the sybmgmtdb, this is the database the JS is using.

You can verify the jobs with the following procedures ( you need to be in sybmgmtdb):

use sybmgmtdb

go

sp_sjobhelp

go

-> Generates a list or report about all the schedulded jobs. It will list also the collectors and ATM jobs. If you use an older version of DBACockpit, the description is always "SAP DBA Planning Calendar: SQL Script", cause all manual jobs are called SQL Script.

Example:

2> sp_sjobhelp SAP_JOBSCH_SCRPT_20140220154016_1
3> go

--------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
sjob_id: 22  name: 'SAP_JOBSCH_SCRPT_20140220154016_1'
    owner          : sapsa
    created        : Feb 20 2014  3:40PM
    state          : enabled
    job name       : 22 - 'SAP_JOB_SCRPT_20140220154016'
    schedule name  : 16 - 'SAP_SCHEDULE_SCRPT_20140220154016_1'
    server         : SKL
    -- job --------:
    description    : SAP DBA Planning Calendar: SQL Script
    owner          : sapsa
    created        : Feb 20 2014  3:40PM
    properties     : shared
    -- schedule ---:
    description    : SAP DBA Planning Calendar
    owner          : sapsa
    created        : Feb 20 2014  3:40PM
    starttime      : 15:49
    startdate      : 20 Feb 2014

(1 row affected)

If you want details about a job you can use:

sp_sjobcmd <job name, like in our example the SAP_JOBSCH_SCRPT_20140220154016_1 >

go

This will return the commands executed by this job.

To stop a job of being run:

sp_sjobmodify @name='<jobname>', @option='enable = 0'

go

For our example this will be:

sp_sjobmodify @name = "SAP_JOBSCH_SCRPT_20140220154016_1", @option='enable = 0'

This should stop the job of being executed.

Hope this will help.

With kind regards

Stefan

[tobias_ptz · Accepted solution]

Hello Stefan,

Thank you for you quick reply, it helped a lot.

I had to restart the DB to make the changes working, is that right, or do I miss a command?

An other question, is there a way to find out in which db tables I'll find the jobs, to disable them with a select and update command?

Thank you for your help!

Best regards,

Tobias