A broker requires a database to contain operational and state data. Multiple brokers within a single instance can access the same database, if appropriate, because all tables are qualified by the broker name. Brokers in different installation locations on the same system cannot share a database. You can also configure message flows to access user databases.
The broker tables are created when you invoke the mqsicreatebroker 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 broker 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 | DB2®1 | Microsoft SQL Server | Oracle1 | Sybase |
---|---|---|---|---|
AIX |
8.22 |
Not applicable |
![]() 9i Rel 2 Patch Set 4 ![]() 10G |
12.5 |
HP-UX |
8.22 |
Not applicable |
![]() 9i Rel 2 Patch Set 4 ![]() 10G |
12.5 |
Linux (x86 platform) |
8.22 |
Not applicable |
![]() 9i Rel 2 Patch Set 4 ![]() 10G |
12.5 |
Linux (zSeries platform) |
8.22 |
Not applicable |
Not supported |
Not supported |
OS/4003 |
8.22 |
Not applicable |
Not applicable |
Not applicable |
Solaris |
8.22 |
Not applicable |
![]() 9i Rel 2 Patch Set 4 ![]() 10G |
12.5 |
Windows |
8.22+4 |
2000 SP3a |
![]() 9i Rel 2 Patch Set 4 ![]() 10G |
12.5 |
z/OS |
7.15 8.15 |
Not applicable |
Not supported |
Not applicable |
XA coordination for messages in the MRM domain on Windows requires DB2 Version 8.2 FixPak 10 or later.