Cause ~~~~~ The value for the init.ora parameter LARGE_POOL_SIZE is too low. This parameter specifies the size (in bytes) of the large pool allocation heap, which is (among others) used by the shared servers systems for session memory. When the value is too low, the shared server will crash. As a result of this crash, Export will be terminated too. Fix ~~~~ 1. Increase the value of the LARGE_POOL_SIZE. To check current (or default) value of the LARGE_POOL_SIZE: SQL> conn / as sysdba SQL> show parameter large NAME TYPE VALUE -------------------- ----------- -------- large_pool_size big integer 8388608 a. When SGA_MAX_SIZE has a high enough value, increase LARGE_POOL_SIZE dynamically. E.g.: SQL> conn / as sysdba SQL> ALTER SYSTEM SET large_pool_size=50m SCOPE=BOTH; SQL> show parameter large NAME TYPE VALUE -------------------- ----------- --------- large_pool_size big integer 58720256 b. When SGA_MAX_SIZE is too low in order to increase the LARGE_POOL_SIZE dynamically (ORA-2097 and ORA-4033 is reported), you have to modify the value in the spfile (or manually in the init.ora), and restart the database; e.g.: SQL> conn / as sysdba SQL> ALTER SYSTEM SET large_pool_size=50m SCOPE=SPFILE; SQL> shutdown immediate SQL> startup SQL> show parameter large NAME TYPE VALUE -------------------- ----------- --------- large_pool_size big integer 58720256 Restart export, e.g.: exp system/manager@t920 full=y file=exp_full.dmp log=exp_full.log or: 2. Use a dedicated connection. When MTS has been configured, all new connections will be made to the shared server by default. To force the usage of a dedicated server: a. make a new Oracle9i Net alias in the tnsnames.ora (e.g.: "t920nomts") and specify (SERVER = DEDICATED) in the CONNECT_DATA section. b. restart export while making a dedicated server connection, e.g.: exp system/manager@t920nomts full=y file=exp_full.dmp log=exp_full.log
Cause :
The value for the init.ora parameter LARGE_POOL_SIZE is too low. This parameter specifies the size (in bytes) of the large pool allocation heap, which is (among others) used by the shared servers systems for session memory. When the value is too low, the shared server will crash. As a result of this crash, Export will be terminated too.
Fix :
1. Increase the value of the LARGE_POOL_SIZE.
To check current (or default) value of the LARGE_POOL_SIZE:
SQL> conn / as sysdba
SQL> show parameter large NAME TYPE VALUE -------------------- ----------- -------- large_pool_size big integer 8388608
a. When SGA_MAX_SIZE has a high enough value, increase LARGE_POOL_SIZE dynamically.
E.g.:
SQL> conn / as sysdba
SQL> ALTER SYSTEM SET large_pool_size=50m SCOPE=BOTH;
SQL> show parameter large NAME TYPE VALUE -------------------- ----------- --------- large_pool_size big integer 58720256
b. When SGA_MAX_SIZE is too low in order to increase the LARGE_POOL_SIZE dynamically (ORA-2097 and ORA-4033 is reported), you have to modify the value in the spfile (or manually in the init.ora), and restart the database;
e.g.:
SQL> conn / as sysdba
SQL> ALTER SYSTEM SET large_pool_size=50m SCOPE=SPFILE;
SQL> shutdown immediate
SQL> startup
SQL> show parameter large NAME TYPE VALUE -------------------- ----------- --------- large_pool_size big integer 58720256
Restart export, e.g.:
exp system/manager@t920 full=y file=exp_full.dmp log=exp_full.log
2. Use a dedicated connection. When MTS has been configured, all new connections will be made to the shared server by default. To force the usage of a dedicated server:
a. make a new Oracle9i Net alias in the tnsnames.ora (e.g.: "t920nomts") and specify (SERVER = DEDICATED) in the CONNECT_DATA section.
b. restart export while making a dedicated server connection, e.g.:
exp system/manager@t920nomts full=y file=exp_full.dmp log=exp_full.log