13 Configuring Implicit Apply

Creating an Apply Process for Captured LCRs

The following example runs the ADD_SCHEMA_RULES procedure in the DBMS_STREAMS_ADM package to create an apply process that applies captured LCRs:

BEGIN
  DBMS_STREAMS_ADM.ADD_SCHEMA_RULES(
    schema_name        => 'hr',
    streams_type       => 'apply',
    streams_name       => 'strm01_apply',
    queue_name         => 'streams_queue',
    include_dml        => TRUE,
    include_ddl        => FALSE,
    include_tagged_lcr => FALSE,
    source_database    => 'dbs1.net',
    inclusion_rule     => TRUE);
END;
/

Running this procedure performs the following actions:

• Creates an apply process named strm01_apply that applies captured LCRs to the local database. The apply process is created only if it does not already exist.

• Associates the apply process with an existing queue named streams_queue.

• Creates a positive rule set and associates it with the apply process, if the apply process does not have a positive rule set, because the inclusion_rule parameter is set to TRUE. The rule set uses the SYS.STREAMS$_EVALUATION_CONTEXT evaluation context. The rule set name is system generated.

• Creates one rule that evaluates to TRUE for row LCRs that contain the results of DML changes to database objects in the hr schema. The rule name is system generated.

• Adds the rule to the positive rule set associated with the apply process because the inclusion_rule parameter is set to TRUE.

• Sets the apply_tag for the apply process to a value that is the hexadecimal equivalent of '00' (double zero). Redo entries generated by the apply process have a tag with this value.

• Specifies that the apply process applies a row LCR only if it has a NULL tag, because the include_tagged_lcr parameter is set to FALSE. This behavior is accomplished through the system-created rule for the apply process.

• Specifies that the LCRs applied by the apply process originate at the dbs1.net source database. The rules in the apply process rule sets determine which messages are dequeued by the apply process. If the apply process dequeues an LCR with a source database other than dbs1.net, then an error is raised.

Creating an Apply Process for User Messages

The following example runs the ADD_MESSAGE_RULE procedure in the DBMS_STREAMS_ADM package to create an apply process that dequeues and processes user messages in a persistent queue:

BEGIN
  DBMS_STREAMS_ADM.ADD_MESSAGE_RULE(
    message_type       => 'oe.order_typ',
    rule_condition     => ':msg.order_status = 1',
    streams_type       => 'apply',
    streams_name       => 'strm02_apply',
    queue_name         => 'strm02_queue',
    inclusion_rule     => TRUE);
END;
/

Running this procedure performs the following actions:

• Creates an apply process named strm02_apply that dequeues user messages of oe.order_typ type and sends them to the message handler for the apply process. The apply process is created only if it does not already exist.

• Associates the apply process with an existing queue named strm02_queue.

• Creates a positive rule set and associates it with the apply process, if the apply process does not have a positive rule set, because the inclusion_rule parameter is set to TRUE. The rule set name is system generated, and the rule set does not use an evaluation context.

• Creates one rule that evaluates to TRUE for user messages that satisfy the rule condition. The rule uses a system-created evaluation context for the message type. The rule name and the evaluation context name are system generated.

• Adds the rule to the positive rule set associated with the apply process because the inclusion_rule parameter is set to TRUE.

• Sets the apply_tag for the apply process to a value that is the hexadecimal equivalent of '00' (double zero). Redo entries generated by the apply process, including any redo entries generated by a message handler, have a tag with this value.

Creating an Apply Process for Captured LCRs with DBMS_APPLY_ADM

The following example runs the CREATE_APPLY procedure in the DBMS_APPLY_ADM package to create an apply process that applies captured LCRs:

BEGIN
  DBMS_APPLY_ADM.CREATE_APPLY(
    queue_name             => 'strm03_queue',
    apply_name             => 'strm03_apply',
    rule_set_name          => 'strmadmin.strm03_rule_set',
    message_handler        => NULL,     
    ddl_handler            => 'strmadmin.history_ddl',
    apply_user             => 'hr',
    apply_database_link    => NULL,
    apply_tag              => HEXTORAW('5'),
    apply_captured         => TRUE,
    precommit_handler      => NULL,
    negative_rule_set_name => NULL,
    source_database        => 'dbs1.net');
END;
/

Running this procedure performs the following actions:

• Creates an apply process named strm03_apply. An apply process with the same name must not exist.

• Associates the apply process with an existing queue named strm03_queue.

• Associates the apply process with an existing rule set named strm03_rule_set. This rule set is the positive rule set for the apply process.

• Specifies that the apply process does not use a message handler.

• Specifies that the DDL handler is the history_ddl PL/SQL procedure in the strmadmin schema. The user who runs the CREATE_APPLY procedure must have EXECUTE privilege on the history_ddl PL/SQL procedure. An example in the Oracle Streams Replication Administrator's Guide creates this procedure.

• Specifies that the user who applies the changes is hr, and not the user who is running the CREATE_APPLY procedure (the Oracle Streams administrator).

• Specifies that the apply process applies changes to the local database because the apply_database_link parameter is set to NULL.

• Specifies that each redo entry generated by the apply process has a tag that is the hexadecimal equivalent of '5'.

• Specifies that the apply process applies captured LCRs, and not persistent LCRs or persistent user messages. Therefore, if an LCR that was constructed by a user application, not by a capture process, is staged in the queue for the apply process, then this apply process does not apply the LCR.

• Specifies that the apply process does not use a precommit handler.

• Specifies that the apply process does not use a negative rule set.

• Specifies that the LCRs applied by the apply process originate at the dbs1.net source database. The rules in the apply process rule sets determine which messages are dequeued by the apply process. If the apply process dequeues an LCR with a source database other than dbs1.net, then an error is raised.

Creating an Apply Process for Persistent LCRs with DBMS_APPLY_ADM

The following example runs the CREATE_APPLY procedure in the DBMS_APPLY_ADM package to create an apply process that applies persistent LCRs:

BEGIN
  DBMS_APPLY_ADM.CREATE_APPLY(
    queue_name             => 'strm04_queue',
    apply_name             => 'strm04_apply',
    rule_set_name          => 'strmadmin.strm04_rule_set',
    message_handler        => NULL,
    ddl_handler            => NULL,
    apply_user             => NULL,
    apply_database_link    => NULL,
    apply_tag              => NULL,
    apply_captured         => FALSE,
    precommit_handler      => NULL,
    negative_rule_set_name => NULL);
END;
/

Running this procedure performs the following actions:

• Creates an apply process named strm04_apply. An apply process with the same name must not exist.

• Associates the apply process with an existing queue named strm04_queue.

• Associates the apply process with an existing rule set named strm04_rule_set. This rule set is the positive rule set for the apply process.

• Specifies that the apply process does not use a message handler.

• Specifies that the apply process does not use a DDL handler.

• Specifies that the user who applies the changes is the user who runs the CREATE_APPLY procedure, because the apply_user parameter is NULL.

• Specifies that the apply process applies changes to the local database, because the apply_database_link parameter is set to NULL.

• Specifies that each redo entry generated by the apply process has a NULL tag.

• Specifies that the apply process does not apply captured LCRs. Therefore, the apply process can apply persistent LCRs or persistent user messages that are in the persistent queue portion of the apply process queue.

• Specifies that the apply process does not use a precommit handler.

• Specifies that the apply process does not use a negative rule set.

After creating the apply process, run the ADD_TABLE_RULES or ADD_SUBSET_RULES procedure to add rules to the apply process rule set. These rules direct the apply process to apply LCRs for the specified tables.

Creating an Apply Process for Persistent User Messages with DBMS_APPLY_ADM

The following example runs the CREATE_APPLY procedure in the DBMS_APPLY_ADM package to create an apply process that applies persistent user messages:

BEGIN
  DBMS_APPLY_ADM.CREATE_APPLY(
    queue_name             => 'strm05_queue',
    apply_name             => 'strm05_apply',
    rule_set_name          => 'strmadmin.strm05_rule_set',
    message_handler        => 'strmadmin.mes_handler',
    ddl_handler            => NULL,
    apply_user             => NULL,
    apply_database_link    => NULL,
    apply_tag              => NULL,
    apply_captured         => FALSE,
    precommit_handler      => NULL,
    negative_rule_set_name => NULL);
END;
/

Running this procedure performs the following actions:

• Creates an apply process named strm05_apply. An apply process with the same name must not exist.

• Associates the apply process with an existing queue named strm05_queue.

• Associates the apply process with an existing rule set named strm05_rule_set. This rule set is the positive rule set for the apply process.

• Specifies that the message handler is the mes_handler PL/SQL procedure in the strmadmin schema. The user who runs the CREATE_APPLY procedure must have EXECUTE privilege on the mes_handler PL/SQL procedure.

• Specifies that the apply process does not use a DDL handler.

• Specifies that the user who applies the changes is the user who runs the CREATE_APPLY procedure, because the apply_user parameter is NULL.

• Specifies that the apply process applies changes to the local database, because the apply_database_link parameter is set to NULL.

• Specifies that each redo entry generated by the apply process has a NULL tag.

• Specifies that the apply process does not apply captured LCRs. Therefore, the apply process can apply persistent LCRs or persistent user messages that are in the persistent queue portion of the apply process queue.

• Specifies that the apply process does not use a precommit handler.

• Specifies that the apply process does not use a negative rule set.