标题: resize Operation Completed For File# 201; FILE# Does Not Exist [打印本页] 作者: 郑全 时间: 2019-3-9 07:03 标题: resize Operation Completed For File# 201; FILE# Does Not Exist resize Operation Completed For File# 201; FILE# Does Not Exist (文档 ID 2246369.1)
In this Document
Goal
Solution
References
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
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)
References
NOTE:1982901.1 - Resize Operation Completed For File#