Database security
The Oracle database stores all report data. The Reporting Database is usually installed on the Portal Server, but you can just as easily install it on a separate server, preferably a dedicated database server. These binaries are installed during the first step of the installation procedure.
Data is managed in the Reporting Database with automatic purging scripts that run with specific retention periods per product and even data type. Some reports are more valuable when they have access to historical data. Because the Reporting Database only stores metadata, the amount of data on the Reporting Database is relatively small (GBs).
As recommended by Oracle, the ORA_STIG_PROFILE user profile is applied to all user accounts, unless a more restricted profile is used.
Some queries that retrieve more information on the user profiles are given below.
To see which profile is used for PORTAL and APTARE_RO users and to view the properties of the resources under these profiles:
SELECT du.USERNAME, dp.PROFILE, du.ACCOUNT_STATUS, dp.* FROM DBA_USERS du, DBA_PROFILES dp WHERE du.username IN ('PORTAL', 'APTARE_RO') AND du.profile = dp.profile ORDER BY USERNAME;To view details of all the available user profiles that can be portentially used:
SELECT * FROM DBA_PROFILES;
To assign a profile to an existing user or to create a new profile, see Creating a Profile section of the Oracle documentation.
Note:
: If any changes to the assignment of a user profile for PORTAL and/or APTARE_RO takes place then it may force to change the existing password of these users as per the new profile's restrictions. If the password for these users is then changed, it is mandatory to update in the application.