hcimsgarchive
This command works on the data from the message archive database cache.
hcimsgarchive {-l | -L | -w | -d | -v | -c-c | -e} [-V] [-c templatename]
[-I templatename] [-p proc] [-t tablename] [-s threadname]
-
-l
lists the messages waiting to be updated to the external database. This outputs the list and the number of messages that are waiting to be written to the external database. -
-L
lists messages with Ultra Long form. Overrides-l
. -
-w
writes the messages to the external database. This outputs the list and the number of messages that are written to the external database. -
-d
deletes the messages without writing to the external database. This outputs the list and the number of message that are deleted. -
-v
verifies the connection to the external database. This tests the external database configuration. If the table does not exist in the external database, then the tool attempts to create the database using the table creation template. A row with placeholder data is inserted. The MID for this row is "0.0.0". -
-e
verifies whether a table exists in the external database.For example:
hcimsgarchive -e -t tableName
-
-c
cycles the log file. -
-V
is verbose mode. -
-C templatename
specifies the template to create the database table. -
-I templatename
specifies the template for inserting data to the external database. -
-p proc
is the Tcl procedure to modify the message data. If this is not specified, then the message is processed as usual. -
-t tablename
is the external database table name. This can be combined with-v
,-w
, or-e
. If not specified, then this processes all tables or messages. -
-s threadname
is the protocol thread name. This can be combined with-l
,-L
,-d
,-w
, or-p
. If not specified, then this processes all tables or messages.
The hcimsgarchive command runs the Tcl procedure before writing the message to the external database. After the procedure is run, hcimsgarchive inserts the values into the external database that are based on the returned values.
The procedure is valid when writing the message to the external
database. For the other actions, such as list
or
delete
, it is invalid.