F.M ENQUEUE & DEQUEUE_ : URGENT

i AM USING THESE F.M TO LOCK THE DATABASE TABLE SO AS TO AVOID DOUBLE NUMBER GENERATION WHILE SAVING A RECORD, I AM FACING A PROBLEM THAT THE TABLE IS BEING LOCKED BUT THE SECOND SEEION IS TERMINIATED AFTER 5 SECONDS , I WANT THAT THE SECOND SEEION SHOULD KEEP ON HOLD UNTILL THE FIRST IS SAVE COMPLETETLY , REPLY SOON

hi,
Wait for 3 seconds. use this statement and make the control wait until the completion of the previous session.
Regards,
Sailaja.

Similar Messages

DEQUEUING ORDER DIFFERS FROM ENQUEUING ORDER,URGENT ONE, PLS HELP

Hi ,
we are using ORACLE ADVANCED QUEUING for queue functionality.
our Oracle version is Oracle 8i release 8.1.5
Sometimes dequeuing order differs from enqueuing order. we are
enqueuing to the queue using default options only , i mean we
are not setting any prriority for messages .We are enqueuing 100
messages continuously to the queue.After completing enqueuing we
are dequeuing from the queue first in browse and then in remove
mode. We are using thin driver for database connectivity. If U
have any idea about this problem pls feel free to share with me .
Thanx in advance
Regards
Shilda Joseph
see the code snippet
enqueuing
aqMsg = qOracleQueue.createMessage();
aqRawPayload = aqMsg.getRawPayload();
byMsg = sMsgInfo.getBytes();
aqRawPayload.setStream(byMsg, byMsg.length);
AQEnqueueOption aqEnqueueOption = new AQEnqueueOption
qOracleQueue.enqueue(aqEnqueueOption, aqMsg);
dequeuing
aqDequeueOption.setWaitTime(1);
aqDequeueOption.setDequeueMode
(aqDequeueOption.DEQUEUE_BROWSE);
aqMsg = qOracleQueue.dequeue(aqDequeueOption);
//removing
AQDequeueOption aqDequeueOption1 = new AQDequeueOption
aqDequeueOption1.setDequeueMode
(aqDequeueOption.DEQUEUE_REMOVE);
AQMessage aqRemMsg = qOracleQueue.dequeue
(aqDequeueOption1);
see the enqueuing order and dequeuing order of hello 57, hello
58
2001/10/17 15:38:42:3 INFO [main] message enqueued - Helloo 1 to
HL7MESSAGEQUEUE
2001/10/17 15:38:42:124 INFO [main] message enqueued - Helloo 2
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:234 INFO [main] message enqueued - Helloo 3
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:334 INFO [main] message enqueued - Helloo 4
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:434 INFO [main] message enqueued - Helloo 5
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:544 INFO [main] message enqueued - Helloo 6
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:644 INFO [main] message enqueued - Helloo 7
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:755 INFO [main] message enqueued - Helloo 8
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:865 INFO [main] message enqueued - Helloo 9
to HL7MESSAGEQUEUE
2001/10/17 15:38:42:965 INFO [main] message enqueued - Helloo 10
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:75 INFO [main] message enqueued - Helloo 11
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:175 INFO [main] message enqueued - Helloo 12
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:275 INFO [main] message enqueued - Helloo 13
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:375 INFO [main] message enqueued - Helloo 14
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:476 INFO [main] message enqueued - Helloo 15
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:576 INFO [main] message enqueued - Helloo 16
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:686 INFO [main] message enqueued - Helloo 17
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:786 INFO [main] message enqueued - Helloo 18
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:886 INFO [main] message enqueued - Helloo 19
to HL7MESSAGEQUEUE
2001/10/17 15:38:43:986 INFO [main] message enqueued - Helloo 20
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:86 INFO [main] message enqueued - Helloo 21
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:187 INFO [main] message enqueued - Helloo 22
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:287 INFO [main] message enqueued - Helloo 23
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:397 INFO [main] message enqueued - Helloo 24
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:497 INFO [main] message enqueued - Helloo 25
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:597 INFO [main] message enqueued - Helloo 26
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:697 INFO [main] message enqueued - Helloo 27
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:797 INFO [main] message enqueued - Helloo 28
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:898 INFO [main] message enqueued - Helloo 29
to HL7MESSAGEQUEUE
2001/10/17 15:38:44:988 INFO [main] message enqueued - Helloo 30
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:98 INFO [main] message enqueued - Helloo 31
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:188 INFO [main] message enqueued - Helloo 32
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:298 INFO [main] message enqueued - Helloo 33
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:388 INFO [main] message enqueued - Helloo 34
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:488 INFO [main] message enqueued - Helloo 35
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:598 INFO [main] message enqueued - Helloo 36
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:689 INFO [main] message enqueued - Helloo 37
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:799 INFO [main] message enqueued - Helloo 38
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:899 INFO [main] message enqueued - Helloo 39
to HL7MESSAGEQUEUE
2001/10/17 15:38:45:989 INFO [main] message enqueued - Helloo 40
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:99 INFO [main] message enqueued - Helloo 41
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:189 INFO [main] message enqueued - Helloo 42
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:299 INFO [main] message enqueued - Helloo 43
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:390 INFO [main] message enqueued - Helloo 44
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:500 INFO [main] message enqueued - Helloo 45
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:600 INFO [main] message enqueued - Helloo 46
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:700 INFO [main] message enqueued - Helloo 47
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:790 INFO [main] message enqueued - Helloo 48
to HL7MESSAGEQUEUE
2001/10/17 15:38:46:900 INFO [main] message enqueued - Helloo 49
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:0 INFO [main] message enqueued - Helloo 50
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:111 INFO [main] message enqueued - Helloo 51
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:201 INFO [main] message enqueued - Helloo 52
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:301 INFO [main] message enqueued - Helloo 53
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:411 INFO [main] message enqueued - Helloo 54
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:501 INFO [main] message enqueued - Helloo 55
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:631 INFO [main] message enqueued - Helloo 56
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:731 INFO [main] message enqueued - Helloo 57
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:822 INFO [main] message enqueued - Helloo 58
to HL7MESSAGEQUEUE
2001/10/17 15:38:47:932 INFO [main] message enqueued - Helloo 59
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:22 INFO [main] message enqueued - Helloo 60
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:132 INFO [main] message enqueued - Helloo 61
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:222 INFO [main] message enqueued - Helloo 62
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:332 INFO [main] message enqueued - Helloo 63
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:432 INFO [main] message enqueued - Helloo 64
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:533 INFO [main] message enqueued - Helloo 65
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:623 INFO [main] message enqueued - Helloo 66
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:733 INFO [main] message enqueued - Helloo 67
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:823 INFO [main] message enqueued - Helloo 68
to HL7MESSAGEQUEUE
2001/10/17 15:38:48:933 INFO [main] message enqueued - Helloo 69
to HL7MESSAGEQUEUE
2001/10/17 15:38:49:23 INFO [main] message enqueued - Helloo 70
to HL7MESSAGEQUEUE
2001/10/17 15:38:49:123 INFO [main] message enqueued - Helloo 71
to HL7MESSAGEQUEUE
2001/10/17 15:38:49:214 INFO [main] message enqueued - Helloo 72
to HL7MESSAGEQUEUE
2001/10/17 15:38:49:324 INFO [main] message enqueued - Helloo 73
to HL7MESSAGEQUEUE
2001/10/17 15:38:49:684 INFO [main] message enqueued - Helloo 74
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:5 INFO [main] message enqueued - Helloo 75
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:105 INFO [main] message enqueued - Helloo 76
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:215 INFO [main] message enqueued - Helloo 77
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:305 INFO [main] message enqueued - Helloo 78
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:405 INFO [main] message enqueued - Helloo 79
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:505 INFO [main] message enqueued - Helloo 80
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:605 INFO [main] message enqueued - Helloo 81
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:696 INFO [main] message enqueued - Helloo 82
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:796 INFO [main] message enqueued - Helloo 83
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:886 INFO [main] message enqueued - Helloo 84
to HL7MESSAGEQUEUE
2001/10/17 15:38:50:996 INFO [main] message enqueued - Helloo 85
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:96 INFO [main] message enqueued - Helloo 86
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:186 INFO [main] message enqueued - Helloo 87
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:286 INFO [main] message enqueued - Helloo 88
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:387 INFO [main] message enqueued - Helloo 89
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:487 INFO [main] message enqueued - Helloo 90
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:587 INFO [main] message enqueued - Helloo 91
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:687 INFO [main] message enqueued - Helloo 92
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:797 INFO [main] message enqueued - Helloo 93
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:887 INFO [main] message enqueued - Helloo 94
to HL7MESSAGEQUEUE
2001/10/17 15:38:51:987 INFO [main] message enqueued - Helloo 95
to HL7MESSAGEQUEUE
2001/10/17 15:38:52:88 INFO [main] message enqueued - Helloo 96
to HL7MESSAGEQUEUE
2001/10/17 15:38:52:188 INFO [main] message enqueued - Helloo 97
to HL7MESSAGEQUEUE
2001/10/17 15:38:52:278 INFO [main] message enqueued - Helloo 98
to HL7MESSAGEQUEUE
2001/10/17 15:38:52:378 INFO [main] message enqueued - Helloo 99
to HL7MESSAGEQUEUE
2001/10/17 15:38:52:478 INFO [main] message enqueued - Helloo
100 to HL7MESSAGEQUEUE
2001/10/17 15:54:51:259 INFO [main] DS::run: Dequeue BROWSE -
Helloo 1
2001/10/17 15:54:51:319 INFO [main] DS::run: Dequeue
REMOVEHelloo 1
2001/10/17 15:54:51:619 INFO [main] DS::run: Dequeue BROWSE -
Helloo 2
2001/10/17 15:54:51:649 INFO [main] DS::run: Dequeue
REMOVEHelloo 2
2001/10/17 15:54:51:929 INFO [main] DS::run: Dequeue BROWSE -
Helloo 3
2001/10/17 15:54:51:960 INFO [main] DS::run: Dequeue
REMOVEHelloo 3
2001/10/17 15:54:52:290 INFO [main] DS::run: Dequeue BROWSE -
Helloo 4
2001/10/17 15:54:52:360 INFO [main] DS::run: Dequeue
REMOVEHelloo 4
2001/10/17 15:54:52:640 INFO [main] DS::run: Dequeue BROWSE -
Helloo 5
2001/10/17 15:54:52:671 INFO [main] DS::run: Dequeue
REMOVEHelloo 5
2001/10/17 15:54:52:951 INFO [main] DS::run: Dequeue BROWSE -
Helloo 6
2001/10/17 15:54:52:971 INFO [main] DS::run: Dequeue
REMOVEHelloo 6
2001/10/17 15:54:53:301 INFO [main] DS::run: Dequeue BROWSE -
Helloo 7
2001/10/17 15:54:53:321 INFO [main] DS::run: Dequeue
REMOVEHelloo 7
2001/10/17 15:54:53:672 INFO [main] DS::run: Dequeue BROWSE -
Helloo 8
2001/10/17 15:54:53:692 INFO [main] DS::run: Dequeue
REMOVEHelloo 8
2001/10/17 15:54:56:926 INFO [main] DS::run: Dequeue BROWSE -
Helloo 9
2001/10/17 15:54:56:946 INFO [main] DS::run: Dequeue
REMOVEHelloo 9
2001/10/17 15:54:57:257 INFO [main] DS::run: Dequeue BROWSE -
Helloo 10
2001/10/17 15:54:57:277 INFO [main] DS::run: Dequeue
REMOVEHelloo 10
2001/10/17 15:54:57:557 INFO [main] DS::run: Dequeue BROWSE -
Helloo 11
2001/10/17 15:54:57:627 INFO [main] DS::run: Dequeue
REMOVEHelloo 11
2001/10/17 15:54:57:918 INFO [main] DS::run: Dequeue BROWSE -
Helloo 12
2001/10/17 15:54:57:938 INFO [main] DS::run: Dequeue
REMOVEHelloo 12
2001/10/17 15:54:58:268 INFO [main] DS::run: Dequeue BROWSE -
Helloo 13
2001/10/17 15:54:58:278 INFO [main] DS::run: Dequeue
REMOVEHelloo 13
2001/10/17 15:54:58:569 INFO [main] DS::run: Dequeue BROWSE -
Helloo 14
2001/10/17 15:54:58:589 INFO [main] DS::run: Dequeue
REMOVEHelloo 14
2001/10/17 15:54:58:869 INFO [main] DS::run: Dequeue BROWSE -
Helloo 15
2001/10/17 15:54:58:959 INFO [main] DS::run: Dequeue
REMOVEHelloo 15
2001/10/17 15:54:59:260 INFO [main] DS::run: Dequeue BROWSE -
Helloo 16
2001/10/17 15:54:59:280 INFO [main] DS::run: Dequeue
REMOVEHelloo 16
2001/10/17 15:54:59:600 INFO [main] DS::run: Dequeue BROWSE -
Helloo 17
2001/10/17 15:54:59:620 INFO [main] DS::run: Dequeue
REMOVEHelloo 17
2001/10/17 15:54:59:911 INFO [main] DS::run: Dequeue BROWSE -
Helloo 18
2001/10/17 15:54:59:931 INFO [main] DS::run: Dequeue
REMOVEHelloo 18
2001/10/17 15:55:0:251 INFO [main] DS::run: Dequeue BROWSE -
Helloo 19
2001/10/17 15:55:0:321 INFO [main] DS::run: Dequeue REMOVEHelloo
19
2001/10/17 15:55:0:602 INFO [main] DS::run: Dequeue BROWSE -
Helloo 20
2001/10/17 15:55:0:622 INFO [main] DS::run: Dequeue REMOVEHelloo
20
2001/10/17 15:55:0:922 INFO [main] DS::run: Dequeue BROWSE -
Helloo 21
2001/10/17 15:55:0:932 INFO [main] DS::run: Dequeue REMOVEHelloo
21
2001/10/17 15:55:1:263 INFO [main] DS::run: Dequeue BROWSE -
Helloo 22
2001/10/17 15:55:1:283 INFO [main] DS::run: Dequeue REMOVEHelloo
22
2001/10/17 15:55:1:623 INFO [main] DS::run: Dequeue BROWSE -
Helloo 23
2001/10/17 15:55:1:633 INFO [main] DS::run: Dequeue REMOVEHelloo
23
2001/10/17 15:55:1:933 INFO [main] DS::run: Dequeue BROWSE -
Helloo 24
2001/10/17 15:55:1:953 INFO [main] DS::run: Dequeue REMOVEHelloo
24
2001/10/17 15:55:2:484 INFO [main] DS::run: Dequeue BROWSE -
Helloo 25
2001/10/17 15:55:2:504 INFO [main] DS::run: Dequeue REMOVEHelloo
25
2001/10/17 15:55:2:775 INFO [main] DS::run: Dequeue BROWSE -
Helloo 26
2001/10/17 15:55:2:855 INFO [main] DS::run: Dequeue REMOVEHelloo
26
2001/10/17 15:55:3:135 INFO [main] DS::run: Dequeue BROWSE -
Helloo 27
2001/10/17 15:55:3:155 INFO [main] DS::run: Dequeue REMOVEHelloo
27
2001/10/17 15:55:3:436 INFO [main] DS::run: Dequeue BROWSE -
Helloo 28
2001/10/17 15:55:3:456 INFO [main] DS::run: Dequeue REMOVEHelloo
28
2001/10/17 15:55:3:736 INFO [main] DS::run: Dequeue BROWSE -
Helloo 29
2001/10/17 15:55:3:756 INFO [main] DS::run: Dequeue REMOVEHelloo
29
2001/10/17 15:55:4:86 INFO [main] DS::run: Dequeue BROWSE -
Helloo 30
2001/10/17 15:55:4:106 INFO [main] DS::run: Dequeue REMOVEHelloo
30
2001/10/17 15:55:4:407 INFO [main] DS::run: Dequeue BROWSE -
Helloo 31
2001/10/17 15:55:4:427 INFO [main] DS::run: Dequeue REMOVEHelloo
31
2001/10/17 15:55:4:707 INFO [main] DS::run: Dequeue BROWSE -
Helloo 32
2001/10/17 15:55:4:727 INFO [main] DS::run: Dequeue REMOVEHelloo
32
2001/10/17 15:55:5:68 INFO [main] DS::run: Dequeue BROWSE -
Helloo 33
2001/10/17 15:55:5:88 INFO [main] DS::run: Dequeue REMOVEHelloo
33
2001/10/17 15:55:5:468 INFO [main] DS::run: Dequeue BROWSE -
Helloo 34
2001/10/17 15:55:5:488 INFO [main] DS::run: Dequeue REMOVEHelloo
34
2001/10/17 15:55:5:769 INFO [main] DS::run: Dequeue BROWSE -
Helloo 35
2001/10/17 15:55:5:789 INFO [main] DS::run: Dequeue REMOVEHelloo
35
2001/10/17 15:55:6:69 INFO [main] DS::run: Dequeue BROWSE -
Helloo 36
2001/10/17 15:55:6:149 INFO [main] DS::run: Dequeue REMOVEHelloo
36
2001/10/17 15:55:6:430 INFO [main] DS::run: Dequeue BROWSE -
Helloo 37
2001/10/17 15:55:6:450 INFO [main] DS::run: Dequeue REMOVEHelloo
37
2001/10/17 15:55:6:730 INFO [main] DS::run: Dequeue BROWSE -
Helloo 38
2001/10/17 15:55:6:750 INFO [main] DS::run: Dequeue REMOVEHelloo
38
2001/10/17 15:55:7:31 INFO [main] DS::run: Dequeue BROWSE -
Helloo 39
2001/10/17 15:55:7:51 INFO [main] DS::run: Dequeue REMOVEHelloo
39
2001/10/17 15:55:7:381 INFO [main] DS::run: Dequeue BROWSE -
Helloo 40
2001/10/17 15:55:7:401 INFO [main] DS::run: Dequeue REMOVEHelloo
40
2001/10/17 15:55:7:692 INFO [main] DS::run: Dequeue BROWSE -
Helloo 41
2001/10/17 15:55:7:702 INFO [main] DS::run: Dequeue REMOVEHelloo
41
2001/10/17 15:55:7:992 INFO [main] DS::run: Dequeue BROWSE -
Helloo 42
2001/10/17 15:55:8:12 INFO [main] DS::run: Dequeue REMOVEHelloo
42
2001/10/17 15:55:8:372 INFO [main] DS::run: Dequeue BROWSE -
Helloo 43
2001/10/17 15:55:8:392 INFO [main] DS::run: Dequeue REMOVEHelloo
43
2001/10/17 15:55:8:683 INFO [main] DS::run: Dequeue BROWSE -
Helloo 44
2001/10/17 15:55:8:703 INFO [main] DS::run: Dequeue REMOVEHelloo
44
2001/10/17 15:55:8:983 INFO [main] DS::run: Dequeue BROWSE -
Helloo 45
2001/10/17 15:55:9:3 INFO [main] DS::run: Dequeue REMOVEHelloo
45
2001/10/17 15:55:9:314 INFO [main] DS::run: Dequeue BROWSE -
Helloo 46
2001/10/17 15:55:9:394 INFO [main] DS::run: Dequeue REMOVEHelloo
46
2001/10/17 15:55:9:704 INFO [main] DS::run: Dequeue BROWSE -
Helloo 47
2001/10/17 15:55:9:724 INFO [main] DS::run: Dequeue REMOVEHelloo
47
2001/10/17 15:55:10:15 INFO [main] DS::run: Dequeue BROWSE -
Helloo 48
2001/10/17 15:55:10:35 INFO [main] DS::run: Dequeue REMOVEHelloo
48
2001/10/17 15:55:10:335 INFO [main] DS::run: Dequeue BROWSE -
Helloo 49
2001/10/17 15:55:10:355 INFO [main] DS::run: Dequeue
REMOVEHelloo 49
2001/10/17 15:55:10:696 INFO [main] DS::run: Dequeue BROWSE -
Helloo 50
2001/10/17 15:55:10:716 INFO [main] DS::run: Dequeue
REMOVEHelloo 50
2001/10/17 15:55:10:996 INFO [main] DS::run: Dequeue BROWSE -
Helloo 51
2001/10/17 15:55:11:16 INFO [main] DS::run: Dequeue REMOVEHelloo
51
2001/10/17 15:55:11:337 INFO [main] DS::run: Dequeue BROWSE -
Helloo 52
2001/10/17 15:55:11:357 INFO [main] DS::run: Dequeue
REMOVEHelloo 52
2001/10/17 15:55:11:687 INFO [main] DS::run: Dequeue BROWSE -
Helloo 53
2001/10/17 15:55:11:707 INFO [main] DS::run: Dequeue
REMOVEHelloo 53
2001/10/17 15:55:11:998 INFO [main] DS::run: Dequeue BROWSE -
Helloo 54
2001/10/17 15:55:12:18 INFO [main] DS::run: Dequeue REMOVEHelloo
54
2001/10/17 15:55:12:338 INFO [main] DS::run: Dequeue BROWSE -
Helloo 55
2001/10/17 15:55:12:348 INFO [main] DS::run: Dequeue
REMOVEHelloo 55
2001/10/17 15:55:12:709 INFO [main] DS::run: Dequeue BROWSE -
Helloo 56
2001/10/17 15:55:12:729 INFO [main] DS::run: Dequeue
REMOVEHelloo 56
2001/10/17 15:55:12:989 INFO [main] DS::run: Dequeue BROWSE -
Helloo 58
2001/10/17 15:55:13:9 INFO [main] DS::run: Dequeue REMOVEHelloo
58
2001/10/17 15:55:13:319 INFO [main] DS::run: Dequeue BROWSE -
Helloo 57
2001/10/17 15:55:13:339 INFO [main] DS::run: Dequeue
REMOVEHelloo 57
2001/10/17 15:55:13:670 INFO [main] DS::run: Dequeue BROWSE -
Helloo 59
2001/10/17 15:55:13:690 INFO [main] DS::run: Dequeue
REMOVEHelloo 59
2001/10/17 15:55:13:970 INFO [main] DS::run: Dequeue BROWSE -
Helloo 60
2001/10/17 15:55:13:990 INFO [main] DS::run: Dequeue
REMOVEHelloo 60
2001/10/17 15:55:14:291 INFO [main] DS::run: Dequeue BROWSE -
Helloo 61
2001/10/17 15:55:14:311 INFO [main] DS::run: Dequeue
REMOVEHelloo 61
2001/10/17 15:55:14:591 INFO [main] DS::run: Dequeue BROWSE -
Helloo 62
2001/10/17 15:55:14:671 INFO [main] DS::run: Dequeue
REMOVEHelloo 62
2001/10/17 15:55:15:603 INFO [main] DS::run: Dequeue BROWSE -
Helloo 63
2001/10/17 15:55:15:623 INFO [main] DS::run: Dequeue
REMOVEHelloo 63
2001/10/17 15:55:15:933 INFO [main] DS::run: Dequeue BROWSE -
Helloo 64
2001/10/17 15:55:15:953 INFO [main] DS::run: Dequeue
REMOVEHelloo 64
2001/10/17 15:55:16:274 INFO [main] DS::run: Dequeue BROWSE -
Helloo 65
2001/10/17 15:55:16:294 INFO [main] DS::run: Dequeue
REMOVEHelloo 65
2001/10/17 15:55:16:624 INFO [main] DS::run: Dequeue BROWSE -
Helloo 66
2001/10/17 15:55:16:644 INFO [main] DS::run: Dequeue
REMOVEHelloo 66
2001/10/17 15:55:16:934 INFO [main] DS::run: Dequeue BROWSE -
Helloo 67
2001/10/17 15:55:16:944 INFO [main] DS::run: Dequeue
REMOVEHelloo 67
2001/10/17 15:55:17:325 INFO [main] DS::run: Dequeue BROWSE -
Helloo 68
2001/10/17 15:55:17:345 INFO [main] DS::run: Dequeue
REMOVEHelloo 68
2001/10/17 15:55:17:665 INFO [main] DS::run: Dequeue BROWSE -
Helloo 69
2001/10/17 15:55:17:685 INFO [main] DS::run: Dequeue
REMOVEHelloo 69
2001/10/17 15:55:17:956 INFO [main] DS::run: Dequeue BROWSE -
Helloo 70
2001/10/17 15:55:17:976 INFO [main] DS::run: Dequeue
REMOVEHelloo 70
2001/10/17 15:55:18:326 INFO [main] DS::run: Dequeue BROWSE -
Helloo 71
2001/10/17 15:55:18:346 INFO [main] DS::run: Dequeue
REMOVEHelloo 71
2001/10/17 15:55:18:617 INFO [main] DS::run: Dequeue BROWSE -
Helloo 72
2001/10/17 15:55:18:687 INFO [main] DS::run: Dequeue
REMOVEHelloo 72
2001/10/17 15:55:19:17 INFO [main] DS::run: Dequeue BROWSE -
Helloo 73
2001/10/17 15:55:19:37 INFO [main] DS::run: Dequeue REMOVEHelloo
73
2001/10/17 15:55:19:338 INFO [main] DS::run: Dequeue BROWSE -
Helloo 74
2001/10/17 15:55:19:358 INFO [main] DS::run: Dequeue
REMOVEHelloo 74
2001/10/17 15:55:19:668 INFO [main] DS::run: Dequeue BROWSE -
Helloo 75
2001/10/17 15:55:19:688 INFO [main] DS::run: Dequeue
REMOVEHelloo 75
2001/10/17 15:55:20:19 INFO [main] DS::run: Dequeue BROWSE -
Helloo 76
2001/10/17 15:55:20:39 INFO [main] DS::run: Dequeue REMOVEHelloo
76
2001/10/17 15:55:20:359 INFO [main] DS::run: Dequeue BROWSE -
Helloo 77
2001/10/17 15:55:20:379 INFO [main] DS::run: Dequeue
REMOVEHelloo 77
2001/10/17 15:55:20:660 INFO [main] DS::run: Dequeue BROWSE -
Helloo 78
2001/10/17 15:55:20:680 INFO [main] DS::run: Dequeue
REMOVEHelloo 78
2001/10/17 15:55:21:20 INFO [main] DS::run: Dequeue BROWSE -
Helloo 79
2001/10/17 15:55:21:40 INFO [main] DS::run: Dequeue REMOVEHelloo
79
2001/10/17 15:55:21:361 INFO [main] DS::run: Dequeue BROWSE -
Helloo 80
2001/10/17 15:55:21:381 INFO [main] DS::run: Dequeue
REMOVEHelloo 80
2001/10/17 15:55:21:661 INFO [main] DS::run: Dequeue BROWSE -
Helloo 81
2001/10/17 15:55:21:681 INFO [main] DS::run: Dequeue
REMOVEHelloo 81
2001/10/17 15:55:22:72 INFO [main] DS::run: Dequeue BROWSE -
Helloo 82
2001/10/17 15:55:22:82 INFO [main] DS::run: Dequeue REMOVEHelloo
82
2001/10/17 15:55:22:382 INFO [main] DS::run: Dequeue BROWSE -
Helloo 83
2001/10/17 15:55:22:402 INFO [main] DS::run: Dequeue
REMOVEHelloo 83
2001/10/17 15:55:22:692 INFO [main] DS::run: Dequeue BROWSE -
Helloo 84
2001/10/17 15:55:22:713 INFO [main] DS::run: Dequeue
REMOVEHelloo 84
2001/10/17 15:55:23:53 INFO [main] DS::run: Dequeue BROWSE -
Helloo 85
2001/10/17 15:55:23:63 INFO [main] DS::run: Dequeue REMOVEHelloo
85
2001/10/17 15:55:23:403 INFO [main] DS::run: Dequeue BROWSE -
Helloo 86
2001/10/17 15:55:23:413 INFO [main] DS::run: Dequeue
REMOVEHelloo 86
2001/10/17 15:55:23:694 INFO [main] DS::run: Dequeue BROWSE -
Helloo 87
2001/10/17 15:55:23:714 INFO [main] DS::run: Dequeue
REMOVEHelloo 87
2001/10/17 15:55:24:886 INFO [main] DS::run: Dequeue BROWSE -
Helloo 88
2001/10/17 15:55:24:966 INFO [main] DS::run: Dequeue
REMOVEHelloo 88
2001/10/17 15:55:25:286 INFO [main] DS::run: Dequeue BROWSE -
Helloo 89
2001/10/17 15:55:25:296 INFO [main] DS::run: Dequeue
REMOVEHelloo 89
2001/10/17 15:55:25:637 INFO [main] DS::run: Dequeue BROWSE -
Helloo 90
2001/10/17 15:55:25:657 INFO [main] DS::run: Dequeue
REMOVEHelloo 90
2001/10/17 15:55:25:937 INFO [main] DS::run: Dequeue BROWSE -
Helloo 91
2001/10/17 15:55:25:957 INFO [main] DS::run: Dequeue
REMOVEHelloo 91
2001/10/17 15:55:26:338 INFO [main] DS::run: Dequeue BROWSE -
Helloo 92
2001/10/17 15:55:26:358 INFO [main] DS::run: Dequeue
REMOVEHelloo 92
2001/10/17 15:55:26:628 INFO [main] DS::run: Dequeue BROWSE -
Helloo 93
2001/10/17 15:55:26:648 INFO [main] DS::run: Dequeue
REMOVEHelloo 93
2001/10/17 15:55:26:928 INFO [main] DS::run: Dequeue BROWSE -
Helloo 94
2001/10/17 15:55:26:948 INFO [main] DS::run: Dequeue
REMOVEHelloo 94
2001/10/17 15:55:27:319 INFO [main] DS::run: Dequeue BROWSE -
Helloo 95
2001/10/17 15:55:27:339 INFO [main] DS::run: Dequeue
REMOVEHelloo 95
2001/10/17 15:55:27:609 INFO [main] DS::run: Dequeue BROWSE -
Helloo 96
2001/10/17 15:55:27:629 INFO [main] DS::run: Dequeue
REMOVEHelloo 96
2001/10/17 15:55:27:910 INFO [main] DS::run: Dequeue BROWSE -
Helloo 97
2001/10/17 15:55:27:930 INFO [main] DS::run: Dequeue
REMOVEHelloo 97
2001/10/17 15:55:28:280 INFO [main] DS::run: Dequeue BROWSE -
Helloo 98
2001/10/17 15:55:28:360 INFO [main] DS::run: Dequeue
REMOVEHelloo 98
2001/10/17 15:55:28:631 INFO [main] DS::run: Dequeue BROWSE -
Helloo 99
2001/10/17 15:55:28:651 INFO [main] DS::run: Dequeue
REMOVEHelloo 99
2001/10/17 15:55:28:941 INFO [main] DS::run: Dequeue BROWSE -
Helloo 100
2001/10/17 15:55:28:951 INFO [main] DS::run: Dequeue
REMOVEHelloo 100

As other members adviced
Please check the following as a list
1) Check first fi the Material is in APO relevant
2) Check if it has active integration model in cfm5 (R/3)
3) Check if the material has no blocked queues in /n/sapapo/cq (APO)
If there are any blocked queues please clear them accordingly.
4) After that perform a reconciliation of the transactional data through.
/n/sapapo/ccr(APO). perform it only for that material and on planned orders.
If there are any errors it will usggest you to follow few steps.
5) then again go back and check the /n/sapapo/cq transaction.
6) Check if the material and its location has publication Types maintained in SPRO transaction.
7) Check if the change pointers of this Planned order exists in /n/sapapo/c5
This si change pointers transaction , soemtimes you can release ti from there also.
If you still have problem, give the resutls of the following for reference.
Let us know once you perform all these.
8) Incase you need to perform the consistency checks externally.

Enqueue and Dequeue consept----Please explain urgent

hi all,
i want to use sap locking mechanisn (Enqueue and dequeue consept) while updating database table....please explain how to use this while updating a database table.
Thanks in advance
Nandha kumar

Nandha,
Good document on this concept..
Activating a lock object in the ABAP Dictionary automatically creates function modules for setting (ENQUEUE_<lock object name>) and releasing (DEQUEUE_<lock object name>) locks.
The generated function modules are automatically assigned to function groups. You should not change these function modules and their assignment to function groups since the function modules are generated again each time the lock object is activated.
Never transport the function groups, which contain the automatically generated function modules. The generated function modules of a lock object could reside in a different function group in the target system. Always transport the lock objects. When a lock object is activated in the target system, the function modules are generated again and correctly assigned to function groups.
Parameters of the Function Modules
Field Names of the Lock Object
The keys to be locked must be passed here.
A further parameter X_<field> that defines the lock behavior when the initial value is passed exists for every lock field <field>. If the initial value is assigned to <field> and X_<field>, then a generic lock is initialized with respect to <field>. If <field> is assigned the initial value and X_<field> is defined as X, the lock is set with exactly the initial value of <field>.
Parameters for Passing Locks to the Update Program
A lock is generally removed at the end of the transaction or when the corresponding DEQUEUE function module is called. However, this is not the case if the transaction has called update routines. In this case a parameter must check that the lock has been removed.
Parameter _SCOPE controls how the lock or lock release is passed to the update program (see The Owner Concept for Locks). You have the following options:
_SCOPE = 1: Locks and lock releases are not passed to the update program. The lock is removed when the transaction is ended.
_SCOPE = 2: The lock or lock release is passed to the update program. The update program is responsible for removing the lock. The interactive program with which the lock was requested no longer has an influence on the lock behavior. This is the standard setting for the ENQUEUE function module.
_SCOPE = 3: The lock or lock release is also passed to the update program. The lock must be removed in both the interactive program and in the update program. This is the standard setting for the DEQUEUE function module.
Parameters for Lock Mode
A parameter MODE_<TAB> exists for each base table TAB of the lock object. The lock mode for this base table can be set dynamically with this parameter. Valid values for this parameter are S (shared), E (exclusive) and X (exclusive but not cumulative).
The lock mode specified when the lock object for the table is created is the default value for this parameter. This default value can however be overridden as required when the function module is called.
If a lock set with a lock mode is to be removed by calling the DEQUEUE function module, this call must have the same value for the parameter MODE_<TAB>.
Controlling Lock Transmission
Parameter _COLLECT controls whether the lock request or lock release should be performed directly or whether it should first be written to the local lock container. This parameter can have the following values:
Initial value: The lock request or lock release is sent directly to the lock server.
X : The lock request or lock release is placed in the local lock container. The lock requests and lock releases collected in this lock container can then be sent to the lock server at a later time as a group by calling the function module FLUSH_ENQUEUE.
Behavior for Lock Conflicts (ENQUEUE only)
The ENQUEUE function module also has the parameter _WAIT. This parameter determines the lock behavior when there is a lock conflict.
You have the following options:
Initial value: If a lock attempt fails because there is a competing lock, the exception FOREIGN_LOCK is triggered.
X : If a lock attempt fails because there is a competing lock, the lock attempt is repeated after waiting for a certain time. The exception FOREIGN_LOCK is triggered only if a certain time limit has elapsed since the first lock attempt. The waiting time and the time limit are defined by profile parameters.
Controlling Deletion of the Lock Entry (DEQUEUE only)
The DEQUEUE function module also has the parameter _SYNCHRON.
If X is passed, the DEQUEUE function waits until the entry has been removed from the lock table. Otherwise it is deleted asynchronously, that is, if the lock table of the system is read directly after the lock is removed, the entry in the lock table may still exist.
Exceptions of the ENQUEUE Function Module
FOREIGN_LOCK: A competing lock already exists. You can find out the name of the user holding the lock by looking at system variable SY-MSGV1.
SYSTEM_FAILURE: This exception is triggered when the lock server reports that a problem occurred while setting the lock. In this case, the lock could not be set.
If the exceptions are not processed by the calling program itself, appropriate messages are issued for all exceptions.
Reference Fields for RFC-Enabled Lock Objects
The type of an RFC-enabled function module must be completely defined. The parameters of the generated function module therefore have the following reference fields for RFC-enabled lock objects:
Parameters
Reference fields
X_<field name>
DDENQ_LIKE-XPARFLAG
_WAIT
DDENQ_LIKE-WAITFLAG
_SCOPE
DDENQ_LIKE-SCOPE
_SYNCHRON
DDENQ_LIKE-SYNCHRON
Pls. reward if useful

URGENT: Not able to Enqueu/Dequeue messages

Hi,
I am using Java Programming language to create Qs. I am trying to enqueue a message into the Q and I am not getting any error or exception. But when I check the Queue table for the message, I find no records in the table.
Any pointers as what is going wrong?
Quick response will be much appreciated.
Thanks,
Sunil

Many possible reasons:
- there was an error enqueueing (try to look more for log, maybe log is disabled? Are you using Log4J?)
- you didn't commit transaction
- your messages are already consumed
- you specify invalid queue name (for example, in PL/SQL, it's a good idea to specify queue name with owner prefix - like 'AQ.MW')
Myrra

How to create ENQUEUE function module for s567 table

Hi Experts,
Anyone Plz tell the steps how to create a ENQUEUE function module for the table s567.
Its somewht urgent, plz help me.
<REMOVED BY MODERATOR>
Mohana
Edited by: Alvaro Tejada Galindo on Mar 10, 2008 4:21 PM

Hi,
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
Hope this will give a basic idea.
Regards
Sudheer

Very urgent --pls help Report Painter Problem,

Hi to all,
I have created 5 operating expenses report by cost centres through report painter. some for full period , some for actual and sone for budget.
Under one set of that cost centre reports I have many subsets under which there are cost centre groups and then the cost centres.
I want to add one more set to existing set. I have added the set and set contains one cost centre group and their are also cost centres under it.
The table which i am using for cost centre grous is GLT1 and field is RCNTR and for cost centres it is CCSS and KOSTL respectively.
In the above procedure I have two queries.
1)even after adding the set and when i try to execute the report from T- code SERP it doesnot show my created set in variation.
2)Also even if it was showing the set earlier but report was showing zero values. When i clicked on zero amount a pop up arises for plan and actual values and when i clicked on plan values it had value of Rs 255000(for cost centres). then outside why this amount doesnot appears.
PLS THIS IS VERY VERY URGENT
Regards
TANUJA

I've just read this thread three times and I have absolutely no idea what you are doing, in what version, and what you are asking for help with.
Do you want to change the message type? If you do you MUST drop the queue and start over again from the beginning.
Do you want to enqueue messages?
Post your DDL and other relevant information or you are on your own. We can not guess at your issue.

Where do I use These lock object FM's (Enqueue & D? and How do I use them?

I created lock object for user defined table (zconsist). The system automatically created 2 FM's (Enquiue & Dequeue).
I created a new TCode and accessing this with mulitple users to do some updates and inserts in that above table.
I used INSERT ZCONSIST statement in 5 places in my program (4 include programs).
Where do I use These FM's? and How do I use them?
I mean before inserting which FM I need to use? after immediately what fm used?.
every insert statemnt before i need to use the respective fm? so 5 places i need to call the respective FM is it right?
thank in advance.

Hi Sekhar,
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
check this link for example.
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
tables:vbak.
call function 'ENQUEUE_EZLOCK3'
exporting
mode_vbak = 'E'
mandt = sy-mandt
vbeln = vbak-vbeln
X_VBELN = ' '
_SCOPE = '2'
_WAIT = ' '
_COLLECT = ' '
EXCEPTIONS
FOREIGN_LOCK = 1
SYSTEM_FAILURE = 2
OTHERS = 3
if sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Normally ABAPers will create the Lock objects, because we know when to lock and how to lock and where to lock the Object then after completing our updations we unlock the Objects in the Tables
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
purpose: If multiple user try to access a database object, inconsistency may occer. To avoid that inconsistency and to let multiple user give the accessibility of the database objects the locking mechanism is used.
Steps: first we create a loc object in se11 . Suppose for a table mara. It will create two functional module.:
1. enque_lockobject
1. deque_lockobject
before updating any table first we lock the table by calling enque_lockobject fm and then after updating we release the lock by deque_lockobject.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
GO TO SE11
Select the radio button "Lock object"..
Give the name starts with EZ or EY..
Example: EYTEST
Press Create button..
Give the short description..
Example: Lock object for table ZTABLE..
In the tables tab..Give the table name..
Example: ZTABLE
Save and generate..
Your lock object is now created..You can see the LOCK MODULES..
In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
Lock objects:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Match Code Objects:
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
See this link:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Check these links -
lock objects
Lock Objects
Lock Objects
kindly reward if found helpful.
cheers,
Hema.

JMS Exception for oc4j 9.0.3 with 9.0.1.1.1 database (Urgent)

When I enqueue message into the AQ, I got the following error message
oracle.jms.AQjmsException: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'AQ$_JMS_ENQUEUE_TEXT_MESSAGE'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1161)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1371)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1221)
Please help, this is very urgent! Should I apply any patch to my database? Or something is wrong with the oc4j 9.0.3 container. From 9.0.2 container, I am able to publish a message into the queue from a standalone JMS client.
Thanks

When I enqueue message into the AQ, I got the following error message
oracle.jms.AQjmsException: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'AQ$_JMS_ENQUEUE_TEXT_MESSAGE'Chunming -- just replace the ../j2ee/home/lib/aqapi.jar with your $oracle_home/rdbms/jlib/aqapi13.jar ... remember to rename it :). This worked for me.
have you been able to get an MDB to dequeue from aq? I can enqueue fine (msgs show up in the queue_table) .
good luck!
z

[URGENT] Get Inbound Message in EBS Using XML Gateway + SOAP

Hi experts,
I want to ask you about how to process the inbound message using XML Gateway and SOAP protocol.
I have 2 EBS instances, let's called it A (source) and B (destination).
FYI, I'm following this ebook: "Oracle E-Business Suite Development and Extensibility Handbook" in chapter 12 regarding Oracle XML Gateway.
So I don't use BPEL PM to do this.
I'm just using EBS with XML Gateway and Integrated SOA Gateway responsibilities.
When I tried to send the XML from A to B using OXTA, it's success, the data can be processed in B and could store in the database.
But when I tried to use SOAP, the XML message that has been sent from A is success, and when I check it on B (Integrated SOA Gateway -> SOA Monitor), the message is in there and I can see the SOAP request and response as well.
SOAP request:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://xmlns.oracle.com/apps/fnd/XMLGateway" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <env:Header>
- <ns0:XMLGateway_Header>
<ns0:MESSAGE_TYPE>XML</ns0:MESSAGE_TYPE>
<ns0:MESSAGE_STANDARD>OAG</ns0:MESSAGE_STANDARD>
<ns0:TRANSACTION_TYPE>XKLB</ns0:TRANSACTION_TYPE>
<ns0:TRANSACTION_SUBTYPE>ORDER_DETAILS_XO</ns0:TRANSACTION_SUBTYPE>
<ns0:DOCUMENT_NUMBER>9282</ns0:DOCUMENT_NUMBER>
<ns0:PARTY_SITE_ID>142</ns0:PARTY_SITE_ID>
<ns0:USERNAME>cons.ade</ns0:USERNAME>
<ns0:PASSWORD>cons.ade</ns0:PASSWORD>
</ns0:XMLGateway_Header>
</env:Header>
- <env:Body>
<ns0:ReceiveDocument xsi:type="xsd:string"><ORDER_DETAILS_XO xmlns=""> <ORDER> <ORDNO>100002</ORDNO> <ORDWT>100002</ORDWT> <RDATE/> <CITY>JAKARTA</CITY> <ZIP>17121</ZIP> </ORDER> </ORDER_DETAILS_XO></ns0:ReceiveDocument>
</env:Body>
</env:Envelope>
SOAP response:
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
- <env:Body>
- <ReceiveDocument_Response xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">
<ResponseCode xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">200</ResponseCode>
<ResponseMsgId xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">BD4EAD91E76051D5E0440021287448DA</ResponseMsgId>
<ResponseInfo xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">Document received and pushed into queue for asynchronous processing. Enqueued message id is 'BD4EAD91E76051D5E0440021287448DA'.</ResponseInfo>
</ReceiveDocument_Response>
</env:Body>
</env:Envelope>
But the problem is the message that has been got in B can't store into the database yet.
I had already changed the Queue in the XML Gateway -> Define Transaction, from APPLSYS.ECX_IN_OAG_Q (this is for OXTA) to APPLSYS.WF_WS_JMS_IN.
After I invoke the webservice and the SOAP message has been got in B, I checked APPLSYS.WF_WS_JMS_IN in database and there is 1 record, the value of USER_DATA column is:
((, , , , , , ((BES_EVENT_NAME, 100, oracle.apps.fnd.wf.ws.inbound.xmltx.receive, , 27), (BES_EVENT_KEY, 100, 796550960, , 27), (BES_PRIORITY, 200, , 1, 23), (BES_FROM_AGENT, 100, [email protected], , 27), (BES_TO_AGENT, 100, [email protected], , 27), (MSG_ID, 100, 1334117503435, , 27), (ECX_MESSAGE_TYPE, 100, XML, , 27), (ECX_MESSAGE_STANDARD, 100, OAG, , 27), (ECX_PARTY_SITE_ID, 100, 142, , 27), (WS_PORT_OPERATION, 100, ReceiveDocument, , 27), (ECX_TRIGGER_ID, 100, 7101, , 27), (UserId, 100, 3020, , 27), (ECX_USERNAME, 100, CONS.ADE, , 27), (ECX_TRANSACTION_SUBTYPE, 100, ORDER_DETAILS_XO, , 27), (ECX_PASSWORD, 100, CONS.ADE, , 27), (ECX_DOCUMENT_NUMBER, 100, 9285, , 27), (BES_PAYLOAD_OBJECT, 100, false, , 27), (ECX_ATTACHMENTS, 100, , , 27), (ECX_TRANSACTION_TYPE, 100, XKLB, , 27), , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , )), 0, , )
When I tried to select APPLSYS.WF_WS_JMS_IN for the 2nd time, there is no result, which means the business event has been triggered, right?
So in this point I still don't have any idea why the process is (likely) ended after enter the Queue and the message can't store into B's database yet.
Do I miss any setup when changing from OXTA into SOAP protocol to send XML message?
Any urgent help most appreciated.
Best Regards,
Rheza

Hi,
Did you ever get any answers to this? We are thinking about the same thing.
Thanks
Darma
[email protected]

How to dequeue Oracle queue(enqueue in Ora) in java using JMS text message

I'm trying below java code but its giving me error:
public class testq {
public static void main(String[] args) throws Exception {
testq q = new testq();
AQSession aq_sess = createSession();
q.runTest(aq_sess);
public static AQSession createSession() {
Connection db_conn;
AQSession aq_sess = null;
try {
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
/* Load the Oracle8i AQ driver: */
Class.forName("oracle.AQ.AQOracleDriver");
db_conn = DriverManager.getConnection("jdbc:oracle:thin:@10.10.10.10:1521:demo", "demo_app", "demo");
System.out.println("JDBC Connection opened ");
db_conn.setAutoCommit(false);
/* Creating an AQ Session: */
aq_sess = AQDriverManager.createAQSession(db_conn);
System.out.println("Successfully created AQSession ");
catch (Exception ex) {
System.out.println("Exception: " + ex);
ex.printStackTrace();
return aq_sess;
public void runTest(AQSession aq_sess) {
//AQQueueTable q_table;
AQQueue queue;
AQMessage message;
AQRawPayload raw_payload;
AQDequeueOption deq_option;
byte[] b_array;
Connection db_conn;
try {
db_conn = ((AQOracleSession)aq_sess).getDBConnection();
/* Get a handle to a queue - aq_queue4 in aquser schema: */
queue = aq_sess.getQueue ("myadmin", "STREAM_QUEUE_DEMO");
System.out.println("Successful getQueue");
/* Creating a AQDequeueOption object with default options: */
deq_option = new AQDequeueOption();
deq_option.setDequeueMode(AQDequeueOption.DEQUEUE_REMOVE);
/* Set wait time to 10 seconds: */
deq_option.setWaitTime(10);
/* Dequeue a message: */
message = queue.dequeue(deq_option);
System.out.println("Successful dequeue");
/* Retrieve raw data from the message: */
raw_payload = message.getRawPayload();
b_array = raw_payload.getBytes();
db_conn.commit();
String value = new String(b_array);
System.out.println("queue="+value);
} catch(Exception e) {
e.printStackTrace();
The error says "oracle.AQ.AQException: JMS-174: Class must be specified for queues with object payloads
Use dequeue(deq_option, payload_fact) or dequeue(deq_option, sql_data_cl)"
Can any one tell me how to fix this error & how to get bulk dequeue messages?
And i am using sys.AQ$_JMS_TEXT_MESSAGE payload type during enqueue.
Can any one tell me how to fix this Java program to dequeue it?
Thanks in advance...Please its urgent
Thanks!

the code is as bellow
File fBlob = new File ("test.pdf");
FileInputStream fIS = new FileInputStream(fBlob);
pstUpdate= con.prepareStatement("UPDATE table set file = ? where id = ?");
pstUpdate.setBinaryStream(1, fIS, (int) fBlob.length());
pstUpdate.setString(2, rs.getString("id"));
pstUpdate.execute();
con.commit();

Query on sap locks(ENQUEUE/DEQUEUE)

Hi All,
should the sap locks ENQUEUE/DEQUEUE need to be used for all the updation/insertion of records ino the table?
Please confirm.Should this locking technique be used even for insertion of records into the table?
Regards,
Pra.

Hi,
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
   protects read access to an object. The read lock allows other transactions read access but not write access to
   the locked area of the table
- Write Lock(exclusive lock)
   protects write access to an object. The write lock allows other transactions neither read nor write access to
    the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
Hope this will give a basic idea.

Very Urgent Pls help : Change of payload type to user-defined types

Hello Experts
I was using sys.xml_type as payload type in my queue table creation.
consider xml message
<order>
<id>1</id>
<load rerer="mq" erere='gg" > </load>
</order>
This i inserted into queue table using enqueue process.
this is done.
BUT NOW My manager wants to change the payload type.
he created a type
create or replace type systype as object (msg varchar2(4000));
Now payload type of queue table is changed to
PayloadType==>aq.systype.
Pls help me how can i insert xml messages into this queue table.
This is very urgent. Pls help me
S

I've just read this thread three times and I have absolutely no idea what you are doing, in what version, and what you are asking for help with.
Do you want to change the message type? If you do you MUST drop the queue and start over again from the beginning.
Do you want to enqueue messages?
Post your DDL and other relevant information or you are on your own. We can not guess at your issue.

Change Data Capture HELP URGENT

I have read all the Oracle Documentation for Change Data Capture, however I have been unable to find some specific things, the first one being: is it possible for another Oracle DB to be a subscriber to the changes published in CDC? If so, how can this be done?
I have several databases that are going to be changing constantly and I need to integrate all those changes to one specific target DB how can I set up my target DB to gather the changes published from all the other databases? is it even possible? can it be done automatically? or do I have to create a separate interface (like a java based application) to gather those changes in some way from the subscriber views enqueue them, process them ,and then apply them to my target DB?
Some help will be appreciated a lot!
Thanks.
Angel M.

You won't get help if you put URGENT in your subject.
Everyone here donates their time and offers help on a purely voluntary, goodwill basis.
If you want something answered urgently, you visit metalink and ask your support questions of the Oracle support staff whom you pay to provide you with a service of which you can quite legitimately make service-level demands.
Otherwise, you wait your turn here and don't try to jump the queue by claiming urgency and priority you aren't paying for.

ENQUEUE, DEQUEUE of objects

Hi all,
i want to lock sales orders with fm ENQUEUE_EVVBAKE and
DEQUEUE_EVVBAKE.
This two fms work fine if i am in the same mode.
I start the fm ENQUEUE_EVVBAKE from one mode and want to unlock the entries from another mode.
The fm DEQUEUE_EVVBAKE runs with no errors. But the lock entry in the SM12 still exists.
Any ideas?
regards

Hi
See this and do accordingly
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
You have to use these function module in your program.
check this link for example.
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
tables:vbak.
call function 'ENQUEUE_EZLOCK3'
exporting
mode_vbak = 'E'
mandt = sy-mandt
vbeln = vbak-vbeln
X_VBELN = ' '
_SCOPE = '2'
_WAIT = ' '
_COLLECT = ' '
EXCEPTIONS
FOREIGN_LOCK = 1
SYSTEM_FAILURE = 2
OTHERS = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Normally ABAPers will create the Lock objects, because we know when to lock and how to lock and where to lock the Object then after completing our updations we unlock the Objects in the Tables
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
purpose: If multiple user try to access a database object, inconsistency may occer. To avoid that inconsistency and to let multiple user give the accessibility of the database objects the locking mechanism is used.
Steps: first we create a loc object in se11 . Suppose for a table mara. It will create two functional module.:
1. enque_lockobject
1. deque_lockobject
before updating any table first we lock the table by calling enque_lockobject fm and then after updating we release the lock by deque_lockobject.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
GO TO SE11
Select the radio button "Lock object"..
Give the name starts with EZ or EY..
Example: EYTEST
Press Create button..
Give the short description..
Example: Lock object for table ZTABLE..
In the tables tab..Give the table name..
Example: ZTABLE
Save and generate..
Your lock object is now created..You can see the LOCK MODULES..
In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
Lock objects:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Match Code Objects:
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
See this link:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Check these links -
lock objects
Lock Objects
Lock Objects
Regards
Anji

Different _scope parameter of Enqueue_ lock object and Dequeue_ lock objec

Hi, all.
When we create lock object and generate enqueue_<lock object> and
dequeue_<lock object>, the default value of _scope is
enqueue : _scope = 2(update owner only)
dequeue : _scope = 3(for both dialog owner and update owner).
Does anyone tell me the reason of this different default values?
i read help.sap.com - lock related help but i couldn't get the idea
of these different default values between enqueue and dequeue.
Best Regards.
Sejoon

Hi,
When you use ENQUEUE, the owner is going to lock that record. So at that time, the only person who can modify the record in the one who has locked it using ENQUEUE. So only he needs to be informed.
Whereas when you use DEQUEUE, the owner who has locked the record and processed it + the 2nd user who wants to lock it needs to be informed. Hence it is to update the 1st User(who has done the update and planning to release the lock) + 2nd User(who wants to do the update and planning to lock the record ).
Best regards,
Prashant

F.M ENQUEUE & DEQUEUE_ : URGENT

Similar Messages

Maybe you are looking for