Subversion Repositories Sigmater

Rev

Details | Last modification | View Log | RSS feed

Rev Author Line No. Line
84 Andrea 1
 
2
####################  Ora2Pg Configuration file   #####################
3
 
4
# Support for including a common config file that may contain any
5
# of the following configuration directives.
6
#IMPORT	common.conf
7
 
8
#------------------------------------------------------------------------------
9
# INPUT SECTION (Oracle connection or input file)
10
#------------------------------------------------------------------------------
11
 
12
# Set this directive to a file containing PL/SQL Oracle Code like function,
13
# procedure or a full package body to prevent Ora2Pg from connecting to an
14
# Oracle database end just apply his conversion tool to the content of the
15
# file. This can only be used with the following export type: PROCEDURE,
16
# FUNCTION or PACKAGE. If you don't know what you do don't use this directive.
17
#INPUT_FILE	ora_plsql_src.sql
18
 
19
# Set the Oracle home directory
20
ORACLE_HOME	/usr/lib/oracle/11.2/client64
21
 
22
# Set Oracle database connection (datasource, user, password)
23
ORACLE_DSN	dbi:Oracle:host=172.25.102.41;sid=sigmater
24
ORACLE_USER	srm310
25
ORACLE_PWD	syssrm
26
 
27
# Set this to 1 if you connect as simple user and can not extract things
28
# from the DBA_... tables. It will use tables ALL_... This will not works
29
# with GRANT export, you should use an Oracle DBA username at ORACLE_USER
30
USER_GRANTS     0
31
 
32
# Trace all to stderr
33
DEBUG		0
34
 
35
# This directive can be used to send an initial command to Oracle, just after
36
# the connection. For example to unlock a policy before reading objects.
37
ORA_INITIAL_COMMAND
38
 
39
 
40
#------------------------------------------------------------------------------
41
# SCHEMA SECTION (Oracle schema to export and use of schema in PostgreSQL)
42
#------------------------------------------------------------------------------
43
 
44
# Export Oracle schema to PostgreSQL schema
45
EXPORT_SCHEMA	0
46
 
47
# Oracle schema/owner to use
48
SCHEMA		SRM310
49
 
50
# Enable/disable the CREATE SCHEMA SQL order at starting of the output file.
51
# It is enable by default and concern on TABLE export type.
52
CREATE_SCHEMA	0
53
 
54
# Enable this directive to force Oracle to compile schema before exporting code.
55
# This will ask to Oracle to validate the PL/SQL that could have been invalidate
56
# after a export/import for example. If the value is 1 ora2pg will execute:
57
# DBMS_UTILITY.compile_schema(schema => sys_context('USERENV', 'SESSION_USER'));
58
# but if you provide the name of a particular schema it will use the following
59
# command: DBMS_UTILITY.compile_schema(schema => 'schemaname');
60
COMPILE_SCHEMA	0
61
 
62
# PostreSQL search path schema to use. Can be a comma delimited list,
63
# for example: users_schema,public will result in the following PostgreSQL 
64
# schema path: SET search_path = users_schema,public;
65
# The default is the value defined for the connection user in PostgreSQL.
66
#PG_SCHEMA	
67
PG_SCHEMA registrazione	
68
 
69
# Use this directive to add a specific schema to the search path to look
70
# for PostGis functions.
71
#POSTGIS_SCHEMA		
72
 
73
# Allow to add a comma separated list of system user to exclude from 
74
# from Oracle extraction. Oracle have many of them following the modules
75
# installed. By default it will suppress all object owned by the following
76
# system users:
77
#        CTXSYS,DBSNMP,EXFSYS,LBACSYS,MDSYS,MGMT_VIEW,OLAPSYS,ORDDATA,OWBSYS,
78
#        ORDPLUGINS,ORDSYS,OUTLN,SI_INFORMTN_SCHEMA,SYS,SYSMAN,SYSTEM,WK_TEST,
79
#        WKSYS,WKPROXY,WMSYS,XDB,APEX_PUBLIC_USER,DIP,FLOWS_020100,FLOWS_030000,
80
#        FLOWS_040100,FLOWS_FILES,MDDATA,ORACLE_OCM,SPATIAL_CSW_ADMIN_USR,
81
#        SPATIAL_WFS_ADMIN_USR,XS$NULL,PERFSTAT,SQLTXPLAIN,DMSYS,TSMSYS,WKSYS,
82
#        APEX_040200,DVSYS,OJVMSYS,GSMADMIN_INTERNAL,APPQOSSYS
83
# Other list of users set to this directive will be added to this list.
84
#SYSUSERS	OE,HR
85
 
86
 
87
#------------------------------------------------------------------------------
88
# ENCODING SECTION (Define client encoding at Oracle and PostgreSQL side)
89
#------------------------------------------------------------------------------
90
 
91
# Enforce default language setting following the Oracle database encoding. This
92
# may be used with multibyte characters like UTF8. Here are the default values
93
# used by Ora2Pg, you may not change them unless you have problem with this
94
# encoding. This will set $ENV{NLS_LANG} to the given value.
95
#NLS_LANG	AMERICAN_AMERICA.AL32UTF8
96
# This will set $ENV{NLS_NCHAR} to the given value.
97
#NLS_NCHAR	AL32UTF8
98
 
99
# By default PostgreSQL client encoding is automatically set to UTF8 to avoid
100
# encoding issue. If you have changed the value of NLS_LANG you might have to
101
# change  the encoding of the PostgreSQL client.
102
#CLIENT_ENCODING	UTF8
103
 
104
 
105
#------------------------------------------------------------------------------
106
# EXPORT SECTION (Export type and filters)
107
#------------------------------------------------------------------------------
108
 
109
# Type of export. Values can be the following keyword:
110
#	TABLE		Export tables, constraints, indexes, ...
111
#	PACKAGE		Export packages
112
#	INSERT		Export data from table as INSERT statement
113
#	COPY		Export data from table as COPY statement
114
#	VIEW		Export views
115
#	GRANT		Export grants
116
#	SEQUENCE	Export sequences
117
#	TRIGGER		Export triggers
118
#	FUNCTION	Export functions
119
#	PROCEDURE	Export procedures
120
#	TABLESPACE	Export tablespace (PostgreSQL >= 8 only)
121
#	TYPE		Export user defined Oracle types
122
#	PARTITION	Export range or list partition (PostgreSQL >= v8.4)
123
#	FDW		Export table as foreign data wrapper tables
124
#	MVIEW		Export materialized view as snapshot refresh view
125
#       QUERY		Convert Oracle SQL queries from a file.
126
#       KETTLE		Generate XML ktr template files to be used by Kettle.
127
 
128
#TYPE		FUNCTION, PROCEDURE, TRIGGER, PACKAGE
129
TYPE		COPY
130
 
131
# Set this to 1 if you don't want to export comments associated to tables and
132
# column definitions. Default is enabled.
133
DISABLE_COMMENT         0
134
 
135
# Set which object to export from. By default Ora2Pg export all objects.
136
# Value must be a list of object name or regex separated by space. Note
137
# that regex will not works with 8i database, use % placeholder instead
138
# Ora2Pg will use the LIKE operator. There is also some extended use of
139
# this directive, see chapter "Limiting object to export" in documentation.
140
#ALLOW		TABLE_TEST
141
#ALLOW		WS_APPLICAZIONI, WS_CONF_AGP, WS_EVENTI, WS_FILTRI, WS_LIVELLI, WS_LOGO_ENTE_UTENTE, WS_LOG_LOGIN, WS_RAGGR_ENTI, WS_RAGG_COMUNI
142
#ALLOW		WS_ABILITAZIONI, WS_ABILITAZIONI_TERMINALE, WS_ATTRIBUTI_APPLICAZIONE, WS_ATTRIBUTI_FUNZIONE
143
ALLOW		WS_ISTANZE_APPL, WS_PROFILI_EVENTO, WS_PROFILI_FUNZIONE, WS_PROFILI_UTENTE
144
 
145
# Set which object to exclude from export process. By default none. Value
146
# must be a list of object name or regexp separated by space. Note that regex
147
# will not works with 8i database, use % placeholder instead Ora2Pg will use
148
# the NOT LIKE operator. There is also some extended use of this directive,
149
# see chapter "Limiting object to export" in documentation.
150
#EXCLUDE	OTHER_TABLES
151
 
152
# Set which view to export as table. By default none. Value must be a list of
153
# view name or regexp separated by space. If the object name is a view and the
154
# export type is TABLE, the view will be exported as a create table statement.
155
# If export type is COPY or INSERT, the corresponding data will be exported.
156
#VIEW_AS_TABLE	VIEW_NAME
157
 
158
# When exporting GRANTs you can specify a comma separated  list of objects
159
# for which privilege will be exported. Default is export for all objects.
160
# Here are the possibles values TABLE, VIEW, MATERIALIZED VIEW, SEQUENCE,
161
# PROCEDURE, FUNCTION, PACKAGE BODY, TYPE, SYNONYM, DIRECTORY. Only one object
162
# type is allowed at a time. For example set it to TABLE if you just want to
163
# export privilege on tables. You can use the -g option to overwrite it.
164
# When used this directive prevent the export of users unless it is set to
165
# USER. In this case only users definitions are exported.
166
#GRANT_OBJECT    TABLE
167
 
168
# By default Ora2Pg will export your external table as file_fdw tables. If
169
# you don't want to export those tables at all, set the directive to 0.
170
EXTERNAL_TO_FDW		0
171
 
172
# Add a TRUNCATE TABLE instruction before loading data on COPY and INSERT
173
# export. When activated, the instruction will be added only if there's no
174
# global DELETE clause or one specific to the current table (see bellow).
175
TRUNCATE_TABLE	0
176
 
177
# Support for include a DELETE FROM ... WHERE clause filter before importing
178
# data and perform a delete of some lines instead of truncatinf tables.
179
# Value is construct as follow: TABLE_NAME[DELETE_WHERE_CLAUSE], or
180
# if you have only one where clause for all tables just put the delete
181
# clause as single value. Both are possible too. Here are some examples:
182
#DELETE  1=1	# Apply to all tables and delete all tuples
183
#DELETE	TABLE_TEST[ID1='001']	# Apply only on table TABLE_TEST
184
#DELETE	TABLE_TEST[ID1='001' OR ID1='002] DATE_CREATE > '2001-01-01' TABLE_INFO[NAME='test']
185
# The last applies two different delete where clause on tables TABLE_TEST and
186
# TABLE_INFO and a generic delete where clause on DATE_CREATE to all other tables.
187
# If TRUNCATE_TABLE is enabled it will be applied to all tables not covered by
188
# the DELETE definition.
189
 
190
# When enabled this directive forces ora2pg to export all tables, index
191
# constraints, and indexes using the tablespace name defined in Oracle database.
192
# This works only with tablespaces that are not TEMP, USERS and SYSTEM.
193
USE_TABLESPACE		0
194
 
195
# Enable this directive to reorder columns and minimized the footprint
196
# on disk, so that more rows fit on a data page, which is the most important
197
# factor for speed. Default is same order than in Oracle table definition, 
198
# that should be enough for most usage.
199
REORDERING_COLUMNS	0
200
 
201
# Support for include a WHERE clause filter when dumping the contents
202
# of tables. Value is construct as follow: TABLE_NAME[WHERE_CLAUSE], or
203
# if you have only one where clause for each table just put the where
204
# clause as value. Both are possible too. Here are some examples:
205
#WHERE  1=1	# Apply to all tables
206
#WHERE	TABLE_TEST[ID1='001']	# Apply only on table TABLE_TEST
207
#WHERE	TABLE_TEST[ID1='001' OR ID1='002] DATE_CREATE > '2001-01-01' TABLE_INFO[NAME='test']
208
# The last applies two different where clause on tables TABLE_TEST and
209
# TABLE_INFO and a generic where clause on DATE_CREATE to all other tables
210
#WHERE WS_UTENTI[USERNAME <> 'admin']
211
WHERE WS_ISTANZE_APPL[istanza_appl_id  <> 62]
212
 
213
# Sometime you may want to extract data from an Oracle table but you need a
214
# a custom query for that. Not just a "SELECT * FROM table" like Ora2Pg does
215
# but a more complex query. This directive allows you to override the query
216
# used by Ora2Pg to extract data. The format is TABLENAME[SQL_QUERY].
217
# If you have multiple tables to extract by replacing the Ora2Pg query, you can
218
# define multiple REPLACE_QUERY lines.
219
#REPLACE_QUERY	EMPLOYEES[SELECT e.id,e.fisrtname,lastname FROM EMPLOYEES e JOIN EMP_UPDT u ON (e.id=u.id AND u.cdate>'2014-08-01 00:00:00')]
220
 
221
#------------------------------------------------------------------------------
222
# FULL TEXT SEARCH SECTION (Control full text search export behaviors)
223
#------------------------------------------------------------------------------
224
 
225
# Force Ora2Pg to translate Oracle Text indexes into PostgreSQL indexes using
226
# pg_trgm extension. Default is to translate CONTEXT indexes into FTS indexes
227
# and CTXCAT indexes using pg_trgm. Most of the time using pg_trgm is enough,
228
# this is why this directive stand for.
229
#
230
CONTEXT_AS_TRGM		0
231
 
232
# By default Ora2Pg creates a function-based index to translate Oracle Text
233
# indexes. 
234
#    CREATE INDEX ON t_document
235
#                 USING gin(to_tsvector('french', title));
236
# You will have to rewrite the CONTAIN() clause using to_tsvector(), example:
237
#    SELECT id,title FROM t_document
238
#                    WHERE to_tsvector(title)) @@ to_tsquery('search_word');
239
#
240
# To force Ora2Pg to create an extra tsvector column with a dedicated triggers
241
# for FTS indexes, disable this directive. In this case, Ora2Pg will add the
242
# column as follow: ALTER TABLE t_document ADD COLUMN tsv_title tsvector;
243
# Then update the column to compute FTS vectors if data have been loaded before
244
#     UPDATE t_document SET tsv_title =
245
#                       to_tsvector('french', coalesce(title,''));
246
# To automatically update the column when a modification in the title column
247
# appears, Ora2Pg adds the following trigger:
248
#
249
# CREATE FUNCTION tsv_t_document_title() RETURNS trigger AS $$
250
# BEGIN
251
#        IF TG_OP = 'INSERT' OR new.title != old.title THEN
252
#                new.tsv_title :=
253
#                to_tsvector('french', coalesce(new.title,''));
254
#        END IF;
255
#        return new;
256
# END
257
# $$ LANGUAGE plpgsql;
258
# CREATE TRIGGER trig_tsv_t_document_title BEFORE INSERT OR UPDATE
259
#  ON t_document
260
#  FOR EACH ROW EXECUTE PROCEDURE tsv_t_document_title();
261
#
262
# When the Oracle text index is defined over multiple column, Ora2Pg will use
263
# setweight() to set a weight in the order of the column declaration.
264
#
265
FTS_INDEX_ONLY	1
266
 
267
# Use this directive to force text search configuration to use. When it is not
268
# set, Ora2Pg will autodetect the stemmer used by Oracle for each index and
269
# pg_catalog.english if nothing is found. 
270
271
#FTS_CONFIG	pg_catalog.french
272
 
273
# If you want to perform your text search in an accent insensitive way, enable
274
# this directive. Ora2Pg will create an helper function over unaccent() and
275
# creates the pg_trgm indexes using this function. With FTS Ora2Pg will
276
# redefine your text search configuration, for example:
277
#
278
#	CREATE TEXT SEARCH CONFIGURATION fr (COPY = pg_catalog.french); 
279
#	ALTER TEXT SEARCH CONFIGURATION fr
280
#		ALTER MAPPING FOR hword, hword_part, word WITH unaccent, french_stem;
281
#
282
# When enabled, Ora2pg will create the wrapper function:
283
#
284
#	CREATE OR REPLACE FUNCTION unaccent_immutable(text)
285
#	RETURNS text AS
286
#	$$
287
#		SELECT public.unaccent('public.unaccent', )
288
#	$$  LANGUAGE sql IMMUTABLE
289
#	    COST 1;
290
#
291
# indexes are exported as follow:
292
#
293
#	CREATE INDEX t_document_title_unaccent_trgm_idx ON t_document 
294
#        	USING gin (unaccent_immutable(title) gin_trgm_ops);
295
#
296
# In your queries you will need to use the same function in the search to
297
# be able to use the function-based index. Example:
298
#
299
#	SELECT * FROM t_document
300
#		WHERE unaccent_immutable(title) LIKE '%donnees%';
301
#
302
USE_UNACCENT		0
303
 
304
# Same as above but call lower() in the unaccent_immutable() function:
305
#
306
#      CREATE OR REPLACE FUNCTION unaccent_immutable(text)
307
#      RETURNS text AS
308
#      $$
309
#          SELECT lower(public.unaccent('public.unaccent', ));
310
#      $$ LANGUAGE sql IMMUTABLE;
311
#
312
USE_LOWER_UNACCENT	0
313
 
314
#------------------------------------------------------------------------------
315
# CONSTRAINT SECTION (Control constraints export and import behaviors)
316
#------------------------------------------------------------------------------
317
 
318
# Support for turning off certain schema features in the postgres side
319
# during schema export. Values can be : fkeys, pkeys, ukeys, indexes, checks
320
# separated by a space character.
321
# fkeys		: turn off foreign key constraints
322
# pkeys		: turn off primary keys
323
# ukeys		: turn off unique column constraints
324
# indexes	: turn off all other index types
325
# checks	: turn off check constraints
326
#SKIP	fkeys pkeys ukeys indexes checks
327
 
328
# By default, primary key names in the source database are ignored, and
329
# default key names are created in the target database. If this is set to true,
330
# primary key names are kept.
331
KEEP_PKEY_NAMES 0
332
 
333
# Enable this directive if you want to add primary key definitions inside the
334
# create table statements. If disabled (the default) primary key definition
335
# will be added with an alter table statement. Enable it if you are exporting
336
# to GreenPlum PostgreSQL database.
337
PKEY_IN_CREATE		0
338
 
339
# This directive allow you to add an ON UPDATE CASCADE option to a foreign
340
# key when a ON DELETE CASCADE is defined or always. Oracle do not support
341
# this feature, you have to use trigger to operate the ON UPDATE CASCADE.
342
# As PostgreSQL has this feature, you can choose how to add the foreign
343
# key option. There is three value to this directive: never, the default
344
# that mean that foreign keys will be declared exactly like in Oracle.
345
# The second value is delete, that mean that the ON UPDATE CASCADE option
346
# will be added only if the ON DELETE CASCADE is already defined on the
347
# foreign Keys. The last value, always, will force all foreign keys to be
348
# defined using the update option.
349
FKEY_ADD_UPDATE		never
350
 
351
# When exporting tables, Ora2Pg normally exports constraints as they are;
352
# if they are non-deferrable they are exported as non-deferrable.
353
# However, non-deferrable constraints will probably cause problems when
354
# attempting to import data to PostgreSQL. The following option set to 1
355
# will cause all foreign key constraints to be exported as deferrable
356
FKEY_DEFERRABLE	0
357
 
358
# In addition when exporting data the DEFER_FKEY option set to 1 will add
359
# a command to defer all foreign key constraints during data export and
360
# the import will be done in a single transaction. This will work only if
361
# foreign keys have been exported as deferrable and you are not using direct
362
# import to PostgreSQL (PG_DSN is not defined). Constraints will then be
363
# checked at the end of the transaction. This directive can also be enabled 
364
# if you want to force all foreign keys to be created as deferrable and
365
# initially deferred during schema export (TABLE export type).
366
DEFER_FKEY	0
367
 
368
# If deferring foreign keys is not possible du to the amount of data in a
369
# single transaction, you've not exported foreign keys as deferrable or you
370
# are using direct import to PostgreSQL, you can use the DROP_FKEY directive.
371
# It will drop all foreign keys before all data import and recreate them at
372
# the end of the import.
373
DROP_FKEY	0
374
 
375
 
376
#------------------------------------------------------------------------------
377
# TRIGGERS AND SEQUENCES SECTION (Control triggers and sequences behaviors)
378
#------------------------------------------------------------------------------
379
 
380
# Disables alter of sequences on all tables in COPY or INSERT mode.
381
# Set to 1 if you want to disable update of sequence during data migration.
382
DISABLE_SEQUENCE	0
383
 
384
# Disables triggers on all tables in COPY or INSERT mode. Available modes 
385
# are USER (user defined triggers) and ALL (includes RI system 
386
# triggers). Default is 0 do not add SQL statement to disable trigger.
387
# If you want to disable triggers during data migration, set the value to
388
# USER if your are connected as non superuser and ALL if you are connected
389
# as PostgreSQL superuser. A value of 1 is equal to USER.
390
DISABLE_TRIGGERS 0
391
 
392
 
393
#------------------------------------------------------------------------------
394
# OBJECT MODIFICATION SECTION (Control objects structure or name modifications)
395
#------------------------------------------------------------------------------
396
 
397
# You may wish to just extract data from some fields, the following directives
398
# will help you to do that. Works only with export type INSERT or COPY
399
# Modify output from the following tables(fields separate by space or comma)
400
#MODIFY_STRUCT	TABLE_TEST(dico,dossier)
401
 
402
# You may wish to change table names during data extraction, especally for
403
# replication use. Give a list of tables separate by space as follow.
404
#REPLACE_TABLES	ORIG_TB_NAME1:NEW_TB_NAME1 ORIG_TB_NAME2:NEW_TB_NAME2 
405
 
406
# You may wish to change column names during data extraction, especially for
407
# replication use. Give a list of tables and columns separate by space as
408
# follow.
409
#REPLACE_COLS	TB_NAME(ORIG_COLNAME1:NEW_COLNAME1,ORIG_COLNAME2:NEW_COLNAME2)
410
 
411
# By default all object names are converted to lower case, if you
412
# want to preserve Oracle object name as-is set this to 1. Not recommended
413
# unless you always quote all tables and columns on all your scripts.
414
PRESERVE_CASE	0
415
 
416
# Add the given value as suffix to index names. Useful if you have indexes
417
# with same name as tables. Not so common but it can help.
418
#INDEXES_SUFFIX		_idx
419
 
420
# Enable this directive to rename all indexes using tablename_columns_names.
421
# Could be very useful for database that have multiple time the same index name
422
# or that use the same name than a table, which is not allowed by PostgreSQL
423
# Disabled by default.
424
INDEXES_RENAMING	0
425
 
426
# Operator classes text_pattern_ops, varchar_pattern_ops, and bpchar_pattern_ops
427
# support B-tree indexes on the corresponding types. The difference from the
428
# default operator classes is that the values are compared strictly character by
429
# character rather than according to the locale-specific collation rules. This
430
# makes these operator classes suitable for use by queries involving pattern
431
# matching expressions (LIKE or POSIX regular expressions) when the database
432
# does not use the standard "C" locale. If you enable, with value 1, this will
433
# force Ora2Pg to export all indexes defined on varchar2() and char() columns
434
# using those operators. If you set it to a value greater than 1 it will only
435
# change indexes on columns where the charactere limit is greater or equal than
436
# this value. For example, set it to 128 to create these kind of indexes on
437
# columns of type varchar2(N) where N >= 128.
438
USE_INDEX_OPCLASS	0
439
 
440
# Enable this directive if you want that your partition table name will be
441
# exported using the parent table name. Disabled by default. If you have
442
# multiple partitioned table, when exported to PostgreSQL some partitions
443
# could have the same name but different parent tables. This is not allowed,
444
# table name must be unique. 
445
PREFIX_PARTITION	0
446
 
447
# If you don't want to reproduce the partitioning like in Oracle and want to
448
# export all partitionned Oracle data into the main single table in PostgreSQL
449
# enable this directive. Ora2Pg will export all data into the main table name.
450
# Default is to use partitionning, Ora2Pg will export data from each partition
451
# and import them into the PostgreSQL dedicated partition table.
452
DISABLE_PARTITION	0
453
 
454
# Activating this directive will force Ora2Pg to add WITH (OIDS) when creating
455
# tables or views as tables. Default is same as PostgreSQL, disabled.
456
WITH_OID		0
457
 
458
# Allow escaping of column name using Oracle reserved words.
459
ORA_RESERVED_WORDS	audit,comment
460
 
461
# Enable this directive if you have tables or column names that are a reserved
462
# word for PostgreSQL. Ora2Pg will double quote the name of the object. 
463
USE_RESERVED_WORDS	0
464
 
465
#------------------------------------------------------------------------------
466
# OUTPUT SECTION (Control output to file or PostgreSQL database)
467
#------------------------------------------------------------------------------
468
 
469
# Define the following directive to send export directly to a PostgreSQL
470
# database. This will disable file output.
471
#PG_DSN		dbi:Pg:dbname=test_db;host=localhost;port=5432
472
#PG_USER	test
473
#PG_PWD		test
474
PG_DSN		dbi:Pg:dbname=S3_vda;host=172.25.102.42;port=5432
475
PG_USER	s3_vda
476
PG_PWD		s3
477
 
478
# By default all output is dump to STDOUT if not send directly to postgresql
479
# database (see above). Give a filename to save export to it. If you want
480
# a Gzip'd compressed file just add the extension .gz to the filename (you
481
# need perl module Compress::Zlib from CPAN). Add extension .bz2 to use Bzip2
482
# compression.
483
OUTPUT		output_copy_ws_enti.sql
484
 
485
# Base directory where all dumped files must be written
486
#OUTPUT_DIR	/var/tmp
487
 
488
# Path to the bzip2 program. See OUTPUT directive above.
489
BZIP2	
490
 
491
# Allow object constraints to be saved in a separate file during schema export.
492
# The file will be named CONSTRAINTS_OUTPUT. Where OUTPUT is the value of the
493
# corresponding configuration directive. You can use .gz xor .bz2 extension to
494
# enable compression. Default is to save all data in the OUTPUT file. This 
495
# directive is usable only with TABLE export type.
496
FILE_PER_CONSTRAINT	0
497
 
498
# Allow indexes to be saved in a separate file during schema export. The file
499
# will be named INDEXES_OUTPUT. Where OUTPUT is the value of the corresponding
500
# configuration directive. You can use the .gz, .xor, or .bz2 file extension to 
501
# enable compression. Default is to save all data in the OUTPUT file. This 
502
# directive is usable only with TABLE or TABLESPACE export type.  With the 
503
# TABLESPACE export, it is used to write "ALTER INDEX ... TABLESPACE ..." into 
504
# a separate file named TBSP_INDEXES_OUTPUT that can be loaded at end of the 
505
# migration after the indexes creation to move the indexes.
506
FILE_PER_INDEX		0
507
 
508
# Allow data export to be saved in one file per table/view. The files
509
# will be named as tablename_OUTPUT. Where OUTPUT is the value of the
510
# corresponding configuration directive. You can use .gz xor .bz2
511
# extension to enable compression. Default is to save all data in one
512
# file. This is usable only during INSERT or COPY export type.
513
FILE_PER_TABLE	0
514
 
515
# Allow function export to be saved in one file per function/procedure.
516
# The files will be named as funcname_OUTPUT. Where OUTPUT is the value
517
# of the corresponding configuration directive. You can use .gz xor .bz2
518
# extension to enable compression. Default is to save all data in one
519
# file. It is usable during FUNCTION, PROCEDURE, TRIGGER and PACKAGE
520
# export type.
521
FILE_PER_FUNCTION	0
522
 
523
# By default Ora2Pg will force Perl to use utf8 I/O encoding. This is done through
524
# a call to the Perl pragma:
525
#
526
#    use open ':utf8';
527
#
528
# You can override this encoding by using the BINMODE directive, for example you
529
# can set it to :locale to use your locale or iso-8859-7, it will respectively use
530
# 
531
#    use open ':locale';
532
#    use open ':encoding(iso-8859-7)';
533
# 
534
# If you have change the NLS_LANG in non UTF8 encoding, you might want to set this
535
# directive. See http://perldoc.perl.org/5.14.2/open.html for more information.
536
# Most of the time, you might leave this directive commented.
537
#BINMODE		utf8
538
 
539
# Set it to 0 to not include the call to \set ON_ERROR_STOP ON in all SQL
540
# scripts. By default this order is always present.
541
STOP_ON_ERROR		1
542
 
543
# Enable this directive to use COPY FREEZE instead of a simple COPY to
544
# export data with rows already frozen. This is intended as a performance
545
# option for initial data loading. Rows will be frozen only if the table
546
# being loaded has been created or truncated in the current subtransaction.
547
# This will only works with export to file and when -J or ORACLE_COPIES is
548
# not set or default to 1. It can be used with direct import into PostgreSQL
549
# under the same condition but -j or JOBS must also be unset or default to 1.
550
COPY_FREEZE		0
551
 
552
#------------------------------------------------------------------------------
553
# TYPE SECTION (Control type behaviors and redefinitions)
554
#------------------------------------------------------------------------------
555
 
556
# If you're experiencing problems in data type export, the following directive
557
# will help you to redefine data type translation used in Ora2pg. The syntax is
558
# a comma separated list of "Oracle datatype:Postgresql data type". Here are the
559
# data type that can be redefined and their default value. If you want to
560
# replace a type with a precision and scale you need to escape the coma with
561
# a backslash. For example, if you want to replace all NUMBER(*,0) into bigint
562
# instead of numeric(38)add the following:
563
# 	DATA_TYPE	NUMBER(*\,0):bigint
564
# Here is the default replacement for all Oracle's types. You don't have to
565
# recopy all type conversion but just the one you want to rewrite.
566
#DATA_TYPE	DATE:timestamp,LONG:text,LONG RAW:bytea,CLOB:text,NCLOB:text,BLOB:bytea,BFILE:bytea,RAW:bytea,ROWID:oid,FLOAT:double precision,DEC:decimal,DECIMAL:decimal,DOUBLE PRECISION:double precision,INT:numeric,INTEGER:numeric,REAL:real,SMALLINT:smallint,BINARY_FLOAT:double precision,BINARY_DOUBLE:double precision,TIMESTAMP:timestamp,XMLTYPE:xml,BINARY_INTEGER:integer,PLS_INTEGER:integer,TIMESTAMP WITH TIME ZONE:timestamp with time zone,TIMESTAMP WITH LOCAL TIME ZONE:timestamp with time zone
567
 
568
# If set to 1 replace portable numeric type into PostgreSQL internal type.
569
# Oracle data type NUMBER(p,s) is approximatively converted to real and
570
# float PostgreSQL data type. If you have monetary fields or don't want
571
# rounding issues with the extra decimals you should preserve the same
572
# numeric(p,s) PostgreSQL data type. Do that only if you need very good
573
# precision because using numeric(p,s) is slower than using real or double.
574
PG_NUMERIC_TYPE	1
575
 
576
# If set to 1 replace portable numeric type into PostgreSQL internal type.
577
# Oracle data type NUMBER(p) or NUMBER are converted to smallint, integer
578
# or bigint PostgreSQL data type following the length of the precision. If
579
# NUMBER without precision are set to DEFAULT_NUMERIC (see bellow).
580
PG_INTEGER_TYPE	1
581
 
582
# NUMBER() without precision are converted by default to bigint only if
583
# PG_INTEGER_TYPE is true. You can overwrite this value to any PG type,
584
# like integer or float.
585
DEFAULT_NUMERIC bigint
586
 
587
# Set it to 0 if you don't want to export milliseconds from Oracle timestamp
588
# columns. Timestamp will be formated with to_char(..., 'YYYY-MM-DD HH24:MI:SS')
589
# Enabling this directive, the default, format is 'YYYY-MM-DD HH24:MI:SS.FF'.
590
ENABLE_MICROSECOND      1
591
 
592
# If you want to replace some columns as PostgreSQL boolean define here a list
593
# of tables and column separated by space as follows. You can also give a type
594
# and a precision to automatically convert all fields of that type as a boolean.
595
# For example: NUMBER:1 or CHAR:1 will replace any field of type number(1) or
596
# char(1) as a boolean in all exported tables.
597
#REPLACE_AS_BOOLEAN	TB_NAME1:COL_NAME1 TB_NAME1:COL_NAME2 TB_NAME2:COL_NAME2
598
 
599
# Use this to add additional definitions of the possible boolean values in Oracle
600
# field. You must set a space separated list of TRUE:FALSE values. BY default:
601
#BOOLEAN_VALUES	yes:no y:n 1:0 true:false enabled:disabled
602
 
603
# When Ora2Pg find a "zero" date: 0000-00-00 00:00:00 it is replaced by a NULL.
604
# This could be a problem if your column is defined with NOT NULL constraint.
605
# If you can not remove the constraint, use this directive to set an arbitral
606
# date that will be used instead. You can also use -INFINITY if you don't want
607
# to use a fake date.
608
#REPLACE_ZERO_DATE	1970-01-01 00:00:00
609
 
610
# Some time you need to force the destination type, for example a column
611
# exported as timestamp by Ora2Pg can be forced into type date. Value is
612
# a comma-separated list of TABLE:COLUMN:TYPE structure. If you need to use
613
# comma or space inside type definition you will have to backslash them.
614
#MODIFY_TYPE     TABLE1:COL3:varchar,TABLE1:COL4:decimal(9\,6)
615
 
616
#------------------------------------------------------------------------------
617
# GRANT SECTION (Control priviledge and owner export)
618
#------------------------------------------------------------------------------
619
 
620
# Set this to 1 to replace default password for all extracted user
621
# during GRANT export
622
GEN_USER_PWD	0
623
 
624
# By default the owner of database objects is the one you're using to connect
625
# to PostgreSQL. If you use an other user (e.g. postgres) you can force
626
# Ora2Pg to set the object owner to be the one used in the Oracle database by
627
# setting the directive to 1, or to a completely different username by setting
628
# the directive value # to that username. 
629
FORCE_OWNER	0
630
 
631
 
632
#------------------------------------------------------------------------------
633
# DATA SECTION (Control data export behaviors)
634
#------------------------------------------------------------------------------
635
 
636
# Extract data by bulk of DATA_LIMIT tuples at once. Default 10000. If you set
637
# a high value be sure to have enough memory if you have million of rows.
638
DATA_LIMIT	10000
639
 
640
 
641
# When Ora2Pg detect a table with some BLOB it will automatically reduce the
642
# value of this directive by dividing it by 10 until his value is below 1000.
643
# You can control this value by setting BLOB_LIMIT. Exporting BLOB use lot of
644
# ressources, setting it to a too high value can produce OOM.
645
#BLOB_LIMIT	500
646
 
647
# By default all data that are not of type date or time are escaped. If you
648
# experience any problem with that you can set it to 1 to disable it. This
649
# directive is only used during a COPY export type.
650
# See STANDARD_CONFORMING_STRINGS for enabling/disabling escape with INSERT
651
# statements.
652
NOESCAPE	0
653
 
654
# This directive may be used if you want to change the default isolation
655
# level of the data export transaction. Default is now to set the level
656
# to a serializable transaction to ensure data consistency. Here are the
657
# allowed value of this directive: readonly, readwrite, serializable and
658
# committed (read committed).
659
TRANSACTION	serializable
660
 
661
# This controls whether ordinary string literals ('...') treat backslashes
662
# literally, as specified in SQL standard. This was the default before Ora2Pg
663
# v8.5 so that all strings was escaped first, now this is currently on, causing
664
# Ora2Pg to use the escape string syntax (E'...') if this parameter is not
665
# set to 0. This is the exact behavior of the same option in PostgreSQL.
666
# This directive is only used during INSERT export to build INSERT statements.
667
# See NOESCAPE for enabling/disabling escape in COPY statements.
668
STANDARD_CONFORMING_STRINGS	1
669
 
670
# Use this directive to set the database handle's 'LongReadLen' attribute to
671
# a value that will be the larger than the expected size of the LOB. The default
672
# is 1MB witch may not be enough to extract BLOB objects. If the size of the LOB
673
# exceeds the 'LongReadLen' DBD::Oracle will return a 'ORA-24345: A Truncation'
674
# error.  Default: 1023*1024 bytes. Take a look at this page to learn more:
675
# http://search.cpan.org/~pythian/DBD-Oracle-1.22/Oracle.pm#Data_Interface_for_Persistent_LOBs
676
#
677
# Important note: If you increase the value of this directive take care that 
678
# DATA_LIMIT will probably needs to be reduced. Even if you only have a 1MB blob
679
# trying to read 10000 of them (the default DATA_LIMIT) all at once will require
680
# 10GB of memory. You may extract data from those table separately and set a
681
# DATA_LIMIT to 500 or lower, otherwise you may experience some out of memory.
682
#LONGREADLEN	1047552
683
 
684
# If you want to bypass the 'ORA-24345: A Truncation' error, set this directive
685
# to 1, it will truncate the data extracted to the LongReadLen value.
686
#LONGTRUNCOK	0
687
 
688
# Disable this if you don't want to load full content of BLOB and CLOB and use
689
# LOB locators instead. This is usefull to not having to set LONGREADLEN. Note
690
# that this will not improve speed of BLOB export as most of the time is always
691
# consumed by the bytea escaping and in this case export is done line by line
692
# and not by chunk of DATA_LIMIT rows. For more information on how it works, see
693
# http://search.cpan.org/~pythian/DBD-Oracle-1.74/lib/DBD/Oracle.pm#Data_Interface_for_LOB_Locators
694
# Default is enabled, it will not use LOB locators for backward compatibility.
695
NO_LOB_LOCATOR  1
696
 
697
# Use getStringVal() instead of getClobVal() for XML data export. Default is
698
# enabled for backward compatibility.
699
XML_PRETTY	0
700
 
701
# Enable this directive if you want to continue direct data import on error.
702
# When Ora2Pg receives an error in the COPY or INSERT statement from PostgreSQL
703
# it will log the statement to a file called TABLENAME_error.log in the output
704
# directory and continue to next bulk of data. Like this you can try to fix the
705
# statement and manually reload the error log file. Default is disabled: abort
706
# import on error.
707
LOG_ON_ERROR		0
708
 
709
# If you want to convert CHAR(n) from Oracle into varchar(n) or text under
710
# PostgreSQL, you might want to do some triming on the data. By default
711
# Ora2Pg will auto-detect this conversion and remove any withspace at both
712
# leading and trailing position. If you just want to remove the leadings
713
# character, set the value to LEADING. If you just want to remove the trailing
714
# character, set the value to TRAILING. Default value is BOTH.
715
TRIM_TYPE		BOTH
716
 
717
# The default triming character is space, use the directive bellow if you need
718
# to change the character that will be removed. For example, set it to - if you
719
# have leading - in the char(n) field. To use space as triming charger, comment
720
# this directive, this is the default value.
721
#TRIM_CHAR		-
722
 
723
# Internal timestamp retrieves from custom type are extracted in the following
724
# format: 01-JAN-77 12.00.00.000000 AM. It is impossible to know the exact century
725
# that must be used, so by default any year below 49 will be added to 2000
726
# and others to 1900. You can use this directive to change this default value.
727
# this is only relevant if you have user defined type with a column timestamp.
728
INTERNAL_DATE_MAX	49
729
 
730
#------------------------------------------------------------------------------
731
# PERFORMANCES SECTION (Control export/import performances)
732
#------------------------------------------------------------------------------
733
 
734
# Multiprocess support. This directive replace the obsolete THREAD_COUNT
735
# variable. Ora2Pg now use fork() to do parallel process instead of Perl
736
# threads. This directive should defined the number of parallel connection
737
# to PostgreSQL for direct data migration. The limit is the number of cores
738
# on your machine. This is useful if PostgreSQL is the bottleneck. COPIES
739
JOBS		1
740
 
741
# Multiprocess support. This directive should defined the number of parallel
742
# connection to Oracle when extracting data. The limit is the number of cores
743
# on your machine. This is useful if Oracle is the bottleneck. Take care that
744
# this directive can only be used if there is a column defined in DEFINED_PK.
745
ORACLE_COPIES	1
746
 
747
# Multiprocess support. This directive should defined the number of tables
748
# in parallel data extraction. The limit is the number of cores on your machine.
749
# Ora2Pg will open one database connection for each parallel table extraction.
750
# This directive, when upper than 1, will invalidate ORACLE_COPIES but not JOBS.
751
# Note that this directive when set upper that 1 will also automatically enable
752
# the FILE_PER_TABLE directive if your are exporting to files.
753
PARALLEL_TABLES	1
754
 
755
# Multiprocess support. This directive is used to split the select queries
756
# between the different connections to Oracle if ORA_COPIES is used. Ora2Pg
757
# will extract data with the following prepare statement:
758
# 	SELECT * FROM TABLE WHERE MOD(COLUMN, $ORA_COPIES) = ?
759
# Where $ORA_COPIES is the total number of cores used to extract data and set
760
# with ORA_COPIES directive, and ? is the current core used at execution time.
761
# This means that Ora2Pg needs to know the numeric column to use in this query.
762
# If this column is a real, float, numeric or decimal, you must add the ROUND()
763
# function with the column to round the value to the nearest integer.
764
#DEFINED_PK	TABLE:COLUMN TABLE:ROUND(COLUMN)
765
 
766
# Enabling this directive force Ora2Pg to drop all indexes on data import
767
# tables, except automatic index on primary key, and recreate them at end
768
# of data import. This may improve speed a lot during a fresh import.
769
DROP_INDEXES	0
770
 
771
# Specifies whether transaction commit will wait for WAL records to be written
772
# to disk before the command returns a "success" indication to the client. This
773
# is the equivalent to set synchronous_commit directive of postgresql.conf file.
774
# This is only used when you load data directly to PostgreSQL, the default is
775
# off to disable synchronous commit to gain speed at writing data. Some modified
776
# versions of PostgreSQL, like Greenplum, do not have this setting, so in this
777
# case set this directive to 1, ora2pg will not try to change the setting.
778
SYNCHRONOUS_COMMIT	0
779
 
780
 
781
#------------------------------------------------------------------------------
782
# PLSQL SECTION (Control SQL and PL/SQL to PLPGSQL rewriting behaviors)
783
#------------------------------------------------------------------------------
784
 
785
# If the above configuration directive is not enough to validate your PL/SQL code
786
# enable this configuration directive to allow export of all PL/SQL code even if
787
# it is marked as invalid. The 'VALID' or 'INVALID' status applies to functions,
788
# procedures, packages and user defined types.
789
EXPORT_INVALID	0
790
 
791
# Enable PLSQL to PLPSQL conversion. This is a work in progress, feel
792
# free modify/add you own code and send me patches. The code is under
793
# function plsql_toplpgsql in Ora2PG/PLSQL.pm. Default enabled.
794
PLSQL_PGSQL	0
795
 
796
# Ora2Pg can replace all conditions with a test on NULL by a call to the
797
# coalesce() function to mimic the Oracle behavior where empty field are
798
# considered equal to NULL. Ex: (field1 IS NULL) and (field2 IS NOT NULL) will
799
# be replaced by (coalesce(field1::text, '') = '') and (field2 IS NOT NULL AND
800
# field2::text <> ''). You might want this replacement to be sure that your
801
# application will have the same behavior but if you have control on you app
802
# a better way is to change it to transform empty string into NULL because
803
# PostgreSQL makes the difference.
804
NULL_EQUAL_EMPTY	0
805
 
806
# Force empty_clob() and empty_blob() to be exported as NULL instead as empty
807
# string for the first one and \\x for the second. If NULL is allowed in your
808
# column this might improve data export speed if you have lot of empty lob.
809
EMPTY_LOB_NULL		0
810
 
811
# If you don't want to export package as schema but as simple functions you
812
# might also want to replace all call to package_name.function_name. If you
813
# disable the PACKAGE_AS_SCHEMA directive then Ora2Pg will replace all call
814
# to package_name.function_name() by package_name_function_name(). Default
815
# is to use a schema to emulate package.
816
PACKAGE_AS_SCHEMA	0
817
 
818
# Enable this directive if the rewrite of Oracle native syntax (+) of
819
# OUTER JOIN is broken. This will force Ora2Pg to not rewrite such code,
820
# default is to try to rewrite simple form of rigth outer join for the
821
# moment.
822
REWRITE_OUTER_JOIN	0
823
 
824
# By default Ora2pg rewrite add_month(), add_year() and date_trunc() functions
825
# set it to 0 to not translate those functions if it breaks code. 
826
DATE_FUNCTION_REWRITE	1
827
 
828
#------------------------------------------------------------------------------
829
# ASSESSMENT SECTION (Control migration assessment behaviors)
830
#------------------------------------------------------------------------------
831
 
832
# Activate the migration cost evaluation. Must only be used with SHOW_REPORT,
833
# FUNCTION, PROCEDURE, PACKAGE and QUERY export type. Default is disabled.
834
# Note that enabling this directive will force PLSQL_PGSQL activation.
835
ESTIMATE_COST		0
836
 
837
# Set the value in minutes of the migration cost evaluation unit. Default
838
# is five minutes per unit.
839
COST_UNIT_VALUE		5
840
 
841
# By default when using SHOW_REPORT the migration report is generated as
842
# simple text, enabling this directive will force ora2pg to create a report
843
# in HTML format.
844
DUMP_AS_HTML		0
845
 
846
# Set the total number of tables to display in the Top N per row and size
847
# list in the SHOW_TABLE and SHOW_REPORT output. Default 10.
848
TOP_MAX			10
849
 
850
# Use this directive to redefined the number of human-days limit where the
851
# migration assessment level must switch from B to C. Default is set to 10
852
# human-days.
853
HUMAN_DAYS_LIMIT	5
854
 
855
# Set the comma separated list of username that must be used to filter
856
# queries from the DBA_AUDIT_TRAIL table. Default is to not scan this
857
# table and to never look for queries. This parameter is used only with
858
# SHOW_REPORT and QUERY export type with no input file for queries.
859
# Note that queries will be normalized before output unlike when a file
860
# is given at input using the -i option or INPUT directive.
861
#AUDIT_USER	USERNAME1,USERNAME2
862
 
863
# By default Ora2Pg will convert call to SYS_GUID() Oracle function
864
# with a call to uuid_generate_v4() from uuid-ossp extension. You can
865
# redefined it to use the gen_random_uuid() function from pgcrypto
866
# extension by changing the function name below.
867
#UUID_FUNCTION	uuid_generate_v4
868
 
869
#------------------------------------------------------------------------------
870
# POSTGRESQL FEATURE SECTION (Control which PostgreSQL features are available)
871
#------------------------------------------------------------------------------
872
 
873
# Allow support of WHEN clause in trigger definition PG>=9.0
874
PG_SUPPORTS_WHEN		1
875
 
876
# Allow support of INSTEAD OF in triggers definition PG>=9.1
877
PG_SUPPORTS_INSTEADOF	1
878
 
879
# Allow support of native MATERIALIZED VIEW PG>=9.3. If disable Ora2Pg
880
# will use old behavior, a normal table with a set of function to refresh
881
# the view.
882
PG_SUPPORTS_MVIEW	1
883
 
884
# If enabled, export view with CHECK OPTION. Disable it if you have PostgreSQL
885
# version prior 9.4. Default, enabled
886
PG_SUPPORTS_CHECKOPTION	1
887
 
888
# PostgreSQL versions below 9.x do not support IF EXISTS in DDL statements.
889
# Disabling the directive with value 0 will prevent Ora2Pg to add those
890
# keywords in all generated statements.
891
PG_SUPPORTS_IFEXISTS	1
892
 
893
# Use btree_gin extenstion to create bitmap like index with pg >= 9.4
894
# You will need to create the extension by yourself:
895
#	create extension btree_gin;
896
# Default is to create GIN index, when disabled, a btree index will be created
897
BITMAP_AS_GIN		1
898
 
899
# Use pg_background extension to create an autonomous transaction instead
900
# of using a dblink wrapper. With pg >= 9.5 only, default is to use dblink.
901
PG_BACKGROUND		0
902
 
903
#------------------------------------------------------------------------------
904
# SPATIAL SECTION (Control spatial geometry export)
905
#------------------------------------------------------------------------------
906
 
907
# Enable this directive if you want Ora2Pg to detect the real spatial type and
908
# dimensions used in a spatial column. By default Ora2Pg will look at spatial
909
# indexes to see if the layer_gtype and sdo_indx_dims constraint parameters have
910
# been set, otherwise column will be created with the non-constrained "geometry"
911
# type. Enabling this feature will force Ora2Pg to scan a sample of 50000 lines
912
# to look at the GTYPE used. You can increase or reduce the sample by setting
913
# the value of AUTODETECT_SPATIAL_TYPE to the desired number of line.
914
AUTODETECT_SPATIAL_TYPE	1
915
 
916
# Disable this directive if you don't want to automatically convert SRID to
917
# EPSG using the sdo_cs.map_oracle_srid_to_epsg() function. Default: enabled
918
# If the SDO_SRID returned by Oracle is NULL, it will be replaced by the
919
# default value 8307 converted to its EPSG value: 4326 (see DEFAULT_SRID)
920
# If the value is upper than 1, all SRID will be forced to this value, in
921
# this case DEFAULT_SRID will not be used when Oracle returns a null value
922
# and the value will be forced to CONVERT_SRID.
923
# Note that it is also possible to set the EPSG value on Oracle side when
924
# sdo_cs.map_oracle_srid_to_epsg() return NULL if your want to force the value:
925
# Ex: system> UPDATE sdo_coord_ref_sys SET legacy_code=41014 WHERE srid = 27572;
926
CONVERT_SRID		1
927
 
928
# Use this directive to override the default EPSG SRID to used: 4326.
929
# Can be overwritten by CONVERT_SRID, see above.
930
DEFAULT_SRID		4326
931
 
932
# This directive can take three values: WKT (default), WKB and INTERNAL.
933
# When it is set to WKT, Ora2Pg will use SDO_UTIL.TO_WKTGEOMETRY() to
934
# extract the geometry data. When it is set to WKB, Ora2Pg will use the
935
# binary output using SDO_UTIL.TO_WKBGEOMETRY(). If those two extract type
936
# are called at Oracle side, they are slow and you can easily reach Out Of
937
# Memory when you have lot of rows. Also WKB is not able to export 3D geometry
938
# and some geometries like CURVEPOLYGON. In this case you may use the INTERNAL
939
# extraction type. It will use a pure Perl library to convert the SDO_GEOMETRY
940
# data into a WKT representation, the translation is done on Ora2Pg side.
941
# This is a work in progress, please validate your exported data geometries
942
# before use.
943
GEOMETRY_EXTRACT_TYPE	INTERNAL
944
 
945
 
946
#------------------------------------------------------------------------------
947
# FDW SECTION (Control Foreign Data Wrapper export)
948
#------------------------------------------------------------------------------
949
 
950
# This directive is used to set the name of the foreign data server that is used
951
# in the "CREATE SERVER name FOREIGN DATA WRAPPER oracle_fdw ..." command. This
952
# name will then be used in the "CREATE FOREIGN TABLE ..." SQL command. Default
953
# is arbitrary set to orcl. This only concerns export type FDW.
954
FDW_SERVER	orcl
955
 
956
 
957
#------------------------------------------------------------------------------
958
# MYSQL SECTION (Control MySQL export behavior)
959
#------------------------------------------------------------------------------
960
 
961
# Enable this if double pipe and double ampersand (|| and &&) should not be
962
# taken as equivalent to OR and AND. It depend of the variable @sql_mode,
963
# Use it only if Ora2Pg fail on auto detecting this behavior.
964
MYSQL_PIPES_AS_CONCAT		0
965
 
966
# Enable this directive if you want EXTRACT() replacement to use the internal
967
# format returned as an integer, for example DD HH24:MM:SS will be replaced
968
# with format; DDHH24MMSS::bigint, this depend of your apps usage.
969
MYSQL_INTERNAL_EXTRACT_FORMAT	0
970