Dependency between Sun Cluster 2.2 and Sun hardware ?
I am evaluating Sun Cluster 2.2 for the usage as clustering software within our project.
Can anybody say me, if there is a dependency between Sun Cluster 2.2 and Sun hardware ?
Can I use Sun Cluster 2.2 with other hardware platforms running Sun Solaris 7 and Veritas Volume Manager ?
I have had this discussion with fellow cluster admins, and we think a port of cluster 2.2 could be done to Intel running Solaris. And here is the BUT, BUT SUN does not support anything except a SPARC based cluster. So currently there is definately a depedancy bewteen the 2.2 software and the hardware.
Hope this helps
Heath
Similar Messages
-
Failover Zones / Containers with Sun Cluster Geographic Edition and AVS
Hi everyone,
Is the following solution supported/certified by Oracle/Sun? I did find some docs saying it is but cannot find concrete technical information yet...
* Two sites with a 2-node cluster in each site
* 2x Failover containers/zones that are part of the two protection groups (1x group for SAP, other group for 3rd party application)
* Sun Cluster 3.2 and Geographic Edition 3.2 with Availability Suite for SYNC/ASYNC replication over TCP/IP between the two sites
The Zones and their application need to be able to failover between the two sites.
Thanks!
Wim OlivierFritz,
Obviously, my colleagues and I, in the Geo Cluster group build and test Geo clusters all the time :-)
We have certainly built and tested Oracle (non-RAC) configurations on AVS. One issue you do have, unfortunately, is that of zones plus AVS (see my Blueprint for more details http://wikis.sun.com/display/BluePrints/Using+Solaris+Cluster+and+Sun+Cluster+Geographic+Edition). Consequently, you can't built the configuration you described. The alternative is to sacrifice zones for now and wait for the fixes to RG affinities (no idea on the schedule for this feature) or find another way to do this - probably hand crafted.
If you follow the OHAC pages (http://www.opensolaris.org/os/community/ha-clusters/) and look at the endorsed projects you'll see that there is a Script Based Plug-in on the way (for OHACGE) that I'm writing. So, if you are interested in playing with OHACGE source or the SCXGE binaries, you might see that appear at some point. Of course, these aren't supported solutions though.
Regards,
Tim
--- -
Migrating a Sun Cluster Running Oracle to New Hardware
Has anyone attempted this? Essentially we are moving a Sun Cluster from one location to hardware at another location while maintaining the same node names. From what I can tell, I need to (on an install lan):
1) Load the OS
2) Configure the IPs
3) Install Sun Cluster
4) Install Oracle Parallel Server/RAC
5) Restore the data on a per node basis
6) Restore the shared data
7) Adjust, tweak, and run
Are there any pitfalls or suggestions on the approach? The shop is relatively new to clustering much less oracle clustering and the original cluster was installed by admins gone bye.I would say that Apple should be able to update your 36-months maintenance agreement with a OSXS 10.4 serial number.
As far as I know, the structure of 10.3 and 10.4 serial numbers is different (wasn't the case between 10.2 and 10.3) so I'm short of a technical answer here.
Maybe you could try :
/System/Library/ServerSetup/serversetup -setServerSerialNumber xxxx-xxx-xxx-x-xxx-xxx-xxx-xxx-xxx-xxx-x
in a Terminal window on the server. It's theorically the same as using Server Admin but maybe this could help. -
Sun Cluster Core Conflict - on SUN Java install
Hi
We had a prototype cluster that we were playing with over two nodes.
We decided to uninstall the cluster by putting node into single user mode and running scinstall -r.
Afterwards we found that the Java Availability Suite was a little messed up - maybe because the kernel/registry had not been updated - it though the cluster and agent software was uninstalled and would not let us re-install. All the executabvles from /etc/cluster/bin had been removed from the nodes.
So, On both nodes we ran the uninstall program from /var/sadm/prod/... and then selected cluster and agents to uninstall.
On the first node, this completely removed the sun cluster compoenets and then allowed us to re-install the cluster software successfully.
On the second node, for some reason, it has left behind the component "Sun Cluster Core", and will not allow us to remove it with the uninstall.
When we try to re-install we get the following:
"Conflict - incomplete version of Sun Cluster Core has been detected"
In then points us to the sun cluster upgrade guide on sun.com.
My question is - how do we 'clean up' this node and remove the sun cluster core so we can re-install the sun cluster software from scratch?
I don't quite understand how this has been left behind....
thanks in advance
S1black.You can use prodreg directly to clean up when your de-install has gone bad.
Use:
# prodreg browse
to list the products. You may need to recurse down into the individual items. The use:
# prodreg unregister ...
to unregister and pkgrm to remove the packages manually.
That has worked for me in the past. Not sure if it is the 'official' way though!
Regards,
Tim
--- -
Sun Ray Software 5 and Sun Ray Soft Client 1.0 Early Access 1 (EA1) is live
Sun Ray Software 5 and Sun Ray Soft Client 1.0 Early Access 1 (EA1) is live!
o Sun Ray Software 5 and Sun Ray Soft Client 1.0 EA1 download link
-> https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SRS-5-EA1-SP-LX-G-B@CDS-CDS_SMI] .
o Supporting documentation is available on the [Sun Ray Software Information Center|http://wikis.sun.com/display/SRS5/Home] providing installation, configuration and administration in a topic-based, wiki format.
o Technical support is available at [Sun Ray Online Forum|http://forums.sun.com/forum.jspa?forumID=875] .
o [Feedback Survey|http://www.surveymonkey.com/s.aspx?sm=RmabpiADfPy90BMFIJQPXQ_3d_3d]
-SunilAnyone know when SRSS5 (4.2?) is coming out? Funny I came across SRSS5 today, as just this morning we began research in what it would take to move to LTSP. We have entire departments running off SRSS4.1 on RHEL5. This has been a pretty good solution but Sun insists on keeping SRSS for Linux a poor product when compared to it on Solaris. Things like sound, USB thumb drives, etc are implemented TERRIBLY on their linux software (if at all).
I'd be willing to give SRSS5 a shot if it became available soon. Even a time frame (like end of 2009, spring 2010, etc) would help. -
Sun Cluster 3.0 and VxVM 3.2 problems at boot
i 've a little problem with a two node cluster (2 x 480r + 2 x 3310 with a single raid ctl.)
Every 3310 has 3 (raid5) luns .
I've mirrored these 3 luns with VxVM, and i've mirror also the 2 internal (o.s.) disks.
One of the disk of the first 3310 is the quorum disk.
Every time i boot the nodes , i read an error at "block 0" of the quorum disk and then starts a fastidious synchronization of the mirrors. (sometimes also of the os mirror..)
Why does it happen?
Thanks.
Regards,
Mauro.We did another test today and again the resource group went into a STOP_FAILED state. On this occasion, the export for the corresponding ZFS pool timed-out. We were able to successfully bring the resource group online on the desired cluster node. Subsequent failovers worked fine. There's something strange happening when the zpool is being exported (eg error correction?). Once the zpool is exported, further imports of it seem to work fine.
When we first had the problem, we were able to manually export and import the zpools, though they did take quite some time to export/import.
"zpool list" shows we have a total of 7 zpools.
"zfs list" shows we have a total of 27 zfs file systems.
Is there any specific Sun or otherwise links to any problems with Sun Cluster and ZFS? -
Sun Cluster: Graph resources and resource groups dependencies
Hi,
Is there anything like the scfdot (http://opensolaris.org/os/community/smf/scfdot/) to graph resource dependencies in Sun Cluster?
Regards,
CiroSolaris 10 8/07 s10s_u4wos_12b SPARC
+ scha_resource_get -O TYPE -R lh-billapp-rs
+ echo SUNW.LogicalHostname:2
+ [ -z sa-billapp-rs ]
+ NETRS=sa-billapp-rs lh-billapp-rs
+ [ true = true -a ! -z sa-billapp-rs lh-billapp-rs ]
cluster2dot.ksh[193]: test: syntax error
+ + tr -s \n
+ scha_resource_get -O RESOURCE_DEPENDENCIES -R sa-billapp-rs
DEP=
+ [ true = true -a ! -z sa-billapp-rs lh-billapp-rs ]
cluster2dot.ksh[193]: test: syntax error
+ + tr -s \n
+ scha_resource_get -O RESOURCE_DEPENDENCIES -R lh-billapp-rs
DEP=
+ [ != ]
+ echo \t\t"lh-billapp-rs";
+ 1>> /tmp/clu-dom3-resources.dot
+ + tr -s \n
+ scha_resource_get -O RESOURCE_DEPENDENCIES_WEAK -R lh-billapp-rs
DEP_WEAK= -
Compatibility between Sun C++ 5.1 and Sun C++ 5.2
Is it possible to create with Sun C++ 5.1 a shared library refering symbols from other libraries created with Sun C++ 5.2 ?
There should be no problem linking 5.1 to 5.2 objects. In fact 5.0, 5.1, 5.2 and 5.3 objects
are all compatible. Note this does not apply to debug binaries. Debug objects are compatible but
the information changed between releases. The latest version of dbx should be used in a mixed
environment.
Alan
Sun Developer Technical Support -
Sun Ray server software and Sun DSEE
I want to have a centralized user administration in the latest sun java 7 directory server. i want to set up the system in that the users of the sun ray thin clients will be authenticated from
the DSEE. Please assist me in how to make this work.Basically, you Sun Ray server must be an LDAP client: it must be set up so that when logging in, it actually authenticates users against DSEE.
DSEE can be installed on the same host as the Sun Ray server, but it's not a requirement. On the contrary, in such a case, you've got to be
careful in the start order of services at boot time. So the easiest way is to have DSEE and the Sun Ray server on separate machines.
How to configure both servers is explained here: http://download.oracle.com/docs/cd/E18752_01/html/816-4556/ldapsetup-1.html
Or at least, it's a good starting point. -
Sun one server 7 and sun app server 8 incompatibility
I had all my ejb code running nicely on sun one server 7. Now I have to port to 8 and while the same ear file deploys successfully, I'm unable to make any create calls on my CMP beans. I get server side error "argument type mismatch", but I've checked and rechecked all arguments, number and type, but can't find anything wrong. Any pointers?
The new one is supposed to be backward comptible. In any case, I've run the migration tool and redeployed, but same issues exist.
-
Sun Ray Server Software and Sun Desktop Manager integration
Hello,
I have installed and configured SRSS and Desktop Manager..and they're working.
But... how to integrate them?...Will the Sun Ray Server Software 1.2 for Workgroup
Servers work on a Sun Blade 100?Yes, it'll work. An SB100 won't support many
concurrent Sun Ray users but it'll be OK for a
handful of users doing normal (non-multimedia)
work. Put as much physical memory into the box
as you can afford, and remember to configure an
appropriate amount of swap.
OttoM. -
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 AubinThis 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 -
RAC: using Sun cluster or Oracle clusterware?
Going to build RAC on SUN machine (Solaris 10) and Sun SAN storage, couldn't decide how to build the foundation-----use Sun cluster 3.1 or Oracle clusterware?
Any idea? Thanks.Starting with 10g Release 2, Oracle provides its own and indipendient cluster management, i.e., Clusterware which can be used as replacement for the OS specific cluster software.
You can still use the OS level cluster, in this case, Oracle Clusterware depends on OS cluster for the node information.
If you are on 10g, you can safely, go with Oracle Clusterware.
Jaffar -
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
ARSSESHi 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 -
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
RamanaHi 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
Maybe you are looking for
-
Reinstalling Mountain Lion after update to 10.8.1
Hello I got a problem, i got a Mac Mini and a MacBook unibody. On both pc's i have the same problem i bought Mountain Lion, installed it, and updated it to 10.8.1 Now after a while my Macbook doenst startup anymore, and today my Mac Mini doesn't star
-
Finding all employees who come under the manager
Hi experts, I have created a report which is attahced in MSS. So i want to restrict the manager to view the details of only the employees who come under this manager. At present the report is showing the details of all employees. So pls tell me whe
-
Entourage: iPhoto 9.4.1 not working!
I've found both 9.4 and 9.4.1 to be unstable. They are slower than previous versions, do not recognize or load my SD cards (it takes several insertions/ejections) and the worst part I can't email from Entourage. That feature was working in 9.4 for a
-
Yesterday the FIOS installer told me I had to 'activate' my account online. He said that since I don't want a verizon email address but want to continue to use gmail, that when the installer got to the email part I should just close the window and I'
-
HT1369 what is the error code mean -42220
Everytime i start up itunes i get the error code -42220 Also i cant seem to download music to my ipod classic?