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 Statement

DBMOVER Configuration File Statement

In the MSQL CAPI_CONNECTION statement in the dbmover.cfg configuration file, you can now specify the following new optional parameters:
LOCKAVOIDANCE={N|Y}
New
. 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.
For more information, see the "DBMOVER Configuration File" chapter in the
PowerExchange Reference Manual
.

0 COMMENTS

We’d like to hear from you!