Story
When attempting to update a non-Preservica object in DCS (901602583) with Preservica information, I received the following failure message from the batch process:
However, the process successfully pulled in all 46 images from Preservica, the largest with dimensions of 5506 x 4350. The first child OID of this object is 901602597, which has image_001.tif attached to it. After running a 'recreate child oid PTIFF' process, images appeared and the object resolved in Blacklight.
We would like to understand why this failure message is displaying, as it may be confusing for users.
QUESTIONS
Was 901602596 potentially the child OID that got deleted? And if so, shouldn't the image just be replaced in the current OID?
Is there already an image file living at the above location in the pair tree, and if so, where did it come from / to what parent does it belong?
If there was already an image there, why did Preservica try to write to that location?
Acceptance
[ ] Determine cause of failure message
[ ] Determine resolution and make a new ticket for fix if the fix is a big one OR, if small fix, ensure this object can successfully sync
Story When attempting to update a non-Preservica object in DCS (901602583) with Preservica information, I received the following failure message from the batch process:
Cannot allocate memory @ io_write - /data/09/96/90/16/02/59/901602596.tif
However, the process successfully pulled in all 46 images from Preservica, the largest with dimensions of 5506 x 4350. The first child OID of this object is 901602597, which has image_001.tif attached to it. After running a 'recreate child oid PTIFF' process, images appeared and the object resolved in Blacklight.
We would like to understand why this failure message is displaying, as it may be confusing for users.
QUESTIONS
Acceptance