Maintain temporary tables
The PPM Server uses several tables for temporary storage during processing (for example, during package migration) for:
-
Logon attempts
- User sessions
-
Debug messages
-
Commands and parameters
PPM Server uses a set of services to monitor and clean up these temporary tables. Make sure the cleanup parameters (described in Cleanup Parameters and in OpenText PPM Configuration parameters) are set so that the temporary tables do not use too much database space.
The KNTA_LOGON_ATTEMPTS
table contains information about attempts to log on to the PPM Server during the previous 14 days. This information includes:
-
USER_ID
of users who attempted to log on -
Status (success or failure) of each logon attempt
-
Messages generated during the logon attempt
The KNTA_LOGON_ATTEMPTS
table is only for auditing purposes. The PPM Server does not require the data to function.
If logon attempts succeed, the records for those most of those attempts are purged. However, the last successful logon based on a combination of USER_ID
and IP address is retained.
If a logon attempt fails, the corresponding record remains in the table for future reference. You must delete the failed logon attempt records manually. the record of the last successful logon attempt also remains in the KNTA_LOGON_ATTEMPTS
table.
The data is automatically purged after the time interval specified by the DAYS_TO_KEEP_LOGON_ATTEMPT_ROWS
server parameter setting.
The PPM_LOGON_SESSIONS table stores information about the sessions created on the PPM server. It includes information such as session start and end time, session type, how uses logged on to PPM, PPM node on which the session was created, and how the session ended.
The data in the table is automatically purged by the Logon Attempts Cleanup service after the duration
specified by the parameter DAYS_TO_KEEP_LOGON_SESSIONS_ROWS
. By default, the value of the
parameter is 60
, which means the table contains information about user sessions during the previous
60 days.
The KNTA_DEBUG_MESSAGES
table contains any debugging text that PL/SQL database packages generate. After you analyze this data, you can safely purge it. The PPM Server purges this data automatically at the frequency determined by the HOURS_TO_KEEP_MESSAGE_ROWS
server configuration parameter setting.