Automic Workload Automation

Expand all | Collapse all

SQL Job Output - ControlM vs Automic

  • 1.  SQL Job Output - ControlM vs Automic

    Posted 25 days ago
    Hi Community members,

    Hope you all are safe and well.

    I have an issue regarding SQL jobs.
    I am trying to run a SQL job in Automic, which is running from Control-M currently. when we compare the output, it looks completely different.
    Control M gives a detailed report which is missing in AUtomic.


    Started:  3:32:30 PM  Error: 2020-08-09 15:32:34.81     Code: 0x00000063     Source: Throw Control Error Demantra Error     Description: Demantra Control Table has wrong Status for T_SRC_SALES_TMPL  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  3:32:30 PM  Finished: 3:32:34 PM  Elapsed:  4.203 seconds.  The package execution failed.  The step failed.

    We have the default setting for report in Automic however we do not find this error in our report.

    job_id;originating_server;name;enabled;description;start_step_id;category;owner;notify_level_eventlog;notify_level_email;notify_level_netsend;notify_level_page;notify_email_operator;notify_netsend_operator;notify_page_operator;delete_level;date_created;date_modified;version_number;last_run_date;last_run_time;last_run_outcome;next_run_date;next_run_time;next_run_schedule_id;current_execution_status;current_execution_step;current_retry_attempt;has_step;has_schedule;has_target;type
    46BD0E33-73E6-431C-8426-D52A8C471F81;KEUTVINTSQL01;GTG_DTC_PutShipmentHistoryToDemantra;1;No description available.;1;[Uncategorized (Local)];NT AUTHORITY\SYSTEM;0;0;0;0;(unknown);(unknown);(unknown);0;2016-12-21 11:26:55.54;2017-02-21 21:14:41.72;5;20200927;153149;0;0;0;0;4;0 (unknown);0;1;0;1;1

    step_id;step_name;subsystem;command;flags;cmdexec_success_code;on_success_action;on_success_step_id;on_fail_action;on_fail_step_id;server;database_name;database_user_name;retry_attempts;retry_interval;os_run_priority;output_file_name;last_run_outcome;last_run_duration;last_run_retries;last_run_date;last_run_time;proxy_id
    1;Execute GMCR_DTC_GMCR567_004_01_Shipment_Hist_to_D;SSIS;/SQL "\"\GMCR\GMCR_DTC_GMCR567_004_01_Shipment_His;0 ((normal));0;1 (quit with success);0;2 (quit with failure);0;;master;;0;0;0 (normal);;0;6;0;20200927;153149;2

    schedule_id;schedule_name;enabled;freq_type;freq_interval;freq_subday_type;freq_subday_interval;freq_relative_interval;freq_recurrence_factor;active_start_date;active_end_date;active_start_time;active_end_time;date_created;schedule_description;next_run_date;next_run_time;schedule_uid;job_count

    server_id;server_name;enlist_date;last_poll_date;last_run_date;last_run_time;last_run_duration;last_run_outcome;last_outcome_message
    0;KEUTVINTSQL01;1998-11-13 00:00:00.0;1998-11-13 00:00:00.0;20200927;153149;6;0;The job failed. The Job was invoked by User UC4AD


    Could someone please check and suggest.

    Thanks in Advance
    Shani


    Attachment(s)

    txt
    0010938792.ACT.txt   825B 1 version
    txt
    0010938792.PLOG.txt   795B 1 version
    txt
    0010938792.REP.txt   1K 1 version
    txt
    CTM - OUTPUT_FILE.txt   3K 1 version


  • 2.  RE: SQL Job Output - ControlM vs Automic

    Posted 25 days ago
    Edited by Pete Wirfs 25 days ago
    We have not run SQL jobs against SQLServer. 

    It is possible that there could be more descriptive error messages in the agent logs that are written to the "temp" folder that is adjacent to the "bin" folder that your SQL agent is running from.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------