One of the RPT commands does not have enough arguments, or contains a carriage return. For example, a macro with no name:

.DEFINE SELECT empno, ename
INTO empno, ename
FROM emp
..

This error indicates that a variable has been declared or a macro has been defined with an illegal name. The rules for naming variables and macros are on p.59.

This error indicates that a label has been used which has an illegal name. The rules for naming statement labels are on p.59.

This error will oclearcase/" target="_blank" >ccur if a two periods (..) are found on a line by themselves, outside of a macro. This indicates the completion of a macro definition. (p.101-2)

This error will occur if the report uses the same label name more than once in the same procedural macro. Since label definitions are local, the same label name may be used in different macros. Also, only the first 30 characters of an identifier name are significant. (p.59,115)

This error will occur if the report uses the same macro name in more than one DEFINE statement. Also, only the first 30 characters of an identifier name are significant. (p.59)

This error will occur if, in a REPORT or EXECUTE statement, the same SQL macro is called recursively.

This message has obvious meaning.

More than one variable with the same name have been declared in the report. Also, only the first 30 characters of an identifier name are significant. (p.59)

This error will occur if a DIV statement attempts to divide a number by zero, which is undefined. (p.123)

Legal display formats for DECLARE statements are found on p.96-99. Check for typos.

Legal display formats for DECLARE statements are found on p.96-99. Check that alphanumeric variables are not declared as more than 255 characters.

This may occur if the report has an IF statement where the expression contains blank characters, but is not enclosed within double quotation marks. For example, .if &counter = 1 then label1 (p.117)

The statement refers to a variable that has not been declared correctly (using a DECLARE statement) within the report, or you have used a literal value where a variable was expected. For example: .EQUAL counter 1 (the SET command should be used to do this). Also, this error will occur if a label is used outside of a procedural macro. Be sure to check for typos. (p.95-9, 115)

This error, along with RPT-0073, will occur if the report uses the SET statement incorrectly. For example:

.SET variable1 variable2.

This error occurs if a macro definition is not ended by two periods (..) on a line by themselves. This may also cause errors RPT-0011 and RPT-0035 to occur. (p.101-2)

The syntax of the IF statement is incorrect. Make sure that all program variable names are preceeded with an ampersand.

This could be caused by a number of errors in the SQL statement of a select macro. Try running the SQL statement in SQL*Plus to determine what is causing this error. Also, check that the select macro only contains the text of the SQL query and nothing else (for example, a Table (#T) command).

This error occurs if an EXECUTE statement attempts to execute a macro that is not defined in the report. Check for typos. (p.105-6)

Try breaking up the SQL statement. The limit in version 1.0 is 2000 characters and the limit in version 1.1 is 10,000 characters.

This error will occur if the select macro is missing an INTO clause. (p.102-4) For select macros using set operations (Union, Intersect, or Minus) refer to p.60 for the correct usage of an INTO clause. Also, in version 1.1.5, this error will occur if a column in the select list has the word "FROM" as part of its name.

This error will occur if a REPORT statement contains a body macro which has not been defined in the report.

This error will occur if the report is disjunctive (where two or more select macros are specified in one REPORT statement joined by ANDs or ORs) and more than 4 select macros have been specified. (p. 112)

This error will occur if the report is disjunctive (the <SELECT macros> argument to the REPORT statement is enclosed within double quotes), but is missing an AND or an OR. (p.112, 114)

There are a number of causes for this error. Look for typos, such as references to macros with different spellings.

Indicates that a STOP statement was encountered in the report.

These messages indicate where the error probably occured.

See RPT-0026.

These messages indicate that an Oracle error has occured.

The following error will occur: conversion error: Month must be between 1 and 12 if a date variable is 'asked' for, but the month is not between 1 and 12.

The following error will occur: conversion error: Year must be between 00 and 99 if a date variable is 'asked' for, but the year is not between 00 and 99.

The following error will occur: conversion error: Day must be between 1 and last of month if a date variable is 'asked' for, but the day is not between 1 and the last of month.

Usage is: RPT inputfile outputfile user/password options

Options are:
-n   Number of open cursors (e.g., -n10 for 10 cursors)
-?   Display RPT version
-x   eXecute report even if syntax errors are found
-a   Number of rows per array_fetch (e.g., -a20 for 20 rows)
-o   format numbers using Old RPT formatting rules

These messages will appear, along with RPT-0066, RPT-0074, and RPT-0075, if the syntax on the RPT command line is incorrect. (p.57)

This message tells you the version of the ORACLE database that the report is using.

The input file specified on the RPT command line does not exist or cannot be opened. Check for typos. (p.57)

These messages have obvious meaning. Normally, you do not need to worry about the number of lines in the interim file.

Indicates that the report program has been terminated, because errors have occured.

Try increasing the number of open cursors. See p.32 and p.231 of the ORACLE Database Administrator's Guide 5.1.

The following error will occur: conversion error: Date format must match date type if a date variable is 'asked' for, but the format of the input is not MM/DD/YY. (p.126)

See RPT-0023.

This error will occur, in version 1.1.8, if the select macro is missing an INTO clause. (p.102-4)

This error will occur, in version 1.1.9.4, if the data of the variable in a .set is greater than the format width defined for the column it is to be printed. The data will be truncated.