DB2 "SQL1032N No start database manager command was issued" when starting database agent (4301998)

Customer is unable to start a DB2 agent data collection. Encountering the following message in the DB2 agent log:

Agent log: DB2 agent started
ECHO FATAL [MYINSTANCE Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: Unable to attach to instance MYINSTANCE
ECHO FATAL [MYINSTANCE Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: ERROR : Instance Attach
SQLCODE : -1032
SQL1032N No start database manager command was issued. SQLSTATE=57019
SQLSTATE 57019: The statement was not successful, because of a problem with a
resource.
ECHO WARN [MYINSTANCE Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent is logging itself out with code DIE

When logging into the command line with the same ID, the DB2 command to list active databases (db2 list active databases) for the MYINSTANCE profile has the message

SQL1032N No start database manager command was issued. SQLSTATE=57019,

which for the foglight user profile has
SQL1611W No data was returned by Database System Monitor. SQLSTATE=00000

Issue was found to be related to security settings for the DB2 AIX profile.