Answer
This has been attributed to an underlying Oracle database issue rather than something wrong in IFS configuration. Where it happens, a full stop-start cycle — stop the application, restart the database, then start the application again — has worked as a practical workaround, even though it doesn't address whatever's triggering the Oracle-side error in the first place.