Skip to Content
avatar image
Former Member

New SQL Monitor: SQLM_UPDATE_DATA job not scheduled automatically

Hi Experts,

Regarding the new SQL Monitor I understood that from SAP Netweaver 7.4 and above SP3, the following background jobs will be scheduled automatically once the servers are activated in SQLM

1. RTM_PERIODIC_JOB

2. SQLM_UPDATE_DATA/SCHEDULE

3. SQLM_DEACTIVATE/SCHEDULE

But when when I activate the servers in SQLM, only the RTM_PERIODIC_JOB is scheduled. The remaining jobs were not scheduled automatically.

Did I miss any settings. Please advise

Thanks in advance

Regards

Anand

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 02, 2017 at 07:36 AM

    Hello Anand,

    you are right, the jobs should be scheduled automatically. Which 7.40 SP do you use?

    What is currently shown in the status overview of transaction SQLM for the lines "Scheduled Data Refresh Job" and "Scheduled Deactivation"?

    Best regards,
    Armin

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 02, 2017 at 07:57 AM

    Hi,

    Thanks for the update.

    Currenty we are using SAP Netweaver 7.4 SP15.

    In SQLM the status overview is shown for the lines requested

    Scheduled Data Refresh - Job Scheduled for Job Event SAP_RTM_COLLECT_ALL_FINISHED

    Scheduled Deactivation - 02/09/2017 / 15:49:20 (UTC+8)

    I also checked im SM37 for the job based on the event given in Scheduled Data Refresh, there is a job SQLM_UPDATE_DATA/SCHEDULE in released status. when the job will be active...?

    Also if i deactivate the servers, the job SQLM_UPDATE_DATA/SCHEDULE is getting deleted.

    Regards

    Anand

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Armin Beil

      Hi Armin,

      Thanks for the reply.

      As you have mentioned, made the SQLM to be continuously active for a few hours and I can see job QLM_UPDATE_DATA/SCHEDULE in finished status.

      The SQLM is working as expected.

      Once again thanks for your info.

      Regards Anand