Delete the SQL PI repository agents
1). From the database "Administration" page, disable the PI extension of database agents
Note: In case you do not know all the agents names, you can choose all agents in the "Global View" and once you enter to the SQL PI admin dashboard select the relevant FglAM with its database agents.
2). Navigate to Administration | Agents | Agent Status and deactivate the SPI agent (SPIRepository-...), then delete the agent.
3). Deactivate the DBSS-SPI agent (DBSS-SPIRepository-i…) and DBO-SPI agent (DBSS-SPIRepository-i…) from the Agent Manager and then delete the agent.
Shut down / Stop the Infobright PI repository
For Linux
- Remotely connect into to the PI repository host
- Browse to the "Infobright" installation folder (by default it is located next to the FglAM installation folder)
- Edit the "Infobright-Stop.ksh" file and add "–m fast" flag to the command line after "pg_data -s -m fast", then save the file.
- Stop all Infobright processes by running the "infobright_stop.ksh" file * This is the recommended process to shut down the PI repository. Please give this one to two minutes to complete *
- If there are still remaining Infobright processes, open the “postmaster.pid” file under the "pg_data" folder.
- Identify the pid number listed in the first line of the file. This corresponds to the parent infobright process.
- Kill the parent pid process "kill -9" pid (where pid is the parent process number from step 9)
- Run the following command to kill the remaining processes "ps -ef | grep 'postgres\|ibengine\|bhloader' | grep -v grep | awk '{print $2}' | xargs kill -9"
Please note that this step will kill and Foglight Management Server (FMS) repository processes where a PI repository is installed on the same server as an embedded Postgresql FMS repository. In these situations it is recommended to shut down the FMS and FMS repository, then run this command and then restart the FMS again. - Run the following command to check for remaining processes "ps -ef | grep 'postgres\|ibengine\|bhloader' "
- This is optional only if SQL PI does not start up, customer can rename or delete postmaster.pid from infrobright/pg_data after ensuring 'postgres\|ibengine\|bhloader' processes are all stopped. This creates a new postmaster.pid with a new PID number after restarting "infobright"Infobright-Start.ksh" from the Infobright folder. The next option is to restart the FglAM host in case there is SQL PI ghost PID captured in the cache, this is only if SQL PI does not link to the Db agents.
For Windows
- Remotely connect into to the PI repository host
- Browse to the Infobright installation folder (By default it is located next to the FglAM installation folder):
- Edit the "Infobright-Stop.bat" file and add "–m fast" flag to the command line, then save the file. * This is the recommended shutdown process. Please give this a minute or two to complete. *
- Stop all Infobright processes by running the "Infobright_stop.bat" file (on some environments this needs to be run as Administrator)
- If there are still remaining Infobright processes, then kill the main postgres process.
* The process pid is the first number in the “postmaster.pid” file under the "pg_data" folder. Locate it in the task manager and kill the entire process tree:
- After this action all PI repository related processes should be killed. If the “ibengine.exe” is still running, then Infobright was not stopped. This can be done by killing all “postgres.exe” processes manually.
Note: If the Foglight repository is running on the same host, it also runs “postgres.exe” processes, so they will be killed as well and the repository will have to be restarted.
If there are still “bhloader.exe” or “ibengine.exe” processes, kill them manually.
Remove the Infobright Repository folder
If the Infobright PI repository is no longer required, the Infobright folder can be deleted from the PI repository server used by Foglight.