HP Integrity NonStop H-Series Podręcznik Użytkownika Pobierz pdf (Strona 265)

HP NonStop Shadowbase Command Definitions

Database Specification Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

256

KEEPALTFILES – Existing alternate key files on the target are kept (not

purged). This only applies to Enscribe files.

PURGEALTFILES – Existing alternate key files for the target file is purged

if the target file is a primary partition (or a single partition file). The

Consumer must be running on the same node as the target file in order for

PURGEALTFILES to function properly in all cases (this is the typical

configuration for HP Shadowbase replication). This is the default if no

ALTFILE option is specified. This only applies to Enscribe files.

ALLPARTS – If the target file or table is a primary partition (or a single

partition file or table), it is purged along with any secondary partitions. If

the target file or table is a secondary partition, the purge event is ignored

(only the purge event against the primary partition purges the target file or

table). This is the default if no partition options specified.

PARTONLY – If the target file or table is a primary partition (or a single

partition file or table), it is purged along with any secondary partitions. If

the target file or table is a secondary partition, only that partition is purged.

The source and target file/table volume names must match to use this

option. Note that this behavior mimics that of the Guardian FILE_PURGE_

call and differs from a FUP PURGE <pri part>, PARTONLY command,

which only purges the primary partition. Note that you cannot do a

PARTONLY purge of a SQL/MP primary partition with SQLCI. If you

issue a SQLCI DROP against a secondary partitions of a SQL/MP table,

all partitions are purged.

CLOSETABLES – By default for SQL/MP alter events, the Consumer will

not close its target tables before processing the PURGE event. By

specifying CLOSETABLES, the Consumer will close its target tables prior

to replicating the purge to the related target table.

NODDLCOORDINATION – By default, all Consumers will complete

processing of all in-progress and queued messages (“drained”) before an

PURGE event is processed. This is necessary for coordinating the order

of the events being processed. By specifying NODDLCOORDINATION,

the Consumers will not be “drained”. The PURGE event will be sent to the

related Consumer in the same manner as insert, update, and delete

events. Note that the coordination is controlled by the related Collector

process. It “drains” all of its Consumers before sending a DDL event.

PURGES { ON }

{ OFF }

Initial Changed

1 2 ... 260 261 262 263 264 265 266 267 268 269 270 ... 345 346

Brak uwag

HP Integrity NonStop H-Series Podręcznik Użytkownika Strona 265