Oracle Database

supported versions

     Oracle Database 11g Release 2 version 11.2.0.4

✓

✓

     Oracle Database 12c Release 1 version 12.1.0.2 and Release 2 version 12.2.0.1

✓

✓

     Oracle Database 18c (all versions)

✓

✓

     Oracle Database 19c (all versions)

✓

✓

     Oracle Database 21c (all versions)

✓

Known issue DEV-36641: column map in Database Writer does not work with wildcard

✓

supported topologies

     PDB / CDB

✓

✓

     application PDB

✓

     RAC (all versions)

✓

✓

can read from

     primary database

✓

✓

     logical standby database

✓

✓

     Active Data Guard non-CDB standby database

via archive log

     Active Data Guard CDB standby database

via archive log (through version 19.9 only)

     Data Guard physical standby

via archive log

     downstream database

✓

     reference-partitioned tables

✓

key features

     DML operations replicable in target

INSERT, UPDATE, DELETE

INSERT, UPDATE, DELETE, TRUNCATE

     schema evolution

for 11g to 18c only, not for PDB / CDB

for all supported versions

     uncommitted transaction support

✓

     Striim-side transaction caching

✓

     recovery

✓

✓

     quiesce

✓

✓

     bidirectional replication

✓

✓

     SSL

✓

✓

     Oracle Native Network Encryption

used automatically in Striim Cloud

not supported in Striim Platform in this release

     supported when Striim Platform is running in Microsoft Windows

✓

summary of supported data types (for full details, see Oracle Reader and OJet data type support and correspondence)Oracle Reader and OJet data type support and correspondence

✓

✓

✓

see Oracle Reader and OJet data type support and correspondenceOracle Reader and OJet data type support and correspondence

see Oracle Reader and OJet data type support and correspondenceOracle Reader and OJet data type support and correspondence

✓

see Oracle Reader and OJet data type support and correspondenceOracle Reader and OJet data type support and correspondence

Bidirectional Marker Table

String

When performing bidirectional replication, the fully qualified name of the marker table (see Bidirectional replication). This setting is case-sensitive.

CDDL Action

enum

Process

18c and earlier only: see Handling schema evolution.

CDDL Capture

Boolean

False

18c and earlier only: enables schema evolution (see Handling schema evolution). When set to True, Dictionary Mode must be set to Offline Catalog and Support PDB and CDB must be False.

Committed Transactions

Boolean

True

LogMiner only: by default, only committed transactions are read. Set to False to read both committed and uncommitted transactions.

Compression

Boolean

False

If set to True, update operations for tables that have primary keys include only the primary key and modified columns, and delete operations include only the primary key. With the default value of False, all columns are included. See Oracle Reader example output for examples.

Set to True when Oracle Reader's output stream is the input stream of Cassandra Writer.

Connection Retry Policy

String

timeOut=30, retryInterval=30, maxRetries=3

With the default setting:

Negative values are not supported.

Connection URL

String

<hostname>:<port>:<SID> or <hostname>:<port>/<service name>

If using Oracle 12c or later with PDB, use the SID for the CDB service. (Note that with DatabaseReader and DatabaseWriter, you must use the SID for the PDB service instead.)

If using Amazon RDS for Oracle, the connection URL is <endpoint>:<port>:<DB name>. The required values are displayed at Instance Actions > see details. 

Database Role

String

PRIMARY

Leave set to the default value of PRIMARY except when you Reading from a standby.

Dictionary Mode

String

OnlineCatalog

Leave set to the default of OnlineCatalog except when CDDL Capture is True or you are Reading from a standby.

Excluded Tables

String

Data for any tables specified here will not be returned. For example, if Tables uses a wildcard, data from any tables specified here will be omitted. Multiple table names (separated by semicolons) and wildcards may be used exactly as for Tables.

Exclude Users

String

Optionally, specify one or more Oracle user names, separated by semicolons, whose transactions will be omitted from OracleReader output. Possible uses include:

External Dictionary File

String

Leave blank except when you Reading from a standby.

Fetch Size

Integer

1000

LogMiner only: the number of records the JDBC driver will return at a time. For example, if Oracle Reader queries LogMiner and there are 2300 records available, the JDBC driver will return two batches of 1000 records and one batch of 300.

Filter Transaction Boundaries

Boolean

True

With the default value of True, BEGIN and COMMIT operations are filtered out. Set to False to include BEGIN and COMMIT operations.

Ignorable Exception

String

Do not change unless instructed to by Striim support.

JAAS Configuration

String

If you Enable Kerberos authentication for Oracle and PostgreSQL, use this property to configure it.

To authenticate Oracle using a Kerberos principal, specify java.security.krb5.conf=/<path>/krb5.conf; doNotPrompt=true; principal=oracleclient@<Kerberos realm>.

For example, java.security.krb5.conf=/etc/krb5.conf; doNotPrompt=true; principal=oracleclient@MYDOMAIN.COM

To authenticate Oracle using a Kerberos credential cache, specify java.security.krb5.conf=/<path>/krb5.conf; doNotPrompt=true; useTicketCache=true; ticketCache=<fully qualified credential cache file name.

For example, java.security.krb5.conf=/etc/krb5.conf; doNotPrompt=true; useTicketCache=true; ticketCache=/home/Jdbc/Security/krbcache/krb5cc'

Password

encrypted password

the password specified for the username (see Encrypted passwords)

Queue Size

Integer

2048

Quiesce Marker Table

String

QUIESCEMARKER

See Creating the QUIESCEMARKER table for Oracle Reader. Modify the default value if the quiesce marker table is not in the schema associated with the user specified in the Username. Three-part CDB / PDB names are not supported in this release.

Send Before Image

Boolean

True

set to False to omit before data from output

Set Conservative Range

Boolean

False

If reading from Oracle 19c, you have long-running transactions, and parallel DML mode is enabled (see Enable Parallel DML Mode), set this to True.

SSL Config

String

If using SSL with the Oracle JDBC driver, specify the required properties. Examples:

If using SSL for encryption only:

oracle.net.ssl_cipher_suites=
  (SSL_DH_anon_WITH_3DES_EDE_CBC_SHA,
    SSL_DH_anon_WITH_RC4_128_MD5, 
    SSL_DH_anon_WITH_DES_CBC_SHA)

If using SSL for encryption and server authentication:

javax.net.ssl.trustStore=
/etc/oracle/wallets/ewallet.p12;
javax.net.ssl.trustStoreType=PKCS12;
javax.net.ssl.trustStorePassword=********

If using SSL for encryption and both server and client authentication:

javax.net.ssl.trustStore=
/etc/oracle/wallets/ewallet.p12;
javax.net.ssl.trustStoreType=PKCS12;
javax.net.ssl.trustStorePassword=********;
javax.net.ssl.keyStore=/opt/Striim/certs;
javax.net.ssl.keyStoreType=JKS;
javax.net.ssl.keyStorePassword=********

Start SCN

String

Optionally specify an SCN from which to start reading (See Replicating Oracle data to another Oracle database for an example). Do not specify a start point prior to when supplemental logging was enabled.

If you are using schema evolution (see Handling schema evolution, set a Start SCN only if you are sure that there have been no DDL changes after that point.Handling schema evolution

See also Switching from initial load to continuous replication.

Start Timestamp

String

null

With the default value of null, only new (based on current system time) transactions are read. Specify a timestamp to read transactions that began after that time. The format is DD-MON-YYYY HH:MI:SS. For example, to start at 5:00 pm on July 15, 2017, specify 15-JUL-2017 17:00:00. Do not specify a start point prior to when supplemental logging was enabled.

If you are using schema evolution (see Handling schema evolution, set a Start Timestamp only if you are sure that there have been no DDL changes after that point.Handling schema evolution

Support PDB and CDB

Boolean

False

Set to True if reading from CDB or PDB.

Tables

String

The table or materialized view to be read (supplemental logging must be enabled as described in Configuring Oracle to use Oracle Reader) in the format <schema>.<table>. (If using Oracle 12c with PDB, use three-part names: <pdb>.<schema>.<table>.) Names are case-sensitive.

You may specify multiple tables and materialized views as a list separated by semicolons or with the % wildcard. For example, HR.% would read all tables in the HR schema. You may not specify a wildcard for the schema (that is, %.% is not supported). The % wildcard is allowed only at the end of the string. For example, mydb.prefix% is valid, but mydb.%suffix is not.

Unused columns are supported. Values in virtual columns will be set to null. If a table contains an invisible column, the application will terminate.

Table and column identifiers (names) may not exceed 30 bytes when using one-byte character sets. When using two-byte character sets, the limit is 15 characters.

Oracle character set AL32UTF8 (UTF-8) and character sets that are subsets of UTF-8, such as US7ASCII, are supported. Other character sets may work so long as their characters can be converted to UTF-8 by Striim.

See also Specifying key columns for tables without a primary key.

Transaction Buffer Disk Location

String

striim/LargeBuffer

See Transaction Buffer Type.

Transaction Buffer Spillover Size

String

100MB

When Transaction Buffer Type is Disk, the amount of memory that Striim will use to hold each in-process transaction before buffering it to disk. You may specify the size in MB or GB.

When Transaction Buffer Type is Memory, this setting has no effect.

Transaction Buffer Type

String

Disk

When Striim runs out of available Java heap space, the application will terminate. With Oracle Reader, typically this will happen when a transaction includes millions of INSERT, UPDATE, or DELETE events with a single COMMIT, at which point the application will terminate with an error message such as "increase the block size of large buffer" or "exceeded heap usage threshold."

To avoid this problem, with the default setting of Disk, when a transaction exceeds the Transaction Buffer Spillover Size, Striim will buffer it to disk at the location specified by the Transaction Buffer Disk Location property, then process it when memory is available.

When the setting is Disk and recovery is enabled (see Recovering applications), after the application halts, terminates, or is stopped the buffer will be reset, and during recovery any previously buffered transactions will restart from the beginning.Recovering applications

To disable transaction buffering, set Transaction Buffer Type to Memory.

Username

String

the username created as described in Configuring Oracle to use Oracle Reader; if using Oracle 12c or later with PDB, specify the CDB user (c##striim) 

Bidirectional Marker Table

String

When performing bidirectional replication, the fully qualified name of the marker table (see Bidirectional replication). This setting is case-sensitive. This property appears only if your Striim cluster has been licensed for bidirectional support.

CDDL Action

enum

Process

See Handling schema evolution.

CDDL Capture

Boolean

False

See Handling schema evolution.

Compression

Boolean

False

If set to True, update operations for tables that have primary keys include only the primary key and modified columns, and delete operations include only the primary key. With the default value of False, all columns are included. See Oracle Reader example output for examples.

Set to True when OJet's output stream is the input stream of Cassandra Writer.

Connection Retry Policy

String

timeOut=30, retryInterval=30, maxRetries=3

With the default setting:

Negative values are not supported.

Connection URL

String

jdbc:oracle:oci:@<hostname>:<port>:<SID> or jdbc:oracle:oci:@<hostname>:<port>/<service name>

If using Oracle 12c or later with PDB, use the SID for the CDB service. (Note that with DatabaseReader and DatabaseWriter, you must use the SID for the PDB service instead.)

If Downstream Capture is enabled, specify the connection URL for the downstream database. Otherwise, specify the connection URL for the primary database.

If the specified connection URL is invalid, deployment will fail with an "ORA-12170: TNS:Connect timeout occurred" error. Note that this error will also occur if Striim is unable to connect to Oracle for any other reason, such as a network outage or the database being offline.

Downstream Capture

Boolean

False

If set to True, downstream capture is enabled.

Downstream Capture Mode

String

None

REAL_TIME: real time downstream capture mode.

ARCHIVED_LOG: archived log downstream capture mode.

Excluded Tables

String

Data for any tables specified here will not be returned. For example, if Tables uses a wildcard, data from any tables specified here will be omitted. Multiple table names (separated by semicolons) and wildcards may be used exactly as for Tables.

Filter Transaction Boundaries

Boolean

True

OJet Config

String

null

A JSON string that specifies the configuration of OJet reader components. All configuration values are disabled by default. It uses the following format:

{
    "<Component name>" : [
        "<Parameter name:value>"
    ]
    ,...
}

The components are OJET and CAPTURE. They have following configuration parameters.

For example:

{
   "OJET":[
      “queuesize:20000”
   ],
   "OJET":[
      “open_txn_delay_time:60000”
   ],
   "CAPTURE":[
      “fetch_lcr_attributes:true”
   ]
}

Password

encrypted password

The password for the Oracle user specified in Username.

Primary Database Connection URL

String

If Downstream Capture is enabled, specify the connection URL for the database that is shipping the redo logs to the downstream database. In an Active Data Guard environment, this may be the primary database or a standby.

Primary Database Password

encrypted password

If Downstream Capture is enabled , specify the password for the user specified in Primary Database Username.

Primary Database Username

String

If Downstream Capture is enabled, specify the Oracle user you created as described in Configuring OJet with Active Data Guard.

Send Before Image

Boolean

True

Set to False to omit before data from output

SSL Config

String

If using SSL with the Oracle JDBC driver, specify the required properties using the syntax oracle.net.ssl_server_cert_dn=<server certificate domain name>;oracle.net.wallet_location="<path>. The wallet location must be accessible by Striim.

Start SCN

String

Optionally specify an SCN from which to start reading (See Replicating Oracle data to another Oracle database for an example). Do not specify a start point prior to when supplemental logging was enabled.

When you set a Start SCN, before running the application trigger a dictionary build by running this command:

EXECUTE DBMS_LOGMNR_D.BUILD( OPTIONS=>
  DBMS_LOGMNR_D.STORE_IN_REDO_LOGS);
SELECT CURRENT_SCN FROM V$DATABASE;

See also Switching from initial load to continuous replication.

Start Timestamp

String

null

With the default value of null, only new (based on current system time) transactions are read. If a timestamp is specified, transactions that began after that time are also read. The format is DD-MON-YYYY HH:MI:SS. For example, to start at 5:00 pm on July 15, 2017, specify 15-JUL-2017 17:00:00. Do not specify a start point prior to when supplemental logging was enabled.

Tables

String

The table or materialized view to be read (supplemental logging must be enabled as described in Configuring Oracle to use Oracle Reader) in the format <schema>.<table>. (If using Oracle 12c or later with PDB, use three-part names: <pdb>.<schema>.<table>.) Names are case-sensitive.

You may specify multiple tables and materialized views as a list separated by semicolons or with the % wildcard. For example, HR.% would read all tables in the HR schema. You may not specify a wildcard for the schema (that is, %.% is not supported). The % wildcard is allowed only at the end of the string. For example, mydb.prefix% is valid, but mydb.%suffix is not.

Unused columns are supported. Values in virtual columns will be set to null. If a table contains an invisible column, the application will terminate.

When reading from Oracle 11g or 12c Release 1 version 12.1, table and column identifiers (names) may not exceed 30 bytes. When using one-byte character sets, the limit is 30 characters. When using two-byte character sets, the limit is 15 characters.

When reading from Oracle 12c Release 2 version 12.2 or later, table and column identifiers (names) may not exceed 128 bytes. When using one-byte character sets, the limit is 128 characters. When using two-byte character sets, the limit is 64 characters.

Oracle character set AL32UTF8 (UTF-8) and character sets that are subsets of UTF-8, such as US7ASCII, are supported. Other character sets may work so long as their characters can be converted to UTF-8 by Striim.

See also Specifying key columns for tables without a primary key.

Transaction Age Spillover Limit

Integer

1000

OJet begins to spill messages from the Oracle server's memory to its hard disk for a particular transaction when the amount of time that any message in the transaction has been in memory exceeds the specified number of seconds.

Transaction Buffer Spillover Count

Integer

10000

OJet begins to spill messages from the Oracle server's memory to its hard disk for a particular transaction when the number of messages in memory for the transaction exceeds the specified number.

Username

String

The name of the OJet user created as described in Running the OJet setup script on Oracle or Configuring OJet with Active Data Guard. if using Oracle 12c or later with PDB, specify the CDB user (c##striim).

AuditSessionID

✓

Audit session ID associated with the user session making the change

BytesProcessed

✓

COMMIT_TIMESTAMP

✓

the UNIX epoch time the transaction was committed, based on the Striim server's time zone: Oracle Reader returns this as jorg.joda.time.DateTime, OJet returns it as java.lang.Long

COMMITSCN

x

✓

system change number (SCN) when the transaction committed

CURRENTSCN

✓

system change number (SCN) of the operation

DBCommitTimestamp

✓

the UNIX epoch time the transaction was committed, based on the Oracle server's time zone: Oracle Reader returns this as jorg.joda.time.DateTime, OJet returns it as java.lang.Long

DBTimestamp

✓

the UNIX epoch time of the operation, based on the Oracle server's time zone: Oracle Reader returns this as jorg.joda.time.DateTime, OJet returns it as java.lang.Long

OperationName

✓

✓

user-level SQL operation that made the change (INSERT, UPDATE, etc.)

OperationType

✓

✓

the Oracle operation type

ParentTxnID

✓

raw representation of the parent transaction identifier

PK_UPDATE

✓

✓

true if an UPDATE operation changed the primary key, otherwise false

RbaBlk

✓

RBA block number within the log file

RbaSqn

✓

sequence# associated with the Redo Block Address (RBA) of the redo record associated with the change

RecordSetID

✓

Uniquely identifies the redo record that generated the row. The tuple (RecordSetID, SSN) together uniquely identifies a logical row change.

RollBack

✓

1 if the record was generated because of a partial or a full rollback of the associated transaction, otherwise 0

ROWID

✓

see comment

Row ID of the row modified by the change (only meaningful if the change pertains to a DML). This will be NULL if the redo record is not associated with a DML.

OJet: will be included only if fetch_lcr_attributes is specified in OJet Config

SCN

✓

system change number (SCN) when the database change was made

SegmentName

✓

name of the modified data segment

SegmentType

✓

type of the modified data segment (INDEX, TABLE, ...)

Serial

✓

serial number of the session that made the change

Serial#

see comment

serial number of the session that made the change; will be included only if fetch_lcr_attributes is specified in OJet Config

Session

✓

session number of the session that made the change

Session#

see comment

session number of the session that made the change; will be included only if fetch_lcr_attributes is specified in OJet Config

SessionInfo

✓

Information about the database session that executed the transaction. Contains process information, machine name from which the user logged in, client info, and so on.

SQLRedoLength

✓

length of reconstructed SQL statement that is equivalent to the original SQL statement that made the change

SSN

✓

SQL sequence number. The tuple (RecordSetID, SSN) together uniquely identifies a logical row change.

TableName

✓

✓

name of the modified table (in case the redo pertains to a table modification)

TableSpace

✓

name of the tablespace containing the modified data segment.

ThreadID

✓

ID of the thread that made the change to the database

Thead#

see comment

ID of the thread that made the change to the database; will be included only if fetch_lcr_attributes is specified in OJet Config

TimeStamp

✓

✓

the UNIX epoch time of the operation, based on the Striim server's time zone: Oracle Reader returns this as jorg.joda.time.DateTime, OJet returns it as java.lang.Long

TransactionName

✓

✓

name of the transaction that made the change (only meaningful if the transaction is a named transaction)

TxnID

✓

✓

raw representation of the transaction identifier

TxnUserID

✓

UserName

✓

name of the user associated with the operation

ADT

not supported, values will be set to null

not supported, application will halt if it reads a table containing a column of this type

ANYDATA, ANYDATASET, ANYTYPE

not supported; values will set to EMPTY_CLOB

not supported; application will halt if it reads a table containing a column of this type

BFILE

not supported, values will be set to null

values for a column of this type will contain the file names, not their contents

BINARY_DOUBLE

Double

Double

BINARY_FLOAT

Float

Float

BLOB

String (a primary or unique key must exist on the table)

An insert or update containing a column of this type generates two CDC log entries: an insert or update in which the value for this column is null, followed by an update including the value.

When reading from Oracle 19c, values for this type may be incorrect when (1) a table contains multiple columns of this type and operations are performed on more than one of those columns in the same transaction or (2) multiple tables containing columns of this type are being read and different user sessions are performing operations on them. If you encounter either of these issues, Contact Striim support for assistance.

Byte[]

CHAR

String

String

CLOB

string (a primary or unique key must exist on the table)

An insert or update containing a column of this type generates two CDC log entries: an insert or update in which the value for this column is null, followed by an update including the value.

When reading from Oracle 19c, values for this type may be incorrect when (1) a table contains multiple columns of this type and operations are performed on more than one of those columns in the same transaction or (2) multiple tables containing columns of this type are being read and different user sessions are performing operations on them. If you encounter either of these issues, Contact Striim support for assistance.

String

DATE

DateTime

java.time.LocalDateTime

FLOAT

String

String

INTERVALDAYTOSECOND

string (always has a sign)

String (unsigned)

INTERVALYEARTOMONTH

string (always has a sign)

String (unsigned)

JSON

not supported, values will be set to null

not supported, application will halt if it reads a table containing a column of this type

LONG

Results may be inconsistent. Oracle recommends using CLOB instead.

String

LONG RAW

Results may be inconsistent. Oracle recommends using CLOB instead.

Byte[]

NCHAR

String

String

NCLOB

String (a primary or unique key must exist on the table)

String (a primary or unique key must exist on the table)

NESTED TABLE

not supported, application will halt if it reads a table containing a column of this type

not supported, application will halt if it reads a table containing a column of this type

NUMBER

String

String

NVARCHAR2

String

String

RAW

String

Byte[]

REF

not supported, application will halt if it reads a table containing a column of this type

not supported, application will halt if it reads a table containing a column of this type

ROWID

String

values for a column of this type will be set to null

SD0_GEOMETRY

SD0_GEOMETRY values will be set to null

Known issue DEV-20726: if a table contains a column of this type, the application will terminate

TIMESTAMP

DateTime

java.time.LocalDateTime

TIMESTAMP WITH LOCAL TIME ZONE

DateTime

java.time.LocalDateTime

TIMESTAMP WITH TIME ZONE

DateTime

java.time.ZonedDateTime

UDT

not supported, values will be set to null

not supported, application will halt if it reads a table containing a column of this type

URIType, DBURIType, HTTPURIType, XDBURIType

not supported; values will be set to null

not supported; application will halt if it reads a table containing a column of this type

UROWID

not supported, a table containing a column of this type will not be read

not supported due to Oracle bug 33147962, application will terminate if it reads a table containing a column of this type

VARCHAR2

String

String

VARRAY

Supported by LogMiner only in Oracle 12c and later. Required Oracle Reader settings:

Limitations:

When the output of an Oracle Reader source is the input of a target using XML Formatter, the formatter's Format Column Value As property must be set to xmlelement for VARRAY data to be formatted correctly.

known issue DEV-29799: if a table contains a column of this type, the application will terminate

XMLTYPE

Supported only for Oracle 12c and later. When DictionaryMode is OnlineCatalog, values in any XMLType columns will be set to null. When DictionaryMode is OfflineCatalog, reading from tables containing XMLType columns is not supported.

String