RAC 启动的时候错误ORA-03113

    xiaoxiao2022-07-03  110

    RDBMS 12.1.0.2 三节点rac

    在单独的节点上startup的时候,发现启动后立马出现错误,end-of-file on communication channel之类的

    在使用srvctl start database -d 命令启动的时候,直接报错

    [grid@rac01 ~]$ srvctl start database -d racdb PRCR-1079 : Failed to start resource ora.racdb.db CRS-5017: The resource action "ora.racdb.db start" encountered the following error: ORA-03113: end-of-file on communication channel Process ID: 1017 Session ID: 355 Serial number: 18700 . For details refer to "(:CLSN00107:)" in "/u01/app/grid/diag/crs/rac03/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.racdb.db' on 'rac03' failed CRS-2632: There are no more servers to try to place resource 'ora.racdb.db' on that would satisfy its placement policy CRS-5017: The resource action "ora.racdb.db start" encountered the following error: ORA-03113: end-of-file on communication channel Process ID: 10909 Session ID: 355 Serial number: 35123 . For details refer to "(:CLSN00107:)" in "/u01/app/grid/diag/crs/rac02/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.racdb.db' on 'rac02' failed CRS-5017: The resource action "ora.racdb.db start" encountered the following error: ORA-03113: end-of-file on communication channel Process ID: 12934 Session ID: 1 Serial number: 27997 . For details refer to "(:CLSN00107:)" in "/u01/app/grid/diag/crs/rac01/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.racdb.db' on 'rac01' failed [grid@rac01 ~]$

    使用命令crsctl status resource -t 查看集群状态,发现集群是正常的,只是三个节点上的db没有起来。

    查看启动时候的报错日志,发现没有可以参考信息。

    查看db的alert log日志,发现是fra满了。 确切地说,应该是归档满了。

    Starting background process ARC2 Wed May 22 01:36:30 2019 ARC2 started with pid=43, OS id=13046 Starting background process ARC3 Wed May 22 01:36:30 2019 ARC3 started with pid=44, OS id=13048 ARC1: Archival started ARC2: Archival started Wed May 22 01:36:30 2019 ARC1: Becoming the 'no FAL' ARCH ARC1: Becoming the 'no SRL' ARCH Wed May 22 01:36:30 2019 ARC2: Becoming the heartbeat ARCH Wed May 22 01:36:30 2019 ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE Wed May 22 01:36:31 2019 Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_ora_12934.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 32212254720 bytes is 100.00% used, and has 0 remaining bytes available. Wed May 22 01:36:31 2019 ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Back up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add disk space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Wed May 22 01:36:31 2019 Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_ora_12934.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 42991616 bytes disk space from 32212254720 limit ARCH: Error 19809 Creating archive log file to '+DATA' Wed May 22 01:36:31 2019 Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_arc0_13042.trc: ORA-19815: WARNING: db_recovery_file_dest_size of 32212254720 bytes is 100.00% used, and has 0 remaining bytes available. Wed May 22 01:36:31 2019 ************************************************************************ You have following choices to free up space from recovery area: 1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard, then consider changing RMAN ARCHIVELOG DELETION POLICY. 2. Back up files to tertiary device such as tape using RMAN BACKUP RECOVERY AREA command. 3. Add disk space and increase db_recovery_file_dest_size parameter to reflect the new space. 4. Delete unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands. ************************************************************************ Wed May 22 01:36:31 2019 Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_arc0_13042.trc: ORA-19809: limit exceeded for recovery files ORA-19804: cannot reclaim 13631488 bytes disk space from 32212254720 limit ARC0: Error 19809 Creating archive log file to '+DATA' Wed May 22 01:36:31 2019 Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_ora_12934.trc: ORA-16038: log 2 sequence# 686 cannot be archived ORA-19809: limit exceeded for recovery files ORA-00312: online log 2 thread 1: '+DATA/RACDB/ONLINELOG/group_2.264.996622773' ORA-00312: online log 2 thread 1: '+DATA/RACDB/ONLINELOG/group_2.263.996622773' Wed May 22 01:36:31 2019 USER (ospid: 12934): terminating the instance due to error 16038 Wed May 22 01:36:31 2019 System state dump requested by (instance=1, osid=12934), summary=[abnormal instance termination]. System State dumped to trace file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_diag_12836_20190522013631.trc Wed May 22 01:36:31 2019 Dumping diagnostic data in directory=[cdmp_20190522013631], requested by (instance=1, osid=12934), summary=[abnormal instance termination]. Wed May 22 01:36:31 2019 Instance terminated by USER, pid = 12934

    删除归档后,启动正常。

    因为是测试环境,关闭归档。

    end

    最新回复(0)