A broker requires access to a database to store operational and state data. Databases from IBM and other suppliers are supported at specific versions on supported operating systems.
You must create the broker database before you create the broker, and specify the name of the database on the mqsicreatebroker command. The command creates tables to hold the broker data; these tables are listed in Database contents.
You can use the same database schema for all brokers that
are at the same version, if appropriate, even if you create the brokers
on different computers. The broker tables are created in a schema
that is determined by the user ID that you specify for the broker
database connection, and the rows within the tables are qualified
by a unique identifier (UUID) for each broker. The schema user ID
is set by -u dataSourceUserId (if you specified
this parameter on the mqsicreatebroker or mqsichangebroker command),
or by -i serviceUserId (if you did not specify
the -u parameter).
You can also create user databases to be accessed from message flows; database support is the same as that defined for brokers except where specifically stated. Some data types supported by these databases are not supported by WebSphere Message Broker; for details, see Data types of values from external sources.
In most environments, the broker does not have to be running on the same operating system as the database server. For details about local and remote database use, and the restrictions that apply, see Database locations.
The following table, and the accompanying notes, indicate the minimum levels of products that are supported for databases on each operating system. For the latest information on all supported platforms, visit the WebSphere Message Broker Requirements Web site.
Operating system | DB2®1+2 | Microsoft® SQL Server1 | Oracle1+3 | Sybase1 | Informix®1+4 |
---|---|---|---|---|---|
AIX® | 8.25 |
2000 SP3a7 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
HP-UX on Itanium | 8.25 |
Not supported | 10g Release 2 |
Not supported | Not supported |
HP-UX on PA-RISC | 8.25 |
2000 SP3a7 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 |
Linux® on POWER™10 | 8.25 |
Not supported | Not supported | Not supported | Not supported |
Linux on x86 | 8.25+11 |
2000 SP3a6 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 |
Linux on System z® | 8.25+12 |
Not supported | Not supported | Not supported | Not supported |
![]() ![]() |
![]() V5R2 ![]() |
Not supported | Not supported | Not supported | Not supported |
Solaris on SPARC | 8.25+14 |
2000 SP3a6 |
9i Release 2 Patch Set 4 |
12.5.3 |
Dynamic Server V9.4 Client SDK V2.90 with |
Solaris on x86-64 | 8.24+14 |
Not supported | 10g Release 1 |
Not supported | Not supported |
Windows® | 8.25+15 |
2000 SP3a |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
z/OS® | 7.117 |
Not supported | Not supported | Not supported | Not supported |
If you use WebSphere MQ Version 6.0 as a transaction manager, all datasources that are connected to DB2 from message flows in both 32-bit and 64-bit execution groups must connect to 64-bit DB2 instances.
XA coordination with 64-bit execution groups is available only with DB2 and Oracle.
XA coordination for messages in the MRM domain on Windows requires DB2 Version 8 Fix Pack 10 or later.
If you deploy message flows that access databases, you can define the message flows to be coordinated so that updates to those databases are synchronized with updates to other resources.
Each broker system requires only the client SDK; install the Dynamic Server on the system on which you create databases.
Support is not provided for 64-bit databases or XA coordination. Informix uses two types of large objects (LOBs); simple and smart. Simple LOBs are data types TEXT and BYTE, and they are supported. Smart LOBs are data types CLOB and BLOB, and they are unsupported.
DB2 Version 8.2 is functionally equivalent to Version 8.1 Fix Pack 7. If you install DB2 Version 8.2 from the supplied CDs or DVD, you might see information that indicates the Version 8.1 level, for example when you use the command db2level.
MQSI_SIGNAL_EXCLUSIONS=10
If you have installed Oracle, you must use the 32-bit client libraries.
If you do not require XA, you can install WebSphere MQ Version 6.0 (64-bit). XA is not supported because the 64-bit queue manager requires 64-bit ODBC drivers and switch files, which are not supplied.