Rebuilding search indexes by using a direct connection to the database

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 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 index node properties of the 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 file.
  4. Run the prpcUtils.bat or script with the indexing option, for example:
    prpcUtils.bat indexing
    prpcUtils script argument Value
    connPropFile The full path to the file that includes information for multiple targets.
    driverClass Your JDBC driver class (example: oracle.jdbc.OracleDriver).
    driverJAR Location of your JDBC .jar file.
    dbType Database vendor type (mssql, udb, oracledate, postgres, 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.