Wednesday, 25 September 2013

About The Author

Hi,
   I am working as an Information Security Consultant in one of the leading IT Organisation in the world. I have been working on Oracle Database,Oracle DB clustering using RAC, Oracle Apps, IBM AIX, LINUX, TIVOLI STORAGE MANAGER, IBM STORAGE and Now Oracle Security Solutions like Audit Vault and Database Firewall etc.

We have been trying to share our work experiences among the enthusiastic audiences through open discussions, Conferences and online and offline classes.

Please suggest and also share your valuable views.So that I will try to improve this blog.





10 comments:

  1. Thanks for inviting me to your blog spot Bhai.I will post my questions very soon regarding DB.
    I hope u will also reply too to me according to my question.

    Thanks,
    Hemanta

    ReplyDelete
  2. How to re-size Database Buffer Cache & Shared Pool dynamically?

    ReplyDelete
    Replies
    1. Hi Hemanta,
      This can be done in recent version of oracle database like 11gr2 oracle database. If your system is not using AMM (Automatic Memory Management, which is highly recommended) you can choose to dynamically reconfigure the sizes of the shared pool, the large pool, the buffer cache and other process memory. The values for these parameters are also dynamically configurable using the ALTER SYSTEM statement except for the log buffer pool and process-private memory(static parameter require startup after change).

      Ex.
      ALTER SYSTEM SET db_cache_size=100M

      ALTER SYSTEM SET shared_pool_size=50M

      Delete
  3. What is granule and how it is used as contiguous virtual memory?

    ReplyDelete
    Replies
    1. granule is a unit to measure allocated memory units for shared pool,buffer cache,java pool and large pool. To get a good idea please read doc below. If still have doubts you can ask.

      http://docs.oracle.com/cd/E11882_01/server.112/e16638/memory.htm#PFGRF94336

      Delete
    2. In other way we can say, granule is a reserved region of RAM memory for the growth of SGA. If the current amount of SGA memory is less than the value of the sga_max_size init.ora parameter, then Oracle is free to allocate more granules until the SGA size reaches the sga_max_size limit.
      NOTE: Oracle does not support dynamic modification of the large_pool_size parameter and the sga_max_size parameter.

      Delete
  4. If the retention policy don't match to the already given value in rman script policy, then what wiil be the problem arise at that time?


    Thanks,
    Hemanta

    ReplyDelete
  5. Thanks for your appreciation!!

    ReplyDelete