zhaoxq-ibm
commented
11 months ago I don't suggest to increase ve.cache.timeout, because it's going to eat up memory, and finally sql tuning service will crush because of out of memory. Instead, remember the jobID returned after you issue /tuningservice/v1/ve API, issue /tuningservice/v1/jobs/xx/result API to get a fresh URL everytime you need to view Visual Explain.
Currently, visual explain can only be exported to an image.
Description of the feature or enhancement
We're have created a process/script that will generated a visual explain using the swagger endpoint (/tuningservice/v1/ve & /tuningservice/v1/jobs/xx/result) It returns a formated sql & a url to the visual explain for all the queries you give as input.
We would like to build upon this process and see to incorporate it in testing or go live scenario's where based a certain criteria, these actions are performed for the queries. This report could then be discussed with a lead developer or even dba.
The issue we currently have is that the url is only available for a limited time.. We reach an error:
"Fail to retrieve data, either because the data is expired or flush out from memory, contact administrator to increase ve.cache.limitation if this happens a lot."
in tuning_service.properties we have --> ve.cache.timeout=1200 (not sure if this is in minutes?) in tmsserver_override.properties we also see --> LINK_LIFE_HOURS = 168 but this is for sure not honored.
So maybe: question 1: can the ve link be kept active for a longer duration (days/weeks) question 2: can we export the data from the ve to a pdf?
thx, Steven