The appmap_pruning table is created as part of the pruning process. Once the pruning is complete, this table is dropped as part of the process. If for some reason, the EM restarts during the pruning process, the table is left in place. When pruning runs in the future, it tries to create this table, but it fails because the table already exists. The above errors can be seen in the EM log on the MOM.
Release : 10.7 Enterprise Manager
Postgres Database only
As a workaround, the appmap_pruning can be manually dropped. You can use the Postgres tools to execute the following SQL statement:
DROP TABLE appmap_prunning;
Note that the problem is addressed in APM 10.7 HF#52 where the pruning process now checks for the existence of the appmap_pruning prior to starting. If it exists, it is dropped prior to pruning commencing.