![]() Propagation may be scheduled in these ways.Ī dedicated schedule in which the propagation runs forever or for a specified duration. ![]() ![]() For example, when exporting an AQ multiconsumer queue table, the following tables are automatically exported:ĪQ$_ queue_table _T (the time-management IOT)ĪQ$_ queue_table_S (the subscriber table)įor transactional event queues, the following tables are automatically exported:ĪQ$_ queue_name_T (time-management table)ĪQ propagation jobs are run by the Oracle Scheduler. In table mode, queue tables, all related tables, and primary object grants are exported automatically. However, doing a user-level export from one schema to another using the FROMUSER TOUSER clause is not supported. In user mode, queue tables, all related tables, and primary object grants are exported automatically. In full database mode, queue tables, all related tables, system-level grants, and primary and secondary object grants are exported automatically. Incremental exports on queue tables are not supported. However, if another problem is encountered while doing the import (such as running out of rollback segment space), then you should correct the problem and repeat the import.Įxporting operates in full database mode, user mode, and table mode. This message can be ignored, because the queuing system automatically corrects the obsolete ROWIDs as a part of the import operation. See Export Modes.īecause the metadata tables contain ROWIDs of some rows in the queue table, the import process generates a note about the ROWIDs being made obsolete when importing the metadata tables. These tables are exported automatically during full database mode, user mode and table mode exports. Transactional event queues are associated with the following objects: For AQ queues, a queue table that supports multiple recipients is associated with the following tables:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |