This section describes the setup that is needed to run ProGate.
The following setup of the Oracle source is needed:
Grant the user under which the migration will run with the following permissions:
GRANT CONNECT, RESOURCE TO PROGATE_USER; GRANT EXECUTE ON DBMS_LOGMNR TO PROGATE_USER; GRANT EXECUTE ON SYS.DBMS_CRYPTO TO PROGATE_USER; -- for procheck to compare LOB objects GRANT EXECUTE_CATALOG_ROLE TO PROGATE_USER; GRANT LOGMINING TO PROGATE_USER; GRANT SELECT ON V_$LOG TO PROGATE_USER; GRANT SELECT ON V_$LOGFILE TO PROGATE_USER; GRANT SELECT ON V_$LOGMNR_LOGS TO PROGATE_USER; GRANT SELECT ON V_$LOGMNR_CONTENTS TO PROGATE_USER; GRANT SELECT ON V_$LOGMNR_PARAMETERS TO PROGATE_USER; GRANT SELECT ON V_$ARCHIVED_LOG TO PROGATE_USER; GRANT SELECT ON V_$TRANSACTION TO PROGATE_USER; GRANT SELECT ON V_$DATABASE TO PROGATE_USER;
For procheck to work with an Oracle source, the following drivers are supported:
oracle, does not require third-party software.
godror, requires installation of the
Oracle Instant Client. Once the downloaded
archive is unpacked, add the path to the catalog to the LD_LIBRARY_PATH
environment variable:
LD_LIBRARY_PATH=<path_to_oracle_client>
No specific setup is needed for the Parquet-format file destination.
The following setup of the Postgres Pro destination is needed:
Install and enable the following extensions, available starting with Postgres Pro 16.4:
CREATE EXTENSION IF NOT EXISTS pgpro_bfile;
CREATE EXTENSION IF NOT EXISTS pgpro_sfile;
CREATE EXTENSION IF NOT EXISTS dbms_lob;
do
$$
BEGIN
PERFORM sf_initialize();
EXCEPTION WHEN OTHERS THEN
RAISE NOTICE 'already initialized';
end;
$$;
To migrate BFILE objects, create the same aliases as in the source DB:
do
$$
BEGIN
PERFORM bfile_directory_create('ALIAS1', '/tmp/alias1');
EXCEPTION WHEN OTHERS THEN
RAISE NOTICE 'alias1 already exists';
end;
$$;
do
$$
BEGIN
PERFORM bfile_directory_create('ALIAS2', '/tmp/alias2');
EXCEPTION WHEN OTHERS THEN
RAISE NOTICE 'alias2 already exists';
end;
$$;
Transfer the schema from the source DB using ora2pgpro.