Database size grows unexpectedly after upgrade to version 5.6.11 (4242089)

1. Stop the FMS service
     
2. Navigate to $FMS_HOME/config and backup the storage-parameters.config to another folder outside of this installation.  Edit the attached storage-parameters.config and replace the tablespace clause below depending on your configuration as per your storage-parameters.config file (adding the OVERFLOW parameter):
     
   If using a custom tablespace for LOB data, search for the "FG_LOB" section and replace with the actual custom tablespace name:
     
   
   ... STORAGE (NEXT 10M MAXEXTENTS UNLIMITED) OVERFLOW TABLESPACE FG_LOB",
   .... STORAGE (NEXT 10M MAXEXTENTS UNLIMITED) OVERFLOW TABLESPACE FG_LOB",
     
   If you are not using a custom tablespace for LOB data, delete the "TABLESPACE FG_LOB":
     
   
    "obs_string-iot" : ... STORAGE (NEXT 10M MAXEXTENTS UNLIMITED) OVERFLOW",
   "obs_binary-iot" :.... STORAGE (NEXT 10M MAXEXTENTS UNLIMITED) OVERFLOW",
   
   Replace the file with the updated storage-parameters.config.
     
3. Start the FMS service
     
4. Edit the attached add-lob-overflow.groovy and replace the "FG_LOB" value under the LOB_TABLESPACE parameter with the actual custom tablespace that you are using for LOB.  
     
   String LOB_TABLESPACE = "FG_LOB";
   
   If you are not using a custom tablespace, set it to null as follows:
     
   String LOB_TABLESPACE = null;
     
   Go to the /bin directory and place the add-lob-overflow.groovy file and run as follows from command prompt.  
   NOTE:  This example uses port 8080, be sure to provide your actual FMS port number.
     
   fglcmd -srv fms_host -port 8080 -usr foglight -pwd foglight -cmd script:run -f add-lob-overflow.groovy > add-lob-overflow.log
     
   This may take some time and just leave it running until it completes.
    

Note: IF upgrading to v5.6.11, it is recommended that you add the OVERFLOW parameter before you restart the FMS; the script only reports tables that have been created recently, because it only operates on index-organized tables, and Foglight didn't use any such tables before 5.6.11.

5. Open the add-lob-overflow.log and ensure that there are no errors inside.  If there are no errors, edit the add-lob-overflow.groovy script
  -set the parameter addOverflow = true 
  -leave the parameter moveLobsLater = false
  -leave the parameter continueonError = true 
  -save the file as add-lob-overflow-true.groovy.

Run the cmd referencing your actual FMS port number.
  
fglcmd -srv fms_host -port 8080 -usr foglight -pwd foglight -cmd script:run -f add-lob-overflow-true.groovy > add-lob-overflow-true.log 
  
This may take a while and ensure it completes successfully.

If there are errors, the script will generate a SQL script for which the DBA will need to run while the FMS is offline to resolve the issue.
  

Monitor the FMS for a few days and see if the LOB tablespace or the entire repository database size has decreased.  If the issue persists, contact Quest Support to reference INTERNAL KB Article 127033 for more troubleshooting tips.