GOE
A simple and flexible way to copy data from an Oracle Database to Google BigQuery.
Downloading GOE
At present GOE is a command line tool. Alongside installing the Python package we also require some extra artefacts, everything you need to run the software is provided in a versioned package which can be downloaded from here or alternatively built locally.
Offload Home
In addition to the GOE software we need a supporting directory tree called the Offload Home. This is identified using the OFFLOAD_HOME environment variable. In this directory we keep configuration files, logs and the GOE software if you choose not to run scripts directly out of the cloned repo. Offload Home will also typically contain a Python virtual environment into which the GOE package and dependencies will be installed, you can run these out of the repository directory but, for separation of duties purposes, may choose to keep the source code away from users of the tool.
Installation From a Package
Installing the GOE Python Package
- Copy the package to the target host, this may not be the same host the repository was cloned to.
- Create the Offload Home directory, for example:
OFFLOAD_HOME=/opt/goe/offload
mkdir -p ${OFFLOAD_HOME}
- Extract the package into the new directory (replace
<goe-version>below):
tar --directory=${OFFLOAD_HOME}/../ -xf goe_<goe-version>.tar.gz
- Create and activate a Python virtual environment, for example:
cd $OFFLOAD_HOME
python3 -m venv .venv && . .venv/bin/activate
- Install the GOE Python package:
cd $OFFLOAD_HOME
python3 -m pip install goe-framework==<goe-version>
or use the bundled wheel file:
cd $OFFLOAD_HOME
GOE_WHEEL="goe_framework-<goe-version>-py3-none-any.whl"
python3 -m pip install lib/${GOE_WHEEL}
Configuration File
Create offload.env in the Offload Home. This file contains the necessary configuration specific to your environment:
cp ${OFFLOAD_HOME}/conf/oracle-bigquery-offload.env.template ${OFFLOAD_HOME}/conf/offload.env
vi ${OFFLOAD_HOME}/conf/offload.env
Variables you will want to pay attention to are:
- ORA_CONN
- ORA_ADM_PASS
- ORA_APP_PASS
- BIGQUERY_DATASET_LOCATION
- OFFLOAD_FS_CONTAINER
- OFFLOAD_FS_PREFIX
If using Google Managed Service for Apache Spark:
- GOOGLE_DATAPROC_CLUSTER
- GOOGLE_DATAPROC_SERVICE_ACCOUNT
- GOOGLE_DATAPROC_REGION
If using Google Managed Service for Apache Spark serverless:
- GOOGLE_DATAPROC_BATCHES_VERSION
- GOOGLE_DATAPROC_SERVICE_ACCOUNT
- GOOGLE_DATAPROC_REGION
- GOOGLE_DATAPROC_BATCHES_SUBNET
Install Database Objects
To install supporting database objects you need access to a database admin account that can create users, grant them system privileges and create objects in the schemas created. SYSTEM has been used in the example below but this is not a necessity:
cd ${OFFLOAD_HOME}/setup
sqlplus system@yourhost:1521/yoursvc
@install_offload
In a SQL*Plus session change the passwords for the GOE_ADM and GOE_APP users to match the values in the offload.env configuration file:
alter user goe_adm identified by ...;
alter user goe_app identified by ...;
Building a Custom Package
If you want to test with the latest commits that have not yet been included in a GitHub release you can build a custom package from the repository.
Prepare the Host/Cloned Repository
Debian prerequisites:
sudo apt-get -y install make python3-venv
java --version || sudo apt-get -y install default-jre
RHEL variant prerequisites:
sudo dnf -y install make
java --version || sudo dnf -y install java-11-openjdk
Install SBT in order to build the Spark Listener:
curl -fL https://github.com/coursier/coursier/releases/latest/download/cs-x86_64-pc-linux.gz | gzip -d > cs && chmod +x cs && ./cs setup && rm ./cs
. ~/.bash_profile
Make a GOE Package
To create a package which contains all required artifacts for running GOE commands use the make target below:
make clean && make package
Install for Development
To create a Python virtual environment and install all required dependencies into the repository directory:
make clean && make install-dev
source ./.venv/bin/activate
PYTHONPATH=${PWD}/src
This enables you to develop and/or run tests.
Note only the Python dependencies for Oracle and BigQuery are installed by default. To install all optional dependencies you can run this command:
make install-dev-extras
Supporting Infrastructure
GOE requires access to cloud storage and Spark. For a Google Cloud installation this is described here: Google Cloud Platform Setup for a BigQuery Target
Running Commands
Activate the GOE Python virtual environment:
source ./.venv/bin/activate
Checking connectivity:
cd bin
./connect
Running an Offload:
cd bin
./offload -t my.table -x
Tests
See Tests
Release files for goe-framework 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| goe_framework-1.1.0.tar.gz | 641.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| goe_framework-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / goe_framework-1.1.0.tar.gz
| Download URL | goe_framework-1.1.0.tar.gz |
|---|---|
| Size | 641.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f42c36018e4b5efd305c86c83b59f4e1d19343f01bb525182318c5e60929e91
|
|
BLAKE2b-256 checksum How to use checksums |
c4b02f8dfcb88a062f3922ba93d9ec3277ff9d6d83ecb25a505a72c57e6c8537
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.
Transparency logRelease files / goe_framework-1.1.0-py3-none-any.whl
| Download URL | goe_framework-1.1.0-py3-none-any.whl |
|---|---|
| Size | 794.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c73032fe3327782782673b70c36bad400a0c66e842f0b97f7889074c7dc72d3a
|
|
BLAKE2b-256 checksum How to use checksums |
e83584254cd5fbf4af59107a412e90b627704b384f0f5a6ee39e06b7db4629e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 22, 2026.
Transparency log