• Article Type: General
• Product: Aleph
• Product Version: 17.01

Description:
Dup50_p_serial_13.07526 contains several error messages and the report did not print. There are two files in /wrkspc1/aleph_tmp/tmp/ - dup50331165 and dup50331166. I have looked at the records in those two files and they seem to have been updated on the database. I am not sure what the errors mean and how we can keep this from happening in the future.

Here are the messages:
Error (serial2_create_omit) : invalid starting date as input 2005 01

Error (serial2_updt_omit_w) :unsupported format of MMWW - 0112

Error (serial2_updt_omit_w) :unsupported format of MMWW - 0906

Error (serial2_check_lvl_at_end) : Check 853 subfields u

Error (serial2_updt_omit_w) :unsupported format of MMWW - 0331

Error (serial2_updt_omit_w) :unsupported format of MMWW - 1229

alloc error: io_buf_levels: size : 10000

I/O error : file '/exlibris/aleph/a17_1/tmp/dup50331165'
error code: 4/6 (ANS85), pc=0, call=12, seg=0
146 No current record defined for sequential read

Resolution:
Each error message is preceded in the log by a doc number. For instance, preceding the first "invalid starting date " we have:
Start handling DOC NO: 000131216

(This an ADM number.)

Please check to see if the records have been updated. If not, then examine the HOL pattern and the subscription record for any oddities which might explain the error.

• Article last edited: 10/8/2013