This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: ah10030_
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:30:05

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. Some datatypes supported by these databases are not supported by WebSphere Message Broker; for details see Datatype support.

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.

Database support is shown below; for the latest details on all supported platforms, visit the WebSphere Message Broker Requirements Web site.

Start of change
Operating system DB21 Microsoft SQL Server Oracle1+2 Sybase1 Informix1+3
AIX

8.24
9.14

2000 SP3a5
2005 SP15

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

10G Release 1
10G Release 25

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

HP-UX (Integrity platform)

8.24
9.14

Not applicable

10G Release 2

Not supported Not supported
HP-UX (PA-RISC platform)

8.24
9.14

2000 SP3a5
2005 SP15

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 HC4 fix pack

Linux (POWER platform)

8.24
9.14

Not applicable

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 (x86 platform)

8.24+7
9.14

2000 SP3a5
2005 SP15

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 UC3 fix pack

Linux (zSeries platform)

8.24
9.14

Not applicable

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

10G Release 1
10G Release 2

Not supported

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

OS/4008

8.23

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

8.24+9
9.14

2000 SP3a5
2005 SP15

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

Solaris (x86-64 platform)

8.24+9
9.14

Not applicable

10G Release 1
10G Release 2

12.5

Not supported
Windows

8.24+10
9.14

2000 SP3a5
2005 SP15

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 TC7 fix pack

Client SDK V2.90
with TC4 fix pack

z/OS

8.111
9.111

Not applicable Not supported Not applicable Not supported
End of change
Notes:
  1. Start of changeSupported releases of DB2, Informix, 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).

    WebSphere MQ Version 6.0.1 or later is required for globally coordinated transaction support (XA).

    If you use WebSphere MQ Version 6 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 with 64-bit execution groups is available only with DB2 and Oracle.

    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.

    End of change
  2. If you install the Oracle Database Server, you must also install the Oracle Runtime Client.
  3. 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.

    Large Objects (LOBs) are not supported.

  4. 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.

  5. On Linux or UNIX systems, you can remotely access a SQL Server database on Windows using a supplied wire protocol driver.
  6. Start of changeOn AIX, Oracle 10G Release 2 requires the AIX fix for APAR IY89080.End of change
  7. If you have installed Linux x86 (64-bit) Red Hat Enterprise Linux AS V4.0 and DB2 Version 8 FixPak 9, 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.
  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 or later; Solaris 10 on Solaris (x86-64 platform) requires DB2 Version 8 FixPak 11 or later.
  10. Start of changeYou can use the embedded Derby database for verification, evaluation, and test purposes only. (Derby refers to the database product based on the Apache Derby open source project from the Apache Software Foundation. For a production system, install and configure your chosen enterprise database.End of change
  11. 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
Configuring databases
Related reference
Database locations
Database contents
Datatype support
Supported processors
Operating system requirements
Additional software requirements
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:05

ah10030_ This topic's URL is: