Vol. 7., No. 11
November 17, 1999

Table of Contents
1. Oracle 7.3.3.x for OpenVMS and Y2K
2. Oracle Trace Turned On ByDefault


1. Oracle 7.3.3.xforOpenVMS and Y2K

On October 26, 1999, Oracle made updates to the Year2000Readiness Disclosure on the Oracle web site. Please note that Oracle 7.3.3.x onAlphaOpenVMS has now been classified as non-compliant and non-supported for issuesdealing withY2K. For the full white paper, please see the following


Oracle and associated patches are now available in the ITECGetsoftware area:

ORA7343AXPTCH 14049 11/99 AXP Oracle Patches 7343
ORA7343AXP 908649 8/99 AXP Oracle

If you plan to upgrade to Oracle please contact SCADM( so that we can fax you a copy of the release notes.This is theonly documentation that explains the migration path to Oracle

Submitted by Joe Lofft,


2. Oracle TraceTurned On ByDefault

It has come to ITEC's attention that on NT and certainUNIXplatforms Oracle Trace is turned on by default during installation. This canlead toserious performance problems. Please see the notes below for additionalinformation andworkarounds.


Doc ID: Note:45482.1
Folder: OEM General Information
Topic: Alerts
Creation date: 04-SEP-1997
Last Revision Date: 02-FEB-1998
Product: Oracle Trace
Oracle Trace is Enabled by default


Versions Affected
Oracle Trace was introduced in Oracle7 release: It is enabled bydefault (wheninstalled) in 7.3.2 onwards.

Platforms Affected
Most Unix platforms 7.3.2 onwards
Windows NT 7.3.3 onwards

Oracle Trace is a new, common tracing mechanism that is automatically enabledin Oracle7.3 on many platforms. Products instrumented with Oracle Trace include:
SQL*Net v2.3
Oracle Server 7.3
Oracle Forms 5.0
Unless specific actions are taken Oracle Trace may be enabled when it is notrequired.

Likelihood of Occurrence
On Unix platforms it is quite likely there is some impact from Oracle Tracebeing enabled,even if this is only a small performance degradation. Most of the problems arefixed withOracle 7.3.3 but it is still sensible to disable Oracle Trace if it is notrequired.

Please Note: Oracle trace works well if correctly configured and used in atargetedmanner. The problems described here can occur when Oracle Trace is notconfigured and iswidely enabled, especially with 7.3.2.

Possible Symptoms
Widespread use of Oracle Trace can have a number of apparently mysterious sideeffectsincluding:
- Very slow database connect times
- Poor Oracle response times
- High disk space usage by the file 'process.dat'
- Oracle errors attaching to the SGA, such as ORA 7307 or ORA 7337
- Protocol errors (such as TNS 12164) errors from SQL*Net
- Sessions aborting or hanging when connecting to the instance
- Bus errors and/or core dumps from SQLPLUS or SVRMGRL
- Trace files being written to the default USER_DUMP_DEST rather than theactual settingof USER_DUMP_DEST
- Zero length trace files

Workaround / Patches
There are no patches available.

Two workarounds exist:
A. If you wish to disable Oracle Trace totally you simply need to remove the'*.dat'configuration files.
B. If you do wish to disable Oracle Trace for specific processes only you canuse theEPC_DISABLED environment variable. Setting this to TRUE will DISABLEtracing.

Workaround A - No Oracle Trace output required:
1. Shut down all 7.3 databases and listeners.
2. Remove the Oracle Trace files:

Unix NT
~~~~ ~~
cd $ORACLE_HOME/otrace/admin cd orant\otrace73\admin
rm -f *.dat del *.dat
Reboot the NT server

Workaround B - Disable Oracle Trace on specific connections
NB: This workaround is not applicable to NT.

1. Shutdown and remove the trace configuration files as in Workaround A.

2. Reinitialize the Oracle Trace files by typing 'otrccref' in theotrace/admindirectory.

3. To disable Oracle Trace for a particular session set the environmentvariableEPC_DISABLED to TRUE.
    Eg: In a Bourne script:

    In the C-Shell:

4. To set EPC_DISABLED=TRUE for SQL*Net connections you can modify the'SID_LIST_listener' clause in the 'listener.ora' file and add:
    to the SID_DESC for each 7.3 database. Add the entry AFTERthe(ORACLE_HOME=...) clause.


    By using two listener processes you can have one SQL*Netalias whichallows tracing and another that has tracing disabled.

5. Restart and databases and SQL*Net listeners.


NB: Many of the problems listed here occur only in the Beta release ofOracle Trace shipped with 7.3.2.
Connection/query time is slow <PR:1020763.6>
Slow connect times [BUG:443047]
ORA 7307 Unable to attach SGA [BUG:374964]
Server Process hanging [BUG:387185]


Displayed below are the messages of the selected thread.

Thread Status: Closed
From: VINAYAK MAHAJAN 19-Aug-99 16:57
Subject: regid.dat / process.dat files??
RDBMS Version:
Operating System and Version: solaris 2.6
Error Number (if applicable):
Product (i.e. SQL*Loader, Import, etc.): Oracle Server Enterprise Edition
Product Version:
regid.dat / process.dat files??


We've several databases running here on different versions/releases. On someof thedatabases (Version:, the $ORACLE_HOME/otrace/admin/regid.dat andprocess.datfiles are continuosly growing. But on other databases(8.0.3/4/5), the file$ORACLE_HOME/otrace/admin/regid.dat is not being updated and there is noprocess.dat filein that directory.

On all the databases, the Oracle Environment and other configurations aresame. No onehas configured anything specifically for this thing. Then why Oracle Tracing isenabled onsome of the databases, but disabled on others.



From: Oracle, Rob Zijlstra 20-Aug-99 11:20
Subject: Re : regid.dat / process.dat files??


There has been an alert which states that on version 7.3.2.X and 7.3.3.X and7.3.4.XOracle Trace is enabled by default (See Note 45482.1)

Workarounds :
- Remove the collect.dat, regid.dat and process.dat and restart the listenerand databaseswhich use this software version.
To disable Oracle Trace for a particular session set the environment variableEPC_DISABLEDto TRUE.
Eg: In a Bourne script:

In the C-Shell:

4. To set EPC_DISABLED=TRUE for SQL*Net connections you can modify the'SID_LIST_listener' clause in the 'listener.ora' file and add:


to the SID_DESC for each 7.3 database. Add the entry AFTER theORACLE_HOME=...) clause.


From: VINAYAK MAHAJAN 24-Aug-99 22:08
Subject: Re : Re : regid.dat / process.dat files??

Thanks for this information. I'd seen Note 45482.1. It means from 7.3.2onwards, oracletrace is enabled by default. Is Oracle Trace Disabled by default in Oracle8?



From: Barbara Boeksool 14-Sep-99 20:31
Subject: Re : regid.dat / process.dat files??

I have also seen the note and solution 1020763.6 which pretty much says toremove thefiles and set environment variables to disable tracing. In the solutiondescription, #2states that you should check to see that process.dat, regid.dat, collect.datandfacility.dat are no larger than 5MB in size but it doesn't address the reasonwhy or whatto do (if anything different) when they are larger than 5MB. Should they bedeletedregardless of the size?



From: Oracle, Ken Robinson 12-Oct-99 18:56
Subject: Re : regid.dat / process.dat files??

Sorry for missing this thread for so long. Yes, this is enabled in Oracle bydefault.Yes you can delete the files no matter how big. I added a remark to the writerof thatnote to have them change the text-- don't see a reason to check for size atall.



Editor:   Barbara A. Boquard
ITEC's General Office 716/878-ITEC (4832)
Operations 716/878-5122
FAX 716/878-4235
Web Page