Remove an additional host

Use this procedure to remove a host from the Grid. Before removing a host from the Grid, you should undeploy any applications running there. For more information on removing applications, see Administering Grid applications.

  1. In the file system of the host you are removing, navigate to the Grid uninstall folder. This is grid_root_installation_path\uninstall.
  2. On Windows, make sure the user running the uninstaller is part of the group named gridname_full.
  3. On Windows, using elevated rights, run as administrator and then run the file named uninstall.cmd.
  4. On Linux, run as root and then run uninstall.

Uninstall errors

One or more of the following errors may occur during the uninstallation:

  • DATABASE_FAIL - The uninstaller failed to connect to the database. Verify the connection details in the datasource.properties file located in grid_root_installation/config.

  • SCALED_OUT - The Grid is scaled out to additional hosts. Remove these hosts before uninstalling the primary host.

  • STOP_SERVICE_FAIL - The uninstaller could not stop the service/daemon. Stop the service/daemon manually, then run the uninstaller again.

    On Windows, the service is named: Infor ION Grid - gridname.

    On Linux, the daemon is named: grid_gridname.

  • STOP_GRID_FAIL - The uninstaller could not stop the grid host.

  • FILE_SYSTEM_LOCKED - Files or folders in the Grid install directory were locked, or the uninstaller did not have sufficient permissions. Close any locking processes and verify that the uninstaller has access to the files and folders.

  • REMOVE_SERVICE_FAIL - The uninstaller could not remove the service/daemon. Remove the service/daemon manually, then run the uninstaller again.

    On Windows, the service is named: Infor ION Grid - gridname.

    On Linux, the daemon is named: grid_gridname.

  • CLEAN_DATABASE_FAIL - The uninstaller could not clean up the database.

  • CLEAN_FILE_SYSTEM_FAIL - The uninstaller could not clean up the file system. If no other error occurred, you can manually delete the remaining files.

  • REMOVE_UNINSTALLER_FILES_FAIL - The uninstaller could not remove the uninstaller files. You can manually delete the remaining files.

Uninstaller flags

If you want to force the uninstallation to ignore a certain problem, you can pass one or more flags to the uninstaller. In the file system of the host you are removing, navigate to the grid uninstall folder. This is grid_root_installation_path\uninstall. Using elevated rights (run as administrator on Windows, root on Linux), run:

java -jar uninstall.jar flags -baseDir grid_root_installation_path

For example, if the database no longer exists, and you want to uninstall the grid, you can use:

java -jar uninstall.jar ignoreDBErrors -baseDir grid_root_installation_path

The flags you can use include:

  • archiveLogsInDatabase - Archive all log files on disk in the database.

  • forceClean - Remove uninstaller files even if errors occurred. You will not be able to rerun the uninstaller.

  • forceCleanIgnoreAll - Remove uninstaller files even if errors occurred and ignore all errors.

  • help - Show the available start options.

  • ignoreDBErrors - Ignore errors relating to database connections and cleanup. Use this if the database is unreachable.

  • ignoreLockedFileErrors - Ignore errors relating to locked files. Files might be left on disk after the uninstaller finishes.

  • ignoreScaleOutErrors - Ignore errors relating to scale out hosts. The whole grid will be deleted from the database. Scaled out hosts might have files left on disk.

  • ignoreServiceErrors - Ignore errors relating to the service/daemon. The service/daemon might not be removed.

  • ignoreStopGridErrors - Ignore errors relating to stopping the grid. Grid processes might be running, and the files on disk might not be deleted.

  • preserveLogFiles - Archive all log files on disk. The grid log files will be in a zip-file named gridname-grid-log-archive-timestamp.zip. The uninstaller log will be named uninstall-gridname.log. Both files will be located in the parent folder of the Grid install directory.