Answer
No — there's no formal IFS-provided SGA/PGA sizing guide or fixed value meant to apply universally; database memory sizing is fundamentally a DBA task, informed by Oracle's own memory advisories (such as its Automatic Memory/SGA/PGA advisor tooling) relative to the actual RAM and workload on that specific server, not a fixed number reused verbatim from a build spec across differently-sized environments. If a build spec's SGA/PGA value was set explicitly low (for example, well below what a server's available RAM would support) and that's now causing 'unable to allocate shared memory' errors under load, that's a sign the value needs to be revisited against the actual server's resources using Oracle's own sizing tools, not that IFS should be supplying a single fixed number for every deployment.