IDS 7.31UD7 on MP-RAS not able to initialize
Bill tried to initialize IDS 7.31UD7 under NCR MP-RAS 3.2 on a Dell T410 (migrating from an NCR 4455). oninit -iv always hung at "Allocating and attaching to shared memory" with no errors and no Informix segments visible in ipcs; it even got that far with an empty ONCONFIG. Suggestions included setting MULTIPROCESSOR=1 and NOAGE=1, raising BUFFERS/LOCKS, verifying environment, permissions and ownership, checking the shared-memory/semaphore kernel parameters in stune/mtune against the release notes, questioning whether MP-RAS is certified on Dell hardware, and searching old CDI archives for the unusual MP-RAS settings. Bill had already copied the 4455's kernel settings and tried the suggestions without success. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I am attempting to initialize 7.31UD7 on NCR MP-RAS 3.2 UNIX on a Dell T410.
This release was initially purchased for and installed and is currently
running on a NCR 4455 with MP-RAS 3.2 box. The Dell is setup to mirror the NCR
box down to the kernel stune, mtune parameters.
The problem is I get to here when running oninit -iv (as both informix:200
and/or root):
Checking group membership to determine server run modesucceeded
Reading configuration file '/home/informix/etc/onconfig.prod'...succeeded
Creating /INFORMIXTMP/.infxdirs ... succeeded
Creating infos file "/home/informix/etc/.infos.tms_prod" ...
"/home/informix/etc/.conf.tms_prod" ... succeeded
Writing to infos file ... succeeded
Checking config parameters...succeeded
Allocating and attaching to shared memory...
and it hangs ... as long as you will let it. No errors, no Informix shmem/semmi
per the "ipcs" command, just nothing. I have retried installing, etc but no go.
I am keep the onconfig as close to basic (non-production) as possible jsut to
get this online. I will reconfigure to meet production demands later.
I noticed by intentionally corrupting the onconfig (for testing) that is does
not throw errors if say the file is basically empty or invalid so that tells me
it might not be able to grab shared memory to load the config file for
reading/parsing.
sqlhosts, hosts, services are all set but i can post if it would help. The
thing here is lack of errors.
Any help is greatly appreciated!
Bill
ipcs looks like this when hung:
IPC status from /dev/kmem as of Wed Mar 16 10:43:17 2011
T ID KEY MODE OWNER GROUP
Message Queues:
q 0 0x390012d8 --rw------- root root
Shared Memory:
m 100 0x350012d8 -Crw-rw-rw- root root
Semaphores:
s 0 0x360012d8 --ra-ra-ra- root root
onconfig.prod is:
ROOTNAME rootdbs_prod # Root dbspace name
ROOTPATH /home/DB/r1dsk3 # Path for device containing root dbspace
ROOTOFFSET 2 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 20000 # Size of root dbspace (Kbytes)
MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
PHYSDBS rootdbs_prod # Location (dbspace) of physical log
PHYSFILE 1000 # Physical log file size (Kbytes)
LOGFILES 6 # Number of logical log files
LOGSIZE 500 # Logical log size (Kbytes)
MSGPATH /usr/informix/online.log # System message log file path
CONSOLE /dev/console # System console message path
ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program pathSYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program path
TBLSPACE_STATS 1
TAPEDEV /dev/null # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)
LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)STAGEBLOB # Informix Dynamic Server/Optical staging area
SERVERNUM 4 # Unique id corresponding to a Dynamic Server instance
DBSERVERNAME tms_prod # Name of default database serverDBSERVERALIASES tms_prod_net, tms_prod_net2 # List of alternate dbservernames
NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype
NETTYPE tlitcp,2,200,NET
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
NUMCPUVPS 1 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
LOCKS 2000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
NUMAIOVPS # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 6 # Maximum number of logical log files
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0x10000000L # Shared memory base address
SHMVIRTSIZE 8000 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 8 # Number of LRU queues
LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
LTXHWM 50 # Long transaction high water mark percentage
LTXEHWM 60 # Long transaction high water mark (exclusive)
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
OFF_RECVRY_THREADS 10 # Default number of offline worker threads
ON_RECVRY_THREADS 1 # Default number of online worker threads
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path
CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)
CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes)CDR_LOGDELTA 30 # % of log space allowed in queue memory
CDR_NUMCONNECT 16 # Expected connections per server
CDR_NIFRETRY 300 # Connection retry (seconds)
CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in /tmp please
BAR_DEBUG_LOG /usr/informix/bar_dbug.log # ON-Bar Debug Log - not in /tmpplease
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
ISM_DATA_POOL ISMData # If the data pool name is changed, be sure to
ISM_LOG_POOL ISMLogs
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
DBSPACETEMP # Default temp dbspaces
DUMPDIR /tmp # Preserve diagnostics in this directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image using 'gcore'
DUMPCORE 0 # Dump a core image (Warning:this aborts Dynamic Server)
DUMPCNT 1 # Number of shared memory or gcore dumps for
# a single user's session
FILLFACTOR 90 # Fill factor for building indexes
USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)
MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
DS_MAX_QUERIES # Maximum number of decision support queries
DS_TOTAL_MEMORY # Decision support memory (Kbytes)
DS_MAX_SCANS 1048576 # Maximum number of decision support scans
DATASKIP # List of dbspaces to skip
OPTCOMPIND 2 # To hint the optimizer
ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 = WAITLBU_PRESERVE 0 # Preserve last log for log backup
OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
HETERO_COMMIT 0
OPT_GOAL -1
DIRECTIVES 1
RESTARTABLE_RESTORE ON
Couple of problems, I don't know how well the MP-RAS 3.2 is supposed to run
on Dell hardware rather than the original Teradata boxes, so I can't comment
on compatibility there. However, I do see some problems with the Informix
configuration. The Dell T410 is a dual socket motherboard and I assume if
you purchased it recently that there are at least two cores per socket (the
default processor for this box, Xeon 5620, is a four core per socket
processor).
However, your configuration shows:
MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
MULTIPROCESSOR should be set to '1' if there are more than a single
processor core (on a single processor chip) in the machine. Otherwise
certain locks and latches will be disabled that prevent concurrent access to
shared memory structures by multiple tasks and threads which is possible if
there are more than one core. This may be the cause of the hang during
server initialization.
NOAGE 0 # Process aging
This has nothing to do with the hang at startup, and I don't know about
MP-RAS, but most UNIX based OSes are agressive about reducing the runtime
priority of long running processes and the Informix engine's oninit
processes are certainly long running by any measure. You should have NOAGE
set to '1'. The release notes files will tell you whether NOAGE is
supported on MP-RAS, but supported or not, it can't hurt to enable this
feature.
LOCKS 2000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
Again, nothing to do with the hang, but, are you really configuring a
production server with only 2000 locks and 200 buffers? Only if there are
fewer than a dozen users and less than 4MB of data on disk! You REALLY
should resize these parameters to something realistic.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Wed, Mar 16, 2011 at 1:23 PM, BILL FLORENCE <spider348@hotmail.com>wrote:
> I am attempting to initialize 7.31UD7 on NCR MP-RAS 3.2 UNIX on a Dell
> T410.
> This release was initially purchased for and installed and is currently
> running on a NCR 4455 with MP-RAS 3.2 box. The Dell is setup to mirror the
> NCR
> box down to the kernel stune, mtune parameters.
>
> The problem is I get to here when running oninit -iv (as both informix:200
> and/or root):
>
> Checking group membership to determine server run modesucceeded
> Reading configuration file '/home/informix/etc/onconfig.prod'...succeeded
> Creating /INFORMIXTMP/.infxdirs ... succeeded
> Creating infos file "/home/informix/etc/.infos.tms_prod" ...
> "/home/informix/etc/.conf.tms_prod" ... succeeded
> Writing to infos file ... succeeded
> Checking config parameters...succeeded
> Allocating and attaching to shared memory...
>
> and it hangs ... as long as you will let it. No errors, no Informix
> shmem/semmi
> per the "ipcs" command, just nothing. I have retried installing, etc but no
> go.
> I am keep the onconfig as close to basic (non-production) as possible jsut
> to
> get this online. I will reconfigure to meet production demands later.
>
> I noticed by intentionally corrupting the onconfig (for testing) that is
> does
> not throw errors if say the file is basically empty or invalid so that
> tells
> me
> it might not be able to grab shared memory to load the config file for
> reading/parsing.
>
> sqlhosts, hosts, services are all set but i can post if it would help. The
> thing here is lack of errors.
>
> Any help is greatly appreciated!
>
> Bill
>
> ipcs looks like this when hung:
>
> IPC status from /dev/kmem as of Wed Mar 16 10:43:17 2011
> T ID KEY MODE OWNER GROUP
> Message Queues:
> q 0 0x390012d8 --rw------- root root
> Shared Memory:
> m 100 0x350012d8 -Crw-rw-rw- root root
> Semaphores:
> s 0 0x360012d8 --ra-ra-ra- root root
>
> onconfig.prod is:
>
> ROOTNAME rootdbs_prod # Root dbspace name
> ROOTPATH /home/DB/r1dsk3 # Path for device containing root dbspace
> ROOTOFFSET 2 # Offset of root dbspace into device (Kbytes)
> ROOTSIZE 20000 # Size of root dbspace (Kbytes)>
> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH # Path for device containing mirrored root
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
> PHYSDBS rootdbs_prod # Location (dbspace) of physical log
> PHYSFILE 1000 # Physical log file size (Kbytes)
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 500 # Logical log size (Kbytes)>
> MSGPATH /usr/informix/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path> SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS 1
>
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)
>
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)> STAGEBLOB # Informix Dynamic Server/Optical staging area
>
> SERVERNUM 4 # Unique id corresponding to a Dynamic Server instance
> DBSERVERNAME tms_prod # Name of default database server> DBSERVERALIASES tms_prod_net, tms_prod_net2 # List of alternate
> dbservernames
> NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype
> NETTYPE tlitcp,2,200,NET
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
>
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors
>
> LOCKS 2000 # Maximum number of locks
> BUFFERS 200 # Maximum number of shared buffers
> NUMAIOVPS # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 6 # Maximum number of logical log files
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0x10000000L # Shared memory base address
> SHMVIRTSIZE 8000 # initial virtual shared memory segment size
> SHMADD 8192 # Size of new shared memory segments (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 8 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark percentage
> LTXEHWM 60 # Long transaction high water m
Art,
re. the buffers and locks low numbers - yes, I agree, however they were left
that way (low) on purpose. Reasoning is I am only trying to get the server
'up' and do not want to introduce other potential issues. At one time we did
try with actual production values (larger) but it still hung. I will
re-configure and/or re-initialize later.
re. You are correct about the Dell hardware. NCR MP-RAS is on it and "running"
albiet this is a new venture. I originally had the multiprocessor = 1 but last
iteration was 0 as seen in my config - great suggestion though.
I set both your suggestions and retried but still hangs....
no shared memory is being allocated per ipcs - arg.
I was not able to find machine notes or much at all regarding Dell T410 and
Informix with MP-RAS so I am not sure where to go from here.
Is it possible this proof of concept will end here because of hardware
differences?
Any other suggestions , opinions ?
Thanks,
Bill
Couple of problems, I don't know how well the MP-RAS 3.2 is supposed to run
on Dell hardware rather than the original Teradata boxes, so I can't comment
on compatibility there. However, I do see some problems with the Informix
configuration. The Dell T410 is a dual socket motherboard and I assume if
you purchased it recently that there are at least two cores per socket (the
default processor for this box, Xeon 5620, is a four core per socket
processor).
However, your configuration shows:
MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
MULTIPROCESSOR should be set to '1' if there are more than a single
processor core (on a single processor chip) in the machine. Otherwise
certain locks and latches will be disabled that prevent concurrent access to
shared memory structures by multiple tasks and threads which is possible if
there are more than one core. This may be the cause of the hang during
server initialization.
NOAGE 0 # Process aging
This has nothing to do with the hang at startup, and I don't know about
MP-RAS, but most UNIX based OSes are agressive about reducing the runtime
priority of long running processes and the Informix engine's oninit
processes are certainly long running by any measure. You should have NOAGE
set to '1'. The release notes files will tell you whether NOAGE is
supported on MP-RAS, but supported or not, it can't hurt to enable this
feature.
LOCKS 2000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
Again, nothing to do with the hang, but, are you really configuring a
production server with only 2000 locks and 200 buffers? Only if there are
fewer than a dozen users and less than 4MB of data on disk! You REALLY
should resize these parameters to something realistic.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
I guess the key here is I am not able to get to the point where the instance
gets as far a reading/parsing the config file...in other words I can point
$ONCONFIG to an empty file ...run oninit -iv and get this far as well...
This action will initialize Informix Dynamic Server;
any existing Informix Dynamic Server databases will NOT be accessible -
Do you wish to continue (y/n)? y
Checking group membership to determine server run modesucceeded
Reading configuration file '/home/informix/etc/onconfig.junk'...succeeded
Creating /INFORMIXTMP/.infxdirs ... succeeded
Creating infos file "/home/informix/etc/.infos.viper4" ...
"/home/informix/etc/.conf.viper4" ... succeeded
Writing to infos file ... succeeded
Checking config parameters...succeeded
Allocating and attaching to shared memory...
Baffled - anyone have ideas ?
Thanks
Yeesh!
- Does NCR certify MP-RAS to run on the Dell box? (If neither company
certifies it......)
- Are there drivers from Dell or NCR to specifically run MP-RAS on this box?
(could affect SHM access)
- Before you start the db, can you view $INFORMIXDIR/etc/$ONCONFIG ok? (is the
environment good)?
- Are all the permissions and ownership under $INFORMIXDIR and subdirectories
correct? Especially $INFORMIXDIR/bin/
Just asking.
Bob
----- Original Message -----
From: "BILL FLORENCE" <spider348@hotmail.com>
To: ids@iiug.org
Sent: Wednesday, March 16, 2011 3:12:11 PM
Subject: Re: IDS 7.31UD7 on MP-RAS not able to initialize [23116]
Art,
re. the buffers and locks low numbers - yes, I agree, however they were left
that way (low) on purpose. Reasoning is I am only trying to get the server
'up' and do not want to introduce other potential issues. At one time we did
try with actual production values (larger) but it still hung. I will
re-configure and/or re-initialize later.
re. You are correct about the Dell hardware. NCR MP-RAS is on it and "running"
albiet this is a new venture. I originally had the multiprocessor = 1 but last
iteration was 0 as seen in my config - great suggestion though.
I set both your suggestions and retried but still hangs....
no shared memory is being allocated per ipcs - arg.
I was not able to find machine notes or much at all regarding Dell T410 and
Informix with MP-RAS so I am not sure where to go from here.
Is it possible this proof of concept will end here because of hardware
differences?
Any other suggestions , opinions ?
Thanks,
Bill
Couple of problems, I don't know how well the MP-RAS 3.2 is supposed to run
on Dell hardware rather than the original Teradata boxes, so I can't comment
on compatibility there. However, I do see some problems with the Informix
configuration. The Dell T410 is a dual socket motherboard and I assume if
you purchased it recently that there are at least two cores per socket (the
default processor for this box, Xeon 5620, is a four core per socket
processor).
However, your configuration shows:
MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
MULTIPROCESSOR should be set to '1' if there are more than a single
processor core (on a single processor chip) in the machine. Otherwise
certain locks and latches will be disabled that prevent concurrent access to
shared memory structures by multiple tasks and threads which is possible if
there are more than one core. This may be the cause of the hang during
server initialization.
NOAGE 0 # Process aging
This has nothing to do with the hang at startup, and I don't know about
MP-RAS, but most UNIX based OSes are agressive about reducing the runtime
priority of long running processes and the Informix engine's oninit
processes are certainly long running by any measure. You should have NOAGE
set to '1'. The release notes files will tell you whether NOAGE is
supported on MP-RAS, but supported or not, it can't hurt to enable this
feature.
LOCKS 2000 # Maximum number of locks
BUFFERS 200 # Maximum number of shared buffers
Again, nothing to do with the hang, but, are you really configuring a
production server with only 2000 locks and 200 buffers? Only if there are
fewer than a dozen users and less than 4MB of data on disk! You REALLY
should resize these parameters to something realistic.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I would check your environment, as the onconfig has been processed
and validated.
Checking config parameters...succeeded
It is trying to allocated shared memory now. I would also check your
kernel parameters, specifically those relating to shared memory and
semaphores.
John F. Miller III
STSM, Embedability Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 03/16/2011 12:46:47 PM:
> [image removed]
>
> Re: IDS 7.31UD7 on MP-RAS not able to initialize [23117]
>
> BILL FLORENCE
>
> to:
>
> ids
>
> 03/16/2011 12:47 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids
>
> I guess the key here is I am not able to get to the point where the
instance
> gets as far a reading/parsing the config file...in other words I can
point
> $ONCONFIG to an empty file ...run oninit -iv and get this far as well...
>
> This action will initialize Informix Dynamic Server;
> any existing Informix Dynamic Server databases will NOT be accessible -
> Do you wish to continue (y/n)? y
> Checking group membership to determine server run modesucceeded
> Reading configuration file '/home/informix/etc/onconfig.junk'...succeeded
> Creating /INFORMIXTMP/.infxdirs ... succeeded
> Creating infos file "/home/informix/etc/.infos.viper4" ...
> "/home/informix/etc/.conf.viper4" ... succeeded
> Writing to infos file ... succeeded
> Checking config parameters...succeeded
> Allocating and attaching to shared memory...
>
> Baffled - anyone have ideas ?
>
> Thanks
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Hey John,
I know the onconfig is being validated for ownership and permissions, I can
break that in testing but I can also get to the same point with a properly
permission empty onconfig file...
The oninit process just does not grab any shared memory for Informix.
We had the kernel parameters set like they are on the NCR 4455 since it
was not working (same issue) as the default parameters but still no luck.
Thanks for your help and please let me know if you think of anything else.
--Bill
I would check your environment, as the onconfig has been processed
and validated.
Checking config parameters...succeeded
It is trying to allocated shared memory now. I would also check your
kernel parameters, specifically those relating to shared memory and
semaphores.
John F. Miller III
STSM, Embedability Architect
miller3@us.ibm.com
503-578-5645 begin_of_the_skype_highlighting 503-578-5645
Bob, Good questions - no known additional drivers just the OS disk - Not able to find out if NCR certify that OS on Dell - the one who got us the box said it was certified....hmmmm. Yes, the EV's are properly owned/perm-ed. I think it is more related to the inability for Informix to grab shared memory since it hangs on that step. I can point it to an empty ONCONFIG file and it gets to same spot with no error ... possible the kernel is not allowing shared memory to be grabbed/owned by others ? however initializing as 'root' did not fix this either. Any feedback is appreciated. Thanks, Bill Yeesh! - Does NCR certify MP-RAS to run on the Dell box? (If neither company certifies it......) - Are there drivers from Dell or NCR to specifically run MP-RAS on this box? (could affect SHM access) - Before you start the db, can you view $INFORMIXDIR/etc/$ONCONFIG ok? (is the environment good)? - Are all the permissions and ownership under $INFORMIXDIR and subdirectories correct? Especially $INFORMIXDIR/bin/ Just asking. Bob
Hi Bill, It's been years since I messed with mp-ras, but by any chance did both the mtune and stune files get updated to meet or exceed the kernel parameters in the release notes ? Everything here points to a kernel setup issue. -Mark Sent from my iPad On Mar 16, 2011, at 7:57 PM, BILL FLORENCE <spider348@hotmail.com> wrote: > Bob, > > Good questions - no known additional drivers just the OS disk - > Not able to find out if NCR certify that OS on Dell - the one who got us the > box said it was certified....hmmmm. > > Yes, the EV's are properly owned/perm-ed. > I think it is more related to the inability for Informix to grab shared memory > since it hangs on that step. I can point it to an empty ONCONFIG file and it > gets to same spot with no error ... possible the kernel is not allowing shared > memory to be grabbed/owned by others ? however initializing as 'root' did not > fix this either. Any feedback is appreciated. > > Thanks, > > Bill > > Yeesh! > > - Does NCR certify MP-RAS to run on the Dell box? (If neither company > certifies it......) > - Are there drivers from Dell or NCR to specifically run MP-RAS on this box? > (could affect SHM access) > - Before you start the db, can you view $INFORMIXDIR/etc/$ONCONFIG ok? (is the > environment good)? > - Are all the permissions and ownership under $INFORMIXDIR and subdirectories > correct? Especially $INFORMIXDIR/bin/ > > Just asking. > > Bob > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Hey Mark, Yes, we setup the stune, mtune to be the same as those on the old NCR 4455 box, since Informix would not initialize with the kernel with default values. Thanks, Bill Hi Bill, It's been years since I messed with mp-ras, but by any chance did both the mtune and stune files get updated to meet or exceed the kernel parameters in the release notes ? Everything here points to a kernel setup issue. -Mark
Wow didn't think MP-RAS still existed.
If you search the CDI archives from around 1999/2000 then I know I was
building a lot of MP-RAS/7.3x servers. You need/needed some very
'strange' settings - hopefully there is something there
Cheers
Paul
> I am attempting to initialize 7.31UD7 on NCR MP-RAS 3.2 UNIX on a Dell
> T410.
> This release was initially purchased for and installed and is currently
> running on a NCR 4455 with MP-RAS 3.2 box. The Dell is setup to mirror the
> NCR
> box down to the kernel stune, mtune parameters.
>
> The problem is I get to here when running oninit -iv (as both informix:200
> and/or root):
>
> Checking group membership to determine server run modesucceeded
> Reading configuration file '/home/informix/etc/onconfig.prod'...succeeded
> Creating /INFORMIXTMP/.infxdirs ... succeeded
> Creating infos file "/home/informix/etc/.infos.tms_prod" ...
> "/home/informix/etc/.conf.tms_prod" ... succeeded
> Writing to infos file ... succeeded
> Checking config parameters...succeeded
> Allocating and attaching to shared memory...
>
> and it hangs ... as long as you will let it. No errors, no Informix
> shmem/semmi
> per the "ipcs" command, just nothing. I have retried installing, etc but
> no
> go.
> I am keep the onconfig as close to basic (non-production) as possible jsut
> to
> get this online. I will reconfigure to meet production demands later.
>
> I noticed by intentionally corrupting the onconfig (for testing) that is
> does
> not throw errors if say the file is basically empty or invalid so that
> tells
> me
> it might not be able to grab shared memory to load the config file for
> reading/parsing.
>
> sqlhosts, hosts, services are all set but i can post if it would help. The
> thing here is lack of errors.
>
> Any help is greatly appreciated!
>
> Bill
>
> ipcs looks like this when hung:
>
> IPC status from /dev/kmem as of Wed Mar 16 10:43:17 2011
> T ID KEY MODE OWNER GROUP
> Message Queues:
> q 0 0x390012d8 --rw------- root root
> Shared Memory:
> m 100 0x350012d8 -Crw-rw-rw- root root
> Semaphores:
> s 0 0x360012d8 --ra-ra-ra- root root
>
> onconfig.prod is:
>
> ROOTNAME rootdbs_prod # Root dbspace name
> ROOTPATH /home/DB/r1dsk3 # Path for device containing root dbspace
> ROOTOFFSET 2 # Offset of root dbspace into device (Kbytes)
> ROOTSIZE 20000 # Size of root dbspace (Kbytes)>
> MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH # Path for device containing mirrored root
> MIRROROFFSET 0 # Offset into mirrored device (Kbytes)>
> PHYSDBS rootdbs_prod # Location (dbspace) of physical log
> PHYSFILE 1000 # Physical log file size (Kbytes)
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 500 # Logical log size (Kbytes)>
> MSGPATH /usr/informix/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path> SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS 1
>
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)
>
> LTAPEDEV /dev/null # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)> STAGEBLOB # Informix Dynamic Server/Optical staging area
>
> SERVERNUM 4 # Unique id corresponding to a Dynamic Server instance
> DBSERVERNAME tms_prod # Name of default database server> DBSERVERALIASES tms_prod_net, tms_prod_net2 # List of alternate
> dbservernames
> NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype
> NETTYPE tlitcp,2,200,NET
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
>
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors
>
> LOCKS 2000 # Maximum number of locks
> BUFFERS 200 # Maximum number of shared buffers
> NUMAIOVPS # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 6 # Maximum number of logical log files
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0x10000000L # Shared memory base address
> SHMVIRTSIZE 8000 # initial virtual shared memory segment size
> SHMADD 8192 # Size of new shared memory segments (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 8 # Number of LRU queues
> LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark percentage
> LTXEHWM 60 # Long transaction high water mark (exclusive)
> TXTIMEOUT 300 # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)
>
> OFF_RECVRY_THREADS 10 # Default number of offline worker threads
> ON_RECVRY_THREADS 1 # Default number of online worker threads
>
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path>
> CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)
> CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
> CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
> CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes)> CDR_LOGDELTA 30 # % of log space allowed in queue memory
> CDR_NUMCONNECT 16 # Expected connections per server
> CDR_NIFRETRY 300 # Connection retry (seconds)
> CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
> BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in /tmp> please
> BAR_DEBUG_LOG /usr/informix/bar_dbug.log # ON-Bar Debug Log - not in /tmp
> please
> BAR_MAX_BACKUP 0
> BAR_RETRY 1
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 31>
> ISM_DATA_POOL ISMData # If the data pool name is changed, be sure to
> ISM_LOG_POOL ISMLogs
>
> RA_PAGES # Number of pages to attempt to read ahead
> RA_THRESHOLD # Number of pages left before next group
>
> DBSPACETEMP # Default temp dbspaces
>
> DUMPDIR /tmp # Preserve diagnostics in this directory
> DUMPSHMEM 1 # Dump a copy of shared memory
> DUMPGCORE 0 # Dump a core image using 'gcore'
> DUMPCORE 0 # Dump a core image (Warning:this aborts Dynamic Server)
> DUMPCNT 1 # Number of shared memory or gcore dumps for>
> # a single user's session
>
> FILLFACTOR 90 # Fill factor for building indexes
>
> USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)
>
> MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
> DS_MAX_QUERIES # Maximum number of decision support queries
> DS_TOTAL_MEMORY # Decision support memory (Kbytes)
> DS_MAX_