Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

DBMOVER Configuration File Statements

DBMOVER Configuration File Statements

The DBMOVER configuration file includes the following new and changed statements:
CONSOLE_MSG={N|
Y
}
New
. On Linux, UNIX, and Windows systems, the CONSOLE_MSG statement specifies whether to write certain messages to the domain log in addition to writing them to the PowerExchange log file on the Integration Service machine.
  • N.
    PowerExchange does not write the messages to the domain log.
  • Y
    .
    PowerExchange writes the messages to the domain log.
Default is Y.
ENCRYPT={AES|
N
|Y}
Changed
. The following table identifies new and deprecated values for the ENCRYPT statement:
Value
New or Deprecated
AES
New
DES
Deprecated
RC2
Deprecated
PowerExchange changes an ENCRYPT value of DES or RC2 to AES.
ENCRYPTLEVEL={
1
|2|3}
Changed
. The ENCRYPTLEVEL statement now defines the encryption level when the ENCRYPT statement specifies
AES
.
Enter one of the following values in the ENCRYPTLEVEL statement:
  • 1
    . Use a128-bit encryption key.
  • 2
    . Use a 192-bit encryption key.
  • 3
    . Use a 256-bit encryption key.
LOWVALUES={
N
|Y}
Changed
. The LOWVALUES statement now applies to PowerExchange NRDB, DB2, and CDC sources and targets. In previous releases, the statement applies only to VSAM files on z/OS and to sequential files on Linux, UNIX, Windows, or z/OS.
The LOWVALUES statement specifies whether PowerExchange preserves hexadecimal '0' values, called
low values
, in source character fields when passing these values to a PowerCenter session. When the session runs, the PowerExchange Client for PowerCenter (PWXPC) can write these values to the target.
MSQL CAPI_CONNECTION
This statement can now contain the following optional parameters:
LOCKAVOIDANCE={N|Y}
New
. For Microsoft SQL Server sources, the LOCKAVOIDANCE parameter in the MSQL CAPI_CONNECTION statement controls whether PowerExchange SELECT statements use the NOLOCK hint when querying the SQL Server distribution database for change data. The NOLOCK hint can avoid lock contention with SQL Server utilities but might cause PowerExchange to miss some change records. Options are:
  • N
    . PowerExchange SELECT queries that retrieve data from the distribution database do not use the NOLOCK hint. If locks are held on some change records, PowerExchange queries cannot retrieve the data until the locks are released. With this setting, PowerExchange queries might take longer to complete. However, no changes are skipped and data integrity is preserved. Use this option only when the MULTIPUB parameter is set to Y.
  • Y
    . PowerExchange SQL SELECT queries that retrieve data from the distribution database use the NOLOCK hint. Use this option only when the MULTIPUB parameter is set to N. If the MULTIPUB parameter is set to Y, SQL Server might use allocation order scans to retrieve data for PowerExchange queries, which can result in missed change data and data corruption.
    Instead of using LOCKAVOIDANCE=Y, Informatica recommends that you set the isolation level for the distribution database to READ_COMMITTED_SNAPSHOT ON to avoid data integrity problems.
Default is
N
if MULTIPUB is set to Y, or
Y
if MULTIPUB is set to N.
RECONNTRIES={
number
|
12
}
New
. For Microsoft SQL Server sources, specifies the maximum number of times that PowerExchange tries to reconnect to the Microsoft SQL Server database after the connection is dropped. Use this parameter in conjunction with the RECONNWAIT parameter if you get the following ODBC connection error and want to improve connection resiliency:
PWX-15790 ODBC driver for Microsoft SQL Server returned error [08S01][Informatica][ODBC SQL Server Wire Protocol driver]Unexpected Network Error. ErrNum = 10054.
Valid values are 0 or any positive number. A value of 0 results in no connection retries. Default is 12.
RECONNWAIT={
seconds
|
5
}
New
. For Microsoft SQL Server sources, specifies the number of seconds that PowerExchange waits before any attempt to reconnect to a Microsoft SQL Server database after the connection has been dropped. Use this parameter in conjunction with the RECONNTRIES parameter if you get the PWX-15790 message for an ODBC driver error and want to improve connection resiliency.
Valid values are 0 through 3600. A value of 0 results in no waiting between connection retries. Default is 5.
UDB CAPI_CONNECTION
This statement can now contain the following optional parameter:
AGEOUTPERIOD=
minutes
New
. For DB2 for Linux, UNIX, and Windows sources, this parameter specifies the age, in minutes, at which an outstanding DB2 UOW that has no change records of CDC interest will be removed from the calculation of the CDC restart point. The age is calculated as the difference between the start time of the outstanding UOW and the current time. Use this parameter to prevent CDC failures that can occur if you shut down and then restart capture processing for a DB2 source while the transaction is outstanding. After the restart, the DB2 transaction log in which the outstanding UOW started might not be available, causing the PowerExchange DB2 read process to fail.
Valid values are 60 to 43200. No default value is provided.
For more information, see the "DBMOVER Configuration File" chapter in the
PowerExchange Reference Manual
.

0 COMMENTS

We’d like to hear from you!