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**************************************** **************
controlfile to trace; translate the control file into a script for creating the control file. The path is in the directory of the user warning file (you can view it through show parameter user_dump;) with the suffix trc.
Or find the following method:
SELECT d. VALUE| '/'| LOWER (RTRIM (I. INSTANCE, CHR (0 )))| '_ Ora _'| P. spid| '. Trc' trace_file_nameFROM (SELECT p. spidFROM v $ mystat m, v $ session s,
. The background trace file is generated based on the running status of the background process. The background trace file is also saved in the directory specified by the BACKGROUND_DUMP_DEST parameter. The file format is siddbwr. trc and sidsmon. trc.
Another type is the user trace file generated by the user process connected to Oracle. These files are generated only when errors occur during user sessions.
-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-lvhome20G 19G 11 M 100%/home/dev/mapper/vgoradata-lvoradata144G 48G 90G 35%/u01/oradata/dev/mapper/vgbackup-lvbackup193G 7.8G 175G 5%/u01/backup via the following command find useless files, then delete [root @ ticketb ~] # Find/home/oracle/admin/dbticb/udump/-name "dbticb _*.
A friend encountered a problem with ORA-04031. Although this error is very common, the Case here is also a little shocking!
A friend encountered a problem with ORA-04031. Although this error is very common, the Case here is also a little shocking!
A friend encountered a problem with ORA-04031. Although this error is very common, the Case here is also a little shocking!
Tue Aug 26 11:51:13 2014Errors in file/Oracle/app/oracle/diag/rdbms/xx/xx1/trace/xx1_p485_28873.
Record A ORA-600 [13013] processing process and an alert Log with a ORA-600 [13013] error found after a database exception is completed
Record A ORA-600 [13013] processing process and an alert Log with a ORA-600 [13013] error found after a database exception is completed
Record one ORA-600 [13013] Process
A ORA-600 [13013] error was found in the alert Log after a database exception was completed
Thu Mar 08 23:29:37 2012
Errors infile/opt/Oracle/diag/rdbms/chf/trace/chf_smon_24137.
Basic Elementsthe day before yesterday finally successfully to the user to export the entire database, and today the user also told the export data can not be imported, first asked the user what error, to my answer is a ' job ' SYSTEM. " Sys_import_full_03 "Because of fatal error in XXXX elapsed 0 03:01:06 Stop", no other hints, the amount of information is too little, this processing is quite troublesome. Problem AnalysisStep One: First or add tracking informationstill have to rely on their own
A customer told me today that the logs of the slave database of a core database are increasing rapidly. Through checking, alert logs continuously report errors, as shown below: The code is as follows:Copy code Fri Dec 11 20:48:37 2015Incomplete read from log member '/arch2/2_82548_864474703.dbf'. Trying next member.Incomplete read from log member '/arch2/2_82548_864474703.dbf'. Trying next member. Archived Log entry 101817 added for thread 2 sequence 82548 ID 0xedd14d2a dest
slave machine.
I went to work on Monday. I didn't remotely check the performance of this xx production center database and set anything because of other issues that need to be handled. This is also the case during the morning peak.
In the afternoon, suddenly, RTX blinks the busy avatar, Y's. Click it, the testing department, the quality check department, the ETL department, and the xx data production department are shouting. How can we not connect to it? I also hurry to remotely look at this xx
Symptom:An error is reported in the alert Log when the Oracle database is started:SUCCESS: diskgroup DATADG was mountedErrors in file/oracle/app/11gR1/diag/rdbms/rac/rac2/trace/rac2_mmon_1_6.trc (incident = 240612 ):ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [17510], [], [], [], [], [], [], [], [], [], [], []ORA-17510: Attempt to do I/o beyond file sizeIncident details in:/oracle/app/11gR1/diag/rdbms/rac/rac2/inciden
/mapper/vgoradata-lvoradata144G 48G 90G 35%/u01/oradata/dev/mapper/vgbackup-lvbackup193G 7.8G 175G 5%/u01/backup via the following command find useless files, then delete [root @ ticketb ~] # Find/home/oracle/admin/dbticb/udump/-name "dbticb _*. trc "-mtime + 50 | xargs rm-rf. Then, check the disk space usage and find that no/home space has changed. [root @ ticketb ~] # Df-hFilesystem Size Used Avail Use % Mounted on/dev/sda1 981 M 203 M 729 M 22%/non
useless files. When I delete the files, I find that the available space has not changed OS: centos4.7: I found the current 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- lvhome 20G 19G 11 M 100%/home/dev/mapper/vgoradata-lvoradata 144G 48G 90G 35%/u01/oradata/dev/mapper/vgbackup-lvbackup
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.