HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
The table below lists the tables supported for data linkage by Datareplicator. The information in this table applies to both the source and the target Datareplicator.
| Classification |
Data linkage support |
| User table |
No option specified. |
Y |
| SHARE option specified. |
R#1 |
| WITHOUT ROLLBACK option specified. |
R#2 |
| INSERT ONLY option specified. |
R#3 |
| INNER CONSTRUCTOR option specified. |
R#4 |
| CHARACTER SET option specified. |
R#5 |
| Triggers are defined. |
R#6 |
| COMPRESSED option specified. |
R#7 |
| Other options are specified. |
Y |
| View table |
N |
| Data dictionary table |
N |
| Temporary table |
N |
- Legend:
- Y: Supported.
- R: Supported with restrictions.
- N: Not supported.
- #1
- Data linkage is supported only for the back-end server that was specified in the server name operand in the create rdarea statement when a shared RDAREA for storing shared tables was created. (Shared tables are tables that have the SHARE option specified.) To apply data linkage to shared tables, you must specify the with lock clause in the load statement in the target Datareplicator's import definition. There is no need to specify this definition in the source Datareplicator. For details about the import definitions, see 5.10.5 Import table definition.
- #2
- There are prerequisites and limitations when data linkage is applied to tables for which the WITHOUT ROLLBACK option specified. For details, see 6.7.3(4) Notes about tables for which the WITHOUT ROLLBACK option is specified.
- #3
- Use the same structure for both source and target tables.
- #4
- Data linkage is supported if a column with this option specified is not extracted.
- #5
- When a column with the CHARACTER SET option specified is to be extracted, both the conditions described below must be satisfied. If either of these conditions is not satisfied, inconsistencies might occur between the source and target databases.
- The same CHARACTER SET option is specified for the source and the target columns.
- If the source database is XDM/DS and EBCDIK is specified in the CHARACTER SET option for a target column, nocodecnv is specified for the field corresponding to that column by using the format statement in the import definition.
- #6
- There are prerequisites and limitations when data linkage is applied to tables for which triggers are defined. For details, see 3.3.6 Data linkage for a table with a trigger set.
- #7
- There are prerequisites and limitations when data linkage is applied to tables for which the COMPRESSED option is specified. For details, see 6.7.3(5) Notes about tables for which the COMPRESSED option is specified.
All rights reserved. Copyright (C) 2007, 2013, Hitachi, Ltd.