In this section: |
Database tables that are defined for replication are listed in the Table List Configuration File. Every entry in the table list has a table name and comma-separated columns list. The Table List Configuration File is generated by an ad-hoc shell script (tabconfig.sh), using table name patterns as an input. All selected tables are listed along with all column names, excluding those of TEXT, BYTE, row, structure, sequence, and user-defined data types on which the Informix Change Data Capture (CDC) API is not supported.
The file name format for the Table List Configuration File uses a subscription name as the base name and the following extension:
‘.config’ (subscr001.config)
The file record contains database/table/column names in the following format:
dbname@owner.tablename>col1,col2,col3,…,...,...,colN
Users can modify the Table List Configuration File by removing or commenting out the rows using ‘#’characters, and removing column names. However, the Primary Key Columns must not be removed.
The following is a sample Table List Configuration File for the STORES demo database:
stores@informix.call_type>call_code,code_descr stores@informix.catalog>catalog_num,stock_num,manu_code,cat_advert stores@informix.classes>classid,class,subject stores@informix.cust_calls>customer_num,call_dtime, user_id,call_code,call_descr,res_dtime,res_descr stores@informix.customer>fname,lname,company, address1,address2,city,state,zipcode,phone,customer_num stores@informix.employee>givenname,familyname,phone stores@informix.items>item_num,order_num,stock_num, manu_code,quantity,total_price stores@informix.manufact>manu_code,manu_name,lead_time stores@informix.orders>order_num,order_date, customer_num,ship_instruct,backlog,po_num, ship_date,ship_weight,ship_charge,paid_date stores@informix.state>code,sname stores@informix.stock>stock_num,manu_code, description,unit_price,unit,unit_descr stores@informix.warehouses>warehouse_name,warehouse_id,warehouse_spec
The tabconfig.sh is a shell script that generates table information for a CDC configuration file.
The only required parameter for this script is a database name (-d <dbname>). The input options for the script include:
The output record lists all table columns, except for those with unsupported data types.
Usage:
The tabconfig.sh script can report on the unsupported columns in a database.
For example:
$ tabconfig.sh -d stores -r Not Supported Columns Report: stores@informix.catalog>cat_descr,cat_picture stores@informix.employee>address
You can edit the configuration file to remove fields that are not required. The tabconfig.sh script also includes an option to validate a configuration file for database, table, and column names.
iWay Software |