For the Postgres Pro Enterprise destination, to use the appropriate data types, install and enable the supporting 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() ON CONFLICT DO NOTHING;
EXCEPTION WHEN OTHERS THEN
    RAISE NOTICE 'already initialized';
end;
$$;

With superuser permissions, grant the following permission to the user under which procopy or prosync connects to the destination database:

GRANT SET ON PARAMETER session_replication_role

This user is specified in the destination.dsn or destination.username configuration parameter.

To migrate BFILE objects, create the same aliases as in the source DB:

do
$$
    BEGIN
        PERFORM bfile_directory_create('ALIAS1', '/tmp/alias1') ON CONFLICT DO NOTHING;
    EXCEPTION WHEN OTHERS THEN
        RAISE NOTICE 'alias1 already exists';
    end;
$$;

do
$$
    BEGIN
        PERFORM bfile_directory_create('ALIAS2', '/tmp/alias2') ON CONFLICT DO NOTHING;
    EXCEPTION WHEN OTHERS THEN
        RAISE NOTICE 'alias2 already exists';
    end;
$$;

Transfer the schema from the source DB using ora2pgpro.