IDS Forum

Re: rootdbs size

Posted By: Art Kagel
Date: Wednesday, 17 November 2010, at 5:00 p.m.

In Response To: RE: rootdbs size (Kennedy, Randy)

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.
> # ON_RECVRY_THREADS: # Number of parallel
> worker threads during an online restore.
> OFF_RECVRY_THREADS 15 # Default number of
> offline worker threads
> ON_RECVRY_THREADS 15 # Default number of
> online worker threads
>
> # Data Replication Variables
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> 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
>
> # Read Ahead Variables
> RA_PAGES 64 # Number of pages to
> attempt to read ahead
> RA_THRESHOLD 16 # Number of pages left
> before 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 smartblob
> space name - this is where blobs
> SYSSBSPACENAME # Default smartblob
> space 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 diagnostics
> in this directory
> DUMPSHMEM 0 # Dump a copy of
> shared memory
> DUMPGCORE 0 # Dump a core image
> using 'gcore'
> DUMPCORE 0 # Dump a core image
> (Warning:this aborts OnLine)
> DUMPCNT 1 # Number of shared
> memory or gcore dumps for a single user's session
>
> # ADT*
> # The following parameters control the type and level of secure auditing
> # present in the OnLine system. By default, ADTMODE is 0 and auditing
> # is disabled
>
> #Index Features
> FILLFACTOR 90 # Fill factor for
> building indexes
> MAX_FILL_DATA_PAGES 0 # Fill data pages
> maximally (Yes = 1, No = 0)
> ONLIDX_MAXMEM 5120 # Per pool per index
> (Kbytes)
>
> # Parallel Database Queries (pdq) # OFF => 0, LOW => 1, HIGH => 100
> MAX_PDQPRIORITY 90 # Maximum allowed
> pdqpriority
> DS_MAX_QUERIES 15 # Maximum number of
> decision support queries
> DS_TOTAL_MEMORY # Decision support
> memory (Kbytes)
> DS_MAX_SCANS 250 # Maximum number of
> decision support scans
> DATASKIP off
> DS_NONPDQ_QUERY_MEM 128 # Non PDQ query memory
> (Kbytes)
>
> #Optimizer Plans, Directives, & SQL Tracing
> # OPTCOMPIND
> # 0 => Nested loop joins will be preferred (where possible) over
> sortmerge joins and hash joins.
> # 1 => If the transaction isolation mode is not "repeatable read",
> optimizer behaves as in (2) below. Otherwise it behaves as in (0)
> above.
> # 2 => Use costs regardless of the transaction isolation mode. Nested
> loop joins are not necessarily preferred. Optimizer bases its decision
> purely on costs.
> OPTCOMPIND 2 # To hint the
> optimizer
> OPT_GOAL -1 # Optimize for all
> rows that the query returns
> DIRECTIVES 1 # Enable optimizer
> directives
> IFX_FOLDVIEW 0 # fold multiple tables
> or union all view with ansi joins
> EXPLAIN_STAT 1 # Enable Query
> Statistics in EXPLAIN file.
> AUTO_REPREPARE 1 # Automatically
> re-optimize after DDL
>
> #Optical Storage Subsystem
> STAGEBLOB #
> INFORMIX-OnLine/Optical staging area
> OPCACHEMAX 0 # Maximum optical
> cache size (Kbytes)
>
> #Onbar settings
> BAR_ACT_LOG /tmp/bar_act.log
> BAR_DEBUG_LOG /tmp/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
> BAR_PROGRESS_FREQ 0
> RESTARTABLE_RESTORE off
>
> #Alarm Program Feature
> SYSALARMPROGRAM /i11.1FC3/etc/evidence.sh # System Alarm program
> path
> ALRM_ALL_EVENTS 0 # Triggers
> ALARMPROGRAM for any event occur
>
> #Informix Storage Manager
> ISM_DATA_POOL ISMData # If the data pool
> name is changed, be sure to
> ISM_LOG_POOL ISMLogs
>
> #Java Configuration
> JVPJAVAHOME /i11.1FC3/extend/krakatoa/jre/# JRE installation
> root directory
> JVPHOME /i11.1FC3/extend/krakatoa/ # Krakatoa
> installation directory
> JVPPROPFILE .jvpprops # JVP property file
> JDKVERSION 1.4 # JDK version
> supported by this server
> JVMTHREAD green # Java VM thread type
> (green or native)
> JVPJAVALIB /bin/j9vm
> JVPJAVAVM libjava.so
> JVPCLASSPATH
> /i11.1FC3/extend/krakatoa/krakatoa.jar:/i11.1FC3/extend/krakatoa/jdbc.ja
> r
> JVPLOGFILE /i11.1FC3/jvp.log # JVP log file.
>
> #Other ER Features
> CDR_SERIAL 0,0 # Serial Column
> Sequence
> CDR_DBSPACE # dbspace for syscdr
> database
> CDR_QHDR_DBSPACE # CDR queue dbspace
> (default same as catalog)
> CDR_QDATA_SBSPACE # List of CDR queue
> smart blob spaces
> CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition
> disabled by default
> CDR_EVALTHREADS 1,2 # evaluator threads
> (per-cpu-vp,additional)
> CDR_DSLOCKWAIT 10 # DS lockwait timeout
> (seconds)
> CDR_QUEUEMEM 4096 # Maximum amount of
> memory for any CDR queue (Kbytes)
> CDR_NIFCOMPRESS 0 # Link level
> compression (-1 never, 0 none, 9 max)
>
> #Security
> IFX_EXTEND_ROLE 1 # To control the usage
> of EXTEND role.
>
> #High Availability Clusters (HDR, SDS, & RSS)
> DRAUTO 0 # DR automatic
> switchover
> DRIDXAUTO 0 # DR automatic index
> repair. 0=off, 1=on
> LOG_INDEX_BUILDS 0 # logically log
> content of indexes
> SDS_ENABLE 0 # SDS Activation 0 -
> no, 1 - yes
> SDS_TIMEOUT 10 # Time Delay that
> Primary will wait for any ACK
> SDS_PAGING # Paging File Location
>
> #Technical Support Parameters
> RAS_PLOG_SPEED 0 # IDS RAS param; do
> not change; auto updated
> RAS_LLOG_SPEED 561 # IDS RAS param; do
> not change; auto updated
>
> Thanks,
> Randy
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Art Kagel
> Sent: Wednesday, November 17, 2010 2:22 PM
> To: ids@iiug.org
> Subject: Re: rootdbs size [21974]
>
> 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
>
> ************************************************************************
> *******
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--20cf3054acd5b48439049546cdac

Messages In This Thread

• rootdbs size
  Kennedy, Randy -- Wednesday, 17 November 2010, at 3:09 p.m.
  • RE: rootdbs size
    Link, David A -- Wednesday, 17 November 2010, at 3:22 p.m.
  • Re: rootdbs size
    DAN MUELLER -- Wednesday, 17 November 2010, at 3:53 p.m.
  • Re: rootdbs size
    Art Kagel -- Wednesday, 17 November 2010, at 4:22 p.m.
    • RE: rootdbs size
      Kennedy, Randy -- Wednesday, 17 November 2010, at 4:52 p.m.
      • Re: rootdbs size
        Art Kagel -- Wednesday, 17 November 2010, at 5:00 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.