Vintela on unix cluster

Hello
I need to install Vintela on unix cluster.
I have 1 virtual cluster name and 2 server name ,in the sap system I have the central system and 4 appl system.
Do I need to write all parameters in all instance profile or just in the default or central instance profile?
Does someone install Vintela on unix cluster and can give me same information?
I will be glad for information?
Thank You
Eyal

You should contact the 3rd party vendor for info.
I did find this guide that might be useful tho.
https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/d0f6ac3c-b3ac-2b10-1b95-c9bd46194977
Regards
Juan

Similar Messages

I need kernal upgrade on hp unix cluster ECC6 process step to step

Hello,
I need kernal upgrade procedure on hp unix cluster ECC6 in step to step
Please help me .
Regards
Mahesh

Hi,
If its a cluster or single instance, the procedure is the same.
As a thumb rule always execute the program RSPARAM from se38 and find the directory structure of the parameter DIR_CT_RUN.
The default value is generally /usr/sap/SID/SYS/exe/run
Download the SAPEXE<NO>.SAR and SAPEXEDB<no>.SAR and extract i in the above directory.
Before you do it make sure thats:
Stop the SAP R/3 resource in the cluster. Leave the SAP disk online.
Replace the Kernel
Start the instance
Replicate executables in the c:windowssapcluster or c:winntsapcluster (on both nodes)
You are done
Thanks Nirmal

MySAP ERP 2004 ECC5 installation on Unix Cluster

hi
I want to install mySAP ERP 2004 ECC5 ABAp component on HP unix 11i cluster. Please let me know the procedure. What are the details I have to give to HP person .
The installation will active-passive ie ci and db will be in the same system.
What are all mount points should be in the cluster and in the local system
Please reply ASAP
Regards
Prasanna.B.S

hi Penbury Young
Thanks for your suggestion, I have installed the mySAP ERP 2004 on HP UX cluster. We are facing one problem, when we move package to second node we are unable to login. Why is it so.
We are able to login to the server in Node 1
please help me out
Regards
Prasanna.B.S

Unix Cluster Services provided with 10G

The information that I have read with regards to Oracle 10G (for Unix customers) suggests that 10G now includes volume management, file systems and the cluster services.
Within earlier release of Oracle DB and Apps, the above components would have been provided by software vendors (e.g. Veritas) or the hardware vendors themselves (Sun, IBM etc..).
The provision of an Oracle 10G architecture to customers without the requirement to procure additional "clusterware" services will clearly appeal to customers on tight budgets or who or currently focused on ROI. However, what about customers who are focused on performance and the highest levels of availability?
Looking at the file system provided by Oracle (OSFS?), does this file system include journaling capabilities (i.e. improve fsck performance under unplanned system crash conditions). In addition, does the ORacle file system allow storage check points to be taken at a file system level? Finally, is there any performance data available comparing the Oracle file system directly with say Vxfs (either vanila product or with direct I/O) or Sun's UFS?
Thanks in advance.
Nathan

In Oracle 10g there are two features that provide files system type functions. The first is Oracle Clustered File System (OCFS). It has been built to support clustered files for RAC deployments on NT and Linux. As I am not an expert on OCFS, I will not attempt to address your specific OCFS questions at this time.
The second feature is Automatic Storage Management (ASM) which is an integrated file system and volume manager purpose built for the Oracle data files. It is a tool for the DBA to manage database storage and to increase their productivity. It speeds up the process of database layout and greatly simplifies the process of extending the storage configuration for a database. However, it is not a general purpose file system nor a general purpose clustered file system as it does not support flat files, trace files or binaries at present. ASM supports both single instance databases on a single node as well as on a clustered set of nodes. It also supports RAC.
As for performance and availability, ASM has been doing very well in stress testing and beta testing. It performs as well as other file system and volume manager environments and in most cases ASM does better than those other environments. As a non ASM database will typically becomes fragmented and needs to have storage capacity added to it, the performance of that database will either decline or will require vast amounts of DBA and SA time to keep its performance optimal. With the database running on ASM managed disks, the performance will stay optimal with minimal maintenance from DBA and SA. ASM will rebalance the data across new storage and by way of its distribution of the data across the entire storage pool, there will be no fragmentation or imbalance of the workload. With ASM the manual task of I/O performance tuning will not be required.
We do not yet have any published benchmarks at this time but hope to be able to publish a number which compares ASM to other volume mgmt and file systems environments at two points in time; one is the set up of a new config (best case) and the other is 6 months later when both environments have had the same fragmentation and storage configuration changes. That benchmark will need to track the time spent managing those two databases over that 6 months of as well. The challenge is that no such benchmark exists today.

Is Unix Cluster is Pre-requisite for RAC

Hi ,
Can anyone please clarify whether for the setup of RAC , does the Unix need to be in clusters?. Is it the pre-requisite for rac installing.
Thanks in advance.
Regards,
Hussain

Hi Hussain,
No, you don't need another OS cluster, only RAC, but you can use another clusterware with RAC (eg. SUN Cluster and others).
I recommend to you read http://download.oracle.com/docs/cd/B19306_01/rac.102/b28759/toc.htm
Regards,
Rodrigo Mufalani
http://mufalani.blogspot.com

HELP - Getting INS0034 Error while running RuntimeAssistant on UNIX

Hy all,
hope anyone here can help me.
The Problem:
OWB 10.1.0.1.4 is installed on a UNIX Cluster-Server (OS: Solaris 10)
(I connect remote to the Server via a tunneled ssh connect x-session).
So, i still have run the reposinst.sh via that connection - No Problem.
Next step was to create a runtime repository. I started the runtimeinst.sh, the wizzard opened in the GUI and i´ve inserted the SYS passord, ip-adress, Port, sid.
Then i made a cklick on Next,... and then : INS0034....needs to run on the server where the Database is installed.
I don´t understand what´s the Problem. The Database is installed on this server.
The owb Software is installed on this server.
The owb is in a different oracle Home installed.
Connect to the Databes is ok.
I can build a design repository, but the runtimeinst.sh said evrytime : INS0034.
Where´s my Fault?
I´ve tried with the IP Adress, with 'localhost',..... The Port and SID is absolutely ok.
I realy hope anyone can help me, i still looked on so much Sites in the web, and in the Oracle Installation Guide.
Thanks in Advance
LoneWolf

Yes , it does. I might be wrong but, I think the problem comes from stage initalization. Because I check the logs and every thing is ok. My environment is:
OS: ubuntu 11.10 - 64 bit
jdk: jdk1.7.0_03 - 32bit
javafx: JavaFX 2.1 build b17
Thanks
sdemirci
Edited by: sdemirci on 20.Mar.2012 07:19

How to Cluster AS

dear all,
i have Oracle9iAS R2 installed(busniss intelgence) with infratstarur on UNIX cluster Node1 and i want to install the Application server so it can be clustered so what can i do, what r the steps, what i did was that i installed Appication server(busniss intelgence) on the other node and when it asked me about an existing SSO i pointed to node 1. i thought it was right anyway thank u all

I'm also puzzled by this problem.
Some OTN documents say that I have to create a cluster instance in OEM, so i do. I try to add a 9iAS BI instance in to the cluster, it raises a error which says only instance with clusterable components can be added into cluster. In other documents it is said portal and wireless are unclusterable components, so I uninstall them, than 9iAS can't startup.
So, I reinstall 9iAS, and try to not install portal and wireless, but find there is no manual intallation type can be choosen. If choose BI installation type, all components will be installed.
How can I cluster oracle 9iAS, especially form service and report service? And how to manually install 9iAS?

Installing dialog instance on cluster.

Hi ,
I have installed ASCS, SCS,CI and DI , on Unix Cluster Evironment ,
Now i am trying to install Dialog instance on Node B, but it is looking for Default profile which is available on /sapmnt/sid/profiles,
How do i get it on node B, Can anyone guide me how to do it using NFS, or is there any other way.
Regards,
SM..

Hi
you need to export your /sapmnt/<SID> structure using NFS on the host where it resides .
If you want to use the inactive Node as an Application Server , you need to mount /sapmnt/<SID> from the NFS-Server , where it was exported , to your Node B Application Server .
There is nothing different to an regular application server so far .
Since there are different management interfaces on different operating systems , I cannot give more detailed informations , but I suppose , you will get this managed .
If you have any technical difficulties , let us know and provide more details to your cluster environment (At least , which operating system you use and which error you get).
Best regards
dirk

LiveCache on Cluster Active/Active

Hi SAP gurus...
is it possible to install liveCache on an Active/Active Cluster (MSCS)?
is there any SAP note or Microsoft document available with instructions?
thanks
Antonio

Hi António,
it depends on how you define the ACTIVE/ACTIVE cluster.
If you want to have the SCM system on one node and the liveCache on the other - this should work, yes.
If you mean something like Oracle RAC where the liveCache is running on both nodes in parallel - no, there's no way to do that.
For installation instructions, simply check the notes that you get by searching for "livecache + mscs":
780759     liveCache 7.5: MSCS Installation
782616     liveCache 7.4.03: MSCS Installation
508979     SAP DB/MaxDB/liveCache-Upgrade mit MSCS Cluster Var.1
843560     SAP DB/MaxDB/liveCache-Upgrade mit MSCS Cluster Var.2
912246     SAP DB/MaxDB/liveCache-Upgrade mit MSCS Cluster Var.3
570969     Servicepack3 mit MSCS Cluster
883537     Restart failed MSCS Cluster MaxDB/liveCache 2003-IA64
803452     MaxDB-Verzeichnisse in UNIX-Cluster für Failover
820824     FAQ: MaxDB / SAP liveCache Technology
regards,
Lars

Using WebLogic in HPUX-Cluster with MC Service Guard

Hi
I have the following problem:
Bea WLS is installed on a shared device with MC Service Guard
Integration. This Package has a distinct IP Address to which the License
File is pointing.
This IP Address belongs also to the maschine the shared device is
attached to.
When I start WebLogic it always uses the IP-Address belonging to the
maschine the shared device is mounted on rather than the one the package
has. This behavior leads to a license exception.
Is there a solution for using MC ServiceGuard IPs or do I have to
convert my license ?
Yours,
Michael Strauß
[strauss.vcf]

We're running BEA Weblogic in a HP-UX cluster over here, and it works without any
problems.
Bart
"Narendra Ravi" <[email protected]> wrote:
>
Hi,
Did you find if it is possible to run BEA WLS on a UNIX cluster?
Thanks,
Michael =?iso-8859-1?Q?Strau=DF?= <[email protected]> wrote:
Hi
I have the following problem:
Bea WLS is installed on a shared device with MC Service Guard
Integration. This Package has a distinct IP Address to which the License
File is pointing.
This IP Address belongs also to the maschine the shared device is
attached to.
When I start WebLogic it always uses the IP-Address belonging to the
maschine the shared device is mounted on rather than the one the package
has. This behavior leads to a license exception.
Is there a solution for using MC ServiceGuard IPs or do I have to
convert my license ?
Yours,
Michael Strauß
Content-Description: Card for Michael Strauß
begin:vcard
n:Strauß;Michael
tel;work:069-29985-183
x-mozilla-html:FALSE
url:http://www.santander.de
org:Santander Direkt Bank ;Anwendungsentwicklung Anlagen
adr:;;Gräfstraße 97;Frankfurt;;60282;Germany
version:2.1
email;internet:[email protected]
fn:Michael Strauß
end:vcard

Recomended Cluster Setup?

We are setting up an HA WebApp based on iAS6sp2 and would like some
clustering recommendations. Here is a basic setup:
4 Solaris boxes (Solaris 8) configured like this:
iWS1 has iPlanet WS 4.1sp?? w/iAS WebConnector
iWS2 has iPlanet WS 4.1sp?? w/iAS WebConnector
iAS1 has iPlanet iAS 6 Sp2
iAS2 has iPlanet iAS 6 Sp2
(Note: both iWS's are frontended by a web server director - there is a
pair for redundancy. The backend (behind the iAS instances) is an
oracle db cluster.)
Right now iWS1 and iAS1 are connnected and use and LDAP on iAS1. The
same pattern exists for iAS2/iWS2. Our WebApplication(s) consists of
state oriented JSPs and servlets that use stateless EJBs (ejbs and
servlets live together in iAS (in single KJS)).
We want all combinations of fail overn (the WSD will handle failover
between iWS instances):
iWS1 -- iAS1
\ / |
/ \ |
iWS2 -- iAS2
So session are replicated between iAS instances and iWS instances (well
the WebConnector) can route to either iAS instance. How would one set
this up? In our NT lab (same basic picture w/o WSD), we have done this
via a shared LDAP instance on one of the iAS boxes. However, that LDAP
instance represnets a single point of failure. How does one set up
failover for LDAP 'master'? Or is this even on the right track.
Ultimately, we will have 2 data centers 'north' and 'sourth' that will
have clustered as described above (we call them local clusters). We
will need to failover between the north and south 'local' clusters, and
would like sessions (and cluster data) to replicate (less frequently)
between the north and south, too. Insight into this setup would be good
too..
Thanks for any help.
Fred Welland

Hi Fred,
Here is the link, as to how to install a simple two iAS cluster :
http://developer.iplanet.com/appserver/samples/cluster/docs/unix-cluster.html
Just go through it and try instaling both the iAS with a common LDAP.
Note: please do the Custom installation only for both iAS servers.
You can install a backup LDAP server also.
I have attached a file in which what ever the inputs are requred
during enabling the directory replication service, are given. Please
go through it and try installing the LDAP same way.
Note: The steps written in the file are the steps asked by installer,
during Custom iAS installation, after initial common steps.
And i don't think that failover between the two already setup clusters
is possible,
as for a cluster, config parameter (iasconfig) and LDAP server should
be same.
And in a cluster to have a distributed session and a failover support,
you need to deploy the application on all the iAS servers
participating in the cluster.
So if you put the same iasconfig name with common LDAP and app.
deployed on all the servers, than it is like a single cluster, not two
local clusters.
I am working on this, and will get back to you after some time with
some solution.
Meanwhile if you have any other doubts, please feel free to mail me.
Regards,
Sanjeev.
Developer Support Group iAS.
Fred Welland wrote:
>
We are setting up an HA WebApp based on iAS6sp2 and would like some
clustering recommendations. Here is a basic setup:
4 Solaris boxes (Solaris 8) configured like this:
iWS1 has iPlanet WS 4.1sp?? w/iAS WebConnector
iWS2 has iPlanet WS 4.1sp?? w/iAS WebConnector
iAS1 has iPlanet iAS 6 Sp2
iAS2 has iPlanet iAS 6 Sp2
(Note: both iWS's are frontended by a web server director - there is a
pair for redundancy. The backend (behind the iAS instances) is an
oracle db cluster.)
Right now iWS1 and iAS1 are connnected and use and LDAP on iAS1. The
same pattern exists for iAS2/iWS2. Our WebApplication(s) consists of
state oriented JSPs and servlets that use stateless EJBs (ejbs and
servlets live together in iAS (in single KJS)).
We want all combinations of fail overn (the WSD will handle failover
between iWS instances):
iWS1 -- iAS1
\ / |
/ \ |
iWS2 -- iAS2
So session are replicated between iAS instances and iWS instances (well
the WebConnector) can route to either iAS instance. How would one set
this up? In our NT lab (same basic picture w/o WSD), we have done this
via a shared LDAP instance on one of the iAS boxes. However, that LDAP
instance represnets a single point of failure. How does one set up
failover for LDAP 'master'? Or is this even on the right track.
Ultimately, we will have 2 data centers 'north' and 'sourth' that will
have clustered as described above (we call them local clusters). We
will need to failover between the north and south 'local' clusters, and
would like sessions (and cluster data) to replicate (less frequently)
between the north and south, too. Insight into this setup would be good
too..
Thanks for any help.
Fred Welland

SAP not started on CI node thru Cluster Script

Hi
We have installed the PI 7.1 on HP Unix 11v3 and oracle conbination. We have done the cluster package failover
of CI to DB system and done the complete installation on DB with high availability option. Let on we have splited
the CI to CI and keep the DB to DB note. The installation happend successfully and system started successfully on
both node.
Now we are doing the HP-UNIX cluster configuration and integration. But we have found that the DB services are
starting up successfully on DB node but the CI services are not starting up on CI node. The cluster error file
are attached for your reference. Since the project golive is left just 20 day . Request you to provide solution
on the same. Please also let us know if any further log is required.
Regards
Vimal Pathak

Oct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: Start
Oct 6 16:16:13 root@htlxici: (start_app ciPP9 01 pp9adm): P: FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 356 returns 0
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_app ciPP9 01 pp9adm): Finishing startup attempt
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 29953
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (start_d): Leaving parallel dialog instance startup delay
Oct 6 16:16:13 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:14 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1016 for 1015 - Timeout: 100 secs)
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1015 returns 1
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 5 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:22 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:23 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:24 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1466 for 1464 - Timeout: 100 secs)
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1464 returns 1
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:25 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 10 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:35 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:36 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 1919 for 1917 - Timeout: 100 secs)
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 1917 returns 1
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:37 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 15 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:16:52 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:16:53 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:16:54 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2412 for 2410 - Timeout: 100 secs)
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2410 returns 1
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:16:55 root@htlxici sapinstance.sh[29446]: (crit_test_app): Delaying 20 secs to allow instance DVEBMGS01 startup/recover
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (is_ip_local): ciPP9 is local
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:15 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:16 root@htlxici sapinstance.sh[29446]: (watchdog): Watchdog initiated (PIDs: 2878 for 2875 - Timeout: 100 secs)
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (watchdog): wait for PID 2875 returns 1
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:17 root@htlxici sapinstance.sh[29446]: (start_d): ERROR: Instance DVEBMGS01 - fatal startup problem detected
Oct 6 16:17:17 root@htlxici master_control_script.sh[28963]: ##### Failed to start package ciPP9, rollback steps #####
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Entering SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: SGeSAP - B.05.00.00 - Last modified 02/11/08
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/sap_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Found: /etc/cmcluster/scripts/sgesap/customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: Not found: /etc/cmcluster/scripts/ext/ciPP9_customer_functions.sh
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Version check passed
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_versions): Log Level is 4
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance administrator : 'pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance home directory : '/home/pp9adm'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Startprofile            : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance profile        : '/usr/sap/PP9/SYS/profile/PP9_DVEBMGS01_ciPP9'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (set_environment DVEBMGS01): Instance work directory : '/usr/sap/PP9/DVEBMGS01/work'
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sappfpar" owner: "pp9adm"
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Trying to determine instance type of DVEBMGS01...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): Package will handle Application Server Instance DVEBMGS01
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /sapmnt/PP9/global...
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3216 for 3215 - Timeout: 100 secs)
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3215 returns 0
Oct 6 16:17:18 root@htlxici sapinstance.sh[3089]: (check_access): /sapmnt/PP9/global accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): Testing directory /usr/sap/PP9...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3244 for 3243 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3243 returns 0
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (check_access): /usr/sap/PP9 accessible
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (init_params_sap_inst): System is not using Instance Agents
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Initiate stopping of dialog instance DVEBMGS01 on ciPP9
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Attempting local stop of instance...
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_d): Waiting for parallel shutdown sequence to finish
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (stop_app ciPP9 01 pp9adm): Running /usr/sap/PP9/DVEBMGS01/exe/sapcontrol -nr 01 -function StopWait 100 1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 3325 for 3322 - Timeout: 100 secs)
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Forked the wait_pidlist background shell. PID: 3319
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDLIST: 3271 -1
Oct 6 16:17:19 root@htlxici sapinstance.sh[3089]: (wait_pidlist): PIDlist watchdog initiated (PIDlist: 3271)
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 3322 returns 0
Oct 6 16:17:20 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/cleanipc" owner: "pp9adm"
Oct 6 16:17:22 root@htlxici sapinstance.sh[3089]: (clean_ipc): Searching shmem of DVEBMGS01 on htlxici using normal cleanup policy
Oct 6 16:17:23 root@htlxici: (clean_ipc): P: OsKey:    10110 0x0000277e Shared Memory Key: 10 removed
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (wait_pidlist): Killed the wait_pidlist background shell. PID: 3319
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (stop_d): Parallel dialog instance shutdown finished
Oct 6 16:17:23 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/sapcontrol" owner: "pp9adm"
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (is_ip_local): ciPP9 is local
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect local dispatcher of instance DVEBMGS01 ...
Oct 6 16:17:25 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/dpmon" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): dpmon: /usr/sap/PP9/DVEBMGS01/exe/dpmon=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (crit_test_app): Trying to connect via RFC to host ciPP9 instance DVEBMGS01 ...
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (find_sap_binary): found location: "/usr/sap/PP9/DVEBMGS01/exe/startrfc" owner: "pp9adm"
Oct 6 16:17:26 root@htlxici sapinstance.sh[3089]: (watchdog): Watchdog initiated (PIDs: 4369 for 4368 - Timeout: 100 secs)
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (watchdog): wait for PID 4368 returns 1
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): No connection to instance DVEBMGS01
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: (crit_test_app): Instance DVEBMGS01 not responding
Oct 6 16:17:27 root@htlxici sapinstance.sh[3089]: Leaving SGeSAP sapinstance.sh 'stop' runtime steps ...
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Removing 172.31.112.131
Oct 6 16:17:27 root@htlxici package_ip.sh[4578]: Remove IP address 172.31.112.131 from subnet 172.31.112.0
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Number of components: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted components in array: 5 6
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: sorted indexes: 0 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 1 /usr/sap/PP9/DVEBMGS01 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: processing 0 /usr/sap/PP9 1
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: Mount order: 1 2
Oct 6 16:17:27 root@htlxici filesystem.sh[4610]: max mnt order: 2
Oct 6 16:17:28 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/DVEBMGS61
Oct 6 16:17:29 root@htlxici filesystem.sh[4610]: Unmounting filesystem on /dev/vx/dsk/pp9cidg/sap_PP9
Oct 6 16:17:29 root@htlxici volume_group.sh[4678]: Deporting disk group pp9cidg
Oct 6 16:17:30 root@htlxici master_control_script.sh[28963]: ###### Failed to start package for ciPP9 ######

Simple two node Cluster Install - Hung after reboot of first node

Hello,
Over the past couple of days I have tried to install a simple two node cluster using two identical SunFire X4200s, firstly following the recipe in: http://www.sun.com/software/solaris/howtoguides/twonodecluster.jsp
and when that failed referring to http://docs.sun.com/app/docs/doc/819-0912 and http://docs.sun.com/app/docs/doc/819-2970.
I am trying to keep the install process as simple as possible, no switch, just back to back connections for the internal networking (node1 e1000g0 <--> node2 e1000g0, node1 e1000g1 <--> node2 e1000g1)
I ran the installer on both X4200s with default answers. This went through smoothly without problems.
I ran scinstall on node1, first time through, choosing "typical" as suggested in the how to guide. Everything goes OK (no errors) node2 reboots, but node1 just sits there waiting for node2, no errors, nothing....
I also tried rerunning scinstall choosing "Custom", and then selecting the no switch option. Same thing happened.
I must be doing something stupid, it's such a simple setup! Any ideas??
Here's the final screen from node1 (dcmds0) in both cases:
Cluster Creation
Log file - /var/cluster/logs/install/scinstall.log.940
Checking installation status ... done
The Sun Cluster software is installed on "dcmds0".
The Sun Cluster software is installed on "dcmds1".
Started sccheck on "dcmds0".
Started sccheck on "dcmds1".
sccheck completed with no errors or warnings for "dcmds0".
sccheck completed with no errors or warnings for "dcmds1".
Configuring "dcmds1" ... done
Rebooting "dcmds1" ...
Output from scconf on node2 (dcmds1):
bash-3.00# scconf -p
Cluster name: dcmdscluster
Cluster ID: 0x47538959
Cluster install mode: enabled
Cluster private net: 172.16.0.0
Cluster private netmask: 255.255.248.0
Cluster maximum nodes: 64
Cluster maximum private networks: 10
Cluster new node authentication: unix
Cluster authorized-node list: dcmds0 dcmds1
Cluster transport heart beat timeout: 10000
Cluster transport heart beat quantum: 1000
Round Robin Load Balancing UDP session timeout: 480
Cluster nodes: dcmds1
Cluster node name: dcmds1
Node ID: 1
Node enabled: yes
Node private hostname: clusternode1-priv
Node quorum vote count: 1
Node reservation key: 0x4753895900000001
Node zones: <NULL>
CPU shares for global zone: 1
Minimum CPU requested for global zone: 1
Node transport adapters: e1000g0 e1000g1
Node transport adapter: e1000g0
Adapter enabled: no
Adapter transport type: dlpi
Adapter property: device_name=e1000g
Adapter property: device_instance=0
Adapter property: lazy_free=1
Adapter property: dlpi_heartbeat_timeout=10000
Adapter property: dlpi_heartbeat_quantum=1000
Adapter property: nw_bandwidth=80
Adapter property: bandwidth=70
Adapter port names: <NULL>
Node transport adapter: e1000g1
Adapter enabled: no
Adapter transport type: dlpi
Adapter property: device_name=e1000g
Adapter property: device_instance=1
Adapter property: lazy_free=1
Adapter property: dlpi_heartbeat_timeout=10000
Adapter property: dlpi_heartbeat_quantum=1000
Adapter property: nw_bandwidth=80
Adapter property: bandwidth=70
Adapter port names: <NULL>
Cluster transport switches: <NULL>
Cluster transport cables
Endpoint Endpoint State
Quorum devices: <NULL>
Rob.

I have found out why the install hung - this needs to be added into the install guide(s) at once!! - It's VERY frustrating when an install guide is incomplete!
The solution is posted in the HA-Cluster OpenSolaris forums at:
http://opensolaris.org/os/community/ha-clusters/ohac/Documentation/SCXdocs/relnotes/#bugs
In particular, my problem was that I selected to make my Solaris install secure (A good idea, I thought!). Unfortunately, this stops Sun Cluster from working. To fix the problem you need to perform the following steps on each secured node:
Problem Summary: During Solaris installation, the setting of a restricted network profile disables external access to network services that Sun Cluster functionality uses, ie: The RPC communication service, which is required for cluster communication
Workaround: Restore external access to RPC communication.
Perform the following commands to restore external access to RPC communication.
# svccfg
svc:> select network/rpc/bind
svc:/network/rpc/bind> setprop config/local_only=false
svc:/network/rpc/bind> quit
# svcadm refresh network/rpc/bind:default
# svcprop network/rpc/bind:default | grep local_only
Once I applied these commands, the install process continued ... AT LAST!!!
Rob.

Unzip/ Untar files

I am remotely logged into a UNIX cluster at the university and attempting to manipulate some files that I have received from a collaborator. He has "tarred" and "zipped" the files. Unzipping the file with the command
<remote host:directory>% gunzip file.tar.gz
(remote host is the machine I am logged into (via ssh -X username): directory is my directory on the remote host)
This creates the unzipped file- file.tar on <remote host:directory>. The problem arises when I attempt to untar the file. I am using the command
tar -xvfp file.tar
After entering this command, I get the message
tar: can't mkdir /net: Permission denied
tar extract: failed mkdir of <:senders directory>
The same error is produced using [tar -xvf] as the bundled-options. I am assuming that it is attempting to make the directory on my collaborators remote host because the listed location of the failed mkdir is the senders directory <:senders directory> on a different UNIX cluster.
I have tried variations on the tar command (-x or -xv) but those produce the error
tar: tape read error: no tape in drive
I am a bit unfamiliar with the syntax for the [[-]bundled-options Args] in the tar command, but I suspect that I need to specify where the untarred archive is going to be written/ copied. Could anyone provide some guidance on this.
Sincerely,
Aric

Hi Aric,
   Did you copy the error message verbatim? Does it really want to create the directory, /net? If so then the problem is likely to be in the tarball itself.
   There's nothing wrong with your initial syntax. The -x tells tar to unpack the tarball, which is what you're trying to do. The -p says to preserve permissions, which is fine. The 'p' is not supposed to go after the 'f' in the options because the tarball, file.tar, is technically an argument of the -f option. However, most implementations of tar are rather forgiving in that regard. The -v option simply tells tar to be verbose and list the files. Of course there are many implementations of tar and you don't bother to tell us into what kind of machine you're logged.
   Tar has the ability to archive many files and preserve the directory structure. However, it has to recreate those directories when unpacking and that's when it had a problem. It seems that tar wants to create a directory named "net" at the root of the boot drive. I assume that the creator of the tarball archived such a directory on his machine.
   However, most implementations of tar strip the leading slash, turning an absolute path into a relative path. That way when unpacked, the directory structure starts at the current working directory. Unless you tried to unpack this tarball from the root directory of the boot drive, the tar that created this tarball appears to be different.
   Unless you can get the privilege of writing to the root of this boot drive, I would guess that your only recourse is to get the person who created the tarball to redo it using relative paths. See if you can get him to create it with GNU's tar, as that version strips the leading slashes by default.
Gary
~~~~
   OK, so you're a Ph.D. Just don't touch anything.

Problem with ora_br_copy.sh

My source ABAP+Java based DBCI is in a UNIX cluster environment. When I run ora_br_copy.sh to create CONTROL.SQL file, it gives me the following error,
<i>Required system resources are missing or not available:
Oracle listener is not started on port 6808;
Cannot establish connection to Oracle database as SYSTEM user:
Io exception: The Network Adapter could not establish the connection.</i>
My listner is running and so is the database. As orasid if I issue sqlplus system/password, it connects fine at port 6808 but ora_br_copy.sh is failing and I believe because it uses local hostname which is different then the cluster hostname.
Is there a way to provide cluster hostname to the ora_br_copy.sh similar to SAPINST where you can set environment variable SAPINST_USE_HOSTNAME?

First, thanks for reply...
And here are the details you have asked for...
The ora_br_copy.sh creates OraBRCopy.console.log and the contents of the log is as follows,
Oracle listener is not started on port 6808;
Cannot establish connection to Oracle database as SYSTEM user:
Io exception: The Network Adapter could not establish the connection.
This happens both as ora<sid> and <sid>adm..
The contents of the ora_br_copy.sh is as below,
#!/bin/sh
Oracle Backup/Restore startup on UNIX
Make sure prerequisite ORACLE_HOME environment variable is set
if [ -z "$ORACLE_HOME" ]; then
echo "The ORACLE_HOME environment variable is not defined."
echo "This environment variable is needed to run this program."
exit 1
fi
Make sure prerequisite ORACLE_SID environment variable is set
if [ -z "$ORACLE_SID" ]; then
echo "The ORACLE_SID environment variable is not defined."
echo "This environment variable is needed to run this program."
exit 1
fi
Make sure prerequisite JAVA_HOME environment variable is set
if [ -z "$JAVA_HOME" ]; then
echo "The JAVA_HOME environment variable is not defined."
echo "This environment variable is needed to run this program."
exit 1
fi
set -x
"$JAVA_HOME"/bin/java -showversion -cp ".:orabrcopy.jar:$ORACLE_HOME/jdbc/lib/classes12.jar" com.sap.inst.orabrcopy.OraBRCopy -oracleHome "$ORACLE_HOME" -sour
ceSid "$ORACLE_SID" "$@"

Vintela on unix cluster

Similar Messages

Maybe you are looking for