MINI MINI MANI MO
/ Copyright (c) 1990, 2017, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ smgus.msg - Oracle Server Manageability Messages
/
/ DESCRIPTION
/ This file should contain translateable non-error messages generated by
/ Server Manageability components like Advisors, Alerts, Self-tuning
/ components, Statistics, etc....
/ These messages are mainly informational in nature.
/
/ NOTES:
/ There is a limit of 390 bytes for English messages so that they can be
/ translated correctly.
/ While adding messages to this file, please make sure they are under this
/ length limit.
/
/ To check if your msg length is acceptable:
/ 1) Add your new msg within the appropriate message range
/
/ 2) Compile the msg file to produce the msb file
/ e.g. recomp smgus.msg
/
/ 3) Run lmsgen which checks lengths of all messages and reports issues
/ lmsgen smgus.msg rdbms ora american -t Y
/
/ If your message produces a warning or info output, please address the
/ issue by shortening the message to under 390 bytes.
/ This will prevent bugs from being filed against you by the NLS team.
/
/ OWNER
/ Shantanu Joshi
/
/ RESERVATION INFO
/ Use this section to reserve your message range.
/
/ ADDM (10g and cleanup of 10g code):
/ 00001 .. 00599
/
/ ADDM Report Only
/ 00600 .. 00699
/
/ ADDM (future use)
/ 00700 .. 00899
/
/ Advisor Framework:
/ 00900 .. 00999
/
/ Sql Tuning Advisor :
/ 01000 .. 01999
/
/ Transaction Layer :
/ 02000 .. 02999
/
/ Tablespace Alerts :
/ 03000 .. 03499
/
/ Threshold-based Alerts :
/ 03500 .. 03599
/
/ Backup/Recovery :
/ 03600 .. 03699
/
/ Object Space Advisor - Create Table :
/ 03700 .. 03799
/
/ Object Space Advisor - Create Index :
/ 03800 .. 03899
/
/ Object Space Advisor - Growth Trend :
/ 03900 .. 03999
/
/ Cluster/Database/Instance Control (e.g. Grid Director):
/ 04000 .. 04099
/
/ High Availability Alert Messages
/ 04100 .. 04299
/
/ Streams :
/ 04300 .. 04499
/
/ Compression Advisor :
/ 04500 .. 04599
/
/ SQL Plan Management Evolve Advisor
/ 04600 .. 04699
/
/ ADDM (11g and onwards)
/ 05000 .. 05999
/
/ SQL Auto-tune UI
/ 06000-06199
/
/ Optimizer Statistics Advisor
/ 07000 .. 07399
/
/==========================================================
/
/ MODIFIED (MM/DD/YY)
/ molagapp 09/08/17 - bug-14309181
/ msabesan 08/31/17 - bug 26712379: exadata-aware test exec msg
/ msabesan 05/31/17 - bug 26139155: exadata-aware profile msg
/ msabesan 05/19/17 - bug 24952618: exadata aware profile msg
/ kyagoub 01/13/17 - add SPA message 01192
/ schakkap 03/18/16 - #(22029499) Fix messages for statistics advisor
/ arbalakr 09/15/15 - Bug 21107502: Add new rules for Scheduler events
/ shjoshi 08/21/15 - bug 21660150: Shorten msgs 1082 and 1085
/ schakkap 08/18/15 - #(21572818) shorten messages
/ jorgrive 06/18/15 - Bug 14312810 - msg 4331, 4332
/ jiayan 05/12/15 - #20476526: shorten message
/ jiayan 09/15/14 - proj 44162: Stats Advisor
/ bhavenka 11/12/13 - bug 17425119: added SPA messages 01180-01182 for
/ adaptive plans
/ sepeng 06/03/13 - #(15956358): update SPM messages 04611-04614 to refer
/ to adaptive plans
/ kdusanj 04/09/13 - bug 16519867: Added message 03919 for chained rows
/ nbenadja 02/22/13 - Add GDS alerts.
/ ddas 03/01/13 - #(15989912) add message 4615
/ ushaft 02/27/12 - Add PDB messages for ADDM (5237-5267)
/ ddas 12/22/11 - enhance SPM for dynamic plans
/ ddas 08/22/11 - SPM Evolve Advisor
/ hayu 05/17/10 - add mesg for multi execution
/ smuthuli 03/18/10 - Change message for easier parsing
/ smuthuli 02/19/10 - Flash advice
/ rmao 12/21/09 - bug 9156278: add server generated alert for streams
/ automatic split/merge
/ arbalakr 09/16/09 - add 5237 PL/SQL rationale with subprogram id
/ molagapp 06/03/09 - remove flash reference
/ vkapoor 04/19/09 - Changing messages
/ smuthuli 03/13/09 - compression message
/ apanagar 03/06/09 - fix columnar compression messages
/ hayu 02/18/09 - fix lrg 3792048
/ rcolle 01/29/09 - add meaningful messages for DB Capture/Replay alerts
/ pbelknap 11/20/08 - new command for rebuild index
/ pbelknap 11/03/08 - add message for dropping index
/ amitsha 01/08/09 - add new message for compression advisor
/ hayu 10/03/08 - add mesg for fix regression
/ ushaft 11/20/08 - add 5236
/ hayu 11/24/08 - add more messages for multi exec
/ hayu 06/27/08 - add new message for pq recommendation
/ hayu 06/09/08 - add message for parallel execution
/ amitsha 09/10/08 - add new message for compression advisor
/ amitsha 08/07/08 - add new message for compression advisor
/ ushaft 06/26/08 - add 686 5030-5031 5033-5035 5094-5095 5222-5235
/ rcolle 06/26/08 - add more meaningful alerts for WRC client metrics
/ rcolle 06/05/08 - add separate alerts for capture/replay
/ ushaft 04/30/08 - add 5092,5093,5200-5221
/ hayu 04/29/08 - add new message for multi exec
/ hayu 04/09/08 - add message for sql tune
/ amitsha 05/04/08 - add message range for compression advisor
/ akini 03/31/08 - modified 232 to remove ASM reco,
/ add 5159-5167 for detailed io component activity
/ rdongmin 11/25/07 - add message 01314 - plan diff service
/ molagapp 01/11/08 - bug 5928104 - truncate 3601
/ rcolle 11/07/07 - add messages for WRC metrics alerts
/ kyagoub 06/05/07 - add message 01191
/ kyagoub 06/04/07 - rename spa
/ pbelknap 06/02/07 - add user i/o time imp rtn
/ pbelknap 05/31/07 - #6070867 - warn for missing binds
/ rdongmin 04/18/07 - add sql patch message 1072,1073,1074
/ ushaft 03/20/07 - Add 5153-5158
/ kyagoub 03/12/07 - add new message for sqltune
/ ansingh 02/16/07 - Add information to sqldiag advisor error msg
/ pbelknap 12/12/06 - add sqltune report msg for FATAL ERROR executions
/ kyagoub 11/29/06 - add messages for sqltune plan baselines support
/ pbelknap 11/28/06 - msgs for auto sql tune rationales
/ sburanaw 11/06/06 - add 5150-5151
/ ddas 10/27/06 - use official names for SQL plan baselines
/ ushaft 08/31/06 - changed typo in 615, added 685, 5137-5149
/ added periods in 1-684
/ pbelknap 10/16/06 - add generic APA hint message
/ pbelknap 10/10/06 - add candidate pruning for auto sqltune
/ pbelknap 08/30/06 - new messages for sqltune report
/ sburanaw 09/08/06 - add 5131-5136
/ kyagoub 07/31/06 - create message 1043
/ pbelknap 07/25/06 - chg sqltune ofe msgs
/ ushaft 08/22/06 add 5130
/ ansingh 08/18/06 - Add validate problem type error message
/ pbelknap 07/19/06 - change ofe default rec msg text
/ ushaft 07/31/06 - add 5091, 5119-5129
/ kyagoub 08/06/06 - add message 1177
/ kyagoub 06/07/06 - add new messages for spi adviosr
/ rdongmin 06/16/06 - add validation message for SQL Diag
/ rdongmin 05/31/06 - add message for compiler diff
/ ansingh 05/23/06 - Add SQL Diagnosis Advisor messages
/ rdongmin 05/22/06 - add SQL Diag messages
/ pbelknap 06/01/06 - test execute messages
/ pbelknap 06/01/06 - test execute messages
/ ushaft 05/09/06 - backwards compatibility bug for 10.2 vs. 10.1.
/ ushaft 04/24/06 - added 923
/ kyagoub 05/12/06 - add test_execute and explain_plan actions to sqltune
/ bpwang 05/15/06 - add streams alert messages
/ kyagoub 05/12/06 - add test_execute and explain_plan actions to sqltune
/ bpwang 05/15/06 - add streams alert messages
/ pbelknap 04/05/06 - automatic sqltune msgs
/ kyagoub 04/12/06 - add messages 00923, 00924, and 00925
/ ushaft 05/01/06 - added 5089-5090
/ ushaft 04/05/06 - added 505,506
/ bkuchibh 03/27/06 -
/ ushaft 03/21/06 - Added 11g ADDM section (5000-5999)
/ ushaft 12/08/05 - changed 445
/ pbelknap 05/16/05 - fix 1140 spelling
/ ushaft 05/12/05 - spelling in 383, 252, 407
/ kyagoub 04/24/05 - add sqltune message 01042
/ ushaft 04/21/05 - added 103,105,110,264-267
/ ushaft 03/18/05 - added 260-263
/ veeve 03/02/05 - modified 375 to have no more than 5 args
/ veeve 02/09/05 - added 399
/ adagarwa 01/27/05 - added message for sql statements with literals,
/ added sqltune reco message for sql that ran
/ in parallel
/ ushaft 01/25/05 - added 259
/ kyagoub 11/17/04 - add descrption for sqltune new parameters
/ commit_rows and local_time_limit
/ adagarwa 12/15/04 - added 501,502
/ dsampath 10/27/04 - modified 46, added 393
/ ushaft 10/19/04 - changed wording on ADDM buffer busy messages.
/ ushaft 10/07/04 - added advisor framework messages range (00900-00999)
/ weizhang 09/15/04 - added 03911
/ nmukherj 08/31/04 -
/ ushaft 08/05/04 - added 448, removed 393, 412, 413, add 407
/ veeve 07/22/04 - added 395-397
/ nmukherj 08/13/04 - changed 3509
/ ushaft 07/13/04 - added 447
/ veeve 06/23/04 - added 385-387
/ ushaft 06/14/04 - added 405, 438-446
/ smuthuli 06/14/04 - Change message for chained rows
/ kneel 06/08/04 - adding Automatic Storage Management HA alerts
/ kneel 06/03/04 - removing object name from HA messages
/ kneel 06/02/04 - adding more HA alert types
/ nikeda 05/28/04 - grabtrans 'nikeda_oci_events_copy'
/ veeve 06/02/04 - added 384
/ kneel 05/22/04 - adding HA alerts
/ ushaft 05/07/04 - added 427-437, deleted 407,408
/ veeve 05/21/04 - added 370 to 383
/ jciminsk 04/28/04 - merge from RDBMS_MAIN_SOLARIS_040426
/ kneel 01/09/04 - add range for dbms director
/ nmukherj 04/05/04 - added 3509
/ ushaft 04/05/04 - changed 102,
/ deleted 103, 110, 114, 116, 117, 122, 123
/ deleted 16, 22, 24, 100, 230
/ added 248-258
/ ushaft 02/19/04 - added 418-426
/ veeve 02/04/04 - modified 349
/ veeve 01/14/04 - modified 12, 76, added 98, 300, 349
/ smuthuli 05/12/04 - auto space advisor
/ veeve 11/19/03 - added 326
/ nmukherj 11/12/03 - added message 03907 in refrence to bug3175681
/ wyang 11/10/03 - undo advisor change bytes to MB
/ kyagoub 10/31/03 - spell check of messages #01032, 01114, 01120, 01128,
/ and 01130
/ nmukherj 10/28/03 -
/ veeve 10/14/03 - added 247
/ veeve 10/09/03 - added 368, 369, 321
/ veeve 09/30/03 - added 334, 335, 311
/ ushaft 09/26/03 - added 246
/ ushaft 09/22/03 - added 245
/ ushaft 09/19/03 - added 242-244
/ wyang 10/15/03 - fix spelling
/ wyang 10/02/03 - bug 3171144
/ veeve 08/26/03 - added 241
/ molagapp 08/25/03 - add more actions for 3601
/ veeve 08/07/03 - added quotes around SQL_ID
/ veeve 08/04/03 - add object_type to the messages
/ veeve 07/28/03 - added 307,309
/ kyagoub 07/30/03 - correct sqlprofile messages
/ ushaft 07/24/03 - changed instance time to db time
/ ushaft 07/16/03 - changed database to instance where appropriate
/ kdias 07/16/03 - change db time
/ ushaft 07/02/03 - added 239
/ changed 211-213, 224, 236, 237
/ kyagoub 06/22/03 - SQL profile: fix sqltune report
/ smuthuli 06/26/03 - change HDM to ADDM
/ kdias 06/27/03 -
/ ushaft 06/26/03 - changed 76
/ veeve 06/20/03 - added 97
/ ushaft 06/20/03 - changed 79 (K to bytes)
/ veeve 06/11/03 - added 95, bitmapped -> ASSM
/ ushaft 06/09/03 - added 238
/ kdias 06/05/03 - msg changes
/ kdias 05/27/03 - cleanup
/ ushaft 05/19/03 - changed 319, 60, 85 added 404
/ remove 99, 311, 326
/ ushaft 05/12/03 - added 219, 230
/ kdias 05/14/03 - add sequence msgs
/ smuthuli 05/27/03 - change alert messages
/ smuthuli 06/02/03 - fix recommendations
/ nwhyte 05/28/03 - More variations in recommendations from segment
/ shrink advisor aka. object growth trend advisor
/ molagapp 05/05/03 - change 3601
/ bdagevil 05/25/03 - add new message to change the old firs_rows mode to new one
/ kdias 05/09/03 - incorporate feedback from doc
/ ushaft 05/06/03 - PGA msgs 223,210,234,235,204
/ veeve 05/02/03 - added more cluster buffer busy msgs
/ kdias 04/25/03 - rac msgs
/ ushaft 04/24/03 - fixed syntax error for msg 123
/ veeve 04/23/03 - modifed hard parse msgs 320-338
/ ushaft 04/23/03 - wait class names in messgaes 29-30,32-45,343-344
/ PGA msgs 223,210,234,235
/ mttr msgs 211-213,224,236,237 (and deleted 238)
/ cursor aging msgs 336,330,406,407
/ removed CAUSE from all msgs in range 000-999
/ veeve 04/22/03 - added msgs 359 to 367
/ ushaft 04/09/03 - changed 201 and 217 to refer to User I/O
/ changed 221, 207, 232, 206 (IO capacity)
/ app IO -- 410-414, deleted 204
/ buffer cache -- 222,233,408,208,209,415,416
/ UndoW -- 417,225,401,402,403
/ Checkpoint rules -- 214-216 and 226-228
/ changed 229,202,203,218,58,78,79,69 (log IO)
/ deleted 219,230
/ veeve 04/07/03 - modified few msgs, added 354 to 358
/ veeve 04/04/03 - got rid of unused messages
/ veeve 04/01/03 - added schema name and object id in all msgs with obj
/ veeve 03/31/03 - added msgs 350 to 353
/ ushaft 03/31/03 - modified msgs for log file sync (58, 69, 78, 79)
/ modified msgs for pipes (23, 25, 26, 28)
/ ushaft 03/27/03 - modified wait class messages
/ ushaft 03/25/03 - added msg 408 (increase SGA)
/ modified msg 235, adding an argument.
/ ushaft 03/18/03 - fixed typo in message 30
/ veeve 03/14/03 - modify 338 to include cursor invalidation
/ kyagoub 05/10/03 - remove messages 11(57,58,59)
/ kyagoub 04/17/03 - add sqltune message range 1147-1154
/ kyagoub 04/11/03 - remove message code 1124
/ kyagoub 03/30/03 - add more sqltune messages
/ bdagevil 04/28/03 - merge new file
/ kyagoub 03/09/03 - remove 1141 code
/ bdagevil 03/06/03 - add message for SQL profile/outline info finding
/ jxchen 02/20/03 - Add message for tablespace threshold notification
/ kyagoub 02/21/03 - correct messages 03900-03903
/ ushaft 02/18/03 - change HDM msgs with SQL to have only signature
/ nwhyte 02/10/03 - Add messages for Object Space Advisors
/ jxchen 02/14/03 - Add threshold notification alert message
/ wyang 02/23/03 - undo advisor
/ veeve 01/25/03 - added time-model finding/recommendations
/ veeve 01/17/03 - added args to 233,234,236
/ bdagevil 02/05/03 -
/ kyagoub 01/31/03 - add parameter to SQL profile messages
/ kyagoub 01/25/03 - add message for index retain recommnedation
/ kyagoub 01/09/03 - add more messages for plan analyze
/ mzait 01/08/03 - add optimizer estimate message
/ bdagevil 01/03/03 - add messages for stat findings and actions
/ kyagoub 12/30/02 - add plan analyze messages
/ bdagevil 12/29/02 - add messages for attr IGNORE_OPTIMIZER_EMBEDDED_HINTS
/ bdagevil 12/29/02 - add messages for attr IGNORE_OPTIMIZER_EMBEDDED_HINTS
/ bdagevil 11/10/02 - add auto-tune messages
/ molagapp 01/22/03 - add 3600, 3601
/ jywang 01/14/03 - Change argument datatype for threshold-based alerts
/ shigupta 01/13/03 - add more HDM messages
/ veeve 01/07/03 - add time-model rule messages
/ wyang 01/01/03 - undo advisor finding and rationale message
/ veeve 12/31/02 - add hdm messages
/ wyang 12/26/02 - undo advisor recommendation message
/ jxchen 12/17/02 - Add messages for threshold-based alerts
/ smuthuli 12/02/02 - tablespace alerts
/ wyang 11/26/02 - long query alert and operation suspended alert
/ jxchen 11/11/02 - Add arguments for test message
/ kdias 09/18/02 - kdias_add_smg_file
/ kdias 09/09/02 - creation
/
/
/ 00000, 00000, "Test [%s] [%s] [%s] [%s] [%s] \n"
/
/
/ =============================================
/ messages for ADDM (10g) [00001-00899]
/ =============================================
/
00001, 00000, "Consider adding more CPUs to the host or adding instances serving the database on other hosts."
/
00002, 00000, "CPU was not a bottleneck for the instance."
/
00003, 00000, "Run SQL Tuning Advisor on the SQL statement with SQL_ID \"%s\"."
/
00004, 00000, "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."
/
00005, 00000, "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."
/
00006, 00000, "Read and write contention on database blocks was consuming significant database time. However, no single object was the predominant cause for this contention."
/
00007, 00000, "Estimated reduction in database time in microseconds."
/
00008, 00000, "Investigate application logic to find the cause of high concurrent read and write activity to the data present in this block."
/
00009, 00000, "Waits on \"buffer busy\" events were not consuming significant database time."
/
00010, 00000, "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."
/
00011, 00000, "Read and write contention on database blocks was consuming significant database time."
/
00012, 00000, "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."
/
00013, 00000, "Consider hash partitioning the %s \"%s.%s\" with object ID %s in a manner that will evenly distribute concurrent DML across multiple partitions."
/
00014, 00000, "Consider rebuilding the %s \"%s.%s\" with object ID %s using a higher value for PCTFREE."
/
00015, 00000, "The UPDATE statement with SQL_ID \"%s\" was significantly affected by \"buffer busy\" waits."
/
00016, 00000, "The INSERT statement with SQL_ID \"%s\" was significantly affected by \"global cache buffer busy\"."
/
00017, 00000, "The instance spent significant time on CPU. However, there were no predominant SQL statements responsible for the CPU load."
/
00018, 00000, "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."
/
00019, 00000, "Consider partitioning the %s \"%s.%s\" with object ID %s in a manner that will evenly distribute concurrent DML across multiple partitions."
/
00020, 00000, "Contention on buffer cache latches was not consuming significant database time."
/
00021, 00000, "Consider using array interface for the INSERT statement with SQL_ID \"%s\"."
/
00022, 00000, "The UPDATE statement with SQL_ID \"%s\" was significantly affected by \"global cache buffer busy\"."
/
00023, 00000, "Waits in DBMS_PIPE.PUT calls were not consuming significant database time."
/
00024, 00000, "The DELETE statement with SQL_ID \"%s\" was significantly affected by \"global cache buffer busy\"."
/
00025, 00000, "Consider adding more pipe read processes or speeding-up the readers."
/
00026, 00000, "Consider increasing the size of pipes created using the DBMS_PIPE package."
/
00027, 00000, "Trace the cause of object contention due to SELECT statements in the application using the information provided."
/
00028, 00000, "Waits in DBMS_PIPE.PUT calls were consuming significant database time."
/
00029, 00000, "Wait class \"Concurrency\" was not consuming significant database time."
/
00030, 00000, "Wait class \"Concurrency\" was consuming significant database time."
/
00031, 00000, "Wait event \"%s\" in wait class \"%s\" was consuming significant database time."
/
00032, 00000, "Wait class \"Administrative\" was not consuming significant database time."
/
00033, 00000, "Wait class \"Application\" was not consuming significant database time."
/
00034, 00000, "Wait class \"Cluster\" was not consuming significant database time."
/
00035, 00000, "Wait class \"Commit\" was not consuming significant database time."
/
00036, 00000, "Wait class \"Configuration\" was not consuming significant database time."
/
00037, 00000, "Wait class \"Network\" was not consuming significant database time."
/
00038, 00000, "Wait class \"Scheduler\" was not consuming significant database time."
/
00039, 00000, "Wait class \"Application\" was consuming significant database time."
/
00040, 00000, "Wait class \"Administrative\" was consuming significant database time."
/
00041, 00000, "Wait class \"Cluster\" was consuming significant database time."
/
00042, 00000, "Wait class \"Commit\" was consuming significant database time."
/
00043, 00000, "Wait class \"Configuration\" was consuming significant database time."
/
00044, 00000, "Wait class \"Network\" was consuming significant database time."
/
00045, 00000, "Wait class \"Scheduler\" was consuming significant database time."
/
00046, 00000, "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."
/
00047, 00000, "There was significant read and write contention on %s \"%s.%s\" with object ID %s in the cluster."
/
00048, 00000, "The SQL statement with SQL_ID \"%s\" was found waiting for a lock when using \"DBMS_LOCK\"."
/
00049, 00000, "The SQL statement with SQL_ID \"%s\" was blocked on row locks."
/
00050, 00000, "The %s \"%s.%s\" with object ID \"%s\" was locked for a significant time."
/
00051, 00000, "Waits for locks obtained by using the \"DBMS_LOCK\" package were consuming significant database time."
/
00052, 00000, "Sequence cache misses were consuming significant database time."
/
00053, 00000, "Contention on table lock waits was consuming significant database time."
/
00054, 00000, "Consider adding more archiver processes by setting the value of parameter \"log_archive_max_processes\"."
/
00055, 00000, "Transactions wait for ITL enqueue when the limit has been reached on the number of transactions concurrently modifying the same database block."
/
00056, 00000, "Verify whether incremental shipping was used for standby databases."
/
00057, 00000, "Tablespace %s was found in backup mode. Verify that it was appropriate."
/
00058, 00000, "Investigate application logic for possible reduction in the number of COMMIT operations by increasing the size of transactions."
/
00059, 00000, "Consider increasing the number of database writers (DBWR) by setting the parameter \"db_writer_processes\"."
/
00060, 00000, "Increase the size of the log files to %s M to hold at least %s minutes of redo information."
/
00061, 00000, "DML to tablespaces in hot backup mode causes generation of additional redo."
/
00062, 00000, "Read and write contention on database blocks was consuming significant database time in the cluster."
/
00063, 00000, "Waits for free buffers were not consuming significant database time."
/
00064, 00000, "High watermark (HW) enqueue waits were not consuming significant database time."
/
00065, 00000, "ITL enqueue waits were not consuming significant database time."
/
00066, 00000, "Waits for archiver processes were not consuming significant database time."
/
00067, 00000, "Log file switch operations were not consuming significant database time while waiting for checkpoint completion."
/
00068, 00000, "Log buffer space waits were not consuming significant database time."
/
00069, 00000, "Waits on event \"log file sync\" while performing COMMIT and ROLLBACK operations were not consuming significant database time."
/
00070, 00000, "Row lock waits were not consuming significant database time."
/
00071, 00000, "Space Transaction (ST) enqueue waits were not consuming significant database time."
/
00072, 00000, "Table lock waits were not consuming significant database time."
/
00073, 00000, "Locks obtained by using the \"DBMS_LOCK\" package were not consuming significant database time."
/
00074, 00000, "The SQL statement with SQL_ID \"%s\" was found waiting for the high watermark (HW) of %s \"%s.%s\" with object ID %s."
/
00075, 00000, "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."
/
00076, 00000, "Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespace for the tablespace \"%s\"."
/
00077, 00000, "SQL statements were found waiting for row lock waits."
/
00078, 00000, "Waits on event \"log file sync\" while performing COMMIT and ROLLBACK operations were consuming significant database time."
/
00079, 00000, "The application was performing %s transactions per minute with an average redo size of %s bytes per transaction."
/
00080, 00000, "Database writers (DBWR) were unable to keep up with the demand for free buffers."
/
00081, 00000, "Sequence cache misses were not consuming significant database time."
/
00082, 00000, "Archiver processes were unable to keep up with redo generation."
/
00083, 00000, "DML to tablespaces in hot backup mode causes generation of additional redo, thereby increasing the work of archiver processes."
/
00084, 00000, "Log file switch operations were consuming significant database time while waiting for checkpoint completion."
/
00085, 00000, "Increase the size of the redo log buffer by setting the value of parameter \"log_buffer\" to %s M."
/
00086, 00000, "Contention on the high watermark (HW) enqueue was consuming significant database time."
/
00087, 00000, "Contention on Space Transaction (ST) enqueue waits was consuming significant database time."
/
00088, 00000, "Waits for ITL enqueue were consuming significant database time."
/
00089, 00000, "The INSERT statement with SQL_ID \"%s\" was significantly affected by \"buffer busy\" waits."
/
00090, 00000, "Host CPU consumption was %s\%."
/
00091, 00000, "Waits for free buffers were consuming significant database time."
/
00092, 00000, "The DELETE statement with SQL_ID \"%s\" was significantly affected by \"buffer busy\" waits."
/
00093, 00000, "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."
/
00094, 00000, "Contention on buffer cache latches was consuming significant database time."
/
00095, 00000, "The database object with object ID \"%s\" was locked for a significant time."
/
00096, 00000, "Session connect and disconnect calls were consuming significant database time."
/
00097, 00000, "Use bigger fetch arrays while fetching results from the SELECT statement with SQL_ID \"%s\"."
/
00098, 00000, "ORACLE strongly recommends not storing any application or temporary data in the SYSTEM tablespace. Consider moving such data to a different tablespace."
/
00099, 00000, "The SELECT statement with SQL_ID \"%s\" was significantly affected by \"buffer busy\" waits."
/
00100, 00000, "The SELECT statement with SQL_ID \"%s\" was significantly affected by \"global cache buffer busy\"."
/
00101, 00000, "Database time in microseconds."
/
00102, 00000, "Inter-instance messaging was consuming significant database time on this instance."
/
00103, 00000, "Streams enqueue operations were blocked on flow control waits due to slow subscribers and consumed significant database time."
/
00104, 00000, "Inter-instance messaging was not consuming significant database time on this instance."
/
00105, 00000, "Streams enqueue operations were not blocked on flow control waits due to slow subscribers."
/
00106, 00000, "Investigate application to reduce inter-instance messaging for segment %s.%s with SEGMENT_ID %s."
/
00107, 00000, "Investigate cause of high network interconnect latency between database instances. Oracle's recommended solution is to use a high speed dedicated network."
/
00108, 00000, "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."
/
00109, 00000, "Verify that the set of services used by the application to connect to the database are optimally distributed if response time is critical."
/
00110, 00000, "Investigate slow subscribers on %s \"%s.%s\"."
/
00111, 00000, "SQL statements responsible for significant inter-instance messaging were found."
/
00112, 00000, "Higher than expected latency of the cluster interconnect was responsible for significant database time on this instance."
/
00113, 00000, "Global Cache Service Processes (LMSn) in other instances were not processing requests fast enough."
/
00114, 00000, "Contention on data by other RAC instances was consuming significant database time on this instance."
/
00116, 00000, "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."
/
00117, 00000, "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."
/
00122, 00000, "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."
/
00123, 00000, "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."
/
00201, 00000, "Wait class \"User I/O\" was consuming significant database time."
/
00202, 00000, "Investigate the possibility of improving the performance of I/O to the online redo log files."
/
00203, 00000, "The average size of writes to the online redo log files was %s K and the average time per write was %s milliseconds."
/
00204, 00000, "The 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."
/
00205, 00000, "Individual SQL statements responsible for significant user I/O wait were found."
/
00206, 00000, "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."
/
00207, 00000, "The throughput of the I/O subsystem was significantly lower than expected."
/
00208, 00000, "The buffer cache was undersized causing significant additional read I/O."
/
00209, 00000, "Buffer caches for blocks of non-default size were undersized, causing significant additional read I/O."
/
00210, 00000, "The PGA was inadequately sized, causing additional I/O to temporary tablespaces to consume significant database time."
/
00211, 00000, "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."
/
00212, 00000, "Buffer cache writes due to low MTTR setting were consuming significant database time."
/
00213, 00000, "Buffer cache writes due to small log files were consuming significant database time."
/
00214, 00000, "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."
/
00215, 00000, "Buffer cache writes due to DROP and TRUNCATE operations had a significant impact on the throughput of the I/O subsystem."
/
00216, 00000, "Buffer cache writes due to ALTER TABLESPACE operations had a significant impact on the throughput of the I/O subsystem."
/
00217, 00000, "Wait class \"User I/O\" was not consuming significant database time."
/
00218, 00000, "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."
/
00219, 00000, "The SQL statement with SQL_ID \"%s\" spent significant time on \"buffer busy\" waits for the hot block."
/
00220, 00000, "No single SQL or database statement was responsible for significant I/O wait."
/
00221, 00000, "The throughput of the I/O subsystem was not significantly lower than expected."
/
00222, 00000, "The buffer cache was not undersized."
/
00223, 00000, "Waits for I/O to temporary tablespaces were not consuming significant database time."
/
00224, 00000, "Buffer cache writes due to log file size and parameter settings were not consuming significant database I/O."
/
00225, 00000, "Undo I/O had no significant impact on the throughput of the I/O subsystem."
/
00226, 00000, "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."
/
00227, 00000, "Buffer cache writes due to DROP and TRUNCATE operations had no significant impact on the throughput of the I/O subsystem."
/
00228, 00000, "Buffer cache writes due to ALTER TABLESPACE operations had no significant impact on the throughput of the I/O subsystem."
/
00229, 00000, "Reducing the size of redo generated by the application may reduce the wait time on \"log file sync\" events."
/
00230, 00000, "The SQL statement with SQL_ID \"%s\" consumed significant database time in \"global cache buffer busy\" wait for the hot block."
/
00231, 00000, "Run \"Segment Advisor\" on %s \"%s.%s\" with object ID %s."
/
00232, 00000, "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."
/
00233, 00000, "Increase the buffer cache size by setting the value of parameter \"db_cache_size\" to %s M."
/
00234, 00000, "Increase the size of the PGA by setting the value of parameter \"pga_aggregate_target\" to %s M."
/
00235, 00000, "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."
/
00236, 00000, "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."
/
00237, 00000, "Consider increasing the MTTR setting by increasing the value of parameter \"fast_start_mttr_target\"."
/
00238, 00000, "Oracle's recommended solution is to use Auto Undo Management for reducing undo contention."
/
00239, 00000, "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."
/
00240, 00000, "There was no significant database activity to run the ADDM."
/
00241, 00000, "Trace the cause of contention on %s \"%s.%s\" with object ID %s in the application."
/
00242, 00000, "Investigate application logic involving I/O on database object with ID %s."
/
00243, 00000, "Contention on index block splits was consuming significant database time."
/
00244, 00000, "Contention on index block splits was not consuming significant database time."
/
00245, 00000, "Contention on index block splits was consuming significant database time. However, no single index was the predominant cause for this contention."
/
00246, 00000, "The SQL statement with SQL_ID \"%s\" spent significant time waiting for User I/O on the hot object."
/
00247, 00000, "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."
/
00248, 00000, "Cluster multi-block requests were consuming significant database time."
/
00249, 00000, "Run SQL Tuning Advisor on the SQL statement with SQL_ID \"%s\". Look for an alternative plan that does not use object scans."
/
00250, 00000, "Cluster communications that were retried due to lost blocks did not consume significant database time."
/
00251, 00000, "Cluster communications that were retried due to lost blocks consumed significant database time."
/
00252, 00000, "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."
/
00253, 00000, "The instance is connected to the network using device \"%s\" with IP address \"%s\"."
/
00254, 00000, "The instance was consuming %s kilo bits per second of interconnect bandwidth."
/
00255, 00000, "The network latency of the cluster interconnect was within acceptable limits of %s milliseconds."
/
00256, 00000, "Global Cache Service Processes (LMSn) in other instances were performing within acceptable limits of %s milliseconds."
/
00257, 00000, "Read and write contention on database blocks was not consuming significant database time in the cluster."
/
00258, 00000, "Investigate the SQL statement with SQL_ID \"%s\" for possible performance improvements. Look for an alternative plan that does not use object scans."
/
00259, 00000, "The database's maintenance windows were active during %s%% of the analysis period."
/
00260, 00000, "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\"."
/
00261, 00000, "Service \"%s\" and Module \"%s\" was responsible for %s%% of this recommendation's benefit."
/
00262, 00000, "Session with ID \"%s\", User ID \"%s\", Program \"%s\" and Module \"%s\" was responsible for %s%% of this recommendation's benefit."
/
00263, 00000, "Check application logic for latch contention."
/
00264, 00000, "Sessions with Service \"%s\" and Module \"%s\" were the blocking sessions responsible for %s%% of this recommendation's benefit."
/
00265, 00000, "Session with ID \"%s\", User ID \"%s\", Program \"%s\" and Module \"%s\" was the blocking session responsible for %s%% of this recommendation's benefit."
/
00266, 00000, "Investigate the cause for latch contention using the given blocking sessions or modules."
/
00267, 00000, "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."
/
00300, 00000, "Investigate the cause for high \"%s\" waits. Refer to Oracle's \"Database Reference\" for the description of this wait event."
/
00301, 00000, "Hard parsing of SQL statements was consuming significant database time."
/
00302, 00000, "Soft parsing of SQL statements was consuming significant database time."
/
00303, 00000, "SQL statements consuming significant database time were found."
/
00304, 00000, "PL/SQL execution consumed significant database time."
/
00305, 00000, "PL/SQL compilation consumed significant database time."
/
00306, 00000, "JAVA execution consumed significant database time."
/
00307, 00000, "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."
/
00308, 00000, "Session connect and disconnect calls were not consuming significant database time."
/
00309, 00000, "The SQL statement with SQL_ID \"%s\" was found waiting for \"%s\" wait event."
/
00310, 00000, "Parsing of SQL statements was not consuming significant database time."
/
00311, 00000, "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."
/
00312, 00000, "Hard parsing of SQL statements was not consuming significant database time."
/
00313, 00000, "Soft parsing of SQL statements was not consuming significant database time."
/
00314, 00000, "No single SQL statement consuming significant database time was found."
/
00315, 00000, "PL/SQL execution did not consume significant database time."
/
00316, 00000, "PL/SQL compilation did not consume significant database time."
/
00317, 00000, "JAVA execution did not consume significant database time."
/
00318, 00000, "Time spent on the CPU by the instance was responsible for a substantial part of database time."
/
00319, 00000, "Waits for redo log buffer space were consuming significant database time."
/
00320, 00000, "Look for top reason for cursor environment mismatch in V$SQL_SHARED_CURSOR."
/
00321, 00000, "Parse errors due to inadequately sized shared pool were not consuming significant database time."
/
00322, 00000, "Investigate appropriateness of DDL operations."
/
00323, 00000, "Investigate application logic to eliminate parse errors."
/
00324, 00000, "Investigate application logic for possible use of bind variables instead of literals."
/
00325, 00000, "Investigate application logic to keep open the frequently used cursors. Note that cursors are closed by both cursor close calls and session disconnects."
/
00326, 00000, "CPU runqueue statistics are not available from the host's OS. This disables ADDM's ability to estimate the impact of this finding."
/
00327, 00000, "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."
/
00328, 00000, "Common causes of environment mismatch are session NLS settings, SQL trace settings and optimizer parameters."
/
00329, 00000, "Cursors were getting invalidated due to DDL operations. This resulted in additional hard parses which were consuming significant database time."
/
00330, 00000, "Hard parses due to an inadequately sized shared pool were consuming significant database time."
/
00331, 00000, "Hard parsing SQL statements that encountered parse errors was consuming significant database time."
/
00332, 00000, "SQL statements were not shared due to the usage of literals. This resulted in additional hard parses which were consuming significant database time."
/
00333, 00000, "Hard parses due to cursor environment mismatch were not consuming significant database time."
/
00334, 00000, "Investigate the cause for high \"%s\" waits in Module \"%s\"."
/
00335, 00000, "Investigate the cause for high \"%s\" waits in Service \"%s\"."
/
00336, 00000, "Hard parsing due to cursors getting aged out of shared pool was not consuming significant database time."
/
00337, 00000, "Hard parsing SQL statements that encountered parse errors was not consuming significant database time."
/
00338, 00000, "Hard parses due to literal usage and cursor invalidation were not consuming significant database time."
/
00339, 00000, "Investigate application logic for possible reduction of connect and disconnect calls. For example, you might use a connection pool scheme in the middle tier."
/
00340, 00000, "Contention for latches related to the shared pool was not consuming significant database time."
/
00341, 00000, "Contention for latches related to the shared pool was consuming significant database time."
/
00342, 00000, "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."
/
00343, 00000, "Wait class \"Other\" was consuming significant database time."
/
00344, 00000, "Wait class \"Other\" was not consuming significant database time."
/
00345, 00000, "The latch \"%s\" with latch ID %s was one of the top latches contributing to high \"latch free\" waits."
/
00346, 00000, "Database latches in the \"Other\" wait class were not consuming significant database time."
/
00347, 00000, "Database latches in the \"Other\" wait class were consuming significant database time."
/
00348, 00000, "Investigate the SQL statement with SQL_ID \"%s\" for possible performance improvements."
/
00349, 00000, "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."
/
00350, 00000, "Waits for \"%s\" amounted to %s\% of database time."
/
00351, 00000, "Waits for lock with identifier %s were consuming significant database time."
/
00352, 00000, "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."
/
00353, 00000, "Investigate application logic involving DDL and DML on provided blocked objects."
/
00354, 00000, "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."
/
00355, 00000, "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."
/
00356, 00000, "A temporary solution may be achieved by increasing the number of free lists in segment \"%s.%s\"."
/
00357, 00000, "A temporary solution may be achieved by increasing the number of free list groups in segment \"%s.%s\"."
/
00358, 00000, "There was significant read and write contention on %s \"%s.%s\" with object ID %s."
/
00359, 00000, "Consider increasing INITRANS for the %s \"%s.%s\" with object ID %s without rebuilding it."
/
00360, 00000, "Consider increasing PCTFREE for the %s \"%s.%s\" with object ID %s."
/
00361, 00000, "Consider rebuilding the %s \"%s.%s\" with object id %s using a higher value for INITRANS."
/
00362, 00000, "Investigate the I/O subsystem's write performance."
/
00363, 00000, "Investigate application logic for possible use of direct path inserts as an alternative for multiple INSERT operations."
/
00364, 00000, "This problem can be caused by use of hot backup mode on tablespaces."
/
00365, 00000, "Consider increasing the maximum number of open cursors a session can have by increasing the value of parameter \"open_cursors\"."
/
00366, 00000, "Consider increasing the session cursor cache size by increasing the value of parameter \"session_cached_cursors\"."
/
00367, 00000, "Investigate the appropriateness of PL/SQL compilation. PL/SQL compilation can be caused by DDL on dependent objects."
/
00368, 00000, "Investigate the cause for Module \"%s\" spending significant database time."
/
00369, 00000, "Investigate the cause for Service \"%s\" spending significant database time."
/
00370, 00000, "Contention for space in temporary tablespace by multiple instances was consuming significant database time."
/
00371, 00000, "Consider increasing the size of the temporary tablespace \"%s\"."
/
00372, 00000, "Consider increasing the size of the temporary tablespaces that are experiencing significant inter-instance contention."
/
00373, 00000, "Investigate the cause for high \"%s\" waits with P1 (\"%s\") value \"%s\"."
/
00374, 00000, "Investigate the cause for high \"%s\" waits with P1 (\"%s\") value \"%s\" and P2 (\"%s\") value \"%s\"."
/
00375, 00000, "Investigate the cause for high \"%s\" waits with P1,P2,P3 (\"%s\") values \"%s\", \"%s\" and \"%s\" respectively."
/
00376, 00000, "Excessive number of bind calls to cursors whose bind variables were already bound was consuming significant database time."
/
00377, 00000, "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."
/
00378, 00000, "Significant virtual memory paging was detected on the host operating system."
/
00379, 00000, "The 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\"."
/
00380, 00000, "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."
/
00381, 00000, "Consider enabling Automatic Shared Memory Management by setting the parameter \"sga_target\" to control the amount of SGA consumed by this instance."
/
00382, 00000, "Consider enabling Automatic PGA Memory Management by setting the parameter \"pga_aggregate_target\" to control the amount of PGA consumed by this instance."
/
00383, 00000, "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."
/
00384, 00000, "Investigate the cause for the \"%s\" processes consuming %s%% of the host CPU."
/
00385, 00000, "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."
/
00386, 00000, "Also consider using Oracle Database Resource Manager to prioritize the workload from various consumer groups."
/
00387, 00000, "SQL statement with SQL_ID \"%s\" was executed %s times and processed %s rows per execution."
/
00388, 00000, "SQL statement with SQL_ID \"%s\" was executed %s times and had an average elapsed time of %s seconds."
/
00389, 00000, "Average time spent in PL/SQL execution was %s seconds."
/
00390, 00000, "Average time spent in Java execution was %s seconds."
/
00391, 00000, "Average time spent in Cluster wait events per execution was %s seconds."
/
00392, 00000, "Average CPU used per execution was %s seconds."
/
00393, 00000, "Service \"%s\" and Module \"%s\" was causing %s% of the row lock contention on this object."
/
00394, 00000, "Average time spent in User I/O wait events per execution was %s seconds."
/
00395, 00000, "Database sessions were found waiting for Oracle Resource Manager's active session slots."
/
00396, 00000, "Sessions were found waiting for active session slots. Consider increasing the active session limit for these Oracle Resource Manager consumer groups."
/
00397, 00000, "Session CPU consumption was throttled by the Oracle Resource Manager. Consider revising the resource plan that was active during the analysis period."
/
00398, 00000, "Alternatively, you may set the parameter \"cursor_sharing\" to \"force\"."
/
00399, 00000, "Parsing SQL statements were consuming significant CPU. Please refer to other findings in this task about parsing for further details."
/
00401, 00000, "Undo I/O was a significant portion (%s\%) of the total database I/O."
/
00402, 00000, "Consider lowering the value of parameter \"undo_retention\" to %s seconds."
/
00403, 00000, "The value of \"undo_retention\" was %s seconds and the longest running query lasted only %s seconds. This extra retention caused unnecessary I/O."
/
00404, 00000, "Reducing the size of redo generated by the application may reduce the wait time on \"log buffer space\" events."
/
00405, 00000, "The value of parameter \"%s\" was \"%s\" during the analysis period."
/
00406, 00000, "Increase the shared pool size by setting the value of parameter \"shared_pool_size\" to %s M."
/
00407, 00000, "The I/O usage statistics for the object are: %s full object scans, %s physical reads, %s physical writes and %s direct reads."
/
00408, 00000, "Increase SGA target size by increasing the value of parameter \"sga_target\" by %s M."
/
00409, 00000, "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\"."
/
00410, 00000, "No single SQL or database statement was responsible for a significant amount of physical I/O."
/
00411, 00000, "Individual database segments responsible for significant user I/O wait were found."
/
00412, 00000, "Individual SQL statements responsible for significant physical I/O were found."
/
00413, 00000, "Individual database segments responsible for significant physical I/O were found."
/
00414, 00000, "Investigate application logic involving I/O on %s \"%s.%s\" with object ID %s."
/
00415, 00000, "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."
/
00416, 00000, "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."
/
00417, 00000, "Undo I/O issues cannot be diagnosed because automatic undo management was turned off."
/
00418, 00000, "The impact of cursors being aged out of the shared pool cannot be determined because of changes in the shared pool size."
/
00419, 00000, "The impact of cursors being aged out of the shared pool cannot be determined because of incomplete AWR snapshots."
/
00420, 00000, "The impact of hard parses due to cursor invalidation and literal usage cannot be determined because of incomplete AWR snapshots."
/
00421, 00000, "I/O capacity issues cannot be diagnosed because of incomplete AWR snapshots."
/
00422, 00000, "ADDM cannot determine if the buffer cache was undersized because of changes in the buffer cache size."
/
00423, 00000, "ADDM cannot determine if the buffer cache was undersized because of incomplete AWR snapshots."
/
00424, 00000, "The impact of checkpoint activity due to MTTR setting cannot be determined because of incomplete AWR snapshots."
/
00425, 00000, "The impact of checkpoint activity due to parallel queries and tablespace DDL cannot be determined because of incomplete AWR snapshots."
/
00426, 00000, "The impact of undo I/O activity cannot be determined because of incomplete AWR snapshots."
/
00427, 00000, "The impact of RMAN I/O activity cannot be determined because of incomplete AWR snapshots."
/
00428, 00000, "RMAN I/O activity had no significant impact on the throughput of the I/O subsystem."
/
00429, 00000, "RMAN I/O activity had a significant impact on the throughput of the I/O subsystem."
/
00430, 00000, "Consider slowing down RMAN activity, or scheduling RMAN jobs when user activity is lower."
/
00431, 00000, "Consider not using the compression option for RMAN jobs. Alternatively, consider slowing down RMAN activity, or scheduling RMAN jobs when user activity is lower."
/
00432, 00000, "The SGA was adequately sized."
/
00433, 00000, "The SGA was inadequately sized, causing additional I/O or hard parses."
/
00434, 00000, "The optimal SGA size could not be determined because the value of \"sga_target\" changed during the analysis period."
/
00435, 00000, "The optimal SGA size could not be determined because of incomplete AWR snapshots."
/
00436, 00000, "Increase the size of the SGA by setting the parameter \"sga_target\" to %s M."
/
00437, 00000, "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."
/
00438, 00000, "The impact of checkpoint activity due to drop and truncate operations cannot be determined because of incomplete AWR snapshots."
/
00439, 00000, "The streams pool was inadequately sized, causing additional I/O."
/
00440, 00000, "The streams pool was adequately sized."
/
00441, 00000, "The optimal streams pool size could not be determined because of incomplete AWR snapshots."
/
00442, 00000, "Increase the size of the streams pool by setting the parameter \"streams_pool_size\" to %s M."
/
00443, 00000, "The optimal streams pool size could not be determined because the streams pool was resized."
/
00444, 00000, "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."
/
00445, 00000, "Waits on event \"log file sync\" were the cause of significant database wait on \"gc buffer busy release\" when releasing a data block."
/
00446, 00000, "Waits on event \"log file sync\" in this instance can cause global cache contention on remote instances."
/
00447, 00000, "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."
/
00448, 00000, "The average response time for single block reads for this file was %s milliseconds."
/
00450, 00000, "SQL statements with PLAN_HASH_VALUE %s were found to be using literals. Look in V$SQL for examples of such SQL statements."
/
00451, 00000, "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."
/
00452, 00000, "Consider using ORACLE's recommended solution of automatic segment space management in a locally managed tablespaces."
/
00455, 00000, "No single SQL statement was responsible for significant inter-instance messaging."
/
00456, 00000, "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."
/
00457, 00000, "The buffer cache for blocks of non-standard size %s K was undersized causing significant additional read I/O."
/
00458, 00000, "Increase the value of parameter \"sga_target\" by %s M in order to make that memory available for the shared pool."
/
00501, 00000, "Streams enqueue operations were blocked due to insufficient memory in the streams pool and consumed significant database time."
/
00502, 00000, "Streams enqueue operations were not blocked due to insufficient memory in the streams pool."
/
00503, 00000, "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\"."
/
00504, 00000, "At least one execution of the statement ran in parallel."
/
00505, 00000, "Wait class \"Queueing\" was not consuming significant database time."
/
00506, 00000, "Wait class \"Queueing\" was consuming significant database time."
/
00507, 00000, "CPU Resource Manager is enabled and database sessions were found waiting for CPU."
/
00508, 00000, "Database sessions were found waiting in Oracle Resource Manager's Parallel Statement Queue."
/
00509, 00000, "Database sessions were consuming significant PGA memory in some database instances (or PDBs)."
/
00510, 00000, "Database sessions were waiting to issue I/O requests because the PDB reached its IO rate limit (MAX_IOPS or MAX_MBPS)."
/
/ =============================================
/ messages for ADDM report [00600-00699]
/ =============================================
/
00600, 00000, "ADDM Report for Task '%s'"
/
00601, 00000, "Analysis Period"
/
00602, 00000, "AWR snapshot range from %s to %s."
/
00603, 00000, "Time period starts at %s"
/
00604, 00000, "Time period ends at %s"
/
00605, 00000, "Analysis Target"
/
00606, 00000, "Database '%s' with DB ID %s."
/
00607, 00000, "Database version %s."
/
00608, 00000, "Database version during analysis period was %s."
/
00609, 00000, "Database version when ADDM was executed was %s."
/
00610, 00000, "All recommendations generated by ADDM are valid for database version %s, the version in which ADDM was executed."
/
00611, 00000, "ADDM performed an analysis of all instances."
/
00612, 00000, "ADDM performed an analysis of instances numbered %s."
/
00613, 00000, "ADDM performed an analysis of instance %s, numbered %s and hosted at %s."
/
00614, 00000, "Analysis was requested for all instances, but ADDM only analyzed a subset of the instances."
/
00615, 00000, "Analysis was requested for all instances, but ADDM analyzed instance %s, numbered %s and hosted at %s."
/
00616, 00000, "Analysis was requested for a subset of instances, but ADDM analyzed instance %s, numbered %s and hosted at %s."
/
00617, 00000, "See the \"Additional Information\" section for more information on the requested instances."
/
00618, 00000, "Activity During the Analysis Period"
/
00619, 00000, "Total database time was %s seconds."
/
00620, 00000, "The average number of active sessions was %s."
/
00621, 00000, "ADDM analyzed %s of the requested %s instances."
/
00622, 00000, "There are no findings to report."
/
00623, 00000, "Database ID %s."
/
00624, 00000, "ADDM performed an analysis of instance number %s."
/
00625, 00000, "Additional Information"
/
00626, 00000, "Instances that were analyzed:"
/
00627, 00000, "Instances that were requested but were not analyzed:"
/
00628, 00000, "Number"
/
00629, 00000, "Name"
/
00630, 00000, "Host Name"
/
00631, 00000, "Active Sessions"
/
00632, 00000, "Percent of Activity"
/
00633, 00000, "Reason Instance was Excluded"
/
00634, 00000, "Startup or shutdown during analysis period"
/
00635, 00000, "Missing or error in snapshots"
/
00636, 00000, "Missing key statistics"
/
00637, 00000, "AWR snapshots could not be found for the instance"
/
00638, 00000, "Warnings"
/
00639, 00000, "Miscellaneous Information"
/
00640, 00000, "Task parameters with non-default setting"
/
00641, 00000, "Impact is %s active sessions, %s\% of total activity."
/
00642, 00000, "Instances that were significantly affected by this finding:"
/
00643, 00000, "Percent Impact"
/
00644, 00000, "ADDM Task Name"
/
00645, 00000, "Check the ADDM analysis of affected instances for recommendations."
/
00646, 00000, "Application Analysis"
/
00647, 00000, "Database Configuration"
/
00648, 00000, "Host Configuration"
/
00649, 00000, "SQL Tuning"
/
00650, 00000, "Segment Tuning"
/
00651, 00000, "Schema Changes"
/
00652, 00000, "Unknown Recommendation Type"
/
00653, 00000, "No recommendations are available."
/
00654, 00000, "The available recommendations have the following types:"
/
00655, 00000, "Recommendation Type"
/
00656, 00000, "Number of Recommendations"
/
00657, 00000, "Estimated benefit is %s active sessions, %s\% of total activity."
/
00658, 00000, "Action"
/
00659, 00000, "Rationale"
/
00660, 00000, "Related Object"
/
00661, 00000, "SQL statement with SQL_ID %s and PLAN_HASH %s."
/
00662, 00000, "SQL statement with SQL_ID %s."
/
00663, 00000, "Database object with ID %s."
/
00664, 00000, "Database block with object number %s, file number %s and block number %s."
/
00665, 00000, "Database file"
/
00666, 00000, "Tablespace %s with ID %s."
/
00667, 00000, "Database latch %s."
/
00668, 00000, "Database enqueue %s."
/
00669, 00000, "Database enqueue %s with ID1 %s."
/
00670, 00000, "Database enqueue %s with ID1 %s and ID2 %s."
/
00671, 00000, "Related object of type %s."
/
00672, 00000, "ATTR1 is %s."
/
00673, 00000, "ATTR2 is %s."
/
00674, 00000, "ATTR3 is %s."
/
00675, 00000, "ATTR4 is %s."
/
00676, 00000, "Recommendation %s:"
/
00677, 00000, "Finding %s:"
/
00678, 00000, "Summary of Findings"
/
00679, 00000, "Description"
/
00680, 00000, "Recommendations"
/
00681, 00000, "Findings and Recommendations"
/
00683, 00000, "Symptoms That Led to the Finding:"
/
00684, 00000, "Impact is %s active sessions, %s\% of total activity."
/
00685, 00000, "Directives that may affect this report:"
/
00686, 00000, "Examine instance ADDM"
/
/ =============================================
/ messages for Advisor Framework [00900-00999]
/ =============================================
/
00900, 00000, "Deprecated Parameter"
/
00901, 00000, "The type of analysis ADDM should perform"
/
00902, 00000, "The expected response time in milliseconds for reading one data block from a data file"
/
00903, 00000, "The amount of database time in milliseconds accumulated in the analysis period"
/
00904, 00000, "The database id for analysis"
/
00905, 00000, "The last snapshot id in the analysis period"
/
00906, 00000, "The instance number for analysis"
/
00907, 00000, "The first snapshot id in the analysis period"
/
00908, 00000, "SQL predicate to filter the SQL from the SQL Tuning Set"
/
00909, 00000, "Plan filter applicable in case there are multiple plans (plan_hash_value) associated with the same statement"
/
00910, 00000, "A first ORDER BY clause on the selected SQL"
/
00911, 00000, "A second ORDER BY clause on the selected SQL"
/
00912, 00000, "A third ORDER BY clause on the selected SQL"
/
00913, 00000, "Limit the number of SQL from the filtered and ranked SQL tuning set"
/
00914, 00000, "A percentage on the sum of a ranking measure"
/
00915, 00000, "The username for whom the SQL statement will be tuned"
/
00916, 00000, "The number of seconds between the begin time of the analysis time period and the current time"
/
00917, 00000, "The number of seconds between the end time of the analysis time period and the current time"
/
00918, 00000, "The unique task id generated by the automatically invoked advisor"
/
00919, 00000, "TRUE if the task was created automatically, FALSE if created manually"
/
00920, 00000, "TRUE if result should include findings with recommendations, FALSE otherwise"
/
00921, 00000, "The number of statements after which commit tuning results for a SQL tuning set"
/
00922, 00000, "Time limit per statement in a SQL Tuning Set"
/
00923, 00000, "SQL predicate to filter SQL from the SQL Tuning Set when resuming a tuning task"
/
00924, 00000, "Specify the default action of a task execution."
/
00925, 00000, "Tune the performance of SQL statements"
/
00926, 00000, "TRUE if SQL Profiles should be created by the task, FALSE otherwise"
/
00927, 00000, "TRUE if SQL Profiles created by the user should be replaced, FALSE otherwise"
/
00928, 00000, "Maximum number of SQL Profiles that can be created by the system in one run"
/
00929, 00000, "Maximum number of system SQL Profiles that are allowable at any one time"
/
00930, 00000, "Test execute of SQL statements"
/
00931, 00000, "Generate explain plan of SQL statements"
/
00932, 00000, "Specifies the expiration time in days for individual executions of the current task"
/
00933, 00000, "Analyze performance of SQL statements"
/
00934, 00000, "Threshold of a SQL statement impact on a workload"
/
00935, 00000, "Threshold of a change impact on a SQL statement"
/
00936, 00000, "Specify an expression of execution statistics to use in performance comparison."
/
00937, 00000, "Name of the first task execution to analyze"
/
00938, 00000, "Name of the second task execution to analyze"
/
00939, 00000, "YES if SQL statements should be test-executed to measure benefit; NO otherwise"
/
00940, 00000, "Indicated whether the advisor could use the compilation environment captured with the SQL statements"
/
00941, 00000, "FULL 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 whatsoever"
/
00942, 00000, "TRUE to require all important binds for test-execution, FALSE to install fake NULL binds in place of missing binds"
/
00943, 00000, "Evolve plans under SQL Plan Management"
/
00944, 00000, "TRUE if SQL plan baselines should be accepted by the task, FALSE otherwise"
/
00945, 00000, "Analyze statistics"
/
/ =============================================
/ messages for SQL Tuning Advisor UI[1000,1200]
/ =============================================
/ ========================================
/ messages for SQL Auto-tune UI[1000,1099]
/ more messages @ 6000 - 6199
/ ========================================
/
01000, 00000, "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."
/
01001, 00000, "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."
/
01002, 00000, "This attribute sets parameter OPTIMIZER_FEATURES_ENABLE to its default value for this statement. This enables the latest optimizer features to be used."
/
01003, 00000, "This attribute causes the optimizer to try an interesting alternative plan for this statement."
/
01005, 00000, "This attribute changes the optimizer mode from %s to %s. The optimizer mode was changed after examining the execution statistics of this statement."
/
01006, 00000, "This attribute preserves the optimizer mode in the user specified hints for the query."
/
01007, 00000, "This attribute enables the cost-based optimizer."
/
01008, 00000, "This attribute adjusts optimizer estimates."
/
01009, 00000, "This attribute enables the \"first rows\" optimizer mode."
/
01010, 00000, "This attribute disables optimizer hints."
/
01011, 00000, "Consider accepting the recommended SQL profile. It is an Exadata-aware SQL profile."
/
01012, 00000, "Consider accepting the recommended SQL profile. It is an Exadata-aware SQL profile. It is recommended to verify this profile by enabling test-execution with SQL Tuning advisor."
/
01013, 00000, "Although execution of the Exadata-aware profile plan may cause higher direct gets and physical I/Os, such a profile is only recommended if it reduces the elapsed time of the SQL."
/
01020, 00000, "Table \"%s\".\"%s\" was not analyzed."
/
01021, 00000, "Table \"%s\".\"%s\" and its indices were not analyzed."
/
01022, 00000, "Index \"%s\".\"%s\" was not analyzed."
/
01023, 00000, "Optimizer statistics for table \"%s\".\"%s\" are stale."
/
01024, 00000, "Optimizer statistics for table \"%s\".\"%s\" and its indices are stale."
/
01025, 00000, "Optimizer statistics for index \"%s\".\"%s\" are stale."
/
01026, 00000, "The optimizer requires up-to-date statistics for the table in order to select a good execution plan."
/
01027, 00000, "The optimizer requires up-to-date statistics for the table and its indices in order to select a good execution plan."
/
01028, 00000, "The optimizer requires up-to-date statistics for the index in order to select a good execution plan."
/
01029, 00000, "This attribute provides the optimizer with basic table statistics because the table statistics are missing for this table."
/
01030, 00000, "This attribute provides the optimizer with basic table statistics because the table statistics are stale for this table."
/
01031, 00000, "This attribute provides the optimizer with basic column statistics because the table statistics are missing for this table."
/
01032, 00000, "This attribute provides the optimizer with basic column statistics because the table statistics are stale for this table."
/
01033, 00000, "This attribute provides the optimizer with basic index statistics because the index statistics are missing for this index."
/
01034, 00000, "This attribute provides the optimizer with basic index statistics because the index statistics are stale for this index."
/
01035, 00000, "Consider accepting the recommended SQL profile."
/
01036, 00000, "Consider collecting optimizer statistics for this table."
/
01037, 00000, "Consider collecting optimizer statistics for this index."
/
01038, 00000, "Stored outline \"%s\" exists for this statement and was ignored during the tuning process. Consider migrating stored outlines to SQL plan baselines using the dbms_spm.migrate_stored_outline API."
/
01039, 00000, "SQL Profile \"%s\" exists for this statement and was ignored during the tuning process."
/
01040, 00000, "A potentially better execution plan was found for this statement."
/
01041, 00000, "Consider collecting optimizer statistics for this table and its indices."
/
01042, 00000, "Type of SQL statement not supported."
/
01043, 00000, "Fixed SQL plan baseline \"%s\" exists for this statement and was ignored during the tuning process."
/
01044, 00000, "An automatically-created %s is present on the system."
/
01045, 00000, "A manually-created %s is present on the system."
/
01046, 00000, "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."
/
01047, 00000, "This statement was skipped because it has already been tuned recently. See task execution \"%s\" for the most recent tuning results."
/
01048, 00000, "The %s is no longer present on the system."
/
01049, 00000, "This statement was skipped because it was targeted by user blacklist filter \"%s\"."
/
01050, 00000, "The %s was not automatically created because the verified benefit was too low."
/
01051, 00000, "The %s was not automatically created because its benefit could not be verified."
/
01052, 00000, "The %s was not automatically created because auto-creation was disabled. Set task parameter ACCEPT_SQL_PROFILES to TRUE to enable auto-creation."
/
01053, 00000, "The %s was not automatically created because the SQL has a fixed SQL plan baseline or a stored outline."
/
01054, 00000, "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."
/
01055, 00000, "The SQL profile was not automatically created because the global SQL profile limit had been reached."
/
01056, 00000, "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."
/
01057, 00000, "The %s was not automatically created because test execution was disabled. Set task parameter TEST_EXECUTE to FULL or AUTO to enable test execution."
/
01058, 00000, "The %s was not automatically created."
/
01059, 00000, "The %s's benefit could not be verified through test execution because an error occurred."
/
01060, 00000, "The %s's benefit could not be verified through test execution because the operation timed out."
/
01061, 00000, "The %s's benefit could not be verified because test execution is not supported for parallel queries."
/
01062, 00000, "The %s's benefit could not be verified because test execution is not supported for DMLs or DDLs."
/
01063, 00000, "The %s's benefit could not be verified because test execution is not supported for this statement type."
/
01064, 00000, "The %s's benefit could not be verified through test execution."
/
01065, 00000, "%s \"%s\" was created automatically for this statement."
/
01066, 00000, "SQL profile \"%s\" and SQL plan baseline \"%s\" were created automatically for this statement."
/
01067, 00000, "The task did not analyze the full set of candidate SQL because the recommendation limit was reached."
/
01068, 00000, "Consider accepting the recommended SQL profile. A SQL plan baseline corresponding to the plan with the SQL profile will also be created."
/
01069, 00000, "Consider accepting the recommended SQL plan baseline."
/
01070, 00000, "Task execution terminated with \"FATAL ERROR\" status, but SQL profile \"%s\" was implemented automatically before the error occurred."
/
01071, 00000, "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."
/
01072, 00000, "Consider accepting the recommended SQL patch."
/
01073, 00000, "Consider accepting the recommended SQL patch. A SQL plan baseline corresponding to the plan with the SQL patch will also be created."
/
01074, 00000, "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."
/
01075, 00000, "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."
/
01076, 00000, "The %s was not automatically created because it may have caused a significant i/o time degradation."
/
01077, 00000, "The statement was first executed to warm the buffer cache."
/
01078, 00000, "Statistics shown were averaged over next %s executions."
/
01079, 00000, "Statistics shown were from the second execution."
/
01080, 00000, "This attribute enables parallel execution."
/
01081, 00000, "A potentially better parallel execution plan was found for this statement."
/
01082, 00000, "Executing this query parallel with DOP %s will improve its response time %s%% over the SQL profile plan. However, this 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."
/
01083, 00000, "Consider accepting the recommended SQL profile to use parallel execution for this statement."
/
01084, 00000, "%s potentially better execution plans were found for this statement. Choose one of the following SQL profiles to implement."
/
01085, 00000, "Executing this query parallel with DOP %s will improve its response time %s%% over the original plan. However, this 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."
/
01086, 00000, "Some alternative execution plans for this statement were found by searching the system's real-time and historical performance data."
/
01087, 00000, "Creating a plan baseline for the plan with the best elapsed time will prevent the Oracle optimizer from selecting a plan with worse performance."
/
01088, 00000, "Consider creating a SQL plan baseline for the plan with the best average elapsed time."
/
01089, 00000, "The 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."
/
01090, 00000, "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. "
/
01091, 00000, "The object is missing."
/
01092, 00000, "The object can be deleted."
/
01093, 00000, "The Original Plan appears to have the best performance, based on the elapsed time per execution."
/
01094, 00000, "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."
/
01095, 00000, "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."
/
01096, 00000, "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."
/
01097, 00000, "All alternative plans other than the Original Plan could not be reproduced in the current environment."
/
01098, 00000, "This plan could not be reproduced because %s is missing."
/
01099, 00000, "This plan could not be reproduced because %s are missing."
/
01100, 00000, "This plan could not be reproduced in the current environment."
/
/ ======================================================
/ Plan analyze and index analyze messages UI[1100, 1200]
/ ======================================================
/
01101, 00000, "Consider using \"UNION ALL\" instead of \"UNION\", if duplicates are allowed or uniqueness is guaranteed."
/
01102, 00000, "\"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."
/
01103, 00000, "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."
/
01104, 00000, "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."
/
01107, 00000, "Consider removing the disconnected table or view from this statement or add a join condition which refers to it."
// *Comment: A cartesian product happens when one or more tables
// have no join conditions to any other tables in a statement.
/
01108, 00000, "A cartesian product should be avoided whenever possible because it is an expensive operation and might produce a large amount of data."
/
01109, 00000, "Consider removing the \"ORDERED\" hint."
// *Comment: A cartesian product happens when one or more tables
// have no join conditions to any other tables in a statement.
/
01110, 00000, "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."
/
01113, 00000, "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."
/
01114, 00000, "The optimizer cannot merge a view that contains a \"ROWNUM\" pseudo column."
/
01115, 00000, "The optimizer cannot merge a view that contains a set operator."
/
01116, 00000, "The optimizer cannot merge a view that contains windowing functions."
/
01117, 00000, "The optimizer cannot merge a view that contains a \"SPREADSHEET\" clause."
/
01118, 00000, "The optimizer cannot merge a view that contains nested aggregate functions."
/
01119, 00000, "The optimizer cannot merge a view that contains aggregate functions without \"GROUP BY\" clause."
/
01120, 00000, "The optimizer cannot merge a view that contains grouping functions."
/
01121, 00000, "The optimizer cannot merge a view that contains a \"GROUP BY\" clause with a \"ROLLUP\", \"CUBE\" or \"GROUPING SETS\" option."
/
01122, 00000, "The optimizer cannot merge a view that contains a \"START WITH\" clause."
/
01123, 00000, "The optimizer cannot merge a view that contains a NO_MERGE hint."
/
01124, 00000, "The optimizer cannot merge a view that contains a \"CURSOR\" expression."
/
01127, 00000, "The optimizer cannot merge a view that contains a \"WITH\" clause."
/
01128, 00000, "The optimizer cannot merge a view with a predicate containing a nested table column involved in an outer join."
/
01129, 00000, "The optimizer could not merge the complex view at line ID %s of the execution plan."
/
01130, 00000, "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."
/
01131, 00000, "The optimizer cannot merge a complex view if its parent query contains a \"START WITH\" clause."
/
01132, 00000, "The optimizer cannot merge a complex view if its parent query is a \"SELECT FOR UPDATE\"."
/
01133, 00000, "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."
/
01134, 00000, "The optimizer cannot merge a complex view if its parent query contains a reference to a \"ROWNUM\" pseudo-column."
/
01135, 00000, "The optimizer cannot merge a complex view if its parent query contains a \"GROUP BY CUBE\" clause."
/
01136, 00000, "The optimizer cannot merge a complex view if its parent query contains a \"GROUPING SETS\" clause."
/
01137, 00000, "The optimizer cannot merge a complex view if the \"SELECT\" list of its parent query contains a \"SEQUENCE\" column."
/
01138, 00000, "The optimizer cannot merge a view that contains a group outer join."
/
01139, 00000, "The optimizer cannot merge a view involved in a group outer join."
/
01140, 00000, "Consider enabling complex view merging by using the \"MERGE\" hint or by setting parameter OPTIMIZER_FEATURES_ENABLE to least 9.0.1."
/
01141, 00000, "An expensive cartesian product operation was found at line ID %s of the execution plan."
/
01142, 00000, "The optimizer could not unnest the subquery at line ID %s of the execution plan."
/
01143, 00000, "The optimizer could not merge the view at line ID %s of the execution plan."
// comment: a complex view is a view that contains a GROUP BY or a DISTINCT
// clause.
/
01144, 00000, "An expensive \"UNION\" operation was found at line ID %s of the execution plan."
/
01145, 00000, "The execution plan of this statement can be improved by creating one or more indices."
/
01146, 00000, "Consider running the Access Advisor to improve the physical schema design or creating the recommended index."
/
01147, 00000, "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\"."
/
01148, 00000, "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\"."
/
01149, 00000, "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\"."
/
01150, 00000, "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\"."
/
01151, 00000, "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."
/
01152, 00000, "Rewrite the predicate into an equivalent form to take advantage of indices. Alternatively, create a function-based index on the expression."
/
01153, 00000, "Rewrite the predicate into an equivalent form to take advantage of indices."
/
01154, 00000, "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\"."
/
01155, 00000, "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\"."
/
01156, 00000, "Creating 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."
/
01157, 00000, "Both 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."
/
01158, 00000, "The plan with the recommended indexes must be loaded as a SQL plan baseline so that the optimizer can use those indexes."
/
01159, 00000, "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."
/
01160, 00000, "A potentially beneficial index exists already but is currently marked unusable. Consider rebuilding the index so that the optimizer can use it."
/
01161, 00000, "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."
/
/ =======================================
/ SQLPIA messages start here
/ =======================================
/
01171, 00000, "The performance of this SQL has improved."
/
01172, 00000, "The performance of this SQL has regressed."
/
01173, 00000, "One of the execution plans required by the analysis is missing for this SQL statement."
/
01174, 00000, "This SQL statement returned zero rows."
/
01175, 00000, "The structure of the SQL execution plan has changed."
/
01176, 00000, "The structure of the SQL plan in execution '%s' is different than its corresponding plan which is stored in the SQL Tuning Set."
/
01177, 00000, "The structure of the SQL plan in execution '%s' is similar to its corresponding plan which is stored in the SQL Tuning Set."
/
01178, 00000, "Error in execution '%s': %s"
/
01179, 00000, "The number of returned rows in execution '%s' is different than in execution '%s'."
/
01180, 00000, "Execution plan for this SQL statement is adaptive."
/
01181, 00000, "Execution plan for this SQL statement in SPA execution '%s' is adaptive."
/
01182, 00000, "Both execution plans are adaptive for this SQL statement."
/
01190, 00000, "%s"
/
01191, 00000, "An error occurred while processing this SQL statement causing task execution to fail. The task execution was successfully resumed after the task failure."
/
01192, 00000, "The result set in execution '%s' is different than in execution '%s'."
/
/ ======================================================
/ SQL Diagnostic Advisor messages UI[1300, 1390]
/ ======================================================
/
01301, 00000, "Feature used: %s"
/
01302, 00000, "Plan for strategy %s has cost %s with plan hash value %s"
/
01303, 00000, "Feature %s was accepted because of %s"
/
01304, 00000, "Strategy execution %s failed with error code %s and error message %s"
/
01305, 00000, "Alternative plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer gets"
/
01306, 00000, "Recommended plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer gets"
/
01307, 00000, "%s CR Diff'ing: Feature %s [base %s, target %s]"
/
01308, 00000, "%s CR Diff'ing: Object base construct %s is %s in target"
/
01309, 00000, "Validation [rule: %s, status: %s]"
/
01310, 00000, "Plan for strategy %s with plan directive (hint) %s has cost %s with plan hash value %s"
/
01311, 00000, "Invalid value for problem type"
/
01312, 00000, "Invalid value for incident identifier"
/
01313, 00000, "Original plan with hash value %s has number of rows %s, check sum %s, execution time %s and %s buffer gets"
/
01314, 00000, "%s P1: %s P2: %s"
/
/ 02000-02999 RESERVED FOR TRANSACTION LAYER
/
02000, 00000, "Snapshot Too Old Error detected: SQL ID %s, Snapshot SCN %s, Recent SCN %s, Undo Tablespace %s, Current Undo Retention %s."
/
02001, 00000, "Snapshot Too Old Error detected: SQL ID %s, Snapshot SCN %s, Recent SCN %s, Rollback Segment %s."
/
02002, 00000, "Please run undo advisor."
/
02003, 00000, "Please check rollback segment usage."
/
02004, 00000, "Operation on resumable session %s session id %s suspended because of errors in tablespace %s. Error message is %s"
/
02005, 00000, "Operation on resumable session %s session id %s suspended because of errors in rollback segment %s. Error message is %s"
/
02006, 00000, "Operation on resumable session %s session id %s suspended because of errors in %s. Error message is %s"
/
02007, 00000, "Operation on resumable session %s session id %s suspended because of errors in user quota. Error message is %s"
/
02008, 00000, "Please check view dba_resumable."
/
02009, 00000, "Set initialization parameter undo_retention to %d"
/
02010, 00000, "Size undo tablespace to %d MB"
/
02011, 00000, "The longest query duration is longer than undo retention setting."
/
02012, 00000, "Some of your queries may fail due to snap shot too old errors."
/
02013, 00000, "Undo Tablespace is under pressure."
/
02014, 00000, "Some of your operations may fail due to full undo tablespace."
/
02015, 00000, "Set undo retention to longest query duration to avoid snap shot too old error."
/
02016, 00000, "Set undo tablespace size based on undo generation rate and undo retention"
/
02017, 00000, "Cannot run Undo advisor when the system is running with manual undo management."
/
02018, 00000, "The system is auto tuning undo retention."
/
02019, 00000, "There is not enough data in AWR."
/
02020, 00000, "There is no target_object."
/
02021, 00000, "Reduce Snapshot Too Old errors."
/
02022, 00000, "Avoid undo tablespace pressure"
/
02023, 00000, "Recommended undo tablespace size is based on undo generation rate and longest query duration in the system."
/
02024, 00000, "Recommended undo retention is based on longest query duration in the system."
/
02025, 00000, "Recommended undo retention is the best possible undo retention based on undo generation rate and current undo tablespace size."
/
02026, 00000, "The undo tablespace is OK."
/
02027, 00000, "Undo tablespace is OK."
/
02028, 00000, "Improve the usage of undo tablespace"
/
02029, 00000, "Undo retention is too high"
/
02030, 00000, "Undo retention is set to higher than best possible retention and undo tablespace will be under pressure"
/
02031, 00000, "Recommended undo tablespace size is based on undo generation rate and undo retention in the system."
/
02032, 00000, "Instance does not have an online undo tablespace"
/
02033, 00000, "Online undo tablespace with size %d MB"
/
02034, 00000, "Instance has an online undo tablespace"
/
02035, 00000, "Instance has an online undo tablespace"
/
02036, 00000, "Many operations may fail without undo tablespace online"
/
02037, 00000, "Recommended undo tablespace size is based on undo generation rate , undo retention and longest query duration in the system."
/
03000, 00000, "Tablespace [%s] is [%s] full"
/
03001, 00000, "Add space to the tablespace"
/
/ 03500 - 03599 Reserved for Threshold-based Alerts.
/
03500, 00000, "Metrics \"%s\" is at %s"
/
03501, 00000, "Metrics \"%s\" is at %s for file \"%s\""
/
03502, 00000, "Metrics \"%s\" is at %s for service \"%s\""
/
03503, 00000, "Metrics \"%s\" is at %s for event class \"%s\""
/
03504, 00000, "Run ADDM to get more performance analysis about your system."
/
03505, 00000, "Session %s is blocking %s other sessions"
/
03506, 00000, "Threshold is updated on metrics \"%s\" for instance \"%s\""
/
03507, 00000, "Check DBA_THRESHOLDS view to verify the result"
/
03508, 00000, "Threshold is updated on metrics \"Tablespace Space Usage\""
/
03509, 00000, "Tablespace [%s] only has [%s] free space"
/
03510, 00000, "Run the calibrate utility and restart a replay with the suggested number of WRC clients, distributed between machines with the necessary capacity."
/
03511, 00000, "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"
/
03512, 00000, "Too many replay client connections (%s\%) are using the CPU concurrently in WRC client %s running on %s as process %s"
/
03513, 00000, "Too many replay client connections (%s\%) are doing concurrent IO operations in WRC client %s running on %s as process %s"
/
03514, 00000, "Database is in capture mode"
/
03515, 00000, "Database is in replay mode"
/
/ 03600-03699 RESERVED FOR BACKUP/RECOVERY
/
03600, 00000, "%s of %s bytes is %s%% used and has %s remaining bytes available."
/
03601, 00000, "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."
/
03602, 00000, "Threshold is updated on metric \"Recovery Area Space Usage\""
/
/ 03700-03799 RESERVED FOR OBJECT SPACE ADVISOR - CREATE TABLE
/
03700, 00000, "Estimated space usage if table is created is %s bytes."
/
/ 03800-03899 RESERVED FOR OBJECT SPACE ADVISOR - CREATE INDEX
/
03800, 00000, "Estimated space usage if index is created is %s bytes."
/
/ 03900-03999 RESERVED FOR OBJECT SPACE ADVISOR - GROWTH TREND
/
03900, 00000, "Growth trend table output."
/
03901, 00000, "Insufficient information to make a recommendation."
/
03902, 00000, "The object has less than 1% free space, it is not worth shrinking."
/
03903, 00000, "Perform shrink, estimated savings is %s bytes."
/
03904, 00000, "The object has some free space but cannot be shrunk because %s."
/
03905, 00000, "The free space in the object is less than the size of the last extent."
/
03906, 00000, "Allocated Space:%s: Used Space:%s: Reclaimable Space :%s:"
/
03907, 00000, "Enable row movement of the table %s.%s and perform shrink, estimated savings is %s bytes. "
/
03908, 00000, "Perform re-org on the object %s, estimated savings is %s bytes. "
/
03909, 00000, "%s percent chained rows can be removed by re-org."
/
03910, 00000, "The object has chained rows that can be removed by re-org."
/
03911, 00000, "The free space in the object is less than 10MB."
/
03912, 00000, "Compress object %s.%s, estimated savings is %s bytes."
/
03913, 00000, "Compress object %s.%s partition %s, estimated savings is %s bytes."
/
03914, 00000, "Compress object %s.%s subpartition %s, estimated savings is %s bytes."
/
03915, 00000, "I/O Requests/min:%s, I/O Waits/min:%s, Segment Size (MB):%s, I/O Waits/Req:%s."
/
03916, 00000, "Move object %s.%s to flash storage, estimated I/O wait reduction is %s millisec"
/
03917, 00000, "Move object %s.%s partition %s to flash storage, estimated I/O wait reduction is %s millisec."
/
03918, 00000, "Move object %s.%s subpartition %s to flash storage, estimated I/O wait reduction is %s millisec."
/
03919, 00000, "%s percent chained rows can be removed by re-org, confirm the object column count is not more than 255."
/
/ 04000-04099 RESERVED FOR CLUSTER/DATABASE/INSTANCE CONTROL (GRID DIRECTOR)
/
04000, 00000, "No action is necessary -- Grid Director to process."
/
04001, 00000, "An instance is being quiesced."
/
/
/ 04100-04299 RESERVED FOR HIGH AVAILABILITY ALERT MESSAGES
/
04100, 00000, "No action is necessary"
/
04101, 00000, "Restart if desired and not automatically restarting"
/
04120, 00000, "Instance %s up on node %s as of time %s; reason code: %s"
/
04121, 00000, "Instance %s down on node %s as of time %s; reason code: %s"
/
04122, 00000, "Composite service %s%s up as of time %s; reason code: %s"
/
04123, 00000, "Composite service %s%s down as of time %s; reason code: %s"
/
04124, 00000, "Service up on instance %s node %s as of time %s; reason code: %s"
/
04125, 00000, "Service down on instance %s node %s as of time %s; reason code: %s"
/
04126, 00000, "Service preconnect up on instance %s node %s as of time %s; reason code: %s"
/
04127, 00000, "Service preconnect down on instance %s node %s as of time %s; reason code: %s"
/
04128, 00000, "Database %s (domain %s) up as of time %s; reason code: %s"
/
04129, 00000, "Database %s (domain %s) down as of time %s; reason code: %s"
/
04130, 00000, "Node %s incarnation %s down as of time %s; reason code: %s"
/
04131, 00000, "ASM Instance %s up on node %s as of time %s; reason code: %s"
/
04132, 00000, "ASM Instance %s down on node %s as of time %s; reason code: %s"
/
04133, 00000, "GSM instance %s in region %s is down or not reachable."
/
04134, 00000, "Check the GSM alert log to find out the exact error message, take the appropriate action and restart the GSM."
/
04135, 00000, "The database instance %s in GDS pool %s and region %s is down or not reachable."
/
04136, 00000, "Check the database instance alert log to find out the exact error message, take the appropriate action and restart the database instance."
/
04137, 00000, "The global service %s in the GDS pool %s, region %s, is running on less than the specified number of databases."
/
04138, 00000, "Make sure that the global service is started in the preferred/available databases."
/
04139, 00000, "For the database instance %s in the GDS pool %s and region %s, the %s threshold was reached."
/
04140, 00000, "Check the workload on the named database instance."
/
04141, 00000, "The replication lag for service %s in GDS pool %s, database %s in region %s has exceeded the specified maximum value."
/
04142, 00000, "Check the replication lag on the named database."
/
04143, 00000, "GDS catalog %s is down or not reachable."
/
04144, 00000, "Check the availability of the named database."
/
4145, 00000, "The database %s in GDS pool %s and region %s is down or not reachable."
/
4146, 00000, "Check the database alert log to find out the exact error message, take the appropriate action and restart the database."
/
/
/
/ 04300-04499 RESERVED FOR STREAMS ALERT MESSAGES
/
04300, 00000, "STREAMS capture process \"%s\" aborted with ORA-%s"
/
04301, 00000, "Obtain 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."
/
04302, 00000, "STREAMS apply process \"%s\" aborted with ORA-%s"
/
04303, 00000, "Obtain 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."
/
04304, 00000, "STREAMS propagation process \"%s\" aborted after 16 failures"
/
04305, 00000, "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."
/
04306, 00000, "If the currently running workload is typical, consider increasing the size of the Streams pool."
/
04307, 00000, "STREAMS error queue for apply process \"%s\" contains new transaction with ORA-%s"
/
04308, 00000, "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."
/
04309, 00000, "STREAMS automatic split happened on original capture process \"%s\", original streams process \"%s\", cloned capture process \"%s\", and cloned streams process \"%s\""
/
04310, 00000, "STREAMS automatic merge executes automatically once the cloned streams process works properly. Check DBA_STREAMS_SPLIT_MERGE for more details."
/
04311, 00000, "XStream capture process \"%s\" aborted with ORA-%s"
/
04312, 00000, "Obtain 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."
/
04313, 00000, "XStream apply process \"%s\" aborted with ORA-%s"
/
04314, 00000, "Obtain 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."
/
04315, 00000, "XStream propagation process \"%s\" aborted after 16 failures"
/
04316, 00000, "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."
/
04317, 00000, "XStream error queue for apply process \"%s\" contains new transaction with ORA-%s"
/
04318, 00000, "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."
/
04319, 00000, "XStream automatic split happened on original capture process \"%s\", original XStream process \"%s\", cloned capture process \"%s\", and cloned XStream process \"%s\""
/
04320, 00000, "XStream automatic merge executes automatically once the cloned Xstream process works properly. Check DBA_STREAMS_SPLIT_MERGE for more details."
/
04321, 00000, "GoldenGate capture process \"%s\" aborted with ORA-%s"
/
04322, 00000, "Obtain 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."
/
04323, 00000, "GoldenGate apply process \"%s\" aborted with ORA-%s"
/
04324, 00000, "Obtain 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."
/
04325, 00000, "GoldenGate propagation process \"%s\" aborted after 16 failures"
/
04326, 00000, "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."
/
04327, 00000, "GoldenGate error queue for apply process \"%s\" contains new transaction with ORA-%s"
/
04328, 00000, "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."
/
04329, 00000, "GoldenGate automatic split happened on original capture process \"%s\", original GoldenGate process \"%s\", cloned capture process \"%s\", and cloned GoldenGate process \"%s\""
/
04330, 00000, "GoldenGate automatic merge executes automatically once the cloned GoldenGate process works properly. Check DBA_STREAMS_SPLIT_MERGE for more details."
/
04331, 00000, "Apply automatic restart on apply process \"%s\"."
/
04332, 00000, "Apply is automatically restarted when the apply user roles are changed."
/
/
/ 04500-04599 RESERVED FOR COMPRESSION ADVISOR
/
04500, 00000, "Table %s sort on column %s - compression ratio by block count is %s"
/
04501, 00000, "Incorrect compression type %s"
/
04502, 00000, "Table %s %s - Estimated compression ratio is %s"
/
04503, 00000, "Table %s with sampling percentage %s"
/
04504, 00000, "Not enough data for compression ratio"
/
04505, 00000, "Estimated compression ratio is %s"
/
04506, 00000, "Obj no %s: Table %s compressable - Number of uncompressed blocks is %s"
/
04507, 00000, "This procedure is not supported for SYSTEM and SYSAUX tablespaces"
/
04508, 00000, "Tablespace %s does not exist"
/
04509, 00000, "Table %s does not exist"
/
04510, 00000, "Table Partition %s.%s %s - Estimated compression ratio is %s"
/
04511, 00000, "Table Partition %s.%s with sampling percentage %s"
/
04512, 00000, "Table Partition %s.%s sort on column %s - estimated compression ratio is %s"
/
04513, 00000, "Obj no %s: Table Partition %s.%s compressable - Number of uncompressed blocks is %s"
/
/ =============================================
/ messages for SPM Evolve Advisor [04600-04699]
/ =============================================
/
04600, 00000, "The baseline plan matches the non-accepted plan being verified."
/
04601, 00000, "None of the accepted plans were reproducible."
/
04602, 00000, "The plan was verified in %s seconds. It failed the benefit criterion because its verified performance was %s times worse than that of the baseline plan."
/
04603, 00000, "The plan was verified in %s seconds. It failed the benefit criterion because its verified performance was only %s times better than that of the baseline plan."
/
04604, 00000, "The plan was verified in %s seconds. It passed the benefit criterion because its verified performance was %s times better than that of the baseline plan."
/
04605, 00000, "The plan was not verified."
/
04606, 00000, "The plan was automatically accepted."
/
04607, 00000, "Consider accepting the SQL plan baseline."
/
04608, 00000, "This plan was skipped because it is already accepted."
/
04609, 00000, "This plan was skipped because it was verified recently."
/
04610, 00000, "This plan was skipped because its SQL statement has not been executed recently."
/
04611, 00000, "The plan is adaptive and different from the final executed plan. Implementing the recommendation will drop the adaptive plan and create a new accepted plan matching the final executed plan."
/
04612, 00000, "The plan is adaptive and different from the final executed plan. The final executed plan already exists in the plan history. Implementing the recommendation will drop the adaptive plan and change the final executed plan to accepted."
/
04613, 00000, "The plan is adaptive and different from the final executed plan. The final executed plan already exists in the plan history as an accepted plan. Implementing the recommendation will drop the adaptive plan."
/
04614, 00000, "The plan is adaptive and matches the final executed plan. Implementing the recommendation will change the plan to static and accepted."
/
04615, 00000, "This plan was skipped because either the database is not fully open or the SQL statement is ineligible for SQL Plan Management."
/
/ =============================================
/ messages for ADDM (11g and onwards) [05000-05999]
/ =============================================
/
/ The following section (05000-05199) is reserved for very short messages
/ containing concepts such as "finding names", "subjects of findings",
/ generic concepts, and headers and tags for ADDM reports.
/
/ Developers and translators should keep the message size to a minimum.
/ Note that the messages contain mostly nouns and are not supposed to be
/ full sentences.
/
/
05000, 00000, "\"Administrative\" Wait Class"
/
05001, 00000, "\"Application\" Wait Class"
/
05002, 00000, "\"Cluster\" Wait Class"
/
05003, 00000, "\"Concurrency\" Wait Class"
/
05004, 00000, "\"Configuration\" Wait Class"
/
05005, 00000, "\"Network\" Wait Class"
/
05006, 00000, "\"Other\" Wait Class"
/
05007, 00000, "\"Scheduler\" Wait Class"
/
05008, 00000, "\"User I/O\" wait Class"
/
05009, 00000, "Buffer Busy"
/
05010, 00000, "Buffer Cache Latches"
/
05011, 00000, "Checkpoints Due to DROP or TRUNCATE"
/
05012, 00000, "Checkpoints Due to Log File Size"
/
05013, 00000, "Checkpoints Due to MTTR"
/
05014, 00000, "Checkpoints Due to Parallel Queries"
/
05015, 00000, "Checkpoints Due to Tablespace DDL"
/
05016, 00000, "Commits and Rollbacks"
/
05017, 00000, "CPU Usage"
/
05018, 00000, "DBMS_LOCK Usage"
/
05019, 00000, "DBMS_PIPE Usage"
/
05020, 00000, "Excessive Rebinds"
/
05021, 00000, "Free Buffer Waits"
/
05022, 00000, "Hard Parse"
/
05023, 00000, "Hard Parse Due to Invalidations"
/
05024, 00000, "Hard Parse Due to Literal Usage"
/
05025, 00000, "Hard Parse Due to Parse Errors"
/
05026, 00000, "Hard Parse Due to Sharing Criteria"
/
05027, 00000, "High Watermark Waits"
/
05028, 00000, "I/O Throughput"
/
05029, 00000, "Index Block Split"
/
05030, 00000, "Global Cache Busy"
/
05031, 00000, "Global Cache Congestion"
/
05032, 00000, "Interconnect Latency"
/
05033, 00000, "Global Cache Lost Blocks"
/
05034, 00000, "Global Cache Messaging"
/
05035, 00000, "Global Cache Multiblock Requests"
/
05036, 00000, "ITL Waits"
/
05037, 00000, "Java Execution"
/
05038, 00000, "Latch Free Waits"
/
05039, 00000, "Log File Switches"
/
05040, 00000, "PL/SQL Compilation"
/
05041, 00000, "PL/SQL Execution"
/
05042, 00000, "RMAN I/O"
/
05043, 00000, "Row Lock Waits"
/
05044, 00000, "Sequence Usage"
/
05045, 00000, "Session Connect and Disconnect"
/
05046, 00000, "Session Slot Scheduling"
/
05047, 00000, "Shared Pool Latches"
/
05048, 00000, "Slow Archivers"
/
05049, 00000, "Soft Parse"
/
05050, 00000, "Space Transaction Waits"
/
05051, 00000, "Streams Flow Control"
/
05052, 00000, "Table Locks"
/
05053, 00000, "Temp Space Contention"
/
05054, 00000, "Top Segments by I/O"
/
05055, 00000, "Top SQL by \"Cluster\" Wait"
/
05056, 00000, "Top SQL by DB Time"
/
05057, 00000, "Top SQL By I/O"
/
05058, 00000, "Undersized Buffer Cache"
/
05059, 00000, "Undersized PGA"
/
05060, 00000, "Undersized Redo Log Buffer"
/
05061, 00000, "Undersized SGA"
/
05062, 00000, "Undersized Shared Pool"
/
05063, 00000, "Undersized Streams Pool"
/
05064, 00000, "Undo I/O"
/
05065, 00000, "Unusual \"Administrative\" Wait Event"
/
05066, 00000, "Unusual \"Application\" Wait Event"
/
05067, 00000, "Unusual \"Cluster\" Wait Event"
/
05068, 00000, "Unusual \"Commit\" Wait Event"
/
05069, 00000, "Unusual \"Concurrency\" Wait Event"
/
05070, 00000, "Unusual \"Configuration\" Wait Event"
/
05071, 00000, "Unusual \"Network\" Wait Event"
/
05072, 00000, "Unusual \"Other\" Wait Event"
/
05073, 00000, "Unusual \"Scheduler\" Wait Event"
/
05074, 00000, "Unusual \"User I/O\" Wait Event"
/
05075, 00000, "Virtual Memory Paging"
/
05076, 00000, "Resource Manager"
/
05077, 00000, "Parsing"
/
05078, 00000, "CPU"
/
05079, 00000, "Data I/O"
/
05080, 00000, "Redo I/O"
/
05081, 00000, "Memory"
/
05082, 00000, "Interconnect"
/
05083, 00000, "Space"
/
05084, 00000, "Internal Concurrency"
/
05085, 00000, "Application Waits"
/
05086, 00000, "Queue Operations"
/
05087, 00000, "Top Consumers"
/
05088, 00000, "Miscellaneous"
/
05089, 00000, "\"Queueing\" Wait Class"
/
05090, 00000, "Unusual \"Queueing\" Wait Event"
/
05091, 00000, "Undersized instance memory"
/
05092, 00000, "Top SQL Statements"
/
05093, 00000, "Top Segments by \"User I/O\" and \"Cluster\""
/
05094, 00000, "Buffer Busy - Hot Block"
/
05095, 00000, "Buffer Busy - Hot Objects"
/
05096, 00000, "Resource Manager CPU Throttling"
/
05097, 00000, "Resource Manager PQ Queueing"
/
05098, 00000, "PGA_AGGREGATE_LIMIT Throttling"
/
05099, 00000, "Resource Manager I/O Throttling"
/
05100, 00000, "Contention for latches related to the shared pool was consuming significant database time in some instances."
/
05101, 00000, "Contention on buffer cache latches was consuming significant database time in some instances."
/
05102, 00000, "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."
/
05103, 00000, "Waits for redo log buffer space were consuming significant database time in some instances."
/
05104, 00000, "Host CPU was a bottleneck for some instances. Wait times will be inflated by wait for CPU."
/
05105, 00000, "Significant virtual memory paging was detected on the host operating system of some instances."
/
05106, 00000, "Database latches in the \"Other\" wait class were consuming significant database time in some instances."
/
05107, 00000, "Buffer caches were undersized in some instances, causing significant additional read I/O."
/
05108, 00000, "The SGA was inadequately sized in some instances, causing additional I/O or hard parses."
/
05109, 00000, "The streams pool was inadequately sized in some instances, causing additional I/O and blocking streams enqueue operations."
/
05110, 00000, "The PGA was inadequately sized in some instances, causing additional I/O to temporary tablespaces to consume significant database time."
/
05111, 00000, "Hard parsing of SQL statements was consuming significant database time in some instances."
/
05112, 00000, "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."
/
05113, 00000, "Hard parses due to an inadequately sized shared pool were consuming significant database time in some instances."
/
05114, 00000, "Hard parsing SQL statements that encountered parse errors was consuming significant database time in some instances."
/
05115, 00000, "Cursors were getting invalidated due to DDL operations. This resulted in additional hard parses which were consuming significant database time in some instances."
/
05116, 00000, "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."
/
05117, 00000, "Soft parsing of SQL statements was consuming significant database time in some instances."
/
05118, 00000, "List of analyzed instance numbers, used when global ADDM analyzes only a subset of instances"
/
05119, 00000, "The instance is using the public interconnect device \"%s\" with IP address %s and source \"%s\"."
/
05120, 00000, "The instance is using the private interconnect device \"%s\" with IP address %s and source \"%s\"."
/
05121, 00000, "Look at the instance level ADDM tasks for a list of interconnect devices used by a specific instance."
/
05122, 00000, "Some instances were using public interconnect devices."
/
05123, 00000, "The Oracle instance memory (SGA and PGA) was adequately sized."
/
05124, 00000, "The Oracle instance memory (SGA and PGA) was inadequately sized, causing additional I/O and CPU usage."
/
05125, 00000, "The optimal memory target for the instance could not be determined because the value of \"memory_target\" changed during the analysis period."
/
05126, 00000, "The optimal memory target for the instance could not be determined because of incomplete AWR snapshots."
/
05127, 00000, "Increase memory allocated to the instance by setting the parameter \"memory_target\" to %s M."
/
05128, 00000, "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."
/
05129, 00000, "The Oracle instance memory (SGA and PGA) was inadequately sized in some instances, causing additional I/O and CPU usage."
/
05130, 00000, "Enables database analysis mode for automatic ADDM runs"
/
05131, 00000, "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."
/
05132, 00000, "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\"."
/
05133, 00000, "Tune the entry point PL/SQL \"%s\" of type \"%s\" and ID %s. Refer to the PL/SQL documentation for addition information."
/
05134, 00000, "Tune the entry point PL/SQL ID %s. Refer to the PL/SQL documentation for addition information."
/
05135, 00000, "%s seconds spent in executing PL/SQL \"%s\" of type \"%s\" and ID %s."
/
05136, 00000, "%s seconds spent in executing PL/SQL ID %s."
/
05137, 00000, "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."
/
05138, 00000, "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."
/
05139, 00000, "Filter recommendations regarding segments that belong to owner \"%s\", named \"%s\" with sub-objects named \"%s\"."
/
05140, 00000, "Filter recommendations regarding the segment with data object number %s."
/
05141, 00000, "Filter recommendations to change the value of parameter \"%s\"."
/
05142, 00000, "Inter-instance messaging was consuming significant database time."
/
05143, 00000, "Inter-instance messaging was not consuming significant database time."
/
05144, 00000, "Higher than expected latency of the cluster interconnect was responsible for significant database time."
/
05145, 00000, "Global Cache Service Processes (LMSn) were not processing requests fast enough."
/
05146, 00000, "The database was consuming %s kilo bits per second of interconnect bandwidth."
/
05147, 00000, "Global Cache Service Processes (LMSn) were performing within acceptable limits of %s milliseconds."
/
05148, 00000, "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."
/
05149, 00000, "Waits on event \"log file sync\" in one instance can cause global cache contention on other instances."
/
05150, 00000, "Investigate cause of congestion on blocks received by this instance from remote instance \"%s\"."
/
05151, 00000, "Investigate cause of congestion on blocks received from remote instance \"%s\"."
/
05152, 00000, "This problem is often related to CPU bottleneck, virtual memory paging or inappropriate LMSn process priority in the remote instance."
/
05153, 00000, "The device \"%s\" was used for %s\% of interconnect traffic and experienced %s send or receive errors during the analysis period."
/
05154, 00000, "The device \"%s\" experienced %s send or receive errors during the analysis period."
/
05155, 00000, "The instance was consuming %s kilo bits per second of interconnect bandwidth for global cache messages. Information on other interconnect traffic is not available."
/
05156, 00000, "The database was consuming %s kilo bits per second of interconnect bandwidth for global cache messages. Information on other interconnect traffic is not available."
/
05157, 00000, "%s\% of this interconnect bandwidth was used for global cache messaging, %s\% for parallel query messaging and %s\% for database lock management."
/
05158, 00000, "The average latency for 8K interconnect messages was %s microseconds."
/
05159, 00000, "Consider slowing down RMAN or Data Pump activity, or scheduling these jobs when user activity is lower."
/
05160, 00000, "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."
/
05161, 00000, "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."
/
05162, 00000, "For file %s, the average response time for single block reads was %s milliseconds, and the total excess I/O wait was %s seconds."
/
05163, 00000, "Investigate the file I/O throughput of the archiver process(es) to make sure it is appropriate for the underlying hardware."
/
05164, 00000, "The archiver's I/O throughput was %s per second on redo log files and %s per second on archive and archive backup log files."
/
05165, 00000, "The total I/O throughput on redo log files was %s per second and the archiver was responsible for %s%% of it."
/
05166, 00000, "The total I/O throughput on redo log files was %s per second for reads and %s per second for writes."
/
05167, 00000, "The 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."
/
05200, 00000, "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."
/
05201, 00000, "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."
/
05202, 00000, "Run SQL Tuning Advisor on the %s statement with SQL_ID \"%s\"."
/
05203, 00000, "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."
/
05204, 00000, "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."
/
05205, 00000, "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."
/
05206, 00000, "The SQL Tuning Advisor cannot operate on this SQL statement."
/
05207, 00000, "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."
/
05208, 00000, "At least %s distinct execution plans were utilized for this SQL statement during the analysis period."
/
05209, 00000, "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\"."
/
05210, 00000, "SQL statements consuming significant database time were found. These statements offer a good opportunity for performance improvement."
/
05211, 00000, "The SQL Tuning Advisor cannot operate on %s statements."
/
05212, 00000, "Full scan of %s \"%s.%s\" with object ID %s consumed %s%% of the database time spent on this SQL statement."
/
05213, 00000, "Full scan of segment with object ID %s consumed %s%% of the database time spent on this SQL statement."
/
05214, 00000, "I/O and Cluster wait for %s \"%s.%s\" with object ID %s consumed %s%% of the database time spent on this SQL statement."
/
05215, 00000, "I/O and Cluster wait for segment with object ID %s consumed %s%% of the database time spent on this SQL statement."
/
05216, 00000, "Individual database segments responsible for significant \"User I/O\" and \"Cluster\" waits were found."
/
05217, 00000, "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."
/
05218, 00000, "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."
/
05219, 00000, "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."
/
05220, 00000, "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."
/
05221, 00000, "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."
/
05222, 00000, "No recommendations are available at the database level. Check the ADDM analysis of affected instances for recommendations."
/
05223, 00000, "Increase the buffer cache size of affected instances. Check the ADDM analysis of affected instances for more details."
/
05224, 00000, "Consider adding more CPUs or more instances serving the database. Check the ADDM analysis of affected instances for additional recommendations."
/
05225, 00000, "Increase the shared pool size of affected instances. Check the ADDM analysis of affected instances for more details."
/
05226, 00000, "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."
/
05227, 00000, "Investigate application logic for possible use of bind variables instead of literals. Alternatively, you may set the parameter \"cursor_sharing\" to \"force\"."
/
05228, 00000, "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."
/
05229, 00000, "Increase the memory allocated to affected instances. Check the ADDM analysis of affected instances for more details."
/
05230, 00000, "Investigate memory allocation to Oracle instances and other applications on affected hosts. Check the ADDM analysis of affected instances for more details."
/
05231, 00000, "Increase the size of the SGA on affected instances. Check the ADDM analysis of affected instances for more details."
/
05232, 00000, "Increase the streams pool size of affected instances. Check the ADDM analysis of affected instances for more details."
/
05233, 00000, "Increase the size of the PGA on affected instances. Check the ADDM analysis of affected instances for more details."
/
05234, 00000, "There were no hot blocks for \"buffer busy\" wait events during the analysis period."
/
05235, 00000, "There were no hot objects for \"buffer busy\" wait events during the analysis period."
/
05236, 00000, "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."
/
05237, 00000, "Subprogam ID %s of PL/SQL ID %s spent %s seconds in execution."
/
05238, 00000, "The SQL statement executed in the root container."
/
05239, 00000, "The SQL statement executed in the container with database ID %s."
/
05240, 00000, "The SQL statement executed in container %s with database ID %s."
/
05241, 00000, "The database segment belongs to the root container."
/
05242, 00000, "The database segment belongs to the container with database ID %s."
/
05243, 00000, "The database segment belongs to container %s with database ID %s."
/
05244, 00000, "The tablespace belongs to the root container."
/
05245, 00000, "The tablespace belongs to the container with database ID %s."
/
05246, 00000, "The tablespace belongs to container %s with database ID %s."
/
05247, 00000, "For file %s in the root container, the average response time for single block reads was %s milliseconds and the total excess I/O wait was %s seconds."
/
05248, 00000, "For file %s in the container with database ID %s, the average response time for single block reads was %s milliseconds and the total excess I/O wait was %s seconds."
/
05249, 00000, "For file %s in container %s with database ID %s, the average response time for single block reads was %s milliseconds and the total excess I/O wait was %s seconds."
/
05250, 00000, "The database block belongs to the root container."
/
05251, 00000, "The database block belongs to the container with database ID %s."
/
05252, 00000, "The database block belongs to container %s with database ID %s."
/
05253, 00000, "The session was active in the root container."
/
05254, 00000, "The session was active in the container with database ID %s."
/
05255, 00000, "The session was active in container %s with database ID %s."
/
05256, 00000, "The module activity was in the root container."
/
05257, 00000, "The module activity was in the container with database ID %s."
/
05258, 00000, "The module activity was in container %s with database ID %s."
/
05259, 00000, "The service connected to the root container."
/
05260, 00000, "The session connected to the container with database ID %s."
/
05261, 00000, "The session connected to container %s with database ID %s."
/
05262, 00000, "Waits for lock with identifier %s in the root container were consuming significant database time."
/
05263, 00000, "Waits for lock with identifier %s in the container with database ID %s were consuming significant database time."
/
05264, 00000, "Waits for lock with identifier %s in container %s with database ID %s were consuming significant database time."
/
05265, 00000, "Tablespace %s of the root container was found in backup mode. Verify that it is appropriate."
/
05266, 00000, "Tablespace %s of container with database ID %s was found in backup mode. Verify that it is appropriate."
/
05267, 00000, "Tablespace %s of container %s with database ID %s was found in backup mode. Verify that it is appropriate."
/
05268, 00000, "Sessions were found waiting for sufficient parallel servers to run the parallel query. Consider reducing the DOP of parallel statements."
/
05269, 00000, "Sessions were found waiting in the parallel statement queue. Consider bypassing this queue by setting the directive PARALLEL_STMT_CRITICAL to TRUE for these Oracle Resource Manager consumer groups."
/
05270, 00000, "Sessions were found waiting for sufficient parallel query processes to run the parallel query. Consider increasing the number of parallel servers used by these Oracle Resource Manager consumer groups (or PDBs) by increasing the value of the directive PARALLEL_SERVER_LIMIT."
/
05271, 00000, "Sessions were consuming significant PGA memory. Consider increasing the PGA limit for these sessions by increasing the value of the parameter PGA_AGGREGATE_LIMIT."
/
05272, 00000, "Sessions were found waiting in Oracle Resource Manager's I/O Queue. Consider increasing the value of the parameter MAX_IOPS or MAX_MBPS."
/
/ ============================================
/ messages for SQL Auto-tune UI[06000-06199]
/ ============================================
06000, 00000, "The %s was first executed to warm the buffer cache."
/
06001, 00000, "Statistics for %s were averaged over next %s executions."
/
06002, 00000, "Statistics for %s were from the second execution."
/
06003, 00000, "Statistics for %s were averaged over %s executions."
/
/ =============================================
/ messages for Statistics Advisor [07000-07999]
/ =============================================
/
07000, 00000, "Automatic statistics collection is not enabled because maintenance window is not created."
/
07001, 00000, "Automatic statistics collection is not enabled because maintenance windows are not enabled."
/
07002, 00000, "Automatic statistics collection is not enabled because automated maintenance tasks are not enabled."
/
07003, 00000, "Automatic statistics collection is not enabled because statistics collection is disabled for Automated Maintenance Tasks."
/
07004, 00000, "Automatic statistics collection is not enabled because _enable_automatic_maintenance != 1."
/
07005, 00000, "Automatic statistics collection is not enabled because _optimizer_autostats_job = false."
/
07006, 00000, "Automatic statistics collection is not enabled because job_queue_processes = 0."
/
07007, 00000, "Create maintenance windows using DBMS_SCHEDULER PL/SQL package or through Oracle Enterprise Manager."
/
07008, 00000, "Enable maintenance windows using DBMS_SCHEDULER PL/SQL package or through Oracle Enterprise Manager."
/
07009, 00000, "Enable auto tasks using DBMS_AUTO_TASK_ADMIN PL/SQL package or through Oracle Enterprise Manager."
/
07010, 00000, "Enable automatic optimizer statistics collection using DBMS_AUTO_TASK_ADMIN PL/SQL package or through Oracle Enterprise Manager."
/
07011, 00000, "Set parameter %s to %s."
/
07012, 00000, "Automatic statistics job avoids the majority of the issues with query optimizer statistics gathering. The recommended options are used and statistics gathered for those objects only that need new statistics. The need for manual tasks for managing the statistics is eliminated, which significantly reduces the chances of getting poor execution plans because of missing or stale statistics."
/
07013, 00000, "There are %s uses of GATHER_TABLE_STATS."
/
07014, 00000, "Use GATHER_SCHEMA_STATS instead of GATHER_TABLE_STATS."
/
07015, 00000, "GATHER_SCHEMA_STATS has more options available, including checking for staleness and gathering statistics concurrently. Also it is more maintainable for new tables added to the schema. If you only want to gather statistics for certain tables in the schema, specify them in the obj_filter_list parameter of GATHER_SCHEMA_STATS."
/
07016, 00000, "There are %s object(s) with no statistics."
/
07017, 00000, "Statistics job not scheduled for %s maintenance window(s)."
/
07018, 00000, "Statistics jobs did not complete at the end of maintenance windows."
/
07019, 00000, "Statistics history tables are too big."
/
07020, 00000, "The CONCURRENT preference is not used."
/
07021, 00000, "Global preference %s is set to a non-default value '%s'."
/
07022, 00000, "SQL Plan Directive has been turned off."
/
07023, 00000, "Please file a Service Request with Oracle."
/
07024, 00000, "Increase the length of the maintenance window."
/
07025, 00000, "Set the CONCURRENT preference."
/
07026, 00000, "Set the value of preference %s to '%s'."
/
07027, 00000, "Turn on SQL Plan Directives."
/
07028, 00000, "Gather Statistics on those objects with no statistics."
/
07029, 00000, "The issue is due to Oracle bugs."
/
07030, 00000, "Increasing the length of the maintenance window gives the statistics gathering job more time to finish."
/
07031, 00000, "The system's condition satisfies the use of concurrent statistics gathering. Using CONCURRENT increases the efficiency of statistics gathering."
/
07032, 00000, "Setting preference %s to non-default value '%s' can cause inaccurate statistics, please refer to %s."
/
07033, 00000, "Index statistics are important for the query optimizer to come up with efficient query plans. With the default value DBMS_STATS.AUTO_CASCADE, DBMS_STATS gathers statistics for indexes in an efficient manner as part of gathering table statistics."
/
07034, 00000, "METHOD_OPT controls the creation of histograms during statistics collection. With the default value FOR ALL COLUMNS SIZE AUTO, Oracle determines which columns require histograms and the number of buckets to use based on the usage of columns in SQL statements and the number of distinct values. The default value helps to create the necessary histograms with an adequate number of buckets."
/
07035, 00000, "Execution plans are not affected by statistics of some (sub)partition types. Setting preference GRANULARITY to the default value 'AUTO' avoids statistics collection of those types."
/
07036, 00000, "Setting preference %s to non-default value '%s' can result in spike in number of hard parses."
/
07037, 00000, "Preference %s is for Oracle internal use only, setting it to nondefault value '%s' could cause unforeseen consequences."
/
07038, 00000, "SQL Plan Directives trigger the creation of extended statistics that help to get better execution plans."
/
07039, 00000, "Stale statistics or no statistics will result in bad plans."
/
07040, 00000, "There are %s SET_[COLUMN|INDEX|TABLE|SYSTEM]_STATS procedures being used for statistics gathering."
/
07041, 00000, "Do not use SET_[COLUMN|INDEX|TABLE|SYSTEM]_STATS procedures. Gather statistics instead of setting them."
/
07042, 00000, "SET_[COLUMN|INDEX|TABLE|SYSTEM]_STATS will cause bad plans due to wrong or inconsistent statistics."
/
07043, 00000, "Importing statistics happened shortly after gathering statistics operation on the same target for %s object(s)."
/
07044, 00000, "Gathering statistics happened shortly after importing statistics operation on the same target for %s object(s)."
/
07045, 00000, "Investigate such sequences and figure out which operation should be used."
/
07046, 00000, "Importing statistics shortly after gathering statistics or vice versa overrides the effect of previous operation."
/
07047, 00000, "There are %s indexes which have inconsistent statistics with their column statistics."
/
07048, 00000, "Using default parameter values for statistics gathering operations is more efficient."
/
07049, 00000, "There are %s table(s) which have been dropped multiple times."
/
07050, 00000, "There are %s statistics operation(s) using nondefault parameters."
/
07051, 00000, "Use default parameters for statistics operations."
/
07052, 00000, "Out-of-range scenarios are observed on %s table(s)."
/
07053, 00000, "Copy table statistics from old partitions to newly created partitions."
/
07054, 00000, "Copying table statistics in such a way would avoid out-of-range errors, and would likely be more accurate for newly created partitions. Refer to: https://blogs.oracle.com/optimizer/entry/maintaining_statistics_on_large_partitioned_tables."
/
07055, 00000, "Out-of-order histogram endpoint errors are observed on %s table(s)."
/
07056, 00000, "Regather statistics for tables with out-of-order histograms."
/
07057, 00000, "Out-of-order histograms indicate that the statistics for the table are not consistent or corrupt. Hence these statistics need to be regathered."
/
07058, 00000, "Recollect statistics for these tables with referential constraints at the same time."
/
07059, 00000, "Statistics should be consistent across columns of tables with Primary Key-Foreign Key referential constraints to get optimal execution plans."
/
07060, 00000, "Recollect statistics for these tables and their indexes at the same time."
/
07061, 00000, "Statistics should be consistent across tables and their indexes to get optimal execution plans."
/
07062, 00000, "Use TRUNCATE TABLE instead of DROP TABLE commands on these tables."
/
07063, 00000, "After the table is dropped, we will lose the column usage information for that table. That might prevent some statistics (for example, histograms) from being collected in the future."
/
07064, 00000, "There are %s object(s) with stale statistics."
/
07065, 00000, "Regather statistics on objects with stale statistics."
/
07066, 00000, "There were %s maintenance windows that failed to open."
/
07067, 00000, "There were %s maintenance windows that failed to close."
/
07068, 00000, "AUTOSTATS_TARGET preference has been set to ORACLE."
/
07069, 00000, "Set the AUTOSTATS_TARGET preference to AUTO."
/
07070, 00000, "Setting AUTOSTATS_TARGET preference to ORACLE restricts the scope of the automatic statistics job. It will collect statistics only for Oracle-owned objects."
/
07071, 00000, "Automatic statistics purging failed."
/
07072, 00000, "Run PURGE_STATS command. If that does not work, file a service request with Oracle Support Services."
/
07073, 00000, "Purge cannot keep up with the retention period."
/
07074, 00000, "Statistics retention period is too high."
/
07075, 00000, "Reduce the statistics retention period."
/
07076, 00000, "Reducing the statistics retention period results in a smaller statistics history table."
/
07077, 00000, "With the default setting, DBMS_STATS.AUTO_INVALIDATE of NO_INVALIDATE parameter, cursors that access the table whose statistics are being regathered will be invalidated gradually over time to ensure there is no performance impact on the shared pool or a spike in CPU usage which could happen if you have a large number of dependent cursors and if all of them were hard parsed at once."
/
07078, 00000, "Setting preference %s to the default value '%s' is more beneficial."
/
07079, 00000, "Setting preference ESTIMATE_PERCENT to the default value DBMS_STATS.AUTO_SAMPLE_SIZE produces more accurate statistics in an efficient manner."
/
07080, 00000, "Preference %s should be set to the default value %s."
/
07081, 00000, "Preference %s is set to a non-default value at the object level for %s object(s)."
/
07082, 00000, "Statistics gathering operations will skip locked objects and may lead to stale or inaccurate statistics."
/
07083, 00000, "Unlock the statistics on non-volatile tables, and use gather statistics operations to gather statistics for these tables."
/
07084, 00000, "Statistics are locked on %s table(s) which are not volatile."
/
07085, 00000, "Volatile tables become stale very quickly, and may not represent the typical workload scenario of the table. Locking the statistics on such tables makes the statistics more accurate and stable. Also if there are no statistics, the Optimizer will build the plan with the help of dynamic statistics."
/
07086, 00000, "There are %s object(s) using \"ANALYZE TABLE <table_name> [COMPUTE | ESTIMATE] STATISTICS\" to gather statistics."
/
07087, 00000, "Use GATHER_SCHEMA_STATS instead of ANALYZE TABLE statements to gather statistics."
/
07088, 00000, "\"ANALYZE TABLE <table_name> [COMPUTE | ESTIMATE] STATISTICS\" is obsolete and no longer supported."
/
07089, 00000, "Statistics are being gathered on %s object(s) when they are not stale."
/
07090, 00000, "GATHER_SCHEMA_STATS with GATHER_STALE option can be used to gather statistics only when the objects are stale."
/
07091, 00000, "Gathering statistics when statistics are not stale wastes resources including the resources needed to collect statistics and the space required to save the statistics and history."
/
07092, 00000, "Bulk DML operations are observed within one hour of statistics collection for %s object(s)."
/
07093, 00000, "Move bulk DML operations before statistics gathering."
/
07094, 00000, "The statistics are inaccurate and stale because bulk DML was executed shortly after statistics gathering."
/
07095, 00000, "There are %s object(s) which have inconsistent statistics for %s with the columns in their referenced tables."
/
07096, 00000, "Gather statistics on volatile tables under a typical workload situation or leave them with no statistics and lock the statistics."
/
07097, 00000, "Statistics are not locked for %s volatile table(s)."
/
07098, 00000, "Out-of-range errors are observed on %s columns after gathering statistics."
/
07099, 00000, "Incremental option should be used on %s object(s) for statistics gathering."
/
07100, 00000, "Use the incremental option for statistics gathering on these objects."
/
07101, 00000, "Using the incremental option reduces the time it takes to gather statistics on partitioned tables. However, it does store additional information, which takes up additional space."
/
07102, 00000, "Incremental option has been turned on for %s table(s), which will not benefit from using the incremental option."
/
07103, 00000, "Do not use the incremental option for statistics gathering on these objects."
/
07104, 00000, "The overhead of using the incremental option on these tables outweighs the benefit of using the incremental option."
/
07105, 00000, "AUTO DEGREE should be used on %s object(s) to gather statistics."
/
07106, 00000, "Use AUTO DEGREE when gathering statistics on these objects."
/
07107, 00000, "Using AUTO DEGREE will speed up statistics gathering on these tables."
/
07108, 00000, "Check the other findings of this rule, as well as the findings for the rules AvoidFrequentStatsCollection, UseDefaultPreference, UseDefaultParams for possible causes and recommendations."
/
07109, 00000, "The size of the statistics history table could be big because of violations of other rules."
/
07110, 00000, "Maintenance window configuration appears to be correct. Requires more investigation by Oracle Support."
/
/
/
/
OHA YOOOO