Once the underlying data source has established a relationship between the User ID and the data it has access to, it’s time to think about how to display user specific data in the report.There are two ways of displaying user specific data: This example demonstrates using both the options to display user specific data.Here is a common list of some of the undocumented parameters:_allow_resetlogs_corruption _column_tracking_level _db_aging_cool_count _db_aging_freeze_cr _db_aging_hot_criteria _db_aging_stay_count _db_aging_touch_time _db_percent_hot_default _db_percent_hot_keep _db_percent_hot_recycle _init_sql_file _kghdsidx_count _log_io_size _realfree_heap_pagesize_hint _recyclebin _small_table_threshold _system_trig_enabled _trace_files_public _use_ism _use_ism_for_pga _wait_for_sync _NUMA_pool_size = 536870912 _collect_undo_stats=false _awr_restrict_mode=true _db_writer_flush_imu=false _db_cache_pre_warm=FALSE _undo_autotune = false _imu_pools = 358 _optimizer_cache_stats = false _optimizer_cost_model = io _cursor_cache_frame_bind_memory = true _db_writer_coalesce_area_size = 16777216 _kghdsidx_count = 1 _ksmg_granule_size=268435456 _two_pass=false _session_idle_bit_latches=3000Many savvy Oracle professionals commonly adjust the hidden parameters to improve the overall performance of their systems.However, because these are "undocumented" parameters, most Oracle professionals rely on publications such as "Oracle Internals" to get insights into the proper setting for the hidden parameters.Queries that happened a month ago are probably no longer useful now.So if it's storing those query results then it's completely worthless because chances are no one is going to run that same exact query again.If I understand correctly, every insert or update will clear the cache for that table?That's what my searching online has found, I don't know if that's true though or if I should be regularly reseting the cache.
Retrieving user-specific data requires the underlying data source to have a relationship between users and the data they have permission to view.
I'm discounting #38551 as this happened more than once since after turning the query cache off.
Unfortunately the thread finally ended so I can't checkout whether #59899 is related or not.
OPQ is an amazing facility for improving the speed of large-table full-table scans, and some DBAs are not aware that there are a dozen hidden parameters that can be changed to affect the behavior of parallel queries.
Earl Shaffer provides this query to display the parameters.