Strange behavior may be seen when PAM's storage becomes full. Different functions may fail, for example upgrades, DB backups, and more. License mismatches in clusters have even been seen, probably due to inability to replicate the database.
Common causes for over consumption of storage are typically setting log levels high and leaving them that way for too long and the growth of a couple of tables in the database. PAM has processes to clean up the tables, but sometimes intervention by Support is required. Support can clean out the bloated tables and compact the database. PAM's GUI does allow for the DB to be compacted by an Admin, but sometimes this may not work, if the storage is too full. When the growth of storage usage was caused by verbose logging Support will be needed to free up the wasted space. Both this and the manual DB compaction will require ssh access to be enabled for Support. Keep you eyes on your storage utilization and open a ticket if it becomes full. Bear in mind the size of the storage assigned to PAM. For example, usage of only 10% can still mean the DB is very large if PAM's storage is very large(10% of 80Gb is 8Gb).