How to relieve the dictionary cache pressure

Method 1) reduce the use of public synonyms in SQL, and specify the schema name in SQL. Large OLTP systems where users log in to the database as their own user ID can benefit from explicitly qualifying the segment owner, rather than using public synonyms. this significantly CES the number of entries in the dictionary cache. for example: SELECT employee_id FROM hr. employees WHERE department_id =: dept_id; 2) the application uses the same id to log on to the DB. An alternative to qualifying table names is to connect to the database through a single user ID, rather than individual user IDs. user-level validation can take place locally on the middle tier. cing the number of distinct userIDs also reduces the load on the dictionary cache. 3) Use PL/SQL Using stored PL/SQL packages can overcome quota of the scalability issues for systems with thousands of users, each with individual user sign-on and public synonyms. this is because a package is executed as the owner, rather than the caller, which has CES the dictionary cache load considerably.