Resize Operation Completed For File# 201; FILE# Does Not Exist (Doc ID 2246369.1)

最新推荐文章于 2024-03-08 09:27:17 发布

翻译最新推荐文章于 2024-03-08 09:27:17 发布 · 1k 阅读

标签

本文解释了Oracle数据库警报日志中关于文件调整大小的记录，这些记录涉及动态生成的临时文件编号，通常与参数db_files关联。文章详细说明了如何通过调整db_files参数来确定具体的临时文件编号，并提到了一个增强请求，旨在改进日志消息，以便包含文件名。此外，还提供了一个参数，可以用来禁用这些仅用于信息目的的调整大小操作的日志记录。

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

GOAL

alert.log has many entries with:

Resize operation completed for file# 201, old size 111616K, new size 112640K

Problematic file# 201 is not existing.

SOLUTION

It's tempfiles and its number is generated dynamically based on parameter db_files - default value 200.
We have to subtract db_files value to get the file number in v$tempfile or db_files parameter value + tempfile# so in this case 201-200=1 is the tempfile#.

There is one Enhancement request raised for this issue to include filename as well in meaasage.

Bug 25661172 : DIAG ENH - INCLUDE FILENAME IN ALERT.LOG FOR DATAFILE/TEMPFILE RESIZE OPS

However these messages are for information only and you can disable this using below parameter:

Apply patch 18603375 first, then set the below parameter along with the fix.

SQL> alter system set "_disable_file_resize_logging"=TRUE ; (Its default value is FALSE)