If you have moved your metadata repository database to
a new host, and the database contains schemas other than the metadata
repository and staging area, such as the operations database, then
you must register these schemas again with the new metadata repository
on the new host. If the metadata repository database contains only
the metadata repository and staging area schemas, you do not need
to complete this task.
- On the services tier computer, list the data
stores that are currently registered.
cd is_install_path\ASBServer\bin
RepositoryAdmin.bat -listRepositories
DSODB
QSSRDDB
ESDB
- Create a properties file for each of the data stores that
exist as schemas within the metadata repository database.
If
you are not sure which data stores are registered to the metadata
repository database, create a properties file for each of the data
stores using the
-displayRepository command as
shown below for each data store listed in step
1. Examine the
Database.name
property
to determine which data stores are schemas in the metadata repository
database. Notice that they are still currently registered with the
metadata repository database on the old host. The old host name is
the information that you will change and register in the new metadata
repository. If you find other data stores that are not in the metadata
repository database that also show the old host name in the
DatabaseServer.host
property,
these will need to be registered again as well. For further details
on reregistering these data stores, see
Relocating repositories examples.
For this example, assume that the operations database (named
DSODB) exists in the metadata repository database, but the exceptions
database (named ESDB) and the InfoSphere QualityStage Standardization
Rules Designer (named QSSRDB) exist in their own databases that have
not been moved. Therefore, you must create a properties file for the
operations database named DSODB.
RepositoryAdmin.bat -displayRepository -rn DSODB -res dsodb.properties
Example
output of a properties file:
DatabasePlatform.databaseType=DB2
DatabasePlatform.version=10.5
DatabaseServer.host=server1
DatabaseServer.port=50000
Database.name=XMETA
Database.alias=XMETA
Database.location=C:\
Repository.name=DSODB
Repository.description=Operations Database.
Repository.tool=DataStage
Repository.context=operations
Repository.schema=DSODB
RepositoryConnection.userName=DSODB
RepositoryConnection.password={iisenc}gwFQseoj24I/SnCFEH+cWg==
RepositoryConnection.connectionURL=jdbc:db2://server1:50000/XMETA
- Unregister the metadata repository database.
This action will also unregister each of the data stores in the database
(except for the staging area and metadata repository itself, which
are not registered in this manner).
In this example, DSODB is the only one that would be unregistered with the
database.
RepositoryAdmin.bat -unregisterDatabase -dn XMETA
- Edit each of the properties files, changing the old metadata
repository database host name to the new one.
In this
example, there is only the properties file for DSODB. If the database
is not configured for high availability, remove the connection URL
property. The tool can derive the URL from other properties in the
file.
DatabasePlatform.databaseType=DB2
DatabasePlatform.version=10.5
DatabaseServer.host=server2
DatabaseServer.port=50000
Database.name=XMETA
Database.alias=XMETA
Database.location=C:\
Repository.name=DSODB
Repository.description=Operations Database.
Repository.tool=DataStage
Repository.context=operations
Repository.schema=DSODB
RepositoryConnection.userName=DSODB
RepositoryConnection.password={iisenc}gwFQseoj24I/SnCFEH+cWg==
- Register each of the data stores that you unregistered,
using the respective edited properties files that contain new host
information. This will automatically register the new metadata repository
database and the database server.
In this example, the
operations database named DSODB is the only data store being registered.
RepositoryAdmin.bat -registerRepository -pf dsodb.properties
- The operations database and exceptions databases require
connection files to connect to the engine. If one or both of these
database schemas are in your newly moved metadata repository database,
log into each engine tier computer and create the connection file
for the database schema.