Author Topic: Unable to close the File (MsgNum 122)  (Read 3366 times)

vjjdavid

  • Guest
Unable to close the File (MsgNum 122)
« on: August 24, 2016, 08:59:21 AM »
We are seeing a huge number of (MsgNum 122) in our System Log, can anyone share why OD in "Unable to close the File".  we have 4 caches define, first one of 250MB and other three of 1TB.  Is there a solution for these (MsgNum 122)?

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2228
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Unable to close the File (MsgNum 122)
« Reply #1 on: August 25, 2016, 08:36:33 AM »
So, we're going to need a lot more info.

Start with Platform & Version numbers.  (You posted in 'Documentation', so I don't even know if you're on MP or z/OS!)

Then we'll need some information on what is happening around the same time as these other messages.  Are these errors close to other messages in the System Log, like retrievals or loads?

Help us to help you by giving us as much info as you can.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

vjjdavid

  • Guest
Re: Unable to close the File (MsgNum 122)
« Reply #2 on: August 25, 2016, 08:54:47 AM »
OD v9.5.0.3
Red Hat Enterprise Linux Server release 6.8 (Santiago)
4 volumes on NetApp, /vol1 250GB and /vol2, /vol3, /vol4 1TB each
The SL is written on /vol1 but actual content on /vol2, /vol3, /vol4 based on round robins.  We have re-mounted the volumes now with NOAC and no longer see the 122 error however we are seeing error 119 (Unable to write the file).  I am able to see the file at the OS location and pull it in ICN v2.0.3 or hard client.  How to get rid of that error message once and for all?     

Alessandro Perucchi

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1002
    • View Profile
Re: Unable to close the File (MsgNum 122)
« Reply #3 on: September 08, 2016, 07:05:57 AM »
OD v9.5.0.3
Red Hat Enterprise Linux Server release 6.8 (Santiago)
4 volumes on NetApp, /vol1 250GB and /vol2, /vol3, /vol4 1TB each
The SL is written on /vol1 but actual content on /vol2, /vol3, /vol4 based on round robins.  We have re-mounted the volumes now with NOAC and no longer see the 122 error however we are seeing error 119 (Unable to write the file).  I am able to see the file at the OS location and pull it in ICN v2.0.3 or hard client.  How to get rid of that error message once and for all?     

Well CMOD use for System Log the following strategy: he keeps the current file in append mode. So if you go in the cache in the retr/SL directory you will see a link called "APPEND"
so instead of writing tons of small files with the size of a few bytes, CMOD keeps them aggragating in one file until some rules comes, like arsmaint -m, and then it will create a new file to be appended.

Now if you use netapps with some retentions policy where you say, the file is written, and now you cannot touch it, because it is read-only, then CMOD is not happy.
Why? Because a cache is meant to be a cache, not to be a retention FS where you put everything in RO as soon as you touch it.

My advice would be to put some delay (if it is possible) on netapp and tell, wait X hours before putting the file in RO mode. and every X-1 hours, run the arsmaint -m command... and then you will never see such errors again.
but it means you have a window were the file could be modified.
Alessandro Perucchi

#Install #Migrations #Conversion #Educate #Repair #Upgrade #Migrate #Enhance #Optimize #AIX #Linux #Multiplatforms #DB2 #Windows #Oracle #TSM #Tivoli #Performance #Audits #Customizing #Availability #HA #DR #JavaApi #ContentNavigator #ICN #WEBi #ODWEK #Services #PDF #AFP #XML