1171650 - Automated Oracle DB Parameter Check

25.04.2012 Page 1 of 13

SAP Note 1171650 - Automated Oracle DB parameter check

Note Language: English Version: 108 Validity: Valid Since10.04.2012

Summary

SymptomYou want the system to automatically check the Oracle DB parameter.In doing so, the system must compare the current recommendations of therelevant parameter note (depending on the Oracle release, patch set and/orsystem type) with the actual DB parameters.

Other termsParameter check, Oracle

Reason and PrerequisitesYou are using Oracle Release 8.1, 9.2., 10.1., 10.2. or 11.2.

The system type (OLAP, OLTP) is known:

o OLAP system: These are systems with mainly BW functions (BW / BI,APO with mainly DP usage, SEM-BPS, BW-based SEM-BCS).

o OLTP system: Systems with mainly non-BW functions (this alsoincludes, for example, Bank Analyzer systems and systems with apure Java stack)

Configure double stack systems (that is, systems with both ABAP stacks andJAVA stacks) as you would an OLTP or OLAP system, depending on the degree to which youuse BW functions (see above).

SolutionThree SQL statements are attached to this note.

o parameter_check_101_or_lower.txtfor Oracle Releases 8.1, 9.2, and 10.1.

o parameter_check_102.txtfor Oracle Release 10.2.

o parameter_check_112.txtfor Oracle Release 11.2.

They can be executed using:

o The SQL Editor in ST04N or in the DBA Cockpit of the system to bechecked.

o The SQL Editor in ST04N or in the DBA Cockpit of a system (forexample, Solution Manager) to which the system to be checked isconnected in accordance with Note 1256322. If required, thisenables you to avoid the restrictions of the SQL Editor (see thenotes below) in the system to be checked.

25.04.2012 Page 2 of 13


o The report RSORADJV

o SQLPLUSTo ensure an acceptable output with SQLPLUS, execute the followingSQLPLUS commands in advance

set linesize 360set pagesize 1000COLUMN name FORMAT a40COLUMN set FORMAT a8COLUMN remark FORMAT a60COLUMN recommendation FORMAT a120COLUMN is_value FORMAT a50COLUMN should_be_value FORMAT a50

You can execute the relevant statement without adjustments for OLTPsystems. For OLAP systems, you need to replace the string '<OLAP System?[n]>' with 'y'. Depending on the statement, the string may occur severaltimes.

Example for the replacement for OLAP systems (as mentioned above, severalreplacements may be required):before: ... substr(upper('<OLAP System? [n]>'),1,1),'Y','B','R' ...after: ... substr(upper('y'),1,1),'Y','B','R' ...

The statement is maintained synchronously to the parameter notes.The system automatically checks whether the current parameterization iscorrect and issues a recommendation or an "OK" for

o Each official parameter

o Each underscore parameter that is recommended

o Each underscore parameter that is set but not recommended

The recommendations are organized according to the type of recommendation.After the first "OK", there are only "OK"s.

Since there are some checks that either cannot be implemented or that arevery time-consuming to implement in an individual SQL statement, you mustmanually check the remaining parameters. The error message is then:

o check if value ... is suitable

o automatic check ok; doublecheck if value ... is suitable

o check if default value ... is suitable

o automatic check ok; doublecheck if default value ... is suitable

o check why set but not mentioned in note

You can use the statements on all of the Oracle releases mentioned above.The system determines the release except for the patch level. As a result,generally, the system cannot automatically check patch-dependent parameterswithin a patch set. The optimizer merge fixes as of Oracle 10.2 are anexception to this. The optimizer merge fix level (and therefore also the

25.04.2012 Page 3 of 13


parameters that only have to be set as of or up to a certain optimizermerge fix level) can be checked automatically and is checked automatically.

Remarks

o Old versions of the SQL editor in ST04N or in the DBA Cockpit orold versions of the report RSORADJV may have execution problems andmay report Oracle syntax errors or, particularly with Basis Release6.20, may report "The length of the current statement is greaterthan the maximum statement length", even if the statement has acorrect syntax. These old versions break statement lines atincorrect places and result in syntax errors or cannot deal withSQL statements greater than approximately 30KB. If an error occurs,try to use the other two options. If there is no SQL Plus accessand if the SQL editor reports a statement that is too long, as aworkaround, you can shorten the statement, for example, by removingall lines with _FIX_CONTROLS and EVENTS and their indentedsubsequent lines as follows:

||'_FIX_CONTROL... ||'... ||'...

or

||'EVENT,... ||'...

It may be possible to execute a statement that is shortened in thisway, but it does not return valid recommendations for _FIX_CONTROLand EVENT. Therefore, a new execution must be performed, but thistime other parameters must be removed and the _FIX_CONTROLparameters and EVENT parameters must be retained so that theirrecommendation is generated.

For extremely old editors, execution is not guaranteed after futureenhancements of the statement. The statement must then be executedin SQL Plus. This variant will work.An actual syntax error occurs only if the error occurs in SQL Plusitself.

o New versions of the SQL editor in ST04N or in the DBA Cockpit, andnew versions of the report RSORADJV may have execution problems andmay report"Oracle Diagnostics Package not licensed. See SAP-note 1028068" ORreturn the SID of the system as an uninformative error message.The reason for this is that the system also accesses the dba_hist_views when you execute the parameter check. These may be accessedonly if the Oracle diagnostic package is licensed. This is usuallythe case so that a relevant indicator can be set in accordance withNote 1028068. The parameter check then works.

o The parameter checks for Release 10.2 and 11.2 contain informationin the output header about whether or not certain parameters werechecked reliably. This is normally the case ("passed"). If thesystem displays a "FAILED" case, note the following:

- Event

25.04.2012 Page 4 of 13


In systems in which several events are separated using ':', areliable event check cannot be performed because SQL cannot beused to read all events if the value string is longer than 512characters. For this reason, you should not use the ':' syntax.Instead, use one of the following options:

To assign several values to the event parameter ininit<sid>.ora, use the following syntax (recommended):Event='<value 1>'...Event='<value n>'OREvent='<value 1>',...,'<value n>'Do NOT use:Event='<value 1>:...:<value n>'

To assign several values to the event parameter inspfile<sid>.ora, use the following syntax:Alter system set EVENT='<value 1>',...,'<value n>'scope=spfile;Do NOT use:Alter system set EVENT='<value 1>:...:<value n>' scope=spfile;

- _fix_controlAlthough _fix_control parameters are set and are correctlydisplayed, Oracle may ignore the settings due to a bug. Thecheck displays whether the bug is relevant or not. For moreinformation about this problem, see Note 1454675.

- RAC/11.2.0.2In RAC systems with releases lower than 11.2.0.2 and 11.2.0.3,the system may generate incorrect recommendations for some RACinstances. This problem is caused by an Oracle bug. This bug isfixed for both patch sets as of March SBP. As long as thesystem displays a RAC bug warning, the SBP is not implementedand the relevant recommendations have to be checked againmanually.

o A recommendation is issued for sizing parameters"automatic check ok; doublecheck if ... is suitable"This recommendation is principally equivalent to"check if ... is suitable"However, certain system-specific heuristics have been met thatindicate that the value has probably been set. For this reason, adifferent recommendation is made. A manual (double)check is stillrequired. Parameters and heuristics are:

- parallel_max_servers= CPU_COUNT*10

- pga_aggregate_targetMaximum used memory since startup between 75% and 90% ofpga_aggregate_target

- processesMaximum processes since DB start <= 75% of processes

- sessions

25.04.2012 Page 5 of 13


Maximum sessions since DB start <= 75% of sessions

- shared_pool_sizeParameter value between 50% and 200% of the value calculatedwith the formula in note 690241

- undo_retentionunexpired stolen blocks since in v$undostat = 0

o Oracle 11: The "SAP Bundle Patch" line in the header of the outputcontains information about the MINIMUM SAP Bundle Patch level thatexists in the system. Note:

- Not every SAP Bundle Patch changes the content ofv$system_fix_control. Therefore, the current version of themerge fix cannot always be queried uniquely using SQL. The SAPBundle Patch that is contained in the system may therefore alsobe newer than displayed.

- Some fixes of a SAP Bundle Patch can be activated by importingthe complete SAP Bundle Patch online, in other words, while thedatabase is running. This way the errors that can be patchedonline can be corrected before an offline patching withoutdowntime. In the period between the online patching and theoffline patchingm the automatic parameter check may issueincorrect recommendations because the system cannot identifythe SAP Bundle Patch clearly. If you import patches online,manually check SAP-Bundle-Patch-dependent parameters from Note1431798. If in doubt, set the parameters as they would have hadto be set before the import of the SAP Bundle Patch.

Change history parameter_check_112.txt/parameter_check_102.txt:

o 11.04.2012

- 11.2: Parameter adjustments in accordance with SAP Note/Version1431798/49; heuristic adjustments for parametershared_pool_size tot he formula from SAP Note 690241; no moreaccess to dba_hist views, so the parameter check can also beused on DBs, on which the diagnostic package is not licensed.Correction of the incorrect parameter recommendation for_optim_peek_user_binds in Version 30.3.2012

- 10.2: Checkscript in accordance with SAP Note/Version830576/222; heuristic adjustments for parametershared_pool_size tot he formula from SAP Note 690241; no moreaccess to dba_hist views, so the parameter check can also beused on DBs, on which the diagnostic package is not licensed.

o 30.03.2012

- 11.2: Parameter adjustments in accordance with SAP Note 1431798Version 48; March SAP Bundle Patch (11.2.0.2 and 11.2.0.3) isrecognized

- 10.2: Check script is synchronized with SAP Note/Version830576/222 (no change)

25.04.2012 Page 6 of 13


o 24.02.2012

- 11.2: Parameter adjustments in accordance with SAP Note 1431798Version 47; February SAP Bundle Patch (11.2.0.2 and 11.2.0.3)is recognized

- 10.2: Parameter adjustments in accordance with Note/Version830576/222

o 18.01.2012

- 11.2: Parameter adjustments in accordance with SAP Note 1431798Version 46; January SAP Bundle Patch (11.2.0.2) is recognized

- 10.2: Check script is synchronized with SAP Note 830576 Version221 (no change)

o 22.12.2011

- 11.2: Parameter adjustments in accordance with SAP Note 1431798Version 45; Oracle 11.2.0.3 parameter check available; DecemberSAP Bundle Patch (11.2.0.3) is recognized; warning for Oraclepatch sets for which bundle patches are no longer created or ifRAC is used in 11.2.0.2 (bug that has not been fixed causingincorrect values)

- 10.2: Parameter adjustments in accordance with SAP Note 830576Version 221; warning for Oracle patch sets for which ExtendedSupport is no longer provided (Release 10.2.0.4 or lower; SAPNote 1339724); warning for Oracle patch sets that are notsupported, for which the parameter note is no longermaintained, for which only Extended Support is available or forOracle patch sets that can be patched only if you purchasedExtended Support (Release 10.2.0.5 or higher; SAP Note 1654734)

o 15.11.2011



o 26.10.2011

- 11.2: HotNews parameter change contained in Note 1431798/40requires a change to the script; information section at thestart of the statement output contains the bug number fromV$SYSTEM_FIX_CONTROL-BUGNO that was used to identify the SAPbundle patch; check script is synchronized with Note/Version1431798/40.

- 10.2: Check script is synchronized with Note/Version 830576/218(no change)

o 13.10.2011

25.04.2012 Page 7 of 13


- 11.2: Optimizer merge fix from October: Patch bundle isrecognized (11.2.0.2); check script is synchronized withNote/Version 1431798/38

- 10.2: Check script is synchronized with Note/Version 830576/218(no change)

o 26.09.2011

- 11.2: Parameter adjustments in accordance with Note/Version1431798/36; shared_pool, open_cursors parameter is checked indetail (in particular in RAC); pseudo warnings are no longerissued for dynamically changed NLS parameters

- 10.2: Parameter adjustments in accordance with Note/Version830576/218; shared_pool, open_cursors parameter is checked indetail (in particular in RAC)

o 12.08.2011

- 11.2: Optimizer merge fix from August: Patch bundle isrecognized (11.2.0.1, 11.2.0.2); check script is synchronizedwith Note/Version 1431798/35

- 10.2: Warning for Version 10.2.0.2. with regard to parametercheck desupport because the underlying parameter note 830576 isno longer maintained for Version 10.2.0.2; check script issynchronized with Note/Version 830576/217.

o 19.07.2011


o 15.06.2011

- 11.2: Parameter adjustments in accordance with Note/Version1431798/34. Optimizer merge fix from June patch bundle isrecognized (11.2.0.2)

- 10.2: Optimizer merge fix from June patch bundle is recognized(10.2.0.4 and 10.2.0.5)

o 31.05.2011

- 11.2: Parameter adjustments in accordance with Note/Version1431798/33Optimizer merge fix from May patch bundle is recognized(11.2.0.1 and 11.2.0.2)

- 10.2: Parameter adjustments in accordance with Note/Version830576/216. Optimizer merge fix from May patch bundle isrecognized (10.2.0.4 and 10.2.0.5)

o 21.04.2011

- Adjustment to extensive parameter note changes

25.04.2012 Page 8 of 13


- 11.2: Parameter adjustments in accordance with Note/Version1431798/31. Optimizer merge fix from March patch bundle isrecognized (11.2.0.2)

- 10.2: Parameter adjustments in accordance with Note/Version830576/214. Optimizer merge fix from April patch bundle isrecognized (10.2.0.4)

o 22.02.2011

- ABAP stack and ASM systems are recognized.


- 10.2: Parameter adjustments in accordance with Note/Version830576/211. Optimizer merge fix from February patch bundle isrecognized (10.2.0.4)

o 12.01.2011



o 14.10.2010


- 10.2: Parameter adjustments in accordance with Note/Version830576/205. Optimizer merge fix from October patch bundle isrecognized

o 13.09.2010


- 10.2: Optimizer merge fix from September: Patch bundle isrecognized (synchronized with Note/Version 830576/204)

o 10.08.2010

- 11.2: No parameter adjustments; check script is synchronizedwith Note /Version 1431798/12.


o 10.07.2010

- 11.2: Optimizer merge fix from June: Patch bundle is recognized(synchronized with Note/Version 1431798/12)

25.04.2012 Page 9 of 13


- 10.2: Optimizer merge fix from July: Patch bundle isrecognized; parameter adjustments in accordance withNote/Version 830576/202

o 10.06.2010



o 10.05.2010



- Adjustments of the merge fix output to the SAP bundle patches

- Implementation of two new columns that contain additionalinformation about the parameter classification

U)sage - provides information about what is influenced by theparameter"p": Performance"f": Functions" ": No further classification

I)mportance - ROUGH indicator of the extent to which theparameter influences the database behavior"1": Extreme effects, for example, performance parameters thataffect most of the queries or functional parameters that mustbe set due to Hot News notes."2"/"3": Strong effect, for example performance parameters thataffect specific queries" ": No further classification

The following still applies: ALL parameters must be set inaccordance with the parameter note. The I)mportance is only anINDICATOR for the urgency. Only parameters that are included inparameter notes are classified. For parameters that have notbeen tested by SAP, the importance or usage cannot bespecified.

o 10.04.2010


- 10.2: No parameter adjustments; check script is synchronizedwith Note /Version 830576/197.

- In addition, the INFORMATION section contains the DB SID.

25.04.2012 Page 10 of 13


- In addition, the INFORMATION section contains information aboutwhether the _fix_control check could be reliably executed (seeabove).

- Minor changes in text output

- The "add" recommendation is suppressed in case of dynamicallychanged underscores or _fix_control parameters.

o 10.03.2010

- No changes (check scripts are consistent with parameter noteand patch note)

o 10.02.2010

- 11.2: Initial version

- Correct recommendation for _CURSOR_FEATURES_ENABLED

- Correct recommendation if the _fix_control value is specifiedin the format'<fix 1>:<VALUE 1>, ..., <fix n>:<VALUE n>'instead of in the recommended format'<fix 1>:<VALUE 1>', ..., '<fix n>:<VALUE n>'

o 10.01.2010

- Parameter adjustment in accordance with Note 830576 (Version193).

o 20.12.2009

- The optimizer merge fix 10.2.0.4/16 is recognized

- Warning if the number of data files in the database is greaterthan 90% of the parameter db_files

- There is no division by 0 if incorrect parameter settings areused.

o 10.12.2009

- No changes (Check script is consistent with parameters andpatch note)

o 10.11.2009


o 10.10.2009

- The optimizer merge fix 10.2.0.4/15 is recognized

- Parameter adjustment in accordance with Note 830576.

25.04.2012 Page 11 of 13


o 10.09.2009


o 10.08.2009

- Workaround for the SQL editor problem:The ORA-00909 problem in old editors (for example, 6.20/SupportPackage 63) is solved using a line break with themultiplication sign and by interpreting the leading "*" as acomment character.

o 23.07.2009

- Workaround for the SQL editor problem:Solution of the problem of long statement length in oldeditors (Functional enhancements of the check statementexceeded the maximum statement length again in the old editors)

- Optimizer merge fix 10.2.0.4/14 is recognized (will bepublished on August 10, 2009)

o 10.07.2009


- Parameters that were changed using "alter system set ...scope=memory" are listed at the beginning of the parameterlist. No recommendations are specified for these parameters.

- For the merge fix level, the date on which the merge fix wasreleased is displayed. This enables you to easily check theinitial date of the optimizer source code in the customersystem.

o 10.06.2009

- Parameter adjustments in accordance with Note 830576

o 10.05.2009


o 29.04.2009

- Use an outer join statement for gv$undostat join. Otherwise,the recommendations when using manual undo management are asfollows:"check why set but mentioned with other prerequisites/notmentioned in note".

o 21.04.2009

- Parameter correction for Windows (_fix_control 6660162:ON onlyon Unix to be set)

25.04.2012 Page 12 of 13


o 10.04.2009


o 23.03.2009

- Workaround for the SQL editor problem:Solution of the problem with long statement length in oldeditors

o 10.03.2009


- RAC enabling

- Heuristics for sizing parameters

Header Data

Release Status: Released for CustomerReleased on: 10.04.2012 14:59:45Master Language: GermanPriority: Recommendations/additional infoCategory: Installation informationPrimary Component: BC-DB-ORA Oracle

Secondary Components:BW-SYS-DB-ORA BW ORACLE

SV-BO-DB-ORA Oracle Performance Problems

The Note is release-independent

Related Notes

Number Short Text

1681396 Query Performance

1641320 NLS* parameters are marked as 'MODIFIED' in V$PARAMETER

1342593 Account search: Performance issue with name and address

830576 Parameter recommendations for Oracle 10g

212986 Required data for processing CBO/RBO problems

25.04.2012 Page 13 of 13


Attachments

FileType

File Name Language Size

TXT parameter_check_102.txt E 36 KB

TXT parameter_check_112.txt E 33 KB

TXT parameter_check_101_or_lower.txt E 36 KB

Documents

1171650 - Automated Oracle DB Parameter Check