The table below lists HiRDB facilities that affect Datareplicator operations and the support provided for those facilities by Datareplicator.

The information provided in this table applies to HiRDB 08-03 and Datareplicator 08-02. For the most recent information, see the manuals published online at the following location:

http://www.hitachi.co.jp/Prod/comp/soft1/manual/common/hirdb.htm

Table A-2 HiRDB facilities and the support provided for those facilities by Datareplicator

HiRDB facility					Supporting Datareplicator versions#1	What happens if a non-supporting Datareplicator version is used
Structure of a table subject to linkage	CREATE TABLE	FIX			Source: 02-00 and later (HiRDB is 03-03 or later)	--
					Target: 01-00 and later
		SHARE			Source: 02-00 and later	--
					Target: 07-01 and later	Import processing results in an SQL execution error.
		SUPPRESS DECIMAL			Source: 03-00 and later	Values imported to the target database differ from the values in the source database.
					Target: 01-00 and later	--
		WITHOUT ROLLBACK			Source: 08-02 and later	Inconsistencies might occur between the source and target databases. Also, import processing might result in an SQL execution error.
					Target: 08-02 and later
		REFERENCES			Source: 02-00 and later	--
					Target: 01-00 and later (with conditions#2)	If the conditions are not satisfied, import processing results in an SQL execution error.
		ARRAY			Source: 05-02 and later (HiRDB is 05-05 and later)	Values imported to the target database differ from the values in the source database.
					Target: 05-02 and later
		NO SPLIT			Source: 05-02 and later	Values imported to the target database differ from the values in the source database.
					Target: 01-00 and later	--
		CHARACTER SET			Source: 08-03 and later	Values imported to the target database differ from the values in the source database.
					Target: 08-03 and later	Unintended import processing is performed on hash-partitioned tables.
		SUPPRESS			Source: 03-00 and later	Values imported to the target database differ from the values in the source database.
					Target: 01-00 and later	--
		COMPRESSED			Source: 08-06 and later	Inconsistencies might occur between the source and target databases. Also, import processing might result in an SQL execution error.
					Target: 08-06 and later
		Data type	INTEGER		Source: 02-00 and later Target: 01-00 and later	--
			SMALLINT
			DECIMAL	Maximum precision is 29	Source: 02-00 and later Target: 01-00 and later	--
				Maximum precision is 38	Source: 08-03 and later Target: 08-03 and later	--
			FLOAT		Source: 02-00 and later Target: 01-00 and later	--
			SMALLFLT
			CHARACTER
			VARCHAR
			NCHAR
			NVARCHAR
			MCHAR
			MVARCHAR
			DATE
			TIME	(Not using a leap second)	Source: 02-00 and later Target: 01-00 and later	--
				(Using a leap second)	Source: 02-00 and later	If the target HiRDB's version is earlier than 08-02, import processing results in an SQL execution error.
					Target: 01-00 and later (HiRDB is 08-02 and later)
			TIMESTAMP		Source: 07-00 and later Target: 07-00 and later	--
			INTERVAL YEAR TO DAY		Source: 02-00 and later Target: 01-00 and later	--
			INTERVAL HOUR TO SECOND
			BLOB		Source: 02-01 and later Target: 02-01 and later	Environment cannot be configured because the hdeprep command results in an error.
			BINARY		Source: 07-00 and later Target: 07-00 and later	--
			Abstract data type	SGMLTEXT	Source: 05-00 and later Target: 05-00 and later	--
				FREEWORD	Source: 08-02 and later Target: 08-02 and later	--
				XML	Source: 08-02 and later Target: 08-02 and later	--
				Abstract data type defined by the user by using CREATE TYPE	Source: Not supported Target: Not supported	Environment cannot be configured because the hdeprep command results in an error.
	Index with at least one column whose definition length is 256 bytes or greater				Source: Not supported	Source system's environment cannot be configured because the hdeprep command results in an error.
					Target: 01-00 and later	--
	Trigger				Source: 07-00 and later Target: 07-00 and later	--
Manipula-tion of a table subject to linkage	PURGE TABLE	Non-partitioned table or row-partitioned table in a server			Source: 04-00 and later (HiRDB is 04-04 and later)	If the source HiRDB's version is earlier than 04-04, Purge table is not linked to the target database.
					Target: 04-00 and later
		Table that is row-partitioned among multiple servers			Source: Not supported	Purge table is not linked to the target database.
					Target: 04-00 and later
	INSERT				Source: 02-00 and later Target: 01-00 and later	--
	UPDATE	Performing a concatenation operation on BLOB type or BINARY type with a length of 32,001 bytes or greater			Source: 06-01 and later Target: 06-01 and later	Values imported to the target database differ from the values in the source database.
		Performing backward deletion updating on BLOB type or BINARY type with a length of 32,001 bytes or greater			Source: 08-01 and later Target: 08-01 and later	Values imported to the target database differ from the values in the source database.
		Other			Source: 02-00 and later Target: 01-00 and later	--
	DELETE				Source: 02-00 and later Target: 01-00 and later	--
	Overall SQL statements	USER (using USER as the update value for the source database) (using USER as the update value for the target database)			Source: 02-00 and later	--
					Target: Not supported	The same value as the update value for the source database is imported.
		CURRENT_DATE value function CURRENT_TIME value function (using the CURRENT_DATE or CURRENT_TIME value function as the update value for the source database) (using the CURRENT_DATE or CURRENT_TIME value function as the update value for the target database)			Source: 02-00 and later Target: 01-00 and later	--
		CURRENT_TIMESTAMP value function (using the CURRENT_TIMESTAMP value function as the update value for the source database) (using the CURRENT_TIMESTAMP value function as the update value for the target database)			Source: 02-00 and later Target: 07-00 and later	--
HiRDB facilities that affect data linkage	Space conversion facility				Source: 02-00 and later	--
					Target: 05-03 and later	Unintended import processing is performed on hash-partitioned tables.
	Character code classification	sjis			Source: 02-00 and later Target: 01-00 and later	--
		euc			Source: 02-00 and later	--
					Target: 01-02 and later	Import environment cannot be configured.
		korea			Source: Not supported Target: Not supported	Environment cannot be configured.
		lang-C			Source: 02-00 and later Target: 01-00 and later	--
		utf-8	Within the range of UCS-2		Source: 07-01 and later Target: 07-01 and later	Environment cannot be configured.
			Within the range of UCS-4		Source: 07-01 and later	Extraction environment cannot be configured.
					Source: 07-01 and later (not supported if the character code classification differs between the source and target databases)	A character whose length is 4 bytes or greater is converted to an undefined character, and then imported.
		chinese			Source: Not supported Target: Not supported	Environment cannot be configured.
	System switchover	When HiRDB and Datareplicator are running on the same server	Monitor mode, server mode, or user server hot standby	IP addresses inherited	Source: 02-00 and later Target: 01-00 and later	--
				IP addresses not inherited	Source: 06-02 and later	Source system does not function when system switchover occurs.
					Target: 01-00 and later	--
			Rapid system switchover facility or standby-less system switchover (1:1) facility		Source: 06-02 and later	Source system does not function when system switchover occurs.
					Target: 01-00 and later	--
			Standby-less system switchover (effects distributed) facility		Source: 07-01 and later (Windows edition is not supported)	Source system does not function when system switchover occurs.
					Target: 01-00 and later	--
		When HiRDB and Datareplicator are running on separate servers			Source: Not supported	Extraction environment cannot be configured.
					Target: 05-01 and later	Once system switchover has occurred, connection with HiRDB is lost and import processing stops.
	Real Time SAN Replication	All synchronous method, all asynchronous method, or log-only synchronous method	Main site		Source: 02-00 and later Target: 01-00 and later	--
			Remote site		Source: Not supported	No update information is extracted.
					Target: 01-00 and later	--
	DNS support				Source: 02-00 and later Target: 01-00 and later	--
	Linkage facility	When using Datareplicator's import transaction synchronization facility			Source: 07-04 and later Target: 07-04 and later	There are no effects.
		When using Datareplicator's data linkage recovery facility			See Table 9-10 Combinations of the versions and products that support data linkage recovery via unload log files.	The data linkage recovery facility is not supported.
	Inner replica facility	Linking updates to current RDAREAs only			Source: 06-01 and later	Updates to original RDAREAs and all replica RDAREAs are subject to linkage processing.
					Target: 01-00 and later	--
		Linking updates to original RDAREAs and all replica RDAREAs			Source: 02-00 and later Target: 01-00 and later	--
Utilities	pdload -d				Source: Not supported Target: Not supported	Import processing results in an SQL execution error. Another possibility is that existing rows are intermixed with rows inserted by pdload.
	pdload -lp pdload -ln				Source: Not supported	Update information is not extracted.
					Target: 01-00 and later	--
	pdrbal				Source: Not supported	Data is not extracted from any added back-end server.
					Target: 01-00 and later	--
	pdrorg -la				Source: Not supported	Import processing results in an SQL execution error. Another possibility is that existing rows are imported twice.
					Target: 01-00 and later	--
UAP execution environ- ment	No-log mode				Source: Not supported	No update information is extracted.
					Target: 01-00 and later	--
	PDCWAITTIME PDSWAITTIME				Source: --	There are no effects.
					Target: Not supported	If 0 is specified in PDCWAITTIME or PDSWAITTIME, SQL statements are executed on the target database.

Legend:

--: There are no unsupported versions.

#1

If a supported version is indicated, extraction and import processing are supported by that version and all versions subsequent to it. If there are conditions, the conditions take precedence over the version information.

#2

The transaction-based import method must be used, and updates to the source database must be performed on referencing tables and referenced tables in this order.