Skip to content

Commit

Permalink
Merge pull request #1865 from EnterpriseDB/bugfix/epas/DF-262-dbms-jo…
Browse files Browse the repository at this point in the history 
…b-extension-update

DF-262 DBMS_JOB Extension update
  • Loading branch information
@drothery-edb
drothery-edb authored Sep 22, 2021
2 parents d1388a9 + b1b1caf commit bd3388f
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 12 deletions.
7 changes: 3 additions & 4 deletions ...s/docs/epas/11/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo

This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.

The following table lists the supported `DBMS_JOB` procedures:
Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:

| Function/Procedure | Return Type | Description |
| ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand All @@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
| `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a | Creates a job and stores its definition in the database. |
| `WHAT(job, what)` | n/a | Change the stored procedure run by a job. |

Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.

Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:

```text
CREATE EXTENSION pgagent;
CREATE EXTENSION dbms_job;
```

When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.
Expand Down
7 changes: 3 additions & 4 deletions ...s/docs/epas/12/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo

This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.

The following table lists the supported `DBMS_JOB` procedures:
Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:

| Function/Procedure | Return Type | Description |
| ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand All @@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
| `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a | Creates a job and stores its definition in the database. |
| `WHAT(job, what)` | n/a | Change the stored procedure run by a job. |

Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.

Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:

```text
CREATE EXTENSION pgagent;
CREATE EXTENSION dbms_job;
```

When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.
Expand Down
7 changes: 3 additions & 4 deletions ...s/docs/epas/13/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The `DBMS_JOB` package provides for the creation, scheduling, and managing of jo

This package relies on the `pgAgent` scheduler. By default, the Advanced Server installer installs `pgAgent`, but you must start the `pgAgent` service manually prior to using `DBMS_JOB`. If you attempt to use this package to schedule a job after un-installing `pgAgent, DBMS_JOB` will throw an error. `DBMS_JOB` verifies that `pgAgent` is installed, but does not verify that the service is running.

The following table lists the supported `DBMS_JOB` procedures:
Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures:

| Function/Procedure | Return Type | Description |
| ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand All @@ -23,12 +23,11 @@ The following table lists the supported `DBMS_JOB` procedures:
| `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a | Creates a job and stores its definition in the database. |
| `WHAT(job, what)` | n/a | Change the stored procedure run by a job. |

Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table above are supported.

Before using `DBMS_JOB`, a database superuser must create the `pgAgent` extension. Use the `psql` client to connect to a database and invoke the command:
Before using `DBMS_JOB`, a database superuser must create the `pgAgent` and `DBMS_JOB` extension. Use the `psql` client to connect to a database and invoke the command:

```text
CREATE EXTENSION pgagent;
CREATE EXTENSION dbms_job;
```

When and how often a job is run is dependent upon two interacting parameters – `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time when the job is to be executed. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.
Expand Down

0 comments on commit bd3388f

Please sign in to comment.