Skip to main content

 –

Creating an SQL script by using a direct connection to the database

Suggest edit Updated on September 29, 2021

If a hotfix requires schema changes and you want to apply them manually, you can generate an SQL script by connecting to the database. This is most commonly done for a stopped instance. Your database administrator can use this script to manually apply the schema changes.

To generate an SQL script by connecting directly to the database, do the following steps.
  1. Configure the common properties of the prpcUtils.properties file.
    Property name Value
    pega.jdbc.driver.jarPath to the database driver .jar file.
    pega.jdbc.driver.classThe database driver class.
    pega.database.typeDatabase vendor type.
    pega.jdbc.urlURL of your database.
    pega.jdbc.usernameDatabase user name.
    pega.jdbc.password Database password.
    rules.schema.nameIf 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.
    data.schema.nameIf you use a split schema, the value for the data schema name.
  2. Configure the script properties of the prpcUtils.properties file.
    Property name Value
    hotfix.operation generateDDL
    hotfix.dlFilePath Comma-delimited list of hotfix package download (DL) file names and paths.
    hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system queues the job and returns a JobID to use to get the job status. A value of false executes the operation synchronously.
  3. Save and close the prpcUtils.properties file.
  4. Run the prpcUtils.bat or prpcUtils.sh script with the manageHotfixes option, for example: prpcUtils.bat manageHotfixes
  5. Optional: Pass one or more arguments.
    prpcUtils script argument Value
    connPropFileThe full path to the connection.properties file that includes information for multiple targets.
    driverClassYour JDBC driver class. For example, oracle.jdbc.OracleDriver.
    driverJARLocation of your JDBC .jar file.
    dbTypeDatabase vendor type, such as mssql, udb, oracledate, postgres, and db2zos.
    dbURLJDBC URL to the database.
    dbUserDatabase user name.
    dbPasswordDatabase password.
    archivePathFull path to the archive to be imported or exported.
    propFileThe full path to the properties file, to override the default prpcUtils.properties.
    hfixActionIf manageHotfixes is selected, sets the hotfix operation. Valid values are commit, rollback, generateDDL, install, and scan.
    rulesSchemaThe rules schema.
    dataSchemaThe data schema.
    noFailOnErrorSet to true or false. When enabled, instances that fail to import are skipped and import continues instead of failing.
    UPega user name.
    PPega password.
    accessGroupAccessGroup in which the Rule-Declare-Index of the classes being exposed exists. Applicable for the expose utility if --U or --P are not provided.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us