Skip to content
pvmehta.com

pvmehta.com

  • Home
  • About Me
  • Toggle search form
  • My FTP Job Scheduling for www.pvmehta.com PHP/MYSQL/Wordpress
  • S3 Basic info AWS
  • DETERMINING WHICH INSTANCE OWNS WHICH SHARED MEMORY & SEMAPHORE SEGMENTS Oracle
  • oracle Dba site Oracle
  • Privileges Required to Create Procedures and Functions that uses objects from other schema. Oracle
  • Oracle Recommended Patches — Oracle Database ID 756671.1 Oracle
  • Very clear article about oracle dataguard Oracle
  • Some useful Unix Commands Linux/Unix
  • refre.sql Oracle
  • Important Script Method for tuning Oracle
  • For Search and replace unix command. Linux/Unix
  • New Latest Param.sql for finding all hidden parameters also Oracle
  • Oracle Identifiers Oracle
  • Paste command syntax Linux/Unix
  • longtx.sql Oracle

How to Make Trace Files Created by Oracle Readable by All Users ?

Posted on 27-May-2009 By Admin No Comments on How to Make Trace Files Created by Oracle Readable by All Users ?

Problem Description:

~~~~~~~~~~~~~~~~~~~~

How do you make all trace files that Oracle creates readable to owner, group,

and world or public?

Any “*.trc” files created by Oracle have permissions of 640, with owner of

Oracle and group DBA.

For example: -rw-r—– oracle dba

Setting umask in the users login script (.cshrc or .profile) does not effect the

permissions on any trace files that are created by Oracle.

Solution Description:

~~~~~~~~~~~~~~~~~~~~~

Edit the “init.ora” file to include the “_trace_files_public”

parameter by doing the following steps:

1. Change your location to the “dbs” directory

% cd to $ORACLE_HOME/dbs

2. Edit the “init.ora” file

Add the line:

_trace_files_public = true

3. Save the file.

4. Bounce the database so the new parameters take effect.

or if using spfile

1. Modify spfile via following sql command

SQL> alter system set “_trace_files_public” = true scope=spfile;

2. Bounce the database so the new parameter takes effect.

Oracle, SQL scripts

Post navigation

Previous Post: How To Limit The Access To The Database So That Only One User Per Schema Are Connected (One Concurrent User Per Schema)
Next Post: find_string_in_database.sql

Related Posts

  • dbinv.sql Oracle
  • cache buffer chain latch Oracle
  • Oracle Support Metalink ID 161818.1 Oracle
  • RAC 11g with vmware Oracle
  • Configure ssh authentications for RAC Oracle
  • EXTPROC Oracle

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • Ansible (0)
  • AWS (2)
  • Azure (1)
  • Django (0)
  • GIT (1)
  • Linux/Unix (150)
  • MYSQL (5)
  • Oracle (403)
  • PHP/MYSQL/Wordpress (10)
  • POSTGRESQL (1)
  • Power-BI (0)
  • Python/PySpark (7)
  • RAC (18)
  • rman-dataguard (26)
  • shell (151)
  • SQL scripts (349)
  • SQL Server (6)
  • Uncategorized (5)
  • Videos (0)

Recent Posts

  • Key Management in Oracle: The Core Issue: Missing Master Key12-May-2026
  • SAT Mathematics 10 questions and answer at the end.30-Apr-2026
  • top 10 AI news today30-Apr-2026
  • runon_allpdbs_show_conname.sh23-Apr-2026
  • runon_allcdbs_find_pdbs.sh23-Apr-2026
  • Running PDB on single node in RAC09-Apr-2026
  • find_arc.sql09-Apr-2026
  • pvm_pre_change.sql08-Apr-2026
  • find_encr_wallet.sql08-Apr-2026
  • find_pdbs.sql08-Apr-2026

Archives

  • 2026
  • 2025
  • 2024
  • 2023
  • 2010
  • 2009
  • 2008
  • 2007
  • 2006
  • 2005
  • Oracle Data Direct to TAPE Oracle
  • shutdown linux Linux/Unix
  • Changing unix system clock when Oracle database is running. Oracle
  • cur_sql.sql Oracle
  • ENQ: KO – FAST OBJECT CHECKPOINT tips Oracle
  • catall.sh Linux/Unix
  • How to change hostname in Linux Linux/Unix
  • Another export with Query Oracle

Copyright © 2026 pvmehta.com.

Powered by PressBook News WordPress theme