
HP NonStop Shadowbase Command Definitions
Database Specification Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
215
Version Version Values Default Minimum Maximum Alter
3.960 OFF OFF ON No
The parameter ABENDONMISMATCH was added to perform a series of
checks and tests for those sites that are performing like-to-like replication
(e.g., a disaster recovery scenario). The default value is OFF. This
parameter can be used when AUDITCOMPRESS is on for the source file
or table.
When set to ON for Enscribe files, the Consumer will abend with an
appropriate EMS message if an audit trail event record length is not equal
to the record length defined for the TARGETFILE. This means that you
must not be using variable length records for this file when you use this
parameter.
When set to ON for an SQL table, the Consumer will abend with an
appropriate EMS message if the SOURCEFILE and TARGETFILE
schemas don't match (with some restrictions, see below) or if an audit trail
event record contains column data that does not match the SOURCEFILE
schema definition (i.e.,i.e., column not defined, event length is too short
(has fewer columns than the target), event length is too long (has more
columns than the target)). Additionally, when
set to ON for an SQL table, the Consumer will abend with an appropriate
EMS message if it detects that the TARGETFILE schema has dynamically
changed, for example via an ALTER TABLE ADD COLUMN command
(the theory being that the target schema is now different than the source).
For SQL, note that it is imperative that the ordinal position of columns and
the data definitions associated with a SOURCEFILE reflect that of the true
source file, i.e.,i.e., the actual event data that HP Shadowbase will
process from the audit trail. If they don't align, this could result in various
column data mapping errors being reported by HP Shadowbase during
replication (causing the Consumer to abend). This is particularly important
to take into consideration when using a DBS MAPTOFILE parameter on a
source node and relating it to a corresponding SOURCEFILE parameter in
a target node configuration for non-Expand environments.
For SQL, ABENDONMISMATCH may not report (and abend on) all
column data type differences between a source schema and a target
schema. This is because HP Shadowbase's primary job is to allow
replication to proceed by mapping the incoming event data into the target
column definitions if at all possible. If the mapping is allowed by SQL, the
Consumer will proceed; if not, the Consumer will abend with an EMS
message describing the problem.
ACTIVETARGET
Commentaires sur ces manuels