Resolution:
InstanceLockedException is repo based and applies to an repo instance(.DAT file).
When an InstanceLockedException occurs, then look for ".lck" file under /data
folder when using remote server deployment (where the applicaton data resides
on your Admin Server) and delete them. If you are using 'local application data' deployment
option then look for the ".lck" files on the machine where you are running your
Appmanage or on the Admin Server machine if the GUI is used. The ".lck" files in this
case will be in a temporary location,  the temporary location is &lttmp>/tempdats where &lttmp>
is the temp directory for the user, delete them. On unix it will under .var/tmp/tempdats
folder.(Aborting or Killing the AppManage commands in between are more likely reasons
to leave such locks).

EntityLockedExceptions are caused when updating the domain data, Restarting the
Admin Server will clear such lock and should let proceed with your Deployments.

InstanceLockedException and EntityLockedExceptions which causes deployment failures.