Restarting dead SNP, ORA-600
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 10 of 10

Thread: Restarting dead SNP, ORA-600

  1. #1
    Join Date
    Oct 2002
    Location
    CA
    Posts
    67

    Restarting dead SNP, ORA-600

    Environment: Oracle 8.1.7 on Solaris 5.8. For some reason, my database is generating bunch of trace files that filled up my filesystem so I had to remove them.
    --------------------------------------------------------
    Alert log shows:

    Wed Apr 7 15:10:59 2004
    Restarting dead background process SNP3
    SNP3 started with pid=8
    Wed Apr 7 15:11:04 2004
    Errors in file /oracle/admin/h8cotrn/bdump/h8cotrn_snp3_17576.trc:
    ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL
    execution], [], [], [], [], [], []
    ORA-06544: PL/SQL: internal error, arguments: [77303], [], [], [], [], [], [],
    []
    ORA-06553: PLS-801: internal error [77303]

    Did some init.ora parameters get changed? Please advise.
    Thanks
    -James
    --------------------------------------
    It's not what the world does to you that matters. It's how you respond...

  2. #2
    Join Date
    Dec 2000
    Posts
    138
    Nope, Looks like some PL/SQL program causes this problem. We have had this kind of problem while interacting with pro* COBOL.

    Check what programming was running at that time that failed.
    HTH.
    -dharma.

  3. #3
    Join Date
    Oct 2002
    Location
    CA
    Posts
    67
    Hi Dharma,

    Actually from what I know, there is noone running anything. I bounced the database twice but the trace files continue.

    There might be some hidden jobs running by cron job of some sort??
    --James
    --------------------------------------
    It's not what the world does to you that matters. It's how you respond...

  4. #4
    Join Date
    Dec 2000
    Posts
    138
    I would check - if it only happens at startup - if there are any database triggers attached.
    -dharma

  5. #5
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    any jobs in dba_jobs that are broken? have failed?
    I'm stmontgo and I approve of this message

  6. #6
    Join Date
    Oct 2002
    Location
    CA
    Posts
    67
    There is one job performing cbo_stats.gather_stats. I think this is a standard job. Is it creating excessive trace files, what do you think?

    SQL> select job,LOG_USER, WHAT, TOTAL_TIME, BROKEN from dba_jobs;

    JOB LOG_USER
    ---------- ------------------------------
    WHAT
    --------------------------------------------------------------------------------
    TOTAL_TIME B
    ---------- -
    21 SYSTEM
    cbo_stats.gather_stats;
    47052 N
    --------------------------------------
    It's not what the world does to you that matters. It's how you respond...

  7. #7
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by james_cc
    There is one job performing cbo_stats.gather_stats. I think this is a standard job. Is it creating excessive trace files, what do you think?

    SQL> select job,LOG_USER, WHAT, TOTAL_TIME, BROKEN from dba_jobs;

    JOB LOG_USER
    ---------- ------------------------------
    WHAT
    --------------------------------------------------------------------------------
    TOTAL_TIME B
    ---------- -
    21 SYSTEM
    cbo_stats.gather_stats;
    47052 N
    your query shows it's broken, so that probably means it failed 16 times and has 16 trace files with it. Anything in the alert log to indicate why it's broken?
    I'm stmontgo and I approve of this message

  8. #8
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Originally posted by stmontgo
    your query shows it's broken
    Hm, the way I see the results of his query it indicates the job is NOT broken (BROKEN = 'N').
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  9. #9
    Join Date
    Oct 2002
    Location
    CA
    Posts
    67
    Originally posted by stmontgo
    your query shows it's broken, so that probably means it failed 16 times and has 16 trace files with it. Anything in the alert log to indicate why it's broken?
    Broken = N, does it mean not broken.

    Anyway the database is going crazy generating tracefiles every 1-2 min. Restarting dead background process SNP1
    SNP1 started with pid=17
    Thu Apr 8 14:00:30 2004
    Errors in file /oracle/admin/h8cotrn/bdump/h8cotrn_snp1_17087.trc:
    ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], []
    ORA-06544: PL/SQL: internal error, arguments: [77303], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [77303]
    Thu Apr 8 14:00:37 2004
    Thread 1 advanced to log sequence 4276
    Current log# 3 seq# 4276 mem# 0: /ora01/oracle/h8cotrn/redo03a.log
    Current log# 3 seq# 4276 mem# 1: /ora02/oracle/h8cotrn/redo03b.log
    Thu Apr 8 14:00:37 2004
    ARC0: Beginning to archive log# 2 seq# 4275
    ARC0: Completed archiving log# 2 seq# 4275



    Why is that job running, can we kill it?

    Here is the alert log again.
    --------------------------------------------------------------
    Restarting dead background process SNP1
    SNP1 started with pid=17
    Thu Apr 8 14:00:30 2004
    Errors in file /oracle/admin/h8cotrn/bdump/h8cotrn_snp1_17087.trc:
    ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], []
    ORA-06544: PL/SQL: internal error, arguments: [77303], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [77303]
    Thu Apr 8 14:00:37 2004
    Thread 1 advanced to log sequence 4276
    Current log# 3 seq# 4276 mem# 0: /ora01/oracle/h8cotrn/redo03a.log
    Current log# 3 seq# 4276 mem# 1: /ora02/oracle/h8cotrn/redo03b.log
    Thu Apr 8 14:00:37 2004
    ARC0: Beginning to archive log# 2 seq# 4275
    ARC0: Completed archiving log# 2 seq# 4275
    --------------------------------------
    It's not what the world does to you that matters. It's how you respond...

  10. #10
    Join Date
    Aug 2002
    Location
    Atlanta
    Posts
    1,187
    Originally posted by jmodic
    Hm, the way I see the results of his query it indicates the job is NOT broken (BROKEN = 'N').
    yep, my bad, tks
    I'm stmontgo and I approve of this message

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