Ideally you would shutdown the applications and concurrent managers then truncate fnd_log_messages drop storage;. Then restart. Both concurrent requests and applications navigation can write to this table.
Thanks for the quick suggestion
Is this the supported method ?
I couldnt see any official note on FND_LOG_MESSAGE table Truncation.
FND_LOG_MESSAGES is a diagnostic table that only gets data when FND: Debug Log Enabled is set to yes. If you operate your system with FND: Debug Level higher than unexpected, you can expect this table to grow very large and need to be purged from time to time.
The official purging methods are contain in the below notes which may involve patching:
FNDLGPRG Not Purging Old Records In The FND_LOG_MESSAGES Table (Doc ID 1099184.1)
How to Purge/Troubleshoot the FND_LOG_MESSAGES table (Doc ID 735138.1)
Here are 4 official notes which request truncate of fnd_log_messages:
R12: "FND: Debug Log Enabled" Profile Option Is Enabled but Debug Data Is Filling the Tablespace. How To Fix This? (Doc ID 2096591.1)
How To Get Log, Trace Files In OA Framework Pages And Concurrent Request Programs (Doc ID 290614.1)
Potential Logging of E-Business Suite Passwords (Doc ID 1579709.1)
Create Accounting Error: ORA-20100: Error: FND_FILE failure. Unable to create file (Doc ID 1137533.1)
You will need to first disable the FND profile that writes into the table.