HP Integrity NonStop H-Series Uživatelská příručka Strana 228

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 346
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 227
HP NonStop Shadowbase Command Definitions
Database Specification Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
219
specifying NODDLCOORDINATION, the Consumers will not be
“drained”. The ALTER 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.
ALTERS {ON}
{OFF}
{(ON [, alter-option]...)}
alter-option is any of:
ADDCOLUMN
AUDIT
AUDITCOMPRESS
BUFFERED
MAXEXTENTS
SECURITY
Initial Changed
Version Version Values Default Value Specificatons Alter
5.001 5.002 OFF Valid Alters options No
This parameter is used to define if Enscribe file and SQL/MP table alter
events are to be replicated to the target. By default, this parameter is set
to OFF. Set it to ON to enable the feature. When set to ON, the file
attributes that are replicated are: maxextents, audit/no-audit (audit on and
audit off), buffered/write-thru-cache, and audit compress on/off. Use the
alter-option(s) to identify the specific attribute(s) you want replicated.
When alter-option(s) is used, only those identified are replicated. Note
that you must set ADDCOLUMN explicitly to enable the SQL/MP column
additions option.
Notes: Altering a file from no-audit to audit will not update the target file
because
an audit trail event is not generated by TMF for this event. To replicate the
change to audit ‘on’ the user must issue a second file alter that will
generate an audit event (after audit is enabled). This can be something
like an alter command of the maxextents – for example, setting the
maxextents to the same number will add an alter event into the audit trail.
The alter event read from the audit trail does not contain the detailed
information for HP Shadowbase to actually use for altering the target file.
Instead, the audit trail event simply tells HP Shadowbase that a FUP
ALTER or SQLCI ALTER was done on the source file, not what
attribute(s) were actually altered. When ALTERS is ON and HP
Shadowbase reads an alter event from the audit trail, HP Shadowbase will
actually use Guardian calls and/or access the SQL/MP catalog to retrieve
the source and target file/table attributes (for example, HP Shadowbase
Zobrazit stránku 227
1 2 ... 223 224 225 226 227 228 229 230 231 232 233 ... 345 346

Komentáře k této Příručce

Žádné komentáře