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 dbti313 |
||
25 | ORACLE_PWD sysdbti |
||
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 DBTI313 |
||
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 dbti |
||
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 S3_CT07T_STRADE_CAT, S3_CT08T_IDENT_UIU, S3_CT14T_RISERVE_TERRENI, S3_CT17T_BILANCIO_GEOMETRIA, S3_CT35T_MUTAZIONI, S3_CT36T_FOGLI, S3_CT38T_SOGGETTI, S3_CT45T_IMMAGINI, S3_CT48T_UIU_X_CIVICI |
||
142 | ALLOW S3_CN01T_NOTE, S3_CN02T_PF_NOTA, S3_CN04T_PG_NOTA |
||
143 | |||
144 | # Set which object to exclude from export process. By default none. Value |
||
145 | # must be a list of object name or regexp separated by space. Note that regex |
||
146 | # will not works with 8i database, use % placeholder instead Ora2Pg will use |
||
147 | # the NOT LIKE operator. There is also some extended use of this directive, |
||
148 | # see chapter "Limiting object to export" in documentation. |
||
149 | #EXCLUDE OTHER_TABLES |
||
150 | |||
151 | # Set which view to export as table. By default none. Value must be a list of |
||
152 | # view name or regexp separated by space. If the object name is a view and the |
||
153 | # export type is TABLE, the view will be exported as a create table statement. |
||
154 | # If export type is COPY or INSERT, the corresponding data will be exported. |
||
155 | #VIEW_AS_TABLE VIEW_NAME |
||
156 | |||
157 | # When exporting GRANTs you can specify a comma separated list of objects |
||
158 | # for which privilege will be exported. Default is export for all objects. |
||
159 | # Here are the possibles values TABLE, VIEW, MATERIALIZED VIEW, SEQUENCE, |
||
160 | # PROCEDURE, FUNCTION, PACKAGE BODY, TYPE, SYNONYM, DIRECTORY. Only one object |
||
161 | # type is allowed at a time. For example set it to TABLE if you just want to |
||
162 | # export privilege on tables. You can use the -g option to overwrite it. |
||
163 | # When used this directive prevent the export of users unless it is set to |
||
164 | # USER. In this case only users definitions are exported. |
||
165 | #GRANT_OBJECT TABLE |
||
166 | |||
167 | # By default Ora2Pg will export your external table as file_fdw tables. If |
||
168 | # you don't want to export those tables at all, set the directive to 0. |
||
169 | EXTERNAL_TO_FDW 0 |
||
170 | |||
171 | # Add a TRUNCATE TABLE instruction before loading data on COPY and INSERT |
||
172 | # export. When activated, the instruction will be added only if there's no |
||
173 | # global DELETE clause or one specific to the current table (see bellow). |
||
174 | TRUNCATE_TABLE 0 |
||
175 | |||
176 | # Support for include a DELETE FROM ... WHERE clause filter before importing |
||
177 | # data and perform a delete of some lines instead of truncatinf tables. |
||
178 | # Value is construct as follow: TABLE_NAME[DELETE_WHERE_CLAUSE], or |
||
179 | # if you have only one where clause for all tables just put the delete |
||
180 | # clause as single value. Both are possible too. Here are some examples: |
||
181 | #DELETE 1=1 # Apply to all tables and delete all tuples |
||
182 | #DELETE TABLE_TEST[ID1='001'] # Apply only on table TABLE_TEST |
||
183 | #DELETE TABLE_TEST[ID1='001' OR ID1='002] DATE_CREATE > '2001-01-01' TABLE_INFO[NAME='test'] |
||
184 | # The last applies two different delete where clause on tables TABLE_TEST and |
||
185 | # TABLE_INFO and a generic delete where clause on DATE_CREATE to all other tables. |
||
186 | # If TRUNCATE_TABLE is enabled it will be applied to all tables not covered by |
||
187 | # the DELETE definition. |
||
188 | |||
189 | # When enabled this directive forces ora2pg to export all tables, index |
||
190 | # constraints, and indexes using the tablespace name defined in Oracle database. |
||
191 | # This works only with tablespaces that are not TEMP, USERS and SYSTEM. |
||
192 | USE_TABLESPACE 0 |
||
193 | |||
194 | # Enable this directive to reorder columns and minimized the footprint |
||
195 | # on disk, so that more rows fit on a data page, which is the most important |
||
196 | # factor for speed. Default is same order than in Oracle table definition, |
||
197 | # that should be enough for most usage. |
||
198 | REORDERING_COLUMNS 0 |
||
199 | |||
200 | # Support for include a WHERE clause filter when dumping the contents |
||
201 | # of tables. Value is construct as follow: TABLE_NAME[WHERE_CLAUSE], or |
||
202 | # if you have only one where clause for each table just put the where |
||
203 | # clause as value. Both are possible too. Here are some examples: |
||
204 | #WHERE 1=1 # Apply to all tables |
||
205 | #WHERE TABLE_TEST[ID1='001'] # Apply only on table TABLE_TEST |
||
206 | #WHERE TABLE_TEST[ID1='001' OR ID1='002] DATE_CREATE > '2001-01-01' TABLE_INFO[NAME='test'] |
||
207 | # The last applies two different where clause on tables TABLE_TEST and |
||
208 | # TABLE_INFO and a generic where clause on DATE_CREATE to all other tables |
||
209 | |||
210 | # Sometime you may want to extract data from an Oracle table but you need a |
||
211 | # a custom query for that. Not just a "SELECT * FROM table" like Ora2Pg does |
||
212 | # but a more complex query. This directive allows you to override the query |
||
213 | # used by Ora2Pg to extract data. The format is TABLENAME[SQL_QUERY]. |
||
214 | # If you have multiple tables to extract by replacing the Ora2Pg query, you can |
||
215 | # define multiple REPLACE_QUERY lines. |
||
216 | #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')] |
||
217 | |||
218 | #------------------------------------------------------------------------------ |
||
219 | # FULL TEXT SEARCH SECTION (Control full text search export behaviors) |
||
220 | #------------------------------------------------------------------------------ |
||
221 | |||
222 | # Force Ora2Pg to translate Oracle Text indexes into PostgreSQL indexes using |
||
223 | # pg_trgm extension. Default is to translate CONTEXT indexes into FTS indexes |
||
224 | # and CTXCAT indexes using pg_trgm. Most of the time using pg_trgm is enough, |
||
225 | # this is why this directive stand for. |
||
226 | # |
||
227 | CONTEXT_AS_TRGM 0 |
||
228 | |||
229 | # By default Ora2Pg creates a function-based index to translate Oracle Text |
||
230 | # indexes. |
||
231 | # CREATE INDEX ON t_document |
||
232 | # USING gin(to_tsvector('french', title)); |
||
233 | # You will have to rewrite the CONTAIN() clause using to_tsvector(), example: |
||
234 | # SELECT id,title FROM t_document |
||
235 | # WHERE to_tsvector(title)) @@ to_tsquery('search_word'); |
||
236 | # |
||
237 | # To force Ora2Pg to create an extra tsvector column with a dedicated triggers |
||
238 | # for FTS indexes, disable this directive. In this case, Ora2Pg will add the |
||
239 | # column as follow: ALTER TABLE t_document ADD COLUMN tsv_title tsvector; |
||
240 | # Then update the column to compute FTS vectors if data have been loaded before |
||
241 | # UPDATE t_document SET tsv_title = |
||
242 | # to_tsvector('french', coalesce(title,'')); |
||
243 | # To automatically update the column when a modification in the title column |
||
244 | # appears, Ora2Pg adds the following trigger: |
||
245 | # |
||
246 | # CREATE FUNCTION tsv_t_document_title() RETURNS trigger AS $$ |
||
247 | # BEGIN |
||
248 | # IF TG_OP = 'INSERT' OR new.title != old.title THEN |
||
249 | # new.tsv_title := |
||
250 | # to_tsvector('french', coalesce(new.title,'')); |
||
251 | # END IF; |
||
252 | # return new; |
||
253 | # END |
||
254 | # $$ LANGUAGE plpgsql; |
||
255 | # CREATE TRIGGER trig_tsv_t_document_title BEFORE INSERT OR UPDATE |
||
256 | # ON t_document |
||
257 | # FOR EACH ROW EXECUTE PROCEDURE tsv_t_document_title(); |
||
258 | # |
||
259 | # When the Oracle text index is defined over multiple column, Ora2Pg will use |
||
260 | # setweight() to set a weight in the order of the column declaration. |
||
261 | # |
||
262 | FTS_INDEX_ONLY 1 |
||
263 | |||
264 | # Use this directive to force text search configuration to use. When it is not |
||
265 | # set, Ora2Pg will autodetect the stemmer used by Oracle for each index and |
||
266 | # pg_catalog.english if nothing is found. |
||
267 | # |
||
268 | #FTS_CONFIG pg_catalog.french |
||
269 | |||
270 | # If you want to perform your text search in an accent insensitive way, enable |
||
271 | # this directive. Ora2Pg will create an helper function over unaccent() and |
||
272 | # creates the pg_trgm indexes using this function. With FTS Ora2Pg will |
||
273 | # redefine your text search configuration, for example: |
||
274 | # |
||
275 | # CREATE TEXT SEARCH CONFIGURATION fr (COPY = pg_catalog.french); |
||
276 | # ALTER TEXT SEARCH CONFIGURATION fr |
||
277 | # ALTER MAPPING FOR hword, hword_part, word WITH unaccent, french_stem; |
||
278 | # |
||
279 | # When enabled, Ora2pg will create the wrapper function: |
||
280 | # |
||
281 | # CREATE OR REPLACE FUNCTION unaccent_immutable(text) |
||
282 | # RETURNS text AS |
||
283 | # $$ |
||
284 | # SELECT public.unaccent('public.unaccent', ) |
||
285 | # $$ LANGUAGE sql IMMUTABLE |
||
286 | # COST 1; |
||
287 | # |
||
288 | # indexes are exported as follow: |
||
289 | # |
||
290 | # CREATE INDEX t_document_title_unaccent_trgm_idx ON t_document |
||
291 | # USING gin (unaccent_immutable(title) gin_trgm_ops); |
||
292 | # |
||
293 | # In your queries you will need to use the same function in the search to |
||
294 | # be able to use the function-based index. Example: |
||
295 | # |
||
296 | # SELECT * FROM t_document |
||
297 | # WHERE unaccent_immutable(title) LIKE '%donnees%'; |
||
298 | # |
||
299 | USE_UNACCENT 0 |
||
300 | |||
301 | # Same as above but call lower() in the unaccent_immutable() function: |
||
302 | # |
||
303 | # CREATE OR REPLACE FUNCTION unaccent_immutable(text) |
||
304 | # RETURNS text AS |
||
305 | # $$ |
||
306 | # SELECT lower(public.unaccent('public.unaccent', )); |
||
307 | # $$ LANGUAGE sql IMMUTABLE; |
||
308 | # |
||
309 | USE_LOWER_UNACCENT 0 |
||
310 | |||
311 | #------------------------------------------------------------------------------ |
||
312 | # CONSTRAINT SECTION (Control constraints export and import behaviors) |
||
313 | #------------------------------------------------------------------------------ |
||
314 | |||
315 | # Support for turning off certain schema features in the postgres side |
||
316 | # during schema export. Values can be : fkeys, pkeys, ukeys, indexes, checks |
||
317 | # separated by a space character. |
||
318 | # fkeys : turn off foreign key constraints |
||
319 | # pkeys : turn off primary keys |
||
320 | # ukeys : turn off unique column constraints |
||
321 | # indexes : turn off all other index types |
||
322 | # checks : turn off check constraints |
||
323 | #SKIP fkeys pkeys ukeys indexes checks |
||
324 | |||
325 | # By default, primary key names in the source database are ignored, and |
||
326 | # default key names are created in the target database. If this is set to true, |
||
327 | # primary key names are kept. |
||
328 | KEEP_PKEY_NAMES 0 |
||
329 | |||
330 | # Enable this directive if you want to add primary key definitions inside the |
||
331 | # create table statements. If disabled (the default) primary key definition |
||
332 | # will be added with an alter table statement. Enable it if you are exporting |
||
333 | # to GreenPlum PostgreSQL database. |
||
334 | PKEY_IN_CREATE 0 |
||
335 | |||
336 | # This directive allow you to add an ON UPDATE CASCADE option to a foreign |
||
337 | # key when a ON DELETE CASCADE is defined or always. Oracle do not support |
||
338 | # this feature, you have to use trigger to operate the ON UPDATE CASCADE. |
||
339 | # As PostgreSQL has this feature, you can choose how to add the foreign |
||
340 | # key option. There is three value to this directive: never, the default |
||
341 | # that mean that foreign keys will be declared exactly like in Oracle. |
||
342 | # The second value is delete, that mean that the ON UPDATE CASCADE option |
||
343 | # will be added only if the ON DELETE CASCADE is already defined on the |
||
344 | # foreign Keys. The last value, always, will force all foreign keys to be |
||
345 | # defined using the update option. |
||
346 | FKEY_ADD_UPDATE never |
||
347 | |||
348 | # When exporting tables, Ora2Pg normally exports constraints as they are; |
||
349 | # if they are non-deferrable they are exported as non-deferrable. |
||
350 | # However, non-deferrable constraints will probably cause problems when |
||
351 | # attempting to import data to PostgreSQL. The following option set to 1 |
||
352 | # will cause all foreign key constraints to be exported as deferrable |
||
353 | FKEY_DEFERRABLE 0 |
||
354 | |||
355 | # In addition when exporting data the DEFER_FKEY option set to 1 will add |
||
356 | # a command to defer all foreign key constraints during data export and |
||
357 | # the import will be done in a single transaction. This will work only if |
||
358 | # foreign keys have been exported as deferrable and you are not using direct |
||
359 | # import to PostgreSQL (PG_DSN is not defined). Constraints will then be |
||
360 | # checked at the end of the transaction. This directive can also be enabled |
||
361 | # if you want to force all foreign keys to be created as deferrable and |
||
362 | # initially deferred during schema export (TABLE export type). |
||
363 | DEFER_FKEY 0 |
||
364 | |||
365 | # If deferring foreign keys is not possible du to the amount of data in a |
||
366 | # single transaction, you've not exported foreign keys as deferrable or you |
||
367 | # are using direct import to PostgreSQL, you can use the DROP_FKEY directive. |
||
368 | # It will drop all foreign keys before all data import and recreate them at |
||
369 | # the end of the import. |
||
370 | DROP_FKEY 0 |
||
371 | |||
372 | |||
373 | #------------------------------------------------------------------------------ |
||
374 | # TRIGGERS AND SEQUENCES SECTION (Control triggers and sequences behaviors) |
||
375 | #------------------------------------------------------------------------------ |
||
376 | |||
377 | # Disables alter of sequences on all tables in COPY or INSERT mode. |
||
378 | # Set to 1 if you want to disable update of sequence during data migration. |
||
379 | DISABLE_SEQUENCE 0 |
||
380 | |||
381 | # Disables triggers on all tables in COPY or INSERT mode. Available modes |
||
382 | # are USER (user defined triggers) and ALL (includes RI system |
||
383 | # triggers). Default is 0 do not add SQL statement to disable trigger. |
||
384 | # If you want to disable triggers during data migration, set the value to |
||
385 | # USER if your are connected as non superuser and ALL if you are connected |
||
386 | # as PostgreSQL superuser. A value of 1 is equal to USER. |
||
387 | DISABLE_TRIGGERS 0 |
||
388 | |||
389 | |||
390 | #------------------------------------------------------------------------------ |
||
391 | # OBJECT MODIFICATION SECTION (Control objects structure or name modifications) |
||
392 | #------------------------------------------------------------------------------ |
||
393 | |||
394 | # You may wish to just extract data from some fields, the following directives |
||
395 | # will help you to do that. Works only with export type INSERT or COPY |
||
396 | # Modify output from the following tables(fields separate by space or comma) |
||
397 | #MODIFY_STRUCT TABLE_TEST(dico,dossier) |
||
398 | MODIFY_STRUCT S3_CT31G_FOGLI(CT31_COD_COM,CT31_SEZ,CT31_FOGLIO,CT31_ALLEGATO,CT31_SVILUPPO,CT31_SCALA,CT31_SIST_RIF,CT31_FI_ORIG_CASSINI,CT31_LAMBDA_ORIG_CASSINI,CT31_GEOMETRIA,CT31_PROT_ULTIMO_AGG,CT31_OBJECT_ID) |
||
399 | MODIFY_STRUCT S3_CT24G_PARTICELLE(CT24_COD_COM,CT24_SEZ,CT24_FOGLIO,CT24_NUMERO,CT24_ALLEGATO,CT24_SVILUPPO,CT24_AREA,CT24_GEOMETRIA,CT24_PROT_ULTIMO_AGG,CT24_OBJECT_ID) |
||
400 | MODIFY_STRUCT S3_CT29G_ACQUE(CT29_COD_COM,CT29_SEZ,CT29_FOGLIO,CT29_ALLEGATO,CT29_SVILUPPO,CT29_GEOMETRIA,CT29_PROT_ULTIMO_AGG,CT29_OBJECT_ID) |
||
401 | MODIFY_STRUCT S3_CT30G_CENTROIDI(CT30_COD_COM,CT30_SEZ,CT30_FOGLIO,CT30_NUMERO,CT30_ALLEGATO,CT30_SVILUPPO,CT30_GEOMETRIA,CT30_PROT_ULTIMO_AGG,CT30_OBJECT_ID) |
||
402 | MODIFY_STRUCT S3_CT32G_STRADE(CT32_COD_COM,CT32_SEZ,CT32_FOGLIO,CT32_ALLEGATO,CT32_SVILUPPO,CT32_GEOMETRIA,CT32_PROT_ULTIMO_AGG,CT32_OBJECT_ID) |
||
403 | MODIFY_STRUCT S3_CT33G_SIMBOLI(CT33_COD_COM,CT33_SEZ,CT33_FOGLIO,CT33_ALLEGATO,CT33_SVILUPPO,CT33_COD_SIMBOLO,CT33_ANGOLO,CT33_GEOMETRIA,CT33_PROT_ULTIMO_AGG,CT33_OBJECT_ID) |
||
404 | MODIFY_STRUCT S3_CT34G_TESTI(CT34_COD_COM,CT34_SEZ,CT34_FOGLIO,CT34_ALLEGATO,CT34_SVILUPPO,CT34_TESTO,CT34_ANGOLO,CT34_DIMENSIONE,CT34_GEOMETRIA,CT34_PROT_ULTIMO_AGG,CT34_OBJECT_ID) |
||
405 | MODIFY_STRUCT S3_CT37G_VARIE(CT37_COD_COM,CT37_SEZ,CT37_FOGLIO,CT37_ALLEGATO,CT37_SVILUPPO,CT37_GEOMETRIA,CT37_PROT_ULTIMO_AGG,CT37_OBJECT_ID) |
||
406 | MODIFY_STRUCT S3_CT51G_LINEE(CT51_COD_COM,CT51_SEZ,CT51_FOGLIO,CT51_ALLEGATO,CT51_SVILUPPO,CT51_COD_LINEA,CT51_GEOMETRIA,CT51_PROT_ULTIMO_AGG,CT51_OBJECT_ID) |
||
407 | MODIFY_STRUCT S3_CT52G_FIDUCIALI(CT52_COD_COM,CT52_SEZ,CT52_FOGLIO,CT52_ALLEGATO,CT52_SVILUPPO,CT52_TIPO_FIDUCIALE,CT52_NUM_FIDUCIALE,CT52_GEOMETRIA,CT52_PROT_ULTIMO_AGG,CT52_OBJECT_ID) |
||
408 | MODIFY_STRUCT S3_CT53G_RIF_RASTER(CT53_COD_COM,CT53_SEZ,CT53_FOGLIO,CT53_ALLEGATO,CT53_SVILUPPO,CT53_URI,CT53_RASTER,CT53_GEOMETRIA,CT53_PROT_ULTIMO_AGG,CT53_OBJECT_ID) |
||
409 | MODIFY_STRUCT S3_CT56G_PUNTI_FIDUCIALI(CT56_COD_COM,CT56_SEZ,CT56_FOGLIO,CT56_ALLEGATO,CT56_SVILUPPO,CT56_ID_PUNTO_FIDUCIALE,CT56_VERIFICA,CT_56_ENTE,CT56_QUOTA_ORTOMETRICA,CT56_QUOTA_ELLISSOIDICA,CT56_XCS,CT56_YCS,CT56_NORDGB,CT56_ESTGB,CT56_XSF,CT56_YSF,CT56_FI_WGS84,CT56_LAMBDA_WGS84,CT56_GEOREFERENZIAZ,CT56_ATTEND_PLAN_RIL,CT56_ATTEND_PLAN_RETE,CT56_ATTEND_QUOTA_RIL,CT56_ATTEND_QUOTA_RETE,CT56_PARTICELLA,CT56_MONOGRAFIA_PLAN,CT56_FOGLIO_ORIG,CT56_ALLEGATO_ORIG,CT56_FIDUCIALE_ORIG,CT56_DATA_AGG,CT56_CAUSALE,CT56_MONOGRAFIA_QUOTA,CT56_GEOMETRIA,CT56_PROT_ULTIMO_AGG,CT56_OBJECT_ID) |
||
410 | MODIFY_STRUCT S3_CT28G_CAMPITURE(CT28_COD_COM,CT28_SEZ,CT28_FOGLIO,CT28_NUMERO,CT28_ALLEGATO,CT28_SVILUPPO,CT28_GEOMETRIA,CT28_PROT_ULTIMO_AGG,CT28_OBJECT_ID) |
||
411 | MODIFY_STRUCT S3_CT54G_TESTI_PARTICELLE(CT54_COD_COM,CT54_SEZ,CT54_FOGLIO,CT54_NUMERO,CT54_ANGOLO,CT54_DIMENSIONE,CT54_ALLEGATO,CT54_SVILUPPO,CT54_GEOMETRIA,CT54_PROT_ULTIMO_AGG,CT54_OBJECT_ID) |
||
412 | |||
413 | # You may wish to change table names during data extraction, especally for |
||
414 | # replication use. Give a list of tables separate by space as follow. |
||
415 | #REPLACE_TABLES ORIG_TB_NAME1:NEW_TB_NAME1 ORIG_TB_NAME2:NEW_TB_NAME2 |
||
416 | |||
417 | # You may wish to change column names during data extraction, especially for |
||
418 | # replication use. Give a list of tables and columns separate by space as |
||
419 | # follow. |
||
420 | #REPLACE_COLS TB_NAME(ORIG_COLNAME1:NEW_COLNAME1,ORIG_COLNAME2:NEW_COLNAME2) |
||
421 | |||
422 | # By default all object names are converted to lower case, if you |
||
423 | # want to preserve Oracle object name as-is set this to 1. Not recommended |
||
424 | # unless you always quote all tables and columns on all your scripts. |
||
425 | PRESERVE_CASE 0 |
||
426 | |||
427 | # Add the given value as suffix to index names. Useful if you have indexes |
||
428 | # with same name as tables. Not so common but it can help. |
||
429 | #INDEXES_SUFFIX _idx |
||
430 | |||
431 | # Enable this directive to rename all indexes using tablename_columns_names. |
||
432 | # Could be very useful for database that have multiple time the same index name |
||
433 | # or that use the same name than a table, which is not allowed by PostgreSQL |
||
434 | # Disabled by default. |
||
435 | INDEXES_RENAMING 0 |
||
436 | |||
437 | # Operator classes text_pattern_ops, varchar_pattern_ops, and bpchar_pattern_ops |
||
438 | # support B-tree indexes on the corresponding types. The difference from the |
||
439 | # default operator classes is that the values are compared strictly character by |
||
440 | # character rather than according to the locale-specific collation rules. This |
||
441 | # makes these operator classes suitable for use by queries involving pattern |
||
442 | # matching expressions (LIKE or POSIX regular expressions) when the database |
||
443 | # does not use the standard "C" locale. If you enable, with value 1, this will |
||
444 | # force Ora2Pg to export all indexes defined on varchar2() and char() columns |
||
445 | # using those operators. If you set it to a value greater than 1 it will only |
||
446 | # change indexes on columns where the charactere limit is greater or equal than |
||
447 | # this value. For example, set it to 128 to create these kind of indexes on |
||
448 | # columns of type varchar2(N) where N >= 128. |
||
449 | USE_INDEX_OPCLASS 0 |
||
450 | |||
451 | # Enable this directive if you want that your partition table name will be |
||
452 | # exported using the parent table name. Disabled by default. If you have |
||
453 | # multiple partitioned table, when exported to PostgreSQL some partitions |
||
454 | # could have the same name but different parent tables. This is not allowed, |
||
455 | # table name must be unique. |
||
456 | PREFIX_PARTITION 0 |
||
457 | |||
458 | # If you don't want to reproduce the partitioning like in Oracle and want to |
||
459 | # export all partitionned Oracle data into the main single table in PostgreSQL |
||
460 | # enable this directive. Ora2Pg will export all data into the main table name. |
||
461 | # Default is to use partitionning, Ora2Pg will export data from each partition |
||
462 | # and import them into the PostgreSQL dedicated partition table. |
||
463 | DISABLE_PARTITION 1 |
||
464 | |||
465 | # Activating this directive will force Ora2Pg to add WITH (OIDS) when creating |
||
466 | # tables or views as tables. Default is same as PostgreSQL, disabled. |
||
467 | WITH_OID 0 |
||
468 | |||
469 | # Allow escaping of column name using Oracle reserved words. |
||
470 | ORA_RESERVED_WORDS audit,comment |
||
471 | |||
472 | # Enable this directive if you have tables or column names that are a reserved |
||
473 | # word for PostgreSQL. Ora2Pg will double quote the name of the object. |
||
474 | USE_RESERVED_WORDS 0 |
||
475 | |||
476 | #------------------------------------------------------------------------------ |
||
477 | # OUTPUT SECTION (Control output to file or PostgreSQL database) |
||
478 | #------------------------------------------------------------------------------ |
||
479 | |||
480 | # Define the following directive to send export directly to a PostgreSQL |
||
481 | # database. This will disable file output. |
||
482 | #PG_DSN dbi:Pg:dbname=test_db;host=localhost;port=5432 |
||
483 | #PG_USER test |
||
484 | #PG_PWD test |
||
485 | PG_DSN dbi:Pg:dbname=S3_vda;host=172.25.102.42;port=5432 |
||
486 | PG_USER s3_vda |
||
487 | PG_PWD s3 |
||
488 | |||
489 | # By default all output is dump to STDOUT if not send directly to postgresql |
||
490 | # database (see above). Give a filename to save export to it. If you want |
||
491 | # a Gzip'd compressed file just add the extension .gz to the filename (you |
||
492 | # need perl module Compress::Zlib from CPAN). Add extension .bz2 to use Bzip2 |
||
493 | # compression. |
||
494 | OUTPUT output_copy_dbti313_6.a.1.sql |
||
495 | |||
496 | # Base directory where all dumped files must be written |
||
497 | #OUTPUT_DIR /var/tmp |
||
498 | |||
499 | # Path to the bzip2 program. See OUTPUT directive above. |
||
500 | BZIP2 |
||
501 | |||
502 | # Allow object constraints to be saved in a separate file during schema export. |
||
503 | # The file will be named CONSTRAINTS_OUTPUT. Where OUTPUT is the value of the |
||
504 | # corresponding configuration directive. You can use .gz xor .bz2 extension to |
||
505 | # enable compression. Default is to save all data in the OUTPUT file. This |
||
506 | # directive is usable only with TABLE export type. |
||
507 | FILE_PER_CONSTRAINT 0 |
||
508 | |||
509 | # Allow indexes to be saved in a separate file during schema export. The file |
||
510 | # will be named INDEXES_OUTPUT. Where OUTPUT is the value of the corresponding |
||
511 | # configuration directive. You can use the .gz, .xor, or .bz2 file extension to |
||
512 | # enable compression. Default is to save all data in the OUTPUT file. This |
||
513 | # directive is usable only with TABLE or TABLESPACE export type. With the |
||
514 | # TABLESPACE export, it is used to write "ALTER INDEX ... TABLESPACE ..." into |
||
515 | # a separate file named TBSP_INDEXES_OUTPUT that can be loaded at end of the |
||
516 | # migration after the indexes creation to move the indexes. |
||
517 | FILE_PER_INDEX 0 |
||
518 | |||
519 | # Allow data export to be saved in one file per table/view. The files |
||
520 | # will be named as tablename_OUTPUT. Where OUTPUT is the value of the |
||
521 | # corresponding configuration directive. You can use .gz xor .bz2 |
||
522 | # extension to enable compression. Default is to save all data in one |
||
523 | # file. This is usable only during INSERT or COPY export type. |
||
524 | FILE_PER_TABLE 0 |
||
525 | |||
526 | # Allow function export to be saved in one file per function/procedure. |
||
527 | # The files will be named as funcname_OUTPUT. Where OUTPUT is the value |
||
528 | # of the corresponding configuration directive. You can use .gz xor .bz2 |
||
529 | # extension to enable compression. Default is to save all data in one |
||
530 | # file. It is usable during FUNCTION, PROCEDURE, TRIGGER and PACKAGE |
||
531 | # export type. |
||
532 | FILE_PER_FUNCTION 0 |
||
533 | |||
534 | # By default Ora2Pg will force Perl to use utf8 I/O encoding. This is done through |
||
535 | # a call to the Perl pragma: |
||
536 | # |
||
537 | # use open ':utf8'; |
||
538 | # |
||
539 | # You can override this encoding by using the BINMODE directive, for example you |
||
540 | # can set it to :locale to use your locale or iso-8859-7, it will respectively use |
||
541 | # |
||
542 | # use open ':locale'; |
||
543 | # use open ':encoding(iso-8859-7)'; |
||
544 | # |
||
545 | # If you have change the NLS_LANG in non UTF8 encoding, you might want to set this |
||
546 | # directive. See http://perldoc.perl.org/5.14.2/open.html for more information. |
||
547 | # Most of the time, you might leave this directive commented. |
||
548 | #BINMODE utf8 |
||
549 | |||
550 | # Set it to 0 to not include the call to \set ON_ERROR_STOP ON in all SQL |
||
551 | # scripts. By default this order is always present. |
||
552 | STOP_ON_ERROR 1 |
||
553 | |||
554 | # Enable this directive to use COPY FREEZE instead of a simple COPY to |
||
555 | # export data with rows already frozen. This is intended as a performance |
||
556 | # option for initial data loading. Rows will be frozen only if the table |
||
557 | # being loaded has been created or truncated in the current subtransaction. |
||
558 | # This will only works with export to file and when -J or ORACLE_COPIES is |
||
559 | # not set or default to 1. It can be used with direct import into PostgreSQL |
||
560 | # under the same condition but -j or JOBS must also be unset or default to 1. |
||
561 | COPY_FREEZE 0 |
||
562 | |||
563 | #------------------------------------------------------------------------------ |
||
564 | # TYPE SECTION (Control type behaviors and redefinitions) |
||
565 | #------------------------------------------------------------------------------ |
||
566 | |||
567 | # If you're experiencing problems in data type export, the following directive |
||
568 | # will help you to redefine data type translation used in Ora2pg. The syntax is |
||
569 | # a comma separated list of "Oracle datatype:Postgresql data type". Here are the |
||
570 | # data type that can be redefined and their default value. If you want to |
||
571 | # replace a type with a precision and scale you need to escape the coma with |
||
572 | # a backslash. For example, if you want to replace all NUMBER(*,0) into bigint |
||
573 | # instead of numeric(38)add the following: |
||
574 | # DATA_TYPE NUMBER(*\,0):bigint |
||
575 | # Here is the default replacement for all Oracle's types. You don't have to |
||
576 | # recopy all type conversion but just the one you want to rewrite. |
||
577 | #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 |
||
578 | 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 |
||
579 | |||
580 | # If set to 1 replace portable numeric type into PostgreSQL internal type. |
||
581 | # Oracle data type NUMBER(p,s) is approximatively converted to real and |
||
582 | # float PostgreSQL data type. If you have monetary fields or don't want |
||
583 | # rounding issues with the extra decimals you should preserve the same |
||
584 | # numeric(p,s) PostgreSQL data type. Do that only if you need very good |
||
585 | # precision because using numeric(p,s) is slower than using real or double. |
||
586 | PG_NUMERIC_TYPE 1 |
||
587 | |||
588 | # If set to 1 replace portable numeric type into PostgreSQL internal type. |
||
589 | # Oracle data type NUMBER(p) or NUMBER are converted to smallint, integer |
||
590 | # or bigint PostgreSQL data type following the length of the precision. If |
||
591 | # NUMBER without precision are set to DEFAULT_NUMERIC (see bellow). |
||
592 | PG_INTEGER_TYPE 1 |
||
593 | |||
594 | # NUMBER() without precision are converted by default to bigint only if |
||
595 | # PG_INTEGER_TYPE is true. You can overwrite this value to any PG type, |
||
596 | # like integer or float. |
||
597 | DEFAULT_NUMERIC bigint |
||
598 | |||
599 | # Set it to 0 if you don't want to export milliseconds from Oracle timestamp |
||
600 | # columns. Timestamp will be formated with to_char(..., 'YYYY-MM-DD HH24:MI:SS') |
||
601 | # Enabling this directive, the default, format is 'YYYY-MM-DD HH24:MI:SS.FF'. |
||
602 | ENABLE_MICROSECOND 1 |
||
603 | |||
604 | # If you want to replace some columns as PostgreSQL boolean define here a list |
||
605 | # of tables and column separated by space as follows. You can also give a type |
||
606 | # and a precision to automatically convert all fields of that type as a boolean. |
||
607 | # For example: NUMBER:1 or CHAR:1 will replace any field of type number(1) or |
||
608 | # char(1) as a boolean in all exported tables. |
||
609 | #REPLACE_AS_BOOLEAN TB_NAME1:COL_NAME1 TB_NAME1:COL_NAME2 TB_NAME2:COL_NAME2 |
||
610 | |||
611 | # Use this to add additional definitions of the possible boolean values in Oracle |
||
612 | # field. You must set a space separated list of TRUE:FALSE values. BY default: |
||
613 | #BOOLEAN_VALUES yes:no y:n 1:0 true:false enabled:disabled |
||
614 | |||
615 | # When Ora2Pg find a "zero" date: 0000-00-00 00:00:00 it is replaced by a NULL. |
||
616 | # This could be a problem if your column is defined with NOT NULL constraint. |
||
617 | # If you can not remove the constraint, use this directive to set an arbitral |
||
618 | # date that will be used instead. You can also use -INFINITY if you don't want |
||
619 | # to use a fake date. |
||
620 | #REPLACE_ZERO_DATE 1970-01-01 00:00:00 |
||
621 | |||
622 | # Some time you need to force the destination type, for example a column |
||
623 | # exported as timestamp by Ora2Pg can be forced into type date. Value is |
||
624 | # a comma-separated list of TABLE:COLUMN:TYPE structure. If you need to use |
||
625 | # comma or space inside type definition you will have to backslash them. |
||
626 | #MODIFY_TYPE TABLE1:COL3:varchar,TABLE1:COL4:decimal(9\,6) |
||
627 | |||
628 | #------------------------------------------------------------------------------ |
||
629 | # GRANT SECTION (Control priviledge and owner export) |
||
630 | #------------------------------------------------------------------------------ |
||
631 | |||
632 | # Set this to 1 to replace default password for all extracted user |
||
633 | # during GRANT export |
||
634 | GEN_USER_PWD 0 |
||
635 | |||
636 | # By default the owner of database objects is the one you're using to connect |
||
637 | # to PostgreSQL. If you use an other user (e.g. postgres) you can force |
||
638 | # Ora2Pg to set the object owner to be the one used in the Oracle database by |
||
639 | # setting the directive to 1, or to a completely different username by setting |
||
640 | # the directive value # to that username. |
||
641 | FORCE_OWNER 0 |
||
642 | |||
643 | |||
644 | #------------------------------------------------------------------------------ |
||
645 | # DATA SECTION (Control data export behaviors) |
||
646 | #------------------------------------------------------------------------------ |
||
647 | |||
648 | # Extract data by bulk of DATA_LIMIT tuples at once. Default 10000. If you set |
||
649 | # a high value be sure to have enough memory if you have million of rows. |
||
650 | #DATA_LIMIT 10000 |
||
651 | DATA_LIMIT 50000 |
||
652 | |||
653 | |||
654 | # When Ora2Pg detect a table with some BLOB it will automatically reduce the |
||
655 | # value of this directive by dividing it by 10 until his value is below 1000. |
||
656 | # You can control this value by setting BLOB_LIMIT. Exporting BLOB use lot of |
||
657 | # ressources, setting it to a too high value can produce OOM. |
||
658 | #BLOB_LIMIT 500 |
||
659 | |||
660 | # By default all data that are not of type date or time are escaped. If you |
||
661 | # experience any problem with that you can set it to 1 to disable it. This |
||
662 | # directive is only used during a COPY export type. |
||
663 | # See STANDARD_CONFORMING_STRINGS for enabling/disabling escape with INSERT |
||
664 | # statements. |
||
665 | NOESCAPE 0 |
||
666 | |||
667 | # This directive may be used if you want to change the default isolation |
||
668 | # level of the data export transaction. Default is now to set the level |
||
669 | # to a serializable transaction to ensure data consistency. Here are the |
||
670 | # allowed value of this directive: readonly, readwrite, serializable and |
||
671 | # committed (read committed). |
||
672 | TRANSACTION serializable |
||
673 | |||
674 | # This controls whether ordinary string literals ('...') treat backslashes |
||
675 | # literally, as specified in SQL standard. This was the default before Ora2Pg |
||
676 | # v8.5 so that all strings was escaped first, now this is currently on, causing |
||
677 | # Ora2Pg to use the escape string syntax (E'...') if this parameter is not |
||
678 | # set to 0. This is the exact behavior of the same option in PostgreSQL. |
||
679 | # This directive is only used during INSERT export to build INSERT statements. |
||
680 | # See NOESCAPE for enabling/disabling escape in COPY statements. |
||
681 | STANDARD_CONFORMING_STRINGS 1 |
||
682 | |||
683 | # Use this directive to set the database handle's 'LongReadLen' attribute to |
||
684 | # a value that will be the larger than the expected size of the LOB. The default |
||
685 | # is 1MB witch may not be enough to extract BLOB objects. If the size of the LOB |
||
686 | # exceeds the 'LongReadLen' DBD::Oracle will return a 'ORA-24345: A Truncation' |
||
687 | # error. Default: 1023*1024 bytes. Take a look at this page to learn more: |
||
688 | # http://search.cpan.org/~pythian/DBD-Oracle-1.22/Oracle.pm#Data_Interface_for_Persistent_LOBs |
||
689 | # |
||
690 | # Important note: If you increase the value of this directive take care that |
||
691 | # DATA_LIMIT will probably needs to be reduced. Even if you only have a 1MB blob |
||
692 | # trying to read 10000 of them (the default DATA_LIMIT) all at once will require |
||
693 | # 10GB of memory. You may extract data from those table separately and set a |
||
694 | # DATA_LIMIT to 500 or lower, otherwise you may experience some out of memory. |
||
695 | #LONGREADLEN 1047552 |
||
696 | |||
697 | # If you want to bypass the 'ORA-24345: A Truncation' error, set this directive |
||
698 | # to 1, it will truncate the data extracted to the LongReadLen value. |
||
699 | #LONGTRUNCOK 0 |
||
700 | |||
701 | # Disable this if you don't want to load full content of BLOB and CLOB and use |
||
702 | # LOB locators instead. This is usefull to not having to set LONGREADLEN. Note |
||
703 | # that this will not improve speed of BLOB export as most of the time is always |
||
704 | # consumed by the bytea escaping and in this case export is done line by line |
||
705 | # and not by chunk of DATA_LIMIT rows. For more information on how it works, see |
||
706 | # http://search.cpan.org/~pythian/DBD-Oracle-1.74/lib/DBD/Oracle.pm#Data_Interface_for_LOB_Locators |
||
707 | # Default is enabled, it will not use LOB locators for backward compatibility. |
||
708 | NO_LOB_LOCATOR 1 |
||
709 | |||
710 | # Use getStringVal() instead of getClobVal() for XML data export. Default is |
||
711 | # enabled for backward compatibility. |
||
712 | XML_PRETTY 0 |
||
713 | |||
714 | # Enable this directive if you want to continue direct data import on error. |
||
715 | # When Ora2Pg receives an error in the COPY or INSERT statement from PostgreSQL |
||
716 | # it will log the statement to a file called TABLENAME_error.log in the output |
||
717 | # directory and continue to next bulk of data. Like this you can try to fix the |
||
718 | # statement and manually reload the error log file. Default is disabled: abort |
||
719 | # import on error. |
||
720 | LOG_ON_ERROR 0 |
||
721 | |||
722 | # If you want to convert CHAR(n) from Oracle into varchar(n) or text under |
||
723 | # PostgreSQL, you might want to do some triming on the data. By default |
||
724 | # Ora2Pg will auto-detect this conversion and remove any withspace at both |
||
725 | # leading and trailing position. If you just want to remove the leadings |
||
726 | # character, set the value to LEADING. If you just want to remove the trailing |
||
727 | # character, set the value to TRAILING. Default value is BOTH. |
||
728 | TRIM_TYPE BOTH |
||
729 | |||
730 | # The default triming character is space, use the directive bellow if you need |
||
731 | # to change the character that will be removed. For example, set it to - if you |
||
732 | # have leading - in the char(n) field. To use space as triming charger, comment |
||
733 | # this directive, this is the default value. |
||
734 | #TRIM_CHAR - |
||
735 | |||
736 | # Internal timestamp retrieves from custom type are extracted in the following |
||
737 | # format: 01-JAN-77 12.00.00.000000 AM. It is impossible to know the exact century |
||
738 | # that must be used, so by default any year below 49 will be added to 2000 |
||
739 | # and others to 1900. You can use this directive to change this default value. |
||
740 | # this is only relevant if you have user defined type with a column timestamp. |
||
741 | INTERNAL_DATE_MAX 49 |
||
742 | |||
743 | #------------------------------------------------------------------------------ |
||
744 | # PERFORMANCES SECTION (Control export/import performances) |
||
745 | #------------------------------------------------------------------------------ |
||
746 | |||
747 | # Multiprocess support. This directive replace the obsolete THREAD_COUNT |
||
748 | # variable. Ora2Pg now use fork() to do parallel process instead of Perl |
||
749 | # threads. This directive should defined the number of parallel connection |
||
750 | # to PostgreSQL for direct data migration. The limit is the number of cores |
||
751 | # on your machine. This is useful if PostgreSQL is the bottleneck. COPIES |
||
752 | JOBS 1 |
||
753 | |||
754 | # Multiprocess support. This directive should defined the number of parallel |
||
755 | # connection to Oracle when extracting data. The limit is the number of cores |
||
756 | # on your machine. This is useful if Oracle is the bottleneck. Take care that |
||
757 | # this directive can only be used if there is a column defined in DEFINED_PK. |
||
758 | ORACLE_COPIES 1 |
||
759 | |||
760 | # Multiprocess support. This directive should defined the number of tables |
||
761 | # in parallel data extraction. The limit is the number of cores on your machine. |
||
762 | # Ora2Pg will open one database connection for each parallel table extraction. |
||
763 | # This directive, when upper than 1, will invalidate ORACLE_COPIES but not JOBS. |
||
764 | # Note that this directive when set upper that 1 will also automatically enable |
||
765 | # the FILE_PER_TABLE directive if your are exporting to files. |
||
766 | #PARALLEL_TABLES 1 |
||
767 | PARALLEL_TABLES 2 |
||
768 | |||
769 | # Multiprocess support. This directive is used to split the select queries |
||
770 | # between the different connections to Oracle if ORA_COPIES is used. Ora2Pg |
||
771 | # will extract data with the following prepare statement: |
||
772 | # SELECT * FROM TABLE WHERE MOD(COLUMN, $ORA_COPIES) = ? |
||
773 | # Where $ORA_COPIES is the total number of cores used to extract data and set |
||
774 | # with ORA_COPIES directive, and ? is the current core used at execution time. |
||
775 | # This means that Ora2Pg needs to know the numeric column to use in this query. |
||
776 | # If this column is a real, float, numeric or decimal, you must add the ROUND() |
||
777 | # function with the column to round the value to the nearest integer. |
||
778 | #DEFINED_PK TABLE:COLUMN TABLE:ROUND(COLUMN) |
||
779 | |||
780 | # Enabling this directive force Ora2Pg to drop all indexes on data import |
||
781 | # tables, except automatic index on primary key, and recreate them at end |
||
782 | # of data import. This may improve speed a lot during a fresh import. |
||
783 | DROP_INDEXES 0 |
||
784 | |||
785 | # Specifies whether transaction commit will wait for WAL records to be written |
||
786 | # to disk before the command returns a "success" indication to the client. This |
||
787 | # is the equivalent to set synchronous_commit directive of postgresql.conf file. |
||
788 | # This is only used when you load data directly to PostgreSQL, the default is |
||
789 | # off to disable synchronous commit to gain speed at writing data. Some modified |
||
790 | # versions of PostgreSQL, like Greenplum, do not have this setting, so in this |
||
791 | # case set this directive to 1, ora2pg will not try to change the setting. |
||
792 | SYNCHRONOUS_COMMIT 0 |
||
793 | |||
794 | |||
795 | #------------------------------------------------------------------------------ |
||
796 | # PLSQL SECTION (Control SQL and PL/SQL to PLPGSQL rewriting behaviors) |
||
797 | #------------------------------------------------------------------------------ |
||
798 | |||
799 | # If the above configuration directive is not enough to validate your PL/SQL code |
||
800 | # enable this configuration directive to allow export of all PL/SQL code even if |
||
801 | # it is marked as invalid. The 'VALID' or 'INVALID' status applies to functions, |
||
802 | # procedures, packages and user defined types. |
||
803 | EXPORT_INVALID 0 |
||
804 | |||
805 | # Enable PLSQL to PLPSQL conversion. This is a work in progress, feel |
||
806 | # free modify/add you own code and send me patches. The code is under |
||
807 | # function plsql_toplpgsql in Ora2PG/PLSQL.pm. Default enabled. |
||
808 | PLSQL_PGSQL 0 |
||
809 | |||
810 | # Ora2Pg can replace all conditions with a test on NULL by a call to the |
||
811 | # coalesce() function to mimic the Oracle behavior where empty field are |
||
812 | # considered equal to NULL. Ex: (field1 IS NULL) and (field2 IS NOT NULL) will |
||
813 | # be replaced by (coalesce(field1::text, '') = '') and (field2 IS NOT NULL AND |
||
814 | # field2::text <> ''). You might want this replacement to be sure that your |
||
815 | # application will have the same behavior but if you have control on you app |
||
816 | # a better way is to change it to transform empty string into NULL because |
||
817 | # PostgreSQL makes the difference. |
||
818 | NULL_EQUAL_EMPTY 0 |
||
819 | |||
820 | # Force empty_clob() and empty_blob() to be exported as NULL instead as empty |
||
821 | # string for the first one and \\x for the second. If NULL is allowed in your |
||
822 | # column this might improve data export speed if you have lot of empty lob. |
||
823 | EMPTY_LOB_NULL 0 |
||
824 | |||
825 | # If you don't want to export package as schema but as simple functions you |
||
826 | # might also want to replace all call to package_name.function_name. If you |
||
827 | # disable the PACKAGE_AS_SCHEMA directive then Ora2Pg will replace all call |
||
828 | # to package_name.function_name() by package_name_function_name(). Default |
||
829 | # is to use a schema to emulate package. |
||
830 | PACKAGE_AS_SCHEMA 0 |
||
831 | |||
832 | # Enable this directive if the rewrite of Oracle native syntax (+) of |
||
833 | # OUTER JOIN is broken. This will force Ora2Pg to not rewrite such code, |
||
834 | # default is to try to rewrite simple form of rigth outer join for the |
||
835 | # moment. |
||
836 | REWRITE_OUTER_JOIN 0 |
||
837 | |||
838 | # By default Ora2pg rewrite add_month(), add_year() and date_trunc() functions |
||
839 | # set it to 0 to not translate those functions if it breaks code. |
||
840 | DATE_FUNCTION_REWRITE 1 |
||
841 | |||
842 | #------------------------------------------------------------------------------ |
||
843 | # ASSESSMENT SECTION (Control migration assessment behaviors) |
||
844 | #------------------------------------------------------------------------------ |
||
845 | |||
846 | # Activate the migration cost evaluation. Must only be used with SHOW_REPORT, |
||
847 | # FUNCTION, PROCEDURE, PACKAGE and QUERY export type. Default is disabled. |
||
848 | # Note that enabling this directive will force PLSQL_PGSQL activation. |
||
849 | ESTIMATE_COST 0 |
||
850 | |||
851 | # Set the value in minutes of the migration cost evaluation unit. Default |
||
852 | # is five minutes per unit. |
||
853 | COST_UNIT_VALUE 5 |
||
854 | |||
855 | # By default when using SHOW_REPORT the migration report is generated as |
||
856 | # simple text, enabling this directive will force ora2pg to create a report |
||
857 | # in HTML format. |
||
858 | DUMP_AS_HTML 0 |
||
859 | |||
860 | # Set the total number of tables to display in the Top N per row and size |
||
861 | # list in the SHOW_TABLE and SHOW_REPORT output. Default 10. |
||
862 | TOP_MAX 10 |
||
863 | |||
864 | # Use this directive to redefined the number of human-days limit where the |
||
865 | # migration assessment level must switch from B to C. Default is set to 10 |
||
866 | # human-days. |
||
867 | HUMAN_DAYS_LIMIT 5 |
||
868 | |||
869 | # Set the comma separated list of username that must be used to filter |
||
870 | # queries from the DBA_AUDIT_TRAIL table. Default is to not scan this |
||
871 | # table and to never look for queries. This parameter is used only with |
||
872 | # SHOW_REPORT and QUERY export type with no input file for queries. |
||
873 | # Note that queries will be normalized before output unlike when a file |
||
874 | # is given at input using the -i option or INPUT directive. |
||
875 | #AUDIT_USER USERNAME1,USERNAME2 |
||
876 | |||
877 | # By default Ora2Pg will convert call to SYS_GUID() Oracle function |
||
878 | # with a call to uuid_generate_v4() from uuid-ossp extension. You can |
||
879 | # redefined it to use the gen_random_uuid() function from pgcrypto |
||
880 | # extension by changing the function name below. |
||
881 | #UUID_FUNCTION uuid_generate_v4 |
||
882 | |||
883 | #------------------------------------------------------------------------------ |
||
884 | # POSTGRESQL FEATURE SECTION (Control which PostgreSQL features are available) |
||
885 | #------------------------------------------------------------------------------ |
||
886 | |||
887 | # Allow support of WHEN clause in trigger definition PG>=9.0 |
||
888 | PG_SUPPORTS_WHEN 1 |
||
889 | |||
890 | # Allow support of INSTEAD OF in triggers definition PG>=9.1 |
||
891 | PG_SUPPORTS_INSTEADOF 1 |
||
892 | |||
893 | # Allow support of native MATERIALIZED VIEW PG>=9.3. If disable Ora2Pg |
||
894 | # will use old behavior, a normal table with a set of function to refresh |
||
895 | # the view. |
||
896 | PG_SUPPORTS_MVIEW 1 |
||
897 | |||
898 | # If enabled, export view with CHECK OPTION. Disable it if you have PostgreSQL |
||
899 | # version prior 9.4. Default, enabled |
||
900 | PG_SUPPORTS_CHECKOPTION 1 |
||
901 | |||
902 | # PostgreSQL versions below 9.x do not support IF EXISTS in DDL statements. |
||
903 | # Disabling the directive with value 0 will prevent Ora2Pg to add those |
||
904 | # keywords in all generated statements. |
||
905 | PG_SUPPORTS_IFEXISTS 1 |
||
906 | |||
907 | # Use btree_gin extenstion to create bitmap like index with pg >= 9.4 |
||
908 | # You will need to create the extension by yourself: |
||
909 | # create extension btree_gin; |
||
910 | # Default is to create GIN index, when disabled, a btree index will be created |
||
911 | BITMAP_AS_GIN 1 |
||
912 | |||
913 | # Use pg_background extension to create an autonomous transaction instead |
||
914 | # of using a dblink wrapper. With pg >= 9.5 only, default is to use dblink. |
||
915 | PG_BACKGROUND 0 |
||
916 | |||
917 | #------------------------------------------------------------------------------ |
||
918 | # SPATIAL SECTION (Control spatial geometry export) |
||
919 | #------------------------------------------------------------------------------ |
||
920 | |||
921 | # Enable this directive if you want Ora2Pg to detect the real spatial type and |
||
922 | # dimensions used in a spatial column. By default Ora2Pg will look at spatial |
||
923 | # indexes to see if the layer_gtype and sdo_indx_dims constraint parameters have |
||
924 | # been set, otherwise column will be created with the non-constrained "geometry" |
||
925 | # type. Enabling this feature will force Ora2Pg to scan a sample of 50000 lines |
||
926 | # to look at the GTYPE used. You can increase or reduce the sample by setting |
||
927 | # the value of AUTODETECT_SPATIAL_TYPE to the desired number of line. |
||
928 | AUTODETECT_SPATIAL_TYPE 1 |
||
929 | |||
930 | # Disable this directive if you don't want to automatically convert SRID to |
||
931 | # EPSG using the sdo_cs.map_oracle_srid_to_epsg() function. Default: enabled |
||
932 | # If the SDO_SRID returned by Oracle is NULL, it will be replaced by the |
||
933 | # default value 8307 converted to its EPSG value: 4326 (see DEFAULT_SRID) |
||
934 | # If the value is upper than 1, all SRID will be forced to this value, in |
||
935 | # this case DEFAULT_SRID will not be used when Oracle returns a null value |
||
936 | # and the value will be forced to CONVERT_SRID. |
||
937 | # Note that it is also possible to set the EPSG value on Oracle side when |
||
938 | # sdo_cs.map_oracle_srid_to_epsg() return NULL if your want to force the value: |
||
939 | # Ex: system> UPDATE sdo_coord_ref_sys SET legacy_code=41014 WHERE srid = 27572; |
||
940 | CONVERT_SRID 1 |
||
941 | |||
942 | # Use this directive to override the default EPSG SRID to used: 4326. |
||
943 | # Can be overwritten by CONVERT_SRID, see above. |
||
944 | DEFAULT_SRID 4326 |
||
945 | |||
946 | # This directive can take three values: WKT (default), WKB and INTERNAL. |
||
947 | # When it is set to WKT, Ora2Pg will use SDO_UTIL.TO_WKTGEOMETRY() to |
||
948 | # extract the geometry data. When it is set to WKB, Ora2Pg will use the |
||
949 | # binary output using SDO_UTIL.TO_WKBGEOMETRY(). If those two extract type |
||
950 | # are called at Oracle side, they are slow and you can easily reach Out Of |
||
951 | # Memory when you have lot of rows. Also WKB is not able to export 3D geometry |
||
952 | # and some geometries like CURVEPOLYGON. In this case you may use the INTERNAL |
||
953 | # extraction type. It will use a pure Perl library to convert the SDO_GEOMETRY |
||
954 | # data into a WKT representation, the translation is done on Ora2Pg side. |
||
955 | # This is a work in progress, please validate your exported data geometries |
||
956 | # before use. |
||
957 | GEOMETRY_EXTRACT_TYPE INTERNAL |
||
958 | |||
959 | |||
960 | #------------------------------------------------------------------------------ |
||
961 | # FDW SECTION (Control Foreign Data Wrapper export) |
||
962 | #------------------------------------------------------------------------------ |
||
963 | |||
964 | # This directive is used to set the name of the foreign data server that is used |
||
965 | # in the "CREATE SERVER name FOREIGN DATA WRAPPER oracle_fdw ..." command. This |
||
966 | # name will then be used in the "CREATE FOREIGN TABLE ..." SQL command. Default |
||
967 | # is arbitrary set to orcl. This only concerns export type FDW. |
||
968 | FDW_SERVER orcl |
||
969 | |||
970 | |||
971 | #------------------------------------------------------------------------------ |
||
972 | # MYSQL SECTION (Control MySQL export behavior) |
||
973 | #------------------------------------------------------------------------------ |
||
974 | |||
975 | # Enable this if double pipe and double ampersand (|| and &&) should not be |
||
976 | # taken as equivalent to OR and AND. It depend of the variable @sql_mode, |
||
977 | # Use it only if Ora2Pg fail on auto detecting this behavior. |
||
978 | MYSQL_PIPES_AS_CONCAT 0 |
||
979 | |||
980 | # Enable this directive if you want EXTRACT() replacement to use the internal |
||
981 | # format returned as an integer, for example DD HH24:MM:SS will be replaced |
||
982 | # with format; DDHH24MMSS::bigint, this depend of your apps usage. |
||
983 | MYSQL_INTERNAL_EXTRACT_FORMAT 0 |
||
984 |