Oracle performance and maintenance recommendations
This section is relevant for users who run the services under the LocalSystem account; if you use another account, then the PATH environment variable for that account must be changed.
The following Oracle user-accessible parameters influence Oracle database performance:
- In addition to having a buffer cache hit ratio that trends towards 100% for the reference tables, also tune the factors that raise the PGA cache hit percentage trend towards 100%, with an over allocation count of 0.
- Enable parallel I/O. The number of available CPUs on the database server must be taken into account. Having multiple DB writer processes allows for greater throughput.
When running TMTM on Windows Server 2016 with either DB2 or Oracle as the back-end database, you may encounter issues where TMTM services will not load because the database vendor’s DLLs cannot be found, as in the following error message:
Error loading shared library/DLL ./qp_db_ora_121_client.dll, error message: The specified module could not be found.
A change to the registry can be applied to resolve the issue, but we highly recommend you contact your database vendor for instructions on resolving this issue, rather than applying this change yourself. If your database vendor is unable to provide a solution, you can make the registry change described below.
When TMTM services are set up to run as System Local (default mode), the following registry entry needs to be modified:
Directories pointing to DB2 or Oracle client DLLs need to be added to the "Path".
For example for DB2 client DLLs:
For Oracle client DLLs:
This will enable TMTM services to locate the right database client (Oracle or DB2) DLLs and connect to the TMTM database.
You may have to reboot after making the registry change.