The product requires a configuration repository accessed
by the Configuration Manager and a broker database accessed
by each broker. Multiple brokers can access the same database, if appropriate, because
all tables are qualified by the broker name. You can also configure message flows to access user databases.
The broker tables are created when you invoke the mqsicreatebroker command. The configuration repository
tables are created when you invoke the mqsicreateconfigmgr command. The tables that are created are listed in Database contents.
The following table indicates
which levels of database are supported on which operating systems. In
most situations, the component that accesses the database does not have to
be running on the same operating system as the database server. For details
about local and remote database use, and existing restrictions, see Database locations.
Operating system |
DB21+2+3+4 |
Microsoft SQL Server |
Oracle1+2 |
Sybase |
AIX
|
 7.2
8.1
8.2
|
Not applicable
|
9i Rel 25
|
12.56
|
HP-UX
|
 7.2
8.17
8.27
|
Not applicable
|
9i Rel 25
|
12.56
|
Linux on Intel
|
 7.2
8.1
8.2
|
Not applicable
|
Not applicable
|
Not applicable
|
Linux on zSeries
|
 7.2
8.1
8.2
|
Not applicable
|
Not supported
|
Not supported
|
OS/400®8
|
V5R1
V5R2
|
Not applicable
|
Not applicable
|
Not applicable
|
Solaris
|
7.2
8.1
|
Not applicable
|
9i Rel 25
|
12.56
|
Windows 2000
Professional,
Server and
Advanced Server
Windows XP
Professional
|
7.2
8.1
|
2000 SP3
|
9i Rel 25
|
12.5
|
Windows Server 2003
|
8.1
|
2000 SP3a
|
9i Rel 24+5+9
|
 12.56
|
z/OS
|
7.110
|
Not applicable
|
Not supported
|
Not applicable
|
Notes:
XA transaction support: on distributed systems, referred to as
supporting a globally coordinated message flow, is coordinated by WebSphere MQ as
the XA Transaction Manager.
On z/OS, all transactions are coordinated
by RRS, unless CAF is used. See Database locations for further
details about CAF.
64-bit database support is provided on AIX, HP_UX, and Solaris
and refers to database clients only. The broker runs as a 32-bit application
and interacts with 32-bit database libraries.- The broker supports connections to a 32-bit database client that connects
to a 64-bit server.
- The broker does not support connections to a 64-bit database client due
to limitations in both broker and ODBC drivers.
- Oracle 9i supports both 64-bit and 32-bit libraries. 64-bit libraries
are the default selection, and are installed in ${ORACLE_HOME}/lib;
32-bit libraries are installed in ${ORACLE_HOME}/lib32.
Use the mqsi_setupdatabase command
to configure the broker environment if you want it to access the 32-bit libraries.

- You must use DB2 for the configuration
repository maintained by the Configuration Manager on Windows.
No other database is supported for this purpose. If you also use DB2 for your
broker database, you can configure the same database for the configuration
repository and the broker.
Check the readme.html file for your product
to check if a FixPak or other fix is required:- On all distributed systems except Windows 2003, on which it is not supported,
DB2 V7.2 requires FixPak9.
- If coordinated transaction support is required with DB2 8.1 on distributed
systems, apply FixPak 3.
- On Linux on Intel and Linux on zSeries, DB2 V8.1 requires FixPak2.

- To avoid potential stress problems, apply Oracle Patch Set 3 (3095277)
. This does not apply to Windows XP.
For AIX 5.2, HP-UX 11.11, Solaris 9, and Windows 2003, you must
apply ESD#1 (Sybase Version 12.5.0.3).
HP-UX 11.0 does not support DB2 8.1 or DB2 8.2.
- You can configure OS/400 databases for remote user database
access only. For further details of these restrictions, and for information
about the PTFs that are required with this product, see Database locations.
- Oracle Patch Set 2 (2761332) is required.
- PTFs are required with this product. See the WebSphere
Business Integration Message Broker for
z/OS Program Directory for further details.