Durable subscriber problem in 10G

Question

Hello all,
We are trying to upgrade an application which uses AQ from Oracle 9i to 10G (10.2.0).
While having a topic owned by one user (metr_data) and trying to create a durable subscriber as another one (metr), we're getting an ORA-01031 error. Just dequeueing
messages as this user works fine...
Is there some additional privilege to be granted for creating durable subscribers?
A small test program:
// Create queue as metr_data
Properties p = new Properties();
p.put("user","metr_data");
p.put("password","metr_data");
Connection c1 = DriverManager.getConnection("jdbc:oracle:thin:system/system@//localhost:1521/WTS",p);
TopicConnection topicConnection1 = AQjmsTopicConnectionFactory.createTopicConnection(c1);
topicConnection1.start();
AQjmsSession topicSession1 = (AQjmsSession)topicConnection1.createTopicSession(true,0);
AQQueueTableProperty qtp = new AQQueueTableProperty("SYS.AQ$_JMS_TEXT_MESSAGE");
qtp.setMultiConsumer(true);
AQQueueTable qt = topicSession1.createQueueTable("metr_data", "testtab", qtp);
System.out.println("Created table");
AQjmsDestinationProperty dp = new AQjmsDestinationProperty();
AQjmsDestination t = (AQjmsDestination) topicSession1.createTopic(qt, "test",dp);
System.out.println("Created queue" );
Topic topic1 = topicSession1.createTopic("METR_DATA.test");
System.out.println(topic1);
( (AQjmsDestination)topic1).grantTopicPrivilege(topicSession1, "DEQUEUE","metr", false);
// Access queue as metr
Connection c = DriverManager.getConnection("jdbc:oracle:thin:system/system@//localhost:1521/WTS","metr","metr");
TopicConnection topicConnection = AQjmsTopicConnectionFactory.createTopicConnection(c);
topicConnection.start();
TopicSession topicSession = topicConnection.createTopicSession(true,0);
Topic topic = topicSession.createTopic("metr_data.test");
System.out.println(topic);
TopicSubscriber s = topicSession.createDurableSubscriber(topic,"metr");
System.out.println(s);
I do have granted the metr user execute on the 4 traditional aq packages.....
Regards,
Francois.

Answer 1

Hi All,
I am able to connect again using the same clientid when i stop/start the web application. I am just curious why the command "imqcmd destroy dur" has no effect on such a situation.