v3.11.0

Add support for Oracle 11 (closes #14).

We changed the default configuration of the reverse proxy to use HTTPS.
This means you have to install a TLS/SSL certificate or create a self signed certificate, otherwise the web-server will refuse to start. To facilitate the installation of the certificate we added a new option --tls to the migrator configure command. Check out the FAQ for detailed information how to install a TLS/SSL certificate.

migrator configure --tls self-signed-cert       Generate self-signed TLS/SSL certificate
migrator configure --tls cert:<file-location>   Install TLS/SSL certificate
migrator configure --tls key:<file-location>    Install private key of TLS/SSL certificate

Attention
If you upgrade from a previous Migrator version you have to create the TLS/SSL certificate after upgrading to the new version, before restarting the new Migrator.

./migrator update
./migrator upgrade
# Don't forget the create or install a TLS/SSL certificate
./migrator configure --tls self-signed-cert
./migrator up

Add support for secured communication (TCPS) access to Oracle databases. For details check our FAQ - How do I configure TCPS for Oracle databases?.

Read meta-data of additional Oracle database object types: jobs and operators

Users may provide a custom Data Query, thus manipulating the SELECT statement executed on the source database to migrate the data.

• Migrate the table partially by filtering rows with WHERE
• Migrate only the table structure but no data (WHERE ROWID < 0)
• You want to keep the table structure, but not the data of a specific column (see screenshot above)
• Retrieve (and thus insert) the data in a specific ORDER BY
• Convert the column data of an unsupported data type into a string representation which can be “cast” into a valid PostgreSQL type via the COPY statement

Improve output for erroneous SQL execution when reading Oracle meta-data.