Database Administration (MOSC)

MOSC Banner

Why do some of my MAXIMO databases on Oracle 19c databases have lots of hidden parameters set?

in Database Administration (MOSC) 3 commentsAnswered ✓

Is it possible a combination of a recent Oracle patch and a certain release of IBM's Maximo application has enabled these hidden settings? I provide most of the DBA support for Maximo and would know if they were intentionally changed.

_always_anti_join = "CHOOSE"
_always_semi_join = "CHOOSE"
_bct_public_dba_buffer_size= 3899328
_bloom_serial_filter = "ON"
_b_tree_bitmap_plans = TRUE
_complex_view_merging = TRUE
_compression_compatibility= "19.0.0.0"
_diag_adr_trace_dest = "/oracle/diag/rdbms/mmxmnt/mmxmnt/trace"
_ds_xt_split_count = 1
_eliminate_common_subexpr= TRUE
_fast_full_scan_enabled = TRUE
_generalized_pruning_enabled= TRUE
_gs_anti_semi_join_allowed= TRUE

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center