Oracle Reports Messages and Codes Manual

Reports Messages and Codes Manual
Release 2.5

Release 2.5
Part No. A324901
Oracle Reportst Messages and Codes Manual, Release 2.5 Part No. A324901, April 1995 Copyright E Oracle Corporation 1984, 1988, 1995 All rights reserved. Printed in the U.S.A. Contributing Authors: Anne Bers and Lori Ann White Contributors: Per Brondum, Karen DenchfieldMasterson, Alex Hsieh, YuehHong Lin, Ashok Natesan, Boris Protasov, Greg Rogalski, Frank Rovitto, Yuri Sharonin, Jerry Sherman, Gene Sohn, Atul Suklikar, Marco Tilli, Simon Wong This software was not developed for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It is the customers responsibility to take all appropriate measures to ensure the safe use of such applications if the programs are used for such purposes. This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable: Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.2277013, 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 not within the Department of Defense, then it is delivered with Restricted Rights, as defined in FAR 52.22714, Rights in Data General, including Alternate III (June 1987). The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is errorfree. ORACLE, Pro*COBOL, Pro*FORTRAN, Pro*Pascal, Pro*PL/I, SQL*Connect, SQL*Net, SQL*Plus, and SQL*ReportWriter are registered trademarks of Oracle Corporation. Developer/2000, ORACLE7, Oracle Book, Oracle Forms, Oracle Graphics, Oracle Help, Oracle*Mail, Oracle Reports, PL/SQL, and Pro*C are trademarks of Oracle Corporation. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Read This First

he Reports Messages and Codes Manual is one of six documents in the 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 product comments
Before you use this book, we recommend that you become familiar with the Building Reports Manual.
Read This First
Audience
The information in this manual is intended for application developers who want to create reports. Readers should have a working knowledge 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 several programming languages. Sometimes, knowledge of these other products is necessary. The following map is provided to help you determine any additional documentation you may need.
ii
Oracle Reports Documentation
The following books are included in the Oracle Reports documentation set:

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 Reports Version 2.5. Building Reports Manual Version 2.5, Part No. A32488, contains a tutorial and a rich discussion of Oracle Reports concepts as well as many example reports. Reports Reference Manual Version 2.5, Part No. A32489, contains detailed reference information about all aspects of Oracle Reports. It is intended primarily to answer specific questions that 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 action descriptions. Reports Runtime Manual, Graphical and Character Mode Interfaces, Version 2.5, Part No. A32493, contains information for end users (i.e., those who only run reports). It contains a tutorial and reference information about the Oracle Reports runtime executable. Reports Migration Manual Version 2.5, Part No. A32491, contains all information that you need to convert SQL*ReportWriter Version 1.1 reports and printer definitions to Oracle Reports Version 2.5. The online help system consists of the Reports Reference Manual, Reports Messages and Codes Manual, Reports Runtime Manual, and procedural information in online format.
Each Oracle Reports manual is also shipped as an Oracle Book document. For the names and locations of the document files, see your Developer/2000 Installation Guide.
Related Information
As an application designer using Oracle Reports Version 2.5, you may need to refer to some or all of the documents listed below. Please see the document in question for information on its specific purpose and usage.
Developer/2000 Installation Guide or System Release Bulletin. This document is different for each hardware/software platform. Ask your sales representative for the appropriate part number.
Read This First
iii
ORACLE7 Server Documentation Set, Part No. 503070 ORACLE7 Server Documentation Set V7.1, Part No. A12383 Oracle Network Products Messages Manual, Part No. A16263 MultiProtocol Interchange Administrators Guide, Part No. A10157 PL/SQL Users Guide and Reference, Version 1.0, Part No. 800V1.0 PL/SQL Users Guide and Reference, Version 2.0, Part No. 80020 Programmers 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 Administrators Guide, Part No. A16264
How to Use this Book

The Reports Messages and Codes Manual provides comprehensive information about Oracle Reports messages and how to handle them. Before you use this book, we recommend that you read the first three chapters of the Building Reports Manual. This book contains the following chapters:
Chapter 1, Using Messages, which explains how to identify the origin of messages (i.e., whether they arise from an Oracle Reports error, an ORACLE server error, a component error, or an error specific to your platform) and how to look up causes and actions for errors. It also covers how to contact Customer Support. Chapter 2, Oracle Reports Messages, a numerical listing of all Oracle Reports error messages, including causes for the raising of each message and actions you can take to resolve them..
iv
Notational Conventions
You should be familiar with the notational conventions listed in the following table. Convention File>New>Report Data/Selection:Repeat
Font Change
Explanation Indicates a selection of submenu item Report from the New submenu of the File menu. Indicates a selection of Repeat from the Data/Selection tab of a property sheet. Indicates text to be entered exactly as shown. Indicates command, column, parameter, field, boilerplate, and anchor names. Indicates table, menu, query, group, frame, and repeating frame names, as well as property sheet names. Indicates items within a menu, buttons, or tabs on a property sheet. Indicates options for Oracle Reports settings.
UPPERCASE Initial Caps
Bold Italics
Read This First
Your Comments Are Welcome

We value and appreciate your comments as an Oracle user. As we write, revise, and evaluate our work, your opinions are the most important input we receive. At the back of this manual is a Readers Comment Form. We encourage you to use this form to tell us both what you like and dislike about this (or other) Oracle manuals. If the form is gone, or you would like to contact us, please use the following addresses and phone numbers. For documentation questions/comments, contact: Oracle Reports Documentation Manager Oracle Corporation 500 Oracle Parkway Box 659412 Redwood Shores, California 940655028 (415) 5067000 (415) 5067200 (fax)
For product questions/comments, contact: Oracle Reports Product Manager Oracle Corporation 500 Oracle Parkway Box 659412 Redwood Shores, California 940655028 (415) 5067000 (415) 5067200 (fax)
vi
Contents
Chapter 1
Using Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coping with Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Information about Messages . . . . . . . . . . . . . . . . . . . . Looking Up Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ORACLE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abnormal Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calling Oracle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Reports Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . Using this Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 12 12 12 13 13 14 14 14 15 15 16
Chapter 2
Oracle Reports Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1 Oracle Reports Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2
Contents
vii
viii
CHAPTER
Using Messages
his chapter explains how to use messages issued by Oracle Reports. It covers the following topics:

coping with messages 1 2 ORACLE messages 1 3 abnormal conditions 1 3 calling Oracle customer support 1 4
Using Messages
11
Coping with Messages

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

finding information about errors looking up messages
Finding Information about Messages
Messages that may appear when using Oracle Corporation programs are documented in a number of manuals: Oracle Reports messages ORACLE messages Productspecific messages These messages are specific to Oracle Reports and are documented in this book. These messages are detected by ORACLE, and they can appear while you are running nearly any Oracle program. These messages are specific to one product, and are therefore documented in the manuals for that product. For example, you might get an Oracle*Mail message, which is documented in the Oracle*Mail documentation. These messages are specific to one operating system. A range of message numbers has been reserved for each operating system. For example, the range 7500 7999 is for DEC VAX/VMS messages. For information on these messages, see your Developer/2000 Installation Guide.
Systemspecific messages
Looking Up Messages
The prefix of each message tells you where to find information about the message. For example, Oracle Reports messages have the prefix REP. RDBMS messages have the prefix ORA. If you are using Oracle Reports 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 either check this manual or select Help in the message dialog to display an online version of this manual, positioned at the correct message. If the message is not an Oracle Reportsspecific message, look at the message prefix to determine which product/component generated the message. Then look at the message code number to find that specific message description. Messages are listed in order by the code number.
12
Message Prefixes
The following table lists the prefixes of messages that you may encounter: Prefix REP ORA DBA EXP IMP LCC ORA PCC PLS RTL SQL*Loader VGS PDE Type of Message Oracle Reports message ORACLE messages (includes PL/SQL messages) SQL*DBA message Export Utility message Import Utility message Parameter file message Generic ORACLE message Precompiler Compiletime message PL/SQL message Precompiler Runtime message SQL*Loader message Oracle internal graphics system Oracle internal PL/SQL Development Environment
ORACLE Messages
When using Oracle Reports, you might get an ORACLE message (i.e., a message prefixed with ORA). For more information, see the ORACLE7 Server Messages and Codes Manual.
Abnormal Conditions
Sometimes you may encounter an error that is known as an abnormal condition. These are errors for which the exact cause is not clear. The following sections describe the probable causes of abnormal conditions and the actions you can take to solve them.
Using Messages
13
Cause
Abnormal conditions may arise from one of the following causes:
Someone has done something that prevented Oracle Reports from completing the requested task. For example, if someone bypassed the user interface and changed data in Oracle Reports tables directly, they might have entered an invalid value in these tables which has prevented Oracle Reports from completing the requested task. A bug in Oracle Reports prevented the requested task from completing.
Action
You should first contact your DBA and/or system administrator to determine if the message was caused by something other than Oracle Reports. If you determine that the message was not the result of user error or a system problem, then you should take the following steps: 1. 2. Write down the message number and its text. Write down the circumstances that lead up to the message. Try to recall the actions you took, the objects involved (if any), and the exact sequence of keys that you pressed prior to the message. Contact Oracle Customer Support. See Calling Oracle Customer Support below for more information.
3.
Calling Oracle Customer Support

Some messages recommend calling Oracle Customer Support to report the problem. When you call Customer Support, please have the following information at hand: 1. 2. The hardware, operating system, and release number of the operating system on which Oracle Reports is running. The complete version number of Oracle Reports including revision number and port release number, if any. For example, V2.0.05 or V2.0.13. All products (with version numbers) in use when the message was displayed (ORACLE V6.0, SQL*Net V2.0, or SQL*Forms V3.0, for example). If you encountered one or more messages, the exact code numbers and message texts, in the order they appeared.
3.
4.
14
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 overall operations. 4 = Problem circumvented by customer. Minimal effect, if any, on operations.
6. 7.
A description of the problem, including any unusual conditions. Also, you will be expected to give your:

name companys name companys ORACLE Support ID Number phone number
Oracle Reports Message Descriptions

This section includes the following:

conventions used in this section startup messages Note: GUI Oracle Reports will always attempt to display messages in an alert. If Oracle Reports cannot bring up an alert (e.g., the problem occurred during startup), then the message will be sent to your standard SYSOUT.
Using this Section
Each description contains the message number and text as well as the following: Cause Action Is a description of the possible causes of the error. Is a description of the possible actions you might take to resolve the error.
Using Messages
15
Recognizing Embedded Variables
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 angle brackets <>. For example, the message:
REP1232: Matrix X_Cross has an invalid source frame.
would appear in this section as:

REP1232 frame. Matrix <matrix name> has an invalid source
Startup Messages
When an error is encountered and its message cannot be obtained from the message file, then Oracle Reports will display one of the following messages:

Error raised but unable to open message file. Still attempting to report error.
After these messages, Oracle Reports displays a hardcoded message. Hardcoded Messages Following is a list of the hardcoded messages:
File not found: <filename> <filename> Error opening file:
ORACLE error number: <ORACLE error number> <ORACLE description of the error> Bad argument in command list. No runfile was specified. Error opening specified terminal description file: <filename> Unable to get message for error <error number> <Additional information: <information>> Argument was: <argument>
There is one other time a hardcoded message will appear. When an error occurs and for some reason the message subsystem does not execute 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.
16
Action
When you receive a startup message, you should take the following steps: 1. Contact your DBA. The DBA should be able to verify whether the product has been installed correctly. Refer to your Developer/2000 Installation Guide. If the product was not installed correctly, the DBA should correct the problem. If the product has been installed correctly and the error persists, you should contact Oracle Customer Support for assistance. For more information, see Calling Oracle Customer Support on page 1 4.
2.
Using Messages
17
18
CHAPTER
Oracle Reports Messages

his chapter lists messages issued by Oracle Reports. Each message code follows the format REPnnnnn, where nnnnn is an integer. Messages specific to an operating system or an Oracle product are not listed in this chapter, although the message code may be listed with a reference to another Oracle document. In general, for more information regarding the conditions that generate messages in this chapter, see the Reports Reference Manual.
21

REP0001 Cause Action REP0002 Cause Action REP0003 Cause Unable to initialize message subsystem. The file of error messages could not be opened or an internal error occurred while opening it. Contact Oracle Customer Support for assistance. Unable to retrieve string from message file. Oracle Reports could not retrieve the necessary error message or string. Contact Oracle Customer Support for assistance. Warning Unable to open global preference file. The global Oracle Reports preference file shipped with Oracle Reports could not be opened. This is just a warning, so the product will continue to run even if this occurs. The possible causes of this error include the following: Case 1: Case 2: Case 3: Action The file was not found under the specified name in the specified location. You lacked the necessary privileges to open the file. 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 appropriate directory. For more information, see your Developer/2000 Installation Guide. Or contact your DBA. If Case 2: Make sure that you have the privileges necessary to access the file. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
REP0004 Cause
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: Case 1: Case 2: The file was not found under the specified name in the specified location. You lacked the necessary privileges to open the file.
22
Case 3: Action
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 prefs.ora is located in your home directory (if your system has such a concept as home directory). If it is not, change the directory and/or filename as appropriate. If Case 2: Make sure that you have the privileges necessary to access the file. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
REP0005 Cause
Warning Syntax error at line <line number> in global preference file. One or more of the preferences in the global preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, Oracle Reports will ignore the incorrectly specified preferences. You or your DBA should edit the global preference file and ensure that all preferences are correctly specified. If they are not, make the necessary updates. Warning Syntax error at line <line number> in user preference file. One or more of the preferences in the user preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, Oracle Reports will ignore the incorrectly specified preferences. You should edit the global preference file and ensure that all preferences are correctly specified. If they are not, make the necessary updates. 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: Case 2: You lacked the necessary privileges to write the file. A system error made it impossible to write the file.
Action
REP0006 Cause
Action
REP0007 Cause
23
Action
You can take the following actions to correct this error: If Case 1: Make sure that you have the privileges necessary to write the file. If you dont, change your privileges accordingly. If Case 2: Consult your operating system documentation or contact your system administrator.
REP0008 Cause Action REP0059 Cause
Unexpected memory error while initializing preferences. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to locate resources for subcomponent <component name>. Check the 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: Case 2: Case 3: The resource file doesnt exist. The resource file is in the wrong place. The environment is not configured properly.
Action
You can take the following actions to correct this error: If Case 1: Make sure that the resource files are present. If Case 2: Make sure that the resource files are in the proper directory. If Case 3: Make sure that your environment is set correctly. On Unix, make sure that the proper environment variable is set, and on MicroSoft Windows check the file oracle.ini.
REP00060 Cause
Unable to run synchronous job concurrently with another report. You are trying to run a report initiated by another Oracle Tool (e.g., Oracle Forms) and requiring data passed from that tool, but one or more other reports are running or queued to run. Reports requiring passed data must be run immediately. Wait for all other reports currently listed in the Oracle Reports Server queue to run, then try your report again. Internal error rxmobfree: reference count is zero. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
REP0061 Cause Action
24
REP0062 Cause Action REP0063 Cause Action REP0064 Cause Action REP0065 Cause Action
Internal error rxmobnew: size mismatch. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error rxmobnew: memory manager mismatch. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error rxmobnew: type mismatch. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Virtual Memory System error. Oracle Reports has encountered a memory error. Make note of the errorspecific code and contact Oracle Customer Support. For more information, see Calling Oracle Customer Support on page 1 4. Error executing CA utility. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 not valid. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s).
REP0066 Cause Action REP0067 Cause Action
25
Invalid value for keyword STYPE. Valid options are DATABASE or REXFILE. In R25MREP, you provided an argument for the STYPE keyword that was not valid. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s). 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 not valid. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s). Invalid value for keyword DTYPE. Valid options are DATABASE, REXFILE, or RDFFILE. In R25MREP, you provided an argument for the DTYPE keyword that was not valid. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s). Unable to allocate SSL context. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to initialize NNIT interface. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Trying to run unknown product. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
REP0071 Cause Action REP0072 Cause Action REP0073 Cause Action
26
Failure to run another product using SSL. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 error encountered by the called application. Resolve the error encountered by the called application and retry the operation. Internal failure in product integration. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 documents definition. 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 not supported. Use an executable by which you integrate using multiple processes. Otherwise, Oracle Reports can only be called with batch=yes. Invalid value for keyword OVERWRITE. Valid options are YES, NO, or PROMPT. In R25CONV, you provided an argument for the OVERWRITE keyword that was not valid. Reenter the command, specifying a value of YES, NO, or PROMPT for the OVERWRITE keyword.
Action
REP0078 Cause
Action
27
REP0080 Cause Action REP0081 Cause Action REP0082 Cause
Please enter YES, NO or CANCEL. In R25CONV, you typed OVERWRITE=PROMPT on the command line, then entered a value other than YES or NO when prompted. Specify a value of YES or NO at the prompt, or CANCEL the operation. Error during file I/O operation. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error executing SCA utility. The possible causes of this error include the following: Case 1: Case 2: Your initialization file is not current. An abnormal condition.
Action
You can take the following actions to correct this error: If Case 1: Ensure that your initialization file is current. If Case 2: For information, see Abnormal Conditions on page 1 3.
Invalid value for keyword DUNIT. Valid options are CENTIMETER, CHARACTER, INCH, or POINT. In R25CONV, you entered an invalid value for the keyword DUNIT. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s). 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 in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value and the proper syntax for the keyword.
28
Invalid value for keyword FORMSIZE. Syntax is <width>x<height>. In R25CONV, you entered an invalid value for the keyword FORMSIZE. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value and the proper syntax for the keyword. DUNIT must be different than source reports unit of measurement. In R25CONV, you entered a value for the keyword DUNIT that was in the same unit of measurement as the report you wish to convert. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value and the proper syntax for the keyword. 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. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command, using a valid value for the keyword(s). 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 Settings tab of the Tools Options dialog or on the command line. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.) 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 Settings tab of the Tools Options dialog or on the command line. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.)
29
Invalid value for keyword ACCESS. Valid options are FILE and DATABASE. 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 check the online help system.) Invalid value for parameter <parameter name>. You entered an invalid value for the named parameter. For example, in the R25RUN command string, you entered a character value for a parameter with a datatype of Number. Retry the operation, specifying a valid value for the parameter. Warning Version 1.1 LANGUAGE argument not supported. Use ORACLE National Language environment variable instead. For R25DES or R25RUN, you included the LANGUAGE keyword in the command line string. Remove the LANGUAGE argument string from the command string, and set the ORACLE National Language environment variable NLS_LANG to the appropriate value. For more information, see National Language Support in Appendix C of the Reports Reference Manual. You can also check the online help system.) FORMSIZE must be 80x24 if DUNIT is Character. While using R25CONV with DUNIT=Character, you specified a parameter form size that was not equal to 80x24. The charactermode parameter form size must be 80x24. Either specify a FORMSIZE of 80x24 when DUNIT=Character, or do not specify a FORMSIZE. 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 Runtime Settings tab of the Tools Options dialog or on the command line. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.)
REP0091 Cause
Action REP0092 Cause Action
2 10
Invalid value for keyword MODE. Valid options are DEFAULT, BITMAP, or CHARACTER. You entered an invalid value for MODE. Specify DEFAULT, BITMAP, or CHARACTER either in the Runtime Settings tab of the Tools Options dialog or on the command line. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.) Invalid value for keyword TRACEMODE. Valid options are TRACE_APPEND or TRACE_REPLACE. Either you specified an invalid value for TRACEMODE, or did not specify a value for TRACEMODE, or specified keywords out of order on the command line but did not name them. Either specify Append or Replace for Trace Mode in the Trace Settings dialog or TRACE_APPEND or TRACE_REPLACE on the command line, or check the syntax of your command. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.) Report not run user cancelled in the parameter form. Your report was not executed because you selected Cancel instead of Run Report in the Runtime Parameter Form. No action is necessary. Report is aborted upon user request. You stopped a report while it was executing. No action is necessary. Unable to position file pointer in file <filename>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to read file <filename>. Oracle Reports tried to read the file shown in the message. The file could be opened but not read. Consult your operating system documentation or contact your system administrator.
REP0097 Cause
Action
2 11
REP0102 Cause
Unable to write file <filename>. Oracle Reports tried to write the file shown in the message and couldnt. The possible causes of this error include the following: Case 1: Case 2: Case 3: You lacked the necessary privileges to write the file. The file system does not have enough room for the file. A system error made it impossible to open the file.
Action
You can take the following actions to correct this error: If Case 1: Make sure that you have the privileges necessary to write the file. If you dont, change your privileges accordingly. If Case 2: Make more room by deleting unnecessary files or expanding your storage. If Case 3: Consult your operating system documentation or contact your system administrator.
Unable to close file <filename>. Oracle Reports tried to close the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to close the file. Consult your operating system documentation or contact your system administrator. Unable to delete file <filename>. Oracle Reports tried to delete the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to delete the file. Consult your operating system documentation or contact your system administrator. Unable to lock file <filename> in exclusive mode. Oracle Reports tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file. Consult your operating system documentation or contact your system administrator.
2 12
Unable to lock file <filename> in shared mode. Oracle Reports tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file. Consult your operating system documentation or contact your system administrator. Attempt to open a file with a bad name <filename>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 before the filename, or modify the REPORTS25_PATH environment variable to include the directory where the file is located. Too many files open. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to open file <filename>. Oracle Reports tried to open the file shown and couldnt. The possible causes of this error include the following: Case 1: Case 2: Case 3: The file was not found under the specified name in the specified location. You lacked the necessary privileges to open the file. A system error made it impossible to open the file.
Action
You can take the following actions to correct this error: If Case 1: Make sure the file is stored in the specified directory under the specified name. If it is not, change the directory and/or filename as appropriate. If Case 2: Make sure that you have the privileges necessary to open the file. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
2 13
Directory <directory path> is protected. You specified that Oracle Reports read from or write to a directory that you dont have permission to read from or write to. Change the permissions on the directory so that you can read from it or write to it. File <filename> is write protected. You specified that Oracle Reports write to a file that is write protectedi.e., you dont have permission to write to the file. Change the permissions of the file so that you can write to it. File <filename> is read protected. You specified that Oracle Reports read a file that is read protectedi.e., you dont have permission to read the file. Change the permissions of the file so that you can read it. File <filename> no longer exists. You specified that Oracle Reports access a file that no longer exists. Remove the call to the file, recreate the file, or specify a different file. Unable to read directory <directory path>. You most likely specified that Oracle Reports read from or write to a directory that doesnt exist. Make sure the directory you specify exists. Unable to connect to directory <directory path>. Oracle Reports could not access the specified directory for some reason. Consult your system administrator. Exit to host operating system failed. You attempted to exit out of the program and return control to the host operating system. No action is necessary.
REP0112 Cause Action REP0113 Cause Action REP0114 Cause Action REP0115 Cause Action REP0116 Cause Action REP0117 Cause Action
2 14
REP0118 Cause
Unable to create a temporary file. Oracle Reports tried to create a temporary file but couldnt do so. The possible causes of this error include the following: Case 1: Case 2: Case 3: The environment variable that determines in what directory to create temporary files is set to an invalid directory. There is not enough free space on the disk to create the temporary file. A temporary file that cannot be modified already exists.
Action
You can take the following actions to correct this error: If Case 1: Set your environment variable for temporary files to a valid directory. If Case 2: Free up some space on your disk. If Case 3: Remove the existing temporary file, if possible.
REP0119 Cause
Boilerplate <boilerplate name>s external source file <filename> not found. Oracle Reports tried to find the source file specified for a piece of external boilerplate and couldnt do so. The possible causes of this error include the following: Case 1: Case 2: Case 3: The file was not found under the specified name in the specified location. You lacked the necessary privileges to open the file. A system error made it impossible to open the file.
Action
You can take the following actions to correct this error: If Case 1: Make sure the file is stored in the specified directory under the specified name. If it is not, change the directory and/or filename as appropriate. If Case 2: Make sure that you have the privileges necessary to open the file. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
REP0120 Cause
Oracle Graphics display <display name>s external source file <filename> not found. Oracle Reports tried to find the display specified for an Oracle Graphics display object, but couldnt do so. The possible causes of this error include the following:
2 15
Case 1: Case 2: Case 3: Action
The display was not found under the specified name in the specified location. You lacked the necessary privileges to open the display. A system error made it impossible to open the display.
You can take the following actions to correct this error: If Case 1: Make sure the display is stored in the specified directory under the specified name. If it is not, change the directory and/or filename as appropriate. If Case 2: Make sure that you have the privileges necessary to open the display. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
Too many arguments. You have entered more than the allowable number of arguments for the command. Check the syntax of the command. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command correctly. Duplicate argument specification for keyword <keyword>. You have entered an argument more than once for the keyword shown. The possible causes of this error include the following: Case 1: Case 2: You entered a positional argument for the keyword and then entered the keyword with another argument. You entered the same keyword twice (e.g., KEYWORD1=YES and KEYWORD1=NO).
REP0151 Cause
Action
Check the syntax of the command. For more information, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system. You can take the following actions to correct this error: If Case 1: Reenter the command with just the positional argument or just the keyword argument. If Case 2: Reenter the command specifying the keyword only once.
2 16
REP0152 Cause
Positional argument specified after keyword. On the command line, you entered an argument without its keyword after entering an argument with its keyword. Once you have used a keyword on the command line, all subsequent arguments must use keywords as well. Reenter the command making sure that no positional arguments (arguments where the keyword is implicit) are specified after arguments with keywords. Multiple values not allowed for keyword <keyword>. In your command, you have entered more than the allowable number values for the keyword argument shown. For example, you might have entered KEYWORD=(A, B), where KEYWORD only accepts a single value. Check the syntax of the command. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command without the extra value(s). Unable to open command file <filename>. You entered a command that referenced the command file shown and the file could not be opened. The possible causes of this error include the following: Case 1: Case 2: Case 3: The file was not found under the specified name in the specified location. You lacked the necessary privileges to open the file. A system error made it impossible to open the file.
Action
REP0153 Cause
Action
REP0154 Cause
Action
You can take the following actions to correct this error: If Case 1: Make sure the file is stored in the specified directory under the specified name. If it is not, change the directory and/or filename or move the file into the specified directory. If Case 2: Make sure that you have the privileges necessary to access the file. If you dont, change your privileges accordingly. If Case 3: Consult your operating system documentation or contact your system administrator.
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 in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command with the appropriate value for the keyword(s).
2 17
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 was not valid. Check the syntax of the keyword. For more information, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system. Reenter the command with the appropriate value for the keyword(s). 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 and the keyword only accepts YES or NO. Reenter the command and use a value of YES or NO for the keyword shown. 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 in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command using the appropriate keywords for the task you want to perform. Syntax error on command line. The string you entered on the command line could not be parsed. The most likely cause of this error is that you entered quotes or parentheses without also entering matching end quotes or parentheses. Check the syntax of the command. For more information, see Executables in Chapter 1 of the Reports Reference Manual. (You can also check the online help system.) Reenter the command using the appropriate syntax. Syntax error in command file. Something you entered in your command file could not be parsed. The most likely cause of this error is that you entered quotes or parentheses without also entering matching end quotes or parentheses. 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 online help system.) Edit the file and modify the commands as necessary to correct the command(s).
REP0159 Cause
Action
REP0160 Cause
Action
2 18
No command line arguments specified. You invoked R25CONV or R25MREP without specifying any command line arguments. Specify the appropriate command line arguments (e.g., SOURCE, DEST, etc.) for R25CONV or R25MREP. For more information, see Executables in Chapter 1 of the Reports Reference Manual. Cannot run to screen in background. You specified that the report be run in the background, but you also specified a DESTYPE of Screen. You cannot execute a report in the background while having its output sent to the screen. If you want the output to go to the screen, you must run it in the foreground. If you want the report to run in the background, you must specify a different DESTYPE. Cannot run character report in bitmap mode using this executable. You are attempting use the charactermode executable to run a charactermode report 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. Cannot run report in bitmap mode to screen using this executable. You are attempting use the charactermode executable to run a bitmapped report to the screen. This is not allowed. Run the report using BATCH=YES or use a bitmapped executable. Cannot run report in background. You specified YES for BACKGROUND under one of the following conditions, none of which are allowed: Case 1: Case 2: You are running the report from the designer. You set BATCH to YES.
REP0190 Cause
Action
2 19
Case 3: Case 4: Action
You are running the report using the packaged procedure srw.run_report. The platform on which youre running the report does not support spawning of another process.
Ensure that BACKGROUND is set to NO when any of the above condition are true. Must specify BATCH=YES or BACKGROUND=YES on command line when running bitmapped report. You tried to run a bitmapped report using the charactermode executable in the foreground or during an interactive session. This is not supported. If you wish to run a bitmapped report using the charactermode executable, you must choose either BATCH=YES or BACKGROUND=YES (unlike BATCH=YES, this setting gives you access to the Runtime Parameter Form). Cannot allocate enough memory. Oracle Reports cannot obtain enough memory from the system to complete the current task. Make more memory available, if you can, or ask your system administrator for assistance. Zero or negative block size requested. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to free a null pointer. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Passed a null pointer as a handle. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 20
REP0204 Cause Action REP0205 Cause Action REP0206 Cause Action REP0207 Cause Action REP0208 Cause Action REP0209 Cause Action REP0210 Cause Action REP0211 Cause Action
Handle does not point into an mp block. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Too many simultaneous locks on one object. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Null cache pointer passed to virtual memory routine. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Requested block is larger than virtual memory space. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. rmaloc was not given a function identifier. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. rmaloc was not given a structure identifier. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Illegal operation was requested on a locked handle. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to use a handle after freeing it. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 21
No literal specified. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to lock handle failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot allocate a virtual memory buffer of size <number> KB. Please try a smaller size. Oracle Reports tried to allocate a virtual memory buffer size at or below the number specified (by you or by default) for the BUFFERS keyword. Specify a smaller size for BUFFERS (either in the Runtime Settings tab of the Tools Options dialog or on the command line), or free up more memory. (To check the command line syntax, see Executables in Chapter 1 of the Reports Reference Manual. You can also check the online help system.) Error locking, dereferencing, or freeing a memory handle. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Symbol table overflow. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Identifier does not match a defined symbol. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Warning: The path specified by environment variable <variable name> is too long and will be ignored. The path designated by the environment variable is too long. Shorten the length of the designated path.
2 22
Warning: The total length of the search paths is too long and will be truncated. The combined length of search paths in the path environment is too long. The combined length cannot exceed 255 characters. Shorten the length of one or more paths in the path environment. ORACLE error occurred. Oracle Reports encountered an ORACLE error. Scroll through the error message to see where the error occurred and, if possible, fix it. Otherwise, contact your DBA. The SELECT statement may not contain an INTO clause. You entered an INTO clause in a SELECT statement, which is not allowed in Oracle Reports. Remove the INTO clause. Parameter <parameter name> not found in report. You made reference to a parameter that is not defined in the report. The most likely cause is that you deleted a parameter but did not delete all references to it. Delete all references to the deleted parameter. The statement you have entered is not a SELECT statement. What was entered in the SELECT Statement field is something other than a SELECT statement. The possible causes of this error include the following: Case 1: Case 2: You entered something besides a SELECT statement in the SELECT Statement field. You referenced an external query that did not contain a SELECT statement.
Action REP0303 Cause
Action
You can take the following actions to correct this error: If Case 1: Enter a valid SELECT statement. If Case 2: Modify the external query or reference another external query.
2 23
REP0304 Cause
& in SELECT statement was not followed by a valid lexical parameter. An ampersand (&) appeared in the SELECT statement by itself. The possible causes of this error include the following: Case 1: You intended to make a lexical reference but either left out the name of the column or parameter altogether or inadvertently typed a space between the ampersand and the name of the column or parameter. In typing the SELECT statement, you accidentally typed in an ampersand.
Case 2: Action
You can take the following actions to correct this error: If Case 1: Make sure that the column or parameter name immediately follows the ampersand with no spaces in between. If Case 2: Delete the ampersand.
REP0305 Cause
<lexical reference> can not be used as a lexical parameter because it is not a character value. You entered an invalid lexical reference in your SELECT statement. Lexical references can only be made to parameters or columns containing character data. The possible causes of this error include the following: Case 1: Case 2: Case 3: You referenced the wrong column or parameter. You meant for the reference to be a bind reference, not a lexical reference. You created the parameter or column referenced with a noncharacter Datatype.
Action
You can take the following actions to correct this error: If Case 1: Change the name that follows the ampersand (&) so it references a parameter or column with a Datatype of Character. If Case 2: Replace the ampersand (&) with a colon (:) when referencing the parameter or column. If Case 3: Change the Datatype of the parameter or column to be Character, if appropriate.
2 24
REP0306 Cause
<name> is not a valid parameter name. In making reference to a parameter, you have tried to create a parameter with an invalid name. When you use a bind reference, a parameter definition is automatically created using the name specified in the bind parameter. In this case, Oracle Reports could not create the parameter because the name you supplied was not a valid name. Check the naming conventions for data model objects and rules for parameter names. For more information on naming conventions, see Naming Conventions in Appendix D of the Reports Reference Manual. Rename the parameter and change the name in the bind reference. The SELECT statement may not contain a FOR UPDATE clause. You entered a FOR UPDATE clause in the SELECT statement, which is not allowed in Oracle Reports. Remove the FOR UPDATE clause. Internal error Unknown column type. The possible causes of this error include the following: Case 1: You tried to display the value of a column using SRW.MESSAGE, but the columns datatype (e.g., LONG, LONG RAW, ROWID) is not supported for that operation. You tried to pass the value of a column to another Oracle product (e.g., Oracle Graphics) as a parameter, but the columns datatype (e.g., LONG, LONG RAW, ROWID) is not supported for that operation.
Action
Case 2:
You cannot display or pass this columns value. Unable to connect to ORACLE after three attempts. Access denied. Some part of the logon string you entered was incorrect. After three failed attempts, Oracle Reports displays a dialog box with this message. Your only option from this dialog box is to accept it and then Oracle Reports quits and returns you to the operating system. Accept the dialog box. Confirm your logon information with your DBA, if necessary. 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 new ORACLE logon for you.
Action
2 25
REP0310 Cause Action REP0311 Cause Action REP0312 Cause Action REP0313 Cause Action REP0314 Cause Action REP0315 Cause
Error while processing Bind Variables in query. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal ErrorSegmented memory used for lexical parameter. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal errorError dealing with segmented memory. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal errorFetching data records would cause memory overflow. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Column name exceeds 256 characters. Unable to describe. Use column alias for <column_name>. One of your SQL SELECT statements contains an expression that is longer than 256 characters, but has no alias. Edit the SELECT statement and assign an alias to the expression. Each select statement must have the same number of columns in compound query. You entered a query with a UNION, INTERSECT, or MINUS set operator in which the SELECT statements in the query do not have the same number of selected columns. Modify the SELECT statements so that they have the same number of columns.
Action
2 26
REP0316 Cause
The types of corresponding columns must match in compound query. You entered a query with a UNION, INTERSECT, or MINUS set operator in which corresponding columns have different typese.g., column 1 in the first SELECT statement has datatype CHAR, while column 1 in the second SELECT statement has datatype NUMBER. Modify the SELECT statements so that all corresponding columns have the same datatype. Could not connect to the database. An attemp to connect to the database failed. Recheck the userid and password and try again. Internal ErrorCould not put back fetched rows. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 querys select statement. 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 querys select statement. GET_REF PL/SQL funtions last parameter must be of type ROWID. You did not provide a parameter of type ROWID as the last parameter for a GET_REF function. Check your parameter list and ensure the last parameter is of type ROWID. <PL/SQL error>. Oracle Reports encountered the following PL/SQL error while running a report. Edit and recompile the PL/SQL in the report to avoid this error.
Action
2 27
REP0451 Cause Action REP0452 Cause Action REP0453 Cause Action REP0490 Cause Action REP0491 Cause
<PL/SQL error>. Oracle Reports encountered the following PL/SQL error while running a report. Edit and recompile the PL/SQL in the report to avoid this error. <PL/SQL error>. Oracle Reports encountered the following PL/SQL error while running a report. Edit and recompile the PL/SQL in the report to avoid this error. <PL/SQL error>. Oracle Reports encountered the following PL/SQL error while running a report. Edit and recompile the PL/SQL in the report to avoid this error. Internal Error Toolkit context unavailable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Warning: Data truncation possible in column <column name>. The database columns width in the report is defined to be less than its width in the database. This can sometimes occur when the columns in the database are updated subsequent to the report being defined. This warning is raised only when RUNDEBUG is YES. Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement field and then accept the property sheet. Unrecognized token: <tokenname>. The SELECT statement that you entered contains an item that is not part of SQL syntax. Review your SELECT statement and ensure that it follows SQL syntax. Internal Error Unable to expand Lexical references. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
2 28
Internal Error Unable to process Lexical references. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal Error Unable to tokenize the query. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal Error Unable to parse the query. The SQL statement that you have entered cannot be parsed because it contains an error. Review the SQL statement that you entered and ensure that you are using the correct syntax. For more information, see the ORACLE7 Server SQL Language Reference Manual. Internal Error Query failed in rodslt. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Number of columns selected by the query is incompatible with report definition. The query is selecting more columns than the report definition is expecting. This can happen when you are using an external query and the query has been changed since the report was defined. 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 and accept it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated. Column selected by the query is incompatible with report definition. The column from the database does not match the column in the report definition. The possible causes of this error include the following: Case 1: The definition of the column in the database has changed since the report was defined.
Action
REP0499 Cause
2 29
Case 2: Action
The report uses an external query and the external query was changed since the report was defined.
You can take the following actions to correct this error: If Case 1: Update the report definition so that it accepts the changed column. For example, if the datatype of the column has changed, reaccept the Query property sheet so the column in the report definition has its datatype updated. Formulas, summaries, and fields that rely on the changed column may also need to be updated. If Case 2: Update the report definition so that it accepts the changed query. For example, reaccept the Query property sheet that references the changed external query and accept it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated.
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 described and enter a number that is within the limits. Unable to connect to ORACLE. Oracle Reports tried to but could not connect to ORACLE. The possible causes of this error include the following: Case 1: Case 2: ORACLE is temporarily unavailable. Your connect information was not valid.
REP0501 Cause
Action
You can take the following actions to correct this error: If Case 1: Retry the operation. Contact your DBA if the problem persists. Note that after three failed attempts, you will be forced to leave Oracle Reports. If Case 2: Check your connect information to make sure it is correct. If it is not, reenter it and try to connect again. Note that after three failed attempts, you will be forced to leave Oracle Reports.
REP0502 Cause
Error attempting to open <filename> terminal file. Oracle Reports tried to but could not open the terminal definition file you specified. You either specified the name of the file incorrectly after the TERM keyword or the file could not be found. Make sure that you specified the name of the terminal definition correctly and that it resides in the correct path. If the problem persists, contact your DBA.
Action
2 30
You did not specify the name of a report. You specified an invalid name or nothing when you should have specified the name of a report. Specify the name of a report. You are not connected to ORACLE. You tried to perform an operation that requires you be connected to the database and you were not connected. Connect to the database using File>Connect.... This is not a valid width for this column. The value you entered in Width was invalid. The possible causes of this error include the following: Case 1: Case 2: Case 3: You entered zero or a negative number. Width must be greater than zero. You entered something that was not a number. For a column of nonnumeric Datatype, you entered a width of the form (x, y) where x is the precision and y is the scale. This type of Width specification is only valid when Datatype is Number.
Action
You can take the following actions to correct this error: If Case 1: Enter a number greater than zero. If Case 2: Enter a number greater than zero. If Case 3: Enter a number greater than zero or, if possible, change the Datatype of the column to Number.
REP0506 Cause
Database columns can not be moved between queries. You tried to move a column into another group belonging to another query and the column is a database column. A database column must be selected by the query that owns its group. Select the column, if possible, in the query that owns the group to which you want to move it.
Action
2 31
REP0507 Cause Action REP0508 Cause Action REP0509 Cause Action REP0510 Cause Action REP0511 Cause Action REP0512 Cause Action REP0513 Cause Action
You must enter a filename before performing this operation. In a file selection dialog box, you tried to accept the dialog box without specifying a filename. Enter a name and then accept or cancel the dialog box. You must enter an object name before performing this operation. In a database object selection dialog box, you tried to accept the dialog box without specifying an object name. Enter a name and then accept or cancel the dialog box. 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. 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. 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. A decimal value is not appropriate here. The number that you entered was a decimal value and Oracle Reports was expecting a nondecimal value. Enter a nondecimal value. 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.
2 32
You must specify the Page Size. You left the Page Width and/or Page Height settings blank and they require a value. Enter a number for Page Width and/or Page Height. You must specify the Parameter Form Size. You left the Parameter Form Width and/or Parameter Form Height settings blank and they require a value. Enter a number for Parameter Form Width and/or Parameter Form Height. You must specify the Page Size in characters. The value you entered for Page Size was not in character units, and Page Size requires character units. Enter a value in characters for Page Size. You must specify the Form Size in characters. The value you entered for Form Size was not in character units, and Form Size requires character units. Enter a value in characters for Form Size. 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. 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. The value for group or frame indentation must be between 0 and 4. The value you entered for Group/Frame Indentation was outside the valid range of values. Enter a number between 0 and 4.
2 33
<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 ensure that the name follows those conventions. For more information, see Naming Conventions in Appendix D of the Reports Reference Manual. You can not build a default layout because this report has no groups. You selected Tools>Default Layout... or drew a region using the Default Layout tool in the Layout editor before having created any groups for the report. Groups are required in order to create a default layout. Create one or more queries to allow Oracle Reports to automatically create a group, then retry the operation. Invalid Default Layout Style. See the list of values. You entered a value for Default Layout Style that is not one of the valid options. Select a layout style from the list of values. 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. Valid options are Screen, File, Printer, Mail, or Sysout. You entered a destination type for the system parameter DESTYPE that is not one of the valid options. Possible causes of this error include the following: Case 1: Case 2: You entered an invalid value for Destination Type in the Runtime Parameter Form. You entered an invalid Initial Value in the Parameter property sheet for DESTYPE.
REP0522 Cause
Action
Action
You can take the following actions to correct this error: If Case 1: Enter one of the valid values, Screen, File, Printer, Mail, or Sysout. If Case 2: Select a value for Initial Value from the list of the values.
2 34
REP0526 Cause
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 Parameter property sheet. The possible causes of this error include the following: Case 1: Case 2: You entered a value in Initial Value that is too big, given what you specified for the parameters Width. You entered a value for Width that is too small to contain the values you want to be able to enter for the parameter.
Action
You can take the following actions to correct this error: If Case 1: Reenter the Initial Value, making sure that it is not wider than what you specified in Width. If Case 2: Delete the Initial Value you have entered. Move to the Width setting for the parameter and increase it such that it can contain the Initial Value you had specified. Reenter the Initial Value.
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, you can suppress the display of the parameter on the Runtime Parameter Form by using the Default Parameter Form dialog box or the Parameter Form editor. For more information, see Parameter Form Editor in Chapter 9 of the Reports Reference Manual. Also, see your online help. Valid options are Character, Number or Date. The datatype you entered in Datatype for the parameter was not one of the valid datatypes. Select a datatype for Datatype from the list of values. Valid options are Box, Graphic, Line or Text. The value you entered in Type for the boilerplate was not one of the valid types. Select a value for Type from the list of values.
2 35
REP0530 Cause
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 the size of the file. Oracle Reports only imported as much of the file as could fit in the field. If you wish to import the entire file, increase the size of the field. Invalid Object Type. See the list of values. In the Navigate to Object dialog box, you entered an invalid value for Object Type. Select a value from the list of values. There is no object of that type with this name. The value you entered in the Object Name field of the Navigate to Object dialog box does not correspond to an object of the specified type in the report. Make sure that you specified the name correctly and that the object is contained in the current report. You can only import to a text entry field. You selected Edit>Import while in a nontext entry field (e.g., a field that accepts only a number). You can only import into a text entry field in a property sheet. If you wish to import something, move to a text entry field to do so. You can only export from a text entry field. You selected Edit>Export... while in a nontext entry field (e.g., a field that accepts only a number). You can only export from a text entry field in a property sheet. There is no object named <object name> in the database. You tried to perform an operation on a module stored in the database, but Oracle Reports could not find the object. Make sure that you specified the name correctly and are connected to the database where the module resides.
Action REP0531 Cause Action REP0532 Cause Action
REP0533 Cause
2 36
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 must be the objects owner. Have the owner delete the object, if possible. 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, you must be the objects owner. Have the owner rename the object, if possible. 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 existing object. 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 that the parameter form can span. Page size too small for default parameter form. The current Form Width and Form Height settings are too small for the default parameter form. Increase the size of the parameter form pages in the Report Properties property sheet by changing Form Width and Form Height. Alternatively, you can default the parameter form by selecting Tools>Default Parameter Form... and reduce its size by editing it in the Parameter Form editor. Source must be a report. For R25RUN, R25CONV, or File>Convert..., you specified something other than a report as the source. These operations all require a report as their source. Specify a report as the source for the operation.
REP0541 Cause
Action
2 37
REP0542 Cause
No date masks have been specified as preferences. While in the Parameter or Field property sheet of a parameter/field of Type Date, you chose the List button for Input Mask or Format Mask, but no masks are specified in the Date Mask list of the Preferences tab of the Tools Options dialog box. Enter a date format mask manually or go to the Preferences tab of the Tools Options dialog box and enter some date format masks in the Date Mask list. No number masks have been specified as preferences. While in the Parameter or Field property sheet of a parameter/field of Type Number, you chose the List button for Input Mask or Format Mask, but no masks are specified in the Number Mask list of the Preferences tab of the Tools Options dialog box. Enter a number format mask manually or go to the Preferences tab of the Tools Options dialog and enter some number format masks in the Number Mask list. The online help system is not available. You selected Help>Help System, but help could not be found. This may have happened because the help files could not be found or because of a help system error. Ensure that the help files and help system are properly installed. If they are and the error persists, you should contact Oracle Customer Support for assistance. For more information, see Calling Oracle Customer Support on page 1 4. The number must be greater than 0. You entered zero for Page Width, Page Height, or Logical Page Size in the Report Properties property sheet. You must enter a number greater than zero. Enter a number greater than zero for Page Width, Page Height, or Logical Page Size. 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 parameter with a datatype of Number. Retry the operation, entering a valid value for the parameter.
Action
REP0543 Cause
Action
REP0544 Cause
Action
REP0546 Cause
Action
2 38
Problem initializing Oracle Toolkit. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 you specified a DESTYPE that is invalid for running in the background. Change the DESTYPE to File, Printer, Mail, or Sysout, or do not run the report with BATCH=YES. Invalid Parent Group. The name you entered does not identify a valid parent group in the report you are currently defining. Select a group from the list of values. Invalid Parent Column. The name you entered does not identify a valid parent column in the report you are currently defining. The column you specified does not exist in the parent group. Select a column from the list of values. If the column you want does not appear, add it to the SELECT statement of the parent query of the group specified in Parent Group. Invalid Child Column. The name you entered does not identify a valid child column in the report you are currently defining. The column you specified does not exist in the query. Select a column from the list of values. If the column you want does not appear, add it to the SELECT statement of the query. 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.
Action
2 39
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. Warning: START WITH is ORACLEspecific SQL syntax. Report will not run against nonORACLE database. The START WITH clause is only available with the ORACLE database. If you are not connected to any database or you are connected to a nonORACLE database, this warning is raised. Ensure that you either run the report against an ORACLE database or remove the START WITH clause before running it against a nonORACLE database. No data links were created. No foreign key in the child query <query name> refers to a primary key in the parent query <query name>. You attempted to create a querytoquery link but no foreign key exists in the child query. Verify whether the tables referred to are on your local database and accessible. If so, add the appropriate column constraints if desired. 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. Invalid Group. The group name you entered in Group is not a valid group for the column. The group you specified does not exist or cannot own the column. Create or modify the group such that it can own the column. A database column must be owned by the group associated with the query that selects it. A summary or formula column must be owned by a group that is below the group(s) that owns the columns being summarized in the group hierarchy (i.e., the order of groups as they appear in the Data Model editor). 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 columns Type.
Action
2 40
REP0562 Cause Action REP0563 Cause Action REP0564 Cause Action REP0565 Cause Action REP0566 Cause Action
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. 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. Invalid File Type. The file type value you entered in Read From File was not one of the valid types. You either misspelled the value or the value you entered does not exist. Select a file type from the list of values for Read from File. 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. 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 the column will be deleted automatically. Invalid Summary Source. See the list of values. The column you entered in Source for the summary is not one of the valid choices. The possible causes of this error include the following: Case 1: Case 2: The column does not exist. The Datatype of the Source is Character or Date. You cannot use numeric functions (such as Percent, Sum, or Average) unless the Datatype is Number.
REP0567 Cause
Action
You can take the following actions to correct this error: If Case 1: Select a column from the list of values for the function. If Case 2: Enter the name of another column in Source that is of Datatype Number.
2 41
REP0568 Cause
Value if Null is invalid. The value of Value if Null in the Column property sheet is invalid for that column. For example, if datatype of the column is Number, and you specify a character string in Value if Null, you will receive this error. Specify a valid value for Value if Null. 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. 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 must have at least one group. If you want to delete the group, delete the groups query. You can not move a group out of its query. You cannot move a group between queries. Groups can only be moved within the set of groups belonging to the same query. You can create a group similar to the one you were trying to move under the other query, if possible. Invalid SQL Select Statement. The SQL SELECT statement that you entered is not valid. Check the SELECT statement for errors and correct them. For more information, see the ORACLE7 Server SQL Language Reference Manual. Lexical parameters are not permitted in External Queries. You made a lexical reference in your external query. You cannot make lexical references from an external query. Delete the reference altogether or, if possible, change it to a bind reference.
Action REP0580 Cause Action REP0581 Cause Action REP0582 Cause Action
2 42
REP0585 Cause
Parent group <group name> for child query <query name> nonexistent. You have deleted a query without deleting references to its groups in data links. This usually happens when you have deleted a query without cascading the deletion to its associated objects. Update the data link in the child query. Adding this data link will create a cycle. The group you specified as the parent group for the data link is not eligible to be a parent because it is, directly or indirectly, a child of the query to which you are linking it. If possible, move the group such that it is not a child of the query and therefore eligible to be its parent group. Otherwise, there is no action you can take. 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 about using PL/SQL within Oracle Reports, see PL/SQL Interface in Chapter 13 of the Reports Reference Manual. For more information about PL/SQL, see the PL/SQL Users Guide and Reference. Invalid PL/SQL Column Formula. You selected Formula as the columns Type, but entered no PL/SQL for the formula. Create a formula or change the columns Type. For more information about using PL/SQL within Oracle Reports, see PL/SQL Interface in Chapter 13 of the Reports Reference Manual. For more information about PL/SQL, see the PL/SQL Users Guide and Reference. 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 total number 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. You are already on the first page. In the Previewer, you selected First while you were already on the first page of the report. None. You cannot scroll up from the first page of the report.
Action
2 43
You are already on the last page. In the Previewer, you selected Last while you were already on the last page of the report. None. You cannot scroll down from the last page of the report. Page <page number> is the current page. In the Previewer, you entered the page number of the current page and chose Go To. If you intended to go to another page, enter a different page number and chose Go To. No report output generated. The report you ran resulted in no output. Check the accompanying messages for errors in the data model and layout. If the problem persists, contact Oracle Customer Support for assistance. Report definition modified. Rerunning report. You ran a report and while its output was still in the Previewer you modified the report definition. If you return to the Previewer without rerunning the report, 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. Number can not be bigger than <number> or less than 1. You entered an invalid value for the Page Number setting on the Field property sheet for a parameter form field. The most likely cause is that you entered zero, a negative number, or a number that is larger than the largest allowable value. Enter a number within the range shown in the message. 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 the screen. Retry the operation so that it will not move objects off the screen.
REP0595 Cause
2 44
You have moved the anchor end point out the boundary of the object, please try again. In moving an anchor, you moved the end point off of the boundary of the object it anchors Move the anchor such that its endpoint is still on the boundary of the object. This text boilerplate is not editable. You attempted to edit the text of an external boilerplate object while it was displayed in the Layout editor. If you wish to edit the text of the external boilerplate object, exit the report and edit the file containing the external boilerplate text using a text editor. There is no list of values available for this field. You attempted to access a list of values for the current field when none is available. No action necessary. 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. In order for some lists of values to contain values, another part of your report must be built first. For example, if a list of values is made up solely of column names and you have not completed your data model, you may get this error. Building your report fully should fix this error. If the error persists, contact Oracle Customer Support. For more information, see Calling Oracle Customer Support on page 1 4. Unable to read list of tables. The dictionary view of accessible tables is not present or not available. See your DBA. Unable to describe table <table name>. The dictionary view of accessible tables is not present or not available. See your DBA.
Action
2 45
REP0604 Cause
Unable to build SELECT statement no values selected. You accepted the Table and Columns Names dialog box without having selected anything with which to build the SELECT statement. If you choose the columns or table radio button, but no columns or tables are selected when you accept the dialog box, you will get this error message. Select a table and, if desired, column(s) or choose the SELECT columns FROM table radio button, and then accept the dialog box. To exit the dialog box without building a SELECT statement, choose the Close button. Unable to read link file <filename>. Check link file format. The file you specified in the Link File field of the Boilerplate property sheet cannot 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 you entered in the Format field matches the format of the file. Runonly 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 an extension of .rdf. Invalid Source Type. See the list of values. You selected File>Convert... and the source type that you specified is not valid. Select the source type from the list of values. 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. Error while attempting to print screen. Make sure log file <filename> is accessible. Oracle Reports attempted to write the contents of the screen to the file printdef.dat but could not locate the file. To determine the proper location for printdef.dat, see your Developer/2000 Installation Guide.
Action
2 46
Valid options are Screen, File, Printer, or Mail. In the Runtime Parameter Form, you provided a value for Destination Type that was not valid. Specify a value of Screen, File, Printer, or Mail for Destination Type. Invalid date mask. The date mask that you entered does not correspond to any of the valid date masks. Check to make sure that you entered the mask correctly. For more information, see Format Mask in Chapter 8 of the Reports Reference Manual. Value does not match mask <mask string>. The mask you entered in Format Mask is not a valid mask. The possible causes of this error include the following: Case 1: Case 2: The string that you entered as a mask contained invalid characters. You entered a number format mask for a field with Datatype of Character.
REP0613 Cause
Action
You can take the following actions to correct this error: If Case 1: Select a value from the list of values. For more information, see Format Mask in Chapter 8 of the Reports Reference Manual. If Case 2: Change the Datatype of the field to be Number, if possible. If the field is supposed to be Character Datatype and cannot be changed, you cannot have a format mask for it.
REP0614 Cause
There is no window active for your search/replace action. You attempted a search/replace operation using the Search/Replace dialog box, but did not have the cursor positioned in an active Oracle Reports window. Position your cursor in a text entry field before you perform a search/replace operation.
Action
2 47
REP0615 Cause
You can only search/replace a text entry field. You attempted a search/replace operation using the Search/Replace dialog box, but did not have the cursor positioned in a text entry field. Search/replace operations are valid only in text entry fields. Position your cursor in a entry field before you perform a search/replace operation. You cannot replace text in an uneditable region. Using the Search/Replace dialog box, you attempted to replace text in an inaccessible field. You can replace text only in editable regions. Warning: Runtime Parameter Form is already open. To run a new one, please close 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. Warning: Previewer is already opened. To run a new one, please close the old one and run again. You tried to run a report with the Previewer already open. Close the currently open Previewer and try running again. 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. Invalid Vertical Sizing. See the list of values. The value you entered for the objects Vertical Sizing is not one of the valid values. Select a value from the list of values. Invalid Horizontal Sizing. See the list of values. The value you entered for the objects Horizontal Sizing is not one of the valid values. Select a value from the list of values.
Action
2 48
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 valid values. Select a value from the list of values. Invalid Print Condition Object. See the list of values. The value you entered for the Object of the Print Condition is not one of the valid values. Select a value from the list of values. Invalid Text Alignment. See the list of values. The value you entered for Alignment was not one of the valid values. The value is not valid given the datatype of the object. Flush/Left, Flush/Center, and Flush/Right are only valid for fields with Datatype of Character. Select a value from the list of values. You must specify the objects 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. An objects 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. 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. 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 the message.
Action REP0626 Cause Action REP0627 Cause Action REP0630 Cause Action REP0631 Cause Action
2 49
REP0632 Cause
Value already exists in the list. You attempted to add an item to a list, but the item was previously added to the list. For example, if you attempted to add lib1 to your reports Attached Library list, and lib1 was already found in the Attached Library list, you would receive this error. Once an item has been added to a list, it does not need to be added again. No value specified. You attempted to perform a list operation on an item, but you did not specify an item. For example, if you attempted to add a library to your reports Attached Library list, but you left the Library field in the Attached Libraries dialog 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 a button. Destination name must be shorter than <number> character(s). You specified a destination (probably a filename) that is too long. Destination names must be shorter in length. Specify the filename again and ensure that it is of valid length. Value does not exist in the list. You specified a value that is not in the list of valid choices. It could be that you typed the value rather than using the list of values. Specify one of the valid choices in the list. If possible, use the list of values to ensure that it is a valid choice. Invalid Field Source. See the list of values. You entered an invalid value in the fields Source setting. Select a value from the list of values. Close property sheets for all the selected objects and retry. You tried to bring up the Common Properties property sheet while the property sheet for at least one of the selected objects was already being displayed. Close all open property sheets and try again.
Action
2 50
Invalid Source Group. See the list of values. The group name you entered in Source for the repeating frame is not valid. Select a value from the list of values. 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). Select a value from the list of values. Invalid Vertical Spacing. You did not enter a number for the Vertical Spacing field and you tried to leave the field or accept the Repeating Frame property sheet. Enter zero or a positive integer for Vertical Spacing. If you want to leave the property sheet without saving changes or making further updates, choose the Close button. Invalid Horizontal Spacing. You did not enter a number for the Horizontal Spacing field and you tried to leave the field or accept the Repeating Frame property sheet. Enter zero or a positive integer for Horizontal Spacing. If you want to leave the property sheet without saving changes or making further updates, choose the Close button. Invalid value for maximum records per page. You did not enter a number or blank for Maximum Records per Page and you tried to leave the field or accept the Repeating Frame property sheet. Enter blank or a positive integer for Maximum Records per Page. If you want to leave the property sheet without saving changes or making further updates, choose the Close button. Invalid value for minimum widow records. You did not enter a number or blank for Minimum Widow Records and you tried to leave the field or accept the Repeating Frame property sheet. Enter blank or a positive integer for Minimum Widow Records. If you want to leave the property sheet without saving changes or making further updates, choose the Close button.
2 51
Invalid button source. You must select a column. You selected Multimedia Column as the source for your button action, then either did not specify a source column, or specified an invalid source column. 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. Invalid button source. You must specify a source file. You selected Multimedia File as the source for your button action, then either did not specify a source file, or specified an invalid source file. 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. 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 all necessary path information. Invalid boilerplate type. See the list of values. The value you entered in Type for the boilerplate was not one of the valid values (Box, Line, Graphic, and Text). Select a Type from the list of values. Invalid link file name. The file to which you tried to link the boilerplate is not a valid file. Reenter the name, making sure that it references an existing file in the current directory. Invalid value for minimum widow lines. You did not enter a number or blank for Minimum Widow Lines in the property 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 to leave the property sheet without saving changes or making further updates, choose the Close button.
2 52
REP0680 Cause
Invalid anchoring object name. See the list of values. The object name you entered in the Anchored To field of the Anchor Position dialog box is not the name of an object to which you can anchor this object. You tried to accept the dialog box without entering a valid anchoring object name. Select an object name for Anchored To from the list of values. If you want to leave the dialog box without saving the changes or further modifying its fields, choose the Close button. 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 without entering a valid edge for the anchor. Select a value for Parent Edge or Object Edge from the list of values. If you want to leave the dialog box without saving the changes or further modifying its fields, choose the Close button. 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 to accept the dialog box or move to another field without entering a valid value for %. Enter a value in the valid range for %. Invalid Starting Page Number. You left Start At blank. You tried to leave the Start At field or accept the Page Numbering dialog box without entering a value for Start At. Enter zero or a positive integer for Start At. If you want to leave the dialog box without saving the changes or making further changes, choose the Close button. Invalid Page Increment. You left Increment By blank. You tried to leave the Increment By field or accept the Page Numbering dialog box without entering a value for Increment By. Enter zero or a positive whole number for Increment By. If you want to leave the dialog box without saving the changes or making further changes, choose the Close button.
Action
REP0681 Cause
Action
REP0682 Cause
2 53
Invalid Page Number Reset. You left Reset At blank. You tried to leave the Reset At field or accept the Page Numbering dialog box without entering a value for Reset At. Select a repeating frame name or &Report from the list of values to indicate where you want to reset the page number to its Start At value. If you want to leave the dialog box without saving the changes or making further changes, choose the Close button. 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. 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. 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. 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. 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. 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.
2 54
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. Invalid Text Spacing. You have entered number for spacing that is not in the valid range. Enter a number in the valid range. Invalid Character Mode Attribute. See the list of values. The value you entered in this field is not valid. The values you enter in Character Mode Attribute must be defined in your Oracle Terminal or printer definition. (To have these attributes appear in the list of values, you must also list them in VISUAL_PREFS in the preferences file.) Select the desired values from the list of values. If the value you want is not in the list of values, you can check your Oracle Terminal or printer definition to see if the value is a valid one. Sysout is only valid in batch mode. You entered Sysout as the destination type when you were not running the report in batch mode. The possible causes of this error include the following: Case 1: Case 2: You entered Sysout for DESTYPE in the Runtime Parameter Form. You have Sysout as the Initial Value for DESTYPE and you accepted it when not running in batch mode. You might have accepted it without knowing it if you have the Hide Parameter Form preference checked.
Action
REP0709 Cause
Action
You can take the following actions to correct this error: If Case 1: Run the report again, but enter a DESTYPE of something other than Sysout unless you are running in batch mode. If Case 2: Change the Initial Value for DESTYPE to something else or change the DESTYPE to something other than Sysout in the Runtime Parameter Form. If you leave the Initial Value as Sysout, you should not run in nonbatch mode with Hide Parameter Form checked.
2 55
Unable to find printer description file. Oracle Reports could not find the printer description file you specified for DESFORMAT. Specify a valid printer description file for DESFORMAT (e.g., dflt). Destination type must be File, Printer, or Mail when printing from previewer. You pressed the Print button in the Previewer, but DESTYPE is restricted to a value other than File, Printer, or Mail. Ensure that DESTYPE can be set to one of the above values before attempting to print from the Previewer. No printer specified. You attempted to print a report, but did not specify a printer name in either DESNAME or in the Printer Chooser dialog box. Specify a valid printer name using DESNAME. If you often print to the same printer, enter the printer name in the Printer Chooser dialog box. Remember that entering a printer name using DESFORMAT will override the printer name set in the Printer Chooser dialog box. Invalid printer name <printer name> specified by parameter <parameter name>. You attempted to output a report, but did not specify a valid printer name or printer driver name (depending on which is applicable for your platform) in DESFORMAT (if DESTYPE was File or Mail) or DESNAME (if DESTYPE was Printer). Specify a valid printer name for DESFORMAT if DESTYPE was File or Mail, or a valid printer name for DESNAME if DESTYPE was Printer. Invalid mail destination. You attempted to mail report output to another user, but did not specify a valid username for DESNAME. Specify a valid username for DESNAME. 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.
REP0713 Cause
Action
2 56
Invalid option specified for tracing. You specifed invalid trace options. Respecify your trace options. For more information about trace options, see your online help. 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. Cannot trace break information with runtime executable. You attempted to trace breaks while running the report using the runtime executable. Do not specify the Break option when using the runtime executable. 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. Invalid Repeating Frame. See the list of values. The repeating frame that you specified as the Vertical or Horizontal Frame in the Matrix property sheet is not valid. You tried to leave the Vertical or Horizontal Frame field without entering a valid repeating frame. Select a repeating frame name from the list of values. If you want to leave the property sheet without saving the changes or making further changes, select the Close button. Invalid Cross Product Group. See the list of values. The group that you entered for Cross Product Group in the Matrix property sheet is not valid. Select a group name from the list of values. If you want to leave the property sheet without saving the changes or making further changes, select the Close button.
REP0717 Cause Action REP0718 Cause Action REP0719 Cause Action REP0720 Cause
Action
2 57
REP0724 Cause
Cannot get the value of Column <column name> here. You attempted to get the value of the specified column via either issuing a command from the command line of the PL/SQL Interpreter or by executing a standalone PL/SQL program unit. You can only get a column value during report execution. Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a column when the report has suspended execution (e.g., at a breakpoint). Use an alternate method, such as one of the reportlevel triggers, to obtain the column value. Cannot set the value of Column <column name> here. You attempted to set the value of the specified column via either issuing a command from the command line of the PL/SQL Interpreter or by executing a standalone PL/SQL program unit. You can only set a column value during report execution. Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a column when the report has suspended execution (e.g., at a breakpoint). Use an alternate method, such as one of the reportlevel triggers, to set the column value. Cannot get the value of Parameter <parameter name> here. You attempted to get the value of the specified parameter via either issuing a command from the command line of the PL/SQL Interpreter or by executing a standalone PL/SQL program unit. You can only get a parameter value during parameter form execution. Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a parameter when the report has suspended execution (e.g., at a breakpoint). Use an alternate method, such as one of the reportlevel triggers, to obtain the parameter value. Cannot set the value of Parameter <parameter name> here. You attempted to set the value of the specified parameter via either issuing a command from the command line of the PL/SQL Interpreter or by executing a standalone PL/SQL program unit. You can only set a parameter value during parameter form execution. Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a parameter when the report has suspended execution (e.g., at a breakpoint). Use an alternate method, such as one of the reportlevel triggers, to set the parameter value.
Action
REP0725 Cause
Action
REP0726 Cause
Action
REP0727 Cause
Action
2 58
Column <column name> may not be referenced by parameter triggers. You attempted to reference a column in a parameterrelated trigger (Before Form, After Form, Validation), which is not allowed. Remove the reference(s) from the parameterrelated trigger(s) and add them to the Before Report trigger. The program unit <program unit name> of size <number> bytes is too big to be loaded for current platform at the limit of <limit> Your program unit was created on another operating platform and it too large to be loaded into the current operating platform. Reduce the size of the PL/SQL program unit you are trying to load. The following bind variable is not defined: <bind variable> You made a bind reference to a parameter or column that has not been defined yet. You must define the parameter or column before making a bind reference to it. Create a column or parameter definition for the object you want to reference. You could also try using a lexical reference rather than a bind reference, if possible. Error destroying program unit. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Name already exists. Please select another name. You attempted to create a PL/SQL subprogram whose name is identical to an existing subprogram stored in the report. Rename the new subprogram so that it does not conflict with any existing subprograms. No argument is allowed. Needs to be removed. You entered a PL/SQL function or procedure requiring arguments in a PL/SQL field that does not allow PL/SQL with argumentsfor example, in a Format Trigger field, a Formula field, or as a group filter. Remove the argument(s) from the PL/SQL source.
Action
REP0734 Cause
Action
2 59
REP0735 Cause
Unable to load DE Program Unit. Will try to load PL/SQL source texts. Make sure you are connected to a database. Oracle Reports could not load the entire program unit. It could be that the program unit references one or more objects stored in the database, but these objects could not be found. Make sure you are connected to the correct database. Also check to ensure that your program unit is making the correct references. There exists uncompiled program units. You have attempted to convert a report, or loaded an old report, containing PL/SQL which needed to be recompiled. Load the report using R25DES and modify the DE program unit(s). 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. Only function is allowed here. You have entered something other than a function where a function is required. Enter a function. 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 on which the PL/SQL in the report was compiled. The report does not contain the PL/SQL source and, as a result, Oracle Reports could not recompile the PL/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 and recompile it from the current platform. An anchor cannot be anchored with another object. You attempted to anchor an anchor to another layout object, or anchor a layout object to an anchor. Anchors cannot be anchored with other layout objects.
Action
Action
2 60
A matrix cannot be anchored with another object. You attempted to anchor a matrix object to another layout object, or anchor a layout object to a matrix object. Matrix objects cannot be anchored with other layout objects. A margin cannot be anchored with a layout object. You attempted to anchor the margin to a layout object, or anchor a layout object to the margin. The margin cannot be anchored with layout objects. A matrix repeating frame cannot be anchored with another object. You attempted to anchor a matrix repeating frame with a Print Direction of Down or Across to another layout object. Matrix repeating frames with Print Directions of Down or Across cannot be anchored with other layout objects. An anchor must have different parent and child objects. You attempted to create an anchor whose parent and child objects are the samei.e., you tried to anchor an object to itself. You cannot anchor an object to itself. Anchors must have different parent and child objects. 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. PL/SQL references an object which does not exist. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Before form trigger cannot reference a report column. The Before Form trigger for the report references a column in the report. You cannot reference columns from the Before Form trigger. Remove any column references from the Before Form trigger. (If you need to set the value of a column, you should do it from the Before Report trigger.)
2 61
A parameter trigger cannot reference report columns. A Validation Trigger for a parameter references one or more columns in the report. You cannot reference columns from a Validation Trigger. Remove any column references in the Validation Trigger of the Parameter property sheet. After Form trigger cannot reference a report column. The After Form trigger for the report references a column in the report. You cannot reference columns from the After Form trigger. Remove any column references in the After Form trigger. (If you need to set the value of a column, you should do it from the Before Report trigger.) Error closing the PL/SQL library. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error accessing program units from the PL/SQL library. This is an abnormal condition. If you made any changes to your external PL/SQL library, consider selecting File>Save As... and save it under a different name. For information, see Abnormal Conditions on page 1 3. Unable to save the PL/SQL library. This is an abnormal condition. If you made any changes to your external PL/SQL library, consider selecting File>Save As... and save it under a different name. For information, see Abnormal Conditions on page 1 3. Error attaching PL/SQL library <libname>. You tried to attach an invalid external PL/SQL library. This could happen because the library is corrupted, or because the file or object you named does not contain an external PL/SQL library. Make sure that the file or object you named contains a valid external PL/SQL library.
Action
2 62
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 a file or object that is not an external PL/SQL library. Ensure that the file or object you named contains a valid external PL/SQL library and consider using File>Save As... to save the current program unit. Error opening the PL/SQL library <libname>. You tried to open a corrupted external PL/SQL library, or a file or object that is not an external PL/SQL library. Make sure that the file or object that you tried to open contains a valid external PL/SQL library. Warning: Unable to find PL/SQL library <libname>. You tried to attach an external PL/SQL library that doesnt exist, or to open a report 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 a report, reattach the external PL/SQL library. Unable to create external location spec. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. PL/SQL library <libname> is already in use. You tried to attach an external PL/SQL library that has the same name as another external PL/SQL library that is already attached. This could happen if you renamed a file that contains an external PL/SQL library, but the internal name recognized by Oracle Reports was not changed. Use File>Save As... to save the external PL/SQL library under a different name. 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 external PL/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 add such changes (e.g., number or type of parameters) to the calling functions. Make sure your reportlevel PL/SQL correctly references attached libraries.
Action
REP0759 Cause
Action
2 63
You are in the print document session. You already selected File>Administration>Report Doc to produce a report on one or more reports. Finish producing the current report on reports, then select File>Administration>Report Doc again to run another report on reports. Cant open the resource for printing the report. Oracle Reports cannot find the reports (shipped with Oracle Reports) that document your reports. Make sure that the reports that document other reports (shipped with Oracle Reports) are located in the proper directory. For details on the exact location of these reports, see your Developer/2000 Installation Guide. 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 Form trigger or to the report) to make the trigger return true. 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 Form trigger or to the report) to make the trigger return true. Parameter Form Fields <fieldname1> and <fieldname2> may not have the same Source. You specified the same Source for two parameter form fields. Fields on the Runtime Parameter Form must have unique sources. Change the Source of one of the fields. No Source specified for Parameter Form Field <fieldname>. You have not specified a Source for a parameter form field or the source parameter was deleted from the data model. Fields on the Runtime Parameter Form must have a source. Specify a valid Source for the parameter form field.
Action
2 64
Warning: No selectable values for the LOV parameter <parameter name>. You have either not specified any values for the LOV parameters select list, or specified values that cannot be selected. Check the select statement or selectable value list of the parameter to ensure that your specified values are selectable. For more information about LOV parameters, see Parameter Properties in Chapter 6 of the Reports Reference Manual. Warning: The datatype of the first column of the select statement does not match the datatype of the LOV parameter <parameter name>. The datatype of the first column you specified in your select statement does not match the datatype you specified for your LOV parameter. Check the datatype of the LOV parameter, the select statement, and the columns in the database tables accessed by the select statement to ensure that they match. Warning: There are columns values in segmented memory when populating LOV parameter <parameter name>. They will be ignored. You have selected columns with values in segmented memory for your LOV parameters select list. This is not allowed. Select different columns or move the columns values. Warning: There are columns whose types cannot be handled when populating LOV parameter <parameter name>. They will be ignored. You have selected columns whose types cannot be handled (e.g., binary data). Select different columns. Warning: Some columns cannot be formatted correctly when populating LOV parameter <parameter name>. These columns are ignored. The SELECT statement selecting values for your parameters LOV retrieves columns 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 the columns are valid.
2 65
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 values which are too long to include in your LOV parameters select list. Check the values of the items and reduce their length if necessary. The initial value you have entered is invalid against the input mask <input mask>. The value you entered in the Initial Value field violates the mask you specified in the Input Mask field. You must either enter a different value in Initial Value or change the mask in Input Mask. 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. The datatype of the parameter doesnt match the datatype of its source column. You have selected a column with an invalid datatype to furnish values for your LOV parameters select list. Change the columns datatype or specify a different column. The possible values list has bad syntax. You used incorrect syntax to create the list of possible values for your LOV parameter. Edit the possible values list to ensure that it is a proper commaseparated list. A possible value has invalid width. A value you specified for your LOV parameters list of possible values has an invalid width. Edit the possible values list so that all possible values have valid widths, or alter the width.
2 66
A possible value is invalid against the input mask. A value you specified for your LOV parameters list of possible values is not formatted in accordance with the specified input mask. Edit the possible values list to ensure that all possible values are valid against the input mask. The initial value is not among the possible values. The initial value you specified for your LOV parameter does not appear on the defined list of possible values. Add the initial value you specified to the possible values list. The name of the first column from the select statement is not the same at runtime from design time. There is a discrepancy between the column(s) you specified in your original SELECT statement and what the table(s) in question now contains. Check the database to determine if the tables in question have been updated since you created the parameter list, or reapply the LOV parameters SELECT statement. Warning: The value is not among the selectable values of the restricted LOV parameter. You have specified a value for a LOV parameter that is not on the parameters select list. Choose a value from the parameters select list. 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 the Runtime Settings tab of the Tools Options dialog box. Both settings must contain a valid value, or be blank. Specify a valid value for the blank setting, or make both settings blank. You can only select all in a text entry field. You selected Edit>Select All with the cursor positioned on an element in a property sheet other than a text field. While in a property sheet, Edit>Select All is valid only in a text field.
2 67
REP0801 Cause
Layout canvas must remain large enough to fit all layout objects. You reduced the size of the painting region of the Layout editor by changing one or more settings in the Report Properties dialog box, or by resizing the margin, but the resized painting region is not large enough to fit all of the layout objects. Make sure all layout objects in the body, margin, header, and trailer sections of your report fit in the resized painting region. Parameter form canvas must remain large enough to fit all parameter form objects. You reduced the size of the painting region of the Parameter Form editor by changing one or more settings in the Report Properties dialog box, but the resized painting region is not large enough to fit all of the parameter form objects. Make sure all parameter form objects fit in the resized painting region. Canvas size specified is too large. Your report contains combined settings of page/form size and either logical page, maximum body page, maximum header page, maximum footer page, or number of parameter form pages that results in a value larger than that supported by 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, or number of parameter form pages. The report definition was modified during the current run. While in the Runtime Parameter Form, you modified the report via a editor or property sheet. Cancel the Runtime Parameter Form and rerun the report. Could not initialize menus. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error reading window resources. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
REP0802 Cause
Action
2 68
You must enter the Array Size. In the Runtime Settings dialog box, you left the Array Size field blank. You must enter a value for Array Size. Enter an Array Size value between 1 and 9999. You must enter the Buffer Size. In the Runtime Settings tab of the Tools Options dialog box, you left the Buffer Size field blank. You must enter a value for Buffer Size. Enter a Buffer Size value between 1 and 9999. You must enter the Long Chunk Size. In the Runtime Settings tab of the Tools Options dialog box, you left the Long Chunk Size field blank. You must enter a value for Long Chunk Size. Enter a Long Chunk Size value between 1 and 9999. Valid options are Noaction, Rollback, or Commit. In the charactermode Runtime Settings dialog box, you chose an invalid value for On Success/On Failure. Valid values are Noaction, Rollback, or Commit. Select a valid value for On Success/On Failure. Valid options are <In Report Definition>, Screen, File, Printer or Mail. In the charactermode Runtime Settings dialog, you chose an invalid value for Destination Type. Valid values are <In Report Definition>, Screen, File, Printer, or Mail. Select a valid value for Destination Type. Valid options are <In Report Definition>, Landscape, or Portrait. In the charactermode Runtime Settings dialog, you chose an invalid value for Orientation. Valid values are <In Report Definition>, Landscape, or Portrait. Select a valid value for Orientation.
2 69
REP0813 Cause
Valid options are <In Report Definition>, Default, Bitmap or Character. In the charactermode Runtime Settings dialog, you chose an invalid value for Mode. Valid values are <In Report Definition>, Default, Bitmap, or Character. Select a valid value for Mode. Valid options are <In Report Definition>, Yes or No. In the charactermode Runtime Settings dialog box, you chose an invalid value for Background. Valid values are <In Report Definition>, Yes, or No. Select a valid value for Background. Valid options are Landscape, or Portrait. In the charactermode Runtime Parameter Form, you chose an invalid value for Orientation. Valid values are Landscape or Portrait. Select a valid value for Orientation. Valid options are Bitmap or Character. In the charactermode Runtime Parameter Form, you chose an invalid value for Mode. Valid values are Bitmap or Character. Select a valid value for Mode. Valid options are Yes or No. In the charactermode Runtime Parameter Form, you chose an invalid value for Background. Valid values are Yes, or No. Select a valid value for Background. Warning: Page height has changed for Parameter Form. Parameters might be crossed by page boundaries. You changed the height of the Runtime Parameter Form in the Report Properties property sheet. Oracle Reports is notifying you that this might cause the page boundary to move such that it appears in the middle of an object in the parameter form. Look at the layout of your parameter form in the Parameter Form editor and ensure that none of the objects are directly on the page boundary (the darkened line in the editor). Alternatively, you could default (or redefault) the parameter form.
Action REP0814 Cause Action REP0815 Cause Action REP0816 Cause Action REP0817 Cause Action REP0818 Cause
Action
2 70
Could not turn AUTOCOMMIT ON for SQL Server connection. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Another option is to remove all instances of SRW.DO_SQL. If you can do so while retaining all necessary functionality in your report, it will run. 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. Cannot export specified image. Check that the name and , Failed to save the image. The possible causes of this error include: Case 1: Case 2: Case 3: You are attempting to save the image to a nonvalid location. You do not have the necessary privileges to access the table. There is not enough space to save the image.
REP0820 Cause Action REP0821 Action Cause
Action
You can take the following actions to correct this error: 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.
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. No drawing exported. The object you are attempting to export as a drawing cannot be exported as a drawing. Create or select a drawing to export.
2 71
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 the Data Dictionary is not available on the database to which you are connected. Connect to another database. The connected database is neither ORACLE nor DB2. It cannot be used to store applications. You are attempting to store a module to a database that is neither ORACLE nor DB2. This is not allowed. Either connect to an ORACLE or DB2 database or store the module as in your filesystem. Invalid printer driver <name> specified by parameter <parameter name>. You are trying to print a report, but the parameter DESNAME is specifying a printer driver that cannot be used to print the report; e.g., you are specifying a driver 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. 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. Oracle Reports tables are not installed in the database. Cancelling Report Doc. Report Doc cannot be run because there are no Oracle Reports tables in the database. Inform your database administrator that Oracle Reports tables were not succesfully installed in the database. Oracle Reports database tables appear to match tables from an older version of Reports. Cancelling Report Doc. The Oracle Reports tables in the database appear to have been installed from a previous version of the product. Report Doc cannot run against an older version of the database tables. Inform your database administrator that Oracle Reports tables for this version were not successfully installed in the database.
REP0826 Cause
REP0829 Cause
Action
2 72
Oracle Reports database tables appear to be corrupted or incorrectly installed. Cancelling Report Doc. Report Doc caoont be run because the Oracle Reports tables are in an unstable state. Inform your database administrator that Oracle Reports tables are either corrupted or incorrectly installed in the database. 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. Tabs/Col function not supported for this database. You are connected to a database server which does not have an accessible Data Dictionary to list tables and columns. None. Tables and Columns functionality is not available for these databases. Unimplemented Error: This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 more information, see Naming Conventions in Appendix D of the Reports Reference Manual. Enter a name that conforms to the conventions. <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 more information, see Naming Conventions in Appendix D of the Reports Reference Manual.
2 73
There is another <object type> with this name. The name that you entered duplicates the name of another object of the same type. Change the name of at least one of the objects. 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 naming conventions. For more information, see Naming Conventions in Appendix D of the Reports Reference Manual. Name length cannot exceed 30 bytes. Name entered was greater than 30 bytes. Valid SQL names cannot be longer than 30 bytes. Reduce the size of the name to 30 bytes or less. Warning: Owner and Access list not overwritten. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 one with which the report was saved. Use the same or a more recent version of Oracle Reports to open the report. Unable to access module names in database. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to save module to file <filename>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 74
Unable to save module to database. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to obtain new module ID from database. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to delete from table <table name>. You tried to delete from a table and the operation failed. You may not have the necessary privileges. Ensure that you have the necessary privileges. If you do not, see your DBA or have someone with the necessary privileges perform the operation. Unable to lock table <table name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to rename object stored in database. You tried to rename a database object and the operation failed. You may not have the necessary privileges. You must own an object in order to rename it. If you do not own the object, you can either make your own copy of it or have the owner change the name. <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. Unable to read module from database. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 75
Unable to read module from file <filename>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to read SRW2_MODULE. Oracle Reports failed to access the SRW2_MODULE view in the current database. Check to see if Oracle Reports was properly installed on the database. For help, contact your system administrator. Unable to read external file <filename>. You activated Read From File and specified a file name as the value of a column, but Oracle Reports could not successfully open or read the specified file. Check the spelling of the specified file in the Column property sheet, and check to see if the specified file exists. If the file does exist, check the permissions on the file to ensure that you have at least read access. Unable to find external query <query name>. The possible causes of this error include the following: Case 1: Case 2: Case 3: REPORTS25_PATH is not set. You are not connected to a database. The specified external query does not exist.
REP1061 Cause
Action
REP1062 Cause
Action
You can take the following actions to correct this error: 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.
PL/SQL <program unit name> has exceeded the platformspecific size limit. The PL/SQL could not be loaded because it is too large for your operating system. It may have been created on a different platform with a higher limit. Reduce the size of the PL/SQL so it can be loaded on your platform.
2 76
Unable to read module <module name>. You attempted to open a module whose definition, stored in either the database or the filesystem, has been lost or corrupted. This module cannot be used. Unable to read external query <query name>. You attempted to read an external query whose definition, stored in either the database or the filesystem, has been lost or corrupted. This external query cannot be used. 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. Some information is missing in the report. The report cannot be opened because the report definition is incomplete. It may have been corrupted. If the report is stored in the database, use SQLPlus to determine whether the Reports tables have been corrupted. If the report is an .rdf file, use a file system utility to check if the file is corrupted. Take appropriate actions to recover your data. Object Store failure. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. end reached. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. object not found. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 77
object found when not expected. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. object too big. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. invalid object. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 or in the database. invalid type. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. nonspecific file error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. unsupported function. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. unique key violation. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 78
page split occurred. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. close error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. file version error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. file header bad or missing. You performed an operation that required Oracle Reports to open a file. The file either didnt have a header or it didnt have the expected header. The header may have been changed in an editor or the file may not be compatible with this release of Oracle Reports. You can attempt to fix the header in an editor, although, in general, it is not recommended that you edit Oracle Reports files in this way. If the file is incompatible with this release of Oracle Reports, you need to migrate it. For more information, see Migrating Reports and Printer Definitions in Chapter 1 of the Reports Migration Manual. file create error. You tried to perform an operation that required Oracle Reports to create a file and an error occurred. You might not have the necessary file privileges to create the file. Obtain the necessary privileges. file open readonly error. You tried to perform an operation that required Oracle Reports to open a file to which you do not have access. You might not have the necessary file privileges to open the file. Obtain the necessary privileges for the file or, if possible, access a file to which you do have the necessary privileges.
Action
REP1085 Cause
Action
2 79
REP1087 Cause
file open readwrite error. You tried to perform an operation that required Oracle Reports to open a file to which you do not have access. You might not have the necessary file privileges to open the file. Obtain the necessary privileges for the file or, if possible, access a file to which you do have the necessary privileges. file write error. You tried to perform an operation that required Oracle Reports to write to a file to which you do not have access. You might not have the necessary file privileges to write the file. Obtain the necessary privileges for the file or, if possible, access a file to which you do have write privileges. file read error. You tried to perform an operation that required Oracle Reports to read a file to which you do not have access. You might not have the necessary file privileges to read the file. Obtain the necessary privileges for the file or, if possible, access a file to which you do have read privileges. file close error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. disk or file system full. You tried to save an object, but there wasnt enough space in which to save it. You need to either delete some unnecessary files or expand your storage space. file unique key violation. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
REP1088 Cause
Action
REP1089 Cause
Action
2 80
allocate failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. reallocate failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. free failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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. PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does not exist. The possible causes of this error include: Case 1: Case 2: The table does not exist. You do not have the necessary privileges to access the table.
Action
You can take the following actions to correct this error: If Case 1: If the table is not already created, create it. If Case 2: Get access to the table by creating a public synonym for the table in the PRODUCT_USER_PROFILE table, or by making the table public via the PRODUCT_USER_PROFILE table.
Error reading PRODUCT_USER_PROFILE or SYSTEM.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.
2 81
Cannot open nonOracle 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. 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 your data model. You can either change your data model to match the selected layout style or select a different layout style to match your data model. For more information, see your online help. Group <group name> has an invalid repeat direction. You tried to create a default layout, but the selected layout style requires a different repeat direction for one of your groups. Some layout styles place restrictions on the repeat directions you can choose for your groups. You can either change the repeat direction to meet the layout style requirements or you can choose a different layout style. Unable to fit default layout onto page of width <width>. Second line of message may be one of the following: Unable to fit column <column name>; Unable to fit group <group name> and its summaries; Unable to fit group <group name> (wrapping not supported inside matrix); Unable to fit matrix <matrix name> and its summaries. Oracle Reports tried to create the default layout you selected but could not fit the entire layout on the page because the page is not wide enough. If possible, increase the Page Width on the Report Properties property sheet or rearrange objects such that the layout will fit on the page. Otherwise, you may have to make the report multiple pages wide. No column is selected in group <group name>. While trying to create a default layout, you did not select a column for a selected group. Consequently, Oracle Reports cannot build a default layout because 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 selected group.
REP1101 Cause
Action
REP1102
Cause Action
REP1103 Cause
Action
2 82
REP1104 Cause
Generated layout of <size> cannot fit into area of <size>. You generated a default layout and it cannot fit within the given amount of space. The possible causes of this error include the following: Case 1: Case 2: The layout you have generated is too large given the dimensions specified in the Report Properties dialog box. The layout is too big given the size of the marked area in the Layout editor.
Action
You can take the following actions to correct this error: If Case 1: Increase your report dimensions such that the layout can fit, or alter the layout so that it will fit within the current dimensions. If Case 2: Increase the size of the marked area.
REP1106 Cause
Warning: no field generated for column <column name>. When you defaulted your layout, a field was not generated for the column in the message. The most likely cause is that a summary was not placed in the data model correctly. For example, you may have specified the source of a summary column to be a column in a group above the summarys group. This is not allowed. Debug your data model and redefault your layout. Missing across or down group in cross product group <group name>. You attempted to create a default layout by selecting a Default Layout Style of Matrix in the Default Layout dialog box, but all of the dimension groups of the cross product group were assigned repeat directions of Down or Across. Each repeat direction should be assigned to the dimension groups in the cross product. Redisplay the Default Layout dialog box and reassign the repeat directions of the dimension groups, making sure that each direction is assigned among the groups. 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 default settings (e.g., shorten some field widths). Alternatively, you can increase the size of a report page using the Report Properties property sheet. Then redefault your layout. Continue making adjustments as necessary.
Action
2 83
Flow compilation failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Query text missing from query <query name>. You named a query and tried to accept it, but you either did not enter any SELECT statement for it or you entered something that did not begin with the keyword SELECT. The Query property sheet only accepts SQL SELECT statements. Enter a SQL SELECT statement that begins with the word SELECT (you may use upper or lower case). No other SQL statements are accepted in the Query property sheet. 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 before rerunning the report. Field <field name> references invalid column. The column specified as the fields Source either is invalid or does not exist. Select a column from the list of values. Repeating frame <repeating frame> references invalid group. The group name you entered in the Group field of the Repeating Frame property sheet either is invalid or does not exist. Select a group from the list of values. There is a loop in the positional dependency tree. You have created explicit anchors such that an object is indirectly anchored to itself. For example, if you anchored object A to object B, object B to object C, and object C to object A, you would get this error. You must remove at least one of the anchors that caused the loop.
Action
Action
2 84
An object is anchored to more than one other object. In your layout, you have anchored an object to more than one other object. An object may only be anchored to one other object. Eliminate the anchors to other objects such that the object is anchored to only one other object. 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 not enter a valid filter. Enter a valid PL/SQL function or change the filter type. Repeating frame of matrix <matrix name> cannot be anchored. You tried to run a report with an anchor from an intersecting repeating frame of a matrix object to another object. You cannot do this. Delete the anchor. You cannot anchor this object to another object. 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. 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 you have attempted to enclose a large object within a small, fixed frame. Identify the object and the enclosing object and adjust their relative sizes and positions until the proper enclosure is achieved. Object <object name> is not fully enclosed by its enclosing object <object name>. The possible causes of this error include the following: Case 1: Case 2: An object is not fully enclosed by the page. That is, the object extends beyond the page boundary. A repeating frame that forms a matrix is one or more layers above a repeating frame that it contains. In a matrix layout, repeating frames must be below repeating frames that they contain.
REP1212 Cause
2 85
Action
You can take the following actions to correct this error: If Case 1: Move or resize the object so that it does not extend outside the page boundary. Alternatively, increase the page size in the Report Properties 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, the following is true: repeating frames are below repeating frames that they contain and down repeating frames are below across repeating frames.
Field <field name> references column <column name> at a frequency below its group. The source column for the field is in a group below that of the repeating frame which encloses it. Move the field into a repeating frame whose source group is at or above the group that contains the fields source column. Otherwise, move the fields source column into the enclosing repeating frames group, if possible. Repeating frame <repeating frame name> is enclosed by a child repeating frame. The enclosed repeating frames source group is above the enclosing repeating frames source group. In the editor, you can make the enclosed repeating frame the enclosing repeating frame. Alternatively, you could, if possible, change your group hierarchy such that the enclosed objects group is below the enclosing objects group. <object name> has an illegal print condition. You set an invalid Print Condition for the specified object. For example, you might have tried to set the Print Condition of a margin object. Change the Print Condition of the object to another, valid setting. <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 two settings are in conflict. Uncheck Page Break Before or Keep with Anchoring Object.
Action
2 86
<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 nonzero height and width. <object name> has minimum widow lines greater than max lines per page. You have set Maximum Records per Page to a smaller value than Minimum Widow Records. This causes a conflict between the two settings and, in effect, indicates that no instances should be printed. Decrease Minimum Widow Records or increase Maximum Records per Page. Invalid body size. You specified a body page width or height that is negative or out of range. You most likely received this error after setting the page size to an invalid value using the PAGESIZE executable argument. Enter a valid value using the PAGESIZE executable argument, or adjust the body panel size by resizing the margins in the Layout editor. 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 value using the PAGESIZE executable argument. Enter a valid value using the PAGESIZE executable argument, or change the physical page size setting in the Report Properties property sheet. 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 a negative number. 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.
Action
REP1223 Cause
Action
2 87
Between record value for repeating frame <repeating frame name> is negative. The value for Vertical Spacing and/or Horizontal Spacing specified for a repeating frame is negative. Respecify the appropriate Spacing setting for the repeating frame identified in the error message. Field <field name> has an invalid page reset group. In the Reset At field of the Page Numbering dialog box, you specified a repeating frame that does not enclose the layout field you want to display the page number. You may have specified an invalid repeating frame, or deleted the repeating frame after specifying it. Specify &Report or the name of a valid repeating frame as the Reset At value for the page number field. <object name> has an invalid text wrap style. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Matrix <matrix name> has an invalid source frame. You specified an invalid object as the source frame of the matrix object, or the repeating frames you specified have invalid Print Directions. Change the Print Direction of horizontal source repeating frame to Down, and the Print Direction of the vertical source repeating frame to Across. The frames of matrix <matrix name> do not fully intersect. The repeating frames that form the matrix do not completely intersect. For example, if you have two down repeating frames, two across repeating frames, and one of the across repeating frames only intersects completely with one of the down repeating frames, you would get this error. Redefault the matrix layout, if possible, or move the repeating frames that make up the matrix such that they fully intersect one another. Matrix <matrix name> position is not at the intersection of its frames. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
REP1230 Cause
Action
REP1233 Cause
Action
2 88
REP1235 Cause Action REP1236 Cause Action REP1237 Cause Action REP1238 Cause Action REP1239 Cause Action REP1240 Cause Action REP1241 Cause
Error generating index for Cross Product. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid query <query name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid data link. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid group <group name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid column <column name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid anchor. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Circular column dependency originating with column <column name>. You have created a column that directly or indirectly references itself. For example, Column A might reference Column B which in turn references Column A. Update or delete the column(s) to eliminate the circular dependency.
Action
2 89
Matrices must have all down frames below all across frames. In a matrix layout, down repeating frames must be below across repeating frames. Using the Arrange>Send to Back, Arrange>Bring to Front, Arrange>Move Backward, and Arrange>Move Forward, arrange your repeating frames such that, in terms of layers, the following is true: repeating frames are below repeating frames that they contain, and down repeating frames are below across repeating frames. Unimplemented type of summary specified in column <column name>. You specified a summary function that is not available. Specify a valid summary function Wrong number of source columns for summary function of column <column name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Oracle Graphics document not found. Oracle Reports cannot find an Oracle Graphics module as listed in the Oracle Graphics Display property sheet. Correct the file name and path in the Oracle Graphics Display property sheet. Report contains uncompiled PL/SQL. You attempted to run your report before all referenced PL/SQL constructs had been compiled. Compile the PL/SQL, then run your report. All source columns of placeholder <column name> must be in the same group. You attempted to set the value of a placeholder column from column(s) belonging to different groups. Change the placeholder columns group to match the group of the column(s) changing the placeholder columns value.
2 90
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 columns Type. Circular query dependency. Your report contains at least two queries, with each requiring the other to be executed first. Edit one or more of your queries to remove the circular dependency. Circular query dependency originating with query <query name>. Your report contains at least two queries, with each requiring the other to be executed first. The query listed in the message is one of the conflicting queries. Edit the query listed or another conflicting query to remove the circular dependency. Matrix should be surrounded by a repeating frame on group <group name>. The data model for your report contains a matrix with a parent group, but in the layout the repeating frame for the parent group either does not exist or does not surround the matrix. Modify the layout of your report so that the parent group has a repeating frame which surrounds the matrix. 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. Anchored objects are on different regions of the layout. The anchoring and anchored objects of an anchor are on different regions of the layout (body, margin, header, or trailer). Move the abovementioned objects to the same report region.
REP1252 Cause
Action
2 91
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. External boilerplate text is missing its link file. You did not specify a filename in the Link File field in an external boilerplate objects property sheet. Specify a directory path and filename in the Link File field in the External Boilerplate property sheet. Cannot pass data for child query from caller. You have invoked Oracle Reports from another product, and Oracle Reports has been instructed to fetch data for a child query from the caller. Data passed to Oracle Reports can only be for a master query. Modify the callers instructions so that Oracle Reports does not request data for a child query. 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. 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. Groups <group name> and <group name> are from the same query and cannot be linked. You have a data link between two groups from the same query. This is not allowed. Remove the data link or relink to another group. 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.
REP1257 Cause
Action
2 92
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 is the child of itself, either directly or indirectly). Remove at least one of the links in the cycle. 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. Cross product groups must have at least two dimension groups. Multiquery cross product groups must have at least two queries within the cross product group. Remove the cross product group or add dimension groups, or dimension queries (if multiquery). Data link of group <group name> crosses cross product boundary. In your multiplequery matrix report, you have a query where some of its groups are inside the cross product and some outside. Move all groups of the query to either outside or inside of the cross product group. Cross product group <group name> has no child groups. You have a cross product group with no child group, which is required. The child group acts as the cell of the matrix. Create a child group for the cross product group. Column <column name>: Page Level columns not allowed in Cross Product. You have created a column in a cross product group that is or relies on a column that is a pagelevel 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 a pagelevel summary. You must remove the column from the cross product group, or change the Reset At value of the column or the pagelevel summary upon which it relies. OG display <display name> references invalid column as bind parameter. The Oracle Graphics property sheet for the specified display references a column that does not exist. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
2 93
REP1268 Cause
OG display <display name> references bind column <column name> at wrong frequency. The column specified in the Oracle Graphics property sheet for the specified display is in a group below that of the repeating frame that encloses the Oracle Graphics object. Move the Oracle Graphics object into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frames group, if possible. OG display <display name> references invalid source group. The group specified in the Oracle Graphics property sheet for the specified display is nonexistent. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. OG display <display name> references source group at the wrong frequency. The source group in the Oracle Graphics property sheet for the specified object is above that of the source group of the repeating frame. Move the Oracle Graphics object into a repeating frame with a source group that is at or above its source group. OG column name <column name> has been specified multiple times in OG display <display name>. The specified Oracle Graphics display column or parameter has been referenced more than once in the Oracle Graphics property sheet. Check the Oracle Graphics columns and parameters you specify in the property sheet and delete any duplicates. Column <column name> may not be used as a Break Column. You specified a Break Order on a summary, function, or placeholder. These types of columns cannot be used as break columns. Review the rules for which columns can be break columns. For more information, see Break Order in Chapter 6 of the Reports Reference Manual.
Action
2 94
REP1273 Cause
Source groups of matrix <matrix name> not from the same cross product. The source groups of the repeating frames that form the dimensions of the matrix are not contained by the same cross product group. The dimensions of a matrix must be contained within the same cross product group. Change the source groups of the repeating frames or choose different repeating frames to form the dimensions of the matrix. 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 a cross product group must have the same Print Direction. Parentchild relationships within a cross product group are used to create nesting in the matrix. As a result, the repeating frames associated with such groups must print in the same direction on the page. Change the Print Direction of the repeating frames as necessary, choose different source groups for the repeating frames, or choose different repeating frames to form the dimensions of the matrix. Pagelevel column <column name> may not be referenced from format trigger <object name>. PL/SQL entered in Format Trigger cannot reference columns with a Reset At or Compute At of Page. Remove the reference to the pagelevel column or change the columns Reset At or Compute At to something other than Page. Placeholder <column name> references one or more nonformula columns. A placeholder column contains SRW.REFERENCE, but the column referenced is not a formula column. For placeholder columns, SRW.REFERENCE must refer to a formula column. Change the column referenced via SRW.REFERENCE. Invalid select element. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
REP1274 Cause
Action
REP1276 Cause
2 95
Invalid PL/SQL procedure in <object name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid frame or repeating frame <frame name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid field <field name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid boilerplate <boilerplate name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid matrix <matrix name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid Oracle Graphics display <display name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Query <query name> has no groups. Your data model contains a query that has no groups. Each query in your data model needs at least one group associated with it. Create a new group for the query. Query <query name> has no select elements. Your data model contains a query that does not select anything. Each query in your data model must select at least one element. Enter a SELECT statement in the query, selecting at least one element.
2 96
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 dimension group for another cross product group. This is not allowed. Make the group either a cross product group or a dimension group, but not both. 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 filter for another group, if necessary. The numeric argument for group filter of <filter type> missing. You specified First or Last for a groups filter, but you did not specify a number dictating how many records the group should filter. Specify a number for the group filter. 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. Source datatype incompatible with summary function in column <column name>. Your summary column was assigned a Source whose datatype is incompatible with the specified Function. For example, you may be trying to sum a character column. Make sure that the datatype of your source column is compatible with the Function you specified in the Summary Column property sheet. Column <column name> has invalid reset group. You specified an invalid Reset At value for a summary column. Reset At can be set to the same group as the summary column, any group above the summary columns, Page, or Report. Specify a valid Reset At value for the summary column in its property sheet.
Action
REP1291 Cause
Action
2 97
REP1292 Cause
Column <column name> has invalid compute group. You specified an invalid Compute At value for a summary column. Compute At can be set to the same group as the summary column, any group above the summary columns, Page, or Report. Specify a valid Compute At value for the summary column in its property sheet. Column <column name> has invalid product order. A column in a cross product group was assigned an invalid value for Product Order, or no value at all. Specify a valid value for Product Order (consisting of only dimension groups within the cross product) in the columns property sheet. Width of column <column name> is too large. The columns width exceeds the maximum allowed for your operating system. Reduce the width of the column in the Column property sheet. Data format of column <column name> is unsupported. You activated Read from File for a column, but specified an invalid or unavailable 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 all valid data formats. Note that for LONG, RAW, and LONG RAW database columns, only Text and Oracle Format (Image) are valid values for Format. 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 cross product group itself. These operations are not allowed. Create data links between columns and groups other than cross product groups and their associated columns. 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.
Action
2 98
REP1298 Cause
Columns <column name> and <column name> have incompatible types to be linked. The parent and child columns in your data link have incompatible datatypes that cannot be linked. For example, you might have tried to link a Number column to a Character column. Make sure the parent and child columns you specify in data links have compatible datatypes. Groups <group name> and <group name> in different cross products cannot be linked. You tried to create a data link between dimension groups of two different cross product groups, or between columns of the dimension groups. These operations are not allowed. You cannot create data links between two different cross product groups or their columns. 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. 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 a cross product group. No siblings of dimension groups are allowed within the cross product. Dimension groups can consist only of chains of groups. No siblings are allowed. Cross product has two or more child groups. A cross product group has more than one child group. Only one child is allowed per cross product group. Remove all but one of the child groups to the cross product group. 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, above the cross product, or below the cross product, respectively. Make sure that each querys groups are all inside of a cross product, above a cross product, or below a cross product.
Action
REP1299 Cause
Action
Action
2 99
Cross product group <group name> contains another cross product as child. You created a cross product group that is a child of another cross product group. This is not allowed. Ensure that the child group of the cross product group is not a cross product group. Warning: Frame <frame name> intersects but does not enclose object <object name>. Your report layout contains a frame that does not completely enclose the named object. Thus, the object is not considered to be inside the frame. If you want the frame to enclose the object, resize or move the frame. Summary column <column name> has invalid source. You specified an invalid source for the summary column. A summary columns source must be from the same group as the summary column, or from a group below the summary column. Change the source of the summary column to be from the same group as the summary column or from a group below the summary column. Summary column <column name> has invalid product order. The possible causes of this error include the following: Case 1: You have a summary which is not a running summary (i.e., its Reset At is not Report), but its Product Order is not a subset of the source columns product order. The source column of the summary must be at least as frequent as the summary, which means that the summarys Product Order should be some subset of the source columns Product Order. You have a running summary (i.e., its Reset At is Report) with a Product Order that is not a prefix of the source columns Product Order. For example, if the source columns Product Order were A,B,C, then the summary columns Product Order would have to be either A (by itself) or A,B. The summarys Product Order could not be B,A.
Action
REP1307 Cause
Case 2:
2 100
Action
You can take the following actions to correct this error: If Case 1: Change the Product Order of the summary such that it is a subset of its source columns Product Order. If Case 2: Change the Product Order of the summary such that it is a prefix of the Source columns Product Order.
Placeholder column <column name> not supported in cross product. You tried to create a placeholder column inside of a cross product group. Cross product groups cannot contain placeholder columns. Delete the placeholder or move it outside the cross product group. Reportlevel summary <column name> cannot be a percent of total. You created a summary at the reportlevel (i.e., a summary outside of all the groups in the data model) with a Function of % of Total. This Function makes no sense for a reportlevel summary because it will always be 100%. Delete the summary or move it into a group where it will make sense. Boilerplate <object name> references &<reference name> which is not a field. A boilerplate object has a reference to a field that does not exist. It could be that the field being referenced was deleted or renamed and so this reference in the boilerplate object is now invalid. Depending on circumstances, you may want to remove the reference, replace it with a reference to another field, or create the field that it references. Object <object name> with pagedependent references changed to fixed sizing. A field or boilerplate object has a reference to a page calculation or a total number of pages variable. (This is known as a forward reference.) Such layout objects must be fixed in size both horizontally and vertically. The layout objects Horizontal and Vertical Sizing have been set to Fixed by Oracle Reports. Check the output to ensure that the values are not being truncated. If they are, you should enlarge the layout object so that it is large enough to contain the values.
Action
REP1311 Cause
Action
2 101
REP1312 Cause
Page Level column <column name> may not be referenced from OG display <display name>. One of the Oracle Reports columns that you tried to pass to an Oracle Graphics display is or depends upon a pagelevel summary (i.e., a summary with a Reset At or Compute At of Page). A column being passed to an Oracle Graphics display cannot be or depend upon a pagelevel summary. Do not pass the column to the Oracle Graphics display. Page Level column <column name> may not be referenced from group filter <group name>. One of the Oracle Reports columns that you tried to reference in a group filter is or depends upon a pagelevel summary (i.e., a summary with a Reset At or Compute At of Page). A column referenced by a group filter cannot be or depend upon a pagelevel summary. Do not reference the column in the group filter. Format trigger <object name> references column <column name> at wrong frequency. One of your format triggers references a column that is located at the wrong frequency. Remove the reference to the column from the format trigger. Group filter <group name> references column <column name> at wrong frequency. One of your group filters attempted to reference a column that is inaccessible. Remove the reference to the column from the group filter. <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.
Action REP1314 Cause Action REP1315 Cause Action REP1316 Cause Action
2 102
REP1317 Cause
Boilerplate <boilerplate name> references field with source <column name> at wrong frequency. The boilerplate object references the field using &fieldname, but the two objects are not located at the same frequency. For example, the boilerplate object and the field it references are located within different repeating frames. Place the boilerplate object and field at the same frequency, or remove the reference. Error while setting transaction readonly. Having specified READONLY=YES, this error occurred at the start of report execution, while ending the current transaction (with a COMMIT) and starting the readonly transaction, or at the end of report execution, while ending the readonly transaction (with a COMMIT). Make sure you are connected to a database, and make sure that no cursors or locks were left pending by the previous transaction. Warning: Implicit anchoring algorithm cannot uniquely identify the anchoring object of <object name 1>. Arbitrarily choosing <object name 2>. The specified object (object name 1) is in the push path of two objects and it is equidistant from both objects. As a result, Oracle Reports cannot use its normal criteria (shortest distance) to determine the implicit anchor. In the absence of its normal criteria, Oracle Reports randomly creates an implicit anchor to the specified object (object name 2). Note that the implicit anchor may vary between runs of the report. For more information, see Implicit Anchoring in Chapter 2 of the Reports Reference Manual. To avoid the random creation of an implicit anchor, explicitly anchor the specified object (object name 1) to another object. Program unit <progunit name> references column with invalid ID: <ID>. You ran a report with invalid PL/SQL (e.g., PL/SQL that didnt compile). The PL/SQL source included a column reference that cannot be resolved. Check the column references in your PL/SQL source, recompile all of the PL/SQL source in the report, and rerun the report.
Action
REP1318 Cause
Action
REP1319
Cause
Action
2 103
REP1322 Cause
Page break after on <object name> has no effect. You activated Page Break After on an object that has no other objects anchored to it (implicitly or explicitly). In this case, Page Break After has no effect and is invalid. Notice that this is a warning, not an error message. Deactivate Page Break After for the object. Cannot have output columns in format trigger <object name>. In the format trigger for the specified object, you attempted to set the value of an Oracle Reports column parameter. For example, you can use the value of a column called COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannot directly set its value in an assignment statement (e.g., COUNT1 = 10). Remove the assignment statement from the format trigger. Cannot have output columns in group filter <group name>. In the filter for the specified group, you attempted to set the value of an Oracle Reports column or parameter. For example, you can use the value of a column called COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannot directly set its value in an assignment statement (e.g., COUNT1 = 10). Remove the assignment statement from the group filter. Cannot have output columns in Between Page Trigger. In the Between Page trigger, you attempted to set the value of an Oracle Reports column or parameter. For example, you can use the value of a column called COUNT1 in a condition (e.g., IF :COUNT1 = 10), but you cannot directly set its value in an assignment statement (e.g., COUNT1 = 10). Remove the assignment statement from the group filter. <Trigger name> writes to column <column name> at wrong frequency. In a report trigger, you attempted to set the value of an Oracle Reports column at the wrong frequency in the report. You can reference and set only reportlevel columns or parameters, and you cannot reference or set any pagedependent columns (i.e., Reset At of Page) or columns that rely on pagedependent columns. Make sure the columns and parameters whose values you reference or set are reportlevel columns and parameters.
Action
2 104
REP1327 Cause
Column <column 1 name> writes to column <column 2 name> at wrong frequency. In a formula column, you attempted to set the value of an Oracle Reports column at the wrong frequency in the report. You can reference and set only columns that are in the same group or in a higher group in the group hierarchy. For example, a formula for a reportlevel column can only reference other reportlevel columns. Make sure the columns whose values you reference or set are in the same group or in a higher group in the group hierarchy. Cannot run report containing ROWLABEL column <column name> in a nontrusted OS. You are attempting to run a report that requires a secure database while connected to a nonsecure database. Run the report while connected to a secure database. 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, or placeholder column. Only database columns can be linked. Create a data link using database columns. Lexical parameter <parameter name> in query <query name> must not change column dependencies. You created a lexical parameter that changes the number, type, or names of columns, or introduces new dependencies on computed columns or new bind references, when the report is run. Change the lexical parameter so that it does not change columns or introduce new dependencies or bind references. 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 columns value is determined by a lexical parameter. This is not allowed. Replace the child column of the data link with another column.
Action
Action
2 105
REP1332 Cause
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 groups query or in a query above it, or references a computed column that depends on an unrelated column. Remove the offending reference from the group filter. 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. Redesign your layout to avoid this. Warning: variable rotated text <boilerplate name> treated as fixed/contract width. Your report contains a boilerplate text object which was rotated to an angle that is not a multiple of 90 degrees, although both Horizontal and Vertical Sizing values were set to Variable or Expand. In this case, the Horizontal Sizing is treated 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 this boilerplate object. The source of field <field name> is Page Level calculation <column name>. 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, but there is no repeating frame for that group that surrounds the field. Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field. Boilerplate <boilerplate name> references field <field name>, whose source is Page Level calculation <column name>. The object must be enclosed by a repeating frame with group <group name> as source. The specified boilerplate object references the specified field, whose Source is a pagelevel computation. However, there is no repeating frame (whose Source is the named group) surrounding the field. Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field.
REP1335 Cause
Action
REP1336
Cause Action
REP1337
Cause
Action
2 106
REP1338 Cause
Column mode not allowed on repeating frame <repeating frame name>. You activated Column Mode for a repeating frame whose setting do not satisfy either of the following conditions:

Print Direction of Down and a Vertical Sizing of Fixed. Print Direction of Across and a Horizontal Sizing of Fixed.
Action
Change the Print Direction or Vertical/Horizontal Sizing of the repeating frame, or deactivate Column Mode. OG display <display name> missing data columns specification. In the Oracle Graphics Display property sheet, you specified a value in Display Query, 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 specify nothing for Display Query and Source. If you do want to pass data, then specify the columns to be passed in addition to Display Query and Source. Cannot match passedin columns with report definition <report name>. This error occurs when another tool (e.g., Oracle Forms) passes a query to Oracle Reports and there is a mismatch between the columns passed and the columns expected by Oracle Reports. Possible causes of this error include: Case 1: Case 2: Oracle Reports is expecting more or fewer columns than the number that was actually passed by the calling application. The parameter list of the calling application describes a column differently than what Oracle Reports expects. For example, if the reports query selects a character column and the calling application assigns that column a date datatype, this error will be raised.
REP1340 Cause
Action
You can take the following actions to correct this error: If Case 1: Ensure that the calling application is passing the same number of columns that Oracle Reports is expecting. If Case 2: Ensure that the datatypes and names of the columns being passed by the calling application match the dataypes and names in the report.
REP1341 Cause
Warning: Data truncation possible in column <column name>. The database columns width in the report is defined to be less than its width in the database. This can occur when the columns in the database are updated subsequent to the creation of the report definition. Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement field and then accept the property sheet.
Action
2 107
REP1342 Cause
Type of data link to query <query name> illegal for nonORACLE server. If you create a data link with the START WITH clause and run it while connected to a nonORACLE database, you will get this error. START WITH is only supported by ORACLE. Remove the data link that uses START WITH or connect to ORACLE. Invalid button <button name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Button <button name> has no action source file. You have specified an action of Multimedia File for the named button, but have either not specified a source file, or specified a source file that does not exist. Open the property sheet for the specified button and verify that you have chosen a valid file as source for the button action. For more information about usercreated buttons, see Button Properties in Chapter 8 of the Reports Reference Manual. Button <button name> has invalid source column. You have specified an action of Multimedia Column for the named button, but have either not specified a source column, or specified an invalid source column. Open the property sheet for the specified button and verify that you have chosen a valid column as source for the button action. For more information about usercreated buttons, see Button Properties in Chapter 8 of the Reports Reference Manual. Button <button name> references source column <column name> at wrong frequency. The column specified in the property sheet for the named button is in a group below that of the repeating frame that encloses the button. Move the button into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frames group, if possible.
Action REP1343 Cause Action REP1344 Cause
Action
REP1345 Cause
Action
2 108
Button <button name> has invalid icon file. You have specified either an invalid file or a nonexistent file as the icon file for the button face. Ensure that your icon file exists and is of the proper format and uncorrupted. 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 a field, but fields cannot display sound and video. Specify another column (not sound or video) as source of the field. PL/SQL action missing from button <button name>. The PL/SQL trigger that serves as the specified buttons action references a piece of PL/SQL that does not exist. Debug your trigger and ensure that it references a valid program unit. Cannot have output columns in action trigger <program unit name>. The PL/SQL trigger that serves as a button action contains a bind variable that returns a value. A PL/SQL action trigger cannot return a value. Remove the bind variable from your PL/SQL. Warning: icon <icon name> on button <button name> not found. The icon you specified as the button face for the named button cannot be found. The report will run, but the button will appear blank. Open the property sheet for the named button and verify that the icon you specified exists and is in the correct format, and that you have included the correct path information. Couldnt initialize coxr This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. <Program unit name>: Unhandled PL/SQL exception. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 109
<Program unit name>: Illegal to suspend PL/SQL procedure. A PL/SQL construct was suspended during execution or generation. Debug and recompile your PL/SQL constructs. Compile failed for some reason. In generating your report, PL/SQL compilation failed. Debug your PL/SQL constructs. Code is not executable. A PL/SQL construct did not compile properly or for some other reason could not be executed. Debug your PL/SQL constructs. Cannot run parameterized code directly. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot initialize PL/SQL. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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. <Program unit name>: Couldnt 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 Abnormal Conditions on page 1 3.
2 110
<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 been compiled and linked. <Program unit name>: User exit <user exit name>. <submessage>. An error occurred in a user exit. Possible errors: a reference to an unknown column, a truncated column value, unretrievable PL/SQL source, or the user exit could not be found. Based on the submessage, debug your user exit. Ensure that you are referencing valid columns and the PL/SQL code and user exit are accessible. <Program unit name>: Invalid integer argument passed to <procedure name>. The packaged procedure that you referenced expected an integer for an argument, but you did not specify one. Verify that the PL/SQL that references the packaged procedure correctly passes it an integer. For more information about PL/SQL packaged procedures, see The Oracle Reports Package: SRW in Chapter 13 of the Reports Reference Manual. <Program unit name>: Passed null arguments to <procedure name>. The exception SRW.NULL_ARGUMENTS was raised, either by a userdefined PL/SQL subprogram, or because a packaged subprogram was passed one or more null arguments. Check any PL/SQL code that might raise this exception. Also, check the argument list that is passed to the specified packaged subprogram. <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. <Program unit name>: PL/SQL program raised a program error. The exception SRW.PROGRAM_ERROR was raised, either by a userdefined PL/SQL subprogram, or because of an abnormal condition. Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, see Abnormal Conditions on page 1 3.
REP1416 Cause
Action
REP1418 Cause
Action
2 111
REP1421 Cause
<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 procedure is not the correct datatype for the packaged procedure (e.g., the packaged procedure was expecting a column of Character datatype and you passed it a column of another datatype). Debug the PL/SQL that references packaged procedures and ensure that you are passing the packaged procedure the name of a column of the correct datatype. Also check the syntax of the packaged procedure to ensure that you are referencing it properly. For more information about PL/SQL packaged procedures, see The Oracle Reports Package: SRW in Chapter 13 of the Reports Reference Manual. Procedure by this name already exists. You tried to create a new PL/SQL procedure with the same name as an existing PL/SQL procedure. Change the name of the new procedure or change the name of the existing procedure. <Program unit name>: Cannot set maximum rows of the query after it started executing. You used the SRW.SET_MAX_ROW packaged procedure to reduce the number of rows fetched by a query. However, you called SRW.SET_MAX_ROW after the query was already fetched. Move your SRW.SET_MAX_ROW to the Before Report trigger. <Program unit name>: Internal error while executing <procedure name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. <Program unit name>: Error running DO_SQL package <embedded message>. 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 your ORACLE7 Server SQL Language Reference Manual and verify that the SQL statement in your SRW.DO_SQL call is correct.
Action
REP1423 Cause
Action
2 112
<Program unit name>: Running <procedure name> from incorrect context. You attempted to call the named packaged procedure from an invalid area. For example, SRW.SET_ATTR cannot be called from a formula. Modify your PL/SQL code so that it does not call the packaged procedure from that context. <Program unit name>: Nonexistent query name referenced in SRW.SET_MAXROW. You included a call to the SRW.SET_MAXROW procedure in a Before Report trigger, but the query referenced in the procedure call does not exist. Change the call to the SRW.SET_MAXROW procedure so that it references an existing query in the report. <Program unit name>: Error while running <procedure name>. The exception SRW.RUN_REPORT_FAILURE was raised, either by a userdefined PL/SQL subprogram, or because of an abnormal condition after SRW.RUN_REPORT was called. Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, check the command line string passed to SRW.RUN_REPORT. Verify that the specified report exists and that all parameter values are correct. Also note that BATCH=NO is not allowed if the report that owns the PL/SQL code is called by a command line string containing BATCH=YES. For more information, see SRW.RUN_REPORT in Chapter 13 of the Reports Reference Manual. <Program unit name>: SRW.RUN_REPORT cannot be invoked with batch=no. You included a call to the SRW.RUN_REPORT procedure with a command line string containing BATCH=NO, which is not allowed. Remove BATCH=NO from the SRW.RUN_REPORT command string. 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.
REP1428 Cause
Action
2 113
<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. <Program unit name>: SRW.RUN_REPORT cannot be invoked with a userid. You included a call to the SRW.RUN_REPORT procedure with a command line string containing a userid/password, which is not allowed. Remove the userid/password from the SRW.RUN_REPORT command string. <Program unit name>: Value of column <column name> was truncated. A column (e.g., a placeholder) was assigned a value larger than its width could contain, raising the SRW.TRUNCATED_VALUE exception. The exception was not handled, raising this error. Make the column wide enough to contain the assigned value, or handle the exception in your PL/SQL source. <Program unit name>: The PL/SQL references an object which is not in the scope. In a parameters Validation Trigger field, you entered PL/SQL source that referenced a report column. This is not allowed. Remove the reference to the report column from the parameters Validation Trigger. 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 details on the problem. If you cannot correct the problem yourself, see Abnormal Conditions on page 1 3. 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 is not of type LONG, LONG RAW, or RAW. Change the second parameter to specify a column of the correct type.
Action
2 114
Cross Product: value of calculation not found. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Group Manager: value of calculation not found. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Column <column 1 name> references column <column 2 name>, which has incompatible frequency. A column in your data model references another column (e.g., in the Formula field) in your data model, but the two columns are assigned to incompatible groups. For example, if a formula column with a Group of Report referenced a column with a Group of G_Emp, this error would be raised. Remove the column reference, or assign the referencing column to a group that is compatible with the group of the referenced column. Group Manager: internal error <Oracle message> while processing group <group name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Record Manager: report level column not available in rdcagt(). This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Record Manager: a query with internal joins has Maximum Number of Rows set. You most likely used SRW.SET_MAXROW to set Maximum Number of Rows on the cell query of a multiquery cross product. Remove the call to SRW.SET_MAXROW for the cell query. Error Utility: internal error #1. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
2 115
REP1761 Cause Action REP1762 Cause Action REP1780 Cause Action REP1781 Cause Action REP1782 Cause Action REP1783 Cause Action REP1800 Cause
Internal error <context info> while processing <object type> <object name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error <context info>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Stack utility: error during allocation. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Stack utility: error during push. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Stack utility: error during pop. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Stack utility: attempt to pop empty stack. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Formatter error. The possible causes of this error include: Case 1: Case 2: Case 3: In conjunction with VGS1101: Reading image file from UNIX: An image file is corrupted. In conjunction with VGS1701: Executing a report: There may not be enough disk space for a temporary file. This is an abnormal condition.
2 116
Action
Possible actions you can take include: If Case 1: Verify that your image file is displayable. If transferred from another location, make sure it was transferred correctly. Also try transferring it without compression. If Case 2: Make sure there is enough space for a temporary file (at least large enough to store the entire report). If Case 3: For information, see Abnormal Conditions on page 1 3.
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. Unable to read contents of a field from a text file. You have checked Read from File for a column, but Oracle Reports could not find the files pointed to by the column. The possible causes of this error include the following: Case 1: Case 2: Case 3: The files do not exist. You do not have the necessary privileges to access the files. A system error made it impossible to find the files.
Action
You can take the following actions to correct this error: If Case 1: Uncheck Read from File or create the necessary files. If Case 2: Update your privileges, if possible. If Case 3: Consult your operating system documentation or contact your system administrator.
Unable to open destination file <filename>. The destination file that you specified for the report could not be opened. Consult your operating system documentation or contact your system administrator. Unable to open printer definition file <filename>. The printer definition file for the printer that you specified could not be opened. Consult your operating system documentation or contact your system administrator.
2 117
Unable to open mail text file <filename>. You tried to send the report output to a mail message, but the file for the message could not be opened. Consult your Oracle*Mail documentation or contact Oracle Customer Support. Unable to open mail command file <filename>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Mail report command failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to open print command file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Print report command failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Switching to use Oracle Reports ASCII Driver to run character report. You are attempting to print a charactermode report to a printer or a file using either a Postscript driver or the Microsoft Windows Generic Text driver. No action necessary. 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.
2 118
REP1812 Cause
Too many pages formatted. There is either too much data or an error in the reports definition. The possible causes of this error include the following: Case 1: Case 2: You have reached a userdefined limit set to catch too much data. You have reached an error in the report definition.
Action
You can take the following actions to correct this error: If Case 1: Abort running of the program. Check the value of PAGE_LIMIT in the PRODUCT_PROFILE table. Ensure that it is either 0, which means the user is allowed to format an unlimited number of pages, or some value sufficiently large to enable the user to format the report. If Case 2: Debug the report in the designer.
Object <object name> too large to fit in matrix cell. The data fetched into a matrix cell exceeds the capacity of the celle.g., the cell may 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 fetched into them, or redefine your data. Infinite report detected Object <object name> can never fit <location>. The referenced object is causing the most recently formatted page to start with exactly the same state as the page previous . Formatting will therefore cycle until abnormally terminated. Possible causes of this error include: Case 1: Case 2: An object whose Print Condition type is All overflows to the next page; An object whose sizing is Variable or Expand does not appear to extend beyond page boundaries in the Layout editor but does when the report is formatted; A repeating frame does not appear to extend beyond page boundaries in the Layout editor but does when the report is formatted.
REP1814 Cause
Case 3: Action
Using the referenced object as a guide, examine your report layout for objects that may extend beyond page boundaries. Note: The object referenced in the message is the object that extends beyond the boundary. This object may be pushed beyond the boundary by another object, and this second object may need modification.
2 119
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 formula specifies a value where necessary. No value specified for COPIES. No output created. In the Runtime Parameter Form or the Print Job dialog box, you specified zero copies. Specify a value of one or more copies. Start page after end page. No pages output. In the Print Job dialog box, you specified a starting page number that is greater than the ending page number. Change either the starting page number or the ending page number such that the starting number is less than the ending number. Unable to read data in image format. Possible causes of this error include: Case 1: Case 2: You attempted to read a file or database column as containing an image, but the file or columns contents are of the wrong format. The width of the Oracle Reports column you specified may be truncating the image because its too small.
REP1818 Cause
Action
You can take the following actions to correct this error: If Case 1: Make sure you specify a file or column containing an image in a valid format. If Case 2: Change the width of the Oracle Reports column so that its large enough to display the image.
REP1819 Cause
Filename <filename> longer than platform maximum of <length>. You have specified a name for your file that is longer than the platformallowed maximum. This is most likely to occur when accessing a file using 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 a platform that accepts filenames of the specified length.
Action
2 120
Cannot use Oracle Reports ASCII Driver to run bitmap report. You are attempting to print a bitmapped report when the Oracle Reports ASCII Driver is your default printer. This is not allowed. Choose a different printer, then print your report. Before Report trigger returned FALSE. Your report includes a Before Report trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops. Make sure that your report trigger is meant to return a value of FALSE. Between Page trigger returned FALSE. Your report includes a Between Page trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops. Make sure that your report trigger is meant to return a value of FALSE. 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. 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. Left parenthesis must precede right parenthesis in format mask. You reversed the order of the parentheses in your format maski.e., used the right, or close, parenthesis before the left, or open parenthesis. Edit your format mask and reverse the order of the parentheses. The Exponent field in a format mask must contain exactly 4 Es. In specifying that you want to use scientific notation for the field, you have entered too many or too few Es. Enter four Es. Enter the format mask with four Es. If you want extra Es to appear in the output, put them in quotation marks ().
Action REP1827 Cause Action REP1828 Cause Action REP1829 Cause Action REP1830 Cause Action
2 121
REP1831 Cause
Missing closing quotation mark in format mask. You entered an opening quotation mark () before the string in the format mask but not a closing one. The possible causes of this error include the following: Case 1: Case 2: You failed to enter the closing quotation mark after the string. You entered one quotation mark within the quotation marks that begin and end the string.
Action
You can take the following actions to correct this error: If Case 1: Add an ending quotation mark after the string. If Case 2: Enter another quotation mark next to the quotation mark inside the string.
Illegal character <character> in format mask. You have entered a character in a format mask which is not valid for format masks. Delete the illegal character. For more information, see Format Mask in Chapter 8 of the Reports Reference Manual. A format mask must contain at least one digit. The format mask you entered contains no digits. You must have at least one token in your mask that represents a digit. Enter a token in your format mask that represents a digit. The tokens that represent digits are 0, 9, *, and S. For more information, see Format Mask in Chapter 8 of the Reports Reference Manual. A format mask may contain at most one < character. You entered two left angle brackets (<<) in your format mask. You either accidentally typed extra left angle brackets or you wanted some of the extra angle brackets be part of a string. Note: The angle brackets need not be entered sequentially to cause the error. Delete the extra left angle brackets or place them inside quotation marks () as part of a string if you want them to appear in the output.
REP1834 Cause
Action
2 122
REP1835 Cause
A format mask may contain at most one > character. You entered two right angle brackets (>>) in your format mask. You either accidentally typed extra right angle brackets or you wanted some of the extra angle brackets to be part of a string. Note: The angle brackets need not be entered sequentially to cause the error. 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. < must come before > in a format mask. The left angle bracket (<) must come before the right angle bracket (>) in a format mask. Ensure that all angle brackets that are to appear in the output are placed inside quotation marks (). For the angle brackets that delineate the beginning and ending of the decimal aligned region, ensure that the left angle bracket precedes the right angle bracket in the format mask. 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 in quotation marks (). Remove any extra decimal points outside of quotation marks. 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 Vs to appear in the output, put them in quotation marks (). Otherwise, delete the Vs until there is only one in the format mask. , 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 in quotation marks () as a string. Otherwise, delete the comma. , 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 in quotation marks () as a string. Otherwise, delete the comma.
Action
2 123
, 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 in quotation marks () as a string. Otherwise, delete the comma. A format mask may contain at most one exponent field. You entered the token EEEE more than once within your format mask. You are only allowed to enter this token once per format mask. If you want the extra Es to appear in the output, put them in quotation marks (). Otherwise, delete the extra EEEE tokens until there is only one in the format mask. Format masks with exponent fields must have exactly one digit before the decimal point. You entered a scientific notation format mask, but had no digits or more than one digit to the left of the decimal point. If you had more than one digit to the left of the decimal point, delete digits until there is only one to the left of the decimal point. If you had no digits to the left of the decimal point, add one digit. Internal error: Bad index in a Flexible Array. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 between the brackets. If roman numeral format mask, must be simply RN or rn. When you specify the Roman numeral format mask token (RN or rn), you cannot specify any other format mask tokens. If you want the values to be formatted as Roman numerals, eliminate all format mask tokens except RN or rn from Format Mask. Otherwise, do not use the RN or rn token.
2 124
REP1847 Cause
Failed while trying to set up for printing. You attempted to print a report. The possible causes of this error include the following: Case 1: In the Runtime Parameter Form or on the command line, you specified Printer for DESTYPE, but specified an invalid printer name for DESNAME. You are executing a report that executes a second report using SRW.RUN_REPORT. DESTYPE for both reports is set to either File or Printer, but the first report must be run to the screen.
Case 2:
Action
You can take the following actions to correct this error: If Case 1: Retry the operation, specifying a valid printer name for DESNAME. If Case 2: Change the DESTYPE for the first report to Screen or Previewer and run it again.
Failed while trying to begin printing. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Failed while printing. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error in column <column number> of line <line number> of printer definition file <file name>: End of file reached inside quoted string. Your printer definition file contains a quoted string that was not ended with a quote before the end of the file. Use the location specified in the error message to locate the error and add the end quote to the quoted string in your printer definition file. Error in column <column number> of line <line number> of printer definition file <filename>: String is longer than <integer> characters. A string in your printer definition file is longer than maximum number of allowable characters. Reduce length of string.
2 125
Error in column <column number> of line <line number> of printer definition 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 in Appendix B of the Reports Reference Manual. Error in column <column number> of line <line number> of printer definition 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 in Appendix B of the Reports Reference Manual. Error in column <column number> of line <line number> of printer definition 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. Error in column <column number> of line <line number> of printer definition 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. Error in column <column number> of line <line number> of printer definition 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. Error in column <column number> of line <line number> of printer definition 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.
2 126
Error in column <column number> of line <line number> of printer definition 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. Error in column <column number> of line <line number> of printer definition 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. 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 the appropriate word. 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 the appropriate word. Error in column <column number> of line <line number> of printer definition 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 followed by the name of the printer in a quoted string, preferably on the first line of the printer definition file. Error in column <column number> of line <line number> of printer definition 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 name of the printer after the printer code.
2 127
REP1864
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 in a printer definition file. Edit your printer definition file and add the code words that are missing. Error in column <column number> of line <line number> of printer definition file <filename>: Expected number after width. Your printer definition file contains the width code, but no number specifying the width of the report appears after it. Edit your printer definition file and insert a number specifying the width of the report after the width code. Error in column <column number> of line <line number> of printer definition file <filename>: Expected number after height. Your printer definition file contains the height code, but no number specifying the height of the report appears after it. Edit your printer definition file and insert a number specifying the height of the report after the height code. Error in column <column number> of line <line number> of printer definition file <filename>: Expected report to follow before. Your printer definition file contains the word before but not the accompanying word report. Edit the printer definition file to include a complete before report entry. Error in column <column number> of line <line number> of printer definition file <filename>: Expected pages to follow between. Your printer definition file contains the word between but not the accompanying word pages. Edit the printer definition file to include a complete between pages entry.
Cause Action REP1865 Cause Action
2 128
Error in column <column number> of line <line number> of printer definition file <filename>: Expected report to follow after. Your printer definition file (for a multipage report) contains the code word after but not the accompanying word report. Edit the printer definition file to include a complete after report entry. Error in column <column number> of line <line number> of printer definition file <filename>: Expected name of code in quotation marks. Your printer definition file contains the code code with a userdefined string, but the string is not enclosed within quotation marks. Edit your printer definition file and enclose the code userdefined string with quotation marks. Error in column <column number> of line <line number> of printer definition 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 value following dec. Error in column <column number> of line <line number> of printer definition file <filename>: Expected number to follow (. Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the right parenthesis. Edit your printer definition file and add a value between the parentheses in the generalized string. Error in column <column number> of line <line number> of printer definition 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 value following octal.
2 129
Error in column <column number> of line <line number> of printer definition file <filename>: Expected number to follow (. Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the left parenthesis. Edit your printer definition file and add a value between the parentheses in the generalized string. Error in column <column number> of line <line number> of printer definition 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 value following hex. Error in column <column number> of line <line number> of printer definition file <filename>: Expected number to follow (. Your printer definition file contains a generalized string (e.g., dec, octal), but no value follows the left parenthesis. Edit your printer definition file and add a value between the parentheses in the generalized string. Error in column <column number> of line <line number> of printer definition file <filename>: Expected control character to follow ^. Your printer definition file contains a generalized string using ^, but no control character follows the ^. Edit your printer definition file and add a control character after ^. Error in column <column number> of line <line number> of printer definition 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.
2 130
Error in column <column number> of line <line number> of printer definition 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 the parentheses after the word control. Error in column <column number> of line <line number> of printer definition file <filename>: Box drawing string must be exactly one character long. Your printer definition file contains the box code string, but the drawing string specified between quotes is more than one character long. Edit your printer definition file, making sure that one and only one character is specified as a drawing string. Error in column <column number> of line <line number> of printer definition file <filename>: Expected string containing box drawing character. Your printer definition file contains the box code string, but no drawing string is specified. Edit your printer definition file and specify a drawing string. 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 following required word (one of horizontal, vertical, top, center, or bottom) is not specified. Edit your printer definition file and add the appropriate required word. Unexpected end of printer definition file. Oracle Reports was able to open your printer definition file, but an error occurred while reading it. Make sure you specified the correct printer definition file. Also, check the contents of the printer definition file. Edit the file if necessary.
REP1880
Cause Action
REP1881
Cause Action REP1882 Cause
2 131
Cant send output to printer. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Expected I after M. The M you entered in a format mask was not followed by I. The only token that begins with M is the MI token. If you want to use the MI token, enter an I after the M. If you want the character M to appear in your output, place it inside double quotes (). Otherwise, delete the M from Format Mask. Expected R after P. The P you entered in a format mask was not followed by R. The only token that begins with P is the PR token. If you meant to use the PR token, enter an R after the P. If you want the character P to appear in your output, you need to place it inside double quotes (). Otherwise, delete the P from Format Mask. 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. 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. 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. 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.
2 132
Invalid Destination Type <string>. Valid options: <option, option,...>. You entered an invalid Destination Type (e.g., batch, while running interactively). Retry the operation, entering one of the valid Destination Types listed. 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). Retry the operation, entering one of the valid Destination Types listed. The report definition was modified during the current run. No new pages will be generated. While previewing a report (using R25DES), you modified the reports definition (e.g., modified a query, added or deleted objects, etc.), and then returned to the Previewer and attempted to view additional pages. This is not allowed. Oracle Reports cannot guarantee that all of the information used at runtime is still present, so formatting is halted. 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. Error in column <column name> of line <line number> of printer definition file <filename>: Expected backspace or overstrike to follow hilight. The specified printer definition file contains the hilight setting, but the setting was not completed properly. Add either overstrike or backspace <sequence> after hilight. Error in column <column name> of line <line number> of printer definition file <filename>: Nonnumeric userdefined printer codes are not supported. The specified printer definition file contains a userdefined printer code that is not a number. Change the userdefined printer code to a number.
Action
2 133
Error in column <column name> of line <line number> of printer definition file <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. Conversion Error A conversion error occurred while executing R25MREP. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. PL/SQL compilation failed. In trying to migrate a report using R25MREP, Oracle Reports encountered a PL/SQL compilation error. Debug the PL/SQL in the report you are trying to convert. 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 is correct for that file or object. 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 is correct for that file or object. Number of Destination items must be zero or match number of Source items. In the Convert dialog box, or while using R25CONV, you specified a list of Destination items, but the number of items specified is greater than zero and does not match the number of Source items specified. To have Oracle Reports derive the Destination names from the specified Source names, leave Destination blank. Otherwise, make sure the number of Destination names specified matches the number of Source names specified. Note: If you use wildcards in the Source specification, make sure the number of Destination names matches the number of Source items in the expanded wildcard list.
REP1952 Cause
Action
2 134
User Exit error. An error occurred in the user exit. If you created the user exit, debug the code. Otherwise, contact your DBA. IAF GET: unknown column. You specified an unknown column name in your user exits IAF GET statement. Make sure you specify the name of a valid column the the IAF GET statement. IAF PUT: unknown column. You specified an unknown column name in your user exits IAF PUT statement. Make sure you specify the name of a valid column in the IAF PUT statement. Unable to find user exit. Oracle Reports could not find the user exit that it was supposed to run at this point. The most likely cause is that the name and/or location of the user exit code was not specified correctly. If you created the user exit, check to make sure you specified the name and location of the code correctly when installing it. Otherwise, contact your DBA. Warning Unable to retrieve PL/SQL source code of <object name>. You selected File>Administration>Report Doc to document one or more reports, but the RWEPLS user exit failed to retrieve the PL/SQL source code of an object. This is most likely an abnormal condition. Check the PL/SQL source code in the named object. For information, see Abnormal Conditions on page 1 3. IAF PUT: value of column <column name> was truncated. Your IAF PUT statement assigned a value to the named column, but the column was not wide enough to hold the entire value, causing it to truncate. Widen the column so that it is can hold the entire value. Calculation Manager error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
REP2004 Cause
Action
2 135
Calculation Manager: source column cannot use segmented memory. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Calculation Manager: computed column cannot use segmented memory. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Column <column name>: PL/SQL formula returned invalid value or no value. The specified formula column contains a PL/SQL function that does not specify a return value. Verify that the function includes a return statement for every code path. <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 ORACLE message, see the ORACLE7 Server Messages and Codes Manual. Error allocating SQLDA descriptor. <ORACLE message> This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error parsing the SQL statement. <ORACLE message> Oracle Reports encountered an error while parsing the SRW.DO_SQL statement. Refer to the ORACLE message to see why the SQL statement could not be parsed. Error describing bind variables. <ORACLE message> Oracle Reports encountered an error while describing bind variables in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the bind variables could not be described.
2 136
Error opening SQL cursor. <ORACLE message> Oracle Reports encountered an error while opening a cursor in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the cursor could not be opened. Error describing select list. <ORACLE message> Oracle Reports encountered an error while describing the select list in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the bind variables could not be described. Error fetching bind variables. <ORACLE message> Oracle Reports encountered an error while fetching bind variables in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the bind variables could not be fetched. Error fetching data record. <ORACLE message> Oracle Reports encountered an error while fetching a data record in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the data record could not be fetched. Error processing select list. <ORACLE message> Oracle Reports encountered an error while processing the select list in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the select list is invalid. Error formatting date field. <ORACLE message> Oracle Reports encountered an error while formatting a date field in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the date field could not format.
2 137
Error putting value into column. <ORACLE message> Oracle Reports encountered an error while trying to insert a value into a column in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the value could not be assigned. Error during Commit. <ORACLE message> Oracle Reports encountered an error while trying to do a commit in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the commit failed. Error allocating data record. <ORACLE message> Oracle Reports encountered an error while allocating a data record in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the record could not be allocated. Error parsing select list. <ORACLE message> Oracle Reports encountered an error while parsing the select list in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the select list could not be parsed. Error closing SQL cursor. <ORACLE message> Oracle Reports encountered an error while trying to close a SQL cursor in an SRW.DO_SQL statement. Refer to the ORACLE message to see why the close cursor operation failed. Error freeing data record. <ORACLE message> This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 the correct column name.
2 138
Value of column <column name> was truncated. A column value obtained via an SRW.DO_SQL statement was truncated. Go to the columns property sheet and increase its Width. Or, restrict the size of the value that your SRW.DO_SQL statement is putting into the column. Internal error starting Oracle Toolkit. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error initializing File Dialog. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error initializing printer information. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error starting Oracle Resource Manager. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error processing menu resource. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error processing window resource. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Resource File not found. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 139
Internal error starting Oracle Observer Model. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error initializing color table. Checking VGS resources is recommended. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Internal error initializing Oracle Image. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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: Case 2: Case 3: The image specified as the source is in an incorrect format. You are out of memory. This is an abnormal condition.
Action
You can take the following actions to correct this error: If Case 1: Ensure that the image file specified as the source of the button action is in a displayable format. If Case 2: Make more memory available, if you can, or ask your system administrator for assistance. If Case 3: For information, see Abnormal Conditions on page 1 3.
REP3082 Cause
Error running sound dialog. You selected a Previewer button with a defined action of playing a sound, but the sound dialog is unavailable. Possible causes of this error include: Case 1: Case 2: Case 3: The sound file specified as the source is in an incorrect format. You are out of memory. This is an abnormal condition.
2 140
Action
You can take the following actions to correct this error: If Case 1: Ensure that the sound file specified as the source of the button action is in a playable format. If Case 2: Make more memory available, if you can, or ask your system administrator for assistance. If Case 3: For information, see Abnormal Conditions on page 1 3.
REP3083 Cause
Error running video player. You selected a Previewer button with a defined action of playing a video, but the video player is unavailable. Possible causes of this error include: Case 1: Case 2: Case 3: The video file specified as the source is in an incorrect format. You are out of memory. This is an abnormal condition.
Action
You can take the following actions to correct this error: If Case 1: Ensure that the video file specified as the source of the button action is in a playable format. If Case 2: Make more memory available, if you can, or ask your system administrator for assistance. If Case 3: For information, see Abnormal Conditions on page 1 3.
REP3085 Cause
Multimedia source file <filename> not found. You activated the button in the Previewer, but the source for the buttons intended action (whether sound, image, or video) cannot be found or 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. Bad multimedia source file. You activated the button in the Previewer, but the source for the buttons intended 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, check the file itself.
Action
2 141
ImageViewer not supported on this configuration. Your platform and/or configuration will not support displaying images via the ImageViewer. No action is necessary. Sound not supported on this configuration. Your platform and/or configuration will not support playback of sound files. No action is necessary. Video not supported on this configuration. Your platform and/or configuration will not support playback of video files. No action is necessary. Matrix must include at least 1 Down and 1 Across repeating frame. You tried to create a matrix (using Tools>Create Matrix) without the proper objects selected in the Layout editor. A matrix layout requires that at least one group have a repeat direction of Down and one have a repeat direction of Across. Select two repeating framesone Down, one Acrossthat overlap, then choose Arrange>Create Matrix. All selected Down and Across repeating frames must be nested. You tried to create a matrix (using Arrange>Create Matrix) and the Down and Across repeating frames were not properly overlapping and nested. Make sure the selected Down and Across repeating frames are properly overlapping and nested before creating the matrix. Anchors, matrices, and margins cannot be grouped. You chose Arrange>Group and at least one of the objects selected was an anchor, matrix, or margin. Deselect all anchors, matrices, and margins before grouping objects.
Action
2 142
REP3103 Cause
Only text and graphical boilerplates can be rotated. You attempted to rotate either a frame, a field, a margin, an anchor, a matrix object, a piece of external boilerplate, an Oracle Graphics display, an OLE2 object, 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 the text of boilerplate text that is rotated. Anchors and matrices cannot be scaled separately. You attempted to scale one of the layout objects listed above without also scaling its associated object. This is not allowed. Select at least one associated object (anchoring object for anchors, repeating frames for matrices), then retry the scaling operation. 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, you must also specify Display Columns. Specify Display Columns or remove the value from Display Query. 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 Display Column but did not enter the name of a Display Query. Enter the name of the display query to which you intend to pass data. Object <object name> cannot be moved in front of its child. Operation disallowed. You tried to move a layout object in front of one or more of its own child objects. If you still want to move the layout object, toggle Confine mode off, then move it. Otherwise, no action necessary.
Action
REP3105 Cause
2 143
Object <object name> cannot be moved behind its container. Operation disallowed. 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 move it. Otherwise, no action necessary. 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 operation would have violated container constraints (i.e., moved a field outside of its enclosing frame). Select Edit>Undo to ensure your layout is the same as before the attempted operation. Then you can either resize or reposition the container in question to enable you to perform the operation, or do nothing. Warning: Same size operation failed because of container constraints. Undo changes to revert to the original state. You tried to change one or more layout objects to the same size, but the result of such an operation would have violated container constraints (i.e., enlarged a field beyond its enclosing frame). Select Edit>Undo to ensure your layout is the same as before the attempted operation. Then, you can either resize or reposition the container in question to enable you to perform the operation, or do nothing. Changing the border width of <object name> violates the constraints of Confine mode. Operation disallowed. You tried to change the border width of an object such that the result would have violated container constraints (i.e., widening the border of a boilerplate object so that it extended beyond its enclosing frame). No action necessary. Parameter form fields and images cannot be rotated. You tried to rotate one of the parameter form objects listed above. This is not allowed. You can rotate any boilerplate objects, except images, in the Parameter Form editor. Depending on your operating system, you may or may not be able to see the text of boilerplate text that is rotated.
REP3109 Cause
Action
REP3110 Cause
Action
REP3111 Cause
2 144
Parameter form boilerplate text cannot fit on the page. You entered text in the Title, Hint, Status, or Label field in the Default Parameter Form property sheet that is too long to fit on the page. Reduce the length of the appropriate text field. Program unit editor internal error. Could not get application handle. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. One editor must remain open for each report. You attempted to close all three of the editors (Data Model, Layout, and Parameter Form) for a report. You must leave at least one editor open. Leave one editor open for each report. Invalid width for column <column name> cannot be highlighted, since group <group name> is not selected. An invalid value was entered for the Width of a column in the Default Layout dialog box. Since the group that owns the column is not selected, the column is not listed. Select the group that owns the column. Scroll down to the column and enter a valid value for Width. Data link, anchor, or polygon creation must be completed in the editor before this action. You tried to perform some action (e.g., close the report) before finishing the creation of a data link in the Data Model editor, an anchor in the Layout editor, or a polygon in the Layout editor or Parameter Form editor. Complete the unfinished object before continuing. 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.
Action
REP3152 Cause
2 145
REP3154 Cause
Insufficient resources to create module. There were insufficient resources available to create the requested module (report, external query, external PL/SQL library. You probably selected File>New, File>Open..., or File>Revert. Make more resources available by closing windows or other applications. Concurrent previewer actions not allowed. You are attempting to activate more than one button at one time, in either the same or multiple Previewers. For example, you may be trying to both play a sound and display a video at the same time. This is not allowed. Only activate one button at a time. Fatal error in <component name>. Returning to the event loop. <product code><number>: <product error>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error occurred in <component name>. Returning to the event loop. <product code><number>: <product error>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Fatal error occurred during Quit. Exiting Oracle Reports. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal CA Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal UI Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action REP3300 Cause Action REP3301 Cause Action REP3302 Cause Action REP03335 Cause Action REP03350 Cause Action
2 146
Undefined failure in UI. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error in UI. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to create with an attribute that is not creatable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to set with an attribute which is not settable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to set with an attribute which is not gettable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to set/get an unknown attribute. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to set attribute values which are conflicting. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to set an attribute to an outofrange value. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 147
This function call is out of context. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The view class does not support being a scrollee. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. This function call provokes an illegal recursion. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The internal mpi allocator failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The clientsupplied memory allocation functions failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to support an unsupported function. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. An attempt to set attributes out of context. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. An attempt to perform an illegal operation on a root view. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 148
One of the parameters to the functions is out of range. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The connection to the windowing system failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The connection to the windowing system has been broken. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The windowing system failed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. uiER_CL_FORMAT_UNAVAILABLE This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. uiER_CL_FORMAT_UNREGISTERED This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Operation was timed out. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. uiER_NOT_FOUND This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 149
REP03375 Cause Action REP03376 Cause Action REP03377 Cause Action REP03378 Cause Action REP03379 Cause Action REP03380 Cause
uiER_ILLEGAL_TOPITEM This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. uiER_SE_BAD_FORMAT This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The view class does not support the scroller interface. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Attempt to remove a readshare color from a palette. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unable to create window. Oracle Reports was unable to create a window. It could be that you have too many reports or windows open, and lack of memory resources. Close some reports and windows. Unable to create view. Oracle Reports was unable to create a view. Possible causes of this error include: Case 1: Case 2: You may have too many reports or windows open, and lack memory resources. The environment variable NLS_LANG in oracle.ini may be set to something other that american_america.WE8ISO8859P1. Other settings for this variable are not supported.
Action
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.
2 150
Unable to create color palette. Oracle Reports was unable to create a color palette. It could be that you have too many reports or windows open, and lack of memory resources. Close some reports and windows. Unhandled Internal DE Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal SRW Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal HH Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid attribute value. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid context. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Specified word not found. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Link to external document. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 151
Help session is null. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Document is not a help document. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Document revision is newer than help. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Specified attribute is not settable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Specified attribute is not gettable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Invalid data link. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Logical attributes missing or bad. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. NLS language string missing or bad. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 152
No search string specified. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. String begins with percent sign. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unknown toolkit error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unknown object store error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Out of memory. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unknown Resource manager error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal REM Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal VGS Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 153
Unhandled Internal UT Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unhandled Internal ZOM Error. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Both module nodes and nonmodule nodes selected. Please select only nodes from one of these types of nodes. You have chosen Navigator>Delete but both object nodes and module nodes are 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 close modules, deselect all object nodes. Then select Navigator>Delete again. Error occurred in the OLE subsystem. An unspecified OLE2 error occurred during initialization. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: Case 2: Case 3: Your OLE2 server is not functioning correctly. An error occurred during installation of Oracle Reports and the OLE2 functionality did not install correctly. This is an abnormal condition.
REP4001 Cause
Action
You can take the following actions to correct this error: If Case 1: Refer to the OLE2 server documentation for more information. If Case 2: Reinstall Oracle Reports. If Case 3: For information, see Abnormal Conditions on page 1 3.
REP4002 Cause
Error occurred while initializing OLE subsystem. An error occurred during initialization of OLE2 libraries. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: Case 2: Your OLE2 server is not functioning correctly. An error occurred during installation of Oracle Reports and the OLE2 functionality did not install correctly.
2 154
Case 3: Action
This is an abnormal condition.
You can take the following actions to correct this error: If Case 1: Refer to the OLE2 server documentation for more information. If Case 2: Reinstall Oracle Reports. If Case 3: For information, see Abnormal Conditions on page 1 3.
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. Error occurred while restoring OLE object. You were attempting to restore an OLE2 object when an OLE error occurred. Refer to the accompanying OLE2 error message for more information. Error occurred while saving OLE object. You were attempting to save an OLE2 object when an OLE error occurred. Refer to the accompanying OLE2 error message for more information. Error occurred while performing Cut/Copy operation. OLE object is not placed in the clipboard. You were trying to cut or copy an OLE2 object when an OLE error occurred. Refer to the accompanying OLE2 error message for more information. Error occurred while pasting OLE object from the clipboard. You were trying to paste an OLE2 object from the clipboard when an OLE error occurred. Refer to the accompanying OLE2 error message for more information. Error occurred while trying to perform operation defined by OLE object. You were trying to perform an action normally supported by the OLE2 server when an OLE error occurred. Refer to the accompanying OLE error message for more information.
2 155
Error occurred while trying to activate OLE object. You were trying to activate an OLE2 object (e.g., doubleclick on it in the Previewer) when an OLE error occurred. Refer to the accompanying OLE2 error message for more information. Conversion of OLE object to a different type failed. You were trying to convert an OLE2 object contained in a piece of boilerplate to an OLE2 object of a different type when an OLE error occurred. This indicates a problem with the OLE2 server. Check that the object is correctly installed and reinstall, if necessary. Microsoft Object Linking and Embedding is not supported on this platform. You are running a report that was created on a platform supporting OLE2, and created with OLE2 objects, but you are now running it on a platform that does not support OLE2. You are trying to access the visual representation of what was once an OLE2 object. No action is necessary. Remove the object if desired. Wrong version of OLE libraries. OLE functionality will be disabled. The OLE2 libraries installed on your machine are incompatible with those supported by your version of Oracle Reports. As Oracle Reports cannot guarantee that your OLE2 support will function, it is disabling OLE2 functionality. Install the correct libraries. There is insufficient memory available to complete operation. There is not sufficient memory remaining on your system to perform the desired action. Exit any unnecessary applications that are running. If that does not work, see your Microsoft documentation for suggested procedures to enhance memory usage. DOS SHARE services required for successful operation. SHARE is not running. The DOS SHARE utility is required, but SHARE is not running. Make sure SHARE is running
2 156
Read failure. Data cannot be read from the specified device. Check the device to determine if it is malfunctioning, and, if so, consult the device documentation to determine the proper error recovery procedures. Write failure. Data cannot be written to the specified device. Check the device to determine if it is readonly. If not, consult the device documentation to determine the proper error recovery procedures. 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 reserve either two or three file handles per object and so you may have more files open than you are aware. No space left on device. The specified device is full. Delete unnecessary data or write to a different device. Failed to obtain presentation of the OLE object. Cannot render an OLE object. You tried to display an OLE2 object in a report but the display aspects defined by the OLE2 server were unavailable. Verify that the OLE2 object has not been corrupted and that the server is correctly installed. Reinstall if necessary. Failed to restore original display aspects of the OLE object. Object content will be used. You tried to display an OLE2 object in a report but the display aspects defined by the OLE2 server were corrupted or stored in the database and could not be restored. Oracle Reports will display the object using the default aspect. Verify that the OLE2 server is correctly installed. Reinstall if necessary.
REP4030 Cause
Action
2 157
REP4031 Cause
The server application cannot be found. Make sure the application is properly installed and registered correctly. You are attempting to access an OLE2 server via an OLE2 object, but the server is currently inaccessible. The server may have been deleted, renamed, or manually reinstalled in a different location. Check the installation of the server and reinstall if necessary. Cannot connect to the linked OLE object source. Make sure that link source has not been moved, renamed, or deleted. Oracle Reports is trying to connect to the specified source of the OLE2 object boilerplate but cannot. Verify that the OLE2 object source has not been moved or deleted, and that its filename has not been changed Cannot connect to the linked object source, because it is across a network that is not connected to this machine. You are trying to link to an OLE2 object that is stored on a device to which you do not currently have an established network connection. Establish a connection to the proper device. 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. A share violation has occurred while performing operation on OLE object. Possible causes: you are trying to link to the same file via multiple OLE2 objects, or trying to access the same temporary file via different applications. Make sure that you do not have multiple OLE2 objects attempting to access the same file at the same time. Also, check the intallation of your OLE2 server. 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.
2 158
File operation on OLE object failed because disk is writeprotected. You tried to save to file an OLE2 object but could not because the disk is writeprotected. Save the object to a disk for which you have write priviledges, if possible. If not, no action is necessary. Unexpected error occured in the file system while performing operation on OLE object. A nonspecific file error such as a corruption of the hard disk occurred. Refer to your operating system documentation more information. Unexpectied error returned by OLE. A nonspecific OLE error occurred. Refer to your Microsoft documentation for more information. Incorrect or corrupted OLE object persistent data. OLE object cannot be restored from this data. The information used by the OLE server to restore the OLE2 object in your report is incorrect or has been corrupted. Possible causes for this error include: Case 1: Case 2: If boilerplate, the file has become corrupted. If field, either the database has been corrupted, or the LONG RAW column referenced does not contain OLE2 objects.
Action
You can take the following actions to correct this error: If Case 1: Verify that the object is viable by embedding it in a container using another application. If Case 2: Use SQLPlus to check the table in the database and verify the contents of the column.
REP4041 Cause
No operations defined on this object or object is static. You tried to take some action on an OLE2 object but no actions have been defined as applying to the object. Possibly the object was converted to a static bitmap. No action necessary.
Action
2 159
REP4042 Cause
Requested action on OLE object is valid, but cannot be performed at this moment. Object server may be busy. You tried to take a valid action on an OLE2 object but cannot, due to lack of server resources. A possible cause is that you are trying to open a second instance of a singleinstance application. Check system resources (memory, etc.) and increase where possible, or try the operation later. 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. Reinstall if necessary. Can not access system registry. Make sure you have enough free system resources and registry is not corrupted. A read or write operation in the system registry failed. Consult your Microsoft documentation. Problem occurred in the system registry. Make sure the object server is properly installed. Some information about the server is missing from the registry. Make sure the OLE server is installed correctly. Reinstall if necessary. Warning: Do you wish to save the current module before disconnecting from the database? You have an open module that is stored in the database. If you disconnect from the database, you will not be able to save your changes to the database. Select Yes to save the module before disconnecting from the database; the module remains open so you can reconnect if desired and save it to the database again. Select No to disconnect from the database without saving the module; the module remains open. Select Cancel to remain connected to the database without saving; once again, the module remains open.
Action
2 160
Printer changed while previewing. Printer font remapping could cause truncation. Continue with printing? In the time between running the report and selecting Print from the Previewer your default printer has changed. Select Yes to print anyway. Select No to halt printing, then close your report and either reset your printer and run your report again, or simply run it again to format it for the current printer. Report was not run with DESTYPE=PREVIEW. Screen font remapping could 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 more accurate view of your reports printed output. Select Yes to print anyway. Select No to halt printing. Then close your report and run it again while specifying Preview to format it for the printer. 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 the version used to create the report. If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report. If you are concerned about losing functionality, do not open the report until you have upgraded to the most recent version of Oracle Reports. 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 before creating a layout. Create a layout, then run your report. The region you have chosen for your default layout is too small. Extend region to page boundaries? You used the Additional Default Layout tool from the Tool palette to draw a region for a layout that was not large enough to accommodate the settings specified in the Default Layout dialog box. Either select Yes to have Oracle Reports extend the possible range of the layout to the boundaries of a report page, or select No and change the settings in the Default Layout dialog box to shrink the size of the layout.
REP20128 Cause
Action
REP20129 Cause
Action
Action
2 161
REP20150 Cause
Warning: Page width of report <report name> changed to fit the font for a character cell. Might be a consequence of fontmapping. A character font has been substitited for a bitmapped font in the report you opened, and the page width has been adjusted accordingly. A possible cause: a bitmapped report is being opened in the charactermode runtime engine. If you want the font mapped to a specific font, edit the uifont.ali file to map the fonts to the desired ones. Otherwise, no action is necessary. Warning: some fonts have been changed according to the mapping in uifont.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 the fonts to the desired ones. Otherwise, no action is necessary. 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 or more reports are still executing or awaiting execution. If you want your reports to finish executing, cancel the operation. Otherwise, accept the warning dialog. Cannot exit Windows when this program is running. Close Reports Server and exit Windows. Oracle Reports Server requires Windows, but you have specified that you want to exit Windows while the Server is still running. Exit the Server before exiting Windows. Converting <source name> to <destination name> failed. The most likely cause of this error is that the source type you specified was incorrect. Ensure that the source file is of the specified source type.
Action
2 162
REP25207 Cause
Invalid conversion: stype and dtype are not of the same document type. You attempted to convert a document of one type to another typei.e., you attempted to convert one of the possible report files to a PL/SQL file, or vice versa. Ensure that the source and destination of your conversion are the same type of document. Cannot locate <user exit .DLL file>. Your report attempted to execute a user exit, but the user exit .DLL file could not be located. This file typically resides in:

Action
REP25401 Cause
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. Internal error Cannot locate <function name> within <user exit .DLL file>. Your report attempted to execute a user exit, but certain functions used to locate and execute user exits cannot be located in the user exit .DLL file. This means that the user exit .DLL was built incorrectly, because these functions are located in a .OBJ file shipped with Oracle Reports, which should always be linked into the user exit .DLL. Rebuild the specified user exit .DLL correctly. An unknown MOVEREP error occurred. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot open rw.log. You specified LOGFILE=filename on the command line, but the file filename could not be opened for writing. Specify another filename in a writable directory.
2 163
Not enough memory available. R25MREP cannot access sufficient memory from the system to complete this task. Make more memory available, if you can, or contact your system administrator for this machine. Abnormal condition: Error while freeing memory. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Field table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Summary table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Text table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Foreign Key table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 164
You cannot execute this report because it does not have queries, groups or fields. 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 the Query Screen by pressing [Q], or by moving the highlight to Query and selecting this item. Enter a name for a query, press [Next Field], then enter a valid SQL SELECT Statement. You can now execute the report by pressing [Menu], [A] (for Action), [E] (for Execute), and [Select]. By default, the output will appear on your screen. Error while matching field <field name> to its group. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Text <text screen> exceeds 10 panels (the maximum allowed). If SQL*ReportWriter produced the report as it is currently defined, it would have to create more than ten panels. Ten, however, is the maximum allowed in any report. There are many ways to reduce the number of panels, such as decreasing the width of fields and summaries, deleting panels or moving fields closer together, etc. Consider the field identified in the error message when estimating how close you currently are to the 10panel maximum. Estimate how close this field is to the end of the report, then take one of the above actions to decrease your report by the necessary amount. Text <text screen> exceeds 10 pages (the maximum allowed). If SQL*ReportWriter produced the report as it is currently defined, it would have to create more than ten pages. Ten, however, is the maximum allowed in any report. There are many ways to reduce the number of pages, such as decreasing the width of fields and summaries, deleting panels or moving fields closer together, etc. Consider the field identified in the error message when estimating how close you currently are to the 10page maximum. Estimate how close this field is to the end of the report, then take one of the above actions to decrease your report by the necessary amount.
Action
REP26417 Cause
Action
2 165
Abnormal condition: The Type for text <text screen> is not in SQL*ReportWriters tables. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Text <text screen> cannot be matched to a SQL*ReportWriter object. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: The group Type for text <text type> is not in SQL*ReportWriters tables. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Foreign keys in SQL*ReportWriters tables cannot be joined. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Summary <summary name> cannot be processed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. ORACLE error occurred during logon. You invoked an Oracle Reports executable (R25MREP, R25CONV, etc.) and an ORACLE error occurred when Oracle Reports attempted to logon to ORACLE. Rerun the executable. If this error occurs repeatedly, contact Oracle Customer Support for assistance. ORACLE error occurred during logoff. You invoked an Oracle Reports executable (R25MREP, R25CONV, etc.) and an ORACLE error occurred when Oracle Reports attempted to logoff of ORACLE. Rerun the executable. If this error occurs repeatedly, contact Oracle Customer Support for assistance.
2 166
Abnormal condition: ORACLE error occurred while attempting to access the Report ID. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: Objects name is not in SQL*ReportWriters tables. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Text cannot be joined to a valid Object. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Parameter table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Text Long table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The report named <report name> cannot be found in SQL*ReportWriters tables. You attempted to open a report that is not stored in the SQL*ReportWriter tables. Specify the correct name of the report, or load the report into the tables. The report named <report name> already exists in SQL*ReportWriters tables. You attempted to load into the SQL*ReportWriter tables a report that already exists there. Rename or drop the report stored in the SQL*ReportWriter tables, then load the report into the tables.
2 167
ORACLE error in processing query. A query in your report cannot be parsed correctly. Correct the query in your report. Not enough memory available for ORACLE to process a SQL*ReportWriter query. ORACLE cannot access sufficient memory from the system to finish querying SQL*ReportWriters tables. Make more memory available, if you can, or contact your system administrator for this machine. There are duplicate panel numbers defined for text <text object>. All panels that belong to a particular text Object and Type must have unique numbers. You may have mistyped the panel number. Use [Insert Record Above] or [Insert Record Below] and enter the panel number you wish. This will automatically renumber the existing panels. Abnormal condition: Error occurred while processing text highlighting characters. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. ORACLE error occurred while trying to lock the SQL*ReportWriter tables. You attempted to logon to ORACLE or lock the SQL*ReportWriter tables under the same username/password as another user, while the other user held an exclusive lock on the SQL*ReportWriter tables. Wait for ORACLE to release the other users locks on the SQL*ReportWriter tables before attempting to access them. Abnormal condition: Invalid text Type for <text screen>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
Action
2 168
REP26438 Cause
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 invalid objects might include: Case 1: Case 2: Case 3: Case 4: A Page Header or Page Footer. A group that falls in a different path of the query structure than the fields own path. A nonbody group object in the same group as the field. For noncomputed fields, the body of a higher group.
Make sure none of the above circumstances apply to your report. The frequency of summary <summary name> in text <text screen> is inconsistent. You referenced the summary in a text object where it is not allowed. These invalid objects might include: Case 1: Case 2: Case 3: Case 4: A group that falls in a different path of the query structure other than the summarys own path. A Title or Trailer Page, Report Header or Footer, or Page Header or Footer whose Print Condition is not Report. The group footer of the field being summarized, if the summary uses a running function. In a matrix report, a group footer belonging to the same group where the summary is referenced in a sub_footer.
Reference this field in a valid text object. Abnormal condition: a fields Data Type has been changed to an invalid value in SQL*ReportWriters tables. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 to more columns than can fit between the report margins.
2 169
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 in this text object. Edit the text object itself; reduce white space, use more lines, etc.
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 to more 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.
Group <group name> on panel <panel number> does not fit within the Width of the report. The boilerplate text and field/summary references in this group text adds up to more 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 in this group text. Edit the group text: reduce white space, use more lines, delete text, or remove field and summary references.
Abnormal condition: Invalid Relative Position for group <group name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: Group <group name> cannot be processed. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 170
Field <field name> on Panel <panel number> does not fit within the Height of the report. The positioning of fields and text on this panel has taken up so much room that there 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. Field <field name> on Panel <panel number> does not fit within the Width of the report. The positioning of fields and text on this panel has taken up so much room that there 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. This report exceeds the limit of 10 panels. The problem occurred while processing 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 the width of fields and summaries, deleting panels or moving fields closer together, etc. Consider the field identified in the error message when estimating how close you currently are to the 10 panel maximum. Estimate how close this field is to the end of the report and take the desired steps to reduce the number of panels a sufficient amount. Abnormal condition: Encountered invalid key while processing a summary. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: Invalid text Justification for <text screen>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: The reset level of field <field name> cannot be lower than its print level. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 171
Abnormal condition: The reset level of summary <summary name> cannot be lower than its print level. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Group <group name> on panel <panel number> does not fit within the Height of the report. The size of each group text object is all right, but, taken together, they exceed the Page Height. Increase the Page Height on the Report Screen, or reduce the size of one or more texts belonging to this group. 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 exceed the Page Height. Increase the Page Height on the Report Screen, or reduce the size of one or more texts belonging to this matrix group. 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 exceed the Page Width. Increase the Page Width on the Report Screen, or reduce the size of one or more texts belonging to this matrix group. A matrix report cannot have multiple panels. You defined more than one panel for this matrix report. Delete the extra panels. The matrix does not fit between the margins of the report. The Page Header and Footer plus the Report Header and Footer exceed the Report Height or the Report Width, or the top margin plus the bottom margin equals the Report Height on the Report Screen. Decrease the margins or increase the page size on the Text Screen, or decrease the size of the matrix.
Action
2 172
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 decrease the size of other text objects. The Report Header or Footer does not fit between the margins of the report. These text objects are too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Title Page does not fit between the margins of the report. The Title Page is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Trailer Page does not fit between the margins of the report. The Trailer Page is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Page Header does not fit between the margins of the report. The Page Header is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Page Footer does not fit between the margins of the report. The Page Footer is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Report Header does not fit between the margins of the report. The Report Header is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects.
2 173
The Report Footer does not fit between the margins of the report. The Report Footer is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Header of group <group name> does not fit between the margins of the report. This group header is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Column Heading of group <group name> does not fit between the margins of the report. This column heading is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Body of group <group name> does not fit between the margins of the report. This group body is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. The Footer of group <group name> does not fit between the margins of the report. This group footer is too large, spanning beyond the reports margins. Decrease the margins or increase the page size on the Text Screen, or decrease the size of other text objects. Abnormal condition: Invalid frequency group for text <text screen>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 174
REP26471 Cause
Summary <summary name> on panel <panel number> extends beyond the left margin of group <group name>. The width of this summary is greater than the width between the right and left margins of the group. Since this summary is either center or rightjustified, SQL*ReportWriter would encounter the left margin while printing it. Decrease the margins of that panel or increase the groups margin, or decrease the summarys width. Summary <summary name> on panel <panel number> extends beyond the right margin of group <group name>. The width of this summary is greater than the width between the right and left margins of the group. Since this summary is either center or leftjustified, SQL*ReportWriter would encounter the right margin while printing it. Decrease the margins of that panel or increase the groups margin, or decrease the summarys width. Abnormal condition: The Align setting for a field is not Left, Right, Center, Wrap, or Variable. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Query <query name> cannot have more than one parent because this is not a 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, or make this a matrix report. Text <text screen> cannot contain a &CR because it has no fields with variable Alignment. Carriage returns (created by embedding &CR in the text) are only allowed in text 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 a hard return, or change the Align setting for one of the fields to Variable.
Action
REP26472 Cause
Action
2 175
Query <query name> cannot reference Field <field name> because the field 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, the group that is created by the query. Press [List] and select a Reset Group for the field you wish to reference at or above the group created by the query. 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 to reference that is at, or above, the group that is created by the query. Field <field name> cannot contain a compute function because its Source is a 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 Summary on a field that has a Source of a user exit. Query <query name> cannot reference a Field (<field name>) that belongs to 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 the right 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 the reference to. Query <query name> cannot reference Summary <summary name> whose Field 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 to the right 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 the reference to.
REP26477
Cause Action
2 176
Query <query name> cannot reference a Field (<field name>) that resets at PAGE. 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. 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. Query <query name> cannot reference a Field (<field name>) with Source of &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. Matrix query <query name> cannot reference a Field or Summary because it is not the cell group query. You can only reference fields or summaries in a query if the querys default group has a Print Direction of Crosstab. Add the field or summary you wish to reference to the Query that has a default group with a Print Direction of Crosstab. Query <query name> cannot have a parent query with no associated group. You created a parentchild relationship between two queries on the Query Screen and then removed the group associated with the parent query on the Group Screen. Create a group on the Group Screen for the parent query and associate it with the query. Field <field name> cannot reset at Page and be referenced in variable length text object <text screen>. You set the Reset Group for the computed field to PAGE, but the computed field is set to print in a text object that contains a field or summary with a Wrap or Variable alignment. Create a summary of the field and place it in the Page Header or Page Footer of the report.
REP26485 Cause
Action
REP26486 Cause
Action
2 177
REP26487 Cause
Summary <summary name> cannot reset at Page and be referenced in variable length text object <text screen>. You set the Reset Group for the summary field to PAGE, but the summary is set to print in a text object that contains a field or summary field with a Wrap or Variable alignment. Create a summary of the summary field and place it in the Page Header or Page Footer of the report. 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 tried to create the user exit. Specify a valid user exit name after the # in the Source. Field <field name> cannot be printed at a higher group. A field cannot print in a higher group because it could possibly have multiple values, and SQL*ReportWriter would not know which one to print. Exceptions include calculated fields that would have a single discrete value if printed in the higher group. Delete the field references on the Text Screen from the group texts that are higher than the fields own group. 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 fields Reset Group. It does not make sense for the calculated fields accumulator to reset more often than the field actually prints. Reference this calculated field in a text object that is at the same level or lower than the Reset Group. Field <field name> cannot reset at a lower level than its logical group. The calculated fields Reset Group is lower than the group that the field belongs to. Make the Reset Group the same level or higher than the fields group.
Action
Action
REP26490 Cause
Action
2 178
Field <field name> cannot reset at a lower or equal level than its print level. The calculated field appears in a text object that is higher or at the same level as the fields Reset Group. Reference this calculated field in a text object that is lower than the Reset Group. Field <field name> cannot reset at a lower or equal level than its logical group. The calculated fields Reset Group is lower or at the same level as the group that the field belongs to. Make the Reset Group higher than the fields group. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Report table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Group table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: ORACLE error occurred while querying SQL*ReportWriters Query table. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 179
REP26408 Cause
The columns in query <query name> are not currently available. Your query defines a SELECT Statement that uses proper SQL syntax, but it references columns that no longer exist in the database. The columns existed when SQL*ReportWriter initially validated the SELECT Statement, but they are no longer accessible. First confirm that you are logged on to the correct database. Then check your database 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 the column definitions are still the same. You can also modify the SELECT Statement, if appropriate. Abnormal condition: Error describing query <query name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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. 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 the summarys Reset Group. Reference this summary in a lower group, or make its Reset Group higher. Summary <summary name> cannot reset at a lower level than its logical group. The summarys Reset Group is lower than the group that the field being summarized belongs to. Reference this summary in a lower group, or make its Reset Group higher. Summary <summary name> cannot reset at a lower or equal level than its print level. This summary appears in a text object that is higher than the summarys Reset Group. Reference this summary in a lower text object, or make its Reset Group higher.
Action
2 180
Summary <summary name> cannot reset at a lower or equal level than its logical group. The summarys Reset Group is lower or at the same level as the group that the field being summarized belongs to. Reference this summary in a lower group, or make its Reset Group higher. The Source and the group for field <field name> cannot belong to queries in different paths. There is an inconsistency between the Source column for this field and the fields group. The fields Source column must be from a query that is in the same path (of the query structure) as the field. The fields path is determined by the fields group. In turn, the groups path is determined by the groups query. 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. Field <field name> references an unknown Source. The Source for this field is currently undefined. This might result from a database link being missing, the underlying table definition changing, or any other reason that prevents SQL*ReportWriter from locating the Source originally referenced. Either define this field in a valid way, or delete the field from your report definition. Field <field name> references a Source whose query, <query name>, has no groups. A fields Source must contain a group name that belongs to a query. You deleted a group that belonged to a query, but that group name is still in the Source column of the field in the error message. Delete the fields Source, and select a valid Source from the list of values. Field, summary, or parameter referenced by query <query name> no longer exists. You deleted a field, summary, or parameter and you did not remove it from the query. Delete the field, summary, or parameter from the query named in the error message. If you do not know which reference needs to be deleted, look at the fields, summaries, and parameters that are found on their respective screens.
Action
REP26500 Cause
Action
REP26501 Cause
2 181
Abnormal condition: incorrect source information for field <field name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 move to the Query Screen and add or rename an appropriate query. Field <field name> references an unknown query. The query associated with the Source column on the Field Screen for this field is not defined. Move to the Field Screen and identify a valid Source, or move to the Query Screen and add, edit, or rename an appropriate query. 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 Group Screen and add or rename an appropriate group. Field <field name> references an unknown reset group. The reset group associated with the computed field on the Field Screen is not defined. Move to the Field Screen and identify a valid reset group, or move to the Group Screen and add or rename an appropriate group. 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 Field Screen and add or rename an appropriate field.
2 182
Summary <summary name> references an unknown print group. The print group associated with the summary on the Summary Screen is not defined. Move to the Summary Screen and identify a valid print group, or move to the Group Screen and add or rename an appropriate group. Summary <summary name> references an unknown reset group. The reset group associated with the summary on the Summary Screen is not defined. Move to the Summary Screen and identify a valid reset group, or move to the Group Screen and add or rename an appropriate group. 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 that matches the name in Parent Query. Text <text screen> references an unknown frequency group. The group identified in Frequency on the Text Screen for this text object is not defined on the Group Screen. Move to Frequency on the Text Screen and identify a valid frequency group, or move the Group Screen and add or rename an appropriate group. ParentChild Relationship <query name> references an unknown item. The item referenced by the foreign key is not defined. Reference a valid item. ParentChild 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 Parent column of the Foreign key in question, and select a parent from the list.
2 183
ParentChild Relationship <query name> has an invalid child column position value. The child column position value referenced by the foreign key is not valid. Reference a valid value. ParentChild Relationship <query name> has an invalid parent column position value. The parent column position value referenced by the foreign key is not valid. Reference a valid value. Abnormal condition: Group order for group <group name> outside of a valid range. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter destype is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter desname is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter desformat is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter copies is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: SQL*ReportWriter objects have duplicate item IDs. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 184
Summary <summary name> cannot reference a field with Data Type of PRT. 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. 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. Abnormal condition: System parameter currency is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter thousands is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Abnormal condition: System parameter decimal is not included. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Summary <summary name> cannot compute Percent, Sum, or Average of a character 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.
2 185
Invalid specification for a matrix report. You used somebut not allof 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 3 groups (each from a different query), and all 3 groups must have an X in Matrix Group. One group must have DOWN for Print Direction, another group must have ACROSS and the third group must have CROSSTAB. If you do not want this to be a matrix report, remove the Xs from Matrix Group for all groups, and either change the Print Direction of the CROSSTAB group or delete it. This report includes both matrix and nonmatrix groups. Your report has at least one group where Matrix Group does not have an X, or at least one Print Direction of DOWN, ACROSS, or CROSSTAB is specified, but all three Print Directions are specified. If any group has an X in Matrix Group, then the report must have exactly 3 groups (each from a different query), and all 3 groups must have an X in Matrix Group. One group must have DOWN for Print Direction, another group must have ACROSS and the third group must have CROSSTAB. Abnormal condition: Invalid Print Direction for group <group name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. The Print Direction for group <group name> and another group is inconsistent. You have defined at least one DOWN (or DOWN/ACROSS) group and one ACROSS (or ACROSS/DOWN) group in this report. Make sure the Print Direction for all the groups in your report is DOWN (or DOWN/ACROSS) or all the groups are ACROSS (or ACROSS/DOWN). Abnormal condition: error message <message number> cannot be generated. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
REP26530 Cause
Action
2 186
Wrap fields and variable fields are not allowed in matrix, across, and across/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] and selecting one of the settings, or change the Print Direction for the group(s), by pressing [List] in the Print Direction entry field (on Group Screen One) and selecting DOWN or DOWN/ACROSS for the setting. Wrap fields and variable fields are not allowed in multipanel reports. You created a multipanel report that contains a Wrap and/or Variable field. Choose another Align setting for the Wrap or Variable field(s) (press [List] to see other Align settings that are available), or modify the text panels so that there is only one panel for each text Object and Type. Groups in a matrix report must reference unique queries. You specified the same query for at least two groups in a matrix report. A matrix report must have three queries and three groups, and each group must assigned to a unique query. Change the Query assignment for the groups so that all three assignments are unique. No report name specified on the command line. You invoked the R25MREP executable but did not specify any Version 1.1 reports to convert to Version 2.5. Reissue the command, remembering to specify the reports you wish to convert using the SOURCE keyword. No user id specified on the command line. You invoked the R25MREP executable but did not specify a username in the command string. Reissue the command, remembering to specify a username and password using the USERID keyword. Invalid keyword: <string>. You invoked the R25MREP executable with an invalid keyword. Reissue the command, specifying valid keywords.
REP26536 Cause
Action
2 187
Abnormal condition: Internal error while reading from SQL*ReportWriters V1.1 Rexfile. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot create loadfile <loadfile name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 containing SQL*ReportWriter V1.1 reports you wish to migrate to Oracle Reports. Error while closing loadfile. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Loadfile <loadfile name> is currently locked by another user. You attempted to migrate report(s) stored in a .rex file, but the .rex file you specified is currently locked by another user. Retry the operation once the user has unlocked the .rex file. Abnormal condition: Internal error on system initialization. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. This report is currently locked by another user. You attempted to migrate a report that is currently being modified by another user. Retry the operation once the user has saved and closed the report.
2 188
Unexpected Column Name encountered in srw_tables. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_fkey data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_field data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_param data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_query data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing expanded query data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_report data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing srw_ste data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 189
Unexpected error processing srw_summary data in the export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unexpected error processing export file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Error generating error message <string>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Not enough memory available. <Requestor> requested <number> bytes on allocate. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Not enough memory available. <Requestor> requested <number> bytes on reallocate. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unanticipated ORACLE error occurred: <component> <number> Routine: <routine name> This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Unanticipated internal error occurred: <component> Routine: <routine name>. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 190
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 retry the operation. Unable to display columns due to ORACLE error: This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. <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 the SQL*ReportWriter tables. Parameter <parameter name> has the same name as another object. One of your reports contains a userdefined parameter with the same name as a query, field, summary, or other report object. Rename the parameter and retry the operation. Parameter <parameter name> has the same name as a command line keyword. You attempted to define a parameter with the same name as an existing system parameter (e.g., DESTYPE, CURRENCY). Choose a new name for your parameter. 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. 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 appropriate symbols. For more information, see the ORACLE7 Server SQL Language Reference Manual.
2 191
ERROR: This report does not contain the data table information. A .rep file cannot be generated. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. 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 the same name as a report that already exists in the database. Rename the reports you wish to migrate, or assign them names that are different from existing reports. Moverep Error: No 1.1 report specified to move. You invoked the R25MREP executable but did not specify any Version 1.1 reports to convert to Version 2.5. Reissue the command, remembering to specify the reports to convert. 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 the correct name. Reissue the command. A fatal error occurred while creating a new report for <report name>. This is an abnormal condition. Check that your NLS_LANG and ORACLE_HOME environment variables are set to the correct values. (For more information, see your CDE2 Installation Guide. Also see National Language Support in Appendix C of the Reports Reference Manual.) Otherwise, see Abnormal Conditions on page 1 3. 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 shortening the name to a valid length. Note that this could possibly generate an invalid name. Change the name in the original SQL*ReportWriter report to less than 25 characters, or edit the converted Oracle Reports report after it is converted.
REP26791 Cause
Action
2 192
Unexpected error. Aborting. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Report already exists in NX file. You tried to overwrite an existing translation file. Choose another name for the translation file. Cannot initialize Reports system. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot initialize VGS system. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Fatal error loading report <report name>. Check version. The specified report cannot be loaded. Make sure youre opening the correct version of the report. Cannot open report file for reading. Report file is unreadable. Check the read permission of the report file. Cannot open <translation file> file for reading. The specified file cannot be opened. Make sure the file exists and is readable. NX Tree does not exist. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3.
2 193
Translations for that language do not exist. The Translation Manager cannot translate into the given target language. Make sure the target language is supported. This is not an Oracle Reports tree. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Source data file <file name> does not match. The translation file youre merging into the report was not created from the selected report. Merge the translation file into the original report. 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. Cannot find matching VGS string in NX file. This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Successfully merged strings for language <language name>. Operation was completed with no errors. No action is necessary. Merge operation failed. The merge operation encountered errors. Check the log file for more information. Cannot find translations in NX file. The translation file does not contain translated strings. Make sure youre using the correct translation file for the given report.
2 194
NX file is corrupt! This is an abnormal condition. For information, see Abnormal Conditions on page 1 3. Cannot open NX file for reading. Translation file cannot be opened. Make sure the file exists and is readable. Unable to unpack the data of image <image name>. The image has been removed. The image data is corrupted. Import the image again. Warning: Some text segments are missing. Text segments cannot be found for some boilerplate text. The report may be corrupted. Check the boilerplate text objects in the report. Remove suspicious ones and create replacements for them.
2 195
2 196
Readers Comment Form

Name of Document: Reports Messages and Codes Manual Part No. A324901 Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of 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 Manager Oracle Corporation 500 Oracle Parkway, Box 659412 Redwood Shores, CA 940655028 (415) 5067000 (415) 5067200 (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* *A32490-1*
A324901
Release 2.5

Oracle Reports Messages and Codes Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Reports Messages and Codes Manual

Uploaded by

Copyright:

Available Formats

Reports Messages and Codes Manual

Reports Messages and Codes Manual

Read This First

Read This First

Oracle Reports Documentation and Related Information

Reports Messages and Codes Manual

Oracle Reports Documentation

Read This First

How to Use this Book

Reports Messages and Codes Manual

UPPERCASE Initial Caps

Read This First

Your Comments Are Welcome

Reports Messages and Codes Manual

Oracle Reports Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1 Oracle Reports Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2

Reports Messages and Codes Manual

Coping with Messages

finding information about errors looking up messages

Finding Information about Messages

Reports Messages and Codes Manual

Abnormal conditions may arise from one of the following causes:

Calling Oracle Customer Support

Reports Messages and Codes Manual

The problem severity, according to the following codes:

name companys name companys ORACLE Support ID Number phone number

Oracle Reports Message Descriptions

Using this Section

Recognizing Embedded Variables

would appear in this section as:

Reports Messages and Codes Manual

Reports Messages and Codes Manual