ORA-16038和ora-19809错误

关注

原创最新推荐文章于 2026-03-04 01:01:10 发布 1k 阅读 AI 写同款· GEO 优化 ›

一文读懂 SAP Web Dispatcher 配置参考：让 Gateway、OData 与后端服务各走各路 SAP Web Dispatcher在Fiori项目中常被低估，实际上它作为企业系统的HTTP(s)入口，承担着流量分发和安全防护双重职责。该组件通过URL路径规则（如/sap/opu/odata/转发至Gateway系统）实现多系统路由，隐藏后端复杂性，提供统一访问入口。配置要点包括HTTPS参数设置、客户端证书转发、端口定义以及系统冲突处理策略。合理的配置能确保前端统一访问、网络边界清晰可控，同时降低跨团队协作成本。生产环境需根据实际网络架构调整官方示例配置。阅读详情

今天遇到ORA-16038 ora-19809错误，查了资料解决了：

结果是发现DB_RECOVERY_FILE_DEST_SIZE太小了，恢复目录空间不够了所至

There are a couple of possible options.
1) Increase the parameter db_recovery_file_dest_size
2) Stop using the db_recovery_file_dest by unsetting the parameter. (This assumes you never really wanted to use this option)
3) Remove the Entries from the rman repository/Controlfile

The removal is desribed in the RMAN documentation but this is a quick and dirty way if you don't have an rman repository - but could endanger your ability to recover - so be careful.

a) delete unwanted archive log files from disk (rm, del commands)
b) connect to rman ( RMAN> connect target / )
c) RMAN> crosscheck archivelog all;
- marks the controlfile that the archives have been deleted
d) RMAN> delete expired archivelog all;
- deletes the log entries identified above.

收录于