4 Replies Latest reply: Jun 7, 2010 2:33 AM by 618702 RSS

    generation of MMON process trace files in large file size (GB Size)

    775855
      Hi,

      I have created a database using the dbca in windows platform. Few days I found that, in the BDUMP directory the MMON process trace files are getting generated. The files starts to generate in MB size and will increase upto GB size. I know that the back ground process trace files cannot be disabled. So now iam force to manually delete these files from the bdump directory.plz help me to resolve this issue.

      I have checked and verified the SGA size, Shared Pool size and other memory areas.

      The statistics level in Typical also.

      But still the files are generated.

      PLease Helppp.....


      Shiyas
        • 1. Re: generation of MMON process trace files in large file size (GB Size)
          618702
          Hi user13170361,

          Do you have the permission to create SR on metalink? I strongly suggest you to create an SR.

          The other thing that you can do is to check your alert.log file for some pointing information to your error.

          What your db version and os btw?

          Ogan
          • 2. Re: generation of MMON process trace files in large file size (GB Size)
            775855
            hi

            As per your instruction i have checked the Alert log file. I have pasted a part of errors that found in the alert log file.


            Mon Jun 07 09:30:58 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:31:02 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:36:00 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:36:08 2010
            Restarting dead background process MMON
            MMON started with pid=11, OS id=656
            Mon Jun 07 09:36:11 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:36:15 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:41:12 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:41:16 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:46:13 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:46:17 2010
            Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
            ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []

            Mon Jun 07 09:50:18 2010
            Shutting down instance: further logons disabled
            Mon Jun 07 09:50:19 2010
            Stopping background process QMNC
            Mon Jun 07 09:50:19 2010
            Stopping background process CJQ0
            Mon Jun 07 09:50:20 2010
            Stopping background process MMNL
            Mon Jun 07 09:50:21 2010
            Stopping background process MMON
            Mon Jun 07 09:50:22 2010
            Shutting down instance (immediate)
            License high water mark = 4
            Mon Jun 07 09:50:22 2010
            Stopping Job queue slave processes, flags = 7
            Mon Jun 07 09:50:22 2010
            Job queue slave processes stopped
            Waiting for dispatcher 'D000' to shutdown
            All dispatchers and shared servers shutdown
            Mon Jun 07 09:50:23 2010
            alter database close normal
            Mon Jun 07 09:50:23 2010
            SMON: disabling tx recovery
            SMON: disabling cache recovery
            Mon Jun 07 09:50:23 2010
            Shutting down archive processes
            Archiving is disabled
            Archive process shutdown avoided: 0 active
            Thread 1 closed at log sequence 71
            Successful close of redo thread 1
            Mon Jun 07 09:50:23 2010
            Completed: alter database close normal
            Mon Jun 07 09:50:23 2010
            alter database dismount
            Completed: alter database dismount
            ARCH: Archival disabled due to shutdown: 1089
            Shutting down archive processes
            Archiving is disabled
            Archive process shutdown avoided: 0 active
            ARCH: Archival disabled due to shutdown: 1089
            Shutting down archive processes
            Archiving is disabled
            Archive process shutdown avoided: 0 active


            But I am not able to understand anything above of this.
            And I am sorry we dont have the metalink support or srs support.
            Is there any other way to resolve this issue.

            Shiyas
            • 3. Re: generation of MMON process trace files in large file size (GB Size)
              Fahd.Mirza
              Just search on metalink .. You can always use below note for trouble shooting 600/7445 errors ..

              153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool
              • 4. Re: generation of MMON process trace files in large file size (GB Size)
                618702
                Hi user13170361,

                There is an ORA-600 Lookup tool at the metalink site. First enter the first parameter in that tool and check what was written than create an SR if you can not find what you are looking for.

                Ogan

                Edited by: Ogan Ozdogan on 07.Haz.2010 10:31

                There is no other way to solve this problem unless those errors are sometimes happining because of a human error or misplaced parameter ETC. So if you have changed a parameter on the database you may have to practise it and roll it back. That is no more than just guessing, you really have to check metalink.