A fix is available
Closed as program error.
If the Managed File is recorded as stored in Commerce staging database (i.e. CMFILE.STORAGE_TYPE = 0 or 1) but the file content is missing (i.e. no corresponding record found in CMSMALLFILE or CMLARGEFILE), the scheduler command, ScheduledContentManagedFileEARUpdateCmdImpl, will throw an ObjectNotFoundException and fail. This results in no managed files getting into the EAR. This fix is to enhance serviceability of the asset upload utility in Management Center
Determine the corresponding managed file with missing content and upload the file again.
USERS AFFECTED: WebSphere Commerce users who upload managed files through CMC or other tools. PROBLEM ABSTRACT: Unable to promote managed files into the WebSphere Commerce EAR due to missing file content in the database. BUSINESS IMPACT: Bad data in any managed file may prevent all the managed files from being promoted to the EAR for that upload operation. RECOMMENDATION: The scheduler command is modified to allow bypassing the problematic managed files and continue with loading the remainder of the managed files into the WebSphere Commerce EAR. The WC_ATTACHMENT trace should be turned on in order to determine the list of problematic managed files and resolve them by either uploading them again or deleting them from the Commerce staging database. Failure to resolve the problematic managed files will eventually slow down the scheduler command.
When the scheduler command for promoting the managed file into Commerce EAR detects managed files with missing content, it will record information of those files into the trace, ignore them and continue. This will allow all the remaining managed files to be processed. ------------------------------------------------------------- The latest available maintenance information can be obtained from the Recommended Fixes for WebSphere Commerce technote: http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
Reported component name
WC COM PROF ED
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
WC COM PROF ED
Fixed component ID
Applicable component levels