DS needs to properly shut down to release any internal locks and write database specific information to the applicable files. The files in question differ depending on the type of backend in use (the PDB backend was deprecated in DS 5 and removed in DS 6):
- JE backend files:
- PDB backend files:
If DS is not shut down properly, it runs a recovery process upon startup; this process takes time and can also cause strange errors to be seen in your logs during startup. In extreme circumstances, failing to shut down DS properly can corrupt the backend databases.
If you use AM with an embedded DS, you must ensure you shut down AM properly for the same reasons prior to restarting the server.
The correct process for shutting down DS is documented in Stop a Server. You should ensure your init script achieves a proper shutdown. Similarly, the Microsoft® Windows® service can also be used to shut down DS properly.