Oracle Database Diagnostic File (log) view Diagnostic File (Diagnostic File) 1: Role of the Diagnostic File Diagnostic files: contains information about Major Events encountered in the background. It is used for parsing issues and is used for daily log file management. 2: diagnostic file logs are classified into two categories: 1: alterSID. log ----- background trace files (Background process trace file) 2: trace files --- ----- user trace file (user trace file) 1: Name the background trace file
spid sid serial # username program ----------------------------------------------------------------------------------------------- 24472 1094 30 robin oracle @ SZDB (TNS V1-V3) sys @ SYBO2SZ> @ get_spec_sess_trace_file Enter value for input_sid: 1094 Enter value for input_serial: 30 sid serial # SPID TRACE_FILE ---------- -------------- limit 1094 30 24472/u02/database/SYBO2SZ/udump/blocks -- The following blocks is the number of chunks for a single read. sys @ SYBO2SZ> ho grep scatter/u02/data
The alterdatabasebackupcontrolfiletotrace command in oracle is used to back up the control file as a text file with the. trc suffix. The file name format is sid.
The alter database backup controlfile to trace command in oracle is used to back up the control file as a text file with the. trc suffix. The file name format is sid.
The alter database backup controlfile to trace command in Oracle is used to
enhance query of 1.3 variants and costing SQL variants through prompt: before cost calculation, the SQL statement is equivalent to deformation. Deformation Rules: (1) SQL cannot be changed. (2) if it can be changed, it can be changed. (3) if it can be changed, but the cost is too large, the constant invisible parameter "_ complex_view_merging" will be changed ", false (8i), true (9i), control whether to read the view definition into SQL when a view exists in SQL, and then perform equivalent var
ORA-600 [kcratr_scan_lastbwr] logical bad block solution database version: 11.2.0.3 problem phenomenon: Today when starting a test database, found that db cannot open, the ERROR is as follows: ERROR at line 1: ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [], [] solution: 1. Check alert Log Mon Jul 22 11:35:12 2013 alter database OPENBeginning crash recovery of 1 threads parallel recovery started with 3 processesStarted redo scanHex dump of
$ instance;
STATUS
------------
MOUNTED
SQL>We can see that the database is in the mount state at this time. View the alarm log file to see the entire process more clearly.
[Oracle @ hoegh trace] $ pwd /U01/app/oracle/diag/rdbms/HOEGH/trace
[Oracle @ hoegh trace] $
[Oracle @ hoegh trace] $ tailf alert_HOEGH.log
......
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 2106090167
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
inserted
SQL> commit;
Commit complete
SQL> delete from eymit;
1 row deleted
SQL>
SQL> declare
2 pragma autonomous_transaction;
3 begin
4 delete from eymit;
5 commit;
6 end;
7/
Declare
Pragma autonomous_transaction;
Begin
Delete from eymit;
Commit;
End;
ORA-00060: deadlock detected while waiting for resources
ORA-06512: In line 5
3. Analyze logs
View Alert file information
Mon Dec 24 18:26:04 2012
ORA-00060: Deadlock detected. More info in file/opt/local/oracle/diag/rdbms/gs3421/
$ PROCESS p
Where S. paddr = P. ADDR and S. Username = upper ('trace _ username ');
Oradebug setospid 12345;
Oradebug unlimit;
Oradebug event 10046 trace name context forever, Level 8;
Oradebug event 10046 trace name context off;
Obtain a trail File
1. Use oradebug
SQL> oradebug setmypid
Statement processed.
SQL> oradebug tracefile_name
/Opt/Oracle/product/9.2.0/rdbms/log/uxdb_ora_9183.trc
2. Set the initial parameter tracefile_identifier.
Alter sess
This error has been shown in the alarm log for the past two days:
ORA-00600: Internal error code, arguments: [kcblasm_1], [103], [], [], [], [], [], [], []
Tue Aug 12 09:20:17 CST 2014
Errors in file/u01/APP/Oracle/admin/orcl/udump/orcl_ora_29974.trc:
ORA-00600: Internal error code, arguments: [kcblasm_1], [103], [], [], [], [], [], [], []
Tue Aug 12 09:30:17 CST 2014
Errors in file/u01/APP/Oracle/admin/orcl/udump/orcl_ora_30084.
obvious failure information is found, indicating that it is okay to start the database instance. Then, perform step 2.
SQL> alter database mount;
Fault
It seems that when a fault occurs when a database file is mounted, this step mainly allows specific maintenance operations, such as renaming, adding, deleting, or renaming a data file to redo log files, enable and disable the redo archiving option to perform full database recovery. It does not allow general access to the database ."
Find the $
Database Buffers 100663296 bytes
Redo Buffers 2924544 bytes
Database mounted.
Database opened.
SQL> alter session set SQL _trace = true;
Session altered.
SQL> show parameter sga
NAME TYPE VALUE
-----------------------------------------------------------------------------
Lock_sga boolean FALSE
Pre_page_sga boolean FALSE
Sga_max_size big integer 208 M
Sga_target big integer 208 M
SQL> select u_dump.value | '/' | db_name.value | '_ ora _' | v $ process. spid | nvl2 (v $ process. tra
where a. group # = B. group #;
GROUP # STATUS MEMBER
------------------------------------------------------------------------------
3 INACTIVE + DATA/anqing/onlinelog/redo03.log
2 INACTIVE + DATA/anqing/onlinelog/redo02.log
1 CURRENT + DATA/anqing/onlinelog/group_1.277.751552735
1 CURRENT + FRA/anqing/onlinelog/group_1.20..751552739
4 CURRENT + DATA/anqing/onlinelog/group_4.282.751560131
5 INACTIVE + DATA/anqing/onlinelog/group_5.283.751560139
6 rows selected.
SYS @ anqing1 (rac1)>Alter syst
ORA-03113: end-of-file on communication channel, filechannel
Oracle open error:
SQL> alter database open2;
Alter database open
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 29196
The Session ID is 1144 Serial number: 7.
SQL>
View the background alert Log. The information is shown as follows:
Errors in file/oracle/app/oracle/diag/rdbms/pdunq/powerdes/trace/powerdes_ora_26567.trc:
ORA-19809: limit exceeded fo
1, database log error ORA-00327, pay attention to the garbled here
Errors in file/Oracle/app/oracle/diag/rdbms/tyolap/tyolap3/trace/tyolap3_lgwr_22388.trc:
ORA-00327: Too Many I 31 (too M too
ORA-00312: Memory
Errors in file/oracle/app/oracle/diag/rdbms/tyolap/tyolap3/trace/tyolap3_lgwr_22388.trc:
ORA-00321: Too Many I 31 (too M too
ORA-00312: Memory
Check the error details. The redo file + DATA
No space is released after CentOS deletes the file.
Today, I found that the home space of a server is full, so I want to clear useless files. After I delete the files, I find that the available space has not changed.OS: centos6.0
Symptom:
Disk space usage:
[Root @ ticketb ~] # Df-hFilesystem Size Used Avail Use % Mounted on/Dev/sda1 981 M 203 M 729 M 22%/None, 16G, 0, 16G, 0%/dev/shm/Dev/sda9 2.9G 37 M 2.7G 2%/tmp/Dev/sda7 4.9G 1.9G 2.7G 42%/usr/Dev/sda8 2.9G 145 M 2.6G 6%/var/Dev/mapper/vghome-
/udump/orcl_ora_4132.trc
SQL> alter session set events 'immediate trace name controlf level 8 ';
Session altered.After dumping the control file, let's take a look at the content of the orcl_ora_4132.trc tracking file:A). database content stored in the control file:**************************************** ***********************************DATABASE ENTRY**************************************** **************
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.