The CA API Gateway uses MySQL with the InnoDB engine to store configuration data, audits, and published service policies. This implementation uses a single database tablespace object (the ibdata file) to store all binary data within the database. The MySQL server is configured to prevent this file from exceeding a certain size. If the file must grow to store more data but cannot grow due to the upper limit then the ibdata file will need to be shrunk and certain data within the database must be discarded. This article prescribes removing all audit data from the database as audit records tend to consume the most storage space in the Gateway database.
Please note that this procedure will result in downtime.
An alternative shrink process is provided in the following link :
the current process can be a bit tricky, use wrong IP address or apply to wrong machine etc, - the alternative knowledge doc aspires to be less prone to error.