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

Export / Import Endeca App between Different Environments

APPLIES TO:

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

Export endeca Application Steps

1. Record Store - Click here to get more details. This Step can be optional if baseline triggers using /atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin Component

2. Dimension Value Id Manager - Navigate To CAS Bin folder and run following commands to export
CAS_Installation_Path/CAS/11.1.0/bin->./cas-cmd.[bat|sh] exportDimensionValueIdMappings -m <> -f /home/atg/dimvalid.csv

3. Endeca Pipeline - Copy Endeca_App/config/mdex folder

4. Editors Config - Copy Endeca_App/config/ifcr/configuration/tools/xmgr folder

5. Workbench Application - Navigate To Endeca Application control folder and run following commands to export content

       <>/control->./runcommand.[bat|sh] IFCR exportApplication

This would generate the zip/exploded folder.

6. Index-Config - Navigate To Endeca Application control folder and run following commands to export index-config.json

     <>/control->./index_config_cmd.[bat|sh] get-config -o all-File_Path/index-config.json

Import ENDECA APPLICATION STEPS

1. Record Store - Click here to get more details. This Step can be optional if baseline triggers using /atg/commerce/endeca/index/ProductCatalogSimpleIndexingAdmin Component.

2. Dimension Value Id Manager - Run below command to import dimension values
/CAS/11.1.0/bin->./cas-cmd.[bat|sh] importDimensionValueIdMappings -m <> -f /home/atg/dimvalid.csv

3. Endeca Pipeline - Use the backup of <>/config/mdex folder and move pipeline.

4. Editors Config - Copy editors_config from step 5 and change host and post information based on environment under each json file and run the following command
         <>/control -> set_editors_config.[bat|sh]

5. Index-Config - Run below command to import index-config.json
<>/control->./index_config_cmd.[bat|sh] set-config -o all -f File_path/index-config.json

6. Endeca Baseline Update-  Run below Command

      <>/control -> ./baseline_update.[bat|sh]

7. Workbench Content - Run below command to import workbench content
        <>/control->./runcommand.sh IFCR importApplication <>

8. Promote Content - Run the following command to promote content from Authoring to Live. Promote content can be run the Workbench as well.

       <>/control -> ./promote_content.[bat|sh]

Important step to be performed in end

In the Last Do base line indexing from Store Dyn/admin from ProductCatalogSimpleIndexingAdmin component. This will help in creating exact dim mapping , data and dim vals for endeca schema. These files will not be visible for you to check the mappings.