Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
wayne martin described why a new instance starts with six small logical logs in rootdbs and said configuring it takes most of a day. Art Kagel disagreed, saying 30 minutes with scripts. Hedwig Fuchs suggested the installer's instance option, Mike Walker suggested dbschema -c for a head start, and Paul Watson agreed about 15-30 minutes unless the instance is huge.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
wayne martin — source: IBM Community (ConnectedCommunity.org) Informix forum
Hi group,
The logic for 6 small log's at initialize a new instance and in root dbspace is :
we know that dbspace will be there.
A lot of on config values are set to small / starting values to get instance up and initialized.
Then set up instance:
add new dbspace's / chunks
Move / create physical log's / logical log's in a different dbspace
update a lot of config values for the environment.
It would take most of the day to get this done with (scripts, commands, restarts).
Wayne
↪ replying to wayne martin
Art Kagel — source: IBM Community (ConnectedCommunity.org) Informix forum
Wayne:
I'm not sure if you have a question with your post or seek to answer one that I don't remember from a parallel thread.
That said, I would take issue with the statements that "It would take most of the day to get this done with (scripts, commands, restarts)." Where "this" is initializing and then configuring a new instance. With planning and, as you note, scripting, it should not take more than 30 minutes tops to set up a new instance including fleshing out the logging (physical and logical), adding expected dbspaces and their chunks, editing the sqlhosts file, and updating the ONCONFIG file with best guess tunable settings.
Art
------------------------------
Art S. Kagel, President and Principal Consultant
ASK Database Management Corp.
www.askdbmgt.com
------------------------------
↪ replying to Art Kagel
Hedwig Fuchs — source: IBM Community (ConnectedCommunity.org) Informix forum
You can try the option to create an instance during installation of the product. This will create a "bigger instance" but very likely not an instance which meets your needs.
------------------------------
Hedwig Fuchs
------------------------------
↪ replying to wayne martin
Mike Walker — source: IBM Community (ConnectedCommunity.org) Informix forum
If you have any kind of running Informix instance now, you could run "dbschema -c" or "dbschema -c -ns" to generate the SQL or the commands that can be used as a head start to set up an instance. Do not run the same commands against the same instance that you run dbschema against, but it will have the statements that you need to create dbspaces, logical logs, etc. You can take these commands and adapt them for your needs. It won't update your onconfig, or create your sqlhosts, or create the underlying files or LVs for your chunks, but it might simplify the process of creating your chunks and logs.
Mike
------------------------------
Mike Walker
xDB Systems, Inc
www.xdbsystems.com
------------------------------
↪ replying to wayne martin
Paul Watson — source: IBM Community (ConnectedCommunity.org) Informix forum
Unless the instance is huge then this 15/30 minutes process. Large dbspaces and encrytion take times
On 1/30/2026 5:31 AM, wayne martin via IBM TechXchange Community wrote:
0100019c0eac2800-7e8bc75b-1e19-4cd3-888c-33beb01f2ee8-000000@email.amazonses.com">
Hi group, The logic for 6 small log's at initialize a new instance and in root dbspace is : we know that dbspace will be there. A lot of on... -posted to the "Informix" group
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.