Failover in BODI 11.7.3 AIX

Can a failover be achieved by Server Groups rather than HACMP on AIX. The latter requres running jobs in Recovery mode, which brings a lot of overhead. What happens if a Job server 1 in a server group stops responding in the middle of the job, will the Job Server 2 of the same server group take over the processing?

Sorry experts ,
My problem is solved . Job server associated to the selected port is not working . So the job did not get started.
Thanks for your suport.
Regards,
Dirasa

Similar Messages

BODS 3.1 and Teradata 12 : AL_ENGINE process hanging issue

Hi All,
We are loading into Teradata 12 target tables using BODS 3.1 and sometime a BODS process is left hanging on Teradata side which blocks the target table. Lock has to be removed by Teradata DBA before the job can be executed sucessfully. On the Teradata side the log shows its a AL_ENGINE process via port 3326 using javaw. on BODS side as the job hangs we kill the job and looking at the processes on BODS server no AL_ENGINE process from the repository from where the ETL job was executed from is hanging. BODS is installed on AIX OS and connectivity to Teradata 12 is via an ODBC driver.
The occurence of this issue is highly erratic and not confined to one specific ETL job.
Majority of the job executions are being initiated from the BODS management console.
Thanks,
rana

Check licensing on 3750x stack. suspect master has IP services, other member have only IP Base.

Issues with DB/CI and DI @ different levels

SAP gurus - Hi
Recently migrated my AIX servers (from 5.3 to 6.1) for the CI and DI instances and ran into issues -
Here is the order of events..
1- First migrated the DI instance, applications started alright, active in SAP
2- Then I migrated the inactive node of the CI HACMP cluster - no impact to service
3- Then I did the fail-over from to migrate the other HACMP node, at this point after the cluster failover (the CI is also at AIX 6.1 now), the DI instance is not showing active in SAP GUI anymore, although the SAP is running on both CI and DI at the OS level.
4- We tried to stop/start just the DI, that didn't work
5- Then we stopped/started both DI and CI in the correct order (CI first then DI), still not good
6- Finally rebooted the DI server, started SAP after reboot and then it showed up
Luckily this was in the test environment, I have to progress the change to Production and I cannot imagine having to reboot the Prod DI instances, that is a big no no.
Does this ring a bell? anyone, anybody seen this before? or know what might have caused the app servers to disappear from SAP? anything we can do proactively to avoid this situation? or avoid reboot post-actively?

I'm not sure what you mean by "DI instance is not showing active in SAP GUI anymore", how did you see that ?
What error you captured in screen for fail logon ?
Is this issue reproduciable after migration completed to 6.1 ?
For improper instance stop/start, dev_* trace files / sapstart/stderr logs are the one the look at as well to find out the reason.
Regards,
Vincent

SAP ECC 6.0 SR3 Cluster failover not working in AIX with DB2 UDB V9.1 FP6

Hi Gurus,
We have installed the SAP ECC 6.0 SR3 High Availability with DB2 UDB V9.1 FP6 in AIX cluster environment.
After installation we are doing the cluster fail test.
Node A
Application Server
Mount Points:
/sapmnt/<SID>
/usr/sap/<SID>
/usr/sap/trans
Node B
Database Server
Mount Points:
/db2//<SID>
The procedure followed to do the cluster failover:
We have down the cluster on Node A and all the resources of the Node A has been moved to Node B.
On Node B when we issued a command to start the SAP. It says u201Cno start profiles foundu201D
WE have down the cluster on Node B and moved the Resource from Node B to Node A . There the db2 User IDu2019s are not available. We have crated the user Idu2019s manually on Node A. however it did not work.
Please suggest the procedure to start the sap in cluster failover.
Best Regards
Sija

Hi Sija,
Can i have detailed scenario in your cluster configuration.
Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
Regards
Nick Loy

BODI XI crashes with signal 15 when attempting to select from DB2 on AIX.

I have inherited the task, started 18 months ago, of upgrading from DI 6.1 to XI release 2. My predecessor set up an AIX evalution box to test the impact of the changes to DI, especially the handling of Nulls. As soon as we try extracting DB2 data on this box (using a query transform) we get a signal 15 error, and a core dump. The query can be as simple as selecting a single column from a single table into a template table with no where clause. An SQL function in a script also crashes.
DB2 connect (version 7.1) is on the AIX evaluation box, and is working - I can go to the DB2 prompt, connect to a database and select data. Designer works with DB2, and I can create a new datastore, import metadata, and view data. Oracle to Oracle and oracle to XML work fine on the job server, DB2 to anything optimises the query then falls over.
We thought that it may be a problem with the version of DB2 on the mainframe, but I've tried against DB2 OS/390 7.1.2 and against DB2/6000 7.2.4, both with the same result.
As far as I can see all the environmental variables on the AIX box are OK. Most are the same as on the functioning development box, except for changes that are part of the XI install. One difference is in the libpath - the working box includes '/usr/opt/db2_08_01/lib', which does not exist!!! The evalution box has '/usr/opt/db2_07_01/lib' instead, which does exist. - can a valid reference instead of an invalid one cause a problem?
BODI 6.1 continues to work fine with DB2, as did 5.5 and 5.1.
Anyone seen anything similar? Anyone got any clues as to what is happening?

Which version of Data Integrator are you exactly migrating to ? It this is DI 11.7.x (XI Release 2 Accelerated) -> a big difference with DI 6.1 is that DI 11.7 is a 64-bit application now, hence also needs 64-bit versions of the database drivers. Could that be the issue ?
I would definitely look into that direction to try to locate what's going on. You already indicated there is a difference in the libpath for the working and not-working environment. Maybe do some cleanup in the libpath to make sure DI will pick u the correct version.
You could also open a case with support, they will be able to give you a faster response time and work with you to troubleshoot the issue.

Need Suggestion on DB2 HA Setup on AIX 6.1

Dear All,
We are configuring HA for PRD System having below configuration:
OS: AIX 6.1
Database: DB2 9.1 Fix pack 7
System: ERP 6.0 EHP4
What we have done so far:
We have installed DB & CI on node 1 (primary node) and ASCS & Dialog Instance on node 2 (secondary node). ASCS instance on node 2 and DB on node 1 is on movable resource group. CI on node 1 and Dialog Instance on node 2 is local. So, e.g. if there is failover on node 1 then DB will move on node 2 and Dialog Instance will take over service provided by CI.
Now my doubts are:
1) I have installed DB2 in resource group and nothing local. But If I am checking redbook for HA on DB2 then it is mentioned there that we should install db2 binaries local on both nodes. Is it mandatory because my understanding is that if whole db2 is moving (log, data and binaries) then it should start there ?
2) I am using the concept of service IP's to install this HA. When I installed CI and DB on node 1 then i used hostname associated with service ip of node 1. Same when i installed ASCS and Dialog instance then I used hostname associated with service IP of node 2. And Even If I am rebooting my node 1 then all resources are going to node 2 and I am also getting hostname and service IP of node 1 on node 2. Then I think I need not to change hostname of node 1 when resources are there on node 2. Am I right ?
3) Is it necessary to catalog database on node 2 ?
4) Am I need to change host entry in db2nodes.cfg when db will move on node 2 ? My understains is that I need not to change hostname in db2nodes.cfg as I am getting ip address and hostname of node 1 on node 2. Since IP are service ip's so the host name associates with them.
Please suggest.
Thanks
Sunny

No need to install binaries on node 2 if it is on movable resource group like in my case.
Database catalog is not required on other node.
Since only IP is moving but hostname is not moving. So need to change change host name in db2nodes.cfg file.
Thanks
Sunny

Strange error when starting tnslsnr on AIX machine

Hello!
I have the following system:
there are two nodes (say, node1 and node2) in HACMP cluster (OS is AIX 5.2). ORACLE runs on node2 and our software - on node1 (in normal state). Also there is an external storage, where ORACLE's and software's file systems are situated.
So, in normal state ORACLE runs on node2 and software - on node1. ORACLE's filesystems are mounted on node2 and software's filesystem - on node1.
There can be two more states of working system:
1. when node1 fails and all it's resources are acquired by node2 (filesystems and IP). In this state ORACLE and software are executed on node2.
2. when node2 fails and it's IP and filesystems are acquired by node1. ORACLE and software are executed on node1.
So, in failover state no.2 everything works ok. In failover state no.1 and in normal state i get an error when i try to run tnslsnr:
oracleuser$> lsnrctl start
LSNRCTL for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production on 26-SEP-2005 14:43:58
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /oracle/MFP/920_64/bin/tnslsnr: please wait...
TNSLSNR for IBM/AIX RISC System/6000: Version 9.2.0.6.0 - Production
System parameter file is /oracle/MFP/920_64/network/admin/listener.ora
Log messages written to /oracle/MFP/920_64/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=prdr3dbt)(PORT=1527)))
TNS-12545: Connect failed because target host or object does not exist
TNS-12560: TNS:protocol adapter error
TNS-00515: Connect failed because target host or object does not exist
IBM/AIX RISC System/6000 Error: 13: Permission denied
Listener failed to start. See the error message(s) above...
oracleuser$
When i edit listener.ora (replace "prdr3dbt" by corresponding IP-address) and try to start tnslsnr again, the startup procedure hangs and does not finish for a long time (it hangs until I press CONTROL-C key combination) and i get a huge amount of such error:
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
26-SEP-2005 15:17:50 * 12531
TNS-12531: TNS:cannot allocate memory
I am sure that there is nothing wrong with oracle's files, becouse they are on EXTERNAL storage and the system doesn't work only in two of three states (in one of states it works fine).

'TNS-12531: TNS:cannot allocate memory' may be misleading, it seems to be a permission problem (see also IBM/AIX RISC System/6000 Error: 13: Permission denied). A possible reason is:
Oracle (more specific the listener) is unable to read /etc/hosts, because of permission problems. So host resolution is not possible.

HA Installation of ERP EHP4 on AIX and DB2

Dear All,
I have to do a HA installation of ERP EHP4 system on AIX and DB2. I have followed the standard inst.guide from SAP but I want more information. Can anyone help me in understanding how to go about installing HA in detail. I would be very grateful if anyone can provide me a guide/document of what and how they have done. Can you pls explain me the steps.
I also have few questions
1. Shall i do a Central installation or distributed installation ( meaning CI, ASCS and DB in one server failover to other; CI,ASCS on one server and DB running on different server which in case of failure will move to other server)
2. I know that OS team will do the cluster configuration but is there any other software to be bought for an automatic switchover in case of failures?
3. Mainly, as a BASIS consultant what is our role in HA configuration? What file systems should be defined and nfs mounted?
Request you to take time and answer. Thanks in Advance.
Lastly, i hope this is the right forum. If not , please let me know.

Hi,
>
> 1. Shall i do a Central installation or distributed installation ( meaning CI, ASCS and DB in one server failover to other; CI,ASCS on one server and DB running on different server which in case of failure will move to other server)
>
I think you did not get basic of HA installation. Its neither central nor distributed installation. You need to install CI and Dialog Instance locally on 2 nodes. DB and ASCS instance on the disk that will move across 2 nodes.
> 2. I know that OS team will do the cluster configuration but is there any other software to be bought for an automatic switchover in case of failures?
>
OS team will do file system config so that file system having ASCS and DB should move across 2 nodes. And rest of the file system should be local.
After installation making cluster movement automatic both OS and SAP Basis guy have to work together.
> 3. Mainly, as a BASIS consultant what is our role in HA configuration? What file systems should be defined and nfs mounted?
>
I would say primary role in HA installation is of Basis guy. Because he is the person who will decide what approach will you take to install HA either active-active or active-passive. Its you on whom requirement OS guy will work.
Thanks
Sunny

Data Guard Broker and Cold Failover clusters

Hi,
I wanted to use Data Guard Broker to control primary/standby systems on AIX clusters but found that without Oracle clusterware it is not supported on failover of a database to another node (unless you drop and recreate the configuration which in my opinion is not support at all!).
The 11g documentation states that DG Broker offers support for single instance databases configured for HA using Oracle Clusterware and "cold failover clusters".
Does anyone know whether this support for cold failover clusters in 11g means "proper support" i.e the configuration detects that the hostname has changed and automatically renames it so it continues to work?, or is the support in 11g the same as that in 10g?.
Thanks,
Andy

Hi Jan,
We already use virtual hostnames.
When I set up the configuration the hostname for the databases default to the server name. The only way I know of changing this is to disable the configuration, then use the "edit database...set property" command but when I enable the configuration again it reverts back to its previous value.
regards,
Andy

How to patch Oracle 9i (9.2.0.1 to 9.2.0.6) in a HACMP environment (AIX 5.2

Hello forum users
I installed Oracle 9i (9.2.0.1) on AIX 5.2 ML7 in a HACMP environment.
Before installing Oracle I created users & groups via "smitty hacmp - Users & groups" so I have same users on each node.
On each node i installed Oracle on internal disk drives and i have an external drive for failover with my database files.
When I try to upgrade to Oracle 9.2.0.6 with Oracle Universal Installer I have a screen "Selected Node" with :
- my first server PRDWSS2 : Available
- my second server PRDWSS3 : Unreachable
I tried to stop HACMP on second server but i have the same message.
I'd like to upgrade on each node separately.
Is anyone know how to do that ?
Thanks for any help
Guillaume

Hi Laurent,
Thanks for your answer.
I have just Failover Cluster.
Do you first install Oracle on each server and then install HACMP or install HACMP and then Oracle ?
I cannot ignore messages because I have :
PRDWSS2 Available
PRDWSS3 Unreachable
Button "install" is unavailable ...
Do you know if i can force "Universal Installer" to only run on available node ?
It's very difficult to find ressources on HACMP/AIX 5.2 with Oracle 9i.
Guillaume

BODS and Oracle RAC

Do we know of any problems with BODS and Oracle Real Application Clusters architecture? For example, a RAC TNS entry would specify one service name but multiple hosts for load balancing and failover. In BODS the connections are specified in many places (web console, datastores, job server). As far as I remember in some of those places we do have to enter the host name. Would this disqualify BODS from benefiting from RAC or would it (even worse) cause problems? Any official note by SAP on BODS and Oracle RAC?
Thanks.

Hi Mahir,
As far as I know it's only the web console that requires the hostname, however I am using DS XI 3.1 and when selecting database type Oracle in the web console there is a checkbox for 'Oracle RAC'. If you check this box then you do not require to enter the hostname.

Failover - How to achieve a transparent failover using SQLPlus

AIX 5.3 Oracle Clusterware 10.2.0.4.0 Oracle Enterprise Edition 10.2.0.4.0
This is the behavior I see from an Oracle Client session which is to be expected if I read RAC: Frequently Asked Questions [ID 220970.1] see below
(1) SQLPlus session connected to NodeA
(2) NodeA - Clusterware services stopped
(3) NodeA-vip has failed over to Node B
(4) SQLPlus session receives an error
(5) SQLPlus establish new connection to NodeA-vip
My question is how is a transparent SQLPLus session failover achieved as illustrated in [ID 339107.1] see below
*** Dedicated Connections to a Migrated VIP Can Lose their Connection after the VIP is Switched Back [ID 339107.1] ***
SQL> select instance_name from v$instance;
INSTANCE_NAME
rac11g1
$ crsctl stop crs
SQL> /
INSTANCE_NAME
rac11g2
RAC: Frequently Asked Questions [ID 220970.1]
*** Why do we have a Virtual IP (VIP) in Oracle RAC 10g or 11g? Why does it just return a dead connection when its primary node fails? ***
The goal is application availability.
When a node fails, the VIP associated with it is automatically failed over to some other node. When this occurs, the following things happen.
(1) VIP detects public network failure which generates a FAN event.
(2) the new node re-arps the world indicating a new MAC address for the IP.
(3) connected clients subscribing to FAN immediately receive ORA-3113 error or equivalent. Those not subscribing to FAN will eventually time out.
(4) New connection requests rapidly traverse the tnsnames.ora address list skipping over the dead nodes, instead of having to wait on TCP-IP timeouts
Without using VIPs or FAN, clients connected to a node that died will often wait for a TCP timeout period (which can be up to 10 min) before getting an error.
As a result, you don't really have a good HA solution without using VIPs and FAN. The easiest way to use FAN is to use an integrated client with Fast Connection Failover (FCF) such as JDBC, OCI, or ODP.NET.
*** What do the VIP resources do once they detect a node has failed/gone down? Are the VIPs automatically acquired, and published, or is manual intervention required? Are VIPs mandatory? ***
With Oracle RAC 10g or higher, each node requires a VIP. With Oracle RAC 11g Release 2, 3 additional SCAN vips are required for the cluster. When a node fails, the VIP associated with the failed node is automatically failed over to one of the other nodes in the cluster. When this occurs, two things happen:
1. The new node re-arps the world indicating a new MAC address for this IP address. For directly connected clients, this usually causes them to see errors on their connections to the old address;
2. Subsequent packets sent to the VIP go to the new node, which will send error RST packets back to the clients. This results in the clients getting errors immediately.
In the case of existing SQL conenctions, errors will typically be in the form of ORA-3113 errors, while a new connection using an address list will select the next entry in the list. Without using VIPs, clients connected to a node that died will often wait for a TCP/IP timeout period before getting an error. This can be as long as 10 minutes or more. As a result, you don't really have a good HA solution without using VIPs.
With Oracle RAC 11g Release 2, you can delegate the management of the VIPs to the cluster. If you do this, the Grid Naming Service (part of the Oracle Clusterware) will automatically allocated and manage all VIPs in the cluster. This requires a DHCP service on the public network.
Thank you
Steve

Answer = Follow MetaLink 377100.1

Service registration 11gr2 RAC AIX

Hi Gurus,
I have created an database service called "MTRXUATR" with srvctl as both nodes as prefered as show below ,this service got registered on both nodes (mvx20b) but only instance 1 is providing the service and not by the other instance .where logically should be provided by both instances.When i shutdown the instance 1(node 1) and tried connecting through sqlplus using this services, started getting error "ORA-12514" where i should have been redirected to instance 2(connect time failover) as i'm using scan name,correct?
Why is it that the service is not providing by both instances?is it some configuration issue that i missed?Services should be registered with the local listeners or SCAN listeners?
Node 1:
Code: Select all
mvx20b:/u01/app/omvmxu1/product/11.2.0/dbhome_1/racg>srvctl config service -d mvmxu2
Service name: mtrxuatr
Service is enabled
Server pool: mvmxu2_mtrxuatr
Cardinality: 2
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: true
Failover type: SELECT
Failover method: BASIC
TAF failover retries: 180
TAF failover delay: 1
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Preferred instances: mvmxu21,mvmxu22
Available instances:
mvx20b:/home/gmvmxu1>lsntrctl services
ksh: lsntrctl: not found
mvx20b:/home/gmvmxu1>lsnrctl services
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 27-OCT-2010 09:58:02
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
Services Summary...
Service "+ASM1" has 1 instance(s).
Instance "+ASM1", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:52549 refused:0
LOCAL SERVER
Service "matrxuat" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:24 refused:0 state:ready
LOCAL SERVER
Service "mtrxuatr" has 1 instance(s).
Instance "mvmxu21", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:4 refused:0 state:ready
LOCAL SERVER
Service "mvmxu1" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:24 refused:0 state:ready
LOCAL SERVER
Service "mvmxu1XDB" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx20b.us.hp.com, pid: 1687592>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx20b.us.hp.com)(PORT=50696))
Service "mvmxu2" has 1 instance(s).
Instance "mvmxu21", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:4 refused:0 state:ready
LOCAL SERVER
Service "mvmxu2XDB" has 1 instance(s).
Instance "mvmxu21", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx20b.us.hp.com, pid: 1667116>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx20b.us.hp.com)(PORT=52509))
The command completed successfully
mvx20b:/home/gmvmxu1>srvctl config service -d mvmxu2
Service name: mtrxuatr
Service is enabled
Server pool: mvmxu2_mtrxuatr
Cardinality: 2
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: true
Failover type: SELECT
Failover method: BASIC
TAF failover retries: 180
TAF failover delay: 1
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: NONE
Preferred instances: mvmxu21,mvmxu22
Available instances:
mvx20b:/home/gmvmxu1>srvctl status database -d mvmxu2
Instance mvmxu21 is running on node mvx20b
Instance mvmxu22 is running on node mvx21b
mvx20b:/home/gmvmxu1>srvctl status service -d mvmxu2
Service mtrxuatr is running on instance(s) mvmxu21
mvx20b:/home/gmvmxu1>srvctl stop instance -d mvmxu2 -i mvmxu21
mvx20b:/home/gmvmxu1>srvctl status database -d mvmxu2
Instance mvmxu21 is not running on node mvx20b
Instance mvmxu22 is running on node mvx21b
mvx20b:/home/gmvmxu1>srvctl status service -d mvmxu2
Service mtrxuatr is not running.
mvx20b:/home/gmvmxu1>sqlplus system@mtrxuatr
SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 27 10:27:27 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
Enter user-name:
mvx20b:/home/gmvmxu1>tnsping mtrxuatr
TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 27-OCT-2010 10:28:51
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/11.2.0/grid/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = mvxuatscan.us.hp.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = MTRXUATR)))
OK (10 msec)
mvx20b:/home/gmvmxu1>nslookup mvxuatscan.us.hp.com
Server: einstein.us.hp.com
Address: 10.35.15.20
Name: mvxuatscan.us.hp.com
Addresses: 10.35.33.170, 10.35.33.172, 10.35.33.171
mvx20b:/home/gmvmxu1>host mvxuatscan.us.hp.com
mvxuatscan.us.hp.com is 10.35.33.171
mvx20b:/home/gmvmxu1>host mvxuatscan.us.hp.com
mvxuatscan.us.hp.com is 10.35.33.171
mvx20b:/home/gmvmxu1>ping mvxuatscan.us.hp.com
PING mvxuatscan.us.hp.com (10.35.33.172): 56 data bytes
64 bytes from 10.35.33.172: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 10.35.33.172: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 10.35.33.172: icmp_seq=2 ttl=255 time=0 ms
64 bytes from 10.35.33.172: icmp_seq=3 ttl=255 time=0 ms
--- mvxuatscan.us.hp.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
mvx20b:/home/gmvmxu1>ping mvxuatscan.us.hp.com
PING mvxuatscan.us.hp.com (10.35.33.171): 56 data bytes
64 bytes from 10.35.33.171: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 10.35.33.171: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 10.35.33.171: icmp_seq=2 ttl=255 time=0 ms
--- mvxuatscan.us.hp.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
mvx20b:/home/gmvmxu1>ping mvxuatscan.us.hp.com
PING mvxuatscan.us.hp.com (10.35.33.170): 56 data bytes
64 bytes from 10.35.33.170: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 10.35.33.170: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 10.35.33.170: icmp_seq=2 ttl=255 time=0 ms
--- mvxuatscan.us.hp.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0/0/0 ms
mvx20b:/home/gmvmxu1>lsnrctl services
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 27-OCT-2010 10:34:16
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
Services Summary...
Service "+ASM1" has 1 instance(s).
Instance "+ASM1", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:52549 refused:0
LOCAL SERVER
Service "matrxuat" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:24 refused:0 state:ready
LOCAL SERVER
Service "mvmxu1" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:24 refused:0 state:ready
LOCAL SERVER
Service "mvmxu1XDB" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx20b.us.hp.com, pid: 1687592>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx20b.us.hp.com)(PORT=50696))
The command completed successfully
mvx20b:/home/gmvmxu1>srvctl start instance -d mvmxu2 -i mvmxu21
mvx20b:/home/gmvmxu1>srvctl status service -d mvmxu2
Service mtrxuatr is running on instance(s) mvmxu21
mvx20b:/home/gmvmxu1>
Node 2:
Code: Select all
mvx21b:/home/gmvmxu1>lsnrctl services
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 27-OCT-2010 10:38:52
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:3973 refused:0 state:ready
LOCAL SERVER
Service "+ASM2" has 1 instance(s).
Instance "+ASM2", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:9 refused:0
LOCAL SERVER
Service "mvmxu1" has 1 instance(s).
Instance "mvmxu12", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:951 refused:0 state:ready
LOCAL SERVER
Service "mvmxu1XDB" has 1 instance(s).
Instance "mvmxu12", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx21b.us.hp.com, pid: 1552450>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx21b.us.hp.com)(PORT=34128))
Service "mvmxu2" has 1 instance(s).
Instance "mvmxu22", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "mvmxu2XDB" has 1 instance(s).
Instance "mvmxu22", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx21b.us.hp.com, pid: 2064564>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx21b.us.hp.com)(PORT=64601))
The command completed successfully
mvx21b:/home/gmvmxu1>ps -ef |grep lsnr
gmvmxu1 1695876 1 0 Sep 13 - 20:40 /u01/app/11.2.0/grid/bin/tnslsnr LISTENER -inherit
gmvmxu1 1732752 1 0 Sep 13 - 5:52 /u01/app/11.2.0/grid/bin/tnslsnr LISTENER_SCAN1 -inherit
gmvmxu1 1855706 2195662 0 10:39:13 pts/0 0:00 grep lsnr
mvx21b:/home/gmvmxu1>lsnrctl services LISTENER_SCAN1
LSNRCTL for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 27-OCT-2010 10:39:25
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))
Services Summary...
Service "+ASM" has 2 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:blocked
REMOTE SERVER
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mvx21b-vip.us.hp.com)(PORT=1521)))
Instance "+ASM2", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mvx21b-vip.us.hp.com)(PORT=1521)))
Service "matrxuat" has 1 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:2 refused:0 state:ready
REMOTE SERVER
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mvx20b-vip.us.hp.com)(PORT=1521)))
Service "mvmxu1" has 2 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:2 refused:0 state:ready
REMOTE SERVER
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mvx20b-vip.us.hp.com)(PORT=1521)))
Instance "mvmxu12", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=mvx21b.us.hp.com)(PORT=1521))
Service "mvmxu1XDB" has 2 instance(s).
Instance "mvmxu11", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx20b.us.hp.com, pid: 1687592>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx20b.us.hp.com)(PORT=50696))
Instance "mvmxu12", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx21b.us.hp.com, pid: 1552450>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx21b.us.hp.com)(PORT=34128))
Service "mvmxu2" has 1 instance(s).
Instance "mvmxu22", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
REMOTE SERVER
(ADDRESS=(PROTOCOL=TCP)(HOST=mvx21b.us.hp.com)(PORT=1521))
Service "mvmxu2XDB" has 1 instance(s).
Instance "mvmxu22", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: mvx21b.us.hp.com, pid: 2064564>
(ADDRESS=(PROTOCOL=tcp)(HOST=mvx21b.us.hp.com)(PORT=64601))
The command completed successfully
mvx21b:/home/gmvmxu1>
Instance 1 parameter:
Code: Select all
SQL> show parameter local_
NAME TYPE VALUE
local_listener string (DESCRIPTION=(ADDRESS_LIST=(AD
DRESS=(PROTOCOL=TCP)(HOST=mvx2
0b-vip.us.hp.com)(PORT=1521)
log_archive_local_first boolean TRUE
SQL> show parameter remote_
NAME TYPE VALUE
remote_dependencies_mode string TIMESTAMP
remote_listener string mvxuatscan:1521
Instance 2 parameter:
Code: Select all
SQL> show parameter local_
NAME TYPE VALUE
local_listener string
log_archive_local_first boolean TRUE
SQL> show parameter remote_
NAME TYPE VALUE
remote_dependencies_mode string TIMESTAMP
remote_listener string mvxuatscan:1521
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
result_cache_remote_expiration integer 0
Edited by: user9097501 on Oct 27, 2010 12:21 PM

I tried starting service on instance 2 but getting the following error...
mvx21b:/home/omvmxu1>srvctl status service -d mvmxu1
Service matrxuat is running on instance(s) mvmxu11
mvx21b:/home/omvmxu1>srvctl start service -d mvmxu1 -s matrxuat -i mvmxu12
PRCR-1064 : Failed to start resource ora.mvmxu1.matrxuat.svc on node mvx21b
CRS-2674: Start of 'ora.mvmxu1.matrxuat.svc' on 'mvx21b' failed
CRS-2678: 'ora.mvmxu1.matrxuat.svc' on 'mvx21b' has experienced an unrecoverable failure
CRS-0267: Human intervention required to resume its availability.
When i say 'srvctl start service -d mvmxu1' should not it bring up services on both nodes won which it is configured as prefered?
Edited by: user9097501 on Oct 28, 2010 6:44 AM

SFSB Instance Sharing across multiple servers/SFSB failover practices

Hello:
My question is in two parts. I have spent a great deal of time searching the forums without a satisfactory answer, so I thought I'd post my question directly.
1) I have two clients that can potentially talk to two different servers, but they both need to interact with the same instance of a SFSB. For example, the first client calls the SFSB and causes it to save some state in its instance variables. The second client connects to a different server (because of a "network dispatcher" load-balancing architecture), but needs to use the same instance of the SFSB that the first client initialized. The two clients will not always talk to different servers, but the possibility exists that they might.
2) What is the proper design pattern for "fail-over" for a SFSB. For example, a client establishes a session, tickles a SFSB and causes its instance variables to contain state, and then WHAMO the application server crashes or becomes unavailable for some reason. We have in place a mechanism to reroute further client request to a second application server, but currently it is a problem because even though the failover is transparent to the client, the backup server creates a new instance of the SFSB and therefore it has none of the previous state information.
I'm thinking that the answer to one of these questions will be the answer to the other.
A little bit of background: this is not a theoretical application. We are building 250+ cars per day, ramping up quickly to 500-650 cars per day. I'm hoping I can solve this problem from an architectural standpoint, without having to modify each individual bean, because we have on the order of 200-300 SFSBs that would have to be changed--not a pretty thing in a production critical application. We have two AIX servers, but one of them is currenlty just a hot standby because we cannot run both of them at the same time because of problem 1) from above. We'd like to be able to run both servers at the same time for load-balancing purposes. Furthermore, if one box fails then all SFSB data will be lost because of the problem is mentioned problem 2) above.
(As a point of clarification, and only because I don't know if this affects any possible suggestions, but the clients do not use remote references to the EJBs. They simply pass "data containers" via HTTP to the server, and this data is passed to the various EJBs and returned back to the client via HTTP Response and in some cases TCP/IP. In either case, we do not use "remote object" references in the most typical sense. The servlet maintains the references to the EJBs.)
I've read things about "session clustering" but have not pinned down the subject. I have the "Core J2EE Patterns" book on order.
Any suggestions or pointers to reading materials would be greatly, greatly appreciated. I also welcome the "what you should have done" variety suggestions.
Thanks!
Regards,
Doug Wilkerson

Doug,
Here are my thoughts, I hope they help.
I don't think there is a possibility to have two different client (different sessions) talk to one and the same SFSB. A SFSB is specific to a users session and cannot be shared.
The way I would tackle this problem is probably by using SLSB which might access either an entity bean or the DB directly. This way, you might cause DB overhead, but you can share the data between clustered servers and the users will work with the correct data.
About the second question, I don't really now a pattern to provide fail-over for SFSB. To my opinion that is the weakest side of SFSB (beside all the load-balancing that needs to take place).
Hope this helps.

HACMP Clustering Script for SAP ECC 6.0 (SR1) - Automatic Failover

Hello,
I have installed the SAP ECC 6.0 (SR1) under AIX 5.3 / DB2 V8 FP12 with HACMP Clustering environment. Manual Failover is working fine. Central System has been installed in share drive with Virtual IP and Virtual name inNode A. Dialog Instance is loaded locally in Node B. I want to get HACMP Clustering script(automatic failover script) for Automation. Please help me if you have. It is single package clustering. If Node A fails, Node B will take care ( Central System and Dialog instance will run in Node B)
Thanks
Gautam Poddar

this post is duplicated at Upgrade to ERP 2005/ECC 6.0 from R/3 4.72/Basis 640 on Z/OS 1.4 DB2 8.1

Failover in BODI 11.7.3 AIX

Similar Messages

Maybe you are looking for