oracle reports messages and codes manual

Reports Messages and Codes Manual

Release 2.5

Reports Messagesand Codes ManualRelease 2.5Part No. A32490–1

Oracle Reports� Messages and Codes Manual, Release 2.5

Part No. A32490–1, April 1995Copyright � Oracle Corporation 1984, 1988, 1995All rights reserved. Printed in the U.S.A.

Contributing Authors: Anne Bers and Lori Ann WhiteContributors: Per Brondum, Karen Denchfield–Masterson, Alex Hsieh,Yueh–Hong Lin, Ashok Natesan, Boris Protasov, Greg Rogalski, Frank Rovitto,Yuri Sharonin, Jerry Sherman, Gene Sohn, Atul Suklikar, Marco Tilli, SimonWong

This software was not developed for use in any nuclear, aviation, masstransit, medical, or other inherently dangerous applications. It is thecustomer’s responsibility to take all appropriate measures to ensure the safeuse of such applications if the programs are used for such purposes.

This software/documentation contains proprietary information of OracleCorporation; it is provided under a license agreement containing restrictions onuse and disclosure and is also protected by copyright law. Reverse engineeringof the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency ofthe Department of Defense, then it is delivered with Restricted Rights and thefollowing legend is applicable:

Restricted Rights Legend Use, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS252.227–7013, Rights in Technical Data and Computer Software (October 1988).

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

If this software/documentation is delivered to a U.S. Government Agency notwithin the Department of Defense, then it is delivered with “Restricted Rights”,as defined in FAR 52.227–14, Rights in Data – General, including Alternate III(June 1987).

The information in this document is subject to change without notice. If youfind any problems in the documentation, please report them to us in writing.Oracle Corporation does not warrant that this document is error–free.

ORACLE, Pro*COBOL, Pro*FORTRAN, Pro*Pascal, Pro*PL/I, SQL*Connect,SQL*Net, SQL*Plus, and SQL*ReportWriter are registered trademarks of OracleCorporation.Developer/2000, ORACLE7, Oracle Book, Oracle Forms, Oracle Graphics,Oracle Help, Oracle*Mail, Oracle Reports, PL/SQL, and Pro*C are trademarksof Oracle Corporation.All other products or company names are used for identification purposes only,and may be trademarks of their respective owners.

T

iRead This First

Read This First

he Reports Messages and Codes Manual is one of six documents inthe Oracle Reports Version 2.5 documentation set. Before you use it,you should be familiar with the following topics:

• audience

• Oracle Reports documentation

• how to use this book

• how to contact Oracle about documentation and productcomments

Before you use this book, we recommend that you become familiarwith the Building Reports Manual.

ii Reports Messages and Codes Manual

Audience

The information in this manual is intended for application developerswho want to create reports. Readers should have a workingknowledge of SQL, PL/SQL, and ORACLE server concepts.

Oracle Reports Documentation and Related Information

Oracle Reports has the capability to interact with a variety of products,such as the ORACLE server, various networking tools, and severalprogramming languages. Sometimes, knowledge of these otherproducts is necessary.

The following map is provided to help you determine any additionaldocumentation you may need.

Oracle ReportsDocumentation

Related Information

iiiRead This First

The following books are included in the Oracle Reports documentationset:

• Oracle Reports Documentation Set Version 2.5, Part No. A32486, is a collection of all Oracle Reports manuals.

• Reports Enhancements Manual Version 2.5, Part No. A32487,contains information about features new to Oracle ReportsVersion 2.5.

• Building Reports Manual Version 2.5, Part No. A32488, contains atutorial and a rich discussion of Oracle Reports concepts as wellas many example reports.

• Reports Reference Manual Version 2.5, Part No. A32489, containsdetailed reference information about all aspects of OracleReports. It is intended primarily to answer specific questionsthat you might have about using Oracle Reports.

• Reports Messages and Codes Manual Version 2.5, Part No. A32490,contains all Oracle Reports messages with cause and actiondescriptions.

• Reports Runtime Manual, Graphical and Character ModeInterfaces, Version 2.5, Part No. A32493, contains information forend users (i.e., those who only run reports). It contains a tutorialand reference information about the Oracle Reports runtimeexecutable.

• Reports Migration Manual Version 2.5, Part No. A32491, containsall information that you need to convert SQL*ReportWriterVersion 1.1 reports and printer definitions to Oracle ReportsVersion 2.5.

• The online help system consists of the Reports Reference Manual,Reports Messages and Codes Manual, Reports Runtime Manual, andprocedural information in online format.

Each Oracle Reports manual is also shipped as an Oracle Bookdocument. For the names and locations of the document files, see yourDeveloper/2000 Installation Guide.

As an application designer using Oracle Reports Version 2.5, you mayneed to refer to some or all of the documents listed below. Please seethe document in question for information on its specific purpose andusage.

• Developer/2000 Installation Guide or System Release Bulletin. Thisdocument is different for each hardware/software platform.Ask your sales representative for the appropriate part number.

iv Reports Messages and Codes Manual

• ORACLE7 Server Documentation Set, Part No. 5030–70

• ORACLE7 Server Documentation Set V7.1, Part No. A12383

• Oracle Network Products Messages Manual, Part No. A16263

• MultiProtocol Interchange Administrator’s Guide, Part No. A10157

• PL/SQL User’s Guide and Reference, Version 1.0, Part No. 800–V1.0

• PL/SQL User’s Guide and Reference, Version 2.0, Part No. 800–20

• Programmer’s Guide to ORACLE Precompilers, Part No. A18820

• Pro*C Precompiler Supplement, Part No. A16084

• Pro*COBOL Precompiler Supplement, Part No. A16083

• Pro*FORTRAN Precompiler Supplement, Part No. A16086

• Pro*Pascal Precompiler Supplement, Part No. A16145

• Pro*PL/I Precompiler Supplement, Part No. A16146

• Understanding SQL*Net, Part No. A16029

• Oracle Network Manager Administrator’s Guide, Part No. A16264

How to Use this Book

The Reports Messages and Codes Manual provides comprehensiveinformation about Oracle Reports messages and how to handle them.Before you use this book, we recommend that you read the first threechapters of the Building Reports Manual.

This book contains the following chapters:

• Chapter 1, ”Using Messages,” which explains how to identify theorigin of messages (i.e., whether they arise from an OracleReports error, an ORACLE server error, a component error, or anerror specific to your platform) and how to look up causes andactions for errors. It also covers how to contact CustomerSupport.

• Chapter 2, “Oracle Reports Messages,” a numerical listing of allOracle Reports error messages, including causes for the raisingof each message and actions you can take to resolve them..

NotationalConventions

vRead This First

You should be familiar with the notational conventions listed in thefollowing table.

Convention Explanation

File—>New—>Report Indicates a selection of submenu item Reportfrom the New submenu of the File menu.

Data/Selection:Repeat Indicates a selection of Repeat from the Data/Selection tab of a property sheet.

Font Change Indicates text to be entered exactly as shown.

UPPERCASE Indicates command, column, parameter, field,boilerplate, and anchor names.

Initial Caps Indicates table, menu, query, group, frame,and repeating frame names, as well as proper-ty sheet names.

Bold Indicates items within a menu, buttons, ortabs on a property sheet.

Italics Indicates options for Oracle Reports settings.

vi Reports Messages and Codes Manual

Your Comments Are Welcome

We value and appreciate your comments as an Oracle user. As wewrite, revise, and evaluate our work, your opinions are the mostimportant input we receive. At the back of this manual is a Reader’sComment Form. We encourage you to use this form to tell us bothwhat you like and dislike about this (or other) Oracle manuals. If theform is gone, or you would like to contact us, please use the followingaddresses and phone numbers.

For documentation questions/comments, contact:

Oracle Reports Documentation Manager

Oracle Corporation

500 Oracle Parkway

Box 659412

Redwood Shores, California 94065–5028

(415) 506–7000

(415) 506–7200 (fax)

For product questions/comments, contact:

Oracle Reports Product Manager

Oracle Corporation

500 Oracle Parkway

Box 659412

Redwood Shores, California 94065–5028

(415) 506–7000

(415) 506–7200 (fax)

viiContents

Contents

Chapter 1 Using Messages 1 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coping with Messages 1 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Finding Information about Messages 1 – 2. . . . . . . . . . . . . . . . . . . . Looking Up Messages 1 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ORACLE Messages 1 – 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abnormal Conditions 1 – 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Cause 1 – 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Action 1 – 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calling Oracle Customer Support 1 – 4. . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Reports Message Descriptions 1 – 5. . . . . . . . . . . . . . . . . . . . . . .

Using this Section 1 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start–up Messages 1 – 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 Oracle Reports Messages 2 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Reports Messages 2 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii Reports Messages and Codes Manual

C H A P T E R

1T

1 – 1Using Messages

Using Messages

his chapter explains how to use messages issued by OracleReports. It covers the following topics:

• coping with messages – 1 – 2

• ORACLE messages – 1 – 3

• abnormal conditions – 1 – 3

• calling Oracle customer support – 1 – 4

Finding Informationabout Messages

Looking Up Messages

1 – 2 Reports Messages and Codes Manual

Coping with Messages

This section gives you general information and helpful tips aboutmessages. It covers the following topics:

• finding information about errors

• looking up messages

Messages that may appear when using Oracle Corporation programsare documented in a number of manuals:

These messages are specific to Oracle Reports andare documented in this book.

These messages are detected by ORACLE, andthey can appear while you are running nearly anyOracle program.

These messages are specific to one product, and aretherefore documented in the manuals for thatproduct. For example, you might get anOracle*Mail message, which is documented in theOracle*Mail documentation.

These messages are specific to one operatingsystem. A range of message numbers has beenreserved for each operating system. For example,the range 7500 – 7999 is for DEC VAX/VMSmessages. For information on these messages, seeyour Developer/2000 Installation Guide.

The prefix of each message tells you where to find information aboutthe message. For example, Oracle Reports messages have the prefixREP. RDBMS messages have the prefix ORA. If you are using OracleReports and see a message without a prefix, first check this manual,then refer to your ORACLE7 Server Messages and Codes Manual..

Following the prefix is the message code number.

To look up an Oracle Reports message (REP prefix), you can eithercheck this manual or select Help in the message dialog to display anonline version of this manual, positioned at the correct message. If themessage is not an Oracle Reports–specific message, look at the messageprefix to determine which product/component generated the message.Then look at the message code number to find that specific messagedescription. Messages are listed in order by the code number.

Oracle Reportsmessages

ORACLEmessages

Product–specificmessages

System–specificmessages

Message Prefixes


The following table lists the prefixes of messages that you mayencounter:

Prefix Type of Message

REP Oracle Reports message

ORA ORACLE messages (includes PL/SQL messages)

DBA SQL*DBA message

EXP Export Utility message

IMP Import Utility message

LCC Parameter file message

ORA Generic ORACLE message

PCC Precompiler Compile–time message

PLS PL/SQL message

RTL Precompiler Run–time message

SQL*Loader SQL*Loader message

VGS Oracle internal graphics system

PDE Oracle internal PL/SQL Development Environment

ORACLE Messages

When using Oracle Reports, you might get an ORACLE message (i.e., amessage prefixed with ORA). For more information, see the ORACLE7Server Messages and Codes Manual.

Abnormal Conditions

Sometimes you may encounter an error that is known as an abnormalcondition. These are errors for which the exact cause is not clear. Thefollowing sections describe the probable causes of abnormal conditionsand the actions you can take to solve them.

Cause

Action


Abnormal conditions may arise from one of the following causes:

• Someone has done something that prevented Oracle Reportsfrom completing the requested task. For example, if someonebypassed the user interface and changed data in Oracle Reports’tables directly, they might have entered an invalid value in thesetables which has prevented Oracle Reports from completing therequested task.

• A bug in Oracle Reports prevented the requested task fromcompleting.

You should first contact your DBA and/or system administrator todetermine if the message was caused by something other than OracleReports. If you determine that the message was not the result of usererror or a system problem, then you should take the following steps:

1. Write down the message number and its text.

2. Write down the circumstances that lead up to the message. Try torecall the actions you took, the objects involved (if any), and theexact sequence of keys that you pressed prior to the message.

3. Contact Oracle Customer Support. See ”Calling Oracle CustomerSupport” below for more information.

Calling Oracle Customer Support

Some messages recommend calling Oracle Customer Support to reportthe problem. When you call Customer Support, please have thefollowing information at hand:

1. The hardware, operating system, and release number of the operating system on which Oracle Reports is running.

2. The complete version number of Oracle Reports including revisionnumber and port release number, if any. For example, V2.0.05 orV2.0.13.

3. All products (with version numbers) in use when the message wasdisplayed (ORACLE V6.0, SQL*Net V2.0, or SQL*Forms V3.0, forexample).

4. If you encountered one or more messages, the exact code numbersand message texts, in the order they appeared.

Using this Section


5. 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 overalloperations.

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

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

7. Also, you will be expected to give your:

• name

• company’s name

• company’s ORACLE Support ID Number

• phone number

Oracle Reports Message Descriptions

This section includes the following:

• conventions used in this section

• start–up messages

Note: GUI Oracle Reports will always attempt to displaymessages in an alert. If Oracle Reports cannot bring up an alert(e.g., the problem occurred during startup), then the messagewill be sent to your standard SYSOUT.

Each description contains the message number and text as well as thefollowing:

Is a description of the possible causes of the error.

Is a description of the possible actions you mighttake to resolve the error.

Cause

Action

Recognizing EmbeddedVariables

Start–up Messages

Hard–coded Messages


To help you find and fix errors, Oracle Reports embeds object names,numbers, and character strings in some messages. In this appendix,these embedded variables are represented by terms placed in anglebrackets <>.

For example, the message:

REP–1232: Matrix ’X_Cross’ has an invalid source frame.

would appear in this section as:

REP–1232 Matrix ’<matrix name>’ has an invalid source

frame.

When an error is encountered and its message cannot be obtained fromthe message file, then Oracle Reports will display one of the followingmessages:

• Error raised but unable to open message file.

• Still attempting to report error.

After these messages, Oracle Reports displays a hard–coded message.

Following is a list of the hard–coded messages:

File not found: <filename>

Error opening file: <filename>

ORACLE error number: <ORACLE error number>

<ORACLE description of the error>

Bad argument in command list. Argument was: <argument>

No runfile was specified.

Error opening specified terminal description file:

<filename>

Unable to get message for error <error number>

<Additional information: <information>>

There is one other time a hard–coded message will appear. When anerror occurs and for some reason the message subsystem does notexecute correctly, then the following message will appear:

The error manager is unable to report an error due to

recursive failure of the error subsystem. Aborting.

Action


When you receive a start–up message, you should take the followingsteps:

1. Contact your DBA. The DBA should be able to verify whether theproduct has been installed correctly. Refer to your Developer/2000Installation Guide. If the product was not installed correctly, theDBA should correct the problem.

2. If the product has been installed correctly and the error persists,you should contact Oracle Customer Support for assistance. Formore information, see “Calling Oracle Customer Support” on page1 – 4.

C H A P T E R

2T

2 – 1Oracle Reports Messages

Oracle ReportsMessages

his chapter lists messages issued by Oracle Reports. Eachmessage code follows the format REP–nnnnn, where nnnnn is aninteger.

Messages specific to an operating system or an Oracle product are notlisted in this chapter, although the message code may be listed with areference to another Oracle document.

In general, for more information regarding the conditions that generatemessages in this chapter, see the Reports Reference Manual.

Cause

Action

Cause

Action

Cause

Action

Cause


Oracle Reports Messages

REP–0001 Unable to initialize message subsystem.

The file of error messages could not be opened or an internal error occurredwhile opening it.

Contact Oracle Customer Support for assistance.

REP–0002 Unable to retrieve string from message file.

Oracle Reports could not retrieve the necessary error message or string.

Contact Oracle Customer Support for assistance.

REP–0003 Warning – Unable to open global preference file.

The global Oracle Reports preference file shipped with Oracle Reports couldnot be opened. This is just a warning, so the product will continue to run evenif this occurs. The possible causes of this error include the following:

Case 1: The file was not found under the specified name in the specifiedlocation.

Case 2: You lacked the necessary privileges to open the file.

Case 3: A system error made it impossible to open the file.

You can take the following actions to correct this error:

If Case 1: Make sure the file named prefs.ora is stored in the appropriatedirectory. For more information, see your Developer/2000 InstallationGuide. Or contact your DBA.

If Case 2: Make sure that you have the privileges necessary to access the file. Ifyou don’t, change your privileges accordingly.

If Case 3: Consult your operating system documentation or contact your systemadministrator.

REP–0004 Warning – Unable to open user preference file.

Your local (customized) Oracle Reports 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:



Action

Cause

Action

Cause

Action

Cause




If Case 1: Make sure the file prefs.ora is located in your ”home” directory (ifyour system has such a concept as home directory). If it is not,change the directory and/or filename as appropriate.



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

One or more of the preferences in the global preference file was specifiedincorrectly on the line number shown in the message. The most likely cause ofthis error is that the file has been edited and one or more preferencesincorrectly specified. As a result, Oracle Reports will ignore the incorrectlyspecified preferences.

You or your DBA should edit the global preference file and ensure that allpreferences are correctly specified. If they are not, make the necessary updates.

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

One or more of the preferences in the user preference file was specifiedincorrectly on the line number shown in the message. The most likely cause ofthis error is that the file has been edited and one or more preferencesincorrectly specified. As a result, Oracle Reports will ignore the incorrectlyspecified preferences.

You should edit the global preference file and ensure that all preferences arecorrectly specified. If they are not, make the necessary updates.

REP–0007 Unable to write user preference file.

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

Cause

Action

Cause

Action

Cause

Action

Cause

Action



If Case 1: Make sure that you have the privileges necessary to write the file. Ifyou don’t, change your privileges accordingly.


REP–0008 Unexpected memory error while initializing preferences.

This is an abnormal condition.

For information, see “Abnormal Conditions” on page 1 – 3.

REP–0059 Unable to locate resources for subcomponent <component name>. Checkthe location of resource file.

One of the subcomponents of Oracle Reports 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.


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 surethat the proper environment variable is set, and on MicroSoftWindows check the file oracle.ini.

REP–00060 Unable to run synchronous job concurrently with another report.

You are trying to run a report initiated by another Oracle Tool (e.g., OracleForms) and requiring data passed from that tool, but one or more other reportsare running or queued to run. Reports requiring passed data must be runimmediately.

Wait for all other reports currently listed in the Oracle Reports Server queue torun, then try your report again.

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



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0062 Internal error – rxmobnew: size mismatch.



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



REP–0064 Internal error – rxmobnew: type mismatch.



REP–0065 Virtual Memory System error.

Oracle Reports has encountered a memory error.

Make note of the error–specific code and contact Oracle Customer Support.For more information, see “Calling Oracle Customer Support” on page 1 – 4.

REP–0066 Error executing CA utility.



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

In R25CONV, you provided an argument for the STYPE keyword that was notvalid.

Check the syntax of the keyword. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command, using a valid value for the keyword(s).

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0068 Invalid value for keyword STYPE. Valid options are DATABASE orREXFILE.

In R25MREP, you provided an argument for the STYPE keyword that was notvalid.


REP–0069 Invalid value for keyword DTYPE. Valid options are DATABASE, REXFILE,RDFFILE, REPFILE, PLLDB, PLLFILE, or PLDFILE.

In R25CONV, you provided an argument for the DTYPE keyword that was notvalid.


REP–0070 Invalid value for keyword DTYPE. Valid options are DATABASE, REXFILE,or RDFFILE.

In R25MREP, you provided an argument for the DTYPE keyword that was notvalid.


REP–0071 Unable to allocate SSL context.



REP–0072 Unable to initialize NNIT interface.



REP–0073 Trying to run unknown product.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0074 Failure to run another product using SSL.



REP–0075 Error occurred when running called product.

Oracle Reports encountered an error after calling another Oracle product (e.g.,Oracle Graphics). The accompanying error message displays the errorencountered by the called application.

Resolve the error encountered by the called application and re–try theoperation.

REP–0076 Internal failure in product integration.



REP–0077 Column in query ’<query name>’ too long for data passing.

You tried to pass data to a column of excessive size (likely a LONG column).This is not supported.

Remove the column from the report definition and the calling document’sdefinition.

REP–0078 Single process integration invoked with batch=no.

You used an executable in which Oracle Reports is linked with another product,and attempted to invoke Oracle Reports specifying batch=no. This is notsupported.

Use an executable by which you integrate using multiple processes. Otherwise,Oracle Reports can only be called with batch=yes.

REP–0079 Invalid value for keyword OVERWRITE. Valid options are YES, NO, orPROMPT.

In R25CONV, you provided an argument for the OVERWRITE keyword thatwas not valid.

Re–enter the command, specifying a value of YES, NO, or PROMPT for theOVERWRITE keyword.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0080 Please enter YES, NO or CANCEL.

In R25CONV, you typed OVERWRITE=PROMPT on the command line, thenentered a value other than YES or NO when prompted.

Specify a value of YES or NO at the prompt, or CANCEL the operation.

REP–0081 Error during file I/O operation.



REP–0082 Error executing SCA utility.

The possible causes of this error include the following:

Case 1: Your initialization file is not current.

Case 2: An abnormal condition.


If Case 1: Ensure that your initialization file is current.

If Case 2: For information, see “Abnormal Conditions” on page 1 – 3.

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

In R25CONV, you entered an invalid value for the keyword DUNIT.


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

In R25CONV, you entered an invalid value for the keyword PAGESIZE.

Check the syntax of the keyword. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command, using a valid value and the proper syntax forthe keyword.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

In R25CONV, you entered an invalid value for the keyword FORMSIZE.


REP–0086 DUNIT must be different than source report’s unit of measurement.

In R25CONV, you entered a value for the keyword DUNIT that was in thesame unit of measurement as the report you wish to convert.


REP–0087 Invalid value for keyword DESTYPE. Valid values are SCREEN, FILE,PRINTER, MAIL, SYSOUT, or PREVIEW.

In R25RUN, you entered an invalid value for the keyword DESTYPE.


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

You entered an invalid value for ONSUCCESS.

Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settingstab of the Tools Options dialog or on the command line. (To check thecommand line syntax, see “Executables” in Chapter 1 of the Reports ReferenceManual. You can also check the online help system.)

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

You entered an invalid value for ONFAILURE.

Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settingstab of the Tools Options dialog or on the command line. (To check thecommand line syntax, see “Executables” in Chapter 1 of the Reports ReferenceManual. You can also check the online help system.)

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0090 Invalid value for keyword ACCESS. Valid options are FILE andDATABASE.

For R25DES, you entered an invalid value for ACCESS.

Specify FILE or DATABASE. (To check the command line syntax, see“Executables” in Chapter 1 of the Reports Reference Manual. You can also checkthe online help system.)

REP–0091 Invalid value for parameter ’<parameter name>’.

You entered an invalid value for the named parameter. For example, in theR25RUN command string, you entered a character value for a parameter with adatatype of Number.

Re–try the operation, specifying a valid value for the parameter.

REP–0092 Warning – Version 1.1 LANGUAGE argument not supported. Use ORACLENational Language environment variable instead.

For R25DES or R25RUN, you included the LANGUAGE keyword in thecommand line string.

Remove the LANGUAGE argument string from the command string, and setthe ORACLE National Language environment variable NLS_LANG to theappropriate value. For more information, see “National Language Support” inAppendix C of the Reports Reference Manual. You can also check the online helpsystem.)

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

While using R25CONV with DUNIT=Character, you specified a parameterform size that was not equal to 80x24.

The character–mode parameter form size must be 80x24. Either specify aFORMSIZE of 80x24 when DUNIT=Character , or do not specify a FORMSIZE.

REP–0095 Invalid value for keyword ORIENT. Valid options are DEFAULT,LANDSCAPE, or PORTRAIT.

You entered an invalid value for ORIENT.

Specify DEFAULT, LANDSCAPE, or PORTRAIT either in the RuntimeSettings tab of the Tools Options dialog or on the command line. (To check thecommand line syntax, see “Executables” in Chapter 1 of the Reports ReferenceManual. You can also check the online help system.)

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0096 Invalid value for keyword MODE. Valid options are DEFAULT, BITMAP, orCHARACTER.

You entered an invalid value for MODE.

Specify DEFAULT, BITMAP, or CHARACTER either in the Runtime Settingstab of the Tools Options dialog or on the command line. (To check thecommand line syntax, see “Executables” in Chapter 1 of the Reports ReferenceManual. You can also check the online help system.)

REP–0097 Invalid value for keyword TRACEMODE. Valid options areTRACE_APPEND or TRACE_REPLACE.

Either you specified an invalid value for TRACEMODE, or did not specify avalue for TRACEMODE, or specified keywords out of order on the commandline but did not name them.

Either specify Append or Replace for Trace Mode in the Trace Settings dialog orTRACE_APPEND or TRACE_REPLACE on the command line, or check thesyntax of your command. (To check the command line syntax, see“Executables” in Chapter 1 of the Reports Reference Manual. You can also checkthe online help system.)

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

Your report was not executed because you selected Cancel instead of RunReport in the Runtime Parameter Form.

No action is necessary.

REP–0099 Report is aborted upon user request.

You stopped a report while it was executing.


REP–0100 Unable to position file pointer in file ’<filename>’.



REP–0101 Unable to read file ’<filename>’.

Oracle Reports tried to read the file shown in the message. The file could beopened but not read.

Consult your operating system documentation or contact your systemadministrator.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0102 Unable to write file ’<filename>’.

Oracle Reports tried to write the file shown in the message and couldn’t. Thepossible 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.



If Case 1: Make sure that you have the privileges necessary to write the file. Ifyou don’t, change your privileges accordingly.

If Case 2: Make more room by deleting unnecessary files or expanding yourstorage.


REP–0103 Unable to close file ’<filename>’.

Oracle Reports tried to close the file shown, but was unsuccessful. The mostlikely reason is that a system error made it impossible to close the file.


REP–0104 Unable to delete file ’<filename>’.

Oracle Reports tried to delete the file shown, but was unsuccessful. The mostlikely reason is that a system error made it impossible to delete the file.


REP–0105 Unable to lock file ’<filename>’ in exclusive mode.

Oracle Reports tried to lock the file shown, but was unsuccessful. The mostlikely reason is that a system error made it impossible to lock the file.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0106 Unable to lock file ’<filename>’ in shared mode.

Oracle Reports tried to lock the file shown, but was unsuccessful. The mostlikely reason is that a system error made it impossible to lock the file.


REP–0107 Attempt to open a file with a bad name – ’<filename>’.



REP–0108 File ’<filename>’ not found.

Oracle Reports tried to access the file shown, but could not find it.

Check that you have specified the correct filename. Specify a directory beforethe filename, or modify the REPORTS25_PATH environment variable to includethe directory where the file is located.

REP–0109 Too many files open.



REP–0110 Unable to open file ’<filename>’.

Oracle Reports tried to open the file shown and couldn’t. The possible causesof this error include the following:





If Case 1: Make sure the file is stored in the specified directory under thespecified name. If it is not, change the directory and/or filename asappropriate.

If Case 2: Make sure that you have the privileges necessary to open the file. Ifyou don’t, change your privileges accordingly.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0111 Directory ’<directory path>’ is protected.

You specified that Oracle Reports read from or write to a directory that youdon’t have permission to read from or write to.

Change the permissions on the directory so that you can read from it or writeto it.

REP–0112 File ’<filename>’ is write protected.

You specified that Oracle Reports write to a file that is write protected—i.e.,you don’t have permission to write to the file.

Change the permissions of the file so that you can write to it.

REP–0113 File ’<filename>’ is read protected.

You specified that Oracle Reports read a file that is read protected—i.e., youdon’t have permission to read the file.

Change the permissions of the file so that you can read it.

REP–0114 File ’<filename>’ no longer exists.

You specified that Oracle Reports access a file that no longer exists.

Remove the call to the file, re–create the file, or specify a different file.

REP–0115 Unable to read directory ’<directory path>’.

You most likely specified that Oracle Reports read from or write to a directorythat doesn’t exist.

Make sure the directory you specify exists.

REP–0116 Unable to connect to directory ’<directory path>’.

Oracle Reports could not access the specified directory for some reason.

Consult your system administrator.

REP–0117 Exit to host operating system failed.

You attempted to exit out of the program and return control to the hostoperating system.


Cause

Action

Cause

Action

Cause


REP–0118 Unable to create a temporary file.

Oracle Reports tried to create a temporary file but couldn’t do so. The possiblecauses of this error include the following:

Case 1: The environment variable that determines in what directory to createtemporary files is set to an invalid directory.

Case 2: There is not enough free space on the disk to create the temporaryfile.

Case 3: A temporary file that cannot be modified already exists.


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 Boilerplate <boilerplate name>’s external source file <filename> not found.

Oracle Reports tried to find the source file specified for a piece of externalboilerplate and couldn’t do so. The possible causes of this error include thefollowing:





If Case 1: Make sure the file is stored in the specified directory under thespecified name. If it is not, change the directory and/or filename asappropriate.

If Case 2: Make sure that you have the privileges necessary to open the file. Ifyou don’t, change your privileges accordingly.


REP–0120 Oracle Graphics display <display name>’s external source file <filename>not found.

Oracle Reports tried to find the display specified for an Oracle Graphicsdisplay object, but couldn’t do so. The possible causes of this error include thefollowing:

Action

Cause

Action

Cause

Action


Case 1: The display was not found under the specified name in the specifiedlocation.

Case 2: You lacked the necessary privileges to open the display.

Case 3: A system error made it impossible to open the display.


If Case 1: Make sure the display is stored in the specified directory under thespecified name. If it is not, change the directory and/or filename asappropriate.

If Case 2: Make sure that you have the privileges necessary to open the display.If you don’t, change your privileges accordingly.


REP–0150 Too many arguments.

You have entered more than the allowable number of arguments for thecommand.

Check the syntax of the command. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command correctly.

REP–0151 Duplicate argument specification for keyword <keyword>.

You have entered an argument more than once for the keyword shown. Thepossible causes of this error include the following:

Case 1: You entered a positional argument for the keyword and then enteredthe keyword with another argument.

Case 2: You entered the same keyword twice (e.g., KEYWORD1=YES andKEYWORD1=NO).

Check the syntax of the command. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. You can also check the online helpsystem. You can take the following actions to correct this error:

If Case 1: Re–enter the command with just the positional argument or just thekeyword argument.

If Case 2: Re–enter the command specifying the keyword only once.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0152 Positional argument specified after keyword.

On the command line, you entered an argument without its keyword afterentering an argument with its keyword. Once you have used a keyword on thecommand line, all subsequent arguments must use keywords as well.

Re–enter the command making sure that no positional arguments (argumentswhere the keyword is implicit) are specified after arguments with keywords.

REP–0153 Multiple values not allowed for keyword <keyword>.

In your command, you have entered more than the allowable number valuesfor the keyword argument shown. For example, you might have enteredKEYWORD=(A, B), where KEYWORD only accepts a single value.

Check the syntax of the command. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command without the extra value(s).

REP–0154 Unable to open command file ’<filename>’.

You entered a command that referenced the command file shown and the filecould not be opened. The possible causes of this error include the following:





If Case 1: Make sure the file is stored in the specified directory under thespecified name. If it is not, change the directory and/or filename ormove the file into the specified directory.



REP–0155 Invalid value for keyword <keyword>.

The value you entered for the keyword shown was not a valid value.

Check the syntax of the keyword. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command with the appropriate value for the keyword(s).

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

In R25RUN, you provided an argument for the DESTYPE parameter that wasnot valid.

Check the syntax of the keyword. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. You can also check the online helpsystem. Re–enter the command with the appropriate value for the keyword(s).

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

You entered a value for the keyword shown that was other than YES or NO andthe keyword only accepts YES or NO.

Re–enter the command and use a value of YES or NO for the keyword shown.

REP–0158 Unknown command line keyword ’<keyword>’.

You entered the referenced string as a keyword, but there is no such keyword.

Check the syntax of the command. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command using the appropriate keywords for the taskyou want to perform.

REP–0159 Syntax error on command line.

The string you entered on the command line could not be parsed. The mostlikely cause of this error is that you entered quotes or parentheses without alsoentering matching end quotes or parentheses.

Check the syntax of the command. For more information, see “Executables” inChapter 1 of the Reports Reference Manual. (You can also check the online helpsystem.) Re–enter the command using the appropriate syntax.

REP–0160 Syntax error in command file.

Something you entered in your command file could not be parsed. The mostlikely cause of this error is that you entered quotes or parentheses without alsoentering matching end quotes or parentheses.

Check the syntax of the command(s). For more information, see “Executables”in Chapter 1 of the Reports Reference Manual. (You can also check the onlinehelp system.) Edit the file and modify the commands as necessary to correctthe command(s).

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–0161 No command line arguments specified.

You invoked R25CONV or R25MREP without specifying any command linearguments.

Specify the appropriate command line arguments (e.g., SOURCE, DEST, etc.)for R25CONV or R25MREP. For more information, see “Executables” inChapter 1 of the Reports Reference Manual.

REP–0190 Cannot run to screen in background.

You specified that the report be run in the background, but you also specified aDESTYPE of Screen. You cannot execute a report in the background whilehaving its output sent to the screen.

If you want the output to go to the screen, you must run it in the foreground. Ifyou want the report to run in the background, you must specify a differentDESTYPE.

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

You are attempting use the character–mode executable to run a character–modereport with MODE set to BITMAP. This is not allowed.

Change the value of the MODE keyword to match the mode of the executable.Or run the report using a bitmapped executable.

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

You are attempting use the character–mode executable to run a bitmappedreport to the screen. This is not allowed.

Run the report using BATCH=YES or use a bitmapped executable.

REP–0196 Cannot run report in background.

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.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


Case 3: You are running the report using the packaged proceduresrw.run_report.

Case 4: The platform on which you’re running the report does not supportspawning of another process.

Ensure that BACKGROUND is set to NO when any of the above condition aretrue.

REP–0197 Must specify BATCH=YES or BACKGROUND=YES on command line whenrunning bitmapped report.

You tried to run a bitmapped report using the character–mode executable in theforeground or during an interactive session. This is not supported.

If you wish to run a bitmapped report using the character–mode executable,you must choose either BATCH=YES or BACKGROUND=YES (unlikeBATCH=YES, this setting gives you access to the Runtime Parameter Form).

REP–0200 Cannot allocate enough memory.

Oracle Reports cannot obtain enough memory from the system to complete thecurrent task.

Make more memory available, if you can, or ask your system administrator forassistance.

REP–0201 Zero or negative block size requested.



REP–0202 Attempt to free a null pointer.



REP–0203 Passed a null pointer as a handle.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0204 Handle does not point into an mp block.



REP–0205 Too many simultaneous locks on one object.



REP–0206 Null cache pointer passed to virtual memory routine.



REP–0207 Requested block is larger than virtual memory space.



REP–0208 rmaloc was not given a function identifier.



REP–0209 rmaloc was not given a structure identifier.



REP–0210 Illegal operation was requested on a locked handle.



REP–0211 Attempt to use a handle after freeing it.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0212 No literal specified.



REP–0213 Attempt to lock handle failed.



REP–0214 Cannot allocate a virtual memory buffer of size <number> KB. Please try asmaller size.

Oracle Reports tried to allocate a virtual memory buffer size at or below thenumber specified (by you or by default) for the BUFFERS keyword.

Specify a smaller size for BUFFERS (either in the Runtime Settings tab of theTools Options dialog or on the command line), or free up more memory. (Tocheck the command line syntax, see “Executables” in Chapter 1 of the ReportsReference Manual. You can also check the online help system.)

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



REP–0250 Symbol table overflow.



REP–0251 Identifier does not match a defined symbol.



REP–0252 Warning: The path specified by environment variable <variable name> istoo long and will be ignored.

The path designated by the environment variable is too long.

Shorten the length of the designated path.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0253 Warning: The total length of the search paths is too long and will betruncated.

The combined length of search paths in the path environment is too long. Thecombined length cannot exceed 255 characters.

Shorten the length of one or more paths in the path environment.

REP–0300 ORACLE error occurred.

Oracle Reports encountered an ORACLE error.

Scroll through the error message to see where the error occurred and, ifpossible, fix it. Otherwise, contact your DBA.

REP–0301 The SELECT statement may not contain an ’INTO’ clause.

You entered an INTO clause in a SELECT statement, which is not allowed inOracle Reports.

Remove the INTO clause.

REP–0302 Parameter ’<parameter name>’ not found in report.

You made reference to a parameter that is not defined in the report. The mostlikely cause is that you deleted a parameter but did not delete all references toit.

Delete all references to the deleted parameter.

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

What was entered in the SELECT Statement field is something other than aSELECT statement. The possible causes of this error include the following:

Case 1: You entered something besides a SELECT statement in the SELECTStatement field.

Case 2: You referenced an external query that did not contain a SELECTstatement.


If Case 1: Enter a valid SELECT statement.

If Case 2: Modify the external query or reference another external query.

Cause

Action

Cause

Action


REP–0304 ’&’ in SELECT statement was not followed by a valid lexical parameter.

An ampersand (&) appeared in the SELECT statement by itself. The possiblecauses of this error include the following:

Case 1: You intended to make a lexical reference but either left out the nameof the column or parameter altogether or inadvertently typed a spacebetween the ampersand and the name of the column or parameter.

Case 2: In typing the SELECT statement, you accidentally typed in anampersand.


If Case 1: Make sure that the column or parameter name immediately followsthe ampersand with no spaces in between.

If Case 2: Delete the ampersand.

REP–0305 ’<lexical reference>’ can not be used as a lexical parameter because it is not acharacter value.

You entered an invalid lexical reference in your SELECT statement. Lexicalreferences can only be made to parameters or columns containing characterdata. 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 lexicalreference.

Case 3: You created the parameter or column referenced with a non–characterDatatype.


If Case 1: Change the name that follows the ampersand (&) so it references aparameter or column with a Datatype of Character.

If Case 2: Replace the ampersand (&) with a colon (:) when referencing theparameter or column.

If Case 3: Change the Datatype of the parameter or column to be Character, ifappropriate.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0306 ’<name>’ is not a valid parameter name.

In making reference to a parameter, you have tried to create a parameter withan invalid name. When you use a bind reference, a parameter definition isautomatically created using the name specified in the bind parameter. In thiscase, Oracle Reports could not create the parameter because the name yousupplied was not a valid name.

Check the naming conventions for data model objects and rules for parameternames. For more information on naming conventions, see “NamingConventions” in Appendix D of the Reports Reference Manual. Rename theparameter and change the name in the bind reference.

REP–0307 The SELECT statement may not contain a ’FOR UPDATE’ clause.

You entered a FOR UPDATE clause in the SELECT statement, which is notallowed in Oracle Reports.

Remove the FOR UPDATE clause.

REP–0308 Internal error – Unknown column type.


Case 1: You tried to display the value of a column using SRW.MESSAGE, butthe column’s datatype (e.g., LONG, LONG RAW, ROWID) is notsupported for that operation.

Case 2: You tried to pass the value of a column to another Oracle product(e.g., Oracle Graphics) as a parameter, but the column’s datatype(e.g., LONG, LONG RAW, ROWID) is not supported for thatoperation.

You cannot display or pass this column’s value.

REP–0309 Unable to connect to ORACLE after three attempts. Access denied.

Some part of the logon string you entered was incorrect. After three failedattempts, Oracle Reports displays a dialog box with this message. Your onlyoption from this dialog box is to accept it and then Oracle Reports quits andreturns you to the operating system.

Accept the dialog box. Confirm your logon information with your DBA, ifnecessary. Go back into Oracle Reports and try connecting to ORACLE again.If the problem persists, you may have to get your DBA to create a newORACLE logon for you.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0310 Error while processing Bind Variables in query.



REP–0311 Internal Error–Segmented memory used for lexical parameter.



REP–0312 Internal error–Error dealing with segmented memory.



REP–0313 Internal error–Fetching data records would cause memory overflow.



REP–0314 Column name exceeds 256 characters. Unable to describe. Use column aliasfor ’<column_name>’.

One of your SQL SELECT statements contains an expression that is longer than256 characters, but has no alias.

Edit the SELECT statement and assign an alias to the expression.

REP–0315 Each select statement must have the same number of columns in compoundquery.

You entered a query with a UNION, INTERSECT, or MINUS set operator inwhich the SELECT statements in the query do not have the same number ofselected columns.

Modify the SELECT statements so that they have the same number of columns.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You entered a query with a UNION, INTERSECT, or MINUS set operator inwhich corresponding columns have different types—e.g., column 1 in the firstSELECT statement has datatype CHAR, while column 1 in the second SELECTstatement has datatype NUMBER.

Modify the SELECT statements so that all corresponding columns have thesame datatype.

REP–0320 Could not connect to the database.

An attemp to connect to the database failed.

Recheck the userid and password and try again.

REP–0322 Internal Error—Could not put back fetched rows.



REP–0330 Internal Error-Location GET_REF parameters failed.

A CDE_MM.GET_REF call in a query did not specify a parameter list.

Add the parameter list to the call in your query’s select statement.

REP–0331 GET_REF PL/SQL function requires 3 parameters.

The parameter list of a CDE_MM.GET_REF call in a query was incomplete.

Add the necessary parameter to the call in your query’s select statement.

REP–0332 GET_REF PL/SQL funtion’s last parameter must be of type ROWID.

You did not provide a parameter of type ROWID as the last parameter for aGET_REF function.

Check your parameter list and ensure the last parameter is of type ROWID.

REP–0450 <PL/SQL error>.

Oracle Reports encountered the following PL/SQL error while running areport.

Edit and recompile the PL/SQL in the report to avoid this error.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action











REP–0490 Internal Error – Toolkit context unavailable.



REP–0491 Warning: Data truncation possible in column <column name>.

The database column’s width in the report is defined to be less than its width inthe database. This can sometimes occur when the columns in the database areupdated subsequent to the report being defined. This warning is raised onlywhen RUNDEBUG is YES.

Force the query to be reparsed. One method is to type a space at the end of aline in the SELECT Statement field and then accept the property sheet.

REP–0492 Unrecognized token: <tokenname>.

The SELECT statement that you entered contains an item that is not part ofSQL syntax.

Review your SELECT statement and ensure that it follows SQL syntax.

REP–0493 Internal Error – Unable to expand Lexical references.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–0494 Internal Error – Unable to process Lexical references.



REP–0495 Internal Error – Unable to tokenize the query.



REP–0496 Internal Error – Unable to parse the query.

The SQL statement that you have entered cannot be parsed because it containsan error.

Review the SQL statement that you entered and ensure that you are using thecorrect syntax. For more information, see the ORACLE7 Server SQL LanguageReference Manual.

REP–0497 Internal Error – Query failed in rodslt.



REP–0498 Number of columns selected by the query is incompatible with reportdefinition.

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 beenchanged since the report was defined.

Update the report definition so that it accepts the changed query. For example,go to the Query property sheet that references the changed external query andaccept it. Formulas, summaries, and fields that rely on any changed columnsmay also need to be updated.

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

The column from the database does not match the column in the reportdefinition. The possible causes of this error include the following:

Case 1: The definition of the column in the database has changed since thereport was defined.

Action

Cause

Action

Cause

Action

Cause

Action


Case 2: The report uses an external query and the external query waschanged since the report was defined.


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 theQuery property sheet so the column in the report definition has itsdatatype updated. Formulas, summaries, and fields that rely on thechanged column may also need to be updated.

If Case 2: Update the report definition so that it accepts the changed query. Forexample, re–accept the Query property sheet that references thechanged external query and accept it. Formulas, summaries, andfields that rely on any changed columns may also need to be updated.

REP–0500 Number entered is out of range.

You have entered a number in a setting which is too large.

Check the limits of the field. Look in the chapter where the field is describedand enter a number that is within the limits.

REP–0501 Unable to connect to ORACLE.

Oracle Reports tried to but could not connect to ORACLE. The possiblecauses of this error include the following:

Case 1: ORACLE is temporarily unavailable.

Case 2: Your connect information was not valid.


If Case 1: Retry the operation. Contact your DBA if the problem persists. Notethat after three failed attempts, you will be forced to leave OracleReports.

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 failedattempts, you will be forced to leave Oracle Reports.

REP–0502 Error attempting to open <filename> terminal file.

Oracle Reports tried to but could not open the terminal definition file youspecified. You either specified the name of the file incorrectly after the TERMkeyword or the file could not be found.

Make sure that you specified the name of the terminal definition correctly andthat it resides in the correct path. If the problem persists, contact your DBA.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You specified an invalid name or nothing when you should have specified thename of a report.

Specify the name of a report.

REP–0504 You are not connected to ORACLE.

You tried to perform an operation that requires you be connected to thedatabase and you were not connected.

Connect to the database using File—>Connect....

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

The value you entered in Width was invalid. The possible causes of this errorinclude the following:

Case 1: You entered zero or a negative number. Width must be greater thanzero.

Case 2: You entered something that was not a number.

Case 3: For a column of non–numeric Datatype, you entered a width of theform (x, y) where x is the precision and y is the scale. This type ofWidth specification is only valid when Datatype is Number.


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 Datatypeof the column to Number.

REP–0506 Database columns can not be moved between queries.

You tried to move a column into another group belonging to another query andthe column is a database column. A database column must be selected by thequery that owns its group.

Select the column, if possible, in the query that owns the group to which youwant to move it.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0507 You must enter a filename before performing this operation.

In a file selection dialog box, you tried to accept the dialog box withoutspecifying a filename.

Enter a name and then accept or cancel the dialog box.

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

In a database object selection dialog box, you tried to accept the dialog boxwithout specifying an object name.

Enter a name and then accept or cancel the dialog box.

REP–0509 Invalid number.

In a numeric field, you entered something other than a digit or a decimal point.

Enter a number that contains only digits and, if necessary, a decimal point.

REP–0510 Valid options are ’Character’, ’Inch’, ’Centimeter’ or ’Point’.

You entered an invalid unit of measurement in the Unit of Measurement field.

Select the option you want from the list of values.

REP–0511 Valid options are ’Across/Down’ or ’Down/Across’.

You entered a Panel Print Order that was not one of the two valid options.

Select the option you want from the list of values.

REP–0512 A decimal value is not appropriate here.

The number that you entered was a decimal value and Oracle Reports wasexpecting a non–decimal value.

Enter a non–decimal value.

REP–0513 You must enter a Unit of Measurement.

The Unit of Measurement is blank and you tried to move to another setting.

Select an option for Unit of Measurement.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0514 You must specify the Page Size.

You left the Page Width and/or Page Height settings blank and they require avalue.

Enter a number for Page Width and/or Page Height.

REP–0515 You must specify the Parameter Form Size.

You left the Parameter Form Width and/or Parameter Form Height settingsblank and they require a value.

Enter a number for Parameter Form Width and/or Parameter Form Height.

REP–0516 You must specify the Page Size in characters.

The value you entered for Page Size was not in character units, and Page Sizerequires character units.

Enter a value in characters for Page Size.

REP–0517 You must specify the Form Size in characters.

The value you entered for Form Size was not in character units, and Form Sizerequires character units.

Enter a value in characters for Form Size.

REP–0518 Valid options are ’Database’, ’File’, or ’File/Database’.

The Object Access setting you entered was not one of the three valid choices.

Select an option from the list of values.

REP–0519 Valid options are ’Insert’ or ’Replace’.

The Default Text Edit Mode you entered was not one of the two valid choices.

Select an option from the list of values.

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

The value you entered for Group/Frame Indentation was outside the validrange of values.

Enter a number between 0 and 4.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0521 ’<Name>’ is not a valid name.

You violated naming conventions and gave an object an invalid name (shown).

Find the naming conventions for the type of object you are creating and ensurethat the name follows those conventions. For more information, see “NamingConventions” in Appendix D of the Reports Reference Manual.

REP–0522 You can not build a default layout because this report has no groups.

You selected Tools—>Default Layout... or drew a region using the DefaultLayout tool in the Layout editor before having created any groups for thereport. Groups are required in order to create a default layout.

Create one or more queries to allow Oracle Reports to automatically create agroup, then re–try the operation.

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

You entered a value for Default Layout Style that is not one of the validoptions.

Select a layout style from the list of values.

REP–0524 Invalid Print Direction. See the list of values.

You entered a Repeat value that is not one of the valid options.

Select a value for Repeat from the list of values.

REP–0525 Valid options are ’Screen’, ’File’, ’Printer’, ’Mail’, or ’Sysout’.

You entered a destination type for the system parameter DESTYPE that is notone of the valid options. Possible causes of this error include the following:

Case 1: You entered an invalid value for Destination Type in the RuntimeParameter Form.

Case 2: You entered an invalid Initial Value in the Parameter property sheetfor DESTYPE.


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.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You entered a value that is too long for the parameter on the Parameterproperty sheet. The possible causes of this error include the following:

Case 1: You entered a value in Initial Value that is too big, given what youspecified for the parameter’s Width.

Case 2: You entered a value for Width that is too small to contain the valuesyou want to be able to enter for the parameter.


If Case 1: Re–enter the Initial Value, making sure that it is not wider than whatyou specified in Width.

If Case 2: Delete the Initial Value you have entered. Move to the Width settingfor the parameter and increase it such that it can contain the InitialValue you had specified. Re–enter the Initial Value.

REP–0527 You can not delete a system parameter.

You tried to delete a packaged parameter from the Parameter property sheet.

Oracle Reports will not allow you to delete a system parameter. However, youcan suppress the display of the parameter on the Runtime Parameter Form byusing the Default Parameter Form dialog box or the Parameter Form editor.For more information, see “Parameter Form Editor” in Chapter 9 of the ReportsReference Manual. Also, see your online help.

REP–0528 Valid options are ’Character’, ’Number’ or ’Date’.

The datatype you entered in Datatype for the parameter was not one of thevalid datatypes.

Select a datatype for Datatype from the list of values.

REP–0529 Valid options are ’Box’, ’Graphic’, ’Line’ or ’Text’.

The value you entered in Type for the boilerplate was not one of the validtypes.

Select a value for Type from the list of values.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You tried to import a file into a field that has a maximum width less than thesize of the file. Oracle Reports only imported as much of the file as could fit inthe field.

If you wish to import the entire file, increase the size of the field.

REP–0531 Invalid Object Type. See the list of values.

In the Navigate to Object dialog box, you entered an invalid value for ObjectType.

Select a value from the list of values.

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

The value you entered in the Object Name field of the Navigate to Object dialogbox does not correspond to an object of the specified type in the report.

Make sure that you specified the name correctly and that the object is containedin the current report.

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

You selected Edit—>Import while in a non–text entry field (e.g., a field thataccepts only a number). You can only import into a text entry field in aproperty sheet.

If you wish to import something, move to a text entry field to do so.

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

You selected Edit—>Export... while in a non–text entry field (e.g., a field thataccepts only a number).

You can only export from a text entry field in a property sheet.

REP–0535 There is no object named <object name> in the database.

You tried to perform an operation on a module stored in the database, butOracle Reports could not find the object.

Make sure that you specified the name correctly and are connected to thedatabase where the module resides.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You tried to delete an object that you do not own. To delete an object, you mustbe the object’s owner.

Have the owner delete the object, if possible.

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

You tried to rename an object that you do not own. To rename an object, youmust be the object’s owner.

Have the owner rename the object, if possible.

REP–0538 There is already an object named <object name> in the database.

The name that you entered for the object is already used for an existing object.

Give the object a different name to avoid the conflict or delete the existingobject.

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

The default parameter form is too big to fit on the number of pages specified.

Select Tools—>Default Parameter Form.... Increase the number of pages thatthe parameter form can span.

REP–0540 Page size too small for default parameter form.

The current Form Width and Form Height settings are too small for the defaultparameter form.

Increase the size of the parameter form pages in the Report Properties propertysheet by changing Form Width and Form Height. Alternatively, you candefault the parameter form by selecting Tools—>Default Parameter Form...and reduce its size by editing it in the Parameter Form editor.

REP–0541 Source must be a report.

For R25RUN, R25CONV, or File—>Convert..., you specified something otherthan a report as the source. These operations all require a report as theirsource.

Specify a report as the source for the operation.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0542 No date masks have been specified as preferences.

While in the Parameter or Field property sheet of a parameter/field of TypeDate, you chose the List button for Input Mask or Format Mask, but no masksare specified in the Date Mask list of the Preferences tab of the Tools Optionsdialog box.

Enter a date format mask manually or go to the Preferences tab of the ToolsOptions dialog box and enter some date format masks in the Date Mask list.

REP–0543 No number masks have been specified as preferences.

While in the Parameter or Field property sheet of a parameter/field of TypeNumber, you chose the List button for Input Mask or Format Mask, but nomasks are specified in the Number Mask list of the Preferences tab of the ToolsOptions dialog box.

Enter a number format mask manually or go to the Preferences tab of the ToolsOptions dialog and enter some number format masks in the Number Mask list.

REP–0544 The on–line help system is not available.

You selected Help—>Help System, but help could not be found. This mayhave happened because the help files could not be found or because of a helpsystem error.

Ensure that the help files and help system are properly installed. If they areand the error persists, you should contact Oracle Customer Support forassistance. For more information, see “Calling Oracle Customer Support” onpage 1 – 4.

REP–0545 The number must be greater than 0.

You entered zero for Page Width, Page Height, or Logical Page Size in theReport Properties property sheet. You must enter a number greater than zero.

Enter a number greater than zero for Page Width, Page Height, or Logical PageSize.

REP–0546 Invalid parameter input.

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 parameterwith a datatype of Number.

Re–try the operation, entering a valid value for the parameter.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0548 Problem initializing Oracle Toolkit.



REP–0549 Destination type must be ’File’, ’Printer’, ’Mail’, or ’Sysout’ in batch mode.

You tried to run a report in the background (i.e., BATCH=YES), but youspecified a DESTYPE that is invalid for running in the background.

Change the DESTYPE to File, Printer, Mail, or Sysout, or do not run the reportwith BATCH=YES.

REP–0550 Invalid Parent Group.

The name you entered does not identify a valid parent group in the report youare currently defining.

Select a group from the list of values.

REP–0551 Invalid Parent Column.

The name you entered does not identify a valid parent column in the reportyou are currently defining. The column you specified does not exist in theparent group.

Select a column from the list of values. If the column you want does notappear, add it to the SELECT statement of the parent query of the groupspecified in Parent Group.

REP–0552 Invalid Child Column.

The name you entered does not identify a valid child column in the report youare currently defining. The column you specified does not exist in the query.

Select a column from the list of values. If the column you want does notappear, add it to the SELECT statement of the query.

REP–0553 Invalid Condition.

The Condition you entered for the query is not among the valid choices.

Select a value from the list of values for Condition.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0554 Valid options are ’WHERE’, ’HAVING’, or ’START WITH’.

The value you entered in SQL Clause is not one of the valid choices.

Select a value from the list of values for SQL Clause.

REP–0555 Warning: ’START WITH’ is ORACLE–specific SQL syntax. Report will notrun against non–ORACLE database.

The START WITH clause is only available with the ORACLE database. If youare not connected to any database or you are connected to a non–ORACLEdatabase, this warning is raised.

Ensure that you either run the report against an ORACLE database or removethe START WITH clause before running it against a non–ORACLE database.

REP–0556 No data links were created. No foreign key in the child query ’<queryname>’ refers to a primary key in the parent query ’<query name>’.

You attempted to create a query–to–query link but no foreign key exists in thechild query.

Verify whether the tables referred to are on your local database and accessible.If so, add the appropriate column constraints if desired.

REP–0559 Note: The query ’<query name>’ has created the bind parameter’<parameter name>’.

The specified query references a bind parameter that did not exist.

None. Oracle Reports has already created the necessary bind parameter.

REP–0560 Invalid Group.

The group name you entered in Group is not a valid group for the column. Thegroup you specified does not exist or cannot own the column.

Create or modify the group such that it can own the column. A databasecolumn 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 thegroup(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–0561 Valid options are ’Formula,’ ’Summary,’ or ’Placeholder’.

The value you entered in Type for the column was not one of the valid choices.

Select a value from the list of values for the column’s Type.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0562 Invalid Column Datatype. See the list of values.

The value you entered in Datatype is not one of the valid choices.

Select a value from the list of values for Datatype.

REP–0563 Valid options are ’Ascending’, ’Descending’, or blank.

The value you entered in Break Order is not one of the valid choices.

Select a value from the list of values for Break Order.

REP–0564 Invalid File Type.

The file type value you entered in Read From File was not one of the validtypes. You either misspelled the value or the value you entered does not exist.

Select a file type from the list of values for Read from File.

REP–0565 Invalid Function. See the list of values.

The function you entered for Function is not one of the valid choices.

Select one of the functions from the list of values.

REP–0566 You may not delete a database column.

You tried to delete a column with a Type of Database.

Remove the column from the SELECT list of the query that selects it and thecolumn will be deleted automatically.

REP–0567 Invalid Summary Source. See the list of values.

The column you entered in Source for the summary is not one of the validchoices. 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 usenumeric functions (such as Percent, Sum, or Average) unless theDatatype is Number.


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 DatatypeNumber.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0568 Value if Null is invalid.

The value of Value if Null in the Column property sheet is invalid for thatcolumn. For example, if datatype of the column is Number, and you specify acharacter string in Value if Null, you will receive this error.

Specify a valid value for Value if Null.

REP–0580 Invalid Filter Type. See the list of values.

The value you entered for Type under Filter is not one of the valid choices.

Select one of the filter types from the list of values.

REP–0581 This is the only group of query ’<query name>’, and may not be deleted.

The group you tried to delete is the only one of the query. Each query musthave at least one group.

If you want to delete the group, delete the group’s query.

REP–0582 You can not move a group out of its query.

You cannot move a group between queries. Groups can only be moved withinthe set of groups belonging to the same query.

You can create a group similar to the one you were trying to move under theother query, if possible.

REP–0583 Invalid SQL Select Statement.

The SQL SELECT statement that you entered is not valid.

Check the SELECT statement for errors and correct them. For moreinformation, see the ORACLE7 Server SQL Language Reference Manual.

REP–0584 Lexical parameters are not permitted in External Queries.

You made a lexical reference in your external query. You cannot make lexicalreferences from an external query.

Delete the reference altogether or, if possible, change it to a bind reference.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

You have deleted a query without deleting references to its groups in datalinks. This usually happens when you have deleted a query without cascadingthe deletion to its associated objects.

Update the data link in the child query.

REP–0586 Adding this data link will create a cycle.

The group you specified as the parent group for the data link is not eligible tobe a parent because it is, directly or indirectly, a child of the query to which youare linking it.

If possible, move the group such that it is not a child of the query and thereforeeligible to be its parent group. Otherwise, there is no action you can take.

REP–0587 Invalid PL/SQL Group Filter condition.

You selected Condition for Filter Type, but entered no PL/SQL condition.

Enter your PL/SQL or change the Filter Type. For more information aboutusing PL/SQL within Oracle Reports, see “PL/SQL Interface” in Chapter 13 ofthe Reports Reference Manual. For more information about PL/SQL, see thePL/SQL User’s Guide and Reference.

REP–0588 Invalid PL/SQL Column Formula.

You selected Formula as the column’s Type, but entered no PL/SQL for theformula.

Create a formula or change the column’s Type. For more information aboutusing PL/SQL within Oracle Reports, see “PL/SQL Interface” in Chapter 13 ofthe Reports Reference Manual. For more information about PL/SQL, see thePL/SQL User’s Guide and Reference.

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

In the Previewer, you tried to go to a page number that is larger than the totalnumber of pages formatted, i.e., you tried to go to a page that does not exist.

None. You cannot scroll down from the last page of the report.

REP–0591 You are already on the first page.

In the Previewer, you selected First while you were already on the first page ofthe report.

None. You cannot scroll up from the first page of the report.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0592 You are already on the last page.

In the Previewer, you selected Last while you were already on the last page ofthe report.

None. You cannot scroll down from the last page of the report.

REP–0593 Page ’<page number>’ is the current page.

In the Previewer, you entered the page number of the current page and choseGo To.

If you intended to go to another page, enter a different page number and choseGo To.

REP–0594 No report output generated.

The report you ran resulted in no output.

Check the accompanying messages for errors in the data model and layout. Ifthe problem persists, contact Oracle Customer Support for assistance.

REP–0595 Report definition modified. Re–running report.

You ran a report and while its output was still in the Previewer you modifiedthe report definition. If you return to the Previewer without re–running thereport, the report output is not updated to reflect the most recent changes and,consequently, the report must be run again.

Close the Previewer and run the report again.

REP–0596 Number can not be bigger than ’<number>’ or less than 1.

You entered an invalid value for the Page Number setting on the Field propertysheet for a parameter form field. The most likely cause is that you enteredzero, a negative number, or a number that is larger than the largest allowablevalue.

Enter a number within the range shown in the message.

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

You tried to move editor objects in such a way that they would be off thescreen.

Re–try the operation so that it will not move objects off the screen.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0598 You have moved the anchor end point out the boundary of the object, pleasetry again.

In moving an anchor, you moved the end point off of the boundary of the objectit anchors

Move the anchor such that its endpoint is still on the boundary of the object.

REP–0599 This text boilerplate is not editable.

You attempted to edit the text of an external boilerplate object while it wasdisplayed in the Layout editor.

If you wish to edit the text of the external boilerplate object, exit the report andedit the file containing the external boilerplate text using a text editor.

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

You attempted to access a list of values for the current field when none isavailable.

No action necessary.

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

You tried to select from a list of values and the list of values has no values. Inorder for some lists of values to contain values, another part of your reportmust be built first. For example, if a list of values is made up solely of columnnames and you have not completed your data model, you may get this error.

Building your report fully should fix this error. If the error persists, contactOracle Customer Support. For more information, see “Calling OracleCustomer Support” on page 1 – 4.

REP–0602 Unable to read list of tables.

The dictionary view of accessible tables is not present or not available.

See your DBA.

REP–0603 Unable to describe table <table name>.

The dictionary view of accessible tables is not present or not available.

See your DBA.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0604 Unable to build SELECT statement – no values selected.

You accepted the Table and Columns Names dialog box without havingselected anything with which to build the SELECT statement. If you choose thecolumns or table radio button, but no columns or tables are selected when youaccept the dialog box, you will get this error message.

Select a table and, if desired, column(s) or choose the SELECT columns FROMtable radio button, and then accept the dialog box. To exit the dialog boxwithout building a SELECT statement, choose the Close button.

REP–0606 Unable to read link file <filename>. Check link file format.

The file you specified in the Link File field of the Boilerplate property sheetcannot be found or its format does not match that specified in the Format field.

Ensure that you correctly specified the name of the file and that the value youentered in the Format field matches the format of the file.

REP–0607 Run–only file <filename> may not be opened.

You attempted to open a runfile (extension .rep). Runfiles cannot be opened,they can only be executed.

Open the report definition that is associated with the .rep file. It should have anextension of .rdf.

REP–0608 Invalid Source Type. See the list of values.

You selected File—>Convert... and the source type that you specified is notvalid.

Select the source type from the list of values.

REP–0609 Invalid Destination Type. See the list of values.

You selected File—>Convert... and the destination type is not valid.

Select the destination type from the list of values.

REP–0610 Error while attempting to print screen. Make sure log file <filename> isaccessible.

Oracle Reports attempted to write the contents of the screen to the fileprintdef.dat but could not locate the file.

To determine the proper location for printdef.dat, see your Developer/2000Installation Guide.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0611 Valid options are ’Screen’, ’File’, ’Printer’, or ’Mail’.

In the Runtime Parameter Form, you provided a value for Destination Typethat was not valid.

Specify a value of Screen, File, Printer, or Mail for Destination Type.

REP–0612 Invalid date mask.

The date mask that you entered does not correspond to any of the valid datemasks.

Check to make sure that you entered the mask correctly. For more information,see “Format Mask” in Chapter 8 of the Reports Reference Manual.

REP–0613 Value does not match mask ’<mask string>’.

The mask you entered in Format Mask is not a valid mask. The possiblecauses 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 ofCharacter.


If Case 1: Select a value from the list of values. For more information, see“Format Mask” in Chapter 8 of the Reports Reference Manual.

If Case 2: Change the Datatype of the field to be Number, if possible. If the fieldis supposed to be Character Datatype and cannot be changed, youcannot have a format mask for it.

REP–0614 There is no window active for your search/replace action.

You attempted a search/replace operation using the Search/Replace dialogbox, but did not have the cursor positioned in an active Oracle Reportswindow.

Position your cursor in a text entry field before you perform a search/replaceoperation.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0615 You can only search/replace a text entry field.

You attempted a search/replace operation using the Search/Replace dialogbox, but did not have the cursor positioned in a text entry field. Search/replaceoperations are valid only in text entry fields.

Position your cursor in a entry field before you perform a search/replaceoperation.

REP–0616 You cannot replace text in an uneditable region.

Using the Search/Replace dialog box, you attempted to replace text in aninaccessible field.

You can replace text only in editable regions.

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

You tried to run a report with the Runtime Parameter Form already open.

Close the currently open Runtime Parameter Form and try running again.

REP–0618 Warning: Previewer is already opened. To run a new one, please close theold one and run again.

You tried to run a report with the Previewer already open.

Close the currently open Previewer and try running again.

REP–0619 You cannot run without a layout.

You attempted to run your report with no layout. The report would be empty.

Create a layout, then run your report.

REP–0621 Invalid Vertical Sizing. See the list of values.

The value you entered for the object’s Vertical Sizing is not one of the validvalues.


REP–0622 Invalid Horizontal Sizing. See the list of values.

The value you entered for the object’s Horizontal Sizing is not one of the validvalues.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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

The value you entered for the Type of the Print Condition is not one of the validvalues.


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

The value you entered for the Object of the Print Condition is not one of thevalid values.


REP–0625 Invalid Text Alignment. See the list of values.

The value you entered for Alignment was not one of the valid values. Thevalue is not valid given the datatype of the object. Flush/Left, Flush/Center, andFlush/Right are only valid for fields with Datatype of Character.


REP–0626 You must specify the object’s position.

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

Enter a coordinate that is in the valid range.

REP–0627 An object’s height or width must be a positive integer.

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

Enter a positive, whole number.

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

The number that you entered is too large or too small.

Specify a number that is within the range shown in the message.

REP–0631 String must be shorter than <number> characters.

The string that you entered is too large.

Enter a string that is smaller than the number of characters shown in themessage.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0632 Value already exists in the list.

You attempted to add an item to a list, but the item was previously added tothe list. For example, if you attempted to add lib1 to your report’s AttachedLibrary list, and lib1 was already found in the Attached Library list, you wouldreceive this error.

Once an item has been added to a list, it does not need to be added again.

REP–0633 No value specified.

You attempted to perform a list operation on an item, but you did not specifyan item. For example, if you attempted to add a library to your report’sAttached Library list, but you left the Library field in the Attached Librariesdialog box blank and chose the Add button, you would receive this error.

Specify the item you wish to add in the appropriate field before choosing abutton.

REP–0634 Destination name must be shorter than <number> character(s).

You specified a destination (probably a filename) that is too long. Destinationnames must be shorter in length.

Specify the filename again and ensure that it is of valid length.

REP–0635 Value does not exist in the list.

You specified a value that is not in the list of valid choices. It could be that youtyped the value rather than using the list of values.

Specify one of the valid choices in the list. If possible, use the list of values toensure that it is a valid choice.

REP–0640 Invalid Field Source. See the list of values.

You entered an invalid value in the field’s Source setting.


REP–0645 Close property sheets for all the selected objects and retry.

You tried to bring up the Common Properties property sheet while the propertysheet for at least one of the selected objects was already being displayed.

Close all open property sheets and try again.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0650 Invalid Source Group. See the list of values.

The group name you entered in Source for the repeating frame is not valid.


REP–0651 Invalid Print Direction. See the list of values.

The value you entered for Print Direction was not one of the valid values(Across, Across/Down, Down, Down/Across, and Matrix Cell).


REP–0652 Invalid Vertical Spacing.

You did not enter a number for the Vertical Spacing field and you tried to leavethe field or accept the Repeating Frame property sheet.

Enter zero or a positive integer for Vertical Spacing. If you want to leave theproperty sheet without saving changes or making further updates, choose theClose button.

REP–0653 Invalid Horizontal Spacing.

You did not enter a number for the Horizontal Spacing field and you tried toleave the field or accept the Repeating Frame property sheet.

Enter zero or a positive integer for Horizontal Spacing. If you want to leave theproperty sheet without saving changes or making further updates, choose theClose button.

REP–0654 Invalid value for maximum records per page.

You did not enter a number or blank for Maximum Records per Page and youtried to leave the field or accept the Repeating Frame property sheet.

Enter blank or a positive integer for Maximum Records per Page. If you wantto leave the property sheet without saving changes or making further updates,choose the Close button.

REP–0655 Invalid value for minimum widow records.

You did not enter a number or blank for Minimum Widow Records and youtried to leave the field or accept the Repeating Frame property sheet.

Enter blank or a positive integer for Minimum Widow Records. If you want toleave the property sheet without saving changes or making further updates,choose the Close button.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0660 Invalid button source. You must select a column.

You selected Multimedia Column as the source for your button action, theneither did not specify a source column, or specified an invalid source column.

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–0661 Invalid button source. You must specify a source file.

You selected Multimedia File as the source for your button action, then eitherdid not specify a source file, or specified an invalid source file.

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–0662 Invalid button icon.

You selected Icon as the button face, but failed to name a valid icon.

Enter the name of a valid icon file in the text field provided. Include allnecessary path information.

REP–0670 Invalid boilerplate type. See the list of values.

The value you entered in Type for the boilerplate was not one of the validvalues (Box, Line, Graphic, and Text).

Select a Type from the list of values.

REP–0671 Invalid link file name.

The file to which you tried to link the boilerplate is not a valid file.

Re–enter the name, making sure that it references an existing file in the currentdirectory.

REP–0672 Invalid value for minimum widow lines.

You did not enter a number or blank for Minimum Widow Lines in theproperty sheet and you tried to leave the field or accept the property sheet.

Enter blank or a positive integer for Minimum Widow Lines. If you want toleave the property sheet without saving changes or making further updates,choose the Close button.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0680 Invalid anchoring object name. See the list of values.

The object name you entered in the Anchored To field of the Anchor Positiondialog 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 objectname.

Select an object name for Anchored To from the list of values. If you want toleave the dialog box without saving the changes or further modifying its fields,choose the Close button.

REP–0681 Invalid Edge. See the list of values.

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 withoutentering a valid edge for the anchor.

Select a value for Parent Edge or Object Edge from the list of values. If youwant to leave the dialog box without saving the changes or further modifyingits fields, choose the Close button.

REP–0682 The anchor point must be a percentage between 0 and 100.

The value you entered for % is not in the valid range (0 to 100). You tried toaccept the dialog box or move to another field without entering a valid valuefor %.

Enter a value in the valid range for %.

REP–0690 Invalid Starting Page Number.

You left Start At blank. You tried to leave the Start At field or accept the PageNumbering dialog box without entering a value for Start At.

Enter zero or a positive integer for Start At. If you want to leave the dialog boxwithout saving the changes or making further changes, choose the Closebutton.

REP–0691 Invalid Page Increment.

You left Increment By blank. You tried to leave the Increment By field or acceptthe Page Numbering dialog box without entering a value for Increment By.

Enter zero or a positive whole number for Increment By. If you want to leavethe dialog box without saving the changes or making further changes, choosethe Close button.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0692 Invalid Page Number Reset.

You left Reset At blank. You tried to leave the Reset At field or accept the PageNumbering dialog box without entering a value for Reset At.

Select a repeating frame name or &Report from the list of values to indicatewhere you want to reset the page number to its Start At value. If you want toleave the dialog box without saving the changes or making further changes,choose the Close button.

REP–0700 Invalid Color. See the list of values.

The color that you entered in the field is not one of the valid choices.

Select a color for the field from the list of values.

REP–0701 Invalid Pattern. See the list of values.

The pattern that you entered in the field is not one of the valid choices.

Select a pattern for the field from the list of values.

REP–0702 Invalid Pen Width.

The value that you entered for the pen width is not one of the valid choices.

Select a pen width from the list of values.

REP–0703 Invalid Font. See the list of values.

The font that you entered is not one of the valid choices.

Select a font from the list of values.

REP–0704 Invalid Text Style. See the list of values.

The text style you entered is not one of the valid styles.

Select one of the styles from the list of values.

REP–0705 Invalid Text Weight. See the list of values.

The text weight you entered is not one of the valid weights.

Select one of the weights from the list of values.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0706 Invalid Text Size.

The point size that you entered is not one of the valid choices.

Select a valid point size from the list of values.

REP–0707 Invalid Text Spacing.

You have entered number for spacing that is not in the valid range.

Enter a number in the valid range.

REP–0708 Invalid Character Mode Attribute. See the list of values.

The value you entered in this field is not valid. The values you enter inCharacter Mode Attribute must be defined in your Oracle Terminal or printerdefinition. (To have these attributes appear in the list of values, you must alsolist them in VISUAL_PREFS in the preferences file.)

Select the desired values from the list of values. If the value you want is not inthe list of values, you can check your Oracle Terminal or printer definition tosee if the value is a valid one.

REP–0709 ’Sysout’ is only valid in batch mode.

You entered Sysout as the destination type when you were not running thereport 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 itwhen not running in batch mode. You might have accepted itwithout knowing it if you have the Hide Parameter Form preferencechecked.


If Case 1: Run the report again, but enter a DESTYPE of something other thanSysout unless you are running in batch mode.

If Case 2: Change the Initial Value for DESTYPE to something else or change theDESTYPE to something other than Sysout in the Runtime ParameterForm. If you leave the Initial Value as Sysout, you should not run innon–batch mode with Hide Parameter Form checked.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0710 Unable to find printer description file.

Oracle Reports could not find the printer description file you specified forDESFORMAT.

Specify a valid printer description file for DESFORMAT (e.g., dflt).

REP–0711 Destination type must be ’File’, ’Printer’, or ’Mail’ when printing frompreviewer.

You pressed the Print button in the Previewer, but DESTYPE is restricted to avalue other than File, Printer, or Mail.

Ensure that DESTYPE can be set to one of the above values before attemptingto print from the Previewer.

REP–0712 No printer specified.

You attempted to print a report, but did not specify a printer name in eitherDESNAME or in the Printer Chooser dialog box.

Specify a valid printer name using DESNAME. If you often print to the sameprinter, enter the printer name in the Printer Chooser dialog box. Rememberthat entering a printer name using DESFORMAT will override the printer nameset in the Printer Chooser dialog box.

REP–0713 Invalid printer name <printer name> specified by parameter <parametername>.

You attempted to output a report, but did not specify a valid printer name orprinter driver name (depending on which is applicable for your platform) inDESFORMAT (if DESTYPE was File or Mail) or DESNAME (if DESTYPE wasPrinter).

Specify a valid printer name for DESFORMAT if DESTYPE was File or Mail, ora valid printer name for DESNAME if DESTYPE was Printer.

REP–0714 Invalid mail destination.

You attempted to mail report output to another user, but did not specify a validusername for DESNAME.

Specify a valid username for DESNAME.

REP–0715 Trace file must be specified when tracing.

You specified trace mode and/or trace options but did not specify a trace file.

Specify a trace file.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0716 Invalid option specified for tracing.

You specifed invalid trace options.

Re–specify your trace options. For more information about trace options, seeyour online help.

REP–0717 Cannot set/unset options if not tracing.

You attempted to set or unset trace options while not tracing.

Begin tracing before you attempt to set or unset options.

REP–0718 Cannot trace break information with runtime executable.

You attempted to trace breaks while running the report using the runtimeexecutable.

Do not specify the Break option when using the runtime executable.

REP–0719 Cannot write to trace file <filename>.

You specified a trace file to which you cannot write.

Check the given trace file name to ensure that it is valid.

REP–0720 Invalid Repeating Frame. See the list of values.

The repeating frame that you specified as the Vertical or Horizontal Frame inthe Matrix property sheet is not valid. You tried to leave the Vertical orHorizontal Frame field without entering a valid repeating frame.

Select a repeating frame name from the list of values. If you want to leave theproperty sheet without saving the changes or making further changes, selectthe Close button.

REP–0721 Invalid Cross Product Group. See the list of values.

The group that you entered for Cross Product Group in the Matrix propertysheet is not valid.

Select a group name from the list of values. If you want to leave the propertysheet without saving the changes or making further changes, select the Closebutton.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0724 Cannot get the value of Column ’<column name>’ here.

You attempted to get the value of the specified column via either issuing acommand from the command line of the PL/SQL Interpreter or by executing astand–alone PL/SQL program unit. You can only get a column value duringreport execution.

Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to getthe value of a column when the report has suspended execution (e.g., at abreakpoint). Use an alternate method, such as one of the report–level triggers,to obtain the column value.

REP–0725 Cannot set the value of Column ’<column name>’ here.

You attempted to set the value of the specified column via either issuing acommand from the command line of the PL/SQL Interpreter or by executing astand–alone PL/SQL program unit. You can only set a column value duringreport execution.

Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to setthe value of a column when the report has suspended execution (e.g., at abreakpoint). Use an alternate method, such as one of the report–level triggers,to set the column value.

REP–0726 Cannot get the value of Parameter ’<parameter name>’ here.

You attempted to get the value of the specified parameter via either issuing acommand from the command line of the PL/SQL Interpreter or by executing astand–alone PL/SQL program unit. You can only get a parameter value duringparameter form execution.

Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to getthe value of a parameter when the report has suspended execution (e.g., at abreakpoint). Use an alternate method, such as one of the report–level triggers,to obtain the parameter value.

REP–0727 Cannot set the value of Parameter ’<parameter name>’ here.

You attempted to set the value of the specified parameter via either issuing acommand from the command line of the PL/SQL Interpreter or by executing astand–alone PL/SQL program unit. You can only set a parameter value duringparameter form execution.

Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to setthe value of a parameter when the report has suspended execution (e.g., at abreakpoint). Use an alternate method, such as one of the report–level triggers,to set the parameter value.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0728 Column ’<column name>’ may not be referenced by parameter triggers.

You attempted to reference a column in a parameter–related trigger (BeforeForm, After Form, Validation), which is not allowed.

Remove the reference(s) from the parameter–related trigger(s) and add them tothe Before Report trigger.

REP–0729 The program unit ’<program unit name>’ of size ’<number>’ bytes is too bigto be loaded for current platform at the limit of ’<limit>’

Your program unit was created on another operating platform and it too largeto be loaded into the current operating platform.

Reduce the size of the PL/SQL program unit you are trying to load.

REP–0730 The following bind variable is not defined: <bind variable>

You made a bind reference to a parameter or column that has not been definedyet. You must define the parameter or column before making a bind referenceto it.

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, ifpossible.

REP–0732 Error destroying program unit.



REP–0733 Name already exists. Please select another name.

You attempted to create a PL/SQL subprogram whose name is identical to anexisting subprogram stored in the report.

Rename the new subprogram so that it does not conflict with any existingsubprograms.

REP–0734 No argument is allowed. Needs to be removed.

You entered a PL/SQL function or procedure requiring arguments in a PL/SQLfield that does not allow PL/SQL with arguments—for example, in a FormatTrigger field, a Formula field, or as a group filter.

Remove the argument(s) from the PL/SQL source.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0735 Unable to load DE Program Unit. Will try to load PL/SQL source texts. Makesure you are connected to a database.

Oracle Reports could not load the entire program unit. It could be that theprogram unit references one or more objects stored in the database, but theseobjects could not be found.

Make sure you are connected to the correct database. Also check to ensure thatyour program unit is making the correct references.

REP–0736 There exists uncompiled program units.

You have attempted to convert a report, or loaded an old report, containingPL/SQL which needed to be recompiled.

Load the report using R25DES and modify the DE program unit(s).

REP–0737 Should be a function with return type <returntype>.

You have entered PL/SQL that does not have the appropriate return type.

Change the return type of the function to the one specified in the message.

REP–0738 Only function is allowed here.

You have entered something other than a function where a function is required.

Enter a function.

REP–0739 Cannot execute compiled PL/SQL from other platform.

You tried to run a report on a platform that is not the same as the platform onwhich the PL/SQL in the report was compiled. The report does not contain thePL/SQL source and, as a result, Oracle Reports could not recompile thePL/SQL on the current platform.

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 andrecompile it from the current platform.

REP–0740 An anchor cannot be anchored with another object.

You attempted to anchor an anchor to another layout object, or anchor a layoutobject to an anchor.

Anchors cannot be anchored with other layout objects.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0741 A matrix cannot be anchored with another object.

You attempted to anchor a matrix object to another layout object, or anchor alayout object to a matrix object.

Matrix objects cannot be anchored with other layout objects.

REP–0742 A margin cannot be anchored with a layout object.

You attempted to anchor the margin to a layout object, or anchor a layout objectto the margin.

The margin cannot be anchored with layout objects.

REP–0743 A matrix repeating frame cannot be anchored with another object.

You attempted to anchor a matrix repeating frame with a Print Direction ofDown or Across to another layout object.

Matrix repeating frames with Print Directions of Down or Across cannot beanchored with other layout objects.

REP–0744 An anchor must have different parent and child objects.

You attempted to create an anchor whose parent and child objects are thesame—i.e., you tried to anchor an object to itself.

You cannot anchor an object to itself. Anchors must have different parent andchild objects.

REP–0745 An object cannot be anchored more than once.

You attempted to create two anchors between the same two layout objects.

You can create only one anchor between the same two layout objects.

REP–0746 PL/SQL references an object which does not exist.



REP–0747 Before form trigger cannot reference a report column.

The Before Form trigger for the report references a column in the report. Youcannot reference columns from the Before Form trigger.

Remove any column references from the Before Form trigger. (If you need toset the value of a column, you should do it from the Before Report trigger.)

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0748 A parameter trigger cannot reference report columns.

A Validation Trigger for a parameter references one or more columns in thereport. You cannot reference columns from a Validation Trigger.

Remove any column references in the Validation Trigger of the Parameterproperty sheet.

REP–0749 After Form trigger cannot reference a report column.

The After Form trigger for the report references a column in the report. Youcannot reference columns from the After Form trigger.

Remove any column references in the After Form trigger. (If you need to setthe value of a column, you should do it from the Before Report trigger.)

REP–0750 Error closing the PL/SQL library.



REP–0751 Error accessing program units from the PL/SQL library.

This is an abnormal condition. If you made any changes to your externalPL/SQL library, consider selecting File—>Save As... and save it under adifferent name.


REP–0752 Unable to save the PL/SQL library.

This is an abnormal condition. If you made any changes to your externalPL/SQL library, consider selecting File—>Save As... and save it under adifferent name.


REP–0753 Error attaching PL/SQL library ’<libname>’.

You tried to attach an invalid external PL/SQL library. This could happenbecause the library is corrupted, or because the file or object you named doesnot contain an external PL/SQL library.

Make sure that the file or object you named contains a valid external PL/SQLlibrary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0754 Error in inserting program units into the PL/SQL library.

You tried to save a program unit into a corrupted external PL/SQL library, or afile or object that is not an external PL/SQL library.

Ensure that the file or object you named contains a valid external PL/SQLlibrary and consider using File—>Save As... to save the current program unit.

REP–0755 Error opening the PL/SQL library ’<libname>’.

You tried to open a corrupted external PL/SQL library, or a file or object that isnot an external PL/SQL library.

Make sure that the file or object that you tried to open contains a valid externalPL/SQL library.

REP–0756 Warning: Unable to find PL/SQL library ’<libname>’.

You tried to attach an external PL/SQL library that doesn’t exist, or to open areport with one or more attached libraries that could not be found.

Make sure that the file or object you want to attach exists. If you opened areport, reattach the external PL/SQL library.

REP–0757 Unable to create external location spec.



REP–0758 PL/SQL library ’<libname>’ is already in use.

You tried to attach an external PL/SQL library that has the same name asanother external PL/SQL library that is already attached. This could happen ifyou renamed a file that contains an external PL/SQL library, but the internalname recognized by Oracle Reports was not changed.

Use File—>Save As... to save the external PL/SQL library under a differentname.

REP–0759 One or more PL/SQL libraries have been modified since the report was saved.The PL/SQL will be recompiled.

You are trying to open or run a report that references one or more externalPL/SQL libraries, and if a library attached to your report has been modified,Oracle Reports invalidates the PL/SQL within the report to remind you to addsuch changes (e.g., number or type of parameters) to the calling functions.

Make sure your report–level PL/SQL correctly references attached libraries.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0760 You are in the print document session.

You already selected File—>Administration—>Report Doc to produce a reporton one or more reports.

Finish producing the current report on reports, then selectFile—>Administration—>Report Doc again to run another report on reports.

REP–0761 Can’t open the resource for printing the report.

Oracle Reports cannot find the reports (shipped with Oracle Reports) thatdocument your reports.

Make sure that the reports that document other reports (shipped with OracleReports) are located in the proper directory. For details on the exact location ofthese reports, see your Developer/2000 Installation Guide.

REP–0770 Before Form trigger failed.

The Before Form trigger in your report returned false.

Make the appropriate changes (either to the PL/SQL source in the Before Formtrigger or to the report) to make the trigger return true.

REP–0771 After Form trigger failed.

The After Form trigger in your report returned false.

Make the appropriate changes (either to the PL/SQL source in the After Formtrigger or to the report) to make the trigger return true.

REP–0772 Parameter Form Fields <fieldname1> and <fieldname2> may not have thesame Source.

You specified the same Source for two parameter form fields. Fields on theRuntime Parameter Form must have unique sources.

Change the Source of one of the fields.

REP–0773 No Source specified for Parameter Form Field <fieldname>.

You have not specified a Source for a parameter form field or the sourceparameter was deleted from the data model. Fields on the Runtime ParameterForm must have a source.

Specify a valid Source for the parameter form field.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0774 Warning: No selectable values for the LOV parameter ’<parameter name>’.

You have either not specified any values for the LOV parameter’s select list, orspecified values that cannot be selected.

Check the select statement or selectable value list of the parameter to ensurethat your specified values are selectable. For more information about LOVparameters, see “Parameter Properties” in Chapter 6 of the Reports ReferenceManual.

REP–0775 Warning: The datatype of the first column of the select statement does notmatch the datatype of the LOV parameter ’<parameter name>’.

The datatype of the first column you specified in your select statement does notmatch the datatype you specified for your LOV parameter.

Check the datatype of the LOV parameter, the select statement, and thecolumns in the database tables accessed by the select statement to ensure thatthey match.

REP–0776 Warning: There are columns values in segmented memory when populatingLOV parameter ’<parameter name>’. They will be ignored.

You have selected columns with values in segmented memory for your LOVparameter’s select list. This is not allowed.

Select different columns or move the columns’ values.

REP–0777 Warning: There are columns whose types cannot be handled whenpopulating LOV parameter ’<parameter name>’. They will be ignored.

You have selected columns whose types cannot be handled (e.g., binary data).

Select different columns.

REP–0778 Warning: Some columns cannot be formatted correctly when populatingLOV parameter ’<parameter name>’. These columns are ignored.

The SELECT statement selecting values for your parameter’s LOV retrievescolumns whose values annot be formatted according to their datatypes.

Convert the values to valid ones or check the database to see if the values of thecolumns are valid.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0779 Warning: Some items of LOV parameter ’<parameter name>’are too long.These columns are ignored.

You have either specified items or selected columns containing some valueswhich are too long to include in your LOV parameter’s select list.

Check the values of the items and reduce their length if necessary.

REP–0780 The initial value you have entered is invalid against the input mask ’<inputmask>’.

The value you entered in the Initial Value field violates the mask you specifiedin the Input Mask field.

You must either enter a different value in Initial Value or change the mask inInput Mask.

REP–0781 Bind variables are not allowed in the select statement.

You have included bind variables in your SELECT statement.

Remove the bind variables from your SELECT statement.

REP–0782 The datatype of the parameter doesn’t match the datatype of its sourcecolumn.

You have selected a column with an invalid datatype to furnish values for yourLOV parameter’s select list.

Change the column’s datatype or specify a different column.

REP–0783 The possible values list has bad syntax.

You used incorrect syntax to create the list of possible values for your LOVparameter.

Edit the possible values list to ensure that it is a proper comma–separated list.

REP–0784 A possible value has invalid width.

A value you specified for your LOV parameter’s list of possible values has aninvalid width.

Edit the possible values list so that all possible values have valid widths, oralter the width.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0785 A possible value is invalid against the input mask.

A value you specified for your LOV parameter’s list of possible values is notformatted in accordance with the specified input mask.

Edit the possible values list to ensure that all possible values are valid againstthe input mask.

REP–0786 The initial value is not among the possible values.

The initial value you specified for your LOV parameter does not appear on thedefined list of possible values.

Add the initial value you specified to the possible values list.

REP–0787 The name of the first column from the select statement is not the same atruntime from design time.

There is a discrepancy between the column(s) you specified in your originalSELECT statement and what the table(s) in question now contains.

Check the database to determine if the tables in question have been updatedsince you created the parameter list, or re–apply the LOV parameter’s SELECTstatement.

REP–0788 Warning: The value is not among the selectable values of the restricted LOVparameter.

You have specified a value for a LOV parameter that is not on the parameter’sselect list.

Choose a value from the parameter’s select list.

REP–0790 Page Width and Height must either both be specified or both be blank.

You specified a blank value for either Page Width or Page Height in theRuntime Settings tab of the Tools Options dialog box. Both settings mustcontain a valid value, or be blank.

Specify a valid value for the blank setting, or make both settings blank.

REP–0800 You can only select all in a text entry field.

You selected Edit—>Select All with the cursor positioned on an element in aproperty sheet other than a text field.

While in a property sheet, Edit—>Select All is valid only in a text field.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0801 Layout canvas must remain large enough to fit all layout objects.

You reduced the size of the painting region of the Layout editor by changingone or more settings in the Report Properties dialog box, or by resizing themargin, but the resized painting region is not large enough to fit all of thelayout objects.

Make sure all layout objects in the body, margin, header, and trailer sections ofyour report fit in the resized painting region.

REP–0802 Parameter form canvas must remain large enough to fit all parameter formobjects.

You reduced the size of the painting region of the Parameter Form editor bychanging one or more settings in the Report Properties dialog box, but theresized painting region is not large enough to fit all of the parameter formobjects.

Make sure all parameter form objects fit in the resized painting region.

REP–0803 Canvas size specified is too large.

Your report contains combined settings of page/form size and either logicalpage, maximum body page, maximum header page, maximum footer page, ornumber of parameter form pages that results in a value larger than thatsupported by Oracle Reports (a dpi value greater than 2 gigabytes).

Make the page/form size smaller, or decrease the value for logical page size,maximum body pages, maximum header pages, maximum footer pages, ornumber of parameter form pages.

REP–0804 The report definition was modified during the current run.

While in the Runtime Parameter Form, you modified the report via a editor orproperty sheet.

Cancel the Runtime Parameter Form and re–run the report.

REP–0805 Could not initialize menus.



REP–0806 Error reading window resources.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0807 You must enter the Array Size.

In the Runtime Settings dialog box, you left the Array Size field blank. Youmust enter a value for Array Size.

Enter an Array Size value between 1 and 9999.

REP–0808 You must enter the Buffer Size.

In the Runtime Settings tab of the Tools Options dialog box, you left the BufferSize field blank. You must enter a value for Buffer Size.

Enter a Buffer Size value between 1 and 9999.

REP–0809 You must enter the Long Chunk Size.

In the Runtime Settings tab of the Tools Options dialog box, you left the LongChunk Size field blank. You must enter a value for Long Chunk Size.

Enter a Long Chunk Size value between 1 and 9999.

REP–0810 Valid options are ’Noaction’, ’Rollback’, or ’Commit’.

In the character–mode Runtime Settings dialog box, you chose an invalid valuefor On Success/On Failure. Valid values are Noaction, Rollback, or Commit.

Select a valid value for On Success/On Failure.

REP–0811 Valid options are ’<In Report Definition>’, ’Screen’, ’File’, ’Printer’ or ’Mail’.

In the character–mode Runtime Settings dialog, you chose an invalid value forDestination Type. Valid values are <In Report Definition>, Screen, File,Printer, or Mail.

Select a valid value for Destination Type.

REP–0812 Valid options are ’<In Report Definition>’, ’Landscape’, or ’Portrait’.

In the character–mode Runtime Settings dialog, you chose an invalid value forOrientation. Valid values are <In Report Definition>, Landscape, or Portrait.

Select a valid value for Orientation.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0813 Valid options are ’<In Report Definition>’, ’Default’, ’Bitmap’ or ’Character’.

In the character–mode Runtime Settings dialog, you chose an invalid value forMode. Valid values are <In Report Definition>, Default, Bitmap, orCharacter.

Select a valid value for Mode.

REP–0814 Valid options are ’<In Report Definition>’, ’Yes’ or ’No’.

In the character–mode Runtime Settings dialog box, you chose an invalid valuefor Background. Valid values are <In Report Definition>, Yes, or No.

Select a valid value for Background.

REP–0815 Valid options are ’Landscape’, or ’Portrait’.

In the character–mode Runtime Parameter Form, you chose an invalid valuefor Orientation. Valid values are Landscape or Portrait.

Select a valid value for Orientation.

REP–0816 Valid options are ’Bitmap’ or ’Character’.

In the character–mode Runtime Parameter Form, you chose an invalid valuefor Mode. Valid values are Bitmap or Character.

Select a valid value for Mode.

REP–0817 Valid options are ’Yes’ or ’No’.

In the character–mode Runtime Parameter Form, you chose an invalid valuefor Background. Valid values are Yes, or No.

Select a valid value for Background.

REP–0818 Warning: Page height has changed for Parameter Form. Parameters might becrossed by page boundaries.

You changed the height of the Runtime Parameter Form in the ReportProperties property sheet. Oracle Reports is notifying you that this might causethe page boundary to move such that it appears in the middle of an object inthe parameter form.

Look at the layout of your parameter form in the Parameter Form editor andensure that none of the objects are directly on the page boundary (the darkenedline in the editor). Alternatively, you could default (or redefault) the parameterform.

Cause

Action

Cause

Action

Action

Cause

Action

Cause

Action

Cause

Action


REP–0819 Could not turn AUTOCOMMIT ON for SQL Server connection.


For information, see “Abnormal Conditions” on page 1 – 3. Another option isto remove all instances of SRW.DO_SQL. If you can do so while retaining allnecessary functionality in your report, it will run.

REP–0820 Cannot import specified image.

The image you are trying to import cannot be imported.

Check the image file to ensure it is a valid image and has not been corrupted.

REP–0821 Cannot export specified image.

Check that the name and ,

Failed to save the image. The possible causes of this error include:

Case 1: You are attempting to save the image to a non–valid location.

Case 2: You do not have the necessary privileges to access the table.

Case 3: There is not enough space to save the image.


If Case 1: Check that the name and path (if saving to the file system) is valid.

If Case 2: Check that you have permission to save the image.

If Case 3: Check that there is enough space to save the image.

REP–0822 No drawing imported.

The drawing you are attempting to import cannot be imported.

Check the file to ensure it is a valid drawing and has not been corrupted.

REP–0823 No drawing exported.

The object you are attempting to export as a drawing cannot be exported as adrawing.

Create or select a drawing to export.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0824 Data Dictionary not available on the database to which you are connected.Unable to retreive table information.

You are attempting to access the Table and Column Names dialog box but theData Dictionary is not available on the database to which you are connected.

Connect to another database.

REP–0825 The connected database is neither ORACLE nor DB2. It cannot be used tostore applications.

You are attempting to store a module to a database that is neither ORACLE norDB2. This is not allowed.

Either connect to an ORACLE or DB2 database or store the module as in yourfilesystem.

REP–0826 Invalid printer driver ’<name>’ specified by parameter <parameter name>.

You are trying to print a report, but the parameter DESNAME is specifying aprinter driver that cannot be used to print the report; e.g., you are specifying adriver other than the Oracle ASCII Driver to print a character mode report.

Enter the name of a valid printer driver as the value of the parameter.

REP–0827 Select exactly one image to export.

The current selection on the editor is not a single image.

Try the procedure again, making sure that you select only one image to export.

REP–0828 Oracle Reports tables are not installed in the database. Cancelling ReportDoc.

Report Doc cannot be run because there are no Oracle Reports tables in thedatabase.

Inform your database administrator that Oracle Reports tables were notsuccesfully installed in the database.

REP–0829 Oracle Reports database tables appear to match tables from an older versionof Reports. Cancelling Report Doc.

The Oracle Reports tables in the database appear to have been installed from aprevious version of the product. Report Doc cannot run against an olderversion of the database tables.

Inform your database administrator that Oracle Reports tables for this versionwere not successfully installed in the database.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–0830 Oracle Reports database tables appear to be corrupted or incorrectlyinstalled. Cancelling Report Doc.

Report Doc caoont be run because the Oracle Reports tables are in an unstablestate.

Inform your database administrator that Oracle Reports tables are eithercorrupted or incorrectly installed in the database.

REP–0900 Cannot close this application while PL/SQL is still executing.

You attempted to close a report while associated PL/SQL was still executing.

Finish executing the PL/SQL or abort it, then close the application.

REP–0901 Tabs/Col function not supported for this database.

You are connected to a database server which does not have an accessible DataDictionary to list tables and columns.

None. Tables and Columns functionality is not available for these databases.

REP–0999 Unimplemented Error:



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

The name you entered violates one or more SQL naming conventions.

Check the naming standards for the object you are naming. For moreinformation, see “Naming Conventions” in Appendix D of the Reports ReferenceManual. Enter a name that conforms to the conventions.

REP–1011 <Object type> must be named.

You left the Name field blank for the object and a name is required.

Name the object according to the appropriate naming conventions. For moreinformation, see “Naming Conventions” in Appendix D of the Reports ReferenceManual.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1012 There is another <object type> with this name.

The name that you entered duplicates the name of another object of the sametype.

Change the name of at least one of the objects.

REP–1013 This name may not be the same as a reserved word.

You entered a name for a parameter that duplicates a reserved word.

Change the name of the parameter such that it conforms to parameter namingconventions. For more information, see “Naming Conventions” in Appendix Dof the Reports Reference Manual.

REP–1014 Name length cannot exceed 30 bytes.

Name entered was greater than 30 bytes. Valid SQL names cannot be longerthan 30 bytes.

Reduce the size of the name to 30 bytes or less.

REP–1048 Warning: Owner and Access list not overwritten.



REP–1049 Cannot open a report saved with a newer version of Oracle Reports.

You tried opening a report with an older version of Oracle Reports than the onewith which the report was saved.

Use the same or a more recent version of Oracle Reports to open the report.

REP–1050 Unable to access module names in database.



REP–1051 Unable to save module to file <filename>.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1052 Unable to save module to database.



REP–1053 Unable to obtain new module ID from database.



REP–1054 Unable to delete from table <table name>.

You tried to delete from a table and the operation failed. You may not have thenecessary privileges.

Ensure that you have the necessary privileges. If you do not, see your DBA orhave someone with the necessary privileges perform the operation.

REP–1055 Unable to lock table <table name>.



REP–1056 Unable to rename object stored in database.

You tried to rename a database object and the operation failed. You may nothave the necessary privileges. You must own an object in order to rename it.

If you do not own the object, you can either make your own copy of it or havethe owner change the name.

REP–1057 <filename> is not a valid Oracle Reports file.

You tried to access a file that is not in the proper format for Oracle Reports.

Make sure you are accessing the correct file.

REP–1058 Unable to read module from database.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1059 Unable to read module from file <filename>.



REP–1060 Unable to read SRW2_MODULE.

Oracle Reports failed to access the SRW2_MODULE view in the currentdatabase.

Check to see if Oracle Reports was properly installed on the database. Forhelp, contact your system administrator.

REP–1061 Unable to read external file <filename>.

You activated Read From File and specified a file name as the value of acolumn, but Oracle Reports could not successfully open or read the specifiedfile.

Check the spelling of the specified file in the Column property sheet, and checkto see if the specified file exists. If the file does exist, check the permissions onthe file to ensure that you have at least read access.

REP–1062 Unable to find external query ’<query name>’.


Case 1: REPORTS25_PATH is not set.

Case 2: You are not connected to a database.

Case 3: The specified external query does not exist.


If Case 1: Set REPORTS25_PATH to a valid value.

If Case 2: Connect to a database.

If Case 3: Make sure you specify the correct name of the external query.

REP–1063 PL/SQL ’<program unit name>’ has exceeded the platform–specific sizelimit.

The PL/SQL could not be loaded because it is too large for your operatingsystem. It may have been created on a different platform with a higher limit.

Reduce the size of the PL/SQL so it can be loaded on your platform.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1064 Unable to read module ’<module name>’.

You attempted to open a module whose definition, stored in either the databaseor the filesystem, has been lost or corrupted.

This module cannot be used.

REP–1065 Unable to read external query ’<query name>’.

You attempted to read an external query whose definition, stored in either thedatabase or the filesystem, has been lost or corrupted.

This external query cannot be used.

REP–1066 Warning: Comment is corrupted. It will be lost.

A storage error caused a comment to be corrupted. It will be discarded.

No action is necessary. If you want to, recreate the comment in the designer.

REP–1067 Some information is missing in the report.

The report cannot be opened because the report definition is incomplete. Itmay have been corrupted.

If the report is stored in the database, use SQLPlus to determine whether theReports tables have been corrupted. If the report is an .rdf file, use a file systemutility to check if the file is corrupted. Take appropriate actions to recover yourdata.

REP–1070 Object Store failure.



REP–1071 end reached.



REP–1072 object not found.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1073 object found when not expected.



REP–1074 object too big.



REP–1075 invalid object.



REP–1076 invalid store.

You attempted to use an invalid file or database object.

Make sure the object you specified is a valid Oracle module, stored in a file orin the database.

REP–1077 invalid type.



REP–1078 non–specific file error.



REP–1079 unsupported function.



REP–1080 unique key violation.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1081 page split occurred.



REP–1082 close error.



REP–1083 file version error.



REP–1084 file header bad or missing.

You performed an operation that required Oracle Reports to open a file. Thefile either didn’t have a header or it didn’t have the expected header. Theheader may have been changed in an editor or the file may not be compatiblewith this release of Oracle Reports.

You can attempt to fix the header in an editor, although, in general, it is notrecommended that you edit Oracle Reports files in this way. If the file isincompatible with this release of Oracle Reports, you need to migrate it. Formore information, see “Migrating Reports and Printer Definitions” in Chapter 1of the Reports Migration Manual.

REP–1085 file create error.

You tried to perform an operation that required Oracle Reports to create a fileand an error occurred. You might not have the necessary file privileges tocreate the file.

Obtain the necessary privileges.

REP–1086 file open read–only error.

You tried to perform an operation that required Oracle Reports to open a file towhich you do not have access. You might not have the necessary file privilegesto open the file.

Obtain the necessary privileges for the file or, if possible, access a file to whichyou do have the necessary privileges.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1087 file open read–write error.

You tried to perform an operation that required Oracle Reports to open a file towhich you do not have access. You might not have the necessary file privilegesto open the file.

Obtain the necessary privileges for the file or, if possible, access a file to whichyou do have the necessary privileges.

REP–1088 file write error.

You tried to perform an operation that required Oracle Reports to write to a fileto which you do not have access. You might not have the necessary fileprivileges to write the file.

Obtain the necessary privileges for the file or, if possible, access a file to whichyou do have write privileges.

REP–1089 file read error.

You tried to perform an operation that required Oracle Reports to read a file towhich you do not have access. You might not have the necessary file privilegesto read the file.

Obtain the necessary privileges for the file or, if possible, access a file to whichyou do have read privileges.

REP–1090 file close error.



REP–1091 disk or file system full.

You tried to save an object, but there wasn’t enough space in which to save it.

You need to either delete some unnecessary files or expand your storage space.

REP–1092 file unique key violation.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1093 allocate failed.



REP–1094 reallocate failed.



REP–1095 free failed.



REP–1096 The <module type> is currently locked.

You tried to open a module that is already opened (locked) by another user.

Wait until the other user closes the module before accessing it.

REP–1097 PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does notexist.

The possible causes of this error include:

Case 1: The table does not exist.

Case 2: You do not have the necessary privileges to access the table.


If Case 1: If the table is not already created, create it.

If Case 2: Get access to the table by creating a public synonym for the table inthe PRODUCT_USER_PROFILE table, or by making the table publicvia the PRODUCT_USER_PROFILE table.

REP–1098 Error reading PRODUCT_USER_PROFILE orSYSTEM.PRODUCT_PROFILE data.

The table is not created correctly.

Ensure that the table was created with the appropriate columns. If it was not,then modify it as necessary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1099 Cannot open non–Oracle Reports files.

You tried to open a file that is not an Oracle Reports report.

Ensure that the file you are opening contains an Oracle Reports report.

REP–1100 Your data model is invalid for this type of report.

You tried to create a default layout with a layout style that does not match yourdata model.

You can either change your data model to match the selected layout style orselect a different layout style to match your data model. For more information,see your online help.

REP–1101 Group ’<group name>’ has an invalid repeat direction.

You tried to create a default layout, but the selected layout style requires adifferent repeat direction for one of your groups. Some layout styles placerestrictions on the repeat directions you can choose for your groups.

You can either change the repeat direction to meet the layout style requirementsor you can choose a different layout style.

REP–1102 Unable to fit default layout onto page of width <width>. Second line ofmessage may be one of the following: Unable to fit column ’<columnname>’; Unable to fit group ’<group name>’ and its summaries; Unable tofit group ’<group name>’ (wrapping not supported inside matrix); Unable tofit matrix ’<matrix name>’ and its summaries.

Oracle Reports tried to create the default layout you selected but could not fitthe entire layout on the page because the page is not wide enough.

If possible, increase the Page Width on the Report Properties property sheet orrearrange objects such that the layout will fit on the page. Otherwise, you mayhave to make the report multiple pages wide.

REP–1103 No column is selected in group ’<group name>’.

While trying to create a default layout, you did not select a column for aselected group. Consequently, Oracle Reports cannot build a default layoutbecause one or more of the dimensions of your layout has no values.

In the Default Layout dialog box, select at least one column from each selectedgroup.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1104 Generated layout of <size> cannot fit into area of <size>.

You generated a default layout and it cannot fit within the given amount ofspace. The possible causes of this error include the following:

Case 1: The layout you have generated is too large given the dimensionsspecified in the Report Properties dialog box.

Case 2: The layout is too big given the size of the marked area in the Layouteditor.


If Case 1: Increase your report dimensions such that the layout can fit, or alterthe layout so that it will fit within the current dimensions.

If Case 2: Increase the size of the marked area.

REP–1106 Warning: no field generated for column ’<column name>’.

When you defaulted your layout, a field was not generated for the column inthe message. The most likely cause is that a summary was not placed in thedata model correctly. For example, you may have specified the source of asummary column to be a column in a group above the summary’s group. Thisis not allowed.

Debug your data model and redefault your layout.

REP–1107 Missing across or down group in cross product group ’<group name>’.

You attempted to create a default layout by selecting a Default Layout Style ofMatrix in the Default Layout dialog box, but all of the dimension groups of thecross product group were assigned repeat directions of Down or Across. Eachrepeat direction should be assigned to the dimension groups in the crossproduct.

Re–display the Default Layout dialog box and re–assign the repeat directions ofthe dimension groups, making sure that each direction is assigned among thegroups.

REP–1108 Cannot fit default layout even in region extending to page boundaries.

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.

Go back to the Default Layout dialog box and reduce the values of defaultsettings (e.g., shorten some field widths). Alternatively, you can increase thesize of a report page using the Report Properties property sheet. Then redefaultyour layout. Continue making adjustments as necessary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1200 Flow compilation failed.



REP–1201 Query text missing from query ’<query name>’.

You named a query and tried to accept it, but you either did not enter anySELECT statement for it or you entered something that did not begin with thekeyword SELECT. The Query property sheet only accepts SQL SELECTstatements.

Enter a SQL SELECT statement that begins with the word SELECT (you mayuse upper or lower case). No other SQL statements are accepted in the Queryproperty sheet.

REP–1202 ORACLE logon not specified.

You tried to run a report without having specified an ORACLE logon.

Enter a logon string in the Connect dialog box and accept the dialog box beforere–running the report.

REP–1203 Field ’<field name>’ references invalid column.

The column specified as the field’s Source either is invalid or does not exist.

Select a column from the list of values.

REP–1204 Repeating frame ’<repeating frame>’ references invalid group.

The group name you entered in the Group field of the Repeating Frameproperty sheet either is invalid or does not exist.

Select a group from the list of values.

REP–1205 There is a loop in the positional dependency tree.

You have created explicit anchors such that an object is indirectly anchored toitself. 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.

You must remove at least one of the anchors that caused the loop.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–1206 An object is anchored to more than one other object.

In your layout, you have anchored an object to more than one other object. Anobject may only be anchored to one other object.

Eliminate the anchors to other objects such that the object is anchored to onlyone other object.

REP–1207 The PL/SQL procedure for group filter of ’<group name>’ is missing.

You entered Condition in Type on the Group property sheet, but you did notenter a valid filter.

Enter a valid PL/SQL function or change the filter type.

REP–1208 Repeating frame of matrix ’<matrix name>’ cannot be anchored.

You tried to run a report with an anchor from an intersecting repeating frame ofa matrix object to another object. You cannot do this.

Delete the anchor. You cannot anchor this object to another object.

REP–1209 Matrix object ’<matrix name>’ cannot be anchored.

You tried to run a report with an anchor from a matrix object to another object.You cannot do this.

Delete the anchor. You cannot anchor this object to another object.

REP–1211 Object ’<object name>’ is larger than its enclosing object ’<object name>’.

An object is larger than its enclosing object. The most likely cause is that youhave attempted to enclose a large object within a small, fixed frame.

Identify the object and the enclosing object and adjust their relative sizes andpositions until the proper enclosure is achieved.

REP–1212 Object <object name> is not fully enclosed by its enclosing object ’<objectname>’.


Case 1: An object is not fully enclosed by the page. That is, the object extendsbeyond the page boundary.

Case 2: A repeating frame that forms a matrix is one or more layers above arepeating frame that it contains. In a matrix layout, repeating framesmust be below repeating frames that they contain.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action



If Case 1: Move or resize the object so that it does not extend outside the pageboundary. Alternatively, increase the page size in the ReportProperties property sheet.

If Case 2: Using Arrange—>Send to Back, Arrange—>Bring to Front,Arrange—>Move Backward, and Arrange—>Move Forward,arrange your repeating frames such that, in terms of layers, thefollowing is true: repeating frames are below repeating frames thatthey contain and down repeating frames are below across repeatingframes.

REP–1213 Field ’<field name>’ references column ’<column name>’ at a frequencybelow its group.

The source column for the field is in a group below that of the repeating framewhich encloses it.

Move the field into a repeating frame whose source group is at or above thegroup that contains the field’s source column. Otherwise, move the field’ssource column into the enclosing repeating frame’s group, if possible.

REP–1214 Repeating frame ’<repeating frame name>’ is enclosed by a child repeatingframe.

The enclosed repeating frame’s source group is above the enclosing repeatingframe’s source group.

In the editor, you can make the enclosed repeating frame the enclosingrepeating frame. Alternatively, you could, if possible, change your grouphierarchy such that the enclosed object’s group is below the enclosing object’sgroup.

REP–1216 ’<object name>’ has an illegal print condition.

You set an invalid Print Condition for the specified object. For example, youmight have tried to set the Print Condition of a margin object.

Change the Print Condition of the object to another, valid setting.

REP–1218 ’<object name>’ cannot page break before AND keep with parent.

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 twosettings are in conflict.

Uncheck Page Break Before or Keep with Anchoring Object.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1219 ’<object name>’ has no size –– length or width is zero.

In creating your layout, you created a layout object of zero width or height.

Enlarge the object so that it has a non–zero height and width.

REP–1220 ’<object name>’ has minimum widow lines greater than max lines per page.

You have set Maximum Records per Page to a smaller value than MinimumWidow Records. This causes a conflict between the two settings and, in effect,indicates that no instances should be printed.

Decrease Minimum Widow Records or increase Maximum Records per Page.

REP–1222 Invalid body size.

You specified a body page width or height that is negative or out of range. Youmost likely received this error after setting the page size to an invalid valueusing the PAGESIZE executable argument.

Enter a valid value using the PAGESIZE executable argument, or adjust thebody panel size by resizing the margins in the Layout editor.

REP–1223 Invalid page size.

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 valueusing the PAGESIZE executable argument.

Enter a valid value using the PAGESIZE executable argument, or change thephysical page size setting in the Report Properties property sheet.

REP–1225 Invalid logical page size.

You specified a logical page height that is negative.

Redefine your logical panel height to ensure that it is not defined using anegative number.

REP–1226 Body location is beyond print area.

The body panel is not enclosed within the physical page.

Adjust the body panel size by resizing the margins in the Layout editor.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1229 Between record value for repeating frame ’<repeating frame name>’ isnegative.

The value for Vertical Spacing and/or Horizontal Spacing specified for arepeating frame is negative.

Re–specify the appropriate Spacing setting for the repeating frame identified inthe error message.

REP–1230 Field ’<field name>’ has an invalid page reset group.

In the Reset At field of the Page Numbering dialog box, you specified arepeating frame that does not enclose the layout field you want to display thepage number. You may have specified an invalid repeating frame, or deletedthe repeating frame after specifying it.

Specify &Report or the name of a valid repeating frame as the Reset At value forthe page number field.

REP–1231 ’<object name>’ has an invalid text wrap style.



REP–1232 Matrix ’<matrix name>’ has an invalid source frame.

You specified an invalid object as the source frame of the matrix object, or therepeating frames you specified have invalid Print Directions.

Change the Print Direction of horizontal source repeating frame to Down, andthe Print Direction of the vertical source repeating frame to Across.

REP–1233 The frames of matrix ’<matrix name>’ do not fully intersect.

The repeating frames that form the matrix do not completely intersect. Forexample, if you have two down repeating frames, two across repeating frames,and one of the across repeating frames only intersects completely with one ofthe down repeating frames, you would get this error.

Re–default the matrix layout, if possible, or move the repeating frames thatmake up the matrix such that they fully intersect one another.

REP–1234 Matrix ’<matrix name>’ position is not at the intersection of its frames.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1235 Error generating index for Cross Product.



REP–1236 Invalid query <query name>.



REP–1237 Invalid data link.



REP–1238 Invalid group <group name>.



REP–1239 Invalid column <column name>.



REP–1240 Invalid anchor.



REP–1241 Circular column dependency originating with column <column name>.

You have created a column that directly or indirectly references itself. Forexample, Column A might reference Column B which in turn referencesColumn A.

Update or delete the column(s) to eliminate the circular dependency.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1242 Matrices must have all down frames below all across frames.

In a matrix layout, down repeating frames must be below across repeatingframes.

Using the Arrange—>Send to Back, Arrange—>Bring to Front,Arrange—>Move Backward, and Arrange—>Move Forward, arrange yourrepeating frames such that, in terms of layers, the following is true: repeatingframes are below repeating frames that they contain, and down repeatingframes are below across repeating frames.

REP–1243 Unimplemented type of summary specified in column ’<column name>’.

You specified a summary function that is not available.

Specify a valid summary function

REP–1245 Wrong number of source columns for summary function of column <columnname>.



REP–1246 Oracle Graphics document not found.

Oracle Reports cannot find an Oracle Graphics module as listed in the OracleGraphics Display property sheet.

Correct the file name and path in the Oracle Graphics Display property sheet.

REP–1247 Report contains uncompiled PL/SQL.

You attempted to run your report before all referenced PL/SQL constructs hadbeen compiled.

Compile the PL/SQL, then run your report.

REP–1248 All source columns of placeholder <column name> must be in the samegroup.

You attempted to set the value of a placeholder column from column(s)belonging to different groups.

Change the placeholder column’s group to match the group of the column(s)changing the placeholder column’s value.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1249 Column <column name> has no PL/SQL formula.

You created a column of Type Formula with nothing in the Formula field.

Create a formula for the column or change the column’s Type.

REP–1250 Circular query dependency.

Your report contains at least two queries, with each requiring the other to beexecuted first.

Edit one or more of your queries to remove the circular dependency.

REP–1251 Circular query dependency originating with query ’<query name>’.

Your report contains at least two queries, with each requiring the other to beexecuted first. The query listed in the message is one of the conflicting queries.

Edit the query listed or another conflicting query to remove the circulardependency.

REP–1252 Matrix should be surrounded by a repeating frame on group ’<groupname>’.

The data model for your report contains a matrix with a parent group, but inthe layout the repeating frame for the parent group either does not exist or doesnot surround the matrix.

Modify the layout of your report so that the parent group has a repeating framewhich surrounds the matrix.

REP–1253 Matrix objects are on different regions of the layout.

The repeating frames of a matrix are on different regions of the layout (body,margin, header, or trailer).

Move all repeating frames of the matrix to the same report region.

REP–1254 Anchored objects are on different regions of the layout.

The anchoring and anchored objects of an anchor are on different regions of thelayout (body, margin, header, or trailer).

Move the above–mentioned objects to the same report region.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1255 Cannot anchor to a hidden object.

The anchored object of an anchor is a hidden object.

Either make the anchored object not hidden, or delete the anchor.

REP–1256 External boilerplate text is missing its link file.

You did not specify a filename in the Link File field in an external boilerplateobject’s property sheet.

Specify a directory path and filename in the Link File field in the ExternalBoilerplate property sheet.

REP–1257 Cannot pass data for child query from caller.

You have invoked Oracle Reports from another product, and Oracle Reportshas been instructed to fetch data for a child query from the caller. Data passedto Oracle Reports can only be for a master query.

Modify the caller’s instructions so that Oracle Reports does not request data fora child query.

REP–1258 Group ’<group name>’ has no columns.

You have created a group that has no columns.

Delete the group or assign one or more columns to the group.

REP–1259 Group ’<group name>’ has no break columns.

You have created a parent group that has no break columns.

Mark the Break Order check box(es) of the break column(s) of the group.

REP–1260 Groups ’<group name>’ and ’<group name>’ are from the same query andcannot be linked.

You have a data link between two groups from the same query. This is notallowed.

Remove the data link or re–link to another group.

REP–1261 Cannot resolve parent of group ’<group name>’.

One group has two queries as its parent (it can only have one).

Remove data links from the same group to different queries.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1262 Circular data link dependency starting from group ’<group name>’.

You have created a cycle with data links (i.e., you have specified that a parent isthe child of itself, either directly or indirectly).

Remove at least one of the links in the cycle.

REP–1263 Cross product group ’<group name>’ has no or only one dimension group.

You have a cross product group that has no or only one group inside. Crossproduct groups must have at least two dimension groups. Multi–query crossproduct groups must have at least two queries within the cross product group.

Remove the cross product group or add dimension groups, or dimensionqueries (if multi–query).

REP–1264 Data link of group ’<group name>’ crosses cross product boundary.

In your multiple–query matrix report, you have a query where some of itsgroups are inside the cross product and some outside.

Move all groups of the query to either outside or inside of the cross productgroup.

REP–1265 Cross product group ’<group name>’ has no child groups.

You have a cross product group with no child group, which is required. Thechild group acts as the cell of the matrix.

Create a child group for the cross product group.

REP–1266 Column ’<column name>’: Page Level columns not allowed in CrossProduct.

You have created a column in a cross product group that is or relies on acolumn that is a page–level summary (i.e., a summary with Reset At of Page).

You cannot have a column in a cross product group that is or relies on apage–level summary. You must remove the column from the cross productgroup, or change the Reset At value of the column or the page–level summaryupon which it relies.

REP–1267 OG display ’<display name>’ references invalid column as bind parameter.

The Oracle Graphics property sheet for the specified display references acolumn that does not exist. This is an abnormal condition.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1268 OG display ’<display name>’ references bind column ’<column name>’ atwrong frequency.

The column specified in the Oracle Graphics property sheet for the specifieddisplay is in a group below that of the repeating frame that encloses the OracleGraphics object.

Move the Oracle Graphics object into a repeating frame whose source group isat or above the group that contains the specified column. Otherwise, move thespecified column into the enclosing repeating frame’s group, if possible.

REP–1269 OG display ’<display name>’ references invalid source group.

The group specified in the Oracle Graphics property sheet for the specifieddisplay is nonexistent. This is an abnormal condition.


REP–1270 OG display ’<display name>’ references source group at the wrongfrequency.

The source group in the Oracle Graphics property sheet for the specified objectis above that of the source group of the repeating frame.

Move the Oracle Graphics object into a repeating frame with a source groupthat is at or above its source group.

REP–1271 OG column name ’<column name>’ has been specified multiple times inOG display ’<display name>’.

The specified Oracle Graphics display column or parameter has beenreferenced more than once in the Oracle Graphics property sheet.

Check the Oracle Graphics columns and parameters you specify in the propertysheet and delete any duplicates.

REP–1272 Column ’<column name>’ may not be used as a Break Column.

You specified a Break Order on a summary, function, or placeholder. Thesetypes of columns cannot be used as break columns.

Review the rules for which columns can be break columns. For moreinformation, see “Break Order” in Chapter 6 of the Reports Reference Manual.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1273 Source groups of matrix ’<matrix name>’ not from the same cross product.

The source groups of the repeating frames that form the dimensions of thematrix are not contained by the same cross product group. The dimensions of amatrix must be contained within the same cross product group.

Change the source groups of the repeating frames or choose different repeatingframes to form the dimensions of the matrix.

REP–1274 Invalid repeat direction combination in matrix ’<matrix name>’.

Matrix dimension repeating frames whose source groups are in the same”family” hierarchy (i.e., are descendants or ancestors of each other) within across product group must have the same Print Direction. Parent–childrelationships within a cross product group are used to create nesting in thematrix. As a result, the repeating frames associated with such groups mustprint in the same direction on the page.

Change the Print Direction of the repeating frames as necessary, choosedifferent source groups for the repeating frames, or choose different repeatingframes to form the dimensions of the matrix.

REP–1275 Page–level column ’<column name>’ may not be referenced from formattrigger ’<object name>’.

PL/SQL entered in Format Trigger cannot reference columns with a Reset At orCompute At of Page.

Remove the reference to the page–level column or change the column’s ResetAt or Compute At to something other than Page.

REP–1276 Placeholder ’<column name>’ references one or more non–formula columns.

A placeholder column contains SRW.REFERENCE, but the column referencedis not a formula column. For placeholder columns, SRW.REFERENCE mustrefer to a formula column.

Change the column referenced via SRW.REFERENCE.

REP–1277 Invalid select element.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1278 Invalid PL/SQL procedure in ’<object name>’.



REP–1279 Invalid frame or repeating frame ’<frame name>’.



REP–1280 Invalid field ’<field name>’.



REP–1281 Invalid boilerplate ’<boilerplate name>’.



REP–1282 Invalid matrix ’<matrix name>’.



REP–1283 Invalid Oracle Graphics display ’<display name>’.



REP–1284 Query ’<query name>’ has no groups.

Your data model contains a query that has no groups. Each query in your datamodel needs at least one group associated with it.

Create a new group for the query.

REP–1285 Query ’<query name>’ has no select elements.

Your data model contains a query that does not select anything. Each query inyour data model must select at least one element.

Enter a SELECT statement in the query, selecting at least one element.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1286 Group ’<group name>’ is a cross product as well as a dimension.

You specified a group to act as both a cross product group and as a dimensiongroup for another cross product group. This is not allowed.

Make the group either a cross product group or a dimension group, but notboth.

REP–1287 Cross product group ’<group name>’ should not have a group filter.

You specified a group filter on a cross product group. This is not allowed.

Remove the group filter from the cross product group. Create the group filterfor another group, if necessary.

REP–1288 The numeric argument for group filter of ’<filter type>’ missing.

You specified First or Last for a group’s filter, but you did not specify a numberdictating how many records the group should filter.

Specify a number for the group filter.

REP–1289 Unimplemented type of group filter specified in group ’<group name>’.

You specified a group filter that is not available or is invalid.

Specify a valid group filter for the group.

REP–1290 Source datatype incompatible with summary function in column ’<columnname>’.

Your summary column was assigned a Source whose datatype is incompatiblewith the specified Function. For example, you may be trying to sum acharacter column.

Make sure that the datatype of your source column is compatible with theFunction you specified in the Summary Column property sheet.

REP–1291 Column ’<column name>’ has invalid reset group.

You specified an invalid Reset At value for a summary column. Reset At canbe set to the same group as the summary column, any group above thesummary column’s, Page, or Report.

Specify a valid Reset At value for the summary column in its property sheet.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1292 Column ’<column name>’ has invalid compute group.

You specified an invalid Compute At value for a summary column. ComputeAt can be set to the same group as the summary column, any group above thesummary column’s, Page, or Report.

Specify a valid Compute At value for the summary column in its propertysheet.

REP–1293 Column ’<column name>’ has invalid product order.

A column in a cross product group was assigned an invalid value for ProductOrder, or no value at all.

Specify a valid value for Product Order (consisting of only dimension groupswithin the cross product) in the column’s property sheet.

REP–1294 Width of column ’<column name>’ is too large.

The column’s width exceeds the maximum allowed for your operating system.

Reduce the width of the column in the Column property sheet.

REP–1295 Data format of column ’<column name>’ is unsupported.

You activated Read from File for a column, but specified an invalid orunavailable data format in the Format field in the Column property sheet.

Specify a valid data format in the Format field. The list of values displays allvalid data formats. Note that for LONG, RAW, and LONG RAW databasecolumns, only Text and Oracle Format (Image) are valid values for Format.

REP–1296 Data link child cannot be in cross product group ’<column name>’.

You tried to link a column to a column in a cross product group, or to the crossproduct group itself. These operations are not allowed.

Create data links between columns and groups other than cross product groupsand their associated columns.

REP–1297 Data link child column ’<column name>’ must be a database column.

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.

You can create data links using only database columns and groups.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1298 Columns ’<column name>’ and ’<column name>’ have incompatible typesto be linked.

The parent and child columns in your data link have incompatible datatypesthat cannot be linked. For example, you might have tried to link a Numbercolumn to a Character column.

Make sure the parent and child columns you specify in data links havecompatible datatypes.

REP–1299 Groups ’<group name>’ and ’<group name>’ in different cross productscannot be linked.

You tried to create a data link between dimension groups of two different crossproduct groups, or between columns of the dimension groups. Theseoperations are not allowed.

You cannot create data links between two different cross product groups ortheir columns.

REP–1300 Text boilerplate ’<boilerplate name>’ has no contents.

You created a text boilerplate object that contains no text.

Enter some text in the boilerplate object, or delete it.

REP–1301 Data link creates sibling of group ’<group name>’ within cross product.

You created a data link that created a sibling of a dimension group within across product group. No siblings of dimension groups are allowed within thecross product.

Dimension groups can consist only of chains of groups. No siblings areallowed.

REP–1302 Cross product has two or more child groups.

A cross product group has more than one child group. Only one child isallowed per cross product group.

Remove all but one of the child groups to the cross product group.

REP–1303 Query must be completely in or out of cross product group ’<group name>’.

You created a query whose groups are not all inside the cross product, abovethe cross product, or below the cross product, respectively.

Make sure that each query’s groups are all inside of a cross product, above across product, or below a cross product.

Cause

Action

Cause

Action

Cause

Action

Cause


REP–1304 Cross product group ’<group name>’ contains another cross product aschild.

You created a cross product group that is a child of another cross productgroup. This is not allowed.

Ensure that the child group of the cross product group is not a cross productgroup.

REP–1305 Warning: Frame ’<frame name>’ intersects but does not enclose object’<object name>’.

Your report layout contains a frame that does not completely enclose thenamed object. Thus, the object is not considered to be inside the frame.

If you want the frame to enclose the object, resize or move the frame.

REP–1306 Summary column ’<column name>’ has invalid source.

You specified an invalid source for the summary column. A summarycolumn’s source must be from the same group as the summary column, or froma group below the summary column.

Change the source of the summary column to be from the same group as thesummary column or from a group below the summary column.

REP–1307 Summary column ’<column name>’ has invalid product order.


Case 1: You have a summary which is not a running summary (i.e., its ResetAt is not Report), but its Product Order is not a subset of the sourcecolumn’s product order. The source column of the summary must beat least as frequent as the summary, which means that the summary’sProduct Order should be some subset of the source column’s ProductOrder.

Case 2: You have a running summary (i.e., its Reset At is Report) with aProduct Order that is not a prefix of the source column’s ProductOrder. For example, if the source column’s Product Order wereA,B,C, then the summary column’s Product Order would have to beeither A (by itself) or A,B. The summary’s Product Order could notbe B,A.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action



If Case 1: Change the Product Order of the summary such that it is a subset ofits source column’s Product Order.

If Case 2: Change the Product Order of the summary such that it is a prefix ofthe Source column’s Product Order.

REP–1308 Placeholder column ’<column name>’ not supported in cross product.

You tried to create a placeholder column inside of a cross product group. Crossproduct groups cannot contain placeholder columns.

Delete the placeholder or move it outside the cross product group.

REP–1309 Report–level summary ’<column name>’ cannot be a percent of total.

You created a summary at the report–level (i.e., a summary outside of all thegroups in the data model) with a Function of % of Total. This Function makesno sense for a report–level summary because it will always be 100%.

Delete the summary or move it into a group where it will make sense.

REP–1310 Boilerplate ’<object name>’ references ’&<reference name>’ which is not afield.

A boilerplate object has a reference to a field that does not exist. It could bethat the field being referenced was deleted or renamed and so this reference inthe boilerplate object is now invalid.

Depending on circumstances, you may want to remove the reference, replace itwith a reference to another field, or create the field that it references.

REP–1311 Object ’<object name>’ with page–dependent references changed to fixedsizing.

A field or boilerplate object has a reference to a page calculation or a totalnumber of pages variable. (This is known as a forward reference.) Such layoutobjects must be fixed in size both horizontally and vertically.

The layout object’s Horizontal and Vertical Sizing have been set to Fixed byOracle Reports. Check the output to ensure that the values are not beingtruncated. If they are, you should enlarge the layout object so that it is largeenough to contain the values.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1312 Page Level column ’<column name>’ may not be referenced from OGdisplay ’<display name>’.

One of the Oracle Reports columns that you tried to pass to an Oracle Graphicsdisplay is or depends upon a page–level summary (i.e., a summary with aReset At or Compute At of Page). A column being passed to an OracleGraphics display cannot be or depend upon a page–level summary.

Do not pass the column to the Oracle Graphics display.

REP–1313 Page Level column ’<column name>’ may not be referenced from groupfilter ’<group name>’.

One of the Oracle Reports columns that you tried to reference in a group filteris or depends upon a page–level summary (i.e., a summary with a Reset At orCompute At of Page). A column referenced by a group filter cannot be ordepend upon a page–level summary.

Do not reference the column in the group filter.

REP–1314 Format trigger ’<object name>’ references column ’<column name>’ atwrong frequency.

One of your format triggers references a column that is located at the wrongfrequency.

Remove the reference to the column from the format trigger.

REP–1315 Group filter ’<group name>’ references column ’<column name>’ at wrongfrequency.

One of your group filters attempted to reference a column that is inaccessible.

Remove the reference to the column from the group filter.

REP–1316 <Object name> references column ’<column name>’ at wrong frequency.

A procedure or function attempted to reference a column that is inaccessible.

Remove the reference to the column from the PL/SQL subprogram.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1317 Boilerplate ’<boilerplate name>’ references field with source ’<columnname>’ at wrong frequency.

The boilerplate object references the field using &fieldname, but the two objectsare not located at the same frequency. For example, the boilerplate object andthe field it references are located within different repeating frames.

Place the boilerplate object and field at the same frequency, or remove thereference.

REP–1318 Error while setting transaction read–only.

Having specified READONLY=YES, this error occurred at the start of reportexecution, while ending the current transaction (with a COMMIT) and startingthe read–only transaction, or at the end of report execution, while ending theread–only transaction (with a COMMIT).

Make sure you are connected to a database, and make sure that no cursors orlocks were left pending by the previous transaction.

REP–1319 Warning: Implicit anchoring algorithm cannot uniquely identify theanchoring object of ’<object name 1>’. Arbitrarily choosing ’<object name2>’.

The specified object (object name 1) is in the ”push path” of two objects and itis equidistant from both objects. As a result, Oracle Reports cannot use itsnormal criteria (shortest distance) to determine the implicit anchor. In theabsence of its normal criteria, Oracle Reports randomly creates an implicitanchor to the specified object (object name 2). Note that the implicit anchormay vary between runs of the report. For more information, see “ImplicitAnchoring” in Chapter 2 of the Reports Reference Manual.

To avoid the random creation of an implicit anchor, explicitly anchor thespecified object (object name 1) to another object.

REP–1320 Program unit ’<progunit name>’ references column with invalid ID: <ID>.

You ran a report with invalid PL/SQL (e.g., PL/SQL that didn’t compile). ThePL/SQL source included a column reference that cannot be resolved.

Check the column references in your PL/SQL source, recompile all of thePL/SQL source in the report, and re–run the report.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1322 Page break after on ’<object name>’ has no effect.

You activated Page Break After on an object that has no other objects anchoredto it (implicitly or explicitly). In this case, Page Break After has no effect and isinvalid. Notice that this is a warning, not an error message.

Deactivate Page Break After for the object.

REP–1323 Cannot have output columns in format trigger ’<object name>’.

In the format trigger for the specified object, you attempted to set the value ofan Oracle Reports column parameter. For example, you can use the value of acolumn called COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannotdirectly set its value in an assignment statement (e.g., COUNT1 = 10).

Remove the assignment statement from the format trigger.

REP–1324 Cannot have output columns in group filter ’<group name>’.

In the filter for the specified group, you attempted to set the value of an OracleReports column or parameter. For example, you can use the value of a columncalled COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannot directlyset its value in an assignment statement (e.g., COUNT1 = 10).

Remove the assignment statement from the group filter.

REP–1325 Cannot have output columns in Between Page Trigger.

In the Between Page trigger, you attempted to set the value of an OracleReports column or parameter. For example, you can use the value of a columncalled COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannot directlyset its value in an assignment statement (e.g., COUNT1 = 10).

Remove the assignment statement from the group filter.

REP–1326 <Trigger name> writes to column ’<column name>’ at wrong frequency.

In a report trigger, you attempted to set the value of an Oracle Reports columnat the wrong frequency in the report. You can reference and set onlyreport–level columns or parameters, and you cannot reference or set anypage–dependent columns (i.e., Reset At of Page) or columns that rely onpage–dependent columns.

Make sure the columns and parameters whose values you reference or set arereport–level columns and parameters.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1327 Column ’<column 1 name>’ writes to column ’<column 2 name>’ at wrongfrequency.

In a formula column, you attempted to set the value of an Oracle Reportscolumn at the wrong frequency in the report. You can reference and set onlycolumns 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 otherreport–level columns.

Make sure the columns whose values you reference or set are in the same groupor in a higher group in the group hierarchy.

REP–1328 Cannot run report containing ROWLABEL column ’<column name>’ in anon–trusted OS.

You are attempting to run a report that requires a secure database whileconnected to a non–secure database.

Run the report while connected to a secure database.

REP–1329 Column ’<column name>’ cannot be linked to column ’<column name>’because the child column is not a database column.

You created a data link in which the child column is a summary, formula, orplaceholder column. Only database columns can be linked.

Create a data link using database columns.

REP–1330 Lexical parameter ’<parameter name>’ in query ’<query name>’ must notchange column dependencies.

You created a lexical parameter that changes the number, type, or names ofcolumns, or introduces new dependencies on computed columns or new bindreferences, when the report is run.

Change the lexical parameter so that it does not change columns or introducenew dependencies or bind references.

REP–1331 Column ’<column name>’ cannot be linked to column ’<column name>’because the child column is determined by a lexical parameter.

You created a dat link in which child column’s value is determined by a lexicalparameter. This is not allowed.

Replace the child column of the data link with another column.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


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.

You created a group filter that references a database column not in the group’squery or in a query above it, or references a computed column that depends onan unrelated column.

Remove the offending reference from the group filter.

REP–1333 Unsupported layout; a matrix may not be inside another matrix.

You created a matrix layout nested within another matrix layout.

Matrix layouts cannot be nested within other matrix layouts. Re–design yourlayout to avoid this.

REP–1335 Warning: variable rotated text ’<boilerplate name>’ treated as fixed/contractwidth.

Your report contains a boilerplate text object which was rotated to an angle thatis not a multiple of 90 degrees, although both Horizontal and Vertical Sizingvalues were set to Variable or Expand. In this case, the Horizontal Sizing istreated as Fixed (if you specified Expand) or Contract (if you specified Variable),and this warning is displayed.

You may want to change the Horizontal and Vertical Sizing values for thisboilerplate object.

REP–1336 The source of field ’<field name>’ is Page Level calculation ’<columnname>’. The object must be enclosed by a repeating frame with group’<group name>’ as source.

The specified field references a page summary owned by the named group, butthere is no repeating frame for that group that surrounds the field.

Create a repeating frame whose Source is the named group to surround thefield. If such a repeating frame already exists, extend it to enclose the field.

REP–1337 Boilerplate ’<boilerplate name>’ references field ’<field name>’, whosesource is Page Level calculation ’<column name>’. The object must beenclosed by a repeating frame with group ’<group name>’ as source.

The specified boilerplate object references the specified field, whose Source is apage–level computation. However, there is no repeating frame (whose Sourceis the named group) surrounding the field.

Create a repeating frame whose Source is the named group to surround thefield. If such a repeating frame already exists, extend it to enclose the field.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1338 Column mode not allowed on repeating frame ’<repeating frame name>’.

You activated Column Mode for a repeating frame whose setting do not satisfyeither of the following conditions:

• Print Direction of Down and a Vertical Sizing of Fixed.

• Print Direction of Across and a Horizontal Sizing of Fixed.

Change the Print Direction or Vertical/Horizontal Sizing of the repeatingframe, or deactivate Column Mode.

REP–1339 OG display <display name> missing data columns specification.

In the Oracle Graphics Display property sheet, you specified a value in DisplayQuery, but no columns to be passed from the report to the display.

If you do not want to pass data from the report to the display, then specifynothing for Display Query and Source. If you do want to pass data, thenspecify the columns to be passed in addition to Display Query and Source.

REP–1340 Cannot match passed–in columns with report definition <report name>.

This error occurs when another tool (e.g., Oracle Forms) passes a query toOracle Reports and there is a mismatch between the columns passed and thecolumns expected by Oracle Reports. Possible causes of this error include:

Case 1: Oracle Reports is expecting more or fewer columns than the numberthat was actually passed by the calling application.

Case 2: The parameter list of the calling application describes a columndifferently than what Oracle Reports expects. For example, if thereport’s query selects a character column and the calling applicationassigns that column a date datatype, this error will be raised.


If Case 1: Ensure that the calling application is passing the same number ofcolumns that Oracle Reports is expecting.

If Case 2: Ensure that the datatypes and names of the columns being passed bythe calling application match the dataypes and names in the report.

REP–1341 Warning: Data truncation possible in column <column name>.

The database column’s width in the report is defined to be less than its width inthe database. This can occur when the columns in the database are updatedsubsequent to the creation of the report definition.

Force the query to be reparsed. One method is to type a space at the end of aline in the SELECT Statement field and then accept the property sheet.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1342 Type of data link to query <query name> illegal for non–ORACLE server.

If you create a data link with the START WITH clause and run it whileconnected to a non–ORACLE database, you will get this error. START WITH isonly supported by ORACLE.

Remove the data link that uses START WITH or connect to ORACLE.

REP–1343 Invalid button <button name>.



REP–1344 Button <button name> has no action source file.

You have specified an action of Multimedia File for the named button, buthave either not specified a source file, or specified a source file that does notexist.

Open the property sheet for the specified button and verify that you havechosen a valid file as source for the button action. For more information aboutuser–created buttons, see “Button Properties” in Chapter 8 of the ReportsReference Manual.

REP–1345 Button <button name> has invalid source column.

You have specified an action of Multimedia Column for the named button, buthave either not specified a source column, or specified an invalid sourcecolumn.

Open the property sheet for the specified button and verify that you havechosen a valid column as source for the button action. For more informationabout user–created buttons, see “Button Properties” in Chapter 8 of the ReportsReference Manual.

REP–1346 Button <button name> references source column <column name> at wrongfrequency.

The column specified in the property sheet for the named button is in a groupbelow that of the repeating frame that encloses the button.

Move the button into a repeating frame whose source group is at or above thegroup that contains the specified column. Otherwise, move the specifiedcolumn into the enclosing repeating frame’s group, if possible.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1347 Button <button name> has invalid icon file.

You have specified either an invalid file or a nonexistent file as the icon file forthe button face.

Ensure that your icon file exists and is of the proper format and uncorrupted.

REP–1348 Source column of field <field name> is in sound or video format.

You have specified a column containing sound or video as the source for afield, but fields cannot display sound and video.

Specify another column (not sound or video) as source of the field.

REP–1349 PL/SQL action missing from button <button name>.

The PL/SQL trigger that serves as the specified button’s action references apiece of PL/SQL that does not exist.

Debug your trigger and ensure that it references a valid program unit.

REP–1350 Cannot have output columns in action trigger <program unit name>.

The PL/SQL trigger that serves as a button action contains a bind variable thatreturns a value. A PL/SQL action trigger cannot return a value.

Remove the bind variable from your PL/SQL.

REP–1351 Warning: icon <icon name> on button <button name> not found.

The icon you specified as the button face for the named button cannot befound. The report will run, but the button will appear blank.

Open the property sheet for the named button and verify that the icon youspecified exists and is in the correct format, and that you have included thecorrect path information.

REP–1400 Couldn’t initialize coxr



REP–1402 ’<Program unit name>’: Unhandled PL/SQL exception.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1403 ’<Program unit name>’: Illegal to suspend PL/SQL procedure.

A PL/SQL construct was suspended during execution or generation.

Debug and re–compile your PL/SQL constructs.

REP–1404 Compile failed for some reason.

In generating your report, PL/SQL compilation failed.

Debug your PL/SQL constructs.

REP–1405 Code is not executable.

A PL/SQL construct did not compile properly or for some other reason couldnot be executed.

Debug your PL/SQL constructs.

REP–1406 Cannot run parameterized code directly.



REP–1408 Cannot initialize PL/SQL.



REP–1412 PL/SQL function ’<program unit name>’ returned invalid value or no value.

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).

Verify that the function includes a return statement for every code path.

REP–1414 ’<Program unit name>’: Couldn’t find lib unit to run.

This is most likely an abnormal condition.

Check your PL/SQL code and recompile it. If this error recurs, see “AbnormalConditions” on page 1 – 3.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1415 ’<Program unit name>’: Unknown user exit ’<user exit name>’.

A user exit was called, but it could not be found.

Ensure that you are using the correct name for the user exit and that it has beencompiled and linked.

REP–1416 ’<Program unit name>’: User exit ’<user exit name>’. <submessage>.

An error occurred in a user exit. Possible errors: a reference to an unknowncolumn, a truncated column value, unretrievable PL/SQL source, or the userexit could not be found.

Based on the submessage, debug your user exit. Ensure that you arereferencing valid columns and the PL/SQL code and user exit are accessible.

REP–1417 ’<Program unit name>’: Invalid integer argument passed to <procedurename>.

The packaged procedure that you referenced expected an integer for anargument, but you did not specify one.

Verify that the PL/SQL that references the packaged procedure correctly passesit an integer. For more information about PL/SQL packaged procedures, see“The Oracle Reports Package: SRW” in Chapter 13 of the Reports ReferenceManual.

REP–1418 ’<Program unit name>’: Passed null arguments to <procedure name>.

The exception SRW.NULL_ARGUMENTS was raised, either by a user–definedPL/SQL subprogram, or because a packaged subprogram was passed one ormore null arguments.

Check any PL/SQL code that might raise this exception. Also, check theargument list that is passed to the specified packaged subprogram.

REP–1419 ’<Program unit name>’: PL/SQL program aborted.

A PL/SQL construct had a fatal error and was aborted.

Check your PL/SQL constructs for errors.

REP–1420 ’<Program unit name>’: PL/SQL program raised a program error.

The exception SRW.PROGRAM_ERROR was raised, either by a user–definedPL/SQL subprogram, or because of an abnormal condition.

Check any PL/SQL code that might raise this exception. If no PL/SQL raisedthe exception, see “Abnormal Conditions” on page 1 – 3.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1421 ’<Program unit name>’: Trying to manipulate column of wrong type in<procedure name>.

The datatype of the column whose name you passed to a packaged procedureis not the correct datatype for the packaged procedure (e.g., the packagedprocedure was expecting a column of Character datatype and you passed it acolumn of another datatype).

Debug the PL/SQL that references packaged procedures and ensure that youare passing the packaged procedure the name of a column of the correctdatatype. Also check the syntax of the packaged procedure to ensure that youare referencing it properly. For more information about PL/SQL packagedprocedures, see “The Oracle Reports Package: SRW” in Chapter 13 of theReports Reference Manual.

REP–1422 Procedure by this name already exists.

You tried to create a new PL/SQL procedure with the same name as an existingPL/SQL procedure.

Change the name of the new procedure or change the name of the existingprocedure.

REP–1423 ’<Program unit name>’: Cannot set maximum rows of the query after itstarted executing.

You used the SRW.SET_MAX_ROW packaged procedure to reduce the numberof rows fetched by a query. However, you called SRW.SET_MAX_ROW afterthe query was already fetched.

Move your SRW.SET_MAX_ROW to the Before Report trigger.

REP–1424 ’<Program unit name>’: Internal error while executing <procedure name>.



REP–1425 ’<Program unit name>’: Error running DO_SQL package – ’<embeddedmessage>’.

An error occurred while Oracle Reports was executing an SRW.DO_SQL call.Embedded in this message, you will find an Oracle Reports message and,possibly, an ORACLE error message describing the exact error that occurred.

Errors in SRW.DO_SQL are most often the result of a SQL error. Refer to yourORACLE7 Server SQL Language Reference Manual and verify that the SQLstatement in your SRW.DO_SQL call is correct.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1426 ’<Program unit name>’: Running <procedure name> from incorrect context.

You attempted to call the named packaged procedure from an invalid area. Forexample, SRW.SET_ATTR cannot be called from a formula.

Modify your PL/SQL code so that it does not call the packaged procedure fromthat context.

REP–1427 ’<Program unit name>’: Nonexistent query name referenced inSRW.SET_MAXROW.

You included a call to the SRW.SET_MAXROW procedure in a Before Reporttrigger, but the query referenced in the procedure call does not exist.

Change the call to the SRW.SET_MAXROW procedure so that it references anexisting query in the report.

REP–1428 ’<Program unit name>’: Error while running <procedure name>.

The exception SRW.RUN_REPORT_FAILURE was raised, either by auser–defined PL/SQL subprogram, or because of an abnormal condition afterSRW.RUN_REPORT was called.

Check any PL/SQL code that might raise this exception. If no PL/SQL raisedthe 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/SQLcode is called by a command line string containing BATCH=YES. For moreinformation, see “SRW.RUN_REPORT” in Chapter 13 of the Reports ReferenceManual.

REP–1429 ’<Program unit name>’: SRW.RUN_REPORT cannot be invoked withbatch=no.

You included a call to the SRW.RUN_REPORT procedure with a command linestring containing BATCH=NO, which is not allowed.

Remove BATCH=NO from the SRW.RUN_REPORT command string.

REP–1430 Cannot create REP File for report ’<report name>’. Compilation errors found.

There is an error in the PL/SQL in the report you are attempting to convert.

Open the report and debug your PL/SQL.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1433 ’<Program unit name>’: Error running user exit ’<user exit name>’.

While running the user exit named in the message, an error occurred.

Debug your user exit and ensure that it is linked.

REP–1434 ’<Program unit name>’: SRW.RUN_REPORT cannot be invoked with auserid.

You included a call to the SRW.RUN_REPORT procedure with a command linestring containing a userid/password, which is not allowed.

Remove the userid/password from the SRW.RUN_REPORT command string.

REP–1435 ’<Program unit name>’: Value of column ’<column name>’ was truncated.

A column (e.g., a placeholder) was assigned a value larger than its width couldcontain, raising the SRW.TRUNCATED_VALUE exception. The exception wasnot handled, raising this error.

Make the column wide enough to contain the assigned value, or handle theexception in your PL/SQL source.

REP–1436 ’<Program unit name>’: The PL/SQL references an object which is not in thescope.

In a parameter’s Validation Trigger field, you entered PL/SQL source thatreferenced a report column. This is not allowed.

Remove the reference to the report column from the parameter’s ValidationTrigger.

REP–1437 Run time error in the PL/SQL development environment (DE).

This is most likely an abnormal condition.

Refer to the accompanying development environment error message for detailson the problem. If you cannot correct the problem yourself, see “AbnormalConditions” on page 1 – 3.

REP–1438 GETREF function parameter <parameter name> must be of type LONG,LONG RAW, or RAW.

The second parameter in a CDE_MM.GET_REF call specifies a column that isnot of type LONG, LONG RAW, or RAW.

Change the second parameter to specify a column of the correct type.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1508 Cross Product: value of calculation not found.



REP–1510 Group Manager: value of calculation not found.



REP–1517 Column ’<column 1 name>’ references column ’<column 2 name>’, whichhas incompatible frequency.

A column in your data model references another column (e.g., in the Formulafield) in your data model, but the two columns are assigned to incompatiblegroups. For example, if a formula column with a Group of Report referenced acolumn with a Group of G_Emp, this error would be raised.

Remove the column reference, or assign the referencing column to a group thatis compatible with the group of the referenced column.

REP–1518 Group Manager: internal error <Oracle message> while processing group’<group name>’.



REP–1607 Record Manager: report level column not available in rdcagt().



REP–1610 Record Manager: a query with internal joins has ’Maximum Number ofRows’ set.

You most likely used SRW.SET_MAXROW to set Maximum Number of Rowson the cell query of a multi–query cross product.

Remove the call to SRW.SET_MAXROW for the cell query.

REP–1760 Error Utility: internal error #1.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–1761 Internal error <context info> while processing <object type> ’<objectname>’.



REP–1762 Internal error <context info>.



REP–1780 Stack utility: error during allocation.



REP–1781 Stack utility: error during ’push’.



REP–1782 Stack utility: error during ’pop’.



REP–1783 Stack utility: attempt to pop empty stack.



REP–1800 Formatter error.

The possible causes of this error include:

Case 1: In conjunction with “VGS–1101: Reading image file from UNIX”: Animage file is corrupted.

Case 2: In conjunction with “VGS–1701: Executing a report”: There may notbe enough disk space for a temporary file.

Case 3: This is an abnormal condition.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


Possible actions you can take include:

If Case 1: Verify that your image file is displayable. If transferred from anotherlocation, make sure it was transferred correctly. Also try transferringit without compression.

If Case 2: Make sure there is enough space for a temporary file (at least largeenough to store the entire report).


REP–1801 Unknown file type for a ’Read from File’ field.

You attempted to create a file column, but the file type you entered is invalid.

Display the list of values and pick a valid file type.

REP–1802 Unable to read contents of a field from a text file.

You have checked Read from File for a column, but Oracle Reports could notfind the files pointed to by the column. The possible causes of this error includethe 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.


If Case 1: Uncheck Read from File or create the necessary files.

If Case 2: Update your privileges, if possible.


REP–1803 Unable to open destination file ’<filename>’.

The destination file that you specified for the report could not be opened.


REP–1804 Unable to open printer definition file ’<filename>’.

The printer definition file for the printer that you specified could not beopened.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1805 Unable to open mail text file ’<filename>’.

You tried to send the report output to a mail message, but the file for themessage could not be opened.

Consult your Oracle*Mail documentation or contact Oracle Customer Support.

REP–1806 Unable to open mail command file ’<filename>’.



REP–1807 Mail report command failed.



REP–1808 Unable to open print command file.



REP–1809 Print report command failed.



REP–1810 Switching to use Oracle Reports ASCII Driver to run character report.

You are attempting to print a character–mode report to a printer or a file usingeither a Postscript driver or the Microsoft Windows Generic Text driver.


REP–1811 Error while generating Oracle Graphics display.

Oracle Reports called Oracle Graphics to generate an Oracle Graphics display,but no display was generated and passed back to Oracle Reports.

Ensure that the named display exists and will run.

Cause

Action

Cause

Action

Cause

Action


REP–1812 Too many pages formatted. There is either too much data or an error in thereport’s definition.


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.


If Case 1: Abort running of the program. Check the value of PAGE_LIMIT inthe PRODUCT_PROFILE table. Ensure that it is either ’0’, whichmeans the user is allowed to format an unlimited number of pages, orsome value sufficiently large to enable the user to format the report.

If Case 2: Debug the report in the designer.

REP–1813 Object ’<object name>’ too large to fit in matrix cell.

The data fetched into a matrix cell exceeds the capacity of the cell—e.g., the cellmay contain a variable field, and the data may be longer than expected.

Either enlarge your matrix cells until they are able to contain the data fetchedinto them, or redefine your data.

REP–1814 Infinite report detected Object ’<object name>’ can never fit ’<location>’.

The referenced object is causing the most recently formatted page to start withexactly the same state as the page previous . Formatting will therefore cycleuntil abnormally terminated. Possible causes of this error include:

Case 1: An object whose Print Condition type is All overflows to the nextpage;

Case 2: An object whose sizing is Variable or Expand does not appear toextend beyond page boundaries in the Layout editor but does whenthe report is formatted;

Case 3: A repeating frame does not appear to extend beyond page boundariesin the Layout editor but does when the report is formatted.

Using the referenced object as a guide, examine your report layout for objectsthat may extend beyond page boundaries. Note: The object referenced in themessage is the object that extends beyond the boundary. This object may bepushed beyond the boundary by another object, and this second object mayneed modification.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1815 Bad Oracle Number encountered.

A formula providing the value of a column failed to specify any value.

Debug any formulas in your report columns and ensure that each formulaspecifies a value where necessary.

REP–1816 No value specified for COPIES. No output created.

In the Runtime Parameter Form or the Print Job dialog box, you specified zerocopies.

Specify a value of one or more copies.

REP–1817 Start page after end page. No pages output.

In the Print Job dialog box, you specified a starting page number that is greaterthan the ending page number.

Change either the starting page number or the ending page number such thatthe starting number is less than the ending number.

REP–1818 Unable to read data in image format.

Possible causes of this error include:

Case 1: You attempted to read a file or database column as containing animage, but the file or column’s contents are of the wrong format.

Case 2: The width of the Oracle Reports column you specified may betruncating the image because it’s too small.


If Case 1: Make sure you specify a file or column containing an image in a validformat.

If Case 2: Change the width of the Oracle Reports column so that it’s largeenough to display the image.

REP–1819 Filename ’<filename>’ longer than platform maximum of <length>.

You have specified a name for your file that is longer than theplatform–allowed maximum. This is most likely to occur when accessing a fileusing Read from File, and the filename in the database is too long.

Ensure that your database is not corrupted, and/or run the report on aplatform that accepts filenames of the specified length.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1820 Cannot use Oracle Reports ASCII Driver to run bitmap report.

You are attempting to print a bitmapped report when the Oracle Reports ASCIIDriver is your default printer. This is not allowed.

Choose a different printer, then print your report.

REP–1825 Before Report trigger returned FALSE.

Your report includes a Before Report trigger that returned a value of FALSErather than TRUE. When a trigger returns a value of FALSE, report formattingstops.

Make sure that your report trigger is meant to return a value of FALSE.

REP–1826 Between Page trigger returned FALSE.

Your report includes a Between Page trigger that returned a value of FALSErather than TRUE. When a trigger returns a value of FALSE, report formattingstops.

Make sure that your report trigger is meant to return a value of FALSE.

REP–1827 Parentheses in format mask do not balance.

You have an unmatched parenthesis in your format mask.

Edit your format mask and insert the necessary parenthesis.

REP–1828 Format mask may contain at most one set of parentheses.

You used more than one set of parentheses in your format mask.

Use only one set of parentheses in your format mask.

REP–1829 Left parenthesis must precede right parenthesis in format mask.

You reversed the order of the parentheses in your format mask—i.e., used theright, or close, parenthesis before the left, or open parenthesis.

Edit your format mask and reverse the order of the parentheses.

REP–1830 The Exponent field in a format mask must contain exactly 4 E’s.

In specifying that you want to use scientific notation for the field, you haveentered too many or too few E’s. Enter four E’s.

Enter the format mask with four E’s. If you want extra E’s to appear in theoutput, put them in quotation marks (”).

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1831 Missing closing quotation mark in format mask.

You entered an opening quotation mark (”) before the string in the format maskbut 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 thatbegin and end the string.


If Case 1: Add an ending quotation mark after the string.

If Case 2: Enter another quotation mark next to the quotation mark inside thestring.

REP–1832 Illegal character <character> in format mask.

You have entered a character in a format mask which is not valid for formatmasks.

Delete the illegal character. For more information, see “Format Mask” inChapter 8 of the Reports Reference Manual.

REP–1833 A format mask must contain at least one digit.

The format mask you entered contains no digits. You must have at least onetoken in your mask that represents a digit.

Enter a token in your format mask that represents a digit. The tokens thatrepresent digits are 0, 9, *, and S. For more information, see “Format Mask” inChapter 8 of the Reports Reference Manual.

REP–1834 A format mask may contain at most one ’<’ character.

You entered two left angle brackets (<<) in your format mask. You eitheraccidentally typed extra left angle brackets or you wanted some of the extraangle brackets be part of a string. Note: The angle brackets need not beentered sequentially to cause the error.

Delete the extra left angle brackets or place them inside quotation marks (”) aspart of a string if you want them to appear in the output.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1835 A format mask may contain at most one ’>’ character.

You entered two right angle brackets (>>) in your format mask. You eitheraccidentally typed extra right angle brackets or you wanted some of the extraangle brackets to be part of a string. Note: The angle brackets need not beentered sequentially to cause the error.

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.

The left angle bracket (<) must come before the right angle bracket (>) in aformat mask.

Ensure that all angle brackets that are to appear in the output are placed insidequotation marks (”). For the angle brackets that delineate the beginning andending of the decimal aligned region, ensure that the left angle bracket precedesthe right angle bracket in the format mask.

REP–1837 A format mask may contain at most one decimal point.

You entered a format mask with multiple decimal points.

Place any extra decimal points that you want to appear in the output inquotation marks (”). Remove any extra decimal points outside of quotationmarks.

REP–1838 A format mask may contain at most one scale point.

You entered the token V more than once within your format mask.

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.

You placed a comma before the first digit in the format mask, which is illegal.

If you want a comma to appear before the digits in the output, place it inquotation marks (”) as a string. Otherwise, delete the comma.

REP–1840 ’,’ is not allowed after the last digit in a format mask.

You placed a comma after the last digit in the format mask, which is illegal.

If you want a comma to appear after the digits in the output, place it inquotation marks (”) as a string. Otherwise, delete the comma.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1841 ’,’ is not allowed after the decimal point in a format mask.

You placed a comma after the decimal point in the format mask.

If you want a comma to appear after the decimal point in the output, place it inquotation marks (”) as a string. Otherwise, delete the comma.

REP–1842 A format mask may contain at most one exponent field.

You entered the token EEEE more than once within your format mask. You areonly allowed to enter this token once per format mask.

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 theformat mask.

REP–1843 Format masks with exponent fields must have exactly one digit before thedecimal point.

You entered a scientific notation format mask, but had no digits or more thanone digit to the left of the decimal point.

If you had more than one digit to the left of the decimal point, delete digitsuntil there is only one to the left of the decimal point. If you had no digits tothe left of the decimal point, add one digit.

REP–1844 Internal error: Bad index in a Flexible Array.



REP–1845 The decimal point must come between ’<’ and ’>’ in a format mask.

You have placed a decimal point outside the left and right angle brackets (<and >) of your format mask.

Edit your format mask to either remove the decimal point or place it betweenthe brackets.

REP–1846 If roman numeral format mask, must be simply RN or rn.

When you specify the Roman numeral format mask token (RN or rn), youcannot specify any other format mask tokens.

If you want the values to be formatted as Roman numerals, eliminate all formatmask tokens except RN or rn from Format Mask. Otherwise, do not use theRN or rn token.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1847 Failed while trying to set up for printing.

You attempted to print a report. The possible causes of this error include thefollowing:

Case 1: In the Runtime Parameter Form or on the command line, youspecified Printer for DESTYPE, but specified an invalid printer namefor DESNAME.

Case 2: You are executing a report that executes a second report usingSRW.RUN_REPORT. DESTYPE for both reports is set to either File orPrinter, but the first report must be run to the screen.


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 andrun it again.

REP–1848 Failed while trying to begin printing.



REP–1849 Failed while printing.



REP–1850 Error in column <column number> of line <line number> of printerdefinition file <file name>: End of file reached inside quoted string.

Your printer definition file contains a quoted string that was not ended with aquote before the end of the file.

Use the location specified in the error message to locate the error and add theend quote to the quoted string in your printer definition file.

REP–1851 Error in column <column number> of line <line number> of printerdefinition file <filename>: String is longer than <integer> characters.

A string in your printer definition file is longer than maximum number ofallowable characters.

Reduce length of string.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1852 Error in column <column number> of line <line number> of printerdefinition file <filename>: Unknown keyword ”<string>”.

An incorrect keyword is included in your printer definition file.

For information on valid keywords, see “Printer Definition File Syntax” inAppendix B of the Reports Reference Manual.

REP–1853 Error in column <column number> of line <line number> of printerdefinition file <filename>: Unknown keyword ”<string>”.

An incorrect keyword is included in your printer definition file.

For more information on valid keywords, see “Printer Definition File Syntax” inAppendix B of the Reports Reference Manual.

REP–1854 Error in column <column number> of line <line number> of printerdefinition file <file name>: Invalid control character ”<character>”.

An invalid control character is included in your printer definition file.

Replace or remove the invalid control character in your printer definition file.

REP–1855 Error in column <column number> of line <line number> of printerdefinition file <filename>: Unknown character ”<character>”.

An unknown character is included in your printer definition file.

Replace or remove the unknown character in your printer definition file.

REP–1856 Error in column <column number> of line <line number> of printerdefinition file <filename>: <character> is not a valid ASCII character.

An invalid ASCII character appears in your printer definition file.

Replace or remove the invalid ASCII character in your printer definition file.

REP–1857 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”)” to follow <text>.

You have an unmatched parenthesis in your printer definition file.

Edit your printer definition file and insert the necessary parenthesis.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1858 Error in column <column number> of line <line number> of printerdefinition file <file name>: octal(<character>) is not a valid ASCII character.

The octal code for an ASCII character in your printer definition file is incorrect.

Edit your printer definition file and correct the code for the ASCII character.

REP–1859 Error in column <column number> of line <line number> of printerdefinition file <filename>: hex(<character>) is not a valid ASCII character.

The hex code for an ASCII character in your printer definition file in incorrect.

Edit your printer definition file and correct the code for the ASCII character.

REP–1860 Column <column number> of line <line number> of printer definition file<filename>: Expected ”left”, ”center”, or ”right” to follow ”<text>”.

Your printer definition file contains an incomplete code string.

Edit your printer definition file and complete the code string with theappropriate word.

REP–1861 Column <column number> line <line number> of file <filename>: Expected”horizontal”, ”vertical”, ”top”, ”center”, or ”bottom” to follow ”box”.

Your printer definition file contains an incomplete ”box” code string.

Edit your printer definition file and complete the ”box” code string with theappropriate word.

REP–1862 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected keyword ”printer”.

Your printer definition file does not include the required code ”printer”.

Edit your printer definition file and add the required code ”printer” followedby the name of the printer in a quoted string, preferably on the first line of theprinter definition file.

REP–1863 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected name of printer in quotation marks.

Your printer definition file contains the name of the printer after the ”printer”code, but the name does not appear in a quoted string.

Edit your printer definition file and place quotation marks (”) around the nameof the printer after the ”printer” code.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1864 Col <column number> line <line number> of file <filename>: Expected”width, height, return, linefeed, before report, between pages, after report,or code”.

Your printer definition file does not contain any of the code words expected ina printer definition file.

Edit your printer definition file and add the code words that are missing.

REP–1865 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected number after ”width”.

Your printer definition file contains the ”width” code, but no numberspecifying the width of the report appears after it.

Edit your printer definition file and insert a number specifying the width of thereport after the ”width” code.

REP–1866 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected number after ”height”.

Your printer definition file contains the ”height” code, but no numberspecifying the height of the report appears after it.

Edit your printer definition file and insert a number specifying the height of thereport after the ”height” code.

REP–1867 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”report” to follow ”before”.

Your printer definition file contains the word ”before” but not theaccompanying word ”report”.

Edit the printer definition file to include a complete ”before report” entry.

REP–1868 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”pages” to follow ”between”.

Your printer definition file contains the word ”between” but not theaccompanying word ”pages”.

Edit the printer definition file to include a complete ”between pages” entry.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1869 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”report” to follow ”after”.

Your printer definition file (for a multi–page report) contains the code word”after” but not the accompanying word ”report”.

Edit the printer definition file to include a complete ”after report” entry.

REP–1870 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected name of code in quotation marks.

Your printer definition file contains the ”code” code with a user–defined string,but the string is not enclosed within quotation marks.

Edit your printer definition file and enclose the ”code” user–defined stringwith quotation marks.

REP–1871 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”(” to follow ”dec”.

Your printer definition file contains a generalized string using ”dec”, but ”dec”is not followed with a left parenthesis.

Edit your printer definition file and add parentheses around the valuefollowing ”dec”.

REP–1872 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected number to follow ”(”.

Your printer definition file contains a generalized string (e.g., dec, octal), but novalue follows the right parenthesis.

Edit your printer definition file and add a value between the parentheses in thegeneralized string.

REP–1873 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”(” to follow ”octal”.

Your printer definition file contains a generalized string using ”octal”, but”octal” is not followed with a left parenthesis.

Edit your printer definition file and add parentheses around the valuefollowing ”octal”.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action



Your printer definition file contains a generalized string (e.g., dec, octal), but novalue follows the left parenthesis.


REP–1875 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”(” to follow ”hex”.

Your printer definition file contains a generalized string using ”hex”, but ”hex”is not followed with a left parenthesis.

Edit your printer definition file and add parentheses around the valuefollowing ”hex”.


Your printer definition file contains a generalized string (e.g., dec, octal), but novalue follows the left parenthesis.


REP–1877 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected control character to follow ”^”.

Your printer definition file contains a generalized string using ”^”, but nocontrol character follows the ”^”.

Edit your printer definition file and add a control character after ”^”.

REP–1878 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected ”(” to follow ”control”.

Your printer definition file contains a keyword and generalized string (e.g.,after report, before report), but no left parenthesis follows the word ”control”.

Edit your printer definition file and add a left parenthesis following the word”control”.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1879 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected control character to follow ”(”.

Your printer definition file contains a keyword and generalized string (e.g.,after report, before report), but no control character follows the left parenthesis.

Edit your printer definition file and add a control character between theparentheses after the word ”control”.

REP–1880 Error in column <column number> of line <line number> of printerdefinition file <filename>: Box drawing string must be exactly one characterlong.

Your printer definition file contains the ”box” code string, but the drawingstring specified between quotes is more than one character long.

Edit your printer definition file, making sure that one and only one character isspecified as a drawing string.

REP–1881 Error in column <column number> of line <line number> of printerdefinition file <filename>: Expected string containing box drawingcharacter.

Your printer definition file contains the ”box” code string, but no drawingstring is specified.

Edit your printer definition file and specify a drawing string.

REP–1882 Column <column number> line <line number> of file <filename>: Expected”horizontal”, ”vertical”, ”top”, ”center”, or ”bottom” to follow ”box”.

Your printer definition file contains the ”box” code string, but the followingrequired word (one of ”horizontal”, ”vertical”, ”top”, ”center”, or ”bottom”) isnot specified.

Edit your printer definition file and add the appropriate required word.

REP–1883 Unexpected end of printer definition file.

Oracle Reports was able to open your printer definition file, but an erroroccurred while reading it.

Make sure you specified the correct printer definition file. Also, check thecontents of the printer definition file. Edit the file if necessary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1885 Can’t send output to printer.



REP–1886 Expected I after M.

The M you entered in a format mask was not followed by I. The only tokenthat begins with M is the MI token.

If you want to use the MI token, enter an I after the M. If you want thecharacter M to appear in your output, place it inside double quotes (”).Otherwise, delete the M from Format Mask.

REP–1887 Expected R after P.

The P you entered in a format mask was not followed by R. The only tokenthat begins with P is the PR token.

If you meant to use the PR token, enter an R after the P. If you want thecharacter P to appear in your output, you need to place it inside double quotes(”). Otherwise, delete the P from Format Mask.

REP–1888 Only one sign token allowed.

You entered more than one sign token in a format mask.

Delete all sign tokens but one from the format mask.

REP–1889 Trailing sign token must be at end.

You did not place a sign token at the end of the format mask.

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.

You did not place the S token at the beginning or the end of the format mask.

Place the S token at the beginning or the end of the format mask or delete it.

REP–1891 Parentheses tokens must surround other tokens.

The parentheses tokens must surround all the other tokens in the format mask.The parentheses do not surround all other tokens.

Place the parentheses around all of the other tokens in the format mask.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1892 Invalid Destination Type ’<string>’. Valid options: <option, option,...>.

You entered an invalid Destination Type (e.g., batch, while runninginteractively).

Re–try the operation, entering one of the valid Destination Types listed.

REP–1893 Destination Type ’<destination type>’ is not supported on this platform.Valid options: <option, option,...>.

You entered a Destination Type that invalid for your operating system (e.g.,Mail, while running on Microsoft Windows).

Re–try the operation, entering one of the valid Destination Types listed.

REP–1894 The report definition was modified during the current run. No new pageswill be generated.

While previewing a report (using R25DES), you modified the report’s definition(e.g., modified a query, added or deleted objects, etc.), and then returned to thePreviewer and attempted to view additional pages.

This is not allowed. Oracle Reports cannot guarantee that all of the informationused at runtime is still present, so formatting is halted.

REP–1895 Date formatting error while processing <field name>.

Oracle Reports could not format the specified date field.

Check the format mask of the specified date field.

REP–1896 Error in column <column name> of line <line number> of printer definitionfile <filename>: Expected ’backspace’ or ’overstrike’ to follow ’hilight’.

The specified printer definition file contains the ’hilight’ setting, but the settingwas not completed properly.

Add either ’overstrike’ or ’backspace <sequence>’ after ’hilight’.

REP–1897 Error in column <column name> of line <line number> of printer definitionfile <filename>: Non–numeric user–defined printer codes are not supported.

The specified printer definition file contains a user–defined printer code that isnot a number.

Change the user–defined printer code to a number.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–1898 Error in column <column name> of line <line number> of printer definitionfile <filename>: Hilight setting can only be defined once.

The specified printer definition file contains more than one hilight setting.

Remove all but one of the hilight settings from the printer definition file.

REP–1900 Conversion Error

A conversion error occurred while executing R25MREP. This is an abnormalcondition.


REP–1901 PL/SQL compilation failed.

In trying to migrate a report using R25MREP, Oracle Reports encountered aPL/SQL compilation error.

Debug the PL/SQL in the report you are trying to convert.

REP–1950 Invalid Source specified.

The source you specified for R25CONV is not a valid source.

Ensure that you are specifying the correct object or file and that the STYPE iscorrect for that file or object.

REP–1951 Invalid Destination specified.

The Destination you specified for R25CONV is not a valid source.

Ensure that you are specifying the correct object or file and that the DTYPE iscorrect for that file or object.

REP–1952 Number of Destination items must be zero or match number of Sourceitems.

In the Convert dialog box, or while using R25CONV, you specified a list ofDestination items, but the number of items specified is greater than zero anddoes not match the number of Source items specified.

To have Oracle Reports derive the Destination names from the specified Sourcenames, leave Destination blank. Otherwise, make sure the number ofDestination names specified matches the number of Source names specified.Note: If you use wildcards in the Source specification, make sure the numberof Destination names matches the number of Source items in the expandedwildcard list.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–2000 User Exit error.

An error occurred in the user exit.

If you created the user exit, debug the code. Otherwise, contact your DBA.

REP–2001 IAF GET: unknown column.

You specified an unknown column name in your user exit’s IAF GET statement.

Make sure you specify the name of a valid column the the IAF GET statement.

REP–2002 IAF PUT: unknown column.

You specified an unknown column name in your user exit’s IAF PUT statement.

Make sure you specify the name of a valid column in the IAF PUT statement.

REP–2003 Unable to find user exit.

Oracle Reports could not find the user exit that it was supposed to run at thispoint. The most likely cause is that the name and/or location of the user exitcode was not specified correctly.

If you created the user exit, check to make sure you specified the name andlocation of the code correctly when installing it. Otherwise, contact your DBA.

REP–2004 Warning – Unable to retrieve PL/SQL source code of ’<object name>’.

You selected File—>Administration—>Report Doc to document one or morereports, but the RWEPLS user exit failed to retrieve the PL/SQL source code ofan object. This is most likely an abnormal condition.

Check the PL/SQL source code in the named object. For information, see“Abnormal Conditions” on page 1 – 3.

REP–2005 IAF PUT: value of column ’<column name>’ was truncated.

Your IAF PUT statement assigned a value to the named column, but thecolumn was not wide enough to hold the entire value, causing it to truncate.

Widen the column so that it is can hold the entire value.

REP–2100 Calculation Manager error.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–2101 Calculation Manager: source column cannot use segmented memory.



REP–2102 Calculation Manager: computed column cannot use segmented memory.



REP–2103 Column ’<column name>’: PL/SQL formula returned invalid value or novalue.

The specified formula column contains a PL/SQL function that does notspecify a return value.

Verify that the function includes a return statement for every code path.

REP–2300 ”<ORACLE message>”.

You entered an SRW.DO_SQL statement that caused the ORACLE message.

Edit the SRW.DO_SQL statement. For more information on the ORACLEmessage, see the ORACLE7 Server Messages and Codes Manual.

REP–2301 Error allocating SQLDA descriptor. <ORACLE message>



REP–2302 Error parsing the SQL statement. <ORACLE message>

Oracle Reports encountered an error while parsing the SRW.DO_SQLstatement.

Refer to the ORACLE message to see why the SQL statement could not beparsed.

REP–2303 Error describing bind variables. <ORACLE message>

Oracle Reports encountered an error while describing bind variables in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the bind variables could not bedescribed.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–2304 Error opening SQL cursor. <ORACLE message>

Oracle Reports encountered an error while opening a cursor in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the cursor could not be opened.

REP–2305 Error describing select list. <ORACLE message>

Oracle Reports encountered an error while describing the select list in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the bind variables could not bedescribed.

REP–2306 Error fetching bind variables. <ORACLE message>

Oracle Reports encountered an error while fetching bind variables in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the bind variables could not befetched.

REP–2307 Error fetching data record. <ORACLE message>

Oracle Reports encountered an error while fetching a data record in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the data record could not be fetched.

REP–2308 Error processing select list. <ORACLE message>

Oracle Reports encountered an error while processing the select list in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the select list is invalid.

REP–2309 Error formatting date field. <ORACLE message>

Oracle Reports encountered an error while formatting a date field in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the date field could not format.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–2310 Error putting value into column. <ORACLE message>

Oracle Reports encountered an error while trying to insert a value into acolumn in an SRW.DO_SQL statement.

Refer to the ORACLE message to see why the value could not be assigned.

REP–2311 Error during Commit. <ORACLE message>

Oracle Reports encountered an error while trying to do a commit in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the commit failed.

REP–2312 Error allocating data record. <ORACLE message>

Oracle Reports encountered an error while allocating a data record in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the record could not be allocated.

REP–2313 Error parsing select list. <ORACLE message>

Oracle Reports encountered an error while parsing the select list in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the select list could not be parsed.

REP–2314 Error closing SQL cursor. <ORACLE message>

Oracle Reports encountered an error while trying to close a SQL cursor in anSRW.DO_SQL statement.

Refer to the ORACLE message to see why the close cursor operation failed.

REP–2315 Error freeing data record. <ORACLE message>



REP–2316 Unknown column ’<column name>’.

A column referred to in an SRW.DO_SQL statement cannot be found.

Debug your PL/SQL and make sure your SRW.DO_SQL statement contains thecorrect column name.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–2317 Value of column ’<column name>’ was truncated.

A column value obtained via an SRW.DO_SQL statement was truncated.

Go to the column’s property sheet and increase its Width. Or, restrict the sizeof the value that your SRW.DO_SQL statement is putting into the column.

REP–3000 Internal error starting Oracle Toolkit.



REP–3001 Internal error initializing File Dialog.



REP–3002 Internal error initializing printer information.



REP–3020 Internal error starting Oracle Resource Manager.



REP–3021 Internal error processing menu resource.



REP–3022 Internal error processing window resource.



REP–3023 Resource File not found.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–3040 Internal error starting Oracle Observer Model.



REP–3060 Internal error initializing color table. Checking VGS resources isrecommended.



REP–3080 Internal error initializing Oracle Image.



REP–3081 Error running image viewer.

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.



If Case 1: Ensure that the image file specified as the source of the button actionis in a displayable format.

If Case 2: Make more memory available, if you can, or ask your systemadministrator for assistance.


REP–3082 Error running sound dialog.

You selected a Previewer button with a defined action of playing a sound, butthe sound dialog is unavailable. Possible causes of this error include:

Case 1: The sound file specified as the source is in an incorrect format.



Action

Cause

Action

Cause

Action

Cause

Action



If Case 1: Ensure that the sound file specified as the source of the button actionis in a playable format.



REP–3083 Error running video player.

You selected a Previewer button with a defined action of playing a video, butthe video player is unavailable. Possible causes of this error include:

Case 1: The video file specified as the source is in an incorrect format.




If Case 1: Ensure that the video file specified as the source of the button actionis in a playable format.



REP–3085 Multimedia source file ’<filename>’ not found.

You activated the button in the Previewer, but the source for the button’sintended action (whether sound, image, or video) cannot be found or has beencorrupted.

Open the property sheet for the button in question and verify the existence,format, and path information for the specified source file.

REP–3086 Bad multimedia source file.

You activated the button in the Previewer, but the source for the button’sintended action (whether sound, image, or video) has been corrupted.

Open the property sheet for the button in question and verify the existence,format, and path information for the specified source file. If it is correct, checkthe file itself.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–3087 ImageViewer not supported on this configuration.

Your platform and/or configuration will not support displaying images via theImageViewer.


REP–3088 Sound not supported on this configuration.

Your platform and/or configuration will not support playback of sound files.


REP–3089 Video not supported on this configuration.

Your platform and/or configuration will not support playback of video files.


REP–3100 Matrix must include at least 1 Down and 1 Across repeating frame.

You tried to create a matrix (using Tools—>Create Matrix) without the properobjects selected in the Layout editor. A matrix layout requires that at least onegroup have a repeat direction of Down and one have a repeat direction ofAcross.

Select two repeating frames—one Down, one Across—that overlap, then chooseArrange—>Create Matrix.

REP–3101 All selected Down and Across repeating frames must be nested.

You tried to create a matrix (using Arrange—>Create Matrix) and the Downand Across repeating frames were not properly overlapping and nested.

Make sure the selected Down and Across repeating frames are properlyoverlapping and nested before creating the matrix.

REP–3102 Anchors, matrices, and margins cannot be grouped.

You chose Arrange—>Group and at least one of the objects selected was ananchor, matrix, or margin.

Deselect all anchors, matrices, and margins before grouping objects.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–3103 Only text and graphical boilerplates can be rotated.

You attempted to rotate either a frame, a field, a margin, an anchor, a matrixobject, a piece of external boilerplate, an Oracle Graphics display, an OLE2object, or a button. None of these can be rotated.

You can rotate any boilerplate objects except images and external boilerplate.Depending on your operating system, you may or may not be able to see thetext of boilerplate text that is rotated.

REP–3104 Anchors and matrices cannot be scaled separately.

You attempted to scale one of the layout objects listed above without alsoscaling its associated object. This is not allowed.

Select at least one associated object (anchoring object for anchors, repeatingframes for matrices), then re–try the scaling operation.

REP–3105 Display Column must be selected for the Display Query.

In the Oracle Graphics property sheet, you entered a name for Display Query,but you did not select any Display Columns. If you specify Display Query, youmust also specify Display Columns.

Specify Display Columns or remove the value from Display Query.

REP–3106 Warning: Source/Display Column is selected without Display Query name.The selected Source/Display Column will be ignored.

In the Oracle Graphics property sheet, you selected a Source or DisplayColumn but did not enter the name of a Display Query.

Enter the name of the display query to which you intend to pass data.

REP–3107 Object <object name> cannot be moved in front of its child. Operationdisallowed.

You tried to move a layout object in front of one or more of its own childobjects.

If you still want to move the layout object, toggle Confine mode off, then moveit. Otherwise, no action necessary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–3108 Object <object name> cannot be moved behind its container. Operationdisallowed.

You tried to move a layout object behind one or more of its own parent objects.

If you still want to move the layout object, toggle Confine mode off, then moveit. Otherwise, no action necessary.

REP–3109 Warning: Alignment operation failed because of container constraints.Undo changes to revert to the original state.

You tried to align multiple layout objects but the result of such an operationwould have violated container constraints (i.e., moved a field outside of itsenclosing frame).

Select Edit—>Undo to ensure your layout is the same as before the attemptedoperation. Then you can either resize or reposition the container in question toenable you to perform the operation, or do nothing.

REP–3110 Warning: Same size operation failed because of container constraints. Undochanges to revert to the original state.

You tried to change one or more layout objects to the same size, but the resultof such an operation would have violated container constraints (i.e., enlarged afield beyond its enclosing frame).

Select Edit—>Undo to ensure your layout is the same as before the attemptedoperation. Then, you can either resize or reposition the container in question toenable you to perform the operation, or do nothing.

REP–3111 Changing the border width of <object name> violates the constraints ofConfine mode. Operation disallowed.

You tried to change the border width of an object such that the result wouldhave violated container constraints (i.e., widening the border of a boilerplateobject so that it extended beyond its enclosing frame).


REP–3130 Parameter form fields and images cannot be rotated.

You tried to rotate one of the parameter form objects listed above. This is notallowed.

You can rotate any boilerplate objects, except images, in the Parameter Formeditor. Depending on your operating system, you may or may not be able tosee the text of boilerplate text that is rotated.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–3131 Parameter form boilerplate text cannot fit on the page.

You entered text in the Title, Hint, Status, or Label field in the DefaultParameter Form property sheet that is too long to fit on the page.

Reduce the length of the appropriate text field.

REP–3140 Program unit editor internal error. Could not get application handle.



REP–3150 One editor must remain open for each report.

You attempted to close all three of the editors (Data Model, Layout, andParameter Form) for a report. You must leave at least one editor open.

Leave one editor open for each report.

REP–3151 Invalid width for column ’<column name>’ cannot be highlighted, sincegroup ’<group name>’ is not selected.

An invalid value was entered for the Width of a column in the Default Layoutdialog box. Since the group that owns the column is not selected, the column isnot listed.

Select the group that owns the column. Scroll down to the column and enter avalid value for Width.

REP–3152 Data link, anchor, or polygon creation must be completed in the editorbefore this action.

You tried to perform some action (e.g., close the report) before finishing thecreation of a data link in the Data Model editor, an anchor in the Layout editor,or a polygon in the Layout editor or Parameter Form editor.

Complete the unfinished object before continuing.

REP–3153 Insufficient resources to create window.

There were insufficient resources available to create the requested window.

Make more resources available by closing windows or other applications.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–3154 Insufficient resources to create module.

There were insufficient resources available to create the requested module(report, external query, external PL/SQL library. You probably selectedFile—>New, File—>Open..., or File—>Revert.

Make more resources available by closing windows or other applications.

REP–3200 Concurrent previewer actions not allowed.

You are attempting to activate more than one button at one time, in either thesame or multiple Previewers. For example, you may be trying to both play asound and display a video at the same time. This is not allowed.

Only activate one button at a time.

REP–3300 Fatal error in ’<component name>’. Returning to the event loop. ’<productcode>–<number>: <product error>.’



REP–3301 Error occurred in ’<component name>’. Returning to the event loop.’<product code>–<number>: <product error>’.



REP–3302 Fatal error occurred during Quit. Exiting Oracle Reports.



REP–03335 Unhandled Internal CA Error.



REP–03350 Unhandled Internal UI Error.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03351 Undefined failure in UI.



REP–03352 Unexpected error in UI.



REP–03353 Attempt to create with an attribute that is not creatable.



REP–03354 Attempt to set with an attribute which is not settable.



REP–03355 Attempt to set with an attribute which is not gettable.



REP–03356 Attempt to set/get an unknown attribute.



REP–03357 Attempt to set attribute values which are conflicting.



REP–03358 Attempt to set an attribute to an out–of–range value.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03359 This function call is out of context.



REP–03360 The view class does not support being a scrollee.



REP–03361 This function call provokes an illegal recursion.



REP–03362 The internal mpi allocator failed.



REP–03363 The client–supplied memory allocation functions failed.



REP–03364 Attempt to support an unsupported function.



REP–03365 An attempt to set attributes out of context.



REP–03366 An attempt to perform an illegal operation on a root view.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03367 One of the parameters to the functions is out of range.



REP–03368 The connection to the windowing system failed.



REP–03369 The connection to the windowing system has been broken.



REP–03370 The windowing system failed.



REP–03371 uiER_CL_FORMAT_UNAVAILABLE



REP–03372 uiER_CL_FORMAT_UNREGISTERED



REP–03373 Operation was timed out.



REP–03374 uiER_NOT_FOUND



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03375 uiER_ILLEGAL_TOPITEM



REP–03376 uiER_SE_BAD_FORMAT



REP–03377 The view class does not support the scroller interface.



REP–03378 Attempt to remove a readshare color from a palette.



REP–03379 Unable to create window.

Oracle Reports was unable to create a window. It could be that you have toomany reports or windows open, and lack of memory resources.

Close some reports and windows.

REP–03380 Unable to create view.

Oracle Reports was unable to create a view. Possible causes of this errorinclude:

Case 1: You may have too many reports or windows open, and lack memoryresources.

Case 2: The environment variable NLS_LANG in oracle.ini may be set tosomething other that american_america.WE8ISO8859P1. Other settingsfor this variable are not supported.

Possible actions to correct these causes are:

If Case 1: Close some reports and windows.

If Case 2: Set NLS_LANG to the correct language.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03381 Unable to create color palette.

Oracle Reports was unable to create a color palette. It could be that you havetoo many reports or windows open, and lack of memory resources.

Close some reports and windows.

REP–03400 Unhandled Internal DE Error.



REP–03420 Unhandled Internal SRW Error.



REP–03430 Unhandled Internal HH Error.



REP–03431 Invalid attribute value.



REP–03432 Invalid context.



REP–03433 Specified word not found.



REP–03434 Link to external document.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03435 Help session is null.



REP–03436 Document is not a help document.



REP–03437 Document revision is newer than help.



REP–03438 Specified attribute is not settable.



REP–03439 Specified attribute is not gettable.



REP–03440 Invalid data link.



REP–03441 Logical attributes missing or bad.



REP–03442 NLS language string missing or bad.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–03443 No search string specified.



REP–03444 String begins with percent sign.



REP–03445 Unknown toolkit error.



REP–03446 Unknown object store error.



REP–3447 Out of memory.



REP–3448 Unknown Resource manager error.



REP–3480 Unhandled Internal REM Error.



REP–3485 Unhandled Internal VGS Error.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause


REP–3500 Unhandled Internal UT Error.



REP–3510 Unhandled Internal ZOM Error.



REP–3600 Both module nodes and non–module nodes selected. Please select onlynodes from one of these types of nodes.

You have chosen Navigator—>Delete but both object nodes and module nodesare selected. You cannot close modules and delete objects in the same action.

If you wish to delete objects, deselect all module nodes. If you wish to closemodules, deselect all object nodes. Then select Navigator—>Delete again.

REP–4001 Error occurred in the OLE subsystem.

An unspecified OLE2 error occurred during initialization. Refer to theaccompanying OLE error message for more information. Other possible causesof this error include the following:

Case 1: Your OLE2 server is not functioning correctly.

Case 2: An error occurred during installation of Oracle Reports and the OLE2functionality did not install correctly.



If Case 1: Refer to the OLE2 server documentation for more information.

If Case 2: Re–install Oracle Reports.


REP–4002 Error occurred while initializing OLE subsystem.

An error occurred during initialization of OLE2 libraries. Refer to theaccompanying OLE error message for more information. Other possible causesof this error include the following:

Case 1: Your OLE2 server is not functioning correctly.

Case 2: An error occurred during installation of Oracle Reports and the OLE2functionality did not install correctly.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action




If Case 1: Refer to the OLE2 server documentation for more information.

If Case 2: Re–install Oracle Reports.


REP–4003 Error occurred while creating OLE object.

You were attempting to create an OLE2 object when an OLE error occurred.

Refer to the accompanying OLE2 error message for more information.

REP–4004 Error occurred while restoring OLE object.

You were attempting to restore an OLE2 object when an OLE error occurred.


REP–4005 Error occurred while saving OLE object.

You were attempting to save an OLE2 object when an OLE error occurred.


REP–4006 Error occurred while performing Cut/Copy operation. OLE object is notplaced in the clipboard.

You were trying to cut or copy an OLE2 object when an OLE error occurred.


REP–4007 Error occurred while pasting OLE object from the clipboard.

You were trying to paste an OLE2 object from the clipboard when an OLE erroroccurred.


REP–4008 Error occurred while trying to perform operation defined by OLE object.

You were trying to perform an action normally supported by the OLE2 serverwhen an OLE error occurred.

Refer to the accompanying OLE error message for more information.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–4009 Error occurred while trying to activate OLE object.

You were trying to activate an OLE2 object (e.g., double–click on it in thePreviewer) when an OLE error occurred.


REP–4020 Conversion of OLE object to a different type failed.

You were trying to convert an OLE2 object contained in a piece of boilerplate toan OLE2 object of a different type when an OLE error occurred. This indicatesa problem with the OLE2 server.

Check that the object is correctly installed and re–install, if necessary.

REP–4021 Microsoft Object Linking and Embedding is not supported on this platform.

You are running a report that was created on a platform supporting OLE2, andcreated with OLE2 objects, but you are now running it on a platform that doesnot support OLE2. You are trying to access the visual representation of whatwas once an OLE2 object.

No action is necessary. Remove the object if desired.

REP–4022 Wrong version of OLE libraries. OLE functionality will be disabled.

The OLE2 libraries installed on your machine are incompatible with thosesupported by your version of Oracle Reports. As Oracle Reports cannotguarantee that your OLE2 support will function, it is disabling OLE2functionality.

Install the correct libraries.

REP–4023 There is insufficient memory available to complete operation.

There is not sufficient memory remaining on your system to perform thedesired action.

Exit any unnecessary applications that are running. If that does not work, seeyour Microsoft documentation for suggested procedures to enhance memoryusage.

REP–4024 DOS SHARE services required for successful operation. SHARE is notrunning.

The DOS SHARE utility is required, but SHARE is not running.

Make sure SHARE is running

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–4025 Read failure.

Data cannot be read from the specified device.

Check the device to determine if it is malfunctioning, and, if so, consult thedevice documentation to determine the proper error recovery procedures.

REP–4026 Write failure.

Data cannot be written to the specified device.

Check the device to determine if it is read–only. If not, consult the devicedocumentation to determine the proper error recovery procedures.

REP–4027 Too many files opened. There are insufficient resources to open another file.

You are attempting to open more files than are supported by Windows.

Close some applications. Also, check your config.sys file and ensure that FILES

is not set below 20. Note: Remember that OLE2 boilerplate objects reserveeither two or three file handles per object and so you may have more files openthan you are aware.

REP–4028 No space left on device.

The specified device is full.

Delete unnecessary data or write to a different device.

REP–4029 Failed to obtain presentation of the OLE object. Cannot render an OLEobject.

You tried to display an OLE2 object in a report but the display aspects definedby the OLE2 server were unavailable.

Verify that the OLE2 object has not been corrupted and that the server iscorrectly installed. Re–install if necessary.

REP–4030 Failed to restore original display aspects of the OLE object. Object contentwill be used.

You tried to display an OLE2 object in a report but the display aspects definedby the OLE2 server were corrupted or stored in the database and could not berestored. Oracle Reports will display the object using the default aspect.

Verify that the OLE2 server is correctly installed. Re–install if necessary.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–4031 The server application cannot be found. Make sure the application isproperly installed and registered correctly.

You are attempting to access an OLE2 server via an OLE2 object, but the serveris currently inaccessible. The server may have been deleted, renamed, ormanually reinstalled in a different location.

Check the installation of the server and re–install if necessary.

REP–4032 Cannot connect to the linked OLE object source. Make sure that link sourcehas not been moved, renamed, or deleted.

Oracle Reports is trying to connect to the specified source of the OLE2 objectboilerplate but cannot.

Verify that the OLE2 object source has not been moved or deleted, and that itsfilename has not been changed

REP–4033 Cannot connect to the linked object source, because it is across a networkthat is not connected to this machine.

You are trying to link to an OLE2 object that is stored on a device to which youdo not currently have an established network connection.

Establish a connection to the proper device.

REP–4034 File not found or invalid filename is used by OLE object.

An OLE2 object is trying to access a file that it cannot find.

Verify that the file has not been corrupted, moved, or renamed.

REP–4035 A share violation has occurred while performing operation on OLE object.

Possible causes: you are trying to link to the same file via multiple OLE2objects, or trying to access the same temporary file via different applications.

Make sure that you do not have multiple OLE2 objects attempting to access thesame file at the same time. Also, check the intallation of your OLE2 server.

REP–4036 Access denied while performing operation on OLE object.

You are trying to update an OLE2 object to which you do not have write access.

Obtain the proper permissions to the file before trying to update it.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–4037 File operation on OLE object failed because disk is write–protected.

You tried to save to file an OLE2 object but could not because the disk iswrite–protected.

Save the object to a disk for which you have write priviledges, if possible. Ifnot, no action is necessary.

REP–4038 Unexpected error occured in the file system while performing operation onOLE object.

A non–specific file error such as a corruption of the hard disk occurred.

Refer to your operating system documentation more information.

REP–4039 Unexpectied error returned by OLE.

A non–specific OLE error occurred.

Refer to your Microsoft documentation for more information.

REP–4040 Incorrect or corrupted OLE object persistent data. OLE object cannot berestored from this data.

The information used by the OLE server to restore the OLE2 object in yourreport 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 RAWcolumn referenced does not contain OLE2 objects.


If Case 1: Verify that the object is viable by embedding it in a container usinganother application.

If Case 2: Use SQLPlus to check the table in the database and verify thecontents of the column.

REP–4041 No operations defined on this object or object is static.

You tried to take some action on an OLE2 object but no actions have beendefined as applying to the object. Possibly the object was converted to a staticbitmap.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–4042 Requested action on OLE object is valid, but cannot be performed at thismoment. Object server may be busy.

You tried to take a valid action on an OLE2 object but cannot, due to lack ofserver resources. A possible cause is that you are trying to open a secondinstance of a single–instance application.

Check system resources (memory, etc.) and increase where possible, or try theoperation later.

REP–4043 Operation requested on OLE object is invalid and cannot be performed.Make sure the application is properly installed.

The action you tried to take on an OLE2 object is not recognized as valid.

Make sure the proper version of the OLE server is correctly installed.Re–install if necessary.

REP–4044 Can not access system registry. Make sure you have enough free systemresources and registry is not corrupted.

A read or write operation in the system registry failed.

Consult your Microsoft documentation.

REP–4045 Problem occurred in the system registry. Make sure the object server isproperly installed.

Some information about the server is missing from the registry.

Make sure the OLE server is installed correctly. Re–install if necessary.

REP–20091 Warning: Do you wish to save the current module before disconnecting fromthe database?

You have an open module that is stored in the database. If you disconnect fromthe database, you will not be able to save your changes to the database.

Select Yes to save the module before disconnecting from the database; themodule remains open so you can reconnect if desired and save it to thedatabase again. Select No to disconnect from the database without saving themodule; the module remains open. Select Cancel to remain connected to thedatabase without saving; once again, the module remains open.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–20099 Printer changed while previewing. Printer font remapping could causetruncation. Continue with printing?

In the time between running the report and selecting Print from the Previeweryour default printer has changed.

Select Yes to print anyway. Select No to halt printing, then close your reportand either reset your printer and run your report again, or simply run it againto format it for the current printer.

REP–20128 Report was not run with DESTYPE=PREVIEW. Screen font remappingcould cause truncation. Continue with printing?

You selected Print from the Previewer, but specified Screen instead of Preview,which formats your report as though using printer fonts and provides a moreaccurate view of your report’s printed output.

Select Yes to print anyway. Select No to halt printing. Then close your reportand run it again while specifying Preview to format it for the printer.

REP–20129 Opening a report saved with a newer version of Oracle Reports.Functionality may be lost. Continue?

You tried to open a report with a version of Oracle Reports older than theversion used to create the report. If the report uses functionality unavailable inthe older version, that functionality will be eliminated from the report.

If you are concerned about losing functionality, do not open the report until youhave upgraded to the most recent version of Oracle Reports.

REP–20135 You cannot run without a layout. Would you like to default a layout?

You attempted to run your report after creating a data model but beforecreating a layout.

Create a layout, then run your report.

REP–20136 The region you have chosen for your default layout is too small. Extendregion to page boundaries?

You used the Additional Default Layout tool from the Tool palette to draw aregion for a layout that was not large enough to accommodate the settingsspecified in the Default Layout dialog box.

Either select Yes to have Oracle Reports extend the possible range of the layoutto the boundaries of a report page, or select No and change the settings in theDefault Layout dialog box to shrink the size of the layout.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–20150 Warning: Page width of report <report name> changed to fit the font for acharacter cell. Might be a consequence of font–mapping.

A character font has been substitited for a bitmapped font in the report youopened, and the page width has been adjusted accordingly. A possible cause: abitmapped report is being opened in the character–mode runtime engine.

If you want the font mapped to a specific font, edit the uifont.ali file to map thefonts to the desired ones. Otherwise, no action is necessary.

REP–20151 Warning: some fonts have been changed according to the mapping inuifont.ali.

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.

If you want the font mapped to a specific font, edit the uifont.ali file to map thefonts to the desired ones. Otherwise, no action is necessary.

REP–20190 Quit will terminate the current report, as well as any other pending reports.

You have specified that you want to exit Oracle Reports Server while one ormore reports are still executing or awaiting execution.

If you want your reports to finish executing, cancel the operation. Otherwise,accept the warning dialog.

REP–20191 Cannot exit Windows when this program is running. Close Reports Serverand exit Windows.

Oracle Reports Server requires Windows, but you have specified that you wantto exit Windows while the Server is still running.

Exit the Server before exiting Windows.

REP–25206 Converting <source name> to <destination name> failed.

The most likely cause of this error is that the source type you specified wasincorrect.

Ensure that the source file is of the specified source type.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–25207 Invalid conversion: stype and dtype are not of the same document type.

You attempted to convert a document of one type to another type—i.e., youattempted to convert one of the possible report files to a PL/SQL file, or viceversa.

Ensure that the source and destination of your conversion are the same type ofdocument.

REP–25401 Cannot locate <user exit .DLL file>.

Your report attempted to execute a user exit, but the user exit .DLL file couldnot 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

Locate the specified .DLL file and place it in one of the directories listed above.

REP–25402 Internal error – Cannot locate <function name> within <user exit .DLL file>.

Your report attempted to execute a user exit, but certain functions used tolocate and execute user exits cannot be located in the user exit .DLL file. Thismeans that the user exit .DLL was built incorrectly, because these functions arelocated in a .OBJ file shipped with Oracle Reports, which should always belinked into the user exit .DLL.

Rebuild the specified user exit .DLL correctly.

REP–26400 An unknown MOVEREP error occurred.



REP–26401 Cannot open rw.log.

You specified LOGFILE=filename on the command line, but the file filenamecould not be opened for writing.

Specify another filename in a writable directory.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26403 Not enough memory available.

R25MREP cannot access sufficient memory from the system to complete thistask.

Make more memory available, if you can, or contact your system administratorfor this machine.

REP–26404 Abnormal condition: Error while freeing memory.



REP–26410 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Field table.



REP–26411 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Summary table.



REP–26412 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Text table.



REP–26413 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Foreign Key table.



Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26414 You cannot execute this report because it does not have queries, groups orfields.

You named a report, but you have not yet defined any queries. As a result,there are no objects (including groups and fields) to process.

Acknowledge the error message by pressing [Spacebar]. Then move to theQuery Screen by pressing [Q], or by moving the highlight to ”Query” andselecting this item. Enter a name for a query, press [Next Field], then enter avalid SQL SELECT Statement. You can now execute the report by pressing[Menu], [A] (for ”Action”), [E] (for ”Execute”), and [Select]. By default, theoutput will appear on your screen.

REP–26415 Error while matching field ’<field name>’ to its group.



REP–26416 Text ’<text screen>’ exceeds 10 panels (the maximum allowed).

If SQL*ReportWriter produced the report as it is currently defined, it wouldhave to create more than ten panels. Ten, however, is the maximum allowed inany report.

There are many ways to reduce the number of panels, such as decreasing thewidth of fields and summaries, deleting panels or moving fields closertogether, etc. Consider the field identified in the error message whenestimating how close you currently are to the 10–panel maximum. Estimatehow close this field is to the end of the report, then take one of the aboveactions to decrease your report by the necessary amount.

REP–26417 Text ’<text screen>’ exceeds 10 pages (the maximum allowed).

If SQL*ReportWriter produced the report as it is currently defined, it wouldhave to create more than ten pages. Ten, however, is the maximum allowed inany report.

There are many ways to reduce the number of pages, such as decreasing thewidth of fields and summaries, deleting panels or moving fields closertogether, etc. Consider the field identified in the error message whenestimating how close you currently are to the 10–page maximum. Estimatehow close this field is to the end of the report, then take one of the aboveactions to decrease your report by the necessary amount.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26418 Abnormal condition: The Type for text ’<text screen>’ is not inSQL*ReportWriter’s tables.



REP–26419 Text ’<text screen>’ cannot be matched to a SQL*ReportWriter object.



REP–26420 Abnormal condition: The group Type for text ’<text type>’ is not inSQL*ReportWriter’s tables.



REP–26421 Foreign keys in SQL*ReportWriter’s tables cannot be joined.



REP–26422 Summary ’<summary name>’ cannot be processed.



REP–26423 ORACLE error occurred during logon.

You invoked an Oracle Reports executable (R25MREP, R25CONV, etc.) and anORACLE error occurred when Oracle Reports attempted to logon to ORACLE.

Re–run the executable. If this error occurs repeatedly, contact Oracle CustomerSupport for assistance.

REP–26424 ORACLE error occurred during logoff.

You invoked an Oracle Reports executable (R25MREP, R25CONV, etc.) and anORACLE error occurred when Oracle Reports attempted to logoff of ORACLE.

Re–run the executable. If this error occurs repeatedly, contact Oracle CustomerSupport for assistance.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26425 Abnormal condition: ORACLE error occurred while attempting to access theReport ID.



REP–26426 Abnormal condition: Object’s name is not in SQL*ReportWriter’s tables.



REP–26427 Text cannot be joined to a valid Object.



REP–26428 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Parameter table.



REP–26429 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Text Long table.



REP–26430 The report named ’<report name>’ cannot be found in SQL*ReportWriter’stables.

You attempted to open a report that is not stored in the SQL*ReportWritertables.

Specify the correct name of the report, or load the report into the tables.

REP–26431 The report named ’<report name>’ already exists in SQL*ReportWriter’stables.

You attempted to load into the SQL*ReportWriter tables a report that alreadyexists there.

Rename or drop the report stored in the SQL*ReportWriter tables, then load thereport into the tables.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26432 ORACLE error in processing query.

A query in your report cannot be parsed correctly.

Correct the query in your report.

REP–26433 Not enough memory available for ORACLE to process a SQL*ReportWriterquery.

ORACLE cannot access sufficient memory from the system to finish queryingSQL*ReportWriter’s tables.

Make more memory available, if you can, or contact your system administratorfor this machine.

REP–26434 There are duplicate panel numbers defined for text ’<text object>’.

All panels that belong to a particular text Object and Type must have uniquenumbers. You may have mistyped the panel number.

Use [Insert Record Above] or [Insert Record Below] and enter the panelnumber you wish. This will automatically renumber the existing panels.

REP–26435 Abnormal condition: Error occurred while processing text highlightingcharacters.



REP–26436 ORACLE error occurred while trying to lock the SQL*ReportWriter tables.

You attempted to logon to ORACLE or lock the SQL*ReportWriter tables underthe same username/password as another user, while the other user held anexclusive lock on the SQL*ReportWriter tables.

Wait for ORACLE to release the other user’s locks on the SQL*ReportWritertables before attempting to access them.

REP–26437 Abnormal condition: Invalid text Type for ’<text screen>’.



Cause

Action

Cause

Action

Cause

Action

Cause


REP–26438 The frequency of field ’<field name>’ in text ’<text screen>’ is inconsistent.

You referenced the field in a text object where it is not allowed. These invalidobjects might include:

Case 1: A Page Header or Page Footer.

Case 2: A group that falls in a different path of the query structure than thefield’s own path.

Case 3: A non–body group object in the same group as the field.

Case 4: For non–computed fields, the body of a higher group.

Make sure none of the above circumstances apply to your report.

REP–26439 The frequency of summary ’<summary name>’ in text ’<text screen>’ isinconsistent.

You referenced the summary in a text object where it is not allowed. Theseinvalid objects might include:

Case 1: A group that falls in a different path of the query structure other thanthe summary’s own path.

Case 2: A Title or Trailer Page, Report Header or Footer, or Page Header orFooter whose Print Condition is not Report.

Case 3: The group footer of the field being summarized, if the summary usesa running function.

Case 4: In a matrix report, a group footer belonging to the same group wherethe summary is referenced in a sub_footer.

Reference this field in a valid text object.

REP–26440 Abnormal condition: a field’s Data Type has been changed to an invalidvalue in SQL*ReportWriter’s tables.



REP–26441 Text ’<text screen>’ does not fit within the specified Width of the report.

The boilerplate text and field/summary references in this text object add up tomore columns than can fit between the report margins.

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


You can do any of the following to correct this problem:

• Increase the Page Width or decrease the left and right margins.

• Decrease the Width of any fields or summaries that are referenced inthis text object.

• Edit the text object itself; reduce white space, use more lines, etc.

REP–26442 Text ’<text screen>’ does not fit within the Height of the report.

The boilerplate text and field/summary references in this text object adds up tomore lines than can fit between the top and bottom report margins.

You can do any of the following to correct the problem:

• Increase the Page Height or decrease the top and bottom margins.

• Delete some of the fields and summaries referenced by the text object.

• Edit the text object itself; reduce white space, use fewer lines, etc.

REP–26443 Group ’<group name>’ on panel ’<panel number>’ does not fit within theWidth of the report.

The boilerplate text and field/summary references in this group text adds up tomore columns than can fit between the left and right report margins.

You can do any of the following to correct the problem:

• Increase the Page Width or decrease the left and right margins.

• Decrease the Width of any fields or summaries that are referenced inthis group text.

• Edit the group text: reduce white space, use more lines, delete text, orremove field and summary references.

REP–26444 Abnormal condition: Invalid Relative Position for group ’<group name>’.



REP–26445 Abnormal condition: Group ’<group name>’ cannot be processed.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26446 Field ’<field name>’ on Panel ’<panel number>’ does not fit within theHeight of the report.

The positioning of fields and text on this panel has taken up so much room thatthere is not enough room to fit the field in question on the page.

Increase the Page Height, or reposition the fields and text on the panel.

REP–26447 Field ’<field name>’ on Panel ’<panel number>’ does not fit within theWidth of the report.

The positioning of fields and text on this panel has taken up so much room thatthere is not enough room to fit the field in question on the page.

Increase the Page Width, or reposition the fields and/or text on the panel.

REP–26448 This report exceeds the limit of 10 panels. The problem occurred whileprocessing field ’<field name>’ on panel ’<panel number>’.

This report would require more than 10 panels to execute.

There are many ways to reduce the number of panels, such as decreasing thewidth of fields and summaries, deleting panels or moving fields closertogether, etc. Consider the field identified in the error message whenestimating how close you currently are to the 10 panel maximum. Estimatehow close this field is to the end of the report and take the desired steps toreduce the number of panels a sufficient amount.

REP–26449 Abnormal condition: Encountered invalid key while processing a summary.



REP–26450 Abnormal condition: Invalid text Justification for ’<text screen>.



REP–26451 Abnormal condition: The reset level of field ’<field name>’ cannot be lowerthan its print level.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26452 Abnormal condition: The reset level of summary ’<summary name>’ cannotbe lower than its print level.



REP–26453 Group ’<group name>’ on panel ’<panel number>’ does not fit within theHeight of the report.

The size of each group text object is all right, but, taken together, they exceedthe Page Height.

Increase the Page Height on the Report Screen, or reduce the size of one ormore texts belonging to this group.

REP–26454 Matrix group ’<group name>’ does not fit within the Height of the report.

The size of each matrix group text is all right, but, taken together, they exceedthe Page Height.

Increase the Page Height on the Report Screen, or reduce the size of one ormore texts belonging to this matrix group.

REP–26455 Matrix group ’<group name>’ does not fit within the Width of the report.

The size of each matrix group text is all right, but, taken together, they exceedthe Page Width.

Increase the Page Width on the Report Screen, or reduce the size of one or moretexts belonging to this matrix group.

REP–26456 A matrix report cannot have multiple panels.

You defined more than one panel for this matrix report.

Delete the extra panels.

REP–26457 The matrix does not fit between the margins of the report.

The Page Header and Footer plus the Report Header and Footer exceed theReport Height or the Report Width, or the top margin plus the bottom marginequals the Report Height on the Report Screen.

Decrease the margins or increase the page size on the Text Screen, or decreasethe size of the matrix.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26458 This report does not fit between the page margins.

The page margins exceed the height and/or width of the report.

Decrease the margins or increase the page size on the Text Screen, or decreasethe size of other text objects.

REP–26459 The Report Header or Footer does not fit between the margins of the report.

These text objects are too large, spanning beyond the report’s margins.


REP–26460 The Title Page does not fit between the margins of the report.

The Title Page is too large, spanning beyond the report’s margins.


REP–26461 The Trailer Page does not fit between the margins of the report.

The Trailer Page is too large, spanning beyond the report’s margins.


REP–26462 The Page Header does not fit between the margins of the report.

The Page Header is too large, spanning beyond the report’s margins.


REP–26463 The Page Footer does not fit between the margins of the report.

The Page Footer is too large, spanning beyond the report’s margins.


REP–26464 The Report Header does not fit between the margins of the report.

The Report Header is too large, spanning beyond the report’s margins.


Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26465 The Report Footer does not fit between the margins of the report.

The Report Footer is too large, spanning beyond the report’s margins.


REP–26466 The Header of group ’<group name>’ does not fit between the margins ofthe report.

This group header is too large, spanning beyond the report’s margins.


REP–26467 The Column Heading of group ’<group name>’ does not fit between themargins of the report.

This column heading is too large, spanning beyond the report’s margins.


REP–26468 The Body of group ’<group name>’ does not fit between the margins of thereport.

This group body is too large, spanning beyond the report’s margins.


REP–26469 The Footer of group ’<group name>’ does not fit between the margins of thereport.

This group footer is too large, spanning beyond the report’s margins.


REP–26470 Abnormal condition: Invalid frequency group for text ’<text screen>’.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26471 Summary ’<summary name>’ on panel ’<panel number>’ extends beyondthe left margin of group ’<group name>’.

The width of this summary is greater than the width between the right and leftmargins of the group. Since this summary is either center– or right–justified,SQL*ReportWriter would encounter the left margin while printing it.

Decrease the margins of that panel or increase the group’s margin, or decreasethe summary’s width.

REP–26472 Summary ’<summary name>’ on panel ’<panel number>’ extends beyondthe right margin of group ’<group name>’.

The width of this summary is greater than the width between the right and leftmargins of the group. Since this summary is either center– or left–justified,SQL*ReportWriter would encounter the right margin while printing it.

Decrease the margins of that panel or increase the group’s margin, or decreasethe summary’s width.

REP–26473 Abnormal condition: The Align setting for a field is not ’Left’, ’Right’,’Center’, ’Wrap’, or ’Variable’.



REP–26474 Query ’<query name>’ cannot have more than one parent because this is nota matrix report.

You defined a query structure where one query has two parent queries.However, none of the groups are matrix groups.

Make Parent Query 2 blank for the query identified in the error message, ormake this a matrix report.

REP–26475 Text ’<text screen>’ cannot contain a &CR because it has no fields withvariable Alignment.

Carriage returns (created by embedding &CR in the text) are only allowed intext objects that contain at least one field with an Align setting of Variable.

Use a soft return (created by pressing the Return key) to achieve the effect of ahard return, or change the Align setting for one of the fields to Variable.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26476 Query ’<query name>’ cannot reference Field ’<field name>’ because thefield is not reset at a group whose query is a parent of ’<group name>.

A field that is referenced in a query must have a Reset Group at, or above, thegroup that is created by the query.

Press [List] and select a Reset Group for the field you wish to reference at orabove the group created by the query.

REP–26477 Query ’<query name>’ cannot reference Summary ’<summary name>’because the summary is not reset at a group whose query is a parent of’<group name>.

A summary that is referenced in a query must have a Reset Group at, or above,the group that is created by the query.

Use the list of values to select a Reset Group for the summary you wish toreference that is at, or above, the group that is created by the query.

REP–26478 Field ’<field name>’ cannot contain a compute function because its Source isa user exit.

A Computed Value (Function) can not be performed on a user exit.

Either compute the function you wish in your user exit, or create a Summaryon a field that has a Source of a user exit.

REP–26479 Query ’<query name>’ cannot reference a Field (<field name>) that belongsto a group in or after the group associated with the query.

You cannot reference a field in a query if the field belongs in, below, or to theright of the group created by the query.

Add the field that you want to reference to a query that creates a group above,or to the left of the group that is created by the query you want to add thereference to.

REP–26480 Query ’<query name>’ cannot reference Summary <summary name> whoseField belongs to a group in or after the group associated with the query.

You cannot reference a summary in a query if the field belongs in, below, or tothe right of the group created by the query.

Add the field that you want to reference to a query that creates a group aboveor to the left of the group that is created by the query you want to add thereference to.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26481 Query ’<query name>’ cannot reference a Field (<field name>) that resets atPAGE.

You cannot reference a field in a query if the field has a Reset Group at PAGE.

Press [List] and select a Reset Group that is not PAGE.

REP–26482 Query ’<query name>’ cannot reference a Summary (’<summary name>’)that resets at PAGE.

You cannot reference a summary that has a Reset Group of PAGE in a query.

Use the list of values to select a Reset Group that is not PAGE.

REP–26483 Query ’<query name>’ cannot reference a Field (’<field name>’) with Sourceof &PAGE or &NUM_PAGES.

You tried to reference a field in a query that has a Source of &PAGE or&NUM_PAGES.

Press [List] and select a Source that is not &PAGE or &NUM_PAGES.

REP–26484 Matrix query ’<query name>’ cannot reference a Field or Summary becauseit is not the cell group query.

You can only reference fields or summaries in a query if the query’s defaultgroup has a Print Direction of Crosstab.

Add the field or summary you wish to reference to the Query that has a defaultgroup with a Print Direction of Crosstab.

REP–26485 Query ’<query name>’ cannot have a parent query with no associated group.

You created a parent–child relationship between two queries on the QueryScreen and then removed the group associated with the parent query on theGroup Screen.

Create a group on the Group Screen for the parent query and associate it withthe query.

REP–26486 Field ’<field name>’ cannot reset at Page and be referenced in variablelength text object ’<text screen>’.

You set the Reset Group for the computed field to PAGE, but the computedfield is set to print in a text object that contains a field or summary with a Wrapor Variable alignment.

Create a summary of the field and place it in the Page Header or Page Footer ofthe report.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26487 Summary ’<summary name>’ cannot reset at Page and be referenced invariable length text object ’<text screen>’.

You set the Reset Group for the summary field to PAGE, but the summary is setto print in a text object that contains a field or summary field with a Wrap orVariable alignment.

Create a summary of the summary field and place it in the Page Header orPage Footer of the report.

REP–26488 Source of field ’<field name>’ cannot contain a ’#’ without a user exit name.

You did not include the name of the user exit after the ’#’ sign when you triedto create the user exit.

Specify a valid user exit name after the ’#’ in the Source.

REP–26489 Field ’<field name>’ cannot be printed at a higher group.

A field cannot print in a higher group because it could possibly have multiplevalues, and SQL*ReportWriter would not know which one to print. Exceptionsinclude calculated fields that would have a single discrete value if printed inthe higher group.

Delete the field references on the Text Screen from the group texts that arehigher than the field’s own group.

REP–26490 Field ’<field name>’ cannot reset at a lower level that its print level.

The calculated field appears in a text object that is higher than the field’s ResetGroup. It does not make sense for the calculated field’s accumulator to resetmore often than the field actually prints.

Reference this calculated field in a text object that is at the same level or lowerthan the Reset Group.

REP–26491 Field ’<field name>’ cannot reset at a lower level than its logical group.

The calculated field’s Reset Group is lower than the group that the field belongsto.

Make the Reset Group the same level or higher than the field’s group.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26492 Field ’<field name>’ cannot reset at a lower or equal level than its printlevel.

The calculated field appears in a text object that is higher or at the same level asthe field’s Reset Group.

Reference this calculated field in a text object that is lower than the ResetGroup.

REP–26493 Field ’<field name>’ cannot reset at a lower or equal level than its logicalgroup.

The calculated field’s Reset Group is lower or at the same level as the groupthat the field belongs to.

Make the Reset Group higher than the field’s group.

REP–26405 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Report table.



REP–26406 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Group table.



REP–26407 Abnormal condition: ORACLE error occurred while queryingSQL*ReportWriter’s Query table.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26408 The columns in query ’<query name>’ are not currently available.

Your query defines a SELECT Statement that uses proper SQL syntax, but itreferences columns that no longer exist in the database. The columns existedwhen SQL*ReportWriter initially validated the SELECT Statement, but they areno longer accessible.

First confirm that you are logged on to the correct database. Then check yourdatabase tables (by pressing [List]), and make sure the table(s) and/or view(s)referenced in the FROM clause are still available. If they are, make sure thecolumn definitions are still the same. You can also modify the SELECTStatement, if appropriate.

REP–26409 Abnormal condition: Error describing query ’<query name>.



REP–26494 Summary ’<summary name>’ cannot be printed at a higher group.

The summary appears in a text object that is higher than that allowed.

Reference this summary in a lower group.

REP–26495 Summary ’<summary name>’ cannot reset at a lower level that its print level.

This summary appears in a text object that is higher or at the same level as thesummary’s Reset Group.

Reference this summary in a lower group, or make its Reset Group higher.

REP–26496 Summary ’<summary name>’ cannot reset at a lower level than its logicalgroup.

The summary’s Reset Group is lower than the group that the field beingsummarized belongs to.


REP–26497 Summary ’<summary name>’ cannot reset at a lower or equal level than itsprint level.

This summary appears in a text object that is higher than the summary’s ResetGroup.

Reference this summary in a lower text object, or make its Reset Group higher.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26498 Summary ’<summary name>’ cannot reset at a lower or equal level than itslogical group.

The summary’s Reset Group is lower or at the same level as the group that thefield being summarized belongs to.


REP–26499 The Source and the group for field ’<field name>’ cannot belong to queriesin different paths.

There is an inconsistency between the Source column for this field and thefield’s group. The field’s Source column must be from a query that is in thesame path (of the query structure) as the field. The field’s path is determinedby the field’s group. In turn, the group’s path is determined by the group’squery.

Either change the Source column or the Group for the field on Field Screen 1.Make sure the Source and Group are from the same path of the query structure.

REP–26500 Field ’<field name>’ references an unknown Source.

The Source for this field is currently undefined. This might result from adatabase link being missing, the underlying table definition changing, or anyother reason that prevents SQL*ReportWriter from locating the Sourceoriginally referenced.

Either define this field in a valid way, or delete the field from your reportdefinition.

REP–26501 Field ’<field name>’ references a Source whose query, ’<query name>, hasno groups.

A field’s Source must contain a group name that belongs to a query. Youdeleted a group that belonged to a query, but that group name is still in theSource column of the field in the error message.

Delete the field’s Source, and select a valid Source from the list of values.

REP–26502 Field, summary, or parameter referenced by query ’<query name>’ no longerexists.

You deleted a field, summary, or parameter and you did not remove it from thequery.

Delete the field, summary, or parameter from the query named in the errormessage. If you do not know which reference needs to be deleted, look at thefields, summaries, and parameters that are found on their respective screens.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26503 Abnormal condition: incorrect source information for field ’<field name>’.



REP–26504 Group ’<group name>’ references an unknown query.

The query identified for this group is undefined.

Move to this Group Screen and identify a valid query for the group, then moveto the Query Screen and add or rename an appropriate query.

REP–26505 Field ’<field name>’ references an unknown query.

The query associated with the Source column on the Field Screen for this fieldis not defined.

Move to the Field Screen and identify a valid Source, or move to the QueryScreen and add, edit, or rename an appropriate query.

REP–26506 Field ’<field name>’ references an unknown group.

The group associated with the field on the Field Screen is not defined.

Move to the Field Screen and identify a valid group, or move to the GroupScreen and add or rename an appropriate group.

REP–26507 Field ’<field name>’ references an unknown reset group.

The reset group associated with the computed field on the Field Screen is notdefined.

Move to the Field Screen and identify a valid reset group, or move to the GroupScreen and add or rename an appropriate group.

REP–26508 Summary ’<summary name>’ references an unknown field.

The field associated with the summary on the Summary Screen is not defined.

Move to the Summary Screen and identify a valid field, or move to the FieldScreen and add or rename an appropriate field.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26509 Summary ’<summary name>’ references an unknown print group.

The print group associated with the summary on the Summary Screen is notdefined.

Move to the Summary Screen and identify a valid print group, or move to theGroup Screen and add or rename an appropriate group.

REP–26510 Summary ’<summary name>’ references an unknown reset group.

The reset group associated with the summary on the Summary Screen is notdefined.

Move to the Summary Screen and identify a valid reset group, or move to theGroup Screen and add or rename an appropriate group.

REP–26511 Query ’<query name>’ references an unknown parent query.

The query associated with the parent query on the Query Screen is not defined.

Identify a valid query for the parent query, or add or rename a query thatmatches the name in Parent Query.

REP–26512 Text ’<text screen>’ references an unknown frequency group.

The group identified in Frequency on the Text Screen for this text object is notdefined on the Group Screen.

Move to Frequency on the Text Screen and identify a valid frequency group, ormove the Group Screen and add or rename an appropriate group.

REP–26513 Parent–Child Relationship ’<query name>’ references an unknown item.

The item referenced by the foreign key is not defined.

Reference a valid item.

REP–26514 Parent–Child Relationship ’<query name>’ references an unknown parent.

The parent referenced by the foreign key is not defined.

Reference a valid parent. To do so, press [List] while the cursor is in the Parentcolumn of the Foreign key in question, and select a parent from the list.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26515 Parent–Child Relationship ’<query name>’ has an invalid child columnposition value.

The child column position value referenced by the foreign key is not valid.

Reference a valid value.

REP–26516 Parent–Child Relationship ’<query name>’ has an invalid parent columnposition value.

The parent column position value referenced by the foreign key is not valid.

Reference a valid value.

REP–26517 Abnormal condition: Group order for group ’<group name>’ outside of avalid range.



REP–26518 Abnormal condition: System parameter ’destype’ is not included.



REP–26519 Abnormal condition: System parameter ’desname’ is not included.



REP–26520 Abnormal condition: System parameter ’desformat’ is not included.



REP–26521 Abnormal condition: System parameter ’copies’ is not included.



REP–26522 Abnormal condition: SQL*ReportWriter objects have duplicate item ID’s.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26523 Summary ’<summary name>’ cannot reference a field with Data Type ofPRT.

You tried to create a summary of a field that has a Data Type of PRT.

Press [List] and select a field from the list of valid values.

REP–26524 Summary ’<summary name>’ cannot reference a field with Source of&DATE, &PAGE, or &NUM_PAGES.

You tried to create a Summary of a field that has a Source of &DATE, &PAGE,or &NUM_PAGES.

Press [List] and select a field from the list of valid values.

REP–26525 Abnormal condition: System parameter ’currency’ is not included.



REP–26526 Abnormal condition: System parameter ’thousands’ is not included.



REP–26527 Abnormal condition: System parameter ’decimal’ is not included.



REP–26528 Summary ’<summary name>’ cannot compute Percent, Sum, or Average of acharacter or date field.

You tried to compute a summary of a Character or Date field, which is invalid.

You can compute a summary only for Number fields.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26529 Invalid specification for a matrix report.

You used some—but not all—of the conventions for defining a matrix report.You must use all, or none of the conventions.

If any group has an X in Matrix Group, then the report must have exactly 3groups (each from a different query), and all 3 groups must have an X in MatrixGroup. One group must have DOWN for Print Direction, another group musthave ACROSS and the third group must have CROSSTAB. If you do not wantthis to be a matrix report, remove the X’s from Matrix Group for all groups,and either change the Print Direction of the CROSSTAB group or delete it.

REP–26530 This report includes both matrix and non–matrix groups.

Your report has at least one group where Matrix Group does not have an X, orat least one Print Direction of DOWN, ACROSS, or CROSSTAB is specified, butall three Print Directions are specified.

If any group has an X in Matrix Group, then the report must have exactly 3groups (each from a different query), and all 3 groups must have an X in MatrixGroup. One group must have DOWN for Print Direction, another group musthave ACROSS and the third group must have CROSSTAB.

REP–26531 Abnormal condition: Invalid Print Direction for group ’<group name>’.



REP–26532 The Print Direction for group ’<group name>’ and another group isinconsistent.

You have defined at least one DOWN (or DOWN/ACROSS) group and oneACROSS (or ACROSS/DOWN) group in this report.

Make sure the Print Direction for all the groups in your report is DOWN (orDOWN/ACROSS) or all the groups are ACROSS (or ACROSS/DOWN).

REP–26533 Abnormal condition: error message ’<message number>’ cannot begenerated.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26534 Wrap fields and variable fields are not allowed in matrix, across, andacross/down reports.

One or more fields in the report has an Align setting of Wrap or Variable.

Change the Align setting for the Wrap or Variable field(s) by pressing [List] andselecting one of the settings, or change the Print Direction for the group(s), bypressing [List] in the Print Direction entry field (on Group Screen One) andselecting DOWN or DOWN/ACROSS for the setting.

REP–26535 Wrap fields and variable fields are not allowed in multi–panel reports.

You created a multi–panel report that contains a Wrap and/or Variable field.

Choose another Align setting for the Wrap or Variable field(s) (press [List] to seeother Align settings that are available), or modify the text panels so that there isonly one panel for each text Object and Type.

REP–26536 Groups in a matrix report must reference unique queries.

You specified the same query for at least two groups in a matrix report. Amatrix report must have three queries and three groups, and each group mustassigned to a unique query.

Change the Query assignment for the groups so that all three assignments areunique.

REP–26537 No report name specified on the command line.

You invoked the R25MREP executable but did not specify any Version 1.1reports to convert to Version 2.5.

Re–issue the command, remembering to specify the reports you wish to convertusing the SOURCE keyword.

REP–26538 No user id specified on the command line.

You invoked the R25MREP executable but did not specify a username in thecommand string.

Re–issue the command, remembering to specify a username and passwordusing the USERID keyword.

REP–26539 Invalid keyword: ’<string>’.

You invoked the R25MREP executable with an invalid keyword.

Re–issue the command, specifying valid keywords.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26540 Abnormal condition: Internal error while reading from SQL*ReportWriter’sV1.1 Rexfile.



REP–26541 Cannot create loadfile ’<loadfile name>’.



REP–26542 Cannot open loadfile ’<loadfile name>’.

The SQL*ReportWriter V1.1 .rex file you specified could not be found.

Specify the correct directory path and filename of the .rex file containingSQL*ReportWriter V1.1 reports you wish to migrate to Oracle Reports.

REP–26543 Error while closing loadfile.



REP–26544 Loadfile ’<loadfile name>’ is currently locked by another user.

You attempted to migrate report(s) stored in a .rex file, but the .rex file youspecified is currently locked by another user.

Re–try the operation once the user has unlocked the .rex file.

REP–26545 Abnormal condition: Internal error on system initialization.



REP–26546 This report is currently locked by another user.

You attempted to migrate a report that is currently being modified by anotheruser.

Re–try the operation once the user has saved and closed the report.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26547 Unexpected Column Name encountered in srw_tables.



REP–26548 Unexpected error processing srw_fkey data in the export file.



REP–26549 Unexpected error processing srw_field data in the export file.



REP–26550 Unexpected error processing srw_param data in the export file.



REP–26551 Unexpected error processing srw_query data in the export file.



REP–26552 Unexpected error processing expanded query data in the export file.



REP–26553 Unexpected error processing srw_report data in the export file.



REP–26554 Unexpected error processing srw_ste data in the export file.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26555 Unexpected error processing srw_summary data in the export file.



REP–26556 Unexpected error processing export file.



REP–26650 Error generating error message ’<string>’.



REP–26750 Not enough memory available. ’<Requestor>’ requested ’<number>’ byteson allocate.



REP–26751 Not enough memory available. ’<Requestor>’ requested ’<number>’ byteson reallocate.



REP–26752 Unanticipated ORACLE error occurred: ’<component>’ ’<number>’ Routine:’<routine name>



REP–26753 Unanticipated internal error occurred: ’<component>’ Routine: ’<routinename>’.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26754 The SQL Statement you have entered is invalid ’<value>’ ’<value>’’<value>’.

You tried to migrate a report containing an invalid SQL statement.

Open the report, correct the SQL statement, save the report, and re–try theoperation.

REP–26755 Unable to display columns due to ORACLE error:



REP–26756 ’<value>’ ’<value>’ not found in internal tables.

The SQL*ReportWriter tables could not be found in the current database.

Contact your system or database administrator to install or locate theSQL*ReportWriter tables.

REP–26757 Parameter ’<parameter name>’ has the same name as another object.

One of your reports contains a user–defined parameter with the same name asa query, field, summary, or other report object.

Rename the parameter and re–try the operation.

REP–26758 Parameter ’<parameter name>’ has the same name as a command linekeyword.

You attempted to define a parameter with the same name as an existing systemparameter (e.g., DESTYPE, CURRENCY).

Choose a new name for your parameter.

REP–26760 Parameter name lengths cannot exceed 27:

Your report contains a parameter whose name exceeds 27 characters.

Make sure the names of your parameters do not exceed 27 characters.

REP–26761 Comment not properly ended.

Your report includes a query containing comments that are not properly ended.

Edit the query, ensuring that you end all comments with the appropriatesymbols. For more information, see the ORACLE7 Server SQL LanguageReference Manual.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–26765 ERROR: This report does not contain the data table information. A .rep filecannot be generated.



REP–26767 There may already be reports with the same names in the Version 2.0 tables.

You attempted to migrate one or more reports stored in the database using thesame name as a report that already exists in the database.

Rename the reports you wish to migrate, or assign them names that aredifferent from existing reports.

REP–26770 Moverep Error: No 1.1 report specified to move.

You invoked the R25MREP executable but did not specify any Version 1.1reports to convert to Version 2.5.

Re–issue the command, remembering to specify the reports to convert.

REP–26771 No reports with name ’<report name>’ found in database.

You specified a report not found in the database.

Determine if you are connected to the correct database and specifying thecorrect name. Re–issue the command.

REP–26790 A fatal error occurred while creating a new report for ’<report name>’.


Check that your NLS_LANG and ORACLE_HOME environment variables areset to the correct values. (For more information, see your CDE2 InstallationGuide. Also see “National Language Support” in Appendix C of the ReportsReference Manual.) Otherwise, see “Abnormal Conditions” on page 1 – 3.

REP–26791 Warning: The name ’<report name>’ will be truncated to <integer>characters.

You attempted to migrate a report, and R25MREP found a report, column,group, or field name that was not unique and must be changed by shorteningthe name to a valid length. Note that this could possibly generate an invalidname.

Change the name in the original SQL*ReportWriter report to less than 25characters, or edit the converted Oracle Reports report after it is converted.

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–32600 Unexpected error. Aborting.



REP–32601 Report already exists in NX file.

You tried to overwrite an existing translation file.

Choose another name for the translation file.

REP–32602 Cannot initialize Reports system.



REP–32603 Cannot initialize VGS system.



REP–32604 Fatal error loading report ’<report name>’. Check version.

The specified report cannot be loaded.

Make sure you’re opening the correct version of the report.

REP–32605 Cannot open report file for reading.

Report file is unreadable.

Check the read permission of the report file.

REP–32606 Cannot open ’<translation file>’ file for reading.

The specified file cannot be opened.

Make sure the file exists and is readable.

REP–32607 NX Tree does not exist.



Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–32608 Translations for that language do not exist.

The Translation Manager cannot translate into the given target language.

Make sure the target language is supported.

REP–32609 This is not an Oracle Reports tree.



REP–32610 Source data file ’<file name>’ does not match.

The translation file you’re merging into the report was not created from theselected report.

Merge the translation file into the original report.

REP–32612 Cannot merge for Base language.

You are trying to merge the untranslated strings back into the original report.

Translate the strings in the translation file and try again.

REP–32613 Cannot find matching VGS string in NX file.



REP–32614 Successfully merged strings for language ’<language name>’.

Operation was completed with no errors.


REP–32615 Merge operation failed.

The merge operation encountered errors.

Check the log file for more information.

REP–32616 Cannot find translations in NX file.

The translation file does not contain translated strings.

Make sure you’re using the correct translation file for the given report.

Cause

Action

Cause

Action

Cause

Action

Cause

Action


REP–32617 NX file is corrupt!



REP–32618 Cannot open NX file for reading.

Translation file cannot be opened.

Make sure the file exists and is readable.

REP–32750 Unable to unpack the data of image ’<image name>’. The image has beenremoved.

The image data is corrupted.

Import the image again.

REP–32751 Warning: Some text segments are missing.

Text segments cannot be found for some boilerplate text. The report may becorrupted.

Check the boilerplate text objects in the report. Remove suspicious ones andcreate replacements for them.

Reader’s Comment Form

Name of Document: Reports Messages and Codes ManualPart No. A32490–1

Oracle Corporation welcomes your comments and suggestions on the quality and usefulnessof this publication. Your input is an important part of the information used for revision.

• Did you find any errors?

• Is the information clearly presented?

• Do you need more information? If so, where?

• Are the examples correct? Do you need more examples?

• What features did you like most about this manual?

If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,and page number below:

Please send your comments to:

Oracle Reports Documentation ManagerOracle Corporation500 Oracle Parkway, Box 659412Redwood Shores, CA 94065–5028(415) 506–7000(415) 506–7200 (FAX)

If you would like a reply, please give your name, address, and telephone number below:

Thank you for helping us improve our documentation.

��

A32490–1

��

��

oracle reports messages and codes manual

Documents