SUN Cluster 3.2 monitoring,
Hi
You can certainly configure SNMP and the MIB on Solaris Cluster - see http://docs.sun.com/app/docs/doc/819-2971/gbppm?a=view for the documentation and http://blogs.sun.com/SC/entry/sun_cluster_3_2_snmp for a blog entry. However, I don't think you can configure it to go directly to syslog. I would guess (since I don't know much about SNMP) you'd need configure the trap handle to log events to syslog and that's probably dependent on how the trap handler works.
Regards,
Tim
---
Similar Messages
-
Sun Cluster.. Why?
What are the advantages of installing RAC 10.2.0.3 on a Sun Cluster.? Are there any benefits?
Oracle 10g onward, there is no such burning requirement for Sun Cluster (or any third party cluster) as far as you are using all Oracle technologies for your Oracle RAC database. You should Oracle RAC with ASM for shared storage and that would not require any third party cluster. Bear inmind that
You may need to install Sun Cluster in the following scenarios:
1) If there is applicaiton running with in the cluster along with Oracle RAC database that you want to configure for HA and Sun Cluster provide the cluster resourced (easy to use) to manage and monitor the application. THIS can be achieved with Oracle Clusterware but you will have to write your own cluster resource for that.
2) If you want to install cluster file system such as QFS then you will need to install the Sun Cluster. If this cluster is only running the Oracle RAC database then you can rely on Oracle technologies such as ASM, raw devices without installing Sun Cluster.
3) Any certification conflicts.
Any correction is welcome..
-Harish Kumar Kalra -
Beta Refresh Release Now Available! Sun Cluster 3.2 Beta Program
The Sun Cluster 3.2 Release team is pleased to announce a Beta Refresh release. This release is based on our latest and greatest build of Sun Cluster 3.2, build 70, which is close to the final Revenue Release build of the product.
To apply for the Sun Cluster 3.2 Beta program, please visit:
https://feedbackprograms.sun.com/callout/default.html?callid=%7B11B4E37C-D608-433B-AF69-07F6CD714AA1%7D
or contact Eric Redmond <[email protected]>.
New Features in Sun Cluster 3.2
Ease of use
* New Sun Cluster Object Oriented Command Set
* Oracle RAC 10g improved integration and administration
* Agent configuration wizards
* Resources monitoring suspend
* Flexible private interconnect IP address scheme
Availability
* Extended flexibility for fencing protocol
* Disk path failure handling
* Quorum Server
* Cluster support for SMF services
Flexibility
* Solaris Container expanded support
* HA ZFS
* HDS TrueCopy campus cluster
* Veritas Flashsnap Fast Mirror Resynchronization 4.1 and 5.0 option support
* Multi-terabyte disk and EFI label support
* Veritas Volume Replicator 5.0 support
* Veritas Volume Manager 4.1 support on x86 platform
* Veritas Storage Foundation 5.0 File System and Volume Manager
OAMP
* Live upgrade
* Dual partition software swap (aka quantum leap)
* Optional GUI installation
* SNMP event MIB
* Command logging
* Workload system resource monitoring
Note: Veritas 5.0 features are not supported with SC 3.2 Beta.
Sun Cluster 3.2 beta supports the following Data Services
* Apache (shipped with the Solaris OS)
* DNS
* NFS V3
* Java Enterprise System 2005Q4: Application Server, Web Server, Message Queue, HADBWithout speculating on the release date of Sun Cluster 3.x or even its feature list, I would like to understand what risk Sun would take when Sun Cluster would support ZFS as a failover filesystem? Once ZFS is part of Solaris 10, I am sure customers will want to use it in clustered environments.
BTW: this means that even Veritas will have to do something about ZFS!!!
If VCS is a much better option, it would be interesting to understand what features are missing from Sun Cluster to make it really competitive.
Thanks
Hartmut -
Sun Cluster failed to switchover
Hi,
I have configured two node sun cluster and was working fine all these days.
Since yesterday, i am unable to failover the cluster to second node.
instead, resources are stopped and started again on the first node.
when i use the command "scswitch -z -g oracle_failover_rg -h MFIN-SOL02" in first node I am getting these messages on the console
Sep 28 17:53:16 MFIN-SOL01 ip: [ID 678092 kern.notice] TCP_IOC_ABORT_CONN: local = 010.010.007.120:0, remote = 000.000.000.00
0:0, start = -2, end = 6
Sep 28 17:53:16 MFIN-SOL01 ip: [ID 302654 kern.notice] TCP_IOC_ABORT_CONN: aborted 0 connection
Pl. suggest me to solve this problem.Those messages aren't important here. I think that might be related to the fault monitor being stopped.
As I said in the previous post, you need to diagnose this bit by bit. Try the procedure manually, i.e. stop Oracle on node 1, manually switch-over the disks and storage to node 2, mount the file system, bring up the logical address, start the database.
I expect there is something wrong with your configuration, e.g. incorrect listener configuration.
There is also a way of increasing the debug level for the Oracle agent. This is documented in the manuals IIRC.
Regards,
Tim
--- -
Sun Cluster 3.2 without share storage. (Sun StorageTek Availability Suite)
Hi all.
I have two node sun cluster.
I am configured and installed AVS on this nodes. (AVS Remote mirror replication)
AVS working fine. But I don't understand how integrate it in cluster.
What did I do:
Created remote mirror with AVS.
v210-node1# sndradm -P
/dev/rdsk/c1t1d0s1 -> v210-node0:/dev/rdsk/c1t1d0s1
autosync: on, max q writes: 4096, max q fbas: 16384, async threads: 2, mode: sync, group: AVS_TEST_GRP, state: replicating
v210-node1#
v210-node0# sndradm -P
/dev/rdsk/c1t1d0s1 <- v210-node1:/dev/rdsk/c1t1d0s1
autosync: on, max q writes: 4096, max q fbas: 16384, async threads: 2, mode: sync, group: AVS_TEST_GRP, state: replicating
v210-node0# Created resource group in Sun Cluster:
v210-node0# clrg status avs_test_rg
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
avs_test_rg v210-node0 No Offline
v210-node1 No Online
v210-node0# Created SUNW.HAStoragePlus resource with AVS device:
v210-node0# cat /etc/vfstab | grep avs
/dev/global/dsk/d11s1 /dev/global/rdsk/d11s1 /zones/avs_test ufs 2 no logging
v210-node0#
v210-node0# clrs show avs_test_hastorageplus_rs
=== Resources ===
Resource: avs_test_hastorageplus_rs
Type: SUNW.HAStoragePlus:6
Type_version: 6
Group: avs_test_rg
R_description:
Resource_project_name: default
Enabled{v210-node0}: True
Enabled{v210-node1}: True
Monitored{v210-node0}: True
Monitored{v210-node1}: True
v210-node0# In default all work fine.
But if i need switch RG on second node - I have problem.
v210-node0# clrs status avs_test_hastorageplus_rs
=== Cluster Resources ===
Resource Name Node Name State Status Message
avs_test_hastorageplus_rs v210-node0 Offline Offline
v210-node1 Online Online
v210-node0#
v210-node0# clrg switch -n v210-node0 avs_test_rg
clrg: (C748634) Resource group avs_test_rg failed to start on chosen node and might fail over to other node(s)
v210-node0# If I change state in logging - all work.
v210-node0# sndradm -C local -l
Put Remote Mirror into logging mode? (Y/N) [N]: Y
v210-node0# clrg switch -n v210-node0 avs_test_rg
v210-node0# clrs status avs_test_hastorageplus_rs
=== Cluster Resources ===
Resource Name Node Name State Status Message
avs_test_hastorageplus_rs v210-node0 Online Online
v210-node1 Offline Offline
v210-node0# How can I do this without creating SC Agent for it?
Anatoly S. ZiminNormally you use AVS to replicate data from one Solaris Cluster to another. Can you just clarify whether you are replicating to another cluster or trying to do it between a single cluster's nodes? If it is the latter, then this is not something that Sun officially support (IIRC) - rather it is something that has been developed in the open source community. As such it will not be documented in the Sun main SC documentation set. Furthermore, support and or questions for it should be directed to the author of the module.
Regards,
Tim
--- -
TimesTen database in Sun Cluster environment
Hi,
Currently we have our application together with the TimesTen database installed at the customer on two different nodes (running on Sun Solaris 10). The second node acts as a backup to provide failover functionality, although right now only manual failover is supported.
We are now looking into a hot-standby / high availability solution using Sun Cluster software. As understood from the documentation, applications can be 'plugged-in' to the Sun Cluster using Agents to monitor the application. Sun Cluster Agents should be already available for certain applications such as:
# MySQL
# Oracle 9i, 10g (HA and RAC)
# Oracle 9iAS Application Server
# PostgreSQL
(See http://www.sun.com/software/solaris/cluster/faq.jsp#q_19)
Our question is whether Sun Cluster Agents are already (freely) available for TimesTen? If so, where to find them. If not, should we write a specific Agent separately for TimesTen or handle database problems from the application.
Does someone have any experience using TimesTen in a Sun Cluster environment?
Thanks in advance!Yes, we use 2-way replication, but we don't use cache connect. The replication is created like this on both servers:
create replication MYDB.REPSCHEME
element SERVER01_DS datastore
master MYDB on "SERVER01_REP"
transmit nondurable
subscriber MYDB on "SERVER02_REP"
element SERVER02_DS datastore
master MYDB on "SERVER02_REP"
transmit nondurable
subscriber MYDB on "SERVER01_REP"
store MYDB on "SERVER01_REP"
port 16004
failthreshold 500
store MYDB on "SERVER02_REP"
port 16004
failthreshold 500
The application runs on SERVER01 and is standby on SERVER02. If an invalid state is detected in the application, the application on SERVER01 is stopped and the application on SERVER02 is started.
In addition to this, we want to fail over if the database on the SERVER01 is in invalid state. What should we have monitored by the Clustering Agent to detect an invalid state in TT? -
Close/shutdown the Sun Cluster Package/resource Group
Hi,
I have a SUN cluster system.
I want to know what script do when the SUN cluster shutdown the package "app-gcota-rg" as I may need to modify it ?? Where can I find out this information in the system??
In which directory and log file ???
Any suggestion ???
Resource Groups --
Group Name Node Name State
Group: ora_gcota_rg ytgcota-1 Online
Group: ora_gcota_rg ytgcota-2 Offline
Group: app-gcota-rg ytgcota-1 Online
Group: app-gcota-rg ytgcota-2 OfflineHi,
you would first find out which resources belong to app-gcota-rg.
Do a "clrs list -g app-gcota-rg". Then find out which of the resource is the one dealing with your application. Then try to find out its resource type:
"clrs show -v <resource name>| fgrep Type". If it is a standard type like HA Oracle, it is an extremely bad idea to hack the scripts, as you'll lose support. If type is SUNWgds, the scripts to start, stop and monitor the application are user supplied. You can find their pathnames using:
"clrs show -v <resource-name>| fgrep _command". This should display full pathnames.
Regards
Hartmut -
Instant Messaging Core works on Sun Cluster?
The question is if the instant messaging core works on Sun Cluster for High Availability?
a n sthis will be available in jes4.
If it is really needed before then, the watchdog feature in JES 3 makes it easy to write your own cluster agents. Basically all the cluster agent has to do is monitor the watchdog pid. -
Sun Cluster 2.2 configuration
Hi all,
is it possible to configure Sun Cluster 2.2 to use "sqlplus" instead of "svrmgrl" to start an oracle db (9i)?
thanksOracle 9i is not supported on SC 2.2.
Just replacing svrmgrl with 'sqlplus' will not be sufficient to make HA-Oracle work with Oracle 9i. You will most likely encounter problems in fault monitor, it will just fail.
Oracle 8i fault monitor is likely to be incompatible with 9i server.
If you really want to use Oracle 9i on SC2.2, you will be better of by writing a custom agent or moving to SC 3.x. -
Folks,
Did you come across any products, who SMFied their product and how it impacts their cluster installations ?. Please provide details if you have any
Thanks mUch
_DSince I am currently not aware of third party products shipping an SMF service for their application (which does not mean much, ie. they could well exist) I just make two generic statements:
1) If for that application a standard Sun Cluster agent exists, then the instructions for installing this data service would include to disable the SMF on the cluster nodes (like on pre Solaris 10 systems the legacy runlevel script would need to get deactivated).
2) If for that application no standard Sun Cluster agent exists, then one would have the ability to leverage the new proxy SMF resource types coming with Sun Cluster 3.2. They would use the SMF manifest to start and stop the application. Note that by using this resource type you would not have any application fault monitoring.
Details to 2) can be found at
http://blogs.sun.com/SC/entry/making_smf_services_highly_available and
http://docs.sun.com/app/docs/doc/819-2974/6n57pdk2b?a=view
Greets
Thorsten
Message was edited by:
Thorsten.Frueauf -
Does sun Cluster 3.0/3.1 HA Oracle agent support to use Oracle spfile?
When defining the resource, the 'parameter_file' properties is usually sets to the Oracle pfile. Is it possible to use Oracle spfile?
It is said if leaving 'parameter_file' NULL, it will be default to Oracle default. Suppose leaving it NULL and with Oracle spfile created in default location, will it use the spfile?You did not specify which Sun Cluster version and Oracle version you are running.
Within SC 3.1 my understanding is that beginning with Oracle 9i it is possible to use the spfile.
If you leave the "parameter_file" property empty (NULL) then the default behaviour for 9i should work:
search under $ORACLE_HOME/dbs in the order:
1. spfile$(ORACLE_SID}.ora
2. spfile.ora
3. init${ORACLE_SID}.ora
Greets
Thorsten -
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 4169291Check 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) -
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 -
Creating Logical hostname in sun cluster
Can someone tell me, what exactly logical hostname in sun cluster mean?
For registering logical hostname resource in failoover group, what exactly i need to specify
for example, i have two nodes in sun cluster , How to create or configure a logical hostanme and it should point to which IP Address ( Whether it should point to IP addresses of nodes in sun cluster). Can i get clarification on this?Thanks Thorsten for ur continue help...
The output of clrs status abc_lg
=== Cluster Resources ===
Resource Name Node Name State Status Message
abc_lg node1 Offline Offline
node2 Offline Offline
The status is offline...
the output of clresourcegroup status
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
abc_rg node1 No Unmanaged
node2 No Unmanaged
You say that the resource should de enabled after creating the resource.. I am using GDS and i am just following the steps he provided to acheive high availabilty (in developers guide...)
I have 1) Logical hostname resorce.
2) Application resource in my failover resource group
When i bring online the failover resource group , what should my failover resource group status and the status of resource in my resource group -
SUN AI24PO 24" LCD Monitor C-Viedo / S-Video Problem... No Image
We have few SUN AI24PO 24" LCD Monitors that are hooked up to Blade2000 and Blade2500 systems. These monitors have 1-Digital/DVI, 1-Analog/VGA, 1-S-Video, 1-C-Video inputs. The Digital and Analog inputs work fine but I cannot display anything that I feed to the S or C video inputs.
When we connect a (inspection/security) camera signal to the C-video or S-video input on these monitors, we cannot get an image. The Screen stays blue. Once or twice the image from the camera flashes and then disappears. For the image to flash again, I need to disconnect the c-video connector and wait for more than 30mins and reconnect.
I have verified the video signal and all my cabling on some of the newer 24' monitors and they all work fine.
It seems some of the earlier monitors have a problems with the S-video and C-video inputs.
Does anybody have see this problem on thier 24" SUN LCDs. Is there a fix.
Any suggestions welcome.
Thanks
Surendra
[email protected]My post has started a more extensive discussion on this problem at an Ars Technica forum:
<http://episteme.arstechnica.com/groupee/forums?a=tpc&s=50009562&f=67909965&m=41 90936913&r=796009877731#796009877731>
It appears that the problem may be inherent in all PVA-based LCD's, which include the Dell 2405FPW. It's not noticeable by everyone but so far everyone I've seen who's taken the time to run an objective test has uncovered the lag. If you can run the test, please do! (See earlier in this thread, or see the Ars Technica thread for a better test involving a stopwatch program run on two monitors).
The good news is Apple's 23" Cinema Display is based on a SIPS LCD panel (as is a similar HP display, and I think a Sony display), and these don't suffer from the lag.
Scott
Maybe you are looking for
-
TSV_TNEW_PAGE_ALLOC_FAILED dump in WDBU: Assortment listing
Hi all, when my SD consultants are executing WDBU either in background or foreground we are getting dump: TSV_TNEW_PAGE_ALLOC_FAILED details are as follows: No more storage space available for extending an internal table. Error anslysis The internal
-
Hello,<br /><br />Is is possible to check the XML Element name exists or not from XML Structure through JavaScript. For example I want to check <flot> element and if that is available execute other code otherwise ignore the next statement.
-
Hi. Just tryed to sync my iphone and restore it by acsident. It wasnt my ariginaly and person who give it to me dosnt know itunes password. Wnen i put my pasword in for activate it, its tell me "cannot be used to unlock this IPhone" What should i do?
-
My IMac is being serviced and I double checked my backup files on my Hitachi 1T Ex HD. I'm viewing the drive on my Win7 machine using Paragon HFS but all my files are empty or 0KB. Anyone know why?
-
After I wiped my disk and updated my OS, I reinstalled Dreamweaver/Fireworks/Flash using recover files (Recover Dreamweaver.exe, Recover Flash.exe, etc.) Everything worked except for Flash, which does the download and then gives me the error "2004 Va