12.2 DB RMAN Backup Generate Large Trace File even though PATCH 27674384 has been installed
(Doc ID 2428828.1)
Last updated on SEPTEMBER 14, 2018
Applies to:Oracle Database Cloud Schema 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
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Huge trace files generated by Rman even though tracing has not been enabled.
Issue not reproduced in Base release 12.2
After Installing Patch description: "Database Apr 2018 Release Update : 126.96.36.199.180417 (27674384)" issue is reported during rman backup.
One off fix 28174827 raised earlier for similar issue has also been applied .Trace file still gets generated .
Trace file would have
** SESSION ID:(29.40793) 2018-07-23T18:19:04.552613-07:00 *** CLIENT ID:() 2018-07-23T18:19:04.552621-07:00 *** SERVICE NAME:(SYS$USERS) 2018-07-23T18:19:04.552628-07:00 *** MODULE NAME:(rman@test1(TNS V1-V3)) 2018-07-23T18:19:04.552636-07:00 *** ACTION NAME:() 2018-07-23T18:19:04.552643-07:00 *** CLIENT DRIVER:() 2018-07-23T18:19:04.552650-07:00 2018-07-23 18:19:04.552*:KRB:krbi.c@8857:krbitrc(): Got krbitrc 2018-07-23 18:19:04.552*:KRB:krbi.c@8887:krbiwtrc(): (bkrsmain - Action is NULL) 2018-07-23 18:19:04.552*:KRB:krbi.c@8857:krbitrc(): Got krbitrc 2018-07-23 18:19:04.552*:KRB:krbi.c@9960:krbiovac(): Got krbiovac *** ACTION NAME:(0000001 STARTED1) 2018-07-23T18:19:04.552833-07:00
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!