ATG - Bcc Full Deployment Failure with IOException

Error

Deployments Fail Due to Corruption in Version File Store, IOException in Log: Unexpected end of stream while reading deployment protocol

Applies to:

Oracle Commerce Platform - Version 9.4 and later
Information in this document applies to any platform.

Symptoms

Deployments fail as a result of problems with a file asset, such as targeter or scenario .properties file, in the VersionFileStore .  In the BCC UI, the deployment status shows that the deployment failed and references a versioned file that the VersionManagerService is trying to reference.

Deployment Failed

Deployment Status: Error Applying
Error Message:
Deployment FailedDeployment 'ID' to target 'TARGET' encountered a system level deployment error during data transfer.

Asset:
uri:atgvm://VersionManagerService/PublishingFiles/targeter/fa108888 (note URI maybe different for your project)

Note: The error "atg.deployment.common.DeploymentException: Deployment 'ID' to target 'TARGET' encountered a system level deployment error during data transfer" is a generic error for any deployment failure and is not specific to only this issue.

Cause

It is possible, but not mandatory, that a problem occurred during a previous deployment. For example, a deployment was run and a target was restarted in the middle, or a previous deployment failed. It is also possible that no specific deployment problem was detected.

Solution

Note:  Exercise caution when directly modifying the versioned database schema.  For assistance identifying this problem and implementing the solution, please open an SR with Oracle Support.

1. Follow the steps in sequence

• login into PUB schema with sql developer or ssh on particular environment.
• take backup/export of table epub_file_asset table content
• run following command <update epub_file_asset set VERSION_DELETE=1;
• commit the changes
• invalidate the caches on PublishingRepository through Dyn/Admin of BCC instance.
• Error will disappear