Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
Configuring SDR
Configuring SDR Capture
Retaining Captured DDL
At the time you perform either primary database updates or DDL operations, you might
not have configured RDF yet, or even have a backup database. You can decide,
weeks after an application has started updating a database on the primary system, to
initialize RDF and replicate all the updates that were performed in past weeks to a
backup database. All you need to do is save the TMF audit trails.
Similarly, SDR captures and preserves the DDL being executed on a primary table,
with no knowledge of RDF. Indeed, DDL capture is completely independent of DDL
replication. This is very similar to the use of TMF that is independent of RDF.
The de-coupling of DDL capture from replication is why the DDL retention period is
important. It can be set to any value between 1 day and 60 days. The default is one
week. Set retention higher if you plan to initialize RDF to a date that goes back in time
more than one week. To change the default retention period, set the global parameter
RETENTION to the desired value.
Note. SDR allows one extra day past the configured retention period when deleting old
records from SDRDEPOT files on the backup system. In the normal case, old records are
deleted on the primary system and those deletes are quickly replicated by RDF to the backup
system. The delay prevents the backup system from deleting old records before the primary
system has a chance to do so.If the backup SDR deletes records before the primary SDR,
RDF issues EMS message 700, error 11 on the SDRDEPOT file. This has no ill effect but is an
additional distraction for the operator.
Handling DDL Operations performed under a User
Transactions
Certain types of DDL operations can be done in a user-initiated transaction. For
example, you can DROP and CREATE a table as a single transaction; if the
transaction fails, the original table is still available. User transactions containing DDL
operations are rare, but they are allowed.
User transactions complicate the DDL replication. At the time SDR replicates the DDL,
the outcome of the user transaction is not known.
You can configure how you want SDR to handle DDL operations that are executed in a
user transaction, by setting the global parameter USERTRANSACTION to one of the
following options:
ABORT: disallow DDL inside a user transaction. If a user attempts such an
operation, the transaction is aborted, the DDL operation fails, and the database is
rolled back to the state it was when the transaction began. SDR writes a message
to the home terminal and to EMS whenever it aborts a transaction.
ASSUMECOMMIT: assume that user transactions containing DDL always commits.
SDR ignores the fact that the DDL is part of a user transaction and always
replicates it.
HP NonStop SQL DDL Replicator User’s Guide —545799-006
3-4
... Este manual também é adequado para os modelos :
Computadores - HP Integrity NonStop J-Series (333.11 kb)
Computadores - HP NonStop G-Series (333.11 kb)
Computadores - HP NonStop L-Series (333.11 kb)