23.1.2 Notes on using the embedded database

An embedded DB service consumes the desktop heap, which is used by service processes, in proportion to the number of its connections to the DB server. For that reason, services set to the JP1/AJS3 system account might fail and become unable to start. In such cases, you can change the desktop heap by using the OS settings.

Edit the third parameter value of SharedSection, which is the registry variable to define the size of the desktop heap. For details about how to edit the registry, go to the Microsoft website and see the related articles in the support and technical information sections.

If the value of the PATH environment variable specified as a system environment variable includes a network drive name (a path to another machine), and the user does not have access permissions for that machine, the following might occur:

• A 0xC0000022 error (cannot initialize the application correctly) might occur during startup of an embedded DB service.

• Service Control Manager might output warning messages with the event IDs 7009 and 7000.

Check whether the user has access permissions for the specified server.

Make sure not to delete the files under %TMP% during execution. An embedded DB normally creates under the-embedded-DB-operation-directory\tmp temporary files to be used as working files for executing the command daemon. However, when the %TMP% environment variable is set, some temporary files will be created under %TMP%.

During execution, take care not to delete the files located under $TMPDIR. Usually, the embedded DB creates the temporary files used for tasks during daemon (or command) execution under the-embedded-DB-operation-directory/tmp. However, some temporary files with the environment variable $TMPDIR set are created under $TMPDIR.

After the embedded DB is set up, do not use the chown command to change the owner. If you change the owner by using the chown command, you might not be able to start the embedded DB.

The following directories and files are not deleted automatically when the embedded database is deleted. Delete them as necessary.

• embedded-DB-operation-directory

• embedded-DB-operation-directory/conf

• Files located under The-embedded-DB-operation-directory/conf

When the embedded database is set up by running the ajsembdbinstl command with the -v9standard option specified, JP1/AJS3 - Manager generates a file that contains the path of the embedded database in the following directory:

In Linux

/etc/init

In HP-UX, Solaris, or AIX

/etc/inittab

Do not manually delete or edit this file. When JP1/AJS3 or the embedded database is uninstalled, this file is deleted from the preceding directories. For details about the ajsembdbinstl command, see ajsembdbinstl in 2. Commands Used during Setup in the manual JP1/Automatic Job Management System 3 Command Reference.

Note that if the run level of the OS is single-user mode and processing takes time before this file is generated in the preceding directories, the embedded database might not be registered. As a result, the embedded database and JP1/AJS3 might be unable to operate normally.

If you want to change the run level to single-user mode, be sure to stop JP1/AJS3 and the embedded DB before changing the run level.