I am using 4.5.3. and recently I encounter an issue related to .lockdir.
To test my deploy script, I download all needed files from a remote schema to my localhost. Then I use my deployment script to deploy the schema back to the remote host. But my ctl file mistakenly includes the \bin\java folder. After running the deployment script I realize that: the \bin\java folder was copied over to the remote server under \Server\registry\repository\schema_name\runtime. So I decide to delete the folder. Under the \bin\java folder, there is a .lockdir folder, I delete that folder as well. Since the remote server is a shared environment. I later learn: the \bin\java folder under \client is gone, and that cause other schema fail on finding some system objects. And here are my questions:
1. did my action cause this consequence?
2. Actually I am not sure if the \client\bin\java folder is gone or only the .lockdir folder. My question is if only the \client\bin\java\.lockdir is deleted, what kind of consequence it might cause in a shared environment?
To test my deploy script, I download all needed files from a remote schema to my localhost. Then I use my deployment script to deploy the schema back to the remote host. But my ctl file mistakenly includes the \bin\java folder. After running the deployment script I realize that: the \bin\java folder was copied over to the remote server under \Server\registry\repository\schema_name\runtime. So I decide to delete the folder. Under the \bin\java folder, there is a .lockdir folder, I delete that folder as well. Since the remote server is a shared environment. I later learn: the \bin\java folder under \client is gone, and that cause other schema fail on finding some system objects. And here are my questions:
1. did my action cause this consequence?
2. Actually I am not sure if the \client\bin\java folder is gone or only the .lockdir folder. My question is if only the \client\bin\java\.lockdir is deleted, what kind of consequence it might cause in a shared environment?