Sun Cluster 3.x connecting to SE3510 via Network Fibre Switch

Sun Cluster 3.x connecting to SE3510 via Network Fibre Switch
Hi,
Currently the customer have 3 nodes clusters that are connected to the SE3510 via to the Sun StorEdge[TM] Network Fibre Channel Switch(SAN_Box Manager) and running SUN Cluster 3.X with Disk-Set.The customer want to decommised the system but want to access the 3510 data on the NEW system.
Initially, I remove one of the HBA card from one the cluster nodes and insert it into the NEW System and is able to detect the 2 LUNS from the SE3150 but not able to mount the file system.After some checking, I decided follow the steps from SunSolve Info ID:85842 as show below:
1.Turn off all resources groups
2.Turn off all device groups
3.Disable all configured resources
4.remove all resources
5.remove all resources groups
6.metaset �s < setname> -C purge
7.boot to non cluster node, boot �sx
8.Remove all the reservations from the shared disks
9.Shutdown all the system
Now, I am not able to see the two luns from the NEW system from the format command.cfgadm �al shows as below:
Ap_Id Type Receptacle Occupant Condition
C4 fc-fabric connected configured
Unknown
1.Is it possible to get back the data and mount back accordingly?
2.Any configuration need to done on the SE3150 or the SAN_Manager?

First, you will probably need to change the LUN masking on the SE3510 and probably the zoning on the switches to make the LUN available to another system. You'll have to check the manual for this as I don't have these commands committed to memory!
Once you can see the LUNs on the new machine, you will need to re-create the metaset using the commands that you used to create it on the Sun Cluster. As long as the partitioning hasn't changed from the default, you should get your data back intact. I assume you have a backup if things go wrong?!
Tim
---

Similar Messages

I cant connect to internet via network

My wifes iPhone 4S will not connect to safari via verizon network. I've tried google, etc.. Search wheel just keeps rotating but not response. It will connect via WiFi at home. But when in the car and she wants to get directions it won't connect. Is there something in settings I'm missing?
Thanks.
Greg

Hi Greg, you may find the following helpful:
Open the "Settings" app then press "General". Then proceed to "Network" and ensure that "Cellular Data" is toggled on. Try navigating to a website in Safari now. If this didn't work try going to "General" then "Reset". You will see a series of six options; select "Reset Network Settings". Try to visit a website once more. If you were unable to load the website try restarting the phone. If all else fails try bringing the phone to a genius bar at an Apple retail store for a diagnostic test.
Hope this helps

Can't connect to internet via airport after switching off

I can create a new network connection and successfully connect to the net. However when I come back to surf later after a couple of power downs it will not connect. My mac can see the network, recognise the name and security type but will not allow connection, even when I retype any password accessing via other network. I've tried setting up a location, used it once but on power back the same issue happens. I can surf via a LAN cable no problem. Help!

By power downs do you mean Sleep?
One thing that might work is to set the IP to Static in Network>Configure IPv4>DHCP with Manual Address.

Solaris Newbie.. Cannot connect to Internet via network

PROBLEM: I have setup solaris 8 and everything installed properly. I can ping the machines locally but outside the local network
I have a linux server running dns and internet sharing gateway.
In sun, I have added the linux as the default router in /etc/defaultrouter
also added linux as the nameserver in /etc/resolv.conf and I have rebooted.
Still I cannot ping outside....anyone help?

Well I solved the problem...
Basically, I had to add the following in nsswitch.conf file
hosts: files dns
Before, I only had files.

Airport express connect with Imac via lan line or can not?

I using IMac with connect to internet with DSL modem router (having 4 lan ports).
Now I put Airport express connect with one of Lan ports from DSL router and still connect my IMac with DSL router via lan line and still connect to internet via lan line (switch off airport function in Imac).
The Airport express is using for provide wireless internet and printer to my other PC.
My Question is can I still set up as above and connect share file to my PC via airport express?
Forget to tell that I'm very newby to mac.

chounws, Welcome to the discussion area!
Yes you can do that. Configure the AirPort Express (AX) to operate in bridge mode (not sharing a single IP address).

Sun Cluster & 6130/6140 thru switch with cross-connections not supported?

Hi:
I noticed that the 6140 does not support cross-connecting the 2 controllers to 2 switches for higher availability when using Sun Cluster:
http://docs.sun.com/source/819-7497-10/chapter3.html
Does anyone know why this restriction is there?
Thanks!

Since there was no real answer to the question in this forum, I cross posted this issue to the cluster forum.
See http://forum.java.sun.com/thread.jspa?threadID=5261282&tstart=0 for the full thread.
Basically, the restriction against cross-connections is no longer valid and the documentation should be updated to remove the note.
This is all a good thing, because I had my 6140's wired into my sun cluster environment via the 'cross-connections' method diagramed in figure 3-4. :-)

Connected to an idle instance in sun cluster nodes.

i have two sun cluster node sharing common storage.
Two schema's:
test1 for nodeA
test2 for nodeB.
My requirement is as below:
Login into b node.
export ORACLE_SID=test1.
sqlplus / as sysdba.
But i am getting as
"connected to an idle instance"
Is there any way to connect to node A schema from Node B.

I found the answer..
sqlplus <sysdbauser>/<password>@test1 as sysdba

Sun cluster, 6140 and 'cross-connections'

This was brought up in the storage forum by somebody else, but the responses never answered the original question:
In the 6140 setup document located at http://docs.sun.com/source/819-7497-11/chapter3.html#50589714_93886 it shows two different ways to cable a host to a 6140 via a SAN switch. figure 3-3 and 3-4
It states that the setup in 3-4 is not supported in a sun cluster environment.
The problem is that given the acive/passive nature of the 6140, the setup shown in 3-4 is the obvious one to use since it prevents one from having to force all of the luns over in the event of an hba port or switch failure.
To make life more interesting, the 6140 setup doc does not make not of what version of sun cluster it is not supported on. Or what the bugid is, or any informationto know if the restriction is still valid.
So, does this restriction still exist? If so, for what version of sun cluster? What version of solaris?

Thanks for the clarification.
As an aside, it would be nice if in the future, the documentation could contain a bit more information than just a simple note saying 'this is not supported'. A reference to a bugid or info doc would go a long way in helping folks determine if the restriction is still valid.
--john

Any experience with NFS failover in Sun Cluster?

Hello,
I am planning to install dual-node Sun Cluster for NFS failover configuration. The SAN storage is shared between nodes via Fibre Channel. The NFS shares will be manually assigned to nodes and should fail over / takeback between nodes.
Is this setup tested well? How the NFS clients survive the failover (without "stale NFS handle" errrors)? Does it work smoothly for Solaris,Linux,FreeBSD clients?
Please share your experience.
TIA,
-- Leon

My 3 year old linux installtion on my laptop, which is my NFS client most of the time uses udp as default (kernel 2.4.19).
Anyway the key is that the NFS client, or better, the RPC implementation on the client is intelligent enough to detect a failed TCP connection and tries to reestablish it with the same IP address. Now once the cluster has failed over the logical IP the reconnect will be successful and NFS traffic continues as if nothing bad had happened. This only(!) works if the NFS mount was done with the "hard" option. Only this makes the client retry the connection.
Other "dumb" TCP based applications might not retry and thus would need manual intervention.
Regarding UFS or PxFS, it does not make a difference. NFS does not know the difference. It shares a mount point.
Hope that helped.

Sun Cluster, vx mode - "mode: enabled: cluster inactive"

Hi,
I have installed sun cluster 3.2 on solaris 9 (Solaris 9 9/05). I want to make it an active-active setup with shared veritas DGs. This setup also has vxvm 5 (Veritas-5.0_MP1_RP4.4) with rolling pack 4 and solaris has all the latest pathes updated via "updatemanager". The shared storage comes from DMX800.
In order to get VxVM in cluster mode I have installed licenses for CVM, VCS and also ORCLudlm (3.3.4.8 ) package.
The sun cluster install has all the necessary framework packages. But the VX mode refuses to be in cluster mode:
#vxdctl -c mode
mode: enabled: cluster inactive
Issue is udlm daemon "dlmmon" isnt starting.
Also I see the below errors
cacao: Error: Fail to start cacao agent. (instance default)
Error: Fail to start cacao agent. (instance default)
AND messages file on nodeA shows the below error
[ID 988885 daemon.error] libpnm error: can't connect to PNMd on nodeB
I am at my wits end on how to resolve this issue :(
Any help is appreciated.
Regards,
Ashish

Well it could be the problem I ran into... and I went round and round for ages trying to figure out what was wrong - before I realised my mistake.
Assuming you have VxVM/CVM licensed properly, check that ORCLudlm is installed on all nodes. Then create your rac-framework-rg and ensure you have a rac-framework-rs, rac-udlm-rs AND a rac-cvm-rs resource. Now, unless you have both of these and they can be brought enabled and brought online, then you'll have exactly the problem you are seeing.
Hope that helps,
Tim
Edited by: Tim.Read on Feb 19, 2008 4:08 AM
Ooops missed the rac-udlm-rs ... Doh!

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

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

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

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

Connection to CRX via RMI and getting WeakReference value..... with an exception!

Hi there,
I have the following problem.
I opened a ticket in Day Care Support system, about CRX users/group membership that got lost while synchronization with our LDAP server.
Although when the user and the group had been created (and therefore taken from that same LDAP server), the membership was good.... but after some time the membership got lost......
So what i am trying to do now is a Java program that connects to CRX via RMI.
And gets the list of all the users from a group (aka membership).
The idea is to monitor the membership each seconds.
But when trying to get the property "rep:members" of the group, I have the following exception :
javax.jcr.ValueFormatException: Unknown value type 10
          at org.apache.jackrabbit.rmi.server.ServerObject.getRepositoryException(ServerObject.java:13 9)
          at org.apache.jackrabbit.rmi.server.ServerProperty.getValues(ServerProperty.java:71)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at java.lang.reflect.Method.invoke(Method.java:611)
          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)"
I searched a little bit and found that "10" is the number for type WeakReference.
That's normal to me because memberships are stored in the group as a list reference to users linked to that group....
Anyways, what's not normal to me is that when the type is "10" the API does not let me get the Value (cf. ServerProperty.getValues() method)
Here is the program:
import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;
import javax.imageio.spi.ServiceRegistry;
import javax.jcr.Node;
import javax.jcr.NodeIterator;
import javax.jcr.Property;
import javax.jcr.PropertyIterator;
import javax.jcr.Repository;
import javax.jcr.RepositoryException;
import javax.jcr.RepositoryFactory;
import javax.jcr.Session;
import javax.jcr.SimpleCredentials;
import javax.jcr.Value;
public class Test {
          public static void main(String[] args) {
                    String uri = "rmi://sma11c02.............:1234/crx";
                    String username = "admin";
                    char[] password = {....................};
                    String workspace = "crx.default";
                    String nodePath = "/home/groups/a";
                    Repository repository = null;
                    Session session = null;
                    try {
                              // Connection to repository via RMI
                                        Map<String, String> jcrParameters = new HashMap<String, String>();
                                        jcrParameters.put("org.apache.jackrabbit.repository.uri", uri);
                                        Iterator<RepositoryFactory> iterator = ServiceRegistry.lookupProviders(RepositoryFactory.class);
                                        while (null == repository && iterator.hasNext()) {
                                                  repository = iterator.next().getRepository(jcrParameters);
                              if (repository == null) {
                                        throw new IllegalStateException("Problem with connection to the repository...");
                              // Creation of a session to the workspace
                              session = repository.login(new SimpleCredentials(username, password), workspace);
                              if (session == null) {
                                        throw new IllegalStateException("Problem with creation of session to the workspace...");
                              // Get the targetted node
                              Node node = session.getNode(nodePath);
                              System.out.println("Node : " + node.getName());
                              System.out.println();
                              PropertyIterator properties = node.getProperties();
                              System.out.println("List of properties for this node :");
                              while (properties.hasNext()) {
                                        Property property = properties.nextProperty();
                                        System.out.print("\t"+property.getName() + " : ");
                                        if (property.isMultiple()) {
                                                  Value[] values = property.getValues();
                                                  for (int i = 0; i < values.length; i++) {
                                                            System.out.print(values[i]);
                                                            if (i+1 != values.length) {
                                                                      System.out.print(", ");
                                                  System.out.println();
                                        } else {
                                                  Value value = property.getValue();
                                                  System.out.println(value);
                              System.out.println();
                              NodeIterator kids = node.getNodes();
                              System.out.println("List of children nodes for this node :");
                              while (kids.hasNext()) {
                                        Node kid = kids.nextNode();
                                        System.out.println("\tChild node : "+kid.getName());
                                        PropertyIterator kidProperties = kid.getProperties();
                                        System.out.println("List of properties for this child :");
                                        while (kidProperties.hasNext()) {
                                                  Property property = kidProperties.nextProperty();
                                                  System.out.print("\t"+property.getName() + " : ");
                                                  if (property.isMultiple()) {
                                                            Value[] values = property.getValues();
                                                            for (int i = 0; i < values.length; i++) {
                                                                      System.out.print(values[i]);
                                                                      if (i+1 != values.length) {
                                                                                System.out.print(", ");
                                                            System.out.println();
                                                  } else {
                                                            Value value = property.getValue();
                                                            System.out.println(value);
                                        System.out.println();
                    } catch (RepositoryException e) {
                              e.printStackTrace();
                    } finally {
                              if (session != null) {
                                        session.logout();
Here is the output of the below program:
Node : a
List of properties for this node :
          jcr:createdBy : admin
          jcr:mixinTypes : mix:lockable
          jcr:created : 2011-10-25T16:58:48.140+02:00
          jcr:primaryType : rep:AuthorizableFolder
List of children nodes for this node :
          Child node : administrators
List of properties for this child :
          jcr:createdBy : admin
          rep:principalName : administrators
          rep:members : javax.jcr.ValueFormatException: Unknown value type 10
          at org.apache.jackrabbit.rmi.server.ServerObject.getRepositoryException(ServerObject.java:13 9)
          at org.apache.jackrabbit.rmi.server.ServerProperty.getValues(ServerProperty.java:71)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
          at java.lang.reflect.Method.invoke(Method.java:611)
          at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
          at sun.rmi.transport.Transport$1.run(Transport.java:171)
          at java.security.AccessController.doPrivileged(AccessController.java:284)
          at sun.rmi.transport.Transport.serviceCall(Transport.java:167)
          at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:547)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:802)
          at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:661)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919)
          at java.lang.Thread.run(Thread.java:736)
          at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
          at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
          at sun.rmi.server.UnicastRef.invoke(Unknown Source)
          at org.apache.jackrabbit.rmi.server.ServerProperty_Stub.getValues(Unknown Source)
          at org.apache.jackrabbit.rmi.client.ClientProperty.getValues(ClientProperty.java:173)
          at Test.main(Test.java:96)
Here is the list of jar files i'm using with this program:
          2862818581          61388           crx-rmi-2.2.0.jar
          732434195           335603           jackrabbit-jcr-commons-2.4.0.jar
          1107929681           411330           jackrabbit-jcr-rmi-2.4.0.jar
          3096295771           69246           jcr-2.0.jar
          1206850944           367444           log4j-1.2.14.jar
          685167282           25962           slf4j-api-1.6.4.jar
          2025068856           9748           slf4j-log4j12-1.6.4.jar
Finally, we are using CQ 5.4 (CRX 2.2) with the latest hotfix and under Websphere 7.0
Best regards,
Vincent FINET

Je suis absent(e) du bureau jusqu'au 17/04/2012
Je suis absent.
Je répondrai à votre sollicitation à mon retour le 17 avril 2012.
Cordialement,
Vincent FINET
Remarque : ceci est une réponse automatique à votre message "[CQ5]
Connection to CRX via RMI and getting WeakReference value..... with an
exception!" envoyé le 13/4/12 0:32:14.
C'est la seule notification que vous recevrez pendant l'absence de cette
personne.
Le papier est un bien precieux, ne le gaspillez pas. N'imprimez ce document que si vous en avez vraiment besoin !
Ce message est confidentiel.
Sous reserve de tout accord conclu par ecrit entre vous et La Banque Postale, son contenu ne represente en aucun cas un engagement de la part de La Banque Postale.
Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement.
Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur.

Sun Ray error when connecting to Oracle VDI - No Kiosk Sessions Available

When the Sun Ray DTUs go to connect to the Oracle VDI cluster at times they will throw the error "Error starting Kiosk session: No Kiosk accounts configured." We have tried going through the steps to confirm that the Kiosk sessions are configured on the two secondary hosts but the problem persists. When the Sun Ray DTUs do connect they will work for a while and then when left idle for a period of time will loose their connection and be unable to restart the connection with the error mentioned. The Screen Blanking option on the Sun Ray DTUs is set to "0" to prevent them from going into power-save mode but this makes no difference. The Sun Ray DTUs are all updated with the latest GUI firmware and there are no custom options set in the Sun Ray Session Servers.
The thing that bothers me the most is I have not seen any error messages in the logs. I will post up the logs as links in a follow-up post.
Has anyone had any similar issues while connecting with a Sun Ray DTU?
Currently we are running Oracle VDI 3.2.1 on the cluster.
Here are the commands we used to reset the Sun Ray Kiosk accounts:
# /opt/SUNWkio/bin/kioskstatus -c
# /opt/SUNWkio/bin/kioskuseradm status
# /opt/SUNWkio/bin/kioskuseradm delete
# /opt/SUNWkio/bin/kioskuseradm create -l utku -g utkiosk -i auto -u –c

I was trying to transfer data from oracle to sql server 2008 on a daily basis.
I have very hard time connecting to oracle from ssis package on windows server 2008. I am almost dead and cannot find any help. i was able to connect to oracle using import/export 64 bit feature of SQL Server 2008 using Oracle provider for OLEDB. But I am not sure why the same does not work with BIDS?
Here's the environment info:
1. Oracle Client 10g
2. SQL Server 2008
3. Windows Server 2008
Appreciate your help. Please save me.
Thanks,

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.x connecting to SE3510 via Network Fibre Switch

Similar Messages

Maybe you are looking for