v$ db_cache_advice

Similar Questions

• Insert - Performance problem

  Hi Experts,

  I am new to Oracle. Ask for your help to fix the performance of a query of insertion problem.

  I have an insert query that is go search for records of the partitioned table.

  Background: the user indicates that the query was running in 30 minutes to 10 G. The database is upgraded to 12 by one of my colleague. Now the query works continuously for hours, but no result. Check the settings and SGA is 9 GB, Windows - 4 GB. DB block size is 8192, DB Multiblock read file Count is 128. Overall target of PGA is 2457M.

  The parameters are given below

  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ----------
  DBFIPS_140 boolean FALSE
  O7_DICTIONARY_ACCESSIBILITY boolean FALSE
  whole active_instance_count
  aq_tm_processes integer 1
  ARCHIVE_LAG_TARGET integer 0
  asm_diskgroups chain
  asm_diskstring chain
  asm_power_limit integer 1
  asm_preferred_read_failure_groups string
  audit_file_dest string C:\APP\ADM
  audit_sys_operations Boolean TRUE

  AUDIT_TRAIL DB string
  awr_snapshot_time_offset integer 0
  background_core_dump partial string
  background_dump_dest string C:\APP\PRO
  \RDBMS\TRA
  BACKUP_TAPE_IO_SLAVES boolean FALSE
  bitmap_merge_area_size integer 1048576
  blank_trimming boolean FALSE
  buffer_pool_keep string
  buffer_pool_recycle string
  cell_offload_compaction ADAPTIVE channel

  
  cell_offload_decryption Boolean TRUE
  cell_offload_parameters string
  cell_offload_plan_display string AUTO
  cell_offload_processing Boolean TRUE
  cell_offloadgroup_name string
  whole circuits
  whole big client_result_cache_lag 3000
  client_result_cache_size big integer 0
  clonedb boolean FALSE
  cluster_database boolean FALSE
  cluster_database_instances integer 1

  
  cluster_interconnects chain
  commit_logging string
  commit_point_strength integer 1
  commit_wait string
  string commit_write
  common_user_prefix string C#.
  compatible string 12.1.0.2.0
  connection_brokers string ((TYPE = DED
  ((TYPE = EM
  control_file_record_keep_time integer 7
  control_files string G:\ORACLE\

  TROL01. CTL
  FAST_RECOV
  NTROL02. CT
  control_management_pack_access string diagnostic
  core_dump_dest string C:\app\dia
  bal12\cdum
  cpu_count integer 4
  create_bitmap_area_size integer 8388608
  create_stored_outlines string
  cursor_bind_capture_destination memory of the string + tell
  CURSOR_SHARING EXACT string

  cursor_space_for_time boolean FALSE
  db_16k_cache_size big integer 0
  db_2k_cache_size big integer 0
  db_32k_cache_size big integer 0
  db_4k_cache_size big integer 0
  db_8k_cache_size big integer 0
  db_big_table_cache_percent_target string 0
  db_block_buffers integer 0
  db_block_checking FALSE string
  db_block_checksum string TYPICAL
  Whole DB_BLOCK_SIZE 8192

  db_cache_advice string WE
  db_cache_size large integer 0
  db_create_file_dest chain
  db_create_online_log_dest_1 string
  db_create_online_log_dest_2 string
  db_create_online_log_dest_3 string
  db_create_online_log_dest_4 string
  db_create_online_log_dest_5 string
  db_domain chain
  db_file_multiblock_read_count integer 128
  db_file_name_convert chain

  DB_FILES integer 200
  db_flash_cache_file string
  db_flash_cache_size big integer 0
  db_flashback_retention_target around 1440
  chain of db_index_compression_inheritance NONE
  DB_KEEP_CACHE_SIZE big integer 0
  chain of db_lost_write_protect NONE
  db_name string ORCL
  db_performance_profile string
  db_recovery_file_dest string G:\Oracle\
  y_Area

  
  whole large db_recovery_file_dest_size 12840M
  db_recycle_cache_size large integer 0
  db_securefile string PREFERRED
  channel db_ultra_safe
  db_unique_name string ORCL
  db_unrecoverable_scn_tracking Boolean TRUE
  db_writer_processes integer 1
  dbwr_io_slaves integer 0
  DDL_LOCK_TIMEOUT integer 0
  deferred_segment_creation Boolean TRUE
  dg_broker_config_file1 string C:\APP\PRO

  
  \DATABASE\
  dg_broker_config_file2 string C:\APP\PRO
  \DATABASE\
  dg_broker_start boolean FALSE
  diagnostic_dest channel directory
  disk_asynch_io Boolean TRUE
  dispatchers (PROTOCOL = string
  12XDB)
  distributed_lock_timeout integer 60
  dml_locks whole 2076
  whole dnfs_batch_size 4096

  dst_upgrade_insert_conv Boolean TRUE
  enable_ddl_logging boolean FALSE
  enable_goldengate_replication boolean FALSE
  enable_pluggable_database boolean FALSE
  event string
  exclude_seed_cdb_view Boolean TRUE
  fal_client chain
  fal_server chain
  FAST_START_IO_TARGET integer 0
  fast_start_mttr_target integer 0
  fast_start_parallel_rollback string LOW

  
  file_mapping boolean FALSE
  fileio_network_adapters string
  filesystemio_options chain
  fixed_date chain
  gcs_server_processes integer 0
  global_context_pool_size string
  global_names boolean FALSE
  global_txn_processes integer 1
  hash_area_size integer 131072
  channel heat_map
  hi_shared_memory_address integer 0

  hs_autoregister Boolean TRUE
  iFile file
  inmemory_clause_default string
  inmemory_force string by DEFAULT
  inmemory_max_populate_servers integer 0
  inmemory_query string ENABLE
  inmemory_size big integer 0
  inmemory_trickle_repopulate_servers_ integer 1
  percent
  instance_groups string
  instance_name string ORCL

  
  instance_number integer 0
  instance_type string RDBMS
  instant_restore boolean FALSE
  java_jit_enabled Boolean TRUE
  java_max_sessionspace_size integer 0
  JAVA_POOL_SIZE large integer 0
  java_restrict string no
  java_soft_sessionspace_limit integer 0
  JOB_QUEUE_PROCESSES around 1000
  LARGE_POOL_SIZE large integer 0
  ldap_directory_access string NONE

  
  ldap_directory_sysauth string no.
  license_max_sessions integer 0
  license_max_users integer 0
  license_sessions_warning integer 0
  listener_networks string
  LOCAL_LISTENER (ADDRESS = string
  = i184borac
  (NET) (PORT =
  lock_name_space string
  lock_sga boolean FALSE
  log_archive_config string

  
  Log_archive_dest chain
  Log_archive_dest_1 chain
  LOG_ARCHIVE_DEST_10 string
  log_archive_dest_11 string
  log_archive_dest_12 string
  log_archive_dest_13 string
  log_archive_dest_14 string
  log_archive_dest_15 string
  log_archive_dest_16 string
  log_archive_dest_17 string
  log_archive_dest_18 string

  
  log_archive_dest_19 string
  LOG_ARCHIVE_DEST_2 string
  log_archive_dest_20 string
  log_archive_dest_21 string
  log_archive_dest_22 string
  log_archive_dest_23 string
  log_archive_dest_24 string
  log_archive_dest_25 string
  log_archive_dest_26 string
  log_archive_dest_27 string
  log_archive_dest_28 string

  
  log_archive_dest_29 string
  log_archive_dest_3 string
  log_archive_dest_30 string
  log_archive_dest_31 string
  log_archive_dest_4 string
  log_archive_dest_5 string
  log_archive_dest_6 string
  log_archive_dest_7 string
  log_archive_dest_8 string
  log_archive_dest_9 string
  allow the chain of log_archive_dest_state_1

  
  allow the chain of log_archive_dest_state_10
  allow the chain of log_archive_dest_state_11
  allow the chain of log_archive_dest_state_12
  allow the chain of log_archive_dest_state_13
  allow the chain of log_archive_dest_state_14
  allow the chain of log_archive_dest_state_15
  allow the chain of log_archive_dest_state_16
  allow the chain of log_archive_dest_state_17
  allow the chain of log_archive_dest_state_18
  allow the chain of log_archive_dest_state_19
  allow the chain of LOG_ARCHIVE_DEST_STATE_2

  allow the chain of log_archive_dest_state_20
  allow the chain of log_archive_dest_state_21
  allow the chain of log_archive_dest_state_22
  allow the chain of log_archive_dest_state_23
  allow the chain of log_archive_dest_state_24
  allow the chain of log_archive_dest_state_25
  allow the chain of log_archive_dest_state_26
  allow the chain of log_archive_dest_state_27
  allow the chain of log_archive_dest_state_28
  allow the chain of log_archive_dest_state_29
  allow the chain of log_archive_dest_state_3

  allow the chain of log_archive_dest_state_30
  allow the chain of log_archive_dest_state_31
  allow the chain of log_archive_dest_state_4
  allow the chain of log_archive_dest_state_5
  allow the chain of log_archive_dest_state_6
  allow the chain of log_archive_dest_state_7
  allow the chain of log_archive_dest_state_8
  allow the chain of log_archive_dest_state_9
  log_archive_duplex_dest string
  log_archive_format string ARC%S_%R.%
  log_archive_max_processes integer 4

  log_archive_min_succeed_dest integer 1
  log_archive_start Boolean TRUE
  log_archive_trace integer 0
  whole very large log_buffer 28784K
  log_checkpoint_interval integer 0
  log_checkpoint_timeout around 1800
  log_checkpoints_to_alert boolean FALSE
  log_file_name_convert chain
  whole MAX_DISPATCHERS
  max_dump_file_size unlimited string
  max_enabled_roles integer 150

  
  whole max_shared_servers
  max_string_size string STANDARD
  memory_max_target big integer 0
  memory_target large integer 0
  NLS_CALENDAR string GREGORIAN
  nls_comp BINARY string
  nls_currency channel u
  string of NLS_DATE_FORMAT DD-MON-RR
  nls_date_language channel ENGLISH
  string nls_dual_currency C
  nls_iso_currency string UNITED KIN

  nls_language channel ENGLISH
  nls_length_semantics string OCTET
  string nls_nchar_conv_excp FALSE
  nls_numeric_characters chain.,.
  nls_sort BINARY string
  nls_territory string UNITED KIN
  nls_time_format HH24.MI string. SS
  nls_time_tz_format HH24.MI string. SS
  chain of NLS_TIMESTAMP_FORMAT DD-MON-RR
  NLS_TIMESTAMP_TZ_FORMAT string DD-MON-RR
  noncdb_compatible boolean FALSE

  
  object_cache_max_size_percent integer 10
  object_cache_optimal_size integer 102400
  olap_page_pool_size big integer 0
  open_cursors integer 300
  Open_links integer 4
  open_links_per_instance integer 4
  optimizer_adaptive_features Boolean TRUE
  optimizer_adaptive_reporting_only boolean FALSE
  OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES boolean FALSE
  optimizer_dynamic_sampling integer 2
  optimizer_features_enable string 12.1.0.2

  optimizer_index_caching integer 0
  OPTIMIZER_INDEX_COST_ADJ integer 100
  optimizer_inmemory_aware Boolean TRUE
  the string ALL_ROWS optimizer_mode
  optimizer_secure_view_merging Boolean TRUE
  optimizer_use_invisible_indexes boolean FALSE
  optimizer_use_pending_statistics boolean FALSE
  optimizer_use_sql_plan_baselines Boolean TRUE
  OPS os_authent_prefix string $
  OS_ROLES boolean FALSE
  parallel_adaptive_multi_user Boolean TRUE

  
  parallel_automatic_tuning boolean FALSE
  parallel_degree_level integer 100
  parallel_degree_limit string CPU
  parallel_degree_policy chain MANUAL
  parallel_execution_message_size integer 16384
  parallel_force_local boolean FALSE
  parallel_instance_group string
  parallel_io_cap_enabled boolean FALSE
  PARALLEL_MAX_SERVERS integer 160
  parallel_min_percent integer 0
  parallel_min_servers integer 16

  parallel_min_time_threshold string AUTO
  parallel_server boolean FALSE
  parallel_server_instances integer 1
  parallel_servers_target integer 64
  parallel_threads_per_cpu integer 2
  pdb_file_name_convert string
  pdb_lockdown string
  pdb_os_credential string
  permit_92_wrap_format Boolean TRUE
  pga_aggregate_limit great whole 4914M
  whole large pga_aggregate_target 2457M

  -
  Plscope_settings string IDENTIFIER
  plsql_ccflags string
  plsql_code_type chain INTERPRETER
  plsql_debug boolean FALSE
  plsql_optimize_level integer 2
  plsql_v2_compatibility boolean FALSE
  plsql_warnings DISABLE channel: AL
  PRE_PAGE_SGA Boolean TRUE
  whole process 300
  processor_group_name string
  query_rewrite_enabled string TRUE

  
  applied query_rewrite_integrity chain
  rdbms_server_dn chain
  read_only_open_delayed boolean FALSE
  recovery_parallelism integer 0
  Recyclebin string on
  redo_transport_user string
  remote_dependencies_mode string TIMESTAMP
  remote_listener chain
  Remote_login_passwordfile string EXCLUSIVE
  REMOTE_OS_AUTHENT boolean FALSE
  remote_os_roles boolean FALSE

  replication_dependency_tracking Boolean TRUE
  resource_limit Boolean TRUE
  resource_manager_cpu_allocation integer 4
  resource_manager_plan chain
  result_cache_max_result integer 5
  whole big result_cache_max_size K 46208
  result_cache_mode chain MANUAL
  result_cache_remote_expiration integer 0
  resumable_timeout integer 0
  rollback_segments chain
  SEC_CASE_SENSITIVE_LOGON Boolean TRUE

  sec_max_failed_login_attempts integer 3
  string sec_protocol_error_further_action (DROP, 3)
  sec_protocol_error_trace_action string PATH
  sec_return_server_release_banner boolean FALSE
  disable the serial_reuse chain
  service name string ORCL
  session_cached_cursors integer 50
  session_max_open_files integer 10
  entire sessions 472
  Whole large SGA_MAX_SIZE M 9024
  Whole large SGA_TARGET M 9024

  
  shadow_core_dump string no
  shared_memory_address integer 0
  SHARED_POOL_RESERVED_SIZE large integer 70464307
  shared_pool_size large integer 0
  whole shared_server_sessions
  SHARED_SERVERS integer 1
  skip_unusable_indexes Boolean TRUE
  smtp_out_server chain
  sort_area_retained_size integer 0
  sort_area_size integer 65536
  spatial_vector_acceleration boolean FALSE

  
  SPFile string C:\APP\PRO
  \DATABASE\
  sql92_security boolean FALSE
  SQL_Trace boolean FALSE
  sqltune_category string by DEFAULT
  standby_archive_dest channel % ORACLE_HO
  standby_file_management string MANUAL
  star_transformation_enabled string TRUE
  statistics_level string TYPICAL
  STREAMS_POOL_SIZE big integer 0
  tape_asynch_io Boolean TRUE

  temp_undo_enabled boolean FALSE
  entire thread 0
  threaded_execution boolean FALSE
  timed_os_statistics integer 0
  TIMED_STATISTICS Boolean TRUE
  trace_enabled Boolean TRUE
  tracefile_identifier chain
  whole of transactions 519
  transactions_per_rollback_segment integer 5
  UNDO_MANAGEMENT string AUTO
  UNDO_RETENTION integer 900

  undo_tablespace string UNDOTBS1
  unified_audit_sga_queue_size integer 1048576
  use_dedicated_broker boolean FALSE
  use_indirect_data_buffers boolean FALSE
  use_large_pages string TRUE
  user_dump_dest string C:\APP\PRO
  \RDBMS\TRA
  UTL_FILE_DIR chain
  workarea_size_policy string AUTO
  xml_db_events string enable

  Thanks in advance

  Firstly, thank you for posting the 10g implementation plan, which was one of the key things that we were missing.

  Second, you realize that you have completely different execution plans, so you can expect different behavior on each system.

  Your package of 10g has a total cost of 23 959 while your plan of 12 c has a cost of 95 373 which is almost 4 times more.  All things being equal, cost is supposed to relate directly to the time spent, so I expect the 12 c plan to take much more time to run.

  From what I can see the 10g plan begins with a scan of full table on DEALERS, and then a full scan on SCARF_VEHICLE_EXCLUSIONS table, and then a full scan on CBX_tlemsani_2000tje table, and then a full scan on CLAIM_FACTS table.  The first three of these analyses tables have a very low cost (2 each), while the last has a huge cost of 172K.  Yet once again, the first three scans produce very few lines in 10g, less than 1,000 lines each, while the last product table scan 454 K lines.

  It also looks that something has gone wrong in the 10g optimizer plan - maybe a bug, which I consider that Jonathan Lewis commented.  Despite the full table scan with a cost of 172 K, NESTED LOOPS it is part of the only has a cost of 23 949 or 24 K.  If the math is not in terms of 10g.  In other words, maybe it's not really optimal plan because 10g optimizer may have got its sums wrong and 12 c might make his right to the money.  But luckily this 'imperfect' 10g plan happens to run fairly fast for one reason or another.

  The plan of 12 starts with similar table scans but in a different order.  The main difference is that instead of a full table on CLAIM_FACTS scan, it did an analysis of index on CLAIM_FACTS_AK9 beach at the price of 95 366.  It is the only main component of the final total cost of 95 373.

  Suggestions for what to do?  It is difficult, because there is clearly an anomaly in the system of 10g to have produced the particular execution plan that he uses.  And there is other information that you have not provided - see later.

  You can try and force a scan of full table on CLAIM_FACTS by adding a suitable example suspicion "select / * + full (CF) * / cf.vehicle_chass_no...". "However, the tips are very difficult to use and does not, guarantee that you will get the desired end result.  So be careful.  For the essay on 12 c, it may be worth trying just to see what happens and what produces the execution plan looks like.  But I would not use such a simple, unique tip in a production system for a variety of reasons.  For testing only it might help to see if you can force the full table on CLAIM_FACTS scan as in 10g, and if the performance that results is the same.

  The two plans are parallel ones, which means that the query is broken down into separate, independent steps and several steps that are executed at the same time, i.e. several CPUS will be used, and there will be several readings of the disc at the same time.  (It is a mischaracterization of the works of parallel query how).  If 10g and 12 c systems do not have the SAME hardware configuration, then you would naturally expect different time elapsed to run the same parallel queries.  See the end of this answer for the additional information that you may provide.

  But I would be very suspicious of the hardware configuration of the two systems.  Maybe 10 g system has 16-core processors or more and 100's of discs in a matrix of big drives and maybe the 12 c system has only 4 cores of the processor and 4 disks.  That would explain a lot about why the 12 c takes hours to run when the 10 g takes only 30 minutes.

  Remember what I said in my last reply:

  "Without any contrary information I guess the filter conditions are very low, the optimizer believes he needs of most of the data in the table and that a table scan or even a limited index scan complete is the"best"way to run this SQL.  In other words, your query takes just time because your tables are big and your application has most of the data in these tables. "

  When dealing with very large tables and to do a full table parallel analysis on them, the most important factor is the amount of raw hardware, you throw the ball to her.  A system with twice the number of CPUS and twice the number of disks will run the same parallel query in half of the time, at least.  It could be that the main reason for the 12 c system is much slower than the system of 10g, rather than on the implementation plan itself.

  You may also provide us with the following information which would allow a better analysis:

  • Row counts in each tables referenced in the query, and if one of them are partitioned.
  • Hardware configurations for both systems - the 10g and the 12 a.  Number of processors, the model number and speed, physical memory, CPU of discs.
  • The discs are very important - 10g and 12 c have similar disk subsystems?  You use simple old records, or you have a San, or some sort of disk array?  Are the bays of identical drives in both systems?  How are they connected?  Fast Fibre Channel, or something else?  Maybe even network storage?
  • What is the size of the SGA in both systems?  of values for MEMORY_TARGET and SGA_TARGET.
  • The fact of the CLAIM_FACTS_AK9 index exist on the system of 10g.  I guess he does, but I would like that it confirmed to be safe.

  John Brady

• Fix the activation parameters for caching the results of the customer? No performance gain

  I gathered and made every detail I could search. I use Oracle EE 11.2 g 32-bit on Windows 7 64 bit
  
  But despite I activate client caching result, I see no difference response API despite I have remote, connect to the server on LAN 1Gbit network
  
  I see > difference 1 sec only when you enable caching of server (2nd opening files 300% faster 57 dry-> 18 s) and 32 MB are cached for the opening.
  I don't know how to see the client_result_cache except the network traffic, detours, IO
  MEASURES_
  * 1.* I activated the parameter setting Statement Caching on the client and dbhome and set it equal to my ora.ini file OPEN_CURSORS (300) the registry as possible. And rebooted the system, of course.
  ---------
  HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > ORACLE > KEY_OraClient11g_home1 > OLED > StmtCacheSize
  HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > ORACLE > KEY_OraDb11g_home1 > OLED > StmtCacheSize
  -There is no standard oracle registry dir - probably cause its 64 bit +.
  -* 2 I have Super-activated all relevant SYSTEM parameters. 3 X the size necessary to be cached, FORCED cach, 100% of the result, 600000ms lag(10min)
  -------
  client_result_cache_lag... large integer 600000
  client_result_cache_size... great integer.100M
  ...
  db_cache_advice... chain... WE
  db_cache_size... large integer 0
  ...
  ... full object_cache_max_size_percent... 10
  ... full object_cache_optimal_size... 102400
  ... full result_cache_max_result... 100
  result_cache_max_size... big integer.100M-this is for caching wright + server
  result_cache_mode... chain... FORCE
  ... full result_cache_remote_expiration... 30
  session_cached_cursors... around... 50
  -Is everything OK? Why not better time response then?
  The LAN 1Gbit 1 customer is perhaps too fast anyway, and I should try via internet or something?
  
  Hope that you have an idea, I can't search to find or think of something.

  As said by John, SQL * Plus does not implement caching the result to the client. You write an application for OIC (or another application that knows the OIC calls appropriate to make) that implements the setting cache the result of the customer.

  Your test is behaving as expected.

  Justin

• Oracle 10g, how to determine the memory allocated is healthy or sufficient.

  Hi guys,.
  
  I have a 10.2.0.5 production database.
  Currently, my server has 8 GB of physical RAM.
  / 3GB is allocated to the SGA and 1 GB for the PGA.
  Let's say a day is needed for the application (for example, weblogic) to increase the pool of connections from 20 to 50.
  How are we able to know if the memory allocated is sufficient for the existing load as well as the increase in workload?
  CPU is altogether would apply us we can generate on the CPU. If the load is low, I assumed is quite safe to increase the connection.
  Please share your experiences of dealing with this situation.
  
  Thank you

  Chewy wrote:
  How are we able to know if the memory allocated is sufficient for the existing load as well as the increase in workload?

  There are a set of views memory Advisor which will tell you if your memory structures of appropriate size:
  v$ db_cache_advice
  v$ shared_pool_advice
  v$ java_pool_advice
  v$ sga_target_advice
  v$ pga_target_advice
  --
  John Watson
  Oracle Certified Master s/n
  http://skillbuilders.com

• The amount of memory actually are used? db_32k_cache_size

  Hello world
  
  Using Oracle 10 g on RHEL 5.3.
  
  I was invited to check the amount of memory actually used by our db cache. Currently, we use the parameters db_32k_cache_size (defined by the user) and db_8k_cache_size (default), both allocated with 12 GB. Now I want to know if it is possible to find how on the 12 GB are actually used by the cache.
  
  Is this possible?
  
  Thank you

  make you view tips help available in oracle.
  V$ SGA_TARGET_ADVICE
  V$ DB_CACHE_ADVICE

• The SGA Advisor

  Hello
  in 10g R2, we can find what is advised on Dbconsole (DBCONTROLE) on BMG (Advisor Consultant Central/memory / SGA tab advice) in a table with a query?
  
  In fact, in Performance Tuning Guide, I found the following to the size of the cache:

  COLUMN size_for_estimate FORMAT 999,999,999,999 heading 'Cache Size (MB)'
  COLUMN buffers_for_estimate FORMAT 999,999,999 heading 'Buffers'
  COLUMN estd_physical_read_factor FORMAT 999.90 heading 'Estd Phys|Read Factor'
  COLUMN estd_physical_reads FORMAT 999,999,999 heading 'Estd Phys| Reads'
  SELECT size_for_estimate, buffers_for_estimate, estd_physical_read_factor, estd_physical_reads
  FROM V$DB_CACHE_ADVICE
  WHERE name = 'DEFAULT'
  AND block_size = (SELECT value FROM V$PARAMETER WHERE name = 'db_block_size')
  AND advice_status = 'ON';

  Thank you.

  Hello

  There are a lot of views that you can use the tuning of the SGA as advisers.

  below there are views the tuning of a specific area in the SGA.

  V$DB_CACHE_ADVICE
  V$SHARED_POOL_ADVICE
  V$JAVA_POOL_ADVICE
  V$STREAMS_POOL_ADVICE
  

  below it is a view that can help you deal with BMG.

  V$SGA_TARGET_ADVICE
  

  You can query the Dictiorary to find all of the Councillors views

  SELECT table_name
     FROM dict
        WHERE table_name LIKE '%ADVICE%';
  

  HTH - johnxjean-