Forcing a reset of global search

Applies to:

In some rare cases, it might be necessary to reset the IBM OpenPages® global search component if you cannot restore it from the Global Search administration page. These issues might prevent you from successfully completing tasks in the global search administration page. To resolve these issues, complete the following steps.

Procedure

If you started a global search indexing process from the OpenPages user interface, click System Configuration > Global Search. Make a note of the Id of the indexing process. You need the Id in step 9.
Log on to the search server as a user with administrative privileges.
Open a command line on the search server.
Go to the <SEARCH_HOME>/opsearchtools/ directory to run the commands in the following steps.

Attention: At the successful completion of each command, the statement Normal completion of command should appear. If it does not, contact Customer Support to diagnose the issue.
Ensure that Solr is running and is reachable on port 8983. If Solr is not running, then run the following command to start it.
Microsoft Windows:
```
opsearchtool.cmd startSolr
```
Linux®:
```
./opsearchtool.sh startSolr
```

Run the following commands to stop indexing.

Microsoft Windows:

opsearchtool.cmd stopIndexing -indexname openpages
opsearchtool.cmd stopIndexing -indexname folderacl

Linux:

./opsearchtool.sh stopIndexing -indexname openpages
./opsearchtool.sh stopIndexing -indexname folderacl

Verify that no opsearchtool.jar processes are running.

On Microsoft Windows operating systems, use the task manager to see whether any opsearchtool.jar processes are running. If there are, terminate them.

On Linux operating systems, use the ps command to see whether any opsearchtool.jar processes are running. If there are, terminate them.

Run the following commands to clear any PID states that might still be set if the opsearchtool.jar processes did not end successfully.

Microsoft Windows:

opsearchtool.cmd clearState -indexname openpages
opsearchtool.cmd clearState -indexname folderacl

Linux:

./opsearchtool.sh clearState -indexname openpages
./opsearchtool.sh clearState -indexname folderacl

If a global search indexing process was started from the OpenPages user interface, run the following commands:

Replace %lrpf-pid% with the Id of the indexing process.

Microsoft Windows:

opsearchtool.cmd syncIndex -terminatepid %lrpf-pid%
opsearchtool.cmd fullIndex -indexname openpages -terminatepid %lrpf-pid%
opsearchtool.cmd fullIndex -indexname folderacl -terminatepid %lrpf-pid%

Linux:

./opsearchtool.sh syncIndex -terminatepid %lrpf-pid%
./opsearchtool.sh fullIndex -indexname openpages -terminatepid %lrpf-pid%
./opsearchtool.sh fullIndex -indexname folderacl -terminatepid %lrpf-pid%

Run the following commands to reset global search.

Microsoft Windows:

opsearchtool.cmd resetSolr -indexname openpages
opsearchtool.cmd resetSolr -indexname folderacl
opsearchtool.cmd resetDb
opsearchtool.cmd stopSolr
opsearchtool.cmd startSolr

Linux:

./opsearchtool.sh resetSolr -indexname openpages
./opsearchtool.sh resetSolr -indexname folderacl
./opsearchtool.sh resetDb
./opsearchtool.sh stopSolr
./opsearchtool.sh startSolr

Log on to OpenPages as a user with administrative privileges.
Click Open Administration menu > System Configuration > Global Search and click Create.
Create appears only on initial enablement.
Creating the index also enables global search.

What to do next

Resetting the global search component does not change your global search settings, such as object types, fields that are enabled for search, registry settings, or property settings.