Re: ORA-600 Internal shared memory fragmentation - HELP!

Placing your home grown functions into a package and then using sys.dbms_shared_pool.keep('owner.package_name','P') may be of some assistance. Increasing the shared pool is not a bad idea either, but you are right in that this may only buy time. Try bringing your database up in restricted mode, running the pin routine for all heavy hit and large packages, then compile these packages to actually fetch the complete package into the shared pool. The pin routine does not physically retrieve the entire package into memory in 7.015 or 7.1.3. I can not say for sure about 7.1.4 but you can check the sharable memory column on a select from v$db_object_cache to verify what I am saying is true. Oracle distributed a formula for calculating shared pool size in one of their bulletins on 04301 and 06501 errors.

Note I pulled the error codes from memory and could be off, but the two errors are for 'no storage available in shared pool' and 'module not found' which we have received when only part of a package would fit into the shared pool.

Mark D. Powell -- the only advise that counts is the advise you take

                           so take your own advise.