The STREAMS_CONFIGURATION Data Pump Import utility parameter specifies whether to import any general Streams metadata that is present in the export dump file. This import parameter is relevant only if you are performing a full database import. By default the STREAMS_CONFIGURATION Import utility parameter is set to y.
Typically, specify y if an import is part of a backup or restore operation.
The following objects are imported regardless of the STREAMS_CONFIGURATION setting if the information is present in the export dump file:
■ ANYDATA queues and their queue tables.
■ Queue subscribers.
■ Advanced Queuing agents.
■ Job queue jobs related to Streams propagations.
■ Rules, including their positive and negative rule sets and evaluation contexts. All rules are imported, including Streams rules and non-Streams rules. Streams rules are rules generated by the system when certain procedures in the DBMS_
STREAMS_ADM package are run, while non-Streams rules are rules created using the DBMS_RULE_ADM package.
If the STREAMS_CONFIGURATION parameter is set to n, then information about Streams rules is not imported into the following data dictionary views: ALL_
STREAMS_RULES, ALL_STREAMS_GLOBAL_RULES, ALL_STREAMS_SCHEMA_
Note:
■ If you perform a network import using Data Pump, then an implicit export is performed in the same mode as the import.
For example, if the network import is in schema mode, then the implicit export is in schema mode also.
■ The import session tag is not set if the Data Pump import is performed in TRANSPORTABLE TABLESPACE mode. An import performed in this mode does not generate any redo data for the imported data. Therefore, setting the session tag is not
required.
See Also: Chapter 4, "Streams Tags"
Oracle Data Pump and Streams Instantiation
RULES, ALL_STREAMS_TABLE_RULES, DBA_STREAMS_RULES, DBA_STREAMS_
GLOBAL_RULES, DBA_STREAMS_SCHEMA_RULES, and DBA_STREAMS_TABLE_
RULES. However, regardless of the STREAMS_CONFIGURATION parameter setting, information about these rules is imported into the ALL_RULES, ALL_RULE_SETS, ALL_RULE_SET_RULES, DBA_RULES, DBA_RULE_SETS, DBA_RULE_SET_RULES, USER_RULES, USER_RULE_SETS, and USER_RULE_SET_RULES data dictionary views.
When the STREAMS_CONFIGURATION Import utility parameter is set to y, the import includes the following information, if the information is present in the export dump file; when the STREAMS_CONFIGURATION Import utility parameter is set to n, the import does not include the following information:
■ Capture processes that capture local changes, including the following information for each capture process:
■ Name of the capture process.
■ State of the capture process.
■ Capture process parameter settings.
■ Queue owner and queue name of the queue used by the capture process.
■ Rule set owner and rule set name of each positive and negative rule set used by the capture process.
■ Capture user for the capture process.
■ Extra attribute settings if a capture process is configured to include extra attributes in LCRs.
■ The time that the status of the capture process last changed. This information is recorded in the DBA_CAPTURE data dictionary view.
■ If the capture process disabled or aborted, then the error number and message of the error that was the cause. This information is recorded in the DBA_
CAPTURE data dictionary view.
■ If any tables have been prepared for instantiation at the export database, then these tables are prepared for instantiation at the import database.
■ If any schemas have been prepared for instantiation at the export database, then these schemas are prepared for instantiation at the import database.
■ If the export database has been prepared for instantiation, then the import database is prepared for instantiation.
■ The state of each ANYDATA queue that is used by a Streams client, either started or stopped. Streams clients include capture processes, propagations, apply process, and messaging clients. ANYDATA queues themselves are imported regardless of the STREAMS_CONFIGURATION Import utility parameter setting.
■ Propagations, including the following information for each propagation:
■ Name of the propagation.
■ Queue owner and queue name of the source queue.
■ Queue owner and queue name of the destination queue.
■ Destination database link.
■ Rule set owner and rule set name of each positive and negative rule set used by the propagation.
Oracle Data Pump and Streams Instantiation
■ Apply processes, including the following information for each apply process:
■ Name of the apply process.
■ State of the apply process.
■ Apply process parameter settings.
■ Queue owner and queue name of the queue used by the apply process.
■ Rule set owner and rule set name of each positive and negative rule set used by the apply process.
■ Whether the apply process applies captured or user-enqueued messages.
■ Apply user for the apply process.
■ Message handler used by the apply process, if one exists.
■ DDL handler used by the apply process, if one exists.
■ Precommit handler used by the apply process, if one exists.
■ Tag generated in the redo log for changes made by the apply process.
■ Apply database link, if one exists.
■ Source database for the apply process.
■ The information about apply progress in the DBA_APPLY_PROGRESS data dictionary view, including applied message number, oldest message number (oldest SCN), apply time, and applied message create time.
■ Apply errors.
■ The time that the status of the apply process last changed. This information is recorded in the DBA_APPLY data dictionary view.
■ If the apply process disabled or aborted, then the error number and message of the error that was the cause. This information is recorded in the DBA_
APPLY data dictionary view.
■ DML handlers.
■ Error handlers.
■ Update conflict handlers.
■ Substitute key columns for apply tables.
■ Instantiation SCN for each apply object.
■ Ignore SCN for each apply object.
■ Messaging Clients, including the following information for each messaging client:
■ Name of the messaging client.
■ Queue owner and queue name of the queue used by the messaging client.
■ Rule set owner and rule set name of each positive and negative rule set used by the messaging client.
■ Message notification settings.
■ Some data dictionary information about Streams rules. The rules themselves are imported regardless of the setting for the STREAMS_CONFIGURATION parameter.
■ Data dictionary information about Streams administrators, messaging clients, message rules, and extra attributes used in message rules.