ODP.NET :: Is Failover Supported In Managed Driver
Nov 7, 2013
I can see that some failover events etc aren't supported (Differences between the ODP.NET Managed Driver and Unmanaged Driver), but is failover supported at all? I don't need to get notified, just to get the failover (clustered node switching) working. Is it supported in the managed driver?
I am trying to use oracle wallet with the new odp.net managed driver, but I am getting
"invalid username/password".
As the wallet itself is ok (it works with the unmanaged client), seems to me that this new provider is not fully compatible with Oracle Wallet. Is this true? I am trying this:
I have one database which is recently upgraded from oracle 8.1.5 to oracle 10.2.0.4.The database is having around 300 tablespace and total size of the database is 1.5 TB.
The database was created in oracle 8i and all the teblespace were DMT(Dictionary Managed Tablespace) .Usually after up gradation all the tablespace are in DMT mode. Now my requirement is to convert all the tablespace into LMT (Locally Managed Tablespace) so that I can AVAIL ALL THE FEATURES OF LMT.
This database is a mission critical database and very less downtime can be allowed.
In my production -- we have 3 nodes Primary RAC with 2 Nodes Physical secondary Standby RAC. Due to some reason we will have to failover means 3 nodes Primary Standby RAC to 2 Nodes secondary physical Standby RAC. share Steps for Failover ( not switchover) from 3 Nodes Primary RAC to 2 Nodes Physical Standby RAC. I know this is generic and can be find from google but issue is how can failover from 3 nodes primary standby rac to 2 nodes secondary physical standby rac.
I've got one database which was Initially upgraded from Oracle 8i to 10.2.04 running on windows. Most of the tabespaces are Dictionary managed. Do you think moving them to locally managed tablespace would give me better performance?
if Yes, what approach I should apply to move them to locally managed? I would like to do this with minimum/no downtime.
When a database is configured to use AL16UTF16 what character set is sent from DG4ODBC to an ODBC driver when passing in Arabic characters ?
i am using easy soft odbc driver for transfering data from oracle to MS SQL server. English text is going fine, but when i am trying to transfer some arabic text, it is getting corrupted.
I'm using following connection string: +connectionString="Driver={Oracle ODBC Driver};Server=someDb;Uid=useruidr;Pwd=password"+
when I call method "Open" on "OdbConnection" I get following exception: +ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified+
"someDb" is specified correctly in tsnames.ora, "...client" and "...clientin" are added to PATH environmental variable ORACLE_HOME is set to "...client"
I have Oracle Client 11.2.0.3.0 installed Operating system is Windows 7 32 bit
When I change Driver to "Microsoft ODBC for Oracle" it works fine. However I want to use Oracle ODBC Driver.
Since JDK 6, DatabaseMetaData.getCrossReference contract is :Retrieves a description of the foreign key columns in the given foreign key table that reference the primary key or the columns representing a unique constraint of the parent table (could be the same or a different table). But the Oracle JDBC Driver executed query is :
SELECT NULL AS pktable_cat, p.owner as pktable_schem, p.table_name as pktable_name, pc.column_name as pkcolumn_name,
My standby database was working fine which was running in maximum performance mode .Suddenly i found that logs are not being applied though archived logs are received from primary database.i issued the command in mount mode: alter database recover managed standby database disconnect from session;
altered database this command runs successfully. but MRP process in not initiated which i confirmed with the query (select process,status from v$managed_standby;)
What is expected behavior for VIP on Linux servers? ( 2-node RAC)
1.When entire RAC stack is running, and one node is rebooted or crashed? Will VIP fail over to second node? 2.When one node RAC stack is contained (crsctl stop crs), shutting down RAC stack on remaining node? What happens to the VIP and Scan IP? 3.When RAC stacks are down on both nodes, one node has VIP on (eth0:1), reboot this node. What happens to the VIP?
We see some behavior in scenario 3, but don't know why the VIP was moved to second node as all Oracle processes are down.
I am very new to data guard...I have a primary and a physical standby database...If the primary got crashed, are the users directly switched to physical standyby (is it automated) or the DBA has to manually do the fail over or switch over....is it the same concept as in RAC like TAF....How can the DBA know that the users are disconnected from the database.....explain with some steps...
configure correctly my application, Oracle is version 11R1
My physical configuration is :
Site 1 (main building) database on cluster : server1, server2 database : BASE1 available
Site2 (Backup Site) database on cluster : server3, server4 database : DGBASE1 not available for users (dataguard)
I want to acces BASE1 first in load balancing server1,2 (normal usage) and DGBASE1 in load balancing server3,4 in case of failover after 5 retries of 10 secondes (in case of main buiding out of order, DGBASE1 will be available for users)
My trouble is that with this configuration, access it randomly BASE1 or DGBASE1 but DGBASE1 is not available for users then I have failure
What could be the right configuration to obtain BASE1 first in load balancing (normal usage) and DGBASE1 in load balancing in case of failover of the BASE1 after 5 retries of 10 secondes ?
I am running some small tests here in my test env, using dataguard. I have configured the Primary and Standby with Maximum Availability... they're running just fine. Now i want to execute a failover test (i have already ran a Switchover test with the Broker successfully).
My question is very simple, at my point of view: What are the required steps to execute a successful manual failover? For example, i have my env as follows:
- Primary: prim1 - Standby: stdb1
Suppose that the primary database crashes in an unrecoverable way... is this case a manual failover would be necessary.
To do so, i would have to execute the following command, in my Standby database:
-- stdb1 is the standby database... DGMGRL> failover to stdb1
The above command is correct? Are there any required configurations after the failover? I read the Oracle Docs, and it says
if it is possible to create a failover setup without RAC and DG...For example:
I have 11.2.0.2 database (with EBS 12.1.3) on dbnode1...I would like to create another node to failover my primary datbas in case of any failure.
Steps i will follow: 1: creat dbnode2 2: install same os as dbnode1 3: install same oracle as dbnode1 4: share dbnode2 database between dbnode1 and dbnode2
Now, if hardware fails on dbnode1, can i manually failover and start my database on dbnode2?
I know we can do with RAC and DG,BUT without RAC and DG If not possible..
I am developing an 64bit And-In software. My OS is windows7 64bit Ultimate. Developer tool is Microsoft Visual Studio 2010 Ultimate 64bit any-CUP.Server is SUN server and Oracle database 10.2.0.5 64bit enterprise edition.I have installed instantclient-odbc-win64-10.2.0.5 on my computer.I am able to connect through the command line sqlplus user/pass@server.In date source(c:windowssystem32odbcad32.exe), ODBC Driver connection successful.But in VS2010 C#, use Tools -> Connect Database,I get an error 193 (Oracle in instantclient10_2,c:ora10_64SQORA32.dll) cann't be loaded.SQORA32.dll is 32bit ODBC Driver or 64bit ODBC Driver?How can I connect database with vs2010 64bit?
what is the configuration dba has do for enabling the "fast-start failover concept" in the event of loss of primary database without requiring any manual steps to invoke the failover.whether the configuration are to be made in parameter file if yes what are those ?
I have installed Oracle RAC 10g on Redhat Linux 4.0. Till yesterday failover was happening that is when i stopped one instance on node01 the vip of node01 was transferred to node02.This was shown using ifconfig -a but now that is now happening.
Below information is given:
[oracle@node01 ~]$ crs_stat -t Name Type Target State Host ------------------------------------------------------------ ora.hitesh.db application ONLINE ONLINE node02 ora....h1.inst application ONLINE ONLINE node01
I am following lab instruction from my Oracle Admin Workshop book. The exercise is to create a 2nd listener to support connect-time failover. I have two listeners up and running. I connected the second listener using Static Database Registration in OEM, and then I started it.
When I looked in the listener.ora file, I was expecting to find the entries for FAILOVER=TRUE but it is not there. Both listeners are designed to connect to the same instance 'orcl'.
My questions:
1) Is the FAILOVER entry supposed to be done automatically when the second listener is created ? or is it always a manual entry ? 2) How can I test that it is working ?
My Data Guard 's Enviroment: Primary: 11.1.0.7 RAC 2 Nodes Standby: 11.1.0.7 Single Instance
I want to implement Fast-Start Failover at my enviroment. Reading requirements, I found that Oracle Flashback is needed (I don't use Flashback on my databases).
Best Practices recommends 60 min (1 hr) for DB_FLASHBACK_RETENTION_TARGET if I just want to use Flashback to fast-start failover.
My questions:
What 's better, setup up flash recovery area on ASM or O.S. filesystem? What is the recommended size for flash recovery area?
I am using the dblink to merge the data. I am using the following merge statement.
merge into APP_USER.USR_NEW_RIGHTS@NEW_RIGHTS t Using (select 'test' GRANTEE,'TESTxxx'ROLE from dual ) s on (t.GRANTEE = s.GRANTEE and t.ROLE = s.ROLE) when not matched then insert (ID,GRANTEE,ROLE,XRIGHT,COMPANY,OWNER,TABLENAME) values ('','test','TESTxxx',null, null, null, null);
I know that I have to set a commit and it's working when I insert information's with a normal insert statement via database link, but it seems that merging doesn't work.