AW: 4031 errors in 19.7
Date: Mon, 1 Mar 2021 13:21:36 +0000
Message-ID: <VI1PR05MB6976D1C153B700CE7B2C2B44F39A9_at_VI1PR05MB6976.eurprd05.prod.outlook.com>
Hallo Jeff,
I had similar experience . After upgrade from 12.2 single tenant to 19c multitenant the SQLArea was much smaller for same shared pool size. In AWR the difference between shared pool size in DBA_HIST_MEM_DYNAMIC_COMP - sum( Shared Pool components) from DBA_HIST_SGASTAT increased after upgrade for the DB with 400G sga_target from 6G to 35G. May be some internal memory structures related to multitenant ? For 19c single tenant this difference was almost same as under 12c
Best Regards
Petr
Von: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> im Auftrag von Beckstrom, Jeffrey <jbeckstrom_at_gcrta.org> Gesendet: Montag, 1. März 2021 14:01
An: oracle-l_at_freelists.org
Betreff: 4031 errors in 19.7
Since upgrading our Oracle EBS 12.1.3 IT Test system to 19.7 mutltenant from 11.2.0.4. We have been experiencing shared pool errors. After the last one, we increased sga_target to 1 G larger than we had in 11g. However, we just experienced another 4031 error. The IT database only has the EBS concurrent managers running and very other light activity. The error occurred on Saturday when only thing else running was stats. Does 19c multitenant require a much larger sga_target?
Jeffrey Beckstrom
Greater Cleveland Regional Transit Authority
1240 W. 6th Street
Cleveland, Ohio 44113
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 01 2021 - 14:21:36 CET