Oracle报错Non critical error ORA-00001 caught while writing to trace file"XXX"

测试库今天巡检DB alert日志发现如下报错,Non critical error ORA-00001 caught while writing to trace file“xxx”, 详细查询如下红色标识原因为, DB空间不足。
查询ORA-00001报错如下, 介绍ORA-00001能触发的原因, 并非为空间不足问题引起的, 而此处DB因空间问题引发ORA-00001异常,应该为DB(11.2.0.1.0)一个BUG.
[oracle@jietestdb ~]$ oerr ora 00001
00001, 00000, "unique constraint (%s.%s) violated"
// *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
//         For Trusted Oracle configured in DBMS MAC mode, you may see
//         this message if a duplicate entry exists at a different level.
// *Action: Either remove the unique restriction or do not insert the key.

Wed Dec 02 01:01:36 2015
Non critical error ORA-00001 caught while writing to trace file "/u01/app/oracle/diag/rdbms/test11g/test11g/trace/test11g_dw00_31506.trc"
Error message: 
Writing to the above trace file is disabled for now on...
Wed Dec 02 01:01:39 2015
Non critical error ORA-00001 caught while writing to trace file "/u01/app/oracle/diag/rdbms/test11g/test11g/trace/test11g_dm00_31499.trc"
Error message: 
Writing to the above trace file is disabled for now on...
Wed Dec 02 01:30:00 2015
Non critical error ORA-00001 caught while writing to trace file "/u01/app/oracle/diag/rdbms/test11g/test11g/trace/test11g_j000_31856.trc"
Error message: Linux-x86_64 Error: 28: No space left on device

解决方法:
此处为/u01分区空间不足.
1.  /u01下 undo,tem p,system,sysaux等空间, 迁移到其它空间充足的分区. 以释放/u01空间.
    此处我在其它DB分区, 如/data目录下, 重新创建undo tablespace  UNDOTBS2, 并设置undotbs2表空间为默认表空间（ALTER SYSTEM SET undo_tablespace='UNDOTBS2' SCOPE=BOTH;）.
并drop UNDOTBS1表空间(DROP TABLESPACE UNDOTBS1 INCLUDING CONTENTS AND DATAFILES), 以释放/u01分区空间.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/28569596/viewspace-1851250/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/28569596/viewspace-1851250/