Scope
The SOS Support team neads to have informations of your JobScheduler environment. This article describes how you can provide these informations.
The jobs and job chains you find attached to this article to the following.
Job get_environment_data
This is a standalone job that
uname
detect running JobScheduler instances
reads all environment variables
executes a top command.
The output will be stored in the file that; output_file_name; ./sos_support.log
number of top command iterations;number_of_iterations;1
Please run the job and send the log file to the SOS support team.
The job chain job_chain_get_support_data executes some db sql statements to get
the number of active orders
the number of active tasks
the number of configuration files for
orders
job chains
jobs
Please note that the reporting interface have to be installed and activated.
The last step in the job chains reports to the order log.
Example
2016-04-13 16:09:58.336+0200 [info] (Task support/report:18367873) 10 active orders found in the database
2016-04-13 16:09:58.342+0200 [info] (Task support/report:18367873) 0 active tasks found in the database
2016-04-13 16:09:58.353+0200 [info] (Task support/report:18367873) 19 orders defined for 24 job chains
2016-04-13 16:09:58.364+0200 [info] (Task support/report:18367873) 46 jobs defined
Please send the order log to the SOS support team.
Configuration
The job /support/DB Statement has the following parameters
db_class;SOSConnectin according;SOSOracleConnection
db_driver;The jdbc driver class;oracle.jdbc.driver.OracleDriver
db_url;The jdbc connection string;jdbc:oracle:thin:@//d_host:1521/db_name
db_user;The db user
db_password;The password for the db user
You can find the values for your database in the file $SCHEDULER_DATA/config/factory.ini in the section [spooler] in the entry db
The order to start the job chain can be parameterized with the parameter scheduler_id. If empty, the scheduler_id of the actual JobScheduler will be used.