Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Caché System Administration Guide - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Using <strong>Caché</strong> on UNIX, Linux, and Mac OS X<br />
6.2.4.2 Step 2. Perform Recovery<br />
The startup script tests for the existence of the CACHE.WIJ file in the install-dir/mgr directory:<br />
• If the CACHE.WIJ file does not exist, startup proceeds to Step 3.<br />
• If the CACHE.WIJ file does exist, the startup script runs the recovery program (cwdimj). The<br />
recovery program checks for the existence of the ids shared memory object:<br />
- If the ids shared memory object exists, the system is assumed to be up and running. The<br />
recovery program exits with an error. Startup halts.<br />
Action: The user must run cstop or cforce to halt the running instance.<br />
- If the ids shared memory object does not exist, the recovery program checks the Daemon<br />
Resource Locks:<br />
• If no Daemon Resource Locks are held, recovery assumes <strong>Caché</strong> is not running. The<br />
recovery process locks the Control Process Resource Lock to prevent concurrent startups,<br />
and performs recovery on the instance. When the process exits, the lock is released, and<br />
startup continues with Step 3.<br />
• If Daemon Resource Locks are held, one or more daemons are running on some node<br />
for this instance. The recovery program reports this and exits with an error. Startup halts.<br />
Action: The user must run cstop or cforce to halt the running instance on the appropriate<br />
node. This deletes the cache.ids file and the ids shared memory object.<br />
6.2.4.3 Step 3. Start <strong>Caché</strong><br />
The <strong>Caché</strong> startup process (cache) is run. Checks are repeated to ensure that another startup is not<br />
competing for the startup resources:<br />
• If Daemon Resource Locks are held, indicating one or more daemons are running on some node<br />
for this instance, <strong>Caché</strong> reports this and exits with an error. Startup halts.<br />
The node on which the daemons are running is unknown if the cache.ids file does not exist.<br />
Action: The user must assume that another startup has occurred on some node. To determine on<br />
which node the instance has started, examine the cache.ids file.<br />
<strong>Caché</strong> continues startup. At the end of the first phase (Control process startup and daemon initialization),<br />
shared memory, the ids shared memory object, and the cache.ids file are created.<br />
74 <strong>Caché</strong> <strong>System</strong> <strong>Administration</strong> <strong>Guide</strong>