Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Step 4. Create the ActiveVOS SchemaStep 4. Create the ActiveVOS Database

Step 4. Create the ActiveVOS Schema
Step 4. Create the ActiveVOS Database

To install ActiveVOS, you need to create the ActiveVOS schema. To create the schema, run the
create_bpm
script.
To install ActiveVOS, you need to create the ActiveVOS database. To create the database, run the
create_bpm
script.
If you want to create multiple MDM Hub Master Databases, create an ActiveVOS schema for each MDM Hub Master Database.
If you want to use the Oracle multitenant feature, create the ActiveVOS schema in a pluggable database (PDB).
If you want to create multiple MDM Hub Master Databases, create an ActiveVOS database for each MDM Hub Master Database.
  1. Open a command prompt and change to the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
  2. Run the following command:
    On UNIX.
    ./sip_ant.sh create_bpm
    On Windows.
    sip_ant.bat create_bpm
  3. Answer the prompts that appear.
    The prompt displays default text in brackets. Press
    Enter
    to use the default value and go to the next prompt.
    IBM DB2 data sources are case-sensitive. To avoid issues related to case-sensitivity, Informatica recommends that you use uppercase letters to define names, such as those for schemas, columns, and triggers.
    Property
    Description
    Database Type
    Type of database to use. For IBM DB2, specify
    DB2
    . The database type must be the same as the database type selected for the MDM Hub Master Database and the Operational Reference Stores.
    ActiveVOS Database Host Name
    Name of the machine that hosts the database.
    ActiveVOS Database TCP/IP Port
    Port number that the database listener uses.
    ActiveVOS Database Name
    Name of the database.
    ActiveVOS Database Schema/User Name
    User name of the ActiveVOS Server administrative user.
    ActiveVOS User Password
    Password of the administrative user.
    DBA User Name
    User name of the database administrative user.
    DBA Password
    Password of the administrative user.
    ActiveVOS Tablespace Name
    The name of the tablespace that contains the records that are involved in MDM workflows.
    Property
    Description
    Database Type
    The type of database. For an Oracle database, specify
    Oracle
    . The database type must be the same as the database type selected for the MDM Hub Master Database and the Operational Reference Stores.
    Oracle Connection Type
    Connection type. Use one of the following values:
    • SERVICE. Uses the service name to connect to Oracle.
    • SID. Uses the Oracle System ID to connect to Oracle.
    ActiveVOS Database Host Name
    Name of the machine that hosts the database.
    ActiveVOS Database Port
    Port number that the database listener uses.
    Database Service Name
    Name of the Oracle service. This property is required when the selected Oracle connection type is SERVICE.
    Oracle Net Connect Identifier (TNS Name)
    Oracle TNS name.
    Database SID
    Name of the Oracle System ID. This property is required when the selected Oracle connection type is SID.
    DBA User Name
    User name of the database administrative user.
    DBA Password
    Password of the administrative user.
    ActiveVOS User Name
    User name of the ActiveVOS Server administrative user.
    ActiveVOS User Password
    Password of the administrative user.
    ActiveVOS User Tablespace
    The name of the tablespace that contains the records that are involved in MDM workflows.
    ActiveVOS User Temp Tablespace
    The name of the temporary tablespace.
    Property
    Description
    Database Type
    Type of database to use. For Microsoft SQL Server, specify
    MSSQL
    . The database type must be the same as the database type selected for the MDM Hub Master Database and the Operational Reference Stores.
    ActiveVOS User Name
    User name of the ActiveVOS Server administrative user.
    ActiveVOS User Password
    Password of the administrative user.
    ActiveVOS Collation Name
    Name of the ActiveVOS database collation.
    For example,
    Latin1_General_CI_AS
    .
    ActiveVOS Database Host Name
    Name of the machine that hosts the database.
    ActiveVOS Database Path
    Path to the database location.
    DBA User Name
    User name of the SA user.
    DBA Password
    Password of the SA user account.
  4. After you create the schema, review the
    sip_ant.log
    file in the following directory:
    After you create the database, review the
    sip_ant.log
    file in the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
    The
    sip_ant.log
    file logs any errors that might occur when you run the
    sip_ant
    script to create the ActiveVOS database schema.

0 COMMENTS

We’d like to hear from you!