<HTML
><HEAD
><TITLE
>The Installation Process</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
"><LINK
REL="HOME"
TITLE="Ingres II HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Preparing for the Installation"
HREF="prep.html"><LINK
REL="NEXT"
TITLE="Basic System and Database Administration"
HREF="admin.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Ingres II HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="prep.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="admin.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="INSTALL"
>5. The Installation Process</A
></H1
><P
>In this section, the actual installation of
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> takes place.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="START"
>5.1. Starting the Installation Program</A
></H2
><P
>In the following I will presume that you install directly from the CD
which is mounted under <TT
CLASS="FILENAME"
>/cdrom</TT
>.
Depending on whether you install the <SPAN
CLASS="ACRONYM"
>SDK</SPAN
> or the full
version of <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>, you have to start the installation
differently.</P
><P
>For the <SPAN
CLASS="ACRONYM"
>SDK</SPAN
>:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Log in as <EM
>ingres</EM
>.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>cd</B
> to
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres</TT
> if it is not
your home directory.</P
></LI
><LI
><P
>Unpack the <TT
CLASS="FILENAME"
>install</TT
>
subdirectory from the tar file.</P
></LI
><LI
><P
>Start the <B
CLASS="COMMAND"
>ingbuild</B
> program.</P
></LI
></OL
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ cd $II_SYSTEM/ingres
$ tar xf /cdrom/int_lnx/ingres.tar install
$ install/ingbuild
</PRE
></FONT
></TD
></TR
></TABLE
><P
>For the full version:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>Log in as <EM
>root</EM
>.</P
></LI
><LI
><P
>Start the installer.</P
></LI
></OL
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
># /cdrom/install.sh
</PRE
></FONT
></TD
></TR
></TABLE
><P
>In this latter case, you have to let the installer know the owner of
the installation (ingres), and the value of <TT
CLASS="ENVAR"
>II_SYSTEM</TT
>.
After that, <B
CLASS="COMMAND"
>install.sh</B
> starts <B
CLASS="COMMAND"
>ingbuild</B
>
for you.</P
><P
>From this point on, the installation process is the same for both
options.</P
><P
>On the starting screen of <B
CLASS="COMMAND"
>ingbuild</B
> you have to
specify the path to the tar file and select the type of install:
<SPAN
CLASS="GUIMENUITEM"
>Custom</SPAN
> or <SPAN
CLASS="GUIMENUITEM"
>Package</SPAN
>.
I suggest you go for <SPAN
CLASS="GUIMENUITEM"
>Custom Install</SPAN
>
to be able to choose exactly those elements you want to install.</P
><P
>After choosing <SPAN
CLASS="GUIMENUITEM"
>Custom Install</SPAN
>, a table on
the next screen shows all components of your <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>
version together with their respective sizes.
Because of common parts in different components, the sizes added up indicate
much more disk space than is really needed for the installation.</P
><P
>By default every component is set to be installed.
If you want to exclude some of them, write <TT
CLASS="CONSTANT"
>"No"</TT
>
in their <TT
CLASS="VARNAME"
>"Install?"</TT
> field.</P
><P
>You had previously decided if the default values for the "stable"
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variables were acceptable
for your installation.
If this is the case, you can choose <SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
>
here.
Remember that you can alter the value of <TT
CLASS="ENVAR"
>II_LOG_FILE</TT
> as well as
the size of the transaction log at any time later.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If this is your first <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> install,
you have the necessary space under
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres</TT
>
and the "stable" parameters' default values are OK, I suggest you choose
<SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
>.</P
></TD
></TR
></TABLE
></DIV
><P
>Therefore, let us see this option first.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="EXPRESS"
>5.2. Express Install</A
></H2
><P
>In the case of <SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
>, the installer
executes the following tasks:</P
><P
></P
><UL
><LI
><P
>It untars all chosen components from the
<TT
CLASS="FILENAME"
>ingres.tar</TT
> file to the
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres/install/tmp</TT
>
directory.</P
></LI
><LI
><P
>Checks the integrity of the components.</P
></LI
><LI
><P
>Puts the components in appropriate subdirectories under
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres</TT
>.</P
></LI
><LI
><P
>Sets the <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment
variables to their default values.</P
></LI
><LI
><P
>Starts <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>.</P
></LI
><LI
><P
>Creates the <SPAN
CLASS="DATABASE"
>iidbdb</SPAN
> database.</P
></LI
><LI
><P
>Takes a checkpoint of <SPAN
CLASS="DATABASE"
>iidbdb</SPAN
>.</P
></LI
><LI
><P
>Stops <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>.</P
></LI
><LI
><P
>Sets up those components that require this (<SPAN
CLASS="ACRONYM"
>ABF</SPAN
>,
Enhanced Security, etc).</P
></LI
></UL
><P
>If the installation process went OK, the program tells you that every
installed component is ready to use.
In the table on the screen the <TT
CLASS="VARNAME"
>"Install?"</TT
> column shows
<TT
CLASS="CONSTANT"
>"Ready"</TT
> for every selected component.</P
><P
><SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> is installed on your machine.
Jump to <A
HREF="install.html#COMPL"
>Completing the Initial Configuration</A
>.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="MANUAL"
>5.3. Manual Install</A
></H2
><P
>If you choose <SPAN
CLASS="GUIMENUITEM"
>Install</SPAN
> rather than
<SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
>, the installer untars
<TT
CLASS="FILENAME"
>ingres.tar</TT
>, checks the integrity of the components
and puts them in their respective directories.
Then it asks you if you want to setup these components now.</P
><P
>If you decide to do the setup later, the installer stops.
In the table containing the components the <TT
CLASS="VARNAME"
>"Install?"</TT
>
column shows <TT
CLASS="CONSTANT"
>"Not Set Up"</TT
> for every
selected component.
You can run <B
CLASS="COMMAND"
>ingbuild</B
> again at any time and choose one of
the options <SPAN
CLASS="GUIMENUITEM"
>Setup All</SPAN
> or
<SPAN
CLASS="GUIMENUITEM"
>Setup</SPAN
> to set up all or one of the components.
A component cannot be used until it has been set up.</P
><P
>Let us see what happens if you choose to set up the components.</P
><P
>First, you have to set up the <SPAN
CLASS="ACRONYM"
>DBMS</SPAN
> server.
On the screens to follow you will see a fair amount of explanatory text about
the parameters we have covered earlier.</P
><P
>During the setup phase, the installer prompts you for the values of
the <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variables and the other
necessary parameters:</P
><P
></P
><UL
><LI
><P
><TT
CLASS="ENVAR"
>II_INSTALLATION</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_DATABASE</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_CHECKPOINT</TT
>: if you set it to the same value
as <TT
CLASS="ENVAR"
>II_DATABASE</TT
>, the installer warns you of the dangers
of losing a database and its backup at the same time.
You have to repeat <TT
CLASS="ENVAR"
>II_CHECKPOINT</TT
>'s value for the
program to accept it.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_JOURNAL</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_DUMP</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_WORK</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_LOG_FILE</TT
>: the installer reminds you of
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>' capability of mirroring the
transaction log.
Naturally, it only makes sense if the mirrored log file is on a
different disk than the primary log file.
The installer asks you if you want to <EM
>disable</EM
>
dual logging.
Then you have to specify the size of the log (16 Mb by default,
make it bigger if you have free disk space as I suggested earlier).
After this you have to tell the installer where to put the primary
log file, and, if you did not switch off dual logging, the dual log
file (<TT
CLASS="ENVAR"
>II_DUAL_LOG</TT
>).</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_NUM_OF_PROCESSORS</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_TIMEZONE_NAME</TT
>.</P
></LI
><LI
><P
><TT
CLASS="ENVAR"
>II_CHARSET</TT
>.</P
></LI
><LI
><P
>Expected number of concurrent users.</P
></LI
><LI
><P
><SPAN
CLASS="ACRONYM"
>SQL-92</SPAN
> compatible databases.</P
></LI
></UL
><P
>At every prompt, enter the appropriate parameter's previously decided
value.</P
><P
>The installer may also ask you about other components you have chosen
to install.
Accept the defaults for these.</P
><DIV
CLASS="INFORMALTABLE"
><A
NAME="AEN902"
></A
><P
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><THEAD
><TR
><TH
WIDTH="100%"
ALIGN="CENTER"
VALIGN="TOP"
>Full Version
</TH
></TR
></THEAD
><TBODY
><TR
><TD
WIDTH="100%"
ALIGN="CENTER"
VALIGN="TOP"
>If you requested the installation of Net,
make <B
CLASS="COMMAND"
>ingbuild</B
> set it up.
Do not bother setting an <EM
>installation password</EM
>,
unless you know what it is: we will complete Net's
configuration later, in its own section (<A
HREF="net.html"
>Ingres/Net</A
>).
</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="COMPL"
>5.4. Completing the Initial Configuration</A
></H2
><P
>After an <SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
> (but perhaps after
a manual install as well), you may want to change the values of some of the
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variables.
You will see how to do this here.
Stay logged in as ingres.</P
><P
>You can view the current values of <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>
environment variables with the <B
CLASS="COMMAND"
>ingprenv</B
> command:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ ingprenv
</PRE
></FONT
></TD
></TR
></TABLE
><P
>You can change the value of any variable with the
<B
CLASS="COMMAND"
>ingsetenv</B
> command:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ ingsetenv II_TIMEZONE_NAME GMT1
</PRE
></FONT
></TD
></TR
></TABLE
><P
>In the example we set <TT
CLASS="ENVAR"
>II_TIMEZONE_NAME</TT
> to
<TT
CLASS="CONSTANT"
>GMT1</TT
> (Greenwich Mean Time + 1 hour),
which happens to be the time zone Hungary is placed in.
You can find all possible values for <TT
CLASS="ENVAR"
>II_TIMEZONE_NAME</TT
> in the
file <TT
CLASS="FILENAME"
>$II_SYSTEM/ingres/files/tz.crs</TT
> (look for the lists
beginning with the word <TT
CLASS="CONSTANT"
>VALID</TT
>).</P
><P
>You can change the value of any other <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>
environment variable in a similar way.
<B
CLASS="COMMAND"
>ingprenv</B
> and <B
CLASS="COMMAND"
>ingsetenv</B
> do not require a
running <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> server.</P
><P
>The <I
CLASS="CITETITLE"
>System Reference Guide</I
> contains the
description of every <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variable.
Let me mention two of those that we have not covered yet.</P
><P
><TT
CLASS="ENVAR"
>II_DATE_FORMAT</TT
> determines the display format of dates.
By default, its value is <TT
CLASS="CONSTANT"
>US</TT
> which provides the format
<TT
CLASS="CONSTANT"
>dd-mmm-yy</TT
>.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The setting of <TT
CLASS="ENVAR"
>II_DATE_FORMAT</TT
> has no effect on
the way dates are stored in the database.
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> always stores full date values,
century included.
Hence, you can change the setting of <TT
CLASS="ENVAR"
>II_DATE_FORMAT</TT
> without
the risk of corrupting data.
In order to avoid <SPAN
CLASS="ACRONYM"
>Y2K</SPAN
> problems in your applications,
you should use a date format that contains the century, such as
<TT
CLASS="CONSTANT"
>MULTINATIONAL4</TT
> (<TT
CLASS="CONSTANT"
>dd/mm/yyyy</TT
>)
or <TT
CLASS="CONSTANT"
>FINLAND</TT
> (<TT
CLASS="CONSTANT"
>yyyy-mm-dd</TT
>).
The latter seems especially proper under Linux :-)</P
></TD
></TR
></TABLE
></DIV
><P
>Another <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variable that
has a good chance to be changed from its default value is
<TT
CLASS="ENVAR"
>II_MONEY_FORMAT</TT
>.
This one is responsible for how values of money type are displayed.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Just like with dates, the value of <TT
CLASS="ENVAR"
>II_MONEY_FORMAT</TT
>
has no impact on the storage format of money columns.</P
></TD
></TR
></TABLE
></DIV
><P
><TT
CLASS="ENVAR"
>II_MONEY_FORMAT</TT
> consists of two parts: the first part
tells whether the currency sign precedes the amount (<TT
CLASS="CONSTANT"
>L</TT
>
= Leading or <TT
CLASS="CONSTANT"
>T</TT
> = Trailing), the second part describes
the currency itself (<TT
CLASS="CONSTANT"
>$</TT
>, <TT
CLASS="CONSTANT"
>DM</TT
>,
<TT
CLASS="CONSTANT"
>Ft</TT
>, etc.: this part is a string of maximum 4 characters).
The two parts are separated by a colon.
<TT
CLASS="ENVAR"
>II_MONEY_FORMAT</TT
> defaults to <TT
CLASS="CONSTANT"
>L:$</TT
>.</P
><P
>Only the ingres user is allowed to use <B
CLASS="COMMAND"
>ingsetenv</B
>,
since these <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variables apply to
the whole installation.
However, some <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> environment variables
(including <TT
CLASS="ENVAR"
>II_DATE_FORMAT</TT
> and <TT
CLASS="ENVAR"
>II_MONEY_FORMAT</TT
>)
can be overridden in the users' shell, via Linux variables of the same name.
You can check the <I
CLASS="CITETITLE"
>System Reference Guide</I
> about which
other variables fall into this category.</P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Be careful: <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> will not prevent
you from changing the value of any <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>
environment variable, including <TT
CLASS="ENVAR"
>II_DATABASE</TT
>,
<TT
CLASS="ENVAR"
>II_CHECKPOINT</TT
>, <TT
CLASS="ENVAR"
>II_CHARSET</TT
>, etc.
(the "stable" parameters as we saw earlier).
However, if you change one of these, prepare for the nastiest possible
consequences, the mildest one of which is that
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> will not run.</P
></TD
></TR
></TABLE
></DIV
><P
>You can find information on how to setup Net and <SPAN
CLASS="ACRONYM"
>ICE</SPAN
>
in separate sections (<A
HREF="net.html"
>Ingres/Net</A
>, and <A
HREF="ice.html"
>ICE</A
>,
respectively).</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="REINST"
>5.5. Re-installation</A
></H2
><P
>If you want to re-install <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> for
any reason, remember to do the following first:</P
><P
></P
><UL
><LI
><P
>Backup everything you need from
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres</TT
>
(user databases, source code of applications stored there, etc.).
Also backup any other databases you want to keep that are stored in
different locations.
You can use the <B
CLASS="COMMAND"
>unloaddb</B
> utility for creating
portable copies of databases.
On <B
CLASS="COMMAND"
>unloaddb</B
> see the <I
CLASS="CITETITLE"
>System Reference
Guide</I
>.</P
></LI
><LI
><P
>Stop <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>.</P
></LI
><LI
><P
>Remove everything under
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres</TT
>.
Also remove the contents of every other location where you stored any
part of any database.</P
></LI
></UL
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Databases that are not completely removed can cause problems
when you try to re-create them.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="COMMAND"
>5.6. Command Line Install (SDK)</A
></H2
><P
>For installing the <SPAN
CLASS="ACRONYM"
>SDK</SPAN
>, you can run
<B
CLASS="COMMAND"
>ingbuild</B
> in batch mode as well.
The easiest way to do an <SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
> is to start
<B
CLASS="COMMAND"
>ingbuild</B
> in the following way (logged in as ingres):</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ cd $II_SYSTEM/ingres
$ tar xf /cdrom/int_lnx/ingres.tar install
$ install/ingbuild -express /cdrom/int_lnx/ingres.tar
</PRE
></FONT
></TD
></TR
></TABLE
><P
>In this case a regular <SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
> takes
place without having to press another key.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="CLIINST"
>5.7. Client Installation (Full Version)</A
></H2
><P
>If you have the full <SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> version, you may
want to set up a client installation.
If your application will run on a different machine than the database
server, all you need on the application server is a client
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> installation.</P
><P
>For a client install, choose <SPAN
CLASS="GUIMENUITEM"
>PackageInstall</SPAN
>
in <B
CLASS="COMMAND"
>ingbuild</B
>, then mark
<SPAN
CLASS="GUIMENUITEM"
>"Ingres Networked Client"</SPAN
> to be installed.
After the installation has been finished, go to section <A
HREF="net.html"
>Ingres/Net</A
>
to set up Net.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="INSTLOG"
>5.8. The Installer's Log</A
></H2
><P
>No matter which type of install you have chosen (Express or Manual),
you can find all of <B
CLASS="COMMAND"
>ingbuild</B
>'s messages in
<TT
CLASS="FILENAME"
>$II_SYSTEM/ingres/files/install.log</TT
>.
I suggest you check this file after an
<SPAN
CLASS="GUIMENUITEM"
>Express Install</SPAN
> to see what happened during the
installation process.
On the other hand, if <B
CLASS="COMMAND"
>ingbuild</B
> stops with an error message,
also check this log for possible clues to the cause of the error.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="CHECK"
>5.9. Checking the Installation</A
></H2
><P
>After you have installed and configured
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
>, it is time to check if it works properly.
Supposing you are still logged in as ingres, start the
<SPAN
CLASS="APPLICATION"
>Ingres</SPAN
> system:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ ingstart
</PRE
></FONT
></TD
></TR
></TABLE
><P
>Create a new database:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ createdb test
</PRE
></FONT
></TD
></TR
></TABLE
><P
>Start the command line <SPAN
CLASS="ACRONYM"
>SQL</SPAN
> interface:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>$ sql test
</PRE
></FONT
></TD
></TR
></TABLE
><P
>Create a table, insert a row into it and query the table's contents:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>create table t1 (col1 char(10));
insert into t1 values ('abcde');
select * from t1;
\g
</PRE
></FONT
></TD
></TR
></TABLE
><P
>If everything went OK, you should see something like the following:</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>$ sql test
INGRES TERMINAL MONITOR Copyright (c) 1981, 1998 Computer Associates Intl, Inc.
Ingres Linux Version II 2.0/9808 (lnx.us5/95)libc6 login
Sun Oct 3 03:43:54 1999
continue
* create table t1 (col1 char(10));
* insert into t1 values ('abcde');
* select * from t1;
* \g
Executing . . .
(1 row)
col1
abcde
(1 row)
continue
*
</PRE
></FONT
></TD
></TR
></TABLE
><P
>You can leave <B
CLASS="COMMAND"
>sql</B
> with the command
<B
CLASS="COMMAND"
>\q</B
>.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="prep.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="admin.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Preparing for the Installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Basic System and Database Administration</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
