When getting such exception [ORA-03113: end-of-file on communication channel] which means a connectivity issue between the Oracle Client/Server, the actual Publisher service is unable to start/resume transactions left in the queue and items remain in "Waiting For Publish" status indefinitely, or until the Publisher service is restarted.
Naturally, a stable network should be in place however it would be handy to have a retry mechanism integrated.
Business Case:
A mass publish actions scheduled may not be picked up in case of DB Connectivity issue.