Installer 10.7 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Migrate Database Components | Migrate Database Components Using Database Component Configurator
 
Migrate Database Components Using Database Component Configurator
On the machine on which you installed the new Database Configuration, open a command window or shell, go to the new_Software AG_directory/common/db/bin directory, and migrate database components by running the command below.
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}
{-c db_component | -pr product} -v latest -l db_server_URL
-u existing_db_user -p password
Database scripts are executed as sections, with each section concluding with a commit to the database. If a migrate action fails (for example, because of a network outage, an expired connection, or invalid credentials), the failed section will not have been committed, and therefore can safely be re-attempted. To do so, re-enter the failed command and add the --resume option. You must specify the same values for all parameters except the credential parameters, which can be different if necessary.
After you run each command, check the log file log_yyyymmddhhmmss in the new_Software AG_directory/common/db/logs directory.
If you are using an Oracle or DB2 RDBMS, and you are not using the default tablespace, also specify the -tsdata data_tspace_name and -tsindex index_tspace_name parameters.
On a UNIX or Linux system, enclose the values “ db_server_URL ”, ” existing_db_user ”, and “ password ” in quotation marks.
If you are using Optimize with a DB2 RDBMS, there are special considerations for the URL you specify on the database component migration command. You must do the following:
*Specify the schema name in the URL using all capital letters.
*Specify the options CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000. These settings will affect all database components in the same schema or database.
If you are upgrading...
Values for product...
ActiveTransfer Server
-c {ActiveTransfer|ActiveTransferArchive}
API Gateway
-c APIGatewayEvents
Archive database component (used to archive ISCoreAudit and ProcessAudit data)
-c Archive
Integration Server
-c {ISInternal|ISCoreAudit|CrossReference|
DocumentHistory|DistributedLocking}
If the listed database components are in the same schema, you can specify the following instead:
-pr IS
Note:
Migrate the Integration Server database components before migrating other database components.
Microservices Runtime
-c {ISInternal|ISCoreAudit|CrossReference|
DocumentHistory|DistributedLocking}
If the listed database components are in the same schema, you can specify the following instead:
-pr MSR
Note:
Migrate the Microservices Runtime database components before migrating other database components.
My webMethods Server
-c {MywebMethodsServer}
Or:
-pr MWS
Note:
The CentralConfiguration database component is automatically migrated.
OneData
-c {OneDataMetadata|OneDataReleaseArea|OneDataWorkArea}
Optimize
-c {Analysis|ProcessTracker|ProcessAudit|DataPurge|DatabaseManagement}
If the listed database components are in the same schema, you can specify the following instead:
-pr OPTI
Note:
The OperationManagement database component is automatically migrated.
Process Engine
These database components contain business process run time data for in-progress, completed, or failed business process instances. Migrate these database components if you want to finish running in-progress process instances or resubmit completed or failed process instances from your old installation in your new installation.
-c {ProcessEngine|ProcessAudit}
If the listed database components are in the same schema, you can specify the following instead:
-pr PRE
Rules Engine
-c BusinessRules
Reporting and Staging database components (used to simulate business processes)
-c {Reporting|Staging}
Trading Networks
-c {TradingNetworks|TradingNetworksArchive}
If the listed database components are in the same schema, you can specify the following instead:
-pr TN