command to dump recovery database pending messages

[Jennifer Schlender]

Does anyone have the command to dump the number of pending messages to an outbound thread in the recovery database? I don’t want to see the messages, just the number of them. The messages I’m curious about are all in state 7, so they don’t show as pending yet in the outbound thread, and the inbound thread has a negative queue depth that is slowly coming up to 0–neither is helpful. I can’t remember what causes a negative queue depth, but I’m about to go look in the archives. Thanks!

Jennifer

Topic

[Charlie Bursell]

hcidbdump -r -s 7 -d | wc

will give you a count.  Subtract 8 for the header and you have the number of messages in state 7 for the specified destivation thread.

Charlie

[Jared Miller]

I have a bunch of messages in state 7 of the recovery db going to a thread that doesn’t exist anymore.  Is there a command to have them removed??

[Kevin Scantlan]

hcidbdump -r -d -s 7 -D -F

Just type in “hcidbdump” with no options to get a list of options.

[Anonymous]

I stumbled onto an undocumented feature that causes hcidbdump to tell you what the count is.  Add a non switch string at the end of the command:

hcidbdump -r -s 7 -d conn_1 count

You get something like:

Processed 0 messages.

What it’s really doing is opening a file and writing the list to the file.

[Charlie Bursell]

This is *NOT* an undocumented feature:

hcidbdump {-r|-e} [-U userid] [-l] [-L] [-v] [-D] [-f source_system]

         [-o owner_system] [-d dest_system] [-t type] [-s state]

         [-S time] [-E time] [-M map] [-O time] [-b] [-a] [-F]

         [-m mid] [Output_file]

This is the Output_file option.  It is a count of the number of messages dumped into the Output_file.  I suppose you could use it as a count of the number of messages.  But, be aware you have created a file which may be rather large if a lot of messages or zero-length if no messages.

[Tom Henderson]

If you dump to the /dev/null file, the output goes nowhere (which is faster than storing in a file), you don’t get the side effect of a really big file, and you still get the number of messages reported to you.

So hcidump -r -s 7 target_connection /dev/null should report the number of messages

You may be able to do the same thing on Windows by specifying the output file as NUL:, but I have no way of testing it.

[Author]

Replies