Blog

  • Zero Data Lose

    Zero Data Lose

     

    Associations need to precisely dissect the capacities of these high accessibility frameworks and guide their abilities to the business necessities to guarantee they have an ideal blend of high accessibility answers for keeping their business running. Consider the business with a noteworthy web-based business nearness for instance.


     Oracle is exceptionally situated in the business by offering clients a thorough arrangement of database high availability capacities that consistently cooperate to help diminish both arranged and spontaneous downtime. What's more, Oracle Maximum Availability Architecture (MAA) gives clients an accepted procedures outline that can essentially decrease the cost and unpredictability of database high accessibility arrangements.

     

    On the off chance that impromptu and arranged blackouts happen, the information that backings higher volume web-based business exchanges must be ensured enough and be accessible with negligible downtime. This data ought to not exclusively to be moved down at standard interims at the neighborhood server farms, however, ought to likewise be duplicated to databases at a remote server farm associated over a fast, repetitive system. This remote server farm ought to be outfitted with optional servers and databases promptly accessible, and be synchronized with the essential servers and databases. This gives the business the ability to change to these servers immediately with negligible downtime if there is a blackout, rather than sitting tight for a considerable length of time and days to revamp servers and recoup information from went down tapes.

     

    As Oracle provides new additional feature from Oracle 11g Real Application Cluster (RAC), that feature called it as “Oracle High Availability Services” in short but sweet is known as “OHAS”.

     

    OHAS is actualized through another daemon procedure which is called ohasd’ on the OS layer, and the 11g documentation noticed that this Oracle High Availability Services Daemon (OHASD) grapples the lower some portion of the Oracle Clusterware stack, which comprises of processes that facilitate cluster operations in RAC databases. This incorporates the GPNPD, GIPC, MDNS and GNS background processes.

     

    It appears that RAC DBA's will continue to use the traditional crsctl commands for cluster management and that there are no direct commands for Oracle High Availability Services.

     

    The rundown in this segment depicts the procedures that contain the Oracle High Availability Services stack.

    • Grid Plug and Play (GPNPD): GPNPD gives access to the Grid Plug and Play profile, and facilitates updating of the profile among the hubs of the cluster to guarantee that the majority of the nodes node has the latest profile.
    • Grid Interprocess Communication (GIPC): A support daemon that enables Redundant Interconnect Usage.
    • Multicast Domain Name Service (mDNS): Used by Grid Plug and Play to locate profiles in the cluster, as well as by GNS to perform name resolution. The mDNS process is a background process on Linux and UNIX and on Windows. Allows DNS requests. The mDNS process is a background process on Linux and UNIX, and a service on Windows.
    • Oracle Grid Naming Service (GNS): Handles requests sent by external DNS servers, performing name resolution for names defined by the cluster. A gateway between the cluster mDNS and external DNS servers. The gnsd process performs name resolution within the cluster.

     

    Finally, the overall IT infrastructure for this e-commerce business should be extremely secure, to protect against malicious external and internal electronic attacks.