GO Loader Aviation 1.2 is here! Take a look at what's new.
Skip to end of metadata
Go to start of metadata

Database Schemas required for GO Publisher Workflow

In order for GO Publisher Workflow to run, a number of database pre-requisites need to be prepared. This is the customers responsibility and is outlined below.

Pre-requisites

The SQL on this page is Oracle database specific. Alterations may need to be made to run the SQL on other platforms.

A database user (and table space) is required for GO Publisher Workflow to connect to.

Specifically the following tablespace, user and permissions are required:

  1. Create a table space GPWORKFLOW
  2. Create a user GPWORKFLOW
  3. Grant permission to the GPWORKFLOW user on the table space.

 

The schema required by GO Publisher Workflow is referred to as GPWORKFLOW throughout this documentation, however you can choose a different schema name if you wish to do so.

Before running the below script, please review and edit it as required:

-- Create user GPWORKFLOW 
-----------------------------
-- Create Tablespace BIGFILE
-----------------------------
CREATE BIGFILE TABLESPACE "GPWORKFLOW"
  DATAFILE 'C:\oracle\ORCL1\GPWORKFLOW.DBF' SIZE 1G AUTOEXTEND ON NEXT
100M MAXSIZE UNLIMITED;
-----------------------------
-- Create User
-----------------------------
CREATE USER GPWORKFLOW IDENTIFIED BY GPWORKFLOW default tablespace GPWORKFLOW;
ALTER USER GPWORKFLOW quota unlimited ON users;
 
GRANT CONNECT, RESOURCE, UNLIMITED TABLESPACE, SELECT ANY TABLE, UPDATE ANY TABLE, INSERT ANY TABLE to GPWORKFLOW;
COMMIT;

The SQL on this page is Oracle database specific.

Further Reading

Take note of the GPWorkflow Control Tables and the Publish Job Configuration Tables.


  • No labels