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, and the accompanying notes, indicate the minimum levels of database that 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 | Sybase1 | Informix2 |
---|---|---|---|---|---|
AIX |
8.23 |
2000 SP3a4 |
9i Rel 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
HP-UX |
8.23 |
2000 SP3a4 |
9i Rel 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
Linux (POWER platform) |
8.23 |
Not applicable | Not supported | Not supported | Not supported |
Linux (x86 platform) |
8.23 |
2000 SP3a4 |
9i Rel 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
Linux (zSeries |
8.23+5 |
Not applicable |
Not supported |
Not supported |
Not supported |
OS/4006 |
8.23 |
Not applicable |
Not applicable |
Not applicable |
Not supported |
Solaris |
8.23+7 |
2000 SP3a4 |
9i Rel 2 Patch Set 4 |
12.5 |
![]() Dynamic Server V9.4 ![]() |
![]() Solaris (x86-64 platform) ![]() |
![]() 8.23+7 ![]() |
![]() Not applicable ![]() |
![]() 10G ![]() |
![]() 12.5.3 ![]() |
![]() Not supported ![]() |
Windows |
8.23+8 |
2000 SP3a |
9i Rel 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
z/OS |
7.19 |
Not applicable |
Not supported |
Not applicable |
Not supported |
XA coordination for messages in the MRM domain on Windows requires DB2 Version 8 FixPak 10 or later.
If you use WebSphere MQ Version 6.0 as a transaction manager, all datasources connected to DB2 from message flows in both 32-bit and 64-bit execution groups must connect to 64-bit DB2 instances.
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.
If you install the client SDK on Solaris (SPARC platform), request fix pack UC4X8 from Informix.
DB2 Version 8.2 is functionally equivalent to Version 8.1 FixPak 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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah10030_ |