1.utl_file_dir: indicate the directory which the pl/sql packages and procedure can access and use
2.V$SHARED_POOL_RESERVED :lists statistics that help you tune the reserved pool and space within the shared pool.
SHARED_POOL_RESERVED_SIZE: specifies (in bytes) the shared pool space that is reserved for large contiguous requests for shared pool memory.
3.v$circuit:contains information about virtual circuits, which are user connections to the database through dispatchers and servers
4.V$SESSTAT:This view lists user session statistics.The V$SESSTAT
view displays statistics on a per-session basis and is valid only for the session currently connected.When a session disconnects, all statistics for the session are updated in V$SYSSTAT
. The values for the statistics are cleared until the next session uses them.
V$SYSSTAT:This view lists system statistics.
V$SESSION_EVENT:This view lists information on waits for an event by a session.
5.your servers and dispatchers count as background processes for the instance.be careful that your setting of PROCESSES allows for all possible servers and dispatchers, or new users may not be able to log in.setting MTS_MAX_SERVERS and MTS_MAX_DISPATCHERS can act as useful ceiling.
6.The large pool is used to provide large memory allocations for session memory for the: • I/O server processes • Oracle backup and restore operations The memory for Oracle server backup and restore operations and for I/O server processes is allocated in buffers of a few hundred kilobytes. The large pool is better able to satisfy such requests than the shared pool. • Multithreaded server: By allocating session memory from the large pool for the multithreaded server, the Oracle server can use the shared pool primarily for caching shared SQL and avoid the performance overhead caused by shrinking the shared SQL cache. • Parallel execution: When the PARALLEL_AUTOMATIC_TUNING parameter is set to TRUE, the Oracle Server allocates parallel execution buffers from the large pool. When this parameter is set to FALSE, Oracle allocates parallel execution buffers from the shared pool. The Oracle server automatically computes the LARGE_POOL_SIZE parameter value if the PARALLEL_AUTOMATIC_TUNING parameter value is set to TRUE. To manually set a value for LARGE_POOL_SIZE, query the V$SGASTAT view and increase or decrease the value for LARGE_POOL_SIZE depending on your needs. |
7.
A) you need a larger rollback segment for the big batch transaction, larger then
you need for the OLTP transactions in any case, just to handle the volume of
updates it performs.
B) you need larger rollback segments for the OLTP transactions to use as well
during the batch job to support the consistent read mechanism employed by Oracle -- not only does the batch job need to have a big rollback segment but you want to try and make it so that your other rollback segments used by the OLTP job do not wrap while the batch job is processing else it (the batch job) will get the ORA-1555 when it tries to reconstruct some data from the RBS's used by the OLTP jobs.