I suggest you to verify if the Oracle Database Maintenance Tasks are enable.
Also, try to check the memory used by the AOS service.
The posting problem is the same also after the AOS is restarted
Thanks & Regards
Respect the provided answers from other community members. Don't provide or do not copy the same answer to the same thread. Additional insights are welcome!
how to check memory used by the AOS service.
You can run Task Manager on the AOS' host, find ax32serv.exe process and check its memory (private working set) consumption. In Axapta 3.0 an AOS cannot use more then 2 Gb; in fact it used to crash at about 1.8 Gb.
Axapta 3.0 actually runs Object Server Manager (ax32mgr.exe) process as a Windows service, and that in turn spawns AOSes as child processes.