IDS Forum

Re: cannot initialize rootdbs

Posted By: Obnoxio The Clown
Date: Tuesday, 29 June 2004, at 5:17 a.m.

In Response To: cannot initialize rootdbs (NOOR ANSARI AB RAZAK)

NOOR ANSARI.... said:
> *****************************
> informix 7.3 UD1
> running on Solaris 8 with 70 Mhz CPU and
> 168 MB RAM
> ******************************

168MB of RAM? You're kidding, right?

> Problem : Fatal error in shared memory creation
> error 156
> command :
> $ oninit -i
>
> 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
> oninit: Fatal error in shared memory creation
>
> $ onstat -
> onstat: Cannot attach to shared memory. errno = 156
>
>
> message in online.log : 15:47:33 mt_shm_init: can't create virtual
> segment
>
> 15:52:13 shmat: [EMFILE][24]: out of shared memory segments, check system
> SHMSEG

And did you?

Could be that you're trying to bring up too big an instance, or that a
previous instance wasn't cleared from memory, or that there is an instance
already at that address.

Try running onmode -ky a couple of times before retrying the oninit, or
reboot the server.

> 15:52:13 mt_shm_init: can't create virtual segment
>
> 15:56:33 shmat: [EMFILE][24]: out of shared memory segments, check system
> SHMSEG
>
> 15:56:33 mt_shm_init: can't create virtual segment
>
> 08:48:35 shmat: [EMFILE][24]: out of shared memory segments, check system
> SHMSEG
>
> 08:48:35 mt_shm_init: can't create virtual segment
>
> 08:53:26 shmget: [EEXIST][17]: key 52574801: shared memory already exists
> 08:53:26 mt_shm_init: can't create resident segment
>
> 09:18:51 shmget: [EEXIST][17]: key 52574801: shared memory already exists
> 09:18:51 mt_shm_init: can't create resident segment
>
> 09:40:53 shmget: [EEXIST][17]: key 52574801: shared memory already exists
> 09:40:53 mt_shm_init: can't create resident segment
>
>
> onconfig file : # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /netra/chunk/root-cook-01
> # Path for device containing root dbspace
> ROOTOFFSET # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 20000 # Size of root dbspace (Kbytes)
>
> # Disk Mirroring Configuration Parameters
>
> MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH /netra/chunk/mroot-cook-01
> # Path for device containing mirrored root
> MIRROROFFSET # Offset into mirrored device (Kbytes)
>
> # Physical Log Configuration
>
> PHYSDBS rootdbs # Location (dbspace) of physical log
> PHYSFILE 1000 # Physical log file size (Kbytes)
>
> # Logical Log Configuration
>
> LOGFILES 6 # Number of logical log files
> LOGSIZE 500 # Logical log size (Kbytes)
>
> # Diagnostics
>
> MSGPATH /informix/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> ALARMPROGRAM /informix/etc/log_full.sh # Alarm program path
> SYSALARMPROGRAM /informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS 1
>
> # System Archive Tape Device
>
> TAPEDEV superserver:/dev/rmt/0 # Tape device path
> TAPEBLK 16 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape
> (Kbytes)
>
> # Log Archive Tape Device
>
> LTAPEDEV superserver:/dev/rmt/0 # Log tape device path
> LTAPEBLK 16 # Log tape block size (Kbytes)
> LTAPESIZE 10240 # Max amount of data to put on log tape
> (Kbytes)
>
> # Optical
>
> STAGEBLOB # Informix Dynamic Server/Optical staging
> area
>
> # System Configuration
>
> SERVERNUM 1 # Unique id corresponding to a Dynamic
> Server instance
> DBSERVERNAME imiti # Name of default database server
> DBSERVERALIASES # List of alternate dbservernames
> NETTYPE tlitcp,1,100,NET # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
> env.
> RESIDENT # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR # for single-processor, 1 for
> multi-processor
> NUMCPUVPS 1 # Number of user (cpu) vps
> SINGLE_CPU_VP # If non-zero, limit number of cpu vps to
> one
>
> NOAGE # Process aging
> AFF_SPROC # Affinity start processor
> AFF_NPROCS # Affinity number of processors
>
> # Shared Memory Parameters
>
> AFF_SPROC # Affinity start processor
> AFF_NPROCS # Affinity number of processors
>
> # Shared Memory Parameters
>
> LOCKS 20000 # Maximum number of locks
> BUFFERS 2000 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 128 # Physical log buffer size (Kbytes)
> LOGBUFF 64 # Logical log buffer size (Kbytes)
> LOGSMAX 20 # Maximum number of logical log files
> CLEANERS 2 # Number of buffer cleaner processes
> SHMBASE 0xa000000 # Shared memory base address
> SHMVIRTSIZE 10000 # initial virtual shared memory segment
> size
> SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 16 # Number of LRU queues
> LRU_MAX_DIRTY 40 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 30 # LRU percent dirty end cleaning limit
> LTXHWM 40 # Long transaction high water mark
> percentage
> LTXEHWM 50 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)
> # System Page Size
> # BUFFSIZE - Dynamic Server no longer supports this configuration
> parameter.
> # To determine the page size used by Dynamic Server on your
> platform
> # see the last line of output from the command, 'onstat -b'.
>
>
> # 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 10 # Default number of offline worker
> threads
> ON_RECVRY_THREADS 1 # Default number of online worker
> threads
>
> # Data Replication Variables
> # DRAUTO: manual, 1 retain type, 2 reverse type
> DRAUTO # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer flushes
> (in sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /informix/etc/dr.lostfound # DR lost+found file path
>
> # CDR Variables
> 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 # Link level compression (-1 never, 0
> none, 9 max)
>
> # Backup/Restore variables
> BAR_ACT_LOG /tmp/bar_act.log
> BAR_MAX_BACKUP 0
> BAR_RETRY 1
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 31
>
> # Informix Storage Manager variables
> ISM_DATA_POOL ISMData # If the data pool name is changed, be
> sure to
> # update $INFORMIXDIR/bin/onbar. Change
> to
> # ism_catalog -create_bootstrap -pool <new
> name>
> ISM_LOG_POOL ISMLogs
>
> # Read Ahead Variables
> RA_PAGES # Number of pages to attempt to read ahead
> RA_THRESHOLD # Number of pages left before next group
>
> # DBSPACETEMP:
> # Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces
> # that the Dynamic Server SQL Engine will use to create temp tables etc.
> # If specified it must be a colon separated list of dbspaces that exist
> # when the Dynamic Server system is brought online. If not specified, or
> if
> # all dbspaces specified are invalid, various ad hoc queries will create
> # temporary files in /tmp instead.
>
> DBSPACETEMP # Default temp dbspaces
>
> # DUMP*:
> # The following parameters control the type of diagnostics information
> which
> # is preserved when an unanticipated error condition (assertion failure)
> occurs
> # during Dynamic Server operations.
> # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, means No.
>
> DUMPDIR /tmp # Preserve diagnostics in this directory
> DUMPSHMEM 1 # Dump a copy of shared memory
> DUMPGCORE # Dump a core image using 'gcore'
> DUMPCORE # 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
>
> # method for Dynamic Server to use when determining current time
> USEOSTIME # 0: use internal time(fast), 1: get time
> from OS(slow)
>
> # Parallel Database Queries (pdq)
> 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 off # List of dbspaces to skip
>
> # OPTCOMPIND
> # => 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
>
> ONDBSPACEDOWN 2 # Dbspace down option: = CONTINUE, 1 =
> ABORT, 2 = WAIT
> LBU_PRESERVE # Preserve last log for log backup
> OPCACHEMAX # Maximum optical cache size (Kbytes)
>
> # HETERO_COMMIT (Gateway participation in distributed transactions)
> # 1 => Heterogeneous Commit is enabled
> # (or any other value) => Heterogeneous Commit is disabled
> HETERO_COMMIT 0
>
> # Optimization goal: -1 = ALL_ROWS(Default), = FIRST_ROWS
> OPT_GOAL -1
>
> # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
> DIRECTIVES 1
>
> # Status of restartable restore
> RESTARTABLE_RESTORE off
>
>
>


--
Bye now,
Obnoxio

"C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
- Coluche

"I'm trying to see things your way, but I can't get my head up my ass"
- JCH

"Ogni uomo mi guarda come se fossi una testa di cazzo"
- Marco

http://www.catb.org/~esr/faqs/smart-questions.html

Messages In This Thread

• cannot initialize rootdbs
  NOOR ANSARI AB RAZAK -- Monday, 28 June 2004, at 9:49 p.m.
  • Re: cannot initialize rootdbs
    paul@oninit.com -- Tuesday, 29 June 2004, at 3:54 a.m.
  • Re: cannot initialize rootdbs
    Obnoxio The Clown -- Tuesday, 29 June 2004, at 5:17 a.m.
  • RE: cannot initialize rootdbs
    NormaJean.Sebastian@tellabs.com -- Tuesday, 29 June 2004, at 8:34 a.m.
    • Re: RE: cannot initialize rootdbs
      NOOR ANSARI AB RAZAK -- Sunday, 4 July 2004, at 11:22 p.m.
      • Re: cannot initialize rootdbs
        paul@oninit.com -- Monday, 5 July 2004, at 3:14 a.m.
        • Re: cannot initialize rootdbs
          sergeimo@hot.ee -- Monday, 5 July 2004, at 4:50 a.m.
        • RV: cannot initialize rootdbs
          Alberto Otero -- Tuesday, 6 July 2004, at 3:31 a.m.
      • RE: RE: cannot initialize rootdbs
        Simmons, Keith -- Monday, 5 July 2004, at 4:05 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.