HOW TO DISABLE HINTS FROM BEING AUTOGENERATED IN MAPPING SQL CODE

Question

Hi Everybody,
1. the customer has 2 environments of OWB . production and dev.
2. In the production, in every SQL a /*+ no_merge */ hint is generated, which can cause loss of performance
3. In development the hint is not generated.
4. note:577544.1 is described how to change this behaviour for a single mapping.
How can I change this without manually changing every single mapping as described in the Note:577544.1 ? or can we change it using one OMBPLUS command for all mappings
Best regards,
Ashraf Hussein

Answer 1

Hi Ashraf
You can use OMB to do this kind of tedious work by changing a single map like the following;
To switch off automatic hints:
OMBALTER MAPPING '$map' MODIFY OPERATOR '$tablename' SET PROPERTIES (AUTOMATIC_HINTS_ENABLED) VALUES ('FALSE')
To blank out extraction hints for a table:
OMBALTER MAPPING '$map' MODIFY OPERATOR '$tablename' SET PROPERTIES (EXTRACTION_HINT) VALUES ('')
To blank out loading hints for a table:
OMBALTER MAPPING '$map' MODIFY OPERATOR '$tablename' SET PROPERTIES (LOADING_HINT) VALUES ('')
you can do something like the following to get all the mappings in a module and perform the
set maps \[OMBLIST MAPPINGS\]
foreach map $maps {
puts "Processing map $map"
# Do your alters here or may retrieve table operators etc.. to process each table
# for example....
set tables \[OMBRETRIEVE MAPPING '$map' GET TABLE OPERATORS\]
foreach table $tables {
puts "Processing map / table: $map / $table"
# Do your generic table operator processing here
Cheers
David