IO08983: ICM7015/ORA-01830 when moving a document from one collection to another collection

APAR status

• Closed as program error.

Error description

• Customer run API app to move the docs from one collection to
  another collection.
  The collid is updated in RMOBJECTS, but not in ICMUT00300001
  due to ICM7015/ORA-01830 error.
  

Local fix

• For temporary workarround, user can change NLS_DATE_FORMAT to
  all session to 'YYYY-MM-DD-HH24.MI.SS.FF6'.
  

Problem summary

• When a document is being moved from one collection to another
  collection, the library server returns the errors ICM7015 and
  ORA-01830 because of the date/time format mismatch.
  
  An example of the code that will cause the error follows:
  
  
  
  documentDDO.retrieve(DKConstant.DK_CM_CONTENT_NO);
  
  // To change collection for parts:
  // a) flag the part to request for changing collection
  // b) set the new collection
  // c) update the document DDO.
  short dataId = documentDDO.dataId(DKConstantICM.DK_CM_DKPARTS);
  DKParts parts = (DKParts)ddo.getData(dataId);
  dkIterator partIter = parts.createIterator();
  while(partIter.more())
  - {
  - - DKLobICM part = (DKLobICM) partIter.next();
  - - //-Retrieves the parts attributes to get the source
  collection
  - - part.retrieve(DKConstant.DK_CM_CONTENT_NO);
  - - DKStorageManageInfoICM storeInfo = - - - -
  (DKStorageManageInfoICM)part.getExtension("DKStorageManageInfoIC
  M");
  - - storeInfo.setCollectionName("NEWCOLLECTION");
  - - part.setChangeSMSRequested(true);
  - }
  

Problem conclusion

• This problem was fixed in DB2 Content Manager Version 8.3 Fix
  Pack 10.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LIBRARY SERVER

• Fixed component ID

  5724B1907

Applicable component levels