Documentation installation

This documentation describes how the scheduler server software must be installed.

Pre install

The following is needed before we can start installing the scheduler server software.

Back to top 

Files needed for the server installation

Place the zipfile in a (new) directory and unzip it. The following files must be present after unzipping the server software.

admin.sql
body.sql
createusr.sql
install.sql
model.sql
private.sql
queue.sql
readme.txt
schuser.sql
script.sql
so_administrator.bdy
so_administrator.spc
so_client.bdy
so_client.spc
so_error.bdy
so_error.spc
so_interface.bdy
so_interface.spc
so_queue.bdy
so_queue.spc
so_task.bdy
so_task.spc
so_run.bdy
so_run.spc
so_script.bdy
so_script.spc
so_server.bdy
so_server.spc
so_shared.bdy
so_shared.spc
so_vw_queues.sql
so_vw_scheduler_log.sql
so_vw_scheduler_privileges.sql
so_vw_scheduler_queues.sql
so_vw_scheduler_users.sql
so_vw_scheduler_user_views.sql
so_vw_script_parameters.sql
so_vw_script_parameter_values.sql
so_vw_script_privileges.sql
so_vw_scripts.sql
so_vw_task_output.sql
so_vw_task_parameters.sql
so_vw_tasks.sql
so_vw_task_volume.sql
spec.sql
views.sql
  
Back to top 

Dbms_support package

The scheduler server program needs the oracle DBMS_SUPPORT package. Normally this package is not installed.
The installation of this package can be done by running the SQL*Plus script dbmssupp.sql. This file can be found in the oracle server rdbms/admin directory. For the Oracle Database 10g Express Edition (XE) release 10.2.0 on linux the server directory is /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
Go to this directory, login as sysdba and run the script dbmssupp.sql.

$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Beta on Wed Feb 7 14:36:48 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Beta

SQL> @dbmssupp.sql

Package created.


Package body created.

SQL> 
  
Back to top 

Installation user

An oracle database user is needed under which the plsql scheduler server software is going to be installed. Login as oracle sysdba and make sure you're in the directory where you have unzipped the server software.

It is possible to install the server software under an existing account. The same steps must be followed as if a new account was created.
Do not use the SYS, SYSTEM or any other pre installed oracle account for installation.

Login as sysdba with the command

sqlplus / as sysdba

When succesfully connected run the SQL*Plus script createusr.sql for creating the scheduler server user. The scripts needs four parameters.

If an existing account is used a new default tablespace will be set for this user.

If an error occurs when running the SQL*Plus script createusr.sql solve the problem and start the script again.
When everything works fine end the sql session by exit. The following is an installation example; the new oracle user used here is PLSCH with the password PLSCH (not visible) and tablespace USERS.

$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Beta on Fri Nov 3 17:10:01 2006

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Beta

SQL> @createusr

Create user needed for installation plsql scheduler
User will be given extra privileges
Script must be run as sysdba

Username                   : PLSCH
Password                   :
Reuse existing account [Y] : N
Default tablespace [USERS] :

> create user plsch identified by plsch;
> create role plsch_scripts;
> grant plsch_scripts to plsch with admin option;
> alter user plsch default tablespace users;
> alter user plsch quota unlimited on users;
> grant select on dba_jobs_running to plsch;
> grant alter system to plsch;
> grant alter session to plsch;
> grant create session to plsch;
> grant execute any procedure to plsch;
> grant create any synonym to plsch;
> grant create public synonym to plsch;
> grant create procedure to plsch;
> grant create sequence to plsch;
> grant create table to plsch;
> grant create trigger to plsch;
> grant create view to plsch;
> grant drop any synonym to plsch;
> grant drop public synonym to plsch;
> grant select on sys.dba_ddl_locks to plsch;
> grant select on sys.dba_lock to plsch;
> grant select on sys.dba_synonyms to plsch;
> grant select on sys.v_$db_pipes to plsch;
> grant select on sys.dba_role_privs to plsch;
> grant execute on sys.dbms_support to plsch;
> grant execute on sys.dbms_pipe to plsch;
> grant execute on sys.dbms_lock to plsch;
> grant select on sys.v_$session to plsch;
> grant select on sys.v_$instance to plsch;
> grant select on sys.v_$database to plsch;

PL/SQL procedure successfully completed.

SQL> exit
 
Back to top 

Server installation

After creating (or reuse an existing) an oracle user login using SQL*Plus: sqlplus [the account] When succesfully connected run the installation SQL*Plus script install.sql.

@install.sql

No errors should occur during running this script, if so correct it. The output is saved in the file install.out.
Next is an example of the installation output (not all is displayed):

$ sqlplus plsch

SQL*Plus: Release 10.2.0.1.0 - Beta on Fri Nov 3 17:29:45 2006

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:

Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Beta

SQL> @install.sql
Start installation scheduler
Creating Sequence 'SCHEDULER_LOG_SEQ_ID'

Sequence created.

Creating Sequence 'SCHEDULER_VIEWS_SEQ_ID'

Sequence created.

...... etc ......

Create administrator (scheduler owner)

PL/SQL procedure successfully completed.

Creating scheduler server queue

PL/SQL procedure successfully completed.

Creating server script

PL/SQL procedure successfully completed.

SQL>
  
Back to top 

Public installation

It is possible to install multiple scheduler instances in one database. If this is the case the SQL*Plus script private.sql must also be run.
After running the script for each scheduler user private synonyms are created by the scheduler server, otherwise public synonyms are created on the first time the server is started.

SQL> @private

Create multiple plsql scheduler installations in one database.
Script must be run for each scheduler under the installation user.

Multiple installations [Y] : Y

Multiple private installations set.

PL/SQL procedure successfully completed.
SQL>
  

If already a scheduler server was installed for which the SQL*Plus script private.sql was not executed and a second scheduler installation is needed follow the next three steps.

  1. Stop the server.
  2. Run the SQL*Plus script private.sql for the already existing scheduler and the new installed scheduler.
  3. Start all servers.

The server process will drop the public synonyms and creates for each scheduler user private synonyms.

Back to top 

Oracle parameters

On a default oracle installation there is a maximum number of background processes that can be started. The server uses one background process for each activated scheduler task.

The server process is also a scheduler task.

The maximum number of background processes is determined by the oracle parameter JOB_QUEUE_PROCESSES. Increase the value of this parameter if the scheduler is used for running more concurrent processes; the total number of scheduler tasks that must be able to run parallel.
Changing the value can be done on the fly.

$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.1.0 - Beta on Tue Jan 16 20:59:52 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Beta

SQL>show parameter job_queue_processes

NAME_COL_PLUS_SHOW_PARAM TYPE         VALUE_COL_PLUS_SHOW_PARAM
======================== ============ =========================
job_queue_processes      integer      20

SQL>alter system set job_queue_processes=30;

System altered.

SQL> exit
  

There are two extra parameters that must be set if a large number of background sessions are needed.

The PROCESSES and SESSIONS parameters must be set in the oracle pfile or spfile.

Back to top 

Client software

The scheduler client program is a full graphical user interface (GUI) covering all scheduler functionality. This program is for free and no license is needed.
Read the scheduler client installation how to download and install it.
After starting up the client connect with the installation user and start the server. If this succeeds the installation is finished and the scheduler is ready for usage.
The next step is to register scheduler users, create scheduler scripts and schedule scheduler tasks.

Back to top