Tuxedo: Expanding The Size Of A Configuration Filesystem, For Example TUXCONFIG, While Tuxedo Is Running (Doc ID 1572139.1)

Last updated on OCTOBER 03, 2024

Applies to:

Goal

When a Tuxedo filesystem(e.g. TUXCONFIG1) is not properly sized initially and Tuxedo configuration components are dynamically added beyond those initial limits we are prevented

from adding anything else without shutting Tuxedo down and redefining the filesystem.

For example - if we run tmloadcf on a configuration with MAXSERVERS 8000, and no server configured, we get a TUXCONFIG1 file of size 10000 blocks. We boot the application and dynamically add (e.g. through TMIB calls) servers continuously.

After adding a few hundred servers one gets the following message:

Normally we would then shutdown Tuxedo, rebuild the TUXCONFIG1 filesystem (e.g. "tmloadcf -b 60000 UBB"), and this would resolve the issue but with a complete outage.

How can this be done dynamically while Tuxedo is still running?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.