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.
Original Message:
Sent: Fri January 30, 2026 06:42 AM
From: Art Kagel
Subject: Logical log's and initialize new instance
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
Original Message:
Sent: Fri January 30, 2026 06:31 AM
From: wayne martin
Subject: Logical log's and initialize new instance
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