Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Replication 9.8.0 HotFix 2
  • All Products

Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

User Guide

User Guide

Back Next

Command Line Parameters for the Extractor

Command Line Parameters for the Extractor

You can start the Extractor executable or script from the command line with the following optional parameters:
CLEAN_SQLITEREP= {y|
n
}
Removes repository information about previous revisions to the current configuration file from the revision control system. Options are:
  • y
    . Remove the repository information.
  • n
    . Do not remove the repository information.
Default value:
 n
CONFIG=
path/configuration_SQLite_database_file
Specifies the path and file name of a configuration SQLite database file for a replication configuration.
Default value:
 No default
FORCE_EXTRACT_ REGARDLESS_SYNC_ SCN={y|
n
}
For DB2 for Linux, UNIX, and Windows sources, indicates whether to extract changes from source tables that appear to not have been previously synchronized with the target. For these tables, the previous Extractor run did not write the Sync Point (LSN) values in the DBSYNC_SYNC_LSN to the configuration file. Options are:
  • y
    . Force change data extraction for source tables that do not have a Sync Point value in the configuration file.
  • n
    . Do not extract change data for source tables that do not have a Sync Point value in the configuration file.
Default value:
 n
JOURNAL_MODE={
DELETE
|TRUNCATE|PERSIST|MEMORY|WAL|OFF}
Specifies the rollback journal mode for the SQLite repository that contains configuration information. Journal mode options are:
  • DELETE
    . Delete the rollback journal at the conclusion of each transaction.
  • TRUNCATE
    . Commit transactions by truncating the rollback journal to zero-length instead of deleting it.
  • PERSIST
    . Prevent the rollback journal from being deleted at the end of each transaction.
  • MEMORY
    . Store the rollback journal in volatile RAM.
  • WAL
    . Use a write-ahead log instead of a rollback journal to implement transactions.
  • OFF
    . Disable the rollback journal completely.
For more information about SQLite journal modes, see the SQLite documentation.
Default value:
 DELETE for Linux and UNIX, WAL for Windows
Ensure that this parameter has the same value for all Data Replication components.
INT_FILES_DIR=
path/directory_name
Specifies the directory that contains the intermediate files. The Extractor transmits intermediate files to the specified directory. The Applier gets intermediate files from the specified directory.
Default value:
DataReplication_installation
/output
KEYS_STORAGE_PATH
Specifies the path to the internal master key that the Oracle Extractor uses to decrypt Oracle keys from a replication configuration. When the Server Manager starts the Extractor, it sets this command-line parameter to the
Internal Master Key Path
 value that you set in the Server Manager advanced properties in the Data Replication Console.
ONLINE_FILES_PREFIX=
path_to_the_mounted_directory
For Oracle sources, specifies the directory on the local file system that the Extractor searches for online redo logs. By default, the Extractor searches for online redo logs in the location that it gets from the Oracle server. Use this parameter to extract change data from online redo logs over the network from the mounted file system.
For example, if Oracle uses the redo online log /u01/app/oracle/oradata/orcl/redo01.log, and you mounted the directory with online redo logs to the directory C:\APP\USERNAME\ORADATA\ORCL, use the following command to run the Extractor: 
extract.cmd some_configuration.xml ONLINE_FILES_PREFIX=C:\APP\USERNAME\ORADATA\ORCL\
The Extractor can access the online redo log C:\APP\USERNAME\ORADATA\ORCL\redo01.log.
Default value:
 No default
OUTPUT_LOG_NAME=
file_name
Specifies the name of the first execution log file that contains output from the Data Replication component.
Default value:
 No default
OUTPUT_LOGS_FOLDER=
path_to_directory
Specifies the directory in which Data Replication creates execution log files for the Data Replication component.
Default value:
 No default
REALTIME_ MODE={y|
n
}
Enables continuous replication. Options are:
  • y
    . Run the Extractor or Applier in continuous replication mode.
  • n
    . Run the Extractor or Applier on demand.
Default value:
 n
SKIP_CONTINUITY_CHECK={y|
n
}
For Microsoft SQL Server and Oracle sources, indicates whether to skip integrity checking for the database logs during the first Extractor run.
  • y
    . Skip integrity checking for the database logs during the first Extractor run.
  • n
    . Perform integrity checking for the database logs. The start time of each log must match the end time of the previous log record. The Extractor stops processing logs when it detects any inconsistency.
Default value:
 n
SKIP_DEFAULT_TX={
y
|n}
Indicates whether to capture change data for transactions that have the default name of DbSyncTransaction. Options are:
  • y
    . Skip change data capture for the transactions that have the name of DbSyncTransaction.
  • n
    . Capture change data for the transactions that have the name of DbSyncTransaction.
Default value:
 y
SKIP_TEM_ISSUES_FOR_THREADS=
redo_thread1,redo_thread2, ...
For Oracle RAC sources, specifies the list of redo threads for which the Extractor ignores Thread Enable Marker (TEM) issues. If a TEM issue occurs, the Extractor continues processing redo log records. The following types of TEM issues indicate that the Extractor might have missed change data records for a redo thread:
  • The Extractor encounters a TEM for an online Oracle redo thread.
  • A TEM for an offline redo thread refers to an unexpected log sequence number.
Ignoring these TEM issues for a redo thread might result in change data loss.
Use this parameter only if you must continue the Extractor processing despite possible change data loss.
Default value:
 None
SKIP_TX=
transaction_names
Specifies a comma-separated list of transaction names to skip. When extracting change data, the Extractor skips all of the transactions that have matching names. You can use the asterisk (*) and question mark (?) wildcard characters to specify a mask for the transaction names. For example, use the following value to skip all of the transactions that have the name "A_Transaction" and all of the transactions that have the name starting with "B": 
SKIP_TX=A_Transaction,B*
Default value:
 No default
SM_RUN_ID=
server_manager_run_ID
Specifies the run ID that the Server Manager assigns to the replication task.
The Server Manager uses the SM_RUN_ID parameter to set the run ID value when starting a task. Do not change this parameter value or delete this parameter from the commands that start replication tasks.
Default value:
 No default
SQLITE_CACHE_SIZE=
cache_size
Specifies the maximum number of database disk pages that SQLite will hold in memory at once per open database file. The Data Replication component uses this parameter to open SQLite database files.
Default value:
 16384 bytes
Change the default value only at the request of Informatica Global Customer Support.
SQLITE_PAGE_SIZE=
page_size
Specifies the page size of the SQLite database when a new database is created, a database is still empty, or prior to running the VACUUM command. The Data Replication component uses this parameter to open SQLite database files.
Default value:
 16384 bytes
Change the default value only at the request of Informatica Global Customer Support.
UDP_SERVER_PORT=
port_number
Specifies the User Datagram Protocol (UDP) port of the Server Manager through which the Data Replication component communicates with the Server Manager. Valid values are integers from 1 through 65535.
Default value:
 8087
Ensure that the UDP_SERVER_PORT parameter value matches the value of the UDP_PORT parameter for the Server Manager.
0 COMMENTS
We’d like to hear from you!