Skip to main content

Oracle 10 days rule and how it work

Oracle's “Ten Days Rule” ?? I know it's very confusing and hard to understand " Oracle Ten Days Rule”. I will try to explain these "Ten Days Rule”. Please check my post on oracle auditing risks too. Oracle's “Ten Days Rule” are very confusing not even for us but sometimes for oracle's sales representatives too. You have to pay a lot of money means a lot if you follow them wrongly. We all may thinks that by these "Oracle 10 day rules" we can run our DR(disaster  recovery) server for ten days without purchasing any license. Let me tell you, This is totally a myth.


I was working for one of our client in INDIA and They were so confident about these Ten day rules that they are under these rules. After discussing with their IT mgr, We come to the point that yes they were totally confused with this "Oracle 10 days rule".


So What is Oracle 10 day rule?


These "Ten Days Rule” are actually very simple. It can applies for fail-over situation and yes its very important part. These "Ten Days Rule” can apply to  active/passive hardware where oracle is installed on both of your nodes or you are sharing the storage. We know what cluster services we are using like Fail safe for Microsoft (similar to RAC), OCRS ( Oracle Cluster Ready Services), Oracle RAC etc. . Like for an example our primary server got fails and we have a fail-over server that means our services will get less impacted because of any crash. The good part of oracle is, They will allow you to install binaries on fail-over site without any licencing cost for that node for only 10 days.


But according to this 10 days rule, you need to buy the licences for your fail-over site/server if and only if it is up and running for more than 10 days in given calendar year. That means if you have used your all ten days in the starting year than you cannot use this for rest of the year.


Also the interesting part is if your primary server got failed at 11:30 pm Saturday and you moved to fail-over at 11:35 pm  and after the help of your DBA's and your Team you manage to get back to primary site by 02:00 am i.e. Sunday. So this will count two days. haha interesting right? So for by using just approx one and half hour, We have just used our two days out of ten days. Really crazy,
So now we know that Oracle 10 days rule will work on calendar days not on time.


The ten days rule is also confused with Oracle’s license policy for testing backups. In this case we can install Oracle on a different server and check backup that is it reliable or not. But after checking backup we need to shutdown the servers until you need to  test the backup again. Also the interesting part in this is, you cannot keep checking your database backup again and again every other month. There is one restriction and that is, you can only start and check that server to check your backup for four times, and you cannot test the scenario for more than 2 days regularly, yeah off course in  any given calendar of year.


I hope it will help you to avoid the trouble, As we already paying much to oracle and don't want to pay them more ;). Please comment on this post if you find  anything wrong.

Keep sharing, keep smile.

Popular posts from this blog

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...

Video Conferencing Project in Java Source Code

Video Conferencing Project in Java Source Code     ################################################################################# FEATURE ################################################################################# 1.Multi Chat(Used Threadpole) 2.P2P Chat 3.P2P Audio Chat 4.P2P Video Chat 5.Complete Automated 6.H.263 compression Video 7.raw audio PREREQUISITE: 1. JUST INSTALL jmf-2.1.1 e @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ *****/  just need to copy the client side code and run it to a pc   not need any manual IP ***/  How to run : Just run server side code in a PC and then Run Client side code to different  PC.Then the work is done. Server Side Code: ClientListener.java Clients.java Main.java MessageListener.java ServerConstant.java ServerManager.java ServerMonitor.java ServerStatusListener.java   ClientListener.java /*  * To change this template, choose Tools | Templates  * and open the tem...

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...

JAX-WS Hello World Example – RPC Style

JAX-WS Hello World Example – RPC Style AX-WS is bundled with JDK 1.6, which makes Java web service development easier to develop. This tutorial shows you how to do the following tasks: Create a SOAP-based RPC style web service endpoint by using JAX-WS. Create a Java web service client manually. Create a Java web service client via  wsimport  tool. Create a Ruby web service client. You will be surprise of how simple it is to develop a RPC style web service in JAX-WS. Note In general words, “ web service endpoint ” is a service which published outside for user to access; where “ web service client ” is the party who access the published service. JAX-WS Web Service End Point The following steps showing how to use JAX-WS to create a RPC style web service endpoint. 1. Create a Web Service Endpoint Interface File : HelloWorld.java package com.mkyong.ws ;   import javax.jws.WebMethod ; import javax.jws.WebService ; import javax.jws.soap.SOA...

Oracle character AL32UTF8

The character set determines what languages can be represented in the database. Oracle recommends using Unicode (AL32UTF8) as the database character set. AL32UTF8 is Oracle's name for the UTF-8 encoding of the Unicode standard. The Unicode standard is the universal character set that supports most of the currently spoken languages of the world. The use of the Unicode standard is indispensable for any multilingual technology, including database processing. Changing the database character set is a time consuming and complex project. Therefore, it is very important to select the right character set at installation time. If the language is American English or a Western European language, then the default character set is WE8MSWIN1252. Each Microsoft Windows ANSI Code Page can store data from only one language or a limited group of languages, such as only Western European, or only Eastern European, or only Japanese. AL32UTF8 is a multibyte character set, database operations on character...

ORA-02291: integrity constraint violated - parent key not found

“Error: ORA-02291: integrity constraint violated - parent key not found” Reason:    A Primary key does not have the same value as the foreign key. We will discuss it in detail later in this article. Action:   For  ORA-02291: integrity constraint violated - parent key not found  You may either delete the foreign key or the matching primary key can be added. In either way, you may try to get this error corrected. Let's understand more about ORA-02291: integrity constraint violated - parent key not found? The Oracle software brought us the strength by which multiple tables in the database can pass on information so efficiently. Not only this, there are numerous devices in this software which enables access to and sourcing data from multiple tables. You can easily execute complicated database issues without an unusual uncertainty by creating statements with the fantastic characteristic of this software. Realistically, if we talk about user or database no one is perf...