Table of Contents

Committing hotfixes by using a direct connection to the database


Only available versions of this content are shown in the dropdown

Commit all uncommitted hotfixes to make the hotfixes a permanent part of the system by using a direct connection to the database. This is most commonly done for a stopped instance.

To connect directly to the database to commit hotfixes, do the following steps.

You cannot roll back committed hotfixes.
  1. Configure the common properties of the file.

    Property name Value
    pega.jdbc.driver.jar Path to the database driver .jar file.
    pega.jdbc.driver.class The database driver class.
    pega.database.type Database vendor type.
    pega.jdbc.url URL of your database.
    pega.jdbc.username Database user name.
    pega.jdbc.password Database password. If you use a split schema, the value for the rules schema name. If you do not use a split schema, the value for the schema name. If you use a split schema, the value for the data schema name.
  2. Configure the commit properties of the file.

    Property name Value
    hotfix.operation commit
  3. Save and close the file.

  4. Run the prpcUtils.bat or script with the manageHotfixes option, for example: prpcUtils.bat manageHotfixes

  5. Optional: Pass one or more arguments.

    prpcUtils script argument Value
    connPropFile The full path to the file that includes information for multiple targets.
    driverClass Your JDBC driver class. For example, oracle.jdbc.OracleDriver.
    driverJAR Location of your JDBC .jar file.
    dbType Database vendor type, such as mssql, udb, oracledate, postgres, and db2zos.
    dbURL JDBC URL to the database.
    dbUser Database user name.
    dbPassword Database password.
    archivePath Full path to the archive to be imported or exported.
    propFile The full path to the properties file, to override the default
    hfixAction If manageHotfixes is selected, sets the hotfix operation. Valid values are commit, rollback, generateDDL, install, and scan.
    rulesSchema The rules schema.
    dataSchema The data schema.
    noFailOnError Set to true or false. When enabled, instances that fail to import are skipped and import continues instead of failing.
    U Pega user name.
    P Pega password.
    accessGroup AccessGroup in which the Rule-Declare-Index of the classes being exposed exists. Applicable for the expose utility if --U or --P are not provided.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.