The following is a list of file types and names used by Oracle.
Database files such as
sid
.
DBS
.
CONTROL
.
DBF
,
sid
.
DBS
.
DATABASE1
.
DBF
, or
sid
.
DBS
.
LOG1
.
DBF
contain the entire Oracle database including data dictionary, user tables, log files, and so on.
Parameter file used when instance is started.
Environment file containing user environment. Always to be run before start of an instance or an application:
/DO
sid
.
P
.
ORAENV
.
S.E.tsn.YYYY-MM-DD.hh.mm.ss
Temporary
ENTER-PROCEDURE
file for starting background processes (using
$ORAC1020.DEMO.P.ENTER
).
S.OUT.tsn.YYYY-MM-DD.hhmmss
Temporary files of background processes containing run-time
information. After a task is successfully completed, these files are
removed. These files can help diagnosis.
Run-time listing documenting the start of a background process. When process finishes orderly listings are removed, except the
SDF-P
variable
BJGOUT
is set to
KEEP
in
sid
.
P
.
ORAENV
for diagnosis purposes.
xxxx corresponds with the identifier of Oracle background jobs.
Oracle Net Services LOG files
All errors encountered in Oracle network products are appended to a log file. The default directory path on BS2000/OSD is
network.log
. For more information about Oracle Net Services log files, refer to
Oracle Database Net Services Administrator's Guide .
This file lists the log of significant events and errors of the
database. If this file exits, the same file is used, else a new file is
created. This file is valuable for diagnosis, and should not be removed.
To be removed after successful installation.
To be removed after successful installation.
To be removed after successful installation, for example,
L
.
sid
.
CATALOG
.
LOG
.
ORAXALOG.tsn-NULL-YYMMDD.TRC
This file is used to trace errors when
openUTM is used with Oracle. This file is created only when an error occurs.
NULL
can be replaced by a
db_name
when specified in the open string.
This trace file is created for one of the following reasons:
-
To be analyzed by TKPROF utility, created after switch on of SQL trace by
alter session set sql_trace=true;
-
To be analyzed when internal errors (example: ORA-00600) or special events occur