Oracle Report Errors

REP-0808: You must enter the Buffer Size.
Cause: In the Runtime Settings tab of the Tools Options dialog box,
you left the Buffer Size field blank. You must enter a value for Buffer
Size.
Action: Enter a Buffer Size value between 1 and 9999.
REP-0809: You must enter the Long Chunk Size.
Cause: In the Runtime Settings tab of the Tools Options dialog box,
you left the Long Chunk Size field blank. You must enter a value for
Long Chunk Size.
Action: Enter a Long Chunk Size value between 1 and 9999.
REP-0810: Valid options are 'Noaction', 'Rollback', or 'Commit'.
Cause: In the character-mode Runtime Settings dialog box, you chose
an invalid value for On Success/On Failure. Valid values
are Noaction, Rollback, or Commit.
Action: Select a valid value for On Success/On Failure.
REP-0811: Valid options are '<In Report Definition>', 'Screen', 'File',
'Printer' or 'Mail'.
Cause: In the character-mode Runtime Settings dialog, you chose an
invalid value for Destination Type. Valid values are <In Report
Definition>, Screen, File, Printer, or Mail.
Action: Select a valid value for Destination Type.
REP-0812: Valid options are '<In Report Definition>', 'Landscape',

or 'Portrait'.
invalid value for Orientation. Valid values are <In Report
Definition>, Landscape, or Portrait.
Action: Select a valid value for Orientation.
REP-0813: Valid options are '<In Report Definition>', 'Default',
'Bitmap' or 'Character'.
invalid value for Mode. Valid values are <In Report
Definition>, Default, Bitmap, or Character.
Action: Select a valid value for Mode.
REP-0814: Valid options are '<In Report Definition>', 'Yes' or 'No'.
Cause: In the character-mode Runtime Settings dialog box, you chose
an invalid value for Background. Valid values are <In Report
Definition>, Yes, or No.
Action: Select a valid value for Background.
REP-0815: Valid options are 'Landscape', or 'Portrait'.
Cause: In the character-mode Runtime Parameter Form, you chose an
invalid value for Orientation. Valid values are Landscape or Portrait.
Action: Select a valid value for Orientation.
REP-0816: Valid options are 'Bitmap' or 'Character'.

invalid value for Mode. Valid values are Bitmap or Character.
Action: Select a valid value for Mode.
REP-0817: Valid options are 'Yes' or 'No'.
invalid value for Background. Valid values are Yes, or No.
Action: Select a valid value for Background.
REP-0818: Warning: Page height has changed for Parameter Form.
Parameters might be crossed by page boundaries.
Cause: You changed the height of the Runtime Parameter Form in the
Report property palette. Report Builder is notifying you that this might
cause the page boundary to move such that it appears in the middle of
an object in the parameter form.
Action: Look at the layout of your parameter form in the Parameter
Form editor and ensure that none of the objects are directly on the page
boundary (the darkened line in the editor). Alternatively, you could
default (or redefault) the parameter form.
REP-0819: Could not turn AUTOCOMMIT ON for SQL Server
connection.
Cause: This is an abnormal condition.
Action: For information, see Abnormal Conditions. Another option is to

remove all instances of SRW.DO_SQL. If you can do so while retaining
all necessary functionality in your report, it will run.
REP-0820: Cannot import specified image.
Cause: The image you are trying to import cannot be imported.
Action: Check the image file to ensure it is a valid image and has not
been corrupted.
REP-0821: Cannot export specified image.
Cause: The object you are trying to export as an image cannot be
exported as an image.
Action: Create or select an image to export.
REP-0822: No drawing imported.
Cause: The drawing you are attempting to import cannot be imported.
Action: Check the file to ensure it is a valid drawing and has not been
corrupted.
REP-0823: No drawing exported.
Cause: The object you are attempting to export as a drawing cannot be
exported as a drawing.
Action: Create or select a drawing to export.
REP-0824: Data dictionary not available on the database to which

you are connected. Unable to retrieve table/column information.
Cause: You are attempting to access the Table and Column Names
dialog box but the Data Dictionary is not available on the database to
which you are connected.
Action: Connect to another database.
REP-0825: The connected database is not ORACLE or DB2. It
cannot be used to store report documents.
Cause: You are attempting to store a document to a database that is
neither ORACLE nor DB2. This is not allowed.
Action: Either connect to an ORACLE or DB2 database or store the
document as a file.
REP-0828: Report Builder tables are not installed in the database.
Cancelling Report Doc.
Cause: Report Doc cannot be run because there are no Report Builder
tables in the database.
Action: Inform your database administrator that Report Builder tables
were not successfully installed in the database.
REP-0829: Report Builder database tables appear to match the
tables from an older version of Report Builder (<Version>).
Cancelling Report Doc.
Cause: The Report Builder tables in the database appear to have been
installed from a previous version of the product. Report Doc cannot run
against an older version of the database tables.
for this version were not successfully installed in the database.
REP-0830: Report Builder database tables appear to be corrupted
or incorrectly installed. Cancelling Report Doc.
Cause: Report Doc cannot be run because the Report Builder tables
are in an unstable state.
are either corrupted or incorrectly installed in the database.
REP-0831: Query could not be built.
Cause: Report Builder was asked to build a query at startup but it failed.
One cause is that the database account against which the query was
being built was not correct. Otherwise it is an abnormal condition.
Action: If Report Builder was launched from another product check that
the database connection string in the other product is correct. For
information about abnormal conditions, seeAbnormal Conditions.
REP-0900: Cannot close this report while PL/SQL is still executing.
Cause: You attempted to close a report while associated PL/SQL was
still executing.
Action: Finish executing the PL/SQL or abort it, then close the report.
REP-0901: Tables and Columns function is not supported for this

database server.
Cause: You are connected to a database server which does not have
an accessible Data Dictionary to list tables and columns.
Action: None. Tables and Columns functionality is not available for
these databases.
REP-0910: The Cue Cards cannot be found. Please reinstall the
Cue Cards and try again.
Cause: You attempted to run the Cue Cards, but it has not been
properly installed.
Action: Reinstall the Cue Cards.
REP-0911: The Quick Tour cannot be found. Please reinstall the
Quick Tour and try again.
Cause: You attempted to run the Quick Tour, but it has not been
properly installed.
Action: Reinstall the Quick Tour.
REP-0999: Unimplemented Error:
Action: For information, see Abnormal Conditions.
REP-1010: This name does not conform to SQL naming standards.

Cause: The name you entered violates one or more SQL naming
conventions.
Action: Check the naming standards for the object you are naming. For
more information, see . Enter a name that conforms to the conventions.
REP-1011: <Object type> must be named.
Cause: You left the Name field blank for the object and a name is
required.
Action: Name the object according to the appropriate naming
conventions. For more information, see .
REP-1012: There is another <object type> with this name.
Cause: The name that you entered duplicates the name of another
object of the same type.
Action: Change the name of at least one of the objects.
REP-1013: This name may not be the same as a reserved word.
Cause: You entered a name for a parameter that duplicates a reserved
word.
Action: Change the name of the parameter such that it conforms to
parameter naming conventions. For more information, see .
REP-1014: Name length cannot exceed 30 bytes.
Cause: Name entered was greater than 30 bytes. Valid SQL names
cannot be longer than 30 bytes.
Action: Reduce the size of the name to 30 bytes or less.
REP-1048: Warning: Owner and Access list not overwritten.
REP-1049: Cannot open a report saved with a newer version of
Report Builder.
Cause: You tried opening a report with an older version of Report
Builder than the one with which the report was saved.
Action: Use the same or a more recent version of Report Builder to
open the report.
REP-1050: Unable to access document names in database.
REP-1051: Unable to save document to file '<filename>'.
REP-1052: Unable to save document to database.

REP-1053: Unable to obtain new document ID from database.
REP-1054: Unable to delete from table '<table name>'.
Cause: You tried to delete from a table and the operation failed. You
may not have the necessary privileges.
Action: Ensure that you have the necessary privileges. If you do not,
see your DBA or have someone with the necessary privileges perform
the operation.
REP-1055: Unable to lock table '<table name>'.
REP-1056: Unable to rename object stored in database.
Cause: You tried to rename a database object and the operation failed.
You may not have the necessary privileges. You must own an object in
order to rename it.
Action: If you do not own the object, you can either make your own
copy of it or have the owner change the name.
REP-1057: '<Filename>' is not a valid Report Builder file.
Cause: You tried to access a file that is not in the proper format for
Report Builder.
Action: Make sure you are accessing the correct file.
REP-1058: Unable to read document from database.
REP-1059: Unable to read document from file '<filename>'.
REP-1060: The Report Builder database tables have not been
installed.
Cause: Report Builder failed to access the SRW2_DOCUMENT view in
the current database.
Action: Check to see if Report Builder was properly installed on the
database. For help, contact your system administrator.
REP-1061: Unable to read external file '<filename>'.

Cause: You activated Read From File and specified a file name as the
value of a column, but Report Builder could not successfully open or
read the specified file.
Action: Check the spelling of the specified file in the Column property
palette, and check to see if the specified file exists. If the file does exist,
check the permissions on the file to ensure that you have at least read
access.
REP-1062: Unable to find external query '<filename>'.
Cause: The possible causes of this error include the following:
Case 1: REPORTS30_PATH is not set.
Case 2: You are not connected to a database.
Case 3: The specified external query does not exist.
Action: You can take the following actions to correct this error:
If Case 1: Set REPORTS30_PATH to a valid value.
If Case 2: Connect to a database.
If Case 3: Make sure you specify the correct name of the external query.
REP-1063: The PL/SQL '<program unit name>' has exceeded the
platform specific size limit.
Cause: The PL/SQL could not be loaded because it is too large for your
operating system. It may have been created on a different platform with
a higher limit.
Action: Reduce the size of the PL/SQL so it can be loaded on your

platform.
REP-1064: Unable to read document '<document name>'.
Cause: You attempted to open a document whose definition, stored in
either the database or the filesystem, has been lost or corrupted.
Action: This document cannot be used.
REP-1065: Unable to read external query '<filename>'.
Cause: You attempted to read an external query whose definition,
stored in either the database or the filesystem, has been lost or
corrupted.
Action: This external query cannot be used.
REP-1066: Warning: Comment is corrupted. It will be lost.
Cause: A storage error caused a comment to be corrupted. It will be
discarded.
Action: No action is necessary. If you want to, recreate the comment in
the designer.
REP-1067: Some information is missing in the report.
Cause: The report cannot be opened because the report definition is
incomplete. It may have been corrupted.
Action: If the report is stored in the database, use SQLPlus to

determine whether the Report Builder tables have been corrupted. If the
report is an .rdf file, use a file system utility to check if the file is
corrupted. Take appropriate actions to recover your data.
REP-1070: Error while opening or saving a document.
Cause: An error occurred while opening or saving a document.
Action: Check to make sure that you have proper access privileges for
the document.
REP-1071: Reached the end of an object/record scan.
REP-1072: Object was not found in the object store.
REP-1073: Object was found in the object store when not expected.
REP-1074: Object is too big.

REP-1075: Object is invalid.
REP-1076: Specified object store is invalid.
Cause: You attempted to use an invalid file or database object.
Action: Make sure the object you specified is a valid Oracle document,
stored in a file or in the database.
REP-1077: Type specified for the object is invalid.
REP-1078: Non-specific file error occurred.
REP-1079: Function is unsupported.

REP-1080: Unique key violation occurred.
REP-1081: Page split occurred.
REP-1082: Close error occurred.
REP-1083: File version error occurred.
REP-1084: File header is bad or missing.
Cause: You performed an operation that required Report Builder to
open a file. The file either didn't have a header or it didn't have the
expected header. The header may have been changed in an editor or
the file may not be compatible with this release of Report Builder.
Action: You can attempt to fix the header in an editor, although, in

general, it is not recommended that you edit Report Builder files in this
way. If the file is incompatible with this release of Report Builder, you
need to migrate it. For more information, see "Migrating Report Builder
and Printer Definitions" in the Report Builder Migration Manual.
REP-1085: File create error occurred.
Cause: You tried to perform an operation that required Report Builder to
create a file and an error occurred. You might not have the necessary
file privileges to create the file.
Action: Obtain the necessary privileges.
REP-1086: File open read-only error occurred.
open a file to which you do not have access. You might not have the
necessary file privileges to open the file.
Action: Obtain the necessary privileges for the file or, if possible,
access a file to which you do have the necessary privileges.
REP-1087: File open read-write error occurred.
open a file to which you do not have access. You might not have the
necessary file privileges to open the file.
access a file to which you do have the necessary privileges.
REP-1088: File write error occurred.

write to a file to which you do not have access. You might not have the
necessary file privileges to write the file.
access a file to which you do have write privileges.
REP-1089: File read error occurred.
read a file to which you do not have access. You might not have the
necessary file privileges to read the file.
access a file to which you do have read privileges.
REP-1090: File close error occurred.
REP-1091: Disk or file system is full.
Cause: You tried to save an object, but there wasn't enough space in
which to save it.
Action: You need to either delete some unnecessary files or expand
your storage space.
REP-1092: File unique key violation occurred.

REP-1093: Allocate failed.
REP-1094: Reallocate failed.
REP-1095: Free failed.
REP-1096: The <document type> is currently locked.
Cause: You tried to open a document that is already opened (locked) by
another user.
Action: Wait until the other user closes the document before accessing
it.
REP-1097: PRODUCT_USER_PROFILE or
SYSTEM.PRODUCT_PROFILE does not exist.
Case 1: The table does not exist.
Case 2: You do not have the necessary privileges to access the table.
If Case 1: If the table is not already created, create it.
If Case 2: Get access to the table by creating a public synonym for the
table in the PRODUCT_USER_PROFILE table, or by making the table
public via the PRODUCT_USER_PROFILE table.
REP-1098: Error reading PRODUCT_USER_PROFILE or
SYSTEM.PRODUCT_PROFILE data.
Cause: The table is not created correctly.
Action: Ensure that the table was created with the appropriate columns.
If it was not, then modify it as necessary.
REP-1099: Cannot open files not created with Report Builder.
Cause: You tried to open a file that is not a Report Builder report.
Action: Ensure that the file you are opening contains a Report Builder
report.
REP-1100: Your data model is invalid for this type of report.
Cause: You tried to create a default layout with a layout style that does
not match your data model.
Action: You can either change your data model to match the selected
layout style or select a different layout style to match your data model.
REP-1101: Group '<group name>' has invalid repeat direction.
Cause: You tried to create a default layout, but the selected layout style
requires a different repeat direction for one of your groups. Some layout
styles place restrictions on the repeat directions you can choose for your
groups.
Action: You can either change the repeat direction to meet the layout
style requirements or you can choose a different layout style.
REP-1102: Unable to fit default layout onto page of size <number>.
Cause: Report Builder tried to create the default layout you selected but
could not fit the entire layout on the page because the page is not wide
enough.
Action: If possible, increase the Page Width on the Report property
palette or rearrange objects such that the layout will fit on the page.
Otherwise, you may have to make the report multiple pages wide.
REP-1103: No column is selected in group '<group name>'.
Cause: While trying to create a default layout, you did not select a
column for a selected group. Consequently, Report Builder cannot build
a default layout because one or more of the dimensions of your layout
has no values.
Action: In the Report Wizard, select at least one column from each
selected group.
REP-1104: Page level summaries are not supported in defaulting.
Cause: You generated a default layout and it cannot fit within the given
amount of space. The possible causes of this error include the following:
Case 1: The layout you have generated is too large given the
dimensions specified in the Report Properties dialog box.
Case 2: The layout is too big given the size of the marked area in the
Layout Model editor.
If Case 1: Increase your report dimensions such that the layout can fit,
or alter the layout so that it will fit within the current dimensions.
If Case 2: Increase the size of the marked area.
REP-1106: Warning: no field generated for column '<column
name>'.
Cause: When you defaulted your layout, a field was not generated for
the column in the message. The most likely cause is that a summary
was not placed in the data model correctly. For example, you may have
specified the source of a summary column to be a column in a group
above the summary's group. This is not allowed.
Action: Debug your data model and redefault your layout.
REP-1107: Missing across or down group in cross product group

'<group name>'.
Cause: You attempted to create a default layout by selecting a Style
of Matrix in the Report Wizard, but all of the dimension groups of the
cross product group were assigned repeat directions of Down or Across.
Each repeat direction should be assigned to the dimension groups in the
cross product.
Action: Redisplay the Report Wizard and reassign the repeat directions
of the dimension groups, making sure that each direction is assigned
among the groups.
REP-1108: Cannot fit default layout even in region extending to
page boundaries.
Cause: You are attempting to default a layout that, if created using
current settings, would be too large to fit within the defined height and
width of a report page.
Action: Go back to the Report Wizard and reduce the values of default
settings (e.g., shorten some field widths). Alternatively, you can increase
the size of a report page using the Report property palette. Then
redefault your layout. Continue making adjustments as necessary.
REP-1109: Multiple group selection incompatible with single group
layout style.
Cause: You have selected more than one group to be defaulted but you
have also selected a defaulting style designed for a single group.
Action: Change your group selection so that only a single group is

selected. Alternatively change your selection of your layout style to one
that supports multiple groups.
REP-1110: Missing matrix across group in cross product group
'<group name>'.
of Matrix or Matrix with Group in the Report Wizard, but all of the
dimension groups of the cross product group were assigned repeat
directions of Down.
Action: Change the repeat direction of one of the cross product
dimension groups so that there is at least one Across group and
one Down group.
REP-1111: Missing matrix down group in cross product group
'<group name>'.
of Matrix or Matrix with Group in the Report Wizard, but all of the
dimension groups of the cross product group were assigned repeat
directions of Across.
Action: Change the repeat direction of one of the cross product
dimension groups so that there is at least one Down group and
one Across group.
REP-1112: Missing matrix cross product group in matrix report.

of Matrix or Matrix with Group in the Report Wizard, but have not
selected a cross product group to be used as the matrix group.
Action: Change the repeat direction of one of the cross product groups
to Matrix.
REP-1113: No groups or reports level columns have been selected.
Cause: While trying to create a default layout, you did not select any
groups or report level columns. Consequently, Report Builder cannot
build a default layout because one or more of the dimensions of your
layout has no values.
Action: In the Report Wizard, select at least one report level column or
a group that you wish to be defaulted.
REP-1114: Single group selection incompatible with multiple group
layout style.
Cause: You have selected a single group to be defaulted but you have
also selected a defaulting style designed for a multiple groups.
Action: Change your group selection so that more than one group is
selected. Alternatively, change your selection of your layout style to one
that supports single groups.
REP-1115: Unable to show full template layout because it does not
fit onto the page.
Cause: The template layout could not be shown properly because it is
too large to fit within the defined height and width of the report page. Not
being able to show the layout does not mean that your template is wrong
in any way.
Action: To show the template layout you can temporarily enlarge the
width and height of the report page. To do this, select the template in the
Object Navigator and open the Property Palette. Increase the Width and
Height properties under the Report node. Do not forget to reset the
width and height properties before you save your template.
REP-1200: Flow compilation failed.
REP-1201: Query text missing from query '<query name>'.
Cause: You named a query and tried to accept it, but you either did not
enter any SELECT statement for it or you entered something that did not
begin with the keyword SELECT. The SQL Query Statement dialog only
accepts SQL SELECT statements.
Action: Enter a SQL SELECT statement that begins with the word
SELECT (you may use upper or lower case). No other SQL statements
are accepted in the SQL Query Statement dialog.
REP-1202: ORACLE logon not specified.
Cause: You tried to run a report without having specified an ORACLE
logon.
Action: Enter a logon string in the Connect dialog box and accept the
dialog box before re-running the report.
REP-1203: Field '<field name>' references invalid column.

Cause: The column specified as the field's Source either is invalid or
does not exist.
Action: Select a column from the list of values.
REP-1204: Repeating frame '<frame name>' references invalid
group.
Cause: The group name you entered in the Group field of the Repeating
Frame property palette either is invalid or does not exist.
Action: Select a group from the list of values.
REP-1205: There is a loop in the positional dependency tree.
Cause: You have created explicit anchors such that an object is
indirectly anchored to itself. For example, if you anchored object A to
object B, object B to object C, and object C to object A, you would get
this error.
Action: You must remove at least one of the anchors that caused the
loop.
REP-1206: An Object is anchored to more than one other object.
Cause: In your layout, you have anchored an object to more than one
other object. An object may only be anchored to one other object.
Action: Eliminate the anchors to other objects such that the object is
anchored to only one other object.
REP-1207: The PL/SQL procedure for group filter of '<group

name>' is missing.
Cause: You entered Condition in Type on the Group property palette,
but you did not enter a valid filter.
Action: Enter a valid PL/SQL function or change the filter type.
REP-1208: Repeating frame of matrix '<matrix name>' cannot be
anchored.
Cause: You tried to run a report with an anchor from an intersecting
repeating frame of a matrix object to another object. You cannot do this.
Action: Delete the anchor. You cannot anchor this object to another
object.
REP-1209: Matrix object '<matrix name>' cannot be anchored.
Cause: You tried to run a report with an anchor from a matrix object to
another object. You cannot do this.
Action: Delete the anchor. You cannot anchor this object to another
object.
REP-1211: Object '<object name1>' is larger than its enclosing
object '<object name2>'.
Cause: An object is larger than its enclosing object. The most likely
cause is that you have attempted to enclose a large object within a
small, fixed frame.
Action: Identify the object and the enclosing object and adjust their
relative sizes and positions until the proper enclosure is achieved.
REP-1212: Object '<object name1>' is not fully enclosed by its
enclosing object '<object name2>'.
Case 1: An object is not fully enclosed by the page. That is, the object
extends beyond the page boundary.
Case 2: A repeating frame that forms a matrix is one or more layers
above a repeating frame that it contains. In a matrix layout, repeating
frames must be below repeating frames that they contain.
If Case 1: Move or resize the object so that it does not extend outside
the page boundary. Alternatively, increase the page size in the Report
property palette.
If Case 2: Using Arrange Send to Back, Arrange Bring to
Front, Arrange Move Backward, and Arrange Move Forward,
arrange your repeating frames such that, in terms of layers, the following
is true: repeating frames are below repeating frames that they contain
and down repeating frames are below across repeating frames.
REP-1213: Field '<field name>' references column '<column name>'
at a frequency below its group.
Cause: The source column for the field is in a group below that of the
repeating frame which encloses it.
Action: Move the field into a repeating frame whose source group is at
or above the group that contains the field's source column. Otherwise,
move the field's source column into the enclosing repeating frame's
group, if possible.
REP-1214: Repeating frame '<frame name>' is enclosed by a child
repeating frame.
Cause: The enclosed repeating frame's source group is above the
enclosing repeating frame's source group.
Action: In the editor, you can make the enclosed repeating frame the
enclosing repeating frame. Alternatively, you could, if possible, change
your group hierarchy such that the enclosed object's group is below the
enclosing object's group.
REP-1216: '<Object name>' has an illegal print condition.
Cause: You set an invalid Print Condition for the specified object. For
example, you might have tried to set the Print Condition of a margin
object.
Action: Change the Print Condition of the object to another, valid
setting.
REP-1218: '<Object name>' cannot page break before AND keep
with parent.
Cause: You set Page Break Before for an object as well as Keep with
Anchoring Object. The anchoring object, however, precedes the object
and therefore the two settings are in conflict.
Action: Uncheck Page Break Before or Keep with Anchoring Object.

REP-1219: '<Object name>' has no size -- length or width is zero.
Cause: In creating your layout, you created a layout object of zero width
or height.
Action: Enlarge the opject so that it has a non-zero height and width.
REP-1220: '<Object name>' has minimum widow lines greater than
max lines per page.
Cause: You have set Maximum Records per Page to a smaller value
than Minimum Widow Records. This causes a conflict between the two
settings and, in effect, indicates that no instances should be printed.
Action: Decrease Minimum Widow Records or increase Maximum
Records per Page.
REP-1222: Invalid body size.
Cause: You specified a body page width or height that is negative or out
of range. You most likely received this error after setting the page size to
an invalid value using the PAGESIZE executable argument.
Action: Enter a valid value using the PAGESIZE executable argument,
or adjust the body panel size by resizing the margins in the Layout
Model editor.
REP-1223: Invalid page size.
Cause: You specified a physical page width or height that is negative or

out of range. You most likely received this error after setting the page
size to an invalid value using the PAGESIZE executable argument.
Action: Enter a valid value using the PAGESIZE executable argument,
or change the physical page size setting in the Report property palette.
REP-1225: Invalid logical page size.
Cause: You specified a logical page height that is negative.
Action: Redefine your logical panel height to ensure that it is not
defined using a negative number.
REP-1226: Body location is beyond print area.
Cause: The body panel is not enclosed within the physical page.
Action: Adjust the body panel size by resizing the margins in the Layout
Model editor.
REP-1229: Between record value for repeating frame '<repeating
frame name>' is negative.
Cause: The value for Vertical Spacing and/or Horizontal Spacing
specified for a repeating frame is negative.
Action: Re-specify the appropriate Spacing setting for the repeating
frame identified in the error message.
REP-1230: Field '<field name>' has an invalid page reset group.
Cause: In the Reset At field of the Page Numbering dialog box, you
specified a repeating frame that does not enclose the layout field you
want to display the page number. You may have specified an invalid
repeating frame, or deleted the repeating frame after specifying it.
Action: Specify &Report or the name of a valid repeating frame as the
Reset At value for the page number field.
REP-1231: '<Object name>' has an invalid text wrap style.
REP-1232: Matrix '<matrix name>' has an invalid source frame.
Cause: You specified an invalid object as the source frame of the matrix
object, or the repeating frames you specified have invalid Print
Directions.
Action: Change the Print Direction of horizontal source repeating frame
to Down, and the Print Direction of the vertical source repeating frame
to Across.
REP-1233: The frames of matrix '<matrix name>' do not fully
intersect.
Cause: The repeating frames that form the matrix do not completely
intersect. For example, if you have two down repeating frames, two
across repeating frames, and one of the across repeating frames only
intersects completely with one of the down repeating frames, you would
get this error.
Action: Re-default the matrix layout, if possible, or move the repeating

frames that make up the matrix such that they fully intersect one
another.
REP-1234: Matrix '<matrix name>' position is not at the intersection
of its frames.
REP-1235: Error generating index for Cross Product.
REP-1236: Invalid query '<query name>'.
REP-1237: Invalid data link.
REP-1238: Invalid group '<group name>'.

REP-1239: Invalid column '<column name>'.
REP-1240: Invalid anchor.
REP-1241: Circular column dependency originating with column
'<column name>'.
Cause: You have created a column that directly or indirectly references
itself. For example, Column A might reference Column B which in turn
references Column A.
Action: Update or delete the column(s) to eliminate the circular
dependency.
REP-1242: Matrices must have all down frames below all across
frames.
Cause: In a matrix layout, down repeating frames must be below across
repeating frames.
Action: Using the Arrange-->Send to Back, Arrange-->Bring to
Front, Arrange-->Move Backward, and Arrange-->Move Forward,
arrange your repeating frames such that, in terms of layers, the following
is true: repeating frames are below repeating frames that they contain,
and down repeating frames are below across repeating frames.
REP-1243: Unimplemented type of summary specified in column
'<column name>'.
Cause: You specified a summary function that is not available.
Action: Specify a valid summary function
REP-1245: Wrong number of source columns for summary
function of column '<column name>'.
REP-1246: Chart document not found.
Cause: Report Builder cannot find the associated chart document for
the chart.
Action: Correct the file name and path of the chart document.
REP-1247: Report contains uncompiled PL/SQL.
Cause: You attempted to run your report before all referenced PL/SQL
constructs had been compiled.
Action: Compile the PL/SQL, then run your report.
REP-1248: All source columns of placeholder '<column name>'

must be in the same group.
Cause: You attempted to set the value of a placeholder column from
column(s) belonging to different groups.
Action: Change the placeholder column's group to match the group of
the column(s) changing the placeholder column's value.
REP-1249: Column '<column name>' has no PL/SQL formula.
Cause: You created a column of Type Formula with nothing in the
Formula field.
Action: Create a formula for the column or change the column's Type.
REP-1250: Circular query dependency.
Cause: Your report contains at least two queries, with each requiring
the other to be executed first.
Action: Edit one or more of your queries to remove the circular
dependency.
REP-1251: Circular query dependency originating with query
'<query name>'.
Cause: Your report contains at least two queries, with each requiring
the other to be executed first. The query listed in the message is one of
the conflicting queries.
Action: Edit the query listed or another conflicting query to remove the
circular dependency.
REP-1252: Matrix should be surrounded by a repeating frame on
group '<group name>'.
Cause: The data model for your report contains a matrix with a parent
group, but in the layout the repeating frame for the parent group either
does not exist or does not surround the matrix.
Action: Modify the layout of your report so that the parent group has a
repeating frame which surrounds the matrix.
REP-1253: Matrix objects are on different regions of the layout.
Cause: The repeating frames of a matrix are on different regions of the
layout (body, margin, header, or trailer).
Action: Move all repeating frames of the matrix to the same report
region.
REP-1254: Anchored objects are on different regions of the layout.
Cause: The anchoring and anchored objects of an anchor are on
different regions of the layout (body, margin, header, or trailer).
Action: Move the above-mentioned objects to the same report region.
REP-1255: Cannot anchor to a hidden object.
Cause: The anchored object of an anchor is a hidden object.
Action: Either make the anchored object not hidden, or delete the
anchor.
REP-1256: Link file boilerplate text is missing its source file.
Cause: You did not specify a filename in the Link File field in a link file
boilerplate object's property palette.
Action: Specify a directory path and filename in the Link File field in the
Link File Boilerplate property palette.
REP-1257: Cannot pass data for child query from caller.
Cause: You have invoked Report Builder from another product, and
Report Builder has been instructed to fetch data for a child query from
the caller. Data passed to Report Builder can only be for a master query.
Action: Modify the caller's instructions so that Report Builder does not
request data for a child query.
REP-1258: Group '<group name>' has no columns.
Cause: You have created a group that has no columns.
Action: Delete the group or assign one or more columns to the group.
REP-1259: Group '<group name>' has no break columns.
Cause: You have created a parent group that has no break columns.
Action: Mark the Break Order check box(es) of the break column(s) of
the group.
REP-1260: Groups '<group name1>' and '<group name2>' are from

the same query and cannot be linked.
Cause: You have a data link between two groups from the same query.
This is not allowed.
Action: Remove the data link or re-link to another group.
REP-1261: Cannot resolve parent of group '<group name>'.
Cause: One group has two queries as its parent (it can only have one).
Action: Remove data links from the same group to different queries.
REP-1262: Circular data link dependency starting from group
'<group name>'.
Cause: You have created a cycle with data links (i.e., you have specified
that a parent is the child of itself, either directly or indirectly).
Action: Remove at least one of the links in the cycle.
REP-1263: Cross product group '<group name>' has no or only one
dimension group.
Cause: You have a cross product group that has no or only one group
inside. Cross product groups must have at least two dimension groups.
Multi-query cross product groups must have at least two queries within
the cross product group.
Action: Remove the cross product group or add dimension groups, or
dimension queries (if multi-query).
REP-1264: Data link of group '<group name>' crosses cross

product boundary.
Cause: In your multiple-query matrix report, you have a query where
some of its groups are inside the cross product and some outside.
Action: Move all groups of the query to either outside or inside of the
cross product group.
REP-1265: Cross product group '<group name>' has no child
groups.
Cause: You have a cross product group with no child group, which is
required. The child group acts as the cell of the matrix.
Action: Create a child group for the cross product group.
REP-1266: Column '<column name>': Page Level columns are not
allowed in a Cross Product.
Cause: You have created a column in a cross product group that is or
relies on a column that is a page-level summary (i.e., a summary with
Reset At of Page).
Action: You cannot have a column in a cross product group that is or
relies on a page-level summary. You must remove the column from the
cross product group, or change the Reset At value of the column or the
page-level summary upon which it relies.
REP-1267: Chart '<display name>' references an invalid column as
a bind parameter.
Cause: The chart references a column that does not exist. This is an
abnormal condition.
REP-1268: Chart '<display name>' references a bind column
'<column name>' at the wrong frequency.
Cause: The column specified for the chart is in a group below that of
the repeating frame that encloses the chart.
Action: Move the chart into a repeating frame whose source group is at
or above the group that contains the specified column. Otherwise, move
the specified column into the enclosing repeating frame's group, if
possible.
REP-1269: Chart '<display name>' references an invalid report
group.
Cause: The report group specified for the chart does not exist. This is
an abnormal condition.
REP-1270: Chart '<display name>' references a report group at the
wrong frequency.
Cause: The report group specified for the chart is above the source
group of the enclosing repeating frame.
Action: Move the chart into a repeating frame with a source group that
is at or above its report group.
REP-1271: Chart column name '<column name>' has been multiply

specified in the chart document '<display name>'.
Cause: The specified chart column or parameter has been referenced
more than once in the chart document.
Action: Check the columns and parameters that you specify for the
chart and delete any duplicates.
REP-1272: Column '<column name>' may not be used as a Break
Column.
Cause: You specified a Break Order on a summary, function, or
placeholder. These types of columns cannot be used as break columns.
Action: Review the rules for which columns can be break columns. For
more information, see .
REP-1273: Source groups of matrix '<matrix name>' not from the
same cross product.
Cause: The source groups of the repeating frames that form the
dimensions of the matrix are not contained by the same cross product
group. The dimensions of a matrix must be contained within the same
Action: Change the source groups of the repeating frames or choose
different repeating frames to form the dimensions of the matrix.
REP-1274: Invalid repeat direction combination in matrix '<matrix
name>'.
Cause: Matrix dimension repeating frames whose source groups are in

the same "family" hierarchy (i.e., are descendants or ancestors of each
other) within a cross product group must have the same Print Direction.
Parent-child relationships within a cross product group are used to
create nesting in the matrix. As a result, the repeating frames associated
with such groups must print in the same direction on the page.
Action: Change the Print Direction of the repeating frames as
necessary, choose different source groups for the repeating frames, or
choose different repeating frames to form the dimensions of the matrix.
REP-1275: Page level column '<column name>' may not be
referenced from format trigger '<program unit name>'.
Cause: PL/SQL entered in Format Trigger cannot reference columns
with a Reset At or Compute At of Page.
Action: Remove the reference to the page-level column or change the
column's Reset At or Compute At to something other than Page.
REP-1276: Placeholder '<column name>' references one or more
non-formula columns.
Cause: A placeholder column contains SRW.REFERENCE, but the
column referenced is not a formula column. For placeholder columns,
SRW.REFERENCE must refer to a formula column.
Action: Change the column referenced via SRW.REFERENCE.
REP-1277: Invalid select element.

REP-1278: Invalid PL/SQL procedure in '<program unit name>'.
REP-1279: Invalid frame or repeating frame '<frame name>'.
REP-1280: Invalid field '<field name>'.
REP-1281: Invalid boilerplate '<boilerplate name>'.
REP-1282: Invalid matrix '<matrix name>'.
REP-1283: Invalid chart document '<display name>'.

REP-1284: Query '<query name>' has no groups.
Cause: Your data model contains a query that has no groups. Each
query in your data model needs at least one group associated with it.
Action: Create a new group for the query.
REP-1285: Query '<query name>' has no select elements.
Cause: Your data model contains a query that does not select anything.
Each query in your data model must select at least one element.
Action: Enter a SELECT statement in the query, selecting at least one
element.
REP-1286: Group '<group name>' is a cross product as well as a
dimension.
Cause: You specified a group to act as both a cross product group and
as a dimension group for another cross product group. This is not
allowed.
Action: Make the group either a cross product group or a dimension
group, but not both.
REP-1287: Cross product group '<group name>' should not have a

group filter.
Cause: You specified a group filter on a cross product group. This is not
allowed.
Action: Remove the group filter from the cross product group. Create
the group filter for another group, if necessary.
REP-1288: The numeric argument for group filter of '<group
name>' missing.
Cause: You specified First or Last for a group's filter, but you did not
specify a number dictating how many records the group should filter.
Action: Specify a number for the group filter.
REP-1289: Unimplemented type of group filter specified in group
'<group name>'.
Cause: You specified a group filter that is not available or is invalid.
Action: Specify a valid group filter for the group.
REP-1290 Source datatype incompatible with summary function in
column '<column name>'.
Cause: Your summary column was assigned a Source whose datatype
is incompatible with the specified Function. For example, you may be
trying to sum a character column.
Action: Make sure that the datatype of your source column is

compatible with the Function you specified in the Summary Column
property palette.
REP-1291: Column '<column name>' has invalid reset group.
Cause: You specified an invalid Reset At value for a summary column.
Reset At can be set to the same group as the summary column, any
group above the summary column's, Page, orReport.
Action: Specify a valid Reset At value for the summary column in its
property palette.
REP-1292: Column '<column name>' has invalid compute group.
Cause: You specified an invalid Compute At value for a summary
column. Compute At can be set to the same group as the summary
column, any group above the summary column's, Page, or Report.
Action: Specify a valid Compute At value for the summary column in its
property palette.
REP-1293: Column '<column name>' has invalid product order.
Cause: A column in a cross product group was assigned an invalid
value for Product Order, or no value at all.
Action: Specify a valid value for Product Order (consisting of only
dimension groups within the cross product) in the column's property
palette.
REP-1294: Width of column '<column name>' is too large.
Cause: The column's width exceeds the maximum allowed for your
operating system.
Action: Reduce the width of the column in the Column property palette.
REP-1295: Data format of column '<column name>' is unsupported.
Cause: You activated Read from File for a column, but specified an
invalid or unavailable data format in the Format field in the Column
property palette.
Action: Specify a valid data format in the Format field. The list of values
displays all valid data formats. Note that for LONG, RAW, and LONG
RAW database columns, only Text and Oracle Format (Image) are valid
values for Format.
REP-1296: Data link child cannot be in cross product group
'<group name>'.
Cause: You tried to link a column to a column in a cross product group,
or to the cross product group itself. These operations are not allowed.
Action: Create data links between columns and groups other than cross
product groups and their associated columns.
REP-1297: Data link child column '<column name>' must be a
database column.
Cause: You tried to link a column to another column that is not a
database column (e.g., a summary, formula, or placeholder column),
which is not allowed.
Action: You can create data links using only database columns and
groups.
REP-1298: Columns '<column name>' and '<column name>' have
incompatible types to be linked.
Cause: The parent and child columns in your data link have
incompatible datatypes that cannot be linked. For example, you might
have tried to link a Number column to a Character column.
Action: Make sure the parent and child columns you specify in data
links have compatible datatypes.
REP-1299: Groups '<group name>' and '<group name>' in different
cross products cannot be linked.
Cause: You tried to create a data link between dimension groups of two
different cross product groups, or between columns of the dimension
groups. These operations are not allowed.
Action: You cannot create data links between two different cross
product groups or their columns.
REP-1300: Text boilerplate '<boilerplate name>' has no contents.
Cause: You created a text boilerplate object that contains no text.
Action: Enter some text in the boilerplate object, or delete it.
REP-1301: Data link creates sibling of group '<group name>' within
cross product.
Cause: You created a data link that created a sibling of a dimension

group within a cross product group. No siblings of dimension groups are
allowed within the cross product.
Action: Dimension groups can consist only of chains of groups. No
siblings are allowed.
REP-1302: Cross product has two or more child groups.
Cause: A cross product group has more than one child group. Only one
child is allowed per cross product group.
Action: Remove all but one of the child groups to the cross product
group.
REP-1303: Query must be completely in or out of cross product
group '<group name>'.
Cause: You created a query whose groups are not all inside the cross
product, above the cross product, or below the cross product,
respectively.
Action: Make sure that each query's groups are all inside of a cross
product, above a cross product, or below a cross product.
REP-1304: Cross product group '<group name>' contains another
cross product as child.
Cause: You created a cross product group that is a child of another
cross product group. This is not allowed.
Action: Ensure that the child group of the cross product group is not a
REP-1305: Warning: Frame '<frame name>' intersects but does not

enclose object '<object name>'.
Cause: Your report layout contains a frame that does not completely
enclose the named object. Thus, the object is not considered to be
inside the frame.
Action: If you want the frame to enclose the object, resize or move the
frame.
REP-1306: Summary column '<column name>' has invalid source.
Cause: You specified an invalid source for the summary column. A
summary column's source must be from the same group as the
summary column, or from a group below the summary column.
Action: Change the source of the summary column to be from the same
group as the summary column or from a group below the summary
column.
REP-1307: Summary column '<column name>' has invalid product
order.
Case 1: You have a summary which is not a running summary (i.e., its
Reset At is not Report), but its Product Order is not a subset of the
source column's product order. The source column of the summary
must be at least as frequent as the summary, which means that the
summary's Product Order should be some subset of the source
column's Product Order.
Case 2: You have a running summary (i.e., its Reset At is Report) with a
Product Order that is not a prefix of the source column's Product Order.
For example, if the source column's Product Order were A,B,C, then the
summary column's Product Order would have to be either A (by itself) or
A,B. The summary's Product Order could not be B,A.
If Case 1: Change the Product Order of the summary such that it is a
subset of its source column's Product Order.
If Case 2: Change the Product Order of the summary such that it is a
prefix of the Source column's Product Order.
REP-1308: Placeholder column '<column name>' not supported in
cross product.
Cause: You tried to create a placeholder column inside of a cross
product group. Cross product groups cannot contain placeholder
columns.
Action: Delete the placeholder or move it outside the cross product
group.
REP-1309: Report level summary '<column name>' cannot be a
percent of total.
Cause: You created a summary at the report-level (i.e., a summary
outside of all the groups in the data model) with a Function of % of Total.
This Function makes no sense for a report-level summary because it will
always be 100%.
Action: Delete the summary or move it into a group where it will make
sense.
REP-1310: Boilerplate '<boilerplate name>' references '&<reference
name>' which is not a field.
Cause: A boilerplate object has a reference to a field that does not exist.
It could be that the field being referenced was deleted or renamed and
so this reference in the boilerplate object is now invalid.
Action: Depending on circumstances, you may want to remove the
reference, replace it with a reference to another field, or create the field
that it references.
REP-1311: Object '<object name>' with page-dependent references
changed to fixed sizing.
Cause: A field or boilerplate object has a reference to a page
calculation or a total number of pages variable. (This is known as a
forward reference.) Such layout objects must be fixed in size both
horizontally and vertically.
Action: The layout object's Horizontal and Vertical Sizing have been set
to Fixed by Report Builder. Check the output to ensure that the values
are not being truncated. If they are, you should enlarge the layout object
so that it is large enough to contain the values.
REP-1312: Page Level column '<column name>' may not be
referenced from chart '<display name>'.
Cause: One of the Report Builder columns that you tried to pass to a
chart is or depends upon a page-level summary (i.e., a summary with a
Reset At or Compute At of Page). A column being passed to a Chart

cannot be or depend upon a page-level summary.
Action: Do not pass the column to the Chart.
REP-1313: Page Level column '<column name>' may not be
referenced from group filter '<group name>'.
Cause: One of the Report Builder columns that you tried to reference in
a group filter is or depends upon a page-level summary (i.e., a summary
with a Reset At or Compute At of Page). A column referenced by a
group filter cannot be or depend upon a page-level summary.
Action: Do not reference the column in the group filter.
REP-1314: Format trigger '<program unit name>' references
column '<column name>' at wrong frequency.
Cause: One of your format triggers references a column that is located
at the wrong frequency.
Action: Remove the reference to the column from the format trigger.
REP-1315: Group filter '<program unit name>' references column
'<column name>' at wrong frequency.
Cause: One of your group filters attempted to reference a column that is
inaccessible.
Action: Remove the reference to the column from the group filter.
REP-1316: <Object name> references column '<column name>' at

wrong frequency.
Cause: A procedure or function attempted to reference a column that is
inaccessible.
Action: Remove the reference to the column from the PL/SQL
subprogram.
REP-1317: Boilerplate '<boilerplate name>' references field with
source '<column name>' at wrong frequency.
Cause: The boilerplate object references the field using &fieldname, but
the two objects are not located at the same frequency. For example, the
boilerplate object and the field it references are located within different
repeating frames.
Action: Place the boilerplate object and field at the same frequency, or
remove the reference.
REP-1318: Error while setting transaction read-only.
Cause: Having specified READONLY=YES, this error occurred at the
start of report execution, while ending the current transaction (with a
COMMIT) and starting the read-only transaction, or at the end of report
execution, while ending the read-only transaction (with a COMMIT).
Action: Make sure you are connected to a database, and make sure
that no cursors or locks were left pending by the previous transaction.
REP-1319: Warning: Implicit anchoring algorithm cannot uniquely

identify the anchoring object of '<object1 name>'. Arbitrarily
choosing '<object2 name>'.
Cause: The specified object (object name 1) is in the "push path" of two
objects and it is equidistant from both objects. As a result, Report
Builder cannot use its normal criteria (shortest distance) to determine
the implicit anchor. In the absence of its normal criteria, Report Builder
randomly creates an implicit anchor to the specified object (object name
2). Note that the implicit anchor may vary between runs of the report.
For more information, see .
Action: To avoid the random creation of an implicit anchor, explicitly
anchor the specified object (object name 1) to another object.
REP-1320: Program unit '<program unit name>' references column
with invalid ID: <column ID>.
Cause: You ran a report with invalid PL/SQL (e.g., PL/SQL that didn't
compile). The PL/SQL source included a column reference that cannot
be resolved.
Action: Check the column references in your PL/SQL source, recompile
all of the PL/SQL source in the report, and re-run the report.
REP-1322: Page break after on '<object name>' has no effect.
Cause: You activated Page Break After on an object that has no other
objects anchored to it (implicitly or explicitly). In this case, Page Break
After has no effect and is invalid. Notice that this is a warning, not an
error message.
Action: Deactivate Page Break After for the object.
REP-1323: Cannot have output columns in format trigger

'<program unit name>'.
Cause: In the format trigger for the specified object, you attempted to
set the value of a Report Builder column parameter. For example, you
can use the value of a column called COUNT1 in a condition (e.g., IF
:COUNT1 = 10), but you cannot directly set its value in an assignment
statement (e.g., COUNT1 = 10).
Action: Remove the assignment statement from the format trigger.
REP-1324: Cannot have output columns in group filter '<group
name>'.
Cause: In the filter for the specified group, you attempted to set the
value of a Report Builder column or parameter. For example, you can
use the value of a column called COUNT1 in a condition (e.g., IF
:COUNT1 = 10), but you cannot directly set its value in an assignment
statement (e.g., COUNT1 = 10).
Action: Remove the assignment statement from the group filter.
REP-1325: Cannot have output columns in Between Page Trigger.
Cause: In the Between Page trigger, you attempted to set the value of a
Report Builder column or parameter. For example, you can use the
value of a column called COUNT1 in a condition (e.g., IF :COUNT1 =
10), but you cannot directly set its value in an assignment statement
(e.g., COUNT1 = 10).
Action: Remove the assignment statement from the group filter.
REP-1326: <trigger name> writes to column '<column name>' at

wrong frequency.
Cause: In a report trigger, you attempted to set the value of a Report
Builder column at the wrong frequency in the report. You can reference
and set only report-level columns or parameters, and you cannot
reference or set any page-dependent columns (i.e., Reset At of Page) or
columns that rely on page-dependent columns.
Action: Make sure the columns and parameters whose values you
reference or set are report-level columns and parameters.
REP-1327: Column '<column name>' writes to column '<column
name>' at wrong frequency.
Cause: In a formula column, you attempted to set the value of a Report
Builder column at the wrong frequency in the report. You can reference
and set only columns that are in the same group or in a higher group in
the group hierarchy. For example, a formula for a report-level column
can only reference other report-level columns.
Action: Make sure the columns whose values you reference or set are
in the same group or in a higher group in the group hierarchy.
REP-1328: Cannot run report containing ROWLABEL column
'<column name>' in a non-trusted OS.
Cause: You are attempting to run a report that requires a secure
database while connected to a non-secure database.
Action: Run the report while connected to a secure database.
REP-1329: Column '<column name>' cannot be linked to column

'<column name>' because the child column is not a database
column.
Cause: You created a dat link in which the child column is a summary,
formula, or placeholder column. Only database columns can be linked.
Action: Create a data link using database columns.
REP-1330: Lexical parameter '<parameter name>' in query '<query
name>' must not change column dependencies.
Cause: You created a lexical parameter that changes the number, type,
or names of columns, or introduces new dependencies on computed
columns or new bind references, when the report is run.
Action: Change the lexical parameter so that it does not change
columns or introduce new dependencies or bind references.
REP-1331: Column '<column name>' cannot be linked to column
'<column name>' because the child column is determined by a
lexical parameter.
Cause: You created a dat link in which child column's value is
determined by a lexical parameter. This is not allowed.
Action: Replace the child column of the data link with another column.
REP-1332: Group filter for '<group name>' cannot reference
column '<column name>'. It is not a valid database column or it
depends on a related query.
Cause: You created a group filter that references a database column not
in the group's query or in a query above it, or references a computed
column that depends on an unrelated column.
Action: Remove the offending reference from the group filter.
REP-1333: Unsupported layout; a matrix may not be inside another
matrix.
Cause: You created a matrix layout nested within another matrix layout.
Action: Matrix layouts cannot be nested within other matrix layouts. Redesign your layout to avoid this.
REP-1335: Warning: variable rotated text '<boilerplate name>'
treated as fixed/contract width.
Cause: Your report contains a boilerplate text object which was rotated
to an angle that is not a multiple of 90 degrees, although both Horizontal
and Vertical Elasticity values were set toVariable or Expand. In this
case, the Horizontal Elasticity is treated as Fixed (if you
specified Expand) or Contract (if you specified Variable), and this
warning is displayed.
Action: You may want to change the Horizontal and Vertical Elasticity
values for this boilerplate object.
REP-1336: The source of field '<field name>' is Page Level
calculation '<column name>'. <group name>.
Cause: The specified field references a page summary owned by the

named group, but there is no repeating frame for that group that
surrounds the field.
Action: Create a repeating frame whose Source is the named group to
surround the field. If such a repeating frame already exists, extend it to
enclose the field.
REP-1337: Boilerplate '<boilerplate name>' references field '<field
name>', whose source is Page Level calculation '<column name>'.
<group name>.
Cause: The specified boilerplate object references the specified field,
whose Source is a page-level computation. However, there is no
repeating frame (whose Source is the named group) surrounding the
field.
Action: Create a repeating frame whose Source is the named group to
surround the field. If such a repeating frame already exists, extend it to
enclose the field.
REP-1338: Column mode not allowed on repeating frame '<frame
name>'.
Cause: You activated Column Mode for a repeating frame whose setting
do not satisfy either of the following conditions:
Print Direction of Down and a Vertical Elasticity of Fixed.
Print Direction of Across and a Horizontal Elasticity of Fixed.
Action: Change the Print Direction or Vertical/Horizontal Elasticity of the
repeating frame, or deactivate Column Mode.
REP-1339: Chart '<display name>' missing data column

specification.
Cause: You specified a value for the chart Query, but no columns to be
passed from the report to the chart document.
Action: If you do not want to pass data from the report to the chart
document, then specify nothing for chart Query and Source. If you do
want to pass data, then specify the columns to be passed in addition to
chart Query and Source.
REP-1340: Cannot match passed-in columns with report definition
of '<report name>'.
Cause: This error occurs when another component (e.g., Form Builder)
passes a query to Report Builder and there is a mismatch between the
columns passed and the columns expected by Report Builder. Possible
causes of this error include:
Case 1: Report Builder is expecting more or fewer columns than the
number that was actually passed by the calling application.
Case 2: The parameter list of the calling application describes a column
differently than what Report Builder expects. For example, if the report's
query selects a character column and the calling application assigns
that column a date datatype, this error will be raised.
If Case 1: Ensure that the calling application is passing the same
number of columns that Report Builder is expecting.
If Case 2: Ensure that the datatypes and names of the columns being
passed by the calling application match the dataypes and names in the
report.
REP-1341: Warning: Data truncation possible in column '<column
name>'.
Cause: The database column's width in the report is defined to be less
than its width in the database. This can occur when the columns in the
database are updated subsequent to the creation of the report definition.
Action: Force the query to be reparsed. One method is to type a space
at the end of a line in the SELECT Statement field and then accept the
SQL Query Statement dialog.
REP-1342: Type of data link to query '<query name>' illegal for non
ORACLE server.
Cause: If you create a data link with the START WITH clause and run it
while connected to a non-ORACLE database, you will get this error.
START WITH is only supported by ORACLE.
Action: Remove the data link that uses START WITH or connect to
ORACLE.
REP-1343: Invalid button '<button name>'.
REP-1344: Button '<button name>' has no action source file.
Cause: You have specified an action of Multimedia File for the named
button, but have either not specified a source file, or specified a source
file that does not exist.
Action: Open the property palette for the specified button and verify that
you have chosen a valid file as source for the button action. For more
information, see .
REP-1345: Button '<button name>' has invalid source column.
Cause: You have specified an action of Multimedia Column for the
named button, but have either not specified a source column, or
specified an invalid source column.
Action: Open the property palette for the specified button and verify that
you have chosen a valid column as source for the button action. For
more information about user-created buttons, see .
REP-1346: Button '<button name>' references source column
'<column name>' at wrong frequency.
Cause: The column specified in the property palette for the named
button is in a group below that of the repeating frame that encloses the
button.
Action: Move the button into a repeating frame whose source group is
at or above the group that contains the specified column. Otherwise,
move the specified column into the enclosing repeating frame's group, if
possible.
REP-1347: Button '<button name>' has invalid icon file.
Cause: You have specified either an invalid file or a nonexistent file as

the icon file for the button face.
Action: Ensure that your icon file exists and is of the proper format and
uncorrupted.
REP-1348: Source column of field '<field name>' is in sound or
video format.
Cause: You have specified a column containing sound or video as the
source for a field, but fields cannot display sound and video.
Action: Specify another column (not sound or video) as source of the
field.
REP-1349: PL/SQL action missing from button '<button name>'.
Cause: The PL/SQL trigger that serves as the specified button's action
references a piece of PL/SQL that does not exist.
Action: Debug your trigger and ensure that it references a valid
program unit.
REP-1350: Cannot have output columns in action trigger '<program
unit name>'.
Cause: The PL/SQL trigger that serves as a button action contains a
bind variable that returns a value. A PL/SQL action trigger cannot return
a value.
Action: Remove the bind variable from your PL/SQL.
REP-1351: Warning: Icon '<icon name>' on button '<button name>'

not found.
Cause: The icon you specified as the button face for the named button
cannot be found. The report will run, but the button will appear blank.
Action: Open the property palette for the named button and verify that
the icon you specified exists and is in the correct format, and that you
have included the correct path information.
REP-1352: The fonts specified for this report cannot be found for
the character set specified by NLS_LANG.
Cause: The NLS_LANG environment variable specifies a character set
for which no font is available.
Action: You may choose a font that exists in the character set specified
by NLS_LANG. Alternatively, you may use the Font Alias file to force an
available font to be used instead of the one specified in the report.
REP-1353: Web property of layout object '<layout object name>'
references field or column '<field or column name>' at wrong
frequency.
Cause: One of the layout object properies: Bookmark, Action, Hyperlink,
or Linktag references the field or column &columnname, but the two
objects are not located at the same frequency. For example, the layout
object is located within a repeating frame whose source is a different
group to that the column is in.
Action: Place the layout object in a repeating frame at the same
frequency as the column object, or remove the reference.
REP-1354: Web property of layout object '<layout object name>'

references page-dependent field or column '<field or column
name>'.
Cause: One of the layout object properies: Bookmark, Action,, Hyperlink
or Linktag references a field boilerplate object that has a reference to a
page calculation or a total number of pages variable. Web properties
may only reference columns and fields that are not based on page
calculations.
Action: Remove the web property reference to the page-dependent
field or column.
REP-1400: Couldn't initialize coxr.
REP-1401: '<program unit name>': Fatal PL/SQL error occurred.
REP-1402'<program unit name>': Unhandled PL/SQL exception.
REP-1403: '<program unit name>': Illegal to suspend PL/SQL

procedure.
Cause: A PL/SQL construct was suspended during execution or
generation.
Action: Debug and re-compile your PL/SQL constructs.
REP-1404: Compile failed for some reason.
Cause: In generating your report, PL/SQL compilation failed.
Action: Debug your PL/SQL constructs.
REP-1405: Code is not executable.
Cause: A PL/SQL construct did not compile properly or for some other
reason could not be executed.
Action: Debug your PL/SQL constructs.
REP-1406: Cannot run parameterized code directly.
REP-1408: Cannot initialize PL/SQL.

Oracle Report Errors

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Oracle Report Errors

Diunggah oleh

Hak Cipta:

Format Tersedia

REP-0808: You must enter the Buffer Size.

REP-0812: Valid options are '<In Report Definition>', 'Landscape',

REP-0816: Valid options are 'Bitmap' or 'Character'.

Action: For information, see Abnormal Conditions. Another option is to

REP-0824: Data dictionary not available on the database to which

REP-0901: Tables and Columns function is not supported for this

REP-1010: This name does not conform to SQL naming standards.

REP-1052: Unable to save document to database.

REP-1061: Unable to read external file '<filename>'.

Action: Reduce the size of the PL/SQL so it can be loaded on your

Action: If the report is stored in the database, use SQLPlus to

Cause: This is an abnormal condition.

Action: For information, see Abnormal Conditions.

Action: You can attempt to fix the header in an editor, although, in

REP-1088: File write error occurred.

REP-1092: File unique key violation occurred.

REP-1107: Missing across or down group in cross product group

Action: Change your group selection so that only a single group is

Cause: You attempted to create a default layout by selecting a Style

REP-1203: Field '<field name>' references invalid column.

REP-1207: The PL/SQL procedure for group filter of '<group

Action: Uncheck Page Break Before or Keep with Anchoring Object.

Cause: You specified a physical page width or height that is negative or

Action: Re-default the matrix layout, if possible, or move the repeating

Action: For information, see Abnormal Conditions.

REP-1248: All source columns of placeholder '<column name>'

REP-1260: Groups '<group name1>' and '<group name2>' are from

REP-1264: Data link of group '<group name>' crosses cross

REP-1271: Chart column name '<column name>' has been multiply

Cause: Matrix dimension repeating frames whose source groups are in

Action: For information, see Abnormal Conditions.

REP-1283: Invalid chart document '<display name>'.

REP-1287: Cross product group '<group name>' should not have a

Action: Make sure that the datatype of your source column is

Cause: You created a data link that created a sibling of a dimension

REP-1305: Warning: Frame '<frame name>' intersects but does not

Reset At or Compute At of Page). A column being passed to a Chart

REP-1316: <Object name> references column '<column name>' at

REP-1319: Warning: Implicit anchoring algorithm cannot uniquely

REP-1323: Cannot have output columns in format trigger

REP-1326: <trigger name> writes to column '<column name>' at

REP-1329: Column '<column name>' cannot be linked to column

Cause: The specified field references a page summary owned by the

REP-1339: Chart '<display name>' missing data column

Cause: You have specified either an invalid file or a nonexistent file as

REP-1351: Warning: Icon '<icon name>' on button '<button name>'

REP-1354: Web property of layout object '<layout object name>'

REP-1403: '<program unit name>': Illegal to suspend PL/SQL

Anda mungkin juga menyukai