Examples with "changes or data definition language" and their translation in Japans
We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
A table rule may be created for data manipulation language (DML) changes or data definition language (DDL) changes (or both) for each table, and a user-defined condition may be added to each rule, depending on the selections in the previous page.
An apply process is an optional Oracle background process that dequeues logical change records (LCRs) and user messages from a specific queue and either applies each one directly or passes it as a parameter to an apply handler. An apply handler is a user-defined procedure used by an apply process for customized processing of messages. The LCRs dequeued by an apply process contain the results of data manipulation language (DML) changes or data definition language (DDL) changes that an apply process can apply to database objects in a destination database. A user-enqueued message dequeued by an apply process is of type ANYDATA and can contain any user message, including a user-created LCR.
A DDL LCR describes a data definition language (DDL) change. A DDL statement changes the structure of the example, a DDL statement may create, alter, or drop a database object.
To update the LogMiner internal dictionary if a data definition language (DDL) event occurs, click Update internal dictionary with DDL changes. This ensures that LogMiner can generate the correct redo or undo statements for objects that are modified after the LogMiner dictionary is built.
The type of change recorded in the LCR, either data manipulation language (DML) or data definition language (DDL)
LCRに記録された変更のタイプ(データ操作言語(DML)またはデータ定義言語(DDL))。
Do not allow data manipulation language (DML) or data definition language (DDL) changes to the specified tables at the destination database while the procedure is running.
For captured LCRs, the message creation time is the time when the data manipulation language (DML) or data definition language (DDL) change generated the redo data at the source database for the message.
Typically, you can retry a transaction when you have corrected the conditions that caused the error. In some cases, you may need to make data manipulation language (DML) or data definition language (DDL) changes to database objects to correct the conditions that caused apply errors before you retry error transactions.
With implicit capture, data definition language (DDL) and data manipulation language (DML) changes are captured automatically either by a capture process or by synchronous capture. A specific type of message called logical change record (LCR) describes these database changes. Both a capture process and synchronous capture can filter database changes with user-defined rules. Therefore, only changes to specified objects are captured.
You can control what information is put into a stream, how the stream flows or is routed from database to database, what happens to messages in the stream as they flow into each database, and how the stream configuring specific capabilities of Streams, you can address specific requirements. Streams can capture, stage, and manage messages in the database automatically, including, but not limited to, data manipulation language (DML) changes and data definition language (DDL) changes.
Redo logs are used to guarantee recoverability in the event of human error or media failure. A capture process is an optional Oracle background process that scans the database redo log to capture data manipulation language (DML) and data definition language (DDL) changes made to database objects. When a capture process is configured to capture changes from a redo log, the database where the changes were generated is called the source database for the capture process.
This wizard configures the Streams environment to maintain data manipulation language (DML) changes to the tablespace set and to the database objects in the tablespace set. It does not configure the Streams environment to maintain data definition language (DDL) changes to these objects. For example, the Streams environment is configured to maintain INSERT, UPDATE, and DELETE operations on tables in the tablespace set. However, the Streams environment is not configured to replicate ALTER TABLESPACE statements on the tablespace, nor is it configured to replicate ALTER TABLE statements on tables in the tablespace. You may configure the Streams environment to maintain DDL changes manually or modify generated scripts to achieve this.
Using Oracle Streams, you control what information is put into a stream, how the stream flows or is routed from database to database, what happens to messages in the stream as they flow into each database, and how the stream configuring specific capabilities of Streams, you can address specific requirements. Based on your specifications, Streams can capture, stage, and manage messages in the database automatically, including, but not limited to, data manipulation language (DML) changes and data definition language (DDL) changes. You can also put user-defined messages into a stream, and Streams can propagate the information to other databases or applications messages reach a destination, Streams can consume them based on your specifications.
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.