File size mismatch or file missing during BCC deployment

This means there is some mismatch between files in ConfigFileSystem VFS and the data present in the publishing file repository (holds metadata for these files). This can happen when you copy database from one environment to the other and the version files present in the environment doesnt match with the database.

Cause of this issue: 

1. Files on the disk in the versionFileStore directory were modified by hand
2. Database modified by hand
3. May be errors during a previous deployment
4. Files were restored from backup but database not restored to the same point, or vice versa
5. If the location of ATG-Data changes, then versionFileStore could get lost. For example, if the Java system property atg.dynamo.data-dir is not defined and a standalone EAR is deployed, then ATG-Data can get created in the current working directory on system startup, even if there is a actual ATG-Data defined elsewhere. It's very important to determine and use the location of ATG-Data on a BCC server.
6. If the BCC is launched with a different versioned schema or a different datasource this error can appear.

One of the possible solutions:

1. If many files are corrupt, restoring a backup of both the database and the matching backup of the file system may be the fastest route

2. Add the problematic files to a project, make a small change, save the change and check the meta data and file system data are now in sync.

3. If it is a small number of files, you could find the real size of the file on disk, and update the epub_file_asset.size_types in the database to match.

Enable debug for troubleshoot: 

If you need to find the name of the file asset that is corrupted you can enable the following loggingDebug and then look in the logs:

/atg/epub/DeploymentServer.loggingDebug=true

/atg/deployment/DeploymentManager.loggingDebug=true

/atg/deployment/DeploymentManager.loggingThreadDebug=true

/atg/deployment/DeploymentManager.loggingFileDebug=true

Verifing file meta-data:

Check if data in epub_file_asset table in PUB schema is in sync with the files in ConfigFileSystem. If still an issue, truncate epub_file_asset table in PUB schema.

Using RQL you can see the versioned meta data.

1. In dyn/admin go to the /atg/epub/file/PublishingFiles-ver/ component
2. In the box labeled "Run XML Operation Tags on the Repository" type this query substituting the fileAsset ID of the problematic asset: 
3. <query-items item-descriptor="fileAsset">id="fa100237"</query-items>
4. Click Enter
5. The results will be similar to:

Query: returns 1 items:
<add-item item-descriptor="scenario">
  <set-property name="size"><![CDATA[6454]]></set-property>
  <set-property name="parentFolder"><![CDATA[ff100012]]></set-property>
  <set-property><![CDATA[false]]></set-property>
  <set-property name="branch_id"><![CDATA[10100]]></set-property>
  <set-property><![CDATA[5/22/2015 14:15:28]]></set-property>
  <set-property name="asset_version"><![CDATA[1]]></set-property>
  <set-property><![CDATA[5/22/2015 14:15:28]]></set-property>
  <set-property name="checksum"><![CDATA[5789576582746396372]]></set-property>
  <set-property name="filename"><![CDATA[GrantPromotions.sdl]]></set-property>
  <set-property><![CDATA[/refresh/home/ATG/ATG10.1/home/Publishing/versionFileStore/PublishingFiles/fa100/0/GrantPromotionsxsdl._fa100237#1]]></set-property>
  <set-property name="id"><![CDATA[fa100142]]></set-property>
  <set-property><![CDATA[10600]]></set-property>
   <set-property name="historyIdProperty"><![CDATA[fa100237]]></set-property>
  <set-property name="type"><![CDATA[scenario]]></set-property>
  <set-property name="version_editable"><![CDATA[false]]></set-property>
  <set-property name="is_head"><![CDATA[true]]></set-property>
</add-item>

The size property shows the size in byes (size_bytes) as recorded by the meta data, and the content property gives the physical location of the file on disk.

Here fa100237#1 means 1st version in pub db.