Create directory on a two-node Oracle server cluster

Hi,
How can I create directory on a two-node Oracle server cluster (2 identical servers running the same Oracle database instances with shared disks)? Both of them run Windows 2008.
I know this works for Oracle running in a single server. How about in failover cluster environment?
CREATE OR REPLACE DIRECTORY g_vid_lib AS 'X:\video\library\g_rated';
Thanks.
Andy

Using 11.2.0.? Using ASM? use ACFS - it is a SHARED file system.
http://docs.oracle.com/cd/E16338_01/server.112/e10500/asmfilesystem.htm
create [big empty disk group]
create ACFS volume {container file that lives in that diskgroup]
create ACFS file system
mount the file system.
Now, all nodes in the cluster can access that shared device at the OS level just as if it were any other device.

Similar Messages

[b]Migrating the DB-Tier (DB and CM) to Two node non RAC cluster[/b]

Hi,
The current set-up of our E-business suite is a two node install:-
The DB Tier (Database and Concurrent Manager) on one node
The Apps Tier (Forms /Web Server) on another node.
For the HA solution (NON ORACLE RAC) we are planning to:-
Move the DB Tier (Database and Concurrent Manager) to a three node hardware sun cluster managed by veritas cluster manager (NOT ORACLE RAC). We need to know will the Database Tier (Database and Concurrent Manager) work on Hardware cluster node and will it support COLD FAILOVER from one Node to another. We know the database on its own would be fine with a cold failover because we have tested the database cold failover on the three node cluster for non E-business suite database. But here we have the added thing of the Concurrent manger sitting on the node along with the Database on the DB Tier.
The Apps Tier (Forms / Web server) will be put on a separate set of server using Load balances etc.
Has anybody implemented similar HA set-up and will this planned set-up work or are there any issues with this.
Any help / info would be appreciated.
Thanks

Hi,
Yes, you can do the cold failover the database and all the 11i services also.
1. In the concurrent manager service
== when you failover the concurrent manager do the following things before failover.
create the listener/tnsnames files which includes the new hostname and keep it with the veritas failover service. i mean, when you failover, these files should replace the existing files, before the existing files should backedup. and create a script to change the hostname,logfile_hostname,outfile_hostname in fnd_concurent_processes table.
add the nodes in the install->nodes navigation
do the failover manually and check the listener files are properly pinging using tnsping. and start the concurrent manager.
so tatally, you have to prepare two sql scripts
one for change the hostname from node b to node a
one for node a to node b.
and 2 listener + 2 tnsnames files which contains the seperate hostname accordingly.
use the adcmctl.sh top stop and start
finally, create a shell script to kill the sysmgr for the current managers when the manager takes long time to shutdown. before run the kill script, wait for 5 mts atleast.
I done the same scenario many times, with veritas failover service with 2 sun v880 servers.
regards,
Pandian

No communication between the two nodes in weblogic cluster

Hi All,
We have installed weblogic cluster in our environment(LINUX 64-Redhat.5).On one node admin server ,managed server1,on second node we have managed server2.When we try to deploy application on one node it is not getting reflected in othe node.We have ran datagram test to check communication between 2 node.
Here we observed that listener and pulisher are picking wrong IPs not the server Ips.
can any one explain why and what is the problem.
thanks,
sudheer.

Hi Sudheer,
While performing the datagram test you mention the ports and ip so I am not sure how they are picking wrong ip and port. Follow the instructions to perform the test http://coherence.oracle.com/display/COH35UG/Performing+a+Datagram+Test+for+Network+Performance
Re the deployments, you need to ensure that multicast is enabled in your environment and both your managed server are in the same subnet otherwise you need to specify WKA for unicast communication. I am assuming that you are building SOA infrastructure as it internally uses Coherence for deploying applications and you can follow the instructions http://download.oracle.com/docs/cd/E15523_01/core.1111/e12036/extend_soa.htm#CHDEAFJH else use the intructions as mentioned here http://download.oracle.com/docs/cd/E17904_01/web.1111/e13709/features.htm
Hope this helps!
Cheers,
NJ

Can anyone help me?Creating the shadow copies in the file server cluster ,there are some errors occured, OS version is WSS 2012

I construct a failover cluster(file server,AP module) for sharing files by WSS 2012,and I want to use the shadow copies to backup my data,but when making a shadow copies on the volume which is added to the cluster(not the CSV,just add
it to the cluster and use it to share files,it plays the role of file server),there are some errors occured, these errors result in the shadow copies failed,error likes the following pictures:
1: the disk F is added to the cluster,first I make the shadow copies by click the right key of mouse on the disk F,and chouse the configeration shadow copies,and click the settings, then click the schedule , and I wait just a few seconds, the error is appeared,like
this picture 1, the wait operation timed out,and then ,
I click the schedule button once again,a different error occured,like the following picture," the object already exists",if i don't set the schedule at first ,use the default shedule,and click the enable button also the same error must
accure
but the only diffrence is that, a shadow copy time point is created, also ,you can make the shadow copies by click " create now", that is creating the shadow copies manually. Although it can succesfully make the shadow copies, but when I select
a time point to revert, error occured, "A volume that contains operating system files or resides on a cluster shared disk cannot be reverted"
In a word,all the errors above make the shadow copies by schedulling failed,except making the shadow copies manually,but what makes me confused is that I have ever maked the shadow copies succesfully by schedul a policy,I don't know what makes it succesful,
it's small probability, most of time ,it's failed.No matter what kind of situation, revert must be failed.
I'm sorry for my pool english , it's the first time for me getting help in forum by english ,I don't know if I descripe my question clearly, also ,other method like the link
http://technet.microsoft.com/en-us/library/cc784118(v=ws.10).aspx I have tried,but the same errors occured.Can anyone tell me How can I make the shadow copies in File Server
cluster（AP module）？And I make a mistake in operating？ Looking forward for your reply.Thanks!

Hi,
Please check the following 2 places:
HKEY_LOCAL_MACHINE\Cluster\Tasks
C:\Windows\System32\Tasks
First please compare permission settings of the folder C:\Windows\System32\Tasks with a working computer. Correct permission settings if anything wrong. Specifically, confirm you current account do have permission on this folder.
As it said "object already exists", find the schedules you created before, backup and delete all these schedules in both registry key and folder.
Then test to create a new schedule to see if issue still exists.
Meanwhile what kind of storage device you are using? The issue could occur on specific storage device, so test to enable shadow copy on a local disk to see if that will work.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]
Thank you for you reply.On the local volume,all of these errors will not occur, but the volume in the file server cluser.There is no value in HKEY_LOCAL_MACHINE\Cluster\Tasks. On local volume, everything goes well about the shadow copy, so I do not
think something is wrong about the permission settings of the folder C:\Windows\System32\Tasks.Storage device is a SAN,we use RAID6 and provide the LUNs to the NAS engine, and the make the volume on these LUNs, Is Angthing wrong? Hope for you
reply~~

Database control in a two node oracle fail safe cluster

os windows server 2003 r2
db 10.2.0.4
ofs 3.4.1
i've configured db control in the following
D:\oracle\product\10.2.0\db_1\BIN>emca -config dbcontrol db -repos recreate -cluster_name name_of_the_cluster
is this right?
next question
the -cluster flag and the -EM_NODE / -EM_SID_LIST parameters in the emca are only for rac?
with my configuration i can't login to my database over dbcontrol
Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor The Connection descriptor used by the client was: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1.blah)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ABBA)))

How to Configure the 10.2 DB Control in a Failsafe Environment
ID: 452305.1
HOWTO: PUBLISHED 17-OCT-2008
In this Document
   Goal
   Solution
   References
Applies to:
Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
Information in this document applies to any platform.
Goal
The goal of the document is to provide the steps to configure the DB Console in an Oracle Failsafe environment.
Please note that the solution offered in this document is not certified by Oracle. It's only provided as a workaround for customers who wish to use this setup for the Database Control Console in a failsafe environment. Support for the procedure outlined in this document will be provided on a 'best efforts' approach.
As an alternative to this approach you can use Grid Control Agents to monitor a database in a failsafe environment. For more details please see:
Note 396659.1 How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
We assume the following:
- the database binaries are installed on each node on the local disk
- you already have a failsafe group with the database, the listener, disk resource, and virtual
ip/hostname
Note: This is specific for Windows environments using Oracle Failsafe. For setting up the DB Console in Active/Passive clusters on UNIX please use the following note instead:
Note 362524.1 Configure DB Control 10.2 for use in Active/Passive High Availability Environments
Solution
1. Drop the DB Control repository and configuration files on the active node:
<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
2. Recreate the DB Control using the virtual hostname:
- in a command window do the following:
set oracle_sid=<your_sid>
set oracle_home=<your_oracle_home>
set oracle_hostname=<virtual_hostname>
cd %oracle_home%\bin
emca -config dbcontrol db -repos create
-- make sure that the virtual host name was picked up by emca (it will display a summary screen
before continuing)
3. Verify that the DB Console works fine and can be accessed using the virtual host name in the URL
4. Stop the DB Console
5. Create a directory path on the group disk resource similar to your oracle home path on the local disk.
For example:
If the oracle home on the local disk is C:\oracle\product\10.2.0\db_1 and the shared disk is D:
then create the following path: D:\oracle\product\10.2.0\db_1
Copy C:\oracle\product\10.2.0\db_1\<hostname_sid> and
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
to D:\oracle\product\10.2.0\db_1\<hostname_sid> and respectively
D:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
Remember to change the values enclosed in <> with those in your environment.
6. Delete the following directories from the local disk
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
7. Create NTFS junction points from the local disk to the shared disk (these work like symbolic
links on UNIX) . It is your responsibility to create these.
You can find a brief guide as well as some tools that will help you create them at:
http://en.wikipedia.org/wiki/NTFS_junction_point
http://www.microsoft.com/technet ... dDisk/Junction.mspx
Important: Please note that this functionality is not certified nor supported by Oracle. Make sure you understand the
implications. Especially don't delete the junction points from Windows Explorer !!
In the end you should have the junction points on the local disk (with the same names as the
original directories) that would point to the directories you copied on the shared disk.
8. Start the DB Console service and verify that everything is still working fine.
9. Stop the DB Console service.
10. Move the Fail Safe group to the 2nd node.
11. Once the database is started, create the DB Console configuration files on the 2nd node:
<ORACLE_HOME>/bin/emca -config dbcontrol db
12. Stop the DB Console
13. Delete the created configuration files from the local disk:
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
14. Create junction points from the local disk to the directories already located on the shared
disk.
15. Start the DB Console service and verify that is working fine.
16. Add the DB Console service as a resource to the fail safe group and put dependencies on the
database and listener services.
17. Perform a fail over and see if everything works fine.
References
Note 298238.1 - Oracle10g Grid Control with Oracle Fail Safe
Note 362524.1 - Configure DB Control 10.2, 11g for use in Active/Passive High Availability Environments
Note 396659.1 - How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
Keywords
EMCA ; DB~CONTROL ; FAILSAFE ; DBCONTROL ; ENTERPRISE~MANAGER ;

Patch applying on Two node application server(load balancing)

Hi,
We have Two aplication servers with load balancing with PCP.
I want to know about applying patches order.
First patch has to be applied on primary applicaton node.
and next it has to be applied on secodary application node.
Please confirm.
Regards,
maleem

maleem wrote:
Hi Mapps,
We do not have shared aplicaton Tier. I think in that case we have to apply patches on both applicaton nodes.
am i right? please correct me if i am wrong.
Regards,
maleem
Correct.
Thanks,
Hussein

System error 1460 has occurred (0x000005b4). when trying to create two-node cluster in R2

I'm trying to create a brand new two node Windows 2008 R2 Enterprise 64bit cluster. When I try with the GUI I get the following:
An error occurred while creating the cluster.
An error occurred creating cluster 'printcluster'.
This operation returned because the timeout period expired
When I try via command prompt using the following command:
cluster /cluster:PrintServices /create /nodes:"node1 node2" /ipaddr:10.9.11.194/255.255.255.0
I get the following:
4% Initializing Cluster PrintServices.
9% Validating cluster state on node <node1>.
13% Searching the domain for computer object PrintServices
18% Creating a new computer object for PrintServices in the domain
22% Configuring computer object PrintServices as cluster name object
27% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node1>.
31% Validating installation of the Cluster Disk Driver on node <node1>.
36% Configuring Cluster Service on node <node1>.
40% Validating installation of the Microsoft Failover Cluster Virtual Adapter on node <node2>.
45% Validating installation of the Cluster Disk Driver on node <node2>.
50% Configuring Cluster Service on node <node2>.
54% Starting Cluster Service on node <node1>.
54% Starting Cluster Service on node <node2>.
59% Forming cluster PrintServices.This phase has failed for Cluster object 'PrintServices' with an error status of 1460 (0x000005B4).
Cleaning up <node1>.
Cleaning up <node2>.
Cleaning up PrintServices.
When I run a Cluster validation, I get 100% Green, no errors.
My disks are SAN Attached.
I have other Windows 2008 non-R2 clusters that never had this problem... Any ideas?
-PaulPaul S

Hi Paul,
I suggest trying the following steps to troubleshoot this issue:
1. Open Registry Editor.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
3. Under this subkey, find the subkey that holds a DriverDesc string value entry whose value is "Microsoft Failover Cluster Virtual Adapter."
4. Under the subkey that you found in step 3, add the following string value registry entry:
Name: DatalinkAddress
Value data: 02-AA-BB-CC-DD-01
5. Restart the computer.
6. Repeat step 1 through step 5 on other computers on which you experience this problem. When you do this on other computers, replace the value data of the registry with different values in order to set a unique value for each node. For example, set the value on the second node to 02-AA-BB-CC-DD-02, and set value on the third node to 02-AA-BB-CC-DD-03. If you notice this behavior on distinct clusters, make sure that you use an address for each node that is unique across all clusters.
7. On each computer that you want to make a cluster node, use the Server Manager console to remove the Failover Clustering feature.
8. Restart each computer from which you have removed the Failover Clustering feature.
9. Add the Failover Clustering feature on all these computers again.
10. Run cluster validation against these computers.
11. Try creating a cluster.
If the issue persists, please let me know what errors are logged in Event Logs.
Tim Quan - MSFT

Cloned two vm cluster nodes from development cluster to act as template to create production cluster

Morning,
There was so much done to setup the development cluster, I thought it would be easy to have the two nodes in the cluster cloned. To my surprise, the development cluster was up and happily running on the new vm servers. Stopping resources verifies
it is stopping and starting resources on the original cluster. I am not sure how to safely have the two new servers not manage the development cluster and create a new production cluster on them.
I am hesitant to destroy the cluster as I suspect it will destroy the real development cluster. How do I do this? How do I delete the windows cluster software and re-install without affecting the development cluster?
Note that I tried to create a new cluster in the failover cluster manager and specify the new vm cluster servers, but it says they are part of a cluster already. I do not see them listed as nodes. I am not sure how to see what cluster it thinks
the new servers are part of or how to not make them part of the development cluster. That might be the path to my solution.

This actually has worked out okay. I found these steps and did them on both of the nodes that were claiming to be in a cluster already:
powershell
Import-Module FailoverClusters;
clear-clusternode

Step by Step change of IP's in Two node Cluster WIndows 2003 server

Hi,
I am looking for step by step information for changing IP's in Two Node windows 2003 cluster setup. Information on KB on technet as well on windows site, not covering step by step details. If anyone had experience of change IP's in WIndows 2003 cluster environment,
Please share, it will be great help.
Regards,
Avnish

If you have done the setup correctly and have two separate networks, changing IPs is pretty straightforward.
Make sure both networks can carry cluster communications.
Change the NICs on ONE network (usually the private network) only.
Validate the nodes can communicate over that network.
Change the NICs on the PUBLIC network.
Change the clustered IP addresses. Note that some clustered services may require a restart to accept the new IP address.
Geoff N. Hiten Architect Microsoft SQL Server MVP

ASM instances on 2 node Oracle RAC 10g r2 on Red Hat 4 u1

Hi all
I'm experiencing a problem in configuring diskgroups under +ASM instances on a two node Oracle RAC.
I followed the official guide and also official documents from metalink site, but i'm stuck with the visibility of asm disks.
I created fake disks on nfs with Netapp certified storage binding them to block device with the usual trick "losetup /dev/loopX /nfs/disk1 " ,
run "oracleasm createdisk DISKX /dev/loopX" on one node and
"oracleasm scandisks" on the other one.
With "oracleasm listdisks" i can see the disks at OS level in both nodes , but , when i try to create and mount diskgroup in the ASM instances , on the instance on which i create the diskgroup all is well, but the other one doesn't see the disks at all, and diskgroup mount fails with :
ERROR: no PST quorum in group 1: required 2, found 0
Tue Sep 20 16:22:32 2005
NOTE: cache dismounting group 1/0x6F88595E (DG1)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup DG1 was not mounted
any help would be appreciated
thanks a lot.
Antonello

I'm having this same problem. Did you ever find a solution?

Two nodes Cluster problems

hello experts, I has the following problem:
I has a two nodes oracle RAC(version: 11.1.0.7 and OS: Enterprise Suse 10). Yesterday I had to delete one node of the cluster configuration and after I re-install it again I added it to the cluster configuration. Everything was ok but now there are two problems:
1- When I down the new instance using the srvctl utility the instance goes down normaly but when I try to start it one message appears notice me that the instance_number does not configured. I think it is very rare because when I start it using the sqlplus the instance goes up without problems.
Could you please give a suggestion about that problem?
2-Normally, before the delete and add the node, the cluster startup by itself when I restart the server but now it does not, so I have to execute crsctl start crs and this is not optimal.
Again, Do you have any suggestion?
Really there is not big problem because now I have a two nodes RAC again but I would like to solve this remain problems.
Thank in advance, I hope you can help me.

Hello thank you for your answer:
ASM show parameter instance_number 1
BD show parameter instance_number 1
I can found one difference(I think it is the only one) between the ora.bdm.bdm1.inst resource and the ora.bdm.bdm2.inst resource. That is, the ora.bdm.bdm2.inst has as required resource ora.bls2.ASM2.asm while ora.bdm.bdm1.inst does not has.
crs_stat -p
NAME=ora.bdm.bdm1.inst
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for Instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=300
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bdm.bdm2.inst
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for Instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls2.ASM2.asm
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=300
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bdm.db
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for the Database
FAILOVER_DELAY=0
FAILURE_INTERVAL=60
FAILURE_THRESHOLD=1
HOSTING_MEMBERS=
OPTIONAL_RESOURCES=
PLACEMENT=balanced
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.ASM1.asm
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for ASM instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=180
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysasm
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=mount
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.LISTENER_BLS1.lsnr
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for listener on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls1.vip
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.gsd
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for GSD on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.ons
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=CRS application for ONS on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=3
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls1.vip
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=15
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls1
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=bond0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.128
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=90.40.100.115
NAME=ora.bls2.ASM2.asm
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=300
DESCRIPTION=CRS application for ASM instance
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=900
STOP_TIMEOUT=180
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysasm
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=mount
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.LISTENER_BLS2.lsnr
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/db/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for listener on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=ora.bls2.vip
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.gsd
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=1
CHECK_INTERVAL=600
DESCRIPTION=CRS application for GSD on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=5
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.ons
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=0
AUTO_START=always
CHECK_INTERVAL=60
DESCRIPTION=CRS application for ONS on node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=restricted
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=3
SCRIPT_TIMEOUT=600
START_TIMEOUT=600
STOP_TIMEOUT=600
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=
NAME=ora.bls2.vip
TYPE=application
ACTION_SCRIPT=/opt/oracle/product/11g/crs/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=15
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=bls2
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=bond0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.128
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=90.40.100.116
I hope you can help me.

How is the impact when a sql server cluster instance failover to a downlevel version node?

Hi,
I have a one instance two nodes sql 2012 cluster, node1's sql 2012 version is 11.0.5522, node2's sql 2012 version is 11.0.3000, node1 is active.
When sql server failover from node1 to node2, it succeed. I want to konw if this downlevel failover impact database (data or usage)?
Many thanks.

I would not say this as a correct configuration although you can do it. Downside is suppose node 1 which is on higer version has some bug fixed with patch when you failover to lower version that bug might re surface. I have never used nodes with different
version nor i recommend.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Dblink creation between sql and oracle server

Hi dears,
I need to create dblink between the sql and oracle server.
(For me the requirement is sql datas need to import in oracle database).
My questions is,
Without installting gateway is't possibale to get the sql data in the oracle server.
my database version is 11.2.0.3 64bit
Kindly let me know, Waiting for your suggestsion.
Regards
Athish

About the Linked Server mechanism have a look at the MS Knowledge base article:
Article ID: 280106 - HOW TO: Set Up and Troubleshoot a Linked Server to Oracle in SQL Server
or
How to run a SQL Server 2005 Integration Services package as a SQL Server Agent job step Article ID : 912911
Regarding DG4ODBC and DG4MSQL, please have a look at our Support portal and look for the gateway master note:
Master Note for Oracle Gateway Products [Document 1083703.1]
It contains generic information how to connect to the foreign database
Document 233876.1 Options for Connecting to Foreign Data Stores and Non-Oracle Databases - For example - DB2, SQL*Server, Sybase, Informix, Teradata, MySQL
as well as the functional differences between the Database Gateway for ODBC (Generic Connectivity) and MS SQL Server
Document 252364.1 Functional Differences Between Generic Connectivity and Database Gateways
Document 232482.1 Gateway and Generic Connectivity Licensing Considerations
as well as where to find the latest release and how to install and configure them.

Do someone knows how to create a cluster with two nodes on oracle VM Ware

dear members,
can someone guide us through creating a cluster with two nodes on oracle VM. it will be nice if we can virtualiza RAC, atleast for education purposes.
Thank you all in advance

Here is an excellent article that explains how to do this:
http://startoracle.com/2007/09/30/so-you-want-to-play-with-oracle-11gs-rac-heres-how/

Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

Hi All,
Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
aa

I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
Same edition media has to be used in above two operation.
you can install two separate instances with one enterprise and one standard.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Create directory on a two-node Oracle server cluster

Similar Messages

Maybe you are looking for