Solaris Cluster 4 with Solaris 11/11/11 -- LDOM farm

Hi,
In the 2011 Openworld, I had the opportunity to meet some of the Oracle cluster experts. In conversations, I found that when configuring LDOMs within a clustered environments, we could pass a complete "/dev/did/*dsk/d<num>" device directly to the guest domain.
Are there any notes/whitepapers that someone within Oracle could direct me to that elaborates this a little more? I can reach out via our regular pre-sales channels, but I'm posting here since I know the Cluster gurus frequent this watering hole :)

Hi Hartmut,
I chose to use the DID namespace because of it's simplicity. I can reference a /dev/did/rdsk/d<> and be consistent across the cluster. Also, since I'm using HA to cluster the LDOMs, I don't have to worry about bringing up resources on the Control domain (since all the FC storage I use is for guest domains). The control domains themselves (which are also the IO domains) have the internal drives of the T4-4 that contain the rpool etc.
My vds devices look like this --
<pre>
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
primary_vds0 sol11 /local/sol-11-1111-text-sparc.iso
sol10u10 ro /local/sol-10-u10-ga2-sparc-dvd.iso
primary_shared_vds1 d9 /dev/did/dsk/d9s2
d11 /dev/did/dsk/d11s2
d12 /dev/did/dsk/d12s2
d25 /dev/did/dsk/d25s2
d27 /dev/did/dsk/d27s2
d28 /dev/did/dsk/d28s2
d29 /dev/did/dsk/d29s2
d30 /dev/did/dsk/d30s2
d31 /dev/did/dsk/d31s2
d32 /dev/did/dsk/d32s2
d33 /dev/did/dsk/d33s2
d34 /dev/did/dsk/d34s2
d35 /dev/did/dsk/d35s2
d36 /dev/did/dsk/d36s2
d37 /dev/did/dsk/d37s2
</pre>
Edited by: implicate_order on May 11, 2012 2:11 PM
Also, I have a script that extracts the EMC array ID, scsi id, ctd name and size etc from the DID framework.
Edited by: implicate_order on May 11, 2012 2:11 PM

Similar Messages

Issue with installation of Solaris 10 UFS in Ldoms

Hi Guys, I'm trying to install Solaris 10 with UFS but not able to make more than one partition. My vdisk is a slice of physical server hard disk.
When I try to modify the table partition of vdisk, it fails.
I cheeked in documentation and saw that vdisk can only be use for one whole s0 partition. How can I create swap and other partition?
Someone have try to install Solaris 10 UFS in Ldoms with success??

Thank a lot Pascal,
I Also use file container and it work fine!!

Error while creating zone inside Solaris 11.2 beta ldom

hi
i have installed solaris 11.2 in ldom (sparc ovm 3.1 )
and i try to create zone inside guest domain , it always give this error
Error occurred during execution of 'generated-transfer-3442-1' checkpoint.
        Failed Checkpoints:
        Checkpoint execution error:
                Error refreshing publishers, 0/1 catalogs successfully updated:
                Framework error: code: 28 reason: Operation too slow. Less than 1024 bytes/sec transfered the last 30 seconds
                URL: 'http://pkg.oracle.com/solaris/beta/solaris/catalog/1/catalog.summary.C' (happened 4 times)
Installation: Failed. See install log at /system/volatile/install.3442/install_log
ERROR: auto-install failed.

You might want to tune PKG_CLIENT_LOWSPEED_TIMEOUT before running "zoneadm install"
For example:
# export PKG_CLIENT_LOWSPEED_TIMEOUT=300

Issue listeneing queue from Weblogic Cluster server with multiple managed server

Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
--ManagedServer01(http://server01.myhost.com:7001)
--ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
JMSserver01 targeting: ManagedServer01
JMSserver02 targeting: ManagedServer02
JMSmodule
ConnectionFactory01 targeting:JMSserver01,JMSserver02
UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
mysystemmodule!JMSserver01@UDQueue01
mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
mysystemmodule!JMSserver01@UDQueue01 10
mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
mysystemmodule!JMSserver01@UDQueue01 0
mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.

You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz

How to get cluster name with c++ API?

Hi everyone,
I want to get cluster name with c++ API, do you know how to do that?
Thanks very much!!!
Guangyin

937347 wrote:
Hi Robert,
For Java, we can get the cluster name like this:
cache.getCacheService.getCluster().getClusterName(),
for c++, just as you said, do you mean that i can try to get cluster name like this:
Sting::View name = cache->getCacheService()->getInfo()->getServiceName();
InvocationService::handle invocation = cast<InvocationService::handle>(CacheFactory::getService(name));
String clusterName = invocation->getInfo()->getServiceName();
But i can not get the right result.
I know little about how to use InvocationService, could you give me example?
Thanks very much!!!
GuangyinHi Guangyin,
I do not know the C++ API, I never used it, but what you wrote definitely does not look right.
InvocationService is a way to send arbitrary Java logic (you need to write both the Java logic and a C++ counterpart class, the C++ class will serialize itself with POF and the Java class will deserialize the same data appropriately) as a command to the cluster via the TCP*Extend connection and the command would execute on the proxy node and thus it would have access to the cluster itself.
You probably should start with the documentation of the Coherence*Extend C++ API documentation for samples.
http://docs.oracle.com/cd/E24290_01/coh.371/e22839/toc.htm
http://docs.oracle.com/cd/E24290_01/coh.371/e22839/cpp_part.htm#CHDHCIEJ
Best regards,
Robert

Start a cluster locally with 2 nodes

Hi,
I just want to ask that how to start a cluster locally with 2 nodes?
By default i think that it starts only 1.
Thanks

Hi,
Just start another instance of the same process using the same coherence configuration and they will form a cluster.
mark

TES v6.1 want to install a Win Tidal Agent on a Cluster Resource with Fail Over... help

I am working with my Window Admins and they want to know how to install the Win Tidal Agent on a Cluster Resource with Fail Over. Currently running Tidal Master (UNIX) v6.1.0.483
Thanks,
Rich

Please refer to the Agent Installation and Configuration guide.pdf from Cisco. The steps to configure the agents in a cluster have been explained in section Configuring the Agents for a Cluster

[svn] 2277: 1) Update the messaging-config. xml under resource and add the cluster definition with shared-backend attribute .

Revision: 2277
Author: [email protected]
Date: 2008-06-27 08:22:18 -0700 (Fri, 27 Jun 2008)
Log Message:
1) Update the messaging-config.xml under resource and add the cluster definition with shared-backend attribute. [#blz-197]
2) Minor update to the session test.
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-197
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/src/remoting/session/FlexSessionAttribu teListenerTest.java
blazeds/branches/3.0.x/resources/config/messaging-config.xml

To use servlets u have indeed to update your web.xml...Well I'm not sure this is relevant to your case anyway.
You have to add a <servlet> element to this file.
Something like this:
<servlet>
<servlet-name>blabla</servlet-name>
<servlet-class>blablapackage.Blablaclass</servlet-class>
<init-param>...</init-param>
</servlet>
Now this may not solve your problem. Make sure you refer to your servlets using their full qualified names.btw, just to be sure, what is your definition of "servlet"? (i mean: any java class or only javax.servlet.Servlet)

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

Cluster test with zones

Hi there,
I would like to install and test sun cluster software. I installed 64 bit Solaris 10 into vmware workstation 6. Is it possible to setup some zones and test sun cluster software within one solaris installation? Or do I have to install 2 solaris into vmware and then go with cluster?

You can install a single node cluster. You may need to change /etc/syslog.conf to lower the severity level to ignore the pm_tickdelay messages to kernel.notice. Although not supported, this is a very good environment for development and testing.
And it is also possible to have a resource group failing over between two non-global zones running on that single-node cluster. For an example have a look at http://blogs.sun.com/SC/entry/new_solaris_10_experience which describes how to set this up for HA samba.
Greets
Thorsten

J2EE Recommended Patch Cluster fails with Kernel patch 108528-26

As part of the J2EE recommended cluster, I attempted installing patch 108528-26 to my Solaris 8 box (all of which was downloaded from sun.com):
SunOS boedev 5.8 Generic_108528-14 sun4u sparc SUNW,UltraAX-MP
It failed and rolled back as part of the cluster with the following error log:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Without rebooting, I then downloaded the patch from sunsolve as a separate patch and attempted to load it with patchadd, to no avail but with additional errors (WARNING:) along with the original ones:
Package not patched:
PKG=FJSVhea
Original package not installed.
Package not patched:
PKG=FJSVmdb
Original package not installed.
Package not patched:
PKG=FJSVmdbx
Original package not installed.
Package not patched:
PKG=FJSVvplr.us
Original package not installed.
Package not patched:
PKG=FJSVvplu.us
Original package not installed.
Package not patched:
PKG=SUNWcar.d
Original package not installed.
Package not patched:
PKG=SUNWcar.m
Original package not installed.
Package not patched:
PKG=SUNWcar.us
Original package not installed.
Package not patched:
PKG=SUNWcarx.us
Original package not installed.
Package not patched:
PKG=SUNWcpc.us
Original package not installed.
Package not patched:
PKG=SUNWcpcx.us
Original package not installed.
Package not patched:
PKG=SUNWcpr.m
Original package not installed.
Package not patched:
PKG=SUNWcpr.us
Original package not installed.
Package not patched:
PKG=SUNWcprx.us
Original package not installed.
Package not patched:
PKG=SUNWdrr.u
Original package not installed.
Package not patched:
PKG=SUNWdrr.us
Original package not installed.
Package not patched:
PKG=SUNWdrrx.u
Original package not installed.
Package not patched:
PKG=SUNWdrrx.us
Original package not installed.
Package not patched:
PKG=SUNWefcx.u
Original package not installed.
Package not patched:
PKG=SUNWidn.u
Original package not installed.
Package not patched:
PKG=SUNWidnx.u
Original package not installed.
Package not patched:
PKG=SUNWkvm.us
Original package not installed.
Package not patched:
PKG=SUNWkvmx.us
Original package not installed.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarc> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWarcx> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
Installation of <SUNWcar> was successful.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
WARNING: /kernel/sys/sparcv9/rpcmod <no longer a regular file>
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-100/kernel/misc/sparcv9/platmod> is corrupt
file cksum <38281> expected <38278> actual
pkgadd: ERROR: source path </export/home/src/patches/108528-26/SUNWcarx.u/reloc/platform/SUNW,Sun-Blade-1000/kernel/misc/sparcv9/platmod> is corrupt
file size <4832> expected <4830> actual
file cksum <34048> expected <33987> actual
Installation of <SUNWcarx> partially failed.
Now I have a box with many J2EE patches but without the proper kernel!!! Halp! jj.

did you try and removed the IDR? I.e: patchrm IDR138540-01 ?
.7/M.

Solaris 10 Memory and Ldoms

Hi
Got a problem installing in a Guest Ldom on a T5120. I made the DVD ( Solaris 10 5/09 ) avaliable as a virtual disk and booted from it.
I used the same media installing the controller Ldom. Did'nt get any problems with it.
I allocated 512MB Memory to this Guest LDom. Configured 2GB swap during installastion and selected Entire Distribution.
It works when i allocate 1GB Memory to it.
Is 1GB Memory the new requirement for Solaris 10??
Don't want to use 1GB for these Guest Ldoms. Don't have enough memory for that.
Error message::
Solaris 10 software installation succeeded
Customizing system files
- Mount points table (/etc/vfstab)
- Network host addresses (/etc/hosts)
- Environment variables (/etc/default/init)
Cleaning devices
Customizing system devices
- Physical devices (/devices)
- Logical devices (/dev)
Installing boot information
- Installing boot blocks (c0d0s0)
- Installing boot blocks (/dev/rdsk/c0d0s0)
- Updating system firmware for automatic rebooting
Installation log location
- /a/var/sadm/system/logs/install_log (before reboot)
- /var/sadm/system/logs/install_log (after reboot)
Installation complete
Executing SolStart postinstall phase...
Executing finish script "patch_finish"...
Finish script patch_finish execution completed.
Executing JumpStart postinstall phase...
The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.
The finish script log 'finish.log'
is located in /var/sadm/system/logs after reboot.
Launching installer. Please Wait...
Installing Additional Software
|-1%--------------25%-----------------50%-----------------75%--------------100%|
Pausing for 30 seconds at the "Summary" screen. The wizard will continue to
the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
continue. [c]
Pausing for 90 seconds at the "Reboot" screen. The wizard will continue to
the next step unless you select "Pause". Enter 'p' to pause. Enter 'c' to
continue. [c]
Creating boot_archive for /a
updating /a/platform/sun4v/boot_archive
15+0 records in
15+0 records out
syncing file systems... done
rebooting...
Resetting...
SPARC Enterprise T5120, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.29.2, 512 MB memory available, Serial #83592229.
Ethernet address 0:14:4f:fb:84:25, Host ID: 84fb8425.
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args:
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: exec(/sbin/init) failed with errno 11. Retrying...
WARNING: exec(/sbin/init) failed (file not found).
(unix: Could not start init) Program terminated
SPARC Enterprise T5120, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.29.2, 512 MB memory available, Serial #83592229.
Ethernet address 0:14:4f:fb:84:25, Host ID: 84fb8425.
{0} ok
SPARC Enterprise T5120, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.29.2, 512 MB memory available, Serial #83592229.
Ethernet address 0:14:4f:fb:84:25, Host ID: 84fb8425.
{0} ok boot -sv
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -sv
module /platform/SUNW,SPARC-Enterprise-T5120/kernel/sparcv9/unix: text at [0x1000000, 0x10b373d] data at 0x1800000
module /platform/SUNW,SPARC-Enterprise-T5120/kernel/sparcv9/genunix: text at [0x10b3740, 0x127420f] data at 0x1899a40
module /platform/SUNW,SPARC-Enterprise-T5120/kernel/misc/sparcv9/platmod: text at [0x1274210, 0x1274227] data at 0x18efd18
module /platform/SUNW,SPARC-Enterprise-T5120/kernel/cpu/sparcv9/SUNW,UltraSPARC-T2: text at [0x1274240, 0x127995f] data at 0x18f0480
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Ethernet address = 0:14:4f:fb:84:25
mem = 524288K (0x20000000)
avail mem = 432463872
root nexus = SPARC Enterprise T5120
pseudo0 at root
pseudo0 is /pseudo
scsi_vhci0 at root
scsi_vhci0 is /scsi_vhci
virtual-device: cnex0
cnex0 is /virtual-devices@100/channel-devices@200
vdisk@0 is online using ldc@5,0
channel-device: vdc0
vdc0 is /virtual-devices@100/channel-devices@200/disk@0
root on /virtual-devices@100/channel-devices@200/disk@0:a fstype ufs
pseudo-device: dld0
dld0 is /pseudo/dld@0
cpu0: UltraSPARC-T2 (chipid 0, clock 1165 MHz)
cpu1: UltraSPARC-T2 (chipid 0, clock 1165 MHz)
iscsi0 at root
iscsi0 is /iscsi
WARNING: init(1M) exited on fatal signal 9: restarting automatically
WARNING: Sorry, no swap space to grow stack for pid 1 (init)
WARNING: exec(/sbin/init) failed with errno 8.
WARNING: failed to restart init(1M) (err=8): system reboot required
Thanks

My bad. The memory per guest domain is 1GB. Se the Section 1 (NEW) - Hardware http://wikis.sun.com/display/SolarisLogicalDomains/LDoms%20Community%20Cookbook
Ignore the http://www.sun.com/software/solaris/specs.jsp

How can we achive active/active cluster setup with Oracle

Hi Experts,
How can we achieve active/active database setup with oracle WITHOUT USING RAC.. As far as I know it's impossible (unless I'm wrong)..
We are using Oracle 11.2.0.1 64bit on Windows 2008 server. We deployed Oracle FailSafe but that's more of an active/passive solution based on a windows cluster.
The other solution we were thinking about is to use DataGuard and replication.. two servers.. the oracle instance running on one server generating logs, and the other server receive the logs and apply them to the physical standby db.. Still, this is not a real active/active setup.
So, is it possible to run 2 servers in an active/active cluster and have the oracle database in an active/active setup or have the instance running on multiple nodes (at the same time)?
Thanks

Let me give you a brief explanation of what the situation is and you can be the judge..
My client have four databases with the smallest one being 20GB and the biggest around the 35gb (SGA 750mb to 1.4gb (Tiny by DB standards) and probably on a normal day, you can run all four of them on a decent desktop).. The DBs are used to keep track of people information. Through out the year, the databases are almost sitting idle, and by idle I mean, the odd update here and there, the odd report..etc. No hard real processing of any sort. Two days of the year (end of year) we have all the operators consolidating records and what's not and they will be pounding away entering data and updating the tables - with hourly reports that goes to 3rd parties. The client expects a 99.99 up time and availability during those 2 days.
Now, tell me, How can I justify using RAC and spending hundreds of thousands of dollars in licensing and what ever extra costs introduced by the complexity of the environment for the above scenario knowing that I don't have any real use for RAC for 363 days of the year; and we MIGHT need it for 2 days of the year? This is the dilemma we're facing.
Thanks
Edited by: rsar001 on Sep 3, 2010 9:42 AM

VM creation on a cluster fails with Internal error code: 0x80990C1D

I am getting the following error when creating a VM from template on a 2012 R2 cluster:
Error (3101)
VMM failed to mount virtual hard disk (VHD) file XXXX.vhdx on the XXXX server. A timeout occurred.
Internal error code: 0x80990C1D
Recommended Action
Open Services to make sure the startup type for Virtual Disk service is set to manual or automatic. Ensure that the service can start and then try the operation again.
The errer occurs while running "Install VM Components" task. I did check services on the host and all is running as expected. The same template works without problem on non-clustered hosts, but fails two out of three times on HV cluster with
CSV storage on FC SAN. I am running SCVMM 2012 R2 UR3.
Any ideas what may cause this issue?
Thanks
Gleb.

Hi,
it's a strentgh issue. I don't have any certain information on the hand but I am just thinking out loud now. Maybe it helps.
If it fails at "Install VM Components" this would mean that the problem occurs during injecting or ejecting the integration services. I am right now not sure if VMM injects the integration services as an ISO file or as an vhd file. The second option is also
possible.
From this point of view my question would be;
1) Are you creating the VM from a blank disk with an ISO OS file attached ? If yes
2) Are you experienceing the same problem with an syspreped vhd or vhdx file too ?
3) How many VM's are running on your Cluster Nodes ?
4) Are there any differences in the behavior when you select a different cluster node as destination host during the creation of a VM from template ?
5) What's the workload on your cluster nodes right now disk, memory, cpu ?
Regards,
Cengiz Kuskaya

OSB cluster setup with SSL

Hi,
Could any one help me here..
Cluster setup for OSB with SSL enable
1) Admin and 2 Managed server are running on same host
2) cluster domain created in development mode
2) While starting second managed server getting below error..
<Oct 4, 2010 8:04:58 AM PDT> <Error> <ClusterTimer> <BEA-000000> <Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with
the time skew 0
java.rmi.RemoteException: ClusterTimerAuthority error; nested exception is:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://hostname:SSLport: Destination unreachable; nest
ed exception is:
java.io.IOException: Stream closed.; No available router to destination]
at com.bea.wli.sb.init.RemoteClusterTimerAuthority.getClusterTimerAuthorityCurrentTime(RemoteClusterTimerAuthority.java:38)
at com.bea.wli.timer.ClusterTimerService.clusterTimeAuthorityCurrentTimeMillis(ClusterTimerService.java:177)
at com.bea.wli.timer.ClusterTimerService.initialize(ClusterTimerService.java:88)
at com.bea.wli.sb.init.FrameworkStarter._preStart(FrameworkStarter.java:221)
at com.bea.wli.sb.init.FrameworkStarter.access$000(FrameworkStarter.java:79)
Truncated. see log file for complete stacktrace
Thanks,
Sushma.

Even I faced the same issue..but eventually the problem got resolved with below resolution:
Resolution: The managed server was not able to connect to t3s://hostname:sslport. The SSL configuration on Adminserver was wrong. After correcting SSL setting on Adminserver..i was able to resolve this error.

Solaris Cluster 4 with Solaris 11/11/11 -- LDOM farm

Similar Messages

Maybe you are looking for