If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Installing DB2 V.8.1 on Redhat 8 !!!

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-20-04, 09:51
bollin99 bollin99 is offline
Registered User
 
Join Date: Sep 2002
Posts: 30
Installing DB2 V.8.1 on Redhat 8 !!!

HI

Trying to install DB2 v.8 in Redhat 8.

Encountering the folloiwing problem. Can you please advise ?

/db2/pe/db2/linux/install/db2jinst: line 131: 6015 Segmentation fault $JAVA_PATH/$JAVA_INTERPRETER $JAVA_OPTIONS -cp $JAVA_CLASSPATH $DB2SetupRun "$@" 2>/tmp/db2setup.err****nning


Thank You
Bollin99
Reply With Quote
  #2 (permalink)  
Old 04-21-04, 06:08
lahiru lahiru is offline
Registered User
 
Join Date: Apr 2004
Posts: 13
Hi,

I don't know a clue on this error but I have successfully installed UDB 8.1 on Redhat 2.1 Advanced Server with neccessary Kernal Upgrades. Why don't you check the supported OS versions for your UDB installation from IBM site.

Cheers
Lahiru
Reply With Quote
  #3 (permalink)  
Old 04-21-04, 08:13
msundaram msundaram is offline
Registered User
 
Join Date: Jun 2003
Location: Chennai
Posts: 26
Re: Installing DB2 V.8.1 on Redhat 8 !!!

I am not sure how far this info. helpful for linux 8.0. For the segmentation fault, Linux kernel parameters will help


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

Modifying kernel parameters (Linux)
Before installing DB2, you may want to update Linux kernel parameters. DB2 will automatically raise the IPC limits where necessary. You may still want to raise these limits depending on your particular needs.

Prerequisites

You must have root authority to modify kernel parameters.

Procedure

To update kernel parameters:


RedHat and SuSE
Systems using a 2.4.x series kernel have a default value for the message queue parameter (msgmni), which allows only a few simultaneous connections to DB2. Semaphore array parameters also have to be changed for DB2 to run successfully. To check shared memory segment, semaphore array, and message queue limits, issue the ipcs -l command.
The following is the output from the the ipcs -l command.

# ipcs -l

------ Shared Memory Limits --------
max number of segments = 4096 // SHMMNI
max seg size (kbytes) = 32768
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

------ Semaphore Limits --------
max number of arrays = 1024 // SEMMNI
max semaphores per array = 250
max semaphores system wide = 128000
max ops per semop call = 32
semaphore max value = 32767

------ Messages: Limits --------
max queues system wide = 1024 // MSGMNI
max size of message (bytes) = 65536
default max size of queue (bytes) = 16384 // MSGMAX

Modify the kernel parameters by adding the following entries to the default system control configuration file, /etc/sysctl.conf:

kernel.msgmni = 512
kernel.sem = 250 128000 32 1024

where max semaphores system wide = max number of arrays x max semaphores per array****n sysctl with -p parameter to load in sysctl settings from the default file /etc/sysctl.conf.

sysctl -p

The entries from the sysctl.conf file are read during startup by the network initialization script.

On some distributions you may be required to add sysctl -p in the one of the system initialization files (for example, rc.local) so that kernel parameters are set after each reboot.
__________________
MS
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On