This content has been marked as final. Show 4 replies
I think you would be getting more information in the logs which can give some more clue about the issue. You can also check in AVM_ASSET_LOCK table and see if there are no locks existing on that particular asset.
Thanks for your reply. I checked the " AVM_ASSET_LOCK table". configurable sku is not there in this table. Any other information to Debug this.
Set loggingDebug=true in /atg/deployment/DeploymentManager. Apart from usual loggingDebug, DeploymentManager component also includes some additional properties for including debugging information in server logs:1 person found this helpful
loggingThreadDebug - for thread-level debugging
loggingItemDebug - for debugging at repository items level
loggingPropertyDebug - at repository item property level debugging
loggingFileDebug - for file assets
Setting these debug properties can result in large logs but particularly in this case you can just set loggingItemDebug to true and see if you get some clue for your issue. You may also set loggingDebug on the _production repository.
It is resolved .There are some unnecessary properties at product item.Once i removed those properties , i am able to delete configurable sku.
Edited by: Aaaaaparz1 on Oct 11, 2012 3:19 AM
Edited by: Aaaaaparz1 on Oct 11, 2012 3:20 AM