In the event that the look-aside indexes do not get rebuilt or are not synchronized correctly, you can use the ProfilesService.rebuildLookAsideIndexes()
command to explicitly rebuild them.
Before you begin
To run administrative commands, you must use the wsadmin client. See Starting the wsadmin client
for information about how to start the wsadmin command-line tool.
About this task
In a clean database population, the indexes are built as the data is populated and there is no need to use the ProfilesService.rebuildLookAsideIndexes()
command. Similarly, when you migrate a database from one version of IBM
Connections to another, the system is designed to detect that the look-aside indexes need to be built and update those tables automatically.
However, in situations in which the look-aside index data does not get rebuilt or is out of synchronization for some reason, the ProfilesService.rebuildLookAsideIndexes()
command allows you to explicitly rebuild the look-aside indexes. Consider using this command if name-search does not work after upgrading to a newer version of IBM
To rebuild the look-aside indexes, complete the following steps:
Parent topic: Resolving a problem
Synchronizing the application member tables and corporate directory
- Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager:
is the WebSphere
® Application Server installation directory and <dm_profile_root>
is the Deployment Manager profile directory, typically dmgr01.
You must start the client from this directory or subsequent commands that you enter do not execute correctly. For more information, see Starting the wsadmin client
- Start the Profiles Jython script interpreter.
- Use the following command to access the Profiles configuration files:
If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
- Use the following command:
Creates a background process that runs through the Profiles database and corrects any issues. The command does not take any parameters.
When you run the command, a message is logged to record that the process has started and, after every block of 5000 users has been processed, a check-up message indicates the number of users that have been successfully updated or flags errors in that block of users.
At the end of the process, a message containing information about the total number of users updated, the number of users successfully updated, and the number of users with errors, is logged. The logs contain the UIDs of the users who could not be successfully updated as well as any error messages.
The logs are output to the SystemOut.log file of the IBM WebSphere Application Server node that the MBean connected to. Typically this is the first node defined in the Profiles cluster.