Blueshire Services

Scheduler FE Grid

User Documentation

For Version 7.3.0.0 Upgrade

 

 

 

Table of Contents

Technical Overview

Setting Up The System

Introduction

The Log and Run Screens

Setting Up The Connection Parameters

Security

Appendix A - Table Dba_Scheduler_Running_Jobs

Appendix B - Table Dba_Scheduler_Job_Log

Appendix C - Table Dba_Scheduler_Job_Run_Details

Appendix D - Table Dba_Scheduler_Running_Chains

Appendix E - Table Dba_Scheduler_Window_Log

Appendix F - Table Dba_Scheduler_Window_Details

 

Technical Overview

From a technical perspective the system consists of two sides. There is the database, currently Scheduler FE Grid supports Oracle 10g Release 1 and 2, Oracle 11g Release 1 and 2, and Oracle 12c. On the client side there is the Java application. Connecting the two is a JDBC connection. In summary then we have the following:-

 

 

The java source files are compiled with a target option of 1.7 allowing computers with a java VM of 1.7 and above to run Scheduler FE Grid. Given that this was released in Jul. 2011 this enables Scheduler FE Grid to operate on a wide a variety of machines.

 

Scheduler FE Grid incorporates the following external libraries:-

 

Setting Up The System

 

To set up the system download the zip file,

Extract the three files :-

and put them in a directory.Now create an icon on your desktop that has the following as the target :-

 

{Directory of the java exe}\java.exe -jar Scheduler.jar

 

The "Start in" should have the directory where Scheduler.jar is found.

 

The user that will run the system will need write permissions on this directory as the system will need to update the file SchedFileInit.csv and will need to create the following files :-

 

The setup is now completed.

 

Introduction

 

This documentation describes the additional functionality that has been incorporated into Scheduler Grid 7.3.0.0. It does not attempt to describe the functionality of Scheduler Grid only the changes that have been made to Version 7.3.0.0. This documents builds on the Scheduler Grid documentation.

 

The Log and Run Screens

 

The aim of the Scheduler FE Grid upgrade was to extend the database grid aspect of the system. With this in mind it seemed appropriate to have the Log screens displaying information from multiple databases. This was applied to the following views:-

For the above screens the data displayed will be from all currently open databases and not as previously from the currently selected database.

 

 

With the "Log View - Standard", the screen is split into two parts, the upper contains data from the table Dba_Scheduler_Job_Log.

The following seven columns are displayed on the screen.

 

 

The screen display in the lower half of the display shows data from the view, Dba_Scheduler_Window_Log. The following six columns are displayed on the screen.

This is shown in the screen image shown above. The database name is the name given in the connection details to that database. It can be seen from the screen display above that the data is still displayed in date/time order with the earliest entries shown at the top.

 

On the tool bar at the top of the screen are two buttons, the left and right button. These are used in conjuction with the Job Log View screens, both standard and detailed. Pressing the Left button results in the date going back one day and pressing the right button will cause the date to go forward one day. The data displayed in either of the two screens will be updated and the data for the respective day displayed. The Logs data is usually only kept for one week so entering a date prior to one week or in the future will result in the Log View Screen displaying no data.

 

The Standard Job Log View only displays seven items of data. It is possible to display all of the information for a specific Job entry. This is carried out by one of several methods. The first method is to double click on the left mouse button on the row that you want the details for. Alternatively you can highlight the row and then press the Detail button. The third method is to highlight the row and then enter the Job Detail menu option found under the Job main menu. The result will be the display of the Job detail screen. To return to the Standard Job Log view screen press the OK button found on the Job detail screen.

 

The second screen that can incorporate data from multiple databases is the "Log View - Detail" screen shown on the left.

The following seven columns are displayed on the screen.

 

 

The screen display in the lower half of the display shows data from the view, Dba_Scheduler_Window_Details. The following six columns are displayed on the screen.

As with the "Log View - Standard" the left and right arrow shift the current date of the date to the previous date or next date respectively. The display of detail data for a specific row is also the same.

 

With both the Log View screens it is important to filter the information otherwise the number of rows returned and therefore displayed is likely to be considerable causing performance issues. The solution is to apply appropriate filters on the data to limit the number of rows returned and displayed. How this is achieved is detailed in the following section.

 

The final screen that can be displayed is the Scheduler Run View. This displays all the Jobs and Chains that are currently running. The screen is divided into two with the Jobs that are currently running being displayed in the top screen and the Chains that are currently running being displayed in the lower screen.

The Job screen displays five columns. These are as follows :-

The Chain screen displays seven columns. These are as follows:-

 

As with the Job Log screen the Run Job screen has the "Detail" button active in the right side of the Toolbar. On pressing this button a screen showing the details of either the Job or the Chain will be displayed. For this detail screen to be displayed either a Job or a Screen has to be highlighted.

 

Setting Up The Connection Parameters

Setting up the connection can be carried out by either editing an existing connection or alternatively by creating a new connection. The existing connections can be seen in the tree structure under the Scheduler Manager node. To edit an existing connection highlight the connection and then press the update button. The screen shown on the right will appear. Update the entries and press the OK button to save the updated values.

 

To create a new entry open the Create menu option and then press the Connection option. This will result in the same screen as the update option appearing but with all the fields being set to null. Enter the values of the new connection and then press the OK button. The new connection will appear in the tree structure.

 

The Connection screen has changed considerable with the new release.

 

Going through the fields. At the top is the Connection Name which can be anything you choose. This is the name that will appear in the tree structure and the database name of the log views and which will identify the specific connection. It should ideally be reasonable short and describe succinctly the connection. The next field is the Username which is the username that you will use to connect to the database.

There then follows the Password which previously was not saved but now can be. If the password has been saved then it will appear as a series of asterics as shown in the screen shot on the right, so that it will always remain hidden.

 

Then follows the Host which is the name of the server on which the database sits. This can be either a name or an IP address. If the database is on the same machine as you are running Scheduler FE Grid then enter localhost as the Host. The next field is the port which is 1521 by default. Your organisation might use an alternative port number, check with your database administrator. The last field is the Database which was originally the database Oracle_Sid. This has now changed to the Oracle service name which is usually the same as the Oracle Sid but can vary, again check with your database administrator.

 

Below all the text fields is a checkbox with "Logon as Sysdba" as its title. If you are setting up the Resource Manager for a CDB (container database) on Oracle 12c then the username you are using to logon to the database will require sysdba privileges and you will need to logon as sysdba. In that case this checkbox will need to be set. Otherwise there is no need.

 

There then follows two checkboxes that are new to Version 7.3.0.0. First is the "Save Password" checkbox. If this is set then the current password will be saved in an encrypted format. The password saving option works as follows. If there are no passwords to be saved then no output is written to the password file. This means that if you enter a number of passwords with the "Save Password" checkbox set and then exit the passwords will be saved. If you then enter the system again and uncheck the "Save Password" checkbox for these entries then no attempt will be made to overwrite the password file and on subsequent use of the system the passwords will be read.

The final entry is the "Automatic Logon" checkbox. This works in combination with the new menu entry "Auto-Connect" found under the "File" main menu entry. When the "Automatic Logon" is set and the "Auto-Connect" menu entry is entered then the system will automatically connect to this database. The thinking behind this functionality is to enable the user to monitor a number of databases at the same time. If the user wants access to the logs of a number of databases then the "Automatic Logon" can be set for these databases and then when the "Auto-Connect" menu item is entered the system will connect to all of the databases. It does assume that the password for that database has been saved otherwise the automatic logon will skip the database.

 

The logon that occurs from an "Automatic Logon" differs from a standard logon. When a standard logon occurs the system logs onto the database and reads all of the information on the scheduler objects into memory. With an "Automatic Logon" the system connects to the database only, none of the scheduler data is read into memory. The aim is to minimise the use of memory if there are a large number of databases that are being monitored with regard to the log views then there is no need to collect the data on the scheduler objects.

 

The two different logons are indicated by the different icons that are displayed on the connection node. On the right is an image showing the two different logon icons. At the top is the icon that shows that the database has a connection but it is an automatic logon connection. Below is displayed the icon with a full connection where the database objects have been loaded into memory. You will notice that the full logon icon has a flag at the side which if pressed will open the tree displaying the scheduler objects. If you want to move from a basic connection to a full connection where the scheduler objects can be seen then highlight the specific connection and then enter the connect button. This will result in the scheduler objects being loaded and the icon being changed to a full logon icon.

 

It was stated in the previous section, the Log and Run Screens, that it is essential to filter the display screens that access rows from multiple databases. This is to avoid getting infinite quantities of data together with the performance issues this causes. To prevent this the filtering of the data is required and this is handled in the connection screens.

 

The connection screen in version 7.3.0.0 now has three tabs of which tab two, "Select Criteria 1", and tab three, "Select Criteria 2" are directly related to filtering the output rows. Tab two can be seen in the screen shot above and in the screen shot can be seen three input areas. These are where the filter statements for the running jobs data and the two job logs are entered and displayed. On tab three are again three input araes but on tab three the input areas are for the running chains data and the two window log data filters.

 

The filters that can be entered are dependent on the data tables as the statement entered is the where clause in the SQL statement with the "where" part removed. The column names that can be entered are dependent on the tables and these are shown in Appendix A through to Appendix F. The most used filters will be the most simplest like the filter shown above "OWNER != 'SYS'". Any constants entered like the 'SYS' above must be enclosed in single quotes and not double quotes. After entering a filter it is suggested that you test the value entered by moving to the display screen. If no data is displayed then an invalid entry has been saved. Check with the error log file to confirm this.

 


Security

 

From the Connection setup screen shown above it can be seen that the password can be entered and also that it can be saved by ticking the "Save Password" box. When this box is set the password will be save in an encrypted format within the file SchedFilePass.csv. The encryption uses AES (Advanced Encryption Standard).

As part of the encryption an initialisation vector is used. This is set in the system setup file SchedFileData and is an entry in the "09" system parameters section, specifically the entry "5" which is the initialisation vector parameter. This value consists of 16 numeric characters and it is suggested that you reset this value. If you do reset it then it will not be possible to decrypt any passwords stored in the file SchedFilePass.csv. You will need to delete the existing SchedFilePass.csv file and re-enter the passwords.

 

As part of the system security it is possible to reset the directory and name of the flat files. There are five flat files as shown in the table below, of which it is possible to reset the directory and name of four. The file SchedFileData.csv has to be situated in the same directory as the system jar file. The table below gives the id number of the specific directory/file name. All of the parameters are set in the file SchedFileData.csv in the "09" system parameters section. The id number is the number in the second column of the parameter line followed in the third by the parameter value.

 

Scheduler FE Grid - Flat Files
Default File Name Reset Dir/Name (Y/N) Parameter Id
SchedFileData.csv N
SchedFileInit.csv Y 1
SchedErrors.log Y 2
SchedAudit.log Y 3
SchedFilePass.csv Y 4

 

Appendix A - Table Dba_Scheduler_Running_Jobs

 

Table - Dba_Scheduler_Running_Jobs
Column Name Column Type Max. Len.
Owner Varchar2 30
Job_Name Varchar2 30
Job_Subname Varchar2 30
Job_Style Varchar2 11
Detached Varchar2 5
Session_Id Number
Slave_Process_Id Number
Slave_Os_Process_Id Varchar2 12
Running_Instance Number
Resource_Consumer_Group Varchar2 32
Elapsed_Time Interval
Cpu_Used Interval
Destination_Owner Varchar2 128
Destination Varchar2 128
Credential_Owner Varchar2 30
Credential_Name Varchar2 30

 

Appendix B - Table Dba_Scheduler_Job_Log

 

Table - Dba_Scheduler_Job_Log
Column Name Column Type Max. Len.
Log_Id Number
Log_Date Timestamp
Owner Varchar2 30
Job_Name Varchar2 65
Job_Subname Varchar2 65
Job_Class Varchar2 30
Operation Varchar2 30
Status Varchar2 30
User_Name Varchar2 30
Client_Id Varchar2 64
Global_Uid 32
Credential_Owner Varchar2 65
Credential_Name Varchar2 65
Destination_Owner Varchar2 128
Destination Varchar2 128
Additional_Info Clob

 

Appendix C - Table Dba_Scheduler_Job_Run_Details

 

Table - Dba_Scheduler_Job_Run_Details
Column Name Column Type Max. Len.
Log_Id Number
Log_Date Timestamp
Owner Varchar2 30
Job_Name Varchar2 65
Job_Subname Varchar2 65
Status Varchar2 30
Error# Number
Req_start_Date Timestamp
Actual_Start_Date Timestamp
Run_Duration Interval
Instance_Id Number
Session_Id Varchar2 30
Slave_Pid Varchar2 30
Cpu_Used Interval
Credential_Owner Varchar2 65
Credential_Name Varchar2 65
Destination_Owner Varchar2 128
Destination Varchar2 128
Additional_Info Varchar2 4000

 

Appendix D - Table Dba_Scheduler_Running_Chains

 

Table - Dba_Scheduler_Running_Chains
Column Name Column Type Max. Len.
Owner Varchar2 30
Job_Name Varchar2 30
Job_Subname Varchar2 30
Chain_Owner Varchar2 30
Chain_Name Varchar2 30
Step_Name Varchar2
State Varchar2 15
Error_Code Number
Completed Varchar2 5
Start_Date Timestamp
End_Date Timestamp
Duration Interval
Skip Varchar2 5
Pause Varchar2 5
Restart_On_Recovery Varchar2 5
Restart_On_Failure Varchar2 5
Step_Job_Subname Varchar2 30
Step_Job_Log_Id Number

 

Appendix E - Table Dba_Scheduler_Window_Log

 

Table - Dba_Scheduler_Window_Log
Column Name Column Type Max. Len.
Log_Id Number 6
Log_Date Timestamp
Window_Name Varchar2 65
Operation Varchar2 30
Status Varchar2 30
User_Name Varchar2 30
Client_Id Varchar2 64
Global_Uid Varchar2 32
Additional_Info Clob

 

Appendix F - Table Dba_Scheduler_Window_Details

 

Table - Dba_Scheduler_Window_Details
Column Name Column Type Max. Len.
Log_Id Number
Log_Date Timestamp
Window_Name Varchar2 65
Req_Start_Date Timestamp
Actual_Start_Date Timestamp
Window_Duration Interval
Actual_Duration Interval
Instance_Id Number
Additional_Info Varchar2 4000