АндрейФ Гость
|
Добавлено: Чт Июл 31 2003 11:35 Заголовок сообщения: надыбал кой чего |
|
|
В принципе я надыбал вот чего, только незнаю увеличивать или уменьшать LARGE_POOL_SIZE: Facts ~~~~~ 1. Oracle9i Enterprise Edition Release 9.2.0.1.0 on MS-Windows Platform. 2. Multi-Threaded Server option (MTS) is configured, e.g.: SQL> SELECT name,value FROM v$parameter WHERE name in ('dispatchers','max_dispatchers','circuits', 'shared_servers','max_shared_servers','shared_server_session s'); NAME VALUE -------------------------- --------------- dispatchers (protocol=TCP) max_dispatchers 5 circuits 170 shared_server_sessions 165 shared_servers 1 max_shared_servers 20 3. Invoke Export utility, and connect using Oracle9i Net to a shared server, e.g.: exp system/manager@t920 full=y file=exp_full.dmp log=exp_full.log Symptoms ~~~~~~~~ 1. Export terminates unsuccessfully with: ... (left out first part) . exporting system procedural objects and actions . exporting pre-schema procedural objects and actions EXP-00008: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel EXP-00008: ORACLE error 1041 encountered ORA-01041: internal error. hostdef extension doesn't exist EXP-00000: Export terminated unsuccessfully 2. In alert_.log in BACKGROUND_DUMP_DEST, you see that a shared server has crashed: found dead shared server 'S000', pid = (10, 1) 3. In trace file of the shared server (e.g.: _s000.trc) in USER_DUMP_DEST you can find the following line (example): 07/30/2002 09:27:14 UNWIND with no STOPEXIT active. Changes ~~~~~~~ 1. You recently upgraded to Oracle9i release 2 (9.2.0.x). 2. You recently configured the Multi-Threaded Server (MTS) Option in order to enable shared server connections to the database. 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 ... |
|