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)
![[Next]](FIGURE/AFTER.GIF)
To execute a send data UOC routine, you must specify the directory path to the shared library file (libhdesuoc.sl or libhdesuoc.so) in the SHLIB_PATH environment variable (LD_LIBRARY_PATH environment variable for the Solaris or Linux Datareplicator, and LIBPATH environment variable for the AIX Datareplicator).
If the SHLIB_PATH environment variable (LD_LIBRARY_PATH environment variable for the Solaris or Linux Datareplicator, and LIBPATH environment variable for the AIX Datareplicator) is not specified or there is no shared library file at the directory path specified in the environment variable, Datareplicator executes import processing without using the send data UOC routine.
- Organization of this subsection
- (1) Limitations on signals
- (2) Limitations on file manipulations
- (3) Limitations on shared memory
- (4) Limitations on data types
- (5) Limitations on SQL execution
- (6) Other limitations
(1) Limitations on signals
- Do not conduct signal operations in a send data UOC routine's function.
- Do not use a function that controls processes (such as exit() or abort()).
- Do not execute free() at the address of the pre-update or post-update column data in HDE_EXT_DATAINFO within a send data UOC routine.
(2) Limitations on file manipulations
You can manipulate only user-specific files (that are open) within a send data UOC routine's function. The following are the file-related rules:
- Do not use the standard input, standard output, or standard error output.
- Do not read, write, or close any file that is not opened by the UOC routine.
- Do not manipulate any file that belongs to HiRDB or Datareplicator.
- Do not process the data that is passed to the send data UOC routine.
- You cannot inherit resources allocated within a send data UOC routine from one session to another (that is, the resources are not still available the next time the send data UOC routine is called).
(3) Limitations on shared memory
Do not use the same shared memory that is used by Datareplicator or by any other system.
(4) Limitations on data types
Columns of the following data types are not supported by send data UOC routines:
- Abstract data types (SGMLTEXT, FREEWORD, XML)
- BLOB and BINARY types on which addition or update operations have been performed
- BLOB and BINARY types on which backward deletion updating has been performed.
(5) Limitations on SQL execution
Do not execute any SQL statement within or as an extension of the send data UOC routine's function. If executed, transaction management by Datareplicator might become invalid.
(6) Other limitations
- Even if EBCDIK is specified as the transmission character code set, Datareplicator passes data in the character code set used before the EBCDIK conversion.
- When you create a send data UOC routine, do not overlook the fact that processing for the same target might be divided into multiple processes.
- The table ID and column IDs passed in the arguments are those in effect at the time of execution of the hdeprep command. If the UOC uses these IDs and a table is re-created after execution of the hdeprep command, you must correct the UOC routine.
All rights reserved. Copyright (C) 2007, 2013, Hitachi, Ltd.