Supported databases

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.

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

AIX

8.22

2000 SP3a3

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

10G

12.5

HP-UX

8.22

2000 SP3a3

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

10G

12.5

Linux (POWER platform)

8.22

Not applicable Not supported Not supported

Linux (x86 platform)

8.22

2000 SP3a3

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

10G

12.5

Linux (zSeries
platform)

8.22+4

Not applicable

Not supported

Not supported

Solaris
(SPARC platform)

8.22+5

2000 SP3a3

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

10G

12.5

Start of change

Solaris (x86-64 platform)

End of change
Start of change

8.22+5

End of change
Start of change

Not applicable

End of change
Start of change

10G

End of change
Start of change

12.5.3

End of change

Windows

8.210

2000 SP3a

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

10G8

12.5

z/OS

7.17
8.17

Not applicable

Not supported

Not applicable

Notes:
  1. Start of changeSupported releases of DB2, Oracle, and Sybase can participate as a Resource Manager in a distributed XA transaction, and can be coordinated by WebSphere MQ as the XA Transaction Manager. In WebSphere Event Broker, this support is referred to as a globally coordinated message flow. On z/OS, all transactions are coordinated by Recoverable Resource Services (RRS).

    XA coordination for messages in the MRM domain on Windows requires DB2 Version 8.2 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.

    End of change
  2. Check the readme.html file for your product to check if a fix pack or other fix is required.

    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.

  3. SQL Server is supported only as a remote database on Windows from a Linux or UNIX system using a supplied wire protocol driver.
  4. 31-bit support only is provided.
  5. Start of changeSolaris 10 on Solaris (SPARC platform) requires DB2 Version 8 FixPak 9 and Solaris (x86-64 platform) requires DB2 Version 8 FixPak 11.End of change
  6. You can use the embedded Derby database for verification, evaluation, and test purposes only. (Derby refers to IBM Cloudscape™ Version 10.0, a database product that is built on the Derby database from the Apache Software Foundation.) For a production system, install and configure your chosen enterprise database.
  7. On z/OS, DB2 is a mandatory requirement. You must create a unique database for each broker. See the Program Directory for WebSphere Event Broker for z/OS.
  8. Start of changeFor XA coordination with Oracle 10G on Windows you must install patch set three for Oracle 10G (10.1.0.4.0)End of change
Related concepts
Using Derby databases on Windows
Related tasks
Finding the latest information
Creating the databases
Related reference
Database locations
Database contents
Supported processors
Operating system requirements
Additional software requirements and support