Shared pool fragmentation

Question

Find below a modified version of a script retrieved from Metalink 146599.1 to check for shared pool fragmentation
I am not sure if it is possible, but is there any way to incorporate into this script a query that will show the effectiveness of using an ALTER SYSTEM FLUSH SHARED_POOL command .
select bucket, freespace,
ROUND(ratio_to_report(freespace) over () * 100, 5) AS "Percentage"
from
(select '0 (<140)' BUCKET, sum(KSMCHSIZ) freespace
from x$ksmsp
where KSMCHSIZ<140
and KSMCHCLS='free'
UNION ALL
select '1 (140-267)' BUCKET, sum(KSMCHSIZ) freespace
from x$ksmsp
where KSMCHSIZ between 140 and 267
and KSMCHCLS='free'
UNION ALL
select '2 (268-523)' BUCKET, sum(KSMCHSIZ) freespace
from x$ksmsp
where KSMCHSIZ between 268 and 523
and KSMCHCLS='free'
UNION ALL
select '3-5 (524-4107)' BUCKET, sum(KSMCHSIZ) freespace
from x$ksmsp
where KSMCHSIZ between 524 and 4107
and KSMCHCLS='free'
UNION ALL
select '6+ (4108+)' BUCKET, sum(KSMCHSIZ) freespace
from x$ksmsp
where KSMCHSIZ >= 4108
and KSMCHCLS='free');

Answer 1

Running this SQL, flushing the shared pool, and the re-running should show what the difference before and after is - or does this not suffice?
Flushing the shared pool is also not really addressing the root cause - which most often is non-sharable SQL.
Thus I'm not exactly sure what you're trying to achieve here. The SQL identifies the symptoms - flushing the shared pool treats those symptoms. For a while.
Surely you should rather be looking at the shared pool itself to determine what the problem is and try and fix that instead? A db logon trigger for a poorly written app can for example force cursor sharing for all sessions created by that app.