// $Id: err.txt,v 1.17 2009/02/08 23:02:04 mschenke Exp $
// ARCS: $Header: /u02/webapps/workbench/cvs/RDA_4/src/scripting/lib/modules/err.txt,v 1.17 2009/02/08 23:02:04 mschenke Exp $
// ///////////////////////////////////////////////////////////////////////////
//   00000.00099      General Errors
// ///////////////////////////////////////////////////////////////////////////
//
00000,0, "Cannot change to the RDA install directory"
// *Cause: RDA failed to change the current directory to the RDA install
//         directory.
// *Action: Check the path and the permissions of the install directory.
// *Mnemonic: RDA_CD_HOME_FAIL
//
00001,0, "Cannot change to the output directory"
// *Cause: RDA failed to change the current directory to the output directory.
// *Action: Check the path and the permissions of the output directory. The
//          directory does not always exist before data is collected.
// *Mnemonic: RDA_CD_OUTPUT_FAIL
//
00002,0, "Cannot zip the reports"
// *Cause: RDA detected an error when using zip to package the reports.
// *Action: Check for any other errors reported by the zip command. Check the
//          path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: GU_ZIP_ERROR
//
00003,0, "Cannot package the reports using 'pax'"
// *Cause: RDA detected an error when using pax to package the reports.
// *Action: Check for any other errors reported by the pax command. Check the
//          path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: GU_PAX_ERROR
//
00004,0, "Cannot package the reports using 'tar'"
// *Cause: RDA detected an error when using tar to package the reports.
// *Action: Check for any other errors reported by the tar command. Check the
//          path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: GU_TAR_ERROR
//
00005,0, "Cannot list the reports"
// *Cause: RDA cannot open the output directory.
// *Action: Check access to the reports.
// *Mnemonic: GU_DIR_ERROR
//
00006,0, "Archive command not -yet- identified"
// *Cause: No packaging tool paths have been found.
// *Action: RDA cannot find any packaging tool paths. Typically this occurs
//          when the end report has not been produced yet or if these commands
//          are not found in the current execution path (cf. PATH).
// *Mnemonic: GU_PKG_ERROR
//
00007,0, "Error <err> not found"
// *Cause: RDA failed to find the explanation of the specified error.
// *Action: Report this error to Oracle Support. Describe the circumstances
//          under which the error was encountered.
// *Mnemonic: GU_BAD_ERROR
//
00008,0, "External package '<class>' not available"
// *Cause: RDA cannnot load the specified package.
// *Action: The next line provides more information about this error. Take
//          appropriate actions to fix it.
// *Mnemonic: GU_BAD_PACKAGE
//
00009,0, "Error in external call"
// *Cause: RDA encountered an error when evaluating the external call.
// *Action: The next line provides more information about that error. Take
//          appropriate actions to fix it.
// *Mnemonic: GU_BAD_CALL
//
00010,0, "Cannot locate required RDA modules"
// *Cause: RDA encountered an error when loading RDA Perl packages.
// *Action: The next line provides more information about that error. Take
//          appropriate actions to fix it.
// *Mnemonic: GU_NO_AGENT
//
00011,0, "Missing file list"
// *Cause: RDA encountered an error when loading RDA Perl packages.
// *Action: Reinstall RDA.
// *Mnemonic: GU_NO_LIST
//
00012,0, "Directory structure not preserved"
// *Cause: RDA found the file list in the top RDA directory.
// *Action: Reinstall RDA, ensuring that the directory structure is well
//          preserved.
// *Mnemonic: GU_BAD_TOPO
//
00013,0, "File list corrupted"
// *Cause: The checksum of the file list is incorrect.
// *Action: Reinstall RDA.
// *Mnemonic: GU_BAD_LIST
//
00014,0, "%d issue(s) found in the RDA installation"
// *Cause: RDA encountered issues when checking the installation.
// *Action: Reinstalling RDA is usually the easiest way to fix file
//          alteration problems. However, permission problems can also result
//          from other factors:
//          - If RDA has been installed by another user, the default settings
//            may be too restrictive. Review the local context with that user
//            and your local system administrator.
//          - Execution permissions can be missing from startup scripts for
//            other platforms and when Perl is not available from the command
//            line.
// *Mnemonic: GU_BAD_INST
//
00015,0, "Warning - %d database request(s) not executed in %s module(s)"
// *Cause: RDA encountered execution timeouts or requests have been skipped.
// *Action: More details about these errors can be found in 'Report Settings'.
//          If there are no database problems, increase the SQL_TIMEOUT value
//          using one of the following methods:
//          - Edit the setup file.
//          - At the command line, use an option such as -e SQL_TIMEOUT=120
//          The value indicates the number of seconds a database request can
//          run before being interrupted. A zero value disables any timeout.
// *Mnemonic: GU_SQL_WARNINGS
//
00016,0, "END module setup required for managing authentication"
// *Cause: RDA cannot find the END module in the configuration file.
// *Action: Set up the END module by using the following command arguments:
//          -S END
// *Mnemonic: GU_NO_END
//
00017,0, "Warning - %d command(s) not executed in %s module(s)"
// *Cause: RDA encountered execution timeouts.
// *Action: More details about these errors can be found in 'Report Settings'.
//          If there are no system problems, increase the RDA_TIMEOUT value
//          using one of the following methods:
//          - Edit the setup file.
//          - At the command line, use an option such as -e RDA_TIMEOUT=600
//          The value indicates the number of seconds an operating system
//          command can run before being interrupted. A zero value disables any
//          timeout.
// *Mnemonic: GU_OS_WARNINGS
//
00018,0, "Warning - %d XML request(s) not executed in %s module(s)"
// *Cause: RDA encountered execution timeouts.
// *Action: More details about these errors can be found in 'Report Settings'.
//          If there are no system problems, increase the RDA_TIMEOUT value
//          using one of the following methods:
//          - Edit the setup file.
//          - At the command line, use an option such as -e RDA_TIMEOUT=600
//          The value indicates the number of seconds an operating system
//          command can run before being interrupted. A zero value disables any
//          timeout.
// *Mnemonic: GU_XML_WARNINGS
//
00019,0, "Cannot package the reports using 'jar'"
// *Cause: RDA detected an error when using jar to package the reports.
// *Action: Check for any other errors reported by the jar command. Also check 
//          the path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: GU_JAR_ERROR
//
00020,0, "Cannot create the transfer directory"
// *Cause: RDA failed to create the transfer directory in the report directory.
// *Action: Check the permissions and ownership of the report directory.
// *Mnemonic: GU_XFR_CREATE
//
00021,0, "Cannot delete the module"
// *Cause: An attempt was made to delete a module that must be executed at each
//         run.
// *Action: Consider setup as an alternative.
// *Mnemonic: GU_DEL_MODULE
//
00022,0, "Option '-f' required to delete the module and its collected data"
// *Cause: RDA collected data for that module already.
// *Action: Use the '-f' option to remove the collected data also.
// *Mnemonic: GU_DEL_REPORTS
//
00023,0, "Invalid list type"
// *Cause: An invalid list type was provided.
// *Action: Use 'levels', 'modules', 'profiles', 'tests', or 'tools' as list
//          types.
// *Mnemonic: GU_BAD_TYPE
//

// ///////////////////////////////////////////////////////////////////////////
//   00100.00199      Setup Errors (Agent.pm, Module.pm, Setting.pm)
// ///////////////////////////////////////////////////////////////////////////
//
00100,0, "Cannot create the setup file"
// *Cause: RDA cannot create the setup file.
// *Action: Check to see if the current user has write permissions to the
//          existing setup file and to the related directory (by default, the
//          RDA top directory.)
// *Mnemonic: SETUP_CREATE_FAIL
//
00101,0, "Invalid setup file"
// *Cause: RDA encountered an error when loading the setup file.
// *Action: Do not edit the setup file directly. Use the setup mode of RDA.
// *Mnemonic: SETUP_BAD_FILE
//
00102,0, "Invalid character in setting value"
// *Cause: RDA found a carriage return, a line feed, or a &#nnn; character 
//         in a setting value.
// *Action: These characters are not allowed in setting values and must be
//          removed because they can cause setup file corruptions.
// *Mnemonic: SETUP_BAD_CHAR
//
00103,0, "Cannot open the setup specification file"
// *Cause: RDA cannot open the module setup specification file.
// *Action: Verify that the current user has permission to access
//          and to open the setup specification file.
// *Mnemonic: SETUP_OPEN_FAIL
//
00104,0, "Invalid setup attribute keyword"
// *Cause: RDA found an invalid attribute keyword.
// *Action: Ensure that the keyword corresponds to a known attribute.
// *Mnemonic: SETUP_BAD_KEY
//
00105,0, "Invalid setup attribute value"
// *Cause: RDA found an invalid attribute value.
// *Action: There are invalid character(s) in the attribute value or extra
//          characters are found after an attribute value. RDA allows comments
//          only after an attribute value. Remove the offending characters.
// *Mnemonic: SETUP_BAD_VALUE
//
00106,0, "Unexpected setup specification"
// *Cause: RDA found an invalid setup specification.
// *Action: The corresponding line does not correspond to valid syntax.
//          Correct the invalid syntax.
// *Mnemonic: SETUP_BAD_SPEC
//
00107,0, "Error(s) in <module> setup"
// *Cause: RDA detected errors when loading the setup specifications.
// *Action: Check the previous messages related to all errors found.
// *Mnemonic: SETUP_LOAD_ERROR
//
00108,0, "Invalid name"
// *Cause: RDA found an invalid setting name.
// *Action: The setting name can contain alphanumeric characters and
//          underscores only. A special name - also exists. Rename the setting
//          and omit the illegal characters.
// *Mnemonic: SETUP_BAD_NAME
//
00109,0, "Invalid type"
// *Cause: RDA found an invalid setting type.
// *Action: Enter a valid setting type. Valid types are: B (Boolean),
//          C (Comment), D (Directory), F (File), N (Number), T (Text).
// *Mnemonic: SETUP_BAD_TYPE
//
00110,0, "Cannot backup the setup file"
// *Cause: RDA cannot rename the setup file under a new name.
// *Action: Verify that the current user has write permissions to the existing
//          setup file and to the related directory, by default the RDA top
//          directory.
// *Mnemonic: SETUP_BACKUP_FAIL
//
00111,0, "Setup file already in use"
// *Cause: The setup file is currently used by a concurrent run.
// *Action: Wait until the completion of the other run and try again.
// *Mnemonic: SETUP_IN_USE
//
00112,0, "Cannot open the profile definition file"
// *Cause: RDA cannot open the setup profile definition file.
// *Action: Verify that the current user has permission to access and to open
//          the setup profile definition file.
// *Mnemonic: PROFILE_OPEN_FAIL
//
00113,0, "Invalid profile specification value"
// *Cause: RDA found an invalid value.
// *Action: Invalid characters are found in the specification value or
//          extra characters are found after the value. RDA allows comments only
//          after a value. Remove the offending characters.
// *Mnemonic: PROFILE_BAD_VALUE
//
00114,0, "Invalid profile module list"
// *Cause: RDA found an invalid module list.
// *Action: Invalid characters were found in the module list or extra
//          characters were found after the list. RDA allows comments only
//          after a list. Remove the offending characters.
// *Mnemonic: PROFILE_BAD_LIST
//
00115,0, "Unexpected profile specification"
// *Cause: RDA found an invalid setup profile specification.
// *Action: The corresponding line does not correspond to valid syntax.
//          Correct the invalid syntax.
// *Mnemonic: PROFILE_BAD_SPEC
//
00116,0, "Error(s) in profile definition file"
// *Cause: RDA detected errors when loading the setup profile specifications.
// *Action: Check the previous messages related to all errors found.
// *Mnemonic: PROFILE_LOAD_ERROR
//
00117,0, "Invalid validation type"
// *Cause: RDA found an invalid setting validation.
// *Action: Enter a valid setting validation type. Valid types are: E (Error),
//          N (No validation), W (Warning)
// *Mnemonic: SETUP_BAD_VALIDATION
//
00118,0, "Invalid setting value"
// *Cause: RDA detected an invalid setting value.
// *Action: See the previous line(s) for more explanations about the error.
// *Mnemonic: SETUP_INVALID_SETTING
//
00119,0, "Cannot create the lock file"
// *Cause: RDA cannot create the lock file.
// *Action: Check the permissions of the lock directory specified by the
//          RDA_LOCK environment variable or the directory containing the setup
//          file.
// *Mnemonic: SETUP_BAD_LOCK
//
00120,0, "Cannot open pager"
// *Cause: RDA failed to open the pager.
// *Action: Check the setting of the PAGER environment variable.
// *Mnemonic: SETUP_PAGER_FAIL
//
00121,0, "RDA setup interrupted"
// *Cause: The RDA program was interrupted during the setup of a data
//         collection module.
// *Action: Run RDA again as appropriate.
// *Mnemonic: SETUP_INTERRUPT
//
00122,0, "Invalid profile name"
// *Cause: RDA cannot find the specified profile name.
// *Action: Check the list of defined profiles, particularly if the RDA_PROFILE
//          environment variable is used.
// *Mnemonic: PROFILE_BAD_NAME
//
00123,0, "Missing setup file"
// *Cause: The INI module was not configured yet in that setup file.
// *Action: Configure a module first before executing that request.
// *Mnemonic: SETUP_MISSING
//
00124,0, "Filter not enabled"
// *Cause: The filter is not defined or not active.
// *Action: Define the filter and enable it.
// *Mnemonic: NO_FILTER
//
00125,0, "Cannot create the filter file"
// *Cause: RDA encountered an error when creating the filter file.
// *Action: Check the existence and the permissions of the work directory and
//          of a possible previous file.
// *Mnemonic: SAVE_FILTER
//

// ///////////////////////////////////////////////////////////////////////////
//   00200.00299      Collect Errors (Block.pm, Value.pm)
// ///////////////////////////////////////////////////////////////////////////
//
00200,0, "Cannot create the report directory"
// *Cause: RDA failed to create the report directory.
// *Action: Check the existence, permissions, and ownership of the report
//          directory's parent directories. Verify that the name of the report
//          directory does not contain references to shell variables.
// *Mnemonic: COLLECT_DIR_CREATE
//
00201,0, "Output file not specified"
// *Cause: A report declaration is missing.
// *Action: Declare the report. The report must be declared before the first
//          attempt to write to the output file.
// *Mnemonic: COLLECT_NO_REPORT
//
00202,0, "Cannot create the output file"
// *Cause: RDA cannot create the output file.
// *Action: Correct the permission problem and execute RDA again. Alternatively,
//          specify another report directory by running the setup of the
//          initialization module again, using the following command arguments:
//          -S INI
// *Mnemonic: COLLECT_OUTPUT_CREATE
//
00203,0, "Cannot create the TOC file"
// *Cause: RDA cannot create the Table of Content file.
// *Action: Correct the permission problem and execute RDA again. Alternatively,
//          specify another report directory by running the setup of the
//          initialization module again, using the following command arguments:
//          -S INI
// *Mnemonic: COLLECT_TOC_CREATE
//
00204,0, "Cannot create a test file in the report directory"
// *Cause: RDA cannot create the test file in the report directory.
// *Action: Correct the permission problem and execute RDA again. Alternatively,
//          specify another report directory by running the setup of the
//          initialization module again, using the following command arguments:
//          -S INI
// *Mnemonic: COLLECT_TEST_CREATE
//
00205,0, "Cannot remove the test file from the report directory"
// *Cause: RDA cannot remove the test file from the report directory.
// *Action: RDA must be able to remove temporary and report files from the
//          output directory. It is required for maintaining the report
//          consistency when running RDA multiple times. Correct the permission
//          problem and execute RDA again. Alternatively, specify another
//          report directory by running the setup of the initialization module
//          again, using the following command arguments:
//          -S INI
// *Mnemonic: COLLECT_TEST_UNLINK
//
00206,0, "RDA data collection interrupted"
// *Cause: The RDA program was interrupted during data collection.
// *Action: Report the error, providing contextual information when RDA
//          was interrupted for a possible hang.
// *Mnemonic: COLLECT_INTERRUPT
//
00207,0  "Not enough free space for running RDA"
// *Cause: The available space on the output disk is less than the minimum
//         specified by the RDA_FREE setting.
// *Action: Free some space or relocate the output directory on a disk with
//          more available space.
// *Mnemonic: COLLECT_FREE
//
00208,0  "Not enough free space to complete the output request"
// *Cause: The available space on the output disk is less than the minimum
//         specified by the RDA_FREE setting.
// *Action: Free some space or relocate the output directory on a disk with
//          more available space.
// *Mnemonic: OUTPUT_FREE
//
00210,0, "Invalid or missing macro call"
// *Cause: RDA found an invalid argument in a call command.
// *Action: Make sure that the argument of a 'call' command is a macro call.
// *Mnemonic: COLLECT_CALL_ARG
//
00211,0, "Missing scalar variable"
// *Cause: No scalar variable was specified in the for/loop command.
// *Action: Make sure that all 'for' or 'loop' commands include a scalar
//          variable to contain the current iteration value.
// *Mnemonic: COLLECT_LOOP_VAR
//
00212,0, "Invalid command format"
// *Cause: RDA found an invalid for format.
// *Action: Make sure that all 'for' statements have 2 or 3 values, to define
//          the value interval and the incrementation value.
// *Mnemonic: COLLECT_FOR_INTERVAL
//
00213,0, "Missing scalar variable"
// *Cause: No variable was specified in the decr/incr command.
// *Action: Make sure that a scalar variable (including an array or hash item)
//          is the first argument of a decr or incr command.
// *Mnemonic: COLLECT_INCR_VAR
//
00214,0, "Extra value(s) found"
// *Cause: RDA found more values than expected.
// *Action: Make sure that a decrementation/incrementation value is included
//          after the variable in a decr or incr command. In addition,
//          make sure that the value can be evaluated as a number.
// *Mnemonic: COLLECT_EXTRA_VALUE
//
00215,0, "Invalid or missing name"
// *Cause: RDA detected an invalid or missing name.
// *Action: Make sure that all output and macro names start with a letter
//          that is followed by additional alphanumeric characters.
// *Mnemonic: COLLECT_NAME
//
00216,0, "Invalid or missing name"
// *Cause: RDA detected an invalid or missing name.
// *Action: Make sure that all sub module names in a run command contain
//          alphanumeric characters only.
// *Mnemonic: COLLECT_RUN_NAME
//
00217,0, "Invalid left value list"
// *Cause: The left value list of a var command does not contain variables only.
// *Action: Make sure that the left value list contains variables,
//          variable references, array or hash items only.
// *Mnemonic: COLLECT_VAR_BAD_LIST
//
00218,0, "Invalid left value"
// *Cause: The left value is not a variable.
// *Action: Make sure that the left value in a var command contains a
//          variable, a variable reference, an array or hash item only.
// *Mnemonic: COLLECT_VAR_BAD_VARIABLE
//
00219,0, "Invalid or missing variable"
// *Cause: RDA detected an invalid or missing variable in a var command.
// *Action: Make sure that the var command argument begins with a variable
//          or a variable list followed by an assignment if required.
// *Mnemonic: COLLECT_VAR_BAD_LIST
//
00220,0, "Invalid value(s) found in variable list"
// *Cause: RDA found invalid values in 'delete', 'global', or 'import'
//         arguments.
// *Action: Make sure that variables are included as arguments only.
// *Mnemonic: COLLECT_BAD_VARIABLE
//
00221,0, "Invalid variable"
// *Cause: RDA detected an invalid variable in a 'set' or an 'append' command.
// *Action: Make sure that a scalar variable is used.
// *Mnemonic: COLLECT_NO_VARIABLE
//
00222,0, "Missing opening parenthesis"
// *Cause: RDA expects an opening parenthesis.
// *Action: Make sure that the value or argument list begins with a parenthesis.
// *Mnemonic: COLLECT_START_PARENTHESIS
//
00223,0, "Missing closing parenthesis"
// *Cause: RDA expects a closing parenthesis.
// *Action: A closing parenthesis terminates lists. The parser can be
//          confused by invalid syntax inside a list. Make sure that the list
//          ends with a parenthesis.
// *Mnemonic: COLLECT_END_PARENTHESIS
//
00224,0, "Invalid or missing array index"
// *Cause: RDA expected a single value as an array index.
// *Action: Make sure that the array index contains only one value, and that
//          the value can be evaluated as a number.
// *Mnemonic: COLLECT_BAD_INDEX
//
00225,0, "Invalid array index end"
// *Cause: RDA expects a closing bracket at the array index end.
// *Action: Make sure that the array index ends with a closing (square) bracket.
// *Mnemonic: COLLECT_END_BRACKET
//
00226,0, "Invalid or missing hash key"
// *Cause: RDA expects a single value as a hash key.
// *Action: Make sure that the hash key contains only one value, and that the
//          value can be evaluated as a text string.
// *Mnemonic: COLLECT_BAD_KEY
//
00227,0, "Invalid hash key end"
// *Cause: RDA expects a closing brace as hash key end.
// *Action: Make sure that the hash key ends with a closing brace (curly
//          bracket).
// *Mnemonic: COLLECT_END_BRACE
//
00228,0, "Invalid macro end"
// *Cause: RDA expects a closing parenthesis at macro end.
// *Action: Make sure that the macro has an argument list. Even if there are no
//          arguments, an empty list must be provided. This list must be
//          terminated by a closing parenthesis.
// *Mnemonic: COLLECT_END_MACRO
//
00229,0, "Invalid value"
// *Cause: RDA found an unrecognized value.
// *Action: The parser is not able to identify the value.
// *Mnemonic: COLLECT_BAD_VALUE
//
00230,0, "Invalid output file type"
// *Cause: An invalid output file type was specified.
// *Action: Specify a valid output file type: OF, ON, RF, RN, SF, or SN.
// *Mnemonic: COLLECT_OUTPUT_TYPE
//
00231,0, "Cannot open the output file"
// *Cause: RDA cannot open the output file.
// *Action: Verify the permissions of the output file and take appropriate
//          actions.
// *Mnemonic: COLLECT_OUTPUT_OPEN
//
00232,0, "Cannot create the reference file"
// *Cause: RDA cannot create the reference file.
// *Action: Correct the permission problem and execute RDA again.
// *Mnemonic: COLLECT_REF_CREATE
//
00233,0, "Cannot open the reference file"
// *Cause: RDA cannot open the reference file.
// *Action: Verify the permissions of the reference file and take appropriate
//          actions.
// *Mnemonic: COLLECT_REF_OPEN
//
00234,0, "Cannot create the sample file"
// *Cause: RDA cannot create the sample file.
// *Action: Correct the permission problem and execute RDA again.
// *Mnemonic: COLLECT_SAMPLE_CREATE
//
00235,0, "Cannot open the sample file"
// *Cause: RDA cannot open the sample file.
// *Action: Verify the permissions of the sample file and take appropriate
//          actions.
// *Mnemonic: COLLECT_SAMPLE_OPEN
//
00236,0, "Cannot create the alias file"
// *Cause: RDA cannot create the alias file in the report directory.
// *Action: Correct the permission problem and execute RDA again.
// *Mnemonic: COLLECT_ALIAS_CREATE
//
00237,0, "The output file prefix is too long"
// *Cause: Key parts of the report file names could be truncated.
// *Action: Specify a shorter prefix. Rerun the initialisation module setup by
//          specifying '-S INI' as command arguments.
// *Mnemonic: COLLECT_ALIAS_OPEN
//
00238,0, "Cannot create the output pipe"
// *Cause: RDA cannot create the output pipe.
// *Action: Verify the output command.
// *Mnemonic: COLLECT_OUTPUT_PIPE
//
00239,0, "Cannot open pager"
// *Cause: RDA failed to open the pager.
// *Action: Check the setting of the PAGER environment variable.
// *Mnemonic: COLLECT_PAGER_FAIL
//
00240,0, "Break or next used outside a loop"
// *Cause: RDA found a break or next command outside a for, a loop, or a while
//         command.
// *Action: Report the error, providing contextual information to
//          reproduce the problem.
// *Mnemonic: COLLECT_BAD_BREAK
//
00241,0, "Error encountered in the block called"
// *Cause: RDA detected an error when executing a sub module.
// *Action: Report the error and the previous errors.
// *Mnemonic: COLLECT_RUN_ERROR
//

00250,0, "Invalid value type"
// *Cause: An invalid type is specified in value creation.
// *Action: Report the error and provide contextual information to
//          reproduce the problem.
// *Mnemonic: VAL_BAD_TYPE
//
00251,0, "Invalid reference assignment"
// *Cause: RDA expects a reference to be assigned to that variable.
// *Action: Report the error.
// *Mnemonic: VAL_BAD_REF
//
00252,0, "Incompatible types"
// *Cause: Variable and value types are incompatible.
// *Action: Report the error and provide contextual information to
//          reproduce the problem.
// *Mnemonic: VAL_INCOMPATIBLE
//
00253,0, "Error encountered in the macro called"
// *Cause: RDA encountered an error in a macro and propagated it to the
//         calling context.
// *Action: Report the error, along with any previous errors.
// *Mnemonic: VAL_MACRO_ERROR
//
00254,0, "Undefined macro"
// *Cause: The macro is not defined.
// *Action: Report the error.
// *Mnemonic: VAL_UNKNOWN_MACRO
//
00255,0, "Not a numeric value"
// *Cause: RDA cannot convert the value to a number.
// *Action: Report the error and provide contextual information to
//          reproduce the problem.
// *Mnemonic: VAL_BAD_NUMBER
//
00256,0, "Not a text string"
// *Cause: RDA cannot convert the value to a text string.
// *Action: Report the error and provide contextual information to
//          reproduce the problem.
// *Mnemonic: VAL_BAD_TEXT
//

00260,0, "Cannot open the specification file"
// *Cause: RDA cannot find a specification file found for the specified module.
// *Action: An invalid module name has been specified. Look in the
//          module list or in the modules directory for the exact name.
// *Mnemonic: LOAD_FILE
//

00290,0, "No filter rules"
// *Cause: No filter rules found
// *Action: Review the filter definition and take appropriate actions.
// *Mnemonic: NO_RULES
//
00291,0, "Filter code error"
// *Cause: RDA cannot create the filter code created from the specified rules.
// *Action: Review the filter definition and take appropriate actions.
// *Mnemonic: BAD_FILTER
//

// ///////////////////////////////////////////////////////////////////////////
//   00300.00399      Render Errors (Render.pm)
// ///////////////////////////////////////////////////////////////////////////
//
00300,0, "Cannot create the report directory"
// *Cause: RDA failed to create the report directory.
// *Action: Check the existence, permissions, and ownership of the report
//          directory's parent directories. Verify that the name of the report
//          directory does not contain references to shell variables.
// *Mnemonic: RPT_DIR_CREATE
//
00301,0, "Cannot open the report directory"
// *Cause: RDA failed to read the report directory content.
// *Action: Check the permissions to access the report directory.
// *Mnemonic: RPT_DIR_OPEN
//
00302,0, "Cannot open the format specification file"
// *Cause: RDA failed to open the format specification file.
// *Action: Check the permissions to access files in the report directory.
// *Mnemonic: RPT_TEXT_OPEN
//
00303,0, "Cannot create the report file"
// *Cause: RDA failed to create the report file in the report directory.
// *Action: Check the permissions of the report directory.
// *Mnemonic: RPT_HTML_CREATE
//
00304,0, "Cannot create the index format specifications"
// *Cause: RDA failed to create the index format specification file in the
//         report directory.
// *Action: Check the permissions of the report directory.
// *Mnemonic: RPT_INDEX_CREATE
//
00305,0, "Cannot create the sub index format specifications"
// *Cause: RDA failed to create the sub index format specification file in the
//         report directory.
// *Action: Check the permissions of the report directory.
// *Mnemonic: RPT_SUB_INDEX_CREATE
//
00306,0, "Cannot create the start file"
// *Cause: RDA failed to create the start file in the report directory.
// *Action: Check the permissions of the report directory.
// *Mnemonic: RPT_START_CREATE
//
00307,0, "Cannot create the blank file"
// *Cause: RDA failed to create the blank file in the report directory.
// *Action: Check the permissions of the report directory.
// *Mnemonic: RPT_BLANK_CREATE
//
00308,0, "Cannot launch rendering sub process"
// *Cause: RDA is not able to execute itself.
// *Action: Adapt the configuration to allow RDA to be launched by itself.
// *Mnemonic: COLLECT_RENDER_PIPE
//

// ///////////////////////////////////////////////////////////////////////////
//   00400.00499      Manual Page Errors (Pod.pm)
// ///////////////////////////////////////////////////////////////////////////
//
00400,0, "Cannot display manual pages"
// *Cause: RDA failed to display the manual pages due to missing Perl packages.
// *Action: If available, use a more recent/complete Perl environment.
// *Mnemonic: MAN_DISPLAY_FAIL
//
00401,0, "Missing or invalid manual file"
// *Cause: RDA failed to find the corresponding file.
// *Action: Check to see if the name corresponds to an existing module or to
//          a '.def' or 'pod' file in the modules directory.
// *Mnemonic: MAN_MISSING
//
00402,0, "Cannot open the manual file"
// *Cause: RDA failed to open the manual file.
// *Action: Check the permissions of the modules directory and contained files.
// *Mnemonic: MAN_OPEN_FAIL
//
00403,0, "Cannot open pager"
// *Cause: RDA failed to open the pager.
// *Action: Check the setting of the PAGER environment variable.
// *Mnemonic: MAN_PAGER_FAIL
//

// ///////////////////////////////////////////////////////////////////////////
//   00500.00599      Macro Errors
// ///////////////////////////////////////////////////////////////////////////
//
00500,0, "Expecting a hash variable as argument"
// *Cause: The argument is not a hash.
// *Action: Verify that 'keys' has a hash as an argument.
// *Mnemonic: INVALID_HASH
//
00501,0, "Database accesses disabled due to a connection problem"
// *Cause: RDA cannot connect to execute a simple SQL statement.
// *Action: Look at the associated error message for more details about the
//          problem.
//          - Ensure there are no prompts being made by
//            $ORACLE_HOME/sqlplus/admin/glogin.sql or $HOME/login.sql.
//          - If the userid is incorrect, rerun the database module setup by
//            specifying '-S DB' as command arguments.
//          - If the userid is correct, it is possible an incorrect password was
//            specified
//          - If the password is incorrect, provide a valid password when
//            prompted.
//          Remember that for SYSDBA users, the password used should be the
//          database password for the user and not the password stored in the
//          password file.
// *Mnemonic: NO_CONNECTION
//
00502,0, "Database connection timeout"
// *Cause: The database cannot execute the SQL statement(s) in the specified
//         time.
// *Action: If there are no database problems, increase the SQL_TIMEOUT value
//          using one of the following methods:
//          - Edit the setup file.
//          - At the command line, use an option such as -e SQL_TIMEOUT=120
//          The value indicates the number of seconds a database request can
//          run before being interrupted. A zero value disables any timeout.
// *Mnemonic: SQL_TIMEOUT
//
00503,0, "Cannot create the pipe"
// *Cause: RDA cannot create a communication pipe.
// *Action: Report the problem to Oracle Support. Include details about the
//          Perl version used (cf. Perl -V)
// *Mnemonic: PIPE_ERROR
//
00504,0, "Cannot fork"
// *Cause: A new process cannot be forked.
// *Action: Report the problem to Oracle Support. Include details about the
//          Perl version used (cf. Perl -V)
// *Mnemonic: FORK_ERROR
//
00505,0, "Cannot launch SQL*Plus"
// *Cause: RDA cannot launch SQL*Plus.
// *Action: Verify that SQL*Plus is available from the command line.
// *Mnemonic: NO_SQLPLUS
//
00506,0, "Cannot create the temporary SQL script"
// *Cause: RDA failed to create a temporary file with the SQL script.
// *Action: Check the permissions of the report directory.
// *Mnemonic: SQL_TEMP_ERROR
//
00507,0, "SQL Error"
// *Cause: RDA received an error when executing the SQL statements.
// *Action: Check the associated error message and take appropriate actions.
// *Mnemonic: SQL_ERROR
//
00508,0, "Null password given; logon denied"
// *Cause: An empty password was provided
// *Action: A password must be specified.
// *Mnemonic: NO_PASSWORD
//
00509,0, "Missing SQL code"
// *Cause: No SQL code was provided.
// *Action: Provide some SQL code.
// *Mnemonic: NO_SQL
//
00510,0, "SQL execution disabled"
// *Cause: The maximum number of tries has been reached.
// *Action: The execution of SQL statements is disabled due to a
//          connection test error or too many timeouts. If there are
//          no database problems, increase the SQL_TIMEOUT value using one
//          of the following methods:
//          - Edit the setup file.
//          - At the command line, use an option such as -e SQL_TIMEOUT=120
//          The value indicates the number of seconds a database request can
//          run before being interrupted. A zero value disables any timeout.
// *Mnemonic: SQL_DISABLED
//
00511,0, "Cannot create the remote directory"
// *Cause: RDA failed to create the remote directory in the report directory.
// *Action: Check the permissions and ownership of the report directory.
// *Mnemonic: REM_DIR_CREATE_FAIL
//
00512,0, "Cannot create the remote log file"
// *Cause: RDA cannot create the remote log file in the remote directory.
// *Action: Check the permissions and ownership of the remote directory in the
//          report directory.
// *Mnemonic: REM_LOG_CREATE_FAIL
//
00513,0, "Missing remote shell command"
// *Cause: RDA cannot find a remote shell command (ssh, rsh, or remsh).
// *Action: Check the PATH environment variable or define a reference to
//          an alternative tool with the REMOTE_SSH_COMMAND and 
//          REMOTE_SSH_OPTIONS settings.
// *Mnemonic: REM_NO_SSH
//
00514,0, "Missing remote file copy command"
// *Cause: RDA cannot find a remote file copy command (scp or rcp).
// *Action: Check the PATH environment variable or define a reference to
//          an alternative tool with the REMOTE_SSH_COMMAND and
//          REMOTE_SSH_OPTIONS settings.
// *Mnemonic: REM_NO_SCP
//
00515,0, "Cannot access environment variables"
// *Cause: PERL_ENV_TABLES is not set correctly. When perl "-V" is executed, it
//         also produces an error: %RMS-F-SYN, file specification syntax error.
// *Action: Check that PERL_ENV_TABLES has well CRTL_ENV as the first element
//          in its value list and that all elements are valid.
// *Mnemonic: ENV_COPY_ERROR
//
00516,0, "Expecting an array or a hash variable as first argument"
// *Cause: The first argument is neither an array nor a hash.
// *Action: Verify that the first argument is an array or a hash.
// *Mnemonic: INVALID_ARRAY_HASH
//

// ///////////////////////////////////////////////////////////////////////////
//   00600.00699      Background Collection Errors (Daemon.pm)
// ///////////////////////////////////////////////////////////////////////////
//
00600,0, "Cannot create the daemon file"
// *Cause: RDA failed to create the background collection control file.
// *Action: Check if the current user can create a file in the directory where
//          the setup file is located or in the directory specified by the
//          RDA_PID environment variable, when defined.
// *Mnemonic: DMN_CREATE_CTL
//
00601,0, "Cannot redirect input"
// *Cause: RDA failed to redirect the standard input of the background process.
// *Action: Check that the current user can read from /dev/null.
// *Mnemonic: DMN_INPUT
//
00602,0, "Cannot redirect output"
// *Cause: RDA failed to redirect the standard output of the background process.
// *Action: If an output file has been specified, check that it can be
//          created. Otherwise, check that the current user can write to
//          /dev/null.
// *Mnemonic: DMN_OUTPUT
//
00603,0, "Cannot halt the background collection"
// *Cause: RDA failed to rename the background collection control file.
// *Action: If the file is still present, check the file permissions and owner.
// *Mnemonic: DMN_HALT
//
00604,0, "Cannot create the archive directory"
// *Cause: RDA failed to create the archive directory inside the report
//         directory.
// *Action: Check the permissions and ownership of the report directory.
// *Mnemonic: DMN_CREATE_ARC
//
00605,0, "Cannot create the ref directory"
// *Cause: RDA failed to create the ref directory inside the report directory.
// *Action: Check the permissions and ownership of the report directory.
// *Mnemonic: DMN_CREATE_REF
//
00606,0, "Cannot create the sample directory"
// *Cause: RDA failed to create the sample directory inside the report
//         directory.
// *Action: Check the permissions and ownership of the report directory.
// *Mnemonic: DMN_CREATE_SMP
//
00607,0, "Cannot change to the sample directory"
// *Cause: RDA failed to change the current directory to the sample directory.
// *Action: Check the path and the permissions of the sample directory. The
//          directory does not always exist before samples are collected.
// *Mnemonic: DMN_CD_SMP
//
00608,0, "Cannot list the samples"
// *Cause: RDA cannot open the sample directory.
// *Action: Check access to the samples.
// *Mnemonic: DMN_LS_SMP
//
00609,0, "Cannot change to the RDA install directory"
// *Cause: RDA failed to change the current directory to its install directory.
// *Action: Check the path and the permissions of the install directory.
// *Mnemonic: DMN_CD_HOME
//
00610,0, "Cannot zip the reports"
// *Cause: RDA detected an error when using zip to package the reports.
// *Action: Check for any other error reported by the zip command. Also check
//          the path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: DMN_ZIP_ERROR
//
00611,0, "Cannot package the reports using pax"
// *Cause: RDA detected an error when using pax to package the reports.
// *Action: Check for any other error reported by the pax command. Also check
//          the path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: DMN_PAX_ERROR
//
00612,0, "Cannot package the reports using tar"
// *Cause: RDA detected an error when using tar to package the reports.
// *Action: Check for any other error reported by the tar command. Also check
//          the path that is stored in the setup file, which is  used to
//          execute that command.
// *Mnemonic: DMN_TAR_ERROR
//
00613,0, "Archive command not -yet- identified"
// *Cause: RDA cannot find any packaging tool paths.
// *Action: The path to zip or tar commands has not been collected. This
//          typically occurs when the end report has not been produced yet
//          or if these commands have not been found in the current execution
//          path (cf. PATH).
// *Mnemonic: DMN_PKG_ERROR
//
00614,0, "Cannot package the reports using jar"
// *Cause: RDA detected an error when using jar to package the reports.
// *Action: Check for any other error reported by the jar command. Also check
//          the path that is stored in the setup file, which is used to execute
//          that command.
// *Mnemonic: DMN_JAR_ERROR
//
00615,0, "Cannot create the sample alias file"
// *Cause: RDA cannot create the alias file in the sample directory.
// *Action: Correct the permission problem and execute RDA again.
// *Mnemonic: DMN_ALIAS_CREATE
//
00616,0, "Cannot open the sample alias file"
// *Cause: RDA cannot open the sample alias file.
// *Action: Correct the permission problem and execute RDA again.
// *Mnemonic: DMN_ALIAS_CREATE
//

// ////////////////////////////////////////////////////////////////////////////
// Copyright Notice
// Copyright (c) 2002-2009, Oracle. All rights reserved.
//
// Trademark Notice
// Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of
// Oracle Corporation and/or its affiliates. Other names may be trademarks of
// their respective owners.
// ////////////////////////////////////////////////////////////////////////////