DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: Data Base Crashes

  1. #1
    Join Date
    Sep 2000
    Posts
    384
    Hi,
    i have a problem with my database,
    it crashes frequently,
    application is a 3 tier architecture based application(web based application),we use COM and DCOM objects and the database crashes frequently saying unspecified errors,and some one told m ethat this might be due to memory leakage issue in 8.1.7.
    is this true,please let me know the fix fo rthis,
    my version is 8.1.7.
    Radhakrishnan.M

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    What's the alert.log say? Any Trace files dumped?
    Jeff Hunter

  3. #3
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Platform?
    Jeff Hunter

  4. #4
    Join Date
    Aug 2001
    Posts
    390
    What version of ORacle are you running on ??? you are right about the memory leak on 8.1.7 but Memory leak won't cause your database crashed. It will dergrade your performance. 8.1.7.3.0 should take care of the memory leak problem.

  5. #5
    Join Date
    Dec 2001
    Location
    SAN FRANCISCO, CA
    Posts
    306

    Does this usually happen when u run/ execute a front end application with backend data



    Eat , Drink & Enjoy life -

    pravin_kini@hotmail.com

  6. #6
    Join Date
    Sep 2000
    Posts
    384
    yes this does happen when we execute front end application,
    Version is 8.1.7 and platform is NT,
    thanks,
    Radhakrishnan.M

  7. #7
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    8.1.7.3.0 should take care of the memory leak problem.
    Having in mind that 8.1.7.3.0 has its own memory leak bugs :-)

  8. #8
    Join Date
    Sep 2000
    Posts
    384
    Does oracle 8.1.7.3.0 has also leaks ,
    pls let me know,
    thanks,
    Radhakrishnan.M

  9. #9
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    Yes, it has, the workaround is:

    event="10262 trace name context forever, level 10000"

    You can replace 10000 with 1 if you want to neglect all leaks, not only the ones below 10000 bytes.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width