IDS 10 instance can't initialize dbspace
Posted in 2007
Gary couldn't initialize a new IDS 10 instance: oninit kept reporting "Not enough room in ROOT DBspace", asking for more space each time he raised ROOTSIZE. He had also set PHYSFILE equal to ROOTSIZE because of a message saying PHYSDBS should equal ROOTDBS. Replies explained he misread that message: it refers to the physical log's dbspace name, not its size. Setting PHYSDBS to the root dbspace name (dbroot) and PHYSFILE to a small value (e.g. 20000 KB) fixes it; the log can be enlarged or moved after initialization. Gary confirmed he understood.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Backup & Restore, Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration, Platform-Specific Issues
Continuing the saga from my ontape restore to a different server I am
taking the suggestions to use archecker and IDS 10 to do a table
restore. My current server is 9.4.
I created an IDS 10 directory and changed all the paths and ENV vars to
use the new location for an instance. When I try to initialize the new
instance it chokes on:
oninit: Not enough room in ROOT DBspace.
Requested 1017076K, ONCONFIG value 'ROOTSIZE' 1008538K.
My OS is Solaris 9 (Sparc) with IDS10.0UC5
Every time I increase the size it wants more. I increased the size 6
times and it keeps wanting more space. I reduced my logs to 3 and IDS
10 insists on the physical space being the same as the rootsize. No
matter how big I make the root it wants a little more than I
configured.
Onconfig:
ROOTNAME dbroot # Root dbspace nameROOTPATH /mnt/data/ids10/ids10root
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 1008538 # Size of root dbspace (Kbytes)PHYSDBS dbplog # Location (dbspace) of physical log
PHYSFILE 1008538 # Physical log file size (Kbytes)
LOGFILES 3 # Number of logical log files
LOGSIZE 2500 # Logical log size (Kbytes)MSGPATH /u/ids10/online.log # System message log file path
CONSOLE /dev/console # System console message path
TAPEDEV /dev/null # Tape device path
TAPEBLK 512 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape
(Kbytes)
LTAPEDEV /dev/null
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 2000 # Max amount of data to put on log tape
(Kbytes)
SERVERNUM 1 # Unique id corresponding to a OnLineinstance
DBSERVERNAME dev1_ids10 # Name of default database serverDBSERVERALIASES dev1_ids10_net # List of alternate dbservernames
DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed env.
RESIDENT 1 # Forced residency flag (Yes = 1, No =
0)
NETTYPE ipcshm,3,200,CPU # Configure poll thread(s) for sharedmem
NETTYPE tlitcp,3,130,NET # Configure poll thread(s) for sharedmem
MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 3 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
#LOCKS 2000000 # Maximum number of locks
LOCKS 500000 # Maximum number of locks#BUFFERS 800000 # Maximum number of shared buffers
BUFFERS 200000 # Maximum number of shared buffers
NUMAIOVPS 3 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0xa000000#SHMVIRTSIZE 8000 # initial virtual shared memory
segment size
SHMVIRTSIZE 16384 # initial virtual shared memory segmentsize
#SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMADD 12288 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 128 # Number of LRU queues
LRU_MAX_DIRTY 1.000000 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 0.000000 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80
HI,
Reduce your
PHYSFILE 1008538 # Physical log file size (Kbytes)
to a small value!
Frank
On 5 Jan 2007 13:52:28 -0800, Gary Quiring <gquiring@gmail.com> wrote:
>
> Continuing the saga from my ontape restore to a different server I am
> taking the suggestions to use archecker and IDS 10 to do a table
> restore. My current server is 9.4.
>
> I created an IDS 10 directory and changed all the paths and ENV vars to
> use the new location for an instance. When I try to initialize the new
> instance it chokes on:
>
> oninit: Not enough room in ROOT DBspace.
> Requested 1017076K, ONCONFIG value 'ROOTSIZE' 1008538K.
>
> My OS is Solaris 9 (Sparc) with IDS10.0UC5
>
> Every time I increase the size it wants more. I increased the size 6
> times and it keeps wanting more space. I reduced my logs to 3 and IDS
> 10 insists on the physical space being the same as the rootsize. No
> matter how big I make the root it wants a little more than I
> configured.
>
>
> Onconfig:
> ROOTNAME dbroot # Root dbspace name> ROOTPATH /mnt/data/ids10/ids10root
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 1008538 # Size of root dbspace (Kbytes)> PHYSDBS dbplog # Location (dbspace) of physical log
> PHYSFILE 1008538 # Physical log file size (Kbytes)
>
> LOGFILES 3 # Number of logical log files
> LOGSIZE 2500 # Logical log size (Kbytes)> MSGPATH /u/ids10/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 512 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape
> (Kbytes)
> LTAPEDEV /dev/null
> LTAPEBLK 32 # Log tape block size (Kbytes)
> LTAPESIZE 2000 # Max amount of data to put on log tape
> (Kbytes)
>
> SERVERNUM 1 # Unique id corresponding to a OnLine> instance
> DBSERVERNAME dev1_ids10 # Name of default database server> DBSERVERALIASES dev1_ids10_net # List of alternate dbservernames
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in> distributed env.
> RESIDENT 1 # Forced residency flag (Yes = 1, No =
> 0)
> NETTYPE ipcshm,3,200,CPU # Configure poll thread(s) for shared> mem
> NETTYPE tlitcp,3,130,NET # Configure poll thread(s) for shared> mem
>
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 3 # 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>
> # Shared Memory Parameters
>
> #LOCKS 2000000 # Maximum number of locks
> LOCKS 500000 # Maximum number of locks> #BUFFERS 800000 # Maximum number of shared buffers
> BUFFERS 200000 # Maximum number of shared buffers
> NUMAIOVPS 3 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0xa000000> #SHMVIRTSIZE 8000 # initial virtual shared memory
> segment size
> SHMVIRTSIZE 16384 # initial virtual shared memory segment> size
> #SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMADD 12288 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 128 # Number of LRU queues
> LRU_MAX_DIRTY 1.000000 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 0.000000 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)
> DYNAMIC_LOGS 2
> LTXHWM 70
> LTXEHWM 80>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
FRANK wrote:
> HI,
>
> Reduce your
>
> PHYSFILE 1008538 # Physical log file size (Kbytes)>
> to a small value!
>
> Frank
>
>
HI Frank, as I mention in my post IDS 10 will not allow the physical to
be smaller than the root. This is the message:
For disk space initialization, the value specified in the ONCONFIG file
for
PHYSDBS (dbplog) should be equal to that of ROOTDBS (dbroot).
FAILED
"Gary Quiring" <gquiring@gmail.com> wrote in message
news:1168035825.877111.296820@q40g2000cwq.googlegroups.com...
>
> FRANK wrote:
>> HI,
>>
>> Reduce your
>>
>> PHYSFILE 1008538 # Physical log file size (Kbytes)>>
>> to a small value!
>>
>> Frank
>>
>>
> HI Frank, as I mention in my post IDS 10 will not allow the physical to
> be smaller than the root. This is the message:
>
> For disk space initialization, the value specified in the ONCONFIG file
> for
> PHYSDBS (dbplog) should be equal to that of ROOTDBS (dbroot).
> FAILED
The English of the error message is not perfect, Gary, but it should be
clear enough! The message refers not to the *size* of PHYSDBS, but of its
actual value. So, to spell it out, set PHYSDBS to dbroot, and as Frank says
set PHYSFILE to something small.
PHYSFILE specifies the size of the physical log.
PHYSDBS specifies the name of the dbspace that contains the physical log.
When you initialize disk space (oninit -i), the PHYSDBS value must be
equal to the ROOTDBS value.
Refer to - Size of the Root Dbspace - for more info
http://publib.boulder.ibm.com/infocenter/ids9help/index.jsp?topic=/com.ibm.admin.doc/admin372.htm
Regards,
Nilesh
"Gary Quiring" <gquiring@gmail.com>
Sent by: informix-list-bounces@iiug.org
01/05/2007 03:52 PM
To
informix-list@iiug.org
cc
Subject
IDS 10 instance can't initialize dbspace
Continuing the saga from my ontape restore to a different server I am
taking the suggestions to use archecker and IDS 10 to do a table
restore. My current server is 9.4.
I created an IDS 10 directory and changed all the paths and ENV vars to
use the new location for an instance. When I try to initialize the new
instance it chokes on:
oninit: Not enough room in ROOT DBspace.
Requested 1017076K, ONCONFIG value 'ROOTSIZE' 1008538K.
My OS is Solaris 9 (Sparc) with IDS10.0UC5
Every time I increase the size it wants more. I increased the size 6
times and it keeps wanting more space. I reduced my logs to 3 and IDS
10 insists on the physical space being the same as the rootsize. No
matter how big I make the root it wants a little more than I
configured.
Onconfig:
ROOTNAME dbroot # Root dbspace nameROOTPATH /mnt/data/ids10/ids10root
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 1008538 # Size of root dbspace (Kbytes)PHYSDBS dbplog # Location (dbspace) of physical log
PHYSFILE 1008538 # Physical log file size (Kbytes)
LOGFILES 3 # Number of logical log files
LOGSIZE 2500 # Logical log size (Kbytes)MSGPATH /u/ids10/online.log # System message log file path
CONSOLE /dev/console # System console message path
TAPEDEV /dev/null # Tape device path
TAPEBLK 512 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on tape
(Kbytes)
LTAPEDEV /dev/null
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 2000 # Max amount of data to put on log tape
(Kbytes)
SERVERNUM 1 # Unique id corresponding to a OnLineinstance
DBSERVERNAME dev1_ids10 # Name of default database serverDBSERVERALIASES dev1_ids10_net # List of alternate dbservernames
DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed env.
RESIDENT 1 # Forced residency flag (Yes = 1, No =
0)
NETTYPE ipcshm,3,200,CPU # Configure poll thread(s) for sharedmem
NETTYPE tlitcp,3,130,NET # Configure poll thread(s) for sharedmem
MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 3 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
#LOCKS 2000000 # Maximum number of locks
LOCKS 500000 # Maximum number of locks#BUFFERS 800000 # Maximum number of shared buffers
BUFFERS 200000 # Maximum number of shared buffers
NUMAIOVPS 3 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0xa000000#SHMVIRTSIZE 8000 # initial virtual shared memory
segment size
SHMVIRTSIZE 16384 # initial virtual shared memory segmentsize
#SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMADD 12288 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 128 # Number of LRU queues
LRU_MAX_DIRTY 1.000000 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 0.000000 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
> The English of the error message is not perfect, Gary, but it should be > clear enough! The message refers not to the *size* of PHYSDBS, but of its > actual value. So, to spell it out, set PHYSDBS to dbroot, and as Frank says > set PHYSFILE to something small. Thanks I get it. I had a fixation on the size and not it's location. Gary
Hola Gary,
si estas inicializando IDS 10 (oninit -i), el valor de PHYSFILE debe
ser menor que el ROOTSIZE, bastante menor, ademas el PHYSDBS debe igual
que ROOTNAME. Por ejemplo:
> ROOTNAME dbroot # Root dbspace name
> ROOTSIZE 1008538 # Size of root dbspace (Kbytes)> PHYSDBS dbroot # Location (dbspace) of physical log
> PHYSFILE 20000 # Physical log file size (Kbytes)
Una vez inicializado, puedes aumentar el tama'o y cambiarle de
dbspace.
Si lo que quieres es levantar los dbspaces de una version 9 con una
version 10, no tienes que hacer nada excepto copiar el onconfig y el
sqlhots de una version a la otra, y tener suficiente espacio en todos
los dbspaces para que pueda convertirlos a la version 10. Esto es mas o
menos un 12% libre de espacio en todos los dbspaces.
Saludos.
Gary Quiring wrote:
> Continuing the saga from my ontape restore to a different server I am
> taking the suggestions to use archecker and IDS 10 to do a table
> restore. My current server is 9.4.
>
> I created an IDS 10 directory and changed all the paths and ENV vars to
> use the new location for an instance. When I try to initialize the new
> instance it chokes on:
>
> oninit: Not enough room in ROOT DBspace.
> Requested 1017076K, ONCONFIG value 'ROOTSIZE' 1008538K.
>
> My OS is Solaris 9 (Sparc) with IDS10.0UC5
>
> Every time I increase the size it wants more. I increased the size 6
> times and it keeps wanting more space. I reduced my logs to 3 and IDS
> 10 insists on the physical space being the same as the rootsize. No
> matter how big I make the root it wants a little more than I
> configured.
>
>
> Onconfig:
> ROOTNAME dbroot # Root dbspace name> ROOTPATH /mnt/data/ids10/ids10root
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 1008538 # Size of root dbspace (Kbytes)> PHYSDBS dbplog # Location (dbspace) of physical log
> PHYSFILE 1008538 # Physical log file size (Kbytes)
>
> LOGFILES 3 # Number of logical log files
> LOGSIZE 2500 # Logical log size (Kbytes)> MSGPATH /u/ids10/online.log # System message log file path
> CONSOLE /dev/console # System console message path
> TAPEDEV /dev/null # Tape device path
> TAPEBLK 512 # Tape block size (Kbytes)
> TAPESIZE 10240 # Maximum amount of data to put on tape
> (Kbytes)
> LTAPEDEV /dev/null
> LTAPEBLK 32 # Log tape block size (Kbytes)
> LTAPESIZE 2000 # Max amount of data to put on log tape
> (Kbytes)
>
> SERVERNUM 1 # Unique id corresponding to a OnLine> instance
> DBSERVERNAME dev1_ids10 # Name of default database server> DBSERVERALIASES dev1_ids10_net # List of alternate dbservernames
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in> distributed env.
> RESIDENT 1 # Forced residency flag (Yes = 1, No =
> 0)
> NETTYPE ipcshm,3,200,CPU # Configure poll thread(s) for shared> mem
> NETTYPE tlitcp,3,130,NET # Configure poll thread(s) for shared> mem
>
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 3 # 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>
> # Shared Memory Parameters
>
> #LOCKS 2000000 # Maximum number of locks
> LOCKS 500000 # Maximum number of locks> #BUFFERS 800000 # Maximum number of shared buffers
> BUFFERS 200000 # Maximum number of shared buffers
> NUMAIOVPS 3 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> CLEANERS 1 # Number of buffer cleaner processes
> SHMBASE 0xa000000> #SHMVIRTSIZE 8000 # initial virtual shared memory
> segment size
> SHMVIRTSIZE 16384 # initial virtual shared memory segment> size
> #SHMADD 8192 # Size of new shared memory segments
> (Kbytes)
> SHMADD 12288 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes).
> 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 128 # Number of LRU queues
> LRU_MAX_DIRTY 1.000000 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 0.000000 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)
> DYNAMIC_LOGS 2
> LTXHWM 70
> LTXEHWM 80
Related threads
- the longer you surf, the MORE $$$ you earn !!
- Store procedure
- emulation for Vt100
- extent size questions again ...