TSA.SERVICEs that run on AUTO mode all day must have light select queries ,otherwise this can be troublesome

The attached document is a holistic oracle health check guide that helps in tuning various oracle parameters

Avoid database triggers on big tables like
STMT.ENTRY,CATEG.ENTRY&
RE.CONSOL.SPEC.ENTRY

Surprisingly indexes created the incorrect way can cause performance issues and slowness.

L3 routines attached to version should not call JOURNAL.UPDATE.This will destroy transaction integrity.

REPORT.LOCKS field can be set to NO in the VERSION application for high volume application versions.

The adapter min/max sessions,response time outs etc can be set up some formulas used in the attached document

Many best practices have been covered in this document in relation to T24 application servers and oracle db

COB jobs with more than 1 SELECT need to be split into 2 and run separately(in the same batch)

In T24 enquiries the use of L to read multiple files can be avoided for performance sake

Default swift messages can get generated when we input some fields in FT.This can be avoided

AWR report in oracle gives plenty of useful information for monitoring performance and solving degradation issues