
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Purged partition 2 for table I_TRANSACTION_DETAIL
Purged partition 2 for table PROBLEM
Purged inbound i_transaction records
Purged inbound i_transmission records
PL/SQL procedure successfully completed.
SQL> @purge_partitioned_tables
This routine will truncate the oldest partition for each table that has
been identified to be purged
at the inputted frequency. The valid values are 'Q' for quarterly, 'MM'
for monthly,
or 'WW' for weekly, or 'D' for daily.
By purging the old data, it can prepare room for the next week, month,
or quarter.
Please enter a frequency (Q, MM, WW, D): D
Purging partition 3...
Purged partition 3 for table EXPLANATION
Purged partition I_LOG_DET_MSG_PART3 for table I_LOG_DETAIL
Purged partition I_LOG_MSG_PART3 for table I_LOG
Purged partition I_LOG_DET_MSG_PART3 for table I_LOG_DETAIL
Purged partition I_MSG_PART3 for table I_MESSAGE
Purged partition I_MSG_ACK_PART3 for table I_MESSAGE_ACK
Purged partition I_TRANSACTION_MSG_PART3 for table I_TRANSACTION
Purged partition I_TRNSCTN_ACK_MSG_PART3 for table
I_TRANSACTION_ACK
Purged partition I_TRNSCTN_DET_MSG_PART3 for table
I_TRANSACTION_DETAIL
Purged partition I_TRNSCTN_RFNM_MSG_PART3 for table
I_TRANSACTION_REFNUM
Purged partition I_TRANSMISSION_MSG_PART3 for table I_TRANSMISSION
Purged partition I_TRNSMSN_ACK_MSG_PART3 for table
I_TRANSMISSION_ACK
Purged partition I_TRNSMSN_RFNM_MSG_PART3 for table
I_TRANSMISSION_REFNUM
Purged partition I_TRNSMSN_REP_MSG_PART3 for table
I_TRANSMISSION_REPORT
PL/SQL procedure successfully completed.
Pinning Large Object in Memory
This section is for a production database and an experienced DBA.
Oracle Database requires space in the System Global Area (SGA) for stored packages and functions. If
SGA space is fragmented, there may not be enough space to load a package or function. Oracle
Database recommends pre-allocating space in the SGA shared pool for frequently used packages,
procedures and functions. Pinning objects in the shared pool can improve database performance, if it
is done correctly. For large packages, when pinned they do not need to be loaded and parsed from the
database again and again. Pinning large package also helps to avoid ORA-04031 error (unable to
allocate xxx bytes of shared memory).
Kommentare zu diesen Handbüchern