ORA-03113: end-of-file on communication channel
ORA-03113: end-of-file on communication channel
1. 当启动Oracle 发现报错
SQL> startup
报错:
ORA-03113: end-of-file on communication channel
查看alert.log文件,发现
ORA-03113: end-of-file on communication channel
cannot reclaim 45680128 bytes disk space from 2147483648 limit
ARCH: Error 19809 Creating archive log file to '/u01/flash_recovery_area/ORCL/archivelog/2014_01_17/o1_mf_1_6_%u_.arc'
这是由于归档表空间已满,分配不到空间所致
解决办法如下:打开数据库至mount模式,而后删除需要废弃的文件:
RMAN> startup nomount;
Oracle instance started
Total System Global Area 835104768 bytes
Fixed Size 2217952 bytes
Variable Size 587204640 bytes
Database Buffers 243269632 bytes
Redo Buffers 2412544 bytes
RMAN> resotre spfile from autobackup;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "advise, allocate, alter, backup, @, catalog, change, configure, connect, convert, copy, create, crosscheck, delete, drop, duplicate, exit, flashback, grant, host, import, list, mount, open, print, quit, recover, register, release, repair, replace, report, reset, restore, resync, revoke, run, send, set, show, shutdown, spool, sql, startup, switch, transport, unregister, upgrade, validate, {, "
RMAN-01008: the bad identifier was: resotre
RMAN-01007: at line 1 column 1 file: standard input
RMAN> alter database mount;
database mounted
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 1 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 2 27-DEC-13
Backup Piece 2 27-DEC-13 /u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_nnndf_TAG20131227T172528_9cwb48k0_.bkp
Archive Log 2 27-DEC-13 /u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_7_9cwq8sbj_.arc
Backup Set 1 27-DEC-13
Backup Piece 1 27-DEC-13 /u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_ncsnf_TAG20131227T172528_9cwb7lrp_.bkp
Archive Log 1 27-DEC-13 /u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_6_9cwq0xm1_.arc
Archive Log 3 27-DEC-13 /u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_5_9cwm7cv6_.arc
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_nnndf_TAG20131227T172528_9cwb48k0_.bkp RECID=2 STAMP=835306248
deleted archived log
archived log file name=/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_7_9cwq8sbj_.arc RECID=2 STAMP=835306247
deleted backup piece
backup piece handle=/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_ncsnf_TAG20131227T172528_9cwb7lrp_.bkp RECID=1 STAMP=835306248
deleted archived log
archived log file name=/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_6_9cwq0xm1_.arc RECID=1 STAMP=835306247
deleted archived log
archived log file name=/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_5_9cwm7cv6_.arc RECID=3 STAMP=835306247
Deleted 5 objects
RMAN> alter datatbase open;
推荐阅读:
ORA-01172、ORA-01151错误处理
ORA-00600 [2662]错误解决
ORA-01078 和 LRM-00109 报错解决方法
ORA-00471 处理方法笔记
ORA-00314,redolog 损坏,或丢失处理方法
ORA-00257 归档日志过大导致无法存储的解决办法

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
