4 Replies Latest reply: Mar 30, 2014 6:46 AM by LaserSoft RSS

    Installing multiple databases on exadata..Solution Requested

    Saurabh Gupta-OC

      Dear Folks,


      We have a requirement of installing few databases on Exadata 1/8th Rack. The proposed plan is to utilize the 1/8th rack for DR, DEV, SIT, CIT, UAT & Performance Testing environment.

       

      The details plan is outlined as below:

      Environment

      HA / Standalone

      % of Production Server Capacity

      % of Production Storgage Capacity

      Disaster Recovery

      HA

      100%

      100%

      Development

      Standalone

      30%

      20%

      UAT

      Standalone

      20%

      25%

      Performance Testing

      Standalone

      30%

      25%

      SIT

      Standalone

      20%

      30%

      CIT

      Standalone

      20%

      30%

       

      As we know the configuration details of Exadata 1/8th Rack is:


      Exadata 1/8th Rack

      Database Servers

      2

      Storage Servers

      3

      # of Hard Disks

      18

      Usable Storage

      30 TB

      CPU Cores per DB Server

      12

      Memory per DB Server

      512 GB

      CPU Cores per Cell Server

      18

       

      Please note that, Production environment would be installed on a separate Exadata 1/8th rack.


      Now I have few queries and requesting all Exadata experts to kindly give some of your valuable time to clear my doubts:

       

      1. 1. Do we need to implement ASM-Scoped & Database-Scoped Security features to keep DR, non-production environment separate & restrict non-production databases access?
      2. 2. In order to allocate IO Requirement & manage all Databases performance, do we require implementing IORM?
      3. 3. If any body has experienced such implementation, would be great if you can share some thoughts on it.
      4. Best solution to implement 20+ databases in Exadata environment in OLTP environment.

       

      Your assistance is highly appreciate.

       

      Thanks,

      Vineet

        • 1. Re: Installing multiple databases on exadata..Solution Requested
          Marc Fielding

          Hi Vineet,

           

           

          I can't follow your math here:  you're proposing an environment with 220% of production server capacity, and 230% of production storage capacity.  If production uses the full capcity of an eighth rack, where do you expect this additional capacity to come from?

           

           

           

          1. Do we need to implement ASM-Scoped & Database-Scoped Security features to keep DR, non-production environment separate & restrict non-production databases access?

           

           

           

          ASM-level security is designed to restrict which databases can access which ASM diskgroups;  it does not cover access to the datbase itself.  I rarely see this level of security implemented, as most shops trust their superusers.

           

           

           

          2. 2. In order to allocate IO Requirement & manage all Databases performance, do we require implementing IORM?

           

           

           

          IORM lets you prioritize I/O capacity along business rules.  If you have a business requirement to give higher priority to some databases, by all means, implement IORM.

           

           

           

          3. 3. If any body has experienced such implementation, would be great if you can share some thoughts on it.

           

           

           

          I'd suggest staying with the Exadata default settings as much as possible and not "over-configuring" too much.  For example, if you don't have an I/O bottleneck, IORM policies will have little effect.  Test out the system to see how well it performs with the out-of-the-box config, and apply targetted changes to address issues encountered.

           

           

           

          4. Best solution to implement 20+ databases in Exadata environment in OLTP environment.

           

           

           

          Well, first of all, try and see if you can consolidate into fewer instances.  One of the biggest challenges you may run into is RAM:  your purchase of the additoinal RAM upgrade was a good idea, but if you want to run RAC, you'll end up with well over 20 instances, each with their own shared pool, buffer cache, etc.  By putting so many small databases, you limit your ability to do full-scale performance tests in a configuration approaching what you run in production.

           

          Marc

          • 2. Re: Installing multiple databases on exadata..Solution Requested
            Saurabh Gupta-OC

            Thanks Mark for your reply.

             

            Actually, the proposal is to allocate initial allocation of production server & storage capacity, which would not be 100% server & storage capacity, and the some of the allocated environment (UAT, PT, CIT, SIT) would be decommissioned after few months once their requirement is finished and those left server & storage capacity would be utilized for DR environment.

             

            We are not using clustered database for each environment except DR. Why you think RAM would be an issue as we are having 528 GB RAC on each DB node?

             

            Regards

            Saurabh

            • 3. Re: Installing multiple databases on exadata..Solution Requested
              Marc Fielding

              Hi Saurabh,

               

               

              If using percentages, I'd suggest using percentages of total system capacity rather than percentages of your expecetd production usage.  You can then translate these percentages into storage space values, max utilization limits, or other places where you make allocations.

               

               

              The issue with RAM is that, if you're allocating for a production-sized performance test environment (with production-sized memory regions), plus DR and other non-produ activities, you'd either end up leaving a lot of production capacity unused, or overcommitting non-production capacity.

               

               

              HTH!

               

               

              Marc

              • 4. Re: Installing multiple databases on exadata..Solution Requested
                LaserSoft

                Hi Friend,

                1. Do we need to implement ASM-Scoped & Database-Scoped Security features to keep DR, non-production environment separate & restrict non-production databases access?


                In Exadata, ASM-Scoped and Database_Scoped security provides control on which ASM clusters and database clients can access specific grid disks on storage server cells. So implementing both are good security for your multiple databases.


                2. In order to allocate IO Requirement & manage all Databases performance, do we require implementing IORM


                Include IORM with DBRM, so that you can control IO as well DB resources at greater extent.


                3. If any body has experienced such implementation, would be great if you can share some thoughts on it.


                We have implemented 8 databases in 1/8th rack and used ASM scoped and Database-scoped security.

                 

                4. Best solution to implement 20+ databases in Exadata environment in OLTP environment.


                Best Implementation is :


                1. No of databases - each database size + memory required (SGA + PGA)

                2. Future growth of each database

                3. Out 20+ daabases, which are most important databases ? so that we can keep these databases in interleaved grid disks

                for performance

                4. No of databases - each database find out the objects required to keep smart flash cache

                5. Based on priority of database implement IORM with DBRM


                Hope it helps..


                Thanks

                LaserSoft