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

HP NonStop Shadowbase Command Definitions

Database Specification Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

253

processes are “drained” of events first, and then the DDL event is sent to

the appropriate Consumer to be processed. After the DDL event has

been processed, non-DDL replication can resume. This coordination is

necessary so that events are processed synchronously in the correct

sequence across multiple Consumer threads.

It is recommended that an AUDCOM SUSPENDUPD be issued before

any DDL sequences that create a base file or table and then subsequently

create alternate key files or indexes. The AUDCOM RESUMEUPD should

be issued after the multi-step sequence is finished. This is necessary to

have HP Shadowbase see the indexes and alternate key files when it

processes the create event so that it can create them for the target file or

table. Otherwise, it is possible that the index and alternate key files don’t

get created.

If you have Enscribe or SQL/MP DDL replication operating in a bi-

directional environment and you have user exits that alter, create,

purge/drop, or purgedata against a target table that may be processed in

the reverse direction, your user exit should be programmed using the

following steps to prevent ping-pong:

1. Call the user exit SBSETDDLNOALTERS API function.

2. Call the user exit SBSETDDLALLPTNS API function.

3. For an Enscribe target, alter the audit attribute to off on the target file.

4. Call the user exit SBBEGINDDL API function.

5. Call the user exit SBSUSPENDTRANSACTION API function (sets

transaction nil state).

6. Perform your custom DDL related logic.

7. Call the user exit SBRESUMETRANSACTION API function (resumes

the SB transaction).

8. Call the user exit SBENDDDL API function.

9. Call the user exit SBSETIGNORE API function.

PURGEDATAOPTIONS { purgedata-option }

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

Initial Changed

Version Version Values Default Value Specification Alter

4.091 5.002 <See Below> Valid Purgedata-Options No

This parameter controls what action is taken when the Consumer receives

a PURGEDATA event. The PURGEDATAOPTIONS allow the user to

specify whether to keep or purge the data in existing Enscribe alternate

key files and to specify whether the purgedata should be done for the

target partition only, or for all partitions. In the case of all partitions, the

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

1 2 ... 257 258 259 260 261 262 263 264 265 266 267 ... 345 346

Komentarze do niniejszej Instrukcji

Brak uwag

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

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Oprogramowanie HP Integrity NonStop H-Series