Kbase 19810: SonicMQ: "Version mismatch" Error Starting Broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/15/2000 |
|
SUMMARY:
When the Progress SonicMQ Version 2000.x broker is started, it may
issue the following error message:
Version mismatch between broker and database. Version of the
broker tables in the database is NONE. Expected version is
<SonicMQ version #>.
EXPLANATION:
This error can occur in the following scenarios:
- The value of the BROKER_NAME property in the broker.ini file
does not match the broker name in the broker's database.
This can happen after installing a new release of SonicMQ over
an existing installation. During installation, as each file is
about to be copied to disk, if a file with the same name is
found, you are prompted with a question asking if you wish to
overwrite the existing file. If you inadvertently answer "yes"
when prompted whether to overwrite broker.ini, and you then
accept the default broker name ("SonicMQ"), if you had been
using a different broker name previously, the BROKER_NAME
property in broker.ini will not match the broker name stored in
the database.
- The basic tables have not been created in the broker's
database.
- For the broker in a single broker configuration, or for the
configuration server in an interbroker configuration, security
is enabled via the ENABLE_SECURITY property in the broker.ini
file, but the security tables have not been created in the
broker's database.
SOLUTION:
In the first case discussed above, if you have overwritten the broker
name in broker.ini in a previously working installation of SonicMQ,
all you need to do is set the BROKER_NAME property in broker.ini to
the value you have been using up to that point, and with which the
broker's database was initialized. Reinitializing the database will
also eliminate the error, but if you do so you will lose all messages,
queues, topics, and other information stored in the database.
In the second case discussed above, the basic database tables must be
created, and in the third case, the security database tables must be
created. In both of these cases, the remedy is to reinitialize the
broker's database using the dbtool script. This will recreate the
broker's database tables based on the current values in broker.ini.
References To Written Documentation:
SonicMQ Installation and Administration Guide, "Chapter 1,
Installation," the "Database Table Creation and Deletion Scripts"
subsection in the "Installation of the Broker" section.