Supported databases

A broker requires access to a database to store operational and state data. You must create the 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.

Multiple brokers within a single instance can access the same database, if appropriate, because the tables that are created are qualified by the broker name. Brokers in different installation locations on the same system cannot share a database.

The following table, and the accompanying notes, indicate the minimum levels of database products that are supported on each operating system.

You can also configure message flows that access user databases. The support provided is the same as for broker databases, shown in the table below.

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.

Start of change
Operating system DB2®1 Microsoft SQL Server Oracle1 Sybase1 Informix2
AIX

8.23

2000 SP3a4

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

10G Release 1
10G Release 2

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

Start of changeHP-UX (Itanium platform)End of change Start of change

8.23

End of change
Start of changeNot applicableEnd of change Start of change

10G Release 2

End of change
Start of changeNot supportedEnd of change Start of changeNot supportedEnd of change
HP-UX (PA-RISC platform)

8.23

2000 SP3a4

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

10G Release 1
10G Release 2

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

Linux (POWER platform)

8.23+5

Not applicable Not supported Not supported Not supported
Linux (x86 platform)

8.23+6

2000 SP3a4

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

10G Release 1
10G Release 2

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

Linux (zSeries platform)

8.23+7

Not applicable Not supported Not supported Not supported
OS/4008

8.23

Not applicable Not applicable Not applicable Not supported
Solaris (SPARC platform)

8.23+9+10

2000 SP3a4

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

10G Release 1
10G Release 2

12.5.3

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90 with
UC4X8 fix pack

Solaris (x86-64 platform)

8.23+9

Not applicable

10G Release 1
10G Release 2

12.5.3

Not supported

Windows

8.23+11

2000 SP3a

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

10G Release 112
10G Release 212

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

z/OS

7.113
8.113

Not applicable Not supported Not applicable Not supported
End of change
Notes:
  1. Supported 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 Message Broker, this support is referred to as globally coordinated message flow support. On z/OS, all transactions are coordinated by Recoverable Resource Services (RRS).

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

  2. Informix is supported only as a user database accessed by message flows; you cannot create a broker database as an Informix database. The client SDK only is required on each broker system; install the Dynamic Server on the system on which you create databases. Support is not provided for 64-bit databases, XA coordination, or Large Objects (LOBs).

    If you install the client SDK on Solaris (SPARC platform), request fix pack UC4X8 from Informix.

  3. Check the readme.html file for your product to check whether 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.

  4. You can use a remote SQL Server database on Windows from a Linux or UNIX system using a supplied wire protocol driver.
  5. Start of changeOn Linux (POWER platform), XA coordination is restricted to 32-bit brokers only.End of change
  6. Start of changeIf you have installed Linux x86 (64-bit) Red Hat Enterprise Linux AS V4.0:
    • DB2 is the only database supported on this operating system.
    • If you have installed DB2 V8 FP9, you must use a 32-bit database instance. If you have a later release of DB2, you can use both 32-bit and 64-bit database instances.
    • XA is not supported.
    End of change
  7. Start of changeIf you have installed Linux zSeries (64-bit) Red Hat Enterprise Linux AS V4.0, and you install a 31-bit DB2 Runtime Client, the client must be at DB2 V8 FP10 or higher, and no other DB2 product can be installed on the same system. Therefore, the 64-bit DB2 server must be located on a separate Linux zSeries image from the one in which the broker is installed.End of change
  8. You can configure message flows to access DB2 databases on OS/400 for user data. The message flows can run on any supported broker platform. You cannot create a broker database on OS/400 as a remote DB2 database from any broker platform. For further details of these restrictions, and for information about the PTFs that are required with this product, see Database locations.
  9. Solaris 10 on Solaris (SPARC platform) requires DB2 Version 8 FixPak 9; Solaris 10 on Solaris (x86-64 platform) requires DB2 Version 8 FixPak 11.
  10. Start of changeOn Solaris (SPARC platform), XA coordination is restricted to 32-bit brokers only.End of change
  11. 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.
  12. On Windows, for XA coordination with Oracle 10G you must install Patch Set 3 for Oracle 10G (10.1.0.4.0).
  13. On z/OS, DB2 is a mandatory requirement. You must create a unique database for each broker. See the Program Directory for WebSphere Message Broker for z/OS or the Program Directory for WebSphere Message Broker for z/OS for further details.
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