Skip to main content

Posts

Showing posts from June, 2016

Image import stuck

Root cause:  --------------- This error is due to improper optimizations during project checkin when the number of assets in the project is greater than the /atg/epub/version/VersionManagerService.workspaceOptimizationThresholdAssetCount (default of 500). Solution: ------------ You can clear the conflict with project in BCC which appears stuck. Go to the component browser(dynamo admin) To workaround the error, set the  /atg/epub/version/VersionManagerService.workspaceOptimizationThresholdAssetCount  PROPERTY to a higher value. Specifically, set the workspaceOptimizationThresholdAssetCount property to a number that is larger than the number of assets in the project. For example, if the project contains 1000 assets, set the workspaceOptimizationThresholdAssetCount property to 10000.

BCC Snapshot Issue

Reason for this issue: Snapshot issue occurs when you kill the deployment in middle of deployment or rollback. To resolve the Above Issue, try the following steps. Following case explains for Staging(Preview) server . 1. Run the below query on mgmt schema. select epub_target.display_name as "Target", epub_prj_tg_snsht.snapshot_id as "Snapshot id", epub_project.display_name as "Project name" from epub_target, epub_project, epub_prj_tg_snsht where epub_prj_tg_snsht.project_id in (select project_id from epub_project where workspace is not null and checked_in = '1' ) and epub_target.target_id = epub_prj_tg_snsht.target_id and epub_prj_tg_snsht.project_id = epub_project.project_id order by epub_project.checkin_date desc; 2. Fetch the recent snapshot for the corresponding Target(Staging or Production) 1   3.  Initialise the same in Deployment Server from dyn/admin of Publishing. http://h...

Project is Stuck and not deploying in BCC

If you see below error during project deployment please follow below steps. 1.          Go to the mgmt. schema and run the below query. select * from avm_asset_lock; 2.          If you will find any row, clear that then try to resume the deployment.