After upgrading a FMS or database cartridges agents are missing after deploying the cartridge to the FglAM using the Agent Status or Agent Managers dashboard.
High record count on pcm_encoded_data and persistable_config_model tables in the FMS repository.
Ideally, the number of rows in both of these tables should be less than 15,000 rows or the size of the current_version table. Rowcounts of hundreds of thousands or millions of rows in either of these tables would be of concern and could cause performance issues including
In 5.9.8 release FMS version a daily maintenance job runs daily at 2am beginning on the first night after the FMS has been upgraded to this version.
This was included a part of Enhancement FGL-20607.
In lower FMS versions and during the time between when the FMS was upgraded and the beginning of this first maintenance job, there may be a huge number of rows in the following two FMS repository tables.
A delete statement could be run against the FMS repository to reduce the number of rows to those ASP properties at the current version. This however is a very highly transactional statement and may put a lot of activity on the FMS repository database, transaction logs, and temporary databases or datafiles.
1). Take a backup of the FMS repository database
2). Delete the non current ASP configuration from the FMS repository using the following SQL
delete from persistable_config_model where user_created = 1 and version_id not in (select version_id from current_version);
delete from pcm_encoded_data where version_id not in (select version_id from current_version);
Note: The information in the script(s) provided is known to work successfully; however, they have not been officially tested by our Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by our Support and Development. Support and Development recommend always making a backup of the current database prior to execution of any script(s) that may modify it.
An alternative to the delete statement, especially useful in FMS systems with rowcounts in these tables over 500,000 rows, would be to create a new set of replacement tables with the necessary rows and then replace the large tables with the new smaller tables. They is much less transactional and sets a much lower high water mark on the tables.
1). Shut down the FMS service or process
2). Back up the FMS repository database
3). Run the scripts using a SQL query tool for the specific platform used. Each set consists of 4 scripts which have to be executed in the following order.
4). Restart the FMS service or process
Note: The Oracle version of the table creation scripts includes a default TABLE SPACE setting of USER, this may need to be changed if the customer environment does not use the default Table Space.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz