4 Responses to “oracle advance queue 简单测试”

1. roger Says:
   
   1月 4, 2012 at 上午 5:13

   Procedure to Dequeue Messages from any Queue not using Message Grouping [ID 243665.1] -------------------------------------------------------------------------------- 修改时间 01-FEB-2011 类型 SCRIPT 状态 PUBLISHED In this Document Purpose Software Requirements/Prerequisites Configuring the Script Running the Script Caution Script Script Output References -------------------------------------------------------------------------------- Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.2 - Release: 8.1.7 to 11.2 Information in this document applies to any platform. Checked for currency on 18-MAY-2010 Purpose 1. Dequeues messages from a queue not using message grouping regardless of the payload type for a specified consumer by dequeuing messages with the REMOVE_NODATA option. Messages are removed without reading the data. This means that the payload parameter is not used and can be of any type (in this example RAW(1)). 2. For Single Consumer Queues specify the consumer parameter as NULL. For Multi-Consumer Queues specify the consumer. 3. Note that the message state will be changed to PROCESSED and whether the messages are removed from the underlying queue table depends on the retention time specified for that queue. 4. For For Queues created in Queue Tables with message_grouping set to DBMS_AQ.TRANSACTIONAL Queues, see Note: 305641.1. Software Requirements/Prerequisites Execution Environment: SQL*Plus, iSQL*Plus Configuring the Script Access Privileges: The user that owns the procedure should be granted AQ_ADMINISTRATOR_ROLE. Running the Script Usage: sqlplus user/password; a) For a Single Consumer Queue: EXEC aq_cleanup_queue ('Queue_Name', NULL); where 'Queue_Name' is replaced appropriately. b) For Multi Consumer Queue: EXEC aq_cleanup_queue ('Queue_Name','Consumer_Name'); where 'Queue_Name' and 'Consumer_Name' is replaced appropriately. Caution This script is provided for educational purposes only and not supported by Oracle Support Services. It has been tested internally, however, and works as documented. We do not guarantee that it will work for you, so be sure to test it in your environment before relying on it. Proofread this script before using it! Due to the differences in the way text editors, e-mail packages and operating systems handle text formatting (spaces, tabs and carriage returns), this script may not be in an executable state when you first receive it. Check over the script to ensure that errors of this type are corrected. Script CREATE OR REPLACE PROCEDURE aq_cleanup_queue(queue VARCHAR2, consumer VARCHAR2) AS deqopt DBMS_AQ.DEQUEUE_OPTIONS_T; mprop DBMS_AQ.MESSAGE_PROPERTIES_T; msgid RAW(16); more_msgs BOOLEAN := TRUE; payload RAW(1); cnt NUMBER := 0; cnt_max NUMBER := 1000; no_messages EXCEPTION; pragma EXCEPTION_INIT (no_messages, -25228); BEGIN deqopt.consumer_name := consumer; deqopt.navigation := DBMS_AQ.FIRST_MESSAGE; deqopt.wait := DBMS_AQ.NO_WAIT; deqopt.dequeue_mode := DBMS_AQ.REMOVE_NODATA; WHILE (more_msgs) LOOP BEGIN DBMS_AQ.DEQUEUE ( queue_name => queue, dequeue_options => deqopt, message_properties => mprop, payload => payload, msgid => msgid); COMMIT; -- to avoid ORA-1555 messages (Snapshot too old), re-execute the cursor -- and get a new snapshot by dequeuing with the FIRST_MESSAGE option cnt := cnt + 1; IF MOD (cnt, cnt_max) = 0 THEN deqopt.navigation := DBMS_AQ.FIRST_MESSAGE; ELSE deqopt.navigation := DBMS_AQ.NEXT_MESSAGE; END IF; EXCEPTION WHEN no_messages then more_msgs := FALSE; END; END LOOP; END; / EXAMPLE: Dequeuing messages from an Exception Queue --------------------------------------------------- o Enable your exception queue for dequeue. i.e. Execute dbms_aqadm.start_queue('', false, true); o Once the queue has been enabled you have to dequeue the message by its unique msgid. SQL> select queue, msg_id, msg_state from aq$multipleqtable; QUEUE MSG_ID MSG_STATE ------------------------------ -------------------------------- --------- AQ$_MULTIPLEQTABLE_E C0747533628E59A1E0340003BA10B7CA EXPIRED Where aq$multipleqtable is the queue table name for the exception queue. Dequeue the message: Example: DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; dq_msgid RAW(16); payload RAW(1); no_messages exception; pragma exception_init (no_messages, -25263); msg_count number(2); BEGIN dequeue_options.wait := DBMS_AQ.NO_WAIT; dequeue_options.navigation := DBMS_AQ.FIRST_MESSAGE; dequeue_options.dequeue_mode := dbms_aq.remove_nodata; dequeue_options.msgid := 'C0747533628E59A1E0340003BA10B7CA'; msg_count := 0; LOOP DBMS_AQ.DEQUEUE(queue_name => 'aqadm.AQ$_MULTIPLEQTABLE_E', dequeue_options => dequeue_options, message_properties => message_properties, payload => payload, msgid => dq_msgid); COMMIT; msg_count := msg_count + 1; dequeue_options.navigation := DBMS_AQ.NEXT_MESSAGE; END LOOP; EXCEPTION WHEN no_messages THEN DBMS_OUTPUT.PUT_LINE ('No of Messages Removed: '||msg_count); END; -- Disable your exception queue for dequeue. Execute dbms_aqadm.stop_queue('', true, true); The msg_count variable and output is purely for informational purposes. It shows that the message was found and removed (dequeued). If the syntax was correct, but the msgid was incorrect, the pl/sql block could 'successfully complete' but fail to remove any messages. Any variation of this can be used, if desired, depending on your requirements. The message was dequeued with dequeue_options.dequeue_mode := dbms_aq.remove_nodata; This will remove the message but will not attempt to read the data. In this example the aim was solely to remove the message and this was the most efficient manner in which to do that. When using this option, the data will be lost when the dequeue commits, so change it if this is not desired. For example, if the aim is to re-enqeueue the message after removal from the exception queue, remove_nodata would not be appropriate. The example above demonstrates how to remove a single message from an exception queue. When there are many messages in the exception queue it would not be practical to remove them all in this manner. It would be better to remove them all within the same pl/sql block or procedure. The following example reads all the msg_id's into a cursor prior to entering the dequeue process, and uses the cursor to pass the msg_id's to the dequeue procedure. Example: DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; dq_msgid RAW(16); payload RAW(1); no_messages exception; pragma exception_init (no_messages, -25263); msg_count number(2); cursor c_msg_ids is select msg_id from aq$multipleqtable where queue = 'AQ$_MULTIPLEQTABLE_E'; BEGIN dequeue_options.wait := DBMS_AQ.NO_WAIT; dequeue_options.navigation := DBMS_AQ.FIRST_MESSAGE; dequeue_options.dequeue_mode := dbms_aq.remove_nodata; For v_msg_id in c_msg_ids loop dequeue_options.msgid := v_msg_id.msg_id; msg_count := 0; DBMS_AQ.DEQUEUE(queue_name => 'aqadm.AQ$_MULTIPLEQTABLE_E', dequeue_options => dequeue_options, message_properties => message_properties, payload => payload, msgid => dq_msgid); dbms_output.put_line('Message id : '||v_msg_id.msg_id||' removed'); msg_count := msg_count + 1; dequeue_options.msgid := null; dequeue_options.navigation := DBMS_AQ.NEXT_MESSAGE; END LOOP; EXCEPTION WHEN no_messages THEN DBMS_OUTPUT.PUT_LINE ('No of Messages Removed: '||msg_count); COMMIT; END; / Demonstration: For the purpose of this demonstration all the messages in the queue table are in the exception queue. The PL/SQL block above has been saved as a script called deqexc.sql. SQL> select count(*) from multipleqtable; COUNT(*) ---------- 6 SQL> Execute dbms_aqadm.start_queue('AQ$_MULTIPLEQTABLE_E', false, true); PL/SQL procedure successfully completed. SQL> @deqexc Connected. Message id : C074E1DD06345A82E0340003BA10B7CA removed Message id : C0754D3E0A135A31E0340003BA10B7CA removed Message id : C074E199153F5A81E0340003BA10B7CA removed Message id : C074E21D13065A83E0340003BA10B7CA removed Message id : C074E2572D005A84E0340003BA10B7CA removed Message id : C074E29808AD5A85E0340003BA10B7CA removed PL/SQL procedure successfully completed. SQL> select count(*) from multipleqtable; COUNT(*) ---------- 0 Script Output No expected output.

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278

   Procedure to Dequeue Messages from any Queue not using Message Grouping [ID 243665.1]   --------------------------------------------------------------------------------   修改时间 01-FEB-2011     类型 SCRIPT     状态 PUBLISHED     In this Document   Purpose   Software Requirements/Prerequisites   Configuring the Script   Running the Script   Caution   Script   Script Output   References       --------------------------------------------------------------------------------       Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.2 - Release: 8.1.7 to 11.2 Information in this document applies to any platform. Checked for currency on 18-MAY-2010 Purpose 1. Dequeues messages from a queue not using message grouping regardless of the payload type for a specified consumer by dequeuing messages with the REMOVE_NODATA option. Messages are removed without reading the data. This means that the payload parameter is not used and can be of any type (in this example RAW(1)).   2. For Single Consumer Queues specify the consumer parameter as NULL. For Multi-Consumer Queues specify the consumer.   3. Note that the message state will be changed to PROCESSED and whether the messages are removed from the underlying queue table depends on the retention time specified for that queue.   4. For For Queues created in Queue Tables with message_grouping set to DBMS_AQ.TRANSACTIONAL Queues, see Note: 305641.1.   Software Requirements/Prerequisites Execution Environment:   SQL*Plus, iSQL*Plus Configuring the Script Access Privileges:   The user that owns the procedure should be granted AQ_ADMINISTRATOR_ROLE.   Running the Script Usage:   sqlplus user/password;   a) For a Single Consumer Queue: EXEC aq_cleanup_queue ('Queue_Name', NULL);   where 'Queue_Name' is replaced appropriately.   b) For Multi Consumer Queue: EXEC aq_cleanup_queue ('Queue_Name','Consumer_Name');   where 'Queue_Name' and 'Consumer_Name' is replaced appropriately.   Caution This script is provided for educational purposes only and not supported by Oracle Support Services. It has been tested internally, however, and works as documented. We do not guarantee that it will work for you, so be sure to test it in your environment before relying on it. Proofread this script before using it! Due to the differences in the way text editors, e-mail packages and operating systems handle text formatting (spaces, tabs and carriage returns), this script may not be in an executable state when you first receive it. Check over the script to ensure that errors of this type are corrected.   Script CREATE OR REPLACE PROCEDURE aq_cleanup_queue(queue VARCHAR2, consumer VARCHAR2) AS deqopt DBMS_AQ.DEQUEUE_OPTIONS_T; mprop DBMS_AQ.MESSAGE_PROPERTIES_T; msgid RAW(16); more_msgs BOOLEAN := TRUE; payload RAW(1); cnt NUMBER := 0; cnt_max NUMBER := 1000;   no_messages EXCEPTION; pragma EXCEPTION_INIT (no_messages, -25228);   BEGIN   deqopt.consumer_name := consumer;   deqopt.navigation := DBMS_AQ.FIRST_MESSAGE;   deqopt.wait := DBMS_AQ.NO_WAIT;   deqopt.dequeue_mode := DBMS_AQ.REMOVE_NODATA;     WHILE (more_msgs) LOOP    BEGIN     DBMS_AQ.DEQUEUE ( queue_name => queue,                       dequeue_options => deqopt,                       message_properties => mprop,                       payload => payload,                       msgid => msgid);     COMMIT;   -- to avoid ORA-1555 messages (Snapshot too old), re-execute the cursor -- and get a new snapshot by dequeuing with the FIRST_MESSAGE option      cnt := cnt + 1;      IF MOD (cnt, cnt_max) = 0 THEN     deqopt.navigation := DBMS_AQ.FIRST_MESSAGE;    ELSE     deqopt.navigation := DBMS_AQ.NEXT_MESSAGE;    END IF;      EXCEPTION    WHEN no_messages then     more_msgs := FALSE;    END;     END LOOP;   END; /     EXAMPLE: Dequeuing messages from an Exception Queue ---------------------------------------------------   o Enable your exception queue for dequeue. i.e.   Execute dbms_aqadm.start_queue('', false, true);   o Once the queue has been enabled you have to dequeue the message by its unique msgid.   SQL> select queue, msg_id, msg_state from aq$multipleqtable;   QUEUE MSG_ID MSG_STATE ------------------------------ -------------------------------- --------- AQ$_MULTIPLEQTABLE_E C0747533628E59A1E0340003BA10B7CA EXPIRED   Where aq$multipleqtable is the queue table name for the exception queue.   Dequeue the message:   Example:   DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; dq_msgid RAW(16); payload RAW(1); no_messages exception; pragma exception_init (no_messages, -25263); msg_count number(2);   BEGIN dequeue_options.wait := DBMS_AQ.NO_WAIT; dequeue_options.navigation := DBMS_AQ.FIRST_MESSAGE; dequeue_options.dequeue_mode := dbms_aq.remove_nodata; dequeue_options.msgid := 'C0747533628E59A1E0340003BA10B7CA'; msg_count := 0;   LOOP DBMS_AQ.DEQUEUE(queue_name => 'aqadm.AQ$_MULTIPLEQTABLE_E', dequeue_options => dequeue_options, message_properties => message_properties, payload => payload, msgid => dq_msgid); COMMIT;   msg_count := msg_count + 1; dequeue_options.navigation := DBMS_AQ.NEXT_MESSAGE; END LOOP;   EXCEPTION WHEN no_messages THEN DBMS_OUTPUT.PUT_LINE ('No of Messages Removed: '||msg_count); END;   -- Disable your exception queue for dequeue.   Execute dbms_aqadm.stop_queue('', true, true);     The msg_count variable and output is purely for informational purposes. It shows that the message was found and removed (dequeued). If the syntax was correct, but the msgid was incorrect, the pl/sql block could 'successfully complete' but fail to remove any messages. Any variation of this can be used, if desired, depending on your requirements.   The message was dequeued with dequeue_options.dequeue_mode := dbms_aq.remove_nodata; This will remove the message but will not attempt to read the data. In this example the aim was solely to remove the message and this was the most efficient manner in which to do that. When using this option, the data will be lost when the dequeue commits, so change it if this is not desired. For example, if the aim is to re-enqeueue the message after removal from the exception queue, remove_nodata would not be appropriate.   The example above demonstrates how to remove a single message from an exception queue. When there are many messages in the exception queue it would not be practical to remove them all in this manner. It would be better to remove them all within the same pl/sql block or procedure. The following example reads all the msg_id's into a cursor prior to entering the dequeue process, and uses the cursor to pass the msg_id's to the dequeue procedure.   Example:   DECLARE dequeue_options DBMS_AQ.dequeue_options_t; message_properties DBMS_AQ.message_properties_t; dq_msgid RAW(16); payload RAW(1); no_messages exception; pragma exception_init (no_messages, -25263); msg_count number(2);   cursor c_msg_ids is select msg_id from aq$multipleqtable where queue = 'AQ$_MULTIPLEQTABLE_E';   BEGIN   dequeue_options.wait := DBMS_AQ.NO_WAIT; dequeue_options.navigation := DBMS_AQ.FIRST_MESSAGE; dequeue_options.dequeue_mode := dbms_aq.remove_nodata;   For v_msg_id in c_msg_ids loop   dequeue_options.msgid := v_msg_id.msg_id; msg_count := 0;   DBMS_AQ.DEQUEUE(queue_name => 'aqadm.AQ$_MULTIPLEQTABLE_E', dequeue_options => dequeue_options, message_properties => message_properties, payload => payload, msgid => dq_msgid);   dbms_output.put_line('Message id : '||v_msg_id.msg_id||' removed'); msg_count := msg_count + 1; dequeue_options.msgid := null; dequeue_options.navigation := DBMS_AQ.NEXT_MESSAGE; END LOOP;   EXCEPTION WHEN no_messages THEN DBMS_OUTPUT.PUT_LINE ('No of Messages Removed: '||msg_count); COMMIT;   END; /     Demonstration:   For the purpose of this demonstration all the messages in the queue table are in the exception queue. The PL/SQL block above has been saved as a script called deqexc.sql.   SQL> select count(*) from multipleqtable;   COUNT(*) ---------- 6   SQL> Execute dbms_aqadm.start_queue('AQ$_MULTIPLEQTABLE_E', false, true);   PL/SQL procedure successfully completed.   SQL> @deqexc Connected. Message id : C074E1DD06345A82E0340003BA10B7CA removed Message id : C0754D3E0A135A31E0340003BA10B7CA removed Message id : C074E199153F5A81E0340003BA10B7CA removed Message id : C074E21D13065A83E0340003BA10B7CA removed Message id : C074E2572D005A84E0340003BA10B7CA removed Message id : C074E29808AD5A85E0340003BA10B7CA removed   PL/SQL procedure successfully completed.   SQL> select count(*) from multipleqtable;   COUNT(*) ---------- 0   Script Output No expected output.

2. www.chaojishop.com Says:
   
   1月 14, 2012 at 下午 3:57

   永远支持博主。

3. 惜分飞 Says:
   
   1月 14, 2012 at 下午 4:31

   roger，申请加入友情链接，我已经加你了
   惜分飞 http://www.xifenfei.com

4. admin Says:
   
   1月 15, 2012 at 上午 8:46

   to 惜分飞： 已经add了。

Leave a Reply

You must be logged in to post a comment.