rootdbs size
Upgrading from 9.40 (HP-UX) to 11.1 on RHEL/VMware, the poster's oninit -I kept failing with "Not enough room in ROOT DBspace" and demands for ever-larger ROOTSIZE, seemingly wanting physdbs as big as rootdbs. The cause: the onconfig was carried over from 9.4 and still had PHYSDBS, which 11.1 no longer supports, so the physical log (plus logical logs) had to fit inside rootdbs at initialization. Advice: drop PHYSDBS, set PHYSFILE/LOGSIZE small so everything fits in rootdbs, then once the server is online create a separate dbspace and use onparams to move and resize the physical log.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
We are trying to initialize our 11.1FC3 install on RHEL 5 as part of an
upgrade to a VMware server and from an existing HP/UX-9.4 environment.
We are using raw devices for our chunks.
Based on our 9.4 installed, I created chunks for rootdbs of 350MB and a
chunk for physdbs of 100MB. The onconfig values were 358400 & 102400
respectively.
When we did oninit -I, we received the following error in the log:
12:36:02 oninit: Not enough room in ROOT DBspace.
Requested 605198K, ONCONFIG value 'ROOTSIZE' 300000K.
So I made a 650MB chunk for rootdbs and did another oninit -I and
received a message about physdbs needing to be the same size as rootdbs.
I made a 650MB chunk for physdbs and did another oninit -I and received
this message. We also changed the onconfig values to 614400 since that
is what the message originally told us it wanted and wanted physdbs to
match rootdbs.
12:44:33 oninit: Not enough room in ROOT DBspace.
Requested 1127438K, ONCONFIG value 'ROOTSIZE' 614400K
What are we not getting right and why does 11.1 want the physdbs to be
the same size as the rootdbs?
Thanks,
Randy
Just out of curiousity did you copy you onconfig file? The number of logical
logs files may be getting created in the root dbspace.
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Kennedy,
Randy
Sent: Wednesday, November 17, 2010 2:09 PM
To: ids@iiug.org
Subject: rootdbs size [21971]
We are trying to initialize our 11.1FC3 install on RHEL 5 as part of an
upgrade to a VMware server and from an existing HP/UX-9.4 environment.
We are using raw devices for our chunks.
Based on our 9.4 installed, I created chunks for rootdbs of 350MB and a
chunk for physdbs of 100MB. The onconfig values were 358400 & 102400
respectively.
When we did oninit -I, we received the following error in the log:
12:36:02 oninit: Not enough room in ROOT DBspace.
Requested 605198K, ONCONFIG value 'ROOTSIZE' 300000K.
So I made a 650MB chunk for rootdbs and did another oninit -I and
received a message about physdbs needing to be the same size as rootdbs.
I made a 650MB chunk for physdbs and did another oninit -I and received
this message. We also changed the onconfig values to 614400 since that
is what the message originally told us it wanted and wanted physdbs to
match rootdbs.
12:44:33 oninit: Not enough room in ROOT DBspace.
Requested 1127438K, ONCONFIG value 'ROOTSIZE' 614400K
What are we not getting right and why does 11.1 want the physdbs to be
the same size as the rootdbs?
Thanks,
Randy
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Unless I am missing something here you are trying to oninit -i and are using
the PHYSDBS parameter to locate your Physical log. In ver 11, we no longer use
PHYSDBS so your physical log will have to fit inside of your rootdbs along
with everything else. Make it small, lose the PHYSDBS parameter and move plog
once you are online and add another dbspace for it.
Just for the heck of it, post the entire ONCONFIG file.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
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, Nov 17, 2010 at 3:09 PM, Kennedy, Randy
<RKennedy@scottsdaleaz.gov>wrote:
> We are trying to initialize our 11.1FC3 install on RHEL 5 as part of an
> upgrade to a VMware server and from an existing HP/UX-9.4 environment.
> We are using raw devices for our chunks.
>
> Based on our 9.4 installed, I created chunks for rootdbs of 350MB and a
> chunk for physdbs of 100MB. The onconfig values were 358400 & 102400
> respectively.
>
> When we did oninit -I, we received the following error in the log:
> 12:36:02 oninit: Not enough room in ROOT DBspace.
>
> Requested 605198K, ONCONFIG value 'ROOTSIZE' 300000K.
>
> So I made a 650MB chunk for rootdbs and did another oninit -I and
> received a message about physdbs needing to be the same size as rootdbs.
>
> I made a 650MB chunk for physdbs and did another oninit -I and received
> this message. We also changed the onconfig values to 614400 since that
> is what the message originally told us it wanted and wanted physdbs to
> match rootdbs.
> 12:44:33 oninit: Not enough room in ROOT DBspace.
>
> Requested 1127438K, ONCONFIG value 'ROOTSIZE' 614400K
>
> What are we not getting right and why does 11.1 want the physdbs to be
> the same size as the rootdbs?
>
> Thanks,
> Randy
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf3054acd5a91790049546441c
The hardware is, according to RHEL within the VM, Dual Xeon X5660 2.8GHz
( 6 core, 12MB cache) with 6GB memory using SAN space for dbspace
storage. The box's only purpose is the Informix DB and we are primarily
a OLTP environment, but at night we do many DSS style batch jobs via
cron.
This was crafted based on our current 9.4 onconfig and looking at the
onconfig.std from 11.1, we now realize the physlog and logical logs will
be created within rootdbs upon initialization and then they will be
changed to different size and dbspace.
#***********************************************************************
***
# INFORMIX SOFTWARE, INC.
# Title: onconfig (for 11.1)
# Description: INFORMIX-OnLine Configuration Parameters
#***********************************************************************
***
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace name
ROOTPATH /db/links/rootdbs # Path for devicecontaining root dbspace
ROOTOFFSET 0 # Offset of rootdbspace into device (Kbytes)
ROOTSIZE 102400 # Size of root
dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes
= 1, No = 0)
MIRRORPATH # Path for devicecontaining mirrored root
MIRROROFFSET 0 # Offset into mirrored
device (Kbytes)
# Physical Log Configuration
PHYSDBS physdbs # Location (dbspace)
of physical log
PHYSFILE 102400 # Physical log file
size (Kbytes)
PHYSBUFF 128 # Physical log buffer
size (Kbytes)
# Logical Log Configuration
LOGFILES 3 # Number of logicallog files
LOGSIZE 10240 # Logical log size
(Kbytes)
LOG_BACKUP_MODE CONT
DYNAMIC_LOGS 2 # Add logical logsfiles dynamically/automatically - newly added for 11.1
LOGBUFF 64 # Logical log buffer
size (Kbytes)
# Long Transaction Rollback
LTXHWM 70 # Long transactionhigh water mark percentage
LTXEHWM 80 # Long transactionhigh water mark (exclusive)
#Tblspace tblspace in Root dbspace
TBLTBLFIRST 0 # First extent size
(Kbytes) (0 = default)
TBLTBLNEXT 0 # Next extent size
(Kbytes) (0 = default)
TBLSPACE_STATS 1
# Diagnostics
MSGPATH /i11.1FC3/online.log # System message logfile path
CONSOLE /dev/console # System consolemessage path
ALARMPROGRAM /db/scripts/no_log.sh # Alarm program path
# System Archive Tape Device
TAPEDEV /remote/recovery/informix/level0 # Tape device path
TAPEBLK 16 # Tape block size
(Kbytes)
TAPESIZE 30720000 # Maximum amount ofdata to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /remote/recovery/informix/log1 # Log tape device
path
LTAPEBLK 16 # Log tape block size
(Kbytes)
LTAPESIZE 460800 # Max amount of datato put on log tape (Kbytes)
# System Configuration
SERVERNUM 1 # Unique idcorresponding to a OnLine instance
DBSERVERNAME courtshm # Name of defaultdatabase server
DBSERVERALIASES # List of alternatedbservernames
#Network Configuration
NETTYPE soctcp,4,150,NET
NETTYPE ipcshm,1,25,NET
FASTPOLL 1 # fast polling enabled
- added for 11.1
LISTEN_TIMEOUT 30 # Timeout (in Seconds)
#CPU & VPs
RESIDENT 0 # Forced residency
flag (Yes = 1, No = 0)
MULTIPROCESSOR 1 # 0 forsingle-processor, 1 for multi-processor
SINGLE_CPU_VP 0 # multiple CPU VPs
VPCLASS cpu,num=12,noage #
VPCLASS aio,num=2AUTO_AIOVPS 1 # auto adds AIO VPs if
needed.
VPCLASS idsxmlvp,num=1 # for xmlfunction usage
DIRECT_IO 1 # enabled (Yes = 1, No
= 0) will use KAIO if enabled.
CLEANERS 2 # Number of buffercleaner processes (guideline is 1 per disk drive)
#Do not use the following if we have the VPCLASS in use
#NUMAIOVPS 2 # Number of IO vps
#NUMCPUVPS 2 # Number of user (cpu)
vps
#NOAGE 0 # Process aging
#AFF_SPROC 0 # Affinity start
processor
#AFF_NPROCS 0 # Affinity number of
processors
# Shared Memory #BUFFERPOOL - replaces buffers, lrus, lru_min_dirty, &
lru_mas_dirty - needs two lines
BUFFERPOOL
size=2K,buffers=150000,lrus=8,lru_min_dirty=50.000000,lru_max_dirty=60.000000
AUTO_LRU_TUNING 1
LOCKS 200000 # Maximum number oflocks
#BUFFERS 150000 # Maximum number of
shared buffers - not used in 11.1
SHMBASE 0x44000000L # Shared memory baseaddress
SHMVIRTSIZE 160000 # initial virtualshared memory segment size
SHMADD 81920 # Size of new sharedmemory segments (Kbytes)
SHMTOTAL 0 # Total shared memory
(Kbytes). 0=>unlimited
EXTSHMADD 8192 # Size of newextension shared memory segments (Kbytes)
SHMVIRT_ALLOCSEG 0.000000 # Values between 0 and
.99 are %, values > 1 are#LRUS 20 # Number of LRU queues
#LRU_MAX_DIRTY 5.000000 # LRU percent dirty
begin cleaning limit
#LRU_MIN_DIRTY 2.000000 # LRU percent dirty
end cleaning limit
PC_POOLSIZE 110 # Stored ProceduresCache
#Checkpoints & System Block
CKPTINTVL 300 # Check point interval
(in sec)AUTO_CKPTS 1 # Monitor critical
resources and trigger
RTO_SERVER_RESTART 0 # Recovery TimeObjective for IDS restart after
BLOCKTIMEOUT 3600 # Default timeout forsystem block
#OS & Session Features
USEOSTIME 0 # 0: use internal
time(fast), 1: get time from OS(slow)
STACKSIZE 128 # Stack size (Kbytes)
USELASTCOMMITTED NONE # Wait on locks in anyisolation level
ALLOW_NEWLINE 0 # embedded
newlines(Yes = 1, No = 0 or anything but 1)
EILSEQ_COMPAT_MODE 0 # Enables errormessage -202
#Distributed Transactions
TXTIMEOUT 300 # Transaction timeout
(in sec)
DEADLOCK_TIMEOUT 60 # Max time to wait oflock in distributed env.
HETERO_COMMIT 0
# Recovery Variables
# OFF_RECVRY_THREADS: # Number of parallel
worker threads during fast recovery or an offline restore.
# ON_RECVRY_THREADS: # Number of parallel
worker threads during an online restore.
OFF_RECVRY_THREADS 15 # Default number ofoffline worker threads
ON_RECVRY_THREADS 15 # Default number ofonline worker threads
# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRINTERVAL 30 # DR max time betweenDR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout
(in sec)
DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found filepath
# Read Ahead Variables
RA_PAGES 64 # Number of pages toattempt to read ahead
RA_THRESHOLD 16 # Number of pages leftbefore next group
#Temp & Perm dbspaces & sbspaces
DBSPACETEMP tempdbs1,tempdbs2,tempdbs3,tempdbs4
# Default temp dbspaces
ONDBSPACEDOWN 0 # Dbspace down option:
0 = CONTINUE, 1 = ABORT, 2 = WAIT for User Input
SBSPACENAME # Default smartblobspace name - this is where blobs
SYSSBSPACENAME # Default smartblobspace for use by the Informix
# DUMP*:
# The following parameters control the type of diagnostics information
which
# is preserved when an unanticipated error condition (assertion failure)
occurs
# during OnLine operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPDIR /tmp # Preserve diagnosticsin this directory
DUMPSHMEM 0 # Dump a copy ofshared memory
DUMPGCORE 0 # Dump a core imageusing 'gcore'
DUMPCORE 0 # Dump a core image
(W
The problem, as someone already mentioned, is that you cannot position the
physical log in a different dbspace during server initialization since only
the rootdbs will exist at that time. Change PHYSFILE to something rather
small (less than 300MB) and remove the no longer supported PHYDBS
parameter. After the server comes online, create the physical log dbspace
and use the onparams utility to move the physical log into that new dbspace
and resize it to the size you want.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
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, Nov 17, 2010 at 4:52 PM, Kennedy, Randy
<RKennedy@scottsdaleaz.gov>wrote:
> The hardware is, according to RHEL within the VM, Dual Xeon X5660 2.8GHz
> ( 6 core, 12MB cache) with 6GB memory using SAN space for dbspace
> storage. The box's only purpose is the Informix DB and we are primarily
> a OLTP environment, but at night we do many DSS style batch jobs via
> cron.
>
> This was crafted based on our current 9.4 onconfig and looking at the
> onconfig.std from 11.1, we now realize the physlog and logical logs will
> be created within rootdbs upon initialization and then they will be
> changed to different size and dbspace.
>
> #***********************************************************************
> ***
> # INFORMIX SOFTWARE, INC.
> # Title: onconfig (for 11.1)
> # Description: INFORMIX-OnLine Configuration Parameters
> #***********************************************************************
> ***
> # Root Dbspace Configuration
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /db/links/rootdbs # Path for device> containing root dbspace
> ROOTOFFSET 0 # Offset of root> dbspace into device (Kbytes)
> ROOTSIZE 102400 # Size of root
> dbspace (Kbytes)>
> # Disk Mirroring Configuration Parameters
> MIRROR 0 # Mirroring flag (Yes
> = 1, No = 0)
> MIRRORPATH # Path for device> containing mirrored root
> MIRROROFFSET 0 # Offset into mirrored
> device (Kbytes)>
> # Physical Log Configuration
> PHYSDBS physdbs # Location (dbspace)
> of physical log
> PHYSFILE 102400 # Physical log file
> size (Kbytes)
> PHYSBUFF 128 # Physical log buffer
> size (Kbytes)>
> # Logical Log Configuration
> LOGFILES 3 # Number of logical> log files
> LOGSIZE 10240 # Logical log size
> (Kbytes)
> LOG_BACKUP_MODE CONT
> DYNAMIC_LOGS 2 # Add logical logs> files dynamically/automatically - newly added for 11.1
> LOGBUFF 64 # Logical log buffer
> size (Kbytes)>
> # Long Transaction Rollback
> LTXHWM 70 # Long transaction> high water mark percentage
> LTXEHWM 80 # Long transaction> high water mark (exclusive)
>
> #Tblspace tblspace in Root dbspace
> TBLTBLFIRST 0 # First extent size
> (Kbytes) (0 = default)
> TBLTBLNEXT 0 # Next extent size
> (Kbytes) (0 = default)
> TBLSPACE_STATS 1>
> # Diagnostics
> MSGPATH /i11.1FC3/online.log # System message log> file path
> CONSOLE /dev/console # System console> message path
> ALARMPROGRAM /db/scripts/no_log.sh # Alarm program path>
> # System Archive Tape Device
> TAPEDEV /remote/recovery/informix/level0 # Tape device path
> TAPEBLK 16 # Tape block size
> (Kbytes)
> TAPESIZE 30720000 # Maximum amount of> data to put on tape (Kbytes)
>
> # Log Archive Tape Device
> LTAPEDEV /remote/recovery/informix/log1 # Log tape device
> path
> LTAPEBLK 16 # Log tape block size
> (Kbytes)
> LTAPESIZE 460800 # Max amount of data> to put on log tape (Kbytes)
>
> # System Configuration
> SERVERNUM 1 # Unique id> corresponding to a OnLine instance
> DBSERVERNAME courtshm # Name of default> database server
> DBSERVERALIASES # List of alternate> dbservernames
>
> #Network Configuration
> NETTYPE soctcp,4,150,NET
> NETTYPE ipcshm,1,25,NET
> FASTPOLL 1 # fast polling enabled
> - added for 11.1
> LISTEN_TIMEOUT 30 # Timeout (in Seconds)>
> #CPU & VPs
> RESIDENT 0 # Forced residency
> flag (Yes = 1, No = 0)
> MULTIPROCESSOR 1 # 0 for> single-processor, 1 for multi-processor
> SINGLE_CPU_VP 0 # multiple CPU VPs
> VPCLASS cpu,num=12,noage #
> VPCLASS aio,num=2> AUTO_AIOVPS 1 # auto adds AIO VPs if
> needed.
> VPCLASS idsxmlvp,num=1 # for xml> function usage
> DIRECT_IO 1 # enabled (Yes = 1, No
> = 0) will use KAIO if enabled.
> CLEANERS 2 # Number of buffer> cleaner processes (guideline is 1 per disk drive)
> #Do not use the following if we have the VPCLASS in use
> #NUMAIOVPS 2 # Number of IO vps
> #NUMCPUVPS 2 # Number of user (cpu)
> vps
> #NOAGE 0 # Process aging
> #AFF_SPROC 0 # Affinity start
> processor
> #AFF_NPROCS 0 # Affinity number of
> processors
>
> # Shared Memory #BUFFERPOOL - replaces buffers, lrus, lru_min_dirty, &
> lru_mas_dirty - needs two lines
> BUFFERPOOL
> size=2K,buffers=150000,lrus=8,lru_min_dirty=50.000000,lru_max_dirty=60.0> 00000
> AUTO_LRU_TUNING 1
> LOCKS 200000 # Maximum number of> locks
> #BUFFERS 150000 # Maximum number of
> shared buffers - not used in 11.1
> SHMBASE 0x44000000L # Shared memory base> address
> SHMVIRTSIZE 160000 # initial virtual> shared memory segment size
> SHMADD 81920 # Size of new shared> memory segments (Kbytes)
> SHMTOTAL 0 # Total shared memory
> (Kbytes). 0=>unlimited
> EXTSHMADD 8192 # Size of new> extension shared memory segments (Kbytes)
> SHMVIRT_ALLOCSEG 0.000000 # Values between 0 and
> ..99 are %, values > 1 are> #LRUS 20 # Number of LRU queues
> #LRU_MAX_DIRTY 5.000000 # LRU percent dirty
> begin cleaning limit
> #LRU_MIN_DIRTY 2.000000 # LRU percent dirty
> end cleaning limit
> PC_POOLSIZE 110 # Stored Procedures> Cache
>
> #Checkpoints & System Block
> CKPTINTVL 300 # Check point interval
> (in sec)> AUTO_CKPTS 1 # Monitor critical
> resources and trigger
> RTO_SERVER_RESTART 0 # Recovery Time> Objective for IDS restart after
> BLOCKTIMEOUT 3600 # Default timeout for> system block
>
> #OS & Session Features
> USEOSTIME 0 # 0: use internal
> time(fast), 1: get time from OS(slow)
> STACKSIZE 128 # Stack size (Kbytes)
> USELASTCOMMITTED NONE # Wait on locks in any> isolation level
> ALLOW_NEWLINE 0 # embedded
> newlines(Yes = 1, No = 0 or anything but 1)
> EILSEQ_COMPAT_MODE 0 # Enables error> message -202
>
> #Distributed Transactions
> TXTIMEOUT 300 # Transaction timeout
> (in sec)
> DEADLOCK_TIMEOUT 60 # Max time to wait of> lock in distributed env.
> HETERO_COMMIT 0>
> # Recovery Variables
> # OFF_RECVRY_THREADS: # Number of parallel
> worker threads during fast recovery or an offline restore.
>