Hi,

I'm running containers/zones on Solaris 10:

SunOS be2900 5.10 Generic_118833-33 sun4u sparc SUNW,Netra-T12

zoneadm list -vc gives:

ID NAME STATUS PATH
0 global running /
1 bvsmapp01 running /zones/bvsmapp01
2 bvsmapp04 running /zones/bvsmapp04
3 bvsmdb01 running /zones/bvsmdb01
4 bvsmapp03 running /zones/bvsmapp03
5 bvsmapp02 running /zones/bvsmapp02
6 bvsmapp05 running /zones/bvsmapp05

The zone ID 3 called bvsmdb01 is the database zone; this needs to be started up before all the other zones following a reboot. All the databases on bvsmdb01 (118 Oracle9i and Oracle10g databases) need to be started up and open before zones 1,2,4,5,6 are started. Otherwise the automatic startup of the applications on these zones will fail - they will not be able to connect to an open database.

All zones are currently set to automatically reboot.

How can I guarantee that the database zone is rebooted first following a full server reboot and that all the databases on that database zone are open and available before the other zones are rebooted?

Thanks,

Jabberwocky

If thats the case, I will rather have the database sitting in my global zone.
If you insist on booting from the zone, then you'll have to disable auto boot and do it manually. If you're using VCS cluster for eg, all this can be controlled easily

for the time being, i would make a script for this. place it in the legacy. set each to autoboot false and have the script boot up each zone appropriately and in the order you want.

That'll be the way to go for now. Scripting that out is pretty easy.