Page History

...

Database Table Usage

...

• In releases 1.11.0 and 1.11.1 the inventory data remain in the Reporting Database if a JobScheduler Master is uninstalled.
  Note that with releases 1.11.2 and newer inventory data is automatically deleted if a JobScheduler Master is uninstalled.

  Jira
  server SOS JIRA serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key SET-96

  
  
• If the JobScheduler ID or HTTP port are modified. This causes a new set of inventory data to be written and allows the obsolete inventory data set to remain in place.

...

• This script cleans all INVENTORY_* database tables  in the Reporting Database.
• It expects the database connection settings in ./config/reporting_hibernate.cfg.xml.

• Anchor
  instance instance

  This script has three arguments to identify a specific JobScheduler instance. These are
  
  • JobScheduler ID
  • Host
  • HTTP port
• With the single argument "remove".
  • This call determines the three parameters above automatically for the instance from which this script is started and cleans all INVENTORY_* database tables for this instance only.
    • This means that only the entry for this JobScheduler Master will be removed from the INVENTORY_INSTANCES table.
    • Additionally all entries from all other INVENTORY_* tables related to this JobScheduler Master instance will be removed also.
    • In case of a cluster, only the clustermember cluster member from which the script was started will be removed from the INVENTORY_* tables. Therefore consider to execute the script from the installation directory of each JobScheduler Master cluster member.
  • Be careful to Be carefull, make sure this instance is not running when executing this script with the single parameter "remove".
• With the single argument info a list of existing JobScheduler Master instances from the inventory will be displayed.
  • This call is helpful to see the exact values of SCHEDULER_ID, host and HTTP port.

• If this script is called without an argument then you get its usage clause:

  Code Block

  Usage: cleanup_inventory_tables.(cmd|sh) [JobSchedulerId JobSchedulerHost JobSchedulerHTTPPort] | [info] | [remove] JobSchedulerId | The Id, hostname and http port of a JobSchedulerHost | JobScheduler which data should be JobSchedulerHTTPPort | removed in the INVENTORY tables of the | reporting database. or info | Shows a list of existing JobScheduler | instances in the INVENTORY tables or remove | Determines the parameters automatically | for the instance in which the cleanup was | started and removes this instance from | the database. | CAUTION! Make sure beforehand | that this instance is not running!

• Example for an info output:

  Code Block
  JobSchedulerId | Host | Port --------------------------------------------------------------------------- scheduler.1.11-reporting | OH | 40413 scheduler.1.11-x86 | OH | 40186 SP_41110x1 | SP | 40119 scheduler.1.11 | OH | 40411 scheduler.1.11-reporting | OH | 40423 scheduler.1.11.1 | OH | 40471

...