VCS with Solaris 10 zones

Greetings,
Has anyone tried running VCS in a zone or vice versa?
Thanks
Troy

Veritas will soon have a Beta that supports Solaris 10. Since VCS requires LLT and GAB kernel modules, I doubt you will be able to run VCS within a zone.

Similar Messages

  • Sun Live Upgrade with local zones Solaris 10

    I have M800 server running global root (/) fs on local disk and running 6 local zones on another local disk. I am running solaris 5.10 8/07.
    I used live upgrade to patch the system and created new BE (lucreate). Both root fs are mirror as RAID-1.
    When I ran lucreate, it copies all 6 local zones root fs to the global root fs and failed no enogh space.
    What is the best procedure to use lu with local zones.
    Note: I used lu with global zone only, and worked without any problem.
    regards,

    I have been trying to use luupgrade for Solaris10 on Sparc, 05/09 -> 10/09.
    lucreate is successful, but luactivate directs me to install 'the rest of the packages' in order to make the BE stable enough to activate. I try to find the packages indicated , but find only "virtual packages" which contain only pkgmap.
    I installed upgrade 6 on a spare disk to make sure my u7 installation was not defective, but got similar results.
    I got beyond luactivate on x86 a while ago, but had other snags which I left unattended.

  • Confused about ZFS filesystems created with Solaris 11 Zone

    Hello.
    Installing a blank Zone in Solaris *10* with "zonepath=/export/zones/TESTvm01" just creates one zfs filesystem:
    +"zfs list+
    +...+
    +rzpool/export/zones/TESTvm01 4.62G 31.3G 4.62G /export/zones/TESTvm01"+
    Doing the same steps with Solaris *11* will ?create? more filesystems:
    +"zfs list+
    +...+
    +rpool/export/zones/TESTvm05 335M 156G 32K /export/zones/TESTvm05+
    +rpool/export/zones/TESTvm05/rpool 335M 156G 31K /rpool+
    +rpool/export/zones/TESTvm05/rpool/ROOT 335M 156G 31K legacy+
    +rpool/export/zones/TESTvm05/rpool/ROOT/solaris 335M 156G 310M /export/zones/TESTvm05/root+
    +rpool/export/zones/TESTvm05/rpool/ROOT/solaris/var 24.4M 156G 23.5M /export/zones/TESTvm05/root/var+
    +rpool/export/zones/TESTvm05/rpool/export 62K 156G 31K /export+
    +rpool/export/zones/TESTvm05/rpool/export/home 31K 156G 31K /export/home"+
    I dont understand why Solaris 11 is doing that. Just one FS (like in Solaris 10) would be better for my setup. I want to configure all created volumes by myself.
    Is it possible to deactivate this automatic "feature"?

    There are several reasons that it works like this, all guided by the simple idea "everything in a zone should work exactly like it does in the global zone, unless that is impractical." By having this layout we get:
    * The same zfs administrative practices within a zone that are found in the global zone. This allows, for example, compression, encryption, etc. of parts of the zone.
    * beadm(1M) and pkg(1) are able to create boot environments within the zone, thus making it easy to keep the global zone software in sync with non-global zone software as the system is updated (equivalent of patching in Solaris 10). Note that when Solaris 11 updates the kernel, core libraries, and perhaps other things, a new boot environment is automatically created (for the global zone and each zone) and the updates are done to the new boot environment(s). Thus, you get the benefits that Live Upgrade offered without the severe headaches that sometimes come with Live Upgrade.
    * The ability to have a separate /var file system. This is required by policies at some large customers, such as the US Department of Defense via the DISA STIG.
    * The ability to perform a p2v of a global zone into a zone (see solaris(5) for examples) without losing the dataset hierarchy or properties (e.g. compression, etc.) set on datasets in that hierarchy.
    When this dataset hierarchy is combined with the fact that the ZFS namespace is virtualized in a zone (a feature called "dataset aliasing"), you see the same hierarchy in the zone that you would see in the global zone. Thus, you don't have confusing output from df saying that / is mounted on / and such.
    Because there is integration between pkg, beadm, zones, and zfs, there is no way to disable this behavior. You can remove and optionally replace /export with something else if you wish.
    If your goal is to prevent zone administrators from altering the dataset hierarchy, you may be able to accomplish this with immutable zones (see zones admin guide or file-mac-profile in zonecfg(1M)). This will have other effects as well, such as making all or most of the zone unwritable. If needed, you can add fs or dataset resources which will not be subject to file-mac-profile and as such will be writable.

  • Monitoring services in zones with Solaris container Manager

    I need to know how to Manage Solaris services (SMF) in sparse zone with Solaris container manager.
    I have navigated all the documentation and I have not found any clue.
    I installed the Sun management center (SMC) server on a server box and the agents on others. I can manage the SMF of the global zone by drilling down via the console GUI. But having access to the container manager, I have to go via https connection. And drilling down on the zone did not reveal that SMF can be monitored.
    Please if you have any idea, share it with me.

    Hi,
    check these:
    - Version of webserver latest is 3.1
    # smcwebserver -V
    - check webconsole is started and running
    # smcwebserver status
    Sun Java(TM) Web Console is running
    # svcs webconsole
    STATE STIME FMRI
    online 19:38:06 svc:/system/webconsole:console
    # svcs -pl webconsole
    fmri svc:/system/webconsole:console
    name java web console
    enabled true
    state online
    next_state none
    state_time Wed Feb 10 19:38:06 2010
    logfile /var/svc/log/system-webconsole:console.log
    restarter svc:/system/svc/restarter:default
    contract_id 64
    dependency require_all/none svc:/milestone/network (online)
    dependency require_all/refresh svc:/milestone/name-services (online)
    dependency require_all/none svc:/system/filesystem/local (online)
    dependency optional_all/none svc:/system/filesystem/autofs (online) svc:/network/nfs/client (online)
    dependency require_all/none svc:/system/system-log (online)
    process 843 /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4
    - check port 6789 is listen mode
    # netstat -an | grep 6789
    *.6789 *.* 0 0 49152 0 LISTEN
    if the output show
    localhost .6789 *.* 0 0 49152 0 LISTEN
    than do these:
    - check that the tcp_listen of webconsole service is true, default is false
    # svccfg -s webconsole listprop options/tcp_listen
    options/tcp_listen boolean false
    # svcadm disable svc:/system/webconsole:console
    # svccfg -s webconsole setprop options/tcp_listen=true
    # svccfg -s webconsole listprop options/tcp_listen
    options/tcp_listen boolean true
    # svcadm enable svc:/system/webconsole:console
    Regards

  • Oracle licensing in Solaris zones

    Hi all,
    I've read a few documents about Oracle licensing :
    http://www.sun.com/third-party/global/oracle/consolidation/Containers_Oracle_041305.pdf
    http://www.oracle.com/corporate/pricing/partitioning.pdf
    However, there's one thing not clear to me. In Solaris zones, you dedicate threads (usually referred to as 'CPU' on Solaris) to zones. Oracle licensing is always about the number of cores used by the partition, not the number of threads. How do you convert from threads to cores?
    I'll give an example:
    A T2 system with 2 processors, 8 cores each, 8 threads each (128 threads in total). You create a resource pool with 2 CPUs (threads): 1 thread from one core, and 1 thread from another one (or they are assigned like that for you) and associate a zone that runs Oracle.
    I can think of two ways of calculating the number of cores used:
    1) divide the number of dedicated threads by the number of threads per core: 2 / 8 = 0.25 (optionally round it up to 1) -- This is how IBM does its licensing.
    2) count the number of physical cores that are being used by the zone. In this case this is 2, as the threads are not running on the same core.
    Can anyone help me figuring this out?
    Thanks!
    Regards,
    Mathieu

    Hi Dezutterm,
    I'm not a sales guy, but from how I understand things... you've already figured it out yourself:
    dezutterm wrote:
    I'll give an example:
    A T2 system with 2 processors, 8 cores each, 8 threads each (128 threads in total). You create a resource pool with 2 CPUs (threads): 1 thread from one core, and 1 thread from another one (or they are assigned like that for you) and associate a zone that runs Oracle.
    I can think of two ways of calculating the number of cores used:
    1) divide the number of dedicated threads by the number of threads per core: 2 / 8 = 0.25 (optionally round it up to 1) -- This is how IBM does its licensing.
    2) count the number of physical cores that are being used by the zone. In this case this is 2, as the threads are not running on the same core.
    Can anyone help me figuring this out?Like you've seen, Oracle cares about how many cores are running Oracle software, not threads (from "Processor" definition here: http://www.oracle.com/corporate/pricing/technology-price-list.pdf). If you have 2 cores running Oracle software, you take "2" and multiple by the Core Processor Licensing Factor for that model of CPU (http://www.oracle.com/corporate/contracts/library/processor-core-factor-table.pdf) which for a T2 is 0.25... meaning you need 2 x 0.25 = 0.5 processor licenses. If you would have used both threads from the same core, you would need 0.25.
    If this isn't correct, somebody please let us know, thanks!
    [email protected]

  • Zfs core dumps in Solaris Zones after patchcluster installation

    Hi
    I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
    Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
    Some Output:
    Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
    bash-3.00# svcs
    STATE STIME FMRI
    online 13:58:50 svc:/system/svc/restarter:default
    online 13:58:51 svc:/system/filesystem/root:default
    online 13:58:51 svc:/network/loopback:default
    online 13:58:53 svc:/network/pfil:default
    online 13:58:54 svc:/system/installupdates:default
    online 13:58:55 svc:/system/boot-archive:default
    online 13:58:56 svc:/network/physical:default
    online 13:58:57 svc:/system/filesystem/usr:default
    online 13:58:57 svc:/system/identity:node
    online 13:58:58 svc:/system/device/local:default
    online 13:58:58 svc:/system/keymap:default
    online 13:58:58 svc:/milestone/devices:default
    online 13:58:58 svc:/system/filesystem/minimal:default
    online 13:58:58 svc:/system/rmtmpfiles:default
    online 13:58:58 svc:/system/cryptosvc:default
    online 13:58:59 svc:/system/identity:domain
    online 13:58:59 svc:/system/name-service-cache:default
    online 13:58:59 svc:/system/coreadm:default
    online 13:58:59 svc:/network/ipsec/ipsecalgs:default
    online 13:58:59 svc:/application/print/ppd-cache-update:default
    online 13:58:59 svc:/network/ipsec/policy:default
    online 13:59:00 svc:/milestone/network:default
    online 13:59:00 svc:/network/initial:default
    online 13:59:00 svc:/system/manifest-import:default
    online 13:59:00 svc:/network/service:default
    online 13:59:00 svc:/milestone/single-user:default
    online 13:59:00 svc:/network/dns/client:default
    online 13:59:00 svc:/network/routing-setup:default
    online 13:59:00 svc:/milestone/name-services:default
    online 13:59:03 svc:/milestone/sysconfig:default
    online 13:59:03 svc:/system/utmp:default
    online 13:59:03 svc:/system/console-login:default
    offline 13:58:51 svc:/system/sysidtool:net
    offline 13:58:51 svc:/network/rpc/bind:default
    offline 13:58:51 svc:/system/sysidtool:system
    offline 13:58:52 svc:/network/nfs/status:default
    offline 13:58:52 svc:/network/nfs/nlockmgr:default
    offline 13:58:52 svc:/network/nfs/cbd:default
    offline 13:58:52 svc:/network/nfs/mapid:default
    offline 13:58:52 svc:/network/inetd:default
    offline 13:58:52 svc:/network/nfs/client:default
    offline 13:58:52 svc:/system/filesystem/autofs:default
    offline 13:58:53 svc:/system/system-log:default
    offline 13:58:53 svc:/network/smtp:sendmail
    offline 13:58:53 svc:/system/cron:default
    offline 13:58:53 svc:/milestone/multi-user:default
    offline 13:58:54 svc:/application/management/snmpdx:default
    offline 13:58:54 svc:/application/management/dmi:default
    offline 13:58:54 svc:/application/management/seaport:default
    offline 13:58:54 svc:/network/ssh:default
    offline 13:58:54 svc:/milestone/multi-user-server:default
    offline 13:58:54 svc:/application/font/fc-cache:default
    offline 13:58:55 svc:/application/management/sma:default
    offline 13:58:58 svc:/system/sac:default
    offline 13:59:00 svc:/network/shares/group:default
    offline 13:59:00 svc:/system/boot-archive-update:default
    maintenance 15:34:43 svc:/system/filesystem/local:default
    uninitialized 13:58:52 svc:/network/rpc/gss:default
    uninitialized 13:58:54 svc:/application/font/stfsloader:default
    uninitialized 13:58:55 svc:/network/rpc/rstat:default
    uninitialized 13:58:55 svc:/application/print/rfc1179:default
    uninitialized 13:58:55 svc:/application/x11/xfs:default
    uninitialized 13:58:55 svc:/network/finger:default
    uninitialized 13:58:55 svc:/network/ftp:default
    uninitialized 13:58:56 svc:/network/login:rlogin
    uninitialized 13:58:56 svc:/network/nfs/rquota:default
    uninitialized 13:58:56 svc:/network/rpc/rusers:default
    uninitialized 13:58:56 svc:/network/rpc/smserver:default
    uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
    uninitialized 13:58:57 svc:/network/shell:default
    uninitialized 13:58:57 svc:/network/telnet:default
    uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
    uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
    uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
    bash-3.00# svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
    State: maintenance since Wed Dec 15 15:34:43 2010
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/system-filesystem-local:default.log
    Impact: 24 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/gss:default (Generic Security Service)
    State: uninitialized since Wed Dec 15 13:58:52 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: gssd(1M)
    Impact: 11 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/rstat:default (kernel statistics server)
    State: uninitialized since Wed Dec 15 13:58:55 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: rpc.rstatd(1M)
    See: rstatd(1M)
    Impact: 1 dependent service is not running. (Use -v for list.)
    bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
    [ Jul 10 03:41:35 Enabled. ]
    [ Jul 10 03:43:45 Rereading configuration. ]
    [ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 03:44:18 Method "start" exited with status 0 ]
    [ Jul 10 12:44:36 Enabled. ]
    [ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:44:45 Method "start" exited with status 0 ]
    [ Jul 10 12:45:03 Enabled. ]
    [ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:45:09 Method "start" exited with status 0 ]
    [ Jul 10 13:54:39 Enabled. ]
    [ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 13:54:46 Method "start" exited with status 0 ]
    [ Jul 18 12:34:19 Enabled. ]
    [ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 12:34:27 Method "start" exited with status 0 ]
    [ Jul 18 17:29:08 Enabled. ]
    [ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 17:29:15 Method "start" exited with status 0 ]
    [ Jul 19 11:13:34 Enabled. ]
    [ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:13:42 Method "start" exited with status 0 ]
    [ Jul 19 11:32:23 Enabled. ]
    [ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:32:31 Method "start" exited with status 0 ]
    [ Jul 19 11:57:06 Enabled. ]
    [ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:57:13 Method "start" exited with status 0 ]
    [ Jul 19 12:40:05 Enabled. ]
    [ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 12:40:12 Method "start" exited with status 0 ]
    [ Jul 20 15:51:46 Enabled. ]
    [ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 20 15:51:54 Method "start" exited with status 0 ]
    [ Jul 24 11:42:17 Enabled. ]
    [ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 24 11:42:25 Method "start" exited with status 0 ]
    [ Jul 27 12:05:06 Stopping because service disabled. ]
    [ Jul 27 12:05:07 Executing stop method (null) ]
    [ Jul 27 12:13:10 Enabled. ]
    [ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 12:13:17 Method "start" exited with status 0 ]
    [ Jul 27 13:10:26 Stopping because service disabled. ]
    [ Jul 27 13:10:26 Executing stop method (null) ]
    [ Jul 27 13:18:19 Enabled. ]
    [ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 13:18:26 Method "start" exited with status 0 ]
    [ Jul 31 10:12:31 Enabled. ]
    [ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 31 10:12:39 Method "start" exited with status 0 ]
    [ Aug  7 10:08:52 Stopping because service disabled. ]
    [ Aug  7 10:08:52 Executing stop method (null) ]
    [ Aug  7 10:34:50 Enabled. ]
    [ Aug  7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  7 10:34:58 Method "start" exited with status 0 ]
    [ Aug  9 09:14:50 Stopping because service disabled. ]
    [ Aug  9 09:14:50 Executing stop method (null) ]
    [ Aug  9 09:55:03 Enabled. ]
    [ Aug  9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  9 09:55:11 Method "start" exited with status 0 ]
    [ Aug 16 10:46:43 Enabled. ]
    [ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 10:46:50 Method "start" exited with status 0 ]
    [ Aug 16 12:06:56 Enabled. ]
    [ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 12:07:02 Method "start" exited with status 0 ]
    [ Aug 16 13:45:10 Enabled. ]
    [ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 13:45:16 Method "start" exited with status 0 ]
    [ Aug 16 14:36:59 Enabled. ]
    [ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 14:37:07 Method "start" exited with status 0 ]
    [ Aug 16 15:00:40 Enabled. ]
    [ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 15:00:47 Method "start" exited with status 0 ]
    [ Aug 22 16:00:13 Enabled. ]
    [ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 22 16:00:21 Method "start" exited with status 0 ]
    [ Aug 23 09:49:04 Enabled. ]
    [ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 09:49:11 Method "start" exited with status 0 ]
    [ Aug 23 09:49:23 Stopping because service disabled. ]
    [ Aug 23 09:49:23 Executing stop method (null) ]
    [ Aug 23 10:04:13 Enabled. ]
    [ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:04:20 Method "start" exited with status 0 ]
    [ Aug 23 10:06:57 Enabled. ]
    [ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:07:05 Method "start" exited with status 0 ]
    [ Oct 23 08:43:05 Enabled. ]
    [ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 23 08:43:14 Method "start" exited with status 0 ]
    [ Nov 21 14:51:50 Enabled. ]
    [ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 21 14:51:59 Method "start" exited with status 0 ]
    [ Nov 29 15:33:19 Enabled. ]
    [ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 29 15:33:27 Method "start" exited with status 0 ]
    [ Dec 18 13:37:35 Enabled. ]
    [ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 18 13:37:42 Method "start" exited with status 0 ]
    [ Dec 19 08:48:07 Enabled. ]
    [ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:48:14 Method "start" exited with status 0 ]
    [ Dec 19 08:56:07 Enabled. ]
    [ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:56:14 Method "start" exited with status 0 ]
    [ Dec 19 08:57:41 Enabled. ]
    [ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:57:48 Method "start" exited with status 0 ]
    [ Feb  1 10:39:48 Enabled. ]
    [ Feb  1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  1 10:39:56 Method "start" exited with status 0 ]
    [ Feb  8 11:12:50 Enabled. ]
    [ Feb  8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  8 11:12:57 Method "start" exited with status 0 ]
    [ Jun  6 10:08:34 Enabled. ]
    [ Jun  6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jun  6 10:08:46 Method "start" exited with status 0 ]
    [ Aug  8 09:45:48 Enabled. ]
    [ Aug  8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  8 09:46:36 Method "start" exited with status 0 ]
    [ Aug 14 17:53:59 Enabled. ]
    [ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:54:06 Method "start" exited with status 0 ]
    [ Aug 14 17:55:20 Enabled. ]
    [ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:55:27 Method "start" exited with status 0 ]
    [ Aug 18 15:19:17 Enabled. ]
    [ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 18 15:19:24 Method "start" exited with status 0 ]
    [ Aug 29 12:56:48 Enabled. ]
    [ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 29 12:56:55 Method "start" exited with status 0 ]
    [ Oct 13 11:59:43 Enabled. ]
    [ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 13 11:59:51 Method "start" exited with status 0 ]
    [ Feb 26 16:47:00 Enabled. ]
    [ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb 26 16:47:07 Method "start" exited with status 0 ]
    [ Apr 14 15:54:17 Enabled. ]
    [ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Apr 14 15:54:25 Method "start" exited with status 0 ]
    [ Aug 28 08:49:58 Stopping because service disabled. ]
    [ Aug 28 08:49:58 Executing stop method (null) ]
    [ Aug 28 08:52:54 Enabled. ]
    [ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 28 08:53:01 Method "start" exited with status 0 ]
    [ Aug 28 09:08:20 Stopping because service disabled. ]
    [ Aug 28 09:08:20 Executing stop method (null) ]
    [ Sep  1 16:05:36 Enabled. ]
    [ Sep  1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 16:06:05 Method "start" exited with status 0 ]
    [ Sep  1 19:29:19 Enabled. ]
    [ Sep  1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 19:29:27 Method "start" exited with status 0 ]
    [ Sep  1 23:04:00 Enabled. ]
    [ Sep  1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 23:04:08 Method "start" exited with status 0 ]
    [ Sep  2 00:23:41 Stopping because service disabled. ]
    [ Sep  2 00:23:42 Executing stop method (null) ]
    [ Sep  2 00:46:46 Enabled. ]
    [ Sep  2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  2 00:46:54 Method "start" exited with status 0 ]
    [ Sep 26 12:04:34 Enabled. ]
    [ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep 26 12:04:42 Method "start" exited with status 0 ]
    [ Oct 20 13:05:09 Stopping because service disabled. ]
    [ Oct 20 13:05:10 Executing stop method (null) ]
    [ Oct 20 13:24:01 Enabled. ]
    [ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 20 13:24:09 Method "start" exited with status 0 ]
    [ Oct 21 16:30:59 Enabled. ]
    [ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:31:09 Method "start" exited with status 0 ]
    [ Oct 21 16:32:42 Stopping because service disabled. ]
    [ Oct 21 16:32:42 Executing stop method (null) ]
    [ Oct 21 16:42:05 Enabled. ]
    [ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:42:15 Method "start" exited with status 0 ]
    [ Oct 21 17:27:37 Enabled. ]
    [ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 17:27:47 Method "start" exited with status 0 ]
    [ Oct 22 11:08:34 Enabled. ]
    [ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 22 11:08:43 Method "start" exited with status 0 ]
    [ Dec  9 09:17:33 Stopping because service disabled. ]
    [ Dec  9 09:17:33 Executing stop method (null) ]
    [ Dec 10 11:47:14 Enabled. ]
    [ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
    [ Dec 10 11:47:25 Method "start" exited with status 0 ]
    [ Dec 15 10:52:25 Stopping because service disabled. ]
    [ Dec 15 10:52:25 Executing stop method (null) ]
    [ Dec 15 12:42:16 Enabled. ]
    [ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 12:42:28 Method "start" exited with status 95 ]
    [ Dec 15 13:13:19 Enabled. ]
    [ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:13:30 Method "start" exited with status 95 ]
    [ Dec 15 13:58:51 Enabled. ]
    [ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:59:03 Method "start" exited with status 95 ]
    [ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
    [ Dec 15 15:34:41 Enabled. ]
    [ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 15:34:43 Method "start" exited with status 95 ]
    bash-3.00# /usr/sbin/zfs mount -a
    internal error: Unknown error
    Abort (core dumped)
    Before that I've installed the patch cluster with halted solaris zones which produced following output:
    Application of patches finished : 2010.12.15 12:08:43
    Following patches were applied :
    119254-77 119812-10 125719-31 140159-03 142911-01
    141588-04 119900-11 125731-05 142292-01 142933-02
    142251-02 119906-16 126206-05 141444-09 142909-17
    118666-28 120460-17 126363-08 141500-07 143140-04
    118667-28 121012-03 126365-16 141502-02 143502-01
    118777-16 121308-20 126868-04 141506-09 143506-01
    140860-02 122212-40 127724-02 141514-02 143615-02
    119059-56 122261-03 136998-09 141518-12 143731-01
    119213-23 122675-05 137000-07 141552-03 143733-01
    124628-10 123003-04 137080-05 141558-01 143977-01
    119252-29 123590-12 137147-06 141586-01 144053-04
    119280-23 123893-22 138195-04 141590-02 144106-01
    124188-03 124393-11 138822-07 141874-09 144254-01
    120199-15 124457-02 138826-07 141876-07 144488-04
    119534-19 124630-42 138880-02 142084-04 144492-01
    120272-28 125215-03 139099-04 142397-01 145124-01
    119757-18 125388-03 139620-01 142529-01 145796-01
    119783-15 125555-07
    Following patches were skipped :
    Patches already applied
    120900-04 119063-01 119810-05 123005-07 137093-01
    121133-02 119081-25 119986-03 124444-01 138866-03
    119317-01 119130-33 120061-02 124939-03 137137-09
    121296-01 123611-04 120201-05 124943-01 137871-02
    138215-01 140899-01 120292-02 124997-01 138181-01
    127884-01 122640-05 120329-02 125279-05 138361-01
    118712-23 126897-02 121975-01 125539-06 138373-02
    118918-24 127755-01 120719-02 125891-01 138647-01
    138217-01 125503-02 120830-06 126440-01 141016-01
    119578-30 125547-02 121095-02 126540-02 139555-08
    121453-02 140796-01 121606-04 127127-11 139967-01
    121453-02 120011-14 124171-07 136882-02 140455-01
    121118-16 139520-02 123630-03 137032-01 140563-01
    118833-36 119764-06
    Patches obsoleted by one or more patches already applied
    118731-01 124204-04 122660-10
    Patches not applicable to packages on the system
    121181-03 120410-33 121211-02 125533-15 143317-03
    119115-35 120412-11 122259-03 125541-06 143510-01
    119117-52 120414-27 122470-03 125952-20 143725-01
    119315-19 120543-21 122911-24 137004-08 143727-01
    119548-14 120739-06 122958-06 138387-01 143739-01
    119903-02 120811-09 123938-02 138824-07 144325-01
    120094-30 120849-04 125136-24 138876-01 145006-02
    120185-21 121104-11 125137-24 139986-01 145080-01
    119368-04 121136-02 125332-14 142244-02 145200-01
    120286-03
    Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
    when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
    Does anyone have got an idea how to find out which patch or whatever do produce these errors?

    Hi,
    I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
    I answered the following questions asked by the grid deinstall tool:
    1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
    2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
    3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
    4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
    If I answer no to question 1, the tool exits with error.
    How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
    Deinstall of Oracle db Home 11.2.0.1 was successful.
    The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
    Thanks,
    Lisa
    Edited by: user12018917 on Apr 19, 2011 10:21 AM

  • [SOLVED] SGA_MAX_SIZE pre-allocated with Solaris 10?

    Hi all,
    I'm about to build a new production database to migrate an existing 8.1.7 database to 10.2.0.3. I'm in the enviable position of having a good chunk of memory to play with on the new system (compared with the existing one) so was looking at a suitable size for the SGA... when something pinged in my memory about SGA_MAX_SIZE and memory allocation in the OS where some platforms will allocate the entire amount of SGA_MAX_SIZE rather than just SGA_TARGET.
    So I did a little test. Using Solaris 10 and Oracle 10.2.0.3 I've created a basic database with SGA_MAX_SIZE set to 400MB and SGA_TARGET 280MB
    $ sqlplus
    SQL*Plus: Release 10.2.0.3.0 - Production on Wed Jan 30 18:31:21 2008
    Copyright (c) 1982, 2006, Oracle.  All Rights Reserved.
    Enter user-name: / as sysdba
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    SQL> show parameter sga
    NAME                                 TYPE        VALUE
    lock_sga                             boolean     FALSE
    pre_page_sga                         boolean     FALSE
    sga_max_size                         big integer 400M
    sga_target                           big integer 280MSo I was expecting to see the OS pre-allocate 280MB of memory but when I checked the segment is actually the 400MB (i.e. SGA_MAX_SIZE) (my database owner is 'ora10g'):
    $ ipcs -a
    IPC status from <running system> as of Wed Jan 30 18:31:36 GMT 2008
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP CBYTES  QNUM QBYTES LSPID LRPID   STIME    RTIME    CTIME
    Message Queues:
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP NATTCH      SEGSZ  CPID  LPID   ATIME    DTIME    CTIME
    Shared Memory:
    m         22   0x2394e4   rw-r---   ora10g   10gdba   ora10g  
    10gdba     20  419438592  2386  2542 18:31:22 18:31:28 18:28:18
    T         ID      KEY        MODE        OWNER    GROUP  CREATOR  
    CGROUP NSEMS   OTIME    CTIME
    Semaphores:
    s         23   0x89a070e8 ra-r---   ora10g   10gdba   ora10g  
    10gdba   154 18:31:31 18:28:18
    $ I wasn't sure whether Solaris 10 was one of the OSs with truly dynamic memory for the SGA but had hoped it was... this seems to say different. Really I'm just after some confirmation that I'm reading this correctly.
    Thanks.
    Joseph
    Message was edited by:
    Joseph Crofts
    Edited for clarity

    I don't want to get bogged down in too many details, as the links provided in previous posts have many details of SGA tests and the results of what happened. I just want to add a bit of explanation about the Oracle SGA and shared memory on UNIX and Solaris in particular.
    As you know Oracle's SGA is generally a single segment of shared memory. Historically this was 'normal' memory and could be paged out to the swap device. So a 500 MB SGA on a 1 GB physical memory system, would allocate 500 MB from the swap device for paging purposes, but might not use 500 MB of physical memory i.e. free memory might not decrease by 500 MB. How much physical memory depended on what pages in the SGA were accessed, and how frequently.
    At some point some people realised that this paging of the SGA was actually slowing performance of Oracle, as now some 'memory' accesses by Oracle could actually cause 'disk' accesses by paging in saved pages from the swap device. So some operating systems introduced a 'lock' option when creating a shared memory segment (shmat system call if memory serves me). And this was often enabled by a corresponding Oracle initialisation parameter, such as lock_sga.
    Now a 'locked' SGA did use up the full physical memory, and was guaranteed not to be paged out to disk. So Oracle SGA access was now always at memory speed, and consistent.
    Some operating systems took advantage of this 'lock' flag to shared memory segment creation to implement some other performance optimisations. One is not to allocate paging storage from swap space anyway, as it cannot be used by this shared memory segment. Another is to share the secondary page tables within the virtual memory sub-system for this segment over all processes attached to it i.e. one shared page table for the segment, not one page table per process. This can lead to massive memory savings on large SGAs with many attached shadow server processes. Another optimisation on this non-paged, contiguous memory segment is to use large memory pages instead of standard small ones. On Solaris instead of one page entry covering 8 KB of physical memory, it covers 8 MB of physical memory. This reduces the size of the virtual memory page table by a factor of 1,000 - another major memory saving.
    These were some of the optimisations that the original Red Hat Enterprise Linux had to introduce, to play catch up with Solaris, and to not waste memory on large page tables.
    Due to these extra optimisations, Solaris chose to call this 'locking' of shared memory segments 'initimate shared memory' or ISM for short. And I think there was a corresponding Oracle parameter 'use_ism'. This is now the default setting in Oracle ports to Solaris.
    As a result, this is why when Oracle grabs its shared memory segment up front (SGA_MAX_SIZE), it results in that amount of real physical memory being allocated and used.
    With Oracle 9i and 10g when Oracle introduced the SGA_TARGET and other settings and could dynamically resize the SGA, this messed things up for Solaris. Because the shared memory segment was 'Intimate' by default, and was not backed up by paging space on the swap device, it could never shrink in size, or release memory as it could not be paged out.
    Eventually Sun wrote a work around for this problem, and called it Dynamic Intimate Shared Memory (DISM). This is not on by default in Oracle, hence you are seeing all your shared memory segments using the same amount of physical memory. DISM allows the 'lock' flag to be turned on and off on a shared memory segment, and to be done over various memory sizes.
    I am not sure of the details, and so am beginning to get vague here. But I remember that this was a workaround on Sun's part to still get the benefits of ISM and the memory savings from large virtual memory pages and shared secondary page tables, while allowing Oracle to manage the SGA size dynamically and be able to release memory back for use by other things. I'm not sure if DISM allows Oracle to mark memory areas as pageable or locked, or whether it allows Oracle to really grow and shrink the size of a single shared memory segment. I presumed it added yet more flags to the various shared memory system calls.
    Although DISM should work on normal, single Solaris systems, as you know it is not enabled by default, and requires a special initialisation parameter. Also be aware that there are issues with DISM on high end Solaris systems that support Domains (F15K, F25K, etc.) and in Solaris Zones or Containers. Domains have problems when you want to dynamically remove a CPU/Memory board from the system, and the allocations of memory on that board must be reallocated to other memory boards. This can break the rule that a locked shared memory segment must occupy contiguous physical memory. It took Sun another couple of releases of Solaris (or patches or quarterly releases) before they got DISM to work properly in a system with domains.
    I hope I am not trying to teach my granny to suck eggs, if you know what I mean. I just thought I'd provide a bit more background details.
    John

  • EM 12c and Solaris Zone Monitoring

    Hi all,
    I am using Oracle EM 12c to monitor Oracle database server which run on Solaris zone, which is capped to run using only 4 cores.
    BUT the Host management home page is still showing "Total Cores" of 8 (I am using Sun T4-1).
    Is there some configuration which required to be done to reflect the number of capped CPU.
    Also is there a way to isolate the CPU, Memory, Filesystem and Network utilization to only look at the local zone?
    I suspect what I see now represent the resource utilization of the physical machine.
    Thank you.
    -Joel

    Loc,
    I've opened quite a few SRs, some handled well, some not. My biggest issue perhaps is that SRs are needed at all. We are a small shop that relied on OEM 10.2 for a long time, skipped over 11G and went right to 12R2. It was a culture shock, and I'm not sure if skipping the version added to our woes.
    There are 3 DBAs here, with Oracle experience between 13 and 18 years, we are not newbies. I took the em12c class from Oracle.
    But still, acceptance of its use has not been high, mostly because it's no longer the quick, targeted place we 'go to'. It's a huge product now, with much built-in. We are finding we need a mind adjustment to use it and the transition period related to how much time we can spend on that. Our intent, though, was to make things easier, not harder.
    Case in point is our implementation of DataGuard. This project was new to us and I made EM12C upgrade as a predecessor project because I needed its help. I ultimately abandoned it, we hired a consultant, we learned manual steps, and that's what we use today. Everything is homegrown.
    I feel as through the purpose for EM moved from a DBA monitoring tool. Remember OEM 10.2 and its initial summary page that showed the overall health of everything on one shot? I can't do that in em12c, or at least haven't found that.
    Here are some SRs:
    SR 3-6392247151
    Sr 3-7159111371
    SR 3-6645421051
    * SR 3-6608820051
    SR 3-6667182071
    * Covers "invalid objects" missing, something we previously relied on.
    Back to the original question of this post - I understand now that if we use EM to switch our databases, the role reversal will show. We would have loved to rely on EM for everything. Now that we must do everything manually, I have to then manually drop the target being monitored and re-add it. Again, something that should make our jobs easier is now harder.
    Thanks for listening. Am I really the only DBA that says EM12C is harder to use for basic functionality?
    Sherrie

  • Routing in solaris zones

    Lets see the hypothetical situation. I have Solaris 10 with 3 zones ( + global).
    I have 4 network interfaces. Every zone has it's own interface.
    Now from what i've learnt all network configuration must be done in global zone. It means that every single network interface must have an adress assigned in the global zone even if i only intend to use it in sub zone. Also all routes must be added in global zone (if i try to add anything in sub zone i am disallowed with information "operation not permitted"). Every interface needs its own default gateway, so i have 3 default gws in global zone. What more every sub zone inherits all default gws, which is very confusing to the network traffic. I want a situation, where every zone inherits only part of routing which is intented for that very zone. How can i achieve that if i have to do all routing in global zone and after adding any route it appears automatically in sub zones?

    From my understandig Solaris 11 is going to offer some features you're requesting right now. For now you can take a look a defining routes yourself to match the behavior you want, or take a look at zebra if you have routing protocols available on your network. But I have to urge you to consult your networkadministrator before you continue in both case so you don't take down your system or the network.

  • SAP Java and Solaris Zones SolMan 4.0

    May require Solaris Zones experience to continue.
    I have three SAP database instances/central instances running in three sparse Solaris zones with no problem.
    I have created a new sparse zone for a new SAP installation (Solution Manager 4.0) and started the installation. SAP requires a 1.4.2 SDK even though Java 1.5 comes with Solaris 10. The 1.4.2 SDK is in /usr/j2se. The installation in the sparse zone errors out because it can't get "write" rights to /usr/j2se/jre/lib/security/local_policy.jar as it is trying to install some security encryption JCE component.
    I have thought about creating a /usr/j2se_zonename file system, copying the contents of /usr/j2se into it and then mounting /usr/j2se_zonename in the zone as a lofs with the name /usr/j2se. However when I do the copy of /usr/j2se I get some recursion errors.
    Any thoughts about how to add a writable /usr/j2se into the sparse zone with the least amount of effort ? Otherwise plan B would be to create a "large" zone with a writable /usr directory.
    Received a great answer, that while it may not be architecturally "pure" it may get the job done.
    You might just download the relevant JDK tarball and unpack that
    somewhere in your zone (anywhere you like), and point SAP at it...
    http://java.sun.com/j2se/1.4.2/download.html
    Get the one called "self extracting file"-- you can unpack that anywhere
    you want.
    Message was edited by: Atis Purins

    Hi Russ,
    no you only have to generate two RFCs to your R/3 and assign them in SMSY to for system monitoring
    Then you need a Solution, assign your R/3 to the Solution, setup the system monitoring.
    Regards,
    uDo

  • Resource Management and Solaris Zones Developer Guide

    Solaris Information Products ("Pubs") is creating a
    developer guide for resource management and Solaris Zones.
    The department is seeking input on content from application
    developers and ISVs.
    We plan to discuss the different categories of applications
    that can take advantage of Solaris resource management
    features, and provide implementation examples that discuss
    the particular RM features that can be used.
    Although running in a zone poses no differences to most
    applications, we will describe any possible limitations and
    offer appropriate workarounds. We will also provide
    information needed by the ISV, such as determining
    the appropriate system calls to use in a non-global zone.
    We plan to use case studies to document the zones material.
    We would like to know the sorts of topics that you would
    like to see covered. We want to be sure that we address
    your specific development concerns with regard to these
    features.
    Thank you for your comments and suggestions.

    Hi there, i'm using solaris resource management in a
    server with more thant 2thousand acounts.
    Created profiles for users, defaul, staff, root and
    services.Seeing the contents of your /etc/project file could be helpful.
    But while using rctladm to enable syslog'ing, I set up
    global flags of "deny" and "no-local-action" in almos
    everything.The flags on the right hand side of the rctladm(1M) output are read-only:
    they are telling you the characteristics of the resource control in question (what
    operations the system will allow the resource control to take).
    Now, many aplications don't work because they are
    denied enough process.max-stack-size and
    process.max-file-descriptor for them to work.
    Applications such has prstat.If prstat(1) is failing due to the process.max-file-descriptor control value, that's
    probably a bug. prstat(1) is more likely bumping into the limit to assess how many file
    descriptors are available, and then carrying on--you're just seeing a log message since
    prstat(1) tested the file descriptor limit, and you've enabled syslog for that control. Please
    post the prstat(1) output, and we'll figure out if something's breaking.
    I don't find a way to disable the global flags. You can't. I would disable the syslog action on the process.max-stack-size control first;
    there is an outstanding bug on this control, in that it will report a false triggering event--
    no actual effect to the process. (If you send me some mail, I will add you as a call record
    on the bug.)
    Can anyone tell me:
    how to disable global flags?
    how to disable and enable solaris resource management
    all together?You could raise all of the control values, but the resource control facility (like the resource
    limit facility it superseded) is always active. Let's figure out if you're hitting the bug I mentioned,
    and then figure out how to proceed.
    - Stephen
    Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
    [email protected]

  • Cluster Patch on Solaris Zones

    Hi all,
    Lately, there is a requirement for us to perform a cluster patch on some of
    our Solaris Zone VMs. Under such circumstances, is there a need to patch
    the global zone also ? What are the precautionary measures to take in case
    things break and system goes into panic mode ?
    Pls provide all necessary steps and procedures. Thanks a lot.
    Regards,
    LP

    There are many available patch clusters, however you would normally use the 'Recommended Patch Cluster" or the latest dated cluster, for example "10/08 Patch Bundle". Note that the latest bundles have been split into multiple parts due to the size increase from older bundles.
    Please refer to the [download instructions|http://sunsolve.sun.com/html/cluster_bundle.html] and the readme for the relevant cluster that you download. Note that a password is required to apply that patch clusters and that the password can be found in the readme.
    If you run into any problems with the clusters, please contact [email protected] .

  • OSB and Solaris Zones

    Hi,
    Does anybody have any experience of running OSB inside a Solaris zone?
    I'm experimenting with this at the moment and would like to share the OSB installation with the global zone, but keep the /usr/etc and /usr/tmp directories where the host-specific stuff is stored private.
    Thanks.

    I following Oracle® Secure Backup Installation and Configuration Guide
    Release 10.3 :
    - To Viewing SCSI Bus Name-Instance Parameter Values in Solaris :
    # cd /usr/local/oracle/backup/install
    # installdriver
    bash: installdriver: command not found
    # ./installdriver
    case: Too many arguments
    How could i can run the installdriver script for SCSI information
    Best Regards
    Ch

  • Recommendations for Solaris Zones for NW2004S?

    I'm new to Solaris zones and would appreciate any recommendations from you regarding the setup of zones to run NW2004S. I did a scan of SapNet and SDN, but found nothing.
    So, for example, would you insist on running a Prod instance in the global zone?  For an SAP that runs in a zone, which file-systems would you share from the global zone?
    Another tips/traps you have would be greatly appreciated.

    We consolidated already 7 systems:
    root@consbig / >zoneadm list -vi
      ID NAME             STATUS         PATH                         
       0 global           running        /                            
      22 srmtest          running        /zone/srmtest                
      23 nwdi_ext_1       running        /zone/nwdi_ext_1             
      32 bbbcpy           running        /zone/bbbcpy                 
      35 icht             running        /zone/icht                   
      40 osiris           running        /zone/osiris                 
      42 bi_oracle_test   running        /zone/biorat                 
      43 hpvm             running        /zone/hpvm      
    This is a HP DL585 with 4 CPUs and 48 GB RAM (Opteron, not SPARC).

  • Best Practices for patching Sun Clusters with HA-Zones using LiveUpgrade?

    We've been running Sun Cluster for about 7 years now, and I for
    one love it. About a year ago, we starting consolidating our
    standalone web servers into a 3 node cluster using multiple
    HA-Zones. For the most part, everything about this configuration
    works great! One problem we've having is with patching. So far,
    the only documentation I've been able to find that talks about
    patch Clusters with HA-Zones is the following:
    http://docs.sun.com/app/docs/doc/819-2971/6n57mi2g0
    Sun Cluster System Administration Guide for Solaris OS
    How to Apply Patches in Single-User Mode with Failover Zones
    This documentation works, but has two major drawbacks:
    1) The nodes/zones have to be patched in Single-User Mode, which
    translates to major downtime to do patching.
    2) If there are any problems during the patching process, or
    after the cluster is up, there is no simple back out process.
    We've been using a small test cluster to test out using
    LiveUpgrade with HA-Zones. We've worked out most of bugs, but we
    are still in a position of patching our HA-Zoned clusters based
    on home grow steps, and not anything blessed by Oracle/Sun.
    How are others patching Sun Cluster nodes with HA-Zones? Has any
    one found/been given Oracle/Sun documentation that lists the
    steps to patch Sun Clusters with HA-Zones using LiveUpgrade??
    Thanks!

    Hi Thomas,
    there is a blueprint that deals with this problem in much more detail. Actually it is based on configurations that are solely based on ZFS, i.e. for root and the zone roots. But it should be applicable also to other environments. "!Maintaining Solaris with Live Upgrade and Update On Attach" (http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach)
    Unfortunately, due to some redirection work in the joint Sun and Oracle network, access to the blueprint is currently not available. If you send me an email with your contact data I can send you a copy via email. (You'll find my address on the web)
    Regards
    Hartmut

Maybe you are looking for