LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Blogs > yyazici
User Name
Password

Notices

Rate this Entry

Arcserve r11.5 ingres db setup error

Posted 02-21-2007 at 05:30 AM by yyazici

hi
while i want to install Arcserve Brightstor r11.5 (for linux) on sles 9.3
i have successfully installed Arcserve first but when i run csetup (at the first time) it couldnt set up ingres..you see
install log :
how can i solve the problem thanks





Installing Terminal Monitor utility files...
Setting up the Ingres Intelligent DBMS...

This procedure will set up the following release of the Ingres
Intelligent DBMS:

II 3.0.2 (int.lnx/105)

to run on local host:

hostname

This Ingres instance will be owned by:

ingres

Re-linking iimerge...

Loading INGRES merged server program ...
Using Shared Libraries ...

Loading iimerge ...
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld:
skipping incompatible
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../libc.so when searching for -lc
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld:
skipping incompatible
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../libc.a when searching for -lc
/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/../../../../x86_64-suse-linux/bin/ld:
cannot find -lc
collect2: ld returned 1 exit status


-----------------------------------------------------------------------
| ***ERROR*** |
| |
| Cannot load the merged INGRES server program, iimerge. Please |
| correct the problem before running iilink again. |
| |

-----------------------------------------------------------------------

The command used to load this binary was:


cc -m32 -m32 -m32 -m32 -m32 -m32 -m32 -m32 -m32 -m32 -m32 -m32
-rdynamic -o /opt/CA/ingresii/ingres/bin/iimerge
/opt/CA/ingresii/ingres/lib/iimerge.o -L/opt/CA/ingresii/ingres/lib -lbecompat.1
-lscf.1 -lpsf.1 -lopf.1 -lrdf.1 -lqef.1 -lqsf.1 -ldbutil.1
-ltpf.1 -lrqf.1 -lgcf.1 -lsxf.1 -lcuf.1 -lgwf.1 -ldmf.1 -lulf.1
-ladf.1 /opt/CA/ingresii/ingres/lib/iiclsadt.o
/opt/CA/ingresii/ingres/lib/iiuseradt.o

WARNING:
Ingres Server executable could not be re-linked.
This may cause utilities such as ckpdb and rollforwarddb to fail for
users other than ingres.
Use the following command to do this by hand:

iilink -noudt


Generating default configuration...
/opt/CA/ingresii/ingres/utility/iircpseg: line 18: iishowres: command
not found

II_INSTALLATION configured as WV.

Ingres Location Variables
-------------------------
The Ingres storage locations and the corresponding Ingres variables
are listed below:

Ingres Variable Description
--------------- -----------
II_DATABASE Default location for database files
II_CHECKPOINT Default location for full backup snapshots
II_JOURNAL Default location for journals (backup audit
trails)
II_DUMP Default location for on-line backup change
logs
II_WORK Default location for temporary files


Important Note
--------------
You cannot change the values you assign to the default Ingres
storage location variables once this setup procedure has been
completed.
However you can create additional storage locations and assign
individual databases to them. For information on creating additional
storage locations, refer to the Ingres Database Administrator's Guide.


The Default Database Location
-----------------------------
The Ingres variable II_DATABASE stores the default location used to
store Ingres database files.

Once a value has been assigned to II_DATABASE, you can change it only
by removing and re-installing Ingres. Refer to the Ingres Database
Administrator's Guide for information on moving the default database
file location.


II_DATABASE configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/data...

Creating /opt/CA/ingresii/ingres/data/default...

The Default Checkpoint, Journal and Dump Locations
--------------------------------------------------
The Ingres variables II_CHECKPOINT, II_JOURNAL, and II_DUMP are
used to store the default locations used for full and incremental
on-line backup files. It is essential that II_CHECKPOINT, II_JOURNAL,
and II_DUMP not be assigned to the same physical device as
II_DATABASE. If this restriction is ignored, you will be unable to
recover lost data in the event that the II_DATABASE location fails.

Once assigned, the values of II_CHECKPOINT, II_JOURNAL, and II_DUMP
can only be changed by removing and re-installing Ingres.
Refer to the Ingres Database Administrator's Guide for
information on moving the default backup locations.

Refer to the chapter on "Backup and Recovery" in the Ingres
Database Administrator's Guide for instructions on backup and recovery
of Ingres databases.


II_CHECKPOINT configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/ckp...

Creating /opt/CA/ingresii/ingres/ckp/default...

II_JOURNAL configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/jnl...

Creating /opt/CA/ingresii/ingres/jnl/default...

II_DUMP configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/dmp...

Creating /opt/CA/ingresii/ingres/dmp/default...

The Default Work Location
-------------------------
The Ingres variable II_WORK stores the default location used for
all temporary files created during external sorts and other DBMS server
operations that require large amounts of temporary file space.
Ingres lets you designate a separate storage device as the default
location for these files.

When choosing the II_WORK location, be aware that temporary files tend
to increase fragmentation on storage devices, which can lead to
decreased performance. For this reason, you should assign II_WORK to a
physical device which does not contain database, checkpoint, journal,
or dump files, if possible. Your choice of the default work location
does not affect your ability to recover lost data in the event of a
storage device failure, although it may affect performance.

Once assigned, the value of II_WORK can only be changed by removing
and re-installing Ingres. Refer to the Ingres Database
Administrator's Guide for instructions on moving the default work
location
in this manner.


II_WORK configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/work...

Creating /opt/CA/ingresii/ingres/work/default...

Ingres Transaction Log Locations
--------------------------------
The Ingres Intelligent DBMS uses a transaction log file to store
uncommitted transactions and buffer committed transactions before they
are written to the database file location(s).

In order to guarantee that no committed transactions can be lost in
the event of a single storage device failure, a backup of the Ingres
transaction log should be maintained on a storage device which is
independent of the primary transaction log file device.

By default, Ingres will maintain a backup of the primary transaction
log file on a storage location which you select.

You have the option of disabling the backup transaction log file,
although you should only do so if the location you intend to use
for your primary transaction log file has built-in fault tolerance
(e.g. a fault-tolerant disk array or "mirrored" disk sub-system).



You must verify that the location(s) you intend to select for the
Ingres
transaction log(s) have sufficient disk space. The default transaction
log size is:

32768K bytes ( 32M bytes)

This setup procedure will create the Ingres transaction log(s) as
ordinary (operating system buffered) files, rather than unbuffered
("raw") device files. For information on using the "mkrawlog" utility
to create raw transaction log files after this setup procedure has been
completed, please refer to the Ingres Getting Started Guide.

/opt/CA/ingresii/ingres/utility/iircpseg: line 18: iishowres: command
not found

II_LOG_FILE configured as /opt/CA/ingresii

Creating /opt/CA/ingresii/ingres/log...

Ingres is configured to support 32 concurrent users.

The primary transaction log will now be created as an ordinary
(buffered)
system file. For information on how to create a "raw", or unbuffered,
transaction log, please refer to the Ingres Getting Started Guide,
after
completing this setup procedure.

Creating a 1024000K byte transaction log file...

0% 25% 50% 75% 100%
|||||||||||||||||||||||||||||||||||||||||||||||||||

Formatting the primary transaction log file...
/opt/CA/ingresii/ingres/utility/iisudbms: line 666: rcpconfig: command
not found

Unable to write the primary transaction log file header. You must
correct
the problem described above and re-run this setup program.

Setting up Ingres Networking...

The setup procedure for the following version of the Ingres Intelligent
DBMS:

II 3.0.2 (int.lnx/105)

must be completed up before Ingres Networking can be set up on this
host:

hostname

Setting up Application-By-Forms...
Creating ABF Directory...

The following directory will be used to store Application-By-Forms,
Vision
and VisionPro applications:

/opt/CA/ingresii/ingres/abf

This default location can be changed later by redefining the Ingres
variable ING_ABFDIR, using the command:

ingsetenv ING_ABFDIR <location>

This variable can also be defined in the Unix environment.


ING_ABFDIR configured as /opt/CA/ingresii/ingres/abf

Application-By-Forms setup complete.

Setting up Ingres C2 Security Auditing...

The configuration file is locked by another application (config.lck
exists).

application: Ingres Networking setup
host: hostname
user: ingres
time: Tue Feb 13 09:38:07 2007
pid: 18165

Setting up the Ingres Data Access Server...

The configuration file is locked by another application (config.lck
exists).

application: Ingres Networking setup
host: hostname
user: ingres
time: Tue Feb 13 09:38:07 2007
pid: 18165

Setting up the Ingres JDBC Server...

This procedure will set up the following version of Ingres JDBC Server:

II 3.0.2 (int.lnx/105)

to run on local host:

hostname


Generating default configuration...

Default configuration generated.

Ingres JDBC Server Listen Protocol is tcp_ip
Ingres JDBC Server Listen Port is WV7
Ingres JDBC Server has been successfully set up in this installation
with a startup count of zero. Please adjust the startup count and
check the
listen address with the cbf utility.






Cannot write to default ODBC configuraton path /usr/local/etc.
Writing instead to /opt/CA/ingresii/ingres/files/odbcinst.ini.
Successfully wrote ODBC configuration files
Setting up Replicator...
Creating RepServer Directories...

Replicator setup complete.

Setting up Ingres Star Distributed DBMS...

The setup procedures for the following version of Ingres Intelligent
DBMS and Ingres Networking:

II 3.0.2 (int.lnx/105)

must be completed up before Ingres Star Distributed DBMS can be set
up on host:

hostname

Setting up DTP for Tuxedo...
Creating $II_SYSTEM/ingres/files/tuxedo/
Setting up the Ingres Protocol Bridge...

This procedure will set up the following release of the Ingres
Protocol Bridge:

II 3.0.2 (int.lnx/105)

to run on local host:

hostname

This installation will be owned by:

ingres

II_INSTALLATION configured as WV.

Generating default configuration...
Ingres Protocol Bridge has been successfully set up in this
installation.

You can now use the "ingstart" command to start your Ingres client.
Refer to the Ingres Getting Started Guide for more information about
starting and using Ingres.
Posted in Uncategorized
Views 2913 Comments 0
« Prev     Main     Next »

  



All times are GMT -5. The time now is 07:02 PM.

Main Menu
Advertisement

My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration