/* Copyright (c) Oracle Corporation 1998, 1999. All Rights Reserved. */  
/  
/*  
/   
/   NAME  
/     qsmus.msg - Oracle Summary Management Advisor routines error messages  
/   DESCRIPTION  
/     Contains the various error codes returned by the routines, what they 
/     mean and what the probable cause is and what action(s), if any, to 
/     take.  
/   
/ Errors can be internal or user errors. Internal errors are not reported  
/ specifically, rather a generic error code (QSMA_FAILURE) is used. User  
/ errors have individual error codes so that the user can take corrective 
/ action.   
 
/------------------------------------------------------------------------------/  
/ NOTES:  
/   Language      : American  
/   Character set : US7ASCII  
/  
/  
/  
/ MODIFIED       (MM/DD/YY)  
/ btao            06/14/99 - add msg 514 
/ sramakri        06/30/98 - Add 513, one or more of the workload tables is mis
/ sramakri        06/11/98 - add more messages
/ sramakri        05/29/98 - Add more messages
/ sramakri        03/18/98 - Summary management messages used by summary adviso
/ sramakri        01/19/98 - Creation   
/*/  
  
  
00501, 00000, "unable to initialize Summary Advisor environment"  
// *Cause:  The Summary Advisor external procedure initialization process 
//          failed.  
// *Action: Contact Oracle Worldwide Support. 
  
00502, 00000, "OCI error"  
// *Cause:  A OCI callback routine reported an error
// *Action: Contact Oracle Worldwide Support. 
  
00503, 00000, "out of memory"
// *Cause:  Summary Advisor failed to allocate the necessary memory.
// *Action: Contact Oracle Worldwide Support. 

00504, 00000, "internal error"
// *Cause:  An internal error occurred.
// *Action: Contact Oracle Worldwide Support. 

00505, 00000, "syntax error"
// *Cause:  A syntax error occurred.
// *Action: Correct syntax error if possible or contact Oracle
// Worldwide Support. 

00506, 00000, "no fact-tables could be found"
// *Cause:  The fact-filter is not specified, and there are no 
//          fact-tables in the warehouse. A fact-table is a table
//          having foreign-key constraints to one or more of the 
//          dimension-tables in the data warehouse.
// *Action: Check the fact-filter is correctly specified; check that
//          appropriate constraints exist; and the user has privileges
//          to access the tables

00507, 00000, "no dimensions could be found"
// *Cause:  The database does not have any dimensions
// *Action: Create the dimensions in your warehouse

00508, 00000, "statistics missing on tables/columns"
// *Cause:  The system metadata does not contain statistics
//          on one or more tables or columns. The Advisor
//          needs cardinalities of all fact-tables, and of the
//          level-keys of all dimensions in the data warehouse.
// *Action: Run ANALYZE on the tables and summaries in the
//          warehouse to collect statistics

00509, 00000, "invalid parameter"
// *Cause:  The indicated parameter has an invalid value
// *Action: Supply a value in the proper range

00510, 00000, "statistics missing on summaries"
// *Cause:  The system metadata does not contain statistics
//          on one or more summaries. The Advisor
//          needs cardinalities of all summaries in the 
//          data warehouse.
// *Action: Run ANALYZE on the tables and summaries in the
//          warehouse to collect statistics.

00511, 00000, "invalid fact-tables specified in fact-filter"
// *Cause:  The tables specified in the fact-filter are not
//          valid fact-tables. A fact-table must have foreign-key
//          constraints to one or more of the dimension-tables in the data
//          warehouse.
// *Action: Check the fact-filter is correctly specified; check that
//          appropriate constraints exist; and the user has privileges
//          to access the tables

00512, 00000, "invalid summaries specified in the retention-list"
// *Cause:  The summaries specified in the retention-list are not valid.
// *Action: Check the spelling of the summary-names; check that they are 
//          valid; and the user has privileges to access them.

00513, 00000, "one or more of the workload tables is missing"
// *Cause:  One or both of the workload tables are missing. 
//          The two workload tables which should be present 
//          in the user's schema are V_192216243_F_5_E_14_8_1
//          and V_192216243_F_5_E_15_8_1; the former is mapped
//          to WORK$_IDEAL_MVIEW and the latter to WORK$_MVIEW_USAGE.
//          The workload tables are created by the Oracle Trace Formatter
//          when the data-collection-file (oraclesm.dat) is formatted by 
//          the user.
// *Action: Check whether the Formatter succeeded in formatting the data
//          collection. Sometimes the V_192216243_F_5_E_14_8_1 (i.e
//          WORK$_IDEAL_MVIEW) may not be created whereas the other table
//          is created. The most likely cause of this is the init.ora parameters
//          needed to invoke mview-rewrite are not enabled. Check your
//          documentation for all the init.ora parameters which need to be set
//          for mview-rewrite to occur. Another possibility is no GROUP BY
//          queries were issued during the time the data was collected, in
//          which case, run the Trace collection for a longer time to get a 
//          representative sampling of the queries issued in the data
//          warehouse.

00514, 00000, "the size of must-retain summaries exceeds specified space limit"
// *Cause:  The specified space limit is greater than the size of must-retain
//          summaries.
// *Action: Reduce the number of must-retain summaries or increase the space
//          limit
