Supported databases

A broker requires access to a database to store operational and state data. Databases from IBM and other suppliers are supported at specific versions on supported operating systems.

You must create the broker 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.

Start of changeYou can use the same database schema for all brokers that are at the same version, if appropriate, even if you create the brokers on different computers. The broker tables are created in a schema that is determined by the user ID that you specify for the broker database connection, and the rows within the tables are qualified by a unique identifier (UUID) for each broker. The schema user ID is set by -u dataSourceUserId (if you specified this parameter on the mqsicreatebroker or mqsichangebroker command), or by -i serviceUserId (if you did not specify the -u parameter).End of change

You can also create user databases to be accessed from message flows; database support is the same as that defined for brokers except where specifically stated. Some data types supported by these databases are not supported by WebSphere Message Broker; for details, see Data types of values from external sources.

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.

The following table, and the accompanying notes, indicate the minimum levels of products that are supported for databases on each operating system. For the latest information on all supported platforms, visit the WebSphere Message Broker Requirements Web site.

Operating system DB2®1+2 Microsoft® SQL Server1 Oracle1+3 Sybase1 Informix®1+4
AIX®

8.25
9.15+6

2000 SP3a7

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

10g Release 1
10g Release 28

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC4 fix pack

HP-UX on Itanium

8.25
9.15+6

Not supported

10g Release 2

Not supported Not supported
HP-UX on PA-RISC

8.25
9.15+6+9

2000 SP3a7

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

10g Release 1
10g Release 28

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with HC4 fix pack

Linux® on POWER™10

8.25
9.15+6

Not supported Not supported Not supported Not supported
Linux on x86

8.25+11
9.15+6+11

2000 SP3a6

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

10g Release 1
10g Release 28

12.5

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90
with UC3 fix pack

Linux on System z®

8.25+12
9.15+6+12

Not supported Not supported Not supported Not supported
Start of changei5/OS® and OS/400®13End of change Start of change

V5R2
V5R35

End of change
Not supported Not supported Not supported Not supported
Solaris on SPARC

8.25+14
9.15+6

2000 SP3a6

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

10g Release 1
10g Release 28

12.5.3

Dynamic Server V9.4
with UC7 fix pack

Client SDK V2.90 with
UC4 fix pack

Solaris on x86-64

8.24+14
9.14+5

Not supported

10g Release 1

Not supported Not supported
Windows®

8.25+15
9.15+6

2000 SP3a

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

10g Release 116
10g Release 28

12.5

Dynamic Server V9.4
with TC7 fix pack

Client SDK V2.90
with TC4 fix pack

z/OS®

7.117
8.117

Not supported Not supported Not supported Not supported
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 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 Fix Pack 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. Start of changeAutomatic Client Reroute for DB2 is supported on all platforms except Solaris on SPARC and Windows.End of change
  3. Both the Oracle Database Server and the Oracle Runtime Client are required.
  4. Informix is supported only as a user database accessed by message flows; you cannot create a broker database as an Informix database.

    Each broker system requires only the client SDK; install the Dynamic Server on the system on which you create databases.

    Support is not provided for 64-bit databases or XA coordination. Informix uses two types of large objects (LOBs); simple and smart. Simple LOBs are data types TEXT and BYTE, and they are supported. Smart LOBs are data types CLOB and BLOB, and they are unsupported.

  5. 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 Fix Pack 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.

  6. DB2 Version 9.1 requires WebSphere MQ Version 6.0.2.0 or later.
  7. You can use a remote SQL Server database on Windows from a Linux or UNIX® system using a supplied wire protocol driver.
  8. Start of changeThe Connect-Time Failover feature of Oracle RAC (Real Application Clusters) in a non-XA environment only is supported.End of change
  9. If you use DB2 Version 9.1 on HP-UX on PA-RISC, you must set the following environment variable, and export it in the broker's environment:
    MQSI_SIGNAL_EXCLUSIONS=10
  10. On Linux on POWER, XA coordination is restricted to 32-bit brokers only.
  11. Start of changeIf you have installed Linux x86 (64-bit) Red Hat Enterprise Linux V4.0 or V5.0:
    • If you have installed DB2 Version 8 Fix Pack 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.

      If you have installed Oracle, you must use the 32-bit client libraries.

    • XA is supported only if you use WebSphere MQ Version 6.0 (32-bit).

      If you do not require XA, you can install WebSphere MQ Version 6.0 (64-bit). XA is not supported because the 64-bit queue manager requires 64-bit ODBC drivers and switch files, which are not supplied.

    End of change
  12. If you have installed Linux zSeries® (64-bit) Red Hat Enterprise Linux V4.0, and you install a 31-bit DB2 Runtime Client, the client must be at DB2 Version 8 Fix Pack 10 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.
  13. Start of changeYou can configure message flows to access DB2 databases on i5/OS and OS/400 for user data. The message flows can run on any supported broker platform. You cannot create a broker database as a remote DB2 database on i5/OS or OS/400 from any broker platform. For further details of these restrictions, and for information about the PTFs that are required with DB2 on these operating systems, see Database locations.End of change
  14. Solaris 10 on Solaris on SPARC requires DB2 Version 8 Fix Pack 9 or later; Solaris 10 on Solaris on x86-64 requires DB2 Version 8 Fix Pack 11 or later.
  15. You 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.
  16. For XA coordination with Oracle 10g on Windows, you must install Patch Set 3 for Oracle 10g (10.1.0.4.0).
  17. 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 broker and user databases
Related reference
Database locations
Database contents
Data types of values from external sources
Supported processors
Operating system requirements
Additional software requirements
Related information
WebSphere Message Broker Requirements
DB2 V9.1 information center (distributed systems)
DB2 V8 information center (distributed systems)
DB2 information center (z/OS)
DB2 V7 library (z/OS)
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:59

ah10030_