tailieunhanh - Oracle Built−in Packages- P52

Oracle Built−in Packages- P52: Ah, for the good old days of Version of PL /SQL! Life was so simple then. No stored procedures or functions and certainly no packages. You had your set of built−in functions, like SUBSTR and TO_DATE. You had the IF statement and various kinds of loops. With these tools at hand, you built your batch−processing scripts for execution in SQL*Plus, and you coded your triggers in SQL*Forms , and you went home at night content with a good day's work done. | Appendix A What s on the Companion Disk available in your environment. You will as covered in a later section need to grant access to Oracle AQ to specific users. Before you can execute any programs in the DBMS_AQADM or DBMS_AQ packages you may need to grant EXECUTE privilege on those packages explicitly role-based privileges do not take effect inside stored code . If you have trouble executing any program in these packages connect to the SYS account and execute these commands GRANT EXECUTE ON DBMS_AQADM TO user GRANT EXECUTE ON DBMS_AQ TO user where user is the name of the account to which you want to grant EXECUTE privilege. Database Initialization You will need to set one or more initialization parameters in order to obtain the desired behavior from Oracle AQ. Starting the Queue Monitor One of the features of Oracle AQ is the ability to manage the time in which messages are available for dequeueing and the time after which messages are expired. If you want to employ this time management feature you need to add a parameter to your initialization file or file for your database instance. The name of this parameter is AQ_TM_PROCESSES and it can be assigned a nonzero integer value. If the parameter is set to any number between 1 and 10 that number of Queue Monitor background processes will be created to monitor messages in the various queues. The name of the process created is ora_aqtm_ oracle_SID where oracle_SID is the System ID for the database instance being started. If the parameter is not specified or is set to 0 then the Queue Monitor background process will not be created. Here is an example of a line in the file that specifies that one Queue Monitor process be created AQ_TM_PROCESSES 1 If the Queue Monitor process it not started you will not be able to start and stop the Queue Monitor using the and procedures respectively. Starting propagation processes .