ingstart [-iigcn | -dmfrcp | -dmfacp | -client | -rmcmd | -icesvr | [-iidbms|-iigcc|-iigcb|-iigcd|-iijdbc|-iistar|-oracle|-informix| -mssql|-sybase|-db2udb|-rdb|-rms [= config_name]]] [-cluster] [-node nodename] [-help]
Starts Enterprise Access for IBM DB2 UDB. Valid on UNIX and Windows only.
The file ingstart.log also exist under $II_SYSTEM/ingres/files (ou %II_SYSTEM%\ingres\files) but does not however includes some errors.
The CBF column Startup Count determines which will start in what numbers.
The configuration name deter with the configuration name of CDF.
If the DBMS Server is launched 2 times (that is, same configuration name), you should switch on the setting cache_sharing to avoid base failing.
Ingstart should be launched regularly.
It is feasible to add treatments that can be launched by ingstart before/after treatment. This can be done by adding *.ingstart.*.begin and ii.*.ingstart.*.end. in the file config.dat valued with program names, path adequating with the OS with which Ingres works. If one of these processing returns an error, ingstart itself will be in error.Moreover these resources are not documented and are drawn from a reading of the source code for ingstart.
Under Windows, many things are better if Ingres is started as service.
Ingres 2006 Release 2/ingstart Checking host "asterix" for system resources required to run Ingres 2006 Release 2... Your system has sufficient resources to run Ingres 2006 Release 2. Starting your Ingres 2006 Release 2 installation... Starting the Name Server... Allocating shared memory for Logging and Locking Systems... Starting the Recovery Server... II_DBMS_SERVER = 39553 Starting the Archiver Process... Starting DBMS Server (default)... II_DBMS_SERVER = 39556 Starting Net Server (default)... GCC Server = 39559 TCP_IP port = II (21528) Starting Data Access Server (default)... Starting the Visual DBA Remote Command Server... Ingres 2006 Release 2 installation successfully started.