讲解Oracle数据库ORA-00257故障的解决过程（Explain the Oracle database ORA-00257 fault resolution process）.docVIP

下载本文档

10
0
约7.75千字
约 12页
2017-07-24 发布于河南
举报
版权申诉

讲解Oracle数据库ORA-00257故障的解决过程（Explain the Oracle database ORA-00257 fault resolution process）.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

讲解Oracle数据库ORA-00257故障的解决过程（Explain the Oracle database ORA-00257 fault resolution process）

讲解Oracle数据库ORA-00257故障的解决过程（Explain the Oracle database ORA-00257 fault resolution process） The Oracle database is currently the industrys most commonly used large database system, I met ORA-00257 error in the actual project (space error), by looking for information, most said it was because of the archive log too much, take up hard disk space all cause, by simply deleting the log or increase the storage space can be solved but I am in Oracle 10g found that there is still a lot of storage space, but also reported that this error was originally a new feature in Oracle 10g, resulting in the management of Flash Recovery 1 hardware and software environment Server HP, Proliant, DL580G4 (Intel, Xeon, 3.16GHz/4GB/, 72.8*4/RAID4) Operating system Red, Flag, DC, Server, release 5 (Trinity), for, x86-64, Linux Database Oracle 10.2.0.1.0 2, the phenomenon of problems The database system has been running for more than half a month, and the ORA-00257 error occurred when the data was updated after connecting the database in the evening of July 24th, as shown below That filing errors, by searching the ORACLE error code, explanation for the lack of disk space, need to delete log space increases, but the server space available 200GB, currently only 10GB or so, which is why? 3 diagnostic process: (1) check the ORACLE database archive log status [root@hrmsdb CD /oracle/flash_recovery_area/HKCHR/archivelog /]# [root@hrmsdb archivelog]# LS 2006_07_04, 2006_07_13, 2006_07_17, 2006_07_20, 2006_07_23 2006_07_11, 2006_07_14, 2006_07_18, 2006_07_21, 2006_07_24 2006_07_12, 2006_07_15, 2006_07_19, 2006_07_22, 2006_07_25 [root@hrmsdb archivelog]# CD 2006_07_25 [root@hrmsdb 2006_07_25]# LS [root@hrmsdb 2006_07_25]# CD../2006_07_24 [root@hrmsdb 2006_07_24]# LS O1_mf_1_92_2d933vgb_.arc o1_mf_1_96_2d954ns7_.arc o1_mf_1_98_2d969d5h_.arc O1_mf_1_95_2d9537cs_.arc o1_mf_1_97_2d956km0_.arc Explains that database archiving has been normal before a problem occurs (2) look at the database REDOLOG situation