Skip to main content

Rebuilding search indexes by using a direct connection to the database

Suggest edit
Updated on August 25, 2021

You can rebuild search indexes if they become corrupted or if they were accidentally deleted. To rebuild a search index by using a direct connection to the database, complete 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 index node properties of the prpcUtils.properties file.

    Property name Value
    indexing.indextype Specify one of the following:
    • Rule : Index Rule- classes
    • Data : Index Data- classes
    • Work : Index Work- classes
    indexing.indexdirectory Path to the directory in which to store the indexes.
    indexing.classes Optional: A comma-delimited list of classes to be included or excluded from indexing. This is used with the indexing.exclude property. If nothing is specified, then all classes of the specified type are included.
    indexing.exclude Optional: If indexing.classes has been specified, do one of the following:
    • To indicate that the classes are to be included in indexing, leave the indexing.exclude property commented out.
    • To indicate that the classes are to be excluded from indexing, uncomment the indexing.exclude property.
    indexing.messagesfrequency Optional: The frequency (in seconds) at which indexing progress should be shown. The default is 10 seconds.

  3. Save and close the prpcUtils.properties file.
  4. Run the prpcUtils.bat or prpcUtils.sh script with the indexing option, for example:
    prpcUtils.bat indexing

    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 Support Center to ask questions, engage in discussions, share ideas, and help others.

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