A customer testing the upgrade of Shareplex 126.96.36.199 for oracle 9i on a target environment to Shareplex 188.8.131.52 for 10g on a target environment.
The standard procedure for an upgrade (for this particular client), always includes shutting down Shareplex then exporting a full backup of splex owned database tables AND creating a tar ball out of SP_SYS_PRODDIR and SP_SYS_VARDIR
As the customer is testing this upgrade they are getting an error message when creating the tarball indicating
vardir_2120/state/.ddl-43-0-1644-360792.lck: cannot open file
Customer sees a 0 byte hidden file with no permissions on it ----
It was created or last touched about 2 hours prior to shutting down Shareplex.
Customer wants to know what this file is, more importantly if it is not included in the tarball and the customer was to try to restore Shareplex from the tarball would there be problems if the file does not exist?
Permission on the ddl lock file not set correctly after the move of the vardir.
The customer opted to chmod the file to make it readable, then tar it.
The file is a ddl lock file. Poster creates this at the first encounter of a specific ddl operation. So if you have multiple post queues and/or horizontal. partitioning; it lets poster know that the ddl for that specific operation has been or is being applied.