Scheduler FE Grid
Table of Contents
Scheduler FE Grid has been designed and developed as a front end for Oracle's Scheduler utility. For the Scheduler administrator it aims to give a view of the scheduler objects thereby allowing the administrator to see the whole picture. In addition and complementary to this it makes the administrators tasks simpler by utilising GUI front ends that sits on top of the underlying DBMS_Scheduler package thereby simplifying the modification of the underlying objects. It has update, delete, copy and insert functionality that calls the existing Oracle Scheduler package but removes the time consuming task of creating the scripts.
In addition it provides views that allow the administrator to see which Jobs/Windows have run, the log files, and which Jobs/Windows are currently running.
Scheduler FE Grid has been built on top of the earlier Scheduler FE. It extends Scheduler FE by allowing the user to connect to multple databases at the same time thereby extending the view across the users database grid. It distinguishes between five versions of Oracle's scheduler, these are Oracle 10g Release 1 and 2, Oracle 11g Release 1 and 2, and Oracle 12c. It will display the appropriate screen for the specific object and version. To do this it has in effect unified the four versions of Scheduler FE and presented it into one system, Scheduler FE Grid. If after logging onto an Oracle database it percieves that it is not one of the above versions then it logs itself off.
Scheduler FE Grid Release 7 has extended the functionality of Scheduler FE Grid to encompass the functionality that was given by Resource FE. That is it provides a front end to sit on top of the functionality provided by Oracle's Resource Manager. It enables the user to see the Resource Manager objects currently built within the current database in a tree like structure.
Scheduler FE Grid Release 7.1 included the functionality of connecting to Oracle 12c and displaying the Scheduler and Resource Manager objects. This includes the standard version, the container version and the plugable version.
Scheduler FE Grid Release 7.2 included the functionality of utilising Resource Manager to assign resources across Pluggable Databases. This new functionality is described in the Chapter entitled "Resource Manager under Oracle 12c". There is also the option to logon as sysdba which is required to create the Resource Manager objects for a CDB.
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.
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 :-
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.
The initial screen is shown on the right. It consist of at the top a menu with menu buttons below and then below that the information line which will display the current user, host and current operating date.
Finally occupying the greater part of the screen is the main block which currently has a picture of the Solar System taken from Voyager 1.
The options at this point in time are to exit the system, connect to the database or create or update the connection details. To exit press the "Exit" button. To connect to the database move the focus to the connection node that you wish to connect to and then press the "Connect" button. This will result in the log on dialog screen appearing as shown below. Enter your password. On pressing the "OK" button the system will log you into the database assuming you have entered valid parameters.
As you can see from the screen shot shown in the Tree Panel section the information line which sits below the menu buttons now displays the username and host under which you have logged onto the database. Also the main data block now displays a screen that is split into two sections. On the left is the tree navigation view and on the right is the main data block. When a node in the tree is selected that is a folder and therefore has no associated data then the picture of the solar system will be displayed. This is the case when you first log on to the system and the current node in the tree is the root node. The details of both the tree panel and the main data panel are described in subsequent sections.
This initial screen is called the Scheduler Manager view and is one of seven views. On the main menu line is a radio menu option list, the views menu. The list consists of the following four options:-
The additional six screens will be described in detail later in the document.
The initial Scheduler Manager Tree view is the only screen where you can switch from one database to another. All the other views take the existing selected database, that is the database shown in the information line. When there is no database shown on the information line then it is not possible to switch to the other six views.
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.
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 which you will use to 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. 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 not always.
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.
Having logged onto a database the screen as shown on the right will be displayed. The main screen is divided into two parts as shown in the screen shot. On the left hand side is the tree panel which is the navigation utility of the system. When the user first enters the system all the nodes will be closed with the exception of the Scheduler Manager node and the connection nodes which are directly attached to the Scheduler Manager node. When the user successfully logs onto a database the connection will be redisplayed with the Connect icon. It will then be possible to open up the icon by clicking on the lever positioned to the left of the icon. This will open up the tree to display the next level as shown in the screen shot on the right.
This level shows the Schedulers main object groupings. To display specific objects continue to open up the tree to where the object you want to see is to be found. The whole of the tree structure is shown below.
The structure of the tree is shown in the diagram below. This structure is for an Oracle 11g Release 2 database. If the database is prior to 11g Release2 then some of the objects will not be displayed.
The Tree Panel
By clicking on a node the details of that node are displayed in the right hand data panel. At any point in time there can only be one node on the tree that is in focus.
The structure of the tree is extended beyond the above structure by the inclusion of the following links:-
These links exist by default but can be modified by entering the menu option "File", then "Options", and then updating the "Options" screen. If you do modify the links then the button "Refresh" will need to be pressed so that the tree structure can be refreshed.
To refresh the data highlight the connection node for the database that is open and you want to refresh. The Refresh button will be enabled, press the Refresh button and the data will refresh from the database.
On the right hand side of the screen is the data panel. This consists of the detailed information on the object currently in focus on the tree. The information can be displayed over multiple pages depending on how the page is set up. The screen display can be changed in any number of ways. The labels can be changed and repositioned. The text items can also be repositioned or/and removed for specific groups of users. The size of the label, the font, the font style, and the color of the label are all defined within the parameter file. This also applies to the text and its position. The number of tab pages that make up a screen are also defined as are the tab page descriptions.
On each of the text items it is possible to assign a zoom button. This is one of the setup options and is appropriate when the entry can possible contain a large quantity of text. On the screen display shown to the right the entry "Job Action" has a zoom button assigned to it. The button is identified by being to the right of the text and having an icon of a pair of glasses. Pressing the button results in a dialog box being displayed as shown in the screen display shown below.
The Main Screen with a Dialog displayed
One of the options on the main menu bar is the "Create" option. This allows the creation of the following objects:-
On entering any one of these twelve options a new "Create" screen is displayed. Each of these screens is unique depending on the data that has to be entered for that specific object but they have a similiar look and feel as can be seen from the "Create Job" screen shown on the right.Two of the new entry screens have multiple screens. The "Jobs", shown on the right and the "Windows" entry screen have multiple entry options. With the "Jobs" screen there are six screen options allowing six different sets of data to be entered. These six options are as follows:-
To create a new job any of the six screens can be used but only the data from the screen currently being shown when the "OK" is pressed will be saved.
Creating objects can be carried out by the "Copy" utility in addition to the "Add" utility. The copy utility requires that the object to be copied is currently in focus. On entering the "Copy" button a new input screen will be displayed. The name of the new object will be requested and on pressing the "OK" button this new object will be created taking most of its attributes from the existing object. It is sometimes easier and quicker to copy an object rather then creating a new object.
In addition to creating new objects there is the functionality of updating the existing data. This is achieved by selecting the object from the tree structure that is to be updated, putting the object into focus, then pressing the "Update" button or alternatively the Objects/Update menu option. This will result in the dialog display shown in the screen shot on above being displayed on the screen. The dialogue display includes a pull down list that allows you to select the column that you want to update. It is not possible to update all the columns displayed on the screen and the pull down list only shows the columns that can be updated.
Having selected the column you are now free to enter the value for that column. It is possible to enter any value into the text area but should you attempt to save an invalid value an error box will be displayed pointing out to you the error that you have made. To save the updated value you enter the "Save" button. To return to the original value you press the "Cancel" button.
In addition to creating objects and updating objects the system has additional functionality that amends the data. This includes the "Enable" and "Disable" options which apply to the Jobs, Programs, Chains, Windows and Groups. To use these options you need to have one of these objects in focus. Pressing the "Enable" button when the object is already enabled will not produce an error but nor will it change the status of the object. This applies equally to an object that is disabled when you press the "Disable" button.
The last utility that modifies the objects is the "Drop" utility. This is used to remove objects from the database. As with the Copy and Update utilities the object to be dropped needs to be in focus. Then the user can press the "Drop" button or alternatively press the Object/Drop menu item. On entering either of these a dialog screen will appear asking you to confirm that you require this object to be removed. This is to help prevent the accidental removal of objects. Remember that once you confirm that you require this object to be removed there is no method of restoring the object except from a previous backup.
The menu options and the Buttons displayed at the top of the screen display are all sensitive to the current focus. This means that they are only active where the menu options and buttons can be utilised. For example when the focus is held on a folder thereby resulting in the screen display of the Solar System few of the buttons can be activated. It is not possible to copy a folder or to update the details of the folder and hence these buttons and the associated menu options are disabled. They are shown greyed out.
In the case of the "Create" menu options, the "Job Argument" and "Job Notification" are only active when focus is currently residing on a specific Job. Then the Job argument or Job Notification, when created will be attached to that Job. Similarly this applies with Programs/Program Arguments and Chains/Chain Rules and Chain Steps.
Some of the buttons have multiple functions. The "Run" and "Stop" button that is displayed when Scheduler FE Grid is displaying the object screen is replaced by the "Prev" and "Next" button once the Log View screen is displayed.
In addition to the standard mouse the Scheduler FE Grid system also supports accelerator keys. Nearly all of the funtionality of the system can be called using accelerator keys and these keys are displayed below. Theye are also displayed on the menu options at the right hand side.
The final method of navigation is to use the mnumonic keys. These are activated by using the Alt key plus the mnumonic key. This is the key that is underlined on the menu entries. It is possible to navigate through Scheduler FE Grid without the use of the mouse by instead using the mnumonic keys.
The next screen that can be displayed is the Log View - Standard. An example of this screen is shown to the right.
The screen is split into two parts, the upper contains data from the table Dba_Scheduler_Job_Log.
The following six 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 five columns are displayed on the screen.
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 Job Logs View only displays six items of data. It is possible to display all of the information for a specific Job run. 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 as shown on the right. To return to the Job Log view screen press the OK button found on the Job detail screen.
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.
Scheduler FE Grid Release 7 incorporates the functionality of Resource FE. This gives the user the ability to move from Oracle's Scheduler objects to Oracle's Resource Manager objects which are closely alligned with each other. Because it is the functionality of Resource FE that has been incorporated it serves little purpose to repeat the documentation of Resource FE rather the user should read the existing Resource FE documentation.
Scheduler FE Grid Version 7.2 incorporates support for the CDB (Container Database) that is an option in Oracle 12c. In Oracle 12c there is the option to create multiple Pluggable Databases. It is from within the single CDB that the resources across the multiple PDB are allocated.
From within a CDB it is possible to create a CDB Resource Plan and multiple CDB Resource Directives. Both the CDB Resource Plans and their associated CDB Directives can now be seen from within Scheduler FE Grid. The CDB Resource Directives are shown in the attached screen print.
When a new CDB Resource Plan is created new resource directives are automatically created. These are the directives for automatic tasks, ORA$AUTOTASK, and the default directive, ORA$DEFAULT_PDB_DIRECTIVE, both shown in the screen print.
To create the CDB Directives one has to have logged in as sysdba. To enable this the logon screen has been updated but the user will have to have been assigned sysdba privilege.
There are four flat files that Scheduler FE Grid either creates or requires and these are as follows:-
The first file, the parameter file, contains all of the parameters which consist of the screen setup, the position of all of the items on the screen, the composition of the colours, the entries that make up the pull down lists, the security policy and alternative names and directories for the flat files except this one, the parameter file. More information on the technical content of this file can be found in the document "Scheduler FE - Technical Documentation on the Parameter File". This file is not modified by the system.
The second file contains the values that are passed from one session to the next. So it contains the screen position, the position of the screen break between the two sections of the split screen and the size of the main screen. It also contains the values set in the options menu screen. The final values it holds are the connection details. This flat file can be renamed and set to an alternative directory. See the above document for details on how to set this up. This file is written to when the user exits the system so write permission is required on the directory this file is set to.
The third file is a log of all the errors that are created. If problems occur this is the first place to look. The flat file is obviously writable and needs to be set in a directory with write permission. See the above document on how to set this up.
The fourth and final file is the audit file. This again needs to be in a write enabled directory and can be set off. Again the above document describes how this is to be set up. When set to on, which is the default, it will contain a list of all calls to the database changing the underlying scheduler. It lists all calls to the Oracle package DBMS_SCHEDULER. This flat file needs to be cleared out occasionally to prevent it growing to an unmanageable size.
The Scheduler FE Grid system has been designed to enable the simple operation of Oracle's scheduler system and to provide the Scheduling Manager with the information that will assist him in managing the Scheduling system. It displays the jobs that are expected to run thereby allowing the Scheduling Manager to identify jobs that he/she is not expecting to be there and to identify jobs that he/she expects to be running but is not. The investigations can then occur prior to the event and not after it thereby proactively finding solutions.
In addition it allows the Scheduling Manager to obtain an overview of the Scheduling system being able to see at a glance all of the users that currently have created objects, drilling down to seeing the specific object names that have been created by a user and then drilling down to see the details of a specific object.
This new Scheduler front end allows the Scheduling Manager easy access across multiple databases.