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.
- Configure the common properties of the
prpcUtils.propertiesfile.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.passwordDatabase 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. - Configure the index node properties of the
prpcUtils.propertiesfile.Property name Value indexing.indextypeSpecify one of the following: Rule: Index Rule- classesData: Index Data- classesWork: Index Work- classes
indexing.indexdirectoryPath to the directory in which to store the indexes. indexing.classesOptional: A comma-delimited list of classes to be included or excluded from indexing. This is used with the indexing.excludeproperty. If nothing is specified, then all classes of the specified type are included.indexing.excludeOptional: If indexing.classeshas been specified, do one of the following:-
To indicate that the classes are to be included in indexing, leave the
indexing.excludeproperty commented out. -
To indicate that the classes are to be excluded from indexing, uncomment the
indexing.excludeproperty.
indexing.messagesfrequencyOptional: The frequency (in seconds) at which indexing progress should be shown. The default is 10 seconds. - Save and close the
prpcUtils.propertiesfile. - Run the
prpcUtils.batorprpcUtils.shscript with the indexing option, for example:prpcUtils.bat indexingprpcUtils script argument Value connPropFileThe full path to the connection.propertiesfile 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, andscan.rulesSchemaThe rules schema. dataSchemaThe data schema. noFailOnErrorSet to trueorfalse. 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.
Previous topic Stopping or pausing search reindexing Next topic Reindexing a node in a cluster