Edit D:\app\Administrator\product\11.2.0\dbhome_1\RDBMS\mesg\smgus.msb
" ? r ? D r & - 1 6 : ? D I M R V \ ` e i k n r z ? ? ? ? ? ? ? ? ? ? ? ? ? ? -369?DGKPTX\`dimqvxz{}???????????????????afl{???????????? "&+/289:<=@ADGLNOSV]bilpuz|~??????? ??????? ? ?BI!???????????????? "%(+.PSUY]`bdgiknrr & ? ? ? j ?Consider adding more CPUs to the host or adding instances serving the database on other hosts.CPU was not a bottleneck for the instance.Run SQL Tuning Advisor on the SQL statement with SQL_ID "%s".Host CPU was a bottleneck and the instance was consuming %s\% of the host CPU. All wait times will be inflated by wait for CPU.A hot block of type "%s" with concurrent read and write activity was found. The block belongs to segment "%s.%s" and is block %s in file %s. ? ? p ?Read and write contention on database blocks was consuming significant database time. However, no single object was the predominant cause for this contention.Estimated reduction in database time in microseconds.Investigate application logic to find the cause of high concurrent read and write activity to the data present in this block.Waits on "buffer busy" events were not consuming significant database time. ? ? At least %s SQL statements with PLAN_HASH_VALUE %s were found to be using literals. Look in V$SQL for examples of such SQL statements.Read and write contention on database blocks was consuming significant database time. N ?Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespace for the tablespace "%s" containing the %s "%s.%s" with object ID %s. Alternatively, you can move this object to a different tablespace that is locally managed with automatic segment space management.Consider hash partitioning the %s "%s.%s" with object ID %s in a manner that will evenly distribute concurrent DML across multiple partitions. v ? - ?Consider rebuilding the %s "%s.%s" with object ID %s using a higher value for PCTFREE.The UPDATE statement with SQL_ID "%s" was significantly affected by "buffer busy" waits.The INSERT statement with SQL_ID "%s" was significantly affected by "global cache buffer busy".The instance spent significant time on CPU. However, there were no predominant SQL statements responsible for the CPU load. ? X ? ?Contention on database block of type "%s" was consuming significant database time. The block belongs to segment "%s.%s" and is identified by block number %s in file number %s.Consider partitioning the %s "%s.%s" with object ID %s in a manner that will evenly distribute concurrent DML across multiple partitions.Contention on buffer cache latches was not consuming significant database time.Consider using array interface for the INSERT statement with SQL_ID "%s". & ? ? . r ?The UPDATE statement with SQL_ID "%s" was significantly affected by "global cache buffer busy".Waits in DBMS_PIPE.PUT calls were not consuming significant database time.The DELETE statement with SQL_ID "%s" was significantly affected by "global cache buffer busy".Consider adding more pipe read processes or speeding-up the readers.Consider increasing the size of pipes created using the DBMS_PIPE package. , ? ? ' h ? ?Trace the cause of object contention due to SELECT statements in the application using the information provided.Waits in DBMS_PIPE.PUT calls were consuming significant database time.Wait class "Concurrency" was not consuming significant database time.Wait class "Concurrency" was consuming significant database time.Wait event "%s" in wait class "%s" was consuming significant database time.Wait class "Administrative" was not consuming significant database time. ! , " q # ? $ ? % 9& z ?Wait class "Application" was not consuming significant database time.Wait class "Cluster" was not consuming significant database time.Wait class "Commit" was not consuming significant database time.Wait class "Configuration" was not consuming significant database time.Wait class "Network" was not consuming significant database time.Wait class "Scheduler" was not consuming significant database time. ' 2 ( s ) ? * ? + 0, s- ? ?Wait class "Application" was consuming significant database time.Wait class "Administrative" was consuming significant database time.Wait class "Cluster" was consuming significant database time.Wait class "Commit" was consuming significant database time.Wait class "Configuration" was consuming significant database time.Wait class "Network" was consuming significant database time.Wait class "Scheduler" was consuming significant database time. . / ? 0 #1 z ?Significant row contention was detected in the %s "%s.%s" with object ID %s. Trace the cause of row contention in the application logic using the given blocked SQL.There was significant read and write contention on %s "%s.%s" with object ID %s in the cluster.The SQL statement with SQL_ID "%s" was found waiting for a lock when using "DBMS_LOCK".The SQL statement with SQL_ID "%s" was blocked on row locks. 2 & 3 k 4 ? 5 6 T ?The %s "%s.%s" with object ID "%s" was locked for a significant time.Waits for locks obtained by using the "DBMS_LOCK" package were consuming significant database time.Sequence cache misses were consuming significant database time.Contention on table lock waits was consuming significant database time.Consider adding more archiver processes by setting the value of parameter "log_archive_max_processes". 7 8 ? 9 ? : 9 ?Transactions wait for ITL enqueue when the limit has been reached on the number of transactions concurrently modifying the same database block.Verify whether incremental shipping was used for standby databases.Tablespace %s was found in backup mode. Verify that it was appropriate.Investigate application logic for possible reduction in the number of COMMIT operations by increasing the size of transactions. ; & < ? = ? > 5? ? ?Consider increasing the number of database writers (DBWR) by setting the parameter "db_writer_processes".Increase the size of the log files to %s M to hold at least %s minutes of redo information.DML to tablespaces in hot backup mode causes generation of additional redo.Read and write contention on database blocks was consuming significant database time in the cluster.Waits for free buffers were not consuming significant database time. @ & A u B ? C ? D n ?High watermark (HW) enqueue waits were not consuming significant database time.ITL enqueue waits were not consuming significant database time.Waits for archiver processes were not consuming significant database time.Log file switch operations were not consuming significant database time while waiting for checkpoint completion.Log buffer space waits were not consuming significant database time. E & F ? G ? H 0I n ?Waits on event "log file sync" while performing COMMIT and ROLLBACK operations were not consuming significant database time.Row lock waits were not consuming significant database time.Space Transaction (ST) enqueue waits were not consuming significant database time.Table lock waits were not consuming significant database time.Locks obtained by using the "DBMS_LOCK" package were not consuming significant database time. J K ? L M ? ?The SQL statement with SQL_ID "%s" was found waiting for the high watermark (HW) of %s "%s.%s" with object ID %s.The SQL statement with SQL_ID "%s" was found waiting for the Interested Transaction List (ITL) enqueue on the %s "%s.%s" with object ID %s.Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespace for the tablespace "%s".SQL statements were found waiting for row lock waits. N & O ? P Q ^R ? ?Waits on event "log file sync" while performing COMMIT and ROLLBACK operations were consuming significant database time.The application was performing %s transactions per minute with an average redo size of %s bytes per transaction.Database writers (DBWR) were unable to keep up with the demand for free buffers.Sequence cache misses were not consuming significant database time.Archiver processes were unable to keep up with redo generation. S T ? U V j ?DML to tablespaces in hot backup mode causes generation of additional redo, thereby increasing the work of archiver processes.Log file switch operations were consuming significant database time while waiting for checkpoint completion.Increase the size of the redo log buffer by setting the value of parameter "log_buffer" to %s M.Contention on the high watermark (HW) enqueue was consuming significant database time. W , X ? Y ? Z [ <\ | ?Contention on Space Transaction (ST) enqueue waits was consuming significant database time.Waits for ITL enqueue were consuming significant database time.The INSERT statement with SQL_ID "%s" was significantly affected by "buffer busy" waits.Host CPU consumption was %s\%.Waits for free buffers were consuming significant database time.The DELETE statement with SQL_ID "%s" was significantly affected by "buffer busy" waits. ] ^ ? _ ` ] ?Investigate application or look at top SQL to find hot sequences. Use a larger cache size for those sequences. Try avoiding the use of the ORDER setting if running RAC.Contention on buffer cache latches was consuming significant database time.The database object with object ID "%s" was locked for a significant time.Session connect and disconnect calls were consuming significant database time. a & b ? c d oe ? ?Use bigger fetch arrays while fetching results from the SELECT statement with SQL_ID "%s".ORACLE strongly recommends not storing any application or temporary data in the SYSTEM tablespace. Consider moving such data to a different tablespace.The SELECT statement with SQL_ID "%s" was significantly affected by "buffer busy" waits.The SELECT statement with SQL_ID "%s" was significantly affected by "global cache buffer busy".Database time in microseconds. f g r h ? i E ?Inter-instance messaging was consuming significant database time on this instance.Streams enqueue operations were blocked on flow control waits due to slow subscribers and consumed significant database time.Inter-instance messaging was not consuming significant database time on this instance.Streams enqueue operations were not blocked on flow control waits due to slow subscribers. j k t Investigate application to reduce inter-instance messaging for segment %s.%s with SEGMENT_ID %s.Investigate cause of high network interconnect latency between database instances. Oracle's recommended solution is to use a high speed dedicated network. l m En ? ?Increase throughput of the Global Cache Service (LMSn) processes. Increase the number of Global Cache Service processes by increasing the value of the parameter "gcs_server_processes". Alternatively, if the host is CPU bound consider increasing the OS priority of the Global Cache Service processes.Verify that the set of services used by the application to connect to the database are optimally distributed if response time is critical.Investigate slow subscribers on %s "%s.%s". o p o q ? r I ?SQL statements responsible for significant inter-instance messaging were found.Higher than expected latency of the cluster interconnect was responsible for significant database time on this instance.Global Cache Service Processes (LMSn) in other instances were not processing requests fast enough.Contention on data by other RAC instances was consuming significant database time on this instance. t u ? z W ?A hot block of type "%s" with concurrent read and write activity was found in the cluster. The block belongs to segment "%s.%s" and is block %s in file %s.Contention on database block of type "%s" was consuming significant database time in the cluster. The block belongs to segment "%s.%s" and is block %s in file %s.A hot block of type "%s" with concurrent read and write activity was found in the cluster. The block is identified by block number %s in file number %s. { ? ? ? ? ? N ?A hot data block with concurrent read and write activity was found in the cluster. The block belongs to segment "%s.%s" and is block %s in file %s.Wait class "User I/O" was consuming significant database time.Investigate the possibility of improving the performance of I/O to the online redo log files.The average size of writes to the online redo log files was %s K and the average time per write was %s milliseconds. ? ? VThe PGA was inadequately sized, causing additional I/O to temporary tablespaces to consume significant database time. Further analysis cannot be done because the value of parameter "pga_aggregate_target" was changed during the analysis period.Individual SQL statements responsible for significant user I/O wait were found. ? ? ? ? !? i ?The performance of file %s was significantly worse than other files. If striping all files using the SAME methodology is not possible, consider striping this file over multiple disks.The throughput of the I/O subsystem was significantly lower than expected.The buffer cache was undersized causing significant additional read I/O.Buffer caches for blocks of non-default size were undersized, causing significant additional read I/O. ? ? ? ? K? ? ?The PGA was inadequately sized, causing additional I/O to temporary tablespaces to consume significant database time.Buffer cache writes due to setting of the obsolete parameters "fast_start_io_target", "log_checkpoint_interval" and "log_checkpoint_timeout" were consuming significant database time.Buffer cache writes due to low MTTR setting were consuming significant database time.Buffer cache writes due to small log files were consuming significant database time. ? ? ? ? +? ? ?Buffer cache writes due to concurrent DML and parallel queries on the same objects had a significant impact on the throughput of the I/O subsystem.Buffer cache writes due to DROP and TRUNCATE operations had a significant impact on the throughput of the I/O subsystem.Buffer cache writes due to ALTER TABLESPACE operations had a significant impact on the throughput of the I/O subsystem.Wait class "User I/O" was not consuming significant database time. ? ? ? ? U? ? ?The average number of transactions waiting for a single log file write was %s which exceeds the number of host CPUs %s. Therefore, some transactions waited for a free CPU before completing the COMMIT operation.The SQL statement with SQL_ID "%s" spent significant time on "buffer busy" waits for the hot block.No single SQL or database statement was responsible for significant I/O wait.The throughput of the I/O subsystem was not significantly lower than expected. ? & ? J ? ? ? ? T ?The buffer cache was not undersized.Waits for I/O to temporary tablespaces were not consuming significant database time.Buffer cache writes due to log file size and parameter settings were not consuming significant database I/O.Undo I/O had no significant impact on the throughput of the I/O subsystem.Buffer cache writes due to concurrent DML and parallel queries on the same objects had no significant impact on the throughput of the I/O subsystem. ? ? ? ? ? { ?Buffer cache writes due to DROP and TRUNCATE operations had no significant impact on the throughput of the I/O subsystem.Buffer cache writes due to ALTER TABLESPACE operations had no significant impact on the throughput of the I/O subsystem.Reducing the size of redo generated by the application may reduce the wait time on "log file sync" events.The SQL statement with SQL_ID "%s" consumed significant database time in "global cache buffer busy" wait for the hot block. ? ? V ? 0? ? ?Run "Segment Advisor" on %s "%s.%s" with object ID %s.Consider increasing the throughput of the I/O subsystem. Oracle's recommended solution is to stripe all data files using the SAME methodology. You might also need to increase the number of disks for better performance.Increase the buffer cache size by setting the value of parameter "db_cache_size" to %s M.Increase the size of the PGA by setting the value of parameter "pga_aggregate_target" to %s M. ? ? ? ? ? ?Oracle's recommended solution is to enable the PGA auto memory management feature. This is done by not setting the value of parameter "pga_aggregate_target" to 0.Oracle's recommended solution is to control MTTR setting using the "fast_start_mttr_target" parameter instead of the "fast_start_io_target", "log_checkpoint_interval" and "log_checkpoint_timeout" parameters.Consider increasing the MTTR setting by increasing the value of parameter "fast_start_mttr_target". ? & ? ? ? ? O? ? ?Oracle's recommended solution is to use Auto Undo Management for reducing undo contention.The flushing of snapshots %s and %s took %s seconds which is %s\% of the analysis period time. This may reduce the reliability of the ADDM analysis.There was no significant database activity to run the ADDM.Trace the cause of contention on %s "%s.%s" with object ID %s in the application.Investigate application logic involving I/O on database object with ID %s. ? ? i ? ? ? G ?Contention on index block splits was consuming significant database time.Contention on index block splits was not consuming significant database time.Contention on index block splits was consuming significant database time. However, no single index was the predominant cause for this contention.The SQL statement with SQL_ID "%s" spent significant time waiting for User I/O on the hot object. ? ? ? ? ? ? ?Statistics for %s\% of the analysis time period attributing to approximately %s\% of the workload were missing. This may reduce the reliability of this ADDM analysis.Cluster multi-block requests were consuming significant database time.Run SQL Tuning Advisor on the SQL statement with SQL_ID "%s". Look for an alternative plan that does not use object scans.Cluster communications that were retried due to lost blocks did not consume significant database time. ? ? y ? ? ?Cluster communications that were retried due to lost blocks consumed significant database time.Check the configuration of the cluster interconnect. Check OS setup like adapter setting, firmware and driver release. Check that the OS's socket receive buffers are large enough to store an entire multiblock read. The value of parameter "db_file_multiblock_read_count" may be decreased as a workaround.The instance is connected to the network using device "%s" with IP address "%s". ? ? m ? B ?The instance was consuming %s kilo bits per second of interconnect bandwidth.The network latency of the cluster interconnect was within acceptable limits of %s milliseconds.Global Cache Service Processes (LMSn) in other instances were performing within acceptable limits of %s milliseconds.Read and write contention on database blocks was not consuming significant database time in the cluster. ? ? ?Investigate the SQL statement with SQL_ID "%s" for possible performance improvements. Look for an alternative plan that does not use object scans.The database's maintenance windows were active during %s%% of the analysis period.Waiting for event "%s" in wait class "%s" accounted for %s%% of the database time spent in processing the SQL statement with SQL_ID "%s".Service "%s" and Module "%s" was responsible for %s%% of this recommendation's benefit. ? ? D ?Session with ID "%s", User ID "%s", Program "%s" and Module "%s" was responsible for %s%% of this recommendation's benefit.Check application logic for latch contention.Sessions with Service "%s" and Module "%s" were the blocking sessions responsible for %s%% of this recommendation's benefit.Session with ID "%s", User ID "%s", Program "%s" and Module "%s" was the blocking session responsible for %s%% of this recommendation's benefit. x , )- ? ?Investigate the cause for latch contention using the given blocking sessions or modules.Consider increasing the number of database writers (DBWR) by setting the parameter "db_writer_processes". Also consider if asynchronous I/O is appropriate for your architecture.Investigate the cause for high "%s" waits. Refer to Oracle's "Database Reference" for the description of this wait event.Hard parsing of SQL statements was consuming significant database time. . , / s 0 ? 1 ? 2 3 M ?Soft parsing of SQL statements was consuming significant database time.SQL statements consuming significant database time were found.PL/SQL execution consumed significant database time.PL/SQL compilation consumed significant database time.JAVA execution consumed significant database time.Investigate the cause for high "%s" waits. Refer to Oracle's "Database Reference" for the description of this wait event. Use given SQL for further investigation. 4 5 l 6 ? ? Session connect and disconnect calls were not consuming significant database time.The SQL statement with SQL_ID "%s" was found waiting for "%s" wait event.Parsing of SQL statements was not consuming significant database time. 7 8 /9 z ?Parse errors due to inadequately sized shared pool were consuming significant database time. Note that parse errors can also happen if you have set the parameter "cursor_space_for_time" to "TRUE" and your shared pool is not large enough to hold all open cursors simultaneously.Hard parsing of SQL statements was not consuming significant database time.Soft parsing of SQL statements was not consuming significant database time. : , ; r < ? = ? > #? ? ?No single SQL statement consuming significant database time was found.PL/SQL execution did not consume significant database time.PL/SQL compilation did not consume significant database time.JAVA execution did not consume significant database time.Time spent on the CPU by the instance was responsible for a substantial part of database time.Waits for redo log buffer space were consuming significant database time. @ & A q B ? C ? D 7 ?Look for top reason for cursor environment mismatch in V$SQL_SHARED_CURSOR.Parse errors due to inadequately sized shared pool were not consuming significant database time.Investigate appropriateness of DDL operations.Investigate application logic to eliminate parse errors.Investigate application logic for possible use of bind variables instead of literals. E F ? G 4 ?Investigate application logic to keep open the frequently used cursors. Note that cursors are closed by both cursor close calls and session disconnects.CPU runqueue statistics are not available from the host's OS. This disables ADDM's ability to estimate the impact of this finding.SQL statements with the same text were not shared because of cursor environment mismatch. This resulted in additional hard parses which were consuming significant database time. H I ? J K y ?Common causes of environment mismatch are session NLS settings, SQL trace settings and optimizer parameters.Cursors were getting invalidated due to DDL operations. This resulted in additional hard parses which were consuming significant database time.Hard parses due to an inadequately sized shared pool were consuming significant database time.Hard parsing SQL statements that encountered parse errors was consuming significant database time. L & M ? N O OP ? ?SQL statements were not shared due to the usage of literals. This resulted in additional hard parses which were consuming significant database time.Hard parses due to cursor environment mismatch were not consuming significant database time.Investigate the cause for high "%s" waits in Module "%s".Investigate the cause for high "%s" waits in Service "%s".Hard parsing due to cursors getting aged out of shared pool was not consuming significant database time. Q R ? S ? T ? ?Hard parsing SQL statements that encountered parse errors was not consuming significant database time.Hard parses due to literal usage and cursor invalidation were not consuming significant database time.Investigate application logic for possible reduction of connect and disconnect calls. For example, you might use a connection pool scheme in the middle tier.Contention for latches related to the shared pool was not consuming significant database time. U V z W NX ? ?Contention for latches related to the shared pool was consuming significant database time.The temporary tablespace "%s" containing the %s "%s.%s" with object ID %s was not locally managed. Oracle's recommended solution is to create temporary tablespaces using the CREATE TEMPORARY TABLESPACE statement.Wait class "Other" was consuming significant database time.Wait class "Other" was not consuming significant database time. Y Z ? [ ? \ / ?The latch "%s" with latch ID %s was one of the top latches contributing to high "latch free" waits.Database latches in the "Other" wait class were not consuming significant database time.Database latches in the "Other" wait class were consuming significant database time.Investigate the SQL statement with SQL_ID "%s" for possible performance improvements. ] ^ ? _ ? ` H ?Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespace for all of your tablespaces except the SYSTEM tablespace.Waits for "%s" amounted to %s\% of database time.Waits for lock with identifier %s were consuming significant database time.Investigate application logic that uses the "DBMS_LOCK" package. Consider reducing the time these locks are held by the application or consider using a finer granularity of locks. a b p c ? d } ?Investigate application logic involving DDL and DML on provided blocked objects.A hot block of type "%s" with concurrent read and write activity was found. The block is identified by block number %s in file number %s.A hot data block with concurrent read and write activity was found. The block belongs to segment "%s.%s" and is block %s in file %s.A temporary solution may be achieved by increasing the number of free lists in segment "%s.%s". e & f ? g ? h 3i t ?A temporary solution may be achieved by increasing the number of free list groups in segment "%s.%s".There was significant read and write contention on %s "%s.%s" with object ID %s.Consider increasing INITRANS for the %s "%s.%s" with object ID %s without rebuilding it.Consider increasing PCTFREE for the %s "%s.%s" with object ID %s.Consider rebuilding the %s "%s.%s" with object id %s using a higher value for INITRANS. j k R l ? m ?Investigate the I/O subsystem's write performance.Investigate application logic for possible use of direct path inserts as an alternative for multiple INSERT operations.This problem can be caused by use of hot backup mode on tablespaces.Consider increasing the maximum number of open cursors a session can have by increasing the value of parameter "open_cursors". n o ? p q M ?Consider increasing the session cursor cache size by increasing the value of parameter "session_cached_cursors".Investigate the appropriateness of PL/SQL compilation. PL/SQL compilation can be caused by DDL on dependent objects.Investigate the cause for Module "%s" spending significant database time.Investigate the cause for Service "%s" spending significant database time. r & s ? t ? u Ev ? ?Contention for space in temporary tablespace by multiple instances was consuming significant database time.Consider increasing the size of the temporary tablespace "%s".Consider increasing the size of the temporary tablespaces that are experiencing significant inter-instance contention.Investigate the cause for high "%s" waits with P1 ("%s") value "%s".Investigate the cause for high "%s" waits with P1 ("%s") value "%s" and P2 ("%s") value "%s". w x { ? Investigate the cause for high "%s" waits with P1,P2,P3 ("%s") values "%s", "%s" and "%s" respectively.Excessive number of bind calls to cursors whose bind variables were already bound was consuming significant database time. y z S ?Investigate application logic to reduce the number of bind calls issued. Consider replacing repeated bind by value calls by a single bind by reference or by array binds. Note that even while binding by reference changes to the bind metadata like the max-length or data-type of the bind will cause additional bind calls.Significant virtual memory paging was detected on the host operating system. { TThe total memory consumed by the instance was more than the physical memory available on the host. Consider adding more physical memory to the host or reducing the memory consumed by the instance by altering appropriate INIT.ORA parameters like "sga_target", or "shared_pool_size", "db_cache_size", and "pga_aggregate_target". | } ; ?Host operating system was experiencing significant paging but no particular root cause could be detected. Investigate processes that do not belong to this instance running on the host that are consuming significant amount of virtual memory. Also consider adding more physical memory to the host.Consider enabling Automatic Shared Memory Management by setting the parameter "sga_target" to control the amount of SGA consumed by this instance. ~ ? ?Consider enabling Automatic PGA Memory Management by setting the parameter "pga_aggregate_target" to control the amount of PGA consumed by this instance.Total PGA memory used was above the specified "pga_aggregate_target" value for %s%% of the time. Consider increasing your current "pga_aggregate_target". Note that the sum of "pga_aggregate_target" and SGA size should be less than the physical memory available on the host. ? ? l ? ? ? V ?Investigate the cause for the "%s" processes consuming %s%% of the host CPU.The instance was consuming %s M of SGA memory and %s M of PGA memory, and the physical memory available on the host was %s M.Also consider using Oracle Database Resource Manager to prioritize the workload from various consumer groups.SQL statement with SQL_ID "%s" was executed %s times and processed %s rows per execution. ? , ? ? ? ? ? ? ? @? n ?SQL statement with SQL_ID "%s" was executed %s times and had an average elapsed time of %s seconds.Average time spent in PL/SQL execution was %s seconds.Average time spent in Java execution was %s seconds.Average time spent in Cluster wait events per execution was %s seconds.Average CPU used per execution was %s seconds.Service "%s" and Module "%s" was causing %s% of the row lock contention on this object. ? ? h ? ? ? U ?Average time spent in User I/O wait events per execution was %s seconds.Database sessions were found waiting for Oracle Resource Manager's active session slots.Sessions were found waiting for active session slots. Consider increasing the active session limit for these Oracle Resource Manager consumer groups.Session CPU consumption was throttled by the Oracle Resource Manager. Consider revising the resource plan that was active during the analysis period. ? ? e ? ? ? . vAlternatively, you may set the parameter "cursor_sharing" to "force".Parsing SQL statements were consuming significant CPU. Please refer to other findings in this task about parsing for further details.Undo I/O was a significant portion (%s\%) of the total database I/O.Consider lowering the value of parameter "undo_retention" to %s seconds. ? ? ? ? ? \ ?The value of "undo_retention" was %s seconds and the longest running query lasted only %s seconds. This extra retention caused unnecessary I/O.Reducing the size of redo generated by the application may reduce the wait time on "log buffer space" events.The value of parameter "%s" was "%s" during the analysis period.Increase the shared pool size by setting the value of parameter "shared_pool_size" to %s M. ? ? ? ? ? ? { ?The I/O usage statistics for the object are: %s full object scans, %s physical reads, %s physical writes and %s direct reads.Increase SGA target size by increasing the value of parameter "sga_target" by %s M.Tune the PL/SQL block with SQL_ID "%s". Refer to the "Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User\'s Guide and Reference".No single SQL or database statement was responsible for a significant amount of physical I/O. ? & ? x ? ? ? ? c ?Individual database segments responsible for significant user I/O wait were found.Individual SQL statements responsible for significant physical I/O were found.Individual database segments responsible for significant physical I/O were found.Investigate application logic involving I/O on %s "%s.%s" with object ID %s.Increase size of buffer cache for blocks of non-default size %s K by setting the value of parameter "db_%sk_cache_size" to %s M. ? ? ? X ?When increasing the size of a non-default buffer cache, the memory is taken from the default buffer cache. The recommended action for setting "sga_target" compensates for this by sufficiently increasing the default buffer cache size.Undo I/O issues cannot be diagnosed because automatic undo management was turned off.The impact of cursors being aged out of the shared pool cannot be determined because of changes in the shared pool size. ? ? ? ? ? ] ?The impact of cursors being aged out of the shared pool cannot be determined because of incomplete AWR snapshots.The impact of hard parses due to cursor invalidation and literal usage cannot be determined because of incomplete AWR snapshots.I/O capacity issues cannot be diagnosed because of incomplete AWR snapshots.ADDM cannot determine if the buffer cache was undersized because of changes in the buffer cache size. ? ? } ? ? ? r ?ADDM cannot determine if the buffer cache was undersized because of incomplete AWR snapshots.The impact of checkpoint activity due to MTTR setting cannot be determined because of incomplete AWR snapshots.The impact of checkpoint activity due to parallel queries and tablespace DDL cannot be determined because of incomplete AWR snapshots.The impact of undo I/O activity cannot be determined because of incomplete AWR snapshots. ? ? y ? ? ? wThe impact of RMAN I/O activity cannot be determined because of incomplete AWR snapshots.RMAN I/O activity had no significant impact on the throughput of the I/O subsystem.RMAN I/O activity had a significant impact on the throughput of the I/O subsystem.Consider slowing down RMAN activity, or scheduling RMAN jobs when user activity is lower. ? & ? ? ? ? ? *? ? ?Consider not using the compression option for RMAN jobs. Alternatively, consider slowing down RMAN activity, or scheduling RMAN jobs when user activity is lower.The SGA was adequately sized.The SGA was inadequately sized, causing additional I/O or hard parses.The optimal SGA size could not be determined because the value of "sga_target" changed during the analysis period.The optimal SGA size could not be determined because of incomplete AWR snapshots. ? ? k ? +? ? ?Increase the size of the SGA by setting the parameter "sga_target" to %s M.The SGA was inadequately sized, causing additional I/O or hard parses. Additionally, some buffer caches for blocks of non-default size were undersized, causing significant additional read I/O.The impact of checkpoint activity due to drop and truncate operations cannot be determined because of incomplete AWR snapshots.The streams pool was inadequately sized, causing additional I/O. ? ? F ? ? ? ? VThe streams pool was adequately sized.The optimal streams pool size could not be determined because of incomplete AWR snapshots.Increase the size of the streams pool by setting the parameter "streams_pool_size" to %s M.The optimal streams pool size could not be determined because the streams pool was resized. ? ? ? ? ] ?Investigate cause of contention on blocks received by this instance from remote instance "%s". This problem is often related to long waits on event "gcs log flush sync" in the remote instance.Waits on event "log file sync" were the cause of significant database wait on "gc buffer busy release" when releasing a data block.Waits on event "log file sync" in this instance can cause global cache contention on remote instances. ? ? ? ? / ?During the analysis period, the average data files' I/O throughput was %s per second for reads and %s per second for writes. The average response time for single block reads was %s milliseconds.The average response time for single block reads for this file was %s milliseconds.SQL statements with PLAN_HASH_VALUE %s were found to be using literals. Look in V$SQL for examples of such SQL statements. ? ? ? ? H ?Trace the cause of row contention in the application logic. Use given blocked SQL to identify the database objects involved. Investigate application logic involving DML on these objects.Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespaces.No single SQL statement was responsible for significant inter-instance messaging. ? ? ? ? U ?Inter-instance read and write contention on database blocks was consuming significant database time on this instance. However, there were no predominant hot blocks or objects responsible for the contention.The buffer cache for blocks of non-standard size %s K was undersized causing significant additional read I/O.Increase the value of parameter "sga_target" by %s M in order to make that memory available for the shared pool. ? & ? ? ? ? ? ?? ? ?Streams enqueue operations were blocked due to insufficient memory in the streams pool and consumed significant database time.Streams enqueue operations were not blocked due to insufficient memory in the streams pool.At least %s SQL statements with PLAN_HASH_VALUE %s were found to be using literals. An example is SQL statement with SQL_ID "%s".At least one execution of the statement ran in parallel.Wait class "Queueing" was not consuming significant database time. ? J X ? Y ? Z ? [ ? \ ? ] ? ^ _ *` >a m ?Wait class "Queueing" was consuming significant database time.ADDM Report for Task '%s'Analysis PeriodAWR snapshot range from %s to %s.Time period starts at %sTime period ends at %sAnalysis TargetDatabase '%s' with DB ID %s.Database version %s.Database version during analysis period was %s.Database version when ADDM was executed was %s. b & c ? d ? e ? f > ?All recommendations generated by ADDM are valid for database version %s, the version in which ADDM was executed.ADDM performed an analysis of all instances.ADDM performed an analysis of instances numbered %s.ADDM performed an analysis of instance %s, numbered %s and hosted at %s.Analysis was requested for all instances, but ADDM only analyzed a subset of the instances. g , h ? i j Yk |l ? ?Analysis was requested for all instances, but ADDM analyzed instance %s, numbered %s and hosted at %s.Analysis was requested for a subset of instances, but ADDM analyzed instance %s, numbered %s and hosted at %s.See the "Additional Information" section for more information on the requested instances.Activity During the Analysis PeriodTotal database time was %s seconds.The average number of active sessions was %s. m b n ? o ? p ? q ? r s $t Xu ^v bw kx zy ?z ?{ ? ?ADDM analyzed %s of the requested %s instances.There are no findings to report.Database ID %s.ADDM performed an analysis of instance number %s.Additional InformationInstances that were analyzed:Instances that were requested but were not analyzed:NumberNameHost NameActive SessionsPercent of ActivityReason Instance was ExcludedStartup or shutdown during analysis periodMissing or error in snapshots | \ } r ~ ? ? ? ? ? ? ? !? \? j? x? ?? ?? ?? ? Missing key statisticsAWR snapshots could not be found for the instanceWarningsMiscellaneous InformationTask parameters with non-default settingImpact is %s active sessions, %s\% of total activity.Instances that were significantly affected by this finding:Percent ImpactADDM Task NameCheck the ADDM analysis of affected instances for recommendations.Application AnalysisDatabase ConfigurationHost ConfigurationSQL Tuning ? \ ? j ? x ? ? ? ? ? ? ? ? ? ? W? ]? f? t? ?? ? ?Segment TuningSchema ChangesUnknown Recommendation TypeNo recommendations are available.The available recommendations have the following types:Recommendation TypeNumber of RecommendationsEstimated benefit is %s active sessions, %s\% of total activity.ActionRationaleRelated ObjectSQL statement with SQL_ID %s and PLAN_HASH %s.SQL statement with SQL_ID %s.Database object with ID %s. ? n ? ? ? ? ? ? ? ? ? ? #? N? h? t? ?? ?? ?? ?? ?? ?? ? ?Database block with object number %s, file number %s and block number %s.Database fileTablespace %s with ID %s.Database latch %s.Database enqueue %s.Database enqueue %s with ID1 %s.Database enqueue %s with ID1 %s and ID2 %s.Related object of type %s.ATTR1 is %s.ATTR2 is %s.ATTR3 is %s.ATTR4 is %s.Recommendation %s:Finding %s:Summary of FindingsDescriptionRecommendations ? D ? ` ? ? ? ? ? ? ? ? ? ? .? ?? ? ?Findings and RecommendationsSymptoms That Led to the Finding:Impact is %s active sessions, %s\% of total activity.Directives that may affect this report:Examine instance ADDMDeprecated ParameterThe type of analysis ADDM should performThe expected response time in milliseconds for reading one data block from a data fileThe amount of database time in milliseconds accumulated in the analysis periodThe database id for analysis ? 8 ? c ? ? ? ? ? ? ? R? }? ? ?The last snapshot id in the analysis periodThe instance number for analysisThe first snapshot id in the analysis periodSQL predicate to filter the SQL from the SQL Tuning SetPlan filter applicable in case there are multiple plans (plan_hash_value) associated with the same statementA first ORDER BY clause on the selected SQLA second ORDER BY clause on the selected SQLA third ORDER BY clause on the selected SQL ? , ? o ? ? ? ? ? -? ? ?Limit the number of SQL from the filtered and ranked SQL tuning setA percentage on the sum of a ranking measureThe username for whom the SQL statement will be tunedThe number of seconds between the begin time of the analysis time period and the current timeThe number of seconds between the end time of the analysis time period and the current timeThe unique task id generated by the automatically invoked advisor ? 2 ? w ? ? ? ? >? ?? ? ?TRUE if the task was created automatically, FALSE if created manuallyTRUE if result should include findings with recommendations, FALSE otherwiseThe number of statements after which commit tuning results for a SQL tuning setTime limit per statement in a SQL Tuning SetSQL predicate to filter SQL from the SQL Tuning Set when resuming a tuning taskSpecify the default action of a task execution.Tune the performance of SQL statements ? 2 ? u ? ? ? ? T? r? ? ?TRUE if SQL Profiles should be created by the task, FALSE otherwiseTRUE if SQL Profiles created by the user should be replaced, FALSE otherwiseMaximum number of SQL Profiles that can be created by the system in one runMaximum number of system SQL Profiles that are allowable at any one timeTest execute of SQL statementsGenerate explain plan of SQL statementsSpecifies the expiration time in days for individual executions of the current task ? 2 ? W ? ? ? ? ? ? 1? ] ?Analyze performance of SQL statementsThreshold of a SQL statement impact on a workloadThreshold of a change impact on a SQL statementSpecify an expression of execution statistics to use in performance comparison.Name of the first task execution to analyzeName of the second task execution to analyzeYES if SQL statements should be test-executed to measure benefit; NO otherwise ? ? ~ ? 7 ?Indicated whether the advisor could use the compilation environment captured with the SQL statementsFULL if SQL statements should be test-executed for the full local time limit to measure benefit, AUTO for some automatically-chosen smaller time, and NO for no test execution whatsoeverTRUE to require all important binds for test-execution, FALSE to install fake NULL binds in place of missing binds ? ? ? ?This attribute sets parameter OPTIMIZER_FEATURES_ENABLE to its default value for this statement instead of %s. This enables the latest optimizer features to be used.This attribute sets parameter OPTIMIZER_FEATURES_ENABLE to its default value, since at least one of the optimizer dependent parameters was set to a non-default value. This enables the latest optimizer features to be used. ? ? ? ? ? ? ?This attribute sets parameter OPTIMIZER_FEATURES_ENABLE to its default value for this statement. This enables the latest optimizer features to be used.This attribute causes the optimizer to try an interesting alternative plan for this statement.This attribute changes the optimizer mode from %s to %s. The optimizer mode was changed after examining the execution statistics of this statement.This attribute preserves the optimizer mode in the user specified hints for the query. ? > ? n ? ? ? ? ? ? ? ? K? l ? ?This attribute enables the cost-based optimizer.This attribute adjusts optimizer estimates.This attribute enables the "first rows" optimizer mode.This attribute disables optimizer hints.Table "%s"."%s" was not analyzed.Table "%s"."%s" and its indices were not analyzed.Index "%s"."%s" was not analyzed.Optimizer statistics for table "%s"."%s" are stale.Optimizer statistics for table "%s"."%s" and its indices are stale. S ? + ?Optimizer statistics for index "%s"."%s" are stale.The optimizer requires up-to-date statistics for the table in order to select a good execution plan.The optimizer requires up-to-date statistics for the table and its indices in order to select a good execution plan.The optimizer requires up-to-date statistics for the index in order to select a good execution plan. ? ?This attribute provides the optimizer with basic table statistics because the table statistics are missing for this table.This attribute provides the optimizer with basic table statistics because the table statistics are stale for this table.This attribute provides the optimizer with basic column statistics because the table statistics are missing for this table. & ? ? ? ?This attribute provides the optimizer with basic column statistics because the table statistics are stale for this table.This attribute provides the optimizer with basic index statistics because the index statistics are missing for this index.This attribute provides the optimizer with basic index statistics because the index statistics are stale for this index.Consider accepting the recommended SQL profile.Consider collecting optimizer statistics for this table. , d ? K ? ?Consider collecting optimizer statistics for this index.Outline "%s" exists for this statement and was ignored during the tuning process.SQL Profile "%s" exists for this statement and was ignored during the tuning process.A potentially better execution plan was found for this statement.Consider collecting optimizer statistics for this table and its indices.Type of SQL statement not supported. ? ? ? ?Fixed SQL plan baseline "%s" exists for this statement and was ignored during the tuning process.An automatically-created %s is present on the system.A manually-created %s is present on the system.The %s was tested by executing both its plan and the original plan and measuring their respective execution statistics. A plan may have been only partially executed if the other could be run to completion in less time. & ? ? $ r ?This statement was skipped because it has already been tuned recently. See task execution "%s" for the most recent tuning results.The %s is no longer present on the system.This statement was skipped because it was targeted by user blacklist filter "%s".The %s was not automatically created because the verified benefit was too low.The %s was not automatically created because its benefit could not be verified. ? ?The %s was not automatically created because auto-creation was disabled. Set task parameter ACCEPT_SQL_PROFILES to TRUE to enable auto-creation.The %s was not automatically created because the SQL has a fixed SQL plan baseline or a stored outline.The SQL profile was not automatically created because optimizer statistics were stale or missing. Issues with base optimizer statistics should be resolved prior to creating a SQL profile. ? ! @" ? ?The SQL profile was not automatically created because the global SQL profile limit had been reached.The SQL profile was not automatically created because replacing user SQL profiles was disabled. Set task parameter REPLACE_USER_SQL_PROFILES to TRUE to enable replacing user SQL profiles.The %s was not automatically created because test execution was disabled. Set task parameter TEST_EXECUTE to FULL or AUTO to enable test execution.The %s was not automatically created. # $ x % ? & : ?The %s's benefit could not be verified through test execution because an error occurred.The %s's benefit could not be verified through test execution because the operation timed out.The %s's benefit could not be verified because test execution is not supported for parallel queries.The %s's benefit could not be verified because test execution is not supported for DMLs or DDLs. ' & ( ? ) ? * + Z ?The %s's benefit could not be verified because test execution is not supported for this statement type.The %s's benefit could not be verified through test execution.%s "%s" was created automatically for this statement.SQL profile "%s" and SQL plan baseline "%s" were created automatically for this statement.The task did not analyze the full set of candidate SQL because the recommendation limit was reached. , - ? . ? / _ ?Consider accepting the recommended SQL profile. A SQL plan baseline corresponding to the plan with the SQL profile will also be created.Consider accepting the recommended SQL plan baseline.Task execution terminated with "FATAL ERROR" status, but SQL profile "%s" was implemented automatically before the error occurred.Consider accepting the recommended SQL profile. The SQL plan baseline corresponding to the plan with the SQL profile will also be updated to an accepted plan. 0 1 G 2 ? eConsider accepting the recommended SQL patch.Consider accepting the recommended SQL patch. A SQL plan baseline corresponding to the plan with the SQL patch will also be created.Consider accepting the recommended SQL patch. The SQL plan baseline corresponding to the plan with the SQL patch will also be updated to an accepted plan. 3 , 4 ? 5 36 m7 ?8 ? ?At least one important bind value was missing for this sql statement. The accuracy of the advisor's analysis may depend on all important bind values being supplied.The %s was not automatically created because it may have caused a significant i/o time degradation.The statement was first executed to warm the buffer cache.Statistics shown were averaged over next %s executions.Statistics shown were from the second execution.This attribute enables parallel execution. 9 X A potentially better parallel execution plan was found for this statement. : ?Executing this query parallel with DOP %s will improve its response time %s%% over the SQL profile plan. However, there is some cost in enabling parallel execution. It will increase the statement's resource consumption by an estimated %s%% which may result in a reduction of system throughput. Also, because these resources are consumed over a much smaller duration, the response time of concurrent statements might be negatively impacted if sufficient hardware capacity is not available. ; < p ? Consider accepting the recommended SQL profile to use parallel execution for this statement.%s potentially better execution plans were found for this statement. Choose one of the following SQL profiles to implement. = ?Executing this query parallel with DOP %s will improve its response time %s%% over the original plan. However, there is some cost in enabling parallel execution. It will increase the statement's resource consumption by an estimated %s%% which may result in a reduction of system throughput. Also, because these resources are consumed over a much smaller duration, the response time of concurrent statements might be negatively impacted if sufficient hardware capacity is not available. > ? ? @ - ?Some alternative execution plans for this statement were found by searching the system's real-time and historical performance data.Creating a plan baseline for the plan with the best elapsed time will prevent the Oracle optimizer from selecting a plan with worse performance.Consider creating a SQL plan baseline for the plan with the best average elapsed time. A DThe Original Plan appears to have the best performance, based on the elapsed time per execution. However, if you know that one alternative plan is better than the Original Plan, you can create a SQL plan baseline for it. This will instruct the Oracle optimizer to pick it over any other choices in the future. B C ?D ? ?Because no execution history for the Original Plan was found, the SQL Tuning Advisor could not determine if any of these execution plans are superior to it. However, if you know that one alternative plan is better than the Original Plan, you can create a SQL plan baseline for it. This will instruct the Oracle optimizer to pick it over any other choices in the future. The object is missing.The object can be deleted. E F z G 6 ?The Original Plan appears to have the best performance, based on the elapsed time per execution.The plan with id %s could not be reproduced because %s is missing. For this reason, a SQL plan baseline cannot be created to instruct the Oracle optimizer to pick this plan in the future.The plan with id %s could not be reproduced because %s are missing. For this reason, a SQL plan baseline cannot be created to instruct the Oracle optimizer to pick this plan in the future. H & I ? J LK ?L ? ?The plan with id %s could not be reproduced in the current environment. For this reason, a SQL plan baseline cannot be created to instruct the Oracle optimizer to pick this plan in the future.All alternative plans other than the Original Plan could not be reproduced in the current environment.This plan could not be reproduced because %s is missing.This plan could not be reproduced because %s are missing.This plan could not be reproduced in the current environment. M N y BConsider using "UNION ALL" instead of "UNION", if duplicates are allowed or uniqueness is guaranteed."UNION" is an expensive and blocking operation because it requires elimination of duplicate rows. "UNION ALL" is a cheaper alternative, assuming that duplicates are allowed or uniqueness is guaranteed. O ? Consider replacing "NOT IN" with "NOT EXISTS" or ensure that columns used on both sides of the "NOT IN" operator are declared "NOT NULL" by adding either "NOT NULL" constraints or "IS NOT NULL" predicates. P S ] ?A "FILTER" operation can be very expensive because it evaluates the subquery for each row in the parent query. The subquery, when unnested can drastically improve the execution time because the "FILTER" operation is converted into a join. Be aware that "NOT IN" and "NOT EXISTS" might produce different results for "NULL" values.Consider removing the disconnected table or view from this statement or add a join condition which refers to it. T U ? V ? ?A cartesian product should be avoided whenever possible because it is an expensive operation and might produce a large amount of data.Consider removing the "ORDERED" hint.The "ORDERED" hint might force the optimizer to generate a cartesian product. A cartesian product should be avoided whenever possible because it is an expensive operation and might produce a large amount of data. Y & Z ? [ "\ a] ? ?The optimizer cannot merge a view that contains an "ORDER BY" clause unless the statement is a "DELETE" or an "UPDATE" and the parent query is the top most query in the statement.The optimizer cannot merge a view that contains a "ROWNUM" pseudo column.The optimizer cannot merge a view that contains a set operator.The optimizer cannot merge a view that contains windowing functions.The optimizer cannot merge a view that contains a "SPREADSHEET" clause. ^ & _ q ` ? a b ? ?The optimizer cannot merge a view that contains nested aggregate functions.The optimizer cannot merge a view that contains aggregate functions without "GROUP BY" clause.The optimizer cannot merge a view that contains grouping functions.The optimizer cannot merge a view that contains a "GROUP BY" clause with a "ROLLUP", "CUBE" or "GROUPING SETS" option.The optimizer cannot merge a view that contains a "START WITH" clause. c & d f g ? h ? i Z ?The optimizer cannot merge a view that contains a NO_MERGE hint.The optimizer cannot merge a view that contains a "CURSOR" expression.The optimizer cannot merge a view that contains a "WITH" clause.The optimizer cannot merge a view with a predicate containing a nested table column involved in an outer join.The optimizer could not merge the complex view at line ID %s of the execution plan. j k ? l K ?View merging may improve execution time by enabling generation of a better execution plan. Setting parameter OPTIMIZER_FEATURES_ENABLE to a value less than 9.0.1 prevents the optimizer from merging complex views.The optimizer cannot merge a complex view if its parent query contains a "START WITH" clause.The optimizer cannot merge a complex view if its parent query is a "SELECT FOR UPDATE". m n ? o p g ?A view on the right side of an outer join can be merged only if it contains a single table with a simple "WHERE" clause.The optimizer cannot merge a complex view if its parent query contains a reference to a "ROWNUM" pseudo-column.The optimizer cannot merge a complex view if its parent query contains a "GROUP BY CUBE" clause.The optimizer cannot merge a complex view if its parent query contains a "GROUPING SETS" clause. q & r ? s ? t u ? ?The optimizer cannot merge a complex view if the "SELECT" list of its parent query contains a "SEQUENCE" column.The optimizer cannot merge a view that contains a group outer join.The optimizer cannot merge a view involved in a group outer join.Consider enabling complex view merging by using the "MERGE" hint or by setting parameter OPTIMIZER_FEATURES_ENABLE to least 9.0.1.An expensive cartesian product operation was found at line ID %s of the execution plan. v & w v x ? y z c ?The optimizer could not unnest the subquery at line ID %s of the execution plan.The optimizer could not merge the view at line ID %s of the execution plan.An expensive "UNION" operation was found at line ID %s of the execution plan.The execution plan of this statement can be improved by creating one or more indices.Consider running the Access Advisor to improve the physical schema design or creating the recommended index. { | ? ?The predicate %s used at line ID %s of the execution plan contains an expression on indexed column "%s". This expression prevents the optimizer from selecting indices on table "%s"."%s".The predicate %s used at line ID %s of the execution plan contains an expression on indexed column "%s". This expression prevents the optimizer from efficiently using indices on table "%s"."%s". } ~ ? ?The predicate %s used at line ID %s of the execution plan contains an implicit data type conversion on indexed column "%s". This implicit data type conversion prevents the optimizer from selecting indices on table "%s"."%s".The predicate %s used at line ID %s of the execution plan contains an implicit data type conversion on indexed column "%s". This implicit data type conversion prevents the optimizer from efficiently using indices on table "%s"."%s". ? ? ? P ?The optimizer is unable to use an index if the predicate is an inequality condition or if there is an expression or an implicit data type conversion on the indexed column.Rewrite the predicate into an equivalent form to take advantage of indices. Alternatively, create a function-based index on the expression.Rewrite the predicate into an equivalent form to take advantage of indices. ? ? ? ?Predicate %s used at line ID %s of the execution plan is an inequality condition on indexed column "%s". This inequality condition prevents the optimizer from selecting indices on table "%s"."%s".Predicate %s used at line ID %s of the execution plan is an inequality condition on indexed column "%s". This inequality condition prevents the optimizer from efficiently using indices on table "%s"."%s". ? zCreating the recommended indices significantly improves the execution plan of this statement. However, it might be preferable to run "Access Advisor" using a representative SQL workload as opposed to a single statement. This will allow to get comprehensive index recommendations which takes into account index maintenance overhead and additional space consumption. ? ? ? 1Both an index and a SQL profile were recommended for this statement. The optimizer needs the SQL profile to be created to use the plan with the recommended indexes.The plan with the recommended indexes must be loaded as a SQL plan baseline so that the optimizer can use those indexes. ? ? ?Consider running the Access Advisor to improve the physical schema design or creating the recommended index. If you choose to create the recommended index, consider dropping the index "%s"."%s" because it is a prefix of the recommended index.A potentially beneficial index exists already but is currently marked unusable. Consider rebuilding the index so that the optimizer can use it. ? ? t? ? ?Consider running the Access Advisor to improve the physical schema design or creating the recommended index. Note that there are multiple prefix indexes of the recommended index already existing on the system. If you choose to create the recommended index, consider dropping those that do not enforce any constraints because they are redundant.The performance of this SQL has improved.The performance of this SQL has regressed. ? , ? ? ? ? ? ? ? [? ? ?One of the execution plans required by the analysis is missing for this SQL statement.This SQL statement returned zero rows.The structure of the SQL execution plan has changed.The structure of the SQL plan in execution '%s' is different than its corresponding plan which is stored in the SQL Tuning Set.The structure of the SQL plan in execution '%s' is similar to its corresponding plan which is stored in the SQL Tuning Set.Error in execution '%s': %s ? 2 ? ? ? ? / g ? ?The number of returned rows in execution '%s' is different than in execution '%s'.%sAn error occurred while processing this SQL statement causing task execution to fail. The task execution was successfully resumed after the task failure.Feature used: %sPlan for strategy %s has cost %s with plan hash value %sFeature %s was accepted because of %sStrategy execution %s failed with error code %s and error message %s , ? 5 m ? ?Alternative plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer getsRecommended plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer gets%s CR Diff'ing: Feature %s [base %s, target %s]%s CR Diff'ing: Object base construct %s is %s in targetValidation [rule: %s, status: %s]Plan for strategy %s with plan directive (hint) %s has cost %s with plan hash value %s 2 P ! u " ? ? ? ? i? ? ?Invalid value for problem typeInvalid value for incident identifierOriginal plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer gets%s P1: %s P2: %sSnapshot Too Old Error detected: SQL ID %s, Snapshot SCN %s, Recent SCN %s, Undo Tablespace %s, Current Undo Retention %s.Snapshot Too Old Error detected: SQL ID %s, Snapshot SCN %s, Recent SCN %s, Rollback Segment %s.Please run undo advisor. ? ? D ? ? ? , ?Please check rollback segment usage.Operation on resumable session %s session id %s suspended because of errors in tablespace %s. Error message is %sOperation on resumable session %s session id %s suspended because of errors in rollback segment %s. Error message is %sOperation on resumable session %s session id %s suspended because of errors in %s. Error message is %s ? 8 ? ? ? ? ? ? ? ? U? ?? ? ?Operation on resumable session %s session id %s suspended because of errors in user quota. Error message is %sPlease check view dba_resumable.Set initialization parameter undo_retention to %dSize undo tablespace to %d MBThe longest query duration is longer than undo retention setting.Some of your queries may fail due to snap shot too old errors.Undo Tablespace is under pressure.Some of your operations may fail due to full undo tablespace. ? 8 ? ? ? ? ? ? G? g? ?? ? ?Set undo retention to longest query duration to avoid snap shot too old error.Set undo tablespace size based on undo generation rate and undo retentionCannot run Undo advisor when the system is running with manual undo management.The system is auto tuning undo retention.There is not enough data in AWR.There is no target_object.Reduce Snapshot Too Old errors.Avoid undo tablespace pressure ? 2 ? ? ? ? ? h? ?? ?? ? ?Recommended undo tablespace size is based on undo generation rate and longest query duration in the system.Recommended undo retention is based on longest query duration in the system.Recommended undo retention is the best possible undo retention based on undo generation rate and current undo tablespace size.The undo tablespace is OK.Undo tablespace is OK.Improve the usage of undo tablespaceUndo retention is too high ? 2 ? ? ? ? ? ,? R? x? ? ?Undo retention is set to higher than best possible retention and undo tablespace will be under pressureRecommended undo tablespace size is based on undo generation rate and undo retention in the system.Instance does not have an online undo tablespaceOnline undo tablespace with size %d MBInstance has an online undo tablespaceInstance has an online undo tablespaceMany operations may fail without undo tablespace online ? > ? ? ? ? ? ? ? ? )? O? y? ? ?Recommended undo tablespace size is based on undo generation rate , undo retention and longest query duration in the system.Tablespace [%s] is [%s] fullAdd space to the tablespaceMetrics "%s" is at %sMetrics "%s" is at %s for file "%s"Metrics "%s" is at %s for service "%s"Metrics "%s" is at %s for event class "%s"Run ADDM to get more performance analysis about your system.Session %s is blocking %s other sessions ? , ? b ? ? ? ? ? ? ? ? Threshold is updated on metrics "%s" for instance "%s"Check DBA_THRESHOLDS view to verify the resultThreshold is updated on metrics "Tablespace Space Usage"Tablespace [%s] only has [%s] free spaceRun the calibrate utility and restart a replay with the suggested number of WRC clients, distributed between machines with the necessary capacity.The average response time for a single IO has reached a concerning value (%s ms) for WRC client %s running on %s as process %s ? & ? ? ? ? 1 K ?Too many replay client connections (%s\%) are using the CPU concurrently in WRC client %s running on %s as process %sToo many replay client connections (%s\%) are doing concurrent IO operations in WRC client %s running on %s as process %sDatabase is in capture modeDatabase is in replay mode%s of %s bytes is %s%% used and has %s remaining bytes available. t ?? ? ?Choices to free up space from recovery area: 1. Consider changing RMAN %s. If you are using Data Guard, then consider changing RMAN %s. 2. Backup files to tape using RMAN %s command. 3. Add disk space and increase db_recovery_file_dest_size parameter. 4. Delete unnecessary files using RMAN %s command. If OS command was used to delete files, then use RMAN %s commands.Estimated space usage if table is created is %s bytes.Estimated space usage if index is created is %s bytes. < 2 = L > ~ ? ? @ ? A -B s ?Growth trend table output.Insufficient information to make a recommendation.The object has less than 1% free space, it is not worth shrinking.Perform shrink, estimated savings is %s bytes.The object has some free space but cannot be shrunk because %s.The free space in the object is less than the size of the last extent.Allocated Space:%s: Used Space:%s: Reclaimable Space :%s: C 2 D ? E ? F ? G 7H fI ? ?Enable row movement of the table %s.%s and perform shrink, estimated savings is %s bytes. Perform re-org on the object %s, estimated savings is %s bytes. %s percent chained rows can be removed by re-org.The object has chained rows that can be removed by re-org.The free space in the object is less than 10MB.Compress object %s.%s, estimated savings is %s bytes.Compress object %s.%s partition %s, estimated savings is %s bytes. J 8 ? } ? ? ? ? O ? ?Compress object %s.%s subpartition %s, estimated savings is %s bytes.No action is necessary -- Grid Director to process.An instance is being quiesced.No action is necessaryRestart if desired and not automatically restartingInstance %s up on node %s as of time %s; reason code: %sInstance %s down on node %s as of time %s; reason code: %sComposite service %s%s up as of time %s; reason code: %s 2 l ? ? 9 ?! ? ?Composite service %s%s down as of time %s; reason code: %sService up on instance %s node %s as of time %s; reason code: %sService down on instance %s node %s as of time %s; reason code: %sService preconnect up on instance %s node %s as of time %s; reason code: %sService preconnect down on instance %s node %s as of time %s; reason code: %sDatabase %s (domain %s) up as of time %s; reason code: %sDatabase %s (domain %s) down as of time %s; reason code: %s " , # f $ ? ? ? ? ? ? ?Node %s incarnation %s down as of time %s; reason code: %sASM Instance %s up on node %s as of time %s; reason code: %sASM Instance %s down on node %s as of time %s; reason code: %sSTREAMS capture process "%s" aborted with ORA-%sObtain the exact error message in dba_capture, take the appropriate action for this error, and restart the capture process using dbms_capture_adm.start_capture.STREAMS apply process "%s" aborted with ORA-%s ? ? 3 mObtain the exact error message in dba_apply, take the appropriate action for this error, and restart the apply process using dbms_apply_adm.start_apply. If the error is an ORA-26714, consider setting the 'DISABLE_ON_ERROR' apply parameter to 'N' to avoid aborting on future user errors.STREAMS propagation process "%s" aborted after 16 failures ? ? ? ? - |Obtain the exact error message in dba_queue_schedules, take the appropriate action for this error, and restart the propagation process using dbms_propagation_adm.start_propagation.If the currently running workload is typical, consider increasing the size of the Streams pool.STREAMS error queue for apply process "%s" contains new transaction with ORA-%s ? , ? ? M? j? ?? ? ?Look at the contents of the error queue as well as dba_apply_error to determine the cause of the error. Once the errors are resolved, reexecute them using dbms_apply_adm.execute_error or dbms_apply_adm.execute_all_errors.Table %s sort on column %s - compression ratio by block count is %sIncorrect compression type %sTable %s %s - Estimated compression ratio is %sTable %s with sampling percentage %sNot enough data for compression ratio ? 8 ? Y ? ? ? ? ? ? ? ? O? ? ?Estimated compression ratio is %sObj no %s: Table %s compressable - Number of uncompressed blocks is %sThis procedure is not supported for SYSTEM and SYSAUX tablespacesTablespace %s does not existTable %s does not existTable Partition %s.%s %s - Estimated compression ratio is %sTable Partition %s.%s with sampling percentage %sTable Partition %s.%s sort on column %s - estimated compression ratio is %s ? b ? ? ? ? ? ? ? ? ? ? .? B? T? j? ? ?? ?? ?? ? ?Obj no %s: Table Partition %s.%s compressable - Number of uncompressed blocks is %s"Administrative" Wait Class"Application" Wait Class"Cluster" Wait Class"Concurrency" Wait Class"Configuration" Wait Class"Network" Wait Class"Other" Wait Class"Scheduler" Wait Class"User I/O" wait ClassBuffer BusyBuffer Cache LatchesCheckpoints Due to DROP or TRUNCATECheckpoints Due to Log File SizeCheckpoints Due to MTTR ? t ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? ^? |? ?? ?? ?? ?? ? ?Checkpoints Due to Parallel QueriesCheckpoints Due to Tablespace DDLCommits and RollbacksCPU UsageDBMS_LOCK UsageDBMS_PIPE UsageExcessive RebindsFree Buffer WaitsHard ParseHard Parse Due to InvalidationsHard Parse Due to Literal UsageHard Parse Due to Parse ErrorsHard Parse Due to Sharing CriteriaHigh Watermark WaitsI/O ThroughputIndex Block SplitGlobal Cache BusyGlobal Cache Congestion ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 2? B? J? X? f? ?? ?? ?? ?? ?? ?? ? ?Interconnect LatencyGlobal Cache Lost BlocksGlobal Cache MessagingGlobal Cache Multiblock RequestsITL WaitsJava ExecutionLatch Free WaitsLog File SwitchesPL/SQL CompilationPL/SQL ExecutionRMAN I/ORow Lock WaitsSequence UsageSession Connect and DisconnectSession Slot SchedulingShared Pool LatchesSlow ArchiversSoft ParseSpace Transaction WaitsStreams Flow ControlTable Locks ? n ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 2? I? Q? t? ?? ?? ? ?Temp Space ContentionTop Segments by I/OTop SQL by "Cluster" WaitTop SQL by DB TimeTop SQL By I/OUndersized Buffer CacheUndersized PGAUndersized Redo Log BufferUndersized SGAUndersized Shared PoolUndersized Streams PoolUndo I/OUnusual "Administrative" Wait EventUnusual "Application" Wait EventUnusual "Cluster" Wait EventUnusual "Commit" Wait EventUnusual "Concurrency" Wait Event ? ? ? ? ? ? ? ? ? ? ? ? .? >? E? H? P? X? ^? j? o? ?? ?? ?? ?? ?? ? ?Unusual "Configuration" Wait EventUnusual "Network" Wait EventUnusual "Other" Wait EventUnusual "Scheduler" Wait EventUnusual "User I/O" Wait EventVirtual Memory PagingResource ManagerParsingCPUData I/ORedo I/OMemoryInterconnectSpaceInternal ConcurrencyApplication WaitsQueue OperationsTop ConsumersMiscellaneous"Queueing" Wait ClassUnusual "Queueing" Wait Event ? 2 ? L ? ^ ? ? ? ? ? ? ? " Undersized instance memoryTop SQL StatementsTop Segments by "User I/O" and "Cluster"Buffer Busy - Hot BlockBuffer Busy - Hot ObjectsContention for latches related to the shared pool was consuming significant database time in some instances.Contention on buffer cache latches was consuming significant database time in some instances. ? ? ? ? ? x ?Waits for free buffers were consuming significant database time in some instances. Database writers (DBWR) were unable to keep up with the demand for free buffers.Waits for redo log buffer space were consuming significant database time in some instances.Host CPU was a bottleneck for some instances. Wait times will be inflated by wait for CPU.Significant virtual memory paging was detected on the host operating system of some instances. ? ? ? ? ? ? 7 ?Database latches in the "Other" wait class were consuming significant database time in some instances.Buffer caches were undersized in some instances, causing significant additional read I/O.The SGA was inadequately sized in some instances, causing additional I/O or hard parses.The streams pool was inadequately sized in some instances, causing additional I/O and blocking streams enqueue operations. ? ? ? ? ? ?The PGA was inadequately sized in some instances, causing additional I/O to temporary tablespaces to consume significant database time.Hard parsing of SQL statements was consuming significant database time in some instances.SQL statements with the same text were not shared because of cursor environment mismatch in some instances. This resulted in additional hard parses which were consuming significant database time. ? ? ? ? ? ?Hard parses due to an inadequately sized shared pool were consuming significant database time in some instances.Hard parsing SQL statements that encountered parse errors was consuming significant database time in some instances.Cursors were getting invalidated due to DDL operations. This resulted in additional hard parses which were consuming significant database time in some instances. ? ? ? ? ? { ?SQL statements were not shared due to the usage of literals. This resulted in additional hard parses which were consuming significant database time in some instances.Soft parsing of SQL statements was consuming significant database time in some instances.List of analyzed instance numbers, used when global ADDM analyzes only a subset of instancesThe instance is using the public interconnect device "%s" with IP address %s and source "%s". & ? ? ] ?The instance is using the private interconnect device "%s" with IP address %s and source "%s".Look at the instance level ADDM tasks for a list of interconnect devices used by a specific instance.Some instances were using public interconnect devices.The Oracle instance memory (SGA and PGA) was adequately sized.The Oracle instance memory (SGA and PGA) was inadequately sized, causing additional I/O and CPU usage. ? gThe optimal memory target for the instance could not be determined because the value of "memory_target" changed during the analysis period.The optimal memory target for the instance could not be determined because of incomplete AWR snapshots.Increase memory allocated to the instance by setting the parameter "memory_target" to %s M. ? r ?The Oracle instance memory (SGA and PGA) was inadequately sized, causing additional I/O and CPU usage. Additionally, some buffer caches for blocks of non-default size were undersized, causing significant additional read I/O.The Oracle instance memory (SGA and PGA) was inadequately sized in some instances, causing additional I/O and CPU usage.Enables database analysis mode for automatic ADDM runs ? a ?At least %s SQL statements with FORCE_MATCHING_SIGNATURE %s and PLAN_HASH_VALUE %s were found to be using literals. Look in V$SQL for examples of such SQL statements.At least %s SQL statements with FORCE_MATCHING_SIGNATURE %s and PLAN_HASH_VALUE %s were found to be using literals. An example is SQL statement with SQL_ID "%s".Tune the entry point PL/SQL "%s" of type "%s" and ID %s. Refer to the PL/SQL documentation for addition information. ~ ? ? ?Tune the entry point PL/SQL ID %s. Refer to the PL/SQL documentation for addition information.%s seconds spent in executing PL/SQL "%s" of type "%s" and ID %s.%s seconds spent in executing PL/SQL ID %s.Filter findings of type "%s" if the impact is less than %s active sessions or the impact is less than %s percent of database time for the analysis period. ? 8 ? ?Filter recommendations regarding SQL statements with SQL_ID "%s" if the impact of the SQL is less than %s active sessions or its response time is less than %s microseconds.Filter recommendations regarding segments that belong to owner "%s", named "%s" with sub-objects named "%s".Filter recommendations regarding the segment with data object number %s.Filter recommendations to change the value of parameter "%s". & g ? b ?Inter-instance messaging was consuming significant database time.Inter-instance messaging was not consuming significant database time.Higher than expected latency of the cluster interconnect was responsible for significant database time.Global Cache Service Processes (LMSn) were not processing requests fast enough.The database was consuming %s kilo bits per second of interconnect bandwidth. ? 1 ? ?Global Cache Service Processes (LMSn) were performing within acceptable limits of %s milliseconds.Investigate cause of contention on blocks received from remote instance "%s". This problem is often related to long waits on event "gcs log flush sync" in the remote instance.Waits on event "log file sync" in one instance can cause global cache contention on other instances.Investigate cause of congestion on blocks received by this instance from remote instance "%s". m ! ? " q ?Investigate cause of congestion on blocks received from remote instance "%s".This problem is often related to CPU bottleneck, virtual memory paging or inappropriate LMSn process priority in the remote instance.The device "%s" was used for %s\% of interconnect traffic and experienced %s send or receive errors during the analysis period.The device "%s" experienced %s send or receive errors during the analysis period. # $ ? % ` ?The instance was consuming %s kilo bits per second of interconnect bandwidth for global cache messages. Information on other interconnect traffic is not available.The database was consuming %s kilo bits per second of interconnect bandwidth for global cache messages. Information on other interconnect traffic is not available.%s\% of this interconnect bandwidth was used for global cache messaging, %s\% for parallel query messaging and %s\% for database lock management. & ' _ ( ? YThe average latency for 8K interconnect messages was %s microseconds.Consider slowing down RMAN or Data Pump activity, or scheduling these jobs when user activity is lower.The I/O throughput on data and temp files was divided as follows: %s%% by RMAN, %s%% by Data Pump, %s%% by Recovery and %s%% by all other activity. ) * ? + ^ ?The performance of some data and temp files was significantly worse than others. If striping all files using the SAME methodology is not possible, consider striping these file over multiple disks.For file %s, the average response time for single block reads was %s milliseconds, and the total excess I/O wait was %s seconds.Investigate the file I/O throughput of the archiver process(es) to make sure it is appropriate for the underlying hardware. , - ? . gThe archiver's I/O throughput was %s per second on redo log files and %s per second on archive and archive backup log files.The total I/O throughput on redo log files was %s per second and the archiver was responsible for %s%% of it.The total I/O throughput on redo log files was %s per second for reads and %s per second for writes. / P ? aThe redo log I/O throughput was divided as follows: %s%% by RMAN and recovery, %s%% by Log Writer, %s%% by Archiver, %s%% by Streams AQ and %s%% by all other activity.Investigate the %s statement with SQL_ID "%s" for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID. Q R ? S 4 ?Run SQL Tuning Advisor on the %s statement with SQL_ID "%s". Additionally, investigate this statement for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID.Run SQL Tuning Advisor on the %s statement with SQL_ID "%s".The SQL spent %s%% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. T U ? ?The SQL spent only %s%% of its database time on CPU, I/O and Cluster waits. Therefore, the SQL Tuning Advisor is not applicable in this case. Look at performance data for the SQL to find potential improvements.The SQL spent %s%% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. Look at data given below and an ASH report for further performance improvements. V W \ X ? Y T ?The SQL Tuning Advisor cannot operate on this SQL statement.Database time for this SQL was divided as follows: %s%% for SQL execution, %s%% for parsing, %s%% for PL/SQL execution and %s%% for Java execution.At least %s distinct execution plans were utilized for this SQL statement during the analysis period.Top level calls to execute the %s statement with SQL_ID "%s" are responsible for %s%% of the database time spent on the %s statement with SQL_ID "%s". Z [ ? \ ? ] E ?SQL statements consuming significant database time were found. These statements offer a good opportunity for performance improvement.The SQL Tuning Advisor cannot operate on %s statements.Full scan of %s "%s.%s" with object ID %s consumed %s%% of the database time spent on this SQL statement.Full scan of segment with object ID %s consumed %s%% of the database time spent on this SQL statement. ^ _ ? ` dI/O and Cluster wait for %s "%s.%s" with object ID %s consumed %s%% of the database time spent on this SQL statement.I/O and Cluster wait for segment with object ID %s consumed %s%% of the database time spent on this SQL statement.Individual database segments responsible for significant "User I/O" and "Cluster" waits were found. a b ? ?Look at the "Top SQL Statements" finding for SQL statements consuming significant I/O on this segment. For example, the %s statement with SQL_ID "%s" is responsible for %s%% of "User I/O" and "Cluster" waits for this segment.Look at the "Top SQL Statements" finding for SQL statements consuming significant time in Java execution. For example, the %s statement with SQL_ID "%s" is responsible for %s%% of Java execution time during the analysis period. c d ? ?Look at the "Top SQL Statements" finding for SQL statements consuming significant time on CPU. For example, the %s statement with SQL_ID "%s" is responsible for %s%% of CPU usage during the analysis period.Look at the "Top SQL Statements" finding for SQL statements consuming significant time on Cluster waits. For example, the %s statement with SQL_ID "%s" is responsible for %s%% of Cluster wait during the analysis period. e f ? g Y ?Look at the "Top SQL Statements" finding for SQL statements consuming significant time on the "%s" wait event. For example, the %s statement with SQL_ID "%s" is responsible for %s%% of these waits.No recommendations are available at the database level. Check the ADDM analysis of affected instances for recommendations.Increase the buffer cache size of affected instances. Check the ADDM analysis of affected instances for more details. h i ? Consider adding more CPUs or more instances serving the database. Check the ADDM analysis of affected instances for additional recommendations.Increase the shared pool size of affected instances. Check the ADDM analysis of affected instances for more details. j k ?Investigate the I/O subsystem's write performance. Consider increasing the number of database writers, the appropriateness of asynchronous I/O, and use of direct path inserts. Check the ADDM analysis of affected instances for more details.Investigate application logic for possible use of bind variables instead of literals. Alternatively, you may set the parameter "cursor_sharing" to "force". l m ? n G ?Increase the size of redo log buffers on affected instances. Investigate the performance of I/O to online redo log files. Check the ADDM analysis of affected instances for more details.Increase the memory allocated to affected instances. Check the ADDM analysis of affected instances for more details.Investigate memory allocation to Oracle instances and other applications on affected hosts. Check the ADDM analysis of affected instances for more details. o p ? q r { ?Increase the size of the SGA on affected instances. Check the ADDM analysis of affected instances for more details.Increase the streams pool size of affected instances. Check the ADDM analysis of affected instances for more details.Increase the size of the PGA on affected instances. Check the ADDM analysis of affected instances for more details.There were no hot blocks for "buffer busy" wait events during the analysis period. s & t y p q =r u ?There were no hot objects for "buffer busy" wait events during the analysis period.The session with ID %s and serial number %s in instance number %s was the blocking session responsible for %s%% of this recommendation's benefit.The %s was first executed to warm the buffer cache.Statistics for %s were averaged over next %s executions.Statistics for %s were from the second execution. ?? ??
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de