Sun Cluster - Patching implication

Hi,
Currently, my system is running on a HA. Will the sun recommended patches will affect the stability of the cluster. Anything to watchout on pre-patch? Need advice.
Thank you

Please check the individual patch READMEs. They will document anything special that needs to be done. After that, you should follow the patching procedure discussed in:
http://docs.sun.com/app/docs/doc/819-2971/6n57mi2de?a=view
Regards,
Tim
---

Similar Messages

Sun cluster patch for solaris 10 x86

I have Solaris 10 6/06 installed on x4100 box with 2 node clustering using Sun Cluster 3.1 8/05. I just want to know is there any latest patches available for the OS to prevent cluster related bugs. what are they? My kernel patch is 118855-19.
any inputs needed. let me know.

Well, I would run S10 updatemanager and get the latest patches that way.
Tim
---

Sun cluster upgrade

Any one did an upgrade from Sun cluster 3.0 07/01 release to 12/01 release
was there any problem in the upgrade and what was the approach
any suggestion

This upgrade is delivered as a patch set and some
additional packages. The upgrade procedure is
basically the same as a normal patch procedure.
You might consider getting the latest core Sun Cluster
patch as well, just to be sure you are at the latest rev.
The additional packages provide new features. The
most popular is the Generic Data Service which can
really save development time for simple agents.
-- richard

Patch set on sun cluster

Hi,
I have to upgrade 9.2.0.6 to 9.2.08 on sun cluster.Can you tell me in what sequence I need to install patch set? Is there any pre-requisite which I need to take care in advance?If anybody will provide me exact doc then It will be very helpful.I have seen one doc in metalink but it is not sufficient.
Thanks,
Mk

Have you checked the 9.2.0.8 patch README ? There are several references on how to patch clustered instances - if the information is insufficient or lacking, pl open an SR with Support.
http://updates.oracle.com/ARULink/Readme/process_form?aru=8690150
HTH
Srini

10/22/09 SUN Alert Patch Cluster

I just applied the 10/22/09 SUN Alert Patch Cluster, and only 16 of the 176 patches were applied. Is this reasonable? I've been applying the most recent Alert patch cluster every three months for about 1-1/2 years.

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
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.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

Apply one non-kernel Solaris10 patch at Sun Cluster ***Beginner Question***

Dear Sir/Madam,
Our two Solaris 10 servers are running Sun Cluster 3.3. One server "cluster-1" has one online running zone "classical". Another server
"cluster-2" has two online running zones, namely "romantic" and "modern". We are tying to install a regular non-kernel patch #145200-03 at cluster-1 LIVE which doesn't have prerequisite and no need to reboot afterwards. Our goal is to install this patch at the global zone,
three local zones, i.e., classical, romantic and modern at both cluster servers, cluster-1 and cluster02.
Unfortunately, when we began our patching at cluster-1, it could patch the running zone "classical" but we were getting the following errors which prevent it from continuing with patching at zones, i.e., "romantic" and "modern" which are running on cluster-2. And when we try to patch cluster-2, we are getting similiar patching error about failing to boot non-global zone "classical" which is in cluster-1.
Any idea how I could resolve this ? Do we have to shut down the cluster in order to apply this patch ? I would prefer to apply this
patch with the Sun Cluster running. If not, what's the preferred way to apply simple non-reboot patch at all the zones at both nodes in the Sun Cluster ?
Like to hear from folks who have experience in dealing with patching in Sun Cluster.
Thanks, Mr. Channey
p.s. Below are output form the patch #145200-03 run, zoneadm and clrg
outputs at cluster-1
root@cluster-1# patchadd 145200-03
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
145200-03
Preparing checklist for non-global zone check...
Checking non-global zones...
Failed to boot non-global zone romantic
exiting
root@cluster-1# zoneadm list -iv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
15 classical running /zone-classical native shared
- romantic installed /zone-romantic native shared
- modern installed /zone-modern native shared
root@cluster-1# clrg status
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
classical cluster-1 No Online
cluster-2 No Offline
romantic cluster-1 No Offline
cluster-2 No Online
modern cluster-1 No Offline
cluster-2 No Online

Hi Hartmut,
I kind of got the idea. Just want to make sure. The zones 'romantic' and 'modern' show "installed" as the current status at cluster-1. These 2 zones are in fact running and online at cluster-2. So I will issue your commands below at cluster-2 to detach these zones to "configured" status :
cluster-2 # zoneadm -z romantic detach
cluster-2 # zoneadm -z modern detach
Afterwards, I apply the Solaris patch at cluster-2. Then, I go to cluster-1 and apply the same Solaris patch. Once I am done patching both cluster-1 and cluster-2, I will
go back to cluster-2 and run the following commands to force these zones back to "installed" status :
cluster-2 # zoneadm -z romantic attach -f
cluster-2 # zoneadm -z modern attach -f
CORRECT ?? Please let me know if I am wrong or if there's any step missing. Thanks much, Humphrey
root@cluster-1# zoneadm list -iv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
15 classical running /zone-classical native shared
- romantic installed /zone-romantic native shared
- modern installed /zone-modern native shared

Obtaining obsoleted Sun Alert patch Cluster

I need to build a Solaris 10 Sparc update 3 with Sun Alert Patch Cluster July 16 2007.
I cannot use a more recent Solaris instal version, nor can I use a more recent Sun Alert Patch Cluster version.
I cannot locate this specific Sun Alert Patch Cluster version for download from Sunsolve.
Can anyone advise if it is possible to obtain this Sun Alert Patch Cluster?

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
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.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

Encountered ora-29701 during Sun Cluster for Oracle RAC 9.2.0.7 startup (UR

Hi all,
Need some help from all out there
In our Sun Cluster 3.1 Data Service for Oracle RAC 9.2.0.7 (Solaris 9) configuration, my team had encountered
ora-29701 *Unable to connect to Cluster Manager*
during the startup of the Oracle RAC database instances on the Oracle RAC Server resources.
We tried the attached workaround by Oracle. This workaround works well for the 1^st time but it doesnt work anymore when the server is rebooted.
Kindly help me to check whether anyone encounter the same problem as the above and able to resolve. Thanks.
Bug No. 4262155
Filed 25-MAR-2005 Updated 11-APR-2005
Product Oracle Server - Enterprise Edition Product Version 9.2.0.6.0
Platform Linux x86
Platform Version 2.4.21-9.0.1
Database Version 9.2.0.6.0
Affects Platforms Port-Specific
Severity Severe Loss of Service
Status Not a Bug. To Filer
Base Bug N/A
Fixed in Product Version No Data
Problem statement:
ORA-29701 DURING DATABASE CREATION AFTER APPLYING 9.2.0.6 PATCHSET
*** 03/25/05 07:32 am ***
TAR:
PROBLEM:
Customer applied 9.2.0.6 patchset over 9.2.0.4 patchset.
While creating the database, customer receives following error:
ORA-29701: unable to connect to Cluster Manager
However, if customer goes from 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the problem does not occur.
DIAGNOSTIC ANALYSIS:
It seems that the problem is with libskgxn9.so shared library.
For 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the install log shows the following:
installActions2005-03-22_03-44-42PM.log:,
[libskgxn9.so->%ORACLE_HOME%/lib/libskgxn9.so 7933 plats=1=>[46]langs=1=> en,fr,ar,bn,pt_BR,bg,fr_CA,ca,hr,cs,da,nl,ar_EG,en_GB,et,fi,de,el,iw,hu,is,in, it,ja,ko,es,lv,lt,ms,es_MX,no,pl,pt,ro,ru,zh_CN,sk,sl,es_ES,sv,th,zh_TW, tr,uk,vi]]
installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]]
For 9.2.0.4 -> 9.2.0.6, install log shows:
installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]] does not exist.
This means that while patching from 9.2.0.4 -> 9.2.0.5, Installer copies the libcmdll.so library into libskgxn9.so, while patching from 9.2.0.4 -> 9.2.0.6 does not.
ORACM is located in /app/oracle/ORACM which is different than ORACLE_HOME in customer's environment.
WORKAROUND:
Customer is using the following workaround:
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk rac_on ioracle ipc_udp
RELATED BUGS:
Bug 4169291

Check if following MOS note helps.
Series of ORA-7445 Errors After Applying 9.2.0.7.0 Patchset to 9.2.0.6.0 Database (Doc ID 373375.1)

Is oracle 9.2.0.8 compatible with Sun Cluster 3.3 5/11 and 3.3 3/13?

Is oracle 9.2.0.8 compatible with Sun Cluster 3.3 5/11 and 3.3 3/13?
Where can I check compatibility matrix?

matthew_morris wrote:
This forum is about Oracle professional certifications (i.e. "Oracle Database 12c Administrator Certified Professional"), not about certifying product compatibility.
I concur with Matthew. The release notes for sun cluster and oracle for solaris might tell you. oracle 9.2.0.8 is out of support on solaris and I recall needing a number of patches to get it to a fit state ... and that is without considering sun cluster. Extended support for 9.2.0.8 ended about 4 years ago ... this is not a combination I would currently be touching with a bargepole! You are best to seek on MOS.

Information about Sun Cluster 3.1 5Q4 and Storage Foundation 4.1

Hi,
I have 2 Sunfire V440 with Solaris 9 last release 9/05 with last cluster patchs.. , Qlogic HBA fibre card on a seven disks shared on a Emc Clariion cx500. I have installed and configured Sun cluster 3.1 and Veritas Storage Foundation 4.1 MP1. My problems is when i run format wcommand on each node, I see the disks in a different order and veritas SF (4.1) is also picking up the disks in a different order.
1. Storage Foundation 4.1 is compatible with Sun cluster 3.1 2005Q4?????
2. Do you have a how to or other procedure for Storage foundation 4.1 with Sun Cluster 3.1.
I'm very confuse with veritas Storage foundation
Thanks!
J-F Aubin

This combination does not work today, but it will be available later.
Since Sun and Veritas are two separate companies, it takes more
time than expected to synchronize releases. Products supported by
Sun for Sun Cluster installation undergo extensive testing, which also
takes time.
-- richard

Sun cluster failed when switching, mount /global/ I/O error .

Hi all,
I am having a problem during switching two Sun Cluster nodes.
Environment:
Two nodes with Solaris 8 (Generic_117350-27), 2 Sun D2 arrays & Vxvm 3.2 and Sun Cluster 3.0.
Porblem description:
scswitch failed , then scshutdown and boot up the both nodes. One node failed because of vxvm boot failure.
The other node is booting up normally but cannot mount /global directories. Manually mount is working fine.
# mount /global/stripe01
mount: I/O error
mount: cannot mount /dev/vx/dsk/globdg/stripe-vol01
# vxdg import globdg
# vxvol -g globdg startall
# mount /dev/vx/dsk/globdg/mirror-vol03 /mnt
# echo $?
0
port:root:/global/.devices/node@1/dev/vx/dsk 169# mount /global/stripe01
mount: I/O error
mount: cannot mount /dev/vx/dsk/globdg/stripe-vol01
Need help urgently
Jeff

I would check your patch levels. I seem to remember there was a linker patch that cause an issue with mounting /global/.devices/node@X
Tim
---

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] .

J2SE Cluster Patches

The application which i am trying to install in Solaris 10 has the bellow dependency.
"On the server where you will install the SAS Web Client component, you must install
the J2SE Cluster Patches for Solaris. To download these patches, search for J2SE
Cluster Patches for your version of Solaris at http://www.sun.com/."
I am not able to locate above patch in sun.com
Please anyone point to me the right URL ?
Thanks.

This page includes the J2SE patches
http://sunsolve.sun.com/show.do?target=patch-access
You need to scroll down a bit in the recommended patches menu.

Sun cluster/metaset

I have two E450's connected to a D1000, have install Solaris 9 with patches and installed Sun cluster 3.2.
Both 450's are in the cluster and can see the D1000.
With the drives on the D1000, setup area for meta database on slice 7 starting from block 0 around 200MB and rest of disk on slice 0.
Create the database metadb -a -f ... on the disks from both hosts, and can reboot and can see the databases metadb -i, okay from both hosts
The problem which is occuring is that after I create them in disk sets and reboot both the hosts, the database become unknown showing,
metaset ... there are no existing databases, and when I do a metadb -i
M p unknown unknown /dev/dsk/c5t0d0s7
M p unknown unknown /dev/dsk/c5t1d0s7
I create the metaset doing
# metaset -s data1 -ah host1 host2
# metaset -s data1 -a /dev/did/rdsk/d4 /dev/did/rdsk/d5
This is all I need to to for the meta databases to become unknown after a reboot
Can't workout what I am doing wrong

I can't see anything in /var/adm/messages to give clue to the fault,
cldevice status gives all devices okay
there are no "Warning: rpc.metamedd on host not responding errors"
This is a list of patches
Patch: 112233-12 Obsoletes: 114400-03 114408-01 113361-08 112653-04 112687-02 112701-02 112902-12 112903-03 114760-02 114977-01 112736-03 115243-01 112737-03 113150-03 113156-01 113158-01 113159-01 113163-01 113714-01 113740-04 113963-01 113218-09 114382-01 114384-02 113578-01 112840-03 112841-10 113219-01 113325-01 113445-04 113489-05 113571-03 114226-01 114360-01 114390-01 114391-01 114392-01 114418-03 114466-04 114863-01 115245-01 115246-01 115499-01 115496-01 112904-12 112967-05 113449-04 113453-06 116233-01 116433-01 112961-01 113024-09 113030-02 113223-02 113275-02 113454-14 113538-11 113577-01 114118-02 115244-01 114359-02 114385-03 114393-03 114394-02 114474-01 114487-01 115169-01 115242-01 115251-02 116057-04 116074-01 Requires: Incompatibles: Packages: FJSVhea SUNWarc SUNWarcx SUNWcar SUNWcarx SUNWcpc SUNWcpcx SUNWcpr SUNWcprx SUNWcsl SUNWcslx SUNWcsr SUNWcstl SUNWcstlx SUNWcsu SUNWcsxu SUNWdrcrx SUNWdrr SUNWdrrx SUNWefclx SUNWefcux SUNWefcx SUNWfss SUNWfssx SUNWged SUNWgedu SUNWgedx SUNWhea SUNWidn SUNWidnx SUNWkvm SUNWmdb SUNWmdbx SUNWncar SUNWncarx SUNWncau SUNWncaux SUNWnfscr SUNWnfscx SUNWnisu SUNWpd SUNWpdx SUNWpiclu SUNWpmu SUNWpmux SUNWusx SUNWwrsax SUNWwrsdx SUNWwrsmx SUNWwrsux
Patch: 112839-07 Obsoletes: 112962-01 Requires: 112874-13 Incompatibles: Packages: SUNWcsl SUNWcslx SUNWmdb SUNWmdbx
Patch: 112920-02 Obsoletes: 112712-02 Requires: Incompatibles: Packages: SUNWarc SUNWarcx SUNWcsl SUNWcslx SUNWcsr SUNWcstl SUNWcstlx SUNWhea SUNWmdb SUNWmdbx
Patch: 112963-25 Obsoletes: 112833-01 Requires: Incompatibles: Packages: SUNWarc SUNWbtool SUNWbtoox SUNWcsl SUNWcslx SUNWcsr SUNWcsu SUNWcsxu SUNWhea SUNWmdb SUNWmdbx SUNWosdem SUNWtoo SUNWtoox SUNWxcu4
Patch: 113073-13 Obsoletes: 113005-02 115026-01 113492-04 113006-01 113026-22 113069-04 113282-01 113333-02 113491-01 113276-04 115506-01 116128-02 116446-02 113464-07 116130-01 116448-01 116550-01 117248-02 117069-01 113456-01 113457-05 113993-06 115510-01 Requires: 114127-03 112233-12 Incompatibles: Packages: SUNWcarx SUNWcsl SUNWcslx SUNWcsr SUNWcsu SUNWcsxu SUNWhea SUNWmdau SUNWmdr SUNWmdu SUNWmdx
Patch: 113073-14 Obsoletes: 113005-02 115026-01 113492-04 113006-01 113026-22 113069-04 113282-01 113333-02 113491-01 113276-04 115506-01 116128-02 116446-02 113464-07 116130-01 116448-01 116550-01 117248-02 117069-01 113456-01 113457-05 113993-06 115510-01 Requires: 114127-03 112233-12 Incompatibles: Packages: SUNWcarx SUNWcsl SUNWcslx SUNWcsr SUNWcsu SUNWcsxu SUNWhea SUNWmdau SUNWmdr SUNWmdu SUNWmdx
Patch: 113332-07 Obsoletes: 113539-01 113540-01 114464-01 114376-03 Requires: Incompatibles: Packages: SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWpstl SUNWpstlx
Patch: 113447-21 Obsoletes: 113025-01 113221-03 113574-08 114375-09 114381-06 114465-01 114752-02 114753-02 114765-01 114379-03 114770-03 114930-01 116072-02 116077-01 116416-01 114258-01 114347-01 115526-03 115527-03 114261-04 113488-01 117285-01 117296-01 113573-05 114325-01 114864-02 Requires: 112233-09 114385-01 Incompatibles: Packages: FJSVpiclu SUNWcarx SUNWcsr SUNWefcr SUNWfruip SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWpiclu SUNWpstl SUNWpstlx SUNWsfdr SUNWsfdrr
Patch: 113471-07 Obsoletes: 115484-01 Requires: Incompatibles: Packages: SUNWcpcu SUNWcsu SUNWcsxu SUNWesu SUNWesxu SUNWmdb SUNWrcapu SUNWrmwbu SUNWscpu SUNWtnfc SUNWtoo SUNWtoox
Patch: 113493-02 Obsoletes: Requires: 112874-18 Incompatibles: Packages: SUNWcsl SUNWcslx SUNWmdb SUNWmdbx
Patch: 114371-01 Obsoletes: Requires: Incompatibles: Packages: SUNWmdb SUNWmdbx
Patch: 115010-01 Obsoletes: Requires: Incompatibles: Packages: SUNWhea SUNWkvm SUNWmdb SUNWpstl SUNWpstlx
Patch: 115553-11 Obsoletes: 112836-02 112836-02 115338-01 115557-01 116065-03 115338-01 115557-01 116065-03 117198-02 117382-01 Requires: 112233-12 112954-05 113277-18 114128-02 115004-02 117418-01 Incompatibles: Packages: SUNWcar SUNWcarx SUNWcpr SUNWcprx SUNWcsl SUNWcslx SUNWcstl SUNWcstlx SUNWcsu SUNWcsxu SUNWhea SUNWmdb SUNWmdbx SUNWusb SUNWusbu SUNWusbx
Patch: 115553-20 Obsoletes: 112836-02 115338-01 115557-01 116065-03 117198-02 117382-01 115004-02 117196-01 Requires: 114128-02 113277-18 118558-18 114332-04 112954-05 112233-12 117418-01 Incompatibles: Packages: SUNWcar SUNWcarx SUNWcpr SUNWcprx SUNWcsl SUNWcslx SUNWcstl SUNWcstlx SUNWcsu SUNWcsxu SUNWhea SUNWmdb SUNWmdbx SUNWusb SUNWusbu SUNWusbx
Patch: 115559-01 Obsoletes: Requires: Incompatibles: Packages: SUNWmddr
Patch: 116092-04 Obsoletes: Requires: Incompatibles: Packages: SUNW1394x SUNWcsr SUNWmdr SUNWusb SUNWusx
Patch: 116478-01 Obsoletes: 116075-01 Requires: Incompatibles: Packages: SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWpstl SUNWpstlx
Patch: 116534-01 Obsoletes: Requires: Incompatibles: Packages: SUNWmdau
Patch: 116561-02 Obsoletes: 114388-05 116439-01 116492-01 117297-01 117425-01 Requires: 112233-12 Incompatibles: Packages: SUNWcarx SUNWcsr SUNWdmfex SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWpstl SUNWpstlx
Patch: 116561-13 Obsoletes: 114388-05 116439-01 116492-01 117297-01 117425-01 Requires: 112233-12 Incompatibles: Packages: SUNWcarx SUNWcsr SUNWdmfex SUNWfruip SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWpstl SUNWpstlx
Patch: 116669-18 Obsoletes: 115559-01 119432-01 Requires: 113073-14 Incompatibles: Packages: SUNWhea SUNWmddr SUNWmdr SUNWmdu SUNWmdx
Patch: 116669-32 Obsoletes: 115559-01 119432-01 Requires: 113073-14 Incompatibles: Packages: SUNWhea SUNWmddr SUNWmdr SUNWmdu SUNWmdx
Patch: 117134-01 Obsoletes: Requires: Incompatibles: Packages: SUNWmdr
Patch: 117280-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr SUNWmdr
Patch: 117282-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr SUNWcti2x SUNWmdr SUNWmdu SUNWusb
Patch: 117420-02 Obsoletes: 117250-01 Requires: Incompatibles: Packages: SUNWmdb SUNWmdbx
Patch: 118558-28 Obsoletes: 112987-01 113543-02 114126-03 114338-01 114378-02 114386-03 114395-03 115994-01 113025-01 113221-03 113574-08 114375-09 114381-06 114465-01 114752-02 114753-02 114765-01 114379-03 114770-03 114930-01 116072-02 116077-01 116416-01 114258-01 114347-01 115526-03 115527-03 114261-04 113488-01 117285-01 117296-01 113573-05 114325-01 114864-02 113447-25 114755-01 114756-01 115663-03 115665-10 117427-08 114721-07 116051-02 119936-01 Requires: 112233-12 113073-14 116532-01 117171-17 Incompatibles: Packages: FJSVhea FJSVpiclu SUNWcar SUNWcarx SUNWcsl SUNWcslx SUNWcsr SUNWcsu SUNWcsxu SUNWefcr SUNWfruip SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWmdbx SUNWpd SUNWpdu SUNWpdx SUNWpiclu SUNWpstl SUNWpstlx SUNWsfdr SUNWsfdrr
Patch: 118558-39 Obsoletes: 112987-01 113543-02 114126-03 114338-01 114378-02 114386-03 114395-03 115994-01 113025-01 113221-03 113574-08 114375-09 114381-06 114465-01 114752-02 114753-02 114765-01 114379-03 114770-03 114930-01 116072-02 116077-01 116416-01 114258-01 114347-01 115526-03 115527-03 114261-04 113488-01 117285-01 117296-01 113573-05 114325-01 114864-02 113447-25 114755-01 114756-01 115663-03 115665-10 117427-08 114721-07 116051-02 119936-01 114757-02 115667-05 117125-03 Requires: 112233-12 113073-14 116532-01 117171-17 Incompatibles: Packages: FJSVhea FJSVpiclu SUNWcar SUNWcarx SUNWcsl SUNWcslx SUNWcsr SUNWcsu SUNWcsxu SUNWefcr SUNWfruip SUNWhea SUNWkvm SUNWkvmx SUNWmdb SUNWmdbx SUNWpd SUNWpdu SUNWpdx SUNWpiclu SUNWpstl SUNWpstlx SUNWsfdr SUNWsfdrr

Tmboot fails started by a Sun Cluster Agent (Data Service)

Hi,
we are using TUXEDO 6.5 in conjunction with ADC's Singl.eView.
Starting TUXEDO by calling tmboot -y works fine in the command prompt.
Starting TUXEDO within a Sun Cluster Agent, which internaly calls tmboot -y as
well, fails with the foolowing error messages:
004859.lbgas1!GWTDOMAIN.5762: 08022002: TUXEDO Version 6.5 SunOS 5.5.1 Generic_103640-29
sun4u sparc SUNW,Ultra-1.
004859.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:262: INFO: Standard main starting
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1223: WARN: Reach system open max(0)
limit
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1122: ERROR: Unable to allocate free
fd structure
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1124: ERROR: Unable to open listening
endpoint
004901.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
ubbconfig entries for GWTDOMAIN:
GWTDOMAIN SRVGRP="GWADMGROUP" SRVID=2
REPLYQ = N
RESTART = Y
GRACE = 0
MAXGEN = 5
CLOPT = ""
RQADDR = "GWADMGROUP"
What configuration do I have to change, a TUXEDO one or Sun ?
Can I drop an application server in ubbconfig ?
Lutz

Patch #232, CR041488 seems to address this:
GWTDOMAIN connection problem when maxfiles kernel parm set > 32K
Perhaps the Cluster Agent sets a higher ulimit when it runs.
See if you are running the latest patch.
Scott Orshan
Lutz wrote:
>
Hi,
we are using TUXEDO 6.5 in conjunction with ADC's Singl.eView.
Starting TUXEDO by calling tmboot -y works fine in the command prompt.
Starting TUXEDO within a Sun Cluster Agent, which internaly calls tmboot -y as
well, fails with the foolowing error messages:
004859.lbgas1!GWTDOMAIN.5762: 08022002: TUXEDO Version 6.5 SunOS 5.5.1 Generic_103640-29
sun4u sparc SUNW,Ultra-1.
004859.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:262: INFO: Standard main starting
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1223: WARN: Reach system open max(0)
limit
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1122: ERROR: Unable to allocate free
fd structure
004901.lbgas1!GWTDOMAIN.5762: LIBGWT_CAT:1124: ERROR: Unable to open listening
endpoint
004901.lbgas1!GWTDOMAIN.5762: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
ubbconfig entries for GWTDOMAIN:
GWTDOMAIN SRVGRP="GWADMGROUP" SRVID=2
REPLYQ = N
RESTART = Y
GRACE = 0
MAXGEN = 5
CLOPT = ""
RQADDR = "GWADMGROUP"
What configuration do I have to change, a TUXEDO one or Sun ?
Can I drop an application server in ubbconfig ?
Lutz

Sun Cluster - Patching implication

Similar Messages

Maybe you are looking for