DBI from PAS MSAgent keeps growing

Every transaction is finished within a few hundred milliseconds. 
There is nothing scheduled what every 5 minutes calls the appserver, it seems to be an internal pasoe process causing DBI growth
Agent startup parameters: -T /temp -t -Bt 20000 -tmpbsize 8 

When the MSAgent is stopped logs with logentrytype temp-tables:3 or -tttablerangesize / -ttindexrangesize with ttStats enabled shows the AS-ADMIN process deleting Temp-Tables and the DBI file is eventually removed:

With -t enabled on a Unix like platform, the DBI files are visible. Without enabling 4GLTrace, the DBI files owner process can be determined by the file name. (Note: this format is a convention OpenEdge uses for now, as of version 12.8, which may be changed in the future.) The file name should be like:

DBIthreadid_sessionNumXXXXXX

example:  DBI28880_3a36476 

Where:

-  threadid is some number

- sessionNumber is the ABL Session number (e.g., 4 for AS-4, 7 for AS-7). The AS-Admin temp-table db file name can be identified because it's sessionNumber will always be 3.  And, XXXXXX gets replaced by the OS with something random when the file name is created (trying to guarantee a unique name).           

The DBI file is the Admin Session's temp-table (it owns the _AgentRequest table) and they exist for the life of the agent.  Request metrics are stored in a temp-table and as the number of requests increases, so will the DBI file for the AS-Admin session.  There is currently no way to delete the _AgentRequest temp-table.

Until the fix is available, try using the workarounds below.

1. Server Reboot

2.  Trim the PASOE MSAgent

• How to stop a PASOE agent with OEJMX?
• How to trim and restart PASOE Agents using REST APIs.

3.  Periodically flush records from the Admin Session's temp-table by clearing the collected metrics (since 11.7.5)

• The JMX query will not reduce the current size of the DBI file, but it will prevent it from growing further until the space becomes filled again with request records. 

Alternatively use the REST API via OEMANAGER using a DELETE HTTP request against the OEMANAGER URL endpoint :