Upgrading Solaris OS (9 to 10) in sun cluster 3.1 environment

Hi all ,
I have to upgrade the solaris OS 9 to 10 in Sun cluster 3.1.
Sun Cluster 3.1
data service - Netbackup 5.1
Questions:
1 .Best ways to upgrade the Solaris 9 to 10 and the Problems while upgrading the OS?
2 .Sun Trunking support in Sun Cluster 3.1?
Regards
Ramana

Hi Ramana
We had used the live upgrade for upgrading Solaris 9 to 10 and its the best method for less downtime and risk but you have to follow the proper procedure as it is not the same for normal solaris. Live upgrade with sun cluster is different . you have to take into consideration about global devices and veritas volume manager. while creating new boot environment.
Thanks/Regards
Sadiq

Similar Messages

Install of HA MaxDB in a Sun Cluster 3.2 environment

Hi. I am installing SAP Content Server using MaxDB in a Sun Cluster 3.2 environment. According to the SUN doc, I must install the X_server as a scalable resource/service. For a scalable resource, I have to make the disk available on both nodes of the cluster. I need to identify what are all the executables for the x_server so that I can make those mount points a NFS share. From looking at the content of previous non-clustered installs, I am thinking I need to make the directories /sapdb/data and /sapdb/program NFS to isolate the x_server components. Does anyone have experience with this setup ? I've placed a log with OSS but wanted to see if anyone else in the forum has done this before. Thanks for any input.

Hello Dan,
Please review the SAP Note No. 803452.
X_server tool is the the part of the indepentent database software installation <independent_program_path>. Using NFS you could set up the <independent_program_path> and <independent_data_path> directories as share directories.
Thank you and best regards, Natalia Khlopina

SUn CLuster 3.2 install - scinstall on x86 32 bit Solaris 5.10

Ok - I have 2 machines with 32-bit x86 SOlaris 5.10 - I installed the Sun Cluster 3.2 software but everytime I try scinstall it says rebooting other node and the other node never brings sun cluster up -
Questions:
1. The private interface does not come up on reboot - should it - and should I have an entry for cluster-priv1 in /etc/hosts
2. I know I am supposed to do a scvx -xv - I then try to enable the cluster service, but everything says disabled
I have tried this 5 times no luck - I have lots of cluster experience - and can get Oracle CRS working fine
Any thoughts

Yeahh, guys!!!
I was trying to establish a two-node cluster using VirtualBox + Solaris x86 + Sun Cluster 3.2. The node where I was running scinstall to configure my cluster environment was rebooting the other node in the end of the configuration process but it was hanging in the "Rebooting node01..." message just because it was not able to establish the cluster.
After see your comments, I changed Solaris x86 to Solaris Express Community Edition and Sun Cluster to Cluster Express and now everything is working fine!
Thanks!
Jansen Sena <[email protected]>

Multiple Oracle databases in Sun cluster 3.2 (without RAC setup)

There are 2 Sun SPARC (Sun Fire T2000) servers with Solaris 10 (05/09) OS and Sun Cluster 3.2 software. We need two different Oracle databases & instances (Oracle 10g R2 without RAC) for an application. The first database is for Production and need to be configured in the first node & Shared storage disk and need high availability. This database should run from the second node if the first node fails. The second database is for Quality/Test and it is prefered to be running in the Second node for better load distribution. This DB doesnt require any failover.
The shared storage is Sun SE 3510 FC and multiple LUNs can be created for different databases..
Is it possible to configure two different resource groups (one for Quality and other for Production) and make the first node primary for Production RG, and the second node primary for Quality RG and thus distributing the load on 2 servers ? If possible, what special configuration required in Sun OS and Cluster side ?
Appreciate if you can give some configuration procedures/documents for this multi-master cluster setup..

You can configure two resource groups, such as:
# clrg create -n node-a,node-b prod-rg
# clrg create -n node-b qa-rgand you configure the required resources (disk groups / file systems, logical host, oracle listener, oracle server) as described within
[http://docs.sun.com/app/docs/doc/819-2980?l=en&a=expand|http://docs.sun.com/app/docs/doc/819-2980?l=en&a=expand]
Note that this is not really called a "multi-master" configuration - that has a specific meaning for a resource group (see [http://docs.sun.com/app/docs/doc/820-4682/babefcja?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4682/babefcja?l=en&a=view] ) for details.
With Solaris Cluster all nodes part of a cluster are considered active and can host resource groups. You can have any number of resource groups running, where a subset runs one one node, another subset on other nodes. The nodelist property of the resource group defines where it can run, the first node in the list is the preferred primary.
You can even define resource group dependencies or affinities between the resource groups. Like you could define a negative affinity between qa-rg and prod-rg, such as if prod-rg needs to failover to node-b (since e.g. node-a died), it would offline qa-rg. Details for that kind of possibilities are described at [http://docs.sun.com/app/docs/doc/820-4682/ch14_resources_admin-35?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4682/ch14_resources_admin-35?l=en&a=view].
Regards
Thorsten

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

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

Upgrade from Solaris 8 SPARC with Sun cluster 3.1u3 to Solaris 10 SPARC

Dear All,
We are planning an upgrade of the OS from Solaris 8 SPARC to Solaris 10 SPARC on a two-node active-standby clustered system.
The current major software we have on the Solaris 8 system are:
1: Sun Cluster 3.1u3
2: Oracle 9i 9.2.0.8
3: Veritas File System Vxfs v4.0
4: Sun Solaris 8 2/04 SPARC
Any pointers as to what sequence and how the upgrade should be done?
Thanks in advance.
Regards,
Ray

yes I know it can be quite complicated and complex, but Sun provided us with a detailed documentation, at least in our case Solaris 9 to 10 it was very helpful.
You might get better help in the cluster forum http://forums.sun.com/forum.jspa?forumID=842
-- Nick

Sun Java Application Server 8.1 Upgrade Solaris 9 to Solaris 10

I have Sun Java Application Server 8.1 (version 8.1_02 (build b06-fcs) ) and HA which are currently installed on Solaris 9 box (Sparc).
Now, I plan to upgrade Solaris 9 to Solaris 10. What should I need to do before and after migration?
Thanks.

Before I start, disclaimer -- I have no knowledge of Hibernate and the following comments are based on the stack trace you have included.
I think your permissions might be set all right but you might have an error in the hibernate query. It looks like hibernate uses antlr to parse the queries. While parsing the query, antlr is encountering an exceptional condition and is trying to exit the VM (by calling System.exit()). Obviously, the hibernate code does not have that permission and therefore the exception is logged.
My guess is if you fix the query such that hibernate/antlr can parse it, you will not run into this error.
Hope this helps,

Upgrading Solaris 8 to Solaris 10 on SUN Sparc E2900 server

Hi,
We have a Sparc E2900 server which has Solaris 8 & Veritas Volume Manager 4.0. UFS & VXFS filesystems are under Veritas control.
We are planning to upgrade Solaris 8 to Solaris 10.
My questions are as follows
1) Can we upgrade from Solaris 8 to Solaris 10 directly ?
2) If Yes does Solaris 10 support Veritas Filesystem ?
3) Which is the best site to get information regarding upgradation ?
Regards,
Tejas J Raval

2) If Yes does Solaris 10 support Veritas Filesystem ?No, it dows not. If you want to use VxFS you still need to have Veritas products installed on this server

Upgrading Solaris 10 from 32-bit to 64-bit in a VirtualBox VM

Hello,
I am running 32-bit Sol 10 u5 x86 as a guest in a Sun VirtualBox (Vbox) virtual machine on a 32-bit WinXP host with 64-bit VT-capable Xeon processors, and am considering upgrading Solaris 10 to 64-bit using the latest version of Vbox (2.0.0). After installing WinXP Professional x64 and the 64-bit version of Vbox, will I have to completely re-install Sol 10 to get it to run in 64-bit, or is there some way to get it to 64-bit without a re-install? The Vbox forums suggested that I post this question on a Solaris forum, as they don't know the answer.
They apparently also do not know if Windows XP x64 is a compatible host OS on which to run 64-bit guests. They list only Vista, Linux, and OpenSolaris as supported 64-bit host OSs. Has anyone used WinXP x64 as a host for Vbox 64-bit guests? Due to policy, Vista is not available to me on my system/network.
Thank you...

The x86 installer will place both 32-bit and 64-bit code on the disk.
The loader fired by GRUB will attempt to detect the proper hardware and launch the correct kernel.
Other portions of the upgrade could conceivably cause a problem, but having the CPUs go from 32-bit only to 64-bit capable shouldn't be an issue. You don't have to make any changes.
Darren

Sun Cluster 3.2 upgrade fail

Dear mate,
when I upgrade the cluster from 3.1 to 3.2 by using Live Upgrade, the folloing error message came out, any hints or idea will be appreciate.
The PBE (sol8) is Solaris 8 with sun cluster 3.1. the PBE (sol10) is Solaris 10 and will upgrade to sun cluster 3.2
# cd /Solaris_sparc/Product/sun_cluster/Solaris_10/Tools
# ./scinstall -u update -R /sol10
scinstall: "SUNWesu" is not installed in "/sol10".
scinstall: scinstall did NOT complete successfully!
# luupgrade -p -n sol10 -s /mnt/Solaris_10/Product SUNWesu
Validating the contents of the media </mnt/Solaris_10/Product>.
Mounting the BE <sol10>.
ERROR: The boot environment <sol10> supports non-global zones.The current boot environment does not support non-global zones. Releases prior to Solaris 10 cannot be used to maintain Solaris 10 and later releases that include support for non-global zones. You may only execute the specified operation on a system with Solaris 10 (or later) installed.
cat: cannot open /tmp/.liveupgrade.6951.16469/.lmz.list
Thanks and Regards,
Donald

Hi Tim,
Thanks for the information.
I got the following result.
# pkginfo -R /sol10 SUNWesu
ERROR: information for "SUNWesu" was not found
# pkginfo SUNWesu
system SUNWesu Extended System Utilities
PBE has SUNWesu while ABE missing this package, does it mean SUNWesu hadn't upgrade from PBE to ABE? if so what will be the alternative to do it?
thanks and Regards,
Donald

SAP 7.0 on SUN Cluster 3.2 (Solaris 10 / SPARC)

Dear All;
i'm installing a two nodes cluster (SUN Cluster 3.2 / Solaris 10 / SPARC), for a HA SAP 7.0 / Oracle 10g DataBase
SAP and Oracle softwares were successfully installed and i could successfully cluster the Oracle DB and it is tested and working fine.
for the SAP i did the following configurations
# clresource create -g sap-ci-res-grp -t SUNW.sap_ci_v2 -p SAPSID=PRD -p Ci_instance_id=01 -p Ci_services_string=SCS -p Ci_startup_script=startsap_01 -p Ci_shutdown_script=stopsap_01 -p resource_dependencies=sap-hastp-rs,ora-db-res sap-ci-scs-res
# clresource create -g sap-ci-res-grp -t SUNW.sap_ci_v2 -p SAPSID=PRD -p Ci_instance_id=00 -p Ci_services_string=ASCS -p Ci_startup_script=startsap_00 -p Ci_shutdown_script=stopsap_00 -p resource_dependencies=sap-hastp-rs,or-db-res sap-ci-Ascs-res
and when trying to bring the sap-ci-res-grp online # clresourcegroup online -M sap-ci-res-grp
it executes the startsap scripts successfully as following
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
stty: : No such device or address
stty: : No such device or address
Starting SAP-Collector Daemon
11:04:57 04.06.2008 LOG: Effective User Id is root
Starting SAP-Collector Daemon
11:04:57 04.06.2008 LOG: Effective User Id is root
* This is Saposcol Version COLL 20.94 700 - V3.72 64Bit
* Usage: saposcol -l: Start OS Collector
* saposcol -k: Stop OS Collector
* saposcol -d: OS Collector Dialog Mode
* saposcol -s: OS Collector Status
* Starting collector (create new process)
* This is Saposcol Version COLL 20.94 700 - V3.72 64Bit
* Usage: saposcol -l: Start OS Collector
* saposcol -k: Stop OS Collector
* saposcol -d: OS Collector Dialog Mode
* saposcol -s: OS Collector Status
* Starting collector (create new process)
saposcol on host eccprd01 started
Starting SAP Instance ASCS00
Startup-Log is written to /export/home/prdadm/startsap_ASCS00.log
saposcol on host eccprd01 started
Running /usr/sap/PRD/SYS/exe/run/startj2eedb
Trying to start PRD database ...
Log file: /export/home/prdadm/startdb.log
Instance Service on host eccprd01 started
Jun 4 11:05:01 eccprd01 SAPPRD_00[26054]: Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable) [ntservsserver.cpp 1863]
/usr/sap/PRD/SYS/exe/run/startj2eedb completed successfully
Starting SAP Instance SCS01
Startup-Log is written to /export/home/prdadm/startsap_SCS01.log
Instance Service on host eccprd01 started
Jun 4 11:05:02 eccprd01 SAPPRD_01[26111]: Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable) [ntservsserver.cpp 1863]
Instance on host eccprd01 started
Instance on host eccprd01 started
and the it repeats the following warnings on the /var/adm/messages till it fails to the other node
Jun 4 12:26:22 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:28 eccprd01 last message repeated 1 time
Jun 4 12:26:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:46 eccprd01 last message repeated 1 time
Jun 4 12:26:46 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:49 eccprd01 last message repeated 1 time
Jun 4 12:26:49 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:52 eccprd01 last message repeated 1 time
Jun 4 12:26:52 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:55 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:55 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:58 eccprd01 last message repeated 1 time
Jun 4 12:26:58 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:01 eccprd01 last message repeated 1 time
Jun 4 12:27:01 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:04 eccprd01 last message repeated 1 time
Jun 4 12:27:04 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:07 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:07 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:10 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:10 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:13 eccprd01 last message repeated 1 time
Jun 4 12:27:13 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:16 eccprd01 last message repeated 1 time
Jun 4 12:27:16 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:19 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:19 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:22 eccprd01 last message repeated 1 time
Jun 4 12:27:22 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:25 eccprd01 last message repeated 1 time
Jun 4 12:27:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:34 eccprd01 last message repeated 1 time
Jun 4 12:27:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:37 eccprd01 last message repeated 1 time
Jun 4 12:27:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:43 eccprd01 last message repeated 1 time
Jun 4 12:27:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:46 eccprd01 last message repeated 1 time
Jun 4 12:27:46 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dis
can anyone one help me if there is any error on configurations or what is the cause of this problem.....thanks in advance
ARSSES

Hi all.
I am having a similar issue with a Sun Cluster 3.2 and SAP 7.0
Scenrio:
Central Instance (not incluster) : Started on one node
Dialog Instance (not in cluster): Started on the other node
When I create the resource for SUNW.sap_as like
clrs create --g sap-rg -t SUNW.sap_as .....etc etc
in the /var/adm/messages I got lots of WAITING FOR DISPACHER TO COME UP....
Then after timeout it gives up.
Any clue? What does is try to connect or waiting for? I hve notest that it's something before the startup script....
TIA

Real Application Cluster on Sun Solaris 8 and Sun Cluster 3

Hello,
we want to install Oracle 9i Enterprise Edition in combination with Oracle Real Application Cluster-Option on 2 Nodes. Every node (12-CPU-SMP-Machine) should running Sun Solaris 8 and Sun Cluster 3 Service.
Does this configuration work with ORAC? I found nowhere informations about. Is there anything I have to pay special attention for during installation?
Thank you for helping and best regards from Berlin/Germany
Michael Wuttke

Forms and report services work fine on solaris 8.
My problem is on the client side.
I have to use solaris 8 with netscape like forms clients
and I wasn't able to make it work with java plugins.
Any solution?
Mauro

Upgrade Solaris 8 from 10/01 to 02/02

Hi all, I need to upgrade some systems from Solaris 8 10/01 to 02/02. I use VxVM 3.2 and VxFS 3.4. I don't need to upgrade Veritas Software. I want use Live Upgrade and in all example I find (2.6 ==> 8) I have to reinstall VxVM. In my situation, is Veritas products reinstallaton mandatory?? Can I use unencapsulation and encapsulation??

Hi,
You have to get volume manager out of the way before you upgrade solaris. You can un-encapsulate the root disk, upgrade then re-encapsulate if you want.
The way I do is as follows:
boot up normally from the vxroot disk.
touch /etc/vx/reconfig.d/state.d/install-db
#This will stop volume manager from starting up in a normal mode. Basically stops all the volume management stuff from interferring
remove the root entries in /etc/system for veritas (e.g. rootdev:/psuedo/vxio@0:0 and set vxio:vol_rootdev_is_volume=1)
#this line tells solaris that the root volume is a veritas device. Without this removed Solaris will try to mount up the root disk as a veritas volume and fail.
cp /etc/vfstab /etc/vfstab.old
cp /etc/vfstab.prevm /etc/vfstab
#replaces the /etc/vfstab file with the pre-volume-manager one
reboot the system.
It will now reboot without volume manager. Boot it all up to make sure there are no problems / errors, the do an init 0, then a boot cdrom - install or whatever to install solaris. upgrade solaris.
Machine will then reboot after Solaris has been upgraded. Re-install volume manager (might not be required if you're on the same solaris version) and re-encapsulate the root disk. Initalise the root-mirror, and mirror the root disk to the mirror (after the 2 reboots that volume manager needs)
Much easier to do the upgrade this way ;)
There are some infodocs on this procedure on the support.veritas.com knowledge base as well, if you want the `preferred veritas endorsed` method..

Upgrading Solaris 9 to Solaris 10

Hi, I need to upgrade my workstation from solaris 9 to solaris 10 by CD. And also upgrade solaris 8 to solaris 9.
Do u have any idea how to do it? Can giv step by step?
Thanks
regards,
raymond

You do not need to use liveupgrade to upgrade, unless you want to learn it--it's complicated. It's good for servers and if you wish to go back to pre-upgrade. You need plenty of spare disk space.
First backup your data on your system to another hard disk or DVD.
Then stick in the installation DVD and select "Upgrade" instead of "Initial Install" when asked.

Upgrading Solaris OS (9 to 10) in sun cluster 3.1 environment

Similar Messages

Maybe you are looking for