Journal I/O error

Products

• IDMS
• IDMS - Database

Issue/Introduction

Received an I/O error on a journal file during an archive journal offload.

How to resolve this?

Environment

Release: All supported releases.

Resolution

From the IDMS Database Administration Guide, section Journal Files, sub-heading I/O Error or Corruption of a Journal File:

While CV is active, if a journal encounters an I/O error, or some type of corruption, IDMS will stop using the journal. If the error occurred to the active journal, IDMS will switch to the next journal, and disable the use of this journal. If the error occurred to a journal that was not the active journal, then IDMS will not switch to this journal. It will remain disabled to IDMS until the journal file is corrected.

If two journals are defined to the system, and one becomes corrupted, IDMS will journal to just one journal. When that journal fills, IDMS will wait until the journal is offloaded by the ARCHIVE JOURNAL, before it starts to journal again. All update activity to the database will stop until the ARCHIVE JOURNAL is done. Therefore, it is recommended that you define three or more journals to the system. Most users run with four or more journal files.

To correct the disabled journal; Run an Archive Journal - to offload any data on the corrupted journal. If the offload will not run, identify the journal file that is corrupt and resubmit the Archive Journal using the READ parameter.

DCMT VARY JOURNAL journal-file-name INACTIVE. This makes sure the journal is 'offline' or disabled to IDMS. IDMS will not use the journal at this time.

Format the journal. Run the IDMS FORMAT Utility, specifying just the journal file with the error.

DCMT VARY JOURNAL journal-file-name ACTIVE. This brings the journal back 'online' to IDMS. After this command is issued, IDMS will automatically switch to this journal when the prior journal is full. Until this journal is switched to, the Segment number for this journal will be '0'.