Getting "Failed to save object" When Filing an Imaging within IPM Filer After Applying Patch 16973875
Last updated on SEPTEMBER 21, 2017
Applies to:Oracle Imaging and Process Management - Version 10.1.3.6 and later
Information in this document applies to any platform.
After implementing IPM Patch 16973875, when adding new images that are placed into the input folder for Filer to process, the images are placed into the DiscQ folder but the below error occurs when writing to the final storage location.
|100|2017/09/11 11:58:16|Failed to save object $H%MIG rc = 24892 |SUBSYS|<MACHINE>|9|0||StorageThread.c|529|42856|86920|
|100|2017/09/11 11:58:16|Error: Object Validation Failed! Storage Server A, Volume MAGVOL22, Object $H%MIG does not match what was originally stored!|STORAGE|<MACHINE>|9|27190||DiscJob.cpp|527|42856|19764|
|100|2017/09/11 11:58:16|*** AddToFailedQ: $H%MIG ***|STORAGE|<MACHINE>|0|0||DiscWorker.cpp|231|42856|19764|
|100|2017/09/11 12:07:42|[ServerPrep] Disc Prep posting OLD Save MAGVOL22 $H%MIG|SERVERPREP_TOOL|<MACHINE>H|0|0||ServerPrepTool.cpp|1370|6824|46076|
|100|2017/09/11 12:07:42|WRITE: Server: [A] Vol: [MAGVOL22], Obj ID: $H%MIG [Cache 0] SUCCESS!!|STORAGE|<MACHINE>|0|0||DiscJob.cpp|462|6824|84788|
This process is using previous FNAME files and old dates that have already been used in the past. Therefore, messages appear in the logs which indicate the image already exists.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms