17 Replies Latest reply: Jun 28, 2012 5:50 PM by João Dimas RSS

Database Check and Parameter_check_102

M. Abdul Jamil
Currently Being Moderated

Dear Oracle Expert,

When I execute database_check via DB02 then getting Warning against following Parameters.

 

DBO    ARCHIVE_TOO_OLD  1    Operation: 'Archive log backup' has not been run # Operation too old or has not been run in clean-up period
PROF    LOG_BUFFER  1    Value: 14238720 (>< 4096,512 KB) # Size of redo log buffer in bytes
PROF    OPTIMIZER_INDEX_COST_ADJ  1    Value: 20 (set in parameter file) # Optimizer index cost adjustment
PROF    STATISTICS_LEVEL  1    Value: TYPICAL (set in parameter file) # Statistics level
ORA    Checkpoint not complete  100    Time: Stan-04-09 11.15.52, line: Checkpoint not complete

 

while I have configured mostly parameter in initSID.ora file but still confuse about following parameters.

Parametercheck for Oracle 10.2. based on Note/Version: 830576/222

Parametercheck last changed: 2012-04-10

Parametercheck Execution: 2012-04-11 15:55:00

DB Startup: 2012-04-11 11:09:27

DB SID: PRD

DB Environment: OLTP, not RAC

DB Platform: Microsoft Windows x86 64-bit

DB Patchset: 10.2.0.5.0

Last detectable DB Mergefix: from SAP Bundle Patch (released 2011-06-10)

Reliability checks: events passed, _fix_controls passed

WARNING: Extended support for 10.2.0.5 only available with a special extended support contract (note 1431752)

 

ParameterIS_VALUESHOULD_BE_VALUE
event (10411)
set with level 1 if Winbundle>=3
_b_tree_bitmap_plans
set to FALSE if Winbundle<=2
db_writer_processes4change default in case of dbwr problems only
_fix_control (4728348)4728348:OFFset to 4728348:OFF if Winbundle<=5
_first_spare_parameter1set to 1 if Winbundle>=3

please find attached file parameter_check_102 for remaining parameter which i did set in initSID.ora file.

would anyone guide me about the exact value of above parameters and meaning of Winbundle?


Regards,

  • Database Check and Parameter_check_102
    Leopoldo Capasso
    Currently Being Moderated

    Hi,

    Winbundle should correspond to the version of the SAP Bundle Patch. Which version of this Oracle Patch did you apply?

    regarding parameter db_writer_processes, a SAP guideline is to set this parameter to this value:

    number of CPU Cores \ 6

    In a non-production environment, set to 1.

    Regards

    Leo

    • Re: Database Check and Parameter_check_102
      M. Abdul Jamil
      Currently Being Moderated

      Dear,

      I am getting following error.

      SQL> select BUNDLE_SERIES,VERSION from DBA_REGISTRY_HISTORY;

      select BUNDLE_SERIES,VERSION from DBA_REGISTRY_HISTORY

             *

      ERROR at line 1:

      ORA-00904: "BUNDLE_SERIES": invalid identifier

      while I have install the oracle and applied Oracle patches with this sequence on Window Server 2008.

      1. ORACLE10.2.0.4FailsafeServer3.4.1.5Windows2008(51036975)

      2. ORACLE_Patch_10.2.0.5_LINUX__Windows (51040057_4)

      3. opatch-102051 (old_OPatch_10205_Generic_v0)

      4. Generic patch

      p8350262_10205_Generic

      p9445675_10205_Generic

      p9843740_10205_Generic

      p10357961_10205_Generic

      p10431010_10205_Generic

      p13617518_10205_Generic

       

      5. MSWIN

      p12914913_10205_MSWINx8664

      Latest_p13460968_10205_MSWINx86 (old_p12429524_10205_MSWINx8664)

       

      while the value of db_writer_processes  on PRD server is:

      SQL> show parameter cpu_count;

       

      NAME                                 TYPE        VALUE

      ------------------------------------ ----------- ------

      cpu_count                            integer     32  (Processor_HyperThreading)

       

       

      Regards,

      • Re: Database Check and Parameter_check_102
        Leopoldo Capasso
        Currently Being Moderated

        Hi,

        this is an example of a query to determine which bundle patch is installed:

         

         

        SQL> select action_time, version, bundle_series, comments from dba_registry_history where bundle_series = 'SBP' order by action_time  desc;

         

         

        ACTION_TIME

        ---------------------------------------------------------------------------

        VERSION                        BUNDLE_SERIES

        ------------------------------ ------------------------------

        COMMENTS

        --------------------------------------------------------------------------------

        18-OCT-11 12.16.14.302751 PM

        10.2.0.4                       SBP

        SBP 10.2.0.4.9 201109 containing CPUJul2011

        I suppose that you didn't apply correctly the Bundle Patch. So i suggest you do download the very latest patch ( 10205_Patch14_MSWIN-x86-64.zip ) , and to apply it reading carefully the readme file attached.

        Check this note for more info:

        1431752  Oracle 10.2.0: Patches/Patch Collections for 10.2.0.5

        Regarding db_writer_processes parameter, 4 should be a good value.

        Regards

        Leo

        • Re: Database Check and Parameter_check_102
          M. Abdul Jamil
          Currently Being Moderated

          hi leopoldo,

          10205_Patch12_MSWIN-x86-64.zip 10.11.2011 91487
          10205_Patch14_MSWIN-x86-64.zip 14.02.2012 91984
          p10357961_10205_Generic.zip 13.07.2011 107
          p13617518_10205_Generic.zip 13.03.2012 1394
          p9445675_10205_Generic.zip 13.07.2011 16
          p9584028_102050_Generic.zip 20.07.2011 63
          p9843740_10205_Generic.zip 12.04.2011 34

           

          Patch (p13460968_10205_MSWINx86) is latest and i have already applied.

          .

          You can find the status of above patch in OPatch's log.

           

          E:\oracle\PRD\102\OPatch>opatch lsinventory

          ========================================================

          GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY

          ========================================================

          Invoking OPatch 10.2.0.5.0

           

          Oracle Interim Patch Installer version 10.2.0.5.0

          Copyright (c) 2010, Oracle Corporation.  All rights reserved.

           

           

          Oracle Home       : E:\oracle\PRD\102

          Central Inventory : C:\Program Files\Oracle\Inventory

             from           : n/a

          OPatch version    : 10.2.0.5.0

          OUI version       : 10.2.0.5.0

          OUI location      : E:\oracle\PRD\102\oui

          Log file location : E:\oracle\PRD\102\cfgtoollogs\opatch\opatch2012-04-06_14-49-

          36PM.log

           

          Patch history file: E:\oracle\PRD\102\cfgtoollogs\opatch\opatch_history.txt

           

          Lsinventory Output file location : E:\oracle\PRD\102\cfgtoollogs\opatch\lsinv\ls

          inventory2012-04-06_14-49-36PM.txt

           

          --------------------------------------------------------------------------------

           

          Installed Top-level Products (2):

           

          Oracle Database 10g                                                  10.2.0.4.0

          Oracle Database 10g Release 2 Patch Set 4                            10.2.0.5.0

          There are 2 products installed in this Oracle Home.

           

           

          There are no Interim patches installed in this Oracle Home.

           

           

          --------------------------------------------------------------------------------

           

           

          OPatch succeeded.

           

          ----------------------------------

           

          E:\oracle\PRD\102\OPatch>opatch lsinventory

          ========================================================

          GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY

          ========================================================

          Invoking OPatch 10.2.0.5.1

           

          Oracle Interim Patch Installer version 10.2.0.5.1

          Copyright (c) 2010, Oracle Corporation.  All rights reserved.

           

           

          Oracle Home       : E:\oracle\PRD\102

          Central Inventory : C:\Program Files\Oracle\Inventory

             from           : n/a

          OPatch version    : 10.2.0.5.1

          OUI version       : 10.2.0.5.0

          OUI location      : E:\oracle\PRD\102\oui

          Log file location : E:\oracle\PRD\102\cfgtoollogs\opatch\opatch2012-04-06_15-09-

          19PM.log

           

          Patch history file: E:\oracle\PRD\102\cfgtoollogs\opatch\opatch_history.txt

           

          Lsinventory Output file location : E:\oracle\PRD\102\cfgtoollogs\opatch\lsinv\ls

          inventory2012-04-06_15-09-19PM.txt

           

          --------------------------------------------------------------------------------

           

          Installed Top-level Products (2):

           

          Oracle Database 10g                                                  10.2.0.4.0

          Oracle Database 10g Release 2 Patch Set 4                            10.2.0.5.0

          There are 2 products installed in this Oracle Home.

           

           

          Interim patches (5) :

           

          Patch  13460968     : applied on Fri Apr 06 15:08:50 ACT 2012

          Unique Patch ID:  14454232

             Created on 06 Jan 2012, 02:45:06 hrs

             Bugs fixed:

               13460968, 10103086, 9885553, 9393307, 11858315, 11657004, 11893577

               11693109, 6157713, 7111619, 7119382, 7361418, 8636407, 8650138, 9072105

               9171933, 9586877, 9672816, 9842573, 10076669, 10092858, 10139235

               10355949, 10027403, 9628444, 6337376, 9373370, 9083321, 13349665, 8478250

               9268192, 10353128, 11715752, 13429845, 13401655, 12914913, 10097176

               9545597, 11840910, 6011045, 7509714, 8354642, 8488233, 9322219, 9499302

               9767674, 10208905, 10214450, 10162036, 12565867, 12794025, 12799034

               9187546, 7115910, 9399589, 9386687, 12310567, 12421252, 5245039, 10244177

               8298501, 9431650, 10165083, 9926087, 7710224, 10350832, 12739299

               12807343, 12429524, 11066597, 9935787, 10236704, 11853331, 9825461

               8411930, 6651220, 7026523, 8882576, 9360157, 10068982, 10173237, 10324526

               8332730, 7516536, 11814891, 9871302, 6055658, 12363485, 10220194

               7592673, 10202758, 9735237, 10052339, 12332704, 8666117, 9145204

               9824435, 11703718, 7280234, 9269536, 10132870, 9094926, 9323583, 10144882

               9860769, 9488247, 10306945, 9532911, 9184754, 9656004, 8528171, 10191707

               8943287, 11727013, 10407744, 11930680, 8966823, 10160615, 10637621

               4672767, 5638228, 12328269, 11731166, 9215341, 10159846, 11076894

               10269717, 10091171, 9061785, 8211733, 8412426, 9020537, 9024850, 9150282

               10010310, 7602341, 8865718, 11737047, 11675644, 10111381, 9368502

               8660422, 9032322, 9295217, 10224187, 10080775, 9841679, 8977287, 10054513

               10220046, 9577583, 10352673, 8277300, 8394351, 8350262, 9949948, 9879181

               9469117, 10017048, 8771916, 10155684, 6694396, 10308274, 10312161

               10157402, 8434467, 9668086, 9980062, 6151936, 10091698, 8228796, 9699654

               10114856, 9978573, 10156303, 5575218, 9081686, 10196896, 10080735

               5519322, 6768114, 6904068, 7045446, 7452759, 7612454, 8684595, 8811401

               9109487, 9320130, 9337325, 9362218, 9390484, 9548269, 9770451, 10155844

               9047975, 8663644, 7708267, 6086930, 9539556, 9355794, 8264642, 9495669

               6975402, 9659614, 9387574, 9320786, 9793452, 9024737, 9196440, 8970313

               9308296, 9663844, 10099855, 6402302, 7519406, 8224558, 8487143, 8544696

               8546356, 8664189, 8996060, 9261837, 9577921, 9586637, 9646836, 9683239

               9711859, 9713537, 9714832, 9726739, 9747153, 9772888, 9870614

           

          Patch  13617518     : applied on Fri Apr 06 15:05:10 ACT 2012

          Unique Patch ID:  14610518

             Created on 23 Feb 2012, 11:07:13 hrs PST8PDT

             Bugs fixed:

               9569264, 8874882, 9760734, 9099863, 6670871, 8980899, 8588311, 9680387

               8980918, 13508485, 13090621, 9105438

           

          Patch  10357961     : applied on Fri Apr 06 14:53:06 ACT 2012

          Unique Patch ID:  13813456

             Created on 6 Jun 2011, 01:39:07 hrs PST8PDT

             Bugs fixed:

               10357961

           

          Patch  9843740      : applied on Fri Apr 06 14:52:28 ACT 2012

          Unique Patch ID:  13572258

             Created on 21 Mar 2011, 00:17:02 hrs PST8PDT

             Bugs fixed:

               9843740

           

          Patch  9445675      : applied on Fri Apr 06 14:51:49 ACT 2012

          Unique Patch ID:  13823676

             Created on 17 Jun 2011, 12:52:27 hrs PST8PDT

             Bugs fixed:

               9445675

          ------------------------------

          OPatch succeeded.

           

           

           

          Regards,

          • Re: Database Check and Parameter_check_102
            Leopoldo Capasso
            Currently Being Moderated

            Hi,

            according to output of OPatch lsinventory command, you have Bundle Patch n. 14.

            So you have to apply these parameters as follows:

             

            event (10411)          set with level 1 _b_tree_bitmap_plans     don't set _fix_control (4728348)     don't set _first_spare_parameter     already set to 1 as recommended  Regards Leo

            • Re: Database Check and Parameter_check_102
              M. Abdul Jamil
              Currently Being Moderated

              hi,,

              I am sharing some parameters of initSID.ora, please check the value of following parameters are OK???

               

              *._b_tree_bitmap_plans=

              *._disable_objstat_del_broadcast=FALSE

              *._first_spare_parameter=1

              *._fix_control='5099019:ON','5705630:ON','5765456:3','6055658:OFF','6399597:ON','6430500:ON','6440977:ON','6626018:ON','6670551:ON','6972291:ON',

              '7692248:ON','7891471:ON','9196440:ON','9495669:ON'

              *._OPTIM_PEEK_USER_BINDS=FALSE

              *._optimizer_mjc_enabled=FALSE

              *._sort_elimination_cost_ratio=10

              *.compatible='10.2.0'

              *.control_file_record_keep_time=30

              *.db_block_size=8192

              *.db_files=254

              *.dml_locks=4000

              *.event='10027 trace name context forever, level 1','10028 trace name context forever, level 1','10142 trace name context forever, level 1','10183 trace name context forever, level 1','10191 trace name context forever, level 1','10411 trace name context forever, level 1','10629 trace name context forever, level 32','14532 trace name context forever, level 1','38085 trace name context forever, level 1','38068 trace name context forever, level 100','38087 trace name context forever, level 1','44951 trace name context forever, level 1024'

              *.FILESYSTEMIO_OPTIONS='setall'

              *.job_queue_processes=1

              *.log_buffer=14238720

              *.log_checkpoint_interval=0

              *.log_checkpoints_to_alert=true

              *.max_dump_file_size='20000'

              *.open_cursors=800

              *.optimizer_index_cost_adj=20

              *.parallel_execution_message_size=16384

              *.parallel_max_servers=160 (cpu_count=32 but processor is supported Hyperthreading)

              *.parallel_threads_per_cpu=1

              *.processes=438

              *.query_rewrite_enabled='FALSE'

              *.REPLICATION_DEPENDENCY_TRACKING=FALSE

              *.sort_area_retained_size=0

              *.sort_area_size=2097152

              *.star_transformation_enabled='TRUE'

              *.statistics_level='TYPICAL'

              *.undo_management='AUTO'

              *.undo_retention=21600

              *.workarea_size_policy='AUTO'

               

              please correct/highlight the parameter which is not correct?

               

              Regards,

  • Re: Database Check and Parameter_check_102
    jagadish gudla
    Currently Being Moderated

    Hi..

     

    Please check the parameter recommendation note for SAP - Oracle 10g.

     

    Moreover please always set the parameters in spfile using the command alter system.....

     

    Then copy the pfile from spfile....

     

    Thanks,

    Jagadish.

  • Re: Database Check and Parameter_check_102
    Rachel Holloway
    Currently Being Moderated

    Hello Ma Jamil

     

    "WinnBundle" is the SAP Windows bundle.    What your parameter check tells you is to check the parameters against the oss note for your Oracle version to see what is missing/incorrectly set. 

    A script which can be run in dbacockpit ->sql editor or SE38 RSORADJV report will compare settings on your system to the relevant paramter note and flag any incorrect settings.  The parameter note is

    #830576 for 10g.

     

    The note is #1171650 - parameter check  (please read the note if you have a BI (OLAP) system as there is a change that needs to be made to the script before running.

     

    The note which explains the Bundle terms, etc is note # 1175996

     

    So to anwer your question the above parameters you flagged  for example should be set if the bundle patchset is greater or equal to 3 underlined  here

     

    event (10411)
    set with level 1 if Winbundle>=3
    _b_tree_bitmap_plans
    set to FALSE if Winbundle<=2
    db_writer_processes4change default in case of dbwr problems only
    _fix_control (4728348)4728348:OFFset to 4728348:OFF if Winbundle<=5
    _first_spare_parameter1set to 1 if Winbundle>=3

     

    To get the bundle output simply execute the following SQL statement

     

    select action_time, version, bundle_series, comments

    from dba_registry_history

    where bundle_series = 'WINBUNDLE'

    order by action_time desc

     

    SAP always recommends to run the parameter check script before and after upgrade, patch installation.

     

    Best Regards

    Rachel

    • Re: Database Check and Parameter_check_102
      M. Abdul Jamil
      Currently Being Moderated

      hi Rachel,

      thanks for your reply,

      Dear, the result of mentioned command.

      SQL> select action_time, version, bundle_series, comments from dba_registry_hist

      ory where bundle_series = 'WINBUNDLE' order by action_time desc;

      select action_time, version, bundle_series, comments from dba_registry_history w

      here bundle_series = 'WINBUNDLE' order by action_time desc

       

           *

      ERROR at line 1:

      ORA-00904: "BUNDLE_SERIES": invalid identifier

      while I already shared the OPatch status.

      and current status of Oracle is :

      SQL> select comp_name, version, status from sys.dba_registry;

       

      COMP_NAME

      -----------------------------------------------------------------

       

      VERSION                        STATUS

      ------------------------------ ---------------------------------

      Oracle Database Catalog Views

      10.2.0.5.0                     VALID

       

      Oracle Database Packages and Types

      10.2.0.5.0                     VALID

       

      the Parameter_Check_102

      Parametercheck for Oracle 10.2. based on Note/Version: 830576/222
      Parametercheck last changed: 2012-04-10
      Parametercheck Execution: 2012-04-16 19:43:13
      DB Startup: 2012-04-16 01:33:57
      DB SID: PRD
      DB Environment: OLTP, not RAC
      DB Platform: Microsoft Windows x86 64-bit
      DB Patchset: 10.2.0.5.0
      Last detectable DB Mergefix: from SAP Bundle Patch (released 2011-06-10)
      Reliability checks: events passed, _fix_controls passed

       

      ParameterSETIS_VALUESHOULD_BE_VALUE
      event (10411)N
      set with level 1 if Winbundle>=3
      _b_tree_bitmap_plansN
      set to FALSE if Winbundle<=2
      db_writer_processesN4change default in case of dbwr problems only
      _fix_control (4728348)Y4728348:OFFset to 4728348:OFF if Winbundle<=5
      _first_spare_parameterY1set to 1 if Winbundle>=3

       

      I am really confused about the exact value of above parameters and specially about WinBundle?

       

      Regards,

      • Re: Database Check and Parameter_check_102
        Bhavik G. Shroff
        Currently Being Moderated

        Hi,

         

        ERROR at line 1:

        ORA-00904: "BUNDLE_SERIES": invalid identifier

         

        From the provided information of init<SID>.ora, its looking like that you have not performed Post Installation steps bundle Patch 10.2.0.5 Patch 14. So complete all the listed/applicable post-installation instructions one by one as mentioned in README.html of bundle patch p13460968_10205_MSWINx86.

         

        As a part of post-installation,

        As per point 3.3.5.1 of README.html of bundle patch p13460968_10205_MSWINx86, You will require to perform the following additional actions,

         

        1. set event="8298501 trace name context forever, level 10"

        2. Execute catcpu.sql located at %ORACLE_HOME%\BUNDLE\Patch14

        3. Execute utlprp.sql  as per step 11 of point 3.3.5.1 (if required..)

         

        Then try to execute the below mentioned query,

        select action_time, version, bundle_series, comments from dba_registry_history  where bundle_series = 'WINBUNDLE' order by action_time desc;

        It will give you some output.

         

        I am really confused about the exact value of above parameters and specially about WinBundle?

         

        For Oracle Patch installation on Windows, the table filed bundle_series is maintained with word WINBUNDLE in table dba_registry_history.  WINBUNDLE is the similar term as SBP (SAP Bundle Patch). You can find more information about it in SAP Note 1175996

         

        As per the above SQL query, the query must report WINBUNDLE with Patch level 14. In your case WINBUNDLE level will be 14, so you need to set those Oracle parameters accordingly. You need to set following oracle parameters only.

         

        ParameterSETIS_VALUESHOULD_BE_VALUE
        event (10411)N
        set with level 1 if Winbundle>=3

         

        I hope the above information is helpful for your understanding.

         

        --

        Regards,

        Bhavik G. Shroff

        • Re: Database Check and Parameter_check_102
          M. Abdul Jamil
          Currently Being Moderated

          hi Bhavik,

          bundle of thanks to point out the issue. I updated the remaining commands now the status of said command is :

          SQL> select action_time, version, bundle_series, comments from dba_registry_hist

          ory  where bundle_series = 'WINBUNDLE' order by action_time desc;

           

          ACTION_TIME

          ---------------------------------------------------------------------------

          VERSION                        BUNDLE_SERIES

          ------------------------------ ------------------------------

          COMMENTS

          --------------------------------------------------------------------------------

           

          18-APR-12 11.04.35.156000 AM

          10.2.0.5                       WINBUNDLE

          Patch 14

          now what is the exact value of following parameters.

           

          ParameterIS_VALUESHOULD_BE_VALUE
          event (10411)
          set with level 1 if Winbundle>=3
          _b_tree_bitmap_plans
          set to FALSE if Winbundle<=2
          db_writer_processes4change default in case of dbwr problems only
          _fix_control (4728348)4728348:OFFset to 4728348:OFF if Winbundle<=5
          _first_spare_parameter1set to 1 if Winbundle>=3

           

          Regards,

          • Re: Database Check and Parameter_check_102
            Bhavik G. Shroff
            Currently Being Moderated

            Hi,

             

            The reason for not getting the output of that SQL query was the lack of Post-installation activities. Now, as per the output, your system is running with WINBUNDLE - patch level 14 of Oracle 10.2.0.5. CPU/PSU do updation in that table dba_registry_history which was a part of post-installation activities.

             

            You need to set the following parameter accordingly.

             

            alter system set event="10411 trace name context forever, level 1" scope=spfile sid='*';

             

            In your system _first_spare_parameter is already set with value 1. (see IS_VALUE for parameter _first_spare_parameter). so no need to touch it. For rest of the suggested oracle parameters are not applicable for WINBUNDLE 14.

             

            Re-execute that Parameter check script. Confirm the parameter settings according to recommendations.

             

            Restart your Database after such changes.

             

            --

            Regards,

            Bhavik G. Shroff

            • Re: Database Check and Parameter_check_102
              M. Abdul Jamil
              Currently Being Moderated

              I really appreciate to your expert reply and explanation.

              now please put some light on following parameters which i asked in this post.

              DBO    ARCHIVE_TOO_OLD  1    Operation: 'Archive log backup' has not been run # Operation too old or has not been run in clean-up period
              PROF    LOG_BUFFER  1    Value: 14238720 (>< 4096,512 KB) # Size of redo log buffer in bytes
              PROF    OPTIMIZER_INDEX_COST_ADJ  1    Value: 20 (set in parameter file) # Optimizer index cost adjustment
              PROF    STATISTICS_LEVEL  1    Value: TYPICAL (set in parameter file) # Statistics level
              ORA    Checkpoint not complete  100    Time: Stan-04-09 11.15.52, line: Checkpoint not complete

               

              the last Ora Checkpoint not complete is resolved after increase the size of redo log.

              why am i getting following parameters while these are already exist in initSID.ora file.

              OPTIMIZER_INDEX_COST_ADJ =20

              STATISTICS_LEVEL = TYPICAL

              you can see these parameters in my previous reply.

               

              Thanks and Best Regards,

              • Re: Database Check and Parameter_check_102
                Bhavik G. Shroff
                Currently Being Moderated

                Hi,

                 

                I would recommend you to run "Cleanup logs" job available in DB13 and then perform "Check database" job in DB13.

                 

                If still you are getting the same warnings as you have mentioned, then you need to take actions as following.

                 

                1.

                DBOARCHIVE_TOO_OLD   1Operation: 'Archive log backup' has not been run # Operation too old or has not been run in clean-up period

                It may be possible that Archive log backup is not performed for the complained System. If not yet, then perform it.

                 

                 

                2.

                PROFLOG_BUFFER   1Value: 14238720 (>< 4096,512 KB) # Size of redo log buffer in bytes

                You can reconfigure this parameter check condition in DB17 , if still you are getting frequent warning in DB check result. You can set this parameter check with value 14238720 (this is in KB) with "less than /equal" to condition.

                 

                3.

                OPTIMIZER_INDEX_COST_ADJ

                You can remove Active flag for this check condition in DB17

                 

                4.

                PROFSTATISTICS_LEVEL

                You can reconfigure this parameter check condition with check condition "<>Not equal to" and value TYPICAL in DB17

                 

                I hope the above information will be helpful to you.

                 

                --

                Regards,

                Bhavik G. Shroff

                • Re: Database Check and Parameter_check_102
                  M. Abdul Jamil
                  Currently Being Moderated

                  Dear Respected Bhavik G,

                  I have set the mentioned parameter with the help of alter system set command now these parameter are in SPFILE while not showing in PFILE. now i have to create PFILE from SPFILE or no need.

                  and would you give me last favor, I attached initSID.ora, please have a look and check the value of parameters.

                  • Re: Database Check and Parameter_check_102
                    Bhavik G. Shroff
                    Currently Being Moderated

                    Hi,

                     

                    now i have to create PFILE from SPFILE or no need.

                    You can create PFILE manually or you can simply Restart DB instance.

                     

                    The parameter settings are looking Ok. But keep in mind that when you apply next SAP Bundle Patch /WINBUNDLE Oracle Patch, the some parameter settings will be changed according to relative post installation steps of Bundle patch.

                     

                    You need to plan for Oracle 10g to Oracle 11g upgrade.

                     

                     

                    --

                    Regards,

                    Bhavik G. Shroff

                    • Re: Database Check and Parameter_check_102
                      João Dimas
                      Currently Being Moderated

                      Hello Bhavik G.

                       

                      My Oracle DB version is the 10.2.0.4, I applied the last interim patch file for Windows X64 (p12429521_10204_MSWINx8664) and I perform all the instructions in point 3.3.6 Post Installation Instructions.

                       

                      I found this thread when I tried to find some information about what´s the meaning of the word WINBUNDLE that I see in the recommendations in oracle parameters list which shown all the oracle parameters that is recommended by SAP, regarding the sap notes 1171650 - Automated Oracle DB parameter check and 830576 - Parameter recommendations for Oracle 10g.

                       

                      But now I´m with a little problem... when I run the following SQL query (mentioned in sap note 1175996 - Oracle 10g/11g patches check) anything happens... I don´t know why! Can you please help me...!?

                       

                      SQL> select action_time, version, bundle_series, comments

                      from dba_registry_history

                      where bundle_series = 'WINBUNDLE'

                      order by action_time desc;

                       

                      no rows selected

                       

                      Can you help me please?

                       

                      Thank you very much,

                      JDimas

Actions