Security Dbcs audit

Hi,

We are currently discussing and evaluating whether the administrators should continue using the shared application schema credentials for activities such as compiling procedures/packages and creating or modifying application objects. We are also checking whether these activities can be performed through individual named accounts with appropriate privileges.

While this assessment may take some time, we would like to understand the available options for maintaining individual accountability in the interim.

Could you please advise on the following:

1. If administrators continue to use the application schema credentials temporarily, what Oracle-recommended options are available to trace and identify the individual administrator who performed the activity? We would like to capture details such as the actual user, source/host, session information, timestamp, SQL/DDL executed, and affected objects.