-
Title
Can I control the Oracle Export/Import parameters used in the "copy table" or "append table" comm -
Description
When running the "copy table" or "append table" commands, the question sometimes arises as to whether one can specify the parameters to be used in the Oracle Export/Import processes which are associated with the "copy table", etc. The parameters cover a wide range of options including, but not limited to, BUFFER (buffer size for fetch of rows), COMPRESS (compressing into single extent), DIRECT, ROWS (=N means only object creation DDL to be exported), GRANTS, INDEXES, TRIGGERS, CONSTRAINTS, etc. Users fine tune the parameters, based on their specific needs when running Oracle Export/Import.
-
Cause
N.A.
-
Resolution
When running "copy table" or "append table" commands, Shareplex only allows the parameter BUFFER to be specified, using Shareplex parameters the SP_OSY_EXP_BUFFER_SIZE and SP_OSY_IMP_BUFFER_SIZE. These are classified as sync parameters and are set on source and target for Export and Import respectively.
Additional Information:
The parameters that are passed to Oracle Export/Import by the "copy table" can be viewed in the sync server or sync client files located in the $SP_SYS_VARDIR/log directories on source and target respectively, where $SP_SYS_VARDIR is an environment variable that points to the Shareplex variable directory (also termed as vardir). Here is a sample entry for the parameters from that file:
server_name # more sync_svr_26_SID_server_name_p2474.log
Tue Nov 11/20:10:43.950:: SYNC SERVER START: pid = 2474
Tue Nov 11/20:10:43.952:: Debug : 0x00000000
.
.
Tue Nov 11/20:10:45.100:: File Arg: mode=dynamic
Tue Nov 11/20:10:45.100:: File Arg: target=10.1.1.171
Tue Nov 11/20:10:45.102:: File Arg: source_sid=SID
Tue Nov 11/20:10:45.106:: File Arg: target_sid=SID1
Tue Nov 11/20:10:45.108:: File Arg: routing_spec=32768
Tue Nov 11/20:10:45.108:: File Arg: queue=server_name
Tue Nov 11/20:10:45.110:: File Arg: append=y
Tue Nov 11/20:10:45.110:: File Arg: allmustlock=n
Tue Nov 11/20:10:45.110:: File Arg: port=2501
Tue Nov 11/20:10:45.111:: File Arg: num_threads=5
Tue Nov 11/20:10:45.111:: File Arg: compress=6
Tue Nov 11/20:10:45.111:: File Arg: timeout=60
Tue Nov 11/20:10:45.112:: File Arg: locktimeout=2
Tue Nov 11/20:10:45.112:: File Arg: markertimeout=1800
Tue Nov 11/20:10:45.112:: File Arg: buffer=1024
Tue Nov 11/20:10:45.113:: File Arg: ora_connect=5787d4d0f20c16e699
4545
Tue Nov 11/20:10:45.113:: File Arg: ora_home=/u00/oracle/product/1
0g
Tue Nov 11/20:10:45.113:: File Arg: splex_schema="owner"
Tue Nov 11/20:10:45.113:: File Arg: logdir=/u01/owner/var/log
Tue Nov 11/20:10:45.114:: File Arg: tempdir=/u01/owner/var/temp
Tue Nov 11/20:10:45.114:: File Arg: table_def="owner"."TABLE1"->"owner"."TABLE1"->The important point to note is that you can only view the parameters after the fact, in the sense that the "copy table" is first issued which triggers a configuring of these parameters, which can then be viewed. As previously mentioned, the only parameter that was configurable was BUFFER. Further, once that parameter is configured, it will be applied to subsequent "copy table" commands unless it is changed.