Supported databases

The product requires a configuration repository accessed by the Configuration Manager and a broker database accessed by each broker. Multiple brokers can access the same database, if appropriate, because all tables are qualified by the broker name. You can also configure message flows to access user databases.

Start of changeThe broker tables are created when you invoke the mqsicreatebroker command. The configuration repository tables are created when you invoke the mqsicreateconfigmgr command. The tables that are created in each database are listed in Database contents.End of change

The following table indicates which levels of database are supported on which operating systems. In most situations, the component 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 DB21,2 Microsoft SQL Server Oracle1 Sybase1

AIX

7.23
8.13

Not applicable

9i Rel 24

12.53

HP-UX

7.23
8.13,5

Not applicable

9i Rel 24

12.53

Linux

7.23
8.13

Not applicable

Not applicable

Not applicable

Solaris

7.23
8.13

Not applicable

9i Rel 24

12.5

Windows 2000
Professional,
Server and
Advanced Server
Windows XP
Professional

7.23
8.13

2000 SP3

9i Rel 24

12.5

Windows Server 2003

8.13

2000 SP3a

9i Rel 23,4,6

Not supported

z/OS

7.17

Not applicable

Not supported

Not applicable

OS/400®8

V5R1
V5R2

Not applicable

Not applicable

Not applicable

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 Business Integration Message Broker, this is referred to as supporting a globally coordinated message flow. On z/OS, all transactions are coordinated by RRS.
  2. You must use DB2 for the configuration repository maintained by the Configuration Manager. No other database is supported for this purpose. If you also use DB2 for your broker database, you can configure the same database for the configuration repository and the broker.
  3. Please check the readme.html file for your product to check if a FixPak or other fix is required.
  4. Oracle Patch Set 3 (3095277) is recommended to avoid potential stress problems. This does not apply to Windows XP.
  5. HP-UX 11.0 does not support DB2 8.1.
  6. Oracle Patch Set 2 (2761332) is required.
  7. PTFs are required with this product. See the WebSphere Business Integration Message Broker for z/OS Program Directory for further details.
  8. You can configure OS/400 databases for remote user database access only. For further details of these restrictions, and for information about the PTFs that are required with this product, see Database locations.

Related tasks
Finding the latest information
Checking the operating environment
Checking software prerequisites

Related reference
Supported operating environments
Database locations
Database contents