ORA-39083: Object type TABLE:"ESB_OWNER"."ESB_CONTROLS_JN" failed to create with error: SQL> $expdp full=y dumpfile=fulldb.dmp directory=d userid=system/a Now the export operation runs smoothly as shared pool finds enough memory to do the operation. SQL> alter system set sga_target=300M scope=spfile SQL> alter system set sga_max_size=300M scope=spfile As setting of SGA_TARGET is depend on SGA_MAX_SIZE and to change SGA_MAX_SIZE we need to bounce the database in order to effect. We see these two parameter settings are low. So simply increase of SGA_TARGET likely solves the problem. Since in 10g automatic memory management is enabled and this allows the dba to reserve a pool of shared memory that is used to allocate the shared pool, the buffer cache, the java pool and the large pool with the single parameter SGA_TARGET. If there is still not a single chunk large enough to satisfy the request the ORA-04031 error is returned. Oracle first flushes all objects that are not currently in use from the pool and the resulting free memory chunks are merged. The ORA-04031 error returns whenever oracle attempts to allocate a large piece of contiguous memory in the shared pool but fails to allocate. ORA-25254: time-out in LISTEN while waiting for a message ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool","SELECT job_id FROM v$datapum.","SQLA","tmp") UDE-04031: operation generated ORACLE error 4031
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |