• Find us:
    +1-669-900-5138   |   +44-203-372-5553
  • Free Newsletter

    Get Latest Updates

  • Make Training Enquiry


    Company

  • Categories

  • Archive

  • Errors in Alert Log File of 10.2.0.1 Instances

    Posted by "" in "database" on 2008-03-10

    Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInPin on PinterestEmail this to someone

    These are the following Errors/Warning messages which we will get in 10.2.0.1 release Instances alert log files.  Find the following work arounds/solutions, what I have successfully applied.

     Problem 1:

     Memory Notification: Library Cache Object loaded into SGA
    Heap size 6237K exceeds notification threshold (2048K)
     

    These are warning messages only which should not cause any problems. These warning messages appear due to new event messaging mechanism and memory manager in 10g Release 2. In 10g R2 we have a new undocumented parameter that sets the KGL heap size warning threshold. Warnings are written if heap size exceeds this threshold. 

    Set    _kgl_large_heap_warning_threshold to a reasonable high value to prevent these warning messages: Default Threshold in 10.2.0.1 is 2 MB only. But Default Threshold value in 10.2.0.2 is 50 MB which is reasonable and recommended value.  

    Solution: 

    SQL> alter system set “_kgl_large_heap_warning_threshold”= 52428800 scope=spfile;

    SQL> shutdown immediate; 

    SQL> startup;   

    Problem 2: 

    Trace file created when RMAN issues the controlfile autobackup. 

    Following messages will be appeared in alert log file 

    Errors in file /oracle/product/10.2.0.1/admin/udump/prod_ora_18627.trc:
    Control autobackup written to DISK device
    handle ‘/backup/flash_recovery_area/PROD/autobackup/2008_01_04/o1_mf_s_648508685_3wv4m226_.bkp’ 

     These messages do not have any impact. Only problem is when ever RMAN issues the control file autobackup command, it will create one trace file with the above errors.  

    Work around  

    (1)   This is a bug fixed in 10.2.0.2 or 10.2.0.3       

      Or       

    (2) Write an OS cron job to delete the trace files 

     References:

    330239.1. Memory Notification: Library Cache object loaded into SGA 

     Note: If you are having above problems with your instances, Please login as SR to Oracle Support and then implement the solution under their guidance.       

    6 Responses to “Errors in Alert Log File of 10.2.0.1 Instances”

    1. mahmedocp says:

      Hi All,

      Im getting this Error(warning) in Alert Log file Database version 9.2.0.6.0 and Oracle Apps 11.5.10.2

      WARNING:Oracle instance running on a system with low open file descriptor
      limit. Tune your system to increase this limit to avoid
      severe performance degradation.

      Can u please suggest me what to do…?

      Thanks,
      Ahmed.

    2. amit says:

      Hi Ahmed,

      Increase the number of file descriptors or reduce the number of db_files
      parameter in init.ora and restart the database.

      Let me know if you have any issue.

      Amit

    3. SubbaRao says:

      Ahmed,

      As Amit said, this is mainly because of too high of a setting for the db_files database parameter or too low of a setting for the OS open file descriptor parameter.

      To solve the problem, decrease the db_files parameter value or increase the open file descriptors limit value specific to your os kernel….

      the following metalink note might be helpful to increase the open file descriptors limit

      How to Display and Change UNIX Process Resource Limits Note:188149.1

      Regards,
      Subbu

    4. mahmedocp says:

      Hi,

      Thanks for ur quick responses its very help full for me the oracle NOTE:

      Thanks a lot.
      Ahmed.

    5. SubbaRao says:

      Welcome my friend,

      I really appreciate your words,

      Regards,
      Subbu

    6. ramakrishna says:

      hi i am ramakrishna
      1.how to find how many ptches are installed in my database?
      2.what is the use of root.sh script?
      3.Why small tables keep in keep pool & big tables keep in recycle pool
      4.One user is not possible to access the database means it will take more time to access what can you do as an DBA
      5.What is use of execution plan

    Leave a Reply



  • K21 Technologies is among the most experienced Oracle Gold Partner for Identity Access Management service providers. We work with application development companies and in-house technology division to help achieve significant returns on their IT security investment. Our clientele includes some of the globally renowned corporate, which speaks of our expertise in our field.

    We have the most talented and experienced team that can swiftly deploy security solutions even in complex IT ecosystem. Our clients highly appreciate our timely implementation, interactive training, on-demand support and community resources.
  • CONTACTS

    K21 Technologies
    8 Magnolia Place, Harrow,
    London, HA2 6DS

    UK: +44(0)7476444481
    USA: +1-888-414-1821

  • 2014, K21 Technologies. All rights reserved DMCA.com
  • TOP
    TOP