Changing configuration of databases and data stores

You might need to change the configuration of databases and data stores that are used to run InfoSphere® Information Server or its components. This might be required for a variety of reasons; for example, a change in the physical computer that hosts the data store, a change in host name or port number of the computer that hosts the data store, a change to the high-availability configuration, or a password change.

Some data stores might be deployed as separate schemas within the same database. This is always the case with the active metadata repository and the staging area. Other data stores can also be created as schemas in this same database or they can be created in their own separate database. Such a separate database can also hold multiple data stores.

If the configuration is changed for one of the data stores that is in a shared database, then some configuration details for the other data stores that are schemas within that shared database must also be changed. If any of the following changes are made to a database connection, the configuration for the data stores that use the connection information must be updated:

host name
port number
whether it is a regular or high-availability configuration

Passwords are an exception and are unique for each schema in a shared database.

The following table lists the internal data stores and databases that are used by InfoSphere Information Server and its components, including links to reconfiguration instructions for each.

Table 1. Reconfiguring internal data stores and databases used by InfoSphere Information Server
Repository or database	Description	Default database and schema	Reconfiguration instructions
Active InfoSphere Information Server metadata repository	Stores the metadata about external data sources that are governed, managed, and analyzed by InfoSphere Information Server components. Normally referred to as the metadata repository.	Database: XMETA Schema: XMETA Database must be the same database that is used for the staging metadata repository.	Follow these instructions if you are moving the active metadata repository to a new computer or changing the host name and port: Changing the metadata repository database host name and port Follow these instructions to configure for high-availability: Metadata repository tier clustering for high availability Follow these instructions to change database passwords: Metadata repository database and staging area repository owner password changing
InfoSphere Information Server staging area	Stores metadata that is imported from external data sources so that it can be examined before it is moved to the active metadata repository.	Database: XMETA Schema: XMETASR Database must be the same database that is used for the active metadata repository.	Follow these instructions if you are moving the staging area to a new computer or changing the host name and port: Changing the metadata repository database host name and port Follow these instructions to configure for high-availability: Metadata repository tier clustering for high availability. Follow these instructions to change the database password: Metadata repository database and staging area owner password changing
analysis database	Stores results of information analyis by InfoSphere Information Analyzer.	Database: IADB Schema: IAUSER Database cannot be the same database that is used for the active metadata repository or staging area.	Follow these instructions if you are moving the analysis database to a new computer: Relocating an analysis database to a new location Follow these instructions to change the database password: Changing the analysis database owner account credentials
operations database	Stores monitoring data that is displayed by the InfoSphere DataStage® and QualityStage® Operations Console.	Database: XMETA Schema: User-defined repository user name, typically DSODB Database can be the same or different as the database that is used for the metadata repository.	Follow these instructions if you are moving the data store to a new computer: Relocating the operations database Follow these instructions if you are changing the host name of the server that hosts the database for the data store: Changing host name configuration for data stores Follow these instructions to reconfigure for high-availability: Changing configuration of other databases to high availability. Follow these instructions to change the database password: Changing the user password for the operations database
Standardization Rules Designer database Important: IBM InfoSphere QualityStage Standardization Rules Designer will not be supported after 31 December 2020. No replacement is planned.	Stores a copy of revisions to InfoSphere QualityStage rule sets that have been made in the IBM InfoSphere QualityStage Standardization Rules Designer .	Database: XMETA Schema: User-defined data store user name, typically SRDUSER Database can be the same or different as the database that is used for the metadata repository.	Follow these instructions if you are moving the data store to a new computer: Relocating the Standardization Rules Designer database Follow these instructions if you are changing the host name of the server that hosts the database for the data store: Changing host name configuration for data stores Follow these instructions to reconfigure for high-availability: Changing configuration of other databases to high availability. Follow these instructions to change the password in the connection configuration after you have changed the database password: Example: Changing connection properties
Exceptions database	Stores exceptions that are generated by InfoSphere Information Server products and components.	Database: XMETA Schema: User-defined repository user name, typically ESDB Database can be the same or different as the database that is used for the metadata repository.	Follow these instructions if you are moving the data store to a new computer: Relocating the exceptions database Follow these instructions if you are changing the host name of the server that hosts the database for the data store: Changing host name configuration for data stores Follow these instructions to reconfigure for high-availability: Changing configuration of other databases to high availability To change the password in the connection configuration after you have changed the database password, follow the instructions in the following topic, but substitute the correct parameters for your exceptions database repository: ../../com.ibm.swg.im.iis.esdb.admin.doc/topics/t_exception_chgpasswd.html.
Match Designer database	Stores the results of match test passes by InfoSphere QualityStage Match Designer, a component of InfoSphere QualityStage. This data store is an ODBC data source that is used as a staging area before match designs are checked in to the active metadata repository.	User-defined database name and schema name. No default, but typically MDDB. Database cannot be the same database as that used for the metadata repository.	To change the configuration, you must redefine the DSNs (data source names) of the data source on the client and engine tier computers. Configuring IBM InfoSphere QualityStage Match Designer Updating Match Designer configuration information