Product

IntegrationsAll integrations

Featured

Platforms

Scripting

Business apps

Data & reporting

Cloud & file transfer

Resources

Migrations

JUMP Migration ToolAutomate most of your scheduler migration

Migrate fromAll migrations

Featured

Redwood

Broadcom

SMA

IBM / HCL

Independent

Free & native tools

JUMPJUMP eligible: convert your jobs with a free Dry Run

Free trial

JAMS Oracle Database integration

Oracle Database Job Scheduling and Stored Procedure Automation

JAMS Scheduler runs Oracle stored procedures as jobs, captures their dbms_output in the log, and makes them wait on jobs on any platform.

Request a Demo

Execution method

OracleStoredProc

Pick from a list

Stored procedures load from the database

Also adds

Oracle sequence tasks and Oracle Query parameters

What JAMS Scheduler Runs in Oracle Database

Pick the connection, choose the stored procedure from the list, and optionally write its output to a file. Schedules, dependencies, and alerts work like any other job.

Stored procedures

OracleStoredProc

Runs an Oracle stored procedure. Include its dbms_output in the JAMS log, or keep it out.

Stored procedures

OracleStoredProc

Runs an Oracle stored procedure. Include its dbms_output in the JAMS log, or keep it out.

Sequence steps

Oracle sequence tasks

Run Oracle steps inside a sequence job alongside other tasks.

Sequence steps

Oracle sequence tasks

Run Oracle steps inside a sequence job alongside other tasks.

Query parameters

Oracle Query parameter

Add an Oracle Query parameter to any job.

Query parameters

Oracle Query parameter

Add an Oracle Query parameter to any job.

How JAMS Scheduler Connects to Oracle Database

Store the connection once as an Oracle connection in the JAMS Connection Store and reuse it across jobs. Older setups that keep the connection string in execution method parameters still work.

Each job uses two credentials: the Oracle login on the connection, and the Windows account the job runs as.

Requirements

Install

LOAD/ASSEMBLY=JAMSOracleIntegration in JAMSDBA

Connection

An Oracle connection in the Connection Store, recommended

Credentials

An Oracle login and a Windows run-as account

Read the OracleStoredProc documentation

Oracle Jobs in a Cross-Platform Workflow

A stored procedure can wait for a file transfer to land, load the data, then start an Oracle EBS or Banner job.

When the procedure fails, you get the same alert as any other job.

Oracle FAQ

Can JAMS Scheduler pick a stored procedure from the database?

Yes. Once the connection is set, the Procedure field lists the stored procedures you can run.

Can an Oracle job wait on a job on another platform?

Yes. Oracle jobs take the same dependencies as any other job, whether the upstream job runs on Windows, Linux, z/OS, or in an ERP.

Can I see dbms_output from the procedure?

Yes. Turn on Include dbms_output in JAMS log file, and the output shows on the job’s Log File tab in the Monitor view.

Documentation

Connections to database servers

Working with credentials

Related integrations

Oracle EBS

JAMS Scheduler runs Oracle EBS concurrent programs and request sets from drop-downs that read straight from EBS, then sequences them with jobs outside EBS.

PeopleSoft

JAMS Scheduler sends work to the PeopleSoft Process Scheduler, then lets you monitor, cancel, or restart it from PeopleSoft or JAMS. PeopleSoft jobs share dependencies with everything else you run.

JDE

JAMS Scheduler runs JD Edwards EnterpriseOne reports on Windows or Linux, on the same schedules and dependencies as the rest of your batch. A UBE can wait for a SQL Server load to finish, then start the file transfer that ships its output.

Banner

JAMS Scheduler submits Banner jobs straight through the Banner Oracle database and pulls their .log and .lis output into the job log. Banner jobs share schedules and dependencies with everything else you run, from SQL Server loads to file transfers.