User guide

1. An executor name based on the server name is generated for the new process, see

Executor Naming

for more details.

2. Process quotas are determined for the executor process based on the current quotas

of the executing server.

3. A termination mailbox is setup for the executor process and read issued.

4. CREPRC is used to create a process and SYS$SYSTEM:LOGINOUT.EXE is

executed

5. Steps 3 thru 6 as described in the previous list above.

3.2.5.2 Executor Process Start-up Problems

If the server has a problem creating an executor subprocess, the status codes relating to the

problem will be written to the server log.

Java.sql.SQLException: Unable to start process,

status: 0x56EC03C : substatus 65535

The status code shown is a VMS status code or an Rdb specific status code, see your

OpenVMS and Oracle Rdb documentation for more information on this status code.

The substatus indicates more information about the problem found.

Table 3–1 Subcode

Descriptions

lists the subcode values and their meanings.

Table 3-1 Subcode Descriptions

ubcode

Description

no more memory, check your quotas

unable to create command procedure in

rdb$jdbc_com: directory, either insufficient privilege

or access denied or there already exists an earlier

version of the file with the same name but created by

another user

problem in pathname pointed to by rdb$jdbc_com

logical name, invalid device specified

problem in pathname pointed to by rdb$jdbc_com

logical name, invalid directory specified

too many files open by server already, check your

quotas

disk full, check the disk pointed to by rdb$jdbc_com