Virtualizing an Oracle RAC isn't necessarily a stupid idea, but it should only be done with a full understanding of the benefits and risks. You are asking questions, so that is a good step in the right direction.
Your question doesn't say which virtualization technology, the Oracle version, or the edition. For now I will assume this is for production on ...
No, nothing in SQL Server can give you the same thing out of the box.
Currently, the only SQL Server technology that allows simultaneous writes at multiple nodes is Peer-to-Peer replication. Note that I did not to say "write scale-out," because it works in a way such that the entire system has the write capacity of only a single node. The introductory ...
In this case, should I use TAF or FCF?
TAF- Transparent Application Failover is a database session-level connection failover mechanism and works only for OCI clients.
FCF- Fast Connection Failover is a application-level failover mechanism. It depends on the implicit connection cache feature and implicit connection caching must be enabled.
TAF would be ...
I'm a DBA supporting both SQL 2000-2012, Oracle 11g, and Oracle 11g RAC.
IMO, Always On Availability Groups in SQL 2012 comes very close to the availability and scalability of RAC at much less cost in both dollars and complexity. You can scale out reads by querying against the mirrors, but you'd want to direct all DML to the primary server (SQL Server ...
The straight answer to your question is no, SQL Server does not have equivalent functionality. There are aspects of SQL Server that give you the kind of failure tolerance that you want (even as far back as SQL Server 2005 when using DB mirroring and a mirror-aware application), but there is not a 1:1 with Oracle RAC.
Yes, it is possible.
Oracle Database supports multiple Oracle homes. You can install this
release or previous releases of the software more than once on the
same system, in different Oracle home directories. This allows
flexibility in deployment and maintenance of the database software.
Two transactions won't share an SCN barring a bug in Oracle.
Exactly how Oracle ensures this varies by version, platform, and configuration settings. For example, back in the Oracle 9.2 days, there was by default a non-zero max_commit_propagation_delay which meant that a row that was inserted on one node and committed might not be immediately visible to a ...
I tried the above suggestions, but did not work, such as select SQL did not get results and I still cannot drop the undo table space. The fundamental issue is that the old undo table space is still registered in Oracle as its undo, therefore we need to change it to the new undo table space.
Here are what I did and it worked:
create a new UNDO table space:
We just did the same thing.
install software in new machines and configure different cluster
copy tnsnames.ora, orapwSID files to new machines and prepare pfile
you may need to add SID to /etc/oratab file on new machines
shutdown database on old machines
dismount ASM diskgroups on old machines
present LUNs to new machines
mount diskgroups on new machines
As it turns out, the ODA is factory configured with active-backup bonds. I've tested this to work well without any switch-side LACP/EtherChannel configuration, and each bonded connection may be split across two switches. In my tests, no simulated failure or network reconfiguration caused more than a a few hundred milliseconds worth of network outage.
The recommendation is to have log switches occur a few times an hour. If you have a 100 log switches an hour with 50MB redo logs, you need e.g 1GB redo logs for 5 log switches/hour.
100*50 MB redo/hour for a 6.5GB database is unusually much though.
You can add the new logs, e.g:
ALTER DATABASE ADD LOGFILE THREAD 1 SIZE 1G;
ALTER DATABASE ADD LOGFILE THREAD ...
i've found the definitive answer from the oracle docs
in the Oracle Database Standard Edition and Oracle Real Application Clusters (Oracle RAC) section, it specifies
"Oracle Automatic Storage Management is required for creating and managing all Oracle database file types. Raw ...
What is node eviction?
Word Meaning(Merriam Webster Disctionary): to force(someone) to leave
The process of removing the failed(due to various reasons) node from the cluster is known as eviction. Prior to 11gR2 Oracle tries to prevent from split brain situation by quickly rebooting the failed node . After 11gr2 Clusterware will attempt to ...
Changing the order of the SET seemed to make a difference, as it is working now.
create or replace
AFTER logon ON DATABASE
execute immediate 'ALTER SESSION SET NLS_TERRITORY = ''AMERICA'' NLS_DATE_FORMAT = ''YYYY-MM-DD HH24:MI:SS'' NLS_TIMESTAMP_FORMAT = ''YYYY-MM-DD HH24:MI:SS.FF''';
I don't really like this ...
DISCLAIMER : Not an Oracle DBA
Use srvctl, the grid control program that allows you to manipulate parts of the RAC Cluster
Usage: srvctl <command> <object> [<options>]
We solved this at my previous company by scheduling a cron job for out of trading hours to grow the tablespace when it fell to within a couple of standard deviations of average daily growth free. I researched it extensively at the time, and there is no way to tune the threshold for when Oracle does it (and you probably wouldn't want to anyway, since you ...
30min for 1TB is quite normal. That all writing stops is also normal if your tablespace completely run out of space. When writes has nowhere to go they have to wait for the RESIZE operation to complete. If one extends datafile while there is still space in it database I/O does not stop.
Just why you extended for such huge amount? Now those +1TB will add to ...
I found the solution.
----------shutdown database instance first
$sqlplus / as sysdba
SQL> shutdown immediate;
---------stopping Oracle Clusterware, It will shutdown ASM instance itself
$ su -
# cd /u01/app/11.2.0/grid/bin/
# ./crsctl stop ...
It looks like resource manager is in action. Your dba configured this most likely to give certain processes priority over other processes. Oracle Scheduler is fuly integrated with Resource Manager but the way this is presented is a bit misleading. Often it has nothing to do with Scheduled Jobs at all.
You can find which sessions are waiting for resource ...
First of all, I checked that there were no extents on DISK1.
$ . oraenv
ORACLE_SID = [+ASM1] ?
SQL> select PXN_KFFXP, -- physical extent number
XNUM_KFFXP, -- virtual extent number
DISK_KFFXP, -- disk number
AU_KFFXP -- allocation unit number
no rows selected
I cleared the ...
You can check the value of the CLUSTER_DATABASE parameter:
SQL> select name, value from v$parameter where name = 'cluster_database';
According to the Oracle Database Reference:
CLUSTER_DATABASE is an Oracle RAC parameter that specifies whether or not ...
Yes, Oracle RAC is built using multiple servers sharing their memory - Cache Fusion - and they all access the same shared storage where the database resides. In Oracle an Instance is just the collection of processes that acts as an interface between client connections and the actual database.
Since all storage is shared, when a server crashes, a surviving ...
Oracle RAC requires a clustered file system:
ASM comes with the database
ASM provides a clustered file system
ASM was built specifically to do this
Anything else would be an additional cost 3rd party product that you would have to integrate and get working with your Oracle RAC.
Let me start with another question.
Is catproc.sql/catalog.sql really required?
Try creating a new database manually:
And stop here, don't run any scripts. You have a "functioning" database, you can create tablespaces, users, query v$ views, create tables, indexes, insert and query data. You can even create user-managed backups.
Now try ...
Listener is a process running in the Oracle Server machine. The responsibility of the listener is to listen for the incoming database connection request and spawning server process to handle the request(in Dedicated Server mode) or handing over to dispatcher process(in Shared-Server mode). In RAC architecture we have SCAN listener to redirect connection ...
Connect to third instance and issue
SQL> alter database open;
then to fourth instance and do the same.
But if you want to open all instances at once, you need to use srvctl utility:
srvctl start database -db db_name
When you drop user on primary then this will be also reflected on secondary site. Also impdp will work as expected. But when you are about to import large amount of data MAA might slow down the whole procedure significantly.
If you have enough experience with RMAN you might try:
shutdown and disconnect the secondary
import data into master
backup master ...
The answers provided by previous posters are all correct regarding the syntax to create a new UNDO tablespace and to switch system to the new UNDO tablespace.
The Oracle documentation states that the following statement will switch to the new UNDO tablespace:
ALTER SYSTEM SET UNDO_TABLESPACE = <name of new UNDO TS>;
e.g. for @Mohammad Jolani: