Starting Ingres : ingstart

December 2016






Syntaxe Command


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]
-iigcb

Options

  • -iigcn : Starting the server name
  • -dmfrcp : Starting transaction management
  • -dmfacp : Starting management logging
  • -client :Starts only name server and Ingres / Net. For Windows only
  • -rmcmd: starting server Visual/DBA
  • -icesvr: Starting server ICE
  • -iidbms : Starting the Ingres engine. You can specify the configuration name (Optional).
  • -iigcc - Starting Ingres/Net. You can specify the configuration name (Optional).
  • - starting Sever Bridge (connection towards other SGBD). You can specify the configuration name (Optional).
  • -jjgcd- Starting Server DAS. You can specify the configuration name (Optional).
  • -iistar- Starting Server Star. You can specify the configuration name (Optional).
  • -informix : Starting server Enterprise Access for Informix. (For Unix and Windows only).
  • -mssql: Starting Server Enterprise Access for MSSQL. (For Unix and Windows only).
  • -oracle: Starting Server Enterprise for Oracle. (For Unix and Windows only).
  • -rdb: Starting Server Enterprise Access for RDB. For VMS only.
  • -rms: Starting Ingres RMS Access. For VMS only.
  • -sybase: Starting Server Enterprise Access for Sybase. For Unix and Windows only.
  • -db2udb: Starting Server Enterprise Access for IBM DB2 UDB. For Unix and Windows only.





Starts Enterprise Access for IBM DB2 UDB. Valid on UNIX and Windows only.
  • -cluster :starting Ingres on all nodes of a cluster. Only for cluster installation.
  • -node nodename : Start Ingres on one node of a cluster. Only for cluster installation.
  • -help :help for command

Note


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.


Example:

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.

Related :

This document entitled « Starting Ingres : ingstart » from CCM (ccm.net) is made available under the Creative Commons license. You can copy, modify copies of this page, under the conditions stipulated by the license, as this note appears clearly.