EPMA Transaction Purging Overview

Performance Management Architect creates transactions in the Performance Management

Architect database. This database is automatically created during installation and configuration.
Since Performance Management Architect does not delete these artifacts, the database size can
increase over time. The Performance Management Architect Transaction History Purge Utility
enables you to remove transactions from the database to reduce database size.
The Transaction History Purge removes transactions to reduce database size. If you use the
utility, you should make a full backup of the Performance Management Architect database before
running the utility to keep an audit trail for Sarbanes-Oxley compliance.

Note: You must have the LCM Administrator or EPMA Administrator security role to purge
the transaction history.

Scheduling Database Cleanup Tasks

Go to run and type taskschd.msc
Task scheduler window will open.
Create a task on the actions task scheduler library

The create task window will open

Mention the time when it needs to start on trigger tab in create task window.

Mention the action which this task will perform in the New action tab in create task window
Browse and select the EPMA_database_cleanup_utility.exe in the below mentioned path
E:\Oracle\Middleware\EPMSystem11R1\products\Foundation\BPMA\AppServer\DimensionSer
ver\ServerEngine\bin

Click ok
Add arguments as
EPMA_database_cleanup_utility.exe -uadmin -pM4regvzd -a20 -np
which deletes all applicable transactions older than 20 days without any prompts.
Add start in as the utility folder location .i.e
E:\Oracle\Middleware\EPMSystem11R1\products\Foundation\BPMA\AppServer\DimensionSer
ver\ServerEngine\bin
Click ok.
Now the task is scheduled .
The exit codes and logging capabilities are useful when using Windows Scheduler, since you do
not need to be logged in when it runs, and if it fails you can view a log to determine the cause.
You can find the log file, Database_Cleanup_Utility_Log.txt, in
<EPM_ORACLE_INSTANCE>\logs\epma.
Testing
To run this utility, the EPMA server service should be up.
Right click on the task and click run

The utility will get invoked, which deletes the transactions .

Check the task run details in the task scheduler.To the task to be successful, check the return code
0.

Return codes and their descriptions

Exit Code

Associated
Number

Description

Success

The command ran successfully.

Input Errors

The command line parameter that you used is invalid.

Configuration
File Error

Problem with the BPMA_Server_Config.xml file. For example,

BPMA_Server_Config.xml must be in the same directory as
this utility, otherwise an error occurs. Though this file is not
needed for database connection information, it still must be
present.

Connection
Failure

Connection problem accessing the database.

Hyperion EPMA
Server Not
4
Running

You must start the Hyperion EPMA Server before launching the
Transaction History Purge Utility.

Unknown Error

Contact Oracle Support.

SQL Error

An error occurred while attempting to run the purge against the

database.

Once this invokes the epma server service will be down.

Starting the EPMA Server service

In the Scheduler create a new task with a time gap of 5 to 10 minutes.

The second task will bring the EPMA server service up.

Oracle Documentation is found currently at

https://docs.oracle.com/cd/E40248_01/epm.1112/epma_help/frameset.htm?ch04s20s01.html
or see the epma admin guide.