- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
Adding an extra parameter annotation or comment
Hello, my guys and friends ,
When finished tackling the problem by Why client_info in v$session never show IP address even if creating trigger acquiring IP? and https://asktom.oracle.com/pls/apex/f?p=100:11:116156836395685::::P11_QUESTION_ID:9543192700346829856 I realised that the value of the hidden parameter "_system_trig_enabled" existing on the oracle database had been modified by the former DBA (the default values is TRUE).
So far I don't know the reason why he modify it even if I am able to find out the alter statement on the ALERT log file. Hence I abruptly have a nice idea in my mind - expecting to add an extra parameter annotation or comment on the alter statement, such as, "ALTER SESSION/SYSTEM SET hidden_parameter_name=true/false SCOPE=SPFILE/MEMORY/BOTH annotation/comment=......" in particular setting the boolean value of the hidden parameter on the future new version of oracle database as a NEW FEATURE to enhance/improve the function.
Very simple, with the annotation or comment to have a detailed explanation why you modify the value of hidden parameter.