HP Integrity NonStop H-Series Betriebsanweisung PDF herunterladen (Seite 264)

HP NonStop Shadowbase Command Definitions

Database Specification Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

255

order of the events being processed. By specifying

NODDLCOORDINATION, the Consumers will not be “drained”. The

PURGEDATA 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.

MAPTOPRIPTN – This option causes a secondary partition purgedata

event to be mapped to the related primary partition for the source file and

then sent to the Consumer to be applied to the target. Only a single event

is selected (any other purgedata events for the other partitions are

skipped). This parameter is needed in situations where a primary partition

may be empty. A purgedata event is not generated if a primary partition of

a file or table is empty.

PURGEOPTIONS { purge-option }

{( purge-option [, purge-option] )}

Initial Changed

Version Version Values Default Value Specification Alter

4.091 5.002 <See Below> Valid Purge-Options No

This parameter provides additional options when the Consumer receives a

PURGE event. Prior to the availability of this parameter, if an Enscribe

target for the purge event was a primary partition (including single partition

files), the Consumer purged the file, and any alternate key files associated

with that file. For Enscribe, the PURGEOPTIONS allows the user to

specify whether to keep or purge existing alternate key files. For Enscribe

files and SQL/MP tables, it allows one to specify whether the purge should

be done for a specific target partition only (e.g., “PARTONLY”), or for all

partitions in the target file or table. In the case of all partitions, the purge

is only executed if the target file or table is a primary partition.

For PURGE event replication of partitioned files, the source file/table to

target file/table mapping must be one to one, with each source primary or

secondary partition file/table being mapped to its corresponding target

primary or secondary partition file/table in order for purge events to be

replicated properly for those files/tables. This is typically not the case for

any DBS configured to replicate INSERT, UPDATE, or DELETE events for

partitioned files and tables. Those events typically map all of the source

file/table partitions to the target file/table primary partition, either by

wildcarding the volume portion of the SOURCEFILE name, or by setting

the ALLPARTITIONS DBS option to ON. Because of this, PURGE event

replication for partitioned files and tables currently must be configured in a

separate DBS from other I/O events.

Available Purge-Options:

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

Kommentare zu diesen Handbüchern

Keine Kommentare

HP Integrity NonStop H-Series Betriebsanweisung Seite 264

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Software HP Integrity NonStop H-Series