ici<\/a>. Il sera possible d’opter pour une version ant\u00e9rieure, mais, pour notre exemple, nous avons choisi la derni\u00e8re en date qui est la 20.0.<\/p>\nUne fois ces sources pouss\u00e9es sur notre serveur Debian, la suite consistera \u00e0 lancer le script Perl pour g\u00e9n\u00e9rer les scripts unix, les compiler puis les installer (comme nous l’avons fait pour DBI et DBD::Oracle).<\/p>\n
postgres@:~\/ora2pg$ cd ora2pg-20.0<\/span>\r\npostgres@:~\/ora2pg\/ora2pg-20.0$ perl Makefile.PL<\/strong><\/span>\r\nChecking if your kit is complete...<\/span>\r\nLooks good<\/span>\r\nGenerating a Unix-style Makefile<\/span>\r\nWriting Makefile for Ora2Pg<\/span>\r\nWriting MYMETA.yml and MYMETA.json<\/span>\r\nDone...<\/span>\r\n------------------------------------------------------------------------------<\/span>\r\nPlease read documentation at http:\/\/ora2pg.darold.net\/ before asking for help<\/span>\r\n------------------------------------------------------------------------------<\/span>\r\nNow type: make && make install<\/span><\/pre>\nLe script nous demande de passer un make<\/strong> puis un make install.<\/strong><\/p>\npostgres@:~\/ora2pg\/ora2pg-20.0$ make<\/strong><\/span>\r\ncp lib\/Ora2Pg\/PLSQL.pm blib\/lib\/Ora2Pg\/PLSQL.pm<\/span>\r\ncp lib\/Ora2Pg.pm blib\/lib\/Ora2Pg.pm<\/span>\r\ncp lib\/Ora2Pg\/GEOM.pm blib\/lib\/Ora2Pg\/GEOM.pm<\/span>\r\ncp lib\/Ora2Pg\/MySQL.pm blib\/lib\/Ora2Pg\/MySQL.pm<\/span>\r\ncp scripts\/ora2pg blib\/script\/ora2pg<\/span>\r\n\"\/usr\/bin\/perl\" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib\/script\/ora2pg<\/span>\r\ncp scripts\/ora2pg_scanner blib\/script\/ora2pg_scanner<\/span>\r\n\"\/usr\/bin\/perl\" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib\/script\/ora2pg_scanner<\/span>\r\nManifying 1 pod document<\/span><\/pre>\nAttention, le make install<\/strong> devra \u00eatre pass\u00e9 en “root” car nous avons rencontr\u00e9 des erreurs de type “permission denied” sur certains fichiers (dans \/etc notamment).<\/p>\nroot@:\/var\/lib\/postgresql\/ora2pg\/ora2pg-20.0# make install<\/strong><\/span>\r\nManifying 1 pod document<\/span>\r\nInstalling \/usr\/local\/share\/perl\/5.24.1\/Ora2Pg.pm<\/span>\r\nInstalling \/usr\/local\/share\/perl\/5.24.1\/Ora2Pg\/PLSQL.pm<\/span>\r\nInstalling \/usr\/local\/share\/perl\/5.24.1\/Ora2Pg\/GEOM.pm<\/span>\r\nInstalling \/usr\/local\/share\/perl\/5.24.1\/Ora2Pg\/MySQL.pm<\/span>\r\nInstalling \/usr\/local\/man\/man3\/ora2pg.3<\/span>\r\nInstalling \/usr\/local\/bin\/ora2pg<\/span>\r\nInstalling \/usr\/local\/bin\/ora2pg_scanner<\/span>\r\nInstalling default configuration file (ora2pg.conf.dist) to \/etc\/ora2pg<\/span>\r\nAppending installation info to \/usr\/local\/lib\/x86_64-linux-gnu\/perl\/5.24.1\/perllocal.pod<\/span><\/pre>\nOn donne les droits au user postgres pour \/etc\/ora2pg<\/p>\n
root@:\/var\/lib\/postgresql\/ora2pg\/ora2pg-20.0# chown -R postgres:postgres \/etc\/ora2pg<\/span><\/pre>\nAfin de s’assurer de la bonne connexion avec la base Oracle, nous irons faire un test via l’instant client de notre serveur Debian. Attention, ne pas oublier de sourcer les variables comme effectu\u00e9 au 1er paragraphe<\/p>\n
postgres@:~\/ora2pg\/DBD-Oracle-1.80$ export ORACLE_HOME=\/opt\/oracle\/instantclient_12_2\/ \r\npostgres@:~\/ora2pg\/DBD-Oracle-1.80$ export TNS_ADMIN=\/opt\/oracle\/instantclient_12_2\/ <\/span>\r\npostgres@:~\/ora2pg\/DBD-Oracle-1.80$ export PATH=$ORACLE_HOME:$PATH <\/span>\r\npostgres@:~\/ora2pg\/DBD-Oracle-1.80$ export LD_LIBRARY_PATH=$ORACLE_HOME:$LD_LIBRARY_PATH<\/span><\/pre>\nNous avons d\u00e9fini notre base nomm\u00e9e “SRC_DB” dans notre tnsnames.ora<\/p>\n
postgres@:~$ sqlplus capdata@SRC_DB<\/strong><\/span>\r\nSQL*Plus:\u00a0Release\u00a012.2.0.1.0\u00a0Production\u00a0on\u00a0Thu\u00a0Aug\u00a01\u00a016:29:29\u00a02019<\/span>\r\nCopyright\u00a0(c)\u00a01982,\u00a02016,\u00a0Oracle.\u00a0\u00a0All\u00a0rights\u00a0reserved.<\/span>\r\nEnter\u00a0password: ********<\/span>\r\nConnecte\u00a0a\u00a0:<\/span>\r\nOracle\u00a0Database\u00a011g\u00a0Release\u00a011.1.0.7.0\u00a0-\u00a064bit\u00a0Production<\/span>\r\nSQL>\u00a0exit<\/span>\r\nDeconnecte\u00a0de\u00a0Oracle\u00a0Database\u00a011g\u00a0Release\u00a011.1.0.7.0\u00a0-\u00a064bit\u00a0Production\r\n\r\n<\/span><\/pre>\nNous validons la connexion SQL Net vers la base Oracle, nous pouvons donc passer \u00e0 l’\u00e9tape configuration de ora2pg<\/p>\n
<\/p>\n
Configuration ora2pg<\/h2>\nLe fichier ora2pg.conf<\/span><\/h4>\nDurant l’installation de ora2pg, un fichier a \u00e9t\u00e9 g\u00e9n\u00e9r\u00e9 dans \/etc\/ora2pg<\/strong> nomm\u00e9 “ora2pg.conf.dist”.
\nIl est important de conserver celui ci et d’en faire une copie que l’on pourra \u00e9diter. Il sera question notamment dans ce fichier de renseigner les variables li\u00e9s \u00e0 la connexion Oracle.
\nNous rappelons que notre base source Oracle se nomme SRC_DB et que notre user est capdata. Nous exportons les donn\u00e9es du sch\u00e9ma Oracle nomm\u00e9 REF.<\/p>\nAttention dans le ORACLE_DSN, \u00e0 bien renseigner le SERVICE_NAME de la base et non le SID.<\/p>\n
postgres@:~$ cp \/etc\/ora2pg\/ora2pg.conf.dist \/etc\/ora2pg\/ora2pg.conf.REF<\/span>\r\npostgres@:~$ vi \/etc\/ora2pg\/ora2pg.conf.REF<\/span>\r\n...<\/span>\r\nORACLE_HOME\u00a0\u00a0\u00a0\u00a0\u00a0\/opt\/oracle\/instantclient_12_2\/<\/span>\r\nORACLE_DSN\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0dbi:Oracle:host=HOSTDB;sid=SRC_DB;port=1521<\/span>\r\nORACLE_USER\u00a0\u00a0\u00a0\u00a0\u00a0capdata<\/span>\r\nORACLE_PWD\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0********<\/span>\r\nSCHEMA\u00a0\u00a0GBMREF<\/span>\r\nUSE_RESERVED_WORDS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a01<\/span><\/pre>\nUn test pour v\u00e9rifier notre connexion \u00e0 la base Oracle. Attention, s’assurer que les variables d’environnement propres \u00e0 Oracle (ORACLE_HOME, TNS_ADMIN…) sont bien configur\u00e9es.<\/p>\n
postgres@:~\/ora2pg$ ora2pg -t SHOW_VERSION -c \/etc\/ora2pg\/ora2pg.conf.REF<\/strong><\/span>\r\nOracle\u00a0Database\u00a011g\u00a0Release\u00a011.1.0.7.0<\/span><\/pre>\nEstimation du co\u00fbt de migration<\/span><\/h4>\nIl sera possible d’estimer le co\u00fbt de la migration via l’option SHOW REPORT<\/strong> et –estmate_cost<\/strong> de ora2pg. Cela va nous indiquer si des t\u00e2ches manuelles devront \u00eatre effectu\u00e9es en fin de migration.<\/p>\npostgres@S:~\/ora2pg$ ora2pg -t SHOW_REPORT --estimate_cost -c \/etc\/ora2pg\/ora2pg.conf.REF<\/strong><\/span>\r\n[========================>] 89\/89 tables (100.0%) end of scanning.<\/span>\r\n[========================>] 11\/11 objects types (100.0%) end of objects auditing.<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nOra2Pg v20.0 - Database Migration Report<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nVersion Oracle Database 11g Release 11.1.0.7.0<\/span>\r\nSchema REF<\/span>\r\nSize 6351.56 MB<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nObject Number Invalid Estimated cost Comments Details<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nDATABASE LINK 0 0 0 Database links will be exported as SQL\/MED PostgreSQL's Foreign Data Wrapper (FDW) extensions using oracle_fdw.<\/span>\r\nGLOBAL TEMPORARY TABLE 0 0 0 Global temporary table are not supported by PostgreSQL and will not be exported. You will have to rewrite some application code to match the PostgreSQL temporary table behavior.<\/span>\r\nINDEX 50 0 6.7 17 index(es) are concerned by the export, others are automatically generated and will do so on PostgreSQL. Bitmap will be exported as btree_gin index(es) and hash index(es) will be exported as b-tree index(es) if any. Domain index are exported as b-tree but commented to be edited to mainly use FTS. Cluster, bitmap join and IOT indexes will not be exported at all. Reverse indexes are not exported too, you may use a trigram-based index (see pg_trgm) or a reverse() function based index and search. Use 'varchar_pattern_ops', 'text_pattern_ops' or 'bpchar_pattern_ops' operators in your indexes to improve search with the LIKE operator respectively into varchar, text or char columns. 17 b-tree index(es).<\/span>\r\nJOB 0 0 0 Job are not exported. You may set external cron job with them.<\/span>\r\nPACKAGE BODY 1 0 113.6 Total size of package code: 11374 bytes. Number of procedures and functions found inside those packages: 8. <\/span>\r\nSEQUENCE 16 0 1.6 Sequences are fully supported, but all call to sequence_name.NEXTVAL or sequence_name.CURRVAL will be transformed into NEXTVAL('sequence_name') or CURRVAL('sequence_name').<\/span>\r\nSYNONYM 6 0 1 SYNONYMs will be exported as views. SYNONYMs do not exists with PostgreSQL but a common workaround is to use views or set the PostgreSQL search_path in your session to access object outside the current schema. <\/span>\r\nTABLE 89 0 8.9 Total number of rows: 23632338. Top 10 of tables sorted by number of rows:. <\/span>\r\nTRIGGER 17 0 68.8 Total size of trigger code: 6054 bytes. <\/span>\r\nVIEW 10 0 10 Views are fully supported but can use specific functions.<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nTotal 189 0 210.60 210.60 cost migration units means approximatively 3 man-day(s). The migration unit was set to 5 minute(s)<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nMigration level : B-5<\/span>\r\n-------------------------------------------------------------------------------<\/span>\r\nMigration levels:<\/span>\r\n A - Migration that might be run automatically<\/span>\r\n B - Migration with code rewrite and a human-days cost up to 5 days<\/span>\r\n C - Migration with code rewrite and a human-days cost above 5 days<\/span>\r\nTechnical levels:<\/span>\r\n 1 = trivial: no stored functions and no triggers<\/span>\r\n 2 = easy: no stored functions but with triggers, no manual rewriting<\/span>\r\n 3 = simple: stored functions and\/or triggers, no manual rewriting<\/span>\r\n 4 = manual: no stored functions but with triggers or views with code rewriting<\/span>\r\n 5 = difficult: stored functions and\/or triggers with code rewriting<\/span>\r\n-------------------------------------------------------------------------------<\/span><\/pre>\nDans notre exemple, nous sommes dans un niveau B5, nous aurons donc du code \u00e0 r\u00e9\u00e9crire dans certaines proc\u00e9dures et\/ou triggers.<\/p>\n
Initialisation de l’arborescence du projet<\/span><\/h4>\nAfin de classer les diff\u00e9rents objets (tables, indexes, triggers….) \u00e0 exporter, la commande suivante sera \u00e0 lancer pour cr\u00e9er les r\u00e9pertoires qui constitueront l’arborescence compl\u00e8te du sch\u00e9ma. A noter que le nom du sch\u00e9ma \u00e0 exporter constitue le nom du projet (ici projet REF)<\/p>\n
postgres@:~\/ora2pg$ ora2pg --project_base \/var\/lib\/postgresql\/ora2pg --init_project REF --conf \/etc\/ora2pg\/ora2pg.conf.REF<\/strong><\/span>\r\nCreating project REF.<\/span>\r\n\/var\/lib\/postgresql\/ora2pg\/REF\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0schema\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0dblinks\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0directories\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0functions\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0grants\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0mviews\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0packages\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0partitions\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0procedures\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0sequences\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0synonyms\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0tables\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0tablespaces\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0triggers\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0types\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0views\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0sources\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0functions\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0mviews\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0packages\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0partitions\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0procedures\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0triggers\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0types\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0views\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0data\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0config\/<\/span>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0reports\/<\/span>\r\nGenerating\u00a0generic\u00a0configuration\u00a0file<\/span>\r\nCreating\u00a0script\u00a0export_schema.sh\u00a0to\u00a0automate\u00a0all\u00a0exports.<\/span>\r\nCreating\u00a0script\u00a0import_all.sh\u00a0to\u00a0automate\u00a0all\u00a0imports.<\/span>\r\n\r\n<\/pre>\nC’est \u00e0 cette \u00e9tape que ora2pg cr\u00e9e les 2 fichiers principaux que sont “export_schema<\/strong>.sh<\/strong>” et “import_all<\/strong>.sh<\/strong>” et qui constituent les op\u00e9rations d’export des donn\u00e9es Oracle et l’import des donn\u00e9es vers l’instance PostgreSQL.<\/p>\npostgres@:~\/ora2pg\/REF$ ls -l<\/span>\r\ntotal 40<\/span>\r\ndrwxr-xr-x 2 postgres postgres 4096 ao\u00fbt 8 14:48 config<\/span>\r\ndrwxr-xr-x 2 postgres postgres 4096 ao\u00fbt 8 15:02 data<\/span>\r\n-rwx------ 1 postgres postgres 2010 ao\u00fbt 1 16:51 export_schema.sh<\/strong><\/span>\r\n-rwx------ 1 postgres postgres 16061 ao\u00fbt 1 16:51 import_all.sh<\/strong><\/span>\r\ndrwxr-xr-x 2 postgres postgres 4096 ao\u00fbt 5 14:46 reports<\/span>\r\ndrwxr-xr-x 17 postgres postgres 4096 ao\u00fbt 1 16:51 schema<\/span>\r\ndrwxr-xr-x 10 postgres postgres 4096 ao\u00fbt 1 16:51 sources<\/span>\r\n\r\n<\/pre>\nExport du sch\u00e9ma Oracle<\/span><\/h2>\nC’est ce script “export_schema.sh” qui devra \u00eatre lanc\u00e9. Ce script se charge de g\u00e9n\u00e9rer les DDL de cr\u00e9ation des objets du sch\u00e9ma REF avec les conversions Oracle->PosgreSQL adapt\u00e9es. Aucun param\u00e8tre n’est \u00e0 renseigner.<\/p>\n
postgres@:~\/ora2pg\/GBMREF$ .\/export_schema.sh<\/strong><\/span>\r\n[========================>]\u00a089\/89\u00a0tables\u00a0(100.0%)\u00a0end\u00a0of\u00a0scanning.<\/span>\r\n[========================>]\u00a011\/11\u00a0objects\u00a0types\u00a0(100.0%)\u00a0end\u00a0of\u00a0objects\u00a0auditing.<\/span>\r\nRunning:\u00a0ora2pg\u00a0-p\u00a0-t\u00a0TABLE\u00a0-o\u00a0table.sql\u00a0-b\u00a0.\/schema\/tables\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span>\r\n[========================>]\u00a089\/89\u00a0tables\u00a0(100.0%)\u00a0end\u00a0of\u00a0scanning.<\/span>\r\n[========================>]\u00a089\/89\u00a0tables\u00a0(100.0%)\u00a0end\u00a0of\u00a0table\u00a0export.<\/span>\r\nRunning:\u00a0ora2pg\u00a0-p\u00a0-t\u00a0PACKAGE\u00a0-o\u00a0package.sql\u00a0-b\u00a0.\/schema\/packages\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span>\r\n[========================>]\u00a01\/1\u00a0packages\u00a0(100.0%)\u00a0end\u00a0of\u00a0output.<\/span>\r\nRunning:\u00a0ora2pg\u00a0-p\u00a0-t\u00a0VIEW\u00a0-o\u00a0view.sql\u00a0-b\u00a0.\/schema\/views\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span>\r\n[========================>]\u00a010\/10\u00a0views\u00a0(100.0%)\u00a0end\u00a0of\u00a0output.<\/span>\r\nRunning:\u00a0ora2pg\u00a0-p\u00a0-t\u00a0GRANT\u00a0-o\u00a0grant.sql\u00a0-b\u00a0.\/schema\/grants\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span>\r\nRunning:\u00a0ora2pg\u00a0-p\u00a0-t\u00a0SEQUENCE\u00a0-o\u00a0sequence.sql\u00a0-b\u00a0.\/schema\/sequences\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span>\r\n[========================>]\u00a016\/16\u00a0sequences\u00a0(100.0%)\u00a0end\u00a0of\u00a0output.<\/span>\r\n.......<\/span>\r\n\r\nTo\u00a0extract\u00a0data\u00a0use\u00a0the\u00a0following\u00a0command:<\/span>\r\nora2pg\u00a0-t\u00a0COPY\u00a0-o\u00a0data.sql\u00a0-b\u00a0.\/data\u00a0-c\u00a0.\/config\/ora2pg.conf<\/span><\/pre>\nOn remarque que ce script utilise un nouveau fichier de config qui est “.\/config\/ora2pg.conf<\/strong>“, celui ci est en fait copi\u00e9 depuis la source “\/etc\/ora2pg\/ora2pg.conf.REF<\/strong>“. Chaque commande pass\u00e9e est mentionn\u00e9 au fur et \u00e0 mesure qu’elle est lanc\u00e9e par le script shell “export_schema.sh<\/strong>“.<\/p>\nA la fin, le script donne la commande que nous devrons lancer pour importer les donn\u00e9es dans les tables. Cette partie \u00e9tant la plus longue, il sera peut \u00eatre n\u00e9cessaire de la lancer en “nohup” pour ne pas \u00eatre d\u00e9rang\u00e9 par une \u00e9ventuelle d\u00e9connexion. Le mode COPY pour PostgreSQL est g\u00e9n\u00e9r\u00e9 (ce qui s’apparente \u00e0 peu de chose pr\u00e8s \u00e0 du SQL Loader Oracle).<\/p>\n
Il sera \u00e9galement possible de parall\u00e9liser cette op\u00e9ration en passant le param\u00e8tre –parallel<\/strong><\/span> dans la commande.<\/p>\npostgres@S:~\/ora2pg\/REF$ nohup ora2pg -t COPY -o data.sql -b .\/data -c .\/config\/ora2pg.conf --parallel 2 &<\/strong><\/span>\r\npostgres@S:~\/ora2pg\/REF$ tail -f nohup.out<\/span>\r\n[========================>]\u00a089\/89\u00a0tables\u00a0(100.0%)\u00a0end\u00a0of\u00a0scanning.<\/span>\r\n
![\"twitter\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" "\\"Share")
<\/a>![\"linkedin\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" "\\"Share")
<\/a>![\"mail\"](\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" "\\"Share")
<\/a>![\"\"](\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/08\/elephant_charge.jpg\")
\u00a0![\"\"](\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/08\/oraclehq-300x199.jpg\")
<\/p>\n