Oracle® Database PL/SQL Packages and Types Reference 10g Release 2 (10.2) Part Number B14258-02 |
|
|
PDF · Mobi · ePub |
The DBMS_STREAMS
package, one of a set of Streams packages, provides subprograms to convert ANYDATA
objects into logical change record (LCR) objects, to return information about Streams attributes and Streams clients, and to annotate redo entries generated by a session with a binary tag. This tag affects the behavior of a capture process, a propagation, or an apply process whose rules include specifications for these binary tags in redo entries or LCRs.
See Also:
Oracle Streams Concepts and Administration and Oracle Streams Replication Administrator's Guide for more information about this package and StreamsThis chapter contains the following topics:
Security Model
This section contains topics which relate to using the DBMS_STREAMS
package.
User group PUBLIC
is granted EXECUTE
privilege on this package.
Table 105-1 DBMS_STREAMS Package Subprograms
Subprogram | Description |
---|---|
Returns the |
|
Returns the |
|
Returns the |
|
Converts a |
|
Converts a |
|
Converts a logical change record (LCR) encapsulated in a |
|
Converts an XML object that conforms to the XML schema for LCRs into a logical change record (LCR) encapsulated in a |
|
Returns information about various Streams attributes |
|
Returns the name of the invoker |
|
Returns the type of the invoker |
|
Gets the binary tag for all redo entries generated by the current session |
|
Sets the binary tag for all redo entries subsequently generated by the current session |
Note:
The subprograms in this package do not commit.This function returns the DBMS_STREAMS.COMPATIBLE_10_2
constant.
DBMS_STREAMS.COMPATIBLE_10_2 RETURN INTEGER;
You can use this function with the GET_COMPATIBLE
member function for logical change records (LCRs) to specify behavior based on compatibility.
The constant value returned by this function corresponds to 10.2.0 compatibility in a database. You control the compatibility of an Oracle database using the COMPATIBLE
initialization parameter.
See Also:
Oracle Streams Concepts and Administration for information about creating rules that discard changes that are not supported by Streams
Oracle Database Reference and Oracle Database Upgrade Guide for more information about the COMPATIBLE
initialization parameter
This function returns the DBMS_STREAMS.COMPATIBLE_10_1
constant.
DBMS_STREAMS.COMPATIBLE_10_1 RETURN INTEGER;
You can use this function with the GET_COMPATIBLE
member function for logical change records (LCRs) to specify behavior based on compatibility.
The constant value returned by this function corresponds to 10.1.0 compatibility in a database. You control the compatibility of an Oracle database using the COMPATIBLE
initialization parameter.
See Also:
Oracle Streams Concepts and Administration for information about creating rules that discard changes that are not supported by Streams
Oracle Database Reference and Oracle Database Upgrade Guide for more information about the COMPATIBLE
initialization parameter
This function returns the DBMS_STREAMS.COMPATIBLE_9_2
constant.
DBMS_STREAMS.COMPATIBLE_9_2 RETURN INTEGER;
You can use this function with the GET_COMPATIBLE
member function for logical change records (LCRs) to specify behavior based on compatibility.
The constant value returned by this function corresponds to 9.2.0 compatibility in a database. You control the compatibility of an Oracle database using the COMPATIBLE
initialization parameter.
See Also:
Oracle Streams Concepts and Administration for information about creating rules that discard changes that are not supported by Streams
Oracle Database Reference and Oracle Database Upgrade Guide for more information about the COMPATIBLE
initialization parameter
This function converts a ANYDATA
object into a SYS.LCR$_DDL_RECORD
object.
DBMS_STREAMS.CONVERT_ANYDATA_TO_LCR_DDL( source IN ANYDATA) RETURN SYS.LCR$_DDL_RECORD;
Table 105-2 CONVERT_ANYDATA_TO_LCR_DDL Function Parameters
Parameter | Description |
---|---|
|
The |
You can use this function in a transformation created by the CREATE_TRANSFORMATION
procedure in the DBMS_TRANSFORM
package. Use the transformation you create when you add a subscriber for propagation of DDL LCRs from a ANYDATA
queue to a SYS.LCR$_DDL_RECORD
typed queue.
See Also:
Oracle Streams Concepts and Administration for more information about this functionThis function converts a ANYDATA
object into a SYS.LCR$_ROW_RECORD
object.
DBMS_STREAMS.CONVERT_ANYDATA_TO_LCR_ROW( source IN ANYDATA) RETURN SYS.LCR$_ROW_RECORD;
Table 105-3 CONVERT_ANYDATA_TO_LCR_ROW Function Parameters
Parameter | Description |
---|---|
|
The |
You can use this function in a transformation created by the CREATE_TRANSFORMATION
procedure in the DBMS_TRANSFORM
package. Use the transformation you create when you add a subscriber for propagation of row LCRs from a ANYDATA
queue to a SYS.LCR$_ROW_RECORD
typed queue.
See Also:
Oracle Streams Concepts and Administration for more information about this functionThis function converts a logical change record (LCR) encapsulated in a ANYDATA
object into an XML object that conforms to the XML schema for LCRs. The LCR can be a row LCR or a DDL LCR.
See Also:
Oracle Streams Concepts and Administration for more information about the XML schema for LCRsDBMS_STREAMS.CONVERT_LCR_TO_XML( anylcr IN ANYDATA) RETURN SYS.XMLTYPE;
Table 105-4 CONVERT_LCR_TO_XML Function Parameters
Parameter | Description |
---|---|
|
The |
This function converts an XML object that conforms to the XML schema for logical change records (LCRs) into an LCR encapsulated in a ANYDATA
object. The LCR can be a row or DDL LCR.
See Also:
Oracle Streams Concepts and Administration for more information about the XML schema for LCRsDBMS_STREAMS.CONVERT_XML_TO_LCR( xmldat IN SYS.XMLTYPE) RETURN ANYDATA;
Table 105-5 CONVERT_XML_TO_LCR Function Parameters
Parameter | Description |
---|---|
|
The XML LCR object to be converted. If this object does not conform to XML schema for LCRs, then the function raises an exception. |
This function returns information about various Streams attributes.
DBMS_STREAMS.GET_INFORMATION( name IN VARCHAR2) RETURN ANYDATA;
Table 105-6 GET_INFORMATION Function Parameters
Parameter | Description |
---|---|
|
The type of information you want to retrieve. Currently, the following names are available:
|
This function gets the Streams name of the invoker if the invoker is one of the following Streams types:
CAPTURE
APPLY
ERROR_EXECUTION
If the invoker is not one of these types, then this function returns a NULL
.
DBMS_STREAMS.GET_STREAMS_NAME RETURN VARCHAR2;
You can use this function in rule conditions, rule-based transformations, apply handlers, and error handlers. For example, if you use one error handler for multiple apply processes, then you can use the GET_STREAMS_NAME
function to determine the name of the apply process that raised the error.
This function gets the Streams type of the invoker and returns one of the following types:
CAPTURE
APPLY
ERROR_EXECUTION
If the invoker is not one of these types, then this function returns a NULL
.
DBMS_STREAMS.GET_STREAMS_TYPE RETURN VARCHAR2;
This function can be used in rule conditions, rule-based transformations, apply handlers, and error handlers. For example, you can use the GET_STREAMS_TYPE
function to instruct a DML handler to operate differently if it is processing messages from the error queue (ERROR_EXECUTION
type) instead of the apply process queue (APPLY
type).
This function gets the binary tag for all redo entries generated by the current session.
See Also:
Oracle Streams Replication Administrator's Guide for more information about tagsDBMS_STREAMS.GET_TAG RETURN RAW;
The following example illustrates how to display the current logical change record (LCR) tag as output:
SET SERVEROUTPUT ON DECLARE raw_tag RAW(2000); BEGIN raw_tag := DBMS_STREAMS.GET_TAG(); DBMS_OUTPUT.PUT_LINE('Tag Value = ' || RAWTOHEX(raw_tag)); END; /
You can also display the value by querying the DUAL
view:
SELECT DBMS_STREAMS.GET_TAG FROM DUAL;
This procedure sets the binary tag for all redo entries subsequently generated by the current session. Each redo entry generated by DML or DDL statements in the current session will have this tag. This procedure affects only the current session.
Note:
This procedure is not transactional. That is, the effects ofSET_TAG
cannot be rolled back.See Also:
Oracle Streams Replication Administrator's Guide for more information about tagsDBMS_STREAMS.SET_TAG( tag IN RAW DEFAULT NULL);
Table 105-7 SET_TAG Procedure Parameters
Parameter | Description |
---|---|
|
The binary tag for all subsequent redo entries generated by the current session. A raw value is a sequence of bytes, and a byte is a sequence of bits. By default, the tag for a session is The size limit for a tag value is 2000 bytes. |
To set the tag to the hexadecimal value of '17'
in the current session, run the following procedure:
EXEC DBMS_STREAMS.SET_TAG(tag => HEXTORAW('17'));