Hi,
As there is no archival option available in clarity,you can work on the Data Clean Up Activities and some house keeping Jobs.That will help you to reduce data in some key tables which are very frequently used.And in addition we can also do some activities that will help to improve the over all application performance.
Some of them are below.
1. Allocated the JVM in a better way.(Pls look at CA josh Posts)
2. Schedule the Cleanup Jobs Regularly.(See Below) and schedule all jobs in an meaningful way and Schedule the db intensive jobs (data mart job and
investment allocation job) on minimal usage time.
Clean User Sessions - this job will remove user session records
Delete Investments job - Delete selected investments and their associated data including investment hierarchy, financial data, tasks, timesheets and documents etc.
Delete Process Instance - Delete process instances according to the specified parameters
Purge Temporary Hierarchy Data - Removes temporary data created while computing aggregated costs
Purge Audit Trail - Removes audit trail records
Purge Financial Tables - this job will purge financial data from the project selected at run time
Purge Documents - Delete documents based on supplied parameters
Remove Job Logs and Report Library entries - Remove the job log entries and/or the report library entries that are older that the supplied parameters
3. Very Important--> Reduce the Data in the key tables which is used often in the system like User permission (CMN_SEC_ASSGND_OBJ_PERM) and Slice tables.You can work on it by re-creating the slices to suit your needs.(TEC435572 Document).
4.Re-visit your security access rights which will help you considerably.Don't give any additional access rights unwantedly.
5. Put an regular cleanup process and try to enforce an process.This will help to reduce data in User permission and Slice tables.
For every user the function CMN_SEC_CHECK_RIGHT_FCT is being called every second and inturn it will call an view CMN_SEC_ASSGND_OBJ_PERM_VO
which is pointing out the CMN_SEC_ASSGND_OBJ_PERM table.so if the data is reduced in that table then it helps a lot.
(i,e)
a.Periodically remove the access rights for In Active Resources.
b.In all Inactive projects properly update the allocation finish date for all resources and uncheck the open for time entry.The same for inactive resources
in active projects.
c.Ensure that DOT is updated for In Active Resources so they will not be considered for slices.
d.When an project is de-activated then remove the participants who are not active.
6.Data clean up in DB.(Removed the unwanted custom tables,triggers).Clean the temp tables and whenever need you can generate the data.
7.Set in all objects view,portlet views that unless the user click the filter button the data will not displayed.This will also helps you a bit.
8.Restart all the app/bg/reports/NSA related services daily.
9.set the app session time out to an meaning one.
10.Users will access some Links frequently (i.e Financial Plan screen) you can provide some shortcut links,so the application pages accessed by
users will be short,the hits will be low.
11.CA had given some recommendations for performance (Admin guide,Installation Guide).You can try that in dev server.
12.Do some house keeping at server level.Periodically Clear all the Logs under /clarity/logs and logs under sqltrace.
13.If you have written custom nsql queries in custom portlet ensure that it is optimized and the same applicable for custom reports.
Even 1 bad query can haunt server performance.(you can use Tuesday tips by shawn to work on optimization).
14.In the objects if you have created custom attributes you acn de-cativate the attributes which you are not using,if you are sure that you are not using
any more even you can delete those attributes.
15.If you have enabled audit trail re-visit on it.It is all DB triggers written by CA.If it is really essential then keep it otherwise don't use it.
16.If you are using lot of process then You can also monitor the process engine performance then you can opt for an Dedicated BG Service for
the Process Engine.
17.If the user base is more you can opt for multiple application services and use an load balancer.
cheers,
sundar