Backup Programs Warn That jms.state, Oc4jJmsExceptionQueue, and other JMS Persistence Files are Corrupt or Skipped

(Doc ID 1205823.1)

Last updated on AUGUST 08, 2016

Applies to:

Oracle Applications Technology Stack - Version 12.0.4 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.


When doing a backup of a running E-Business Release 12 instance, such as with Symantec Backup, certain files in the J2EE persistence directories will be skipped or flagged as corrupted:

For example:

.../ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/Oc4jJmsExceptionQueue - skipped.
.../ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/jms.state - skipped.
.../ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/Oc4jJmsExceptionQueue - skipped.
.../ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/jms.state - skipped.
.../ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/Oc4jJmsExceptionQueue - skipped.
.../ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/jms.state - skipped.

or a Windows example:

Backup- "F:\...\ora\10.1.3\j2ee\forms\persistence\forms_default_group_1\jms.state" is a corrupt file.
Backup- "F:\...\ora\10.1.3\j2ee\forms\persistence\forms_default_group_1\jms.state" is a corrupt file.


Running a backup process while the EBS web tier is running.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms