ORA-16038简单的处理过程

本文记录了解决Oracle 10g实例中ORA-16038错误的过程,该错误因归档日志空间不足引起。通过检查归档日志、调整db_recovery_file_dest_size大小及清理旧备份解决此问题。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

作者:gtlions 【转载时请以超链接心事标明文章出处作者信息,谢谢.】

链接:http://blog.youkuaiyun.com/gtlions/archive/2010/04/02/5446069.aspx

今天同事的笔记本上的一个oracle 10g实例出现了错误,同事无法处理,我就接过来看了下并解决之。

解决过程记录如下。

检查了下alter日志:

-------------------------------------------------------------------------------------------------------------

Fri Apr 02 09:56:09 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/bdump/orcl_arc1_5392.trc:
ORA-16014: log 1 sequence# 93 not archived, no available destinations
ORA-00312: online log 1 thread 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO01.LOG'

Fri Apr 02 09:56:09 2010
ARCH: Error 19809 Creating archive log file to 'D:/ORACLE/PRODUCT/10.2.0/FLASH_RECOVERY_AREA/ORCL/ARCHIVELOG/2010_04_02/O1_MF_1_89_U_.ARC'
Fri Apr 02 09:56:09 2010
ARCH: Failed to archive thread 1 sequence 89 (19809)
ORA-16038 signalled during: alter database open...
Fri Apr 02 09:57:09 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 09:58:09 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 09:59:09 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 09:59:44 2010
alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline
Fri Apr 02 09:59:44 2010
ORA-1516 signalled during: alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline...
Fri Apr 02 10:00:09 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:00:56 2010
alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline drop
Fri Apr 02 10:00:56 2010
ORA-1516 signalled during: alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline drop...
Fri Apr 02 10:01:08 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 89 (4)
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:01:23 2010
alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline drop
Fri Apr 02 10:01:23 2010
ORA-1516 signalled during: alter database datafile 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG' offline drop...
Fri Apr 02 10:02:09 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/bdump/orcl_arc1_5392.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 100.00% used, and has 0 remaining bytes available.

Fri Apr 02 10:02:09 2010
************************************************************************
You have following choices to free up space from flash 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.
************************************************************************
Fri Apr 02 10:02:09 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/bdump/orcl_arc1_5392.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 47716352 bytes disk space from 2147483648 limit

ARC1: Error 19809 Creating archive log file to 'D:/ORACLE/PRODUCT/10.2.0/FLASH_RECOVERY_AREA/ORCL/ARCHIVELOG/2010_04_02/O1_MF_1_89_U_.ARC'
ARC1: Failed to archive thread 1 sequence 89 (19809)
ARCH: Archival stopped, error occurred. Will continue retrying
Fri Apr 02 10:02:10 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/bdump/orcl_arc1_5392.trc:
ORA-16038: log 2 sequence# 89 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG'

Fri Apr 02 10:02:56 2010
Archive Log Next
ARCH: Archiving not possible: No primary destinations
ARCH: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:02:56 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_5404.trc:
ORA-16014: 日志 2 的序列号 89 未归档, 没有可用的目的地
ORA-00312: 联机日志 2 线程 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG'

Archive Log Next
ARCH: Archiving not possible: No primary destinations
ARCH: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:02:59 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_5404.trc:
ORA-16014: 日志 2 的序列号 89 未归档, 没有可用的目的地
ORA-00312: 联机日志 2 线程 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG'

Archive Log Next
ARCH: Archiving not possible: No primary destinations
ARCH: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:03:00 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_5404.trc:
ORA-16014: 日志 2 的序列号 89 未归档, 没有可用的目的地
ORA-00312: 联机日志 2 线程 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG'

Fri Apr 02 10:03:09 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 89 (4)
ARCH: Archival stopped, error occurred. Will continue retrying
Fri Apr 02 10:03:09 2010
Errors in file d:/oracle/product/10.2.0/admin/orcl/bdump/orcl_arc0_4208.trc:
ORA-16014: log 2 sequence# 89 not archived, no available destinations
ORA-00312: online log 2 thread 1: 'D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG'

Fri Apr 02 10:04:09 2010
alter database drop logfile member 'D:/oracle/product/10.2.0/oradata/orcl/REDO02.LOG'
Fri Apr 02 10:04:09 2010
ORA-361 signalled during: alter database drop logfile member 'D:/oracle/product/10.2.0/oradata/orcl/REDO02.LOG'...
Fri Apr 02 10:04:09 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 89 (4)
Fri Apr 02 10:04:36 2010
alter database clear unarchived logfile 'D:/oracle/product/10.2.0/oradata/orcl/REDO02.LOG'
Fri Apr 02 10:04:36 2010
WARNING! CLEARING REDO LOG WHICH HAS NOT BEEN ARCHIVED. BACKUPS TAKEN
BEFORE 03/31/2010 09:16:02 (CHANGE 3059992) CANNOT BE USED FOR RECOVERY.
Clearing online log 2 of thread 1 sequence number 89
Completed: alter database clear unarchived logfile 'D:/oracle/product/10.2.0/oradata/orcl/REDO02.LOG'
Fri Apr 02 10:04:50 2010
alter database open
Fri Apr 02 10:04:56 2010
Thread 1 advanced to log sequence 95
Thread 1 opened at log sequence 95
Current log# 2 seq# 95 mem# 0: D:/ORACLE/PRODUCT/10.2.0/ORADATA/ORCL/REDO02.LOG
Successful open of redo thread 1
Fri Apr 02 10:04:57 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Apr 02 10:04:58 2010
ARC0: Archiving not possible: No primary destinations
Fri Apr 02 10:04:58 2010
SMON: enabling cache recovery
Fri Apr 02 10:04:58 2010
ARC0: Failed to archive thread 1 sequence 93 (4)
Fri Apr 02 10:04:58 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 93 (4)
Fri Apr 02 10:04:59 2010
Successfully onlined Undo Tablespace 1.
Fri Apr 02 10:04:59 2010
SMON: enabling tx recovery
Fri Apr 02 10:05:00 2010
Database Characterset is ZHS16GBK
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=21, OS id=4272
Fri Apr 02 10:05:09 2010
Completed: alter database open
Fri Apr 02 10:05:12 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 93 (4)
Fri Apr 02 10:05:15 2010
Starting background process EMN0
EMN0 started with pid=28, OS id=5144
Fri Apr 02 10:05:15 2010
Shutting down instance: further logons disabled
Fri Apr 02 10:05:16 2010
ksvcreate: Process(q001) creation failed
Fri Apr 02 10:05:17 2010
Stopping background process QMNC
Fri Apr 02 10:05:18 2010
Stopping background process CJQ0
Fri Apr 02 10:05:19 2010
Stopping background process MMNL
Fri Apr 02 10:05:23 2010
Stopping background process MMON
Fri Apr 02 10:05:27 2010
Shutting down instance (immediate)
License high water mark = 7
Fri Apr 02 10:05:27 2010
Stopping Job queue slave processes
Fri Apr 02 10:05:27 2010
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Fri Apr 02 10:05:35 2010
ALTER DATABASE CLOSE NORMAL
Fri Apr 02 10:05:36 2010
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Apr 02 10:05:39 2010
LGWR: Waiting for ORLs to be archived...
Fri Apr 02 10:06:08 2010
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 93 (4)
Fri Apr 02 10:06:11 2010
Shutting down archive processes
Fri Apr 02 10:06:16 2010
ARCH shutting down
ARC2: Archival stopped
Fri Apr 02 10:06:16 2010
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 93 (4)
Fri Apr 02 10:06:39 2010
LGWR: Archiving did not complete

### 关于 Oracle 数据库错误 ORA-39083、ORA-31625 和 ORA-01435 的原因及解决方案 #### ORA-39083 错误分析与解决办法 当遇到 `ORA-39083` 错误时,通常表示对象创建过程中出现了其他类型的子错误。具体来说: - 如果伴随的是 `ORA-01917: 用户或角色不存在` 这样的提示,则意味着尝试操作的对象依赖于某个特定用户或角色的存在,但在当前环境中这些实体并不存在[^1]。 针对这种情况的一个常见场景是在执行数据泵导入(`impdp`)命令期间发生此问题,这可能是因为源数据库中存在的某些用户并未被复制到目标环境里所致[^4]。为了修复这个问题,在开始实际的数据迁移之前应该先手动建立好必要的账户结构;另外也可以通过调整参数文件中的设置来忽略掉那些无法找到对应用户的权限授予语句。 对于由索引统计信息引起的同类情况(即带有 `INDEX_STATISTICS` 类型描述的情况),可以考虑利用 Data Pump 工具自带的功能选项排除这类元数据项的传输过程[^2]。 ```sql -- 示例:跳过指定模式下的所有 INDEX 统计信息 EXCLUDE=STATISTIC:"IN ('SCHEMA_NAME')" ``` #### ORA-31625 错误解析及其处理措施 虽然未直接提供有关 `ORA-31625` 的确切解释材料,但从经验来看此类编码往往指向连接至远程服务器所需的信息不足的问题——特别是缺少有效的网络服务名定义或是监听器配置不当等原因造成的链接失败现象。因此建议检查客户端使用的 TNS 配置是否正确无误,并确认远端实例处于可访问状态。 此外,如果应用程序试图启动一个外部作业却未能成功获取足够的上下文支持也会触发类似的警告消息。此时应确保相关组件已正确定义并且具有适当的操作权限。 #### ORA-01435 错误说明以及应对策略 `ORA-01435: user does not exist` 明确指出所指代的用户名不在系统内注册。这一状况经常发生在脚本中硬编码了固定的身份验证凭证但后来又更改了默认方案的情况下,或者是像前面提到过的那样由于跨不同版本间移植而导致部分辅助性账号丢失的情形下发生的[^5]。 要克服这个障碍,最简单的方法就是核实输入的名字拼写准确性,同时核查是否有遗漏创建新实例所需的初始化脚本步骤。如果是批量自动化流程的一部分,则应当增强其健壮性和灵活性以适应动态变化的工作负载需求。 ---
评论 2
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值