Environment variables: Oracle connector

The Oracle Connector stage uses these environment variables.

CC_GUARDIUM_EVENTS
Set this environment variable to specify whether connectors report the InfoSphere DataStage context information to the InfoSphere Guardium Database Activity monitor.
CC_IGNORE_TIME_LENGTH_AND_SCALE
Set this environment variable to change the behavior of the connector on the parallel canvas.
CC_ORA_BIND_DATETIME_AS_CHAR
Set this environment variable to specify whether to bind Date and Timestamp values as character values.
CC_ORA_BIND_FOR_NCHARS
Set this connector environment variable to specify whether to bind a list of the character columns as national character columns with the Oracle database.
CC_ORA_BIND_KEYWORD
Set this environment variable to specify the identifier that indicates a bind parameter in a user-defined SQL statement.
CC_ORA_CHECK_CONVERSION
Set this environment variable to specify whether exceptions are thrown when data loss occurs because of a conversion from the Unicode character set to the native character set of the database.
CC_ORACLECONNECTOR_DEFAULT_CONNECTION_VERSION
Set this environment variable to specify the default value for the Oracle client version property in the Oracle connector stages.
CC_ORA_DEFAULT_DATETIME_TIME
Set this environment variable to specify the values for hours, minutes, and seconds when the connector writes the InfoSphere DataStage Date type to an Oracle DATE or TIMESTAMP column.
CC_ORA_DEFAULT_DATETIME_DATE
Set this environment variable to specify the default values for the month, day, and year when the connector writes from a InfoSphere DataStage Time type to an Oracle DATE or TIMESTAMP column.
CC_ORA_DROP_UNMATCHED_FIELDS_DEFAULT
Set this environment variable to specify the Drop unmatched fields property when the property is not set correctly in an Oracle Connector job generated by the connector migration tool.
CC_ORA_INDEX_MAINT_SINGLE_ROW
Set this environment variable to specify how index rows are inserted during bulk load.
CC_ORA_INVALID_DATETIME_ACTION
Set this environment variable to insert a NULL value into the database for invalid Date, Time or Timestamp fields.
CC_ORA_LOB_LOCATOR_COLUMNS
Set this environment variable to specify whether the connector uses OCI LOB locators when the connector writes data into LOB columns. For example, use this environment variable when you want to support SDO_GEOMETRY and XMLTYPE columns and functions.
CC_ORA_MAX_ERRORS_REPORT
Set this environment variable to specify the maximum number of errors to report to the log file when an operation writes an array or bulk loads data.
CC_MSG_LEVEL
Set this environment variable to specify the minimum severity of the messages that the connector reports in the log file.
CC_ORA_NLS_LANG_ENV
Set this environment variable to specify whether the NLS_LANG character set is used when the connector initializes the Oracle client environment.
CC_ORA_NODE_PLACEHOLDER_NAME
CC_ORA_NODE_USE_PLACEHOLDER
CC_ORA_NULL_CHAR_ACTION
CC_ORA_OPTIMIZE_CONNECTIONS
CC_ORA_PRESERVE_DATE_TYPE_NAME
CC_ORA_ROWS_REJECTED_MSG_INFO
CC_ORA_UNBOUNDED_BINARY_LENGTH
Set this environment variable to override the default length that the connector uses for InfoSphere DataStage Binary and VarBinary columns for which a length is not defined in the design schema.
CC_ORA_UNBOUNDED_STRING_LENGTH
Set this environment variable to override the default length that the connector uses for InfoSphere DataStage Char, VarChar, NChar, and NVarChar columns for which a length is not defined in the design schema.
CC_ORA_XMLTYPE_CSID_BLOB
CC_SE_TIMESTAMP_FF
Set this environment variable to specify whether decimal point and fractional digits are included in the timestamp values, when the connector runs in server jobs.
CC_TRUNCATE_STRING_WITH_NULL
Set this environment variable to truncate string data that includes the string 0x00.
CC_TRUNCATE_NSTRING_WITH_NULL
Set this environment variable to truncate string data that includes the string 0x00.
CC_USE_EXTERNAL_SCHEMA_ON_MISMATCH
Set this environment variable to use an external schema rather than a design schema when the schemas do not match.