Oracle 9i (SE) Solaris 9 (Trace Files)

Hi Guys,
Is it wise to delete the trace files and where are they located. I've got space issues so I need to cleanup.
Thank you.

You're welcome
And please mark this question as answered. [It seems |http://forums.oracle.com/forums/profile.jspa?userID=564174] you don't want to mark questions as answered and give points to users who answered and helped you. ( [Total question 49, 45 unresolved|http://forums.oracle.com/forums/profile.jspa?userID=564174] )
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
[Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

Similar Messages

Oracle XE 11.2 writing trace files every 30 sec.

Hi all,
we are using an oracle xe 11.2 database on linux. By searching the logs we find some trace files from dbrm that will be updated every 30 secs.
Does anyone can help understand whats the problem ?
Thanks a log
/u01/app/oracle/diag/rdbms/xe/XE/trace> tail -f XE_dbrm_8880.trc
Trace file /u01/app/oracle/diag/rdbms/xe/XE/trace/XE_dbrm_8880.trc
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Beta
ORACLE_HOME = /u01/app/oracle/product/11.2.0/xe
System name: Linux
Node name: vtsbpm1
Release: 2.6.32.36-0.5-default
Version: #1 SMP 2011-04-14 10:12:31 +0200
Machine: x86_64
VM name: VMWare Version: 6
Instance name: XE
Redo thread mounted by this instance: 1
Oracle process number: 7
Unix process pid: 8880, image: oracle@vtsbpm1 (DBRM)
*** 2012-02-28 11:39:42.567
*** SESSION ID:(240.1) 2012-02-28 11:39:42.567
*** CLIENT ID:() 2012-02-28 11:39:42.567
*** SERVICE NAME:() 2012-02-28 11:39:42.567
*** MODULE NAME:() 2012-02-28 11:39:42.567
*** ACTION NAME:() 2012-02-28 11:39:42.567
kgsksysstop: blocking mode (2) timestamp: 1330425582566557
kgsksysstop: successful
kgskreset: Threshold setting[numa_pg(0)]
Threshold low[0] = 1, high[0] = 3
kgsksysresume: successful
RESOURCE MANAGER PLAN/CONSUMER GROUP DUMP
type: PLAN, Name: INTERNAL_PLAN_XE, number of directives: 2, bit mask: 0x3
policy index: 0, inst state index: 0, plan id: 1
Data from Management module:
Plan Parameters:
<None>
Plan Directives:
[1] Plan Directive Parameters:
Directive name: MGMT_P1, value: 100
Directive:
type: CONSUMER GROUP, Name: OTHER_GROUPS (addr: 0x8f85b120)
policy index: 0, inst state index: 0, class num: 0x1
mast: INFINITE, ASL qtout: INFINITE, PQQ qtout: INFINITE, mdop: INFINITE
Statistics:
current queued threads: 0,
class total time: 0 msec, penalty # 0
total threads: 0
total CPU yields: 0
total CPU wait: 0 msec
total IO wait: 0 msec
*** 2012-02-28 13:23:15.183
cpu%: cputm: cpuwt: avgrun: avgwt:
1 324 0 0.05 1.00
RQs: < 5: < 10: < 50: < 100: < 200: < 1000: > 1K:
4054 0 3 0 0 0 0
*** 2012-02-28 13:24:45.189
1 308 0 0.00 1.00
4112 0 3 0 0 0 0
4 2049 0 0.05 1.00
*** 2012-02-28 13:26:15.187
6190 14 17 1 1 0 0
*** 2012-02-28 13:27:45.191
24 23051 210 0.15 1.00
20357 30 37 26 17 5 0
*** 2012-02-28 13:29:15.196
9 377 0 0.00 1.00
4309 1 2 0 0 0 0
*** 2012-02-28 13:30:45.207
cpu%: cputm: cpuwt: avgrun: avgwt:
16 448 0 0.00 1.00
RQs: < 5: < 10: < 50: < 100: < 200: < 1000: > 1K:
4294 2 4 0 0 0 0
*** 2012-02-28 13:32:15.207
4 360 0 0.00 1.00
4136 0 4 0 0 0 0
*** 2012-02-28 13:33:45.207
1 392 0 0.00 1.00
4197 1 3 0 0 0 0

understand whats the problem ?Without knowing specifics about what is going on in your instance, its hard to say.
Could be a problem indication, more likely not. Appears to be Resource Manager trace files, the resource manager doesn't have much effect on the instance until the host is getting starved for resources, then the engine can throttle down resources given to different resource groups.
http://docs.oracle.com/cd/E11882_01/server.112/e25494/dbrm001.htm#sthref2760

Oracle generate trace file when log switch

Hi,
i am using oracle 9.2.3 on solaris 9. I found oracle generate a trace file in UDUMP directory when log file switch.
could anyone tell me how to tell oracle not to generate the trace file when log switch?
thanks a log

During switch are seeing any error in alert log? By the way what is the content of that trace file? Is any event set in your init.ora?
Thanks and Regards,
Satheesh Babu.S
Bangalore

Automatic deletion of old archive files and trace files

I've got a database that must run 24x7 without being monitored by a DBA.
Two questions:
1. Is it possible to get Oracle to automatically delete and uncatalog old archive files?
2. Is it possible to get Oracle to automatically delete old trace files located in udump and bdump?
Thanks in advance

1. When you say 'uncatalog old archives do you mean that your database is backed up using RMAN and a catalog? If this is the case then RMAN can delete the backed up archives for you. Just add 'delete input' to the end of the 'backup archive log...' line in your backup script.
2. Oracle can't delete the trace files. Best way is to write a script that delete all files older than X days and schedule it to run every night.

Interpreting Trace File.

Hi i am using 10.2.0.4.0 version of oracle.
I am having trace file info as below, for one of the query. So how should i interpret the trace file? What is the issue in the query, and the scope of improvement in the query? please note that , i have removed the query and its plans from the trace file, i have only posted the wait sections.
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.14       0.13          0          0          1           0
Execute      1      6.63     162.12      33540      72921        383           0
Fetch    17272    178.89    1933.95     274835    3147603         20      259063
total    17274    185.66    2096.21     308375    3220524        404      259063
Misses in library cache during parse: 1
Optimizer mode: CHOOSE
Parsing user id: 36
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
control file sequential read                    4        0.00          0.00
db file sequential read                    302812        0.62       1913.89
latch: cache buffers chains                     3        0.04          0.04
direct path write temp                        501        0.01          0.30
SQL*Net message to client                   17272        0.00          0.04
db file scattered read                        120        0.02          0.63
direct path read temp                         608        0.14          1.71
SQL*Net message from client                 17272       44.81      31865.74
SQL*Net more data to client                    15        0.00          0.00
latch: object queue header operation            1        0.00          0.00
latch: library cache                            3        0.03          0.04
latch: library cache pin                        1        0.00          0.00
latch: cache buffer handles                     1        0.00          0.00
OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.14       0.13          0          0          1           0
Execute      1      6.63     162.12      33540      72921        383           0
Fetch    17272    178.89    1933.95     274835    3147603         20      259063
total    17274    185.66    2096.21     308375    3220524        404      259063
Misses in library cache during parse: 1
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
SQL*Net message to client                   17275        0.00          0.04
SQL*Net message from client                 17274       75.57      31941.39
SQL*Net more data from client                   2        0.00          0.01
db file sequential read                    302812        0.62       1913.89
control file sequential read                    4        0.00          0.00
latch: cache buffers chains                     3        0.04          0.04
direct path write temp                        501        0.01          0.30
db file scattered read                        120        0.02          0.63
direct path read temp                         608        0.14          1.71
SQL*Net more data to client                    15        0.00          0.00
latch: object queue header operation            1        0.00          0.00
latch: library cache                            3        0.03          0.04
latch: library cache pin                        1        0.00          0.00
latch: cache buffer handles                     1        0.00          0.00
OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS
call     count       cpu    elapsed       disk      query    current        rows
Parse       11      0.02       0.01          0          0          0           0
Execute    348      0.20       0.17          0          0          1           0
Fetch      367      0.06       0.37         59       1187          0        3806
total      726      0.28       0.56         59       1187          1        3806
Misses in library cache during parse: 11
Misses in library cache during execute: 10
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                        59        0.01          0.32
    1 user SQL statements in session.
348 internal SQL statements in session.
349 SQL statements in session.
********************************************************************************

below is the estimate and actual results.
| Id | Operation                              | Name                        | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads | Writes | OMem | 1Mem | Us
ed-Mem | Used-Tmp|
|* 1 | COUNT STOPKEY                         |                             | 13475 |        | 13475 |00:01:32.33 |     134K| 11357 |      0 |       |       |
    |         |
|   2 |   NESTED LOOPS                         |                             | 13475 |      2 | 13475 |00:01:31.66 |     134K| 11357 |      0 |       |       |
    |         |
|   3 |    NESTED LOOPS                        |                             | 13475 |      1 | 13475 |00:01:29.22 |   94325 | 11357 |      0 |       |       |
    |         |
|* 4 |     INDEX RANGE SCAN                   |                | 13475 |      1 | 13475 |00:00:26.63 |   40425 |   4014 |      0 |       |       |
    |         |
|   5 |     TABLE ACCESS BY INDEX ROWID        | | 13475 |      1 | 13475 |00:01:02.46 |   53900 |   7343 |      0 |       |       |
    |         |
|* 6 |      INDEX RANGE SCAN                  || 13475 |      1 | 13475 |00:00:16.80 |   40425 |   2056 |      0 |       |       |
    |         |
|* 7 |    TABLE ACCESS FULL                   | | 13475 |      2 | 13475 |00:00:02.26 |   40425 |      0 |      0 |       |       |
    |         |
|   8 | TABLE ACCESS BY INDEX ROWID           || 94399 |      1 | 94399 |00:06:17.09 |     389K| 32207 |      0 |       |       |
    |         |
|* 9 |   INDEX UNIQUE SCAN                    | | 94399 |      1 | 94399 |00:02:59.79 |     294K| 15488 |      0 |       |       |
    |         |
| 10 | TEMP TABLE TRANSFORMATION             |                             |      1 |        |    170K|00:35:11.08 |    1575K|    195K|   6158 |       |       |
    |         |
| 11 |   LOAD AS SELECT                       |                             |      1 |        |      1 |00:04:49.06 |   53704 | 28653 |    264 |   525K|   525K| 5
25K (0)|              |
| 12 |    PARTITION RANGE ALL                 |                             |      1 | 55430 | 16097 |00:06:26.06 |   53433 | 28651 |      0 |       |       |
    |         |
| 13 |     PARTITION HASH ALL                 |                             |     54 | 55430 | 16097 |00:09:20.69 |   53433 | 28651 |      0 |       |       |
    |         |
|* 14 |      TABLE ACCESS BY LOCAL INDEX ROWID | INV                         |    432 | 55430 | 16097 |00:06:11.42 |   53433 | 28651 |      0 |       |       |
    |         |
|* 15 |       INDEX SKIP SCAN                  | |    432 |    125K| 16097 |00:00:39.90 |    4642 |   4508 |      0 |       |       |
    |         |
| 16 |   TABLE ACCESS BY INDEX ROWID          | |      1 |      2 |    170K|00:30:21.66 |    1522K|    166K|   5894 |       |       |
    |         |
| 17 |    NESTED LOOPS                        |                             |      1 |     97 |    276K|34:55:49.92 |    1470K|    150K|   5894 |       |       |
    |         |
| 18 |     NESTED LOOPS                       |                             |      1 |     55 |    105K|00:22:14.57 |    1128K|    134K|   5894 |       |       |
    |         |
| 19 |      NESTED LOOPS OUTER                |                             |      1 |     52 |    105K|00:16:32.91 |     694K|    105K|   5894 |       |       |
    |         |
|* 20 |       HASH JOIN                        |                             |      1 |     52 |    105K|00:16:19.68 |     402K|    102K|   5894 | 9641K| 2205K| 16
27K (1)|        10240 |
| 21 |        VIEW                            |                             |      1 | 65234 |    105K|00:16:16.46 |     402K|    101K|   4655 |       |       |
    |         |
| 22 |         SORT UNIQUE                    |                             |      1 | 65234 |    105K|00:16:16.46 |     402K|    101K|   4655 | 8724K| 1161K| 61
8K (48)|         9216 |
| 23 |          UNION-ALL                     |                             |      1 |        |    105K|00:14:59.93 |     402K| 97342 |    252 |       |       |
    |         |
| 24 |           NESTED LOOPS OUTER           |                             |      1 | 19975 |    105K|00:14:10.24 |     395K| 94655 |      0 |       |       |
    |         |
| 25 |            NESTED LOOPS                |                             |      1 | 19975 |    105K|00:13:58.47 |     140K| 93616 |      0 |       |       |
    |         |
| 26 |             VIEW                       |                             |      1 | 55430 | 16097 |00:00:00.43 |     270 |    531 |      0 |       |       |
    |         |
| 27 |              TABLE ACCESS FULL         | |      1 | 55430 | 16097 |00:00:00.19 |     270 |    531 |      0 |       |       |
    |         |
|* 28 |             TABLE ACCESS BY INDEX ROWID| | 16097 |      1 |    105K|00:13:59.70 |     140K| 93085 |      0 |       |       |
    |         |
|* 29 |              INDEX RANGE SCAN          |     | 16097 |     10 |    145K|00:00:40.42 |   32685 |   8237 |      0 |       |       |
    |         |
| 30 |            TABLE ACCESS BY INDEX ROWID | |    105K|      1 | 84716 |00:00:16.78 |     254K|   1039 |      0 |       |       |
    |         |
|* 31 |             INDEX UNIQUE SCAN          | |    105K|      1 | 84716 |00:00:13.05 |     169K|    982 |      0 |       |       |
    |         |
| 32 |           NESTED LOOPS                 |                             |      1 | 45259 |      0 |00:00:17.19 |    7336 |   2687 |    252 |       |       |
    |         |
|* 33 |            HASH JOIN RIGHT OUTER       |                             |      1 | 45259 |      0 |00:00:17.19 |    7336 |   2687 |    252 |   884K|   884K| 3
09K (0)|              |
| 34 |             TABLE ACCESS FULL          | |      1 |   1673 |   1677 |00:00:00.01 |      24 |      8 |      0 |       |       |
    |         |
|* 35 |             HASH JOIN                  |                             |      1 | 45259 |      0 |00:00:17.13 |    7310 |   2678 |    252 | 3318K| 1235K| 4
47K (1)|         2048 |
|* 36 |              TABLE ACCESS FULL         | |      1 | 45259 | 49043 |00:00:07.41 |    7043 |   2170 |      0 |       |       |
    |         |
| 37 |              VIEW                      |                             |      1 | 55430 | 16097 |00:00:00.14 |     267 |    256 |      0 |       |       |
    |         |
| 38 |               TABLE ACCESS FULL        ||      1 | 55430 | 16097 |00:00:00.12 |     267 |    256 |      0 |       |       |
    |         |
| 39 |            TABLE ACCESS BY INDEX ROWID | |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |
    |         |
|* 40 |             INDEX UNIQUE SCAN          | |      0 |      1 |      0 |00:00:00.01 |       0 |      0 |      0 |       |       |
    |         |
| 41 |        VIEW                            |                             |      1 | 55430 | 16097 |00:00:00.02 |     267 |      0 |      0 |       |       |
    |         |
| 42 |         TABLE ACCESS FULL              | |      1 | 55430 | 16097 |00:00:00.01 |     267 |      0 |      0 |       |       |
    |         |
| 43 |       TABLE ACCESS BY INDEX ROWID      | |    105K|      1 | 93385 |00:00:24.90 |     291K|   2104 |      0 |       |       |
    |         |
|* 44 |        INDEX UNIQUE SCAN               | |    105K|      1 | 93385 |00:00:16.45 |     196K|   1405 |      0 |       |       |
    |         |
| 45 |      TABLE ACCESS BY INDEX ROWID       | |    105K|      1 |    105K|00:05:49.82 |     434K| 29495 |      0 |       |       |
    |         |
|* 46 |       INDEX UNIQUE SCAN                ||    105K|      1 |    105K|00:02:54.37 |     328K| 14644 |      0 |       |       |
    |         |
|* 47 |     INDEX RANGE SCAN                   | |    105K|      2 |    170K|00:03:01.14 |     342K| 15690 |      0 |       |       |
    |         |
Predicate Information (identified by operation id):
   1 - filter(1>=ROWNUM)
   4 - access("XS"."SITEPK"=:B1)
   6 - access("XS"."VENDORPK"="XB"."VENDORPK")
   7 - filter(("XB"."BUYERCOMPANYPK"="CC"."PARENTCOMPANYPK" OR "XB"."BUYERCOMPANYPK"="CC"."CHILDCOMPANYPK"))
   9 - access("INVOICEPK"=:B1 AND "LINENUM"=:B2)
14 - filter(("IH"."INVOICEORIGIN"='APP' AND "IH"."PO_PK" IS NULL AND "IH"."ISPOSTED"='Y'))
15 - access("IH"."PAYPK"=3914297352 AND "IH"."POSTDATE">=1338508800000 AND "IH"."POSTDATE"<1341014400000)
       filter(("IH"."POSTDATE">=1338508800000 AND "IH"."PAYPK"=3914297352 AND "IH"."POSTDATE"<1341014400000))
20 - access("NEWVIEW"."PRIMARYKEY"="TAB"."INVOICEPK")
28 - filter(TO_NUMBER("RAT"."AUDITTYPE")<2)
29 - access("INNERTAB1"."INVOICEPK"="RAT"."INVOICEPK")
       filter("RAT"."INVOICEPK" IS NOT NULL)
31 - access("RAT"."USERPK"="UR"."USERPK")
33 - access("RA"."QUEUEPK"="Q"."QUEUEPK")
35 - access("INNERTAB2"."INVOICEPK"="RA"."INVOICEPK")
36 - filter(("RA"."INVOICEPK" IS NOT NULL AND "RA"."RECEIVERPK" IS NOT NULL))
40 - access("RA"."RECEIVERPK"="UR"."USERPK")
44 - access("TAB"."ENTEREDBY"="UR"."USERPK")
46 - access("TAB"."INVOICEPK"="ISUM"."INVOICEPK")
47 - access("IDD"."INVOICEPK"="TAB"."INVOICEPK")
87 rows selected.
Elapsed: 00:00:04.10
SQL>Edited by: 930254 on Aug 7, 2012 9:33 AM

Need help deleting trace files

Hi,
I am new to Oracle RAC and I need to get rid of trace files since they are growing too big. I have one that is 22Gigs and I only have 60 Gigs available right now on that drive. I want to know if I can delete the file manually using the rm command.
My trace files are in: /u01/app/oracle/diag/rdbms/.../.../trace
The file I am concerned is called: "linux1_pz99_13299.trc" and "linux1_pz99_13299.trm"
I am using Oracle 11.1.0.6.0 on Oracle Unbreakable Linux.
Thanks for any help that can be provided.

Is that really going to work?
It is my understanding (supported by some inconclusive observations and experiments) that once a trace file grows beyond about 8 kilobytes Oracle will hang onto it in a death grip. You may delete it but Oracle will still have the file handle open and be writing to it.
If the database is running on a Windows platform then an equivalent script will not even give the illusion of deleting the file.
It used to be the case that switching trace file output to a different directory would cause Oracle to release the active trace files but now the trace directory is part of the ADR heirarchy so switching is a more global and more intrusive operation and could interfere with other diagnostics.
You may have to rely on ADRCI's "purge" command unless there is a PL/SQL equivalent.
I shall be very interested to see what others have to say.

Shared server trace file

Hi All,
Our production db is 10.2.0.3 with 2 nodes RAC in MS 2003 window servers. I am wondering what kind of information that Oracle capture in the shared server trace file (file name looks like instance_s001_3333.trc) . When I open some of these files I always see one query always there along with the messages like:
WAIT #8: nam='gc cr block 2-way' ela= 1222 p1=65 p2=49677 p3=1 obj#=69689 tim=4137263779
WAIT #8: nam='gc cr block 2-way' ela= 593 p1=65 p2=50863 p3=1 obj#=69689 tim=4137265531
WAIT #8: nam='gc cr block 2-way' ela= 592 p1=65 p2=50879 p3=1 obj#=69689 tim=4137266700
Should we need to tune this query to make it disappear in the shared server trace files? What are the conditions to trigger Oracle put this query into trace file?
Thank you very much in advance for your support!
Shirley

These trace files are very likely generated by some trace statements originating from client programs connected to shared server processes such as client application processes, SQL*Plus, SQL Developer, OEM, TOAD, etc.
Is your client application instrumented ?
Do some people analyze performance problems on the database side ?
The triggering statements may be some ALTER SESSION statements or package calls like DBMS_MONITOR in 10g or other
(see examples in http://www.oracle.com/technology/oramag/oracle/04-jan/o14tech_perf.html).
You should also check that instances are not configured with instance level tracing:
show parameter sql_traceYou can also check current database sessions sql tracing status with:
select sid, serial, program, sql_trace from v$session where username is not null;

Creating trace file in oracle 10g forms

hii there,
I have developed an application in oracle 10g. but it's too slow . Now i have to trace forms . How can trace oracle forms.
please send it in details as early as possible. I don't know about this trace file generation.
-----Sachin

Hi,
To run SQL trace for a form :
a. Get to the point in the form where you want to turn trace on.
For example, if the problem occurs on the commit, wait until you are
ready to commit, THEN turn trace on.
b. Turn tracing on. In GUI versions: Help - Tools - Trace, enable tracing.
c. Execute the steps you want to trace.
d. Turn tracing off. In GUI versions: Help - Tools - Trace, disable tracing.
The trace file will be written to the subdirectory specified in the
'user_dump_dest' parameter in the INIT.ORA file.

Unable to write trace files in Background dump destination in oracle 10g

Hi All,
OS version : RHEL 5.7
DB version : 10.2.0.4
cluster : 2 node RAC database
Today I faced a strange behaviour for one of our production database. Its a 2-node rac database. On the first node there is no auto generation of trace files in the BAckground dump destination. I am able to see trace files of second in its background dump dest. But the strange behaviour occurs on the first node. I see only Alert log file in the background dump dest . Inspite of getting an error which shows trace file generated but no file occurs in the bdump. The following is the error but physically there no trace file generated:
Errors in file /oracle/db/admin/<sid>/bdump/<sid>j0011558.trc:
ORA-12012: error on auto execute of job 94377
ORA-12008: error in materialized view refresh pathCan anyone have any idea for this strange behaviour. There are no maintenance script for removal of trace files.
Regards,
Imran Khan

ORA-00980:synonym translation is no longer valid
Cause:The synonym used is based on a table, view, or synonym that no longer exists.
Action:Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.
Check the following :
From User Number 1 : Osama1
create table osama_table as select empname from scott.emp;
create public synonym osama_tbl for osama_table ;
grant select on osama_tbl to user_b;
From User Number 2 : Osama2
select 1 from osama_tbl;
SMITH
ALLEN
JONES
MARTIN
From User Number 1 : Osama1
drop table osama_table;
From User Number 2 : Osama2
select 1 from osama_tbl;
ORA-00980: synonym translation is no longer valid

Creating a trace file in oracle 9i

Hi,
I would like to genrate a trace file in oracle 9i for a single statement.
Can anyone let me know how to do it.

[http://www.dbasupport.com/oracle/ora10g/session_tracing301.shtml]
[http://www.oracle-base.com/articles/8i/TKPROFAndOracleTrace.php]
[http://www.morganslibrary.org/reference/autotrace.html]
[http://www.morganslibrary.org/reference/trace_tkprof.html]
[http://www.morganslibrary.org/reference/explain_plan.html]

Too many trace files generated by program ORACLE.EXE (J001) in "bdump"

Hi,
Please help!
the following trace file messages have been created in my "bdump" folder about every 6 minutes, so it generates about 200 files per hours. Can someone tell me how to solve the error or stop the trace files be generated. Thanks.
Windows thread id: 5520, image: ORACLE.EXE (J001)
*** 2009-05-22 12:49:21.372
*** ACTION NAME:() 2009-05-22 12:49:21.372
*** MODULE NAME:() 2009-05-22 12:49:21.372
*** SERVICE NAME:(SYS$USERS) 2009-05-22 12:49:21.372
*** SESSION ID:(312.292) 2009-05-22 12:49:21.372
java.io.IOException: service early exit: code=1 : err=The system cannot find the path specified.
: out=
at oracle.wh.runtime.server.Util.execRuntimeService(Util.java:122)
CJ

No version number and not enough information in what you posted to help you.
Did this just start?
If so what actions preceded it?
Or is this a new install?
Have you tried bouncing the instance?
If it were my system I would have already searched the knowledgebase at metalink and opened an SR if I couldn't find a solution. Did you?

LRM -00109:could not open parameter file Oracle 10g in Solaris 10

Hallo! I have just installed Oracle 10g in Solaris 10.When I logged into sqlplus / as sysdba if found that I was connected to an idle instance. When I tried to startup open the db, the following error appeared
Connected to an idle instance.
SQL> startup open;
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/export/home/oracle/product/10.2.0/db_1/dbs/initsolaris.ora'
My pfile has the name init.ora and not initsolaris.ora.How can I change the settings to make the Oracle database start via pfile init.ora.
Eventually,I would like the db to read the spfile spfileorcl.ora during the startup.How can I achieve this?
Thanks

4joey1 wrote:
Hallo! I have just installed Oracle 10g in Solaris 10.When I logged into sqlplus / as sysdba if found that I was connected to an idle instance. When I tried to startup open the db, the following error appeared
Connected to an idle instance.
SQL> startup open;
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/export/home/oracle/product/10.2.0/db_1/dbs/initsolaris.ora'
My pfile has the name init.ora and not initsolaris.ora.How can I change the settings to make the Oracle database start via pfile init.ora.
By default, oracle will look first for a spfile named "spfile<ORACLE_SID>.ora". Lacking that, it will try to find "init<ORACLE_SID>).ora.
Eventually,I would like the db to read the spfile spfileorcl.ora during the startup.How can I achieve this?
Once you have started the db (I believe a startup nomount will be sufficient) you can issue CREATE SPFILE ... Details are in the fine SQL Reference manual found at tahiti.oracle.com
BTW, "open" is the default behavior of "startup", so no need to specify it. A simple "startup" does the same thing.
Thanks

Fail to ping standby . error = 3113 in trace files (oracle 9i)

Hi there. One of my standby databases is not working properly, I mean is not synchronized with primary. Both database are 9i Release 2 running on Compaq Tru64 servers
I look for the primary trace files and I found this trace file:
$ vi umercado_arc1_141731.trc
"umercado_arc1_141731.trc" 28 lines, 1164 characters
/oracle/app/oracle/admin/umercado/bdump/umercado_arc1_141731.trc
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /oracle/app/oracle/product/9.2.0
System name: OSF1
Node name: utora01.emsut.com.sv
Release: V5.1
Version: 2650
Machine: alpha
Instance name: umercado
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 141731, image: [email protected] (ARC1)
*** SESSION ID:(10.1) 2008-09-02 16:03:38.240
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
*** 2008-09-03 11:22:29.405
RFS network connection lost at host 'umercado3'
Fail to ping standby 'umercado3', error = 3113
Error 3113 when pinging standby umercado3.
*** 2008-09-03 11:22:29.411
kcrrfail: dest:3 err:3113 force:0
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
The error I want to highlight is "FAIL TO PING STANDBY UMERCADO3, ERROR 3113"
I did this testings on the primary server:
- Unix ping to standby node , ok
- tnsping to standby database (tnsping umercado3), ok
Therefore I do not find the reason for this error. By this time I have defeered the transfer from the primary to standby.
Any advice is welcome.
Thanks!

Suggestion: would attempt to make a sqlplus connection from the primary to the standby using the tns entry that you have configured for the log_archive_dest parameter. you need to connect to the standby as sys.
What happened:
I did a sqlplus connection ON THE PRIMARY DATABASE using the tns entry that is exactly the same used in log_archive_dest_2 parameter. Here is it:
SQL> conn sys/*********@UMERCADO3 as sysdba
Connected.
Therefore I do not think it is a problem in the standby password file.
Any suggestions?

Do trace files need to be purged in Oracle 11g DB

We have the Oracle 11g database setup. I have a query as to if it is required to purge the trace files found in adump, Bdump & Cdump administration file subdirectories or there is automatic log rotation of the trace files?
I hope my query is clear that if it is required to manually purge the trace files or is there an automatic log rotation for the trace files.
Please revert with the reply to my query.
Regards

starting with 11g and ADRCI there are two Parameters which controls the purging of old log and / or trace files:
SHORTP_POLICY (default 720 hours) and LONGP_POLICY (default 8720 hours). As with the Default most traces and logs stay an entire year it might be worth changing those values like follows:
adrci> set control (SHORTP_POLICY = 168)
adrci> set control (LONGP_POLICY = 720)
you can verify the current values with
adrci> show control
Unfortunately those parameters are only valid for components managed with ADR (Automatic Diagnostic Repository). So adump or any log locations under $ORACLE_HOME are still not managed automatically.

How to disable trace files in oracle version 11g

Senario : trace file are growing
How to disable trace files in oracle version 11g
pls guide with best practice

SHANOJ wrote:
Senario : trace file are growing
How to disable trace files in oracle version 11g
pls guide with best practiceIn 11g, there is an extensive tracing that happens for the reasons best known to Oracle only. But if you want to disable it, Coskan had published a small post mentioning an undocumented parameter(which means you must think twice before using it) to disable it- disablehealth_check* . You may want to read the complete post here,
http://coskan.wordpress.com/2009/06/03/too-many-trace_file-on-11g/
Aman....

Oracle 9i (SE) Solaris 9 (Trace Files)

Similar Messages

Maybe you are looking for