Oracle Database Resize operation completed for file #

Resize operation completed for file # occurs in the standby database in the Orale 12c pluuard environment.

Database version

[Oracle @ ray01 ~] $ Opatch lspatches
22291127; Database Patch Set Update: 12.1.0.20.0419 (22291127)
 
OPatch succeeded.
 
SQL> select * from v $ version;
 
BANNER CON_ID
------------------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0-64bit Production 0
PL/SQL Release 12.1.0.2.0-Production 0
CORE 12.1.0.2.0 Production 0
TNS for Linux: Version 12.1.0.2.0-Production 0
NLSRTL Version 12.1.0.2.0-Production 0
Alert Log prompt
Mon Jun 27 20:56:37 2016
Resize operation completed for file #18, old size 25600000 K, new size 30720000 K
Mon Jun 27 20:56:56 2016
Archived Log entry 210 added for thread 1 sequence 286 rlc 915405135 ID 0x2316988c dest 2:
Mon Jun 27 20:57:01 2016
Primary database is in maximum performance mode
RFS [211]: Assigned to RFS process (PID: 22867)
RFS [211]: Selected log 11 for thread 1 sequence 287 dbid 588725388 branch 915405135
Mon Jun 27 20:57:14 2016
Resize operation completed for file #17, old size 25600000 K, new size 30720000 K
Mon Jun 27 07:57:15 2016
Archived Log entry 211 added for thread 1 sequence 287 ID 0x2316988c dest 1:
Mon Jun 27 20:57:15 2016
Resize operation completed for file #3, old size 972800 K, new size 983040 K
Mon Jun 27 20:57:15 2016
Primary database is in maximum performance mode
RFS [212]: Assigned to RFS process (PID: 22873)
RFS [212]: Selected log 11 for thread 1 sequence 288 dbid 588725388 branch 915405135
Mon Jun 27 20:57:15 2016
Resize operation completed for file #3, old size 983040 K, new size 1024000 K
Resize operation completed for file #3, old size 1024000 K, new size 1034240 K
Mon Jun 27 20:57:54 2016
Resize operation completed for file #15, old size 25600000 K, new size 30720000 K
Mon Jun 27 20:58:15 2016
Resize operation completed for file #18, old size 30720000 K, new size 33554416 K
Mon Jun 27 20:58:34 2016
Resize operation completed for file #17, old size 30720000 K, new size 33554416 K
Mon Jun 27 20:58:54 2016
Resize operation completed for file #15, old size 30720000 K, new size 33554416 K

A large number of Resize operation completed for file # operation records are annoying. Based on years of experience in using oracle, this phenomenon is likely to be blocked by implicit parameters or events, which can be guessed by implicit parameters, event needs to query official information.

Query the hidden parameters of Khan resize

SQL> col name for a52
SQL> col value for a24
SQL> col description for a50
Set linesize 150
Select a. ksppinm name, B. ksppstvl value, a. ksppdesc description
From x $ ksppi a, x $ ksppcv B
Where a. inst_id = USERENV ('instance ')
And B. inst_id = USERENV ('instance ')
And a. indx = B. indx
SQL> 2 3 4 5 6 and upper (a. ksppinm) LIKE upper ('% & param % ')
7 order by name
/
8 Enter value for param: resize
Old 6: and upper (a. ksppinm) LIKE upper ('% & param % ')
New 6: and upper (a. ksppinm) LIKE upper ('% resize % ')
 
NAME VALUE DESCRIPTION
------------------------------------------------------------------------------------------------------------------------------
_ Asm_skip_resize_check FALSE skip the checking of the clients for s/w compatibi
Lity for resize
 
_ Bct_public_dba_buffer_dynresize 2 allow dynamic resizing of public dba buffers, zero
To disable
 
_ Disable_file_resize_logging FALSE disable file resize logging to alert log

Here we can find that the default value of the _ disable_file_resize_logging parameter is false, indicating that the file resize prompt is displayed. Setting it to true should solve this problem.

From: http://www.xifenfei.com/2016/06/resize-operation-completed-for-file.html