Help topic not found.  Check the online help index for related topics.


Connecting to a database

To connect to a database, use one of the following methods:

•	Explicit login

•	Automatic login

•	Remote login


Running a report from Reports Runtime

  Related Topics

To run a .rep file (a runfile) or an .rdf file (a report definition file) from Reports Runtime:

1	Connect to a database.

2	(Optional) Specify parameter values in the Runtime Options dialog box.

3	Choose File [image] Run.

4	In the file selection dialog box, search for the report name and open it.

5	If the Runtime Parameter Form appears, type or select parameter values, then click [image] in the toolbar.

6	View the report output in the Previewer.


Running a report from the command line

  Related Topics

To run a .rep file (a runfile) or an .rdf file (a report definition file) from the command line:

1	Type ORACLE_HOME\BIN\RWRUN60, followed by the report name and desired arguments.

2	If you ran the report in batch mode, and sent the output to a file (DESTYPE=file DESNAME=filename BATCH=yes), open or print the file to verify the output.


Running a report using a command file

  Related Topics

To run a .rep file (a runfile) or an .rdf file (a report definition file) using a command file:

1	Create a text file using a word processor of your choice.

2	Type ORACLE_HOME\BIN\RWRUN60, followed by the report name and desired arguments.

3	If you ran the report in batch mode, and sent the output to a file (DESTYPE=file DESNAME=filename BATCH=yes), open or print the file to verify the output.


Specifying parameter values using the Runtime Options dialog box

To specify parameter values using the Runtime Options dialog box:

1	Choose Edit [image] Runtime Options to display the Runtime Options dialog box.

2	Change settings as desired.

3	Click OK.


Viewing report output in the Previewer

  Related Topics

To view your report output, you can use any of the following Previewer features:

•	scrolling and paging

•	splitting horizontally and vertically

•	magnifying or reducing the output

•	opening multiple Previewers


Scrolling and paging through report output

To move around pages of the report using the scroll bars and paging buttons:

•	Use the mouse cursor to drag the horizontal and vertical scroll bars to move around the current page.

•	Click [image], [image], [image], and [image] in the toolbar to display the indicated pages of the report.

•	To display a specific page, enter the page number in the Page field.


Splitting the Previewer horizontally and vertically
Splitting horizontally and vertically

To create two views of the report output by splitting the Previewer screen, either horizontally or vertically:  Note

1	Drag the box above the vertical scroll bar (to split horizontally), or to the left of the horizontal scroll bar (to split vertically).

2	Release the mouse button at the position you want to split the viewing region.

You can scroll and page within each view to move the contents of that view while the other view remains unchanged.


You cannot split the viewing region horizontally and vertically simultaneously.


Magnifying or reducing the output

To magnify a hard-to-see portion of your report or reduce the image to get a sense of your report's overall layout:

•	To magnify the output displayed in the viewing region, click [image] in the toolbar.

•	To reduce the size of the output display, click [image] in the toolbar.


Opening multiple Previewers

To open a new Previewer window with the same contents as the current one:

•	Click [image] in the toolbar.


Printing a report from the Previewer

  Related Topics

To print a report:

1	Click [image] in the toolbar to verify your printer setup.

2	If the Previewer is displayed, click [image] in the toolbar.

3	In the dialog box, type the number of pages and copies you want to print.

If you ran the report with a DESTYPE of Screen, a warning appears that you should run the report with a DESTYPE of Preview before printing.  Preview creates PostScript output, which is typically more desirable for printing bit-mapped reports.

4	Click OK.


Using a printer definition file

To use a printer definition (used only when running a report on a character-mode platform):

1	Set the DESFORMAT system parameter to the name of the printer definition file.

2	Set DESTYPE to Printer and DESNAME to the name of the printer.


Emailing a report in batch mode

  Examples	  Related Topics

To email a report in batch mode:  Note

1	Log onto your mail system using your mail client application (i.e., start up Microsoft Exchange).

2	Run the report from the command line, specifying BATCH =yes, DESTYPE=mail, and DESNAME=recipient1,recipient2,recipient3,etc.


Emailing a report from Reports Runtime

  Examples	  Related Topics

To email a report from Reports Runtime without first previewing it:

1	Log onto your mail system using your mail client application (i.e., start up Microsoft Exchange).

2	If you are not already connected, connect to a database.

3	Choose File [image] Mail.

4	In the file selection dialog box, search for the report name and open it.

5	In the Runtime Parameter Form , set Destination Type to Mail; leave the value for Destination Name blank.

6	Click [image] in the toolbar.

7	In the mail dialog box, specify the recipients and subject line for your email report.

To email a report from Reports Runtime after first previewing it:

1	Log onto your mail system using your mail client application (i.e., start up Microsoft Exchange).

2	If you are not already connected, connect to a database.

3	(Optional) Specify parameter values in the Runtime Options dialog box .

4	Choose File [image] Run.

5	In the file selection dialog box, search for the report name and open it.

6	In the Runtime Parameter Form , set Destination Type to Preview; leave the value for Destination Name blank.

7	Click [image] in the toolbar.

8	View the report output in the Previewer .


You can also choose File [image] Mail if you do not want to view the report before emailing it.


Ending a session

To end your Reports Runtime session:

1	If the report is displayed in the Previewer, click [image] in the toolbar.

2	Choose File [image] Exit.


About parameters

You use the system parameters and user parameters displayed on the Runtime Parameter Form to control the running of your reports.  You can specify such details as where you want the report sent, the national language in which you want it to appear, the conventions used to format certain fields, and the number of copies you want printed.


About system parameters

System parameters are common to all reports.  However, the report developer is able to prevent the appearance of any or all of the parameters on the Runtime Parameter Form.  You are not able to override such a design decision, although you can specify a new value for the parameters.  Eleven system parameters are generated by Report Builder; if the default values for any of these do not need to be changed, the report developer does not need to include them on the Runtime Parameter Form.

Each system parameter has an equivalent keyword you can use with RWRUN60, and an equivalent option you can specify in the Runtime Options dialog box .


About user parameters

User parameters are created by the report developer to enable you to change the limits or range of data used in a report.


About batch reporting

  Related Topics

If you do not need to examine report output in the Previewer (e.g., you may have to generate large volumes of output from a fully-tested report or run several reports in succession), you can run your report in batch.  This leaves you free to pursue other tasks while your reports are running.

You can run reports in batch mode from the command line, or use a command file to specify arguments.  A command file can save you a great deal of typing if you wish to run several reports using the same set of arguments.


About MAPI

On Windows 95 and Windows NT, you can email your reports via the Microsoft Messaging Application Programming Interface (MAPI).

MAPI support enables you to send your report output via electronic mail to other users on your system. Bitmapped (default) reports are sent as email attachments in encapsulated PostScript format.  Character-mode reports are sent as ASCII text attachments.

Prerequisites:  You must have an appropriate MAPI mail client application, such as Microsoft Exchange, installed with either Windows 95, Windows for Workgroups 3.11, or Windows NT.  For further information, see your operating system documentation to learn how to configure your machine for email capability.


About database roles

Database roles provide a way for you to run reports that query tables to which you do not have access privileges.  Without database roles, you are unable to run these reports.

If a table requires special access privileges, you cannot run a report that retrieves data from that table if you don't have the required privileges.  However, if a database role is defined for the report by the report developer, you can run the report  if you have been granted privileges for that role.  When running multiple reports, Reports Runtime automatically switches to the role defined for the current report.


To run a report for which a database role is defined, you must run the .rdf file, not the .rep file.


A standalone or plug-in reader, such as the Adobe Acrobat Reader, that enables you to display your PDF file.


Runtime Parameter Form

The Runtime Parameter Form is a dialog box where you can set parameter values for report execution.  When enabled (i.e., PARAMFORM=YES), the Runtime Parameter Form appears right after you choose File [image] Run.  In the Runtime Parameter Form, you can specify such things as a printer name, an email ID, the number of copies to be made, and values for bind and lexical parameters at runtime.

Note:  The report developer is also able to specify that the Runtime Parameter Form not appear.  You are not able to override such a design decision.


Previewer

  Related Topics

When you run a report, you can send its output to several places, one of which is the Previewer (DESTYPE=SCREEN or DESTYPE=PREVIEW).  In the Previewer, you can scroll though a single page of report output, page through the entire report, and split the screen to view different sections of the same report concurrently.

A physical page (or panel) is the size of a page that will be output by your printer.  A logical page is the size of one page of your actual report (it can be any number of physical pages wide or long).  The Previewer displays the logical pages of your report output, one at a time.

Using the Previewer, you can:

•	Drill down to detailed reports:  A report can include buttons with PL/SQL actions attached to them.  For example, the report developer could use the packaged procedure SRW.RUN_REPORT to define an action for a button that calls another report.  This second (or detail) report appears in its own, modal Previewer.  There is no limit to the number of levels you can drill down in this way.

•	Access multimedia objects:  A report can include buttons for multimedia objects (e.g., video or sound), which you can invoke by clicking the buttons in the Previewer.

•	Open OLE2-compliant applications:  If OLE2 objects are included in your report, you can double-click these objects in the Previewer to open the associated server application.  (Note if the object is linked, its source object is displayed.)


Runtime Options dialog box

  Related Topics

The Runtime Options dialog box enables you to specify most RWRUN60 arguments.  The settings you specify in the Runtime Options dialog box are not saved with the report, but will affect the report until you either change the settings or log out of your Reports Runtime session.

•	Runtime Values

•	Runtime Settings

Note that there is no corresponding setting in the dialog box for several of the keywords, including the REPORT, BATCH, CMDFILE, or USERID keywords.  These items are not necessary in an interactive environment.

The Runtime Options dialog box is useful when you need to run several reports that have some common settings.


Runtime Values

Description  Runtime Values specifies values that are used when you run reports during the current session.  (To permanently change the default values of these settings for a particular report, the report developer must update the Initial Value of the appropriate parameters in the report definition.)

Background	BACKGROUND

Copies	COPIES

Currency Symbol	CURRENCY

Decimal Indicator	DECIMAL

Destination Format	DESFORMAT

Destination Name	DESNAME

Destination Type	DESTYPE

Mode	MODE

Orientation	ORIENTATION

Print Job	PRINTJOB

Thousands Separator	THOUSANDS


Runtime Settings

  Restrictions

Description  Runtime Settings specifies settings used when you run reports during the current session.  (To permanently change the default values of these settings for a particular report, the report developer must update the Initial Value of the appropriate parameters in the report definition.)

Array Size	ARRAYSIZE

Auto Commit	AUTOCOMMIT

Blank Pages	BLANKPAGES

Buffers	BUFFERS

Error FIle	ERRFILE

Long Chunk	LONGCHUNK

Non-blocking SQL	NONBLOCKSQL

On Failure	ONFAILURE

On Success	ONSUCCESS

Page Width x Height	PAGESIZE

Parameter Form	PARAMFORM

Profile	PROFILE

Read Only	READONLY

Role	ROLE

Run Debug	RUNDEBUG


Runtime Settings restrictions

•	Any values specified in the Runtime Settings tab take precedence over values specified on the command line, and initial values saved with the report definition.  However, you can still modify settings in the Runtime Parameter Form (e.g., Destination Type, Destination Format, Currency, etc.).


Connect dialog box

Description  The Connect dialog box enables you to connect to an Oracle or non-Oracle datasource.  You can type in each field separately or you can type any of the following connect strings all in User Name:

username[/password]

username[/password][@database]

[user[/password]]@ODBC:datasource[:database] or [user[/password]]@ODBC:*

This dialog box contains:

Database	Is the name of the database to which you want to connect.  Enter a valid database string not to exceed 256 bytes.  This value can be the name of a local database, a communication protocol that enables you to access a remote database, or an ODBC datasource name (if accessing a non-Oracle datasource).  The communication protocol you enter depends upon your operating system.  For more details, refer to your SQL*Net documentation for your system and/or consult your DBA.

Password	Is the string you use to confirm your identity.  Enter a valid password not to exceed 30 bytes.

User Name	Is the name you use to connect to the database.  Enter a valid username not to exceed 512 bytes.  It might be different from the username you use to log on to your computer.


Delimited Output dialog box

  Related Topics

Description  The Delimited Output dialog box defines preferences for delimited report output.

This dialog box contains:

Delimiter

Date Format Mask

Number Format Mask

Cell Wrapper


Delimiter

  Related Topics

Description  Delimiter is a value that specifies what character(s) separate cells in your delimited report output.

Values

Tab	means a tab separates each cell
,	means a comma separates each cell
:	means a colon separates each cell
;	means a semicolon separates each cell
|	means a vertical bar separates each cell
?	means a question mark separates each cell
$	means a dollar sign separates each cell
.	means a period separates each cell
Space	means a space separates each cell
Return	means a new line separates each cell
any alphanumeric character or string of alphanumeric  characters	means the character(s) you type in the textbox separates each cell
Default

Tab

Usage Notes

You can also use escape sequences based on the ASCII character set


Date Format Mask

Description  Date Format Mask specifies how the date values display in your delimited report output.

Values

any valid date format mask

Default

none

Usage Notes

•	You can only use this option if you’ve selected a delimiter

The format mask only applies to date data.


Number Format Mask

Description  Number Format Mask specifies how the number values display in your delimited report output.

Values

any valid number format mask

Default

none

Usage Notes

•	You can only use this option if you’ve selected a delimiter.

•	The format mask only applies to all number data in your report output.


Cell Wrapper

Description  Cell Wrapper is a value that specifies what character(s) display around each cell of your delimited report output.

Values

None	means no cell wrapper
"	means a double quote displays on each side of the cell
‘	means a single quote displays on each side of the cell
Space	means a space displays on each side of the cell
any alphanumeric character or string of alphanumeric  characters	means the character(s) you type in the textbox displays on each side of the cell
Default

none

Usage Notes

•	You can only use this option if you’ve selected a delimiter.

•	You can also use escape sequences based on the ASCII character set.


Distribution dialog box

  Related Topics

Description  The Distribution dialog box enables you to specify multiple destinations for report and/or section output and delete destinations from the distribution list.

This dialog box contains:

Distribution List	list the destinations in the distribution list for the current report or section.
Distribution ID	is an identifier for a destination.
DESNAME	is the name of the path and file, printer, or email ID (or distribution list) to which the report output will be sent.  Note:  If you specify a file, the directories in the path must already exist.
	Default repname repnamem reponameh repnamet	for report for main section for header section for trailer section
DESFORMAT	is the destination format, or the printer driver to be used when DESTYPE is FILE.
	Values
	BITMAP	specifies bitmap format, as displayed in the builder, which can be sent to a printer.
	HTML	specifies HTML format that can be read by an HTML 3.0 compliant browser.
	HTMLCSS	specifies HTML format that can be read by an HTML 3.0 compliant browser that supports cascading style sheets.
	PDF	specifies PDF format that can be read by a PDF viewer.  PDF output is based upon the currently configured printer for your system.  The drivers for the currently selected printer is used to produce the output; you must have a printer configured for the machine on which you are running the report.
	ASCII	specifies character (ASCII) format, which can be sent to a MAPI-compliant e-mail application.
	RTF	specifies RTF format that can be read by standard word processors (such as Microsoft Word).
	Default BITMAP
DESTYPE	is the type of destination device that will receive the report output
	Values
	FILE	specifies a file (named by DESNAME).
	MAIL	specifies e-mail (mail IDs identified by DESNAME).  You can send mail to any mail system that is MAPI-compliant or has the service provider driver installed.  The report is sent as an attached file.
	PRINTER	specifies a printer (named by DESNAME).
	Default FILE
COPIES	is the number of copies to distribute.
New	adds the distribution definition in the Settings section to the Distribution List and opens a new line for a new distribution definition.
Remove	removes the selected distribution definition from the Distribution List.
Remove all	clears the Distribution List.


MAPI (Windows) email example:  recipients by first and last names
Email example

Following is an example of specifying email recipients by first and last names when emailing a report in batch mode:  Note

RWRUN60 monthly.rdf USERID=scott/tiger DESTYPE=mail DESNAME="John Robertson,Mary Johnson,Anne" BATCH=yes


MAPI (Windows) email example:  recipient with apostrophe in name
Email example

Following is an example of specifying an email recipient whose name includes an apostrophe (O'Hara) when emailing a report in batch mode:  Note

RWRUN60 monthly.rdf USERID=scott/tiger DESTYPE=mail DESNAME="John,Tim O''Hara,Mary Johnson,Anne" BATCH=yes


MAPI (Windows) email example:  recipients by first and last names
Email example

Following is an example of specifying email recipients by first and last names:  Note

"John Robertson,Steve Johnson,Paul"


MAPI (Windows) email example:  recipient with apostrophe in name
Email example

Following is an example of specifying an email recipient whose name includes an apostrophe (O'Hara):  Note

"John,Tim O''Hara,Steve Johnson,Paul"


Oracle*Mail (UNIX) email example:  multiple recipients
Email example

Following is an example of specifying multiple email recipients:  Note

(JROBERTS, SJOHNSON, PHARVEY)


With BATCH=yes, the subject line and cc list are blank.  To specify the subject line and cc lists, you must run the report interactively from Reports Runtime.


Enclose email IDs in double quotes and separate them with commas.


Use two single quotes for "O'Hara".


Enclose email IDs in parentheses and separate them with commas


Executable names

  Related Topics

Letters are appended to the executable names listed above to indicate if the GUI mode of the executable is something other than the native GUI.  For example, "a" indicates a GUI mode of Apple MacIntosh and "m" a GUI mode of Motif.  (No added letter means the executable's GUI mode is the native GUI.)  In addition, an "x" is used to indicate if user exits are linked to the executable.


Executable invocation

  Related Topics

Executables can be invoked in one of two ways:

•	by command line

•	by double-clicking the executable’s icon

Executable Arguments  When you invoke an executable, you can enter executable arguments that govern how the executable behaves.  If you invoke the executable via command line, you enter the executable arguments on the command line after the executable name.


Help on command line options

  Related Topics

If you are on a command line, you can view an executable's command line options by typing the executable's name, then a space and a question mark, and then pressing Return.  For example, rwrun60 "?".

Note:  Some operating systems require quotes around the question mark.  For example, to view the command line options for the RWRUN60 executable in the UNIX C shell, you need to enter rwrun60 "?".


Executable syntax restrictions

  Related Topics

•	When you enter an executable on the command line, it generally has the form shown below:

executable_name  keyword1=value1  keyword2=value2 ...

•	If your operating system does not have a command line available (e.g., Apple Macintosh or Windows) and you invoke the executable via icon, an intermediary dialog box may appear where you can enter values for the executable arguments or you may need to use the Runtime Values and Runtime Parameters tab on the Preferences dialog box (Tools [image] Preferences) for executable arguments.

•	Each keyword=value is called an executable argument.  Because it would be cumbersome to enter the keywords each time, they may be omitted.

•	No spaces should be placed before or after the equal sign of an argument.

•	Separate arguments with one or more spaces; do not use commas to separate arguments.

•	Values of arguments may be in single or double quotes.  The effect of single or double quotes is operating system-specific.

•	The keyword= part of all arguments is not case sensitive.  The value portion of the SOURCE, DEST, CMDFILE, TERM, DESNAME, DESFORMAT, DNAME, and SNAME arguments may be case sensitive, depending on your operating system.  The value portion of all other arguments is not case sensitive.

•	Keywords may sometimes be omitted.

•	To pass a single quote from the command line, you must enter two quotes (one quote as an escape and one as the actual quote).  For example:

rwrun60 module=myrep destype=file desname=run.out batch=yes
p_value="Roy''s Batch Report"

To pass a parameter value with a single quote in it using the Forms RUN_PRODUCT packaged procedure, you must enter four single quotes (PL/SQL collapses two quotes to one and so does Reports).  For example, if you wanted to pass the following literal value to an Reports' parameter:

where '='

you would enter the following string in RUN_PRODUCT:

'where ''''='''''

•	To give an argument an empty string as its value, you enter keyword= or keyword="".  If you enter an empty string in this way, the Runtime Parameter Form will display an empty string for the argument instead of its Initial Value.

•	Full pathnames are supported for all file references (e.g., desname=/revenues/q1/nwsales).  If you do not specify the full path, the file path search order is used to find the file.  Note: To help ensure the portability of your reports, you can use the environment variable REPORTS60_PATH for referencing reports, external queries, external PL/SQL libraries, text files, graphics, etc.  REPORTS60_PATH enables you to access files stored outside of Report Builder or Reports Runtime without hardcoding directory paths into your report.

•	Values entered from the Runtime Parameter Form override those entered on the command line.  For example, if you specified RWRUN60 on the command line with COPIES equal to 1, but, in the Runtime Parameter Form, specified COPIES equal to 2, then two copies of the report would be generated.

Similarly, values entered on the command line override values specified in command files.  For example, suppose that you specify RWRUN60 from the command line with COPIES equal to 1 and CMDFILE equal to RUNONE (a command file).  In RUNONE, COPIES is set to 2 by a RWRUN60 command.  Only one copy of the report would be generated in this case.

You can specify values for DESTYPE, DESNAME, DESFORMAT, ORIENTATION, and COPIES in a number of different places.  The following list shows the order of precedence for the places where you specify these values.  The first item in the list takes precedence over all others, the second takes precedence over all but the first item, and so on:

•	Print Job dialog box

•	Runtime Parameter Form

•	Runtime Parameters/Settings tab of Tools Options or Runtime Options dialog box

•	keywords on the command line

•	values specified in the report definition

•	Choose Printer dialog


Keyword usage

The keyword= part of each argument is optional as long as the arguments are entered in the order specified by the syntax.  If you skip one of the arguments, you must use keywords after the skipped argument.

If an executable has four arguments and you want to specify only the first, second, and fourth arguments, you can specify the first two without the keywords.  The fourth would require a keyword, though, because you are not entering it in the order specified by the syntax.

Examples (Valid):

Below are examples of valid command line sequences:

rwrun60 userid=scott/tiger paramform=no destype=mail
  desname=rmiller

rwrun60 scott/tiger no destype=mail desname=rmiller

Notice that, in this example, after the keyword DESTYPE is used all subsequent arguments use keywords, too.  Once you have entered a keyword, the rest of the arguments on the command line must also use keywords.

Examples (Invalid):

Below are examples of invalid command line sequences:

rwrun60 paramform=no scott/tiger destype=mail
  desname=rmiller

The sequence above is invalid because scott/tiger has been typed out of order and without the USERID keyword.

rwrun60 scott/tiger mail rmiller no

The sequence above is invalid because the value NO has been entered out of order and without the PARAMFORM keyword.


Database logon

  Related Topics

You can connect to a database in the following ways:

•	Explicit logon

•	Automatic logon

•	Remote logon


Explicit logon

You explicitly login to the database by using the USERID keyword, or by choosing File [image] Connect.


USERID

Description  USERID is your ORACLE username and password with an optional database name, Net8 communication protocol to access a remote database, or ODBC datasource name (if accessing a non-Oracle datasource.

For more information about the optional Net8 communication protocol, see "Remote Logon".  For more information about automatic logon, see "Automatic Logon".

Values

The database connection string must be in one of the following forms and cannot exceed 512 bytes in length:

username[/password]

username[/password][@database]

[user[/password]]@ODBC:datasource[:database] or [user[/password]]@ODBC:*


Automatic logon

The ORACLE automatic logon feature allows you to connect to the database without explicitly stating a username and password.

When you connect in this way, ORACLE uses a default logon (e.g., OPS$) to associate your ORACLE username to your operating system username.  To invoke an automatic logon procedure, do one of the following:

•	Type rwconv60 / on the command line.

•	Type a slash (/ ) in the logon screen as your username.

•	Omit your username/password on the command line and press the Return or Enter key twice when the logon form appears.

Note:  When logging on in this way, you can access a remote logon by typing @database after the slash.

For more information on default logons, see the ORACLE8 Server SQL Language Reference Manual.


Remote logon

Through Net8, you can specify a remote database (i.e., one not on your computer).  When you use the remote logon feature, the remote database is transparent to you.  Refer to the Oracle Net8 documentation  for more information.

Usage Notes

•	To perform a remote connect, you must have an account on the remote computer node where the target database resides.


About error messages

Each component has a unique error message prefix:

Prefix	Component
FRM	Form Builder
OG	Graphics Builder
PDE	Procedure Builder
REP	Report Builder
BRW	Query Builder
BRS	Schema Builder
NX, XBD	Translation Builder
Note:  On UNIX, Report Builder sets the value of the $status variable that appears in some messages to be 0 (successful completion) or 1 (unsuccessful completion).

In addition to the Forms Developer or Reports Developer error messages, you may encounter error messages from other sources:

Prefix	Source	Help
ORA	Oracle Server	Oracle8 Error Messages manual
PLS	PL/SQL	Oracle8 Error Messages manual
NET	SQL*Net	Oracle Network Products Messages manual
The Oracle8 Error Messages manual contains error message codes and descriptions for all database utilities such as SQL*DBA, SQL*Loader,SQL*Module,Export, Import, and the Oracle Precompilers.

System-specific error messages are documented in your operating system documentation.


Calling Oracle Support Services

Some errors (that is, internal errors) will require that you call Oracle Support Services to report the error.  When you call Support Services, please have the following information at hand:

1	Your name, company, and Oracle Support ID number.

2	The hardware, operating system, and release number of the operating system you are using.

3	The complete version number of the component you were using when you encountered the error, including revision number and port release number, if any.  (If you are unsure of the component's version number, choose Help [image] About.)

4	All other products (and version numbers) in use when you encountered the error (for example, Oracle 8.0.4).

5	If you encountered one or more error messages, the exact message numbers and descriptions, in the order they appeared.

6	A description of the problem, including any unusual conditions.

7	The problem severity, according to the following codes:

•	1:  Program not usable.  Critical impact on operations.

•	2:  Program usable.  Operations severely restricted.

•	3:  Program usable with limited functions.  Not critical to overall operations.

•	4:  Problem circumvented by customer.  Minimal effect, if any, on operations.


Abnormal conditions

Sometimes you may encounter an error that is known as an abnormal condition, which may arise from one of the following causes:

•	Someone has done something that prevented your application from completing the requested task.  For example, if someone bypassed the user interface and changed data in a database table, they might have typed an invalid value.

•	A software bug prevented the requested task from completing.

Action   First contact your system administrator to determine if the message was caused by something other than Forms Developer or Reports Developer.  If you determine that the message was not the result of user error or a system problem, then contact Oracle Support Services.


REP-0001:  Unable to find the Report Builder message file.  Please verify your installation.

Cause:	The file of error messages could not be opened or an internal error occurred while opening it.
Action:	Attempt to reinstall Report Builder or contact Oracle Customer Support for assistance.


REP-0002Unable to retrieve string from message file.
REP-0002:  Unable to retrieve string from message file.

Cause:	Report Builder could not retrieve the necessary error message or string.
Action:	Contact Oracle Customer Support for assistance.


REP-0003Warning: Unable to open global preference file.
REP-0003:  Warning: Unable to open global preference file.

Cause:	The global preference file could not be opened.  This is just a warning, so the product will continue to run even if this occurs.  The possible causes of this error include the following:
	Case 1:	The file was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the file named prefs.ora is stored in the appropriate directory.  For more information, your installation instructions, or contact your DBA.
	If Case 2:	Make sure that you have the privileges necessary to access the file.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0004Warning: Unable to open user preference file.
REP-0004:  Warning: Unable to open user preference file.

Cause:	Your local (customized) preference file could not be opened.  This is just a warning, so the product will continue to run even if this occurs.  The possible causes of this error include the following:
	Case 1:	The file was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the file prefs.ora is located in your "home" directory (if your system has such a concept as home directory).  If it is not, change the directory and/or filename as appropriate.
	If Case 2:	Make sure that you have the privileges necessary to access the file.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0005Warning: Syntax error at line <line number> in global preference file.
REP-0005:  Warning: Syntax error at line <line number> in global preference file.

Cause:	One or more of the preferences in the global preference file was specified incorrectly on the line number shown in the message.  The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified.  As a result, Report Builder will ignore the incorrectly specified preferences.
Action:	You or your DBA should edit the global preference file and ensure that all preferences are correctly specified.  If they are not, make the necessary updates.


REP-0006Warning: Syntax error at line <line number> in user preference file.
REP-0006:  Warning: Syntax error at line <line number> in user preference file.

Cause:	One or more of the preferences in the user preference file was specified incorrectly on the line number shown in the message.  The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified.  As a result, Report Builder will ignore the incorrectly specified preferences.
Action:	You should edit the global preference file and ensure that all preferences are correctly specified.  If they are not, make the necessary updates.


REP-0007Unable to write user preference file.
REP-0007:  Unable to write user preference file.

Cause:	You tried to save preferences and the user preference file could not be written.  The possible causes of this error include the following:
	Case 1:	You lacked the necessary privileges to write the file.
	Case 2:	A system error made it impossible to write the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that you have the privileges necessary to write the file.  If you don't, change your privileges accordingly.
	If Case 2:	Consult your operating system documentation or contact your system administrator.


REP-0008Unexpected memory error while initializing preferences.
REP-0008:  Unexpected memory error while initializing preferences.

Cause:	This is an abnormal condition.
Action:	For information, see Abnormal Conditions.


REP-0058:  Data passing to remote Reports Server not supported.

Cause:	You have specified passing a record group to a report that is being run remotely.
Action:	If you are passing a record group, you cannot specify a Reports Server.


REP-0059Unable to locate resources for subcomponent '<component name>'. Check the location of resource file.
REP-0059:  Unable to locate resources for subcomponent '<component name>'. Check the location of resource file.

Cause:	One of the subcomponents of Report Builder could not locate its resource file.  Possible causes of this error include:
	Case 1:	The resource file doesn't exist.
	Case 2:	The resource file is in the wrong place.
	Case 3:	The environment is not configured properly.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that the resource files are present.
	If Case 2:	Make sure that the resource files are in the proper directory.
	If Case 3:	Make sure that your environment is set correctly.  On Unix, make sure that the proper environment variable is set, and on MS Windows check the file system registry.


REP-0060Unable to run synchronous job concurrently with another report.
REP-0060:  Unable to run synchronous job concurrently with another report.

Cause:	You are trying to run a report initiated by the Form Runtime executable and requiring data passed from that tool, but one or more other reports are running or queued to run.  Reports requiring passed data must be run immediately.
Action:	Wait for all other reports currently listed in the Reports Server queue to run, then try your report again.


REP-0061Internal error - rxmobfree: reference count is zero.
REP-0061:  Internal error - rxmobfree: reference count is zero.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0062Internal error - rxmobnew: size mismatch.
REP-0062:  Internal error - rxmobnew: size mismatch.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0063Internal error - rxmobnew: memory manager mismatch.
REP-0063:  Internal error - rxmobnew: memory manager mismatch.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0064Internal error - rxmobnew: type mismatch.
REP-0064:  Internal error - rxmobnew: type mismatch.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0065Virtual Memory System error.
REP-0065:  Virtual Memory System error.

Cause:	Report Builder has encountered a memory error.
Action:	Make note of the error-specific code and contact Oracle Customer Support.  For more information, see Calling Oracle Customer Support.


REP-0066Error executing CA utility.
REP-0066:  Error executing CA utility.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0067Invalid value for keyword STYPE. Valid options are DATABASE, REXFILE, RDFFILE, PLLDB, PLLFILE, or PLDFILE.
REP-0067:  Invalid value for keyword STYPE. Valid options are DATABASE, REXFILE, RDFFILE, PLLDB, PLLFILE, or PLDFILE.

Cause:	In RWCON60, you provided an argument for the STYPE keyword that was not valid.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Reenter the command, using a valid value for the keyword(s).


REP-0068Invalid value for keyword STYPE. Valid options are DATABASE or REXFILE.
REP-0068:  Invalid value for DTYPE.

Cause:	In RWCON60, you provided an argument for the DTYPE keyword that was not valid.
Action:	Check the syntax of the keyword.   For more information, see Executables.  (You can also check the online help system.)  Reenter the command, using a valid value for the keyword(s).


REP-0069 Internal error.
REP-0069:  Internal error

Cause:	Report Builder internal code error.
Action:	Contact Oracle Customer Support for assistance.


REP-0071Unable to allocate SSL context.
REP-0071:  Unable to allocate SSL context.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0072Unable to initialize NNIT interface.
REP-0072:  Unable to initialize NNIT interface.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0073Trying to run unknown product.
REP-0073:  Trying to run unknown product.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0074Failure to run another product using SSL.
REP-0074:  Failure to run another product using SSL.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0075:  Error occurred when running the called component.

Cause:	Report Builder encountered an error after calling the Forms Runtime or Graphics Runtime.  The accompanying error message displays the error encountered by the called application.
Action:	Resolve the error encountered by the called application and retry the operation.


REP-0076Internal failure in product integration.
REP-0076:  Internal failure in product integration.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0077:  Column in query '<query name>' too long for data passing.

Cause:	You tried to pass data to a column of excessive size (likely a LONG column).  This is not supported.
Action:	Remove the column from the report definition and the calling document's definition.


REP-0078Single process integration invoked with batch=no.
REP-0078:  Single process integration invoked with batch=no.

Cause:	You used an executable in which Report Builder is linked with another product, and attempted to invoke Report Builder specifying batch=no.  This is not supported.
Action:	Use an executable by which you integrate using multiple processes.  Otherwise, Report Builder can only be called with batch=yes.


REP-0079Invalid value for keyword OVERWRITE. Valid options are YES, NO, or PROMPT.
REP-0079:  Invalid value for keyword OVERWRITE. Valid options are YES, NO, or PROMPT.

Cause:	In RWCON60, you provided an argument for the OVERWRITE keyword that was not valid.
Action:	Reenter the command, specifying a value of YES, NO, or PROMPT for the OVERWRITE keyword.


REP-0080Please enter YES, NO, or CANCEL:
REP-0080:  Please enter YES, NO, or CANCEL:

Cause:	In RWCON60, you typed OVERWRITE=PROMPT on the command line, then entered a value other than YES or NO when prompted.
Action:	Specify a value of YES or NO at the prompt, or CANCEL the operation.


REP-0081Error during file I/O operation.
REP-0081:  Error during file I/O operation.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0082Error executing SCA utility.
REP-0082:  Error executing SCA utility.

Cause:	The possible causes of this error include the following:
	Case 1:	Your initialization file is not current.
	Case 2:	An abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Ensure that your initialization file is current.
	If Case 2:	For information, see  Abnormal Conditions.


REP-0083Invalid value for keyword DUNIT. Valid options are CENTIMETER, CHARACTER, INCH, or POINT.
REP-0083:  Invalid value for keyword DUNIT. Valid options are CENTIMETER, CHARACTER, INCH, or POINT.

Cause:	In RWCON60, you entered an invalid value for the keyword DUNIT.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command, using a valid value for the keyword(s).


REP-0084Invalid value for keyword PAGESIZE.  Syntax is <width>x<height>.
REP-0084:  Invalid value for keyword PAGESIZE.  Syntax is <width>x<height>.

Cause:	In RWCON60, you entered an invalid value for the keyword PAGESIZE.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command, using a valid value and the proper syntax for the keyword.


REP-0085Invalid value for keyword FORMSIZE.  Syntax is <width>x<height>.
REP-0085:  Invalid value for keyword FORMSIZE.  Syntax is <width>x<height>.

Cause:	In RWCON60, you entered an invalid value for the keyword FORMSIZE.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command, using a valid value and the proper syntax for the keyword.


REP-0086DUNIT must be different than source report's unit of measurement.
REP-0086:  DUNIT must be different than source report's unit of measurement.

Cause:	In RWCON60, you entered a value for the keyword DUNIT that was in the same unit of measurement as the report you wish to convert.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command, using a valid value and the proper syntax for the keyword.


REP-0087Invalid value for keyword DESTYPE. Valid options are SCREEN, FILE, PRINTER, MAIL, INTEROFFICE, SYSOUT, or PREVIEW.
REP-0087:  Invalid value for keyword DESTYPE. Valid options are SCREEN, FILE, PRINTER, MAIL, INTEROFFICE, SYSOUT, or PREVIEW.

Cause:	In RWRUN60, you entered an invalid value for the keyword DESTYPE.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command, using a valid value for the keyword(s).


REP-0088Invalid value for keyword ONSUCCESS. Valid options are COMMIT, ROLLBACK, or NOACTION.
REP-0088:  Invalid value for keyword ONSUCCESS. Valid options are COMMIT, ROLLBACK, or NOACTION.

Cause:	You entered an invalid value for ONSUCCESS.
Action:	Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line.   (To check the command line syntax, see Executables


REP-0089Invalid value for keyword ONFAILURE. Valid options are COMMIT, ROLLBACK, or NOACTION.
REP-0089:  Invalid value for keyword ONFAILURE. Valid options are COMMIT, ROLLBACK, or NOACTION.

Cause:	You entered an invalid value for ONFAILURE.
Action:	Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line.   (To check the command line syntax, see Executables.)


REP-0090Invalid value for keyword ACCESS. Valid options are FILE and DATABASE.
REP-0090:  Invalid value for keyword ACCESS. Valid options are FILE and DATABASE.

Cause:	For RWBLD60, you entered an invalid value for ACCESS.
Action:	Specify FILE or DATABASE.   (To check the command line syntax, see Executables.)


REP-0091Invalid value for parameter '<parameter name>'.
REP-0091:  Invalid value for parameter '<parameter name>'.

Cause:	You entered an invalid value for the named parameter.  For example, in the RWRUN60 command string, you entered a character value for a parameter with a datatype of Number.
Action:	Re-try the operation, specifying a valid value for the parameter.


REP-0092Warning: Version 1.1 LANGUAGE argument not supported.  Use ORACLE National Language environment variable instead.
REP-0092:  Warning: Version 1.1 LANGUAGE argument not supported.  Use ORACLE National Language environment variable instead.

Cause:	For RWBLD60 or RWRUN60, you included the LANGUAGE keyword in the command line string.
Action:	Remove the LANGUAGE argument string from the command string, and set the ORACLE National Language environment variable NLS_LANG to the appropriate value.  For more information, see National Language Support.


REP-0094FORMSIZE must be 80x24 if DUNIT is Character.
REP-0094:  FORMSIZE must be 80x24 if DUNIT is Character.

Cause:	While using RWCON60 with DUNIT=Character, you specified a parameter form size that was not equal to 80x24.
Action:	The character-mode parameter form size must be 80x24.  Either specify a FORMSIZE of 80x24 when DUNIT=Character, or do not specify a FORMSIZE.


REP-0095Invalid value for keyword ORIENTATION. Valid options are DEFAULT, LANDSCAPE, or PORTRAIT.
REP-0095:  Invalid value for keyword ORIENTATION. Valid options are DEFAULT, LANDSCAPE, or PORTRAIT.

Cause:	You entered an invalid value for ORIENTATION.
Action:	Specify DEFAULT, LANDSCAPE, or PORTRAIT either in the Runtime Settings tab of the Tools Options dialog or on the command line.  (To check the command line syntax, see Executables.)


REP-0096Invalid value for keyword MODE. Valid options are DEFAULT, BITMAP, or CHARACTER.
REP-0096:  Invalid value for keyword MODE. Valid options are DEFAULT, BITMAP, or CHARACTER.

Cause:	You entered an invalid value for MODE.
Action:	Specify DEFAULT, BITMAP, or CHARACTER either in the Runtime Settings tab of the Tools Options dialog or on the command line.  (To check the command line syntax, see Executables.)


REP-0097Invalid value for keyword TRACEMODE. Valid options are TRACE_APPEND or TRACE_REPLACE.
REP-0097:  Invalid value for keyword TRACEMODE. Valid options are TRACE_APPEND or TRACE_REPLACE.

Cause:	Either you specified an invalid value for TRACEMODE, or did not specify a value for TRACEMODE, or specified keywords out of order on the command line but did not name them.
Action:	Either specify Append or Replace for Trace Mode in the Trace Settings dialog or TRACE_APPEND or TRACE_REPLACE on the command line, or check the syntax of your command.  (To check the command line syntax, see Executables.)


REP-0098Report not run - user cancelled in the parameter form.
REP-0098:  Report not run - user cancelled in the parameter form.

Cause:	Your report was not executed because you selected Cancel instead of Run Report in the Runtime Parameter Form.
Action:	No action is necessary.


REP-0099Report is aborted upon user request.
REP-0099:  Report is aborted upon user request.

Cause:	You stopped a report while it was executing.
Action:	No action is necessary.


REP-0100Unable to position file pointer in file '<filename>'.
REP-0100:  Unable to position file pointer in file '<filename>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


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

Cause:	Report Builder tried to read the file shown in the message.  The file could be opened but not read.
Action:	Consult your operating system documentation or contact your system administrator.


REP-0102Unable to write file '<filename>'.
REP-0102:  Unable to write file '<filename>'.

Cause:	Report Builder tried to write the file shown in the message and couldn't.  The possible causes of this error include the following:
	Case 1:	You lacked the necessary privileges to write the file.
	Case 2:	The file system does not have enough room for the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that you have the privileges necessary to write the file.  If you don't, change your privileges accordingly.
	If Case 2:	Make more room by deleting unnecessary files or expanding your storage.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0103Unable to close file '<filename>'.
REP-0103:  Unable to close file '<filename>'.

Cause:	Report Builder tried to close the file shown, but was unsuccessful.  The most likely reason is that a system error made it impossible to close the file.
Action:	Consult your operating system documentation or contact your system administrator.


REP-0104Unable to delete file '<filename>'.
REP-0104:  Unable to delete file '<filename>'.

Cause:	Report Builder tried to delete the file shown, but was unsuccessful.  The most likely reason is that a system error made it impossible to delete the file.
Action:	Consult your operating system documentation or contact your system administrator.


REP-0105Unable to lock file '<filename>' in exclusive mode.
REP-0105:  Unable to lock file '<filename>' in exclusive mode.

Cause:	Report Builder tried to lock the file shown, but was unsuccessful.  The most likely reason is that a system error made it impossible to lock the file.
Action:	Consult your operating system documentation or contact your system administrator.


REP-0106Unable to lock file '<filename>' in shared mode.
REP-0106:  Unable to lock file '<filename>' in shared mode.

Cause:	Report Builder tried to lock the file shown, but was unsuccessful.  The most likely reason is that a system error made it impossible to lock the file.
Action:	Consult your operating system documentation or contact your system administrator.


REP-0107Attempt to open a file with a bad name - '<filename>'.
REP-0107:  Attempt to open a file with a bad name - '<filename>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0108File '<filename>' not found.
REP-0108:  File '<filename>' not found.

Cause:	Report Builder tried to access the file shown, but could not find it.
Action:	Check that you have specified the correct filename.  Specify a directory before the filename, or modify the REPORTS30_PATH environment variable to include the directory where the file is located.


REP-0109Too many files open.
REP-0109:  Too many files open.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0110Unable to open file '<filename>'.
REP-0110:  Unable to open file '<filename>'.

Cause:	Report Builder tried to open the file shown and couldn't.  The possible causes of this error include the following:
	Case 1:	The file was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the file is stored in the specified directory under the specified name.  If it is not, change the directory and/or filename as appropriate.
	If Case 2:	Make sure that you have the privileges necessary to open the file.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0111Directory '<directory path>' is protected.
REP-0111:  Directory '<directory path>' is protected.

Cause:	You specified that Report Builder read from or write to a directory that you don't have permission to read from or write to.
Action:	Change the permissions on the directory so that you can read from it or write to it.


REP-0112File '<filename>' is write protected.
REP-0112:  File '<filename>' is write protected.

Cause:	You specified that Report Builder write to a file that is write protected--i.e., you don't have permission to write to the file.
Action:	Change the permissions of the file so that you can write to it.


REP-0113File '<filename>' is read protected.
REP-0113:  File '<filename>' is read protected.

Cause:	You specified that Report Builder read a file that is read protected--i.e., you don't have permission to read the file.
Action:	Change the permissions of the file so that you can read it.


REP-0114File '<filename>' no longer exists.
REP-0114:  File '<filename>' no longer exists.

Cause:	You specified that Report Builder access a file that no longer exists.
Action:	Remove the call to the file, re-create the file, or specify a different file.


REP-0115Unable to read directory '<directory path>'.
REP-0115:  Unable to read directory '<directory path>'.

Cause:	You most likely specified that Report Builder read from or write to a directory that doesn't exist.
Action:	Make sure the directory you specify exists.


REP-0116Unable to connect to directory '<directory path>'.
REP-0116:  Unable to connect to directory '<directory path>'.

Cause:	Report Builder could not access the specified directory for some reason.
Action:	Consult your system administrator.


REP-0117Exit to host operating system failed.
REP-0117:  Exit to host operating system failed.

Cause:	You attempted to exit out of the program and return control to the host operating system.
Action:	No action is necessary.


REP-0118Unable to create a temporary file.
REP-0118:  Unable to create a temporary file.

Cause:	Report Builder tried to create a temporary file but couldn't do so.  The possible causes of this error include the following:
	Case 1:	The environment variable that determines in what directory to create temporary files is set to an invalid directory.
	Case 2:	There is not enough free space on the disk to create the temporary file.
	Case 3:	A temporary file that cannot be modified already exists.
Action:	You can take the following actions to correct this error:
	If Case 1:	Set your environment variable for temporary files to a valid directory.
	If Case 2:	Free up some space on your disk.
	If Case 3:	Remove the existing temporary file, if possible.


REP-0119:  Link file boilerplate <boilerplate name>'s Source Filename not found.

Cause:	Report Builder tried to find the source file specified for a piece of external boilerplate and couldn't do so.  The possible causes of this error include the following:
	Case 1:	The file was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the file is stored in the specified directory under the specified name.  If it is not, change the directory and/or filename as appropriate.
	If Case 2:	Make sure that you have the privileges necessary to open the file.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0120:  Chart <chart name>'s associated document <filename> not found.

Cause:	Report Builder was unable to find the chart document.  The possible causes of this error include the following:
	Case 1:	The chart document was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the chart document.
	Case 3:	A system error made it impossible to open the chart document.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the chart document is stored in the specified directory under the specified name.  If it is not, change the directory and/or filename as appropriate.
	If Case 2:	Make sure that you have the privileges necessary to open the chart document.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0124Unable to write to the temporary file.
REP-0124:  Unable to write to the temporary file.

Cause:	Report Builder tried to write to the temporary file but couldn't do so.  The cause could be that there is not enough free space on the disk to write the temporary file.
Action:	Free up some space on your disk.


REP-0125:  Internal Error:  Unable to load NLS character set.

Cause:	The ORA_NLS is not set, or the directory where it points to doesn’t exist.
Action:	Set ORA_NLS to point to the NLS directory containing character set files.


REP-0150Too many arguments.
REP-0150:  Too many arguments.

Cause:	You have entered more than the allowable  number of arguments for the command.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command correctly.


REP-0151Duplicate argument specification for keyword <keyword>.
REP-0151:  Duplicate argument specification for keyword <keyword>.

Cause:	You have entered an argument more than once for the keyword shown.  The possible causes of this error include the following:
	Case 1:	You entered a positional argument for the keyword and then entered the keyword with another argument.
	Case 2:	You entered the same keyword twice (e.g., KEYWORD1=YES and KEYWORD1=NO).
Action:	Check the syntax of the command.  For more information, see Executables.  You can take the following actions to correct this error:
	If Case 1:	Re-enter the command with just the positional argument or just the keyword argument.
	If Case 2:	Re-enter the command specifying the keyword only once.


REP-0152Positional argument specified after keyword.
REP-0152:  Positional argument specified after keyword.

Cause:	On the command line, you entered an argument without its keyword after entering an argument with its keyword.  Once you have used a keyword on the command line, all subsequent arguments must use keywords as well.
Action:	Re-enter the command making sure that no positional arguments (arguments where the keyword is implicit) are specified after arguments with keywords.


REP-0153Multiple values not allowed for keyword <keyword>.
REP-0153:  Multiple values not allowed for keyword <keyword>.

Cause:	In your command, you have entered more than the allowable  number values for the keyword argument shown.  For example, you might have entered KEYWORD=(A, B), where KEYWORD only accepts a single value.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command without the extra value(s).


REP-0154Unable to open command file.
REP-0154:  Unable to open command file.

Cause:	You entered a command that referenced the command file shown and the file could not be opened.  The possible causes of this error include the following:
	Case 1:	The file was not found under the specified name in the specified location.
	Case 2:	You lacked the necessary privileges to open the file.
	Case 3:	A system error made it impossible to open the file.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure the file is stored in the specified directory under the specified name.  If it is not, change the directory and/or filename or move the file into the specified directory.
	If Case 2:	Make sure that you have the privileges necessary to access the file.  If you don't, change your privileges accordingly.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-0155Invalid value for keyword <keyword>.
REP-0155:  Invalid value for keyword <keyword>.

Cause:	The value you entered for the keyword shown was not a valid value.
Action:	Check the syntax of the keyword.  For more information, see Executables.  Re-enter the command with the appropriate value for the keyword(s).


REP-0156Invalid value for keyword DESTYPE. Valid options are SCREEN, FILE, PRINTER, MAIL, INTEROFFICE, or SYSOUT.
REP-0156:  Invalid value for keyword DESTYPE. Valid options are SCREEN, FILE, PRINTER, MAIL, INTEROFFICE, or SYSOUT.

Cause:	In RWRUN60, you provided an argument for the DESTYPE parameter that was not valid.
Action:	Check the syntax of the keyword.   For more information, see Executables.  Re-enter the command with the appropriate value for the keyword(s).


REP-0157The value for <keyword> must be either YES or NO.
REP-0157:  The value for <keyword> must be either YES or NO.

Cause:	You entered a value for the keyword shown that was other than YES or NO and the keyword only accepts YES or NO.
Action:	Re-enter the command and use a value of YES or NO for the keyword shown.


REP-0158Unknown command line keyword '<keyword>'.
REP-0158:  Unknown command line keyword '<keyword>'.

Cause:	You entered the referenced string as a keyword, but there is no such keyword.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command using the appropriate keywords for the task you want to perform.


REP-0159Syntax error on command line.
REP-0159:  Syntax error on command line.

Cause:	The string you entered on the command line could not be parsed.  The most likely cause of this error is that you entered quotes or parentheses without also entering matching end quotes or parentheses.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command using the appropriate syntax.


REP-0160Syntax error in command file.
REP-0160:  Syntax error in command file.

Cause:	Something you entered in your command file could not be parsed.  The most likely cause of this error is that you entered quotes or parentheses without also entering matching end quotes or parentheses.
Action:	Check the syntax of the command(s).  For more information, see Executables.  Edit the file and modify the commands as necessary to correct the command(s).


REP-0161No command line arguments specified.
REP-0161:  No command line arguments specified.

Cause:	You invoked RWCON60 without specifying any command line arguments.
Action:	Specify the appropriate command line arguments (e.g., SOURCE, DEST, etc.) for RWCON60.  For more information, see Executables.


REP-0162:  Invalid value for keyword SHOWWINDOW. Valid options are DEFAULT, WIZARD, and PREVIEWER.

Cause:	You used the keyword SHOWWINDOW, but gave an invalid value for it.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command using the appropriate syntax.


REP-0163:  Invalid value for keyword DESTYPE. Valid options are FILE, PRINTER, MAIL, INTEROFFICE, or CACHE.

Cause:	You provided an argument for the DESTYPE parameter that was not valid for the Reports Server.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command using the appropriate syntax.


REP-0164: Invalid value for keyword PARAMFORM. Valid options are YES, NO, or HTML<action>.

Cause:	You invoked Reports Runtime (standalone or as a Reports Server engine) with an invalid value for the PARAMFORM parameter.
Action:	Check the syntax of the command.  For more information, see Executables.  Re-enter the command using the appropriate syntax.


REP-0165: Missing required value for keyword SITENAME. Please specify a WEBDB site name.

Cause:	No value was found for the SITENAME keyword. A value is required for SITENAME in order to schedule a report.
Action:	Specify a WEBDB site name for the keyword SITENAME.


REP-0171Unable to retrieve output from remote server
REP-0171:  Unable to retrieve output from remote server.

Cause:	Error occurred when retrieving output from the remote server.
Action:	You may have specified a local file that you don't have access to.  Or the server is set to disallow retrieving outputs.


REP-0172No value provided for keyword SERVER
REP-0172:  No value provided for keyword SERVER.

Cause:	You did not provide a valid argument for the mandatory keyword SERVER.
Action:	Provide a valid argument for the keyword SERVER and rerun the command.


REP-0173Invalid value for keyword SHOWJOBS. Valid options are PAST, CURRENT, or FUTURE
REP-0173:  Invalid value for keyword SHOWJOBS. Valid options are PAST, CURRENT, or FUTURE.

Cause:	In the Reports Queue Viewer, an argument provided in the command line for the SHOWJOBS keyword was not valid.
Action:	Reenter the command, specifying a value of PAST, CURRENT or FUTURE for the SHOWJOBS keyword.


REP-0174Internal error occured while obtaining the Reports Server queue information
REP-0174:  Internal error occured while obtaining the Reports Server queue information.

Cause:	The Reports Server did not return valid information about its queue to the queue viewer. This could be caused by one of the following reasons:
	Case 1:	The connection to the Reports Server unexpectedly went down.
	Case 2:	The Reports Server is in an unstable state, or has been shut down.
Action:	Make sure that the Reports Server to which you are connecting is running. Contact the Reports Server Administrator and retry the command after verifying that it is running. If this problem persists, it is an abnormal condition. For information, see  Abnormal Conditions.


REP-0175Internal error occured while obtaining the Reports Server properties information
REP-0175:  Internal error occured while obtaining the Reports Server properties information.

Cause:	The Reports Server did not return valid information about its properties to the queue viewer. This could be caused by one of the following reasons:
	Case 1:	The connection to the Reports Server unexpectedly went down.
	Case 2:	The Reports Server is in an unstable state, or has been shut down.
Action:	Make sure that the Reports Server to which you are connecting is running. Contact the Reports Server Administrator and retry the command after verifying that it is running. If this problem persists, it is an abnormal condition. For information, see  Abnormal Conditions.


REP-0176Server '$0' is shutting down
REP-0176:  Server '<server>' is shutting down.

Cause:	Cannot submit a report since the specified Reports Server is shutting down.
Action:	Submit to another Reports Server or wait until the Server is back up.


REP-0177Error while running in remote server
REP-0177:  Error while running in remote server.

Cause:	Unable to run the specified command line in the remote server.
Action:	Check the command line.


REP-0178Cannot connect to Reports Server '$0'
REP-0178:  Cannot connect to report server '<server>'.

Cause:	Unable to establish proper connection to the specified Reports Server.
Action:	Check the network and check the status of the report server in question.


REP-0179Report execution terminated unexpectedly while running
REP-0179:  Report execution terminated unexpectedly while running.

Cause:	The Reports Server engine has crashed while running.
Action:	Contact your system administrator.


REP-0180Report has been cancelled from the report server
REP-0180:  Report has been cancelled from the report server.

Cause:	You have stopped the report while it was executing or you have removed it from the queue before it is started.
Action:	No action is necessary.


REP-0181Error reading/writing the configuration file for the report server
REP-0181:  Error reading/writing the configuration file for the report server.

Cause:	The configuration file cannot be opened, or its content is incomprehensible.
Action:	Check the configuration file and its access rights.  Restart the Reports Server.


REP-0182Syntax error on command line for the report server
REP-0182:  Syntax error on command line for the report server.

Cause:	The string you entered on the command line could not be parsed.  The most likely cause of this error is that you entered quotes or parentheses without also entering matching end quotes or parentheses.
Action:	Check the syntax of the command.  Reenter the command using the appropriate syntax.


REP-0183You must provide TNSNAME to start up the report server
REP-0183:  You must provide TNSNAME to start up the report server.

Cause:	You tried to start up the report server without specifying the TNSNAME to which the Server should listen.
Action:	Specify the TNSNAME as a command line argument.


REP-0184Specified MAXCONNECTS out of range
REP-0184:  Specified MAXCONNECTS out of range.

Cause:	The MAXCONNECTS value you specified is out of range for this platform.  MAXCONNECTS must be at least 2, and cannot exceed 4096, and on some platforms the limit is even lower.
Action:	Specify an appropriate value.


REP-0185Bad load arguments supplied when starting up the report server
REP-0185:  Bad load arguments supplied when starting up the report server.

Cause:	You've specified inconsistent values among maxconnects, MINLOAD, MAXLOAD, and INITLOAD.
Action:	Make sure that 0 <= MINLOAD <= INITLOAD <= MAXLOAD < MAXCONNECTS.


REP-0186Daemon failed to listen to port
REP-0186:  Daemon failed to listen to port.

Cause:	You may have another daemon running that is already listening to the port.
Action:	No action is necessary.  Since you already have a daemon running, you can now submit your report to be run.


REP-0187Daemon failed to start up engine
REP-0187:  Daemon failed to start up engine.

Cause:	Daemon can not start up the engine executable and communicate to it.  This is most likely an installation issue.
Action:	Make sure the installation is done properly.


REP-0188Reports Server only accept batch jobs
REP-0188:  Reports Server only accept batch jobs.

Cause:	You have submitted a job to the Reports Server where either batch=no, destype=screen, destype=preview, or destype=sysout.
Action:	These settings are not allowed.  Change the command line accordingly.


REP-0189:  Cannot write to Reports Server cache

Cause:	Reports Server failed to write to the cache directory.
Action:	Make sure the cache directory is specified in the configuration file and it is writable.


REP-0190Cannot run to screen in background.
REP-0190:  Cannot run to screen in background.

Cause:	You specified that the report be run in the background, but you also specified a DESTYPE of Screen.  You cannot execute a report in the background while having its output sent to the screen.
Action:	If you want the output to go to the screen, you must run it in the foreground.  If you want the report to run in the background, you must specify a different DESTYPE.


REP-0194Cannot run character report in bitmap mode using this executable.
REP-0194:  Cannot run character report in bitmap mode using this executable.

Cause:	You are attempting use the character-mode executable to run a character-mode report with MODE set to BITMAP.  This is not allowed.
Action:	Change the value of the MODE keyword to match the mode of the executable.  Or run the report using a bitmapped executable.


REP-0195Cannot run report in bitmap mode to screen using this executable.
REP-0195:  Cannot run report in bitmap mode to screen using this executable.

Cause:	You are attempting use the character-mode executable to run a bitmapped report to the screen.  This is not allowed.
Action:	Run the report using BATCH=YES or use a bitmapped executable.


REP-0196Cannot run report in background.
REP-0196:  Cannot run report in background.

Cause:	You specified YES for BACKGROUND under one of the following conditions, none of which are allowed:
	Case 1:	You are running the report from the designer.
	Case 2:	You set BATCH to YES.
	Case 3:	You are running the report using the packaged procedure srw.run_report.
	Case 4:	The platform on which you're running the report does not support spawning of another process.
Action:	Ensure that BACKGROUND is set to NO when any of the above condition are true.


REP-0197Must specify BATCH=YES or BACKGROUND=YES on command line when running bitmapped report.
REP-0197:  Must specify BATCH=YES or BACKGROUND=YES on command line when running bitmapped report.

Cause:	You tried to run a bitmapped report using the character-mode executable in the foreground or during an interactive session.  This is not supported.
Action:	If you wish to run a bitmapped report using the character-mode executable, you must choose either BATCH=YES or BACKGROUND=YES (unlike BATCH=YES, this setting gives you access to the Runtime Parameter Form).


REP-0200Cannot allocate enough memory.
REP-0200:  Cannot allocate enough memory.

Cause:	Report Builder cannot obtain enough memory from the system to complete the current task.
Action:	Make more memory available, if you can, or ask your system administrator for assistance.


REP-0201Zero or negative block size requested.
REP-0201:  Zero or negative block size requested.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0202Attempt to free a null pointer.
REP-0202:  Attempt to free a null pointer.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0203Passed a null pointer as a handle.
REP-0203:  Passed a null pointer as a handle.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0204Handle does not point into an mp block.
REP-0204:  Handle does not point into an mp block.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0205Too many simultaneous locks on one object.
REP-0205:  Too many simultaneous locks on one object.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0206Null cache pointer passed to virtual memory routine.
REP-0206:  Null cache pointer passed to virtual memory routine.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0207Requested block is larger than virtual memory space.
REP-0207:  Requested block is larger than virtual memory space.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0208rmaloc was not given a function identifier.
REP-0208:  rmaloc was not given a function identifier.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0209rmaloc was not given a structure identifier.
REP-0209:  rmaloc was not given a structure identifier.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0210Illegal operation was requested on a locked handle.
REP-0210:  Illegal operation was requested on a locked handle.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0211Attempt to use a handle after freeing it.
REP-0211:  Attempt to use a handle after freeing it.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0212No literal specified.
REP-0212:  No literal specified.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0213Attempt to lock handle failed.
REP-0213:  Attempt to lock handle failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0214Cannot allocate a virtual memory buffer of size <number> KB.  Please try a smaller size.
REP-0214:  Cannot allocate a virtual memory buffer of size <number> KB.  Please try a smaller size.

Cause:	Report Builder tried to allocate a virtual memory buffer size at or below the number specified (by you or by default) for the BUFFERS keyword.
Action:	Specify a smaller size for BUFFERS (either in the Runtime Settings tab of the Tools Options dialog or on the command line), or free up more memory.  (To check the command line syntax, see Executables.)


REP-0215Error locking, dereferencing, or freeing a memory handle.
REP-0215:  Error locking, dereferencing, or freeing a memory handle.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0230:  Error while starting a thread.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0231 Error while posting thread message.
REP-0231:  Error while posting thread message.

Cause:	This is an abnormal condition.
Action:	For information, see Abnormal Conditions.


REP-0232 Error while getting thread message
REP-0232:  Error while getting thread message

Cause:	This is an abnormal condition.
Action:	For information, see Abnormal Conditions.


REP-0235: Security Server TNSNAME not provided in config file.
REP-0235: Security Server TNSNAME not provided in config file

Cause:	The security server TNSNAME must be specified in Reports Server configuration file on security mode."
Action:	Specify the security server TNSNAME in the SECURITYTNSNAME parameter in Reports Server configuration file.


REP-0236: Unable to connect to Security Server.

Cause:	This is an abnormal condition.
Action:	For information, see Abnormal Conditions.


REP-0237: Security server authentication successful.

Cause:	Authentication was successful."
Action:	None.


REP-0238: Security server authentication failed.

Cause:	Your system userid/password is invalid or does not have necessary privileges to run the report.
Action:	Check your system userid/password to ensure that it is correct or contact your system administrator to grant you the necessary privileges.


REP-0239: Security server authentication failed: invalid user name.

Cause:	Your system user ID is incorrect.
Action:	Check your system user ID to ensure that it is correct or contact your system administrator regarding your system user ID.


REP-0240: Security server authentication failed: invalid password.

Cause:	Your system user ID password is incorrect.
Action:	Check your system userid password to ensure that it is correct or contact your system administrator regarding your system user ID password.


REP-0241: Security server authentication failed: no privilege on the Reports server.

Cause:	Your system user ID does not have the necessary privileges to access the Reports Server.
Action:	Contact your system administrator regarding your system user ID's privileges on the Reports Server.


REP-0242: Security server authentication failed: no privilege on the printer.

Cause:	Your system user ID does not have privilege to access the printer.
Action:	Contact your system administrator regarding your system user ID's privileges on the printer.


REP-0243: Security server authentication failed: no privilege on the module.

Cause:	Your system user ID does not have privileges to access the module.
Action:	Contact your system administrator regarding your system user ID's privileges on the module.


REP-0244: Security server authentication failed: no privilege of this access type.

Cause:	Your system user ID does not have privileges for this access type.
Action:	Contact your system administrator regarding your system user ID's privileges of this access type.


REP-0245: Security server authentication failed: no privilege of this output type.

Cause:	Your system user ID does not have privileges for this output type.
Action:	Contact your system administrator regarding your system user ID's privileges of this output type.


REP-0246: Security server authentication failed: no privilege for the given time.

Cause:	Your system user ID does not have necessary privileges for the given time.
Action:	Contact your system administrator regarding your system user ID's privileges for the given time.


REP-0247: Security server authentication failed: no privilege for the given date.

Cause:	Your system user ID does not have necessary privileges for the given date.
Action:	Contact your system administrator regarding system user ID's privileges for the given date.


REP-0250 Symbol table overflow.
REP-0250:  Symbol table overflow.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0251Identifier does not match a defined symbol.
REP-0251:  Identifier does not match a defined symbol.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0252Warning: The path specified by environment variable '<environment variable name>' is too long and will be ignored.
REP-0252:  Warning: The path specified by environment variable '<environment variable name>' is too long and will be ignored.

Cause:	The path designated by the environment variable is too long.
Action:	Shorten the length of the designated path.


REP-0253Warning: The total length of the search paths is too long and will be truncated.
REP-0253:  Warning: The total length of the search paths is too long and will be truncated.

Cause:	The combined length of search paths in the path environment is too long. The combined length cannot exceed 255 characters.
Action:	Shorten the length of one or more paths in the path environment.


REP-0300ORACLE error occurred.
REP-0300:  ORACLE error occurred.

Cause:	Report Builder encountered an ORACLE error.
Action:	Scroll through the error message to see where the error occurred and, if possible, fix it.  Otherwise, contact your DBA.


REP-0301The SELECT statement may not contain an 'INTO' clause.
REP-0301:  The SELECT statement may not contain an 'INTO' clause.

Cause:	You entered an INTO clause in a SELECT statement, which is not allowed in Report Builder.
Action:	Remove the INTO clause.


REP-0302Parameter '<parameter name>' not found in report.
REP-0302:  Parameter '<parameter name>' not found in report.

Cause:	You made reference to a parameter that is not defined in the report.  The most likely cause is that you deleted a parameter but did not delete all references to it.
Action:	Delete all references to the deleted parameter.


REP-0303The statement you have entered is not a SELECT statement.
REP-0303:  The statement you have entered is not a SELECT statement.

Cause:	What was entered in the SELECT Statement field is something other than a SELECT statement.  The possible causes of this error include the following:
	Case 1:	You entered something besides a SELECT statement in the SELECT Statement field.
	Case 2:	You referenced an external query that did not contain a SELECT statement.
Action:	You can take the following actions to correct this error:
	If Case 1:	Enter a valid SELECT statement.
	If Case 2:	Modify the external query or reference another external query.


REP-0304'&' in SELECT statement was not followed by a valid lexical parameter.
REP-0304:  '&' in SELECT statement was not followed by a valid lexical parameter.

Cause:	An ampersand (&) appeared in the SELECT statement by itself.  The possible causes of this error include the following:
	Case 1:	You intended to make a lexical reference but either left out the name of the column or parameter altogether or inadvertently typed a space between the ampersand and the name of the column or parameter.
	Case 2:	In typing the SELECT statement, you accidentally typed in an ampersand.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that the column or parameter name immediately follows the ampersand with no spaces in between.
	If Case 2:	Delete the ampersand.


REP-0305'<lexical reference>' cannot be used as a lexical parameter because it is not a character value.
REP-0305:  '<lexical reference>' cannot be used as a lexical parameter because it is not a character value.

Cause:	You entered an invalid lexical reference in your SELECT statement.  Lexical references can only be made to parameters or columns containing character data.  The possible causes of this error include the following:
	Case 1:	You referenced the wrong column or parameter.
	Case 2:	You meant for the reference to be a bind reference, not a lexical reference.
	Case 3:	You created the parameter or column referenced with a non-character Datatype.
Action:	You can take the following actions to correct this error:
	If Case 1:	Change the name that follows the ampersand (&) so it references a parameter or column with a Datatype of Character.
	If Case 2:	Replace the ampersand (&) with a colon (:) when referencing the parameter or column.
	If Case 3:	Change the Datatype of the parameter or column to be Character, if appropriate.


REP-0306'<name>' is not a valid parameter name.
REP-0306:  '<name>' is not a valid parameter name.

Cause:	In making reference to a parameter, you have tried to create a parameter with an invalid name.  When you use a bind reference, a parameter definition is automatically created using the name specified in the bind parameter.  In this case, Report Builder could not create the parameter because the name you supplied was not a valid name.
Action:	Check the naming conventions for data model objects and rules for parameter names.  For more information on naming conventions, see Naming Conventions.  Rename the parameter and change the name in the bind reference.


REP-0307The SELECT statement may not contain a 'FOR UPDATE' clause.
REP-0307:  The SELECT statement may not contain a 'FOR UPDATE' clause.

Cause:	You entered a FOR UPDATE clause in the SELECT statement, which is not allowed in Report Builder.
Action:	Remove the FOR UPDATE clause.


REP-0308Internal error - Unknown column type.
REP-0308:  Internal error - Unknown column type.

Cause:	The possible causes of this error include the following:
	Case 1:	You tried to display the value of a column using SRW.MESSAGE, but the column's datatype (e.g., LONG, LONG RAW, ROWID) is not supported for that operation.
	Case 2:	You tried to pass the value of a column to the form or chart runtime executable as a parameter, but the column's datatype (e.g., LONG, LONG RAW, ROWID) is not supported for that operation.
Action:	You cannot display or pass this column's value.


REP-0309Unable to connect to the specified database after three attempts.  Access denied.
REP-0309:  Unable to connect to the specified database after three attempts.  Access denied.

Cause:	Some part of the logon string you entered was incorrect.  After three failed attempts, Report Builder displays a dialog box with this message.  Your only option from this dialog box is to accept it and then Report Builder quits and returns you to the operating system.
Action:	Accept the dialog box.  Confirm your logon information with your DBA, if necessary.  Go back into Report Builder and try connecting to ORACLE again.  If the problem persists, you may have to get your DBA to create a new ORACLE logon for you.


REP-0310Error while processing Bind Variables in query.
REP-0310:  Error while processing Bind Variables in query.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0311Internal Error - Segmented memory used for lexical parameter.
REP-0311:  Internal Error - Segmented memory used for lexical parameter.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0312Internal Error - Error dealing with segmented memory.
REP-0312:  Internal Error - Error dealing with segmented memory.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0313Internal Error - Fetching data records would cause memory overflow.
REP-0313:  Internal Error - Fetching data records would cause memory overflow.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0314Column name exceeds 256 characters. Unable to describe. Use column alias for '<column name>...'.
REP-0314:  Column name exceeds 256 characters. Unable to describe. Use column alias for '<column name>...'.

Cause:	One of your SQL SELECT statements contains an expression that is longer than 256 characters, but has no alias.
Action:	Edit the SELECT statement and assign an alias to the expression.


REP-0315Each select statement must have the same number of columns in compound query.
REP-0315:  Each select statement must have the same number of columns in compound query.

Cause:	You entered a query with a UNION, INTERSECT, or MINUS set operator in which the SELECT statements in the query do not have the same number of selected columns.
Action:	Modify the SELECT statements so that they have the same number of columns.


REP-0316The types of corresponding columns must match in compound query.
REP-0316:  The types of corresponding columns must match in compound query.

Cause:	You entered a query with a UNION, INTERSECT, or MINUS set operator in which corresponding columns have different types--e.g., column 1 in the first SELECT statement has datatype CHAR, while column 1 in the second SELECT statement has datatype NUMBER.
Action:	Modify the SELECT statements so that all corresponding columns have the same datatype.


REP-0320Could not connect to the database.
REP-0320:  Could not connect to the database.

Cause:	An attempt to connect to the database failed.
Action:	Recheck the userid and password and try again.


REP-0321Internal Error - Describe of query failed.
REP-0321:  Internal Error - Describe of query failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0322Internal Error - Could not put back fetched rows.
REP-0322:  Internal Error - Could not put back fetched rows.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0330Internal Error - Location GET_REF parameters failed.
REP-0330:  Internal Error - Location GET_REF parameters failed.

Cause:	A CDE_MM.GET_REF call in a query did not specify a parameter list.
Action:	Add the parameter list to the call in your query's select statement.


REP-0331GET_REF PL/SQL function requires 3 parameters.
REP-0331:  GET_REF PL/SQL function requires 3 parameters.

Cause:	The parameter list of a CDE_MM.GET_REF call in a query was incomplete.
Action:	Add the necessary parameter to the call in your query's select statement.


REP-0332GET_REF PL/SQL function's last parameter must be of type ROWID.
REP-0332:  GET_REF PL/SQL function's last parameter must be of type ROWID.

Cause:	You did not provide a parameter of type ROWID as the last parameter for a  GET_REF function.
Action:	Check your parameter list and ensure the last parameter is of type ROWID.


REP-0340:  Cannot verify role password. Report not opened.

Cause:	You did not type in the correct role password.
Action:	Confirm that you have the correct role password.  Try opening your report again and type in the correct role password.


REP-0341: Cannot set roles specified in the report. Report not opened.

Cause:	The role specified in the report cannot be set when opening the report.
Action:	Confirm that you are granted the role and that the role password is correct.  Try opening your report again and type in the correct role password.


REP-00342:  Warning:  Cannot set roles specified in the report.
REP-0342:  Warning:  Cannot set roles specified in the report.

Cause:	The role specified on the command line cannot be set.
Action:	Confirm that you are granted the role and that the role password is correct.


REP-0343:  Warning:  Cannot set default roles of the current user.

Cause:	Report Builder is unable to set the default roles of the current user that has passwords.
Action:	Do not use default roles with passwords.


REP-344: Role password not confirmed correctly. Please make sure confirmation password matches the role password.
REP-0344: Role password not confirmed correctly. Please make sure confirmation password matches the role password.

Cause:	The password entered in the Confirm Password field is different than the Role Password.
Action:	Re-enter the Confirm Password, ensuring that the password exactly matches the Role Password.


REP-345: Cannot have empty role and non-empty password.
REP-0345: Cannot have empty role and non-empty password.

Cause:	You specified a role password, but not the role.
Action:	Specifiy a role, and then specify the password, or leave all fields empty if you do not intend to associate a role with this report.


REP-0346: Role must be no longer than <number> characters. It will be truncated.

Cause:	You specified a role name that is longer than what is allowed. It will be truncated.
Action:	Specify a shorter role name.


REP-0347: Role password must be no longer than <number> characters. It will be truncated.

Cause:	You specified a role password that is longer than what is allowed. It will be truncated.
Action:	Specify a shorter role pasword.


REP-0348: Incorrect role password.

Cause:	You entered an  incorrect role password.
Action:	Re-enter the correct role password.


REP-0450<PL/SQL error>.
REP-0450:  <PL/SQL error>.

If you edit an object that may have associated PL/SQL code such as a Formula column, Place Holder column or Parameter, this error can occur. Any changes to an object in Report Builder should also be made to associated PL/SQL code.

Cause:	Report Builder encountered this error while running a report.
Action:	Edit and recompile the PL/SQL in the report to avoid this error.
Cause:	A size has not been declared with a datatype.
Action:	Declare each datatype's size. Varchar2(10), for example.
Cause:	The value returned for a variable is too large for the datatype's specified size.
Action:	Change the size for the variable to the same size as the field being selected.
Cause:	An older version of PL/SQL was used to create the report.
Action:	Open the report in the current version of Report Builder, save it, and then close it. Open it again and run it.


REP-0451<PL/SQL error>. <additional messages>.
REP-0451:  <PL/SQL error>. <additional messages>.

Cause:	Report Builder encountered this error while running a report.
Action:	Edit and recompile the PL/SQL in the report to avoid this error.


REP-0452<PL/SQL error>. <additional message>. <additional message>.
REP-0452:  <PL/SQL error>. <additional message>. <additional message>.

Cause:	Report Builder encountered this error while running a report.
Action:	Edit and recompile the PL/SQL in the report to avoid this error.


REP-0453<PL/SQL error>. <additional message>. <additional message>. <additional message>.
REP-0453:  <PL/SQL error>. <additional message>. <additional message>. <additional message>.

Cause:	Report Builder encountered this error while running a report.
Action:	Edit and recompile the PL/SQL in the report to avoid this error.


REP-0490Internal Error - Toolkit context unavailable.
REP-0490:  Internal Error - Toolkit context unavailable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0491Warning: Data truncation possible in column '<column name>'.
REP-0491:  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 sometimes occur when the columns in the database are updated subsequent to the report being defined.  This warning is raised only when RUNDEBUG is YES.
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-0492Unrecognized token: '<token name>'.
REP-0492:  Unrecognized token: '<token name>'.

Cause:	The SELECT statement that you entered contains an item that is not part of SQL syntax.
Action:	Review your SELECT statement and ensure that it follows SQL syntax.


REP-0493Internal Error - Unable to expand Lexical references.
REP-0493:  Internal Error - Unable to expand Lexical references.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0494Internal Error - Unable to process Lexical references.
REP-0494:  Internal Error - Unable to process Lexical references.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0495Internal Error - Unable to tokenize the query.
REP-0495:  Internal Error - Unable to tokenize the query.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0496Internal Error - Unable to parse the query.
REP-0496:  Internal Error - Unable to parse the query.

Cause:	The SQL statement that you have entered cannot be parsed because it contains an error.
Action:	Review the SQL statement that you entered and ensure that you are using the correct syntax.  For more information, see the ORACLE8 Server SQL Language Reference Manual.


REP-0497Internal Error - Query failed in rodslt.
REP-0497:  Internal Error - Query failed in rodslt.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0498Number of columns selected by the query is incompatible with report definition.
REP-0498:  Number of columns selected by the query is incompatible with report definition.

Cause:	The query is selecting more columns than the report definition is expecting.  This can happen when you are using an external query and the query has been changed since the report was defined.
Action:	Update the report definition so that it accepts the changed query.  For example, go to the SQL Query Statement dialog for the query that references the changed external query and modify it.  Formulas, summaries, and fields that rely on any changed columns may also need to be updated.


REP-0499Column selected by the query is incompatible with report definition.
REP-0499:  Column selected by the query is incompatible with report definition.

Cause:	The column from the database does not match the column in the report definition.  The possible causes of this error include the following:
	Case 1:	The definition of the column in the database has changed since the report was defined.
	Case 2:	The report uses an external query and the external query was changed since the report was defined.
Action:	You can take the following actions to correct this error:
	If Case 1:	Update the report definition so that it accepts the changed column.  For example, if the datatype of the column has changed, re-accept the SQL Query Statement dialog external query so the column in the report definition has its datatype updated.  Formulas, summaries, and fields that rely on the changed column may also need to be updated.
	If Case 2:	Update the report definition so that it accepts the changed query.  For example, re-accept the SQL Query Statement dialog box that references the changed external query and accept it.  Formulas, summaries, and fields that rely on any changed columns may also need to be updated.


REP-0500Number entered is out of range.
REP-0500:  Number entered is out of range.

Cause:	You have entered a number in a setting which is too large.
Action:	Check the limits of the field.  Look in the chapter where the field is described and enter a number that is within the limits.


REP-0501Unable to connect to the specified database.
REP-0501:  Unable to connect to the specified database.

Cause:	Report Builder tried to but could not connect to ORACLE.    The possible causes of this error include the following:
	Case 1:	ORACLE is temporarily unavailable.
	Case 2:	Your connect information was not valid.
Action:	You can take the following actions to correct this error:
	If Case 1:	Retry the operation.  Contact your DBA if the problem persists.  Note that after three failed attempts, you will be forced to leave Report Builder.
	If Case 2:	Check your connect information to make sure it is correct.  If it is not, re-enter it and try to connect again.  Note that after three failed attempts, you will be forced to leave Report Builder.


REP-0502Error attempting to open '<filename>' terminal file.
REP-0502:  Error attempting to open '<filename>' terminal file.

Cause:	Report Builder tried to but could not open the terminal definition file you specified.  You either specified the name of the file incorrectly after the TERM keyword or the file could not be found.
Action:	Make sure that you specified the name of the terminal definition correctly and that it resides in the correct path.  If the problem persists, contact your DBA.


REP-0503You did not specify the name of a report.
REP-0503:  You did not specify the name of a report.

Cause:	You specified an invalid name or nothing when you should have specified the name of a report.
Action:	Specify the name of a report.


REP-0504You are not connected to a specified database.
REP-0504:  You are not connected to a specified database.

Cause:	You tried to perform an operation that requires you be connected to the database and you were not connected.
Action:	Connect to the database using File [image] Connect.


REP-0450<PL/SQL error> examples.
REP-0450:  <PL/SQL error> examples.


REP-0505This is not a valid width for this column.
REP-0505:  This is not a valid width for this column.

Cause:	The value you entered in Width was invalid.  The possible causes of this error include the following:
	Case 1:	You entered zero or a negative number.  Width must be greater than zero.
	Case 2:	You entered something that was not a number.
	Case 3:	For a column of non-numeric Datatype, you entered a width of the form (x, y) where x is the precision and y is the scale.  This type of Width specification is only valid when Datatype is Number.
Action:	You can take the following actions to correct this error:
	If Case 1:	Enter a number greater than zero.
	If Case 2:	Enter a number greater than zero.
	If Case 3:	Enter a number greater than zero or, if possible, change the Datatype of the column to Number.


REP-0506Database columns cannot be moved between queries.
REP-0506:  Database columns cannot be moved between queries.

Cause:	You tried to move a column into another group belonging to another query and the column is a database column.  A database column must be selected by the query that owns its group.
Action:	Select the column, if possible, in the query that owns the group to which you want to move it.


REP-0507You must enter a file name before performing this operation.
REP-0507:  You must enter a file name before performing this operation.

Cause:	In a file selection dialog box, you tried to accept the dialog box without specifying a filename.
Action:	Enter a name and then accept or cancel the dialog box.


REP-0508You must enter an object name before performing this operation.
REP-0508:  You must enter an object name before performing this operation.

Cause:	In a database object selection dialog box, you tried to accept the dialog box without specifying an object name.
Action:	Enter a name and then accept or cancel the dialog box.


REP-0509Invalid number.
REP-0509:  Invalid number.

Cause:	In a numeric field, you entered something other than a digit or a decimal point.
Action:	Enter a number that contains only digits and, if necessary, a decimal point.


REP-0510Valid options are 'Character', 'Inch', 'Centimeter' or 'Point'.
REP-0510:  Valid options are 'Character', 'Inch', 'Centimeter' or 'Point'.

Cause:	You entered an invalid unit of measurement in the Unit of Measurement field.
Action:	Select the option you want from the list of values.


REP-0511Valid options are 'Across/Down' or 'Down/Across'.
REP-0511:  Valid options are 'Across/Down' or 'Down/Across'.

Cause:	You entered a Panel Print Order that was not one of the two valid options.
Action:	Select the option you want from the list of values.


REP-0512A decimal value is not appropriate here.
REP-0512:  A decimal value is not appropriate here.

Cause:	The number that you entered was a decimal value and Report Builder was expecting a non-decimal value.
Action:	Enter a non-decimal value.


REP-0513You must enter a Unit of Measurement.
REP-0513:  You must enter a Unit of Measurement.

Cause:	The Unit of Measurement is blank and you tried to move to another setting.
Action:	Select an option for Unit of Measurement.


REP-0514You must specify the Page Size.
REP-0514:  You must specify the Page Size.

Cause:	You left the Page Width and/or Page Height settings blank and they require a value.
Action:	Enter a number for Page Width and/or Page Height.


REP-0515You must specify the Parameter Form Size.
REP-0515:  You must specify the Parameter Form Size.

Cause:	You left the Parameter Form Width and/or Parameter Form Height settings blank and they require a value.
Action:	Enter a number for Parameter Form Width and/or Parameter Form Height.


REP-0516You must specify the Page Size in characters.
REP-0516:  You must specify the Page Size in characters.

Cause:	The value you entered for Page Size was not in character units, and Page Size requires character units.
Action:	Enter a value in characters for Page Size.


REP-0517You must specify the Form Size in characters.
REP-0517:  You must specify the Form Size in characters.

Cause:	The value you entered for Form Size was not in character units, and Form Size requires character units.
Action:	Enter a value in characters for Form Size.


REP-0518Valid options are 'Database', 'File', or 'File/Database'.
REP-0518:  Valid options are 'Database', 'File', or 'File/Database'.

Cause:	The Object Access setting you entered was not one of the three valid choices.
Action:	Select an option from the list of values.


REP-0519Valid options are 'Insert' or 'Replace'.
REP-0519:  Valid options are 'Insert' or 'Replace'.

Cause:	The Default Text Edit Mode you entered was not one of the two valid choices.
Action:	Select an option from the list of values.


REP-0520The value for group or frame indentation must be between 0 and 4.
REP-0520:  The value for group or frame indentation must be between 0 and 4.

Cause:	The value you entered for Group/Frame Indentation was outside the valid range of values.
Action:	Enter a number between 0 and 4.


REP-0521'<Name>' is not a valid name.
REP-0521:  '<Name>' is not a valid name.

Cause:	You violated naming conventions and gave an object an invalid name (shown).
Action:	Find the naming conventions for the type of object you are creating and ensure that the name follows those conventions.  For more information, see Naming Conventions.


REP-0522You cannot build a default layout because this report has no groups.
REP-0522:  You cannot build a default layout because this report has no groups.

Cause:	You selected Tools [image] Default Layout or drew a region using the Default Layout tool in the Layout Model editor before having created any groups for the report.  Groups are required in order to create a default layout.
Action:	Create one or more queries to allow Report Builder to automatically create a group, then retry the operation.


REP-0523Invalid Default Layout Style.  See the list of values.
REP-0523:  Invalid Default Layout Style.  See the list of values.

Cause:	You entered a value for Default Layout Style that is not one of the valid options.
Action:	Select a layout style from the list of values.


REP-0524Invalid Print Direction.  See the list of values.
REP-0524:  Invalid Print Direction.  See the list of values.

Cause:	You entered a Repeat value that is not one of the valid options.
Action:	Select a value for Repeat from the list of values.


REP-0525Valid options are 'Screen', 'File', 'Printer', 'Mail', or 'Sysout'.
REP-0525:  Valid options are 'Screen', 'File', 'Printer', 'Mail', or 'Sysout'.

Cause:	You entered a destination type for the system parameter DESTYPE that is not one of the valid options. Possible causes of this error include the following:
	Case 1:	You entered an invalid value for Destination Type in the Runtime Parameter Form.
	Case 2:	You entered an invalid Initial Value in the Parameter property palette for DESTYPE.
Action:	You can take the following actions to correct this error:
	If Case 1:	Enter one of the valid values, Screen, File, Printer, Mail, or Sysout.
	If Case 2:	Select a value for Initial Value from the list of the values.


REP-0526The initial value you have entered is longer than the parameter width.
REP-0526:  The initial value you have entered is longer than the parameter width.

Cause:	You entered a value that is too long for the parameter on the Parameter property palette.  The possible causes of this error include the following:
	Case 1:	You entered a value in Initial Value that is too big, given what you specified for the parameter's Width.
	Case 2:	You entered a value for Width that is too small to contain the values you want to be able to enter for the parameter.
Action:	You can take the following actions to correct this error:
	If Case 1:	Re-enter the Initial Value, making sure that it is not wider than what you specified in Width.
	If Case 2:	Delete the Initial Value you have entered.  Move to the Width setting for the parameter and increase it such that it can contain the Initial Value you had specified.  Re-enter the Initial Value.


REP-0527You cannot delete a system parameter.
REP-0527:  You cannot delete a system parameter.

Cause:	You tried to delete a packaged parameter from the Parameter property palette.
Action:	Report Builder will not allow you to delete a system parameter.  However, you can suppress the display of the parameter on the Runtime Parameter Form by using the Default Parameter Form dialog box or the Parameter Form editor.  For more information, see Parameter Form Editor.


REP-0528Valid options are 'Character', 'Number' or 'Date'.
REP-0528:  Valid options are 'Character', 'Number' or 'Date'.

Cause:	The datatype you entered in Datatype for the parameter was not one of the valid datatypes.
Action:	Select a datatype for Datatype from the list of values.


REP-0529Valid options are 'Box', 'Graphic', 'Line' or 'Text'.
REP-0529:  Valid options are 'Box', 'Graphic', 'Line' or 'Text'.

Cause:	The value you entered in Type for the boilerplate was not one of the valid types.
Action:	Select a value for Type from the list of values.


REP-0530File too long.  It will be truncated to fit.
REP-0530:  File too long.  It will be truncated to fit.

Cause:	You tried to import a file into a field that has a maximum width less than the size of the file.  Report Builder only imported as much of the file as could fit in the field.
Action:	If you wish to import the entire file, increase the size of the field.


REP-0531Invalid Object Type.  See the list of values.
REP-0531:  Invalid Object Type.  See the list of values.

Cause:	In the Navigate to Object dialog box, you entered an invalid value for Object Type.
Action:	Select a value from the list of values.


REP-0532There is no object of that type with this name.
REP-0532:  There is no object of that type with this name.

Cause:	The value you entered in the Object Name field of the Navigate to Object dialog box does not correspond to an object of the specified type in the report.
Action:	Make sure that you specified the name correctly and that the object is contained in the current report.


REP-0533You can only import to a text entry field.
REP-0533:  You can only import to a text entry field.

Cause:	You selected Edit [image] Import while in a non-text entry field (e.g., a field that accepts only a number).
Action:	If you wish to import something, move to a text entry field to do so.


REP-0534You can only export from a text entry field.
REP-0534:  You can only export from a text entry field.

Cause:	You selected Edit [image] Export while in a non-text entry field (e.g., a field that accepts only a number).
Action:	If you wish to export something, move to a text entry field to do so.


REP-0535There is no object named '<object name>' in the database.
REP-0535:  There is no object named '<object name>' in the database.

Cause:	You tried to perform an operation on a document stored in the database, but Report Builder could not find the object.
Action:	Make sure that you specified the name correctly and are connected to the database where the document resides.


REP-0536You cannot delete an object in the database that you do not own.
REP-0536:  You cannot delete an object in the database that you do not own.

Cause:	You tried to delete an object that you do not own.  To delete an object, you must be the object's owner.
Action:	Have the owner delete the object, if possible.


REP-0537You cannot rename an object in the database that you do not own.
REP-0537:  You cannot rename an object in the database that you do not own.

Cause:	You tried to rename an object that you do not own.  To rename an object, you must be the object's owner.
Action:	Have the owner rename the object, if possible.


REP-0538There is already an object named '<object name>' in the database.
REP-0538:  There is already an object named '<object name>' in the database.

Cause:	The name that you entered for the object is already used for an existing object.
Action:	Give the object a different name to avoid the conflict or delete the existing object.


REP-0539Default parameter form could not be fitted in <number> page(s).
REP-0539:  Default parameter form could not be fitted in <number> page(s).

Cause:	The default parameter form is too big to fit on the number of pages specified.
Action:	Select Tools [image] Default Parameter Form.  Increase the number of pages that the parameter form can span.


REP-0540Page size too small for default parameter form.
REP-0540:  Page size too small for default parameter form.

Cause:	The current Form Width and Form Height settings are too small for the default parameter form.
Action:	Increase the size of the parameter form pages in the Report property palette by changing Form Width and Form Height.  Alternatively, you can default the parameter form by selecting Tools [image] Default Parameter Form and reduce its size by editing it in the Parameter Form editor.


REP-0541Source must be a report.
REP-0541:  Source must be a report.

Cause:	For RWRUN60, RWCON60, or File [image] Convert, you specified something other than a report as the source.  These operations all require a report as their source.
Action:	Specify a report as the source for the operation.


REP-0542No date masks have been specified as preferences.
REP-0542:  No date masks have been specified as preferences.

Cause:	While in the Parameter or Field property palette of a parameter/field of Type Date, you chose the List button for Input Mask or Format Mask, but no masks are specified in the Date Mask list of the Preferences tab of the Tools Options dialog box.
Action:	Enter a date format mask manually or go to the Preferences tab of the Tools Options dialog box and enter some date format masks in the Date Mask list.


REP-0543No number masks have been specified as preferences.
REP-0543:  No number masks have been specified as preferences.

Cause:	While in the Parameter or Field property palette of a parameter/field of Type Number, you chose the List button for Input Mask or Format Mask, but no masks are specified in the Number Mask list of the Preferences tab of the Tools Options dialog box.
Action:	Enter a number format mask manually or go to the Preferences tab of the Tools Options dialog and enter some number format masks in the Number Mask list.


REP-0544The on-line help system is not available.
REP-0544:  The on-line help system is not available.

Cause:	You selected Help [image] Help System, but help could not be found.  This may have happened because the help files could not be found or because of a help system error.
Action:	Ensure that the help files and help system are properly installed.  If they are and the error persists, you should contact Oracle Customer Support for assistance.  For more information, see Calling Oracle Customer Support.


REP-0545The number must be greater than 0.
REP-0545:  The number must be greater than 0.

Cause:	You entered zero for Page Width, Page Height, or Logical Page Size in the Report property palette.  You must enter a number greater than zero.
Action:	Enter a number greater than zero for Page Width, Page Height, or Logical Page Size.


REP-0546Invalid parameter input.
REP-0546:  Invalid parameter input.

Cause:	In the Runtime Parameter Form, you entered an invalid value for a parameter.  For example, you entered one or more characters as the value of parameter with a datatype of Number.
Action:	Re-try the operation, entering a valid value for the parameter.


REP-0548Problem initializing Oracle Toolkit.
REP-0548:  Problem initializing Oracle Toolkit.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0549Destination type must be 'File', 'Printer', 'Mail', or 'Sysout' in batch mode.
REP-0549:  Destination type must be 'File', 'Printer', 'Mail', or 'Sysout' in batch mode.

Cause:	You tried to run a report in the background (i.e., BATCH=YES), but you specified a DESTYPE that is invalid for running in the background.
Action:	Change the DESTYPE to File, Printer, Mail, or Sysout, or do not run the report with BATCH=YES.


REP-0550Invalid Parent Group.
REP-0550:  Invalid Parent Group.

Cause:	The name you entered does not identify a valid parent group in the report you are currently defining.
Action:	Select a group from the list of values.


REP-0551Invalid Parent Column.
REP-0551:  Invalid Parent Column.

Cause:	The name you entered does not identify a valid parent column in the report you are currently defining.  The column you specified does not exist in the parent group.
Action:	Select a column from the list of values.  If the column you want does not appear, add it to the SELECT statement of the parent query of the group specified in Parent Group.


REP-0552Invalid Child Column.
REP-0552:  Invalid Child Column.

Cause:	The name you entered does not identify a valid child column in the report you are currently defining.  The column you specified does not exist in the query.
Action:	Select a column from the list of values.  If the column you want does not appear, add it to the SELECT statement of the query.


REP-0553Invalid Condition.
REP-0553:  Invalid Condition.

Cause:	The Condition you entered for the query is not among the valid choices.
Action:	Select a value from the list of values for Condition.


REP-0554Valid options are 'WHERE', 'HAVING' or 'START WITH'.
REP-0554:  Valid options are 'WHERE', 'HAVING' or 'START WITH'.

Cause:	The value you entered in SQL Clause is not one of the valid choices.
Action:	Select a value from the list of values for SQL Clause.


REP-0555Warning: 'START WITH' is ORACLE-specific SQL syntax.  Report will not run against non-ORACLE database.
REP-0555:  Warning: 'START WITH' is ORACLE-specific SQL syntax.  Report will not run against non-ORACLE database.

Cause:	The START WITH clause is only available with the ORACLE database.  If you are not connected to any database or you are connected to a non-ORACLE database, this warning is raised.
Action:	Ensure that you either run the report against an ORACLE database or remove the START WITH clause before running it against a non-ORACLE database.


REP-0556No data links were created. No foreign key in the child query '<query name>' refers to a primary key in the parent query '<query name>'.
REP-0556:  No data links were created. No foreign key in the child query '<query name>' refers to a primary key in the parent query '<query name>'.

Cause:	You attempted to create a query-to-query link but no foreign key exists in the child query.
Action:	Verify whether the tables referred to are on your local database and accessible.  If so, add the appropriate column constraints if desired.


REP-0558Note:  The query '$0' has created lexical parameter '$1'.
REP-0558:  Note:  The query '<query name>' has created the lexical parameter(s) '<parameter name>'.

Cause:	The specified query references a lexical parameter(s) that did not exist.
Action:	None.  Report Builder has already created the necessary lexical parameter(s).


REP-0559Note: The query '<query name>' has created the bind parameter '<parameter name>'.
REP-0559:  Note: The query '<query name>' has created the bind parameter(s) '<parameter name>'.

Cause:	The specified query references a bind parameter(s) that did not exist.
Action:	None.  Report Builder has already created the necessary bind parameter(s).


REP-0560Invalid Group.
REP-0560:  Invalid Group.

Cause:	The group name you entered in Group is not a valid group for the column.  The group you specified does not exist or cannot own the column.
Action:	Create or modify the group such that it can own the column.  A database column must be owned by the group associated with the query that selects it.  A summary or formula column must be owned by a group that is below the group(s) that owns the columns being summarized in the group hierarchy (i.e., the order of groups as they appear in the Data Model editor).


REP-0561Valid options are 'Formula', 'Summary' or 'Placeholder'.
REP-0561:  Valid options are 'Formula', 'Summary' or 'Placeholder'.

Cause:	The value you entered in Type for the column was not one of the valid choices.
Action:	Select a value from the list of values for the column's Type.


REP-0562Invalid Column Datatype. See the list of values.
REP-0562:  Invalid Column Datatype. See the list of values.

Cause:	The value you entered in Datatype is not one of the valid choices.
Action:	Select a value from the list of values for Datatype.


REP-0563Valid options are 'Ascending', 'Descending', or blank.
REP-0563:  Valid options are 'Ascending', 'Descending', or blank.

Cause:	The value you entered in Datatype is not one of the valid choices.
Action:	Select a value from the list of values for Datatype.


REP-0564Invalid File Type.
REP-0564:  Invalid File Type.

Cause:	The file type value you entered in Read From File was not one of the valid types.  You either misspelled the value or the value you entered does not exist.
Action:	Select a file type from the list of values for Read from File.


REP-0565Invalid Function.  See the list of values.
REP-0565:  Invalid Function.  See the list of values.

Cause:	The function you entered for Function is not one of the valid choices.
Action:	Select one of the functions from the list of values.


REP-0566You may not delete a database column.
REP-0566:  You may not delete a database column.

Cause:	You tried to delete a column with a Type of Database.
Action:	Remove the column from the SELECT list of the query that selects it and the column will be deleted automatically.


REP-0567Invalid Summary Source. See the list of values.
REP-0567:  Invalid Summary Source. See the list of values.

Cause:	The column you entered in Source for the summary is not one of the valid choices.  The possible causes of this error include the following:
	Case 1:	The column does not exist.
	Case 2:	The Datatype of the Source is Character or Date.  You cannot use numeric functions (such as Percent, Sum, or Average) unless the Datatype is Number.
Action:	You can take the following actions to correct this error:
	If Case 1:	Select a column from the list of values for the function.
	If Case 2:	Enter the name of another column in Source that is of Datatype Number.


REP-0568Value if Null is invalid.
REP-0568:  Value if Null is invalid.

Cause:	The value of Value if Null in the Column property palette is invalid for that column.  For example, if datatype of the column is Number, and you specify a character string in Value if Null, you will receive this error.
Action:	Specify a valid value for Value if Null.


REP-0580Invalid Filter Type.  See the list of values.
REP-0580:  Invalid Filter Type.  See the list of values.

Cause:	The value you entered for Type under Filter is not one of the valid choices.
Action:	Select one of the filter types from the list of values.


REP-0581This is the only group of query '<query name>', and may not be deleted.
REP-0581:  This is the only group of query '<query name>', and may not be deleted.

Cause:	The group you tried to delete is the only one of the query.  Each query must have at least one group.
Action:	If you want to delete the group, delete the group's query.


REP-0582You cannot move a group out of its query.
REP-0582:  You cannot move a group out of its query.

Cause:	You cannot move a group between queries.  Groups can only be moved within the set of groups belonging to the same query.
Action:	You can create a group similar to the one you were trying to move under the other query, if possible.


REP-0583Invalid SQL Select Statement.
REP-0583:  Invalid SQL Select Statement.

Cause:	The SQL SELECT statement that you entered is not valid.
Action:	Check the SELECT statement for errors and correct them.  For more information, see the ORACLE8 Server SQL Language Reference Manual.


REP-0584Lexical parameters are not permitted in External Queries.
REP-0584:  Lexical parameters are not permitted in External Queries.

Cause:	You made a lexical reference in your external query.  You cannot make lexical references from an external query.
Action:	Delete the reference altogether or, if possible, change it to a bind reference.


REP-0585Parent group <group name> for child query <query name> nonexistent.
REP-0585:  Parent group <group name> for child query <query name> nonexistent.

Cause:	You have deleted a query without deleting references to its groups in data links.  This usually happens when you have deleted a query without cascading the deletion to its associated objects.
Action:	Update the data link in the child query.


REP-0586Adding this data link will create a cycle.
REP-0586:  Adding this data link will create a cycle.

Cause:	The group you specified as the parent group for the data link is not eligible to be a parent because it is, directly or indirectly, a child of the query to which you are linking it.
Action:	If possible, move the group such that it is not a child of the query and therefore eligible to be its parent group.  Otherwise, there is no action you can take.


REP-0587Invalid PL/SQL Group Filter condition.
REP-0587:  Invalid PL/SQL Group Filter condition.

Cause:	You selected Condition for Filter Type, but entered no PL/SQL condition.
Action:	Enter your PL/SQL or change the Filter Type.  For more information about using PL/SQL within Report Builder, see PL/SQL Interface.  For more information about PL/SQL, see the PL/SQL User's Guide and Reference.


REP-0588Invalid PL/SQL Column Formula.
REP-0588:  Invalid PL/SQL Column Formula.

Cause:	You selected Formula as the column's Type, but entered no PL/SQL for the formula.
Action:	Create a formula or change the column's Type.  For more information about using PL/SQL within Report Builder, see PL/SQL Interface.  For more information about PL/SQL, see the PL/SQL User's Guide and Reference.


REP-0590Only <number> page(s) formatted.  Last page is shown.
REP-0590:  Only <number> page(s) formatted.  Last page is shown.

Cause:	In the Previewer, you tried to go to a page number that is larger than the total number of pages formatted, i.e., you tried to go to a page that does not exist.
Action:	None.  You cannot scroll down from the last page of the report.


REP-0591You are already on the first page.
REP-0591:  You are already on the first page.

Cause:	In the Previewer, you selected First while you were already on the first page of the report.
Action:	None.  You cannot scroll up from the first page of the report.


REP-0592You are already on the last page.
REP-0592:  You are already on the last page.

Cause:	In the Previewer, you selected Last while you were already on the last page of the report.
Action:	None.  You cannot scroll down from the last page of the report.


REP-0593Page <page number> is the current page.
REP-0593:  Page <page number> is the current page.

Cause:	In the Previewer, you entered the page number of the current page and chose Go To.
Action:	If you intended to go to another page, enter a different page number and chose Go To.


REP-0594No report output generated.
REP-0594:  No report output generated.

Cause:	The report you ran resulted in no output.
Action:	Check the accompanying messages for errors in the data model and layout.  If the problem persists, contact Oracle Customer Support for assistance.  For more information, see Calling Oracle Customer Support.


REP-0595Report definition modified.  Re-running report.
REP-0595:  Report definition modified.  Re-running report.

Cause:	You ran a report and while its output was still in the Previewer you modified the report definition.  If you return to the Previewer without re-running the report, the report output is not updated to reflect the most recent changes and, consequently, the report must be run again.
Action:	Close the Previewer and run the report again.


REP-0596Number cannot be greater than <number> or less than 1.
REP-0596:  Number cannot be greater than <number> or less than 1.

Cause:	You entered an invalid value for the Page Number setting on the Field property palette for a parameter form field.  The most likely cause is that you entered zero, a negative number, or a number that is larger than the largest allowable value.
Action:	Enter a number within the range shown in the message.


REP-0597This operation is invalid, since it moves object(s) out of boundary.
REP-0597:  This operation is invalid, since it moves object(s) out of boundary.

Cause:	You tried to move editor objects in such a way that they would be off the screen.
Action:	Re-try the operation so that it will not move objects off the screen.


REP-0598You have moved the anchor end point out the boundary of the object, please try again.
REP-0598:  You have moved the anchor end point out the boundary of the object, please try again.

Cause:	In moving an anchor, you moved the end point off of the boundary of the object it anchors.
Action:	Move the anchor such that its endpoint is still on the boundary of the object.


REP-0599This text boilerplate is not editable.
REP-0599:  This text boilerplate is not editable.

Cause:	You attempted to edit the text of a link file boilerplate object while it was displayed in the Layout Model editor.
Action:	If you wish to edit the text of a link file boilerplate object, exit the report and edit the file containing the link file boilerplate text using a text editor.


REP-0600There is no list of values available for this field.
REP-0600:  There is no list of values available for this field.

Cause:	You attempted to access a list of values for the current field when none is available.
Action:	No action necessary.


REP-0601The list of values for this field is empty.
REP-0601:  The list of values for this field is empty.

Cause:	You tried to select from a list of values and the list of values has no values.  In order for some lists of values to contain values, another part of your report must be built first.  For example, if a list of values is made up solely of column names and you have not completed your data model, you may get this error.
Action:	Building your report fully should fix this error.  If the error persists, contact Oracle Customer Support.  For more information, see Calling Oracle Customer Support.


REP-0602Unable to query accessible tables.
REP-0602:  Unable to query accessible tables.

Cause:	The dictionary view of accessible tables is not present or not available.
Action:	See your DBA.


REP-0603Unable to describe table '<table name>'.
REP-0603:  Unable to describe table '<table name>'.

Cause:	The dictionary view of accessible tables is not present or not available.
Action:	See your DBA.


REP-0604Unable to build SELECT statement - no values selected.
REP-0604:  Unable to build SELECT statement - no values selected.

Cause:	You accepted the Table and Columns Names dialog box without having selected anything with which to build the SELECT statement.  If you choose the columns or table radio button, but no columns or tables are selected when you accept the dialog box, you will get this error message.
Action:	Select a table and, if desired, column(s) or choose the SELECT columns FROM table radio button, and then accept the dialog box.  To exit the dialog box without building a SELECT statement, choose the Close button.


REP-0606Unable to read link file '<filename>'. Check link file format.
REP-0606:  Unable to read link file '<filename>'. Check link file format.

Cause:	The file you specified in the Link File field of the Boilerplate property palette cannot be found or its format does not match that specified in the Format field.
Action:	Ensure that you correctly specified the name of the file and that the value you entered in the Format field matches the format of the file.


REP-0607Run-only file '<filename>' may not be opened.
REP-0607:  Run-only file '<filename>' may not be opened.

Cause:	You attempted to open a runfile (extension .rep).  Runfiles cannot be opened, they can only be executed.
Action:	Open the report definition that is associated with the .rep file.  It should have an extension of .rdf.


REP-0608Invalid Source Type.  See the list of values.
REP-0608:  Invalid Source Type.  See the list of values.

Cause:	You selected File-->Convert... and the source type that you specified is not valid.
Action:	Select the source type from the list of values.


REP-0609Invalid Destination Type.  See the list of values.
REP-0609:  Invalid Destination Type.  See the list of values.

Cause:	You selected File-->Administration-->Convert... and the destination type is not valid.
Action:	Select the destination type from the list of values.


REP-0610Error while attempting to print screen.  Make sure log file '<filename>' is accessible.
REP-0610:  Error while attempting to print screen.  Make sure log file '<filename>' is accessible.

Cause:	Report Builder attempted to write the contents of the screen to the file printdef.dat but could not locate the file.
Action:	To determine the proper location for printdef.dat, see your installation guide.


REP-0611Valid options are 'Screen', 'File', 'Printer', or 'Mail'.
REP-0611:  Valid options are 'Screen', 'File', 'Printer', or 'Mail'.

Cause:	In the Runtime Parameter Form, you provided a value for Destination Type that was not valid.
Action:	Specify a value of Screen, File, Printer, or Mail for Destination Type.


REP-0612Invalid date mask.
REP-0612:  Invalid date mask.

Cause:	The date mask that you entered does not correspond to any of the valid date masks.
Action:	Check to make sure that you entered the mask correctly.  For more information, see Format Mask.


REP-0613Value does not match mask '<mask string>'.
REP-0613:  Value does not match mask '<mask string>'.

Cause:	The mask you entered in Format Mask is not a valid mask.   The possible causes of this error include the following:
	Case 1:	The string that you entered as a mask contained invalid characters.
	Case 2:	You entered a number format mask for a field with Datatype of Character.
Action:	You can take the following actions to correct this error:
	If Case 1:	Select a value from the list of values.  For more information, see Format Mask.
	If Case 2:	Change the Datatype of the field to be Number, if possible.  If the field is supposed to be Character Datatype and cannot be changed, you cannot have a format mask for it.


REP-0614There is no window active for your Find and Replace action.
REP-0614:  There is no window active for your Find and Replace action.

Cause:	You attempted a Find and Replace operation using the Find and Replace dialog box, but did not have the cursor positioned in an active Report Builder window.
Action:	Position your cursor in a text entry field before you perform a search/replace operation.


REP-0615You can only Find and Replace a text entry field.
REP-0615:  You can only Find and Replace a text entry field.

Cause:	You attempted a Find and Replace operation using the Find and Replace dialog box, but did not have the cursor positioned in a text entry field.  Find and Replace operations are valid only in text entry fields.
Action:	Position your cursor in a entry field before you perform a Find and Replace operation.


REP-0616You cannot replace text in an uneditable region.
REP-0616:  You cannot replace text in an uneditable region.

Cause:	Using the Find and Replace dialog box, you attempted to replace text in an inaccessible field.
Action:	You can replace text only in editable regions.


REP-0617Warning: Runtime Parameter Form is already open. To run a new one, please close the old one and run again.
REP-0617:  Warning: Runtime Parameter Form is already open. To run a new one, please close the old one and run again.

Cause:	You tried to run a report with the Runtime Parameter Form already open.
Action:	Close the currently open Runtime Parameter Form and try running again.


REP-0619You cannot run without a layout.
REP-0619:  You cannot run without a layout.

Cause:	You attempted to run your report with no layout.  The report would be empty.
Action:	Create a layout, then run your report.


REP-0621Invalid Vertical Elasticity. See the list of values.
REP-0621:  Invalid Vertical Elasticity. See the list of values.

Cause:	The value you entered for the object's Vertical Elasticity is not one of the valid values.
Action:	Select a value from the list of values.


REP-0622Invalid Horizontal Elasticity. See the list of values.
REP-0622:  Invalid Horizontal Elasticity. See the list of values.

Cause:	The value you entered for the object's Horizontal Sizing is not one of the valid values.
Action:	Select a value from the list of values.


REP-0623Invalid Print Condition Type. See the list of values.
REP-0623:  Invalid Print Condition Type. See the list of values.

Cause:	The value you entered for the Type of the Print Condition is not one of the valid values.
Action:	Select a value from the list of values.


REP-0624Invalid Print Condition Object. See the list of values.
REP-0624:  Invalid Print Condition Object. See the list of values.

Cause:	The value you entered for the Object of the Print Condition is not one of the valid values.
Action:	Select a value from the list of values.


REP-0625Invalid Text Alignment. See the list of values.
REP-0625:  Invalid Text Alignment. See the list of values.

Cause:	The value you entered for Alignment was not one of the valid values.  The value is not valid given the datatype of the object.  Flush/Left, Flush/Center, and Flush/Right are only valid for fields with Datatype of Character.
Action:	Select a value from the list of values.


REP-0626You must specify the object's position.
REP-0626:  You must specify the object's position.

Cause:	You entered an x or y coordinate that is not in the valid range for coordinates.  Coordinates cannot be negative numbers.
Action:	Enter a coordinate that is in the valid range.


REP-0627An object's height or width must be a positive integer.
REP-0627:  An object's height or width must be a positive integer.

Cause:	The Width or Height value that you entered was not a positive, whole number.
Action:	Enter a positive, whole number.


REP-0630Value must be between <number1> and <number2>.
REP-0630:  Value must be between <number1> and <number2>.

Cause:	The number that you entered is too large or too small.
Action:	Specify a number that is within the range shown in the message.


REP-0631String must be no longer than <number> character(s).
REP-0631:  String must be no longer than <number> character(s).

Cause:	The string that you entered is too large.
Action:	Enter a string that is smaller than the number of characters shown in the message.


REP-0632Value already exists in the list.
REP-0632:  Value already exists in the list.

Cause:	You attempted to add an item to a list, but the item was previously added to the list.  For example, if you attempted to add lib1 to your report's Attached PL/SQL Library list, and lib1 was already found in the Attached PL/SQL Library list, you would receive this error.
Action:	Once an item has been added to a list, it does not need to be added again.


REP-0633No value specified.
REP-0633:  No value specified.

Cause:	You attempted to perform a list operation on an item, but you did not specify an item.  For example, if you attempted to add a PL/SQL library to your report's Attached PL/SQL Library list, but you left the PL/SQL Library field in the Attached PL/SQL Libraries dialog box blank and chose the Add button, you would receive this error.
Action:	Specify the item you wish to add in the appropriate field before choosing a button.


REP-0634Destination name must be shorter than <number> characters.
REP-0634:  Destination name must be shorter than <number> characters.

Cause:	You specified a destination (probably a filename) that is too long.  Destination names must be shorter in length.
Action:	Specify the filename again and ensure that it is of valid length.


REP-0635Value does not exist in the list.
REP-0635:  Value does not exist in the list.

Cause:	You specified a value that is not in the list of valid choices.  It could be that you typed the value rather than using the list of values.
Action:	Specify one of the valid choices in the list.  If possible, use the list of values to ensure that it is a valid choice.


REP-0636$0 must be no longer than $1 character(s). It will be truncated.
REP-0636:  <property name> must be no longer than <number> character(s). It will be truncated.

Cause:	You specified a string that is longer than is allowable.  It will be truncated.
Action:	Specify a shorter string.


REP-0637$0 must be no longer than $1 character(s). Please reenter.
REP-0637:  <property name> must be no longer than <number> character(s). Please reenter.

Cause:	You specified a filename that is longer than is allowable.
Action:	Specify a shorter filename.


REP-0640Invalid Field Source. See the list of values.
REP-0640:  Invalid Field Source. See the list of values.

Cause:	You entered an invalid value in the field's Source setting.
Action:	Select a value from the list of values.


REP-0650Invalid Source Group. See the list of values.
REP-0650:  Invalid Source Group. See the list of values.

Cause:	The group name you entered in Source for the repeating frame is not valid.
Action:	Select a value from the list of values.


REP-0651Invalid Print Direction. See the list of values.
REP-0651:  Invalid Print Direction. See the list of values.

Cause:	The value you entered for Print Direction was not one of the valid values (Across, Across/Down, Down, Down/Across, and Matrix Cell).
Action:	Select a value from the list of values.


REP-0652Invalid Vertical Spacing.
REP-0652:  Invalid Vertical Spacing.

Cause:	You did not enter a number for the Vertical Spacing field and you tried to leave the field or accept the Repeating Frame property palette.
Action:	Enter zero or a positive integer for Vertical Spacing.


REP-0653Invalid Horizontal Spacing.
REP-0653:  Invalid Horizontal Spacing.

Cause:	You did not enter a number for the Horizontal Spacing field and you tried to leave the field or accept the Repeating Frame property palette.
Action:	Enter zero or a positive integer for Horizontal Spacing.


REP-0654Invalid value for maximum records per page.
REP-0654:  Invalid value for maximum records per page.

Cause:	You did not enter a number or blank for Maximum Records per Page and you tried to leave the field or accept the Repeating Frame property palette.
Action:	Enter blank or a positive integer for Maximum Records per Page.


REP-0655Invalid value for minimum widow records.
REP-0655:  Invalid value for minimum widow records.

Cause:	You did not enter a number or blank for Minimum Widow Records and you tried to leave the field or accept the Repeating Frame property palette.
Action:	Enter blank or a positive integer for Minimum Widow Records.


REP-0660Invalid button source. You must select a column.
REP-0660:  Invalid button source. You must select a column.

Cause:	You selected Multimedia Column as the source for your button action, then either did not specify a source column, or specified an invalid source column.
Action:	Check to make sure you specified a source column for your button action, and, if so, make sure it contains either sounds, video, or images.


REP-0661Invalid button source. You must specify a source file.
REP-0661:  Invalid button source. You must specify a source file.

Cause:	You selected Multimedia File as the source for your button action, then either did not specify a source file, or specified an invalid source file.
Action:	Check to make sure you specified a source file for your button action, and, if so, make sure it is either sound, video, or image.


REP-0662Invalid button icon.
REP-0662:  Invalid button icon.

Cause:	You selected Icon as the button face, but failed to name a valid icon.
Action:	Enter the name of a valid icon file in the text field provided.  Include all necessary path information.


REP-0670Valid options are 'Box', 'Graphic', 'Line' or 'Text'.
REP-0670:  Valid options are 'Box', 'Graphic', 'Line' or 'Text'.

Cause:	The value you entered in Type for the boilerplate was not one of the valid values (Box, Line, Graphic, and Text).
Action:	Select a Type from the list of values.


REP-0671Invalid link file name.
REP-0671:  Invalid link file name.

Cause:	The file to which you tried to link the boilerplate is not a valid file.
Action:	Re-enter the name, making sure that it references an existing file in the current directory.


REP-0672Invalid value for minimum widow lines.
REP-0672:  Invalid value for minimum widow lines.

Cause:	You did not enter a number or blank for Minimum Widow Lines in the property palette and you tried to leave the field or accept the property palette.
Action:	Enter blank or a positive integer for Minimum Widow Lines.


REP-0680Invalid anchoring object name. See the list of values.
REP-0680:  Invalid anchoring object name. See the list of values.

Cause:	The object name you entered in the Anchored To field of the Anchor Position dialog box is not the name of an object to which you can anchor this object.  You tried to accept the dialog box without entering a valid anchoring object name.
Action:	Select an object name for Anchored To from the list of values.


REP-0681Invalid Edge. See the list of values.
REP-0681:  Invalid Edge. See the list of values.

Cause:	The value you entered in Edge is not one of the valid values (Top, Left, Right, and Bottom).  You tried to leave the Parent Edge or Object Edge field without entering a valid edge for the anchor.
Action:	Select a value for Parent Edge or Object Edge from the list of values.


REP-0682The anchor point must be a percentage between 0 and 100.
REP-0682:  The anchor point must be a percentage between 0 and 100.

Cause:	The value you entered for % is not in the valid range (0 to 100).  You tried to accept the dialog box or move to another field without entering a valid value for %.
Action:	Enter a value in the valid range for %.


REP-0690Invalid Starting Page Number.
REP-0690:  Invalid Starting Page Number.

Cause:	You left Start At blank.  You tried to leave the Start At field or accept the Page Numbering dialog box without entering a value for Start At.
Action:	Enter zero or a positive integer for Start At.


REP-0691Invalid Page Increment.
REP-0691:  Invalid Page Increment.

Cause:	You left Increment By blank.  You tried to leave the Increment By field or accept the Page Numbering dialog box without entering a value for Increment By.
Action:	Enter zero or a positive whole number for Increment By.


REP-0692Invalid Page Number Reset.
REP-0692:  Invalid Page Number Reset.

Cause:	You left Reset At blank.  You tried to leave the Reset At field or accept the Page Numbering dialog box without entering a value for Reset At.
Action:	Select a repeating frame name or &Report from the list of values to indicate where you want to reset the page number to its Start At value.


REP-0700Invalid Color. See the list of values.
REP-0700:  Invalid Color. See the list of values.

Cause:	The color that you entered in the field is not one of the valid choices.
Action:	Select a color for the field from the list of values.


REP-0701Invalid Pattern. See the list of values.
REP-0701:  Invalid Pattern. See the list of values.

Cause:	The pattern that you entered in the field is not one of the valid choices.
Action:	Select a pattern for the field from the list of values.


REP-0702Invalid Pen Width.
REP-0702:  Invalid Pen Width.

Cause:	The value that you entered for the pen width is not one of the valid choices.
Action:	Select a pen width from the list of values.


REP-0703Invalid Font. See the list of values.
REP-0703:  Invalid Font. See the list of values.

Cause:	The font that you entered is not one of the valid choices.
Action:	Select a font from the list of values.


REP-0704Invalid Text Style. See the list of values.
REP-0704:  Invalid Text Style. See the list of values.

Cause:	The text style you entered is not one of the valid styles.
Action:	Select one of the styles from the list of values.


REP-0705Invalid Text Weight. See the list of values.
REP-0705:  Invalid Text Weight. See the list of values.

Cause:	The text weight you entered is not one of the valid weights.
Action:	Select one of the weights from the list of values.


REP-0706Invalid Text Size.
REP-0706:  Invalid Text Size.

Cause:	The point size that you entered is not one of the valid choices.
Action:	Select a valid point size from the list of values.


REP-0707Invalid Text Spacing.
REP-0707:  Invalid Text Spacing.

Cause:	You have entered number for spacing that is not in the valid range.
Action:	Enter a number in the valid range.


REP-0708Invalid Character Mode Attribute. See the list of values.
REP-0708:  Invalid Character Mode Attribute. See the list of values.

Cause:	The value you entered in this field is not valid.  The values you enter in Character Mode Attribute must be defined in your Oracle Terminal or printer definition. (To have these attributes appear in the list of values, you must also list them in VISUAL_PREFS in the preferences file.)
Action:	Select the desired values from the list of values.  If the value you want is not in the list of values, you can check your Oracle Terminal or printer definition to see if the value is a valid one.


REP-0709'Sysout' is only valid in batch mode.
REP-0709:  'Sysout' is only valid in batch mode.

Cause:	You entered Sysout as the destination type when you were not running the report in batch mode.  The possible causes of this error include the following:
	Case 1:	You entered Sysout for DESTYPE in the Runtime Parameter Form.
	Case 2:	You have Sysout as the Initial Value for DESTYPE and you accepted it when not running in batch mode.  You might have accepted it without knowing it if you have the Hide Parameter Form preference checked.
Action:	You can take the following actions to correct this error:
	If Case 1:	Run the report again, but enter a DESTYPE of something other than Sysout unless you are running in batch mode.
	If Case 2:	Change the Initial Value for DESTYPE to something else or change the DESTYPE to something other than Sysout in the Runtime Parameter Form.  If you leave the Initial Value as Sysout, you should not run in non-batch mode with Hide Parameter Form checked.


REP-0710Unable to find printer description file.
REP-0710:  Unable to find printer description file.

Cause:	Report Builder could not find the printer description file you specified for DESFORMAT.
Action:	Specify a valid printer description file for DESFORMAT (e.g., dflt).


REP-0711Destination type must be 'File', 'Printer', or 'Mail' when printing from previewer.
REP-0711:  Destination type must be 'File', 'Printer', or 'Mail' when printing from previewer.

Cause:	You pressed the Print button in the Previewer, but DESTYPE is restricted to a value other than File, Printer, or Mail.
Action:	Ensure that DESTYPE can be set to one of the above values before attempting to print from the Previewer.


REP-0712No printer specified.
REP-0712:  No printer specified.

Cause:	You attempted to print a report, but did not specify a printer name in either DESNAME or in the Printer Chooser dialog box.
Action:	Specify a valid printer name using DESNAME.  If you often print to the same printer, enter the printer name in the Printer Chooser dialog box.  Remember that entering a printer name using DESFORMAT will override the printer name set in the Printer Chooser dialog box.


REP-0713Invalid printer name '<name>' specified by parameter <parameter name>.
REP-0713:  Invalid printer name '<name>' specified by parameter <parameter name>.

Cause:	You attempted to output a report, but did not specify a valid printer name in DESFORMAT (if DESTYPE was File or Mail) or DESNAME (if DESTYPE was Printer).
Action:	Specify a valid printer name for DESFORMAT if DESTYPE was File or Mail, or a valid printer name for DESNAME if DESTYPE was Printer.


REP-0714Invalid mail destination.
REP-0714:  Invalid mail destination.

Cause:	You attempted to mail report output to another user, but did not specify a valid username for DESNAME.
Action:	Specify a valid username for DESNAME.


REP-0715Trace file must be specified when tracing.
REP-0715:  Trace file must be specified when tracing.

Cause:	You specified trace mode and/or trace options but did not specify a trace file.
Action:	Specify a trace file.


REP-0716Invalid option specified for tracing.
REP-0716:  Invalid option specified for tracing.

Cause:	You specified invalid trace options.
Action:	Re-specify your trace options.  For more information, see TRACEOPTS.


REP-0717Cannot set/unset options if not tracing.
REP-0717:  Cannot set/unset options if not tracing.

Cause:	You attempted to set or unset trace options while not tracing.
Action:	Begin tracing before you attempt to set or unset options.


REP-0718Cannot trace break information with runtime executable.
REP-0718:  Cannot trace break information with runtime executable.

Cause:	You attempted to trace breaks while running the report using the runtime executable.
Action:	Do not specify the Break option when using the runtime executable.


REP-0719Cannot write to trace file '<filename>'.
REP-0719:  Cannot write to trace file '<filename>'.

Cause:	You specified a trace file to which you cannot write.
Action:	Check the given trace file name to ensure that it is valid.


REP-0720Invalid Repeating Frame.  See the list of values.
REP-0720:  Invalid Repeating Frame.  See the list of values.

Cause:	The repeating frame that you specified as the Vertical or Horizontal Frame in the Matrix property palette is not valid.  You tried to leave the Vertical or Horizontal Frame field without entering a valid repeating frame.
Action:	Select a repeating frame name from the list of values.


REP-0721Invalid Cross Product Group.  See the list of values.
REP-0721:  Invalid Cross Product Group.  See the list of values.

Cause:	The group that you entered for Cross Product Group in the Matrix property palette is not valid.
Action:	Select a group name from the list of values.


REP-0724Cannot get the value of Column '<column name>' here.
REP-0724:  Cannot get the value of Column '<column name>' here.

Cause:	You attempted to get the value of the specified column via either issuing a command from the command line of the PL/SQL  Interpreter or by executing a stand-alone PL/SQL program unit.  You can only get a column value during report execution.
Action:	Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a column when the report has suspended execution (e.g., at a breakpoint).  Use an alternate method, such as one of the report-level triggers, to obtain the column value.


REP-0725Cannot set the value of Column '<column name>' here.
REP-0725:  Cannot set the value of Column '<column name>' here.

Cause:	You attempted to set the value of the specified column via either issuing a command from the command line of the PL/SQL  Interpreter or by executing a stand-alone PL/SQL program unit.  You can only set a column value during report execution.
Action:	Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a column when the report has suspended execution (e.g., at a breakpoint).  Use an alternate method, such as one of the report-level triggers, to set the column value.


REP-0726Cannot get the value of Parameter '<parameter name>' here.
REP-0726:  Cannot get the value of Parameter '<parameter name>' here.

Cause:	You attempted to get the value of the specified parameter via either issuing a command from the command line of the PL/SQL  Interpreter or by executing a stand-alone PL/SQL program unit.  You can only get a parameter value during parameter form execution.
Action:	Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a parameter when the report has suspended execution (e.g., at a breakpoint).  Use an alternate method, such as one of the report-level triggers, to obtain the parameter value.


REP-0727Cannot set the value of Parameter '<parameter name>' here.
REP-0727:  Cannot set the value of Parameter '<parameter name>' here.

Cause:	You attempted to set the value of the specified parameter via either issuing a command from the command line of the PL/SQL  Interpreter or by executing a stand-alone PL/SQL program unit.  You can only set a parameter value during parameter form execution.
Action:	Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a parameter when the report has suspended execution (e.g., at a breakpoint).  Use an alternate method, such as one of the report-level triggers, to set the parameter value.


REP-0728Column '<column name>' may not be referenced by parameter triggers.
REP-0728:  Column '<column name>' may not be referenced by parameter triggers.

Cause:	You attempted to reference a column in a parameter-related trigger (Before Form, After Form, Validation), which is not allowed.
Action:	Remove the reference(s) from the parameter-related trigger(s) and add them to the Before Report trigger.


REP-0729The program unit '<program unit name>' of size '<number>' bytes is too big to be loaded for the current platform at the limit of '<limit>'
REP-0729:  The program unit '<program unit name>' of size '<number>' bytes is too big to be loaded for the current platform at the limit of '<limit>'

Cause:	Your program unit was created on another operating platform and it too large to be loaded into the current operating platform.
Action:	Reduce the size of the PL/SQL program unit you are trying to load.


REP-0730The following bind variable is not defined:
REP-0730:  The following bind variable is not defined:

Cause:	You made a bind reference to a parameter or column that has not been defined yet.  You must define the parameter or column before making a bind reference to it.
Action:	Create a column or parameter definition for the object you want to reference.  You could also try using a lexical reference rather than a bind reference, if possible.


REP-0732Error destroying program unit.
REP-0732:  Error destroying program unit.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0733Name already exists. Please select another name.
REP-0733:  Name already exists. Please select another name.

Cause:	You attempted to create a PL/SQL subprogram whose name is identical to an existing subprogram stored in the report.
Action:	Rename the new subprogram so that it does not conflict with any existing subprograms.


REP-0734No argument is allowed. It must be removed.
REP-0734:  No argument is allowed. It must be removed.

Cause:	You entered a PL/SQL function or procedure requiring arguments in a PL/SQL field that does not allow PL/SQL with arguments--for example, in a Format Trigger field, a Formula field, or as a group filter.
Action:	Remove the argument(s) from the PL/SQL source.


REP-0735Unable to load DE Program Unit. Will attempt to load PL/SQL source text. Make sure you are connected to a database.
REP-0735:  Unable to load DE Program Unit. Will attempt to load PL/SQL source text. Make sure you are connected to a database.

Cause:	Report Builder could not load the entire program unit.  It could be that the program unit references one or more objects stored in the database, but these objects could not be found.
Action:	Make sure you are connected to the correct database.  Also check to ensure that your program unit is making the correct references.


REP-0736There exist uncompiled program unit(s).
REP-0736:  There exist uncompiled program unit(s).

Cause:	You have attempted to convert a report, or loaded an old report, or .PLL containing PL/SQL which needed to be recompiled.
Action:	Load the report using RWBLD60 and modify the DE program unit(s).
Action:	Recompile the .PLL file.
Action:	Convert the .RDF file to .REX format and back to .RDF format.


REP-0737Should be a function with return type '<returntype>'.
REP-0737:  Should be a function with return type '<returntype>'.

Cause:	You have entered PL/SQL that does not have the appropriate return type.
Action:	Change the return type of the function to the one specified in the message.


REP-0738Only a function is allowed here.
REP-0738:  Only a function is allowed here.

Cause:	You have entered something other than a function where a function is required.
Action:	Enter a function.


REP-0739Cannot execute compiled PL/SQL from other platform.
REP-0739:  Cannot execute compiled PL/SQL from other platform.

Cause:	You tried to run a report on a platform that is not the same as the platform on which the PL/SQL in the report was compiled.  The report does not contain the PL/SQL source and, as a result, Report Builder could not recompile the PL/SQL on the current platform.
Action:	Run the report on the original platform where the PL/SQL was compiled.  Alternatively, get a copy of the source report with the source PL/SQL and recompile it from the current platform.


REP-0740An anchor cannot be anchored with another object.
REP-0740:  An anchor cannot be anchored with another object.

Cause:	You attempted to anchor an anchor to another layout object, or anchor a layout object to an anchor.
Action:	Anchors cannot be anchored with other layout objects.


REP-0741A matrix cannot be anchored with another object.
REP-0741:  A matrix cannot be anchored with another object.

Cause:	You attempted to anchor a matrix object to another layout object, or anchor a layout object to a matrix object.
Action:	Matrix objects cannot be anchored with other layout objects.


REP-0742A margin cannot be anchored with another object.
REP-0742:  A margin cannot be anchored with another object.

Cause:	You attempted to anchor the margin to a layout object, or anchor a layout object to the margin.
Action:	The margin cannot be anchored with layout objects.


REP-0743A matrix repeating frame cannot be anchored with another object.
REP-0743:  A matrix repeating frame cannot be anchored with another object.

Cause:	You attempted to anchor a matrix repeating frame with a Print Direction of Down or Across to another layout object.
Action:	Matrix repeating frames with Print Directions of Down or Across cannot be anchored with other layout objects.


REP-0744An anchor must have different parent and child objects.
REP-0744:  An anchor must have different parent and child objects.

Cause:	You attempted to create an anchor whose parent and child objects are the same--i.e., you tried to anchor an object to itself.
Action:	You cannot anchor an object to itself.  Anchors must have different parent and child objects.


REP-0745An object cannot be anchored more than once.
REP-0745:  An object cannot be anchored more than once.

Cause:	You attempted to create two anchors between the same two layout objects.
Action:	You can create only one anchor between the same two layout objects.


REP-0746The PL/SQL references an object which does not exist.
REP-0746:  The PL/SQL references an object which does not exist.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0747Before form trigger cannot reference a report column.
REP-0747:  Before form trigger cannot reference a report column.

Cause:	The Before Form trigger for the report references a column in the report.  You cannot reference columns from the Before Form trigger.
Action:	Remove any column references from the Before Form trigger.  (If you need to set the value of a column, you should do it from the Before Report trigger.)


REP-0748A parameter trigger cannot reference a report column.
REP-0748:  A parameter trigger cannot reference a report column.

Cause:	A Validation Trigger for a parameter references one or more columns in the report.  You cannot reference columns from a Validation Trigger.
Action:	Remove any column references in the Validation Trigger of the Parameter property palette.


REP-0749After form trigger cannot reference a report column.
REP-0749:  After form trigger cannot reference a report column.

Cause:	The After Form trigger for the report references a column in the report.  You cannot reference columns from the After Form trigger.
Action:	Remove any column references in the After Form trigger.  (If you need to set the value of a column, you should do it from the Before Report trigger.)


REP-0750Error closing the PL/SQL library.
REP-0750:  Error closing the PL/SQL library.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0736:  There exist uncompiled program unit(s) examples.


REP-0751Error accessing program units from the PL/SQL library.
REP-0751:  Error accessing program units from the PL/SQL library.

Cause:	This is an abnormal condition.  If you made any changes to your PL/SQL library, consider selecting File [image] Save As... and save it under a different name.
Action:	For information, see  Abnormal Conditions.


REP-0752Unable to save the PL/SQL library.
REP-0752:  Unable to save the PL/SQL library.

Cause:	This is an abnormal condition.  If you made any changes to your PL/SQL library, consider selecting File [image] Save As... and save it under a different name.
Action:	For information, see  Abnormal Conditions.


REP-0753Error attaching PL/SQL library '<library name>'.
REP-0753:  Error attaching PL/SQL library '<library name>'.

Cause:	You tried to attach an invalid PL/SQL library.  This could happen because the PL/SQL ibrary is corrupted, or because the file or object you named does not contain a PL/SQL library.
Action:	Make sure that the file or object you named contains a valid PL/SQL library.


REP-0754Error in inserting program units into the PL/SQL library.
REP-0754:  Error in inserting program units into the PL/SQL library.

Cause:	You tried to save a program unit into a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.
Action:	Ensure that the file or object you named contains a valid PL/SQL library and consider using File [image] Save As to save the current program unit.


REP-0755Error opening the PL/SQL library '<library name>'.
REP-0755:  Error opening the PL/SQL library '<library name>'.

Cause:	You tried to open a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.
Action:	Make sure that the file or object that you tried to open contains a valid PL/SQL library.


REP-0756Warning: Unable to find PL/SQL library '<library name>'.
REP-0756:  Warning: Unable to find PL/SQL library '<library name>'.

Cause:	You tried to attach a PL/SQL library that doesn't exist, or to open a report with one or more attached PL/SQL libraries that could not be found.
Action:	Make sure that the file or object you want to attach exists.  If you opened a report, reattach the PL/SQL library.


REP-0757Unable to create external location spec.
REP-0757:  Unable to create external location spec.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0758PL/SQL library '<library name>' is already in use.
REP-0758:  PL/SQL library '<library name>' is already in use.

Cause:	You tried to attach a PL/SQL library that has the same name as another PL/SQL library that is already attached.  This could happen if you renamed a file that contains a PL/SQL library, but the internal name recognized by Report Builder was not changed.
Action:	Use File [image] Save As to save the PL/SQL library under a different name.


REP-0759One or more PL/SQL libraries have been modified since the report was saved. The PL/SQL will be recompiled.
REP-0759:  One or more PL/SQL libraries have been modified since the report was saved. The PL/SQL will be recompiled.

Cause:	You are trying to open or run a report that references one or more PL/SQL libraries, and part or all of the PL/SQL has been modified but not compiled since you last saved the report.
Action:	No action is necessary; Report Builder will recompile the PL/SQL for you.


REP-0760You are in the print document session.
REP-0760:  You are in the print document session.

Cause:	You already selected File [image] Administration [image] Report on Reports to produce a report on one or more reports.
Action:	Finish producing the current report on reports, then select File [image] Administration [image] Report on Reports again to run another report on reports.


REP-0761Can't open the resource for printing the report.
REP-0761:  Can't open the resource for printing the report.

Cause:	Report Builder cannot find the reports (shipped with Report Builder) that document your reports.
Action:	Make sure that the reports that document other reports (shipped with Report Builder) are located in the proper directory.


Invalid userid for Interoffice login.
REP 0762.  Invalid userid for Interoffice login.

Cause:	You attempted to save report output to Interoffice repository, but did not specify a valid connect string for Interoffice document server.
Action:	Specify a valid connect string for Interoffice document server.


REP 0763.  Launch Interoffice client $0 failed.

Cause:	You attempted to launch Interoffice client, but somehow it failed to run.
Action:	Please make sure the Interoffice client is properly installed.


REP 0764.  Error while running Interoffice client.  The error code is $0.

Cause:	You were running the Interoffice client to check in the documents into repository, but it failed on the error code above.
Action:	Please check the Interoffice error code/message for the reason of failure.


REP-769:  You cannot run to mail from the parameter form when the live previewer is open.

Cause:	The Live Previewer is open and the destination type (DESTYPE) is set to Mail.
Action:	Choose mail directly from the Live Previewer and not the Runtime Parameter Form.


REP-0770Before Form trigger failed.
REP-0770:  Before Form trigger failed.

Cause:	The Before Form trigger in your report returned false.
Action:	Make the appropriate changes (either to the PL/SQL source in the Before Form trigger or to the report) to make the trigger return true.


REP-0771After Form trigger failed.
REP-0771:  After Form trigger failed.

Cause:	The After Form trigger in your report returned false.
Action:	Make the appropriate changes (either to the PL/SQL source in the After Form trigger or to the report) to make the trigger return true.


REP-0772Parameter Form Fields '<fieldname1>' and '<filedname2>' may not have the same Source.
REP-0772:  Parameter Form Fields '<fieldname1>' and '<filedname2>' may not have the same Source.

Cause:	You specified the same Source for two parameter form fields.  Fields on the Runtime Parameter Form must have unique sources.
Action:	Change the Source of one of the fields.


REP-0773No Source specified for Parameter Form Field '<fieldname>'.
REP-0773:  No Source specified for Parameter Form Field '<fieldname>'.

Cause:	You have not specified a Source for a parameter form field or the source parameter was deleted from the data model.  Fields on the Runtime Parameter Form must have a source.
Action:	Specify a valid Source for the parameter form field.


REP-0774Warning: No selectable values for LOV parameter <parameter name>.
REP-0774:  Warning: No selectable values for LOV parameter <parameter name>.

Cause:	You have either not specified any values for the LOV parameter's select list, or specified values that cannot be selected.
Action:	Check the select statement or selectable value list of the parameter to ensure that your specified values are selectable.  For more information about LOV parameters, see Parameter Properties.


REP-0775Warning: The data type of the first column of the select statement does not match the data type of LOV parameter <parameter name>.
REP-0775:  Warning: The data type of the first column of the select statement does not match the data type of LOV parameter <parameter name>.

Cause:	The datatype of the first column you specified in your select statement does not match the datatype you specified for your LOV parameter.
Action:	Check the datatype of the LOV parameter, the select statement, and the columns in the database tables accessed by the select statement to ensure that they match.


REP-0776Warning: There are columns with values in segmented memory when populating LOV parameter <parameter name>. They will be ignored.
REP-0776:  Warning: There are columns with values in segmented memory when populating LOV parameter <parameter name>. They will be ignored.

Cause:	You have selected columns with values in segmented memory for your LOV parameter's select list.  This is not allowed.
Action:	Select different columns or move the columns' values.


REP-0777Warning: There are columns whose types can not be handled when populating LOV parameter <parameter name>. They will be ignored.
REP-0777:  Warning: There are columns whose types can not be handled when populating LOV parameter <parameter name>. They will be ignored.

Cause:	You have selected columns whose types cannot be handled (e.g., binary data).
Action:	Select different columns.


REP-0778Warning: Some columns can not be formatted correctly when populating LOV parameter <parameter name>. These columns will be ignored.
REP-0778:  Warning: Some columns can not be formatted correctly when populating LOV parameter <parameter name>. These columns will be ignored.

Cause:	The SELECT statement selecting values for your parameter's LOV retrieves columns whose values cannot be formatted according to their datatypes.
Action:	Convert the values to valid ones or check the database to see if the values of the columns are valid.


REP-0779Warning: Some items of LOV parameter <parameter name> are too long.  These items will be truncated.
REP-0779:  Warning: Some items of LOV parameter <parameter name> are too long.  These items will be truncated.

Cause:	You have either specified items or selected columns containing some values which are too long to include in your LOV parameter's select list.
Action:	Check the values of the items and reduce their length if necessary.


REP-0780The initial value you have entered is invalid against the input mask '<input mask>'.
REP-0780:  The initial value you have entered is invalid against the input mask '<input mask>'.

Cause:	The value you entered in the Initial Value field violates the mask you specified in the Input Mask field.
Action:	You must either enter a different value in Initial Value or change the mask in Input Mask.


REP-0781Bind variables are not allowed in the Select statement.
REP-0781:  Bind variables are not allowed in the Select statement.

Cause:	You have included bind variables in your SELECT statement.
Action:	Remove the bind variables from your SELECT statement.


REP-0782The datatype of the parameter doesn't match the datatype of its source column.
REP-0782:  The datatype of the parameter doesn't match the datatype of its source column.

Cause:	You have selected a column with an invalid datatype to furnish values for your LOV parameter's select list.
Action:	Change the column's datatype or specify a different column.


REP-0783The possible values list has bad syntax.
REP-0783:  The possible values list has bad syntax.

Cause:	You used incorrect syntax to create the list of possible values for your LOV parameter.
Action:	Edit the possible values list to ensure that it is a proper comma-separated list.


REP-0784A possible value has invalid width.
REP-0784:  A possible value has invalid width.

Cause:	A value you specified for your LOV parameter's list of possible values has an invalid width.
Action:	Edit the possible values list so that all possible values have valid widths, or alter the width.


REP-0785A possible value is invalid against the input mask.
REP-0785:  A possible value is invalid against the input mask.

Cause:	A value you specified for your LOV parameter's list of possible values is not formatted in accordance with the specified input mask.
Action:	Edit the possible values list to ensure that all possible values are valid against the input mask.


REP-0786The initial value is not among the possible values.
REP-0786:  The initial value is not among the possible values.

Cause:	The initial value you specified for your LOV parameter does not appear on the defined list of possible values.
Action:	Add the initial value you specified to the possible values list.


REP-0787Warning: The name of the first column of LOV parameter <parameter name>'s select statement is not the same at runtime from design time.
REP-0787:  Warning: The name of the first column of LOV parameter <parameter name>'s select statement is not the same at runtime from design time.

Cause:	There is a discrepancy between the column(s) you specified in your original SELECT statement and what the table(s) in question now contains.
Action:	Check the database to determine if the tables in question have been updated since you created the parameter list, or re-apply the LOV parameter's SELECT statement.


REP-0788Warning: The value of restricted LOV parameter <parameter name> is not among the selectable values.
REP-0788:  Warning: The value of restricted LOV parameter <parameter name> is not among the selectable values.

Cause:	You have specified a value for a LOV parameter that is not on the parameter's select list.
Action:	Choose a value from the parameter's select list.


REP-0790Page Width and Height must either both be specified or both be blank.
REP-0790:  Page Width and Height must either both be specified or both be blank.

Cause:	You specified a blank value for either Page Width or Page Height in the Runtime Settings tab of the Tools Options dialog box.  Both settings must contain a valid value, or be blank.
Action:	Specify a valid value for the blank setting, or make both settings blank.


REP-0800You can only select all in a text entry field.
REP-0800:  You can only select all in a text entry field.

Cause:	You selected Edit [image] Select All with the cursor positioned on an element in a property palette other than a text field.
Action:	While in a property palette, Edit [image] Select All is valid only in a text field.


REP-0801Layout canvas must remain large enough to fit all layout objects.
REP-0801:  Layout canvas must remain large enough to fit all layout objects.

Cause:	You reduced the size of the painting region of the Layout Model editor by changing one or more settings in the Report Properties dialog box, or by resizing the margin, but the resized painting region is not large enough to fit all of the layout objects.
Action:	Make sure all layout objects in the body, margin, header, and trailer sections of your report fit in the resized painting region.


REP-0802Parameter form canvas must remain large enough to fit all parameter form objects.
REP-0802:  Parameter form canvas must remain large enough to fit all parameter form objects.

Cause:	You reduced the size of the painting region of the Parameter Form editor by changing one or more settings in the Report Properties dialog box, but the resized painting region is not large enough to fit all of the parameter form objects.
Action:	Make sure all parameter form objects fit in the resized painting region.


REP-0803Canvas size specified is too large.
REP-0803:  Canvas size specified is too large.

Cause:	Your report contains combined settings of page/form size and either logical page, maximum body page, maximum header page, maximum footer page, or number of parameter form pages that results in a value larger than that supported by Report Builder (a dpi value greater than 2 gigabytes).
Action:	Make the page/form size smaller, or decrease the value for logical page size, maximum body pages, maximum header pages, maximum footer pages, or number of parameter form pages.


REP-0804The report definition was modified during the current run. Cannot continue running the parameter form or report.
REP-0804:  The report definition was modified during the current run. Cannot continue running the parameter form or report.

Cause:	While in the Runtime Parameter Form, you modified the report via an editor or property palette.
Action:	Cancel the Runtime Parameter Form and re-run the report.


REP-0805Could not initialize menus.
REP-0805:  Could not initialize menus.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0806Error reading window resources.
REP-0806:  Error reading window resources.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-0807You must enter the Array Size.
REP-0807:  You must enter the Array Size.

Cause:	In the Runtime Settings dialog box, you left the Array Size field blank.  You must enter a value for Array Size.
Action:	Enter an Array Size value between 1 and 9999.


REP-0808You must enter the Buffer Size.
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-0809You must enter the Long Chunk Size.
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-0810Valid options are 'Noaction', 'Rollback', or 'Commit'.
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-0811Valid options are '<In Report Definition>', 'Screen', 'File', 'Printer' or 'Mail'.
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-0812Valid options are '<In Report Definition>', 'Landscape', or 'Portrait'.
REP-0812:  Valid options are '<In Report Definition>', 'Landscape', or 'Portrait'.

Cause:	In the character-mode Runtime Settings dialog, you chose an invalid value for Orientation.  Valid values are <In Report Definition>, Landscape, or Portrait.
Action:	Select a valid value for Orientation.


REP-0813Valid options are '<In Report Definition>', 'Default', 'Bitmap' or 'Character'.
REP-0813:  Valid options are '<In Report Definition>', 'Default', 'Bitmap' or 'Character'.

Cause:	In the character-mode Runtime Settings dialog, you chose an invalid value for Mode.  Valid values are <In Report Definition>, Default, Bitmap, or Character.
Action:	Select a valid value for Mode.


REP-0814Valid options are '<In Report Definition>', 'Yes' or 'No'.
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-0815Valid options are 'Landscape', or 'Portrait'.
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-0816Valid options are 'Bitmap' or 'Character'.
REP-0816:  Valid options are 'Bitmap' or 'Character'.

Cause:	In the character-mode Runtime Parameter Form, you chose an invalid value for Mode.  Valid values are Bitmap or Character.
Action:	Select a valid value for Mode.


REP-0817Valid options are 'Yes' or 'No'.
REP-0817:  Valid options are 'Yes' or 'No'.

Cause:	In the character-mode Runtime Parameter Form, you chose an invalid value for Background.  Valid values are Yes, or No.
Action:	Select a valid value for Background.


REP-0818Warning: Page height has changed for Parameter Form. Parameters might be crossed by page boundaries.
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-0819Could not turn AUTOCOMMIT ON for SQL Server connection.
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-0820Cannot import specified image.
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-0821Cannot export specified image.
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-0822No drawing imported.
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-0823No drawing exported.
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-0824Data dictionary not available on the database to which you are connected. Unable to retrieve table/column information.
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-0825The connected database is not ORACLE or DB2. It cannot be used to store report documents.
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-0828Report Builder database tables are not installed in the database. Cancelling Report Doc.
REP-0828:  Report Builder tables are not installed in the database. Canceling 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-0829Report Builder database tables appear to match the tables from an older version of Report Builder (<Version>).  Cancelling Report Doc.
REP-0829:  Report Builder database tables appear to match the tables from an older version of Report Builder (<Version>).  Canceling 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.
Action:	Inform your database administrator that Report Builder tables for this version were not successfully installed in the database.


REP-0830Report Builder database tables appear to be corrupted or incorrectly installed.  Cancelling Report Doc.
REP-0830:  Report Builder database tables appear to be corrupted or incorrectly installed.  Canceling Report Doc.

Cause:	Report Doc cannot be run because the Report Builder tables are in an unstable state.
Action:	Inform your database administrator that Report Builder tables are either corrupted or incorrectly installed in the database.


REP-0831Query could not be built.
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, see  Abnormal Conditions.


REP-0900Cannot close this report while PL/SQL is still executing.
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-0901Tables and Columns function is not supported for this database server.
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-0910The Cue Cards cannot be found.  Please reinstall the Cue Cards and try again.
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-0911The Quick Tour cannot be found.  Please reinstall the Quick Tour and try again.
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-0999Unimplemented Error:
REP-0999:  Unimplemented Error:

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1010This name does not conform to SQL naming standards.
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 Naming Conventions.  Enter a name that conforms to the conventions.


REP-1011<Object type> must be named.
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 Naming Conventions.


REP-1012There is another <object type> with this name.
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-1013This name may not be the same as a reserved word.
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 Naming Conventions.


REP-1014Name length cannot exceed 30 bytes.
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-1048Warning: Owner and Access list not overwritten.
REP-1048:  Warning: Owner and Access list not overwritten.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1049Cannot open a report saved with a newer version of Report Builder.
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-1050Unable to access document names in database.
REP-1050:  Unable to access document names in database.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1051Unable to save document to file '<filename>'.
REP-1051:  Unable to save document to file '<filename>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1052Unable to save document to database.
REP-1052:  Unable to save document to database.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1053Unable to obtain new document ID from database.
REP-1053:  Unable to obtain new document ID from database.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1054Unable to delete from table '<table name>'.
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-1055Unable to lock table '<table name>'.
REP-1055:  Unable to lock table '<table name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1056Unable to rename object stored in database.
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.
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-1058Unable to read document from database.
REP-1058:  Unable to read document from database.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1059Unable to read document from file '<filename>'.
REP-1059:  Unable to read document from file '<filename>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1060The Report Builder database tables have not been installed.
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-1061Unable to read external file '<filename>'.
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-1062Unable to find external query '<filename>'.
REP-1062:  Unable to find external query '<filename>'.

Cause:	The possible causes of this error include the following:
	Case 1:	REPORTS60_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 REPORTS60_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-1063The PL/SQL '<program unit name>' has exceeded the platform specific size limit.
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-1064Unable to read document '<document name>'.
REP-1064:  Unable to read document '<document name>'.

Cause:	You attempted to open a document whose definition, stored in either the database or the file system, has been lost or corrupted.
Action:	This document cannot be used.


REP-1065Unable to read external query '<filename>'.
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 file system, has been lost or corrupted.
Action:	This external query cannot be used.


REP-1066Warning: Comment is corrupted. It will be lost.
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-1067Some information is missing in the report.
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-1070Error while opening or saving a document.
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-1071Reached the end of an object/record scan.
REP-1071:  Reached the end of an object/record scan.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1072Object was not found in the object store.
REP-1072:  Object was not found in the object store.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1073Object was found in the object store when not expected.
REP-1073:  Object was found in the object store when not expected.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1074Object is too big.
REP-1074:  Object is too big.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1075Object is invalid.
REP-1075:  Object is invalid.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1076Specified object store 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-1077Type specified for the object is invalid.
REP-1077:  Type specified for the object is invalid.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1078Non-specific file error occurred.
REP-1078:  Non-specific file error occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1079Function is unsupported.
REP-1079:  Function is unsupported.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1080Unique key violation occurred.
REP-1080:  Unique key violation occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1081Page split occurred.
REP-1081:  Page split occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1082Close error occurred.
REP-1082:  Close error occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1083File version error occurred.
REP-1083:  File version error occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1084File header is bad or missing.
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-1085File create error occurred.
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-1086File open read-only error occurred.
REP-1086:  File open read-only error occurred.

Cause:	You tried to perform an operation that required Report Builder to 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-1087File open read-write error occurred.
REP-1087:  File open read-write error occurred.

Cause:	You tried to perform an operation that required Report Builder to 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-1088File write error occurred.
REP-1088:  File write error occurred.

Cause:	You tried to perform an operation that required Report Builder to write to a file to which you do not have access.  You might not have the necessary file privileges to write the file.
Action:	Obtain the necessary privileges for the file or, if possible, access a file to which you do have write privileges.


REP-1089File read error occurred.
REP-1089:  File read error occurred.

Cause:	You tried to perform an operation that required Report Builder to read a file to which you do not have access.  You might not have the necessary file privileges to read the file.
Action:	Obtain the necessary privileges for the file or, if possible, access a file to which you do have read privileges.


REP-1090File close error occurred.
REP-1090:  File close error occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1091Disk or file system is full.
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-1092File unique key violation occurred.
REP-1092:  File unique key violation occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1093Allocate failed.
REP-1093:  Allocate failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1094Reallocate failed.
REP-1094:  Reallocate failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1095Free failed.
REP-1095:  Free failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1096The <document type> is currently locked.
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-1097PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does not exist.
REP-1097:  PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does not exist.

Cause:	The possible causes of this error include the following:
	Case 1:	The table does not exist.
	Case 2:	You do not have the necessary privileges to access the table.
Action:	You can take the following actions to correct this error:
	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-1098Error reading PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE data.
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-1099Cannot open files not created with Report Builder.
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-1101Group '<group name>' has invalid repeat direction.
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-1102Unable to fit default layout onto page of size <number>.
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-1103No column is selected in group '<group name>'.
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-1104Page level summaries are not supported in defaulting.
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.
Action:	You can take the following actions to correct this error:
	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-1106Warning: no field generated for column '<column name>'.
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-1107Missing across or down group in cross product group '<group name>'.
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-1108Cannot fit default layout even in region extending to page boundaries.
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-1109Multiple group selection incompatible with single group layout style.
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-1110Missing matrix across group in cross product group '<group name>'.
REP-1110:  Missing matrix across group in cross product group '<group name>'.

Cause:	You attempted to create a default layout by selecting a Style 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-1111Missing matrix down group in cross product group '<group name>'.
REP-1111:  Missing matrix down group in cross product group '<group name>'.

Cause:	You attempted to create a default layout by selecting a Style 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-1112Missing matrix cross product group in matrix report.
REP-1112:  Missing matrix cross product group in matrix report.

Cause:	You attempted to create a default layout by selecting a Style 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-1113No groups or reports level columns have been selected.
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-1114Single group selection incompatible with multiple group layout style.
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-1115Unable to show full template layout because it does not fit onto the page.
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-1200Flow compilation failed.
REP-1200:  Flow compilation failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1201Query text missing from query '<query name>'.
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-1202ORACLE logon not specified.
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-1203Field '<field name>' references invalid column.
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-1204Repeating frame '<frame name>' references invalid group.
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-1205There is a loop in the positional dependency tree.
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-1206An Object is anchored to more than one other object.
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-1207The PL/SQL procedure for group filter of '<group name>' is missing.
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-1208Repeating frame of matrix '<matrix name>' cannot be anchored.
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-1209Matrix object '<matrix name>' cannot be anchored.
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-1211Object '<object name1>' is larger than its enclosing object '<object name2>'.
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-1212Object '<object name1>' is not fully enclosed by its enclosing object '<object name2>'.
REP-1212:  Object '<object name1>' is not fully enclosed by its enclosing object '<object name2>'.

Cause:	The possible causes of this error include the following:
	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.
Action:	You can take the following actions to correct this error:
	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 [image] Send to Back, Arrange [image] Bring to Front, Arrange [image] Move Backward, and Arrange [image] 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-1213Field '<field name>' references column '<column name>' at a frequency below its group.
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-1214Repeating frame '<frame name>' is enclosed by a child repeating frame.
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.
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.
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.
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.
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-1222Invalid body size.
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-1223Invalid page size.
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-1225Invalid logical page size.
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-1226Body location is beyond print area.
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-1229Between record value for repeating frame '<repeating frame name>' is negative.
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-1230Field '<field name>' has an invalid page reset group.
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-1231:  '<Object name>' has an invalid text wrap style.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1232Matrix '<matrix name>' has an invalid source frame.
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-1233The frames of matrix '<matrix name>' do not fully intersect.
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-1234Matrix '<matrix name>' position is not at the intersection of its frames.
REP-1234:  Matrix '<matrix name>' position is not at the intersection of its frames.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1235Error generating index for Cross Product.
REP-1235:  Error generating index for Cross Product.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1236Invalid query '<query name>'.
REP-1236:  Invalid query '<query name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1237Invalid data link.
REP-1237:  Invalid data link.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1238Invalid group '<group name>'.
REP-1238:  Invalid group '<group name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1239Invalid column '<column name>'.
REP-1239:  Invalid column '<column name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1240Invalid anchor.
REP-1240:  Invalid anchor.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1241Circular column dependency originating with column '<column name>'.
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-1242Matrices must have all down frames below all across frames.
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-1243Unimplemented type of summary specified in column '<column name>'.
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-1245Wrong number of source columns for summary function of column '<column name>'.
REP-1245:  Wrong number of source columns for summary function of column '<column name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1246Chart document not found.
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-1247Report contains uncompiled PL/SQL.
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-1248All source columns of placeholder '<column name>' must be in the same group.
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-1249Column '<column name>' has no PL/SQL formula.
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-1250Circular query dependency.
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-1251Circular query dependency originating with query '<query name>'.
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-1252Matrix should be surrounded by a repeating frame on group '<group name>'.
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-1253Matrix objects are on different regions of the layout.
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-1254Anchored objects are on different regions of the layout.
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-1255Cannot anchor to a hidden object.
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-1256Link file boilerplate text is missing its link file.
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-1257Cannot pass data for child query from caller.
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-1258Group '<group name>' has no columns.
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-1259Group '<group name>' has no break columns.
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-1260Groups '<group name1>' and '<group name2>' are from the same query and cannot be linked.
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-1261Cannot resolve parent of group '<group name>'.
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-1262Circular data link dependency starting from group '<group name>'.
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-1263Cross product group '<group name>' has no or only one dimension group.
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-1264Data link of group '<group name>' crosses cross product boundary.
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-1265Cross product group '<group name>' has no child groups.
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-1266Column '<column name>': Page Level columns are not allowed in a Cross Product.
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-1267Chart '<display name>' references an invalid column as a bind parameter.
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.
Action:	For information, see  Abnormal Conditions.


REP-1268Chart '<display name>' references a bind column '<column name>' at the wrong frequency.
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-1269Chart '<display name>' references invalid report group.
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.
Action:	For information, see  Abnormal Conditions.


REP-1270Chart '<display name>' references a report group at the wrong frequency.
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-1271Chart column name '<column name>' has been multiply specified in the chart document '<display name>'.
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-1272Column '<column name>' may not be used as a Break Column.
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 Break Order.


REP-1273Source groups of matrix '<matrix name>' not from the same cross product.
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 cross product group.
Action:	Change the source groups of the repeating frames or choose different repeating frames to form the dimensions of the matrix.


REP-1274Invalid repeat direction combination in matrix '<matrix name>'.
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-1275Page level column '<column name>' may not be referenced from format trigger '<program unit name>'.
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-1276Placeholder '<column name>' references one or more non-formula columns.
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-1277Invalid select element.
REP-1277:  Invalid select element.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1278Invalid PL/SQL procedure in '<program unit name>'.
REP-1278:  Invalid PL/SQL procedure in '<program unit name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1279Invalid frame or repeating frame '<frame name>'.
REP-1279:  Invalid frame or repeating frame '<frame name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1280Invalid field '<field name>'.
REP-1280:  Invalid field '<field name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1281Invalid boilerplate '<boilerplate name>'.
REP-1281:  Invalid boilerplate '<boilerplate name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1282Invalid matrix '<matrix name>'.
REP-1282:  Invalid matrix '<matrix name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


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

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1284Query '<query name>' has no groups.
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-1285Query '<query name>' has no select elements.
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-1286Group '<group name>' is a cross product as well as a dimension.
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-1287Cross product group '<group name>' should not have a group filter.
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-1288The numeric argument for group filter of '<group name>' missing.
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-1289Unimplemented type of group filter specified in group '<group name>'.
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-1291Column '<column name>' has invalid reset group.
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, or Report.
Action:	Specify a valid Reset At value for the summary column in its property palette.


REP-1292Column '<column name>' has invalid compute group.
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-1293Column '<column name>' has invalid product order.
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-1294Width of column '<column name>' is too large.
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-1295Data format of column '<column name>' is unsupported.
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-1296Data link child cannot be in cross product group '<group name>'.
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-1297Data link child column '<column name>' must be a database column.
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-1298Columns '<column name>' and '<column name>' have incompatible types to be linked.
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-1299Groups '<group name>' and '<group name>' in different cross products cannot be linked.
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-1300Text boilerplate '<boilerplate name>' has no contents.
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-1301Data link creates sibling of group '<group name>' within cross product.
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-1302Cross product has two or more child groups.
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-1303Query must be completely in or out of cross product group '<group name>'.
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-1304Cross product group '<group name>' contains another cross product as child.
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 cross product group.


REP-1305Warning: Frame '<frame name>' intersects but does not enclose object '<object name>'.
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-1306Summary column '<column name>' has invalid source.
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-1307Summary column '<column name>' has invalid product order.
REP-1307:  Summary column '<column name>' has invalid product order.

Cause:	The possible causes of this error include the following:
	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.
Action:	You can take the following actions to correct this error:
	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-1308Placeholder column '<column name>' not supported in cross product.
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-1309Report level summary '<column name>' cannot be a percent of total.
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-1310Boilerplate '<boilerplate name>' references '&<reference name>' which is not a field.
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-1311Object '<object name>' with page-dependent references changed to fixed sizing.
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-1312Page Level column '<column name>' may not be referenced from chart '<display name>'.
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-1313Page Level column '<column name>' may not be referenced from group filter '<group name>'.
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-1314Format trigger '<program unit name>' references column '<column name>' at wrong frequency.
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-1315Group filter '<program unit name>' references column '<column name>' at wrong frequency.
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.
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-1317Boilerplate '<boilerplate name>' references field with source '<column name>' at wrong frequency.
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-1318Error while setting transaction read-only.
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-1319Warning: Implicit anchoring algorithm cannot uniquely identify the anchoring object of '<object1 name>'. Arbitrarily choosing '<object2 name>'.
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 Implicit Anchoring.
Action:	To avoid the random creation of an implicit anchor, explicitly anchor the specified object (object name 1) to another object.


REP-1320Program unit '<program unit name>' references column with invalid ID: <column ID>.
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-1322Page break after on '<object name>' has no effect.
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-1323Cannot have output columns in format trigger '<program unit name>'.
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-1324Cannot have output columns in group filter '<group name>'.
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-1325Cannot have output columns in Between Page Trigger.
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.
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-1327Column '<column name>' writes to column '<column name>' at wrong frequency.
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-1328Cannot run report containing ROWLABEL column '<column name>' in a non-trusted OS.
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-1329Column '<column name>' cannot be linked to column '<column name>' because the child column is not a database  column.
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 data 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-1330Lexical parameter '<parameter name>' in query '<query name>' must not change column dependencies.
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-1331Column '<column name>' cannot be linked to column '<column name>' because the child column is determined by a lexical parameter.
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 data 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-1332Group filter for '<group name>' cannot reference column '<column name>'. It is not a valid database column or it depends on a related query.
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-1333Unsupported layout; a matrix may not be inside another matrix.
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.  Re-design your layout to avoid this.


REP-1335Warning: variable rotated text '<boilerplate name>' treated as fixed/contract width.
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 to Variable 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-1336The source of field '<field name>' is Page Level calculation '<column name>'. <group name>.
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-1337Boilerplate '<boilerplate name>' references field '<field name>', whose source is Page Level calculation '<column name>'. <group name>.
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-1338Column mode not allowed on repeating frame '<frame name>'.
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-1339Chart '<display name>' missing data column specification.
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-1340Cannot match passed-in columns with report definition of '<report name>'.
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.
Action:	You can take the following actions to correct this error:
	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 datatypes and names in the report.


REP-1341Warning: Data truncation possible in column '<column name>'.
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 box.


REP-1342Type of data link to query '<query name>' illegal for non ORACLE server.
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-1343Invalid button '<button name>'.
REP-1343:  Invalid button '<button name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1344Button '<button name>' has no action source file.
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 Button Properties.


REP-1345Button '<button name>' has invalid source column.
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 Button Properties.


REP-1346Button '<button name>' references source column '<column name>' at wrong frequency.
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-1347Button '<button name>' has invalid icon file.
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-1348Source column of field '<field name>' is in sound or video format.
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-1349PL/SQL action missing from button '<button name>'.
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-1350Cannot have output columns in action trigger '<program unit name>'.
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-1351Warning: Icon '<icon name>' on button '<button name>' not found.
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-1352The fonts specified for this report cannot be found for the character set specified by NLS_LANG.
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-1353Web property of layout object '<layout object name>' references field or column '<field or column name>' at wrong frequency.
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 properties: 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-1354Web property of layout object '<layout object name>' references page-dependent field or column '<field or column name>'.
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 properties: 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-1355.  PL/SQL missing from query.
REP-1355.  PL/SQL missing from PL/SQL based query ‘$0’.

Cause:	You created a PL/SQL based query, but you did not enter PL/SQL for it.
Action:	Enter PL/SQL for the query.


REP 1356.  Column link not allowed for linking to PL/SQL based query '$0'."
REP-1356.  Column link not allowed for linking to PL/SQL based query '$0'."

Cause:	You tried to link a column to another column that is in PL/SQL based query as bind variables to set up intended column link conditions.
Action:	You can create group links and use the columns in PL/SQL based query as bind variables to set up intended column link conditions.


REP 1357.  Auto foreign key column link creation is only for SQL queries.
REP-1357.  Auto foreign key column link creation is only for SQL queries.

Cause:	You dragged a link between two queries to automatically create column links based on foreign key relationships.  However, this can only be done between two SQL data queries.
Action:	Do this on two SQL data queries, or change the PL/SQL based queries to SQL.


REP-1365. Column link not allowed for linking to Express based query <query name>.
REP 1365. Column link not allowed for linking to Express based query <query name>.

Cause:	You tried to link a column to another column that is in Express based query, which is not allowed.
Action:	You can create group links and use the columns in Express based query as bind variables to set up the intended column link conditions.


REP-1366. The XML Settings of object <layout object name> reference page-dependent field or column <field or column name>.
REP 1366. The XML Settings of object <object name> reference page-dependent column <column name>.

Cause:	One of the object's XML properties references a column that contains a page calculation or a total number of pages variable. XML Settings cannot reference columns that are based on page calculations.
Action:	Remove the XML Settings references to the page-dependent column.


REP-1367. The XML Settings of object <object name> reference field or column <field or column name> at wrong frequency.
REP-1367. The XML Settings of object <object name> reference column <column name> at wrong frequency.

Cause:	One of the object's XML properties references the column, but the column &columnname has a higher frequency than the object (e.g., the column may be in a different group than the object referencing it).
Action:	Move the object such that it has the same frequency as the field or column (e.g., place them in the same or lower group) it references or remove the reference.


REP-1400Couldn't initialize coxr.
REP-1400:  Couldn't initialize coxr.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1401'<program unit name>': Fatal PL/SQL error occurred.
REP-1401:  '<program unit name>': Fatal PL/SQL error occurred.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1402'<program unit name>': Unhandled PL/SQL exception.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1403'<program unit name>': Illegal to suspend PL/SQL procedure.
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-1404Compile failed for some reason.
REP-1404:  Compile failed for some reason.

Cause:	In generating your report, PL/SQL compilation failed.
Action:	Debug your PL/SQL constructs.


REP-1405Code is not executable.
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-1406Cannot run parameterized code directly.
REP-1406:  Cannot run parameterized code directly.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1408Cannot initialize PL/SQL.
REP-1408:  Cannot initialize PL/SQL.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1412PL/SQL function '<program unit name>' returned invalid value or no value.
REP-1412:  L/SQL function '<program unit name>' returned invalid value or no value.

Cause:	Your report contains a PL/SQL function that does not specify a return value (e.g., a format trigger that does not return TRUE or FALSE).
Action:	Verify that the function includes a return statement for every code path.


REP-1414'<program unit name>': Couldn't find lib unit to run.
REP-1414:  '<program unit name>': Couldn't find lib unit to run.

Cause:	This is most likely an abnormal condition.
Action:	Check your PL/SQL code and recompile it.  If this error recurs, see Abnormal Conditions.


REP-1415'<program unit name>': Unknown user exit '<user exit name>'.
REP-1415:  '<program unit name>': Unknown user exit '<user exit name>'.

Cause:	A user exit was called, but it could not be found.
Action:	Ensure that you are using the correct name for the user exit and that it has been compiled and linked.


REP-1416'<program unit name>': User exit '<user exit name>'. <submessage>.
REP-1416:  '<program unit name>': User exit '<user exit name>'. <submessage>.

Cause:	An error occurred in a user exit.  Possible errors:  a reference to an unknown column, a  truncated column value, unretrievable PL/SQL source, or the user exit could not be found.
Action:	Based on the submessage, debug your user exit.  Ensure that you are referencing valid columns and the PL/SQL code and user exit are accessible. Link appropriate libraries/user exits to allow the report to run standalone.


REP-1417'<program unit name>': Invalid integer argument passed to <procedure name>.
REP-1417:  '<program unit name>': Invalid integer argument passed to <procedure name>.

Cause:	The packaged procedure that you referenced expected an integer for an argument, but you did not specify one.
Action:	Verify that the PL/SQL that references the packaged procedure correctly passes it an integer.  For more information about PL/SQL packaged procedures, see Report Builder PL/SQL Package: SRW.


REP-1418'<program unit name>': Passed null arguments to <procedure name>.
REP-1418:  '<program unit name>': Passed null arguments to <procedure name>.

Cause:	The exception SRW.NULL_ARGUMENTS was raised, either by a user-defined PL/SQL subprogram, or because a packaged subprogram was passed one or more null arguments.
Action:	Check any PL/SQL code that might raise this exception.  Also, check the argument list that is passed to the specified packaged subprogram.


REP-1419'<program unit name>': PL/SQL program aborted.
REP-1419:  '<program unit name>': PL/SQL program aborted.

Cause:	A PL/SQL construct had a fatal error and was aborted.
Action:	Check your PL/SQL constructs for errors.
Cause:	REP-1419 'beforerep' errors may be caused by corrupted .RDF files.
Action:	Rebuild .RDF file.
Cause:	One or more fields in a report is accessing data that is not available to that report, i.e. invalid PL/SQL references.
Action:	Make sure that all tables/columns queried in the report are a) available and b) populated with data which matches parameters set in the report.


REP-1420'<program unit name>': PL/SQL program raised a program error.
REP-1420:  '<program unit name>': PL/SQL program raised a program error.

Cause:	The exception SRW.PROGRAM_ERROR was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition.
Action:	Check any PL/SQL code that might raise this exception.  If no PL/SQL raised the exception, see  Abnormal Conditions.


REP-1421'<program unit name>': Trying to manipulate column of wrong type in <procedure name>.
REP-1421:  '<program unit name>': Trying to manipulate column of wrong type in <procedure name>.

Cause:	The datatype of the column whose name you passed to a packaged procedure is not the correct datatype for the packaged procedure (e.g., the packaged procedure was expecting a column of Character datatype and you passed it a column of another datatype).
Action:	Debug the PL/SQL that references packaged procedures and ensure that you are passing the packaged procedure the name of a column of the correct datatype.  Also check the syntax of the packaged procedure to ensure that you are referencing it properly.  For more information about PL/SQL packaged procedures, see Report Builder PL/SQL Package: SRW.


REP-1422Procedure by this name already exists.
REP-1422:  Procedure by this name already exists.

Cause:	You tried to create a new PL/SQL procedure with the same name as an existing PL/SQL procedure.
Action:	Change the name of the new procedure or change the name of the existing procedure.


REP-1423'<program unit name>': Cannot set maximum rows of the query after it started executing.
REP-1423:  '<program unit name>': Cannot set maximum rows of the query after it started executing.

Cause:	You used the SRW.SET_MAX_ROW packaged procedure to reduce the number of rows fetched by a query.  However, you called SRW.SET_MAX_ROW after the query was already fetched.
Action:	Move your SRW.SET_MAX_ROW to the Before Report trigger.


REP-1424'<program unit name>': Internal error while executing <procedure name>.
REP-1424:  '<program unit name>': Internal error while executing <procedure name>.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1425'<program unit name>': Error running DO_SQL package - '<embedded message>' .
REP-1425:  '<program unit name>': Error running DO_SQL package - '<embedded message>' .

Cause:	An error occurred while Report Builder was executing an SRW.DO_SQL call.  Embedded in this message, you will find a Report Builder message and, possibly, an ORACLE error message describing the exact error that occurred.
Action:	Errors in SRW.DO_SQL are most often the result of a SQL error.  Refer to your .ORACLE8 Server SQL Language Reference Manual and verify that the SQL statement in your SRW.DO_SQL call is correct.


REP-1426'<program unit name>': Running <procedure name> from incorrect context.
REP-1426:  '<program unit name>': Running <procedure name> from incorrect context.

Cause:	You attempted to call the named packaged procedure from an invalid area.  For example, SRW.SET_ATTR cannot be called from a formula.
Action:	Modify your PL/SQL code so that it does not call the packaged procedure from that context.


REP-1427'<program unit name>': Nonexistent query name referenced in <procedure name>.
REP-1427:  '<program unit name>': Nonexistent query name referenced in <procedure name>.

Cause:	You included a call to the SRW.SET_MAXROW procedure in a Before Report trigger, but the query referenced in the procedure call does not exist.
Action:	Change the call to the SRW.SET_MAXROW procedure so that it references an existing query in the report.


REP-1428'<program unit name>': Error while running <procedure name>.
REP-1428:  '<program unit name>': Error while running <procedure name>.

Cause:	The exception SRW.RUN_REPORT_FAILURE was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition after SRW.RUN_REPORT was called.
Action:	Check any PL/SQL code that might raise this exception.  If no PL/SQL raised the exception, check the command line string passed to SRW.RUN_REPORT.  Verify that the specified report exists and that all parameter values are correct.  Also note that BATCH=NO is not allowed if the report that owns the PL/SQL code is called by a command line string containing BATCH=YES.  For more information, see SRW.RUN_REPORT.


REP-1429'<program unit name>': <procedure name> cannot be invoked with batch=no.
REP-1429:  '<program unit name>': <procedure name> cannot be invoked with batch=no.

Cause:	You included a call to the SRW.RUN_REPORT procedure with a command line string containing BATCH=NO, which is not allowed.
Action:	Remove BATCH=NO from the SRW.RUN_REPORT command string.


REP-1430Cannot create REP File for report '<filename>'.  Compilation errors found.
REP-1430:  Cannot create REP File for report '<filename>'.  Compilation errors found.

Cause:	There is an error in the PL/SQL in the report you are attempting to convert.
Action:	Open the report and debug your PL/SQL.


REP-1433'<program unit name>': Error running user exit '<user exit name>'.
REP-1433:  '<program unit name>': Error running user exit '<user exit name>'.

Cause:	While running the user exit named in the message, an error occurred.
Action:	Debug your user exit and ensure that it is linked.


REP-1434'<program unit name>': <procedure name> cannot be invoked with a userid.
REP-1434:  '<program unit name>': <procedure name> cannot be invoked with a user ID.

Cause:	You included a call to the SRW.RUN_REPORT procedure with a command line string containing a user ID/password, which is not allowed.
Action:	Remove the user ID/password from the SRW.RUN_REPORT command string.


REP-1435'<program unit name>': Value of column '<column name>' was truncated.
REP-1435:  '<program unit name>': Value of column '<column name>' was truncated.

Cause:	A column (e.g., a placeholder) was assigned a value larger than its width could contain, raising the SRW.TRUNCATED_VALUE exception.  The exception was not handled, raising this error.
Action:	Make the column wide enough to contain the assigned value, or handle the exception in your PL/SQL source.


REP-1436'<program unit name>': The PL/SQL references an object which is not in the scope.
REP-1436:  '<program unit name>': The PL/SQL references an object which is not in the scope.

Cause:	In a parameter's Validation Trigger field, you entered PL/SQL source that referenced a report column.  This is not allowed.
Action:	Remove the reference to the report column from the parameter's Validation Trigger.


REP-1437Run time error in the PL/SQL development environment (DE).
REP-1437:  Run time error in the PL/SQL development environment (DE).

Cause:	This is most likely an abnormal condition.
Action:	Refer to the accompanying development environment error message for details on the problem.  If you cannot correct the problem yourself, see Abnormal Conditions.


REP-1438GETREF function parameter '<parameter name>' must be of type LONG, LONG RAW or RAW.
REP-1438:  GETREF function parameter '<parameter name>' must be of type LONG, LONG RAW or RAW.

Cause:	The second parameter in a CDE_MM.GET_REF call specifies a column that is not of type LONG, LONG RAW, or RAW.
Action:	Change the second parameter to specify a column of the correct type.


REP-1439Cannot compile program units since this is a runtime only report.
REP-1439:  Cannot compile program units since this is a runtime only report.

Cause:	The program units are from a foreign platform or an older version of PL/SQL.
Action:	Use the .rdf file instead of the .rep file, or regenerate the .rep file.


REP-1508Cross Product: value of calculation not found.
REP-1508:  Cross Product: value of calculation not found.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1510Group Manager: unable to compute column '<column name>'.
REP-1510:  Group Manager: unable to compute column '<column name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1517Column '<column1 name>' references column '<column2 name>', which has incompatible frequency.
REP-1517:  Column '<column1 name>' references column '<column2 name>', which has incompatible frequency.

Cause:	A column in your data model references another column (e.g., in the Formula field) in your data model, but the two columns are assigned to incompatible groups.  For example, if a formula column with a Group of Report referenced a column with a Group of G_Emp, this error would be raised.
Action:	Remove the column reference, or assign the referencing column to a group that is compatible with the group of the referenced column.


REP-1518Group Manager: internal error <<Oracle message>> while processing group '<group name>'.
REP-1518:  Group Manager: internal error <<Oracle message>> while processing group '<group name>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1607Record Manager: report level column '<column name>' not available in rdcagt().
REP-1607:  Record Manager: report level column '<column name>' not available in rdcagt().

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1610Record Manager: a query with internal joins has 'Maximum Number of Rows' set.
REP-1610:  Record Manager: a query with internal joins has 'Maximum Number of Rows' set.

Cause:	You most likely used SRW.SET_MAXROW to set Maximum Number of Rows on the cell query of a multi-query cross product.
Action:	Remove the call to SRW.SET_MAXROW for the cell query.


REP-1760Error Utility: internal error #1.
REP-1760:  Error Utility: internal error #1.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1761Internal error <<context info>> while processing <object name> '<object type>'.
REP-1761:  Internal error <<context info>> while processing <object name> '<object type>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1762Internal error <<context info>>.
REP-1762:  Internal error <<context info>>.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1780Stack utility: error during allocation.
REP-1780:  Stack utility: error during allocation.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1781Stack utility: error during 'push'.
REP-1781:  Stack utility: error during 'push'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1782Stack utility: error during 'pop'.
REP-1782:  Stack utility: error during 'pop'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1783Stack utility: attempt to pop empty stack.
REP-1783:  Stack utility: attempt to pop empty stack.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1800Formatter error.
REP-1800:  Formatter error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1801Unknown file type for a 'Read from File' field.
REP-1801:  Unknown file type for a 'Read from File' field.

Cause:	You attempted to create a file column, but the file type you entered is invalid.
Action:	Display the list of values and pick a valid file type.


REP-1802Unable to read contents of a field from a text file.
REP-1802:  Unable to read contents of a field from a text file.

Cause:	You have checked Read from File for a column, but Report Builder could not find the files pointed to by the column. The possible causes of this error include the following:
	Case 1:	The files do not exist.
	Case 2:	You do not have the necessary privileges to access the files.
	Case 3:	A system error made it impossible to find the files.
Action:	You can take the following actions to correct this error:
	If Case 1:	Clear Read from File or create the necessary files.
	If Case 2:	Update your privileges, if possible.
	If Case 3:	Consult your operating system documentation or contact your system administrator.


REP-1803Unable to open destination file '<filename>'.
REP-1803:  Unable to open destination file '<filename>'.

Cause:	The destination file that you specified for the report could not be opened.
Action:	Consult your operating system documentation or contact your system administrator.


REP-1804Unable to open printer definition file '<filename>'.
REP-1804:  Unable to open printer definition file '<filename>'.

Cause:	The printer definition file for the printer that you specified could not be opened.
Action:	Consult your operating system documentation or contact your system administrator.


REP-1805Unable to open mail text file '<filename>'.
REP-1805:  Unable to open mail text file '<filename>'.

Cause:	You tried to send the report output to a mail message, but the file for the message could not be opened.
Action:	Consult your Oracle*Mail documentation or contact Oracle Customer Support.  For more information, see Calling Oracle Customer Support.


REP-1806Unable to open mail command file '<filename>'.
REP-1806:  Unable to open mail command file '<filename>'.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1807Mail report command failed.
REP-1807:  Mail report command failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1808Unable to open print command file.
REP-1808:  Unable to open print command file.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1809Print report command failed.
REP-1809:  Print report command failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1810Switching to use Report Builder ASCII Driver to run character report.
REP-1810:  Switching to use Report Builder ASCII Driver to run character report.

Cause:	You are attempting to print a character-mode report to a printer or a file using either a Postscript driver or the Microsoft Windows Generic Text driver.
Action:	No action necessary.


REP-1811Error while generating a chart.
REP-1811:  Error while generating a chart.

Cause:	Report Builder called the chart runtime executable to generate a chart, but no chart was created.
Action:	Ensure that the named chart document exists and will run.


REP-1812Too many pages formatted.  There is either too much data or an error in the report's definition.
REP-1812:  Too many pages formatted.  There is either too much data or an error in the report's definition.

Cause:	The possible causes of this error include the following:
	Case 1:	You have reached a user-defined limit set to catch too much data.
	Case 2:	You have reached an error in the report definition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Abort running of the program.  Check the value of PAGE_LIMIT in the PRODUCT_PROFILE table.  Ensure that it is either '0', which means the user is allowed to format an unlimited number of pages, or some value sufficiently large to enable the user to format the report.
	If Case 2:	Debug the report in the designer.


REP-1813Object '<object name>' too large to fit in matrix cell.
REP-1813:  Object '<object name>' too large to fit in matrix cell.

Cause:	The data fetched into a matrix cell exceeds the capacity of the cell--e.g., the cell may contain a variable field, and the data may be longer than expected.
Action:	Either enlarge your matrix cells until they are able to contain the data fetched into them, or redefine your data.


REP-1814Report cannot be formatted. Object '<object name>' can never fit within '<location>'.
REP-1814:  Report cannot be formatted. Object '<object name>' can never fit within '<location>'.

Cause:	The referenced object is causing the most recently formatted page to start with exactly the same state as the page previous .  Formatting will therefore cycle until abnormally terminated.  Possible causes of this error include:
	Case 1:	An object whose Print Condition type is All overflows to the next page;
	Case 2:	An object whose sizing is Variable or Expand does not appear to extend beyond page boundaries in the Layout Model editor but does when the report is formatted;
	Case 3:	A repeating frame does not appear to extend beyond page boundaries in the Layout Model editor but does when the report is formatted.
Action 1:	Using the referenced object as a guide, examine your report layout for objects that may extend beyond page boundaries.  Note:  The object referenced in the message is the object that extends beyond the boundary.  This object may be pushed beyond the boundary by another object, and this second object may need modification.
Action 2:	This error can also be caused by a Page Protect or Anchoring Object in the Report that is forcing the report to print groups of data on the same page.  Remove the Page Protect or the Anchoring Object if possible  or create a Group Frame around the all the objects that are supposed to print on the first logical page, and make the frame Vertical Sizing Variable.


REP-1815Bad Oracle Number encountered.
REP-1815:  Bad Oracle Number encountered.

Cause:	A formula providing the value of a column failed to specify any value.
Action:	Debug any formulas in your report columns and ensure that each formula specifies a value where necessary.


REP-1816No value specified for COPIES.  No output created.
REP-1816:  No value specified for COPIES.  No output created.

Cause:	In the Runtime Parameter Form or the Print Job dialog box, you specified zero copies.
Action:	Specify a value of one or more copies.


REP-1817Start page after end page.  No pages output.
REP-1817:  Start page after end page.  No pages output.

Cause:	In the Print Job dialog box, you specified a starting page number that is greater than the ending page number.
Action:	Change either the starting page number or the ending page number such that the starting number is less than the ending number.


REP-1818Unable to read data in image format.
REP-1818:  Unable to read data in image format.

Cause:	Possible causes of this error include:
	Case 1:	You attempted to read a file or database column as containing an image, but the file or column's contents are of the wrong format.
	Case 2:	The width of the Report Builder column you specified may be truncating the image because it's too small.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure you specify a file or column containing an image in a valid format.
	If Case 2:	Change the width of the Report Builder column so that it's large enough to display the image.


REP-1819Filename '<filename>' longer than platform maximum of <number> characters.
REP-1819:  Filename '<filename>' longer than platform maximum of <number> characters.

Cause:	You have specified a name for your file that is longer than the platform-allowed maximum.  This is most likely to occur when accessing a file using Read from File, and the filename in the database is too long.
Action:	Ensure that your database is not corrupted, and/or run the report on a platform that accepts filenames of the specified length.


REP-1820Cannot use Report Builder ASCII Driver to run bitmap report.
REP-1820:  Cannot use Report Builder ASCII Driver to run bitmap report.

Cause:	You are attempting to print a bitmapped report when the Report Builder ASCII Driver is your default printer.  This is not allowed.
Action:	Choose a different printer, then print your report.


REP-1825Before Report trigger returned FALSE.
REP-1825:  Before Report trigger returned FALSE.

Cause:	Your report includes a Before Report trigger that returned a value of FALSE rather than TRUE.  When a trigger returns a value of FALSE, report formatting stops.
Action:	Make sure that your report trigger is meant to return a value of FALSE.


REP-1826Between Page trigger returned FALSE.
REP-1826:  Between Page trigger returned FALSE.

Cause:	Your report includes a Between Page trigger that returned a value of FALSE rather than TRUE.  When a trigger returns a value of FALSE, report formatting stops.
Action:	Make sure that your report trigger is meant to return a value of FALSE.


REP-1827Parentheses in format mask do not balance.
REP-1827:  Parentheses in format mask do not balance.

Cause:	You have an unmatched parenthesis in your format mask.
Action:	Edit your format mask and insert the necessary parenthesis.


REP-1828Format mask may contain at most one set of parentheses.
REP-1828:  Format mask may contain at most one set of parentheses.

Cause:	You used more than one set of parentheses in your format mask.
Action:	Use only one set of parentheses in your format mask.


REP-1829Left parenthesis must precede right parenthesis in format mask.
REP-1829:  Left parenthesis must precede right parenthesis in format mask.

Cause:	You reversed the order of the parentheses in your format mask--i.e., used the right, or close, parenthesis before the left, or open parenthesis.
Action:	Edit your format mask and reverse the order of the parentheses.


REP-1830The Exponent field in a format mask must contain exactly 4 E's.
REP-1830:  The Exponent field in a format mask must contain exactly 4 E's.

Cause:	In specifying that you want to use scientific notation for the field, you have entered too many or too few E's.  Enter four E's.
Action:	Enter the format mask with four E's.  If you want extra E's to appear in the output, put them in quotation marks (").


REP-1831Missing closing quotation mark in format mask.
REP-1831:  Missing closing quotation mark in format mask.

Cause:	You entered an opening quotation mark (") before the string in the format mask but not a closing one.  The possible causes of this error include the following:
	Case 1:	You failed to enter the closing quotation mark after the string.
	Case 2:	You entered one quotation mark within the quotation marks that begin and end the string.
Action:	You can take the following actions to correct this error:
	If Case 1:	Add an ending quotation mark after the string.
	If Case 2:	Enter another quotation mark next to the quotation mark inside the string.


REP-1832Illegal character '<character>' in format mask.
REP-1832:  Illegal character '<character>' in format mask.

Cause:	You have entered a character in a format mask which is not valid for format masks.
Action:	Delete the illegal character.  For more information, see Format Mask.


REP-1833A format mask must contain at least one digit.
REP-1833:  A format mask must contain at least one digit.

Cause:	The format mask you entered contains no digits.  You must have at least one token in your mask that represents a digit.
Action:	Enter a token in your format mask that represents a digit.  The tokens that represent digits are 0, 9, *, and S.  For more information, see Format Mask.


REP-1834A format mask may contain at most one '<' character.
REP-1834:  A format mask may contain at most one '<' character.

Cause:	You entered two left angle brackets (<<) in your format mask.  You either accidentally typed extra left angle brackets or you wanted some of the extra angle brackets be part of a string.  Note:  The angle brackets need not be entered sequentially to cause the error.
Action:	Delete the extra left angle brackets or place them inside quotation marks (") as part of a string if you want them to appear in the output.


REP-1835A format mask may contain at most one '>' character.
REP-1835:  A format mask may contain at most one '>' character.

Cause:	You entered two right angle brackets (>>) in your format mask.  You either accidentally typed extra right angle brackets or you wanted some of the extra angle brackets to be part of a string.  Note:  The angle brackets need not be entered sequentially to cause the error.
Action:	Delete the extra right angle brackets or place them inside quotation marks (") as part of a string if you want them to appear in the output.


REP-1836'<' must come before '>' in a format mask.
REP-1836:  '<' must come before '>' in a format mask.

Cause:	The left angle bracket (<) must come before the right angle bracket (>) in a format mask.
Action:	Ensure that all angle brackets that are to appear in the output are placed inside quotation marks (").  For the angle brackets that delineate the beginning and ending of the decimal aligned region, ensure that the left angle bracket precedes the right angle bracket in the format mask.


REP-1837A format mask may contain at most one decimal point.
REP-1837:  A format mask may contain at most one decimal point.

Cause:	You entered a format mask with multiple decimal points.
Action:	Place any extra decimal points that you want to appear in the output in quotation marks (").  Remove any extra decimal points outside of quotation marks.


REP-1838A format mask may contain at most one scale point.
REP-1838:  A format mask may contain at most one scale point.

Cause:	You entered the token V more than once within your format mask.
Action:	If you want the extra V's to appear in the output, put them in quotation marks (").  Otherwise, delete the V's until there is only one in the format mask.


REP-1839',' is not allowed before the first digit in a format mask.
REP-1839:  ',' is not allowed before the first digit in a format mask.

Cause:	You placed a comma before the first digit in the format mask, which is illegal.
Action:	If you want a comma to appear before the digits in the output, place it in quotation marks (") as a string.  Otherwise, delete the comma.


REP-1840',' is not allowed after the last digit in a format mask.
REP-1840:  ',' is not allowed after the last digit in a format mask.

Cause:	You placed a comma after the last digit in the format mask, which is illegal.
Action:	If you want a comma to appear after the digits in the output, place it in quotation marks (") as a string.  Otherwise, delete the comma.


REP-1841',' is not allowed after the decimal point in a format mask.
REP-1841:  ',' is not allowed after the decimal point in a format mask.

Cause:	You placed a comma after the decimal point in the format mask.
Action:	If you want a comma to appear after the decimal point in the output, place it in quotation marks (") as a string.  Otherwise, delete the comma.


REP-1842A format mask may contain at most one exponent field.
REP-1842:  A format mask may contain at most one exponent field.

Cause:	You entered the token EEEE more than once within your format mask.  You are only allowed to enter this token once per format mask.
Action:	If you want the extra E's to appear in the output, put them in quotation marks (").  Otherwise, delete the extra EEEE tokens until there is only one in the format mask.


REP-1843Format masks with exponent fields must have exactly one digit before the decimal point.
REP-1843:  Format masks with exponent fields must have exactly one digit before the decimal point.

Cause:	You entered a scientific notation format mask, but had no digits or more than one digit to the left of the decimal point.
Action:	If you had more than one digit to the left of the decimal point, delete digits until there is only one to the left of the decimal point.  If you had no digits to the left of the decimal point, add one digit.


REP-1844Internal error: Bad index in a Flexible Array.
REP-1844:  Internal error: Bad index in a Flexible Array.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1845The decimal point must come between '<' and '>' in a format mask.
REP-1845:  The decimal point must come between '<' and '>' in a format mask.

Cause:	You have placed a decimal point outside the left and right angle brackets (< and >) of your format mask.
Action:	Edit your format mask to either remove the decimal point or place it between the brackets.


REP-1846If Roman numeral format mask, must be simply "RN" or "rn".
REP-1846:  If Roman numeral format mask, must be simply "RN" or "rn".

Cause:	When you specify the Roman numeral format mask token (RN or rn), you cannot specify any other format mask tokens.
Action:	If you want the values to be formatted as Roman numerals, eliminate all format mask tokens except RN or rn from Format Mask.  Otherwise, do not use the RN or rn token.


REP-1847Failed while trying to set up for printing.
REP-1847:  Failed while trying to set up for printing.

Cause:	You attempted to print a report.  The possible causes of this error include the following:
	Case 1:	In the Runtime Parameter Form or on the command line, you specified Printer for DESTYPE, but specified an invalid printer name for DESNAME.
	Case 2:	You are executing a report that executes a second report using SRW.RUN_REPORT.  DESTYPE for both reports is set to either File or Printer, but the first report must be run to the screen.
Action:	You can take the following actions to correct this error:
	If Case 1:	Re-try the operation, specifying a valid printer name for DESNAME.
	If Case 2:	Change the DESTYPE for the first report to Screen or Previewer and run it again.


REP-1848Failed while trying to begin printing.
REP-1848:  Failed while trying to begin printing.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1849Failed while printing.
REP-1849:  Failed while printing.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1850Error in column <number> of line <number> of printer definition file <filename>: End of file reached inside quoted string.
REP-1850:  Error in column <number> of line <number> of printer definition file <filename>: End of file reached inside quoted string.

Cause:	Your printer definition file contains a quoted string that was not ended with a quote before the end of the file.
Action:	Use the location specified in the error message to locate the error and add the end quote to the quoted string in your printer definition file.


REP-1851Error in column <number> of line <number> of printer definition file <filename>: String is longer than <number> characters.
REP-1851:  Error in column <number> of line <number> of printer definition file <filename>: String is longer than <number> characters.

Cause:	A string in your printer definition file is longer than maximum number of allowable characters.
Action:	Reduce length of string.


REP-1852Error in column <number> of line <number> of printer definition file <filename>: Unknown keyword "<keyword>...".
REP-1852:  Error in column <number> of line <number> of printer definition file <filename>: Unknown keyword "<keyword>...".

Cause:	An incorrect keyword is included in your printer definition file.
Action:	For information on valid keywords, see Printer Definition File Syntax.


REP-1853Error in column <number> of line <number> of printer definition file <filename>: Unknown keyword "<keyword>".
REP-1853:  Error in column <number> of line <number> of printer definition file <filename>: Unknown keyword "<keyword>".

Cause:	An incorrect keyword is included in your printer definition file.
Action:	For more information on valid keywords, see Printer Definition File Syntax.


REP-1854Error in column <number> of line <number> of printer definition file <filename>: Invalid control character "<character>".
REP-1854:  Error in column <number> of line <number> of printer definition file <filename>: Invalid control character "<character>".

Cause:	An invalid control character is included in your printer definition file.
Action:	Replace or remove the invalid control character in your printer definition file.


REP-1855Error in column <number> of line <number> of printer definition file <filename>: Unknown character "<character>".
REP-1855:  Error in column <number> of line <number> of printer definition file <filename>: Unknown character "<character>".

Cause:	An unknown character is included in your printer definition file.
Action:	Replace or remove the unknown character in your printer definition file.


REP-1856Error in column <number> of line <number> of printer definition file <filename>: <character> is not a valid ASCII character.
REP-1856:  Error in column <number> of line <number> of printer definition file <filename>: <character> is not a valid ASCII character.

Cause:	An invalid ASCII character appears in your printer definition file.
Action:	Replace or remove the invalid ASCII character in your printer definition file.


REP-1857Error in column <number> of line <number> of printer definition file <filename>: Expected ")" to follow <character>.
REP-1857:  Error in column <number> of line <number> of printer definition file <filename>: Expected ")" to follow <character>.

Cause:	You have an unmatched parenthesis in your printer definition file.
Action:	Edit your printer definition file and insert the necessary parenthesis.


REP-1858Error in column <number> of line <number> of printer definition file <filename>: octal(<octal number>) is not a valid ASCII character.
REP-1858:  Error in column <number> of line <number> of printer definition file <filename>: octal(<octal number>) is not a valid ASCII character.

Cause:	The octal code for an ASCII character in your printer definition file is incorrect.
Action:	Edit your printer definition file and correct the code for the ASCII character.


REP-1859Error in column <number> of line <number> of printer definition file <filename>: hex(<character>) is not a valid ASCII character.
REP-1859:  Error in column <number> of line <number> of printer definition file <filename>: hex(<character>) is not a valid ASCII character.

Cause:	The hex code for an ASCII character in your printer definition file in incorrect.
Action:	Edit your printer definition file and correct the code for the ASCII character.


REP-1860Column <number> of line <number> of printer definition file <filename>: Expected "left", "center", or "right" to follow "<character>".
REP-1860:  Column <number> of line <number> of printer definition file <filename>: Expected "left", "center", or "right" to follow "<character>".

Cause:	Your printer definition file contains an incomplete code string.
Action:	Edit your printer definition file and complete the code string with the appropriate word.


REP-1861Column <number> line <number> of file <filename>: Expected "horizontal","vertical","top","center",or "bottom" to follow "box".
REP-1861:  Column <number> line <number> of file <filename>: Expected "horizontal","vertical","top","center",or "bottom" to follow "box".

Cause:	Your printer definition file contains an incomplete "box" code string.
Action:	Edit your printer definition file and complete the "box" code string with the appropriate word.


REP-1862Error in column <number> of line <number> of printer definition file <filename>: Expected keyword "printer".
REP-1862:  Error in column <number> of line <number> of printer definition file <filename>: Expected keyword "printer".

Cause:	Your printer definition file does not include the required code "printer".
Action:	Edit your printer definition file and add the required code "printer" followed by the name of the printer in a quoted string, preferably on the first line of the printer definition file.


REP-1863Error in column <number> of line <number> of printer definition file <filename>: Expected name of printer in quotation marks.
REP-1863:  Error in column <number> of line <number> of printer definition file <filename>: Expected name of printer in quotation marks.

Cause:	Your printer definition file contains the name of the printer after the "printer" code, but the name does not appear in a quoted string.
Action:	Edit your printer definition file and place quotation marks (") around the name of the printer after the "printer" code.


REP-1864Col <number> line <number> of file <filename>: Expected "width, height, return, linefeed, before report, after page, after report, or code".
REP-1864:  Col <number> line <number> of file <filename>: Expected "width, height, return, linefeed, before report, after page, after report, or code".

Cause:	Your printer definition file does not contain any of the code words expected in a printer definition file.
Action:	Edit your printer definition file and add the code words that are missing.


REP-1865Error in column <number> of line <number> of printer definition file <filename>: Expected number after "width".
REP-1865:  Error in column <number> of line <number> of printer definition file <filename>: Expected number after "width".

Cause:	Your printer definition file contains the "width" code, but no number specifying the width of the report appears after it.
Action:	Edit your printer definition file and insert a number specifying the width of the report after the "width" code.


REP-1866Error in column <number> of line <number> of printer definition file <filename>: Expected number after "height".
REP-1866:  Error in column <number> of line <number> of printer definition file <filename>: Expected number after "height".

Cause:	Your printer definition file contains the "height" code, but no number specifying the height of the report appears after it.
Action:	Edit your printer definition file and insert a number specifying the height of the report after the "height" code.


REP-1867Error in column <number> of line <number> of printer definition file <filename>: Expected "report" to follow "before".
REP-1867:  Error in column <number> of line <number> of printer definition file <filename>: Expected "report" to follow "before".

Cause:	Your printer definition file contains the word "before" but not the accompanying word "report".
Action:	Edit the printer definition file to include a complete "before report" entry.


REP-1868Error in column <number> of line <number> of printer definition file <filename>: Expected "pages" to follow "between".
REP-1868:  Error in column <number> of line <number> of printer definition file <filename>: Expected "pages" to follow "between".

Cause:	Your printer definition file contains the word "between" but not the accompanying word "pages".
Action:	Edit the printer definition file to include a complete "between pages" entry.


REP-1869Error in column <number> of line <number> of printer definition file <filename>: Expected "report" or "page" to follow "after".
REP-1869:  Error in column <number> of line <number> of printer definition file <filename>: Expected "report" or "page" to follow "after".

Cause:	Your printer definition file (for a multi-page report) contains the code word "after" but not the accompanying word "report".
Action:	Edit the printer definition file to include a complete "after report" entry.


REP-1870Error in column <number> of line <number> of printer definition file <filename>: Expected name of code in quotation marks.
REP-1870:  Error in column <number> of line <number> of printer definition file <filename>: Expected name of code in quotation marks.

Cause:	Your printer definition file contains the "code" code with a user-defined string, but the string is not enclosed within quotation marks.
Action:	Edit your printer definition file and enclose the "code" user-defined string with quotation marks.


REP-1871Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "dec".
REP-1871:  Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "dec".

Cause:	Your printer definition file contains a generalized string using "dec", but "dec" is not followed with a left parenthesis.
Action:	Edit your printer definition file and add parentheses around the value following "dec".


REP-1872Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".
REP-1872:  Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".

Cause:	Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the right parenthesis.
Action:	Edit your printer definition file and add a value between the parentheses in the generalized string.


REP-1873Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "octal".
REP-1873:  Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "octal".

Cause:	Your printer definition file contains a generalized string using "octal", but "octal" is not followed with a left parenthesis.
Action:	Edit your printer definition file and add parentheses around the value following "octal".


REP-1874Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".
REP-1874:  Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".

Cause:	Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the left parenthesis.
Action:	Edit your printer definition file and add a value between the parentheses in the generalized string.


REP-1875Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "hex".
REP-1875:  Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "hex".

Cause:	Your printer definition file contains a generalized string using "hex", but "hex" is not followed with a left parenthesis.
Action:	Edit your printer definition file and add parentheses around the value following "hex".


REP-1876Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".
REP-1876:  Error in column <number> of line <number> of printer definition file <filename>: Expected number to follow "(".

Cause:	Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the left parenthesis.
Action:	Edit your printer definition file and add a value between the parentheses in the generalized string.


REP-1877Error in column <number> of line <number> of printer definition file <filename>: Expected control character to follow "^".
REP-1877:  Error in column <number> of line <number> of printer definition file <filename>: Expected control character to follow "^".

Cause:	Your printer definition file contains a generalized string using "^", but no control character follows the "^".
Action:	Edit your printer definition file and add a control character after "^".


REP-1878Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "control".
REP-1878:  Error in column <number> of line <number> of printer definition file <filename>: Expected "(" to follow "control".

Cause:	Your printer definition file contains a keyword and generalized string (e.g., after report, before report), but no left parenthesis follows the word "control".
Action:	Edit your printer definition file and add a left parenthesis following the word "control".


REP-1879Error in column <number> of line <number> of printer definition file <filename>: Expected control character to follow "(".
REP-1879:  Error in column <number> of line <number> of printer definition file <filename>: Expected control character to follow "(".

Cause:	Your printer definition file contains a keyword and generalized string (e.g., after report, before report), but no control character follows the left parenthesis.
Action:	Edit your printer definition file and add a control character between the parentheses after the word "control".


REP-1880Error in column <number> of line <number> of printer definition file <filename>: Box drawing string must be exactly 1 character long.
REP-1880:  Error in column <number> of line <number> of printer definition file <filename>: Box drawing string must be exactly 1 character long.

Cause:	Your printer definition file contains the "box" code string, but the drawing string specified between quotes is more than one character long.
Action:	Edit your printer definition file, making sure that one and only one character is specified as a drawing string.


REP-1881Error in column <number> of line <number> of printer definition file <filename>: Expected string containing box drawing character.
REP-1881:  Error in column <number> of line <number> of printer definition file <filename>: Expected string containing box drawing character.

Cause:	Your printer definition file contains the "box" code string, but no drawing string is specified.
Action:	Edit your printer definition file and specify a drawing string.


REP-1882Column <number> line <number> of file <filename>: Expected "horizontal","vertical","top","center",or "bottom" to follow "box".
REP-1882:  Column <number> line <number> of file <filename>: Expected "horizontal","vertical","top","center",or "bottom" to follow "box".

Cause:	Your printer definition file contains the "box" code string, but the following required word (one of "horizontal", "vertical", "top", "center", or "bottom") is not specified.
Action:	Edit your printer definition file and add the appropriate required word.


REP-1883Unexpected end of printer definition file.
REP-1883:  Unexpected end of printer definition file.

Cause:	Report Builder was able to open your printer definition file, but an error occurred while reading it.
Action:	Make sure you specified the correct printer definition file.  Also, check the contents of the printer definition file.  Edit the file if necessary.


REP-1884 Hang while sending output
REP-1884:  Hang while sending output

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1885Can't send output to printer.
REP-1885:  Can't send output to printer.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-1886Expected "I" after "M".
REP-1886:  Expected "I" after "M".

Cause:	The M you entered in a format mask was not followed by I.  The only token that begins with M is the MI token.
Action:	If you want to use the MI token, enter an I after the M.  If you want the character M to appear in your output, place it inside double quotes (").  Otherwise, delete the M from Format Mask.


REP-1887Expected "R" after "P".
REP-1887:  Expected "R" after "P".

Cause:	The P you entered in a format mask was not followed by R.  The only token that begins with P is the PR token.
Action:	If you meant to use the PR token, enter an R after the P.  If you want the character P to appear in your output, you need to place it inside double quotes (").  Otherwise, delete the P from Format Mask.


REP-1888Only one sign token allowed.
REP-1888:  Only one sign token allowed.

Cause:	You entered more than one sign token in a format mask.
Action:	Delete all sign tokens but one from the format mask.


REP-1889Trailing sign token must be at end.
REP-1889:  Trailing sign token must be at end.

Cause:	You did not place a sign token at the end of the format mask.
Action:	Place the sign token (e.g., MI, PR, DB, and CR) at the end of the format mask.


REP-1890"S" token must be at beginning or end.
REP-1890:  "S" token must be at beginning or end.

Cause:	You did not place the S token at the beginning or the end of the format mask.
Action:	Place the S token at the beginning or the end of the format mask or delete it.


REP-1891Parentheses tokens must surround other tokens.
REP-1891:  Parentheses tokens must surround other tokens.

Cause:	The parentheses tokens must surround all the other tokens in the format mask.  The parentheses do not surround all other tokens.
Action:	Place the parentheses around all of the other tokens in the format mask.


REP-1892The destype you specified is not supported for pdf or html.
REP-1892:  The destype you specified is not supported for pdf or html.

Cause:	You entered an Destination Type that is invalid for PDF or HTML output.
Action:	Retry the operation, entering one of the valid Destination Types.


REP-1893The destype you specified is not supported on this platform.
REP-1893:  The destype you specified is not supported on this platform.

Cause:	You entered a Destination Type that is invalid for your operating system (e.g., Sysout, while running on Microsoft Windows).
Action:	Retry the operation, entering one of the valid Destination Types.


REP-1894The report definition was modified during the current run. No new pages will be generated.
REP-1894:  The report definition was modified during the current run. No new pages will be generated.

Cause:	While previewing a report (using RWBLD60), you modified the report's definition (e.g., modified a query, added or deleted objects, etc.), and then returned to the Previewer and attempted to view additional pages.
Action:	This is not allowed.  Report Builder cannot guarantee that all of the information used at runtime is still present, so formatting is halted.


REP-1895Date formatting error while processing <field name>.
REP-1895:  Date formatting error while processing <field name>.

Cause:	Report Builder could not format the specified date field.
Action:	Check the format mask of the specified date field.


REP-1896Error in column <number> of line <number> of printer definition file <filename>: Expected 'backspace' or 'overstrike' to follow 'hilight'.
REP-1896:  Error in column <number> of line <number> of printer definition file <filename>: Expected 'backspace' or 'overstrike' to follow 'hilight'.

Cause:	The specified printer definition file contains the 'hilight' setting, but the setting was not completed properly.
Action:	Add either 'overstrike' or 'backspace <sequence>' after 'hilight'.


REP-1897Error in column <number> of line <number> of printer definition file <filename>: Non-numeric user-defined printer codes are not supported.
REP-1897:  Error in column <number> of line <number> of printer definition file <filename>: Non-numeric user-defined printer codes are not supported.

Cause:	The specified printer definition file contains a user defined printer code that is not a number.
Action:	Change the user defined printer code to a number.


REP-1898Error in column <number> of line <number> of printer definition file <filename>: Hilight setting can only be defined once.
REP-1898:  Error in column <number> of line <number> of printer definition file <filename>: Hilight setting can only be defined once.

Cause:	The specified printer definition file contains more than one hilight setting.
Action:	Remove all but one of the hilight settings from the printer definition file.


REP-1899Unable to convert Graphics Display or Icon to .gif format - image skipped.
REP-1899:  Unable to convert Graphics Display or Icon to .gif format - image skipped.

Cause:	Report Builder was unable to convert an embedded chart display or icon to a GIF format for displaying within an HTML document. This only occurs when Report Builder cannot access a window system in order to draw the image.
Action:	Run the report using the bitmap executable under a windowing system to allow Report Builder access to a display.


REP-1920Character mode runtime incompatible with DESFORMAT of PDF, HTML, HTMLCSS, or RTF.
REP-1920:  Character mode runtime incompatible with DESFORMAT of PDF, HTML, HTMLCSS, or RTF.

Cause:	You are attempting to run a report with a destination format of PDF, HTML, HTMLCSS, or RTF.  These formats are only available when running in a bitmap environment and producing a bitmap output.
Action:	Rerun the report with a bitmap executable or set MODE=BITMAP if already running with a bitmap executable.


REP-1940:  Column <number> line <number> of <filename>: Expected visualorder, logicalorder, contextualshaping. . .

Cause:	Your printer definition file contains the nls code string, but the required word is not specified.
Action:	Edit you printer definition file and add the required word (visualorder, logicalorder, contextualshaping, contextuallayout, multibyte, or pcharset).


REP-1941:  Column <number> line <number> of <filename>: Expected yes or no.

Cause:	Your printer definition file contains one of the following: visualorder, logicalorder, contextualshaping, contextuallayout, multibyte, or pcharset.  However it is missing the yes or no specification.
Action:	Edit your printer definition file and specify yes or no.


REP-1942:  Column <number> line <number> of <filename>: Expected name of character set to follow pcharset.

Cause:	Your printer definition file contains pcharset, but the name of the character set is not specified.
Action:	Edit your printer definition file and specify the character set name.


REP-1943:  Column <number> line <number> of <filename>: Defined printer character set is unsupported.

Cause:	Your printer definition file references an unsupported character set.
Action:	Edit your printer definition file and ensure that the character set name is correct.


REP-1950Invalid Source specified.
REP-1950:  Invalid Source specified.

Cause:	The source you specified for RWCON60 is not a valid source.
Action:	Ensure that you are specifying the correct object or file and that the STYPE is correct for that file or object.


REP-1951Invalid Destination specified.
REP-1951:  Invalid Destination specified.

Cause:	The Destination you specified for RWCON60 is not a valid source.
Action:	Ensure that you are specifying the correct object or file and that the DTYPE is correct for that file or object.


REP-1952Number of Destination items must be zero or match number of Source items.
REP-1952:  Number of Destination items must be zero or match number of Source items.

Cause:	In the Convert dialog box, or while using RWCON60, you specified a list of Destination items, but the number of items specified is greater than zero and does not match the number of Source items specified.
Action:	To have Report Builder derive the Destination names from the specified Source names, leave Destination blank.  Otherwise, make sure the number of Destination names specified matches the number of Source names specified.    Note:  If you use wildcards in the Source specification, make sure the number of Destination names matches the number of Source items in the expanded wildcard list.


REP-2000User Exit error.
REP-2000:  User Exit error.

Cause:	An error occurred in the user exit.
Action:	If you created the user exit, debug the code.  Otherwise, contact your DBA.


REP-2001IAF GET: unknown column '<column name>'
REP-2001:  IAF GET: unknown column '<column name>'

Cause:	You specified an unknown column name in your user exit's IAF GET statement.
Action:	Make sure you specify the name of a valid column in the IAF GET statement.


REP-2002IAF PUT: unknown column '<column name>'
REP-2002:  IAF PUT: unknown column '<column name>'

Cause:	You specified an unknown column name in your user exit's IAF PUT statement.
Action:	Make sure you specify the name of a valid column in the IAF PUT statement.


REP-2003Unable to find user exit.
REP-2003:  Unable to find user exit.

Cause:	Report Builder could not find the user exit that it was supposed to run at this point.  The most likely cause is that the name and/or location of the user exit code was not specified correctly.
Action:	If you created the user exit, check to make sure you specified the name and location of the code correctly when installing it.  Otherwise, contact your DBA.


REP-2004Warning: Unable to retrieve PL/SQL source code of '<object name>'.
REP-2004:  Warning: Unable to retrieve PL/SQL source code of '<object name>'.

Cause:	You selected File [image] Administration [image] Report Doc to document one or more reports, but the RWEPLS user exit failed to retrieve the PL/SQL source code of an object.  This is most likely an abnormal condition.
Action:	Check the PL/SQL source code in the named object.  For information, see  Abnormal Conditions.


REP-2005IAF PUT: value of column '<column name>' was truncated
REP-2005:  IAF PUT: value of column '<column name>' was truncated

Cause:	Your IAF PUT statement assigned a value to the named column, but the column was not wide enough to hold the entire value, causing it to truncate.
Action:	Widen the column so that it is can hold the entire value.


REP-2100Calculation Manager error.
REP-2100:  Calculation Manager error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2101Calculation Manager : source column cannot use segmented memory.
REP-2101:  Calculation Manager : source column cannot use segmented memory.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2102Calculation Manager : computed column cannot use segmented memory.
REP-2102:  Calculation Manager : computed column cannot use segmented memory.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2103Column '<column name>' : PL/SQL formula returned invalid value or no value.
REP-2103:  Column '<column name>' : PL/SQL formula returned invalid value or no value.

Cause:	You entered an SRW.DO_SQL statement that caused the ORACLE message.
Action:	Edit the SRW.DO_SQL statement.  For more information on the ORACLE message, see the ORACLE8 Server Messages and Codes Manual.


REP-2300<Oracle message>
REP-2300:  <Oracle message>

Cause:	You entered an SRW.DO_SQL statement that caused the ORACLE message.
Action:	Edit the SRW.DO_SQL statement.  For more information on the ORACLE message, see the ORACLE8 Server Messages and Codes Manual.


REP-2301Error allocating SQLDA descriptor. <Oracle message>
REP-2301:  Error allocating SQLDA descriptor. <Oracle message>

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2302Error parsing the SQL statement. <Oracle message>
REP-2302:  Error parsing the SQL statement. <Oracle message>

Cause:	Report Builder encountered an error while parsing the SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the SQL statement could not be parsed.


REP-2303Error describing bind variables. <Oracle message>
REP-2303:  Error describing bind variables. <Oracle message>

Cause:	Report Builder encountered an error while describing bind variables in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the bind variables could not be described.


REP-2304Error opening SQL cursor. <Oracle message>
REP-2304:  Error opening SQL cursor. <Oracle message>

Cause:	Report Builder encountered an error while opening a cursor in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the cursor could not be opened.


REP-2305Error describing select list. <Oracle message>
REP-2305:  Error describing select list. <Oracle message>

Cause:	Report Builder encountered an error while describing the select list in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the bind variables could not be described.


REP-2306Error fetching bind variables. <Oracle message>
REP-2306:  Error fetching bind variables. <Oracle message>

Cause:	Report Builder encountered an error while fetching bind variables in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the bind variables could not be fetched.


REP-2307Error fetching data record. <Oracle message>
REP-2307:  Error fetching data record. <Oracle message>

Cause:	Report Builder encountered an error while fetching a data record in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the data record could not be fetched.


REP-2308Error processing select list. <Oracle message>
REP-2308:  Error processing select list. <Oracle message>

Cause:	Report Builder encountered an error while processing the select list in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the select list is invalid.


REP-2309Error formatting date field. <Oracle message>
REP-2309:  Error formatting date field. <Oracle message>

Cause:	Report Builder encountered an error while formatting a date field in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the date field could not format.


REP-2310Error putting value into column. <Oracle message>
REP-2310:  Error putting value into column. <Oracle message>

Cause:	Report Builder encountered an error while trying to insert a value into a column in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the value could not be assigned.


REP-2311Error during Commit. <Oracle message>
REP-2311:  Error during Commit. <Oracle message>

Cause:	Report Builder encountered an error while trying to do a commit in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the commit failed.


REP-2312Error allocating data record. <Oracle message>
REP-2312:  Error allocating data record. <Oracle message>

Cause:	Report Builder encountered an error while allocating a data record in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the record could not be allocated.


REP-2313Error parsing select list. <Oracle message>
REP-2313:  Error parsing select list. <Oracle message>

Cause:	Report Builder encountered an error while parsing the select list in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the select list could not be parsed.


REP-2314Error closing SQL cursor. <Oracle message>
REP-2314:  Error closing SQL cursor. <Oracle message>

Cause:	Report Builder encountered an error while trying to close a SQL cursor in an SRW.DO_SQL statement.
Action:	Refer to the ORACLE message to see why the close cursor operation failed.


REP-2315Error freeing data record. <Oracle message>
REP-2315:  Error freeing data record. <Oracle message>

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2316Unknown column '<column name>'
REP-2316:  Unknown column '<column name>'

Cause:	A column referred to in an SRW.DO_SQL statement cannot be found.
Action:	Debug your PL/SQL and make sure your SRW.DO_SQL statement contains the correct column name.


REP-2317Value of column '<column name>' was truncated.
REP-2317:  Value of column '<column name>' was truncated.

Cause:	A column value obtained via an SRW.DO_SQL statement was truncated.
Action:	Go to the column's property palette and increase its Width.  Or, restrict the size of the value that your SRW.DO_SQL statement is putting into the column.


REP-2400DEBUG : internal error 0
REP-2400:  DEBUG : internal error 0

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-2500  Error $0 occurred.  See the release notes file (relnotes) for further information about this error.
REP-2500  Error <error number> occurred.  See the release notes file (relnotes.txt) for further information about this error.

Cause:	When the Report Wizard attempted to default the layout, an error was raised.
Action:	Fix the problem identified by the error number referenced in the error message text.


REP-3000Internal error starting Oracle Toolkit.
REP-3000:  Internal error starting Oracle Toolkit.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3001Internal error initializing File Dialog.
REP-3001:  Internal error initializing File Dialog.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3002Error initializing printer.  Please make sure a printer is installed.
REP-3002:  Error initializing printer.  Please make sure a printer is installed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3020Internal error starting Oracle Resource Manager.
REP-3020:  Internal error starting Oracle Resource Manager.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3021Internal error processing menu resource.
REP-3021:  Internal error processing menu resource.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3022Internal error processing window resource.
REP-3022:  Internal error processing window resource.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3023Resource File not found.
REP-3023:  Resource File not found.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3040Internal error starting Oracle Observer Model.
REP-3040:  Internal error starting Oracle Observer Model.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3060Internal error initializing color table.  Checking VGS resources is recommended.
REP-3060:  Internal error initializing color table.  Checking VGS resources is recommended.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3080Internal error initializing Oracle Image.
REP-3080:  Internal error initializing Oracle Image.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3081Error running image viewer.
REP-3081:  Error running image viewer.

Cause:	You selected a Previewer button with a defined action of displaying an image, but the image viewer is unavailable.  Possible causes of this error include:
	Case 1:	The image specified as the source is in an incorrect format.
	Case 2:	You are out of memory.
	Case 3:	This is an abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Ensure that the image file specified as the source of the button action is in a displayable format.
	If Case 2:	Make more memory available, if you can, or ask your system administrator for assistance.
	If Case 3:	For information, see  Abnormal Conditions.


REP-3082Error running sound dialog.
REP-3082:  Error running sound dialog.

Cause:	You selected a Previewer button with a defined action of playing a sound, but the sound dialog is unavailable.  Possible causes of this error include:
	Case 1:	The sound file specified as the source is in an incorrect format.
	Case 2:	You are out of memory.
	Case 3:	This is an abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Ensure that the sound file specified as the source of the button action is in a playable format.
	If Case 2:	Make more memory available, if you can, or ask your system administrator for assistance.
	If Case 3:	For information, see  Abnormal Conditions.


REP-3083Error running video player.
REP-3083:  Error running video player.

Cause:	You selected a Previewer button with a defined action of playing a video, but the video player is unavailable.  Possible causes of this error include:
	Case 1:	The video file specified as the source is in an incorrect format.
	Case 2:	You are out of memory.
	Case 3:	This is an abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Ensure that the video file specified as the source of the button action is in a playable format.
	If Case 2:	Make more memory available, if you can, or ask your system administrator for assistance.
	If Case 3:	For information, see  Abnormal Conditions.


REP-3085Multimedia source file '<filename>' not found.
REP-3085:  Multimedia source file '<filename>' not found.

Cause:	You activated the button in the Previewer, but the source for the button's intended action (whether sound, image, or video) cannot be found or has been corrupted.
Action:	Open the property palette for the button in question and verify the existence, format, and path information for the specified source file.


REP-3086Bad multimedia source file.
REP-3086:  Bad multimedia source file.

Cause:	You activated the button in the Previewer, but the source for the button's intended action (whether sound, image, or video) has been corrupted.
Action:	Open the property palette for the button in question and verify the existence, format, and path information for the specified source file.  If it is correct, check the file itself.


REP-3087ImageViewer not supported on this configuration.
REP-3087:  ImageViewer not supported on this configuration.

Cause:	Your platform and/or configuration will not support displaying images via the ImageViewer.
Action:	No action is necessary.


REP-3088Sound not supported on this configuration.
REP-3088:  Sound not supported on this configuration.

Cause:	Your platform and/or configuration will not support playback of sound files.
Action:	No action is necessary.


REP-3089Video not supported on this configuration.
REP-3089:  Video not supported on this configuration.

Cause:	Your platform and/or configuration will not support playback of video files.
Action:	No action is necessary.


REP-3100Matrix must include at least 1 Down and 1 Across repeating frame.
REP-3100:  Matrix must include at least 1 Down and 1 Across repeating frame.

Cause:	You tried to create a matrix (using Tools [image] Create Matrix) without the proper objects selected in the Layout Model editor.  A matrix layout requires that at least one group have a repeat direction of Down and one have a repeat direction of Across.
Action:	Select two repeating frames--one Down, one Across--that overlap, then choose Arrange [image] Create Matrix.


REP-3101All selected Down and Across repeating frames must be nested.
REP-3101:  All selected Down and Across repeating frames must be nested.

Cause:	You tried to create a matrix (using Arrange [image] Create Matrix) and the Down and Across repeating frames were not properly overlapping and nested.
Action:	Make sure the selected Down and Across repeating frames are properly overlapping and nested before creating the matrix.


REP-3102Anchors, matrices, and margins cannot be grouped.
REP-3102:  Anchors, matrices, and margins cannot be grouped.

Cause:	You chose Arrange [image] Group and at least one of the objects selected was an anchor, matrix, or margin.
Action:	Deselect all anchors, matrices, and margins before grouping objects.


REP-3103Only text and graphical boilerplates can be rotated.
REP-3103:  Only text and graphical boilerplates can be rotated.

Cause:	You attempted to rotate either a frame, a field, a margin, an anchor, a matrix object, a piece of link file boilerplate, a chart, an OLE2 object, or a button.  None of these can be rotated.
Action:	You can rotate any boilerplate objects except images and link file boilerplate.  Depending on your operating system, you may or may not be able to see the text of boilerplate text that is rotated.


REP-3104Anchors and matrices cannot be scaled separately from their associated objects.
REP-3104:  Anchors and matrices cannot be scaled separately from their associated objects.

Cause:	You attempted to scale one of the layout objects listed above without also scaling its associated object.  This is not allowed.
Action:	Select at least one associated object (anchoring object for anchors, repeating frames for matrices), then re-try the scaling operation.


REP-3105Chart Column must be selected for the chart Query.
REP-3105:  Chart Column must be selected for the chart Query.

Cause:	You entered a name for chart Query, but you did not select any chart Columns.  If you specify chart Query, you must also specify chart Columns.
Action:	Specify chart Columns or remove the value from chart Query.


REP-3106Warning: Chart Column selected without chart Query name. The selected chart Column will be ignored.
REP-3106:  Warning: Chart Column selected without chart Query name. The selected chart Column will be ignored.

Cause:	You selected a Source or chart Column but did not enter the name of a chart Query.
Action:	Enter the name of the chart query to which you intend to pass data.


REP-3107Object <object name> cannot be moved in front of its child <object name>. Operation disallowed.
REP-3107:  Object <object name> cannot be moved in front of its child <object name>. Operation disallowed.

Cause:	You tried to move a layout object in front of one or more of its own child objects.
Action:	If you still want to move the layout object, toggle Confine mode off, then move it.  Otherwise, no action necessary.


REP-3108Object <object name> cannot be moved behind its container <object name>. Operation disallowed.
REP-3108:  Object <object name> cannot be moved behind its container <object name>. Operation disallowed.

Cause:	You tried to move a layout object behind one or more of its own parent objects.
Action:	If you still want to move the layout object, toggle Confine mode off, then move it.  Otherwise, no action necessary.


REP-3109Warning: Alignment operation failed because of container constraints. Undo changes to revert to the original state.
REP-3109:  Warning: Alignment operation failed because of container constraints. Undo changes to revert to the original state.

Cause:	You tried to align multiple layout objects but the result of such an operation would have violated container constraints (i.e., moved a field outside of its enclosing frame).
Action:	Select Edit [image] Undo to ensure your layout is the same as before the attempted operation.  Then you can either resize or reposition the container in question to enable you to perform the operation, or do nothing.


REP-3110Warning: Same size operation failed because of container constraints. Undo changes to revert to the original state.
REP-3110:  Warning: Same size operation failed because of container constraints. Undo changes to revert to the original state.

Cause:	You tried to change one or more layout objects to the same size, but the result of such an operation would have violated container constraints (i.e., enlarged a field beyond its enclosing frame).
Action:	Select Edit [image] Undo to ensure your layout is the same as before the attempted operation.  Then, you can either resize or reposition the container in question to enable you to perform the operation, or do nothing.


REP-3111Changing the border width of <object name> violates the constraints of confined mode. Operation disallowed.
REP-3111:  Changing the border width of <object name> violates the constraints of confined mode. Operation disallowed.

Cause:	You tried to change the border width of an object such that the result would have violated container constraints (i.e., widening the border of a boilerplate object so that it extended beyond its enclosing frame).
Action:	No action necessary.


REP 3112.  Objects cannot be created in the template layout body layer.

Cause:	You tried to create an object in the layout body layer of a template.  You may only create objects in the margin, header pages, or trailer pages of a template.
Action:	No action necessary.


REP-3130Parameter form fields and images cannot be rotated.
REP-3130:  Parameter form fields and images cannot be rotated.

Cause:	You tried to rotate one of the parameter form objects listed above.  This is not allowed.
Action:	You can rotate any boilerplate objects, except images, in the Parameter Form editor.  Depending on your operating system, you may or may not be able to see the text of boilerplate text that is rotated.


REP-3131Parameter form boilerplate text cannot fit on the page.
REP-3131:  Parameter form boilerplate text cannot fit on the page.

Cause:	You entered text in the Title, Hint, Status, or Label field in the Parameter Form Builder that is too long to fit on the page.
Action:	Reduce the length of the appropriate text field.


REP-3140Program unit editor internal error. Could not get document handle.
REP-3140:  Program unit editor internal error. Could not get document handle.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3150One painter must remain open for each report.
REP-3150:  One painter must remain open for each report.

Cause:	You attempted to close all three of the editors (Data Model, Layout Model, and Parameter Form) for a report.  You must leave at least one editor open.
Action:	Leave one editor open for each report.


REP-3151Invalid width for column '<column name>' cannot be highlighted, since group '<group name>' is not selected.
REP-3151:  Invalid width for column '<column name>' cannot be highlighted, since group '<group name>' is not selected.

Cause:	An invalid value was entered for the Width of a column in the Report Wizard.  Since the group that owns the column is not selected, the column is not listed.
Action:	Select the group that owns the column.  Scroll down to the column and enter a valid value for Width.


REP-3152Link, anchor, or polygon creation must be completed in the painter before this action.
REP-3152:  Link, anchor, or polygon creation must be completed in the painter before this action.

Cause:	You tried to perform some action (e.g., close the report) before finishing the creation of a data link in the Data Model editor, an anchor in the Layout Model editor, or a polygon in the Layout Model editor or Parameter Form editor.
Action:	Complete the unfinished object before continuing.


REP-3153Insufficient resources to create window.
REP-3153:  Insufficient resources to create window.

Cause:	There were insufficient resources available to create the requested window.
Action:	Make more resources available by closing windows or other applications.


REP-3154Insufficient resources to create document.
REP-3154:  Insufficient resources to create document.

Cause:	There were insufficient resources available to create the requested module (report, external query, PL/SQL library.  You probably selected File [image] New, File [image] Open, or File [image] Revert.
Action:	Make more resources available by closing windows or other applications.


REP-3200Concurrent previewer actions not allowed.
REP-3200:  Concurrent previewer actions not allowed.

Cause:	You are attempting to activate more than one button at one time, in either the same or multiple Previewers.  For example, you may be trying to both play a sound and display a video at the same time.  This is not allowed.
Action:	Only activate one button at a time.


REP-3300:  Fatal error<additional messages>.

This is an abnormal condition. For information, see  Abnormal Conditions.

Tip 1: Make sure that your ORACLE_HOME\REPORTS60\ TMP directory has enough space to create the file and that you have write permissions for that directory.

Tip 2: Determine which printer driver your system is using. Try a different driver to see if this eliminates the problem.

Cause:	You have done a server migration and tried to run old reports through the new server.
Action:	Using the Installer, install all old Oracle Server .DLLs to your oracle_home/bin directory where Reports, Oracle Server, and Oracle Database are in the same oracle_home directory.
Cause:	You have tried to run a report requiring fonts that are not installed.
Action:	Download and install required fonts.


REP-3301Error occurred<additional messages>.
REP-3301:  Error occurred<additional messages>.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3302:  Fatal error occurred during Quit.  Exiting Report Builder.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3335Unhandled Internal CA Error.
REP-3335:  Unhandled Internal CA Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3350Unhandled Internal UI Error.
REP-3350:  Unhandled Internal UI Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3351Undefined failure in UI.
REP-3351:  Undefined failure in UI.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3352Unexpected error in UI.
REP-3352:  Unexpected error in UI.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3353Attempt to create with an attribute that is not creatable.
REP-3353:  Attempt to create with an attribute that is not creatable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3354Attempt to set with an attribute which is not settable.
REP-3354:  Attempt to set with an attribute which is not settable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3355Attempt to set with an attribute which is not gettable.
REP-3355:  Attempt to set with an attribute which is not gettable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3356Attempt to set/get an unknown attributes.
REP-3356:  Attempt to set/get an unknown attributes.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3357Attempt to set attributes value which are conflicting.
REP-3357:  Attempt to set attributes value which are conflicting.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3358Attempt to set an attribute to an out of range value.
REP-3358:  Attempt to set an attribute to an out of range value.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3359This function call is out of context.
REP-3359:  This function call is out of context.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3360The view class does not support being a scrollee.
REP-3360:  The view class does not support being a scrollee.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3361This function call provokes an illegal recursion.
REP-3361:  This function call provokes an illegal recursion.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3362The internal api memory allocator failed.
REP-3362:  The internal api memory allocator failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3363The client supplied memory allocation functions failed.
REP-3363:  The client supplied memory allocation functions failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3364Attempt to use an unsupported function.
REP-3364:  Attempt to use an unsupported function.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3365An attempt to set attributes out of context.
REP-3365:  An attempt to set attributes out of context.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3366An attempt to perform an illegal operation on a root view.
REP-3366:  An attempt to perform an illegal operation on a root view.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3367One of the parameters to the functions is out of range.
REP-3367:  One of the parameters to the functions is out of range.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3368The connection to the windowing system failed.
REP-3368:  The connection to the windowing system failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3369The connection to the windowing system has been broken.
REP-3369:  The connection to the windowing system has been broken.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3370The windowing system failed.
REP-3370:  The windowing system failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3371uiER_CL_FORMAT_UNAVAILABLE
REP-3371:  uiER_CL_FORMAT_UNAVAILABLE

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3372uiER_CL_FORMAT_UNREGISTERED
REP-3372:  uiER_CL_FORMAT_UNREGISTERED

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3373Operation was timed out.
REP-3373:  Operation was timed out.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3374uiER_NOT_FOUND
REP-3374:  uiER_NOT_FOUND

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3375uiER_ILLEGAL_TOPITEM
REP-3375:  uiER_ILLEGAL_TOPITEM

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3376uiER_SE_BAD_FORMAT
REP-3376:  uiER_SE_BAD_FORMAT

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3377The view class does not support the scroller interface.
REP-3377:  The view class does not support the scroller interface.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3378Attempt to remove a readshare color from a palette.
REP-3378:  Attempt to remove a readshare color from a palette.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3379Unable to create window.
REP-3379:  Unable to create window.

Cause:	Report Builder was unable to create a window.  It could be that you have too many reports or windows open, and lack of memory resources.
Action:	Close some reports and windows.


REP-3380Unable to create view.
REP-3380:  Unable to create view.

Cause:	Report Builder was unable to create a view.  It could be that you have too many reports or windows open, and lack of memory resources.
Action:	Close some reports and windows.


REP-3381Unable to create color palette.
REP-3381:  Unable to create color palette.

Cause:	Report Builder was unable to create a color palette.  It could be that you have too many reports or windows open, and lack of memory resources.
Action:	Close some reports and windows.


REP-3400Error initializing DE.  Checking DE resources is recommended.
REP-3400:  Error initializing DE.  Checking DE resources is recommended.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3420Internal error in Report Builder.
REP-3420:  Internal error in Report Builder.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3430Unhandled Internal HH Error.
REP-3430:  Unhandled Internal HH Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3431Invalid attribute value.
REP-3431:  Invalid attribute value.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3432Invalid context.
REP-3432:  Invalid context.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3433Specified word not found.
REP-3433:  Specified word not found.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3434Link to external document.
REP-3434:  Link to external document.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3435Help session is null.
REP-3435:  Help session is null.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3436Document is not a help document.
REP-3436:  Document is not a help document.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3437Document revision is newer than help.
REP-3437:  Document revision is newer than help.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3438Specified attribute is not settable.
REP-3438:  Specified attribute is not settable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3439Specified attribute is not gettable.
REP-3439:  Specified attribute is not gettable.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3440Invalid link.
REP-3440:  Invalid link.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3441Logical attributes missing or bad.
REP-3441:  Logical attributes missing or bad.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3442NLS language string missing or bad.
REP-3442:  NLS language string missing or bad.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3443No search string specified.
REP-3443:  No search string specified.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3444String begins with percent sign.
REP-3444:  String begins with percent sign.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3445Unknown toolkit error.
REP-3445:  Unknown toolkit error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3446Unknown object store error.
REP-3446:  Unknown object store error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3447Out of memory.
REP-3447:  Out of memory.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3448Unknown Resource manager error.
REP-3448:  Unknown Resource manager error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3480Unhandled Internal REM Error.
REP-3480:  Unhandled Internal REM Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3485Unhandled Internal VGS Error.
REP-3485:  Unhandled Internal VGS Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3500Unhandled Internal UT Error.
REP-3500:  Unhandled Internal UT Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3510Unhandled Internal ZOM Error.
REP-3510:  Unhandled Internal ZOM Error.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3600Both document nodes and non-document nodes selected. Please select only nodes from one of these types of nodes.
REP-3600:  Both document nodes and non-document nodes selected. Please select only nodes from one of these types of nodes.

Cause:	You have chosen Navigator [image] Delete but both object nodes and document nodes are selected.  You cannot close documents and delete objects in the same action.
Action:	If you wish to delete objects, deselect all document nodes.  If you wish to close documents, deselect all object nodes.  Then select Navigator [image] Delete again.


REP-3601This report style can only have one section.
REP-3601:  This report style can only have one section.

Cause:	Tabular, Form Letter and Mailing Label report styles can only have one Section each.
Action:	You must specify all overrides in the existing Section.


REP 3602.  Can not delete the minimum number of levels.

Cause:	Tabular, Form Letter, and Mailing Label report styles have one Section each.  Group above and Group left have two sections each.  Matrix and Matrix group have one section under each normal, across, down, cell.
Action:	For information, see  Abnormal Conditions.


REP-3700 Selection Observer initialization failed.
REP-3700:  Selection Observer initialization failed.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-3701 Selection Observer failed while shutting down.
REP-3701:  Selection Observer failed while shutting down.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-4001Error occurred in the OLE subsystem.
REP-4001:  Error occurred in the OLE subsystem.

Cause:	An unspecified OLE2 error occurred during initialization.  Refer to the accompanying OLE error message for more information.  Other possible causes of this error include the following:
	Case 1:	Your OLE2 server is not functioning correctly.
	Case 2:	An error occurred during installation of Report Builder and the OLE2 functionality did not install correctly.
	Case 3:	This is an abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Refer to the OLE2 server documentation for more information.
	If Case 2:	Reinstall Report Builder.
	If Case 3:	For information, see  Abnormal Conditions.


REP-4002Error occurred while initializing OLE subsystem.
REP-4002:  Error occurred while initializing OLE subsystem.

Cause:	An error occurred during initialization of OLE2 libraries.  Refer to the accompanying OLE error message for more information.  Other possible causes of this error include the following:
	Case 1:	Your OLE2 server is not functioning correctly.
	Case 2:	An error occurred during installation of Report Builder and the OLE2 functionality did not install correctly.
	Case 3:	This is an abnormal condition.
Action:	You can take the following actions to correct this error:
	If Case 1:	Refer to the OLE2 server documentation for more information.
	If Case 2:	Reinstall Report Builder.
	If Case 3:	For information, see  Abnormal Conditions.


REP-4003Error occurred while creating OLE object.
REP-4003:  Error occurred while creating OLE object.

Cause:	You were attempting to create an OLE2 object when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4004Error occurred while restoring OLE object.
REP-4004:  Error occurred while restoring OLE object.

Cause:	You were attempting to restore an OLE2 object when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4005Error occurred while saving OLE object.
REP-4005:  Error occurred while saving OLE object.

Cause:	You were attempting to save an OLE2 object when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4006Error occurred while performing Cut/Copy operation. OLE object is not placed in the clipboard.
REP-4006:  Error occurred while performing Cut/Copy operation. OLE object is not placed in the clipboard.

Cause:	You were trying to cut or copy an OLE2 object when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4007Error occurred while pasting OLE object from clipboard.
REP-4007:  Error occurred while pasting OLE object from clipboard.

Cause:	You were trying to paste an OLE2 object from the clipboard when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4008Error occurred while trying to perform operation defined by OLE object.
REP-4008:  Error occurred while trying to perform operation defined by OLE object.

Cause:	You were trying to perform an action normally supported by the OLE2 server when an OLE error occurred.
Action:	Refer to the accompanying OLE error message for more information.


REP-4009Error occurred while trying to activate OLE object.
REP-4009:  Error occurred while trying to activate OLE object.

Cause:	You were trying to activate an OLE2 object (e.g., double-click on it in the Previewer) when an OLE error occurred.
Action:	Refer to the accompanying OLE2 error message for more information.


REP-4020Conversion of OLE object to a different type failed.
REP-4020:  Conversion of OLE object to a different type failed.

Cause:	You were trying to convert an OLE2 object contained in a piece of boilerplate to an OLE2 object of a different type when an OLE error occurred.  This indicates a problem with the OLE2 server.
Action:	Check that the object is correctly installed and reinstall, if necessary.


REP-4021Microsoft Object Linking and Embedding is not supported on this platform.
REP-4021:  Microsoft Object Linking and Embedding is not supported on this platform.

Cause:	You are running a report that was created on a platform supporting OLE2, and created with OLE2 objects, but you are now running it on a platform that does not support OLE2.   You are trying to access the visual representation of what was once an OLE2 object.
Action:	No action is necessary.  Remove the object if desired.


REP-4022Wrong version of OLE libraries. OLE functionality will be disabled.
REP-4022:  Wrong version of OLE libraries. OLE functionality will be disabled.

Cause:	The OLE2 libraries installed on your machine are incompatible with those supported by your version of Report Builder.  As Report Builder cannot guarantee that your OLE2 support will function, it is disabling OLE2 functionality.
Action:	Install the correct libraries.


REP-4023There is insufficient memory available to complete operation.
REP-4023:  There is insufficient memory available to complete operation.

Cause:	There is not sufficient memory remaining on your system to perform the desired action.
Action:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.


REP-4024DOS SHARE services required for successful operation. SHARE is not running.
REP-4024:  DOS SHARE services required for successful operation. SHARE is not running.

Cause:	The DOS SHARE utility is required, but SHARE is not running.
Action:	Make sure SHARE is running


REP-4025Read failure.
REP-4025:  Read failure.

Cause:	Data cannot be read from the specified device.
Action:	Check the device to determine if it is malfunctioning, and, if so, consult the device documentation to determine the proper error recovery procedures.


REP-4026Write failure.
REP-4026:  Write failure.

Cause:	Data cannot be written to the specified device.
Action:	Check the device to determine if it is read-only.  If not, consult the device documentation to determine the proper error recovery procedures.


REP-4027Too many files opened. There are insufficient resources to open another file.
REP-4027:  Too many files opened. There are insufficient resources to open another file.

Cause:	You are attempting to open more files than are supported by Windows.
Action:	Close some applications.  Also, check your config.sys file and ensure that FILES is not set below 20.  Note:  Remember that OLE2 boilerplate objects reserve either two or three file handles per object and so you may have more files open than you are aware.


REP-4028No space left on device.
REP-4028:  No space left on device.

Cause:	The specified device is full.
Action:	Delete unnecessary data or write to a different device.


REP-4029Failed to obtain presentation of the OLE object. Cannot render OLE object.
REP-4029:  Failed to obtain presentation of the OLE object. Cannot render OLE object.

Cause:	You tried to display an OLE2 object in a report but the display aspects defined by the OLE2 server were unavailable.
Action:	Verify that the OLE2 object has not been corrupted and that the server is correctly installed.  Reinstall if necessary.


REP-4030Failed to restore original display aspects of the OLE object. Object content will be used.
REP-4030:  Failed to restore original display aspects of the OLE object. Object content will be used.

Cause:	You tried to display an OLE2 object in a report but the display aspects defined by the OLE2 server were corrupted or stored in the database and could not be restored.  Report Builder will display the object using the default aspect.
Action:	Verify that the OLE2 server is correctly installed.  Reinstall if necessary.


REP-4031The server application cannot be found. Make sure the application is properly installed and registered correctly.
REP-4031:  The server application cannot be found. Make sure the application is properly installed and registered correctly.

Cause:	You are attempting to access an OLE2 server via an OLE2 object, but the server is currently inaccessible.  The server may have been deleted, renamed, or manually reinstalled in a different location.
Action:	Check the installation of the server and reinstall if necessary.


REP-4032Cannot connect to the linked OLE object source. Make sure that link source has not been moved, renamed, or deleted.
REP-4032:  Cannot connect to the linked OLE object source. Make sure that link source has not been moved, renamed, or deleted.

Cause:	Report Builder is trying to connect to the specified source of the OLE2 object boilerplate but cannot.
Action:	Verify that the OLE2 object source has not been moved or deleted, and that its filename has not been changed


REP-4033Cannot connect to the linked object source, because it is across a network that is not connected to this machine.
REP-4033:  Cannot connect to the linked object source, because it is across a network that is not connected to this machine.

Cause:	You are trying to link to an OLE2 object that is stored on a device to which you do not currently have an established network connection.
Action:	Establish a connection to the proper device.


REP-4034File not found or invalid filename is used by OLE object.
REP-4034:  File not found or invalid filename is used by OLE object.

Cause:	An OLE2 object is trying to access a file that it cannot find.
Action:	Verify that the file has not been corrupted, moved, or renamed.


REP-4035A share violation has occurred while performing operation on OLE object.
REP-4035:  A share violation has occurred while performing operation on OLE object.

Cause:	Possible causes:  you are trying to link to the same file via multiple OLE2 objects, or trying to access the same temporary file via different applications.
Action:	Make sure that you do not have multiple OLE2 objects attempting to access the same file at the same time.  Also, check the installation of your OLE2 server.


REP-4036Access denied while performing operation on OLE object.
REP-4036:  Access denied while performing operation on OLE object.

Cause:	You are trying to update an OLE2 object to which you do not have write access.
Action:	Obtain the proper permissions to the file before trying to update it.


REP-4037File operation on OLE object failed because disk is write-protected.
REP-4037:  File operation on OLE object failed because disk is write-protected.

Cause:	You tried to save to file an OLE2 object but could not because the disk is write-protected.
Action:	Save the object to a disk for which you have write privileges, if possible.  If not, no action is necessary.


REP-4038Unexpected error occurred in the file system while performing operation on OLE object.
REP-4038:  Unexpected error occurred in the file system while performing operation on OLE object.

Cause:	A non-specific file error such as a corruption of the hard disk occurred.
Action:	Refer to your operating system documentation more information.


REP-4039Unexpected error returned by OLE.
REP-4039:  Unexpected error returned by OLE.

Cause:	A non-specific OLE error occurred.
Action:	Refer to your Microsoft documentation for more information.


REP-4040Incorrect or corrupted OLE object persistent data. OLE object cannot be restored from this data.
REP-4040:  Incorrect or corrupted OLE object persistent data. OLE object cannot be restored from this data.

Cause:	The information used by the OLE server to restore the OLE2 object in your report is incorrect or has been corrupted.  Possible causes for this error include:
	Case 1:	If boilerplate, the file has become corrupted.
	Case 2:	If field, either the database has been corrupted, or the LONG RAW column referenced does not contain OLE2 objects.
Action:	You can take the following actions to correct this error:
	If Case 1:	Verify that the object is viable by embedding it in a container using another application.
	If Case 2:	Use SQLPlus to check the table in the database and verify the contents of the column.


REP-4041No operations defined on this object or object is static.
REP-4041:  No operations defined on this object or object is static.

Cause:	You tried to take some action on an OLE2 object but no actions have been defined as applying to the object.  Possibly the object was converted to a static bitmap.
Action:	No action necessary.


REP-4042Requested action on OLE object is valid, but cannot be performed at this moment. Object server may be busy.
REP-4042:  Requested action on OLE object is valid, but cannot be performed at this moment. Object server may be busy.

Cause:	You tried to take a valid action on an OLE2 object but cannot, due to lack of server resources.  A possible cause is that you are trying to open a second instance of a single-instance application.
Action:	Check system resources (memory, etc.) and increase where possible, or try the operation later.


REP-4043Operation requested on object is invalid and cannot be performed. Make sure the application is properly installed.
REP-4043:  Operation requested on object is invalid and cannot be performed. Make sure the application is properly installed.

Cause:	The action you tried to take on an OLE2 object is not recognized as valid.
Action:	Make sure the proper version of the OLE server is correctly installed.  Re-install if necessary.


REP-4044Cannot access system registry. Make sure you have enough free system resources and registry is not corrupted.
REP-4044:  Cannot access system registry. Make sure you have enough free system resources and registry is not corrupted.

Cause:	A read or write operation in the system registry failed.
Action:	Consult your Microsoft documentation.


REP-4045Problem occurred in the system registry. Make sure the object server is properly installed.
REP-4045:  Problem occurred in the system registry. Make sure the object server is properly installed.

Cause:	Some information about the server is missing from the registry.
Action:	Make sure the OLE server is installed correctly.  Re-install if necessary.


REP-4200Error occurred in the Mail subsystem.
REP-4200:  Error occurred in the Mail subsystem.

Cause:	An unspecified error occurred during one of the mail operations.  Refer to the accompanying error message for more information.  Other possible causes of this error include the following:
	Case 1:	MAPI is not properly installed.
	Case 2:	Your Windows mail service provider is not properly installed.
Action:	You can take the following actions to correct this error:
	If Case 1:	If you have other applications using MAPI, check to see if they are functioning properly.  If not, try reinstalling MAPI.
	If Case 2:	Make sure that your Windows mail service provider is installed, and you have an account on the system.  If you need assistance, ask your Mail administrator.


REP-4201Error occurred while initializing the Mail subsystem.
REP-4201:  Error occurred while initializing the Mail subsystem.

Cause:	Report Builder tried to initialize MAPI, and could not. Refer to the accompanying error message for more information. Other possible causes of this error include the following:
	Case 1:	MAPI is not installed, the MAPI DLL is out of date, or the Mail entry in your WIN.INI file or system registry points to the wrong location.
	Case 2:	There is not enough memory available to perform the operation.
	Case 3:	While logging on, you entered an invalid service profile name, username, or password.
Action:	You can take the following actions to correct this error:
	If Case 1:	Reinstall MAPI, or correct the Mail entry in your WIN.INI file or system registry.
	If Case 2:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.
	If Case 3:	Make sure your logon information is correct, and try again.  If that does not work, confirm your account information with your Mail administrator.


REP-4202Error occurred while logging on to the Mail subsystem.
REP-4202:  Error occurred while logging on to the Mail subsystem.

Cause:	You attempted to log on to the Mail subsystem and an error occurred. Refer to the accompanying error message for more information. Other possible causes of this error include the following:
	Case 1:	You entered an invalid service profile name, username, or password.
	Case 2:	There is not enough memory available.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure your logon information is correct, and try again.  If that does not work, confirm your account information with your Mail administrator.
	If Case 2:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.


REP-4203Error occurred while sending a mail message.
REP-4203:  Error occurred while sending a mail message.

Cause:	An error occurred while you were composing or sending a mail message. Refer to the accompanying error message for more information. Other possible causes of this error include the following:
	Case 1:	There is not enough free space on your disk.
	Case 2:	There is not enough memory available.
Action:	You can take the following actions to correct this error:
	If Case 1:	Free up some space on your disk.
	If Case 2:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.


REP-4204Error occurred while trying to validate recipient's name/address.
REP-4204:  Error occurred while trying to validate recipient’s name/address.

Cause:	Report Builder tried to validate the destination mail address, and an error occurred.
Action:	Confirm that the recipient has a valid mail account, or  ask your Mail administrator for assistance.  Refer to the accompanying error message for more information.


REP-4220There is a problem with the Mail subsystem.
REP-4220:  There is a problem with the Mail subsystem.

Cause:	An unspecified error occurred during one of the mail operations.
Action:	Try to free up some disk space or exit any unnecessary applications that are running.  If you have other applications using MAPI, check to see if they are functioning properly.  If not, try reinstalling MAPI.


REP-4221Cannot access attachment file.
REP-4221:  Cannot access attachment file.

Cause:	An error occurred while trying to access the attachment file.  Possible causes of this error include the following:
	Case 1:	The attachment file was not found.
	Case 2:	The attachment file could not be opened, or there was an error reading or writing it.
Action:	You can take the following actions to correct this error:
	If Case 1:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.
	If Case 2:	Free up some space on your disk.


REP-4222There is insufficient memory to complete the operation.
REP-4222:  There is insufficient memory to complete the operation.

Cause:	The mail operation cannot be completed, because there is not enough memory available.
Action:	Exit any unnecessary applications that are running.  If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage.


REP-4223No space left on device,
REP-4223:  No space left on device.

Cause:	The mail operation cannot be completed because there is not enough free space available on your disk.
Action:	Free up some space on your disk.


REP-4224Incorrect user name, password, or service profile name.
REP-4224:  Incorrect user name, password, or service profile name.

Cause:	The logon information you entered is invalid.
Action:	Make sure your logon information is correct, and try again.  If that does not work, confirm your account information with your Mail administrator.


REP-4225The operation cannot be completed because user is not logged on.
REP-4225:  The operation cannot be completed because user is not logged on.

Cause:	The mail operation could not be completed.
Action:	Log on to the Mail subsystem, and try again.


REP-4226Password is required.
REP-4226:  Password is required.

Cause:	You attempted to log on to the Mail subsystem without specifying a password.
Action:	Specify a valid password, and try again.  If that does not work, contact your Mail administrator.


REP-4227Invalid service configuration.
REP-4227:  Invalid service configuration.

Cause:	The Mail subsystem is incorrectly configured.
Action:	Contact your Mail administrator.


REP-4228:  MAPI does not support the service requested by Report Builder.

Cause:	The given implementation of MAPI has limited functionality.
Action:	You may need to upgrade your Windows mail service provider.  Contact your Mail administrator.


REP-4229The character set requested is not supported.
REP-4229:  The character set requested is not supported.

Cause:	Your default character set is not supported by MAPI.
Action:	Contact your Mail administrator.


REP-4230The size of the text string passed is too large.
REP-4230:  The size of the text string passed is too large.

Cause:	You passed a text string that is too large for the given implementation of MAPI.
Action:	Shorten the string, and try again.


REP-4232Too many files opened.
REP-4232:  Too many files opened.

Cause:	The given implementation of MAPI does not support the number of files open.
Action:	Close all unnecessary documents.


REP-05000:  The notification template file is not set for successful jobs.

Cause:	There is no SUCCNOTEFILE parameter in the Reports Server configuration file for the notification template file for successful job notification.
Action:	Add the SUCCNOTEFILE parameter to the Reports Server configuration file pointing it to the notification template file for successful jobs. See your system administrator for more information.


REP-05001:  The notification template file is not set for failed jobs.

Cause:	There is no FAILNOTEFILE parameter in the Reports Server configuration file for the notification template file for failed job notification.
Action:	Add the FAILNOTEFILE parameter to the Reports Server configuration file pointing it to the notification template file for failed jobs.  See your system administrator for more information.


REP-05002:  Cannot find notification template file.

Cause:	The file specified by SUCCNOTEFILE or FAILNOTEFILE in the Reports Server configuration file does not exist.
Action:	Ensure that the SUCCNOTEFILE or FAILNOTEFILE points to a valid notification template file name.  See your system administrator for more information.  See your system administrator for more information.


REP-05003: Cannot open notification template file.

Cause:	The notification template file specified by SUCCNOTEFILE or FAILNOTEFILE in the Reports Server configuration file cannot be opened.
Action:	Ensure that the SUCCNOTEFILE or FAILNOTEFILE points to a valid notification template file name.  Ensure that the notification template file is readable.  See your system administrator for more information.


REP-05004:  Cannot read notification template file.

Cause:	The notification template file specified by SUCCNOTEFILE or FAILNOTEFILE in the Reports Server configuration file cannot be read.
Action:	Ensure that the SUCCNOTEFILE or FAILNOTEFILE points to a valid notification template file name.  Ensure that the notification template file is readable.  See your system administrator for more information.


REP-06000:  Could not create a query for the Express Query dialog.

Cause:	The query is so large that it is requiring too much memory.
Action:	Simplify the query.


REP-06001:  Failed to invoke the Express Query Dialog.

Cause:	The query is so large that it is requiring too much memory.
Action:	Simplify the query.


REP-06002:  Insufficient memory to complete the operation.

Cause:	The machine has run out of memory.
Action:	Increase the amount of memory by closing applications. A longer term solution is to increase the size of the swap file or to install more memory in the machine.


REP-06003:  Failed to start an Express server session.

Cause:	Express Server is not running or SNAPI is not installed.
Action:	Start Express Server if it is not running and ensure that SNAPI is installed. Contact the Express Server database administrator for assistance.


REP-06004:  Failed to connect to the Express server.

Cause:	Express Server is not running, the system is out of memory, or SNAPI is not installed or is working incorrectly.
Action:	Start Express Server if it is not running. Increase the amount of memory by closing applications. A longer term solution is to increase the size of the swap file or to install more memory in the machine. Ensure that SNAPI is installed. Contact the Express Server database administrator for assistance.


REP-06005:  The Express Query Dialog failed to initialize based on the supplied SNAPI handle.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06006:  Express initialization file XPDATA.INI does not exist.

Cause:	XPDATA.INI could not be found.
Action:	Ensure that the XPDATA.INI exists and that the path is correct.


REP-06007:  Express connection file (XCF) entry not found in [Install] section of Express initialization file XPDATA.INI.

Cause:	An entry is missing from XPDATA.INI
Action:	Add an XCF entry to the XPDATA.INI file, or replace the .INI file with a valid XPDATA.INI.


REP-06008:  ORACLE_HOME not found.

Cause:	The ORACLE_HOME directory could not be found.
Action:	Ensure that your ORACLE_HOME setting is correct. See your Express Server installation instructions for information


REP-06009:  Oracle SNAPI (OSN) entry not found in [Install] section of Express initialization file XPDATA.INI.

Cause:	An entry is missing from XPDATA.INI.
Action:	Add an OSN entry to XPDATA.INI, or replace the .INI file with a valid XPDATA.INI.


REP-06010:  The Express server description can not be found in any Express connection files (XCFs).

Cause:	The XCF files are missing some information.
Action:	Check or recreate the e XCF files.


REP-06011:  The size of generated SQL select statement is greater than 64K.

Cause:	The SQL statement is too large.
Action:	Modify your query to reduce the size of the SQL statement.


REP-06012:  Failed to remove the temporary Express query.

Cause:	A temporary query cannot be removed.
Action:	Disconnect from Express, reconnect, and resubmit or re-create the query


REP-06013:  Failed to run a query. The Express Query Dialog was invoked with a set of measures/dimensions from a previous query.

Cause:	The measures or dimensions are not valid or the query is corrupted.
Action:	Verify that the database is available and re-examine the measures and dimensions in the query.


REP-06014:  Backend XPFetch[N]() called with an undefined report id.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06015:  Backend XPPrepare() invoked with a duplicate report id.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06016:  Error trying to get the next data cell from SNAPI.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06017:  The saved query contains incorrect or missing information.

Cause:	The query is not valid.
Action:	Respecify the query.


REP-06018:  Failed to attach the internal Express system databases.

Cause:	The Express system databases cannot be attached.
Action:	Verify that Express Server is running, that the system databases are in place, and that the ExpressServerDBPath setting is correct.


REP-06019:  Failed to attach the Express database specified in the saved query.

Cause:	The Express system databases cannot be attached.
Action:	Verify that Express Server is running, that the database is in place, and that the ExpressServerDBPath setting is correct.


REP-06020:  Failed to parse the Express Query.

Cause:	The Select statement is damaged.
Action:	Respecify the query.


REP-06021:  Oracle Express support not installed.

Cause:	The support files for running with Express are not installed.
Action:	Install the Express support files. See your installation documentation for information.


REP-06022:  Failed to start the Express Server.

Cause:	Express Server is not running.
Action:	Start Express Server if it is not running. Contact the Express Server database administrator for assistance.


REP-06023:  Unexpected end of line while parsing the Express query.

Cause:	An Express error has occurred.
Action:	Check the Express query for a missing backslash at the end of the line.


REP-06024:  Express execute failed.

Cause:	An Express error has occurred.
Action:	Start Express Server if it is not running. Contact the Express Server database administrator for assistance.


REP-06025:  Express fetch failed.

Cause:	An Express error has occurred.
Action:	Start Express Server if it is not running. Contact the Express Server database administrator for assistance.


REP-06026:  Duplicate Report ID detected.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06027:  Undefined Report ID detected.

Cause:	An internal error occurred.
Action:	Restart the product and resubmit the query.


REP-06028:  Unknown Express support back-end error.

Cause:	An Express error has occurred.
Action:	Start Express Server if it is not running. Contact the Express Server database administrator for assistance.


REP-6029:  Express error

Cause:	An Express error has occurred.
Action:	See your Express documentation for more information.


REP-6030: Missing or invalid xconnect.ini.

Cause:	This is probably due to missing xconnect.ini.  If the xconnect.ini has an invalid [General] section, this error will also be raised.
Action:	Check in Oracle_Home/olap/ecf620 for xconnect.ini. Make sure xconnect.ini has a [General] section.


REP-6101: Failed to start the Java Virtual Machine. Please check the Java Runtime Environment setup.

Cause:	This is usually caused by incorrect value of REPORTS60_CLASSPATH environment variable or invalid setup of Java Runtime Environment.
Action:	Please verify the installation of Java Runtime Environment. Please make sure that REPORTS60_CLASSPATH environment variable contains valid specification of either classes.zip or rt.jar depending on your platform. If necessary, reinstall Reports Runtime or Report Builder to refresh the Java Runtime Environment and REPORTS60_CLASSPATH environment variable setup.


REP-6102: Failed to start the XML parser.

Cause:	Could not start Oracle XML parser due to incorrect setup. This is usually caused by incorrect value of REPORTS60_CLASSPATH
Action:	Please make sure REPORTS60_CLASSPATH contains a valid specification of the Oracle XML parser and the product's .jar files. If necessary, reinstall Reports Runtime or Report Builder to refresh the REPORTS60_CLASSPATH environment variable setup.


REP-6103: Error with the Java Runtime Environment setup.

Cause:	Incorrect or missing setup of Java Runtime Environment.
Action:	Please reinstall Reports Runtime or Report Builder.


REP-6104: Invalid XML report definition.

Cause:	Invalid or missing XML report definition.
Action:	Please specify a valid XML report definition or correct the problem indicated in the report definition.


REP-6106: Error in the XML report definition at line <line number> in <url>

Cause:	There is a problem with the specified XML report definition at the line number.
Action:	lease correct the reported error for the XML report definition at the specified line number.


REP 16500.  This program can only be invoked as a CGI executable.
REP-16500.  This program can only be invoked as a CGI executable.

Cause:	Web CGI executable was invoked outside Web Server context.
Action:	CGI executable must be invoked by a web server to work properly.


REP 16501.  Reports Web Agent key map file not set up properly.
REP-16501.  Reports Web Agent key map file not set up properly.

Cause:	Key map file cannot be found at location specified.
Action:	Check file location.


REP 16504:  Cannot initialize message subsytem.  Make sure message file installed properly.

Cause:	Message file cannot be found/opened..
Action:	Check your installation.


REP 16505.  General error during initialization.  Check your installation.
REP-16505.  General error during initialization.  Check your installation.

Cause:	General error.
Action:	Check your installation and availability of system resources.


REP 16506.  Your URL contains badly-formed escapes.
REP-16506.  Your URL contains badly-formed escapes.

Cause:	Submitted URL is badly formed.
Action:	See URL rules in Web Agent documentation.


REP 16507.  Key is unrecognized.
REP-16507.  Key is unrecognized.

Cause:	Key map configuration is active, but specified key in the URL is unrecognized - cannot build command line.
Action:	Check your key value and keymap file setup/contents.


REP 16508.  Key \"%s\" is unrecognized.  Possible causes:  bad URL syntax; key in URL was not found in the key map file.
REP-16508.  Key \"%s\" is unrecognized.  Possible causes:  bad URL syntax; key in URL was not found in the key map file.

Cause:	Key map configuration is active, but specified key in the URL is unrecognized - cannot build command line.
Action:	Check your key value and keymap file setup/contents.


REP 16509.  Syntax errors in key map file.  Please check a definition of submitted key.
REP-16509.  Syntax errors in key map file.  Please check a definition of submitted key.

Cause:	Syntax errors in the key map file.
Action:	Check key map file contents (see Web Agent documentation for rules).


REP 16510.  Incorrect usage.
REP-16510.  Incorrect usage.

Cause:	Generic error for non-verbose run.
Action:	Enable verbocity and check the real message.


REP 16511.  Your URL contains too many parameters.
REP-16511.  Your URL contains too many parameters.

Cause:	URL contains too many parameters (too long).
Action:	Use shorter URL and/or key map file to shorten URL.


REP 16512.  Out of memory.
REP-16512.  Out of memory.

Cause:	Not enough memory.
Action:	Make sure enough system resources are available.


REP 16513.  Unable to communicate with the Reports Server.
REP-16513.  Unable to communicate with the Reports Server.

Cause:	Reports Server is not answering.
Action:	Make sure Reports Server is up and TNSNAMES.ORA network setup has a correct entry for it.


REP 16514.  Unable to run the report.
REP-16514.  Unable to run the report.

Cause:	Generic error for report run failure.
Action:	See detailed error message from Reports Server, along with this error message.


REP 16515.  Cannot access the report output.
REP-16515.  Cannot access the report output.

Cause:	Web Agent cannot access Report Server run output.
Action:	Check your Web AGent setup (especially WEBLOC variable).


REP 16516.  The Reports Server is being shut down.
REP-16516.  The Reports Server is being shut down.

Cause:	Warning - Reports Server is going down.
Action:	Try again later.


REP 16517.  ReportJob was cancelled upon user request.
REP-16517.  ReportJob was canceled upon user request.

Cause:	Job was canceled by you or the Reports Server administrator.
Action:	Try again if necessary.


REP 16518.  The Reports Server Engine terminated abnormally.
REP-16518.  The Reports Server Engine terminated abnormally.

Cause:	Reports Server Engine had a problem with your report.
Action:	Contact Reports Server Administrator.


REP 16519.  Report Job has terminated with error.
REP-16519.  Report Job has terminated with error.

Cause:	Generic error message for report run error.
Action:	See the associated detailed message.


REP 16520.  Error occurred while queuing job to the Reports Server.
REP-16520.  Error occurred while queuing job to the Reports Server.

Cause:	Error occurred while queuing job to the Reports Server.
Action:	Try again later.


REP 16521.  Error occurred while parsing the Reports Server command line.
REP-16521.  Error occurred while parsing the Reports Server command line.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator.


REP 16522.  Reports Server name is not specified.
REP-16522.  Reports Server name is not specified.

Cause:	Error occurred while attempting to run report and process command line
Action:	Contact the Reports Server Administrator.


REP 16523.  Report name is not specified.
REP-16523.  Report name is not specified.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator.  Check cmdline for report name.


REP 16524.  Database logon is not specified.
REP-16524.  Database logon is not specified.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator.  Check cmdline for database logon.


REP 16525.  Unable to interpret scheduling command.
REP-16525.  Unable to interpret scheduling command.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator.  Check SCHEDULE parameter.


REP 16526.  Unable to interpret time tolerance.
REP-16526.  Unable to interpret time tolerance.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator. Check TOLERANCE parameter.


REP 16527.  Parameter form type is invalid.
REP-16527.  Parameter form type is invalid.

Cause:	Error occurred while attempting to run report and process command line.
Action:	Contact the Reports Server Administrator. Check PARAMFORM parameter.


REP 16528.  Error occurred while communicating with the Reports Server.
REP-16528.  Error occurred while communicating with the Reports Server.

Cause:	Communication problem.
Action:	Try again later.


REP 16529.  Cannot Kill the Job :
REP-16529.  Cannot Kill the Job :

Cause:	Generic message for kill job.
Action:	Examine the reason why.


REP 16530.  Invalid Job ID.
REP-16530.  Invalid Job ID.

Cause:	Invalid ID of Reports Server job to perform action on.
Action:	Make sure ID is valid.


REP 16531.  Job is already finished.
REP-16531.  Job is already finished.

Cause:	Invalid ID of Reports Server job to perform action on
Action:	Make sure ID is valid.


REP 16532.  Job is not done yet.  Try again later.
REP-16532.  Job is not done yet.  Try again later.

Cause:	Invalid ID of Reports Server job to perform action on.
Action:	Make sure ID is valid.


REP 16533Not enough privileges to perform requested action.
REP-16533.  Not enough privileges to perform requested action.

Cause:	Invalid ID of Reports Server job to perform action on.
Action:	Make sure ID is in proper and you have enough privileges.


REP 16534.  Cannot access the report output.  Check your setup (REPORTS 60_WEBLOC)
REP-16534.  Cannot access the report output.  Check your setup (REPORTS 60_WEBLOC)

Cause:	Output directory is not accessible.
Action:	Check directory specifications.


REP 16535.  or Reports60_WEBLOC_TRANSLATED environment is probably invalid.)
REP-16535:  or REPORTS60_WEBLOC_TRANSLATED environment is probably invalid.)

Cause:	Output directory is not accessible.
Action:	Check directory specifications.


REP 16537.  (REPORTS60_WEBLOC_TRANSLATED environment probably points to the same location as Reports Server cache.)
REP-16537:  (REPORTS60_WEBLOC_TRANSLATED environment probably points to the same location as Reports Server cache.)

Cause:	Output of returned name already exists in the web directory.
Action:	Check your Web Agent setup.


REP 16538.  Report output was successfully printed out.
REP-16538:  Report output was successfully printed out.

Cause:	Successful run of report to printer.
Action:	None.


REP 16539 Report output was successfully mailed.
REP-16539:  Report output was successfully mailed.

Cause:	Successful run of report to mail.
Action:	None.


REP 16540 Report output was successfully written to requested destination.
REP-16540:  Report output was successfully written to requested destination.

Cause:	Successful run of report to requested destype..
Action:	None.


REP-16541 Need to Logon before running the report.
REP-16541:  "Need to Logon before running the report."

Cause:	You did not log in before running the report.
Action:	Log in before running the report.


REP-16542 Report output was successfully written to InterOffice repository.
REP-16542:  Report output was successfully written to InterOffice repository."

Cause:	The report ran successfully to the InterOffice repository.
Action:	None.


REP-16543 REPORTS60_PHYSICAL_MAP and REPORTS60_SHARED_CACHE environment is probably invalid.
REP-16543:  REPORTS60_PHYSICAL_MAP and REPORTS60_SHARED_CACHE environment is probably invalid."

Cause:	The output directory is not accessible.
Action:	Check the directory specification.


REP-20091 Do you wish to save the current module before disconnecting from the database?
REP-20091:  Do you wish to save the current module before disconnecting from the database?

Cause:	You have an open module that is stored in the database.  If you disconnect from the database, you will not be able to save your changes to the database.
Action:	Select Yes to save the module before disconnecting from the database; the module remains open so you can reconnect if desired and save it to the database again.  Select No to disconnect from the database without saving the module; the module remains open.  Select Cancel to remain connected to the database without saving; once again, the module remains open.


REP-20099 Printer changed while previewing. Printer font remapping could cause truncation. Continue with printing?
REP-20099:  Printer changed while previewing. Printer font remapping could cause truncation. Continue with printing?

Cause:	In the time between running the report and selecting Print from the Previewer  your default printer has changed.
Action:	Select Yes to print anyway.  Select No to halt printing, then close your report and either reset your printer and run your report again, or simply run it again to format it for the current printer.


REP-20128Warning:  Report was not run with DESTYPE=PREVIEW. Screen font remapping could cause truncation. Continue with printing?
REP-20128:  Warning:  Report was not run with DESTYPE=PREVIEW. Screen font remapping could cause truncation. Continue with printing?

Cause:	You selected Print from the Previewer, but specified Screen instead of Preview, which formats your report as though using printer fonts and provides a more accurate view of your report's printed output.
Action:	Select Yes to print anyway.  Select No to halt printing.  Then close your report and run it again while specifying Preview to format it for the printer.


REP-20129Warning:  Opening a report saved with a newer version of Report Builder. Functionality may be lost. Continue?

Cause:	You tried to open a report with a version of Report Builder older than the version used to create the report.  If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.
Action:	If you are concerned about losing functionality, do not open the report until you have upgraded to the most recent version of Report Builder.


REP-20135You cannot run without a layout.  Would you like to create a default layout?
REP-20135:  You cannot run without a layout.  Would you like to create a default layout?

Cause:	You attempted to run your report after creating a data model but before creating a layout.
Action:	Create a layout, then run your report.


REP-20136The region you have chosen for your default layout is too small.  Extend region to page boundaries?
REP-20136:  The region you have chosen for your default layout is too small.  Extend region to page boundaries?

Cause:	You used the Additional Default Layout tool from the Tool palette to draw a region for a layout that was not large enough to accommodate the settings specified in the Report Wizard.
Action:	Either select Yes to have Report Builder extend the possible range of the layout to the boundaries of a report page, or select No and change the settings in the Report Wizard to shrink the size of the layout.


REP-20138Report Builder tables may not be installed in the database.
REP-20138:  Report Builder tables may not be installed in the database.

Cause:	Report Builder was not able to access its tables in the database.
Action:	Inform your database administrator that Report Builder tables were not successfully installed in the database.


REP-20139New parameter form layout will not fit its current size. Increase the number of pages to fit?
REP-20139:  New parameter form layout will not fit its current size. Increase the number of pages to fit?

Cause:	The new parameter form is too big to fit on the number of pages specified for the parameter form in the Report Properties dialog.
Action:	Either select Yes to have Report Builder increase the number of pages in the parameter form, or select No and change the settings in the Report Properties dialog to enlarge the parameter form.


REP-20140Warning: This will delete the frame and all the objects it encloses.  Continue?.
REP-20140:  Warning: This will delete the frame and all the objects it encloses.  Continue?


REP-20141Warning: This will destroy the entire matrix.  Continue?
REP-20141:  Warning: This will destroy the entire matrix.  Continue?


REP-20142Warning: The mode of the report has changed to CHARACTER. The report will run in a separate window.
REP-20142:  Warning: The mode of the report has changed to CHARACTER. The report will run in a separate window.


REP-20143Warning:  some objects may be moved off the page, potentially leading to a report that cannot be formatted.
REP-20143:  Warning: some objects may be moved off the page, potentially leading to a report that cannot be formatted.


REP-20144:  Opening a report saved with a newer version of Report Builder.  Functionality may be lost.

Cause:	You tried to open a report with a version of Report Builder older than the version used to create the report.  If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.
Action:	If you are concerned about losing functionality, do not open the report until you have upgraded to the most recent version of Report Builder.


REP-20146:  This action may invalidate references to columns in the referenced object.

Cause:	Collapsing a Database Ref, Database Nested Table, or Database Varray column invalidates any external use of the referenced columns (e.g. in PL/SQL Program Units or in Summary Columns).
Action:	To use the referenced columns, do not collapse the Database Ref, Database Nested Table, or Database Varray columns referencing them.


REP-20147:  Cannot implement column link for this detailed SQL query.  Converting to group link.
REP-20147:  Cannot implement column link for this detail SQL query.  Converting to group link.

Cause:	Data links between any query and an object detail query are not supported .
Action:	If you click Yes, you will create a link between the parent groups of the two queries.  If you click Cancel, you will not create a link, but you can then manually create the link using SQL.in the detail query.


REP-20148:  Warning: Report will run to multiple destinations. Continue?
REP-20148:  Warning: Report will run to multiple desinations. Continue?

Cause:	The report you are running has a Distribution property defined that will send the output to more than one destination.
Action:	If you click Continue, the report will run and the output will be sent to all of the defined destinations.  If you click Cancel, the report will not run.


REP-20150Warning: Page width of report '<report name>' changed to fit the font for a character cell. Might be a consequence of font-mapping in the font aliases file.
REP-20150:  Warning: Page width of report '<report name>' changed to fit the font for a character cell. Might be a consequence of font-mapping in the font aliases file.

Cause:	A character font has been substituted for a bitmapped font in the report you opened, and the page width has been adjusted accordingly.  A possible cause: a bitmapped report is being opened in the character-mode runtime engine.
Action:	If you want the font mapped to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on your platform) to map the fonts to the desired ones.  Otherwise, no action is necessary.


REP-20151Warning: some fonts have been changed according to the mapping in the font aliases file.
REP-20151:  Warning: some fonts have been changed according to the mapping in the font aliases file.

Cause:	One or more fonts saved with the report have been mapped to different ones, due to a change in platform, display, report destination, or mode.
Action:	If you want the font mapped to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on your platform) to map the fonts to the desired ones.  Otherwise, no action is necessary.


REP-20190Quit will terminate the current report, as well as any other pending reports.
REP-20190:  Quit will terminate the current report, as well as any other pending reports.

Cause:	You have specified that you want to exit Reports Server or Reports Background Engine while one or more reports are still executing or awaiting execution.
Action:	If you want your reports to finish executing, cancel the operation.  Otherwise, accept the warning dialog.


REP-20191Cannot exit Windows when this program is running. Close the report server and exit Windows.
REP-20191:  Cannot exit Windows when this program is running. Close the Reports Background Engine and exit Windows.

Cause:	The Reports Background Engine requires Windows, but you have specified that you want to exit Windows while the Reports Background Engine is still running.
Action:	Exit the Reports Background Engine before exiting Windows.


REP-25204Conversion successful
REP-25204:  Conversion successful

Cause:	The requested conversion ran successfully.
Action:	none.


REP-25206Converting '<source name>' to '<destination name>' failed.
REP-25206:  Converting '<source name>' to '<destination name>' failed.

Cause:	The most likely cause of this error is that the source type you specified was incorrect.
Action:	Ensure that the source file is of the specified source type.


REP-25207Invalid conversion: stype and dtype are not of the same document type.
REP-25207:  Invalid conversion: stype and dtype are not of the same document type.

Cause:	You attempted to convert a document of one type to another type--i.e., you attempted to convert one of the possible report files to a PL/SQL file, or vice versa.
Action:	Ensure that the source and destination of your conversion are the same type of document.


REP-25401Cannot locate '<user exit .DLL file>'.
REP-25401:  Cannot locate '<user exit .DLL file>'.

Cause:	Your report attempted to execute a user exit, but the user exit .DLL file could not be located.  This file typically resides in:
	•	the current directory
	•	the Windows directory (typically \WINDOWS)
	•	the Windows system directory (typically \WINDOWS\SYSTEM)
	•	the directory containing the executable file for the current task
	•	the directories listed in the PATH environment variable
	•	the list of directories mapped in a network
Action:	Locate the specified .DLL file and place it in one of the directories listed above.


REP-25402Internal Error - Cannot locate '<user exit .DLL file>' within '<filename>'.
REP-25402:  Internal Error - Cannot locate '<user exit .DLL file>' within '<filename>'.

Cause:	Your report attempted to execute a user exit, but certain functions used to locate and execute user exits cannot be located in the user exit .DLL file.  This means that the user exit .DLL was built incorrectly, because these functions are located in a .OBJ file shipped with Report Builder, which should always be linked into the user exit .DLL.
Action:	Rebuild the specified user exit .DLL correctly.


REP 31681.  Warning:  Connecting to a different database may invalidate existing data model.
REP-31681:  Warning:  Connecting to a different database may invalidate existing data model.

Cause:	You can only have one connection to a database at a time.  If you proceed to connect to a different database, existing data model may not be valid afterward.
Action:	In order to keep the existing data model valid, do not reconnect to a different database unless you are sure that the queries are compatible with the new database connection.


REP-31700The report definition is incomplete, or the query does not have break groups.  Cannot run the Web Wizard.
REP-31700:  The report definition is incomplete, or the query does not have break groups.  Cannot run the Web Wizard.

Cause:	You must complete the report definition before running the Web Wizard.  To run the Web Wizard, the report definition must contain a Data Model with multiple groups and a valid Layout Model.
Action:	Create at least one query with multiple groups and default the layout using the Report Wizard.


REP-31800Image file <filename> not found.
REP-31800:  Image file <filename> not found.

Cause:	Report Builder could not locate one of its image files.  Possible causes of this error include:
	Case 1:	The image file does not exist.
	Case 2:	The image file is in the wrong place.
	Case 3:	The environment is not configured properly.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that the image file is present.
	If Case 2:	Make sure that the image file is in the proper directory.
	If Case 3:	Make sure that your environment is set correctly.  On Unix, make sure that the proper environment variable is set, and on MS Windows check the file system registry.


REP-31801Cannot find image <filename> specified in template.
REP-31801:  Cannot find image <filename> specified in template.

Cause:	Report Builder could not locate the image corresponding to the chosen template.  Possible causes of this error include:
	Case 1:	The image file does not exist.
	Case 2:	The image file is in the wrong place.
	Case 3:	The environment is not configured properly.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that the image file is present.
	If Case 2:	Make sure that the image file is in the proper directory.
	If Case 3:	Make sure that your environment is set correctly.  On Unix, make sure that the proper environment variable is set, and on MS Windows check the file system registry.


REP-31802You should enter a SQL statement on this page.
REP-31802:  You should enter a SQL statement on this page.

Cause:	In order for the Report Wizard to create your report, a valid SQL text must exist.
Action:	Enter a SQL statement.


REP-31803You need to be connected to a database in order for your SQL text to be checked.
REP-31803:  You need to be connected to a database in order for your SQL text to be checked.

Cause:	The Report Wizard requires a connection to a database in order to check your SQL text.
Action:	You can connect to a database by typing in your login string whenever the Connect dialog is shown.  You will only be prompted to connect to a database when it is required.  If you are having trouble connecting to a database confirm your logon information with your Database Administrator (DBA).


REP-31804Your SQL is OK.
REP-31804:  Your SQL is OK.

Cause:	The Report Wizard has checked your SQL text against the database and has confirmed that it will work.
Action:	No changes are needed to your SQL text.


REP-31805Break level <break level number> has no valid break columns.
REP-31805:  Break level <break level number> has no valid break columns.

Cause:	Each break level must contain at least one valid break column.  A break column cannot be a summary or placeholder column.  Nor can it have a datatype of Raw, Longraw or Long.
Action:	Provide at least one valid break column for the break level or move all columns that are currently in this break level to another level which contains a valid break column.


REP-31806You cannot designate all fields to be break fields.
REP-31806:  You cannot designate all fields to be break fields.

Cause:	You have chosen all your fields to be break fields.  Each break field you have designated groups the data of the fields that are not break fields.  Since you have no non-break fields this situation is invalid.
Action:	Designate at least one field to be a non-break field.  We suggest that you remove all break fields from your highest numbered break level (i.e., from the bottom of your list of break fields).


REP-31807Cannot find template file '<filename>'.
REP-31807:  Cannot find template file '<filename>'.

Cause:	Report Builder could not locate the template file with the given name.  Possible causes of this error include:
	Case 1:	The image file does not exist.
	Case 2:	The image file is in the wrong place.
	Case 3:	The environment is not configured properly.
Action:	You can take the following actions to correct this error:
	If Case 1:	Make sure that the image file is present.
	If Case 2:	Make sure that the image file is in the proper directory.
	If Case 3:	Make sure that your environment is set correctly.  On Unix, make sure that the proper environment variable is set, and on MS Windows check the system registry.


REP-31808You should enter a SQL statement.
REP-31808:  You should enter a SQL statement.

Cause:	You should enter a SQL statement for the Report Wizard to generate a report.
Action:	Use the Report Wizard to enter a SQL statement.


REP-31809You must choose at least one field to display.
REP-31809:  You must choose at least one field to display.

Cause:	No field has been selected to display.
Action:	Select some fields to display.


REP-31810You must choose at least one break group.
REP-31810:  You must choose at least one break group.

Cause:	The current report style needs break groups.
Action:	Create some break groups.


REP-31811You must choose at least one matrix row.
REP-31811:  You must choose at least one matrix row.

Cause:	Nothing has been selected as matrix rows.
Action:	Select some columns as matrix rows.


REP-31812You must choose at least one matrix column.
REP-31812:  You must choose at least one matrix column.

Cause:	Nothing has been selected as matrix columns.
Action:	Select one or more columns as matrix columns.


REP-31813You must choose at least one matrix cell.
REP-31813:  You must choose at least one matrix cell.

Cause:	Nothing has been selected as matrix cells.
Action:	Select one or more columns as matrix cells.


REP-31814You must choose at least one matrix break.
REP-31814:  You must choose at least one matrix break.

Cause:	Nothing has been selected as matrix breaks.
Action:	Select some columns as matrix break groups.


REP-31815You should have one field displayed per group.
REP-31815:  You should have one field displayed per group.

Cause:	Nothing has been selected as matrix breaks.  This problem is due to:
	1) You have chosen this field as a group field.
	2) You have chosen to default the group of this field, and this field is the only one which has been marked as "to be defaulted" in its group
Action:	1) If you have chosen this field as a group field, you can go to the group page to deselect this field.
	2) If you have chosen to default the group of this column, you can go to the group page to deselect that group


REP-31816You should select groups to be defaulted.
REP-31816:  You should select groups to be defaulted.

Cause:	No group has been selected to be defaulted.
Action:	Select groups to be defaulted.


REP-31817At the top of the group. Cannot move up.
REP-31817:  At the top of the group. Cannot move up.

Cause:	This column is at the top of its group.
Action:	Don't try to move this column up.


REP-31818At the bottom of the group. Cannot move down.
REP-31818:  At the bottom of the group. Cannot move down.

Cause:	This column is at the bottom of its group.
Action:	Don't try to move this column up.


REP-31819Cannot reorder report level columns here.
REP-31819:  Cannot reorder report level columns here.

Cause:	Report level columns don't have the POS attribute.
Action:	Set where to display the report level columns in the Layout Model editor.


REP-31820Selected groups have no columns in them.
REP-31820:  Selected groups have no columns in them.

Cause:	Selected groups have no columns in them. Then no report can be generated.
Action:	Select a group containing columns.


REP-31821There is no text specifiedin the text editor.
REP-31821:  There is no text specified in the text editor.

Cause:	The text for a mailing label or form letter report is empty.
Action:	Type some text in the text editor.


REP-31822You should select one group first.
REP-31822:  You should select one group first.

Cause:	No group has been selected.
Action:	Go to the group page and select one group.


REP-31823You should select one and only one group.
REP-31823:  You should select one and only one group.

Cause:	There is more than one group selected.
Action:	Select one and only one group.


REP-31824Select another group since no columns in the selected group.
REP-31824:  Select another group since no columns in the selected group.

Cause:	There are no columns in the selected group.
Action:	Select a group containing columns.


REP-31825Cancel the wizard and fix the problem in report editors.
REP-31825:  Cancel the wizard and fix the problem in report editors.

Cause:	The data model is invalid or the default region is too small.
Action:	Fix the problem in the Data Model editor or the Layout Model editor.


REP 31827.  Invalid print direction or illegal defaulting of page level summary column.
REP-31827:  Invalid print direction or illegal defaulting of page level summary column.

Cause:	The print direction against one or more groups is invalid for the requested default style, or page level summary column was selected to be defaulted (page level summaries are not supported within defaulting).
Action:	Request the user to alter the print direction against the group or the default style, or deselect all page level summaries.


REP-31950Error occurred in the Report Builder charting support.
REP-31950:  Error occurred in the Report Builder charting support.

Cause:	Error occurred initializing the Chart Wizard.
Action:	Make sure all components are installed properly.  Restart the product.


REP-31951Cannot initialize Chart Wizard.  Make sure it is properly installed.
REP-31951:  Cannot initialize Chart Wizard.  Make sure it is properly installed.

Cause:	The Chart Builder library could not be initialized.
Action:	Make sure that the Chart Builder Wizard and runtime executable are properly installed and that there are enough system resources available.


REP-31952Cannot initialize Chart Wizard.  Incorrect version of libraries.
REP-31952:  Cannot initialize Chart Wizard.  Incorrect version of libraries.

Cause:	The Chart Builder library could not be initialized.
Action:	Make sure that the Chart Builder Wizard libraries are properly installed and that there are enough system resources available.


REP-31953Error occurred in the Report Builder Chart Wizard.
REP-31953:  Error occurred in the Report Builder Chart Wizard.

Cause:	The Chart Builder library could not be initialized.
Action:	Make sure that the Chart Builder Wizard libraries are properly installed and that there are enough system resources available.


REP-31954Error occurred in the Report Builder Chart Wizard user interface.
REP-31954:  Error occurred in the Report Builder Chart Wizard user interface.

Cause:	The Chart Wizard failed to load properly.
Action:	Make sure that the Chart Builder Wizard libraries are properly installed and that there are enough system resources available.


REP-31955Error in the chart runtime executable while attempting to create a chart.
REP-31955:  Error in the chart runtime executable while attempting to create a chart.

Cause:	The Chart Builder failed to build the chart.
Action:	Make sure that the Chart Builder Wizard libraries are properly installed and that there are enough system resources available.


REP-31980Incorrect field mapping specified.  The chart will not be generated.
REP-31980:  Incorrect field mapping specified.  The chart will not be generated.

Cause:	You did not specify fields for both category and value axes in the Chart Wizard.
Action:	Reenter the Chart Wizard and specify fields for both Category and Value axes.


REP-31981Report Data Model is empty or invalid - nothing to chart. Create a data model and try again.
REP-31981:  Report Data Model is empty or invalid - nothing to chart. Create a data model and try again.

Cause:	User tried to invoke the Chart Wizard on empty report.
Action:	Create report (at least a data model) and try again.


REP-32600Unexpected error. Aborting.
REP-32600:  Unexpected error. Aborting.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32601Report already exists in NX file.
REP-32601:  Report already exists in NX file.

Cause:	You tried to overwrite an existing translation file.
Action:	Choose a different name for the translation file.


REP-32602:  Cannot initialize Report Builder system.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32603Cannot initialize VGS system.
REP-32603:  Cannot initialize VGS system.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32604Fatal error loading report '<report name>'. Check version.
REP-32604:  Fatal error loading report '<report name>'. Check version.

Cause:	The specified report cannot be loaded.
Action:	Make sure you're opening the correct version of the report.


REP-32605Cannot open report file for reading.
REP-32605:  Cannot open report file for reading.

Cause:	Report file is unreadable.
Action:	Check the read permission of the report file.


REP-32606Cannot open '<translation file>' file for reading.
REP-32606:  Cannot open '<translation file>' file for reading.

Cause:	The specified file cannot be opened.
Action:	Make sure the file exists and is readable.


REP-32607NX Tree does not exist.
REP-32607:  NX Tree does not exist.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32608Translations for that language do not exist.
REP-32608:  Translations for that language do not exist.

Cause:	The Translation Manager cannot translate into the given target language.
Action:	Make sure the target language is supported.


REP-32609: This is not a Report Builder tree.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32610Source data file ('<file name>') does not match.
REP-32610:  Source data file ('<file name>') does not match.

Cause:	The translation file you're merging into the report was not created from the selected report.
Action:	Merge the translation file into the original report.


REP-32612Cannot merge for Base language.
REP-32612:  Cannot merge for Base language.

Cause:	You are trying to merge the untranslated strings back into the original report.
Action:	Translate the strings in the translation file and try again.


REP-32613Cannot find matching VGS string in NX file.
REP-32613:  Cannot find matching VGS string in NX file.

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32614Successfully merged strings for language '<language name>'.
REP-32614:  Successfully merged strings for language '<language name>'.

Cause:	Operation was completed with no errors.
Action:	No action is necessary.


REP-32615Merge failed.
REP-32615:  Merge failed.

Cause:	The merge operation encountered errors.
Action:	Check the log file for more information.


REP-32616Cannot find translations in NX file.
REP-32616:  Cannot find translations in NX file.

Cause:	The translation file does not contain translated strings.
Action:	Make sure you're using the correct translation file for the given report.


REP-32617NX file is corrupt!
REP-32617:  NX file is corrupt!

Cause:	This is an abnormal condition.
Action:	For information, see  Abnormal Conditions.


REP-32618Cannot open NX file for reading.
REP-32618:  Cannot open NX file for reading.

Cause:	Translation file cannot be opened.
Action:	Make sure the file exists and is readable.


REP-32750Unable to unpack the data of image '<image name>'.  The image has been removed.
REP-32750:  Unable to unpack the data of image '<image name>'.  The image has been removed.

Cause:	The image data is corrupted.
Action:	Import the image again.


REP-32751Warning: Some text segments are missing.
REP-32751:  Warning: Some text segments are missing.

Cause:	Text segments cannot be found for some boilerplate text.  The report may be corrupted.
Action:	Check the boilerplate text objects in the report.  Remove suspicious ones and create replacements for them.


REP-34300No distribution list available
REP-34300:  No distribution list available

Cause:	There is no distribution target.
Action:	Assign a distribution target.


REP-34300Invalid value for the field.
REP-34301:  Invalid value for the field.

Cause:	No value has been entered.
Action:	Enter a value.


REP-34302Destination format is uncompatiable with the runtime mode.
REP-34302:  Destination format is incompatible with the runtime mode.

Cause:	The format is incompatible with the mode (e.g., the report is a bitmap and the distribution destination is set to character mode.
Action:	Check the format in your destination.


REP-34303Distribution Successful!
REP-34303:  Distribution Successful!

Cause:	The distribution ran successfully.
Action:	none.


REP-34304Distribution failed! Check your distribution list!
REP-34304:  Distribution failed! Check your distribution list!

Cause:	The distribution failed
Action:	Check your distribution list.


REP-34305Wrong keyword setting for the destid= '$0'
REP-34305:  Wrong keyword setting for the destid= '<value>’.

Cause:	The keyword settings (e.g., DESNAME) are incorrect in the distribution file.
Action:	Check the keyword settings and make the necessary changes.


REP-34306No distribute ID specified for the destination!
REP-34306:  No distribute ID specified for the destination!

Cause:	In the distribution file, the ID for the destination is missing.
Action:	Add a unique distribution ID to the destination line..


REP-34307Not a unique distribute ID specified for the destination!
REP-34307:  Not a unique distribute ID specified for the destination!

Cause:	In the distribution file, the ID for the destination is not unique.
Action:	Add a unique distribution ID to the destination line..


Sorry, Topic Not Available

The help topic you selected is not available in this Help system.  If you have the Report Builder installed on your system, you can also find the topic by searching the Index of the Report Builder Help system.


Messages

  Related Topics

Click a message range, then page using the browse buttons to find the message you are looking for.

REP-0001 through REP-0089

REP-0090 through REP-0159

REP-0160 through REP-0249

REP-0250 through REP-0499

REP-0500 through REP-0539

REP-0540 through REP-0589

REP-0590 through REP-0659

REP-0660 through REP-0719

REP-0720 through REP-0779

REP-0780 through REP-0899

REP-0900 through REP-1059

REP-1060 through REP-1209

REP-1210 through REP-1259

REP-1260 through REP-1299

REP-1300 through REP-1339

REP-1340 through REP-1429

REP-1430 through REP-1819

REP-1820 through REP-1869

REP-1870 through REP-1999

REP-2000 through REP-3079

REP-3080 through REP-3349

REP-3350 through REP-3439

REP-3440 through REP-4039

REP-4040 through REP-16519

REP-16520 through REP-25339

REP-25400 through REP-32599

REP-32600 through REP-32307


Glossary

A

    action
    active window/view
    ActiveX
    Ada
    aggregation
    alert
    alignment
    alias
    All tool
    ancestor
    ancestor group
    anchor
    anchor point
    anonymous block
    antecedent
    applet
    application
    argument
    ASCII
    attached library
    attribute
    attribute columns
    attribute mask
    Attribute tool
    attribute value
    axis chart

 B

    background element
    background process
    baseline value
    Batch
    batch compile
    bind reference
    bind variable
    block
    body
    boilerplate
    border
    bounding box
    break chart
    break column
    break group
    break report
    break trigger
    breakpoint
    builder
    built-in datatype
    built-ins
    built-in macro
    buffer
    button
    button procedure

C

    cache (memory)
    call interface
    call stack
    canvas
    canvas view
    cartridge
    cascading style sheet
    category
    category axis
    cell
    CGI
    CGM
    CHAR datatype
    chart element
    chart item
    chart template
    check box
    checksum
    child
    child query
    classification
    clause
    client
    client/server architecture
    Clipboard
    CMDFILE
    collection type
    color palette
    column
    column object
    command line
    comment
    commit
    comparison operators
    compile
    component
    concurrency
    condition
    confine mode
    connect
    connect string
    constraint
    construct
    context area
    continuous axis
    control point
    coordinate plane
    coordinate system
    coordinates (x, y)
    copy
    correlated subquery
    cross product
    crosstab
    cursor
    custom measure
    cut

D

    damage
    data dictionary
    data link
    data model
    data structure node
    database
    database trigger
    datasource
    datatype
    DATE
    date axis
    debug
    debug action
    debug trigger
    Debugger
    deconstructed object
    default
    deliver
    dependency tree
    dependency view
    dependent data
    descendant
    Designer
    Designer/2000
    detail query
    dialog box
    DIANA
    dimension
    dimension hierarchy
    dimension value
    disabled
    discrete axis
    display
    display item
    downward-growing
    drag
    drill
    duplicate
    dynamic saved selection

E

    EBCDIC
    edge
    Edge/Fill/Text Display
    editor
    element
    element type
    Ellipsis button
    enabled
    enclosing object
    encryption
    environment
    exception
    Exception tool
    executable argument
    execute
    export
    export file
    expression
    external PL/SQL library
    external query

F

    family
    Family tool
    field
    field template
    file node
    fill area
    filter
    firewall
    flattened object
    flex mode
    focus
    foreground element
    foreign key
    form layout
    form letter layout
    format mask
    format trigger
    formula
    formula column
    frame
    function

G

    generate
    Generate
    Global Registry
    global variable
    grant
    gridlines
    group
    group filter
    group tree
    GUI

H

    handle
    header
    heading node
    hidden
    hierarchy
    HTML
    HTTP
    hyperlink
    hypertext

I

    ICD
    icon
    image
    implied item
    import
    independent data
    index
    inherit
    inner bounding box
    input item
    insert mode
    internet
    Interpreter script
    intranet
    IP (Internet Protocol) Address
    item
    item node

J

    JAR
    Java
    join
    justification

K

    keyword

L

    label
    Launcher
    level
    Level tool
    layout
    layout unit
    lexical reference
    library
    link
    link file
    list box
    list item
    list of values
    List tool
    local database
    local registry
    local variable
    logical operators
    logical page
    loop

M

    macro
    mailing label layout
    margin
    master/detail layout
    Match tool
    matrix cell
    matrix layout
    matrix report
    measure
    megabyte (Mb)
    message box
    method
    modal window
    modeless window
    module
    multi-line field

N

    NA value
    nested matrix
    NOCACHE
    node
    non-caching column
    NULL value
    numeric operators

O

    object
    object column
    object group
    object handle
    Object Navigator
    object table
    object type
    ODBC
    OLE
    OLE container
    OLE Server
    Oracle datatype
    Oracle Designer
    ORACLE_HOME
    organization node
    origin
    outer bounding box
    overflow

P

    packaged function
    package
    package body
    package specification
    page
    page break
    palette
    pane
    panel
    parameter
    parameter list
    parent
    paste
    pattern
    Pcode
    PDF
    physical page
    placeholder username
    plot type
    PL/SQL
    pld file
    pll file
    pls file
    plx file
    pop-up list
    port
    pre-defined action
    pre-defined type
    preference
    preview
    Previewer
    primary key
    primitive
    printer control code
    prt file
    procedure
    program unit
    project
    project file
    project item
    Project Navigator
    project node
    project registry
    project view
    Project Wizard
    property
    property class
    protocol

Q

    qualifying dimension
    query
    query filter function
    quit

R

    radio button
    radio group
    Range tool
    RC4
    RDBMS
    rdf file
    rep file
    read consistency
    record
    record group
    REF column
    reference line
    refresh
    register
    registry
    relational operator
    remote database
    repeating frame
    replace mode
    report-level objects
    Reports Background Engine (RWRBE60)
    Reports Queue Manager (RWRQM60)
    Reports Server (RWMTS60)
    Reports Web Cartridge
    Reports Web CGI (RWCGI60)
    rex file
    RGB
    root
    root node
    row
    row object
    RTF
    run
    runfile
    Runtime
    Runtime Parameter Form

S

    saved selection
    Saved Selection tool
    schema
    scope
    script
    section
    SELECT statement
    selection
    selection script
    Selector
    Selector tool
    session
    sibling
    socket
    Sort tool
    source
    specification
    split bar
    SQL
    sql file
    SQL script
    SQL statement
    stack
    statement
    static saved selection
    stored program unit
    stored subprogram
    style sheet
    subprogram
    subproject
    subproject node
    summary column
    SYLK
    syntax
    system variable

T

    table
    table type
    tabular
    target
    target node
    TCP
    tear-off menu
    text item
    title bar
    title page
    toggle
    tool
    toolbar
    tool palette
    Top/Bottom tool
    trailer
    transaction
    trigger
    type

U

    update
    URL
    user exit
    user-defined action
    user-defined type
    user-defined macro
    user registry

V

    valid XML
    value axis
    value construct
    variable
    varying array type
    VBX
    VBX control
    view
    virtual directory
    virtual file system
    visual attribute

W

    Web
    Web browser
    Web cartridge
    Web link
    Web server
    well-formed XML
    wildcard
    window
    WKS
    WRB
    WWW

X

    XML

Y

Z

    zoom


In Project Builder, a command string supplied either by Project Builder or by the user that applies to files of a given type.  An action is not restricted to a single file type; for example, if the action "Compile" is defined for both forms and C source files, selecting "Compile Project" will compile all .fmb and .c files using the appropriate tools.  See also:  pre-defined action, user-defined action.


A high-level programming language developed by the U.S. Department of Defense for use in embedded computer systems.


A window or view that can receive user input.


(Oracle Express) The consolidation of data for several dimension values into a single value, such as the total units sold for all the cities, or into a smaller set of values, such as the average units sold for cities in each region. Data is often collected at the lowest level of detail and is aggregated into higher level totals for analysis.


A modal window that notifies you of a condition that occurred because of your last action.  You must respond to an alert.


The way in which data is positioned in a field.  It may be positioned to the left, right, center, flush/left, flush/right, or flush/center of the defined width of a field.


A secondary name used in a SQL statement to reference a table, view, or column.


(Oracle Express) A Selector dialog box tool that allows you to select all of the values in a dimension, or all of the values in a dimension for a specific hierarchy.


(Oracle Express) A dimension value at any level above a particular value in a hierarchy. The ancestor value is the aggregated total of the values of its descendants.  The following example shows the dimension value "Europe" as the ancestor of "France," "Lyon," and "Paris" in the GEOGRAPHY dimension.


A group that owns another group, either directly or indirectly.


A layout object used to fix a spot on one object to a spot on another object, ensuring the position of the first object in relation to the second object.


(Oracle Express) A specific dimension value that is used when selecting dimension values based on their family relationship or when navigating through a hierarchy.


A PL/SQL program unit that has no name and does not require the explicit presence of the BEGIN and END keywords to enclose the executable statements.  Since they are unnamed, anonymous blocks cannot be referenced by other program units.


An object that appears in another object's group tree at any position above that other object.  Every object is an antecedent of its descendants.


A Java term for small programs that can be dynamically imported into Web pages or applications as needed.


One or more program modules used to achieve a specific result.  Applications can be nested within other applications.  For example, an application to control a company's inventory could consist of various Form Builder applications for input of data, and various Graphics Builder applications to display the data visually.


1. An optional expression passed to a program unit for the program unit to operate on.
2. Clauses containing keywords and their specified values.


Acronym for American National Standard Code for Information Interchange.


A read only collection of PL/SQL subprograms, usually provided with an application to supply necessary PL/SQL source.  Program units in an attached library are implicitly loaded when they are first called by another program unit at compile-time or runtime.  They remain loaded for quick reuse, which reduces runtime memory requirements and improves the performance of an application.  See also:  library .


1. See property.
2.  A part or component of an Oracle8 object type definition.  Each attribute has a name and an Oracle8 datatype.  When an object table is created based on the object type, the columns in the table correspond to the attributes in the object type definition.  When a column object in a relational table is created based on the object type, the column object contains the equivalent of sub-columns, each of which corresponds to an attribute in the object type definition.  In Oracle Developer, each Oracle8 object attribute in a table is treated as a separate data item, as if it were a separate column.  This is true for both object tables and column objects in relational tables.
3. (Oracle Express) A descriptive characteristic that is shared by dimension values. Attributes represent logical groupings that allow users to select data based on like characteristics. For example, in a database representing footwear, you can use a shoe color attribute to select all boots, sneakers, and slippers that share the same color.


The columns that compose a column object (Oracle8).


In Graphics Builder, the first element in an attribute descriptor.  It is a 32-bit mask that informs the toolkit of the attributes that will be set or retrieved by a subsequent function call.  Only those elements that have their corresponding bits set in the attribute mask are set or retrieved.


(Oracle Express) A Selector dialog box tool that allows you to select dimension values based on attributes and attribute values. For example, in a database representing soft drinks, you might select all products whose size is 1 liter. In this example, Size is an attribute and 1 liter is an attribute value.


(Oracle Express) The values in the database that make up an attribute. For example, in a database representing ice cream products, the following attribute values might belong to a flavor attribute in a Product dimension: vanilla, chocolate, and strawberry. Dimension values at various levels in the Product dimension -- brand, form, and size, for instance -- might share the same value for flavor.


A type of chart in which the data is plotted according to where it lies along the chart's edges, called axes.  An axis chart may contain two or three axes, each of which may be one of the following types:  discrete, continuous, or date.


The white part of a pattern.  You apply color to the background element using the Fill Color palette.


A non-interactive process that runs in an operating system environment and performs some service or action.  Certain Oracle products use background processes for different tasks, such as performing and coordinating tasks on behalf of concurrent users of the database, processing and delivering electronic messages, and managing printing services.


The value used as the starting point for plotting fields on the continuous axis of a chart.


The executable that executes an application in batch mode, without using a windowing system.


To translate, at once, several PL/SQL program units into a machine executable form.


A reference to a parameter used to replace a single literal value (e.g., a character string, number, or date) appearing anywhere in a PL/SQL construct or a SQL SELECT statement.  For a bind reference, you must precede the parameter name with a colon (:).


A global variable you can create and use outside of a PL/SQL package.


1. The basic program unit in PL/SQL, defined by the keywords DECLARE, BEGIN, EXCEPTION, and END.
2. In Form Builder, a logical container that relates to a database table or view.


1. Contains the same information as the program unit specification, and also includes the actual implementation of the subprogram (i.e., its sequence of actions).  In most cases, only a body must be defined for a subprogram.
2. In Report Builder, a region that contains the bulk of the report layout (text, graphics, data, and computations).  The report body appears between the report header and trailer pages.


Text and/or graphics that appear in a report every time it is run.  In some products this is called "constant" text or graphics.


A user-defined outline around a layout object, usually used to highlight its contents.  Borders are drawn such that half the width of the border lies outside the edge of the object, and half inside the edge.


See inner bounding box, outer bounding box.


An axis chart that displays two categories of data along one axis.


A query column assigned to a break group.


A group used to break or categorize report data.  All data in query columns assigned to a break group appear above the data in columns belonging to other groups.  Each record fetched for a break group appears only once, while multiple related records in other groups can be displayed.


A report that contains categories that break the report data into sets.


A PL/SQL block that executes each time a breakpoint is reached.  See also:  breakpoint.


A debug action you can place at any executable source line in a PL/SQL subprogram.  A breakpoint interrupts execution of the program unit and passes control to the PL/SQL Interpreter.  Breakpoints allow you to incrementally execute a subprogram and search for runtime errors.  See also:  break trigger.


Refers to a component of Oracle Developer used to create a specific type of document; for example, Form Builder is used to create forms, while Report Builder is used to create reports.


A datatype defined and supported by the Oracle Server.


A collection of extensions to the PL/SQL language that are designed to be used with Oracle Developer.  Built-ins include datatypes, procedures, functions, exceptions, and constants.


In Project Builder, macro shipped with Project Builder.  See also:  macro.


A temporary storage area for data during the transfer of that data between the computer and a peripheral, or between parts of a computer.  A buffer prevents loss of information due to differences in the speed or timing of the transfer and speeds up certain functions.


1. An interface element used to select an action item, display a dialog box, or acknowledge the current condition.
2. An object in an application that has a PL/SQL procedure associated with it.  The procedure is generally executed upon a user mouse event.


A PL/SQL procedure associated with an application object, that is executed when a specific mouse event occurs on the item at runtime (e.g. clicking the button).  It does this by establishing a hierarchy for the fetched data containing a break group.


A temporary storage place for database data that is currently being accessed or changed by users, or for data that Oracle Server requires to support users. The terms are often used interchangeably.


An interface that enables you to invoke Oracle Developer component executables from other Oracle products, or a 3GL program.


A chain of subprogram calls, from the initial entry point down to the currently executing subprogram.  Each subprogram call is represented by a frame on the downward-growing call stack, in which newly entered subprograms are added to the bottom of the stack.


   See editor.


In Form Builder, the background object on which you place the interface objects that users will interact with in the runtime application.  A canvas view is usually associated with a window.


Manageable objects that plug in to the client, application server, or database through an open API.


See style sheet.


A label component that allows differentiation between information on the basis of non-hierarchical delineation or compartments rather than sensitivity levels.  With classification, they are used as a means of restricting access to information.


See discrete axis.


An instance of data in a spreadsheet (e.g., Microsoft Excel).


Acronym for Common Gateway Interface. The industry-standard technique for running applications on a Web server.  Whereas standard HTML documents retrieved from a Web server are static (the exact same text is retrieved every time) CGI enables a program running on the Web server to communicate with another computer to generate "dynamic" HTML documents in response to user-entered information.


Acronym for Computer Graphics Metafile.  A file format recognized internationally and used to store and transport object-oriented graphics from one system or program to another.


An Oracle datatype provided for ANSI/ISO compatibility.  A CHAR column is a fixed-length column and can contain any printable characters, such as A, 3, &, or blanks, and can have from 1 to 255 characters or can be null.


A bar, line, symbol, or other graphical object that represents a single value for a field.


A bordered rectangle of any size used to embed Graphics Builder charts in a form or report.


A collection of attributes and properties that defines the format of a chart.


A interface element, appearing as a small square, that a user can toggle on or off.


An error-checking algorithm.


1. An object that is a member of a group, and is immediately below that group object in its group tree.  The objects that compose a group object are children of that group.  Every object is a child of its parent.
2. (Oracle Express) A dimension value at the level immediately below a particular value in a hierarchy. Values of children are included in the calculation that produces the aggregated total for a parent.  A dimension value may be a child for more than one parent if the dimension has more than one hierarchy.  The following example shows the dimension values "Lyon" and "Paris" as the children of "France" in the GEOGRAPHY dimension.


See detail query.


A hierarchical level that denotes the sensitivity of the information that is labeled.  Classifications are used as a means of restricting access to information.


A part of a SQL statement that does not constitute the full statement; for example, a "WHERE clause."


A user, software application, or computer that requests the services, data, or processing of another application or computer (the "server").  In a two-task environment, the client is the user process.  In a network environment, the client is the local user process and the server may be local or remote.


Separation of processing between two CPUs, one acting as the server that provides services in a transaction and the other as the client in the transaction, requesting and receiving services.  All responsibilities of shared data management can be processed by the computer running the database management system while the workstations running the database application concentrate on the interpretation and display of data.


A memory buffer.  An object remains on the Clipboard until you cut or copy another object, or until you quit the application.


A user-defined datatype that describes a data unit made up of an indefinite number of elements, all of the same datatype.  Varying array types and table types are collection types.  (Oracle8)


An argument that allows you to specify a file that contains a set of command line arguments for Oracle Developer executables.


Contains all the colors available to the windowing system, the drawing surface, or a window and its views.


1. A vertical space in a database table that represents a particular domain of data.  A column has a column name (e.g., ENAME) and a specific datatype (e.g., CHAR).  For example, in a table of employee information, all of the employees' names would constitute one column.  A record group column represents a database column.
2. In Report Builder, a data model object created automatically for each column expression in a query's SELECT list, or created manually to perform summaries, formulas, or act as a placeholder.


In an Oracle8 relational table or object table, a column whose definition is based on an object type.  The column is a composite, the parts of which correspond to the attributes of the object type.


An operating-system command line.  Most Oracle products can be invoked from a command line using a number of executable arguments.


A language construct for the inclusion of explanatory text in a program, the execution of which remains unaffected.


To make changes to data in the database permanent.  Before changes are stored, both the old and new data exist so that changes can be stored or the data can be restored to its prior state.


(Oracle Express)

>	Greater than

<	Less than

=	Equal to

<=	Less than or equal to

>=	Greater than or equal to

<>	Not equal to

For numbers, the operands are widened to the least common type (Integer is preferred over Long, which is preferred over Single, which is preferred over Double). For Strings, the comparison is case-sensitive and is based on the collating sequence used by the language specified in the Windows Control Panel. The result is 0 for FALSE and -1 for TRUE.


To translate a source program into a binary, executable format.  PL/SQL program units must be compiled before they can be executed.


A specific target object that is a part of a larger application; e.g. a form in an order entry system, or a library that is shared among many other elements.  See also:  target.


The simultaneous access of the same data by multiple users executing different database applications or the same application.  In database software concurrency requires additional logic to ensure that all users see consistent data and that all changes are made in the proper order.


An expression whose value is either true or false, such as X> 100.  For example, you can set a condition in a query when you want the query to display only those rows that evaluate as true in your expression.


Layout editor mode that prevents child objects from being moved or resized on or outside their parent objects.


To log on to a database.  You must connect if you want to create or modify queries or access an application stored in a database.


The set of parameters, including a protocol, that SQL*Net uses to connect to a specific Oracle instance on the network.


A rule or restriction concerning a piece of data (such as a NOT NULL restriction on a column) that is enforced at the database level, rather than the object or application level.


A PL/SQL code structure.  There are two types of constructs: non-value constructs do not return a value; value constructs return a value.


A work area in which Oracle Server stores the current SQL statement, and if the statement is a query, the result's column headings and one row of the result.  Also referred to as cursor.


An axis that plots values that begin with one value and continue until they reach another value.  Thus, these values are mathematically related.  Dependent data is usually plotted along this axis, also called the value axis.


The four corner points of the virtual rectangle that constitutes an object's ideal shape.  When you select an object on the layout, its control points appear.  Depending on the object selected, you may be able to modify it by dragging a control point.


The two-dimensional grid on which drawing takes place.


The type of x, y units used to place and size objects in the Layout Editor view.  The coordinate systems available are 1) character, which uses the platform's native character cell size, and 2) real, which can be in units of pixels, centimeters, inches, or points.


The location points for objects appearing in the layout.  x and y coordinates determine the horizontal (x) and vertical (y) placement of objects.


To store a replica of a selected object on the Clipboard, so that it may be pasted elsewhere in an editor if desired.


A subquery based on the same tables as the parent query (i.e., references columns in the tables included in its parent query).


Group that owns two or more other groups and performs a mathematical cross product (i.e., correlates values between them).


See matrix cell.


1. A small icon representing the position of the mouse.  The shape of the cursor varies, depending on the selected tool.
2. An internal pointer to data retrieved by a query.  A cursor points only to one row of data at a time; however, you can use built-in subprograms to move the cursor to any row in the data set.


(Oracle Express) A formula created by a user, which allows fine-tuning of data analysis. You create custom measures using base measures in the database. For example, if the database contains the existing measure Volume Share, you can use this measure to create a custom measure named Volume Share Year Ago. This custom measure would allow you to look at a product's absolute share from the previous year.


To delete one or more objects and store them in the Clipboard, so that they may be pasted elsewhere in an editor, if desired.


A view is damaged when it is totally or partially occluded by another view.


A set of tables and views owned by the database administrator.  It is a central source of information for Oracle Server and other relational databases.


A data model object used to define a master/detail (parent-child) relationship between a group and a query.


A relational model that defines what data should be fetched from the database, what values should be computed, and how data should be ordered in a report.  Report Builder objects that define the data model are queries, groups, columns, parameters, and links.


A source for data returned by a query, including database objects such as tables, views, synonyms, snapshots, and queries stored as views.


In Project Builder, a node in the Project Navigator denoting a project item that governs the structure of an open project.  For example, the Global Registry node denotes the Global Registry, which contains a list of local registries and a list of global type definitions.


A set of dictionary tables and user tables that are treated as a unit.


A stored PL/SQL block that is implicitly executed when a triggering INSERT, UPDATE, or DELETE statement is issued against the associated table in the database.  See also:  debug trigger.


A standard form of data.  Some common Oracle datatypes are CHAR, VARCHAR2, DATE, NUMBER, LONG, RAW, and LONG RAW.


An Oracle Server datatype.  A date column may contain a date and time between January 1, 9999 BC and December 31, 9999 AD.


An axis that plots date values that begin at one date and continue until they reach another date.


To detect, diagnose, and eliminate runtime errors in programs.


A user-specified event placed in a PL/SQL subprogram, usually for the purpose of troubleshooting runtime errors.


A conditional debug action you can place at any executable source line in a PL/SQL subprogram.  If the specified condition is met, the specified action is taken before execution of the subprogram resumes.  See also:  database trigger.


The Procedure Builder functionality within an Oracle Developer component used for testing and debugging.


In Oracle8, object types and objects are composites, built of parts or attributes.  Oracle Developer treats each part/attribute as an independent, individually-selectable data item.  This treatment results in a deconstructed object (sometimes also known as a flattened object).  The object is not an homogeneous entity within the Oracle Developer environment.


A piece of data that depends on other data for its value.  For example, an employee's  years of service may have the value 10, which is dependent upon the value of the employee's name.  Also called value data.


A value supplied by the system when a user does not specify a required command parameter or attribute.


To prepare and provide a completed application for distribution and deployment.


In Project Builder, the mechanism used by Project Builder to determine how to compile files that are referenced in projects.  Items toward the top left of the tree depend on items toward the lower right; so, for example, if a header file is either out of date or more recent than the executable file it is used to build, then the Project Builder will rebuild the executable file, given a Build command.  Dependencies also extend to subprojects.  For example, if a subproject consisting of a function library has been rebuilt, the Project Builder "knows" the dependent project will need to be rebuilt in order to use the updated library functions.  See also:  dependency view.


In Project Builder, shows files in the Project Navigator in the order in which they depend on each other, with project nodes at the highest point in the hierarchy, followed by target nodes, which are followed by buildable components of those targets.  For example, an executable form depends on and will be followed by an .fmb file, which may depend on and be followed by a library used for a USEREXIT procedure, and so on.  See also: project view, target.


1. An object that appears in another object's group tree at any position below that other object.  Every object is a descendant of its antecedents.
2. (Oracle Express) A dimension value at any level below a particular value in a hierarchy. Values of descendants are included in the calculation that produces the aggregated total for an ancestor.  The following example shows the dimension values "France," "Lyon," and "Paris" as descendants of "Europe" in the GEOGRAPHY dimension.


The interface used to design different components of an Oracle Developer application.


See Oracle Designer.


An application modeling, design and generation toolset.  Using Oracle Designer, you can generate forms and menus from module definitions recorded in the Oracle Repository.


When defining a master/detail report, the detail query retrieves all related records for each record retrieved by the master, or parent, query.


A partial screen or window that prompts you to enter information necessary to complete an operation.


An intermediate representation of a program unit, generated by the compiler.  The DIANA includes all of the syntactic and semantic information for a compiled program unit.  In order to compile a reference to a program unit, the compiler must have access to the referenced program unit's DIANA.  For example, if program unit A calls program unit B, the DIANA for B must be available before A can be compiled.


(Oracle Express) A type of database object that is a list of values that provide categories for data. A dimension acts as an index for identifying values of a variable. For example, if you have sales data with a separate sales figure for each month, then the data has a MONTH dimension; that is, the data is organized by month. A dimension is similar to a key in a relational database.

Any item of data within a multidimensional variable can be uniquely and completely selected by specifying one member from each of the variable's dimensions. For example, if a sales variable is dimensioned by MONTH, PRODUCT, and MARKET, specifying "January" for the MONTH dimension, "Stereos" for the PRODUCT dimension, and "Eastern Region" for the MARKET dimension uniquely specifies a single cell in the variable. Thus, dimensions offer a concise and intuitive way of organizing and selecting data for retrieval, updating, and performing calculations.

A dimension can be simple, with values that are single text or integer values, or it can be conjoint, with values that are combinations of values in other dimensions. A composite is not a dimension, but it is a conjoint-like internal object that Express treats like a dimension for the purpose of handling sparse data.


(Oracle Express) One element in the list that makes up a dimension. For example, a computer company might have dimension values in the PRODUCT dimension called "LAPPC" and "DESKPC." Values in the GEOGRAPHY dimension might include "Boston" and "Paris." Values in the TIME dimension might include "MAY96" and "JAN97."


An interface element state that means a menu item, button, etc., cannot be used in the current context; i.e., it does not respond to keyboard or mouse input.


An axis that plots distinct values at fixed intervals.  These values are not mathematically related.  Independent data is usually plotted along this axis, also called the category axis.


A Graphics Builder document containing any combination of charts, images, text objects and shapes.


In Form Builder, an item that stores or displays information that must be fetched or assigned programmatically with PL/SQL.


As it pertains to the call stack, in which newly entered subprograms are added to the bottom of the stack.  The earliest frame, corresponding to the initial program entry point, is at the top of the stack, while the latest frame, associated with the most deeply nested subprogram call, is at the bottom of the stack.


Press and hold down a mouse button while you slide the mouse pointer to a particular location in a window.


(Oracle Express) To navigate up and down through the levels of aggregation in a dimension that has a hierarchy. When selecting dimension values or viewing data, you can expand or collapse a dimension hierarchy by drilling down or up in it. Drilling down expands the view to include child values that are associated with parent values in the dimension hierarchy. Drilling up collapses the list of descendant values associated with a parent value in the dimension hierarchy.

You can click on a plus icon ( [image]) to drill down on (expand) the hierarchy or on a minus icon ( [image]) to drill up on (collapse) the hierarchy.

In the Selector, you can click on the drill icon ( [image]) to display the Drill dialog box so you can select a level of detail for the entire dimension.


An option that allows you to copy objects directly on the layout without affecting the contents of the Clipboard.


(Oracle Express) A saved selection that can have different dimension values each time it is evaluated. The selected dimension values might differ from use to use. In contrast, a static saved selection is an unchanging list of dimension values. A dynamic saved selection script might include "Select the last three Months", while the script for a static saved selection might have "Select February 1996, March 1996, and April 1996".


Acronym for Extended Binary-Coded Decimal Interchange Code.


The boundary of an object.


A display box on the Layout Editor tool palette that shows the current settings for the edge, fill, and text patterns and colors.


A work area in which you perform a specific set of tasks, such as creating a program unit or designing an application.


A thing of significance about which you may need to record information.  Elements are described by attributes and associations to other elements.


Any element held in the dictionary is classified as being of a particular type.  Examples of element type are entity, attribute, program module, table, diagram, text, softbox.  Occurrences or instances of these are called elements.


(Oracle Express) Displays a dialog box related to the task you are performing, usually so you can select one or more values that you need.


An interface element state that means that a menu item, button, etc., can be used in the current context, that is, it responds to keyboard or cursor/mouse input.


An object that contains another object.  An object is considered to be enclosed by another object only if all of the following are true:  both objects belong to the same region (Body, Margin, Header, or Trailer);  the outermost of the two objects is a frame or repeating frame;  the outermost of the two objects is behind the other object;  the innermost of the two objects lies entirely within the borders of the other object.


The practice of scrambling (encrypting) data in such a way that only an intended recipient can unscramble (decrypt) and read the data.


The user's computer-based workplace, including the tools typically used and their configurations. For Project Builder, this refers to the subset of tools that are used to complete various tasks related to developing Oracle Developer applications.


A warming or error condition generated from a PL/SQL subprogram.


(Oracle Express) A Selector dialog box tool that allows the user to select dimension values associated with data that meets cutoff terms that the user specifies. For example, the user can select all products whose dollar sales were greater than $10,000 for the week ending December 23, 1995 in the Boston market.


An argument you can pass to a product executable, such as 'OPENFILE=my_disp' and 'PRINT=YES'.  These arguments usually are specified when the executable is invoked from a command line.


See run.


To store a copy of an object, module, selected text or image to a file or database.  In Project Builder, the process of writing out a file containing project, type, action, and/or macro definitions in a portable format for distribution to others who may work on heterogeneous platforms.  See also:  export file, import.


In Project Builder, the shareable, portable file created by exporting a project.


1. A PL/SQL construct combining variables, constants, literals, and operations on their values.
2. (Oracle Express) One or more data values that are specified in an Express language program. For example, you can specify expressions as arguments to programs or functions. An expression can be any of the following:

•	A single, literal value (for example, 10)

•	A variable or formula that contains one or more values

•	A function that returns one or more values

•	A calculation that combines values, such as variables, formulas, or functions, with arithmetic or Boolean operators


See library.


An ANSI-standard SQL SELECT statement that can be referenced by other Oracle products.


(Oracle Express) A group of related dimension values that correspond to the levels of the dimension hierarchy. Dimension values within a family can relate to each other as ancestor, parent, child, and descendant.  The following example shows family relationships for the dimension value "France" in the GEOGRAPHY dimension.


(Oracle Express) A Selector dialog box tool that allows the user to select a family of dimension values for a particular hierarchy. A family includes a parent and all of its descendant dimension values. For example, the user can select all of the family members below the Chicago market level in the Geography dimension.


1. An interface element in which you enter, edit, or delete data.  2. In Graphics Builder or Report Builder, a layout object that define how the data for a specific query column appears.


In Graphics Builder, a collection of attributes and properties that determines how dependent data (values) are represented as chart fields, such as bars or lines.


In Project Builder, a node in the Project Navigator denoting a file stored in the file system.  For example, the global and local registry nodes correspond to global and local registry files.


The area within an object to which a fill (color or pattern) should be applied.


A PL/SQL function or anonymous function that restricts the data displayed by a group.


A computer that regulates access to computers on a local area network from outside, and regulates access to outside computers from within the local area network.


See deconstructed object.


Layout Editor mode that automatically resizes or shrinks parent objects when child objects are moved or resized, and adjusts the positions of other layout objects that might otherwise be affected by the repositioning or resizing of the objects.


The state of an entity that is able to respond to input from the user or the client.  If an entity has the keyboard focus, it can receive events when the user presses a key.  If a drawn view has the drawing focus, it can respond to client routines that affect drawing.


The black part of a pattern.  You apply color to the foreground element using the Edge Color palette.


A value or column in one table that refers to a primary key in another table.


In Report Builder, a default layout style in which labels appear to the left of fields, and each record prints on a separate logical page.


In Report Builder, a default layout style that intermixes boilerplate and fields, wrapping lines at "word" breaks.


(Field Properties)  A setting that defines the appearance of the value of a field.  For example, a format mask is used to specify the display of currency amounts and dates.


A PL/SQL function that allows you to dynamically change the formatting attributes of an object.


(Oracle Express) A type of database object that represents a stored calculation, expression, or procedure that produces a value. A formula provides a way to define and save complex or frequently used relationships within the data without resaving the data itself. Each time you use a formula, Express performs the calculation or procedure that is required to produce the value.


A user-created column that gets its data from a PL/SQL function or expression, a user exit, a SQL statement, or any combination of these.


In Graphics Builder, the part of a chart template that defines the basic structure of a chart, but does not determine the way the data is plotted.
2. In Report Builder, a layout object used to enclose other layout objects and control the formatting, frequency, and positioning of several objects simultaneously.


A PL/SQL subprogram that performs a specified sequence of actions, and then returns a value.  Can reside and execute on the client and the database server.


To save an application to a file or database in a binary format that can be executed by Runtime and Batch executables.


The Form Builder executable used to save an application to a file or database in a binary format.


A Project Builder registry that stores information common to an entire Oracle Developer installation.  This information is restricted to type definitions, and their associated actions and pre-defined or user-defined properties.  The use of the Global Registry is optional; its functions can be performed by individual user registries.  See also: registry, user registry.


A logical container that exists across an application.  When an application uses a global variable, the application maintains the variable until the application is exited, or until another object explicitly removes it.


To give a user access to a module.  Only a module's creator can grant its access to other users.


In Graphics Builder, the lines that separate rows and columns in the Layout Editor.


1. An object that is composed of several other objects.
2. In Report Builder, a data model object that is created automatically to contain all the columns selected by a query, or created by the user to modify the hierarchy of the data appearing in a report;  it is used primarily for creating breaks in a report, as well as for resetting computations.
3. In Project Builder, collections of related items available via submenus off the Launcher.  Groups allow users to set up the Launcher much like the Windows 95 Start menu, with arbitrary "groups" as entries that pop up to reveal other items and/or groups.  For example, a user could define a group named "Project Docs", containing a project schedule, to-do list, component specifications, etc.; some files may be .TXT files, other .DOC files.


A PL/SQL function that restricts the data fetched by a group.


A hierarchical model-similar to a "family tree"-that describes the relationships between group objects and the objects that compose them.


Acronym for graphical user interface. The use of pictures rather than just words to represent the input and output of a program.  Programs with GUIs run under a windowing system (such as  X Windows, Microsoft Windows, Apple Macintosh, and so on).  GUI programs display icons, buttons, and so on, in windows on the screen;  users control the GUI programs mainly by moving a pointer on the screen (typically controlled by a mouse).  Also known as a bitmapped interface.


An internal pointer to an application object.  In order to reference an object in a PL/SQL program unit, you must pass its handle as an argument to the appropriate subprogram.


An optional report region that can contain introductory material for the report, including text, graphics, data, and computations.  The report header appears first, before the body and trailer.


A node in the Object Navigator denoting a type of object which can be contained within or associated with a report.  Selecting a heading node does not select an object in the report.


(Field Properties)  A property that specifies whether Report Builder will suppress the indicated field at its location in the layout.  If Hidden is specified, the field's value will appear only where referenced in text objects (using &fieldname).


(Oracle Express) A means of organizing and structuring data. A hierarchy exists when values within a dimension are arranged in levels, with each level representing the aggregated total of the data from the level below. Some dimensions have multiple hierarchies based on them.

The following example shows a hierarchy based on the GEOGRAPHY dimension, in which dimension values are arranged in five levels. Data at the Customers level is aggregated into the Cities level, which, in turn, is aggregated into the Countries/Areas, Continents/Regions, and Global levels.


Acronym for Hypertext Markup Language.  A tag-based ASCII language used to specify the content and links to other documents on Web servers on the Internet.  End users with Web browsers view HTML documents and follow links to display other documents.


Acronym for Hypertext Transfer Protocol. The protocol used to carry WWW traffic between a WWW browser computer and the WWW server being accessed.


A reference (link) from some point in one document to (some point in) another document or another place in the same document.  A Web browser usually displays a hyperlink in some distinguishing way (in a different color, font or style).  When users activate hyperlinks (by clicking on them with a mouse) the browser displays the target of the link.


A collection of documents containing cross-references which, with the aid of a Web browser, allow readers to move easily from one document to another.


Cross-references which, with the aid of a Web browser, allow readers to move easily from one document to another.


Acronym for interface C definition-a PL/SQL application programming interface to functionality implemented in C.


A graphic representation of a window or tool.


A bitmapped object that can be stored and loaded into an application.  The client cannot modify an imported image.


In Project Builder, a project item, usually the result of automatic generation, that Project Builder recognizes and for which it automatically creates entries in the Project Navigator.  For example, Project Builder can recognize .OBJ files, generated as an intermediate step during the compilation of C source files, and create entries for them in the Project Navigator.  Although resetting the properties of an implied item is of limited use (the next compilation will destroy changes) such items can be useful, as they can be examined via actions such as Edit, View, and Print.  See also: item, action.


1. To read a module from the file system or database, and incorporate it into an application.
2. To read in a file containing project information.


A piece of data that does not depend on other data for its value.  For example, an employee's name may have the value Jones, which is independent of the values of other employee's names or associated data.  Also called category data.


An optional structure associated with a table that is used by Oracle Server to locate rows of the table quickly, and (optionally) to guarantee that every row is unique.


In Project Builder, to obtain information for an action, type, macro, or property definition from an ancestor node in the dependency tree.  If related attributes exist in an ancestor node, they may be inherited.  Thus, filesystem items like forms and documents may inherit action definitions from subprojects, projects, the user registry, or the Global Registry; projects may inherit type definitions from the local or the Global Registry; and so on.


The virtual rectangle that constitutes an object's ideal shape and connects its four control points, regardless of edge thickness or other attribute settings.


The file used to build a target: for instance, an .FMB is the input for an .FMX.  Also called source.


A mode in which each character you enter is inserted at the cursor, pushing the following characters to the right.  The opposite of replace mode.


A worldwide TCP/IP-based network of computers.


A file containing any mixture of PL/SQL source, Procedure Builder commands, and SQL statements.


An internal TCP/IP network, access to which is restricted (via a firewall) to individuals inside the company or organization.  An intranet provides similar services within an organization to those provided by the Internet, but is not necessarily connected to the Internet.  A common example of an intranet is when a company sets up one or more Web servers on an internal network for distribution of information or applications within the company.


A four-part number with no more than three digits in each part that uniquely identifies a computer on the Internet.


In Project Builder, an object in the file system associated with the project, such as a form or a document, pointed to or represented by a node in the Project Navigator.


In Project Builder, an entry in the Project Navigator window, consisting of an icon and a descriptive title.  Nodes point to actual items in the filesystem, such as Form Builder files and documents.  See also: node, item.


Acronym for Java ARchive.  A file used for aggregating many files (Java class files, images, and so on)  into one file.


A computer language that supports programming for the Internet in the form of platform-independent "applets".


Combining data from two (or more) tables in a single SELECT statement.


  See alignment.


1. Part of a command line syntax that must be supplied with a corresponding argument.  2. A required part of a PL/SQL construct.


Text identifying the values or meaning of an application's visual objects.


(Oracle Express) A position in a dimension hierarchy. Each level above the base level represents the aggregated total of the data from the level below. For example, the TIME dimension might have ascending levels such as Month, Quarter, and Year. Within a dimension hierarchy, a dimension value at one level has a family relationship with the dimension values at the levels above and below that level.


(Oracle Express) A Selector dialog box tool that allows the user to select dimension values based on their level in a particular hierarchy. For example, the user can select all of the dimension values at the Key Account level in the Geography dimension.


The area of an editor in which you can create, modify, position, or delete objects.


A unit of measurement for ensuring a consistent measurement system across different display devices.  Used to specify a position on the layout, or the dimensions of an object.


A reference to a parameter used to represent a string of text in a SQL SELECT statement.  For a lexical reference, you must precede the parameter name with an ampersand (&).


A collection of one or more PL/SQL program units that are stored together in a file on the client file system or in the database.  Program units stored in a library can be referenced by several applications at once.  Unlike stored program units, which reside and execute in the database, program units in libraries always load and execute within the PL/SQL engine on the client side.  To reference program units that are stored in a library, you must first attach the library.  See also:  attached library.


A data model object used to define a master/detail (parent-child) relationship between a group and a query.


The name of a file to which a boilerplate object is associated.  At runtime, Report Builder imports the file's contents into your report layout.


A list of items within a dialog box.  Usually, the list box offers choices for selection, and it is scrollable.


In Form Builder, an item that displays a list of choices.


Also called LOV. A scrollable popup window that provides the user with a single or multi-column selection list.


(Oracle Express) A Selector dialog box tool that allows you to select dimension values from a list of the currently selected values in the dimension.


1. The database on the computer running the application.  2. The database to which an application is connected.  This database parses and executes all SQL statements generated by the application.


See user registry.


A PL/SQL variable declared only within the scope of the current program unit.


(Oracle Express)

Not	Unary Not -- Operand can be integer or long. The operation is performed bitwise (one's complement).

And	And -- Operands can be integer or long. The operation is performed bitwise.

Or	Inclusive Or -- Operands can be integer or long. The operation is performed bitwise.

Xor	Exclusive Or -- Operands can be integer or long. The operation is performed bitwise.

Eqv	Equivalence -- Operands can be integer or long. The operation is performed bitwise. (A Eqv B) is the same as (Not (A Xor B)).

Imp	Implication -- Operands can be integer or long. The operation is performed bitwise. (A Imp B) is the same as ((Not A) OR B).


One page of your actual report (it may be displayed on one or more physical pages).


In a PL/SQL subprogram, a conditional statement that is repeated until the condition is no longer met.


In Project Builder, a type-specific variable that may be used to customize and extend actions.  A macro may be either a constant or a simple expression (which, in turn, may contain other constants and/or expressions).  The use of macros adds great flexibility in issuing command options, and in allowing the user to modify sets of commands by changing one property definition.


A default layout that displays records in one or more columns on the page.  Fields appear directly beneath each other in a single repeating frame.


An optional report region that appears at the top and bottom of each logical page in the body region.  The margin may include any layout object, but typically contains boilerplate and fields (for page numbers, page totals, grand totals, and current date and time).


A default layout in which the detail records appear below the master records.  Master records appear in form layout style, while detail records appear in tabular layout style.


(Oracle Express) A Selector dialog box tool that allows the user to select dimension values by matching characters in dimension value names to characters that the user specifies. For example, the user can select all dimension values in the Product dimension at the Brand level that contain the characters "new."


A repeat direction that displays each record of a repeating frame as a cell of a matrix.


A default layout, resembling a grid, that formats the four sets of data necessary for a matrix report; one set of data displays as a row of labels, one as a column of labels, one set creates the grid, and one set fills the cells of the grid.


A cross-tabulation of four sets of data:  one set of data displays across the page; one set of data displays down the page; one set of data is the cross-product, determining all possible locations in which the across and down data relate and placing a cell in those locations; and one set of data displays as the "filler" of the cells.


(Oracle Express) Data that can be examined and analyzed, such as sales or cost data. You can select and display the data in a measure. Measures can be stored as variables or relations, or measures can be calculated by means of formulas.


A unit of memory equal to 1,048,576 bytes (1024 x 1024). Often rounded to one million bytes.


A modal window that notifies you of a condition that occurred because of your last action.  You must respond to a message box.


Executable code attached to an Oracle8 object through its object type definition.


A window that elicits a response from the operator before the application can continue.


An unrestricted window that can have as much functionality as the runtime window manager can support.


1. An object that can be shared by multiple applications.  External queries and PL/SQL libraries are examples of modules.  2. In Form Builder, a major component of an application (i.e., a menu module).


A field in a window or dialog that extends for several lines, allowing you to scroll vertically through the information.


(Oracle Express) A special data value that indicates that data is "not available" (NA). NA is the value of any cell to which a specific data value has not been assigned or for which data cannot be calculated.


Matrix report in which either the across and/or down dimension contains one or more master/detail relationships.  There is no limit to the amount of nesting allowed.


A datatype indicating that the data will be fetched when the page on which it appears is formatted (instead of fetched and cached until formatted).


1.  A specific location in the Object Navigator object hierarchy.  Nodes can be expanded to reveal information about an object, such as cross references to other objects.  2.  In Project Builder, an entry in the Project Navigator.  See also:  item, item node, organization node.


A report column that references a database column of datatype NOCACHE.


The absence of a value.


(Oracle Express)

^	Exponentiation,

-,+	Unary minus and plus,

*, /	Numeric multiplication or division. For division, the result is a double.

\	Integer division. The operands can be integer or long.

Mod	Modulus or Remainder. The operands can be integer or long,

-, +	Numeric addition and subtraction. The + operator can also be used for string concatenation.


1.  An item that can be placed on the layout.  The following are examples of objects:  rectangle, line, ellipse, arc, polygon, polyline, rounded rectangle, freehand, chart, text, symbol, and text field.  2.  In Oracle8, an instance of an object type.  An object can be a row in an object table, or the portion of a row contained in a column object in a relational table.


See column object.


A container for a group of objects, used to provide the ability to copy or reference related objects.


See handle.


The window containing a hierarchical list of objects for the current session.  The list appears in outline form, and enables the user to accomplish several tasks such as creating, editing, renaming, and deleting objects.


In Oracle8, a table whose definition is based on an object type.  Each attribute in the object type becomes a column in the object table.  Each row in the table is an individual Oracle8 object.


In Oracle8, a user-supplied definition or template, upon which objects can be built.  An object type is a composite, whose parts are attributes.  Each attribute has a name and a datatype, and the object type as a whole has a name.  An object type may also include one or more methods.


Acronym for Open Database Connectivity.  A standard for accessing different database systems.  An application can submit statements to ODBC using the ODBC flavor of SQL.  ODBC then translates these to whatever flavor the database understands.  Using the Oracle Open Client Adapter (OCA), an application can access different database management systems in one consistent manner.  This allows an application developer to develop, compile, and ship an application without targeting a specific DBMS.


Object Linking and Embedding.


An application that can store and display OLE objects.


An application that creates OLE objects.


See built-in datatype.


An environment variable that indicates the root directory of Oracle products.


An entry in the Project Navigator, such as "Types", "Projects", "Form Files", etc., used to help organize the Navigator and indicate the filetypes of child items.  It may also correspond to a data structure within certain types of filesystem objects.


Represented in x and y coordinates.  The origin of a view indicates the location of the view on its parent's canvas.  The origin of a canvas indicates the position of drawing on a drawn view.


The smallest virtual rectangle that completely surrounds an object.


When an object's contents cannot fit on the current logical page.  In the event of overflow, some of the contents are moved to the next logical page.


A PL/SQL function provided with Oracle Developer that can be referenced anywhere within a program unit.


A method of encapsulating and storing related procedures, functions, variables, and other package constructs together as a unit in the database or on the client.  While packages provide the database administrator or application developer organizational benefits, they also offer increased functionality and database performance.  Oracle Developer provides several built-in packages which contain PL/SQL constructs that can be referenced by client-side program units (e.g., TEXT_IO package).  Several packages are also supplied with the Oracle database server for referencing by stored program units (e.g., DBMS_OUTPUT package).


Includes the actual implementation of the package, which may include private subprograms and datatypes.  The body is optional if the package consists only of declarations.


Declares the public interface to the package-that is, the datatypes and subprograms that can be referenced by other program units.


(Oracle Express) 1. A slice of data included in a report. Additional pages display additional slices of data.

The following figure shows three pages of data.

2. In Express, a page can also refer to a unit of storage in an Express database.


(Oracle Express) A representation of how data selected for a query will appear in your spreadsheet. The page layout shows three edges -- Across, Down, and Page. The edges indicate how the multi-dimensional datacube defined by the query will appear in the two-dimensional spreadsheet. Dimension tiles display the names and positions of the dimensions. A dimension tile on the Across edge indicates that this dimension will appear as a column. A dimension tile on the Down edge indicates that this dimension will appear as a row. A dimension on the Page edge indicates that this dimension will appear in a page box at the top of the results.


A setting that controls whether to move the current object and its children to the next logical page.  You can set page breaks to occur before or after the current object appears in the report output.


An interface element that displays tools, colors, or patterns available in an editor.


A distinct portion of an editor where work is performed, usually resizeable.


The number of physical pages needed to print one logical page.


1. A PL/SQL construct used to pass information to a subprogram.  For example, in the subprogram call MYPROC (x),x is a parameter.  2. In Oracle Developer, parameters are used to pass information between components such as Form Builder and Graphics Builder.  3. A variable you can change at runtime.


A group of parameter names and associated values used to pass information between Oracle Developer components.


1. An object that is immediately above another object in its group tree.  A group object is the parent to each of the objects that compose it.  Every object is the parent of its children.
2. (Oracle Express) A dimension value at the level immediately above a particular value in a hierarchy. The parent value is the aggregated total of the values of its children.  The following example shows the dimension value "France" as the parent of "Lyon" and "Paris" in the GEOGRAPHY dimension.


To place the contents of the Clipboard (cut or copied objects) at the current cursor location.


A graphical property you can apply to the edge or fill of most objects.


The machine code or instruction list for a compiled program unit.


Acronym for Portable Document Format.  A file format (native for Adobe Acrobat) for representing documents in a manner that is independent of the original application software, hardware, and operating system used to create the documents.  A PDF file can describe documents containing any combination of text, graphics, and images in a device-independent and resolution independent format.


The size of a page that is output by your printer.


The type of element used to plot a field on a chart, such as bar, line, or symbol.


Oracle's proprietary extension to the SQL language.  Adds procedural and other constructs to SQL that make it suitable for writing applications.


A Procedure Builder Interpreter script file.


A PL/SQL library file that contains source code and compiled code. The file can be opened in Procedure Builder for editing.


A text file that contains the PL/SQL source of a single program unit.


A runtime PL/SQL library file that contains executable code only.  The file cannot be opened in Procedure Builder for editing.


A list that pops up when the user performs a particular action.


A number that TCP uses to route transmitted data to and from a particular program.


An action shipped with Project Builder and automatically available to the user via a menu item and/or a toolbar button.  Pre-defined actions include Build, Deliver, and several source control options.  When a pre-defined action is defined for a supported file type, the action is invoked for any selected item of that type when the user calls the action from Project Builder.  See also:  action, user-defined action.


See built-in datatype.


A setting that affects the behavior of the application's interface.


(Oracle Express) View the script that would be generated if you accept the current criteria. In the dialog box for any Selector tool you can preview your selection by choosing the Preview button.


The interface with which you view and scroll through report output online.


A column in a database table whose members consist of unique values that can be used to identify a row in a table.


See built-in datatype.


In a printer definition file, an escape sequence to which you assign a printer code that can be referenced in a report.


A file that contains a printer definition in text (e.g., ASCII or EBCDIC) format.


A PL/SQL subprogram that performs a specified sequence of actions. .  Can reside and execute on the client and the database server.


A PL/SQL code structure that can be independently recognized and processed by the PL/SQL compiler.  Anonymous blocks, subprogram specifications and bodies (procedures and functions), and package specifications and bodies are types of program units.  Program units can reside and execute on the client and the database server.  See also:  stored program unit.


The basic data structure created by Project Builder.  Projects are collections of pointers to all the files you consider part of your application, or otherwise want to group together conceptually.  You can define the editors, compilers, and other tools you use to work with the items contained within a project.  All project information is stored within a project registry.  See also:  project item, project file, export.


In Project Builder, project files are all the files associated with an application.  Project files can be of any type, including forms, reports, displays, 3GL modules, documentation, and test scripts. See also:  project, project item.


In Project Builder, anything for which properties may be defined, including all entities stored under the Projects node, types, actions, and macros. See also: project, project file.


The window containing a hierarchical list of project items for the current session.  The list appears in outline form, and enables the user to accomplish several tasks such as creating, editing, renaming, and deleting objects.  Although only one is visible at any time, the user can choose from two different schema by which to organize the objects.


The top-level node for a project.  It represents or points to the project file.  See also: project, project file.


In Project Builder, the file that stores all the information associated with a project:  files belonging to the project, types, actions, and macros defined for the project, and so on.


The project view shows objects organized by their type, and by their project/subproject relationships.  The projects are organized alphabetically by project file, then alphabetically by category.  See also:  dependency view, project, project file, view.


A dialog that assists the user in accomplishing the steps necessary to create a new project or sub project.


A characteristic of an object that determines the behavior or appearance of that object.


A named object that contains a list of properties and their settings used to globally control the appearance and functionality of objects based on that class.


A string you can enter when connecting to a database or server that allows you to connect to a remote database or server.


(Oracle Express) When you select values for one of the dimensions in a measure, the other dimensions that make up that measure are known as qualifying dimensions.

Suppose your Sales measure is dimensioned by Product, Month, and Geography. If you select the top ten cities based on Sales, you must also specify which product and month you want to consider when you compare Sales values. In this case, Product and Month are the qualifying dimensions.


A SQL SELECT statement that specifies the data you wish to retrieve from one or more tables or views of a database.


A PL/SQL function that, when executed, filters data retrieved by a query.  Only the data that meet the conditions in the function are charted.


An option that terminates the current session and returns the user to the operating system.  On some systems, Quit is Exit.


A control (similar to a check box), appearing in sets of two or more, only one of which may be either "on" or "off" at any given time.


A set of two or more radio buttons, only one of which may be either "on" or "off" at any given time.


(Oracle Express) A Selector dialog box tool that allows the user to select consecutive time periods as dimension values. These time periods can be based on any of the following:

•	A specific number of the most recent time periods

•	A beginning time period and a most recent time period

•	A beginning and ending time period

For example, the user can select dimension values for the range from the week ending November 25, 1996 through the week ending December 30, 1996.


A cipher designed by RSA Data Security, Inc. which can accept keys of arbitrary length, and is essentially a pseudo random number generator with the output of the generator being XORed with the data stream to produce the encrypted data.  For this reason, it is very important that the same RC4 key never be used to encrypt two different data streams.


Acronym for Relational Database Management System.  A database that allows the definition of data structures, storage and retrieval operations, and integrity constraints.  In such a database, data and relations between them are organized in tables.


A file that contains a single report definition in binary format.  .RDF files are used to both run and edit reports.


A file that contains a single report definition in binary format.  .rep files are used solely to run reports; you cannot edit a .rep file.


The ability to query the data throughout a database as of a single point in time.


One row fetched by a SQL SELECT statement.


An internal data structure object with a column/row framework, that belong to the form module in which they are defined.


A type of column that points to data in other column objects or object tables (Oracle8).


A line that appears at a specified value on a chart.


(Oracle Express) Fetch the most recent data from an Express database after query results are displayed in your report. When you open a saved Express query, the results are refreshed automatically.


To add the definition of a type or a new project to either the global or local registry.  Upon being registered, a new type can have actions defined for it, while a new project can have its referenced files identified as specific types, so that actions can be invoked against them.  See also:  registry.


A global and/or user-specific configuration file used to store project definitions and environment information.  See also:  Global Registry, user registry.


A symbol used in search criteria to indicate a comparison between two values, such as the equal sign in "WHERE DEPTNO = 10." Rows in which the comparison results in "true" are returned in the result (fetched), while rows in which the comparison returns "false" are rejected from the result.


A database on a computer other than the local database.  Usually a computer on the same network, but at a different node (i.e., a database that you use through a database link).


A layout object used to display rows of data that are fetched for a group.


A mode in which each character you type replaces the current character at the cursor.  The opposite of insert mode.


The objects that are used to define a report's data model and layout.  Report-level objects are assigned to a single report, and cannot be shared by other reports or other Oracle products. Objects include reports, queries, external queries, external PL/SQL libraries, groups, columns, parameters, links, frames, repeating frames, fields, boilerplate, and anchors.


Available on Windows NT and Windows 95 only, waits for any command lines to run a report, then places that report in its queue to run in the background on the local server.  Typically command lines are received from Form Builder or Graphics Builder via RUN_PRODUCT, or from another report via SRW.RUN_REPORT.  You can also use RWISV60 to submit a report to the Reports Background Engine.


Maintains timestamp and status information about reports managed by the Reports Server.


Available on Windows NT, Windows 95, and UNIX, enables running reports on a remote server.  Queues job requests and allows you to schedule when to run reports.  Use RWCLI60 to send a report to the Reports Server.


Provides an interface between your Web Server and Reports Runtime, enabling you to run reports dynamically from your Web browser.


Provides a connection between a Web Server and the Reports Server.


A file that contains a report definition stored in text (e.g., ASCII or EBCDIC) format.  .REX files are used to port reports from one platform to another. Note that .REX files are no longer required. They are available for backward compatibility.


Refers to the intensities of the red, green, and blue components of a color.


The group object to which all other objects in an application belong.


Top-level node for a project representing user's environment.  May correspond to the user registry or the Global Registry, depending on which registry has been chosen to set defaults.


1. One set of field values in a table; for example, the fields representing one employee in the example table EMP.  2.  To generate a runtime version of an application.


An object in an Oracle8 object table.  Each row in the table is an object.  However, in Oracle Developer an object table is deconstructed into individual columns, so that the row object no longer exists as a single entity (only as its separate attributes).


To execute a runtime version of an application or program unit.


Acronym for Rich Text Format.  A non-platform-specific file format based on control words used to represent unformatted text and images in various applications and operating systems.  RTF uses the ANSI, PC-8, Macintosh, or IBM PC character set to control the representation and formatting of a document, both on the screen and in print.


See rep file.


The interface in which users view and interact with a runtime application.


A screen or window appearing optionally at runtime in which a user can modify print options and parameters prior to report execution.


(Oracle Express) A set of dimension values that has been saved either as a list of values or as a script. You can save selections that you build, or your database administrator can create saved selections and make them available to you.

Saved selections are a time-saving feature: each time that you need to re-use a selection, you can simply retrieve a saved selection without having to recreate it.


(Oracle Express) A Selector tool that allows you to retrieve a selection of dimension values that has been saved.


A collection of related database objects, usually grouped by database userid.  Schema objects includes tables, views, sequences, stored program units, synonyms, indexes, clusters, and database links.


The level at, or range in which, an object operates.  For Project Builder:  1.  Describes the range of files affected by Compile and Compile All commands invoked against compilable project items.  2:  Describes the range of files influenced by inheritable definitions.


See SQL script, Interpreter script.


In Report Builder, one of multiple layouts in the same report, each with a different target audience, output format, page layout, page size, or orientation.  For example, a single report can include an executive summary for senior management in one section and also a detailed breakdown for  individual managers in another section.


A SQL statement that specifies which rows and columns to fetch from one or more tables or views.


(Oracle Express) The set of dimension values currently chosen for a dimension, or the script that contains conditions or criteria to specify those values.


(Oracle Express) As shown on various dialog boxes in the Selector, a description of the choices that a user has made in selecting dimension values. It is a translation, in ordinary language, of the Express Language script.


(Oracle Express) A set of tools that you use to choose the dimension values to include, for instance, in a report, table, graph, or dimension list box. For example, you can use the Selector to choose the top 10 cities based on Sales or those cities whose Sales exceeded Quota by 15 percent. The Selector also allows you to sort dimension values and to create and retrieve saved selections.


(Oracle Express) A dialog box or group of dialog boxes that provides a particular way of selecting or sorting dimension values. Each Selector tool is part of the Selector. You can use Selector tools to select dimension values based on their level in the hierarchy, their attributes, the characters in the value name, and so on. You can also use Selector tools to sort the dimension values.


The period between invoking and quitting the executable.


One of two or more objects that have the same parent object in its group tree.  All objects that belong to one group object are siblings.


The combination of an IP address and a port number.


(Oracle Express) A Selector dialog box tool that allows you to rearrange the order of dimension values in a displayed selection. You can sort a selection in ascending or descending order by the following:

•	Alphabet

•	Order in the database

•	Data value

•	Order or level in the hierarchy

•	Time period

You can also sort a selection manually, by dragging and dropping dimension values.


In PL/SQL:  Statements provided in a subprogram or package.  You must have the source code for a program unit before you can compile it into executable form.  In Project Builder:  The input types required to build target types.


Defines only the names, parameters, and return type (applies to functions only) of the subprogram.


A small rectangle at the bottom of the vertical scrollbar and to the left of the horizontal scrollbar in an editor.  Dragging and releasing the mouse button creates a new pane, and divides the scroll bar into separate scroll bars for each pane.


A standard interface for storing and retrieving information in a relational database.  SQL is an acronym for Structured Query Language.


A that contains a query stored in text (e.g., ASCII or EBCDIC) format.


A file containing SQL statements that you can run to perform database administration quickly and easily.  Several SQL scripts are shipped with Oracle products.


A SQL instruction to Oracle.  A SELECT statement is one type of SQL statement.


See call stack.


A PL/SQL construct used for conditional, iterative, and sequential control, and for error handling.  A semi-colon (;) must terminate every PL/SQL statement.


(Oracle Express) A saved selection that contains the same dimension values every time it is evaluated. Static saved selections list the dimension values that are to be selected, rather than the selection criteria. For example, a static saved selection script might include "Select February 1996, March 1996, and April 1996", while the script for a dynamic saved selection might have "Select the last three Months".


A procedure, function, or package that resides and executes in the Oracle database server.


A procedure or function that resides and executes in the Oracle database server.


HTML extensions that provide powerful formatting flexibility in HTML documents.  To view an HTML document that takes advantage of style sheets, display it in a browser that supports style sheets.


A PL/SQL procedure or function.


In Project Builder, a project contained within another project file, rather than being stored in its own file.  See also:  project.


In Project Builder, a node denoting a subproject.  See also:  project, project node, subproject node.


A column, with a type of summary, which computes subtotals, grand totals, running totals, and other summaries of the data in a report, using one of the packaged summary functions provided by Report Builder.


The file format used by the Microsoft Excel program.


The orderly system by which commands, qualifiers, and parameters are combined to form valid command strings.


One of the variables that are provided with Oracle Developer (e.g., &Logical Page, DESTYPE).


A named collection of related information, stored in a relational database or server, in a two-dimensional grid that is made up of rows and columns.


A collection type, which defines a data unit made up of an unordered set of elements, all of the same data type.  The corresponding data unit is a single column nested table, the column type of which is a built-in type or an object type.  (Oracle8)


A default layout displaying labels at the top of the page and rows of data underneath the labels.


In Project Builder, any item in the middle of the dependency tree; for example, an executable is a (compile) target for a library; while a library is a target for a group of objects; and an object is a target for a source file.


A node denoting a target.  See also: target.


Acronym for Transmission Control Protocol. The underlying communication protocol for exchanging HTTP requests between clients and Web servers.


A submenu that the user can remove from its source using a mouse or other pointing device and drag to another part of the display screen.


In Form Builder, an item that displays a character string value.


The horizontal area at the top of a window that displays the name of the application or interface element in that window.


See header.


To turn a setting alternately on or off.  For example, you can hide or show the Object Navigator.


An iconic button used to create and manipulate objects in an application.


Collection of iconic buttons that perform product commands.  Usually aligned horizontally along the top, or vertically down the side of a window.


A collection of tools.


(Oracle Express) A Selector dialog box tool that allows the user to select dimension values based on the top x, bottom y, or top x and bottom y data values. For example, the user can produce a dimension selection that contains products whose Volume Sales were among the top 10 percent of products in the Total U.S. for the four-week time period ending December 30, 1995.


A optional report region that can contain closing material for the report, including text, graphics, data, and computations.  The report trailer appears last, following the header and body.


A sequence of SQL statements treated as a single unit.


A PL/SQL procedure that is executed, or "fired," upon a specific event.


A description of a file type, such as a form, a document, etc., containing such information as type name and description. Each description applies to a single file type.  In addition, there are four meta-types: "updtext", which applies to all text files, “updproj” which applies to all project files, “updlink”, which applies to all project links, and "all" which applies to any file type.  Types are the foundation for defining actions and macros.


To change the values for table data, in particular, by altering data values using the SQL command UPDATE, but also by deleting values using the SQL command DELETE or by inserting values using the command INSERT.


Acronym for Uniform Resource Locator. The "address" used to specify a WWW server and home page.  For example:
http://www.acme.com/
which indicates that the host's address is www.acme.com. An URL most often is a filename (possibly with a long path to it and usually with an extension of .HTML, or .HTM (for PC-DOS filenames).


A way in which to pass control (and possibly arguments) from Oracle Developer to another Oracle product or 3GL, and then return control (and possibly arguments) back to Oracle Developer.


A custom action defined by a Project Builder user.  Such actions may apply to any single file type, or to all file types.  See also:  action, pre-defined action.


See object type.


A custom macro defined by a Project Builder user.  Such macros may be used to modify both built-in actions and user-defined actions.  See also:: macro, built-in macro, action, pre-defined action.


A project file storing configuration information on a per-user basis.  This enables users to customize their individual development environments.  The user registry inherits type information from the Global Registry, and may define new types as well as override aspects of type definitions stored in the Global Registry.  It also stores environment and preference information, such as the user's preferred connection string, UI settings such as "Display Toolbar" and certain general project information such as "Author."  See also:  registry, Global Registry.


See continuous axis.


A PL/SQL code structure that returns a value.  Value constructs include functions and expressions.


A named object that can be assigned a value and whose assigned value may change over time.


A collection type, which defines a data unit made up of an ordered set of elements, all of the same datatype.  The corresponding data unit is a varying array or VARRAY.  The number of elements in a VARRAY (size) is variable.  However, you must specify a maximum size when you declare a varying array type.


Visual Basic extension.  Used as the file extension for special dynamic link libraries distributed on files that contain predefined VBX controls.


A widget, built with the Microsoft Visual Basic language, used to enhance the user interface, obtain user input, and display output  (e.g. sliders, grids, and control knobs).


A virtual table whose rows do not actually exist in the database, but which is based on a table that is physically stored in the database.


A directory mnemonic (essentially a shortcut or synonym) that the virtual file system uses to map files stored in the file system on the host machine.


A mapping that associates the pathnames used in URL to the file system maintained by the host machine's operating system.


The font, color, and pattern properties that you set for objects that appear in your application interface.


See WWW.


A program that end users utilize to read HTML documents and programs stored on a computer (serviced by a Web server).


A program executed on a Web server via the Web Request Broker.


A server process (HTTP daemon) running at a Web site which sends out Web pages in response to HTTP requests from remote Web browsers.


A character used to mean 'any one character' or 'a contiguous set of characters' within a word or phase.


1. A rectangular area of the desktop that contains an application.  Each window has an area where you can interact with the application.  Windows can be opened, resized, moved, reduced to an icon, or enlarged to fill the entire desktop.  2. In Form Builder, an object type you can associate with a canvas view.


The file format used by some spreadsheet programs, such as SQL*Calc, or by Lotus 1-2-3 programs.


Acronym for Oracle Web Request Broker.  Provides a powerful distributed runtime environment for developing and deploying applications for the Web.  The WRB runtime platform enables application developers to write applications that are independent of, and work with a number of, Web servers.


Acronym for World Wide Web.  The network of servers on the Internet, each of which has one or more home pages, which provide information and links to other documents on that and (usually) other servers.


To expand an object to allow more room for editing the contents of the field.


The secondary toolbar docked (by default) to the left of the Project Navigator.  It provides simple organization and application launching abilities.


 the latest version of OLE controls (OCX)


XML output complying with general XML principles such as proper tagging, nesting, and the inclusion of an XML declaration, e.g. <?xml version="1.0" encoding="UTF-8"?>.


A placeholder username enables users to log on to the database using their personal username rather than the Oracle database username (e.g., $user_name@database) when running reports from a Web browser.


Extensible Markup Language -- a metalanguage using SGML to define and structure data. Report Builder supports XML output to enable Web publishing as well as electronic data exchange with third-party applications. You can also use XML to build report definitions that can be merged with other report definitions at runtime or run separately


XML output with structure and element content conforming to a document type definition (DTD). Valid XML is also well-formed.


Connect Dialog Box

Use the Connect dialog box to specify information about connecting to Express.

This dialog box is not translated in all languages.

Dialog Box Components

Express Server box -- Specifies the Express Server connection that you want to establish.

Authentication box -- Allows you to enter the domain, user ID, and password for the Express Server. Some or all of these boxes might be dimmed, depending on the Express Server connection that you selected.

Domain box -- Enter your domain name on the remote system. This component appears only if a domain login is required.

User ID box -- Enter your user ID on the remote system.

Password box -- Enter your password on the remote system.

RDBMS Connection box -- Allows you to enter the user ID, password, and Express ID for the RDBMS. The Express ID box might be dimmed, depending on the Express Server connection that you selected.

User ID box -- Enter your user ID for the RDBMS.

Password box -- Enter your password for the RDBMS.

Express ID box -- Enter your Express ID for the RDBMS.


Reports Runtime Help


RWRUN60

 Command Line Arguments 	 Related Topics

Description  RWRUN60 runs a report (i.e., .rdf or .rep file) interactively or in batch.

Syntax:

RWRUN60 [ [keyword=]value|(value1, value2, ...) ]

where keyword=value is a valid command line argument.

Usage Notes

•	If you are running an .rep file, the PL/SQL is already compiled and will not be recompiled.  If you are running an .rdf file, the PL/SQL is automatically recompiled if necessary (i.e., you didn't compile and save the report from Report Builder, or the platform or version on which you are running the report is incompatible with the platform on which it was last compiled and saved).

•	There are two versions of RWRUN60.  It is important to note that with either executable, you can run character-mode or bit-mapped reports.  The only limiting factor is the output device (e.g., you could not run a bit-mapped report to the screen of a vt220).

•	The character-mode executable is for users who are running reports from character-mode machines (e.g., VT220).

•	The GUI executable is for users who are running reports from bit-mapped machines (e.g., a PC running Windows).


RWRUN60 Command Line Arguments

[MODULE|REPORT=]runfile

[USERID=]userid

[PARAMFORM=]{YES|NO}

[CMDFILE=]cmdfile

[TERM=]termfile

[ARRAYSIZE=]n

[DESTYPE=]{SCREEN|FILE|PRINTER|PREVIEW|SYSOUT|MAIL}]

[DESNAME=]desname

[DESFORMAT=]desformat

[CACHELOB=]{YES|NO}

[COPIES=]n

[CURRENCY=]currency_symbol

[THOUSANDS=]thousands_symbol

[DECIMAL=]decimal_symbol

[READONLY=]{YES|NO}

[LOGFILE=]logfile

[BUFFERS=]n

[BATCH=]{YES|NO}

[PAGESIZE=]width x height

[PROFILE=]profiler_file

[RUNDEBUG=]{YES|NO}

[ONSUCCESS=]{COMMIT|ROLLBACK|NOACTION}

[ONFAILURE=]{COMMIT|ROLLBACK|NOACTION}

[KEYIN=]keyin_file

[KEYOUT=]keyout_file

[ERRFILE=]error_file

[LONGCHUNK=]n

[ORIENTATION=]{DEFAULT|LANDSCAPE|PORTRAIT}

[BACKGROUND=]{YES|NO}

[MODE=]{BITMAP|CHARACTER|DEFAULT}

[PRINTJOB]{YES|NO}

[TRACEFILE=]tracefile

[TRACEMODE=]{TRACE_APPEND|TRACE_REPLACE}

[TRACEOPTS=]{TRACE_ERR|TRACE_PRF|TRACE_APP|TRACE_PLS|
TRACE_SQL|TRACE_TMS|TRACE_DST|TRACE_ALL|(opt1, opt2, ...)}

[AUTOCOMMIT=]{YES|NO}

[NONBLOCKSQL=]{YES|NO}

[ROLE=]rolename/[rolepassword]

[BLANKPAGES=]{YES|NO}

[DISABLEPRINT=]{YES|NO}

[DISABLEMAIL=]{YES|NO}

[DISABLEFILE=]{YES|NO}

[DISABLENEW=]{YES|NO}

[DELIMITER=]value

[CELLWRAPPER=]value

[DATEFORMATMASK=]mask

[NUMBERFORMATMASK=]mask

[DESTINATION=]filename.DST

[DISTRIBUTE=]{YES|NO}

[PAGESTREAM=]{YES|NO}

EXPRESS_SERVER="server=[server]/domain=[domain]/user=[userid]/password=[passwd]"

[CUSTOMIZE]=filename.xml | (filename1.xml, filename2.xml, . . .)

[SAVE_RDF]=filename.rdf

<param>=value


MODULE/REPORT
MODULE|REPORT

  Restrictions	  Related Topics

Description  MODULE|REPORT is the name of the report to run.  (REPORT is allowed for backward compatibility.)

Syntax

[MODULE|REPORT=]runfile

Values

Any valid runfile (i.e., a file with an extension of .rdf or .rep) or an XML report definition (.xml file).  If you do not enter a file extension, Reports Runtime searches first for a file with extension .rep, then extension .rdf, and then no extension.  Reports Runtime will use its file path search order to find the file.

Usage Notes

•	To run the report, it must be a complete report definition (i.e., contain its own data model and layout definition). You cannot run a partial report definition.

•	An XML report definition must have an .XML file extension when specified with the MODULE|REPORT keyword.


MODULE|REPORT Restrictions

  Related Topics

•	If you specify a runfile using MODULE|REPORT, the RWRUN60 window is not raised.  (This behavior provides seamless entry into RWRUN60 from other applications.)  If you do not specify a runfile using MODULE/REPORT and you specify BATCH=NO, the RWRUN60 window is opened, which enables you to run reports interactively.

•	If you run a character-mode report via bit-mapped RWRUN60, Reports Runtime displays a warning, then runs the report using a page size of 8.5" x 11" and a form size of 7" x 6".


PARAMFORM

  Related Topics

Description  PARAMFORM specifies whether to display the Runtime Parameter Form when you execute a report.

Syntax

[PARAMFORM=]{YES|NO}

Values

YES means to display the Form.

NO means to suppress the Form.

Default

YES

Usage Notes

PARAMFORM=YES is incompatible with BATCH=YES because it is not meaningful to have the Runtime Parameter Form appear in batch mode.


CMDFILE

  Restrictions 	  Related Topics

Description  CMDFILE is a file that contains arguments for the RWRUN60 command.  This option enables you to run a report without having to specify a large number of arguments each time you invoke RWRUN60.

Syntax

[CMDFILE=]cmdfile

Values

Any valid command file.


CMDFILE Restrictions

•	A command file may reference another command file.

•	Command file syntax for RWRUN60 arguments is identical to that used on the command line.

•	Values entered on the command line override values specified in command files.  For example, suppose that you specify RWRUN60 from the command line with COPIES equal to 1 and CMDFILE equal to RUNONE (a command file).  In RUNONE, COPIES is set to 2.  Only one copy of the report would be generated in this case.

•	The argument(s) for this keyword may be operating system-specific.


TERM

  Related Topics

Description  TERM is the type of terminal on which you are using RWRUN60.  TERM is useful for the Runtime Parameter Form and Runtime Previewer only.  This keyword is only used in character mode.

Syntax

[TERM=]termtype

Values

Any valid terminal type.

Default

Installation dependent.  (See your System Administrator for a compatible definition.)

Usage Notes

•	The argument(s) for this keyword may be case sensitive, depending on your operating system.


ARRAYSIZE

  Related Topics

Description  ARRAYSIZE is the size (in kilobytes) for use with ORACLE array processing.  Generally, the larger the array size, the faster the report will run.

Syntax

[ARRAYSIZE=]n

Values

A number from 1 through 9,999.  This means that Reports Runtime can use this number of kilobytes of memory per query in your report.

Default

The default array size is 10K.  For details about the ORACLE array processing, see the Oracle8 Server Administrator's Guide.


DESTYPE

  Related Topics

Description  DESTYPE is the type of device that will receive the report output.

Syntax

[DESTYPE=]{SCREEN|FILE|PRINTER|PREVIEW|SYSOUT|MAIL}

Values

SCREEN	Routes the output to the Previewer for interactive viewing.  This value is valid only when the BATCH=NO.  Font aliasing is not performed for Screen.
FILE	Saves the output to a file named in DESNAME (the next keyword discussed).
PRINTER	Routes the output to the printer named in DESNAME (the next keyword discussed).
PREVIEW	Routes the output to the Previewer for interactive viewing.  However, Preview causes the output to be formatted as PostScript output.  The Previewer will use DESNAME to determine which printer's fonts to use to display the output.  Font aliasing is performed for Preview.
SYSOUT	Sends the output to your operating system's default output device.  This value is valid only when BATCH=YES.
MAIL	Sends the output to the mail users specified in DESNAME.  You can send mail to any mail system that is MAPI compliant or has the service provider driver installed.  The report is sent as an attached file.
Default

Taken from the Initial Value property of the DESTYPE parameter.

Usage Notes

•	If you set DESTYPE to PRINTER, FILE, or MAIL, the Print Job dialog box will appear after you accept the Runtime Parameter Form, unless it is suppressed.  After you accept the Print Job dialog box, the report is executed and the output is sent to the  printer (specified in File [image] Choose Printer), file, or mail ID.  (If DESTYPE is something other than PRINTER, FILE, or MAIL, then the report is executed after you accept the Runtime Parameter Form.)  The appearance of the dialog box varies between operating systems.

•	In some cases, this parameter may be overridden by your operating system.

•	Some DESTYPE values are not supported on some operating systems.


DESNAME

  Related Topics

Description  DESNAME is the name of the file, printer, or email ID (or distribution list) to which the report output will be sent.  To send the report output via email, specify the email ID as you do in your email application (any MAPI-compliant application on Windows or your native mail application on UNIX).  You can specify multiple usernames by enclosing the names in parentheses and separating them by commas (e.g., (name, name, . . .name)).

Syntax

[DESNAME=]desname

Values

Any valid filename, printer name, or email ID not to exceed 1K in length.  For printer names, you can optionally specify a port.  For example:

DESNAME=printer,LPT1:

DESNAME=printer,FILE:

Default

Taken from the Initial Value property of the DESNAME parameter.  If DESTYPE=FILE and DESNAME is an empty string, it defaults to reportname.lis at runtime.

Usage Notes

•	This keyword is ignored if DESTYPE is SCREEN or SYSOUT.

•	If DESTYPE is PREVIEW, Reports Runtime uses DESNAME to determine which printer's fonts to use to display the output.

•	The argument(s) for this keyword may be case sensitive, depending on your operating system.

•	In some cases, this parameter may be overridden by your operating system.


DESFORMAT

  Related Topics

Description  In bit-mapped environments, DESFORMAT specifies the printer driver to be used when DESTYPE is FILE.  In character-mode environments, it specifies the characteristics of the printer named in DESNAME.

Syntax

[DESFORMAT=]desformat

Values

Any valid destination format not to exceed 1K in length.  Examples of valid values for this keyword are hpl, hplwide, dec, decwide, decland, dec180, dflt, wide, etc.  Ask your System Administrator for a list of valid destination formats..   In addition, Report Builder supports the following destination formats:

PDF	Means that the report output will be sent to a file that can be read by a PDF viewer.  PDF output is based upon the currently configured printer for your system.  The drivers for the currently selected printer is used to produce the output;  you must have a printer configured for the machine on which you are running the report.
HTML	Means that the report output will be sent to a file that can be read by an HTML 3.0 compliant browser (e.g., Netscape 2.2).
HTMLCSS	Means that the report output sent to a file will include style sheet extensions that can be read by an HTML 3.0 compliant browser that supports cascading style sheets.
HTMLCSSIE	Means that the report output sent to a file will include style sheet extensions that can be read by Microsoft Internet Explorer 3.x.
RTF	Means that the report output will be sent to a file that can be read by standard word processors (such as Microsoft Word).  Note that when you open the file in MS Word, you must choose View [image] Page Layout to view all the graphics and objects in your report.
XML	Means that the report output will be an XML document, saved as a separate file with the .XML extension. This report can be opened and read in an XML-supporting browser, or your choice of XML viewing application.
DELIMITED	Means that the report output will be sent to a file that can be read by standard spreadsheet utilities, such as Microsoft Excel.  Note that you must also specify a DELIMITER.
Default

Taken from the Initial Value property of the DESFORMAT parameter.  For bit-mapped Reports Runtime, if DESFORMAT is blank or dflt, then the current printer (specified in File [image] Choose Printer) is used.  If nothing has been selected in Choose Printer, then Postscript is used by default.

Usage Notes

•	This keyword is ignored if DESTYPE is SCREEN or SYSOUT.

•	The value(s) for this keyword may be case sensitive, depending on your operating system.


COPIES

  Related Topics

Description  COPIES specifies the number of copies of the report output to print.

Syntax

[COPIES=]n

Values

Any valid integer from 1 through 9,999.

Default

Taken from the Initial Value property of the COPIES parameter.

Usage Notes

•	This keyword is ignored if DESTYPE is not Printer.

•	If COPIES is left blank on the Runtime Parameter Form, it defaults to one.


CACHELOB

  Related Topics

Description  CACHELOB specifies whether to cache retrieved Oracle8 large object(s) in the temporary file directory (specified by REPORTS60_TMP).

Values

YES means to cache the LOB in the temporary file directory.

NO means to not cache the LOB in the temporary file directory.

Default

YES

Usage Notes

•	You can only set this option on the command line.

•	If the location of the temporary file directory does not have sufficient available disk space, it is preferable to set this value to NO.  Setting the value to NO, however, may decrease performance, as the LOB may need to be fetched from the server multiple times.


CURRENCY

  Related Topics

Description  CURRENCY is the currency character to be used in number formats.

Syntax

[CURRENCY=]currency_symbol

Values

Any valid alphanumeric string not to exceed 1K in length.

Default

The default for ORACLE is determined by the ORACLE National Language Support facilities.  You can also set a default of up to four characters in the Initial Value field of the Parameter property sheet for the CURRENCY parameter.

Usage Notes

•	A CURRENCY value entered on the Runtime Parameter Form will override any CURRENCY value entered on the command line.


THOUSANDS

  Related Topics

Description  THOUSANDS is the thousands character to be used in number formats.

Syntax

[THOUSANDS=]thousands_symbol

Values

Any valid alphanumeric character.

Default

The default for ORACLE is determined by the ORACLE National Language Support facilities.  You can also set a default in the Initial Value property of the THOUSANDS parameter.

Usage Notes

•	A THOUSANDS value entered on the Runtime Parameter Form will override any THOUSANDS value entered on the command line.

• 	The alphanumeric character defined as the THOUSANDS value is the actual value that is returned. For example, if you define "," as the THOUSANDS value, "," is returned.


DECIMAL

  Related Topics

Description  DECIMAL is the decimal character to be used in number formats.

Syntax

[DECIMAL=]decimal_symbol

Values

Any valid alphanumeric character.

Default

The default for ORACLE is determined by the ORACLE National Language Support facilities.  You can also set a default in the Initial Value property for the DECIMAL parameter.

Usage Notes

•	A DECIMAL value entered on the Runtime Parameter Form will override any DECIMAL value entered on the command line.

• 	The alphanumeric character defined as the DECIMAL value is actual value that is returned. For example,  if you define “.”  as the DECIMAL value, “.” is returned.


READONLY

  Related Topics

Description  READONLY requests read consistency across multiple queries in a report.  When accessing data from ORACLE, read consistency is accomplished by a SET TRANSACTION READ ONLY statement (refer to your Oracle8 Server SQL Language Reference Manual for more information on SET TRANSACTION READ ONLY).

Syntax

[READONLY=]{YES|NO}

Values

YES requests read consistency.

NO means do not provide read consistency.

Default

NO

Usage Notes

•	READONLY is only useful for reports using multiple queries, because ORACLE automatically provides read consistency, without locking, for single query reports.


LOGFILE

  Related Topics

Description  LOGFILE is the name of the file to which File [image] Print Screen output is sent.  If the specified file already exists, output will be appended to it.  This keyword is only used in character mode.

Syntax

[LOGFILE=]logfile

Values

Any valid filename.

Default

dfltrep.log in the current directory.


BUFFERS

  Related Topics

Description  BUFFERS is the size of the virtual memory cache in kilobytes.  You should tune this setting to ensure that you have enough space to run your reports, but not so much that you are using too much of your system's resources.

Syntax

[BUFFERS=]n

Values

A number from 1 through 9,999.  For some operating systems, the upper limit may be lower.

Default

640K

Usage Notes

•	If this setting is changed in the middle of your session, the change does not take effect until the next time the report is run.


BATCH

  Related Topics

Description  BATCH suppresses all terminal input and output, in order to run reports without user intervention.  BATCH=YES enables you to run the report without bringing up the RWRUN60 interface.  To run reports in the background, see BACKGROUND.

Syntax

[BATCH=]{YES|NO}

Values

YES suppresses all terminal input and output.

NO allows special terminal input and output.

Default

NO

Usage Notes

•	If BATCH=YES, error messages are sent to SYSOUT.   For more information on SYSOUT, see DESNAME.

•	If BATCH=YES, PARAMFORM=YES is invalid because it is not meaningful to have the Runtime Parameter Form appear in batch mode.

•	When BATCH=NO and you are using the character-mode RWRUN60, bit-mapped reports cannot be run.  (It is not possible to run a bit-mapped report to the screen of a character-mode device.)

•	When BATCH=YES, MODE=BITMAP, and you are using the character-mode RWRUN60, you cannot run a character-mode report.


PAGESIZE

  Related Topics

Description  PAGESIZE is the dimensions of the physical page (i.e., the size of the page that the printer outputs).  Note that the page must be large enough to contain the report.  For example, if a frame in a report expands to a size larger than the page dimensions, the report will not run.

Syntax

[PAGESIZE=]width x height

Values

Any valid page dimensions of the form:  page width x page height, where page width and page height are zero or more.  The maximum width/height depends upon the unit of measurement.  For inches, the maximum width/height is 512 inches.  For centimeters, it is 1312 centimeters.  For picas, it is 36,864 picas.

Default

For bitmap, 8.5 x 11 inches.  For character mode, 80 x 66 characters.  If the report was designed for character mode and is being run or converted on bitmap, the following formula is used to determine page size if none is specified:  (default page size * character page size)/default character page size.  For example, if the character page size is 80 x 20, the bit-mapped page size would be:  (8.5 * 80)/80 x (11 * 20)/66 = 8.5 x 3.33.

Usage Notes

•	On some printers the printable area of the physical page is restricted.  For example, the sheet of paper a printer takes may be 8.5 x 11 inches, but the printer might only be able to print on an area of 8 x 10.5 inches.  If you define a page width x page height in Reports Runtime that is bigger than the printable area your printer allows, clipping may occur in your report output.  To avoid clipping, you can either increase the printable area for the printer (if your operating system allows it) or you can set the page width x page height to be the size of the printable area of the page.

•	If this keyword is used, its value overrides the page dimensions of the report definition.

•	A PAGESIZE value entered on the Runtime Parameter Form will override any PAGESIZE value entered on the command line.


PROFILE

  Related Topics

Description  PROFILE is the name of a file in which you want to store performance statistics on report execution.  If you specify a filename, Reports Runtime calculates statistics on the elapsed and CPU time spent running the report.  PROFILE calculates the following statistics:

•	TOTAL ELAPSED TIME is the amount of time that passes between when you issue RWRUN60 and when it finishes running the report.  TOTAL ELAPSED TIME is the sum of Reports Runtime Time and ORACLE Time.

•	Time is the amount of time spent in Reports Runtime.

•	ORACLE Time is the amount of time spent in the database and is composed of the following:

•	UPI is the amount of time spent to do such things as connect to the database, parse the SQL, and fetch the data.

•	SQL is the amount of time spent performing SRW.DO_SQL.

•	TOTAL CPU Time used by process is the CPU time spent running the report.

Note: For some operating systems, the Reports Runtime time includes the database time because the database is included in Reports Runtime’s process.

Syntax

[PROFILE=]profiler_file

Values

Any valid filename in the current directory.


RUNDEBUG

  Related Topics

Description  RUNDEBUG is whether you want extra runtime checking for logical errors in the report.  RUNDEBUG checks for things that are not errors but might result in undesirable output.  RUNDEBUG checks for the following:

•	frames or repeating frames that overlap but do not enclose another object.  This can lead to objects overwriting other objects in the output.

•	layout objects with page-dependent references that do not have fixed sizing.  Reports Runtime will make such objects fixed in size regardless of the Vertical Elasticity and Horizontal Elasticity property settings.

•	bind variables referenced at the wrong frequency in PL/SQL.

•	the report is character mode or bitmap and the environment is the opposite.

Syntax

[RUNDEBUG=]{YES|NO}

Values

YES means perform extra runtime error checking.

NO means do not perform extra runtime error checking.

Default

NO


ONSUCCESS

  Related Topics

Description  ONSUCCESS is whether you want a COMMIT or ROLLBACK performed when the report is finished executing.

Syntax

[ONSUCCESS=]{COMMIT|ROLLBACK|NOACTION}

Values

COMMIT means perform a COMMIT when the report is done.

ROLLBACK means perform a ROLLBACK when the report is done.

NOACTION means do nothing when the report is done.

Default

COMMIT, if a USERID is provided.

NOACTION, if called from an external source (e.g., Oracle Forms) with no USERID provided.

Usage Notes

•	The COMMIT or ROLLBACK for ONSUCCESS is performed after the After Report trigger fires.  Other COMMITs and ROLLBACKs can occur prior to this one.  For more information, see READONLY.


ONFAILURE

  Related Topics

Description  ONFAILURE is whether you want a COMMIT or ROLLBACK performed if an error occurs and the report fails to complete.

Syntax

[ONFAILURE=]{COMMIT|ROLLBACK|NOACTION}

Values

COMMIT means perform a COMMIT if the report fails.

ROLLBACK means perform a ROLLBACK if the report fails.

NOACTION means do nothing if the report fails.

Default

ROLLBACK, if a USERID is provided.

NOACTION, if called from an external source (e.g., Form Builder) with no USERID provided.

Usage Notes

•	The COMMIT or ROLLBACK for ONFAILURE is performed after the report fails.  Other COMMITs and ROLLBACKs can occur prior to this one.  For more information, see READONLY.


KEYIN

  Related Topics

Description  KEYIN is the name of a keystroke file that you want to execute at runtime.  KEYIN is used to run the keystroke files created with KEYOUT.  Since KEYIN is used to execute a keystroke file, it is only relevant when running in a character-mode environment.

Syntax

[KEYIN=]keyin_file

Values

Any valid key filename in the current directory.


KEYOUT

  Related Topics

Description  KEYOUT is the name of a keystroke file in which you want Reports Runtime to record all of your keystrokes.  You can then use KEYIN to execute the keystroke file.  KEYOUT and KEYIN are useful when you have certain keystrokes that you want to do each time you run a report.  They are also useful for debugging purposes.  Since KEYOUT is used to create a keystroke file, it is only relevant when running reports in a character-mode environment.

Syntax

[KEYOUT=]keyout_file

Values

Any valid filename.


ERRFILE

  Related Topics

Description  ERRFILE is the name of a file in which you want Reports Runtime to store all error messages that are issued during the execution of your report.

Syntax

[ERRFILE=]error_file

Values

Any valid filename.


LONGCHUNK

  Related Topics

Description  LONGCHUNK is the size (in kilobytes) of the increments in which Reports Runtime retrieves a LONG column value.  When retrieving a LONG value, you may want to retrieve it in increments rather than all at once because of memory size restrictions.  LONGCHUNK applies only to Oracle7 and Oracle8.

Syntax

[LONGCHUNK=]n

Values

A number from 1 through 9,999.  For some operating systems, the upper limit may be lower.

Default

10K


ORIENTATION

  Related Topics

Description  ORIENTATION controls the direction in which the pages of the report will print.

Syntax

[ORIENTATION=]{DEFAULT|LANDSCAPE|PORTRAIT}

Values

DEFAULT means use the current printer setting for orientation.

LANDSCAPE

PORTRAIT

Default

DEFAULT

Usage Notes

•	If ORIENTATION=LANDSCAPE for a character-mode report, you must ensure that your printer definition file contains a landscape clause.

•	Orientation settings are ignored when outputting reports to a PCL printer on Motif. The report is processed using the default settings.


BACKGROUND

  Related Topics

Description  BACKGROUND specifies whether the report should be run in the background.  When BACKGROUND is YES, another process is spawned.  This option is useful when you want to work on something else in the foreground while the report runs.  On Windows, specifying BACKGROUND=YES means that the report will go into the Reports Background Engine’s queue.

Syntax

[BACKGROUND=]{YES|NO}

Values

YES or NO

Default

NO

Usage Notes

•	On Windows, you can use RWRBE60 to submit a report to the Reports Background Engine for execution.  This is a more efficient method because it incurs less performance overhead than Reports Runtime.  The command line arguments for RWRBE60 are the same as the ones for RWRUN60.

•	On the command line, BACKGROUND=YES is not supported for BATCH=YES, DESTYPE=SCREEN or PREVIEW, or RWBLD60.  If you are using SRW.RUN_REPORT, though, BACKGROUND=YES with BATCH=YES is supported.

•	If you run a report from Reports Runtime (i.e., not the command line or SRW.RUN_REPORT), you should commit database changes you make in the Before Form, After Form, and Validation triggers before the report runs.  When running in this way, these triggers will share the parent process' database connection.  When the report is actually executed, however, it will establish its own database connection.


MODE

  Related Topics

Description  MODE specifies whether to run the report in character mode or bitmap.  This enables you to run a character-mode report from bit-mapped Reports Runtime or vice versa.  For example, if you want to send a report to a Postscript printer from a terminal (e.g., a vt220), you could invoke character-mode RWRUN60 and run the report with MODE=BITMAP.  On Windows, specifying MODE=CHARACTER means that the Reports Runtime ASCII driver will be used to produce editable ASCII output.

Syntax

[MODE=]{BITMAP|CHARACTER|DEFAULT}

Values

BITMAP

DEFAULT means to run the report in the mode of the current executable being used.

CHARACTER

Default

DEFAULT


PRINTJOB

  Related Topics

Description  PRINTJOB specifies whether the Print Job dialog box should be displayed before running a report.

Syntax

[PRINTJOB=]{YES|NO}

Values

YES or NO

Default

YES

Usage Notes

•	When a report is run as a spawned process (i.e., one executable, such as RWRUN60, is called from within another executable, such as RWBLD60), the Print Job dialog box will not appear, regardless of PRINTJOB.

•	When DESTYPE=MAIL,  the Print Job dialog box will not appear, regardless of PRINTJOB.


TRACEFILE

  Related Topics

Description  TRACEFILE is the name of the file in which Reports Runtime logs trace information.

Syntax

[TRACEFILE=]tracefile

Values

Any valid filename.

Default

trace.dat

Usage Notes

•	Trace information can only be generated when running a .rdf file.  You cannot specify logging when running a .rep file.

•	If you specify LOGFILE or ERRFILE as well as TRACEFILE, all of the trace information will be placed in the most recently specified file.  For example, in the following case, all of the specified trace information would be placed in err.log because it is the last file specified in the RWRUN60 command.

rwrun60 MODULE=order_entry USERID=scott/tiger
TRACEFILE=trace.log LOGFILE=mylog.log
ERRFILE=err.log


TRACEMODE

  Related Topics

Description  TRACEMODE indicates whether Reports Runtime should add the trace information to the file or overwrite the entire file.

Syntax

[TRACEMODE=]{TRACE_APPEND|TRACE_REPLACE}

Values

TRACE_APPEND adds the new information to the end of the file.

TRACE_REPLACE overwrites the file.

Default

TRACE_APPEND

Usage Notes

•	Trace information can only be generated when running a .rdf file.  You cannot specify logging when running a .rep file.


TRACEOPTS

  Related Topics

Description  TRACEOPTS indicates the tracing information that you want to be logged in the trace file.

Syntax

[TRACEOPTS=]{TRACE_ERR|TRACE_PRF|TRACE_APP|TRACE_PLS|
TRACE_SQL|TRACE_TMS|TRACE_DST|TRACE_ALL|(opt1, opt2, ...)}

Values

A list of options in parentheses means you want all of the enclosed options to be used.  For example, TRACE_OPTS=(TRACE_APP, TRACE_PRF) means you want TRACE_APP and TRACE_PRF applied.

TRACE_ALL means log all possible trace information in the trace file.

TRACE_APP means log trace information on all the report objects in the trace file.

TRACE_DST means list distribution lists in the trace file.  You can use this information to determine which section was sent to which destination.

TRACE_ERR means list error messages and warnings in the trace file.

TRACE_PLS means log trace information on all the PL/SQL objects in the trace file.

TRACE_PRF means log performance statistics in the trace file.

TRACE_SQL means log trace information on all the SQL in the trace file.

TRACE_TMS means enter a timestamp for each entry in the trace file.

Default

TRACE_ALL

Usage Notes

•	Trace information can only be generated when running a .rdf file.  You cannot specify logging when running a .rep file.


AUTOCOMMIT

  Related Topics

Description  AUTOCOMMIT specifies whether database changes (e.g., CREATE) should be automatically committed to the database.  Note that some non-ORACLE databases (e.g., SQL Server) require that AUTOCOMMIT=YES.

Syntax

[AUTOCOMMIT=]{YES|NO}

Values

YES or NO

Default

NO


NONBLOCKSQL

  Related Topics

Description  NONBLOCKSQL specifies whether to allow other programs to execute while Reports Runtime is fetching data from the database.

Syntax

[NONBLOCKSQL=]{YES|NO}

Values

YES means that other programs can execute while data is being fetched.

NO means that other programs cannot execute while data is being fetched.

Default

YES


ROLE

  Related Topics

Description  ROLE specifies the database role to be checked for the report at runtime.  ROLE is useful for giving you the ability to run reports that query database tables to which you would not normally have access privileges.

Syntax

[ROLE=]rolename/[rolepassword]

Values

A valid role and (optionally) a role password.


BLANKPAGES

  Related Topics

Description  BLANKPAGES specifies whether to suppress blank pages when you print a report.  Use this keyword when there are blank pages in your report output that you do not want to print.

Syntax

[BLANKPAGES=]{YES|NO}

Values

YES means print all blank pages

NO means do not print blank pages

Default

YES

Usage Notes  BLANKPAGES is especially useful if your logical page spans multiple physical pages (or panels), and you wish to suppress the printing of any blank physical pages.


DISABLEPRINT

  Related Topics

Description  DISABLEPRINT specifies whether to disable File [image] Print, File [image] Page Setup, File [image] Choose Printer (on Motif) and the equivalent toolbar buttons in the Runtime Previewer.

Syntax

[DISABLEPRINT=]{YES|NO}

Values

YES or NO

Default

NO


DISABLEMAIL

  Related Topics

Description  DISABLEMAIL specifies whether to disable the Mail menu and the equivalent toolbar buttons in the Runtime Previewer.

Syntax

[DISABLEMAIL=]{YES|NO}

Values

YES or NO

Default

NO


DISABLEFILE

  Related Topics

Description  DISABLEFILE specifies whether to disable the File [image] Generate to File menu in the Runtime Previewer.

Syntax

[DISABLEFILE=]{YES|NO}

Values

YES or NO

Default

NO


DISABLENEW

  Related Topics

Description  DISABLENEW specifies whether to disable the View [image] New Previewer menu to prevent the ability to display a new instance of the Runtime Previewer.

Syntax

[DISABLENEW=]{YES|NO}

Values

YES or NO

Default

NO


DESTINATION

  Related Topics

Description  The DESTINATION keyword allows you to specify the name of a .DST file that defines the distribution for the current run of the report.

Syntax

[DESTINATION=]filename.DST

Values

The name of a .DST file that defines a report or report section distribution.

Usage Notes

•	To enable the DESTINATION keyword, you must specify DISTRIBUTE=YES on the command line.


DISTRIBUTE

  Related Topics

Description  DISTRIBUTE enables or disables distributing the report output to multiple destinations, as specified by the distribution list defined in the report distribution definition or a .DST file.

Syntax

[DISTRIBUTE=]{YES|NO}

Values

YES means to distribute the report to the distribution list.

NO means to ignore the distribution list and output the report as specified by the DESNAME and DESFORMAT parameters.  This is fundamentally a debug mode to allow running a report set up for distribution without actually executing the distribution.

Default

NO

Usage Notes

•	To enable the DESTINATION keyword, you must specify DISTRIBUTE=YES.


 DELIMITER

  Related Topics

Description  DELIMITER specifies the character(s) to use to separate the cells in your report output.

Syntax

[DELIMITER=]value

Values

Any alphanumeric character or string of alphanumeric characters, such as:

,	means a comma separates each cell
.	means a period separates each cell
You can also use any of these four reserved values:

tab	means a tab separates each cell
space	means a space separates each cell
return	means a new line separates each cell
none	means no delimiter is used
You can also use escape sequences based on the ASCII character set, such as:

\t	means a tab separates each cell
\n	means a new line separates each cell
Default

Tab

Usage Notes

This argument can only be used if you’ve specified DESFORMAT=DELIMITED.


 CELLWRAPPER

  Related Topics

Description  CELLWRAPPER specifies the character(s) that displays around the delimited cells in your report output.

Syntax

[CELLWRAPPER=]value

Values

Any alphanumeric character or string of alphanumeric characters.

"	means a double quotation mark displays on each side of the cell
‘	means a single quotation mark displays on each side of the cell
You can also use any of these four reserved values:

tab	means a tab displays on each side of the cell
space	means a single space displays on each side of the cell
return	means a new line displays on each side of the cell
none	means no cell wrapper is used
You can also use escape sequences based on the ASCII character set, such as:

\t	means a tab displays on each side of the cell
\n	means a new line displays on each side of the cell
Default

None

Usage Notes

•	This argument can only be used if you’ve specified DESFORMAT=DELIMITED.

•	The cell wrapper is different from the actual delimiter .


 DATEFORMATMASK

  Related Topics

Description  DATEFORMATMASK specifies how date values display in your delimited report output.

Syntax

[DATEFORMATMASK=]mask

Values

Any valid date format mask

Usage Notes

•	This argument can only be used if you’ve specified DESFORMAT=DELIMITED.


 NUMBERFORMATMASK

  Related Topics

Description  NUMBERFORMATMASK specifies how number values display in your delimited report output.

Syntax

[NUMBERFORMATMASK=]mask

Values

Any valid number format mask

Usage Notes

This argument can only be used if you’ve specified DESFORMAT=DELIMITED.


PAGESTREAM

  Related Topics

Description  PAGESTREAM enables or disables page streaming for the report when formatted as HTML or HTMLCSS output, using the navigation controls set by the report developer using either of the following:

•	the Page Navigation Control Type and Page Navigation Control Value properties in the Report Property Palette.

•	PL/SQL in a Before Report trigger (SRW.SET_PAGE_NAVIGATION_HTML).

Syntax

[PAGESTREAM=]{YES|NO}

Values

YES means to stream the pages.

NO means to output the report without page streaming.

Default

NO


EXPRESS_SERVER

  Related Topics

Description  EXPRESS_SERVER specifies the Express Server to which you want to connect.

Syntax

EXPRESS_SERVER="server=[server]/domain=[domain]/
user=[userid]/password=[passwd]"

Syntax with RAM

EXPRESS_SERVER="server=[server]/domain=[domain]/
user=[userid]/password=[passwd]/ramuser=[ramuserid]/
rampassword=[rampasswd]/ramexpressid=[ramexpid]/
ramserverscript=[ramsscript]/rammasterdb=[ramdb]/
ramconnecttype=[ramconn]"

Values

A valid connect string enclosed in double quotes (") where

server	is the Express server string (e.g., ncacn_ip_tcp:olap2-pc/sl=x/st=x/ct=x/sv=x/).
Domain	is the Express Server domain.
User	is the userid to log into the Express Server.
Password	is the password for the userid.
ramuser	is the userid to log into the RDBMS.
rampassword	is the password for the RDBMS.
ramexpressid	is the Oracle Sales Analyzer database userid. This is required for Oracle Sales Analyzer databases only.
ramserverscript	is the complete file name (including the full path) of the remote database configuration file (RDC) on the server. This file specifies information such as the location of code and data databases. Using UNC (Universal Naming Convention) syntax allows multiple users to use the same connection to access the data without having to map the same drive letter to that location. UNC syntax is \\ServerName\ShareName\ followed by any subfolders and/or files.
rammasterdb	is the name of the Relational Access Manager database to attach initially. You must specify only the database file name. This database must reside in a directory that is included in the path list in ServerDBPath for Express Server. You can check the ServerDBPath in the File I/O tab of the Express Configuration Manager dialog box.
ramconnecttype	is the type of Express connection. Always specify 0 for a direct connection.
The server value contains four parameters that correspond to settings that are made in the Oracle Express Connection Editor and stored in connection (.xcf) files. All four parameters are required and can be specified in any order. The following table describes the parameters and their settings.

Parameter	Description	Setting
sl	Server Login	-2: Host (Domain Login) -1: Host (Server Login) 0: No authentication required 1: Host (Domain Login) and Connect security 2: Host (Domain Login) and Call security 3: Host (Domain Login) and Packet security 4: Host (Domain Login) and Integrity security 5: Host (Domain Login) and Privacy security Notes: Windows NT uses all the settings. Unix systems use only the settings 0, -1, and -2. See the Express Connection Editor Help system for information on these settings.
st	Server Type	1: Express Server
ct	Connection Type	0: Express connection
sv	Server Version	1: Express 6.2 or greater
Usage Notes

•	You can have spaces in the string if necessary (e.g., if the userid is John Smith) because the entire string is inside of quotes.

•	If a forward slash (/) is required in the string, you must use another forward slash as an escape character.  For example, if the domain were tools/reports, the command line should be as follows:

EXPRESS_SERVER="server=ncacn_ip_tcp:olap2-pc/sl=0/st=1/
ct=0/sv=1/ domain=tools//reports"

•	You can use single quotes within the string.  It is not treated specially because it is enclosed within double quotes.


EXPRESS_SERVER with RAM (RWRUN60) example

  Related Topics 	  All Examples

rwrun60 userid=scott/tiger@nt805
express_server="server=ncacn_ip_tcp:olap2-pc/sl=0/st=1/
ct=0/sv=1/ramuser=appqa/rampassword=appqa1/ramexpressid=appqa/
ramserverscript=\\olap3-pc\orant\olap\ram6202\ram\sqstnt.rdc/
rammasterdb=sqstnt.db/ramconnecttype=0"
report=exp.rdf destype=file desname=exp1.html
desformat=html batch=yes


EXPRESS_SERVER with userid, password, and domain (RWRUN60) example

  Related Topics 	  All Examples

rwrun60 userid=scott/tiger@nt805
express_server="server=ncacn_ip_tcp:olap2-pc/sl=1/st=1/ct=0/
sv=1/ user=orbuild/domain=tools/password=buildme/"
report=exp.rdf destype=file desname=exp1.html
desformat=html batch=yes


EXPRESS_SERVER without userid, password, and domain (RWRUN60) example

  Related Topics 	  All Examples

rwrun60 userid=scott/tiger@nt805
express_server="server=ncacn_ip_tcp:olap2-pc/sl=0/st=1/ct=0/
sv=1/" report=exp.rdf destype=file desname=exp1.html
desformat=html batch=yes


CUSTOMIZE

  Related Topics

Description  CUSTOMIZE specifies an XML file or list of files that you want to apply to the report selected in the MODULE or REPORT keyword. The XML file contains customizations (e.g., font changes or color changes) that change the report definition in some way.

For more information, refer to the Publishing Reports manual.

Syntax

[CUSTOMIZE=]filename.xml|(filename1.xml, filename2.xml, ...)

Values

The names of files that contain valid XML report definitions, with path information prefixed to the filenames if necessary.

Usage Notes

•	Typically, the file extension of an XML report definition is .XML, but it does not have to be when it is used with the CUSTOMIZE keyword.


SAVE_RDF

  Related Topics

Description  SAVE_RDF specifies a file to which you want to save the report selected in the MODULE or REPORT keyword combined with the XML customization file(s) selected in the CUSTOMIZE keyword. This argument is most useful when you have an .RDF file to which you are applying an XML file via the CUSTOMIZE keyword and want to save the combination of the two to a new .RDF file.

For more information, refer to the Publishing Reports manual.

Syntax

[SAVE_RDF=]filename.rdf

Values

Any valid filename.


<param>

  Related Topics

Description  <param> is a parameter that is part of the report's definition.  The value you specify is used for that parameter's value.

Syntax

<param>=value

Values

Any valid value for that parameter.

Default

Taken from the Initial Value property of the parameter.

Usage Notes

•	You can override the default value on the Runtime Parameter Form.

•	Values of arguments may be in single or double quotes.  The effect of single or double quotes is operating-system specific.

•	If you specify runfile(s) using the REPORT keyword, the PARAM values will be validated using the settings specified for each parameter (e.g., Input Mask, Validation Trigger) in the report(s).

•	If you do not specify runfile(s) using the REPORT keyword, the PARAM value is not parsed, or validated, because the parameters may refer to those that have not yet been defined.