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
  • PowerExchange for CDC and Mainframe 10.4.0 HotFix 1
  • All Products

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

Release Guide

Release Guide

Back Next

DTLUCBRG Utility Parameters

DTLUCBRG Utility Parameters

In PowerExchange 10.2 HotFix 1, the following DTLUCBRG utility parameters are new or changed:
CREATEBICI
New
. Controls whether the DTLUCBRG utility generates a before-image (BI) column, change-indicator (CI) column, or both for data columns in extraction maps. This parameter applies to all extraction maps that the utility creates. If you specify multiple tables by using a table-name mask, the CREATEBICI keywords apply to all of the tables that match the mask.
Syntax: 
CREATEBICI=(COLUMNS={PKFK|ALL|FILE}, MAXCOLS={
number_of_columns
|
500
}, EXTINFO={BI|CI|
BICI
}, INPUT_FN=
input_file_name
, OUTPUT_FN=
output_file_name
, ERROR_FN=
error_file_name
)
Subparameters:
  • COLUMNS
    . Indicates the columns in the extraction map for which the utility generates BI columns, CI columns, or both types of columns, as indicated by the EXTINFO keyword. Options are:
    • PKFK
      . Generate BI and CI columns for primary-key and foreign-key columns.
    • ALL
      . Generate BI and CI columns for all selected columns in the extraction map.
    • FILE
      . Generate BI and CI columns for columns that are defined in the table schema in the utility input file.
    No default is provided.
  • MAXCOLS
    . Specifies the maximum number of columns for which the utility generates BI and CI columns in the extraction map. Valid values are 10 through 32000. Default is 500.
    How you set this keyword depends on the COLUMNS setting. Use the following guidelines:
    • If COLUMNS=FILE, the MAXCOLS value must be equal to or greater than the number of entries in the input file.
    • If COLUMNS=ALL, the MAXCOLS value must be equal to or greater than the largest number of columns for a registered table.
    • If COLUMNS=PKFK, the MAXCOLS value must be equal to or greater than the number of primary and foreign keys in the largest registered table.
  • EXTINFO
    . Specifies the type or types of metadata columns to generate in the extraction maps. Options are:
    • BI
      . Before-image columns.
    • CI
      . Change-indicator columns.
    • BICI
      . Both BI and CI columns.
    Default is BICI.
    In some cases, the BI or CI column cannot be created. For example, the utility cannot create a BI column for DB2 z/OS LOB columns in extraction maps. If you try to create a BI column for DB2 for z/OS LOB columns, the request is ignored and a warning message is written to the output file.
  • INPUT_FN
    . On Linux, Unix, and Windows, specifies an input file that contains the column names for the BI and CI columns when the COLUMNS keyword is set to
    FILE
    . On z/OS, this keyword accepts only
    Y
     or
    N
    . If
    Y
     is specified, the utility uses default, preallocated data sets.
  • OUTPUT_FN
    . On Linux, Unix, and Windows, specifies the name of the output file that contains log information about the BI and CI columns created in the extraction maps. On z/OS, this keyword accepts only
    Y
     or
    N
    . If
    Y
     is specified, the utility uses default, preallocated data sets.
  • ERROR_FN
    . On Linux, Unix, and Windows, specifies a file that lists the columns for which BI and CI columns failed to be generated in the extraction maps. On z/OS, this keyword accepts only
    Y
     or
    N
    . If
    Y
     is specified, the utility uses default, preallocated data sets.
If both CREATEBICI and RPTCOLS=Y are specified, the utility adds BI and CI columns to the output report with the value
Y
 or
N
 in each of these columns.
DBID
Changed
. In this parameter, you can now specify the new
MYS
 option for MySQL CDC sources.
INSTANCE
Changed
. In this parameter, you can now optionally enter a unique, user-defined instance identifier for the MySQL database server when DBID=MYS. Maximum length is seven characters. This identifier is used to identify a set of registrations for tables in the database on the MySQL server. This identifier is also incorporated into the names of the extraction maps that the utility creates. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that this instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this instance value, PowerExchange generates a unique instance identifier that is composed of all or part of the database name followed by a 3-digit number if a number is required to make the identifier unique.
MYSOPTS
New
. This parameter and subparameter have been added for MySQL CDC sources.
Syntax: 
MYSOPTS=(DBSERVER="{
database_server_name
|localhost}[{,
port_number
|
3306
}]")
Subparameter:
  • DBSERVER
    . Enter the server name or IP address of the MySQL server where the source database is located. If the MySQL server is on the local host where the Navigator runs, you can enter
    localhost
    . Optionally, you can append the port number if you use a port other than the default port of 3306, for example,
    DBSERVER=localhost,3456
    .
For more information, see the "DTLUCBRG - Batch Registration Utility" chapter of the
PowerExchange Utilities Guide
.
0 COMMENTS
We’d like to hear from you!