Hello Friends,
FDMEE: System Maintenance Tasks series where we are going to cover Maintain ODI Session Data script.
If you have not read the first post (Maintain FDMEE Data Tables) of this blog series yet, I would suggest you to first go through that post where Maintain FDMEE Data Tables script along with introductory details of FDMEE System Maintenance Tasks has been covered in detail.
In this post, we will focus on the ‘Maintain ODI Session Data’ task and will see how to manually execute ‘Maintain ODI Session Data’ purge script. Other purge scripts of FDMEE System maintenance tasks are covered in subsequent posts of this blog series, which you can find on below links:
Important Note:
- This post has been written and associated activities have been demonstrated on FDMEE version 11.1.2.4.210.
- There is no outage required on the FDMEE application to execute these purge scripts. But it is advisable not to run any data loads during the purge activity.
- Based on the data retention policy of your organization, you should pre-decide how many days of ODI sessions’ data you want to retain for the analysis of ODI log history.
- Don't forget to take complete FDMEE schema backup before attempting to run these purge scripts.
Maintain ODI Session Data
It is very important to regularly purge the Oracle Data Integrator (ODI) sessions log to reduce the size of the ODI session tables and so the ODI work repository size and improve the performance of ODI studio.
Maintain ODI Session Data script cleans up the ODI Sessions logs that are associated with the Process IDs by the number of days you enter as input parameter while running the script.
Primarily Maintain ODI Session Data script deletes log entries from following ODI tables (SNP_ tables):
- SNP_SESSION
- SNP_EXP_TXT
- SNP_PARAM_SESS
- SNP_VAR_SESS
- SNP_SEQ_SESS
- SNP_SESS_STEP
- SNP_SESS_TASK
- SNP_SESS_TASK_LOG
- SNP_TASK_TXT
- SNP_STEP_LOG
- SNP_SESS_STEP_LV
- SNP_SESS_TASK_LS
- SNP_SESS_TXT_LOG
- SNP_EXP_TXT_HEADER
- SNP_STEP_REPORT
These SNP* tables consume a lot of space in your FDMEE schema.
Before proceeding further with purging steps, I would suggest you to maintain an excel sheet to track pre-purge and post-purge FDMEE schema size to see how much space has been freed up post purge activity. Something like below:
Step-by-Step process to execute ‘Maintain ODI Session Data’ purge script
1- Log in to Workspace with Admin credentials.
2- Open FDMEE console (Data Management) from Workspace and on the Workflow tab, under Other, select Script Execution:
3- In Script Execution, and then in Custom Script Group, select System Maintenance Tasks.
4- From the Scripts grid, select Maintain ODI Session Data script and Click Execute.
5- It will prompt to enter the following parameter value on the Execute Script screen.
Days to keep ODI Sessions
Enter the number of days you want to retain data for in live ODI tables.
Note: Maintain ODI Session Data scrip takes some time to execute so its advisable not to purge too much in one go.
Note: Maintain ODI Session Data scrip takes some time to execute so its advisable not to purge too much in one go.
6- Keep Execution mode selected as Online. The online method processes the report immediately.
Execution modes:
online — ODI processes the data in sync mode (immediate processing).
offline — ODI processes the data in async mode (runs in background).
7- Optionally, If you want to schedule the purge script run rather than running it instantly, Click on Schedule option and enter the scheduling details as per your requirement.
8- If you want to instantly run the purge script, then directly click on OK (not on the Schedule option).
You will see a message informing the process ID of your script run as shown below:
9- To see the status of your script execution, click on the Process Details link under the Workflow tab—Monitor—Process Details.
10- Above we can see our script with Process ID 8124 executed successfully.
Click on the Show button for Process ID 8124 to open the corresponding log file.
In the log file, look for the message "Maintain ODI Sessions: Completed" to confirm that script has run successfully without any error. If you encounter any errors, troubleshoot them based on the cause mentioned in the log file. In our case, we see no issue in the script execution.
Once you are done with running the Maintain ODI Sessions Data purge script, now it’s time to check your FDMEE schema size to see how much space has been cleared as a result of ODI tables purging.
Are you surprised to see that FDMEE schema size is still the same despite deleting a significant number of records from ODI tables?
Don't worry! You just need to inform your DBA and ask them to do table reorganization in order to reclaim freed space.
Actually, when you delete the data from the Oracle tables, the data blocks will go onto the free list for that table. That free space will be used for the subsequent insert and update operations into the table. You need to perform table reorganization to reclaim that free space.
Note: reorganization of tables requires outage in your Hyperion environment so you have to stop all your application services prior to the reorganization activity to be performed by your application DBA.
Post tables reorganization by DBA, compare pre and post purge size of your FDMEE schema to see how much has the schema size actually reduced.
That's all for this post.
Maintain ODI Session Data purge script can also be automated to run using Executescript batch file located in the folder:
<drive>\Oracle\Middleware\user_projects\epmsystem1_fdm\FinancialDataQuality.
We will cover the automation of Maintain ODI Session Data purge script in a separate post of this blog series.
No comments:
Post a Comment