size of rootdbs

Hi all, What should be the size of rootdbs .I mean the optimum size. How does the size of rootdbs affect the IDS performance? It is takijng a lot of time to initialize ..Is it normal(as per my configuration) ? Find below the my onconfig file ..which i am using.. ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/online_root # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 15000000 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration Parameters MIRROR 0 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # Path for device containing mirroredroot MIRROROFFSET 0 # Offset into mirrored device (Kbytes) # Physical Log Configuration PHYSDBS rootdbs # Location (dbspace) of physical log PHYSFILE 950000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 90 # Number of logical log files LOGSIZE 60000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) Thanks.

On 30 Nov 2006 01:26:14 -0800, doitman <sunil.saggar@gmail.com> wrote: > Hi all, > > What should be the size of rootdbs .I mean the optimum size. > How does the size of rootdbs affect the IDS performance? > It is takijng a lot of time to initialize ..Is it normal(as per my > configuration) ? > > Find below the my onconfig file ..which i am using.. > > > > ROOTNAME rootdbs # Root dbspace name> ROOTPATH /dev/online_root > # Path for device containing root > dbspace > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 15000000 # 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 rootdbs # Location (dbspace) of physical log > PHYSFILE 950000 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 90 # Number of logical log files > LOGSIZE 60000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, > CONT) > > Thanks. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > Sunil 15 Gb is far too big, but I suspect you have few (if any) other dbspaces! You need to reduce it in size, however this involves re-initialising your instance and trashing all the data! 1 Gb is probably big enough, put your PHYSFILE (which is also possibly a bit large at 950 Mb) into its own dbspace and move all your LOGFILES into their own space(s). Create specific dbspaces in which to create your databases and you will improve performanceand vastly reduce the risk of filling your root dbspace and all its attendant heartache. Many dbspaces also open the possibility of parallel archives. Keith

after initialization you have to create separate DBSPACES for PHYSICAL AND LOGICAL LOGS. rootdbs must be used only for system related purposes not for any other activities. you have to create 3 more dbspaces. one for physical and other one for logical and another one for databases. regards kalyan. Keith Simmons wrote: > On 30 Nov 2006 01:26:14 -0800, doitman <sunil.saggar@gmail.com> wrote: > > Hi all, > > > > What should be the size of rootdbs .I mean the optimum size. > > How does the size of rootdbs affect the IDS performance? > > It is takijng a lot of time to initialize ..Is it normal(as per my > > configuration) ? > > > > Find below the my onconfig file ..which i am using.. > > > > > > > > ROOTNAME rootdbs # Root dbspace name> > ROOTPATH /dev/online_root > > # Path for device containing root > > dbspace > > ROOTOFFSET 0 # Offset of root dbspace into device > > (Kbytes) > > ROOTSIZE 15000000 # 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 rootdbs # Location (dbspace) of physical log > > PHYSFILE 950000 # Physical log file size (Kbytes)> > > > # Logical Log Configuration > > > > LOGFILES 90 # Number of logical log files > > LOGSIZE 60000 # Logical log size (Kbytes)> > LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, > > CONT) > > > > Thanks. > > > > _______________________________________________ > > Informix-list mailing list > > Informix-list@iiug.org > > http://www.iiug.org/mailman/listinfo/informix-list > > > Sunil > > 15 Gb is far too big, but I suspect you have few (if any) other > dbspaces! You need to reduce it in size, however this involves > re-initialising your instance and trashing all the data! > 1 Gb is probably big enough, put your PHYSFILE (which is also possibly > a bit large at 950 Mb) into its own dbspace and move all your LOGFILES > into their own space(s). > Create specific dbspaces in which to create your databases and you > will improve performanceand vastly reduce the risk of filling your > root dbspace and all its attendant heartache. > Many dbspaces also open the possibility of parallel archives. > > Keith

Thanks Keith. # LTXEHWM should be atleast 30% so that we could minimize log overrun issue. DYNAMIC_LOGS 2 LTXHWM 50 LTXEHWM 60 Dynamic logs are ON. meaning that it will be created when previous logs fills up ..right ..? from where these logs will be created . rootdbs ? One more thing : If i create logdbs and create the logs in that logdbs(after the system initialization) leaving a few logical logs in rootdbs . Now when the logs fills up , will they be created from logdbs or rootdbs? Thanks. Keith Simmons wrote: > On 30 Nov 2006 01:26:14 -0800, doitman <sunil.saggar@gmail.com> wrote: > > Hi all, > > > > What should be the size of rootdbs .I mean the optimum size. > > How does the size of rootdbs affect the IDS performance? > > It is takijng a lot of time to initialize ..Is it normal(as per my > > configuration) ? > > > > Find below the my onconfig file ..which i am using.. > > > > > > > > ROOTNAME rootdbs # Root dbspace name> > ROOTPATH /dev/online_root > > # Path for device containing root > > dbspace > > ROOTOFFSET 0 # Offset of root dbspace into device > > (Kbytes) > > ROOTSIZE 15000000 # 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 rootdbs # Location (dbspace) of physical log > > PHYSFILE 950000 # Physical log file size (Kbytes)> > > > # Logical Log Configuration > > > > LOGFILES 90 # Number of logical log files > > LOGSIZE 60000 # Logical log size (Kbytes)> > LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, > > CONT) > > > > Thanks. > > > > _______________________________________________ > > Informix-list mailing list > > Informix-list@iiug.org > > http://www.iiug.org/mailman/listinfo/informix-list > > > Sunil > > 15 Gb is far too big, but I suspect you have few (if any) other > dbspaces! You need to reduce it in size, however this involves > re-initialising your instance and trashing all the data! > 1 Gb is probably big enough, put your PHYSFILE (which is also possibly > a bit large at 950 Mb) into its own dbspace and move all your LOGFILES > into their own space(s). > Create specific dbspaces in which to create your databases and you > will improve performanceand vastly reduce the risk of filling your > root dbspace and all its attendant heartache. > Many dbspaces also open the possibility of parallel archives. > > Keith

On 30 Nov 2006 02:19:10 -0800, doitman <sunil.saggar@gmail.com> wrote: > Thanks Keith. > > # LTXEHWM should be atleast 30% so that we could minimize log overrun > issue. > > DYNAMIC_LOGS 2 > LTXHWM 50 > LTXEHWM 60> > Dynamic logs are ON. > meaning that it will be created when previous logs fills up ..right ..? > from where these logs will be created . rootdbs ? > > > One more thing : > If i create logdbs and create the logs in that logdbs(after the system > initialization) > leaving a few logical logs in rootdbs . > Now when the logs fills up , will they be created from logdbs or > rootdbs? > > Thanks. > Keith Simmons wrote: <SNIPPED> > > > > 15 Gb is far too big, but I suspect you have few (if any) other > > dbspaces! You need to reduce it in size, however this involves > > re-initialising your instance and trashing all the data! > > 1 Gb is probably big enough, put your PHYSFILE (which is also possibly > > a bit large at 950 Mb) into its own dbspace and move all your LOGFILES > > into their own space(s). > > Create specific dbspaces in which to create your databases and you > > will improve performanceand vastly reduce the risk of filling your > > root dbspace and all its attendant heartache. > > Many dbspaces also open the possibility of parallel archives. > > > > Keith > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > Sunil New logs will be created when ALL existing logs are filled and not backed up. These will be created firstly where the existing logs are and then in root dbspace. I know of no reason why you would want to leave any logs in rootdbs, move them all into their own space(s). What is this 'log overrun issue', 5.4Gb of log space should be more than sufficient and if you have a single transaction of this size, or a long transaction spanning 50% of this log space then you have BIG applicatio problems somewhere!! Keith