1. Error Messages
  2. REP-00001 to REP-80012

28 REP-00001 to REP-80012

REP-00001
The Oracle Reports Builder message file cannot be found.
Category:
Other
Cause:
The file of error messages could not be opened or an internal error occurred while opening it.
Action:
Reinstall Oracle Reports Builder or contact Oracle Support Services for assistance.
REP-00002
The string from the message file cannot be retrieved.
Category:
Other
Cause:
Oracle Reports Builder could not retrieve the necessary error message or string.
Action:
For assistance, contact Oracle Support Services.
REP-00003
Global preference file cannot be opened.
Category:
Other
Cause:
The global preference file could not be opened. This is just a warning, so the product will continue to run even if this occurs. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file named prefs.ora is stored in the appropriate directory. For more information, contact the database administrator. If Case 2: Verify privileges necessary to access the file, and change privileges accordingly. If Case 3: Consult the operating system documentation or the system administrator.
REP-00004
User preference file cannot be opened.
Category:
Other
Cause:
The local (customized) preference file could not be opened. This is just a warning, so the product will continue to run even if this occurs. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify the file prefs.ora is located in the home directory, and change the directory and/or file name as appropriate. If Case 2: Verify privileges necessary to access the file, and change privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00005
A syntax error exists at line {0} in global preference file.
Category:
Other
Cause:
One or more of the preferences in the global preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, the Oracle Reports Builder will ignore the incorrectly specified preferences.
Action:
Edit the global preference file and ensure that all preferences are correctly specified, and make the necessary updates.
REP-00006
A syntax error exists at line {0} in user preference file.
Category:
Other
Cause:
One or more of the preferences in the user preference file was specified incorrectly on the line number shown in the message. The most likely cause of this error is that the file has been edited and one or more preferences incorrectly specified. As a result, the Oracle Reports Builder will ignore the incorrectly specified preferences.
Action:
Edit the global preference file and ensure that all preferences are correctly specified. If they are not, make the necessary updates.
REP-00007
The user preference file cannot be written to.
Category:
Other
Cause:
An attempt was made to save preferences and the user preference file could not be written. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: A system error made it impossible to write the file.
Action:
Take the following actions to correct this error: If Case 1: Verify privileges necessary to write the file, and change the privileges accordingly. If Case 2: Consult the operating system documentation or contact the system administrator.
REP-00008
An unexpected memory error occurred while initializing preferences.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00058
Data passing to a remote Reports Server is not supported.
Category:
Data
Cause:
A record group was passed to a report to be run remotely.
Action:
Do not specify a Reports Server when passing a record group.
REP-00059
Resources for subcomponent {0} cannot be located.
Category:
Other
Cause:
One of the subcomponents of the Oracle Reports Builder could not locate its resource file. Possible causes of this error include: Case 1: The resource file does not exist. Case 2: The resource file is in the wrong place. Case 3: The environment is not configured properly.
Action:
Take the following actions to correct this error: If Case 1: Verify that the resource files are present. If Case 2: Verify that the resource files are in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set; on Windows, check oracle.ini.
REP-00060
A synchronous job cannot be run concurrently with another report.
Category:
Other
Cause:
An attempt was made to run a report initiated by Forms Runtime and requiring data passed from that tool, but one or more other reports are running or queued to run. Reports requiring passed data must be run immediately.
Action:
Wait for all other reports currently listed in the Reports Server queue to run, then rerun report.
REP-00061
An internal error occurred - rxmobfree: reference count is zero.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00062
An internal error occurred - rxmobnew: size mismatch.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00063
An internal error occurred - rxmobnew: memory manager mismatch.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00064
An internal error occurred - rxmobnew: type mismatch.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00065
A virtual memory system error occurred.
Category:
Memory
Cause:
Oracle Reports Builder has encountered a memory error.
Action:
Make note of the error-specific code and contact Oracle Support Services.
REP-00066
An error occurred executing the CA utility.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00067
The value for keyword STYPE is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was provided for the STYPE keyword.
Action:
Check the syntax of the keyword. Valid values are DATABASE, REXFILE, RDFFILE, PLLDB, PLLFILE, or PLDFILE. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00068
The value for DTYPE is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was provided for the DTYPE keyword.
Action:
Check the syntax of the keyword. Valid value are DATABASE, REXFILE, RDFFILE, REPFILE, TDFFILE, PLLDB, PLLFILE, PLXFILE, or PLDFILE. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00069
An internal error occurred
Category:
Other
Cause:
An Oracle Reports Builder internal code error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-00071
The SSL context cannot be allocated.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00072
The NNIT interface cannot be initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00073
An unknown product cannot be run.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00074
An attempt to run another product using SSL failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00075
An error occurred when running the called Oracle component,
Category:
Other
Cause:
Oracle Reports Builder encountered an error after calling Forms Runtime or Graphics Runtime. The accompanying error message displays the error encountered by the called application.
Action:
Resolve the error encountered by the called application and retry the operation.
REP-00076
An internal failure occurred in product integration.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00077
The column in query {0} too long for data passing.
Category:
Data
Cause:
An attempt was made to pass data to a column of excessive size (likely a LONG column).
Action:
Remove the column from the report definition and the calling document's definition.
REP-00078
A single process integration was invoked with BATCH=NO.
Category:
Process
Cause:
An attempt was made to invoke Oracle Reports Builder specifying BATCH=NO with executable in which Oracle Reports Builder is linked with another product.
Action:
Use an executable which integrates using multiple processes, or specify BATCH=YES.
REP-00079
Value for keyword OVERWRITE is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was specified for the OVERWRITE keyword.
Action:
Reenter the command, specifying a value of YES, NO, or PROMPT for the OVERWRITE keyword.
REP-00080
The specified value is invalid.
Category:
Other
Cause:
In Reports Converter, OVERWRITE=PROMPT was specified on the command line, then a value other than YES or NO was entered when prompted.
Action:
Specify a value of YES or NO at the prompt, or CANCEL the operation.
REP-00081
An error occurred during the file I/O operation.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00082
An error occurred executing the SCA utility.
Category:
Other
Cause:
The possible causes of this error include the following: Case 1: The initialization file is not current. Case 2: An abnormal condition.
Action:
Take the following actions to correct this error: If Case 1: Ensure that the directory where the report is located is defined in the REPORTS_PATH located in $ORACLE_HOME/bin/reports.sh. If Case 2: For assistance, contact Oracle Support Services.
REP-00083
The value for keyword DUNIT is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was specified for the DUNIT keyword.
Action:
Check the syntax of the keyword. Valid values are CENTIMETER, CHARACTER, INCH, or POINT. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00084
The value for keyword PAGESIZE is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was specified for the PAGESIZE keyword.
Action:
Check the syntax and value of the keyword. Valid syntax is <width>x<height>. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00085
The value for keyword FORMSIZE is invalid.
Category:
Other
Cause:
In Reports Converter, an invalid value was specified for the FORMSIZE keyword.
Action:
Check the syntax and value of the keyword. Valid syntax is <width>x<height>. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00086
DUNIT must be different than source report's unit of measurement.
Category:
Other
Cause:
In Reports Converter, an invalid value was specified for the DUNIT keyword that was in the same unit of measurement as the report to be converted.
Action:
Check the syntax and value of the keyword. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00087
The value for keyword DESTYPE is invalid.
Category:
Other
Cause:
In Reports Runtime, an invalid value was specified for the DESTYPE keyword.
Action:
Check the syntax and value of the keyword. Valid values are SCREEN, FILE, PRINTER, MAIL, SYSOUT, or PREVIEW. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00088
The value for keyword ONSUCCESS is invalid.
Category:
Other
Cause:
An invalid value was specified for the ONSUCCESS keyword.
Action:
Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00089
The value for keyword ONFAILURE is invalid.
Category:
Other
Cause:
An invalid value was specified for the ONFAILURE keyword.
Action:
Specify COMMIT, ROLLBACK, or NOACTION either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00090
The value for keyword ACCESS is invalid.
Category:
Other
Cause:
For Oracle Reports Builder, an invalid value was specified for the ACCESS keyword.
Action:
Specify FILE or DATABASE. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00091
The value for parameter {0} is invalid.
Category:
Other
Cause:
An invalid value was specified for the named parameter. For example, in the Reports Runtime command string, a character value was provided for a parameter with a data type of Number.
Action:
Retry the operation, specifying a valid value for the parameter.
REP-00092
Version 1.1 LANGUAGE argument not supported. Use Oracle National Language environment variable instead
Category:
Other
Cause:
For Oracle Reports Builder or Runtime, the LANGUAGE keyword was included in the command line string.
Action:
Remove the LANGUAGE argument string from the command string, and set the Oracle National Language environment variable NLS_LANG to the appropriate value.
REP-00094
FORMSIZE must be 80x24 if DUNIT is Character.
Category:
Other
Cause:
While using Reports Converter with DUNIT=Character, a Parameter Form size was specified that was not equal to 80x24.
Action:
The character-mode Parameter Form size must be 80x24. Either specify a FORMSIZE of 80x24 when DUNIT=Character, or do not specify a FORMSIZE.
REP-00095
The value for keyword ORIENTATION is invalid.
Category:
Other
Cause:
An invalid value was specified for the ORIENTATION keyword.
Action:
Specify DEFAULT, LANDSCAPE, or PORTRAIT either in the Runtime Settings tab of the Tools Options dialog box or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00096
The value for keyword MODE is invalid.
Category:
Other
Cause:
An invalid value was specified for the MODE keyword.
Action:
Specify DEFAULT, BITMAP, or CHARACTER either in the Runtime Settings tab of the Tools Options dialog or on the command line. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00097
The value for keyword TRACEMODE is invalid.
Category:
Other
Cause:
Either an invalid or no value was specified for the TRACEMODE keyword, or keywords were specified out of order on the command line without being named.
Action:
Either specify Append or Replace for Trace Mode in the Trace Settings dialog or TRACE_APPEND or TRACE_REPLACE on the command line, or check the syntax of the command. To check the command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00098
The report was not run as it was canceled in the Parameter Form.
Category:
Other
Cause:
The report was not executed because Cancel instead of Run Report was selected in the Runtime Parameter Form.
Action:
No action is necessary.
REP-00099
The report is aborted upon user request.
Category:
Other
Cause:
The report was stopped while it was executing.
Action:
No action is necessary.
REP-00100
The file pointer in file {0} cannot be positioned.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00101
File {0} cannot be read.
Category:
Other
Cause:
Oracle Reports Builder tried to read a file, which could be opened but not read.
Action:
Consult the operating system documentation or contact the system administrator.
REP-00102
File {0} cannot be written to.
Category:
Other
Cause:
Oracle Reports Builder tried to write the file shown in the message and could not. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: The file system does not have enough room for the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify the privileges necessary to write the file, and change privileges accordingly. If Case 2: Make more room by deleting unnecessary files or expanding storage. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00103
File {0} cannot be closed.
Category:
Other
Cause:
Oracle Reports Builder tried to close the file, but was unsuccessful. The most likely reason is that a system error made it impossible to close the file.
Action:
Consult the operating system documentation or contact the system administrator.
REP-00104
File {0} cannot be deleted.
Category:
Other
Cause:
Oracle Reports Builder tried to delete the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to delete the file.
Action:
Consult the operating system documentation or contact the system administrator.
REP-00105
File {0} cannot be locked in exclusive mode.
Category:
Other
Cause:
Oracle Reports Builder tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file.
Action:
Consult the operating system documentation or contact the system administrator.
REP-00106
File {0} cannot be locked in shared mode.
Category:
Other
Cause:
Oracle Reports Builder tried to lock the file shown, but was unsuccessful. The most likely reason is that a system error made it impossible to lock the file.
Action:
Consult the operating system documentation or contact the system administrator.
REP-00107
File {0} cannot be opened: bad name.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00108
File {0} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder tried to access the file shown, but could not find it.
Action:
Verify the file name. Specify a directory before the file name, or modify the REPORTS_PATH environment variable to include the directory where the file is located.
REP-00109
There are too many files open.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00110
File {0} cannot be opened.
Category:
Other
Cause:
Oracle Reports Builder tried to open the file shown and could not. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00111
Directory {0} is protected.
Category:
Other
Cause:
Oracle Reports Builder attempted to read from or write to a directory that is read and write protected.
Action:
Change the permissions on the directory as necessary.
REP-00112
File {0} is write-protected.
Category:
Other
Cause:
Oracle Reports Builder attempted to write to a file that is write-protected.
Action:
Change the permissions of the file as necessary.
REP-00113
File {0} is read-protected.
Category:
Other
Cause:
Oracle Reports Builder attempted to read a file that is read-protected.
Action:
Change the permissions of the file as necessary.
REP-00114
File {0} no longer exists.
Category:
Other
Cause:
Oracle Reports Builder attempted to access a file that no longer exists.
Action:
Remove the call to the file, re-create the file, or specify a different file.
REP-00115
Directory {0} cannot be read.
Category:
Other
Cause:
Oracle Reports Builder attempted to read from or write to a directory that does not exist.
Action:
Verify that the specified directory exists.
REP-00116
Directory {0} cannot be accessed.
Category:
Other
Cause:
Oracle Reports Builder could not access the specified directory.
Action:
Consult the system administrator.
REP-00117
Exit to the host operating system failed.
Category:
Operating System
Cause:
Oracle Reports Builder attempted to exit the program and return control to the host operating system.
Action:
No action is necessary.
REP-00118
A temporary file cannot be created.
Category:
Other
Cause:
Oracle Reports Builder tried to create a temporary file but could not do so. The possible causes of this error include the following: Case 1: The environment variable that determines in what directory to create temporary files is set to an invalid directory. Case 2: There is not enough free space on the disk to create the temporary file. Case 3: A temporary file that cannot be modified already exists.
Action:
Take the following actions to correct this error: If Case 1: Set the environment variable for temporary files to a valid directory. If Case 2: Free up some space on the disk. If Case 3: Remove the existing temporary file, if possible.
REP-00119
File link boilerplate {0}'s Source Filename {1} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not find the source file specified in the Source Filename property for the file link boilerplate object. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00120
Graph {0}'s associated document {1} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder was unable to find the graph document. The possible causes of this error include the following: Case 1: The graph document was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the graph document. Case 3: A system error made it impossible to open the graph document.
Action:
Take the following actions to correct this error: If Case 1: Verify that the graph document is stored in the specified directory under the specified name. If it is not, change the directory and/or file name as appropriate. If Case 2: Verify the privileges necessary to open the graph document, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00124
The temporary file cannot be written to.
Category:
Other
Cause:
Oracle Reports Builder tried to write to the temporary file but could not do so.
Action:
Free up some space on the disk.
REP-00125
An internal error occurred: Unable to load NLS character set.
Category:
Other
Cause:
ORA_NLS was not set, or the directory to which it points does not exist.
Action:
Set ORA_NLS to point to the NLS directory containing character set files.
REP-00126
File {0} is not a known type to Oracle Reports Builder. No file conversion can be performed. Check in anyway?
Category:
Other
Cause:
An attempt was made to check in a file of a type that Oracle Reports Builder cannot convert. For example, Oracle Reports Builder cannot convert a Form Builder (FMB) file.
Action:
To continue checking in, click Yes. Otherwise, click No and nothing will be checked in.
REP-00127
File {0} is not a known type to Oracle Reports Builder. No file conversion can be performed. Check out anyway?
Category:
Other
Cause:
An attempt was made to check out a file of a type that Oracle Reports Builder cannot convert. For example, Oracle Reports Builder cannot convert a Form Builder (FMB) file.
Action:
To continue checking out, click Yes. Otherwise, click No and nothing will be checked out.
REP-00128
There are unsaved changes in file {0}. Save before checkin?
Category:
Other
Cause:
An attempt was made to check in a file that is currently open and there are unsaved changes.
Action:
To save and check in the file, click Yes. Click No to check in the file without the changes. Otherwise, click Cancel and nothing will be checked in.
REP-00129
There are unsaved changes in file {0}. Check out anyway?
Category:
Other
Cause:
An attempt was made to check out a file that is is currently open and there are unsaved changes.
Action:
To check out the file, click Yes. Note that this will overwrite all the changes made to this file. Otherwise, click No and nothing will be checked out.
REP-00130
A module saved in the database cannot be checked in. Save it to file before checkin.
Category:
Other
Cause:
Checking in a module saved in the database is not supported.
Action:
Save the module to the filesystem first and then check it in again.
REP-00131
The communication layer cannot be initialized.
Category:
Other
Cause:
The required communication files were not found.
Action:
Check the installation and setup and update with the latest patch.
REP-00132
A JVM cannot be started.
Category:
Other
Cause:
Oracle Reports could not start up the required JVM services.
Action:
Check the installation and setup and update with the latest patch.
REP-00133
Java Classes cannot be found.
Category:
Other
Cause:
Some required files were not found. This could be caused by an invalid installation or missing files.
Action:
Check the installation and setup and update with the latest patch.
REP-00150
There are too many arguments.
Category:
Other
Cause:
More than the allowable number of arguments for the command were entered.
Action:
Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command correctly.
REP-00151
Duplicate arguments are specified for keyword {0}.
Category:
Other
Cause:
An argument was entered more than once for the keyword shown. The possible causes of this error include the following: Case 1: A positional argument was entered for the keyword and then the keyword was entered with another argument. Case 2: The same keyword was entered twice (for example, KEYWORD1=YES and KEYWORD1=NO).
Action:
Check the syntax of the command (see the Command Line Keywords appendix in the Publishing Reports to the Web manual). 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.
REP-00152
A positional argument is specified after a keyword.
Category:
Other
Cause:
On the command line, an argument was entered without its keyword after being an argument was entered with its keyword. Once a keyword is used on the command line, all subsequent arguments must use keywords as well.
Action:
Reenter the command making sure that no positional arguments (arguments where the keyword is implicit) are specified after arguments with keywords.
REP-00153
Multiple values are not allowed for keyword {0}.
Category:
Other
Cause:
In the command, more than the allowable number of values for the keyword were entered. For example, KEYWORD=(A, B) was entered, where KEYWORD accepts only a single value.
Action:
Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command without the extra values.
REP-00154
The command file cannot be opened.
Category:
Other
Cause:
A command referenced the command file shown and the file could not be opened. The possible causes of this error include the following: Case 1: The file was not found under the specified name in the specified location. Case 2: Lack of necessary privileges to open the file. Case 3: A system error made it impossible to open the file.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name. If it is not, change the directory and/or file name or move the file into the specified directory. If Case 2: Verify the privileges necessary to access the file, and change the privileges accordingly. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-00155
The value for keyword {0} is invalid.
Category:
Other
Cause:
The value entered for the keyword shown was not a valid value.
Action:
Check the syntax of the keyword. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
REP-00156
The value for keyword DESTYPE is invalid.
Category:
Other
Cause:
In Reports Runtime, an invalid value was provided for the DESTYPE keyword.
Action:
Check the syntax of the keyword. Valid values are SCREEN, FILE, PRINTER, MAIL or SYSOUT. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
REP-00157
The value for {0} must be either YES or NO.
Category:
Other
Cause:
A value other than YES or NO was entered for the keyword shown, and the keyword only accepts YES or NO.
Action:
Reenter the command using a value of YES or NO for the keyword shown.
REP-00158
The command line keyword {0} is unknown.
Category:
Other
Cause:
The referenced string was entered as a keyword, but there is no such keyword.
Action:
Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command with the appropriate value for the keywords.
REP-00159
A syntax error exists on the command line.
Category:
Other
Cause:
The string entered on the command line could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.
Action:
Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command using the appropriate syntax.
REP-00160
A syntax error exists in the command file.
Category:
Other
Cause:
Something entered in the command file could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.
Action:
Check the syntax of the commands. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Edit the file and modify the commands as necessary to correct the commands.
REP-00161
No command-line arguments are specified.
Category:
Other
Cause:
Reports Converter was invoked without specifying any command-line arguments.
Action:
Specify the appropriate command-line arguments (for example, SOURCE, DEST) for Reports Converter. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00162
The value for keyword SHOWWINDOW is invalid.
Category:
Other
Cause:
The value specified for the SHOWWINDOW keyword was not valid.
Action:
Check the syntax of the keyword. Valid values are DEFAULT, WIZARD, and PREVIEWER. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00163
The value for keyword DESTYPE is invalid.
Category:
Other
Cause:
The value specified for the DESTYPE keyword was not valid for the Reports Server.
Action:
Check the syntax of the keyword. Valid values are FILE, PRINTER, MAIL, or CACHE.
REP-00164
The value for keyword PARAMFORM is invalid.
Category:
Other
Cause:
The value specified for the PARAMFORM keyword was not valid.
Action:
Reenter the command, specifying a value of YES, NO, or HTML[action] for the PARAMFORM keyword.
REP-00165
The value for keyword SITENAME is missing.
Category:
Other
Cause:
No value was specified for the SITENAME keyword. A value is required for SITENAME in order to schedule a report.
Action:
Specify a WEBDB site name for the keyword SITENAME.
REP-00166
Read/write of the specified directory is not allowed.
Category:
Other
Cause:
Oracle Reports attempted to read from or write to a directory without read/write privileges.
Action:
Check the command line options to identify the directory name. Add the directory to REPORTS_PATH, ORACLE_PATH, or the sourceDir property in the engine element in the server configuration file.
REP-00171
Output from the remote server cannot be retrieved.
Category:
Other
Cause:
An error occurred when retrieving output from the remote server.
Action:
Verify that the file is accessible, and that the server is set to allow retrieving outputs.
REP-00172
The value for keyword SERVER is missing.
Category:
Other
Cause:
No value was specified for the mandatory keyword SERVER.
Action:
Provide a valid argument for the keyword SERVER and rerun the command.
REP-00173
The value for keyword SHOWJOBS is invalid.
Category:
Other
Cause:
In the Reports Queue Viewer, an argument provided in command line for the SHOWJOBS keyword was not valid.
Action:
Reenter the command, specifying a value of PAST, CURRENT or FUTURE for the SHOWJOBS keyword.
REP-00174
An internal error occurred while obtaining the Reports Server queue information.
Category:
Other
Cause:
The Reports Server did not return valid information about its queue to the queue viewer. This could be caused by one of the following reasons: Case 1: The connection to the Reports Server unexpectedly went down. Case 2: The Reports Server is in an unstable state, or has been shut down.
Action:
Verify that the Reports Server is running. Contact the system administrator and retry the command after verifying that the Reports Server is running. If this problem persists, contact Oracle Support Services.
REP-00175
An internal error occurred while obtaining the Reports Server properties information.
Category:
Other
Cause:
The Reports Server did not return valid information about its properties to the queue viewer. This could be caused by one of the following reasons: Case 1: The connection to the Reports Server unexpectedly went down. Case 2: The Reports Server is in an unstable state, or has been shut down.
Action:
Verify that the Reports Server is running. Contact the system administrator and retry the command after verifying that the Reports Server is running. If this problem persists, contact Oracle Support Services.
REP-00176
Server {0} is shutting down.
Category:
Other
Cause:
A report cannot be submitted when the specified Reports Server is shutting down.
Action:
Submit to another Reports Server or wait until the Server is back up.
REP-00177
An error occurred while running in a remote server.
Category:
Other
Cause:
An attempt to run a command line in the remote server failed.
Action:
Check the command line.
REP-00178
Reports Server {0} cannot establish connection.
Category:
Other
Cause:
A proper connection could not be established to the specified Reports Server.
Action:
Check the network and check the status of the Reports Server in question.
REP-00179
Report execution terminated unexpectedly while running.
Category:
Other
Cause:
The Reports Engine has crashed while running.
Action:
Contact the system administrator.
REP-00180
The report has been canceled from the Reports Server.
Category:
Other
Cause:
The report was stopped while it was executing or removed from the queue before it was started.
Action:
No action is necessary.
REP-00181
An error occurred reading or writing the configuration file for the Reports Server.
Category:
Configuration
Cause:
The configuration file cannot be opened, or its content is incomprehensible.
Action:
Check the configuration file and its access rights. Restart the server.
REP-00182
A syntax error occurred on command line for the Reports Server.
Category:
Other
Cause:
The string entered on the command line could not be parsed. The most likely cause of this error is that quotation marks or parentheses were entered without matching end quotation marks or parentheses.
Action:
Check the syntax of the command. For more information, see the Command Line Keywords appendix in the Publishing Reports to the Web manual. Reenter the command using the appropriate syntax.
REP-00183
TNSNAME must be provided to start up the Reports Server.
Category:
Other
Cause:
An attempt was made to start up the Reports Server without specifying the TNSNAME to which the Server should listen.
Action:
Specify the TNSNAME as a command-line argument.
REP-00184
The specified MAXCONNECTS is out of range.
Category:
Other
Cause:
The MAXCONNECTS value specified is out of range for this platform. MAXCONNECTS must be at least 2, and cannot exceed 4096, and on some platforms the limit is even lower.
Action:
Specify an appropriate value.
REP-00185
Bad load arguments were supplied when starting up the Reports Server.
Category:
Other
Cause:
Inconsistent values were specified among MAXCONNECTS, MINLOAD, MAXLOAD, and INITLOAD.
Action:
Verify that 0 <= MINLOAD <= INITLOAD <= MAXLOAD < MAXCONNECTS.
REP-00186
A daemon cannot listen to the port.
Category:
Other
Cause:
Another daemon may be running that is already listening to the port.
Action:
No action is necessary. Since a daemon is already running, submit the report to be run.
REP-00187
A daemon cannot start up the engine.
Category:
Other
Cause:
A daemon cannot start up the engine executable and communicate with it. This is most likely an installation issue.
Action:
Verify that the installation is done properly.
REP-00188
Reports Server only accepts batch jobs.
Category:
Other
Cause:
A job was submitted to the Reports Server where BATCH=NO, DESTYPE=SCREEN, DESTYPE=PREVIEW, or DESTYPE=SYSOUT.
Action:
These settings are not allowed. Change the command line accordingly.
REP-00189
The Reports Server cache cannot be written to.
Category:
Other
Cause:
Reports Server failed to write to the cache directory.
Action:
Verify that the cache directory is specified in the server configuration file and it is writable.
REP-00190
A report cannot be run to screen in the background.
Category:
Other
Cause:
The report was specified to be run in the background, with DESTYPE=SCREEN. A report cannot run in the background while having its output sent to the screen.
Action:
To send the output to the screen, run it in the foreground. To run the report in the background, specify a different DESTYPE.
REP-00194
A character report cannot be run in bitmap mode using this executable.
Category:
Other
Cause:
Oracle Reports attempted to use the character-mode executable to run a character-mode report with MODE=BITMAP. This is not allowed.
Action:
Change the value of the MODE keyword to match the mode of the executable.
REP-00195
A report cannot be run in bitmap mode to screen using this executable.
Category:
Other
Cause:
Oracle Reports attempted to use the character-mode executable to run a bitmapped report to the screen. This is not allowed.
Action:
Run the report using BATCH=YES or use a bitmapped executable.
REP-00196
The report cannot be run in the background.
Category:
Other
Cause:
BACKGROUND=YES was specified under one of the following conditions, none of which are allowed: Case 1: Running the report from the designer. Case 2: BATCH=YES. Case 3: Running the report using the packaged procedure srw.run_report. Case 4: The platform on running the report does not support spawning of another process.
Action:
Ensure that BACKGROUND=NO when any of the above condition are true.
REP-00197
BATCH=YES or BACKGROUND=YES must be specified on the command line when running a bitmapped report.
Category:
Other
Cause:
Oracle Reports attempted to run a bitmapped report using the character-mode executable in the foreground or during an interactive session. This is not supported.
Action:
To run a bitmapped report using the character-mode executable, specify either BATCH=YES or BACKGROUND=YES (unlike BATCH=YES, this setting provides access to the Runtime Parameter Form).
REP-00200
Enough memory cannot be allocated.
Category:
Memory
Cause:
Oracle Reports Builder cannot obtain enough memory from the system to complete the current task.
Action:
Make more memory available, if possible, or ask the system administrator for assistance.
REP-00201
A zero or negative block size was requested.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00202
A null pointer cannot be freed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00203
A null pointer was passed as a handle.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00204
The handle does not point into an mp block.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00205
There are too many simultaneous locks on one object.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00206
A null cache pointer is passed to virtual memory routine.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00207
The requested block is larger than virtual memory space.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00208
rmaloc was not given a function identifier.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00209
rmaloc was not given a structure identifier.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00210
An illegal operation was requested on a locked handle.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00211
A handle cannot be used after freeing it.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00212
No literal is specified.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00213
An attempt to lock a handle failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00214
A virtual memory buffer of size {0} KB cannot be allocated. Try a smaller size.
Category:
Memory
Cause:
Oracle Reports Builder tried to allocate a virtual memory buffer size at or below the number specified for the BUFFERS keyword.
Action:
Specify a smaller size for BUFFERS, either on the command line or in the Runtime Settings tab of the Preferences dialog box (select Edit, then Preferences), or free up more memory. For command line syntax, see the Command Line Keywords appendix in the Publishing Reports to the Web manual.
REP-00215
An error occurred locking, dereferencing, or freeing a memory handle.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00216
There is insufficient memory to save the report as a JSP or XML.
Category:
Memory
Cause:
The report definition file has exceeded 10 MB. The report cannot be saved as a JSP or XML if it exceeds 10 MB.
Action:
Reduce the size of the file.
REP-00230
An error occurred while starting a thread.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00231
An error occurred while posting thread message.
Category:
Threads
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00232
An error occurred while getting thread message.
Category:
Threads
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00235
The Security Server TNSNAME is not provided in the config file.
Category:
Security
Cause:
Security Server TNSNAME must be specified in config file on security mode"
Action:
Specify Security Server TNSNAME in the config file by using the keyword 'securitytnsname'.
REP-00236
The Security Server cannot be connected.
Category:
Security
Cause:
An abnormal condition was encountered.
Action:
Contact the system administrator. For assistance, contact Oracle Support Services.
REP-00238
Authentication failed.
Category:
Security
Cause:
The system userid/password is invalid or does not have privilege to run the report.
Action:
Check the system userid/password to verify that it is correct or contact the system administrator to grant the necessary privilege.
REP-00239
The Security server authentication failed: invalid user name.
Category:
Security
Cause:
The system user ID is incorrect.
Action:
Check the system user ID to verify that it is correct or contact the system administrator about the system user ID.
REP-00240
The Security Server authentication failed: invalid password.
Category:
Security
Cause:
The password for the system user ID is incorrect.
Action:
Check the system user ID password to verify that it is correct or contact the system administrator about the system user ID password.
REP-00241
The Security Server authentication failed: no privilege on the Reports Server.
Category:
Security
Cause:
The system user ID does not have privilege to access the Reports Server.
Action:
Contact the system administrator about the system user ID's privilege on the Reports Server.
REP-00242
The Security Server authentication failed: no privilege on the printer.
Category:
Security
Cause:
The system user ID does not have privilege to access the printer.
Action:
Contact the system administrator about the system user ID's privilege on the printer.
REP-00243
The Security Server authentication failed: no privilege on the module.
Category:
Security
Cause:
The system user ID does not have privilege to access the module.
Action:
Contact the system administrator about the system user ID's privilege on the module.
REP-00244
The Security Server authentication failed: no privilege of this access type.
Category:
Security
Cause:
The system user ID does not have privilege of this access type.
Action:
Contact the system administrator about the system user ID's privilege of this access type.
REP-00245
The Security Server authentication failed: no privilege of this output type.
Category:
Security
Cause:
The system user ID does not have privilege of this output type.
Action:
Contact the system administrator about the system user ID's privilege of this output type.
REP-00246
The Security Server authentication failed: no privilege for the given time.
Category:
Security
Cause:
The system user ID does not have privilege for the given time.
Action:
Contact the system administrator about the system user ID's privilege for the given time.
REP-00247
The Security Server authentication failed: no privilege for the given date.
Category:
Security
Cause:
The system user ID does not have privilege for the given date.
Action:
Contact the system administrator about the system user ID's privilege for the given date.
REP-00250
A symbol table overflow occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00251
The identifier does not match a defined symbol.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00252
The path specified by environment variable {0} is too long and will be ignored.
Category:
Other
Cause:
The path specified by the environment variable is too long.
Action:
Shorten the length of the designated path.
REP-00253
The total length of the search paths is too long and will be truncated.
Category:
Other
Cause:
The combined length of search paths in the path environment is too long. The combined length cannot exceed 255 characters.
Action:
Shorten the length of one or more paths in the path environment.
REP-00300
An Oracle error occurred.
Category:
Other
Cause:
Oracle Reports Builder encountered an Oracle error.
Action:
Scroll through the error message to see where the error occurred and, if possible, fix it. Otherwise, contact the system administrator.
REP-00301
The SELECT statement may not contain an INTO clause.
Category:
Other
Cause:
An INTO clause was entered in a SELECT statement, which is not allowed in Oracle Reports Builder.
Action:
Remove the INTO clause.
REP-00302
Parameter {0} cannot be found in the report.
Category:
Other
Cause:
Oracle Reports referenced a parameter that is not defined in the report. The most likely cause is that a parameter was deleted but not all references to it were deleted.
Action:
Delete all references to the deleted parameter.
REP-00303
The statement entered is not a SELECT statement.
Category:
Other
Cause:
What was entered in the SELECT Statement field is something other than a SELECT statement. The possible causes of this error include the following: Case 1: Something besides a SELECT statement was entered in the SELECT Statement field. Case 2: An external query was referecned that did not contain a SELECT statement.
Action:
Take the following actions to correct this error: If Case 1: Enter a valid SELECT statement. If Case 2: Modify the external query or reference another external query.
REP-00304
& in SELECT statement was not followed by a valid lexical parameter.
Category:
Other
Cause:
An ampersand (&) appears in the SELECT statement by itself. The possible causes of this error include the following: Case 1: A lexical reference either left out the name of the column or parameter altogether or there is a space between the ampersand and the name of the column or parameter. Case 2: An ampersand was accidentally typed in the SELECT statement.
Action:
Take the following actions to correct this error: If Case 1: Verify that the column or parameter name immediately follows the ampersand with no spaces in between. If Case 2: Delete the ampersand.
REP-00305
Reference {0} cannot be used as a lexical parameter because it is not a character value.
Category:
Other
Cause:
An invalid lexical reference appears in the 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: The wrong column or parameter was referenced. Case 2: The reference should be a bind reference, not a lexical reference. Case 3: The parameter or column referenced was created with a non-character data type.
Action:
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 data type of Character. If Case 2: Replace the ampersand (&) with a colon (:) when referencing the parameter or column. If Case 3: Change the data type of the parameter or column to be Character, if appropriate.
REP-00306
The name {0} is not a valid parameter name.
Category:
Other
Cause:
In making reference to a parameter, an attempt was made to create a parameter with an invalid name. For a bind reference, a parameter definition is automatically created using the name specified in the bind parameter. In this case, Oracle Reports Builder could not create the parameter because the name supplied was not a valid name.
Action:
Check the naming conventions for data model objects and rules for parameter names. Rename the parameter and change the name in the bind reference.
REP-00307
The SELECT statement may not contain a FOR UPDATE clause.
Category:
Other
Cause:
A FOR UPDATE clause was entered in the SELECT statement, which is not allowed in Oracle Reports Builder.
Action:
Remove the FOR UPDATE clause.
REP-00308
An internal error occurred: Unknown column type.
Category:
Other
Cause:
The possible causes of this error include the following: Case 1: An attempt was made to display the value of a column using SRW.MESSAGE, but the column's data type (for example, LONG, LONG RAW, ROWID) is not supported for that operation. Case 2: An attempt was made to pass the value of a column to Forms Runtime or Graphics Runtime as a parameter, but the column's data type (for example, LONG, LONG RAW, ROWID) is not supported for that operation.
Action:
Do not attempt to display or pass this column's value.
REP-00309
The specified database cannot connect after three attempts. Access denied.
Category:
Other
Cause:
Case 1: Some part of the logon string entered was incorrect. After three failed attempts, Oracle Reports Builder displays a dialog box with this message. Case 2: The NLS_LANG environment variable value may be invalid.
Action:
Case 1: Accept the dialog box. Confirm the logon information with the system administrator, if necessary. Go back into Oracle Reports Builder and try connecting to Oracle again. If the problem persists, the system administrator may need to create a new Oracle logon. Case 2: Verify the NLS_LANG value is valid.
REP-00310
An error occurred while processing bind variables in a query.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00311
An internal error occurred: Segmented memory used for lexical parameter.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00312
An internal error occurred: Error dealing with segmented memory.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00313
An internal error occurred: Fetching data records would cause memory overflow.
Category:
Data
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00314
The column name exceeds 256 characters, and no alias is assigned.
Category:
Other
Cause:
One of the SQL SELECT statements contains an expression that is longer than 256 characters, but has no alias.
Action:
Edit the SELECT statement and assign an alias to the expression.
REP-00315
Each SELECT statement must have the same number of columns in a compound query.
Category:
Other
Cause:
A query with a UNION, INTERSECT, or MINUS set operator was entered in which the SELECT statements in the query do not have the same number of selected columns.
Action:
Modify the SELECT statements so that they have the same number of columns.
REP-00316
The types of corresponding columns must match in a compound query.
Category:
Other
Cause:
A query with a UNION, INTERSECT, or MINUS set operator was entered in which corresponding columns have different types. For example, column 1 in the first SELECT statement has data type CHAR, while column 1 in the second SELECT statement has data type NUMBER.
Action:
Modify the SELECT statements so that all corresponding columns have the same data type.
REP-00320
The database cannot be connected.
Category:
Other
Cause:
An attempt to connect to the database failed.
Action:
Recheck the user ID and password and try again.
REP-00321
An internal error occurred: Describe of query failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00322
An internal error occurred: Attempt to put back fetched rows failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00330
An internal error occurred: Location GET_REF parameters failed.
Category:
Other
Cause:
A CDE_MM.GET_REF call in a query did not specify a parameter list.
Action:
Add the parameter list to the call in the query's SELECT statement.
REP-00331
The GET_REF PL/SQL function requires 3 parameters.
Category:
Other
Cause:
The parameter list of a CDE_MM.GET_REF call in a query was incomplete.
Action:
Add the necessary parameters to the call in the query's SELECT statement.
REP-00332
The GET_REF PL/SQL function's last parameter must be of type ROWID.
Category:
Other
Cause:
A parameter of type ROWID was not provided as the last parameter for a GET_REF function.
Action:
Check the parameter list and ensure the last parameter is of type ROWID.
REP-00340
The role password cannot be verified, and the report is not opened.
Category:
Other
Cause:
Incorrect role password. For security reasons, the report cannot be openend.
Action:
Try opening the report again and type in the correct role password.
REP-00341
The roles specified in the report cannot be set, and the report is not opened.
Category:
Other
Cause:
The roles specified in the report cannot be set while opening the report. For security reasons, the report cannot be opened.
Action:
Check role permissions and password.
REP-00342
Roles specified on the command line cannot be set.
Category:
Other
Cause:
The roles specified on the command line cannot be set.
Action:
Check role permissions and password.
REP-00343
Default roles of the current user cannot be set.
Category:
Other
Cause:
Reports is unable to set the default roles of the current user that has passwords.
Action:
Do not use default roles with passwords.
REP-00344
The role password was not confirmed correctly.
Category:
Other
Cause:
The Confirm Password entered is different from the Role Password.
Action:
Reenter and verify that Confirm Password exactly matches the Role Password.
REP-00345
An empty role and a non-empty password is not valid.
Category:
Other
Cause:
No role is specified, while role password is specified.
Action:
Leave all fields empty to not associate a role with this report.
REP-00346
The role must be no longer than {0} characters. It will be truncated.
Category:
Other
Cause:
The role name specified is longer than is allowable. It will be truncated.
Action:
Specify a shorter role name.
REP-00347
The role password must be no longer than {0} characters. It will be truncated.
Category:
Other
Cause:
The role password specified is longer than is allowable. It will be truncated.
Action:
Specify a shorter role password.
REP-00348
The role password is incorrect.
Category:
Other
Cause:
The role password entered was incorrect.
Action:
Reenter with the correct role password.
REP-00450
PL/SQL error {0} was encountered.
Category:
Other
Cause:
Oracle Reports Builder encountered the identified PL/SQL error while running a report.
Action:
Edit and recompile the PL/SQL in the report to avoid this error.
REP-00451
PL/SQL error {0} was encountered. {1}.
Category:
Other
Cause:
Oracle Reports Builder encountered the identified PL/SQL error while running a report.
Action:
Edit and recompile the PL/SQL in the report to avoid this error.
REP-00452
PL/SQL error {0} was encountered. {1}. {2}.
Category:
Other
Cause:
Oracle Reports Builder encountered the identified PL/SQL error while running a report.
Action:
Edit and recompile the PL/SQL in the report to avoid this error.
REP-00453
PL/SQL error {0} was encountered. {1}. {2}. {3}.
Category:
Other
Cause:
Oracle Reports Builder encountered the identified PL/SQL error while running a report.
Action:
Edit and recompile the PL/SQL in the report to avoid this error.
REP-00490
An internal error occurred: Toolkit context unavailable.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00491
Data truncation is possible in column {0}.
Category:
Data
Cause:
The database column's width in the report is defined to be less than its width in the database. This can sometimes occur when the columns in the database are updated subsequent to the report being defined. This warning is raised only when RUNDEBUG is YES.
Action:
Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement field and then accept the SQL Query Statement dialog.
REP-00492
The token {0} is unrecognized.
Category:
Other
Cause:
The SELECT statement entered contains an item that is not part of SQL syntax.
Action:
Review the SELECT statement and ensure that it follows SQL syntax.
REP-00493
An internal error occurred: Unable to expand lexical references.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00494
An internal error occurred: Unable to process lexical references.
Category:
Process
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00495
An internal error occurred: Unable to tokenize the query.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00496
An internal error occurred: Unable to parse the query.
Category:
Other
Cause:
The SQL statement entered cannot be parsed because it contains an error.
Action:
Review the SQL statement to ensure correct syntax. For more information, see the SQL Language Reference Manual.
REP-00497
An internal error occurred: Query failed in rodslt.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00498
The number of columns selected by the query is incompatible with the report definition.
Category:
Other
Cause:
The query is selecting more columns than the report definition is expecting. This can happen when using an external query and the query has been changed since the report was defined.
Action:
Update the report definition so that it accepts the changed query. For example, go to the SQL Query Statement dialog for the query that references the changed external query and modify it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated.
REP-00499
Column {0} selected by the query is incompatible with the report definition.
Category:
Other
Cause:
The column from the database does not match the column in the report definition. The possible causes of this error include the following: Case 1: The definition of the column in the database has changed since the report was defined. Case 2: The report uses an external query and the external query was changed since the report was defined.
Action:
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 data type of the column has changed, reaccept the SQL Query Statement dialog external query so the column in the report definition has its data type 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 SQL Query Statement dialog that references the changed external query and accept it. Formulas, summaries, and fields that rely on any changed columns may also need to be updated.
REP-00500
The number entered is out of range.
Category:
Other
Cause:
The number specified is too large.
Action:
Check the limits of the field. Look in the chapter where the field is described and enter a number that is within the limits.
REP-00501
The specified database cannot be connected.
Category:
Other
Cause:
Oracle Reports Builder could not connect to Oracle The possible causes of this error include the following: Case 1: The Oracle database is temporarily unavailable. Case 2: The connect information was not valid.
Action:
Take the following actions to correct this error: If Case 1: Retry the operation. Contact the system administrator if the problem persists. Note that after three failed attempts, Oracle Reports Builder closes. If Case 2: Verify the connect information, and try to connect again. Note that after three failed attempts, Oracle Reports Builder closes.
REP-00502
An error occurred attempting to open terminal file {0}.
Category:
Other
Cause:
Oracle Reports Builder was unable to open the terminal definition file specified. Either the name of the file was specified incorrectly after the TERM keyword, or the file was not found.
Action:
Verify the name of the terminal definition file, and its path. If the problem persists, contact the system administrator.
REP-00503
The report name is invalid.
Category:
Other
Cause:
An invalid name was specified for the name of a report.
Action:
Specify a valid report name.
REP-00504
The specified database is not connected.
Category:
Other
Cause:
An attempt was made to perform an operation that requires a connection to the database, but no database connection was established.
Action:
Select File, then Connect to connect to the database.
REP-00505
The width for this column is not valid.
Category:
Other
Cause:
The value entered in Width was invalid. The possible causes of this error include the following: Case 1: Zero or a negative number was entered. Width must be greater than zero. Case 2: Something that was not a number was entered. Case 3: For a column of non-numeric data type, a width of the form (x, y) was entered, where x is the precision and y is the scale. This type of Width specification is only valid when the data type is Number.
Action:
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 data type of the column to Number.
REP-00506
Database columns cannot be moved between queries.
Category:
Other
Cause:
An attempt was made to move a column into another group belonging to another query and the column is a database column. A database column must be selected by the query that owns its group.
Action:
Select the column, if possible, in the query that owns the group to which it should be moved.
REP-00507
The file name is invalid.
Category:
Other
Cause:
In a file selection dialog box, the dialog box was accepted without specifying a file name.
Action:
Enter a name and then accept or cancel the dialog box.
REP-00508
The object name is invalid.
Category:
Other
Cause:
In a database object selection dialog box, the dialog box was accepted without specifying an object name.
Action:
Enter a name and then accept or cancel the dialog box.
REP-00509
The number value is invalid.
Category:
Other
Cause:
In a numeric field, something other than a digit or a decimal point was entered.
Action:
Enter a number that contains only digits and, if necessary, a decimal point.
REP-00510
The Unit of Measurement value is invalid.
Category:
Other
Cause:
An invalid unit of measurement was entered in the Unit of Measurement field.
Action:
Select the desired option from the list of values: 'Character', 'Inch', 'Centimeter' or 'Point'
REP-00511
The Panel Print Order value is invalid.
Category:
Other
Cause:
The Panel Print Order entered was not one of the two valid options.
Action:
Select the desired option from the list of values: 'Across/Down' or 'Down/Across'.
REP-00512
The number value is invalid.
Category:
Other
Cause:
The number entered was a decimal value and Oracle Reports Builder was expecting a non-decimal value.
Action:
Enter a non-decimal value.
REP-00513
The Unit of Measurement value is invalid.
Category:
Other
Cause:
The Unit of Measurement is blank and an attempt was made to move to another setting.
Action:
Select an option for Unit of Measurement.
REP-00514
The Page Size value is invalid.
Category:
Other
Cause:
The Page Width and/or Page Height settings were left blank and they require a value.
Action:
Enter a number for Page Width and/or Page Height.
REP-00515
The Parameter Form Size value is invalid.
Category:
Other
Cause:
The Parameter Form Width and/or Parameter Form Height settings were left blank and they require a value.
Action:
Enter a number for Parameter Form Width and/or Parameter Form Height.
REP-00516
The Page Size value is invalid.
Category:
Other
Cause:
The value entered for Page Size was not in character units, and Page Size requires character units.
Action:
Enter a value in characters for Page Size.
REP-00517
The Form Size value is invalid.
Category:
Other
Cause:
The value entered for Form Size was not in character units, and Form Size requires character units.
Action:
Enter a value in characters for Form Size.
REP-00518
The Object Access value is invalid.
Category:
Other
Cause:
The Object Access setting entered was not one of the three valid choices.
Action:
Select an option from the list of values: Database, File, or File/Database.
REP-00519
The Default Text Edit Mode value is invalid.
Category:
Other
Cause:
The Default Text Edit Mode entered was not one of the two valid choices.
Action:
Select an option from the list of values: Insert or Replace.
REP-00520
The Group/Frame Indentation value is invalid.
Category:
Other
Cause:
The value entered for Group/Frame Indentation was outside the valid range of values.
Action:
Enter a number between 0 and 4.
REP-00521
The name {0} is not valid.
Category:
Other
Cause:
An object was given an invalid name.
Action:
Verify the naming conventions for the object type.
REP-00522
A default layout cannot be built because this report has no groups.
Category:
Other
Cause:
Insert>Report Block was selected or a region was drawn using the Report Block tool in the Paper Layout editor before creating a query. A data source is required in order to create a default layout.
Action:
Create one or more queries, then retry the operation.
REP-00523
The Default Layout Style is invalid.
Category:
Other
Cause:
The Default Layout Style entered is not one of the valid options.
Action:
Select a layout style from the list of values.
REP-00524
The Print Direction is invalid.
Category:
Other
Cause:
The Repeat value entered is not one of the valid options.
Action:
Select a value for Repeat from the list of values.
REP-00525
The destination type is invalid.
Category:
Other
Cause:
The destination type entered for the system parameter DESTYPE is not one of the valid options. Possible causes of this error include the following: Case 1: An invalid value was entered for Destination Type in the Runtime Parameter Form. Case 2: An invalid value was entered for Initial Value in the Parameter Property Inspector for DESTYPE.
Action:
Take the following actions to correct this error: If Case 1: Enter one of the valid values, Screen, File, Printer, Mail, or Sysout. If Case 2: Select a value for Initial Value from the list of the values.
REP-00526
The initial value entered is longer than the parameter width.
Category:
Other
Cause:
The value entered is too long for the parameter on the Parameter Property Inspector. The possible causes of this error include the following: Case 1: The Initial Value entered is too big, given what was specified for the parameter's Width. Case 2: The Width entered is too small to contain the values to be entered for the parameter.
Action:
Take the following actions to correct this error: If Case 1: Reenter the Initial Value, making sure that it is not wider than what is specified in Width. If Case 2: Delete the Initial Value. Move to the Width setting for the parameter and increase it such that it can contain the Initial Value specified. Reenter the Initial Value.
REP-00527
A system parameter cannot be deleted.
Category:
Other
Cause:
An attempt was amde to delete a system parameter from the Parameter Property Inspector. This is not allowed.
Action:
To remove the system parameter from the Runtime Parameter Form, suppress the display of the parameter.
REP-00528
The data type value is invalid.
Category:
Data
Cause:
The value entered in Datatype for the parameter is not a valid data type.
Action:
Select a value for Datatype from the list of values: Character, Number, or Date.
REP-00529
The Type value is invalid.
Category:
Other
Cause:
The value entered in Type for the boilerplate is not a valid type.
Action:
Select a value for Type from the list of values: Box, Graphic, Line, or Text.
REP-00530
The file is too long. It will be truncated to fit.
Category:
Other
Cause:
An attempt was made to import a file into a field that has a maximum width less than the size of the file. Oracle Reports Builder only imported as much of the file as could fit in the field.
Action:
To import the entire file, increase the size of the field.
REP-00531
The Object Type is invalid.
Category:
Other
Cause:
In the Navigate to Object dialog box, the value entered for Object Type was invalid.
Action:
Select a value from the list of values.
REP-00532
There is no object of that type with this name.
Category:
Other
Cause:
The value entered in the Object Name field of the Navigate to Object dialog box does not correspond to an object of the specified type in the report.
Action:
Verify the name and that the object is contained in the current report.
REP-00533
Import is allowed only to a text entry field.
Category:
Other
Cause:
Import was selected from the Edit menu while in a non-text entry field (for example, a field that accepts only a number).
Action:
Move to a text entry field to perform an import operation.
REP-00534
Export is allowed only from a text entry field.
Category:
Other
Cause:
Export was selected from the Edit menu while in a non-text entry field (for example, a field that accepts only a number).
Action:
Move to a text entry field to perform an export operation.
REP-00535
No object named {0} exists in the database.
Category:
Other
Cause:
An attempt was made to perform an operation on a document stored in the database, but Oracle Reports Builder could not find the object.
Action:
Verify the name and connection to the database where the document resides.
REP-00536
An object in the database cannot be deleted without ownership.
Category:
Other
Cause:
An attempt was made to delete an object without ownership privileges.
Action:
Request that the owner delete the object.
REP-00537
An object in the database cannot be renamed without ownership.
Category:
Other
Cause:
An attempt was made to rename an object without ownership privileges.
Action:
Request that the owner rename the object.
REP-00538
An object named {0} already exists in the database.
Category:
Other
Cause:
The name entered for the object is already used for an existing object.
Action:
Provide a different name for the object to avoid the conflict or delete the existing object.
REP-00539
The default Parameter Form cannot fit in {0} pages.
Category:
Other
Cause:
The default Parameter Form is too big to fit on the number of pages allocated.
Action:
In the report's Property Inspector, under Parameter Form Window, set the Number of Pages property to the maximum number of pages that the Parameter Form can span.
REP-00540
The page size is too small for the default Parameter Form.
Category:
Other
Cause:
The current Form Width and Form Height settings are too small for the default Parameter Form.
Action:
Increase the size of the Parameter Form pages in the Report Property Inspector by changing Form Width and Form Height. Alternatively, select Tools>Default Parameter Form to default the Parameter Form and reduce its size by editing it in the Parameter Form editor.
REP-00541
The source must be a report.
Category:
Other
Cause:
For Reports Runtime, Converter, or Tools>File Conversion, something other than a report was specified as the source. These operations all require a report as their source.
Action:
Specify a report as the source for the operation.
REP-00542
No date masks have been specified as preferences.
Category:
Other
Cause:
While in the Parameter or Field Property Inspector of a parameter/field of Type Date, the List button was selected for Input Mask or Format Mask, but no masks are specified in the Date Mask list of the Preferences tab of the Tools Options dialog box.
Action:
Enter a date format mask manually or go to the Preferences tab of the Tools Options dialog box and enter some date format masks in the Date Mask list.
REP-00543
No number masks have been specified as preferences.
Category:
Other
Cause:
While in the Parameter or Field Property Inspector of a parameter/field of Type Number, the List button was selected for Input Mask or Format Mask, but no masks are specified in the Number Mask list of the Preferences tab of the Tools Options dialog box.
Action:
Enter a number format mask manually or go to the Preferences tab of the Tools Options dialog and enter some number format masks in the Number Mask list.
REP-00544
The online help system is not available.
Category:
Other
Cause:
Online help was not found. This may have happened because the help files are not installed or because of a help system error.
Action:
Install Developer Tools during Oracle Fusion Middleware installation to install Oracle Reports Builder, which includes the Oracle Reports Online Help. Or, view the Reports Online Help on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/reports/index.html.
REP-00545
The number must be greater than 0.
Category:
Other
Cause:
Zero (0) was entered for Page Width, Page Height, or Logical Page Size in the Report Property Inspector.
Action:
Enter a number greater than zero for Page Width, Page Height, or Logical Page Size.
REP-00546
The parameter value is invalid.
Category:
Other
Cause:
In the Runtime Parameter Form, the parameter value entered was invalid.
Action:
Retry the operation with a valid value for the parameter.
REP-00548
An error occurred initializing Oracle Toolkit.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00549
The DESTYPE value is invalid.
Category:
Other
Cause:
An attempt was made to run a report in the background (that is, BATCH=YES), but DESTYPE specified was invalid for running in the background.
Action:
Change the DESTYPE to File, Printer, Mail, or Sysout, or do not run the report with BATCH=YES.
REP-00550
The parent group name is invalid.
Category:
Other
Cause:
The name entered does not identify a valid parent group in the report being defined.
Action:
Select a group from the list of values.
REP-00551
The parent group column is invalid.
Category:
Other
Cause:
The name entered does not identify a valid parent column in the report being defined. The column specified does not exist in the parent group.
Action:
Select a column from the list of values. If the required column does not appear, add it to the SELECT statement of the parent query of the group specified in Parent Group.
REP-00552
The child column name is invalid.
Category:
Other
Cause:
The name entered does not identify a valid child column in the report being defined. The column specified does not exist in the query.
Action:
Select a column from the list of values. If the required column does not appear, add it to the SELECT statement of the query.
REP-00553
The condition is invalid.
Category:
Other
Cause:
The Condition entered for the query is not one of the valid choices.
Action:
Select a value from the list of values for Condition.
REP-00554
The SQL clause value is invalid.
Category:
Other
Cause:
The value entered in SQL Clause is not one of the valid choices.
Action:
Select a value from the list of values for SQL Clause: WHERE, HAVING, or START WITH.
REP-00555
START WITH is Oracle-specific SQL syntax. The report will not run against a non-Oracle database.
Category:
Other
Cause:
The START WITH clause is only available with the Oracle database, but there is no connection or a non-Oracle database connection.
Action:
Either run the report against an Oracle database or remove the START WITH clause before running it against a non-Oracle database.
REP-00556
No data links are created. No foreign key in the child query {0} refers to a primary key in the parent query {1}.
Category:
Data
Cause:
An attempt was made to create a query-to-query link but no foreign key exists in the child query.
Action:
Verify that the tables are accessible, and add the appropriate column constraints if desired.
REP-00558
The query {0} created the lexical parameter {1}.
Category:
Other
Cause:
The specified query references one or more lexical parameters that did not exist.
Action:
No action is needed. Oracle Reports Builder has already created the necessary lexical parameters.
REP-00559
The query {0} has created the bind parameter {1}.
Category:
Other
Cause:
The specified query references one or more bind parameters that did not exist.
Action:
No action is needed. Oracle Reports Builder has already created the necessary bind parameters.
REP-00560
The group name value is invalid.
Category:
Other
Cause:
The group name entered in Group is not a valid group for the column. The group specified does not exist or cannot own the column.
Action:
Create or modify the group such that it can own the column. A database column must be owned by the group associated with the query that selects it. A summary or formula column must be owned by a group that is below the groups that owns the columns being summarized in the group hierarchy (that is, the order of groups as they appear in the Data Model editor).
REP-00561
The type value is invalid.
Category:
Other
Cause:
The value entered in Type for the column was not one of the valid choices.
Action:
Select a value from the list of values for the column's Type: Formula, Summary, or Placeholder.
REP-00562
The column data type value is invalid.
Category:
Data
Cause:
The value entered in Datatype was not one of the valid choices.
Action:
Select a value from the list of values for Datatype.
REP-00563
The data type value is invalid.
Category:
Data
Cause:
The value entered in Datatype was not one of the valid choices.
Action:
Select a value from the list of values for Datatype: Ascending, Descending, or blank.
REP-00564
The file type value is invalid.
Category:
Other
Cause:
The file type value entered in Read From File was not one of the valid types.
Action:
Select a file type from the list of values for Read from File.
REP-00565
The function value is invalid.
Category:
Other
Cause:
The function entered for Function was not one of the valid choices.
Action:
Select one of the functions from the list of values.
REP-00566
The database column cannot be deleted.
Category:
Other
Cause:
An attempt was made to delete a column with a Type of Database.
Action:
Remove the column from the SELECT list of the query that selects it and the column will be deleted automatically.
REP-00567
The summary source value is invalid.
Category:
Other
Cause:
The column entered in Source for the summary was not one of the valid choices. The possible causes of this error include the following: Case 1: The column does not exist. Case 2: The data type of the Source is Character or Date. Numeric functions (such as Percent, Sum, or Average) require a data type of Number.
Action:
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 data type Number.
REP-00568
The Value if Null value is invalid.
Category:
Other
Cause:
The value of Value if Null in the Column Property Inspector is invalid for that column. For example, if data type of the column is Number, and a character string was sepcified in Value if Null.
Action:
Specify a valid value for Value if Null.
REP-00569
The query is not parsable, which invalidates associated data link(s).
Category:
Other
Cause:
The query entered in query dialog is not parsable.
Action:
Modify the query and re-create data link(s).
REP-00580
The filter type value is invalid.
Category:
Other
Cause:
The value entered for Type under Filter was not one of the valid choices.
Action:
Select one of the filter types from the list of values.
REP-00581
This is the only group of query {0}, and may not be deleted.
Category:
Other
Cause:
An attempt was made to delete a group that is the only one of the query. Each query must have at least one group.
Action:
To delete the group, delete the group's query.
REP-00582
A group cannot be moved out of its query.
Category:
Other
Cause:
An attempt was made to move a group between queries. Groups can only be moved within the set of groups belonging to the same query.
Action:
Create a group similar to the one that was attempt to be moved under the other query, if possible.
REP-00583
The SQL SELECT Statement is invalid.
Category:
Other
Cause:
The SQL SELECT statement entered was not valid.
Action:
Check the SELECT statement for errors and correct them. For more information, see the SQL Language Reference Manual.
REP-00584
Lexical parameters are not permitted in external queries.
Category:
Other
Cause:
A lexical reference was made in an external query. This is not allowed.
Action:
Delete the reference altogether or, if possible, change it to a bind reference.
REP-00585
The arent group {0} for child query {1} does not exist.
Category:
Other
Cause:
A query was deleted without deleting references to its groups in data links. This usually happens when a query is deleted without cascading the deletion to its associated objects.
Action:
Update the data link in the child query.
REP-00586
Adding this data link will create a cycle.
Category:
Data
Cause:
The group 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 it is linked.
Action:
If possible, move the group such that it is not a child of the query and therefore eligible to be its parent group.
REP-00587
The PL/SQL group filter condition value is invalid.
Category:
Other
Cause:
Condition was selected for Filter Type, but no PL/SQL condition was entered.
Action:
Enter the PL/SQL or change the Filter Type.
REP-00588
The PL/SQL column formula value is invalid.
Category:
Other
Cause:
Formula was selected as the column's Type, but no PL/SQL for the formula was entered.
Action:
Create a formula or change the column's Type.
REP-00590
Only {0} pages were formatted. The last page is shown.
Category:
Other
Cause:
In the Previewer, an attempt was made to go to a page number that is larger than the total number of pages formatted.
Action:
No action is needed. Do not attempt scroll down from the last page of the report.
REP-00591
The first page is already shown.
Category:
Other
Cause:
In the Previewer, First was selected on the first page of the report.
Action:
No action is needed. Do not attempt to scroll up from the first page of the report.
REP-00592
The last page is already show.
Category:
Other
Cause:
In the Previewer, Last was selected on the last page of the report.
Action:
No action is needed. Do not attempt to scroll down from the last page of the report.
REP-00593
Page {0} is the current page.
Category:
Other
Cause:
In the Previewer, the page number of the current page was entered.
Action:
Enter a different page number and select Go To.
REP-00594
No report output is generated.
Category:
Other
Cause:
The report generated no output.
Action:
Check the accompanying messages for errors in the data model and layout. If the problem persists, contact Oracle Support Services for assistance.
REP-00595
The report definition was modified. Rerunning report.
Category:
Other
Cause:
A report was run and while its output was still in the Previewer, the report definition was modified. The report is rerun to reflect the most recent changes
Action:
Save the changes, close the Previewer, and run the report again.
REP-00596
A page number cannot be greater than {0} or less than 1.
Category:
Other
Cause:
An invalid value was entered for the Page Number setting on the Field Property Inspector for a Parameter Form field. The most likely cause is that values entered were zero, a negative number, or a number that is larger than the largest allowable value.
Action:
Enter a number within the range shown in the message.
REP-00597
This operation is invalid, since it moves objects out of bounds.
Category:
Other
Cause:
An attempt was made to move editor objects in such a way that they would be off the screen.
Action:
Retry the operation so that it will not move objects off the screen.
REP-00598
The anchor end point is out of the boundary of the object.
Category:
Other
Cause:
In moving an anchor, the end point was moved off of the boundary of the object it anchors.
Action:
Move the anchor such that its endpoint is still on the boundary of the object.
REP-00599
This text boilerplate is not editable.
Category:
Other
Cause:
An attempt was made to edit the text of a file link text boilerplate object while it was displayed in the Paper Layout view.
Action:
To edit the text of a file link text boilerplate object, exit the report and edit the file containing the boilerplate text using a text editor.
REP-00600
No list of values is available for this field.
Category:
Other
Cause:
An attempt was made to access a list of values for the current field when none is available.
Action:
No action necessary.
REP-00601
The list of values for this field is empty.
Category:
Other
Cause:
An attempt was made 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 the report must be built first. For example, if a list of values is made up solely of column names and the data model is not complete, this error may display.
Action:
Build the report fully. If the error persists, contact Oracle Support Services.
REP-00602
The accessible tables cannot be queried.
Category:
Other
Cause:
The dictionary view of accessible tables is not present or not available.
Action:
See the system administrator.
REP-00603
Table {0} cannot be described.
Category:
Other
Cause:
The dictionary view of accessible tables is not present or not available.
Action:
See the system administrator.
REP-00604
The SELECT statement cannot be built.
Category:
Other
Cause:
The Table and Columns Names dialog box was accepted without anything selected with which to build the SELECT statement.
Action:
Select a table and, if desired, columns or the SELECT columns FROM table option, and then accept the dialog box. To exit the dialog box without building a SELECT statement, click Close.
REP-00606
Link file {0} cannot be read.
Category:
Other
Cause:
Case 1: The file specified in the Source Filename property for the file link boilerplate object cannot be found or its format does not match that specified in the File Format property. Case 2: The REPORTS_DEFAULT_DISPLAY environment variable is set to YES and the image format used is not supported.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file is stored in the specified directory under the specified name, and that it is saved in the specified format. If it is not, change the directory, file name, or format as appropriate. If Case 2: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
REP-00607
Run-only file {0} may not be opened.
Category:
Other
Cause:
An attempt was made to open a runfile (extension .rep). Runfiles cannot be opened, they can only be executed.
Action:
Open the report definition that is associated with the .rep file. It should have an extension of .rdf.
REP-00608
The Source Type is invalid.
Category:
Other
Cause:
Convert was selected from the File menu and the Source Type specified is not valid.
Action:
Select a valid Source Type from the list of values.
REP-00609
The Destination Type is invalid.
Category:
Other
Cause:
Convert was selected from the File menu and the Destination Type specified is not valid.
Action:
Select the Destination Type from the list of values.
REP-00610
An error occurred while attempting to print the screen. Verify that log file {0} is accessible.
Category:
Other
Cause:
Oracle Reports Builder attempted to write the contents of the screen to the file printdef.dat but could not locate the file.
Action:
To determine the proper location for printdef.dat, see the installation instructions.
REP-00611
The Destination Type value is not valid.
Category:
Other
Cause:
In the Runtime Parameter Form, the value provided for Destination Type that was not valid.
Action:
Specify a value of Screen, File, Printer, or Mail for Destination Type.
REP-00612
The date mask value is invalid.
Category:
Other
Cause:
The date mask entered does not correspond to any of the valid date masks.
Action:
Verify the date mask format. For more information, see the date and time format mask information in the Building Reports manual.
REP-00613
The Format Mask value does not match mask {0}.
Category:
Other
Cause:
The mask entered in Format Mask is not a valid mask. The possible causes of this error include the following: Case 1: The string entered as a mask contained invalid characters. Case 2: A number format mask was entered for a field with data type of Character.
Action:
Take the following actions to correct this error: If Case 1: Select a value from the list of values. For more information, see the date and time format mask information in the Building Reports manual. If Case 2: Change the data type of the field to be Number, if possible. If the field is supposed to be Character data type and cannot be changed, a format mask cannot be specified for it.
REP-00614
There is no window active for the Find and Replace action.
Category:
Other
Cause:
A Find and Replace operation was attempted using the Find And Replace dialog box, but the cursor was not positioned in an active Oracle Reports Builder window.
Action:
Position the cursor in a text entry field before performing a Find and Replace operation.
REP-00615
Find and Replace is valid only for a text entry field.
Category:
Other
Cause:
A Find and Replace operation was attempted using the Find And Replace dialog box, but the cursor was not positioned positioned in a text entry field. Find and Replace operations are valid only in text entry fields.
Action:
Position the cursor in a entry field before performing a Find and Replace operation.
REP-00616
Text cannot be replaced in an uneditable region.
Category:
Other
Cause:
Using the Find And Replace dialog box, text replacement was attempted in an inaccessible field.
Action:
Replace text only in editable regions.
REP-00617
The Runtime Parameter Form is already open. To run a new one, close the old one and run again.
Category:
Other
Cause:
An attempt was made to run a report with the Runtime Parameter Form already open.
Action:
Close the currently open Runtime Parameter Form and try running again.
REP-00619
A report cannot be run without a layout.
Category:
Other
Cause:
An attempt was made to run the report with no layout.
Action:
Create a layout, then run the report.
REP-00621
The Vertical Elasticity value is invalid.
Category:
Other
Cause:
The value entered for the object's Vertical Elasticity was not one of the valid values.
Action:
Select a value from the list of values.
REP-00622
The Horizontal Elasticity value is invalid.
Category:
Other
Cause:
The value entered for the object's Horizontal Elasticity was not one of the valid values.
Action:
Select a value from the list of values.
REP-00623
The Print Condition Type value is invalid.
Category:
Other
Cause:
The value entered for the Type of the Print Condition was not one of the valid values.
Action:
Select a value from the list of values.
REP-00624
The Print Condition Object value is invalid.
Category:
Other
Cause:
The value entered for the Object of the Print Condition was not one of the valid values.
Action:
Select a value from the list of values.
REP-00625
The Text Alignment value is invalid.
Category:
Other
Cause:
The value entered for Alignment was not one of the valid values. The value is not valid given the data type of the object. Flush/Left, Flush/Center, and Flush/Right are only valid for fields with data type of Character.
Action:
Select a value from the list of values.
REP-00626
The coordinate position value is invalid.
Category:
Other
Cause:
The x or y coordinate entered was not in the valid range for coordinates. Coordinates cannot be negative numbers.
Action:
Enter a coordinate that is in the valid range.
REP-00627
The object height or width must be a positive integer.
Category:
Other
Cause:
The Width or Height value entered was not a positive, whole number.
Action:
Enter a positive, whole number.
REP-00630
The value must be between {0} and {1}.
Category:
Other
Cause:
The number entered was too large or too small.
Action:
Specify a number that is within the range shown in the message.
REP-00631
The string must be no longer than {0} characters.
Category:
Other
Cause:
The string entered was too large.
Action:
Enter a string that is smaller than the number of characters shown in the message.
REP-00632
The value already exists in the list.
Category:
Other
Cause:
An attempt was made to add an item to a list, but the item was previously added to the list. For example, if an attempt was made to add lib1 to the report's Attached PL/SQL Library list, when lib1 was already found in the Attached PL/SQL Library list, this error displays.
Action:
Once an item has been added to a list, do not attempt to add it again.
REP-00633
No value is specified.
Category:
Other
Cause:
An attempt was made to perform a list operation on an item, but no item was specified. For example, if an attempt was made to add a PL/SQL library to the report's Attached PL/SQL Library list, but the PL/SQL Library field in the Attached PL/SQL Libraries dialog box was left blank and the Add button selected, this error displays.
Action:
Specify the item to add in the appropriate field before choosing a button.
REP-00634
The destination name must be shorter than {0} characters.
Category:
Other
Cause:
The destination specified (probably a file name) was too long.
Action:
Specify a destination that it is of valid length.
REP-00635
The value does not exist in the list.
Category:
Other
Cause:
The value specified was not in the list of valid choices.
Action:
Specify one of the valid choices in the list. If possible, use the list of values to ensure that it is a valid choice.
REP-00636
Property name {0} must be no longer than {1} characters. It will be truncated.
Category:
Other
Cause:
The string specified was longer than is allowable. It will be truncated.
Action:
Specify a shorter string.
REP-00637
Property name {0} must be no longer than {1} characters.
Category:
Other
Cause:
The file name specified was longer than is allowable.
Action:
Specify a shorter file name.
REP-00639
Set a valid DISPLAY value when REPORTS_DEFAULT_DISPLAY is set to NO.
Category:
Other
Cause:
REPORTS_DEFAULT_DISPLAY was set to NO and DISPLAY variable was not set.
Action:
Specify a valid value for DISPLAY when REPORTS_DEFAULT_DISPLAY is set to NO.
REP-00640
The field source value is invalid.
Category:
Other
Cause:
The Source value specified was invalid.
Action:
Select a value from the list of values.
REP-00650
The source group value is invalid.
Category:
Other
Cause:
The group name specified in Source for the repeating frame was invalid.
Action:
Select a value from the list of values.
REP-00651
The Print Direction value is invalid.
Category:
Other
Cause:
The Print Direction specified was not one of the valid values (Across, Across/Down, Down, Down/Across, and Matrix Cell).
Action:
Select a value from the list of values.
REP-00652
The Vertical Spacing value is invalid.
Category:
Other
Cause:
The Vertical Spacing specified was not a valid value.
Action:
Enter zero or a positive integer for Vertical Spacing.
REP-00653
The Horizontal Spacing value is invalid.
Category:
Other
Cause:
The Horizontal Spacing specified was not a valid value.
Action:
Enter zero or a positive integer for Horizontal Spacing.
REP-00654
The Maximum Records per Page value is invalid.
Category:
Other
Cause:
The Maximum Records per Page specified was not a valid value.
Action:
Enter blank or a positive integer for Maximum Records per Page.
REP-00655
The Minimum Widow Records value is invalid.
Category:
Other
Cause:
The Minimum Widow Records specified was not a valid value.
Action:
Enter blank or a positive integer for Minimum Widow Records.
REP-00660
The button source value is invalid.
Category:
Other
Cause:
Multimedia Column was selected as the source for the button action, but the source column was either not specified or invalid.
Action:
Specify a valid source column for the button action, containing sounds, video, or images.
REP-00661
The button source value is invalid.
Category:
Other
Cause:
Multimedia File was selected as the source for the button action, but the source file was either not specified or invalid.
Action:
Specify a valid source file for the button action, containing sounds, video, or images.
REP-00662
The button icon value is invalid.
Category:
Other
Cause:
Icon was selected as the button face, but the icon name was invalid.
Action:
Enter the name of a valid icon file in the text field provided. Include all necessary path information.
REP-00670
The boilerplate type value is invalid.
Category:
Other
Cause:
The Type specified for the boilerplate was not one of the valid values.
Action:
Select a Type from the list of values: Box, Line, Graphic, and Text.
REP-00671
The link file name value is invalid.
Category:
Other
Cause:
The file to which the file link boilerplate object was linked is not a valid file.
Action:
In the Property Inspector for the File Link boilerplate object, check that the Source Filename property is set to an existing file in the current directory.
REP-00672
The Minimum Widow Lines value is invalid.
Category:
Other
Cause:
The Minimum Widow Lines specified was not a valid value.
Action:
Enter blank or a positive integer for Minimum Widow Lines.
REP-00680
The anchoring object name value is invalid.
Category:
Other
Cause:
The object name entered in the Anchored To field of the Anchor Position dialog box was not the name of an object to which this object can be anchored.
Action:
Select an object name for Anchored To from the list of values.
REP-00681
The Edge value is invalid.
Category:
Other
Cause:
The Edge specified was not one of the valid values (Top, Left, Right, and Bottom).
Action:
Select a value for Parent Edge or Object Edge from the list of values.
REP-00682
The anchor point must be a percentage between 0 and 100.
Category:
Other
Cause:
The % specified was not in the valid range (0 to 100).
Action:
Enter a value in the valid range for %.
REP-00690
The starting page number value is invalid.
Category:
Other
Cause:
Start At was left blank.
Action:
Enter zero or a positive integer for Start At.
REP-00691
The page increment value is invalid.
Category:
Other
Cause:
Increment By was blank.
Action:
Enter zero or a positive whole number for Increment By.
REP-00692
The page number reset value is invalid.
Category:
Other
Cause:
Reset At was left blank.
Action:
Select a repeating frame name or &Report from the list of values to indicate where to reset the page number to its Start At value.
REP-00700
The color value is invalid.
Category:
Other
Cause:
The color specified was not one of the valid choices.
Action:
Select a color for the field from the list of values.
REP-00701
The pattern value is invalid.
Category:
Other
Cause:
The pattern specified was not one of the valid choices.
Action:
Select a pattern for the field from the list of values.
REP-00702
The pen width value is invalid.
Category:
Other
Cause:
The pen width specified was not one of the valid choices.
Action:
Select a pen width from the list of values.
REP-00703
The font value is invalid.
Category:
Other
Cause:
The font specified was not one of the valid choices.
Action:
Select a font from the list of values.
REP-00704
The text style value is invalid.
Category:
Other
Cause:
The text style specified was not one of the valid styles.
Action:
Select one of the styles from the list of values.
REP-00705
The text weight value is invalid.
Category:
Other
Cause:
The text weight specified was not one of the valid weights.
Action:
Select one of the weights from the list of values.
REP-00706
The text size value is invalid.
Category:
Other
Cause:
The point size specified was not one of the valid choices.
Action:
Select a valid point size from the list of values.
REP-00707
The text spacing value is invalid.
Category:
Other
Cause:
The spacing value specified was not in the valid range.
Action:
Enter a number in the valid range.
REP-00708
The character mode attribute value is invalid.
Category:
Other
Cause:
The character mode attribute specified was not valid. The values specified in Character Mode Attribute must be defined in the printer definition. To have these attributes appear in the list of values, they must also be listed in VISUAL_PREFS in the preferences file.
Action:
Select the desired values from the list of values. If the desired value is not in the list of values, check the printer definition to verify if the value is a valid one.
REP-00709
Sysout is only valid in batch mode.
Category:
Other
Cause:
Sysout was specified as the destination type when not running the report in batch mode. The possible causes of this error include the following: Case 1: Sysout was specified for DESTYPE in the Runtime Parameter Form. Case 2: Sysout was specified as the Initial Value for DESTYPE and was accepted when not running in batch mode. This may occur inadvertently when the Hide Parameter Form preference is checked.
Action:
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 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 the Initial Value is left as Sysout, do not run in non-batch mode with Hide Parameter Form checked.
REP-00710
The printer description file cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not find the printer description file specified for DESFORMAT.
Action:
Specify a valid printer description file for DESFORMAT (for example, dflt).
REP-00711
The destination type must be File, Printer, or Mail when printing from the Previewer.
Category:
Other
Cause:
The Print button was selected in the Previewer, but DESTYPE was restricted to a value other than File, Printer, or Mail.
Action:
Ensure that DESTYPE can be set to one of the valid values before attempting to print from the Previewer.
REP-00712
No printer is specified.
Category:
Other
Cause:
An attempt was made to print a report, without a printer name specified in either DESNAME or in the Printer Chooser dialog box.
Action:
Specify a valid printer name using DESNAME. If the same printer is often used, enter the printer name in the Printer Chooser dialog box. Remember that entering a printer name using DESFORMAT will override the printer name set in the Printer Chooser dialog box.
REP-00713
The printer name {0} specified by parameter {1} is invalid.
Category:
Other
Cause:
An attempt was made to generate a report, without a valid printer name specified in DESFORMAT (if DESTYPE was File or Mail) or DESNAME (if DESTYPE was Printer).
Action:
Specify a valid printer name for DESFORMAT if DESTYPE was File or Mail, or a valid printer name for DESNAME if DESTYPE was Printer.
REP-00714
The mail destination value is invalid.
Category:
Other
Cause:
An attempt was made to mail report output to another user, but did not specify a valid username for DESNAME.
Action:
Specify a valid username for DESNAME.
REP-00715
A trace file must be specified when tracing.
Category:
Other
Cause:
Trace mode or trace options were specified without specifying a trace file.
Action:
Specify a trace file.
REP-00716
The option specified for tracing is invalid.
Category:
Other
Cause:
Invalid trace options were specified.
Action:
Respecify trace options. For more information about trace options, see the Publishing Reports to the Web manual.
REP-00717
Options cannot be set or unset if not tracing.
Category:
Other
Cause:
An attempt was made to set or unset trace options while not tracing.
Action:
Begin tracing before attempting to set or unset options.
REP-00718
Trace break information cannot be traced with Reports Runtime.
Category:
Other
Cause:
An attempt was made to trace breaks while running the report using Reports Runtime.
Action:
Do not specify the Break option when using Reports Runtime.
REP-00719
Trace file {0} can be written to.
Category:
Other
Cause:
A trace file was specified that does not have write permission.
Action:
Verify the trace file name is valid.
REP-00720
The repeating frame value is invalid.
Category:
Other
Cause:
The repeating frame specified as the Vertical or Horizontal Frame in the Matrix Property Inspector is not valid.
Action:
Select a repeating frame name from the list of values.
REP-00721
The cross product group value is invalid.
Category:
Other
Cause:
The group entered for Cross Product Group in the Matrix Property Inspector is not valid.
Action:
Select a group name from the list of values.
REP-00723
Uncompiled program units exist, possibly due to no connection to the database.
Category:
Other
Cause:
An attempt was made to convert a report or load an old report, containing PL/SQL which needed to be recompiled.
Action:
Load the report using Oracle Reports Builder, connect to database, and recompile the DE program units.
REP-00724
The value of column {0} cannot be retrieved.
Category:
Other
Cause:
An attempt was made to get the value of the specified column by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A column value can only be retrieved during report execution.
Action:
Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a column when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to obtain the column value.
REP-00725
The value of column {0} cannot be set.
Category:
Other
Cause:
An attempt was made to set the value of the specified column by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A column value can only be set during report execution.
Action:
Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a column when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to set the column value.
REP-00726
The value of parameter {0} cannot be retrieved.
Category:
Other
Cause:
An attempt was made to get the value of the specified parameter by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A parameter value can only be retrieved during Parameter Form execution.
Action:
Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to get the value of a parameter when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to obtain the parameter value.
REP-00727
The value of parameter {0} cannot be set.
Category:
Other
Cause:
An attempt was made to set the value of the specified parameter by either issuing a command from the command line of the PL/SQL Interpreter or by executing a stand-alone PL/SQL program unit. A parameter value can only be set during Parameter Form execution.
Action:
Do not attempt to use the PL/SQL Interpreter or a PL/SQL program unit to set the value of a parameter when the report has suspended execution (for example, at a breakpoint). Use an alternate method, such as one of the report-level triggers, to set the parameter value.
REP-00728
Column {0} may not be referenced by parameter triggers.
Category:
Other
Cause:
An attempt was made to reference a column in a parameter-related trigger (Before Form, After Form, Validation), which is not allowed.
Action:
Remove the references from the parameter-related triggers and add them to the Before Report trigger.
REP-00729
The program unit {0} of size {1} bytes is too big to be loaded for the current platform at the limit of {2}.
Category:
Other
Cause:
The program unit was created on another operating platform and it too large to be loaded into the current operating platform.
Action:
Reduce the size of the PL/SQL program unit.
REP-00730
The bind variable is not defined.
Category:
Other
Cause:
A bind reference was made to a parameter or column that has not been defined yet.
Action:
Create the parameter definition or column before making a bind reference to it. Or, attempt to use a lexical reference rather than a bind reference.
REP-00732
An error occurred destroying the program unit.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00733
The specified name already exists.
Category:
Other
Cause:
An attempt was made to create a PL/SQL subprogram whose name is identical to an existing subprogram stored in the report.
Action:
Rename the new subprogram so that it does not conflict with any existing subprograms.
REP-00734
No argument is allowed.
Category:
Other
Cause:
The PL/SQL function or procedure entered requires arguments in a PL/SQL field that does not allow PL/SQL with arguments--for example, in a Format Trigger field, a Formula field, or as a group filter.
Action:
Remove the arguments from the PL/SQL source.
REP-00735
Program unit cannot be loaded.
Category:
Other
Cause:
Oracle Reports Builder could not load the entire program unit. It could be that the program unit references one or more objects stored in the database, but these objects were not found.
Action:
Verify the connection to the correct database, and ensure that the program unit is making the correct references.
REP-00736
Uncompiled program units exist.
Category:
Other
Cause:
An attempt was made to convert a report, or load an old report, containing PL/SQL that needed to be recompiled.
Action:
Load the report using Oracle Reports Builder and modify the program units.
REP-00737
The return type {0} is invalid.
Category:
Other
Cause:
The PL/SQL entered does not have the appropriate return type.
Action:
Change the return type of the function to the one specified in the message.
REP-00738
A function is required.
Category:
Other
Cause:
Something other than a function was entered where a function is required.
Action:
Enter a function.
REP-00739
Compiled PL/SQL from other platform cannot be executed.
Category:
Other
Cause:
An attempt was made 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 Builder could not recompile the PL/SQL on the current platform.
Action:
Run the report on the original platform where the PL/SQL was compiled. Alternatively, obtain a copy of the source report with the source PL/SQL and recompile it from the current platform.
REP-00740
An anchor cannot be anchored with another object.
Category:
Other
Cause:
An attempt was made to anchor an anchor to another layout object, or anchor a layout object to an anchor.
Action:
Remove any anchors of anchors with other layout objects.
REP-00741
A matrix cannot be anchored with another object.
Category:
Other
Cause:
An attempt was made to anchor a matrix object to another layout object, or anchor a layout object to a matrix object.
Action:
Remove any anchors of matrix objects with other layout objects.
REP-00742
A margin cannot be anchored with another object.
Category:
Other
Cause:
An attempt was made to anchor the margin to a layout object, or anchor a layout object to the margin.
Action:
Remove any anchors of the margin to layout objects.
REP-00743
A matrix repeating frame cannot be anchored with another object.
Category:
Other
Cause:
An attempt was made to anchor a matrix repeating frame with a Print Direction of Down or Across to another layout object.
Action:
Remove any anchors of matrix repeating frames with Print Directions of Down or Across to other layout objects.
REP-00744
An anchor must have different parent and child objects.
Category:
Other
Cause:
An attempt was made to create an anchor whose parent and child objects are the same; that is, anchor an object to itself.
Action:
Ensure that all anchors have different parent and child objects.
REP-00745
An object cannot be anchored more than once.
Category:
Other
Cause:
An attempt was made to create two anchors between the same two layout objects.
Action:
Ensure that only one anchor exists between the same two layout objects.
REP-00746
The PL/SQL references an object that does not exist.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00747
A Before Form trigger cannot reference a report column.
Category:
Other
Cause:
The Before Form trigger for the report references a column in the report, which is not allowed.
Action:
Remove any column references from the Before Form trigger. To set the value of a column, do it from the Before Report trigger.
REP-00748
A parameter trigger cannot reference a report column.
Category:
Other
Cause:
A Validation trigger for a parameter references one or more columns in the report, which is not allowed.
Action:
Remove any column references in the Validation trigger of the Parameter Property Inspector.
REP-00749
An After Form trigger cannot reference a report column.
Category:
Other
Cause:
The After Form trigger for the report references a column in the report, which is not allowed.
Action:
Remove any column references in the After Form trigger. To set the value of a column, do it from the Before Report trigger.
REP-00750
An error occurred closing the PL/SQL library.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00751
An error occurred accessing program units from PL/SQL library.
Category:
Other
Cause:
An abnormal condition was encountered. To save changes made to the PL/SQL library, consider saving it under a different name.
Action:
For assistance, contact Oracle Support Services.
REP-00752
The PL/SQL library cannot be saved.
Category:
Other
Cause:
An abnormal condition was encountered. To save changes made to the PL/SQL library, consider saving it under a different name.
Action:
For assistance, contact Oracle Support Services.
REP-00753
An error occurred attaching PL/SQL library {0}.
Category:
Other
Cause:
An attempt was made to attach an invalid PL/SQL library. This could happen because the PL/SQL library is corrupted, or because the file or object specified does not contain a PL/SQL library.
Action:
Verify that the file or object specified contains a valid PL/SQL library.
REP-00754
An error occurred inserting program units into a PL/SQL library.
Category:
Other
Cause:
An attempt was made to save a program unit into a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.
Action:
Verify the file or object specified contains a valid PL/SQL library and consider saving the current program unit.
REP-00755
An error occurred opening PL/SQL library {0}.
Category:
Other
Cause:
An attempt was made to open a corrupted PL/SQL library, or a file or object that is not a PL/SQL library.
Action:
Verify that the file or object contains a valid PL/SQL library.
REP-00756
PL/SQL library {0} cannot be found.
Category:
Other
Cause:
An attempt was made to attach a PL/SQL library that does not exist, or to open a report with one or more attached PL/SQL libraries that were not found.
Action:
Verify that the file or object exists. If the object is a report, reattach the PL/SQL library.
REP-00757
The external location spec cannot be created.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00758
PL/SQL library {0} is already in use.
Category:
Other
Cause:
An attempt was made to attach a PL/SQL library that has the same name as another PL/SQL library that is already attached. This could happen if a file was renamed that contains a PL/SQL library, but the internal name recognized by Oracle Reports Builder was not changed.
Action:
Save the PL/SQL library under a different name.
REP-00759
One or more PL/SQL libraries have been modified since the report was saved; the PL/SQL will be recompiled.
Category:
Other
Cause:
An attempt was made to open or run a report that references one or more PL/SQL libraries, and part or all of the PL/SQL has been modified but not compiled since the report was last saved.
Action:
No action is necessary; Oracle Reports Builder will recompile the PL/SQL.
REP-00760
A print document session is currently in process.
Category:
Other
Cause:
From the File menu, Administration Report was already selected to produce a report on one or more reports.
Action:
Finish producing the current report on reports, then try again to run another report on reports.
REP-00761
The resource for printing the report cannot be opened.
Category:
Other
Cause:
Oracle Reports Builder cannot open the reports that document other reports for printing.
Action:
Verify that the reports that document other reports (shipped with Oracle Reports Builder) are located in the proper directory. For details on the exact location of these reports, see the installation instructions.
REP-00762
The user ID for the interoffice login is invalid.
Category:
Other
Cause:
An attempt was made to save report output to the interoffice repository, but a valid connect string was not specified for the interoffice document server.
Action:
Specify a valid connect string for the interoffice document server.
REP-00763
The interoffice client {0} cannot be launched.
Category:
Other
Cause:
An attempt was made to launch the interoffice client, but it failed to run.
Action:
Verify that the interoffice client is properly installed.
REP-00764
Error {0} occurred running the interoffice client.
Category:
Other
Cause:
The interoffice client was running to check in the documents into repository, but it failed on the indicated error code.
Action:
Check the interoffice error code/message for the reason of failure.
REP-00769
Sending to mail from the Parameter Form when the Paper Design view is open is invalid.
Category:
Other
Cause:
The Paper Design is open and destype is set to mail.
Action:
Select mail directly from the Paper Design view and not from the Parameter Form.
REP-00770
The Before Form trigger failed.
Category:
Other
Cause:
The Before Form trigger in the report returned false.
Action:
Make the appropriate changes (either to the PL/SQL source in the Before Form trigger or to the report) to make the trigger return true.
REP-00771
The After Form trigger failed.
Category:
Other
Cause:
The After Form trigger in the report returned false.
Action:
Make the appropriate changes (either to the PL/SQL source in the After Form trigger or to the report) to make the trigger return true.
REP-00772
Parameter Form Fields {0} and {1} may not have the same Source.
Category:
Other
Cause:
The same Source was specified for two Parameter Form fields. Fields on the Runtime Parameter Form must have unique sources.
Action:
Change the Source of one of the fields.
REP-00773
No Source was specified for Parameter Form Field {0}.
Category:
Other
Cause:
A Source was not specified for a Parameter Form field or the source parameter was deleted from the data model. Fields on the Runtime Parameter Form must have a source.
Action:
Specify a valid Source for the Parameter Form field.
REP-00774
No selectable values are available for LOV parameter {0}.
Category:
Other
Cause:
Either no values were specified for the LOV parameter's select list, or values were specified that cannot be selected.
Action:
Check the SELECT statement or selectable value list of the parameter to ensure that the specified values are selectable.
REP-00775
The data type of the first column of the SELECT statement does not match the data type of LOV parameter {0}.
Category:
Data
Cause:
The data type of the first column specified in the SELECT statement does not match the data type specified for the LOV parameter.
Action:
Check the data type of the LOV parameter, the SELECT statement, and the columns in the database tables accessed by the SELECT statement to ensure that they match.
REP-00776
There are columns with values in segmented memory when populating LOV parameter {0}. They will be ignored.
Category:
Memory
Cause:
Columns were selected with values in segmented memory for the LOV parameter's select list, which is not allowed.
Action:
Select different columns or move the column values.
REP-00777
There are columns whose types cannot be handled when populating LOV parameter {0}. They will be ignored.
Category:
Other
Cause:
Columns were selected whose types cannot be handled (for example, binary data).
Action:
Select different columns.
REP-00778
Some columns cannot be formatted correctly when populating LOV parameter {0}. They will be ignored.
Category:
Other
Cause:
The SELECT statement selecting values for the parameter's LOV retrieves columns whose values cannot be formatted according to their datatypes.
Action:
Convert the values to valid ones or check the database to see if the values of the columns are valid.
REP-00779
Some items of LOV parameter {0} are too long. These items will be truncated.
Category:
Other
Cause:
The items specified or columns selected contain some values that are too long to include in the LOV parameter's select list.
Action:
Check the values of the items and reduce their length if necessary.
REP-00780
The initial value entered is invalid against the input mask {0}.
Category:
Other
Cause:
The value entered in the Initial Value field violates the mask specified in the Input Mask field.
Action:
Either enter a different value in Initial Value or change the mask in Input Mask.
REP-00781
Bind variables are not allowed in the SELECT statement.
Category:
Other
Cause:
Bbind variables were included in the SELECT statement.
Action:
Remove the bind variables from the SELECT statement.
REP-00782
The data type of the parameter does not match the data type of its source columns.
Category:
Data
Cause:
The column selected has an invalid data type to furnish values for the LOV parameter's select list.
Action:
Change the column's data type or specify a different column.
REP-00783
The possible values list has bad syntax.
Category:
Other
Cause:
Incorrect syntax was specified to create the list of possible values for the LOV parameter.
Action:
Edit the possible values list to ensure that it is a proper comma-separated list.
REP-00784
A possible value has invalid width.
Category:
Other
Cause:
A value specified for the LOV parameter's list of possible values has an invalid width.
Action:
Edit the possible values list so that all possible values have valid widths, or alter the width.
REP-00785
A possible value is invalid against the input mask.
Category:
Other
Cause:
A value specified for the LOV parameter's list of possible values is not formatted in accordance with the specified input mask.
Action:
Edit the possible values list to ensure that all possible values are valid against the input mask.
REP-00786
The initial value is not among the possible values.
Category:
Other
Cause:
The initial value specified for the LOV parameter does not appear on the defined list of possible values.
Action:
Add the initial value specified to the possible values list.
REP-00787
The name of the first column of LOV parameter {0}'s select statement is not the same at runtime as design time.
Category:
Other
Cause:
There is a discrepancy between the columns specified in the original SELECT statement and what the tables in question now contains.
Action:
Check the database to determine if the tables in question have been updated since the parameter list was created, or reapply the LOV parameter's SELECT statement.
REP-00788
The value of restricted LOV parameter {0} is not among the selectable values.
Category:
Other
Cause:
The value specified for a LOV parameter is not on the parameter's select list.
Action:
Select a value from the parameter's select list.
REP-00790
Page Width and Page Height must either both be specified or both be blank.
Category:
Other
Cause:
A blank value was specified for either Page Width or Page Height in the Runtime Settings tab of the Tools Options dialog box.
Action:
Specify a valid value for the blank setting, or make both settings blank.
REP-00800
Select All is valid only in a text entry field.
Category:
Other
Cause:
Select All was selected from the Edit menu with the cursor positioned on an element in the Property Inspector other than a text field.
Action:
While in the Property Inspector, select Edit then Select All only in a text field.
REP-00801
The layout canvas must remain large enough to fit all layout objects.
Category:
Other
Cause:
The painting region of the Paper Layout editor was reduced by changing one or more settings in the Report Properties dialog box, or by resizing the margin, but the resized painting region is not large enough to fit all of the layout objects.
Action:
Verify that all layout objects in the body, margin, header, and trailer sections of the report fit in the resized painting region.
REP-00802
The Parameter Form canvas must remain large enough to fit all Parameter Form objects.
Category:
Other
Cause:
The painting region of the Parameter Form editor was reduced by changing one or more settings in the Report Properties dialog box, but the resized painting region is not large enough to fit all of the Parameter Form objects.
Action:
Verify that all Parameter Form objects fit in the resized painting region.
REP-00803
The canvas size specified is too large.
Category:
Other
Cause:
The 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 Builder (a dpi value greater than 2 gigabytes).
Action:
Make the page/form size smaller, or decrease the value for logical page size, maximum body pages, maximum header pages, maximum footer pages, or number of Parameter Form pages.
REP-00804
The report definition was modified during the current run. Oracle Reports Builder cannot continue running the Parameter Form or report.
Category:
Other
Cause:
While in the Runtime Parameter Form, the report was modified through an editor or Property Inspector.
Action:
Cancel the Runtime Parameter Form and rerun the report.
REP-00805
Menus cannot be initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00806
An error occurred reading window resources.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-00807
The array size is missing.
Category:
Other
Cause:
In the Runtime Settings dialog box, the Array Size field was left blank.
Action:
Enter an Array Size value between 1 and 9999.
REP-00808
The buffer size is missing.
Category:
Other
Cause:
In the Runtime Settings tab of the Tools Options dialog box, the Buffer Size field was left blank.
Action:
Enter a Buffer Size value between 1 and 9999.
REP-00809
The long chunk size is missing.
Category:
Other
Cause:
In the Runtime Settings tab of the Tools Options dialog box, the Long Chunk Size field was left blank.
Action:
Enter a Long Chunk Size value between 1 and 9999.
REP-00810
The Success/On Failure value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Settings dialog box, On Success/On Failure specified an invalid value.
Action:
Select a valid value for On Success/On Failure: Noaction, Rollback, or Commit.
REP-00811
The Destination Type value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Settings dialog, Destination Type specified an invalid value.
Action:
Select a valid value for Destination Type: <In Report Definition>, Screen, File, Printer, or Mail.
REP-00812
The Orientation value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Settings dialog, Orientation specified an invalid value.
Action:
Select a valid value for Orientation: <In Report Definition>, Landscape, or Portrait.
REP-00813
The Mode value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Settings dialog, Mode specified an invalid value.
Action:
Select a valid value for Mode: <In Report Definition>, Default, Bitmap, or Character.
REP-00814
The Background value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Settings dialog box, Background specified an invalid value.
Action:
Select a valid value for Background: <In Report Definition>, Yes, or No.
REP-00815
The Orientation value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Parameter Form, Orientation specified an invalid value.
Action:
Select a valid value for Orientation: Landscape or Portrait.
REP-00816
The Mode value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Parameter Form, Mode specified an invalid value.
Action:
Select a valid value for Mode: Bitmap or Character.
REP-00817
The Background value is invalid.
Category:
Other
Cause:
In the character-mode Runtime Parameter Form, Background specified an invalid value.
Action:
Select a valid value for Background: Yes or No.
REP-00818
The page height has changed for the Parameter Form. Parameters might be crossed by page boundaries.
Category:
Other
Cause:
The height of the Runtime Parameter Form was changed in the Report Property Inspector. This might cause the page boundary to move such that it appears in the middle of an object in the Parameter Form.
Action:
Examine the layout of the 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, default (or redefault) the Parameter Form.
REP-00819
AUTOCOMMIT ON for SQL Server connection cannot be set.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services. Another option is to remove all instances of SRW.DO_SQL. If this can be done while retaining all necessary functionality in the report, it will run.
REP-00820
cannot import specified image
Category:
Other
Cause:
The specified image cannot be imported.
Action:
Check the image file to ensure it is a valid image and has not been corrupted.
REP-00821
cannot export specified image
Category:
Other
Cause:
The specified object cannot be exported as an image.
Action:
Create or select an image to export.
REP-00822
no drawing imported
Category:
Other
Cause:
The specified drawing cannot be imported.
Action:
Check the file to ensure it is a valid drawing and has not been corrupted.
REP-00823
no drawing exported
Category:
Other
Cause:
The specified object cannot be exported as a drawing.
Action:
Create or select a drawing to export.
REP-00824
The data dictionary is not available on the connected database.
Category:
Data
Cause:
An attempt was made to access the Table and Column Names dialog box but the Data Dictionary is not available on the connected database.
Action:
Connect to another database.
REP-00825
The connected database is not Oracle or DB2. It cannot be used to store report documents.
Category:
Other
Cause:
An attempt was made to store a document to a database that is neither Oracle nor DB2, which is not allowed.
Action:
Either connect to an Oracle or DB2 database or store the document as a file.
REP-00828
Oracle Reports Builder tables are not installed in the database: cancelling report.
Category:
Other
Cause:
The report cannot be run because there are no Oracle Reports Builder tables in the database.
Action:
Inform the database administrator that the Oracle Reports Builder tables were not successfully installed in the database.
REP-00829
Oracle Reports Builder database tables are from an older version of Oracle Reports Builder ({0}): cancelling report.
Category:
Other
Cause:
Oracle Reports Builder tables in the database appear to have been installed from a previous version of the product. The report cannot run against an older version of the database tables.
Action:
Inform the database administrator that the Oracle Reports Builder tables for this version were not successfully installed in the database.
REP-00830
Oracle Reports Builder database tables appear to be corrupted or incorrectly installed: cancelling report.
Category:
Other
Cause:
The report cannot be run because the Oracle Reports Builder tables are in an unstable state.
Action:
Inform the database administrator that the Oracle Reports Builder tables are either corrupted or incorrectly installed in the database.
REP-00831
The query could not be built.
Category:
Other
Cause:
Oracle Reports Builder attempted to build a query at startup but it failed. One cause is that the database account against which the query was being built was not correct. Otherwise it is an abnormal condition.
Action:
If Oracle Reports Builder was launched from another product, check that the database connection string in the other product is correct.
REP-00900
The report cannot close while PL/SQL is still executing.
Category:
Other
Cause:
An attempt was made to close a report while associated PL/SQL was still executing.
Action:
Finish executing the PL/SQL or abort it, then close the report.
REP-00901
Tables and Columns function is not supported for this database server.
Category:
Other
Cause:
The connected database server does not have an accessible Data Dictionary to list tables and columns.
Action:
No action is needed. Tables and Columns functionality is not available for these databases.
REP-00910
The Cue Cards cannot be found. Reinstall the Cue Cards and try again.
Category:
Other
Cause:
An attempt was made to run the Cue Cards, where have not been properly installed.
Action:
Reinstall the Cue Cards.
REP-00911
The Oracle Reports page on OTN cannot be displayed. Reset the browser settings correctly.
Category:
Browser
Cause:
In the Welcome to Oracle Reports Builder dialog box, Getting Started was selected, which displays the Oracle Reports page on the Oracle Technology Network (OTN), but the browser settings are not set correctly.
Action:
1. Edit the Windows registry using a registry editor (for example, open a command prompt window and type regedit.exe). 2. Select File, then Export to back up the current registry settings. 3. Navigate to the following key: HKEY_CURRENT_USER\Software\Oracle\Toolkit\Tkbrowser. 4. Set the BrowserName and the BrowserPath values to the browser name and location. For example: BrowserName: Internet Explorer BrowserPath: C:\Program Files\Internet Explorer\iexplore.exe 5. Close the registry editor. 6. Shut down and restart Oracle Reports Builder. 7. In the Welcome to Oracle Reports Builder dialog box, select Getting Started and click OK. 8. In the Information Navigator Preferences dialog box that displays, specify the following values: - From the Browser list, select the desired browser (for example, Microsoft Internet Explorer). - In the Command to launch browser field, specify the correct path to the browser; click Browse to navigate to the correct path location. For example: C:\Program Files\Internet Explorer\iexplore.exe 9. Click OK to save the settings and display the Oracle Reports page on the Oracle Technology Network (OTN) using the specified browser.
REP-00999
Unimplemented Error:
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01010
This name does not conform to SQL naming standards.
Category:
Other
Cause:
The name entered violates one or more SQL naming conventions.
Action:
Name the object according to the appropriate naming conventions.
REP-01011
Object {0} must be named.
Category:
Other
Cause:
The Name field was left blank for the object and a name is required.
Action:
Name the object according to the appropriate naming conventions.
REP-01012
There is another {0} object with this name.
Category:
Other
Cause:
The name entered duplicates the name of another object of the same type.
Action:
Change the name of at least one of the objects.
REP-01013
This name may not be the same as a reserved word.
Category:
Other
Cause:
The name entered duplicates a reserved word.
Action:
Change the name of the parameter such that it conforms to parameter naming conventions.
REP-01014
The name length cannot exceed 30 bytes.
Category:
Other
Cause:
The name entered was greater than 30 bytes, which is the limit for SQL names.
Action:
Reduce the size of the name to 30 bytes or less.
REP-01048
Owner and Access list are not overwritten.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01049
A report saved with a newer version of Oracle Reports Builder cannot be opened.
Category:
Other
Cause:
An attempt was made to open a report with an older version of Oracle Reports Builder than the one with which the report was saved.
Action:
Use the same or a more recent version of Oracle Reports Builder to open the report.
REP-01050
Document names in the database cannot be accessed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01051
The document cannot be saved to file {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01052
The document cannot be saved to the database.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01053
A new document ID cannot be obtained from the database.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01054
Table {0} cannot be deleted from.
Category:
Other
Cause:
An attempt was made to delete from a table and the operation failed, possibly due to lack of necessary privileges.
Action:
Contact the system administrator to assign the necessary privileges to delete from the table.
REP-01055
Table {0} cannot be locked.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01056
Object stored in the database cannot be renamed.
Category:
Other
Cause:
An attempt was made to rename a database object and the operation failed, possibly due to lack of necessary privileges.
Action:
Make a copy of the object, or contact the system administrator to assign the necessary privileges to change the name.
REP-01057
File {0} is not a valid Oracle Reports Builder file.
Category:
Other
Cause:
An attempt was made to access a file that is not in the proper format for Oracle Reports Builder.
Action:
Verify that the correct file is being accessed.
REP-01058
The document cannot be read from the database.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01059
unable to read document from file {0}
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01060
Oracle Reports Builder database tables have not been installed.
Category:
Other
Cause:
Oracle Reports Builder failed to access the SRW2_MODULE view in the current database.
Action:
Verify Oracle Reports Builder was properly installed on the database. For help, contact the system administrator.
REP-01061
External file {0} cannot be read.
Category:
Other
Cause:
Read From File was activated and a file name specified as the value of a column, but Oracle Reports Builder could not successfully open or read the specified file.
Action:
Check the spelling of the specified file in the Column Property Inspector, and verif that the specified file exists. If the file does exist, check the permissions on the file for read access.
REP-01062
External query {0} cannot be found.
Category:
Other
Cause:
The possible causes of this error include the following: Case 1: REPORTS_PATH is not set. Case 2: There is no database connection. Case 3: The specified external query does not exist.
Action:
Take the following actions to correct this error: If Case 1: Set REPORTS_PATH to a valid value. If Case 2: Connect to a database. If Case 3: Specify the correct name of the external query.
REP-01063
The PL/SQL {0} has exceeded the platform specific size limit.
Category:
Other
Cause:
The PL/SQL could not be loaded because it is too large for the operating system. It may have been created on a different platform with a higher limit.
Action:
Reduce the size of the PL/SQL so it can be loaded on the platform.
REP-01064
Document {0} cannot be read.
Category:
Other
Cause:
An attempt was made to open a document whose definition, stored in either the database or the filesystem, has been lost or corrupted.
Action:
This document cannot be used.
REP-01065
External query {0} cannot be read.
Category:
Other
Cause:
An attempt was made to read an external query whose definition, stored in either the database or the filesystem, has been lost or corrupted.
Action:
This external query cannot be used.
REP-01066
Comment is corrupted and will be lost.
Category:
Other
Cause:
A storage error caused a comment to be corrupted. It will be discarded.
Action:
No action is necessary. If desired, re-create the comment in the designer.
REP-01067
Some information is missing in the report.
Category:
Other
Cause:
The report cannot be opened because the report definition is incomplete. It may have been corrupted.
Action:
If the report is stored in the database, use SQL*Plus to determine whether the Oracle Reports Builder tables have been corrupted. If the report is an .rdf file, use a file system utility to check if the file is corrupted. Take appropriate actions to recover the data.
REP-01070
An error occurred while opening or saving a document.
Category:
Other
Cause:
An error occurred while opening or saving a document.
Action:
Verify the access privileges for the document.
REP-01071
The end of an object or record scan was reached.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01072
The object cannot be found in the object store.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01073
The object was found in the object store when not expected.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01074
The object is too big.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01075
The object is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01076
The specified object store is invalid.
Category:
Other
Cause:
An attempt was made to use an invalid file or database object.
Action:
Verify that the object specified is a valid Oracle document, stored in a file or in the database.
REP-01077
The type specified for the object is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01078
A non-specific file error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01079
The function is unsupported.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01080
A unique key violation occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01081
A page split occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01082
A close error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01083
A file version error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01084
A file header is bad or missing.
Category:
Other
Cause:
An operation required Oracle Reports Builder to open a file. The file either did not have a header or it did not 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 Builder.
Action:
Attempt to fix the header in an editor, although it is not recommended that Oracle Reports Builder files be edited in this way. For assistance, contact Oracle Support Services.
REP-01085
A file create error occurred.
Category:
Other
Cause:
An operation that required Oracle Reports Builder to create a file failed, most likely due to insufficient privileges to create the file.
Action:
Obtain the necessary privileges for the file.
REP-01086
A file open read-only error occurred.
Category:
Other
Cause:
An operation that required Oracle Reports Builder to open a file failed, most likely due to insufficient privileges to open the file.
Action:
Obtain the necessary privileges for the file.
REP-01087
A file open read-write error occurred.
Category:
Other
Cause:
An operation that required Oracle Reports Builder to open a file failed, most likely due to insufficient privileges to open the file.
Action:
Obtain the necessary privileges for the file.
REP-01088
A file write error occurred.
Category:
Other
Cause:
An operation that required Oracle Reports Builder to write to a file failed, most likely due to insufficient file privileges to write to the file.
Action:
Obtain the necessary privileges for the file.
REP-01089
A file read error occurred.
Category:
Other
Cause:
An operation that required Oracle Reports Builder to read a file failed, most likely due to insufficient file privileges to read the file.
Action:
Obtain the necessary privileges for the file.
REP-01090
A file close error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01091
The disk or file system is full.
Category:
Other
Cause:
An attempt was made to save an object, but there was not enough space in which to save it.
Action:
Either delete some unnecessary files or expand the storage space.
REP-01092
A file unique key violation occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01093
Allocate failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01094
Reallocate failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01095
Free failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01096
The document {0} is currently locked.
Category:
Other
Cause:
An attempt was made to open a document that is already opened (locked) by another user.
Action:
Wait until the other user closes the document before accessing it.
REP-01097
PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE does not exist.
Category:
Other
Cause:
The possible causes of this error include the following: Case 1: The table does not exist. Case 2: The necessary privileges to access the table are not granted.
Action:
Take the following actions to correct this error: If Case 1: If the table is not already created, create it. If Case 2: Get access to the table by creating a public synonym for the table in the PRODUCT_USER_PROFILE table, or by making the table public via the PRODUCT_USER_PROFILE table.
REP-01098
An error occurred reading PRODUCT_USER_PROFILE or SYSTEM.PRODUCT_PROFILE data.
Category:
Other
Cause:
The table is not created correctly.
Action:
Ensure that the table was created with the appropriate columns. If it was not, then modify it as necessary.
REP-01099
Files not created with Oracle Reports Builder cannot be opened.
Category:
Other
Cause:
An attempt was made to open a file that is not an Oracle Reports Builder report.
Action:
Verify that the file is an Oracle Reports Builder report.
REP-01100
The data model is invalid for this type of report.
Category:
Data
Cause:
An attempt was made to create a default layout with a layout style that does not match the data model.
Action:
Either change the data model to match the selected layout style or select a different layout style to match the data model. For more information, see the Oracle Reports online help.
REP-01101
Group {0} has an invalid repeat direction.
Category:
Other
Cause:
An attempt was made to create a default layout, but the selected layout style requires a different repeat direction for one of the groups. Some layout styles place restrictions on the repeat directions that can be selected for groups.
Action:
Either change the repeat direction to meet the layout style requirements or select a different layout style.
REP-01102
The default layout cannot fit onto page of size {0}.
Category:
Other
Cause:
Oracle Reports Builder tried to create the default layout selected but could not fit the entire layout on the page because the page is not wide enough.
Action:
If possible, increase the Page Width on the Report Property Inspector or rearrange objects such that the layout will fit on the page. Otherwise, make the report multiple pages wide.
REP-01103
No column is selected in group {0}.
Category:
Other
Cause:
While trying to create a default layout, a column was not selected for a selected group. Consequently, Oracle Reports Builder cannot build a default layout because one or more of the dimensions of the layout have no value.
Action:
In the Report Wizard, select at least one column from each selected group.
REP-01104
Page level summaries are not supported in the default layout.
Category:
Other
Cause:
A default layout was generated that does not fit within the given amount of space. The possible causes of this error include the following: Case 1: The layout generated is too large given the dimensions specified in the Report Properties dialog box. Case 2: The layout is too big given the size of the marked area in the Paper Layout editor.
Action:
Take the following actions to correct this error: If Case 1: Increase the report dimensions such that the layout can fit, or alter the layout so that it will fit within the current dimensions. If Case 2: Increase the size of the marked area.
REP-01106
no field is generated for column {0}.
Category:
Other
Cause:
When the default layout was created, 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, the source of a summary column may have been specified to be a column in a group above the summary's group, which is not allowed.
Action:
Debug the data model and redefault the layout.
REP-01107
The across or down group in cross product group {0} is missing.
Category:
Other
Cause:
An attempt was made to create a default layout by selecting a Style of Matrix in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Down or Across. Each repeat direction should be assigned to the dimension groups in the cross product.
Action:
Redisplay the Report Wizard and reassign the repeat directions of the dimension groups, making sure that each direction is assigned among the groups.
REP-01108
The default layout cannot fit even in region extending to page boundaries.
Category:
Other
Cause:
An attempt was made to create a default layout that would be too large to fit within the defined height and width of a report page.
Action:
Go back to the Report Wizard and reduce the values of default settings (for example, shorten some field widths). Alternatively, increase the size of a report page using the Report Property Inspector. Then re-create the default layout.
REP-01109
Multiple group selection is incompatible with single group layout style.
Category:
Other
Cause:
More than one group was selected to add to the layout but the style selected only supports one group.
Action:
Change the group selection so that only a single group is selected. Alternatively change the layout style to one that supports multiple groups.
REP-01110
The matrix across group in cross product group {0} is missing.
Category:
Other
Cause:
An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Down.
Action:
Change the repeat direction of one of the cross product dimension groups so that there is at least one Across group and one Down group.
REP-01111
The matrix down group in cross product group {0} is missing.
Category:
Other
Cause:
An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but all of the dimension groups of the cross product group were assigned repeat directions of Across.
Action:
Change the repeat direction of one of the cross product dimension groups so that there is at least one Down group and one Across group.
REP-01112
The matrix cross product group in the matrix report is missing.
Category:
Other
Cause:
An attempt was made to create a default layout by selecting a Style of Matrix or Matrix with Group in the Report Wizard, but a cross product group was not selected to be used as the matrix group.
Action:
Change the repeat direction of one of the cross product group to Matrix.
REP-01113
No groups or reports level columns have been selected.
Category:
Other
Cause:
While trying to create a default layout, no groups or report level columns were selected. Consequently, Oracle Reports Builder cannot build a default layout because one or more of the dimensions of the layout have no value.
Action:
In the Report Wizard, select at least one report level column or a group to be defaulted.
REP-01114
A single group selection is incompatible with a multiple group layout style.
Category:
Other
Cause:
A single group was selected to be defaulted but a defaulting style designed for a multiple groups was also selected.
Action:
Change the group selection so that more than one group is selected. Alternatively, change the layout style to one that supports single groups.
REP-01115
The full template layout cannot be shown because it does not fit onto the page.
Category:
Other
Cause:
The template layout could not be shown properly because it is too large to fit within the defined height and width of the report page. This does not mean that the template is invalid in any way.
Action:
To show the template layout, temporarily enlarge the width and height of the report page. To do this, select the template in the Navigator and open the Property Inspector. Increase the Width and Height properties under the Report heading. Do not forget to reset the Width and Height properties before saving the template.
REP-01118
A cross product group in the Matrix query is missing.
Category:
Other
Cause:
An attempt was made to create a query by selecting the Matrix query option in the Data Wizard, However, the cross product group does not exist in the query to be used as the matrix group.
Action:
Restart the Data Wizard.
REP-01200
The flow compilation failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01201
Query text is missing from query {0}.
Category:
Other
Cause:
A query was named, but either no SELECT statement was entered for it or something that did not begin with the keyword SELECT was entered. The SQL Query Statement dialog box only accepts SQL SELECT statements.
Action:
Enter a SQL SELECT statement that begins with the word SELECT (upper or lower case may be used).
REP-01202
An Oracle logon was not specified.
Category:
Other
Cause:
An attempt was made to run a report without an Oracle logon specified.
Action:
Enter a logon string in the Connect dialog box and accept the dialog box before rerunning the report.
REP-01203
Field {0} references an invalid column.
Category:
Other
Cause:
The column specified as the field's Source either is invalid or does not exist.
Action:
Select a column from the list of values.
REP-01204
Repeating frame {0} references an invalid group.
Category:
Other
Cause:
The group name specified in the Group field of the Repeating Frame Property Inspector either is invalid or does not exist.
Action:
Select a group from the list of values.
REP-01205
There is a loop in the positional dependency tree.
Category:
Other
Cause:
Explicit anchors were created such that an object is indirectly anchored to itself. For example, if object A was anchored to object B, object B to object C, and object C to object A, this error displays.
Action:
Remove at least one of the anchors that caused the loop.
REP-01206
An object is anchored to more than one other object.
Category:
Other
Cause:
In the layout, an object was anchored to more than one other object.
Action:
Eliminate the anchors to other objects such that the object is anchored to only one other object.
REP-01207
The PL/SQL procedure for group filter {0} is missing.
Category:
Other
Cause:
The Filter Type on the Group Property Inspector specified a vlue of PL/SQL, but a valid filter was not specified.
Action:
Enter a valid PL/SQL function or change the filter type.
REP-01208
A repeating frame of matrix {0} cannot be anchored.
Category:
Other
Cause:
An attempt was made to run a report with an anchor from an intersecting repeating frame of a matrix object to another object.
Action:
Delete the anchor.
REP-01209
Matrix {0} cannot be anchored.
Category:
Other
Cause:
An attempt was made to run a report with an anchor from a matrix object to another object, which is not allowed.
Action:
Delete the anchor.
REP-01211
Object {0} is larger than its enclosing object {1}.
Category:
Other
Cause:
An object is larger than its enclosing object. The most likely cause is that an attempt was made to enclose a large object within a small, fixed frame.
Action:
Identify the object and the enclosing object and adjust their relative sizes and positions until the proper enclosure is achieved.
REP-01212
Object {0} is not fully enclosed by its enclosing object {1}.
Category:
Other
Cause:
The possible causes of this error include the following: Case 1: An object is not fully enclosed by the page. That is, the object extends beyond the page boundary. Case 2: A repeating frame that forms a matrix is one or more layers above a repeating frame that it contains. In a matrix layout, repeating frames must be below repeating frames that they contain.
Action:
Take the following actions to correct this error: If Case 1: Move or resize the object so that it does not extend outside the page boundary. Alternatively, increase the page size in the Report Property Inspector. If Case 2: Use Arrange>Send to Back, Arrange>Bring to Front, Arrange>Move Backward, and Arrange>Move Forward to arrange repeating frames such that, in terms of layers, the following is true: repeating frames are below repeating frames that they contain and down repeating frames are below across repeating frames.
REP-01213
Field {0} references column {1} at a frequency below its group.
Category:
Other
Cause:
The source column for the field is in a group below that of the repeating frame that encloses it.
Action:
Move the field into a repeating frame whose source group is at or above the group that contains the field's source column. Otherwise, move the field's source column into the enclosing repeating frame's group, if possible.
REP-01214
Repeating frame {0} is enclosed by a child repeating frame.
Category:
Other
Cause:
The enclosed repeating frame's source group is above the enclosing repeating frame's source group.
Action:
In the editor, make the enclosed repeating frame the enclosing repeating frame. Alternatively, if possible, change the group hierarchy such that the enclosed object's group is below the enclosing object's group.
REP-01216
Object {0} has an illegal print condition.
Category:
Other
Cause:
The Print Condition for the specified object was invalid. For example, an attempt may have been made to set the Print Condition of a margin object.
Action:
Change the Print Condition of the object to another, valid setting.
REP-01218
Object {0} cannot page break before AND keep with parent.
Category:
Other
Cause:
Page Break Before was set for an object as well as Keep with Anchoring Object. The anchoring object, however, precedes the object and therefore the two settings are in conflict.
Action:
Uncheck Page Break Before or Keep with Anchoring Object.
REP-01219
Object {0} has no size; length or width is zero.
Category:
Other
Cause:
A layout object was created of zero width or height.
Action:
Enlarge the opject so that it has a non-zero height and width.
REP-01220
Object {0} has Minimum Widow Records greater than Maximum Records per Page.
Category:
Other
Cause:
Maximum Records per Page was set to a smaller value than Minimum Widow Records. This causes a conflict between the two settings and, in effect, indicates that no instances should be printed.
Action:
Decrease Minimum Widow Records or increase Maximum Records per Page.
REP-01222
The body size is invalid.
Category:
Other
Cause:
A body page width or height was specified that is negative or out of range. This is most likely due to setting the page size to an invalid value using the PAGESIZE executable argument.
Action:
Enter a valid value using the PAGESIZE executable argument, or adjust the body panel size by resizing the margins in the Paper Layout editor.
REP-01223
The page size is invalid.
Category:
Other
Cause:
A physical page width or height was specified that is negative or out of range. This is most likely due to setting the page size to an invalid value using the PAGESIZE executable argument.
Action:
Enter a valid value using the PAGESIZE executable argument, or change the physical page size setting in the Report Property Inspector.
REP-01225
The logical page size is invalid.
Category:
Other
Cause:
A logical page height was specified that is negative.
Action:
Redefine the logical panel height to ensure that it is not defined using a negative number.
REP-01226
The body location is beyond the print area.
Category:
Other
Cause:
The body panel is not enclosed within the physical page.
Action:
Adjust the body panel size by resizing the margins in the Paper Layout editor.
REP-01229
The spacing between records for repeating frame {0} is negative.
Category:
Other
Cause:
The value for Vertical Spacing and/or Horizontal Spacing specified for a repeating frame is negative.
Action:
Respecify the appropriate Spacing setting for the repeating frame.
REP-01230
Field {0} has an invalid page reset group.
Category:
Other
Cause:
In the Reset At field of the Page Numbering dialog box, a repeating frame was specified that does not enclose the layout field that should display the page number. An invalid repeating frame may have been specified, or the repeating frame was deleted after specifying it.
Action:
Specify &Report or the name of a valid repeating frame as the Reset At value for the page number field.
REP-01231
Object {0} has an invalid text wrap style.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01232
Matrix {0} has an invalid source frame.
Category:
Other
Cause:
An invalid object was specified as the source frame of the matrix object, or the repeating frames specified have invalid Print Directions.
Action:
Change the Print Direction of horizontal source repeating frame to Down, and the Print Direction of the vertical source repeating frame to Across.
REP-01233
The frames of matrix {0} do not fully intersect.
Category:
Other
Cause:
The repeating frames that form the matrix do not completely intersect. For example, if there are 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, this error displays.
Action:
Redefault the matrix layout, if possible, or move the repeating frames that make up the matrix such that they fully intersect one another.
REP-01234
The position of matrix {0} is not at the intersection of its frames.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01235
An error occurred generating index for Cross Product.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01236
Query {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01237
The data link is invalid.
Category:
Data
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01238
Group {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01239
Column {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01240
The anchor is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01241
A circular column dependency originating with column {0} exists.
Category:
Other
Cause:
A column was created that directly or indirectly references itself. For example, Column A might reference Column B which in turn references Column A.
Action:
Update or delete columns to eliminate the circular dependency.
REP-01242
Matrices must have all down frames below all across frames.
Category:
Other
Cause:
In a matrix layout, down repeating frames must be below across repeating frames.
Action:
Using Arrange>Send to Back, Arrange>Bring to Front, Arrange>Move Backward, and Arrange>Move Forward, arrange repeating frames such that, in terms of layers, the following is true: repeating frames are below repeating frames that they contain, and down repeating frames are below across repeating frames.
REP-01243
An unimplemented type of summary is specified in column {0}.
Category:
Other
Cause:
A summary function was specified that is not available.
Action:
Specify a valid summary function.
REP-01245
The wrong number of source columns are defined for summary function of column {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01246
The graph document is not found.
Category:
Other
Cause:
Oracle Reports Builder cannot find the associated graph document for the graph.
Action:
Correct the file name and path of the graph document.
REP-01247
The report contains uncompiled PL/SQL.
Category:
Other
Cause:
An attempt was made to run the report before all referenced PL/SQL constructs was compiled.
Action:
Compile the PL/SQL, then run the report.
REP-01248
All source columns of placeholder {0} must be in the same group.
Category:
Other
Cause:
An attempt was made to set the value of a placeholder column from columns belonging to different groups.
Action:
Change the placeholder column's group to match the group of the columns changing the placeholder column's value.
REP-01249
Column {0} has no PL/SQL formula.
Category:
Other
Cause:
A column of Type Formula was created with nothing in the Formula field.
Action:
Create a formula for the column or change the column's Type.
REP-01250
A circular query dependency exists.
Category:
Other
Cause:
The report contains at least two queries, with each requiring the other to be executed first.
Action:
Edit one or more of the queries to remove the circular dependency.
REP-01251
A circular query dependency originating with query {0} exists.
Category:
Other
Cause:
The report contains at least two queries, with each requiring the other to be executed first. The query listed in the message is one of the conflicting queries.
Action:
Edit the query listed or another conflicting query to remove the circular dependency.
REP-01252
The matrix should be surrounded by a repeating frame on group {0}.
Category:
Other
Cause:
The data model for the report contains a matrix with a parent group, but in the layout the repeating frame for the parent group either does not exist or does not surround the matrix.
Action:
Modify the layout of the report so that the parent group has a repeating frame that surrounds the matrix.
REP-01253
Matrix objects are on different regions of the layout.
Category:
Other
Cause:
The repeating frames of a matrix are on different regions of the layout (body, margin, header, or trailer).
Action:
Move all repeating frames of the matrix to the same report region.
REP-01254
Anchored objects are on different regions of the layout.
Category:
Other
Cause:
The anchoring and anchored objects of an anchor are on different regions of the layout (body, margin, header, or trailer).
Action:
Move the above-mentioned objects to the same report region.
REP-01255
An object cannot anchor to a hidden object.
Category:
Other
Cause:
The anchored object of an anchor is a hidden object.
Action:
Either make the anchored object not hidden, or delete the anchor.
REP-01256
File link boilerplate text is missing its source file.
Category:
Other
Cause:
A file name was not specified in the Source Filename property for the file link boilerplate object.
Action:
Specify a directory path and file name in the Source Filename property in the file link boilerplate object's Property Inspector.
REP-01257
Oracle Reports Builder cannot fetch data for child query from caller.
Category:
Data
Cause:
Oracle Reports Builder was invoked from another product, and Oracle Reports Builder has been instructed to fetch data for a child query from the caller. Data passed to Oracle Reports Builder can only be for a master query.
Action:
Modify the caller's instructions so that Oracle Reports Builder does not request data for a child query.
REP-01258
Group {0} has no columns.
Category:
Other
Cause:
A group was created that has no columns.
Action:
Delete the group or assign one or more columns to the group.
REP-01259
Group {0} has no break columns.
Category:
Other
Cause:
A parent group was created that has no break columns.
Action:
Mark the Break Order check boxex of the break columns of the group.
REP-01260
Groups {0} and {1} are from the same query and cannot be linked.
Category:
Other
Cause:
Two groups from the same query were linked with a data link, which is not allowed.
Action:
Remove the data link or relink to another group.
REP-01261
Group {0} can have only one parent.
Category:
Other
Cause:
One group has two queries as its parent (it can only have one).
Action:
Remove data links from the same group to different queries.
REP-01262
A circular data link dependency starting from group {0} exists.
Category:
Data
Cause:
A cycle with data links was created (that is, a parent was specified as the child of itself, either directly or indirectly).
Action:
Remove at least one of the links in the cycle.
REP-01263
Cross product group {0} has no or only one dimension group.
Category:
Other
Cause:
A cross product group was defined 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.
Action:
Remove the cross product group or add dimension groups, or dimension queries (if multiquery).
REP-01264
A data link of group {0} crosses cross a product boundary.
Category:
Data
Cause:
In the multiple-query matrix report, a query has some of its groups are inside the cross product and some outside.
Action:
Move all groups of the query to either outside or inside of the cross product group.
REP-01265
A cross product group {0} has no child groups.
Category:
Other
Cause:
A cross product group has no child group, which is required. The child group acts as the cell of the matrix.
Action:
Create a child group for the cross product group.
REP-01266
Page Level column {0} is not allowed in a cross product.
Category:
Other
Cause:
A column was creted in a cross product group that is or relies on a column that is a page-level summary (that is, a summary with Reset At of Page).
Action:
Remove the column from the cross product group, or change the Reset At value of the column or the page-level summary upon which it relies.
REP-01267
Graph {0} references an invalid column as a bind parameter.
Category:
Other
Cause:
The graph references a column that does not exist. An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01268
Graph {0} references a bind column {1} at the wrong frequency.
Category:
Other
Cause:
The column specified for the graph is in a group below that of the repeating frame that encloses the graph.
Action:
Move the graph into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frame's group, if possible.
REP-01269
Graph {0} references an invalid report group.
Category:
Other
Cause:
The report group specified for the graph does not exist. An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01270
Graph {0} references a report group at the wrong frequency.
Category:
Other
Cause:
The report group specified for the graph is above the source group of the enclosing repeating frame.
Action:
Move the graph into a repeating frame with a source group that is at or above its report group.
REP-01271
Graph column name {1} has been specified multiple times in the graph document {0}.
Category:
Other
Cause:
The specified graph column or parameter has been referenced more than once in the graph document.
Action:
Check the columns and parameters specified for the graph and delete any duplicates.
REP-01272
Column {0} may not be used as a break column.
Category:
Other
Cause:
A Break Order was specified on a summary, function, or placeholder. These types of columns cannot be used as break columns.
Action:
Review the rules for which columns can be break columns. For more information, see the online help topic 'Break Order property'.
REP-01273
Source groups of matrix {0} are not from the same cross product.
Category:
Other
Cause:
The source groups of the repeating frames that form the dimensions of the matrix are not contained by the same cross product group. The dimensions of a matrix must be contained within the same cross product group.
Action:
Change the source groups of the repeating frames or select different repeating frames to form the dimensions of the matrix.
REP-01274
Invalid repeat direction combination in matrix {0}.
Category:
Other
Cause:
Matrix dimension repeating frames whose source groups are in the same "family" hierarchy (that is, are descendants or ancestors of each other) within a cross product group must have the same Print Direction. Parent-child relationships within a cross product group are used to create nesting in the matrix. As a result, the repeating frames associated with such groups must print in the same direction on the page.
Action:
Change the Print Direction of the repeating frames as necessary, select different source groups for the repeating frames, or select different repeating frames to form the dimensions of the matrix.
REP-01275
Page level column {1} may not be referenced from format trigger {0}.
Category:
Other
Cause:
PL/SQL was entered in a Format Trigger that references columns with a Reset At or Compute At of Page.
Action:
Remove the reference to the page-level column or change the column's Reset At or Compute At to something other than Page.
REP-01276
Placeholder {0} references one or more non-formula columns.
Category:
Other
Cause:
A placeholder column contains SRW.REFERENCE, but the column referenced is not a formula column. For placeholder columns, SRW.REFERENCE must refer to a formula column.
Action:
Change the column referenced via SRW.REFERENCE.
REP-01277
The SELECT element is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01278
The PL/SQL procedure in {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01279
Frame or repeating frame {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01280
Field {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01281
Boilerplate {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01282
Matrix {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01283
Graph document {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01284
Query {0} has no groups.
Category:
Other
Cause:
The data model contains a query that has no groups. Each query in the data model needs at least one group associated with it.
Action:
Create a new group for the query.
REP-01285
Query {0} has no SELECT elements.
Category:
Other
Cause:
The data model contains a query that does not select anything. Each query in the data model must select at least one element.
Action:
Enter a SELECT statement in the query, selecting at least one element.
REP-01286
Group {0} is a cross product as well as a dimension.
Category:
Other
Cause:
A group was specified to act as both a cross product group and as a dimension group for another cross product group, which is not allowed.
Action:
Make the group either a cross product group or a dimension group, but not both.
REP-01287
Cross product group {0} may not have a group filter.
Category:
Other
Cause:
A group filter was specified on a cross product group, which is not allowed.
Action:
Remove the group filter from the cross product group. Create the group filter for another group, if necessary.
REP-01288
The numeric argument for group filter of group {0} is missing.
Category:
Other
Cause:
First or Last was specified for a group's filter, but a number dictating how many records the group should filter was not specified.
Action:
Specify a number for the group filter.
REP-01289
An unimplemented type of group filter is specified in group {0}.
Category:
Other
Cause:
A group filter was specified that is not available or is invalid.
Action:
Specify a valid group filter for the group.
REP-01290
The Source data type is incompatible with the summary function in column {0}.
Category:
Data
Cause:
The summary column was assigned a Source whose data type is incompatible with the specified Function. For example, a temp may have been made to sum a character column.
Action:
Verify that the data type of the source column is compatible with the Function specified in the Summary Column Property Inspector.
REP-01291
Column {0} has an invalid reset group.
Category:
Other
Cause:
An invalid Reset At value was specified for a summary column. Reset At can be set to the same group as the summary column, any group above the summary column's, Page, or Report.
Action:
Specify a valid Reset At value for the summary column in its Property Inspector.
REP-01292
Column {0} has an invalid compute group.
Category:
Other
Cause:
An invalid Compute At value was specified for a summary column. Compute At can be set to the same group as the summary column, any group above the summary column's, Page, or Report.
Action:
Specify a valid Compute At value for the summary column in its Property Inspector.
REP-01293
Column {0} has an invalid product order.
Category:
Other
Cause:
A column in a cross product group was assigned an invalid value for Product Order, or no value at all.
Action:
Specify a valid value for Product Order (consisting of only dimension groups within the cross product) in the column's Property Inspector.
REP-01294
The width of column {0} is too large.
Category:
Other
Cause:
The column's width exceeds the maximum allowed for the operating system.
Action:
Reduce the width of the column in the Column Property Inspector.
REP-01295
The data format of column {0} is unsupported.
Category:
Data
Cause:
Read from File was selected for a column, but an invalid or unavailable data format was specified in the Format field in the Column Property Inspector.
Action:
Specify a valid data format in the Format field. The list of values displays all valid data formats. Note that for LONG, RAW, and LONG RAW database columns, only Text and Oracle Format (Image) are valid values for Format.
REP-01296
The data link child cannot be in the cross product group {0}.
Category:
Data
Cause:
An attempt was made to link a column to a column in a cross product group, or to the cross product group itself.
Action:
Create data links between columns and groups other than cross product groups and their associated columns.
REP-01297
The data link child column {0} must be a database column.
Category:
Data
Cause:
An attempt was made to link a column to another column that is not a database column (for example, a summary, formula, or placeholder column).
Action:
Create data links using only database columns and groups.
REP-01298
Columns {0} and {1} have incompatible types to be linked.
Category:
Other
Cause:
The parent and child columns in the data link have incompatible datatypes that cannot be linked. For example, an attempt was made to link a Number column to a Character column.
Action:
Verify that the parent and child columns specified in data links have compatible datatypes.
REP-01299
Groups {0} and {1} in different cross products cannot be linked.
Category:
Other
Cause:
An attempt was made to create a data link between dimension groups of two different cross product groups, or between columns of the dimension groups.
Action:
Delete data links between two different cross product groups or their columns.
REP-01300
Text boilerplate {0} has no contents.
Category:
Other
Cause:
A text boilerplate object was created that contains no text.
Action:
Enter some text in the boilerplate object, or delete it.
REP-01301
The data link creates a sibling of group {0} within a cross product.
Category:
Data
Cause:
A data link was defined that created a sibling of a dimension group within a cross product group. No siblings of dimension groups are allowed within the cross product.
Action:
Delete the sibling of the dimension group.
REP-01302
The cross product has two or more child groups.
Category:
Other
Cause:
A cross product group has more than one child group. Only one child is allowed per cross product group.
Action:
Remove all but one of the child groups to the cross product group.
REP-01303
The query must be completely in or out of cross product group {0}.
Category:
Other
Cause:
A query was created whose groups are not all inside the cross product, above the cross product, or below the cross product, respectively.
Action:
Verify that each query's groups are all inside of a cross product, above a cross product, or below a cross product.
REP-01304
Cross product group {0} contains another cross product as child.
Category:
Other
Cause:
A cross product group was created that is a child of another cross product group, which is not allowed.
Action:
Ensure that the child group of the cross product group is not a cross product group.
REP-01305
Frame {0} intersects but does not enclose object {1}.
Category:
Other
Cause:
The report layout contains a frame that does not completely enclose the named object. Thus, the object is not considered to be inside the frame.
Action:
To enclose the object with the frame, resize or move the frame.
REP-01306
Summary column {0} has an invalid source.
Category:
Other
Cause:
An invalid source was specified for the summary column. A summary column's source must be from the same group as the summary column, or from a group below the summary column.
Action:
Change the source of the summary column to be from the same group as the summary column or from a group below the summary column.
REP-01307
Summary column {0} has an invalid product order.
Category:
Other
Cause:
The possible causes of this error include: Case 1: A summary exists that is not a running summary (that is, its Reset At is not Report), but its Product Order is not a subset of the source column's product order. The source column of the summary must be at least as frequent as the summary, which means that the summary's Product Order should be some subset of the source column's Product Order. Case 2: A running summary (that is, its Reset At is Report) exists with a Product Order that is not a prefix of the source column's Product Order. For example, if the source column's Product Order were A,B,C, then the summary column's Product Order would have to be either A (by itself) or A,B. The summary's Product Order could not be B,A.
Action:
Take the following actions to correct this error: If Case 1: Change the Product Order of the summary such that it is a subset of its source column's Product Order. If Case 2: Change the Product Order of the summary such that it is a prefix of the Source column's Product Order.
REP-01308
Placeholder column {0} is not supported in a cross product.
Category:
Other
Cause:
An attempt was made to create a placeholder column inside of a cross product group. Cross product groups cannot contain placeholder columns.
Action:
Delete the placeholder or move it outside the cross product group.
REP-01309
Report level summary {0} cannot be a percent of total.
Category:
Other
Cause:
A summary was created at the report-level (that is, a summary outside of all the groups in the data model) with a Function of % of Total. This Function makes no sense for a report-level summary because it will always be 100%.
Action:
Delete the summary or move it into a group where it will make sense.
REP-01310
Boilerplate {0} references &{1} which is not a field.
Category:
Other
Cause:
A boilerplate object has a reference to a field that does not exist. It could be that the field being referenced was deleted or renamed and so this reference in the boilerplate object is now invalid.
Action:
Depending on circumstances, remove the reference, replace it with a reference to another field, or create the field that it references.
REP-01311
Object {0} with page-dependent references have been changed to fixed sizing.
Category:
Other
Cause:
A field or boilerplate object has a reference to a page calculation or a total number of pages variable. (This is known as a forward reference.) Such layout objects must be fixed in size both horizontally and vertically.
Action:
The layout object's Horizontal and Vertical Elasticity have been set to Fixed by Oracle Reports Builder. Check the output to ensure that the values are not being truncated. If they are, enlarge the layout object so that it is large enough to contain the values.
REP-01312
Page-level column {1} may not be referenced from graph {0}.
Category:
Other
Cause:
A column passed to a graph is or depends upon a page-level summary (that is, a summary with a Reset At or Compute At of Page). A column being passed to a graph cannot be or depend upon a page-level summary.
Action:
Do not pass the column to the graph.
REP-01313
Page-level column {1} may not be referenced from group filter {0}.
Category:
Other
Cause:
A column that was referenced in a group filter is or depends upon a page-level summary (that is, a summary with a Reset At or Compute At of Page). A column referenced by a group filter cannot be or depend upon a page-level summary.
Action:
Do not reference the column in the group filter.
REP-01314
Format trigger {0} references column {1} at the wrong frequency.
Category:
Other
Cause:
A format trigger references a column that is located at the wrong frequency.
Action:
Remove the reference to the column from the format trigger.
REP-01315
Group filter {0} references column {1} at the wrong frequency.
Category:
Other
Cause:
A group filter attempted to reference a column that is inaccessible.
Action:
Remove the reference to the column from the group filter.
REP-01316
Object {0} references column {1} at the wrong frequency.
Category:
Other
Cause:
A procedure or function attempted to reference a column that is inaccessible.
Action:
Remove the reference to the column from the PL/SQL subprogram.
REP-01317
Boilerplate {0} references field with source {1} at the wrong frequency.
Category:
Other
Cause:
A boilerplate object referenced a field using &fieldname, but the two objects are not located at the same frequency. For example, the boilerplate object and the field it references are located within different repeating frames.
Action:
Place the boilerplate object and field at the same frequency, or remove the reference.
REP-01318
An error occurred while setting transaction to read-only.
Category:
Transactioning
Cause:
Having specified READONLY=YES, this error occurred at the start of report execution, while ending the current transaction (with a COMMIT) and starting the read-only transaction, or at the end of report execution, while ending the read-only transaction (with a COMMIT).
Action:
Verify the database connection, and verify that that no cursors or locks were left pending by the previous transaction.
REP-01319
Implicit anchoring algorithm cannot uniquely identify the anchoring object {0}. Arbitrarily choosing {1}.
Category:
Other
Cause:
The specified object (object1) is in the "push path" of two objects and it is equidistant from both objects. As a result, Oracle Reports Builder cannot use its normal criteria (shortest distance) to determine the implicit anchor. In the absence of its normal criteria, Oracle Reports Builder randomly creates an implicit anchor to the specified object (object2). Note that the implicit anchor may vary between runs of the report.
Action:
To avoid the random creation of an implicit anchor, explicitly anchor the specified object (object1) to another object.
REP-01320
Program unit {0} references a column with invalid ID {1}.
Category:
Other
Cause:
A report was run containing invalid PL/SQL (for example, PL/SQL that did not compile). The PL/SQL source included a column reference that cannot be resolved.
Action:
Check the column references in the PL/SQL source, recompile all of the PL/SQL source in the report, and rerun the report.
REP-01322
Page break after on object {0} has no effect.
Category:
Other
Cause:
A Page Break After was activated on an object that has no other objects anchored to it (implicitly or explicitly). In this case, Page Break After has no effect and is invalid. Notice that this is a warning, not an error message.
Action:
Deactivate Page Break After for the object.
REP-01323
Output columns in format trigger {0} are not allowed.
Category:
Other
Cause:
In the format trigger for the specified object, an attempt was made to set the value of an Oracle Reports Builder column parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).
Action:
Remove the assignment statement from the format trigger.
REP-01324
Output columns in group filter {0} are not allowed.
Category:
Other
Cause:
In the filter for the specified group, an attempt was made to set the value of an Oracle Reports Builder column or parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).
Action:
Remove the assignment statement from the group filter.
REP-01325
Output columns in a Between Page Trigger are not allowed.
Category:
Other
Cause:
In the Between Page trigger, an attempt was made to set the value of an Oracle Reports Builder column or parameter. For example, the value of a column called COUNT1 can be used in a condition (for example, IF :COUNT1=10), but its value cannot be directly set in an assignment statement (for example, COUNT1=10).
Action:
Remove the assignment statement from the group filter.
REP-01326
Trigger {0} writes to column {1} at the wrong frequency.
Category:
Other
Cause:
In a report trigger, an attempt was made to set the value of an Oracle Reports Builder column at the wrong frequency in the report. Only report-level columns or parameters can be referenced and set, and any page-dependent columns (that is, Reset At of Page) or columns that rely on page-dependent columns cannot be referenced or set.
Action:
Verify that the columns and parameters whose values are referenced or set are report-level columns and parameters.
REP-01327
Column {0} writes to column {1} at the wrong frequency.
Category:
Other
Cause:
In a formula column, an attempt was made to set the value of an Oracle Reports Builder column at the wrong frequency in the report. Only columns that are in the same group or in a higher group in the group hierarchy can be referenced and set. For example, a formula for a report-level column can only reference other report-level columns.
Action:
Verify that the columns whose values are referenced or set are in the same group or in a higher group in the group hierarchy.
REP-01328
A report containing ROWLABEL column {0} cannot be run in a non-trusted OS.
Category:
Other
Cause:
An attempt was made to run a report that requires a secure database while connected to a non-secure database.
Action:
Run the report while connected to a secure database.
REP-01329
Column {0} cannot be linked to column {1} because the child column is not a database column.
Category:
Other
Cause:
A data link was created in which the child column is a summary, formula, or placeholder column. Only database columns can be linked.
Action:
Create a data link using database columns.
REP-01330
Lexical parameter {0} in query {1} must not change column dependencies.
Category:
Other
Cause:
A lexical parameter was created that changes the number, type, or names of columns, or introduces new dependencies on computed columns or new bind references, when the report is run.
Action:
Change the lexical parameter so that it does not change columns or introduce new dependencies or bind references.
REP-01331
Column {0} cannot be linked to column {1} because the child column is determined by a lexical parameter.
Category:
Other
Cause:
A data link was created in which child column's value is determined by a lexical parameter, which is not allowed.
Action:
Replace the child column of the data link with another column.
REP-01332
Group filter for {0} cannot reference column {1}. It is not a valid database column or it depends on a related query.
Category:
Other
Cause:
A group filter was created that references a database column not in the group's query or in a query above it, or references a computed column that depends on an unrelated column.
Action:
Remove the offending reference from the group filter.
REP-01333
Unsupported layout: a matrix may not be inside another matrix.
Category:
Other
Cause:
A matrix layout was created nested within another matrix layout, which is not allowed.
Action:
Redesign the layout to avoid the nesting.
REP-01335
Variable rotated text {0} is treated as fixed/contract width.
Category:
Other
Cause:
The report contains a boilerplate text object that was rotated to an angle that is not a multiple of 90 degrees, although both Horizontal and Vertical Elasticity values were set to Variable or Expand. In this case, the Horizontal Elasticity is treated as Fixed (if Expand was specified) or Contract (if Variable was specified), and this warning is displayed.
Action:
Consider changing the Horizontal and Vertical Elasticity values for this boilerplate object.
REP-01336
The source of field {0} is page-level calculation {1}. {2}.
Category:
Other
Cause:
The specified field references a page summary owned by the named group, but there is no repeating frame for that group that surrounds the field.
Action:
Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field.
REP-01337
Boilerplate {3} references field {0}, whose source is page-level calculation {1}. {2}.
Category:
Other
Cause:
The specified boilerplate object references the specified field, whose Source is a page-level computation. However, there is no repeating frame (whose Source is the named group) surrounding the field.
Action:
Create a repeating frame whose Source is the named group to surround the field. If such a repeating frame already exists, extend it to enclose the field.
REP-01338
Column mode is not allowed on repeating frame {0}.
Category:
Other
Cause:
The Column Mode setting for a repeating frame does not satisfy either of the following conditions: Print Direction of Down and a Vertical Elasticity of Fixed. Print Direction of Across and a Horizontal Elasticity of Fixed.
Action:
Change the Print Direction or Vertical/Horizontal Elasticity of the repeating frame, or deactivate Column Mode.
REP-01339
Graph {0} is missing a data column specification.
Category:
Data
Cause:
A value was specified for the graph Query, but no columns were specified to be passed from the report to the graph document.
Action:
To pass no data from the report to the graph document, specify nothing for the graph Query and Source. To pass data, specify the columns to be passed in addition to the graph Query and Source.
REP-01340
Passed-in columns do not match report definition {0}.
Category:
Other
Cause:
Another component (for example, Oracle Forms) passed a query to Oracle Reports Builder and there is a mismatch between the columns passed and the columns expected by Oracle Reports Builder. Possible causes of this error include: Case 1: Oracle Reports Builder was expecting more or fewer columns than the number that was actually passed by the calling application. Case 2: The parameter list of the calling application described a column differently than what Oracle Reports Builder expected. For example, if the report's query selects a character column and the calling application assigns that column a date data type, this error is raised.
Action:
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 Builder expects. If Case 2: Ensure that the datatypes and names of the columns being passed by the calling application match the dataypes and names in the report.
REP-01341
Data truncation is possible in column {0}.
Category:
Data
Cause:
The database column's width in the report is defined to be less than its width in the database. This can occur when the columns in the database are updated subsequent to the creation of the report definition.
Action:
Force the query to be reparsed. One method is to type a space at the end of a line in the SELECT Statement and then accept the SQL Query Statement dialog box.
REP-01342
The type of the data link to query {0} is illegal for a non-Oracle server.
Category:
Data
Cause:
A data link was created with the START WITH clause and run while connected to a non-Oracle database. START WITH is only supported by Oracle.
Action:
Remove the data link that uses START WITH or connect to Oracle.
REP-01343
Button {0} is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01344
Button {0} has no action source file.
Category:
Other
Cause:
An action of Multimedia File was specified for the named button, but either a source file was not specified, or a source file was specified that does not exist.
Action:
Open the Property Inspector for the specified button and verify that a valid file was selected as source for the button action.
REP-01345
Button {0} has an invalid source column.
Category:
Other
Cause:
An action of Multimedia Column was specified for the named button, but either a source column was not specified, or an invalid source column was specified.
Action:
Open the Property Inspector for the specified button and verify that a valid column was selected as source for the button action.
REP-01346
Button {0} references source column {1} at the wrong frequency.
Category:
Other
Cause:
The column specified in the Property Inspector for the named button is in a group below that of the repeating frame that encloses the button.
Action:
Move the button into a repeating frame whose source group is at or above the group that contains the specified column. Otherwise, move the specified column into the enclosing repeating frame's group, if possible.
REP-01347
Button {0} has an invalid icon file.
Category:
Other
Cause:
Either an invalid file or a nonexistent file was specified as the icon file for the button face.
Action:
Ensure that the specified icon file exists and is of the proper format and uncorrupted.
REP-01348
The source column of field {0} is in sound or video format.
Category:
Other
Cause:
A column was specified containing sound or video as the source for a field, but fields cannot display sound and video.
Action:
Specify another column (not sound or video) as source of the field.
REP-01349
The PL/SQL action is missing from button {0}.
Category:
Other
Cause:
The PL/SQL trigger that serves as the specified button's action references a piece of PL/SQL that does not exist.
Action:
Debug the trigger and ensure that it references a valid program unit.
REP-01350
Output columns in action trigger {0} are not allowed.
Category:
Other
Cause:
The PL/SQL trigger that serves as a button action contains a bind variable that returns a value. A PL/SQL action trigger cannot return a value.
Action:
Remove the bind variable from the PL/SQL.
REP-01351
Icon {1} on button {0} cannot be found.
Category:
Other
Cause:
The icon specified as the button face for the named button cannot be found. The report will run, but the button will appear blank.
Action:
Open the Property Inspector for the named button and verify that the icon specified exists and is in the correct format, and that the path information is correct.
REP-01352
The fonts specified for this report cannot be found for the character set specified by NLS_LANG.
Category:
Other
Cause:
The NLS_LANG environment variable specifies a character set for which no font is available.
Action:
Select a font that exists in the character set specified by NLS_LANG. Alternatively, use the Font Alias file to force an available font to be used, instead of the one specified in the report.
REP-01353
The Web property of layout object {0} references field or column {1} at the wrong frequency.
Category:
Other
Cause:
One of the layout object properies (Bookmark, Action. Hyperlink, or Linktag) references a field or column, but the two objects are not located at the same frequency. For example, the layout object is located within a repeating frame whose source is a different group to that the column is in.
Action:
Place the layout object in a repeating frame at the same frequency as the column object, or remove the reference.
REP-01354
The Web property of layout object {0} references a page-dependent field or column {1}.
Category:
Other
Cause:
One of the layout object properies (Bookmark, Action. Hyperlink, or Linktag) references a field or boilerplate object that has a reference to a page calculation or a total number of pages variable. Web properties may only reference columns and fields that are not based on page calculations.
Action:
Remove the Web property reference to the page-dependent field or column.
REP-01355
PL/SQL is missing from PL/SQL-based query {0}.
Category:
Other
Cause:
A PL/SQL based query was created, but no PL/SQL was entered for it.
Action:
Enter PL/SQL for the query.
REP-01356
A column link is not allowed for linking to PL/SQL-based query {0}.
Category:
Other
Cause:
An attempt was made to link a column to another column that is in PL/SQL-based query, which is not allowed.
Action:
Create group links and use the columns in the PL/SQL-based query as bind variables to set up intended column link conditions.
REP-01357
Auto foreign key column link creation is only for SQL queries.
Category:
Other
Cause:
A link was dragged between two queries to automatically create column links based on foreign key relationships. However, this can be done only between two SQL queries.
Action:
Drag a link between two SQL queries, or change the PL/SQL-based queries to SQL.
REP-01365
A column link is not allowed for linking to Express-based query {0}.
Category:
Other
Cause:
An attempt was made to link a column to another column that is an Express-based query, which is not allowed.
Action:
Create group links and use the columns in an Express-based query as bind variables to set up intended column link conditions.
REP-01366
The XML Settings of object {0} reference page-dependent field or column {1}.
Category:
Other
Cause:
One of the object's XML properties references a field that contains a page calculation or a total number of pages variable. XML Settings canot reference columns and fields that are based on page calculations.
Action:
Remove the XML Settings references to the page-dependent field or column.
REP-01367
The XML Settings of object {0} reference field or column {1} at the wrong frequency.
Category:
Other
Cause:
One of the object's XML properties references a field or column that has a different frequency than the object (for example, the column may be in a different group than the object referencing it).
Action:
Move the object such that it has the same frequency as the field or column (for example, place them in the same group) it references or remove the reference.
REP-01368
Group {0} in the graph settings is invalid.
Category:
Other
Cause:
In the graph object's graph settings, the src attribute is an invalid group name.
Action:
Ensure that value of the src attribute is a valid group name.
REP-01369
An internal error occurred caused by form field {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01370
Action {0} is unsupported.
Category:
Other
Cause:
The action specified against the form field is curently not supported.
Action:
Remove the action entry from the report definition.
REP-01371
Form field object {0} is unsupported.
Category:
Other
Cause:
This form field type is currently not supported by Oracle Reports.
Action:
Remove the Form Field element from the report definition.
REP-01372
The export value specified for {0} is invalid.
Category:
Other
Cause:
Either the export value is not specified or the export value is "off".
Action:
Specify a valid export value ("off" is a reserved word).
REP-01373
The validation and formatAndTreatment elements are not allowed for Form Field {0}.
Category:
Other
Cause:
The 'validation' or 'formatAndTreatment' element was specified for a Check Box and Radio Button.
Action:
Remove the 'validation' or 'formatAndTreatment' element for the Form Field object.
REP-01374
Font {0} is used to subset for the Form Field object {1}.
Category:
Other
Cause:
The font that is used to render a Form Field object was subsetted, which is not allowed.
Action:
Either remove the font entry in uifont.ali or modify the font name of the Form Field object to a font that is not subset.
REP-01400
coxr is not initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01401
A fatal PL/SQL error occurred in program unit {2}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01402
An unhandled PL/SQL exception occurred in program unit {2}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01403
A PL/SQL procedure is suspended in program unit {2}.
Category:
Other
Cause:
A PL/SQL construct was suspended during execution or generation.
Action:
Debug and recompile the PL/SQL constructs.
REP-01404
PL/SQL compilation failed.
Category:
Other
Cause:
In generating the report, PL/SQL compilation failed.
Action:
Debug the PL/SQL constructs.
REP-01405
The PL/DQL code is not executable.
Category:
Other
Cause:
A PL/SQL construct did not compile properly or could not be executed.
Action:
Debug the PL/SQL constructs.
REP-01406
Parameterized code cannot be run directly.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01408
The PL/SQL cannot be initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01409
Expected IS after PROCEDURE cannot be found.
Category:
Other
Cause:
A PL/SQL syntax error occurred.
Action:
Correct the PL/SQL procedure in trigger/program unit and compile.
REP-01410
An error occurred executing a PL/SQL filter in program unit {2}.
Category:
Other
Cause:
A PL/SQL syntax error occurred.
Action:
Correct the PL/SQL procedure in trigger/program unit and compile.
REP-01411
An error occurred executing PL/SQL formula in program unit {2}.
Category:
Other
Cause:
A PL/SQL syntax error occurred.
Action:
Correct the PL/SQL procedure in program unit of formula column or trigger. Verify the variable declarations and usage.
REP-01412
PL/SQL function {2} returned an invalid value or no value.
Category:
Other
Cause:
The report contains a PL/SQL function that does not specify a return value (for example, a format trigger that does not return TRUE or FALSE).
Action:
Verify that the function includes a return statement for every code path.
REP-01414
A library unit to run cannot be found in program unit {2}.
Category:
Other
Cause:
This is most likely an abnormal condition.
Action:
Check the PL/SQL code and recompile it. If this error recurs, contact Oracle Support Services.
REP-01415
An unknown user exit {0} was encountered in program unit {2}.
Category:
Other
Cause:
A user exit was called, but it was not found.
Action:
Verify the correct name for the user exit and that it has been compiled and linked.
REP-01416
An error occurred in user exit {0} in program unit {2}. {1}.
Category:
Other
Cause:
An error occurred in a user exit. Possible errors: a reference to an unknown column, a truncated column value, unretrievable PL/SQL source, or the user exit was not found.
Action:
Based on the submessage, debug the user exit. Veirfy columns references are valid and the PL/SQL code and user exit are accessible.
REP-01417
An invalid integer argument was passed to procedure {0} in program unit {2}.
Category:
Other
Cause:
The packaged procedure referenced expected an integer for an argument, but it was not specified.
Action:
Verify that the PL/SQL that references the packaged procedure correctly passes it an integer. For more information about PL/SQL packaged procedures, see the Oracle Reports online help.
REP-01418
Null arguments were passed to procedure {0} in program unit {2}.
Category:
Other
Cause:
The exception SRW.NULL_ARGUMENTS was raised, either by a user-defined PL/SQL subprogram, or because a packaged subprogram was passed one or more null arguments.
Action:
Check any PL/SQL code that might raise this exception. Also, check the argument list that is passed to the specified packaged subprogram.
REP-01419
The PL/SQL program was aborted in program unit {2}.
Category:
Other
Cause:
A PL/SQL construct had a fatal error and was aborted.
Action:
Check the PL/SQL constructs for errors.
REP-01420
The PL/SQL program raised a program error in program unit {2}.
Category:
Other
Cause:
The exception SRW.PROGRAM_ERROR was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition.
Action:
Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, contact Oracle Support Services.
REP-01421
A column of the wrong type was manipulated in procedure {0} in program unit {2}.
Category:
Other
Cause:
The data type of the column whose name was passed to a packaged procedure is not the correct data type for the packaged procedure (for example, the packaged procedure was expecting a column of Character data type and it was passed a column of another data type).
Action:
Debug the PL/SQL that references packaged procedures and ensure that the packaged procedure is passed the name of a column of the correct data type. Also check the syntax of the packaged procedure to ensure that its is referenced properly.
REP-01422
A procedure by this name already exists.
Category:
Other
Cause:
An attempt was made to create a new PL/SQL procedure with the same name as an existing PL/SQL procedure.
Action:
Change the name of the new procedure or change the name of the existing procedure.
REP-01423
Maximum rows of a query cannot be set after the query started executing in program unit {2}.
Category:
Other
Cause:
SRW.SET_MAX_ROW was used to reduce the number of rows fetched by a query. However, SRW.SET_MAX_ROW was called after the query was already fetched.
Action:
Move SRW.SET_MAX_ROW to the Before Report trigger.
REP-01424
An internal error occurred while executing procedure {0} in program unit {2}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01425
An error occurred running DO_SQL package in program unit {2}: {0}.
Category:
Other
Cause:
An error occurred while Oracle Reports Builder was executing an SRW.DO_SQL call. Embedded in this message is an Oracle Reports Builder message and, possibly, an Oracle error message describing the exact error that occurred.
Action:
Errors in SRW.DO_SQL are most often the result of a SQL error. Refer to the SQL Language Reference Manual and verify that the SQL statement in the SRW.DO_SQL call is correct.
REP-01426
Procedure {0} was running from incorrect context in program unit {2}.
Category:
Other
Cause:
An attempt was made to call the named packaged procedure from an invalid area. For example, SRW.SET_ATTR cannot be called from a formula.
Action:
Modify the PL/SQL code so that it does not call the packaged procedure from that context.
REP-01427
A nonexistent query name was referenced in procedure {0} in program unit {2}.
Category:
Other
Cause:
A call was made to the SRW.SET_MAXROW procedure in a Before Report trigger, but the query referenced in the procedure call does not exist.
Action:
Change the call to the SRW.SET_MAXROW procedure so that it references an existing query in the report.
REP-01428
An error occurred while running procedure {0} in program unit {2}.
Category:
Other
Cause:
The exception SRW.RUN_REPORT_FAILURE was raised, either by a user-defined PL/SQL subprogram, or because of an abnormal condition after SRW.RUN_REPORT was called.
Action:
Check any PL/SQL code that might raise this exception. If no PL/SQL raised the exception, check the command line string passed to SRW.RUN_REPORT. Verify that BATCH=YES, that the specified report exists, and that all parameter values are correct.
REP-01429
Procedure {0} cannot be invoked with BATCH=NO in program unit {2}.
Category:
Other
Cause:
A call was made to the SRW.RUN_REPORT procedure with a command line string containing BATCH=NO, which is not allowed.
Action:
Remove BATCH=NO from the SRW.RUN_REPORT command string.
REP-01430
A REP file for report {0} cannot be created: compilation errors found.
Category:
Other
Cause:
There is an error in the PL/SQL in the report to be converted.
Action:
Open the report and debug the PL/SQL.
REP-01433
An error occurred running user exit {0} in program unit {2}.
Category:
Other
Cause:
While running the user exit named in the message, an error occurred.
Action:
Debug the user exit and ensure that it is linked.
REP-01434
Procedure {0} cannot be invoked with a user ID in program unit {2}.
Category:
Other
Cause:
A call was included to the SRW.RUN_REPORT procedure with a command line string containing a userid/password, which is not allowed.
Action:
Remove the userid/password from the SRW.RUN_REPORT command string.
REP-01435
The value of column {0} was truncated in program unit {2}.
Category:
Other
Cause:
A column (for example, a placeholder) was assigned a value larger than its width could contain, raising the SRW.TRUNCATED_VALUE exception. The exception was not handled, raising this error.
Action:
Make the column wide enough to contain the assigned value, or handle the exception in the PL/SQL source.
REP-01436
The PL/SQL references an object that is not in the scope in program unit {2}.
Category:
Other
Cause:
In a parameter's Validation Trigger field, PL/SQL source referenced a report column, which is not allowed.
Action:
Remove the reference to the report column from the parameter's Validation Trigger.
REP-01437
A run time error in the PL/SQL development environment (DE).
Category:
Other
Cause:
This is most likely an abnormal condition.
Action:
Refer to the accompanying development environment error message for details on the problem. For assistance, contact Oracle Support Services.
REP-01438
The GETREF function parameter {0} must be of type LONG, LONG RAW, or RAW.
Category:
Other
Cause:
The second parameter in a CDE_MM.GET_REF call specifies a column that is not of type LONG, LONG RAW, or RAW.
Action:
Change the second parameter to specify a column of the correct type.
REP-01440
An unknown column name was passed to {0} in program unit {2}.
Category:
Other
Cause:
A column name specified in the named program unit in one of the triggers is invalid.
Action:
Verify the column name is correct.
REP-01441
A column value was not available for {0} in program unit {2}.
Category:
Other
Cause:
A column name specified in the named program unit in one of the triggers is not available.
Action:
Verify the column value is correct.
REP-01442
Column value {0} cannot be set in program unit {2}.
Category:
Other
Cause:
A value is not settable for this column.
Action:
Verify the procedure is correct.
REP-01443
Column value {0} is invalid in program unit {2}.
Category:
Other
Cause:
A column value specified in the named program unit in one of the triggers is invalid.
Action:
Verify the column value is correct.
REP-01444
No more rows exist in the group handle.
Category:
Other
Cause:
SRW.GH_NEXT() is called when the group handle is already at the last row.
Action:
Catch a SRW.NO_DATA_FOUND exception in PL/SQL.
REP-01445
The JAVA class cannot be found.
Category:
Other
Cause:
The requested class could not be located within the Reports classpath.
Action:
Ensure that the class is correctly specified (for example, java/lang/String) and that the class is in the Reports classpath specified in the REPORTS_CLASSPATH environment variable.
REP-01446
The JAVA method cannot be found.
Category:
Other
Cause:
The requested method could not be located within in the specified class.
Action:
Ensure that the method exists within the specified class and has the correct signature: '(Ljava/lang/String;)Ljava/lang/String;'.
REP-01447
A JAVA exception was encountered.
Category:
Other
Cause:
An error occurred attempting to start the JVM and access the requested Java class and method.
Action:
Check the JVM install and environment.
REP-01448
The data model group passed to SRW.GH_CREATE() does not exist.
Category:
Data
Cause:
The group name parameter of SRW.GH_CREATE() is invalid.
Action:
Ensure that the group name is correctly specified. Catch the SRW.UNKNOWN_GROUP exception in PL/SQL.
REP-01508
Cross Product: value of calculation cannot be found.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01510
Group Manager: unable to compute column {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01516
Reset At Page is an invalid option for column {0} in Web-based reports.
Category:
Other
Cause:
A column in the report layout has Reset At Page, which is invalid for Web-based reports.
Action:
Specify Reset At for either a group or report for Web-based reports.
REP-01517
Column {0} references column {1}, which has incompatible frequency.
Category:
Other
Cause:
A column in the data model references another column (for example, in the Formula field) in the 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 is raised.
Action:
Remove the column reference, or assign the referencing column to a group that is compatible with the group of the referenced column.
REP-01518
Group Manager: internal error {0} occurred while processing group {1}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01607
Record Manager: the source of report level column {0} is not available.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01610
Record Manager: a query with internal joins has Maximum Number of Rows set.
Category:
Other
Cause:
SRW.SET_MAXROW was probably used to set Maximum Number of Rows on the cell query of a multiquery cross product.
Action:
Remove the call to SRW.SET_MAXROW for the cell query.
REP-01760
Error Utility: internal error #1 occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01761
Internal error {0} occurred while processing {2} {1}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01762
Internal error {0} occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01780
Stack utility: an error occurred during allocation.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01781
Stack utility: an error occurred during push.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01782
Stack utility: an error occurred during pop.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01783
Stack utility: an attempt was made to pop an empty stack.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01800
A formatter error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01801
An unknown file type was encountered for a Read from File field.
Category:
Other
Cause:
An attempt was made to create a file column, but the file type entered was invalid.
Action:
Display the list of values and pick a valid file type.
REP-01802
Contents of a field cannot be read from a text file.
Category:
Other
Cause:
Read from File was selected for a column, but Oracle Reports Builder could not find the files pointed to by the column. The possible causes of this error include the following: Case 1: The files do not exist. Case 2: The necessary privileges to access the files are not granted. Case 3: A system error made it impossible to find the files.
Action:
Take the following actions to correct this error: If Case 1: Uncheck Read from File or create the necessary files. If Case 2: Update privileges, if possible. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-01803
Destination file {0} cannot be opened.
Category:
Other
Cause:
The destination file specified for the report could not be opened.
Action:
Consult the operating system documentation or contact the system administrator.
REP-01804
Printer definition file {0} cannot be opened.
Category:
Other
Cause:
The printer definition file for the specified printer could not be opened.
Action:
Consult the operating system documentation or contact the system administrator.
REP-01805
Mail text file {0} cannot be opened.
Category:
Other
Cause:
An attempt was made to send the report output to a mail message, but the file for the message could not be opened.
Action:
Consult the Oracle*Mail documentation or contact Oracle Support Services.
REP-01806
Mail command file {0} cannot be opened.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01807
The mail report command failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01808
The print command file cannot be opened.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01809
The print report command failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01810
The Oracle Reports Builder ASCII Driver will be used to run a character report.
Category:
Other
Cause:
An attempt was made to print a character-mode report to a printer or a file using either a PostScript driver or the Microsoft Windows Generic Text driver.
Action:
No action necessary.
REP-01811
An error occurred while generating a graph.
Category:
Other
Cause:
Oracle Reports Builder called Graphics Runtime to generate a graph, but no graph was created.
Action:
Verify that the named graph document exists and will run.
REP-01812
Too many pages formatted. There is either too much data or an error in the report's definition.
Category:
Data
Cause:
The possible causes of this error include the following: Case 1: A user-defined limit set to catch too much data has been reached. Case 2: An error in the report definition has been reached.
Action:
Take the following actions to correct this error: If Case 1: Abort running 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 Report Editor.
REP-01813
Object {0} is too large to fit in a matrix cell.
Category:
Other
Cause:
The data fetched into a matrix cell exceeds the capacity of the cell. For example, the cell may contain a variable field, and the data may be longer than expected.
Action:
Either enlarge the matrix cells until they are able to contain the data fetched into them, or redefine the data.
REP-01814
The report cannot be formatted. Object {1} cannot fit within location {0}.
Category:
Other
Cause:
The referenced object is causing the most recently formatted page to start with exactly the same state as the previous page. Formatting will therefore cycle until abnormally terminated. Possible causes of this error include: Case 1: An object whose Print Condition type is All overflows to the next page. Case 2: An object whose sizing is Variable or Expand does not appear to extend beyond page boundaries in the Paper Layout editor but does when the report is formatted. Case 3: A repeating frame does not appear to extend beyond page boundaries in the Paper Layout editor but does when the report is formatted.
Action:
Using the referenced object as a guide, examine the 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.
REP-01815
A bad Oracle Number was encountered.
Category:
Other
Cause:
A formula providing the value of a column failed to specify any value.
Action:
Debug any formulas in the report columns and ensure that each formula specifies a value where necessary.
REP-01816
No value was specified for COPIES, and no output was created.
Category:
Other
Cause:
In the Runtime Parameter Form or the Print Job dialog box, zero (0) copies was specified.
Action:
Specify a value of one or more copies.
REP-01817
The start page occurs after the end page. No pages were generated.
Category:
Other
Cause:
In the Print Job dialog box, a starting page number was specified that is greater than the ending page number.
Action:
Change either the starting page number or the ending page number such that the starting number is less than the ending number.
REP-01818
Data in image format could not be read.
Category:
Data
Cause:
Possible causes of this error include: Case 1: An attempt was made to read a file or database column as containing an image, but the file or column's contents are of the wrong format. Case 2: The width of the Oracle Reports Builder column specified may be truncating the image because it is too small. Case 3: REPORTS_DEFAULT_DISPLAY is set to YES and the image format used is not supported.
Action:
Take the following actions to correct this error: If Case 1: Verify that the file or column specified contains an image in a valid format. If Case 2: Change the width of the Oracle Reports Builder column so that it is large enough to display the image. If Case 3: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
REP-01819
Filename {0} is longer than the platform maximum of {1} characters.
Category:
Other
Cause:
A name was specified for a file that is longer than the platform-allowed maximum. This is most likely to occur when accessing a file using Read from File, and the file name in the database is too long.
Action:
Verify that the database is not corrupted, or run the report on a platform that accepts filenames of the specified length.
REP-01820
The Oracle Reports Builder ASCII Driver cannot be used to run a bitmap report.
Category:
Other
Cause:
An attempt was made to print a bitmapped report when the Oracle Reports Builder ASCII Driver is the default printer.
Action:
Select a different printer, then print the report.
REP-01825
The Before Report trigger returned FALSE.
Category:
Other
Cause:
The report includes a Before Report trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops.
Action:
Verify that the report trigger is meant to return a value of FALSE.
REP-01826
The Between Page trigger returned FALSE.
Category:
Other
Cause:
The report includes a Between Page trigger that returned a value of FALSE rather than TRUE. When a trigger returns a value of FALSE, report formatting stops.
Action:
Verify that the report trigger is meant to return a value of FALSE.
REP-01827
Parentheses in the format mask do not balance.
Category:
Other
Cause:
Unmatched parenthesis exist in the format mask.
Action:
Edit the format mask and insert the necessary parenthesis.
REP-01828
A format mask may contain at most one set of parentheses.
Category:
Other
Cause:
More than one set of parentheses was used in the format mask.
Action:
Use only one set of parentheses in the format mask.
REP-01829
Left parenthesis must precede right parenthesis in a format mask.
Category:
Other
Cause:
The order of the parentheses was reversed in the format mask; that is, the right, or close, parenthesis was used before the left, or open parenthesis.
Action:
Edit the format mask and reverse the order of the parentheses.
REP-01830
The Exponent field in a format mask must contain exactly 4 Es.
Category:
Other
Cause:
The scientific notation specified for the field contained too many or too few E's.
Action:
Enter the format mask with four E's. To have extra E's appear in the output, put them in quotation marks (").
REP-01831
A closing quotation mark in format mask is missing.
Category:
Other
Cause:
An opening quotation mark (") was entered before the string in the format mask, but not a closing one. The possible causes of this error include the following: Case 1: No closing quotation mark was entered after the string. Case 2: One quotation mark was entered within the quotation marks that begin and end the string.
Action:
Take the following actions to correct this error: If Case 1: Add an ending quotation mark after the string. If Case 2: Enter another quotation mark next to the quotation mark inside the string.
REP-01832
Illegal character {0} was encountered in the format mask.
Category:
Other
Cause:
A character was entered in a format mask that is not valid for format masks.
Action:
Delete the illegal character. For more information, see the date and time format mask information in the Building Reports manual.
REP-01833
A format mask must contain at least one digit.
Category:
Other
Cause:
The format mask entered contains no digits. At least one token in the mask must represent a digit.
Action:
Enter a token in the format mask that represents a digit. The tokens that represent digits are 0, 9, *, and S. For more information, see the date and time format mask information in the Building Reports manual.
REP-01834
A format mask may contain at most one < character.
Category:
Other
Cause:
The format mask included two left angle brackets (&lt;&lt;). The angle brackets need not be entered sequentially to cause the error.
Action:
Delete the extra left angle bracket or place it inside quotation marks (") as part of a string if it should appear in the output.
REP-01835
A format mask may contain at most one > character.
Category:
Other
Cause:
The format mask included two right angle brackets (&gt;&gt;). The angle brackets need not be entered sequentially to cause the error.
Action:
Delete the extra right angle bracket or place it inside quotation marks (") as part of a string if it should appear in the output.
REP-01836
A left angle bracket must come before a right angle bracket in a format mask.
Category:
Other
Cause:
The left angle bracket (&lt;) must come before the right angle bracket (&gt;) in a format mask.
Action:
Ensure that all angle brackets that are to appear in the output are placed inside quotation marks ("). For the angle brackets that delineate the beginning and ending of the decimal aligned region, ensure that the left angle bracket precedes the right angle bracket in the format mask.
REP-01837
A format mask may contain at most one decimal point.
Category:
Other
Cause:
A format mask was entered with multiple decimal points.
Action:
To have extra decimal points appear in the output, place them in quotation marks ("). Remove any extra decimal points outside of quotation marks.
REP-01838
A format mask may contain at most one scale point.
Category:
Other
Cause:
The token V was entered more than once within the format mask.
Action:
To have extra V's appear in the output, place them in quotation marks ("). Otherwise, delete the V's until there is only one in the format mask.
REP-01839
A comma is not allowed before the first digit in a format mask.
Category:
Other
Cause:
A comma (,) was entered before the first digit in the format mask, which is illegal.
Action:
To have a comma appear before the digits in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
REP-01840
A comma is not allowed after the last digit in a format mask.
Category:
Other
Cause:
A comma (,) was entered after the last digit in the format mask, which is illegal.
Action:
To have a comma appear after the digits in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
REP-01841
A comma is not allowed after the decimal point in a format mask.
Category:
Other
Cause:
A comma (,) was entered after the decimal point in the format mask.
Action:
To have a comma appear after the decimal point in the output, place it in quotation marks (") as a string. Otherwise, delete the comma.
REP-01842
A format mask may contain at most one exponent field.
Category:
Other
Cause:
The token EEEE was entered more than once within the format mask. This token may be entered only once per format mask.
Action:
To have the extra E's appear in the output, place them in quotation marks ("). Otherwise, delete the extra EEEE tokens until there is only one in the format mask.
REP-01843
Format masks with exponent fields must have exactly one digit before the decimal point.
Category:
Other
Cause:
A scientific notation format mask was entered that had no digits or more than one digit to the left of the decimal point.
Action:
Delete digits or add a digit until there is only one to the left of the decimal point.
REP-01844
An internal error occurred: Bad index in a flexible array.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01845
The decimal point must come between the angle brackets in a format mask.
Category:
Other
Cause:
A decimal point was placed outside the left and right angle brackets (\&lt; and \&gt;) of the format mask.
Action:
Edit the format mask to either remove the decimal point or place it between the brackets.
REP-01846
A Roman numeral format mask must be simply \"RN\" or \"rn\".
Category:
Other
Cause:
A Roman numeral format mask token (RN or rn) was specified, along with other format mask tokens.
Action:
To format the values as Roman numerals, eliminate all format mask tokens except RN or rn from Format Mask. Otherwise, do not use the RN or rn token.
REP-01847
The current process failed while trying to set up for printing.
Category:
Process
Cause:
An attempt was made 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, Printer was specified for DESTYPE, but an invalid printer name was specified for DESNAME. Case 2: The report that was executed in turn executes a second report using SRW.RUN_REPORT. DESTYPE for both reports is set to either File or Printer, but the first report must be run to the screen.
Action:
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.
REP-01848
The current process failed while trying to begin printing.
Category:
Process
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01849
The current process failed while printing.
Category:
Process
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01850
An error occurred in column {0} of line {1} of printer definition file {2}: End of file reached inside quoted string.
Category:
Other
Cause:
The printer definition file contains a quoted string that was not ended with a quote before the end of the file.
Action:
Use the location specified in the error message to locate the error and add the end quote to the quoted string in the printer definition file.
REP-01851
An error occurred in column {0} of line {1} of printer definition file {2}: String is longer than {3} characters.
Category:
Other
Cause:
A string in the printer definition file is longer than the maximum number of allowable characters.
Action:
Reduce the length of the string.
REP-01852
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
An incorrect keyword is included in the printer definition file.
Action:
Verify the printer definition file syntax.
REP-01853
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
An incorrect keyword was found in the printer definition file.
Action:
Verify the printer definition file syntax.
REP-01854
An error occurred in column {0} of line {1} of printer definition file {2}: Invalid control character {3}.
Category:
Other
Cause:
An invalid control character was found in the printer definition file.
Action:
Replace or remove the invalid control character in the printer definition file.
REP-01855
An error occurred in column {0} of line {1} of printer definition file {2}: Unknown character {3}.
Category:
Other
Cause:
An unknown character was found in the printer definition file.
Action:
Replace or remove the unknown character in the printer definition file.
REP-01856
An error occurred in column {0} of line {1} of printer definition file {2}: {3} is not a valid ASCII character.
Category:
Other
Cause:
An invalid ASCII character appears in the printer definition file.
Action:
Replace or remove the invalid ASCII character in the printer definition file.
REP-01857
An error occurred in column {0} of line {1} of printer definition file {2} following {3}.
Category:
Other
Cause:
An unmatched parenthesis was found in the printer definition file.
Action:
Edit the printer definition file and insert the necessary parenthesis.
REP-01858
An error occurred in column {0} of line {1} of printer definition file {2}: octal {3} is not a valid ASCII character.
Category:
Other
Cause:
The octal code for an ASCII character in the printer definition file is incorrect.
Action:
Edit the printer definition file and correct the code for the ASCII character.
REP-01859
An error occurred in column {0} of line {1} of printer definition file {2}: hex {3} is not a valid ASCII character.
Category:
Other
Cause:
The hex code for an ASCII character in the printer definition file in incorrect.
Action:
Edit the printer definition file and correct the code for the ASCII character.
REP-01860
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains an incomplete code string.
Action:
Edit the printer definition file and complete the code string with the appropriate word.
REP-01861
An error occurred in column {0} line {1} of file {2}.
Category:
Other
Cause:
The printer definition file contains an incomplete "box" code string.
Action:
Edit the printer definition file and complete the "box" code string with the appropriate word.
REP-01862
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file does not include the required code "printer".
Action:
Edit the printer definition file and add the required code "printer" followed by the name of the printer in a quoted string, preferably on the first line of the printer definition file.
REP-01863
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the name of the printer after the "printer" code, but the name does not appear in a quoted string.
Action:
Edit the printer definition file and place quotation marks (") around the name of the printer after the "printer" code.
REP-01864
An error occurred in column {0} line {1} of file {2}.
Category:
Other
Cause:
The printer definition file does not contain any of the code words expected in a printer definition file.
Action:
Edit the printer definition file and add the code words that are missing.
REP-01865
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the "width" code, but no number specifying the width of the report appears after it.
Action:
Edit the printer definition file and insert a number specifying the width of the report after the "width" code.
REP-01866
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the "height" code, but no number specifying the height of the report appears after it.
Action:
Edit the printer definition file and insert a number specifying the height of the report after the "height" code.
REP-01867
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the word "before" but not the accompanying word "report".
Action:
Edit the printer definition file to include a complete "before report" entry.
REP-01868
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the word "between" but not the accompanying word "pages".
Action:
Edit the printer definition file to include a complete "between pages" entry.
REP-01869
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file (for a multipage report) contains the code word "after" but not the accompanying word "report".
Action:
Edit the printer definition file to include a complete "after report" entry.
REP-01870
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the "code" code with a user-defined string, but the string is not enclosed within quotation marks.
Action:
Edit the printer definition file and enclose the "code" user-defined string with quotation marks.
REP-01871
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string using "dec", but "dec" is not followed with a left parenthesis.
Action:
Edit the printer definition file and add parentheses around the value following "dec".
REP-01872
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string (for example, dec or octal), but no value follows the right parenthesis.
Action:
Edit the printer definition file and add a value between the parentheses in the generalized string.
REP-01873
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string using "octal", but "octal" is not followed with a left parenthesis.
Action:
Edit the printer definition file and add parentheses around the value following "octal".
REP-01874
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string (for example, dec or octal), but no value follows the left parenthesis.
Action:
Edit the printer definition file and add a value between the parentheses in the generalized string.
REP-01875
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string using "hex", but "hex" is not followed with a left parenthesis.
Action:
Edit the printer definition file and add parentheses around the value following "hex".
REP-01876
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string (for example, dec or octal), but no value follows the left parenthesis.
Action:
Edit the printer definition file and add a value between the parentheses in the generalized string.
REP-01877
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a generalized string using "^", but no control character follows the "^".
Action:
Edit the printer definition file and add a control character after "^".
REP-01878
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a keyword and generalized string (for example, after report or before report), but no left parenthesis follows the word "control".
Action:
Edit the printer definition file and add a left parenthesis following the word "control".
REP-01879
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains a keyword and generalized string (for example, after report or before report), but no control character follows the left parenthesis.
Action:
Edit the printer definition file and add a control character between the parentheses after the word "control".
REP-01880
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the "box" code string, but the drawing string specified between quotation marks is more than one character long.
Action:
Edit the printer definition file, making sure that one and only one character is specified as a drawing string.
REP-01881
An error occurred in column {0} of line {1} of printer definition file {2}.
Category:
Other
Cause:
The printer definition file contains the "box" code string, but no drawing string is specified.
Action:
Edit the printer definition file and specify a drawing string.
REP-01882
An error occurred in column {0} line {1} of file {2}.
Category:
Other
Cause:
The printer definition file contains the "box" code string, but the following required word (one of 'horizontal', 'vertical', 'top', 'center', or 'bottom') is not specified.
Action:
Edit the printer definition file and add the appropriate required word.
REP-01883
Unexpected end of printer definition file was reached.
Category:
Other
Cause:
Oracle Reports Builder was able to open the printer definition file, but an error occurred while reading it.
Action:
Verify that the correct printer definition file is specified. Also, check the contents of the printer definition file. Edit the file if necessary.
REP-01884
A hang occurred while sending output.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01885
Output could not be sent to the printer.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-01886
Expected I after M in the format mask cannot be found.
Category:
Other
Cause:
The M entered in a format mask was not followed by I. The only token that begins with M is the MI token.
Action:
To use the MI token, enter an I after the M. To have the character M appear in the output, place it inside double quotation marks ("). Otherwise, delete the M from Format Mask.
REP-01887
Expected R after P in the format mask cannot be found.
Category:
Other
Cause:
The P entered in a format mask was not followed by R. The only token that begins with P is the PR token.
Action:
To use the PR token, enter an R after the P. To have the character P appear in the output, place it inside double quotation marks ("). Otherwise, delete the P from Format Mask.
REP-01888
Only one sign token is allowed.
Category:
Other
Cause:
More than one sign token was entered in a format mask.
Action:
Delete all sign tokens but one from the format mask.
REP-01889
A trailing sign token must be at the end.
Category:
Other
Cause:
A sign token was not placed at the end of the format mask.
Action:
Place the sign token (for example, MI, PR, DB, and CR) at the end of the format mask.
REP-01890
The S token must be at the beginning or end.
Category:
Other
Cause:
The S token was not placed at the beginning or the end of the format mask.
Action:
Place the S token at the beginning or the end of the format mask or delete it.
REP-01891
Parentheses tokens must surround other tokens.
Category:
Other
Cause:
The parentheses tokens do not surround all other tokens in the format mask.
Action:
Place the parentheses around all of the other tokens in the format mask.
REP-01892
The destype specified is not supported for pdf or html.
Category:
Other
Cause:
An invalid destination type (destype) was specified for pdf or html output.
Action:
Specify a destination type (destype) of file or cache for pdf or html output.
REP-01893
The destype specified is not supported on this platform.
Category:
Other
Cause:
An invalid destination type (destype) was specified for the operating system (for example, Sysout, while running on Microsoft Windows).
Action:
Specify a valid destination type.
REP-01894
The report definition was modified during the current run. No new pages will be generated.
Category:
Other
Cause:
While previewing a report (using Oracle Reports Builder), the report's definition was modified, and then an attempt was made to view additional pages from the Previewer. Oracle Reports Builder cannot guarantee that all of the information used at runtime is still present, so formatting is halted.
Action:
No action required.
REP-01895
A date formatting error occurred while processing field {0}.
Category:
Other
Cause:
Oracle Reports Builder could not format the specified date field.
Action:
Check the format mask of the specified date field.
REP-01896
An error occurred in column {0} of line {1} of printer definition file {2}: Expected backspace or overstrike to follow hilight.
Category:
Other
Cause:
The specified printer definition file contains the 'hilight' setting, but the setting was not completed properly.
Action:
Add either 'overstrike' or 'backspace &lt;sequence&gt;' after 'hilight'.
REP-01897
An error occurred in column {0} of line {1} of printer definition file {2}: Non-numeric user-defined printer codes are not supported.
Category:
Other
Cause:
The specified printer definition file contains a user-defined printer code that is not a number.
Action:
Change the user-defined printer code to a number.
REP-01898
An error occurred in column {0} of line {1} of printer definition file {2}: Hilight setting can only be defined once.
Category:
Other
Cause:
The specified printer definition file contains more than one hilight setting.
Action:
Remove all but one of the hilight settings from the printer definition file.
REP-01899
Graphics Display or Icon cannot be converted to .gif format - image skipped.
Category:
Other
Cause:
Oracle Reports Builder was unable to convert an embedded Graphics Display or icon to a GIF format for displaying within an HTML document. This only occurs when Oracle Reports Builder cannot access a window system in order to draw the image.
Action:
Run the report using the bitmap executable under a windowing system to allow Oracle Reports Builder access to a display.
REP-01920
Character mode runtime is incompatible with DESFORMAT of PDF, HTML, HTMLCSS, SPREADSHEET, or RTF.
Category:
Other
Cause:
An attempt was made to run a report with a destination format of PDF, HTML, HTMLCSS, SPREADSHEET, or RTF. These formats are only available when running in a bitmap environment and producing a bitmap output.
Action:
Rerun the report with a bitmap executable or set MODE=BITMAP if already running with a bitmap executable.
REP-01921
Input printer tray {0} is not available on the selected printer.
Category:
Other
Cause:
An attempt was made to alter the input printer tray but the name of the tray specified is not available on the currently selected printer.
Action:
Change the selected printer to one that supports the specified tray or alter the tray name to one supported by the specified printer. Use Page Setup to view the list of printer trays supported by the printer.
REP-01922
A PDF compression error was encountered.
Category:
Other
Cause:
The compression engine failed compressing this page.
Action:
Turn off compression for this report by specifying PDFCOMP=NO on command line.
REP-01923
A PDF Font Embed error was encountered.
Category:
Other
Cause:
The font specified for embedding into the PDF document cannot be found or is invalid.
Action:
The [PDF:Embed] section must be present in the uifont.ali file. Check to ensure that the entry of font in the uifont.ali is syntactically correct. Verify that the location of font files is added to REPORTS_PATH in the registry/environment variable.
REP-01924
Font file {0} cannot be found.
Category:
Other
Cause:
The font file specified in UIFONT.ALI is not found.
Action:
Verify that the font file exists in REPORTS_PATH.
REP-01925
Font file {0} is invalid.
Category:
Other
Cause:
The font file appears to be corrupt or invalid.
Action:
Ensure the specified file is a valid font file.
REP-01926
Identical name {0} was specified for dissimilar form field types {1} and {2}.
Category:
Other
Cause:
The name specified for a form field conflicts with an existing form field of different type.
Action:
Select a new name for one of the form fields. Change the type of the form field to match that of the existing form field.
REP-01927
Cannot print document or generate output in printer format because the printer is offline or paused.
Category:
Other
Cause:
When destination type is printer or format is printer name, running request fails if the printer is offline or paused.
Action:
Bring the printer online and try again.
REP-01940
An error occurred in column {0} line {1} of file {2}: Expected visualorder, logicalorder, contextualshaping, contextuallayout, multibyte, or pcharset.
Category:
Other
Cause:
The printer definition file contains the 'nls' code string, but the required word (one of 'visualorder', 'logicalorder', 'contextualshaping', 'contextuallayout', 'multibyte', or 'pcharset') is not specified.
Action:
Edit the printer definition file and add the required word.
REP-01941
An error occurred in column {0} line {1} of file {2}: Expected yes or no.
Category:
Other
Cause:
The printer definition file contains 'visualorder', 'logicalorder', 'contextualshaping', 'contextuallayout', 'multibyte', or 'pcharset' code string, but the required word (either 'yes' or 'no) is not specified.
Action:
Edit the printer definition file and add the appropriate 'yes' or 'no'.
REP-01942
An error occurred in column {0} line {1} of file {2}: Expected name of character set to follow pcharset.
Category:
Other
Cause:
The printer definition file contains the 'pcharset' code string, but the required string (name of character set) is not specified.
Action:
Edit the printer definition file and add the name of character set.
REP-01943
An error occurred in column {0} line {1} of file {2}: Defined printer character set is unsupported.
Category:
Other
Cause:
The printer definition file contains an unsupported printer character set.
Action:
Edit the printer definition file and specify the name of a supported character set.
REP-01944
Invalid reference value {0} was specified for Report property {1}
Category:
Other
Cause:
The value specified for the indicated property cannot be resolved or is at a wrong frequency.
Action:
Ensure that the reference exists and resolves to a valid value. Only Report-level columns can be referenced with this property.
REP-01950
The Source specified is invalid.
Category:
Other
Cause:
The Source specified for Reports Converter is not a valid source.
Action:
Verify that the correct object or file is specified and that the STYPE is correct for that file or object.
REP-01951
The Destination specified is invalid.
Category:
Other
Cause:
The Destination specified for Reports Converter is not a valid destination.
Action:
Verify that the correct object or file is specified and that the DTYPE is correct for that file or object.
REP-01952
The number of Destination items must be zero or match the number of Source items.
Category:
Other
Cause:
In the Convert dialog box, or while using Reports Converter, the number of Destination items specified was greater than zero and did not match the number of Source items specified.
Action:
To have Oracle Reports Builder derive the Destination names from the specified Source names, leave Destination blank. Otherwise, verify that the number of Destination names specified matches the number of Source names specified. If wildcards are used in the Source specification, verify that the number of Destination names matches the number of Source items in the expanded wildcard list.
REP-02000
An error occurred in the user exit.
Category:
Other
Cause:
An error occurred in the user exit.
Action:
Debug the code or contact the database administrator.
REP-02001
An error occurred in IAF GET: unknown column {0}.
Category:
Other
Cause:
An unknown column name was specified in the user exit's IAF GET statement.
Action:
Specify a valid column name in the IAF GET statement.
REP-02002
An error occurred in IAF PUT: unknown column {0}.
Category:
Other
Cause:
An unknown column name was specified in the user exit's IAF PUT statement.
Action:
Specify a valid column name in the IAF PUT statement.
REP-02003
The user exit cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not find the user exit that it was supposed to run at this point. The most likely cause is that the name and/or location of the user exit code was not specified correctly.
Action:
Verify the name and location of the code when installing it. Otherwise, contact the database administrator.
REP-02004
PL/SQL source code of object {0} could not be retrieved.
Category:
Other
Cause:
From the File menu, Administration Report was selected to document one or more reports, but the RWEPLS user exit failed to retrieve the PL/SQL source code of an object. This is most likely an abnormal condition.
Action:
Check the PL/SQL source code in the named object. For assistance, contact Oracle Support Services.
REP-02005
An error occurred in IAF PUT: the value of column {0} was truncated.
Category:
Other
Cause:
The IAF PUT statement assigned a value to the named column, but the column was not wide enough to hold the entire value, causing it to truncate.
Action:
Widen the column so that it is can hold the entire value.
REP-02100
An error occurred in Calculation Manager.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02101
Calculation Manager: the source column cannot use segmented memory.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02102
Calculation Manager: the computed column cannot use segmented memory.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02103
The PL/SQL formula returned invalid value or no value for column {0}.
Category:
Other
Cause:
An SRW.DO_SQL statement was entered that caused this Oracle message.
Action:
Edit the SRW.DO_SQL statement. For more information about the Oracle message, see the Oracle Messages and Codes Manual.
REP-02300
Error {0} occurred.
Category:
Other
Cause:
An SRW.DO_SQL statement was entered that caused this Oracle message.
Action:
Edit the SRW.DO_SQL statement. For more information about the Oracle message, see the Oracle Messages and Codes Manual.
REP-02301
An error occurred allocating a SQLDA descriptor: {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02302
An error occurred parsing the SQL statement: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while parsing the SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the SQL statement could not be parsed.
REP-02303
An error occurred describing bind variables: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while describing bind variables in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the bind variables could not be described.
REP-02304
An error occurred opening a SQL cursor: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while opening a cursor in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the cursor could not be opened.
REP-02305
An error occurred describing the SELECT list: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while describing the SELECT list in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the bind variables could not be described.
REP-02306
An error occurred fetching bind variables: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while fetching bind variables in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the bind variables could not be fetched.
REP-02307
An error occurred fetching a data record: {0}.
Category:
Data
Cause:
Oracle Reports Builder encountered an error while fetching a data record in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the data record could not be fetched.
REP-02308
An error occurred processing the SELECT list: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while processing the SELECT list in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the SELECT list is invalid.
REP-02309
An error occurred formatting a date field: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while formatting a date field in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the date field could not format.
REP-02310
An error occurred putting a value into a column: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while trying to insert a value into a column in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the value could not be assigned.
REP-02311
An error occurred during Commit: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while trying to do a commit in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the commit failed.
REP-02312
An error occurred allocating a data record: {0}.
Category:
Data
Cause:
Oracle Reports Builder encountered an error while allocating a data record in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the record could not be allocated.
REP-02313
An error occurred parsing the SELECT list: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while parsing the SELECT list in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the SELECT list could not be parsed.
REP-02314
An error occurred closing a SQL cursor: {0}.
Category:
Other
Cause:
Oracle Reports Builder encountered an error while trying to close a SQL cursor in an SRW.DO_SQL statement.
Action:
Refer to the Oracle message to see why the close cursor operation failed.
REP-02315
An error occurred freeing a data record: {0}.
Category:
Data
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02316
Column {0} cannot be found.
Category:
Other
Cause:
A column referred to in an SRW.DO_SQL statement cannot be found.
Action:
Debug the PL/SQL and verify that the SRW.DO_SQL statement contains the correct column name.
REP-02317
The value of column {0} was truncated.
Category:
Other
Cause:
A column value obtained via an SRW.DO_SQL statement was truncated.
Action:
Go to the column's Property Inspector and increase its Width. Or, restrict the size of the value that the SRW.DO_SQL statement is putting into the column.
REP-02400
DEBUG: internal error 0 occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-02500
Error {0} occurred. See the Release Notes for further information about this error
Category:
Other
Cause:
The error is documented in the Release Notes.
Action:
See the Release Notes.
REP-02550
The in-process server was not started: {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
Refer to the in-process server message to see why it failed to start. Then restart the Oracle Reports Builder.
REP-03000
An internal error occurred starting Oracle Toolkit.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03001
An internal error occurred initializing the File Dialog.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03002
An error occurred initializing the printer. Verify that a printer is installed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03020
An internal error occurred starting Oracle Resource Manager.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03021
An internal error occurred processing a menu resource.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03022
An internal error occurred processing a window resource.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03023
The resource file cannot be found.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03040
An internal error occurred starting Oracle Observer Model.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03060
An internal error occurred initializing the color table. Checking VGS resources is recommended.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03080
An internal error occurred initializing Oracle Image.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03081
An error occurred running the image viewer.
Category:
Other
Cause:
A Previewer button was selected with a defined action of displaying an image, but the image viewer is unavailable. Possible causes of this error include: Case 1: The image specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.
Action:
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 possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
REP-03082
An error occurred running the sound dialog.
Category:
Other
Cause:
A Previewer button was selected with a defined action of playing a sound, but the sound dialog is unavailable. Possible causes of this error include: Case 1: The sound file specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.
Action:
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 possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
REP-03083
An error occurred running the video player.
Category:
Other
Cause:
A Previewer button was selected with a defined action of playing a video, but the video player is unavailable. Possible causes of this error include: Case 1: The video file specified as the source is in an incorrect format. Case 2: There is no available memory. Case 3: An abnormal condition was encountered.
Action:
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 possible, or ask the system administrator for assistance. If Case 3: For assistance, contact Oracle Support Services.
REP-03085
Multimedia source file {0} cannot be found.
Category:
Other
Cause:
The button was clicked in the Previewer, but the source for the button's intended action (whether sound, image, or video) cannot be found or has been corrupted.
Action:
Open the Property Inspector for the button in question and verify the existence, format, and path information for the specified source file.
REP-03086
The multimedia source file is not available.
Category:
Other
Cause:
The button was clicked in the Previewer, but the source for the button's intended action (whether sound, image, or video) has been corrupted.
Action:
Open the Property Inspector for the button in question and verify the existence, format, and path information for the specified source file. If it is correct, check the file itself.
REP-03087
ImageViewer is not supported in this configuration.
Category:
Other
Cause:
The platform or configuration does not support displaying images via the ImageViewer.
Action:
No action is necessary.
REP-03088
Sound is not supported in this configuration.
Category:
Other
Cause:
The platform or configuration does not support playback of sound files.
Action:
No action is necessary.
REP-03089
Video is not supported in this configuration.
Category:
Other
Cause:
The platform or configuration does not support playback of video files.
Action:
No action is necessary.
REP-03100
A matrix must include at least 1 Down and 1 Across repeating frame.
Category:
Other
Cause:
An attempt was made to create a matrix (selecting Arrange, then Create Matrix) without the proper objects selected in the Paper 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.
Action:
Select two repeating frames--one Down, one Across--that overlap, then select Create Matrix from the Arrange Menu.
REP-03101
All selected Down and Across repeating frames must be nested.
Category:
Other
Cause:
An attempt was made to create a matrix (selecting Arrange, then Create Matrix) and the Down and Across repeating frames were not properly overlapping and nested.
Action:
Verify that the selected Down and Across repeating frames are properly overlapping and nested before creating the matrix.
REP-03102
Anchors, matrices, and margins cannot be grouped.
Category:
Other
Cause:
Group was selected from the Arrange menu and at least one of the objects selected was an anchor, matrix, or margin.
Action:
Deselect all anchors, matrices, and margins before grouping objects.
REP-03103
Only text and graphical boilerplate objects can be rotated.
Category:
Other
Cause:
An attempt was made to rotate a frame, a field, a margin, an anchor, a matrix object, a file link boilerplate object, or a graph. None of these can be rotated.
Action:
Rotate any boilerplate objects except images and file link boilerplate objects. Depending on the operating system, the text of a rotated boilerplate text object may or may not be visible.
REP-03104
Anchors and matrices cannot be scaled separately from their associated objects.
Category:
Other
Cause:
An attempt was made to scale one of the layout objects listed above without also scaling its associated object, which is not allowed.
Action:
Select at least one associated object (anchoring object for anchors, repeating frames for matrices), then retry the scaling operation.
REP-03105
A graph Column must be selected for the graph Query.
Category:
Other
Cause:
A name was entered for the graph Query, but no graph Columns were selected. If a graph Query is specified, graph Columns must also be specified.
Action:
Specify graph Columns or remove the value from the graph Query.
REP-03106
a graph Column was selected without a graph Query name. The selected graph Column will be ignored.
Category:
Other
Cause:
A Source or graph Column was selected but a name for a graph Query was not entered.
Action:
Enter the name of the graph query to which to pass data.
REP-03107
Object {0} cannot be moved in front of its child {1}.
Category:
Other
Cause:
An attempt was made to move a layout object in front of one or more of its own child objects.
Action:
To move the layout object, toggle Confine mode off, then move it. Otherwise, no action is necessary.
REP-03108
Object {0} cannot be moved behind its container {1}.
Category:
Other
Cause:
An attempt was made to move a layout object behind one or more of its own parent objects.
Action:
To move the layout object, toggle Confine mode off, then move it. Otherwise, no action is necessary.
REP-03109
The alignment operation failed because of container constraints.
Category:
Other
Cause:
An attempt was made to align multiple layout objects but the result of such an operation would have violated container constraints (that is, moved a field outside of its enclosing frame).
Action:
Select Edit, then Undo to ensure the layout is the same as before the attempted operation. Then, either resize or reposition the container in question to perform the operation, or do nothing.
REP-03110
Same size operation failed because of container constraints.
Category:
Other
Cause:
An attempt was made to change one or more layout objects to the same size, but the result of such an operation would have violated container constraints (that is, enlarged a field beyond its enclosing frame).
Action:
Select Edit, then Undo to ensure the layout is the same as before the attempted operation. Then, either resize or reposition the container in question to perform the operation, or do nothing.
REP-03111
Changing the border width of {0} violates the constraints of confined mode.
Category:
Other
Cause:
An attempt was made to change the border width of an object such that the result would have violated container constraints (that is, widening the border of a boilerplate object so that it extended beyond its enclosing frame).
Action:
No action is necessary.
REP-03112
Objects cannot be created in the template layout body layer.
Category:
Other
Cause:
An attempt was made to create an object in the layout body layer of a template. Objects may only be created in the margin, header pages, or trailer pages of a template.
Action:
No action is necessary.
REP-03130
Parameter Form fields and images cannot be rotated.
Category:
Other
Cause:
An attempt was made to rotate one of the Parameter Form objects, which is not allowed.
Action:
Rotate any boilerplate objects, except images, in the Parameter Form editor. Depending on the operating system, the text of boilerplate text that is rotated may or may not be visible.
REP-03131
Parameter Form boilerplate text cannot fit on the page.
Category:
Other
Cause:
Text was entered in the Title, Hint, Status, or Label field in the Parameter Form Builder that is too long to fit on the page.
Action:
Reduce the length of the appropriate text field.
REP-03140
A Program Unit Editor internal error occurred: Could not get document handle.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03150
One editor must remain open for each report.
Category:
Other
Cause:
An attempt was made to close all three of the editors (Data Model, Layout, and Parameter Form) for a report. At least one editor must remain open.
Action:
Leave one editor open for each report.
REP-03151
The width for column {0} is invalid and cannot be highlighted, since group {1} is not selected.
Category:
Other
Cause:
An invalid value was entered for the Width of a column in the Report Wizard. Since the group that owns the column is not selected, the column is not listed.
Action:
Select the group that owns the column. Scroll down to the column and enter a valid value for Width.
REP-03152
The link, anchor, or polygon creation must be completed in the editor before this action.
Category:
Other
Cause:
An attempt was made to perform some action (for example, close the report) before finishing the creation of a data link in the Data Model editor, an anchor in the Paper Layout editor, or a polygon in the Paper Layout editor or Parameter Form editor.
Action:
Complete the unfinished object before continuing.
REP-03153
Insufficient resources are available to create the window.
Category:
Other
Cause:
There were insufficient resources available to create the requested window.
Action:
Make more resources available by closing windows or other applications.
REP-03154
Insufficient resources are available to create the document.
Category:
Other
Cause:
There were insufficient resources available to create the requested document (report, external query, PL/SQL library).
Action:
Make more resources available by closing windows or other applications.
REP-03200
Concurrent previewer actions are not allowed.
Category:
Other
Cause:
An attempt was made to activate more than one button at one time, in either the same or multiple Previewers. For example, play a sound and display a video at the same time.
Action:
Activate only one button at a time.
REP-03290
Query Builder does not support lexical parameters.
Category:
Other
Cause:
An attempt was made to pass lexical parameters to Query Builder, which is not supported. Query Builder only supports bind parameters.
Action:
Remove all lexical parameters from the query and reenter Query Builder.
REP-03300
A fatal error occurred: {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03301
An error occurred: {0}.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03302
A fatal error occurred during Quit. Exiting Oracle Reports Builder.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03335
An unhandled internal CA error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03350
An unhandled internal UI error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03351
An undefined failure in the UI occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03352
An unexpected error in the UI occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03353
The attribute cannot be created.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03354
The attribute cannot be set.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03355
The attribute cannot be set or retrieved.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03356
The unknown attribute cannot be set or retrieved.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03357
The attributes values are conflicting and cannot be set.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03358
The attribute cannot be set to an out of range value.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03359
This function call is out of context.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03360
The view class does not support being a scrollee.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03361
This function call provokes an illegal recursion.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03362
The internal API memory allocator failed.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03363
The client supplied memory allocation functions failed.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03364
An attempt to use an unsupported function failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03365
Attributes cannot be set out of context.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03366
An attempt to perform an illegal operation on a root view failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03367
One of the parameters to the functions is out of range.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03368
The connection to the windowing system failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03369
The connection to the windowing system is broken.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03370
The windowing system failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03371
uiER_CL_FORMAT_UNAVAILABLE
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03372
uiER_CL_FORMAT_UNREGISTERED
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03373
The operation timed out.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03374
uiER_NOT_FOUND
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03375
uiER_ILLEGAL_TOPITEM
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03376
uiER_SE_BAD_FORMAT
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03377
The view class does not support the scroller interface.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03378
An attempt to remove a readshare color from a palette failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03379
An attempt to create a window failed.
Category:
Other
Cause:
Oracle Reports Builder was unable to create a window. There may be too many reports or windows open, and lack of memory resources.
Action:
Close some reports and windows.
REP-03380
An attempt to create a view failed.
Category:
Other
Cause:
Oracle Reports Builder was unable to create a view. There may be too many reports or windows open, and lack of memory resources.
Action:
Close some reports and windows.
REP-03381
An attempt to create a color palette failed.
Category:
Other
Cause:
Oracle Reports Builder was unable to create a color palette. There may be too many reports or windows open, and lack of memory resources.
Action:
Close some reports and windows.
REP-03400
An error occurred initializing DE. Checking DE resources is recommended.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03420
An internal error occurred in Oracle Reports Builder.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03430
An unhandled internal HH error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03431
The attribute value is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03432
The context is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03433
The specified word cannot be found.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03434
A link to external document was found.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03435
The help session is null.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03436
The document is not a help document.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03437
The document revision is newer than help.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03438
The specified attribute is not settable.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03439
The specified attribute is not gettable.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03440
The link is invalid.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03441
Logical attributes are missing or bad.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03442
The NLS language string is missing or bad.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03443
No search string is specified.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03444
The string begins with a percent sign.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03445
An unknown toolkit error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03446
An unknown object store error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03447
An out of memory condition occurred.
Category:
Memory
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03448
An unknown Resource Manager error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03480
An unhandled internal REM error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03485
An unhandled internal VGS error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03500
An unhandled internal UT error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03510
An unhandled internal ZOM error occurred.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03600
Both document nodes and non-document nodes selected. Select only nodes from one of these types of nodes.
Category:
Other
Cause:
Navigator&gt;Delete was selected, but both object nodes and document nodes are selected. Documents cannot be closed and deleted in the same action.
Action:
To delete objects, deselect all document nodes. To close documents, deselect all object nodes. Then select Navigator&gt;Delete again.
REP-03601
This report style can only have one Section.
Category:
Other
Cause:
Tabular, Form Letter, and Mailing Label report styles have only one Section each.
Action:
Specify all overrides in the existing Section.
REP-03602
The minimum number of levels cannot be deleted.
Category:
Other
Cause:
Tabular, Form Letter, and Mailing Label report styles have one Section each. Group Above and Group Left report styles have two sections each. Matrix and Matrix Group have one section under each normal, across, and down cell.
Action:
Verify that the particular report style has the minimum number of levels.
REP-03700
Selection Observer initialization failed.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-03701
Selection Observer failed while shutting down.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-04001
An error occurred in the OLE subsystem.
Category:
Other
Cause:
An unspecified OLE2 error occurred during initialization. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: The OLE2 server is not functioning correctly. Case 2: An error occurred during installation of Oracle Reports Builder and the OLE2 functionality did not install correctly. Case 3: An abnormal condition was encountered.
Action:
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 Builder. If Case 3: For assistance, contact Oracle Support Services.
REP-04002
An error occurred while initializing OLE subsystem.
Category:
Other
Cause:
An error occurred during initialization of OLE2 libraries. Refer to the accompanying OLE error message for more information. Other possible causes of this error include the following: Case 1: The OLE2 server is not functioning correctly. Case 2: An error occurred during installation of Oracle Reports Builder and the OLE2 functionality did not install correctly. Case 3: An abnormal condition was encountered.
Action:
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 Builder. If Case 3: For assistance, contact Oracle Support Services.
REP-04003
An error occurred while creating OLE object.
Category:
Other
Cause:
An attempt was made to create an OLE2 object when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04004
An error occurred while restoring OLE object.
Category:
Other
Cause:
An attempt was made to restore an OLE2 object when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04005
An error occurred while saving OLE object.
Category:
Other
Cause:
An attempt was made to save an OLE2 object when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04006
An error occurred while performing a cut/copy operation. An OLE object is not placed in the clipboard.
Category:
Other
Cause:
An attempt was made to cut or copy an OLE2 object when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04007
An error occurred while pasting OLE object from clipboard.
Category:
Other
Cause:
An attempt was made to paste an OLE2 object from the clipboard when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04008
An error occurred while trying to perform operation defined by an OLE object.
Category:
Other
Cause:
An attempt was made to perform an action normally supported by the OLE2 server when an OLE error occurred.
Action:
Refer to the accompanying OLE error message for more information.
REP-04009
An error occurred while trying to activate an OLE object.
Category:
Other
Cause:
An attempt was made to activate an OLE2 object (for example, double-click on it in the Previewer) when an OLE error occurred.
Action:
Refer to the accompanying OLE2 error message for more information.
REP-04020
Conversion of OLE object to a different type failed.
Category:
Other
Cause:
An attempt was made to convert an OLE2 object contained in a piece of boilerplate to an OLE2 object of a different type when an OLE error occurred. This indicates a problem with the OLE2 server.
Action:
Check that the object is correctly installed and reinstall, if necessary.
REP-04021
Microsoft Object Linking and Embedding is not supported on this platform
Category:
Other
Cause:
An attempt was made to run a report that was created on a platform supporting OLE2, and created with OLE2 objects, on a platform that does not support OLE2.
Action:
No action is necessary. Remove the object if desired.
REP-04022
The incorrect version of OLE libraries are installed. OLE functionality will be disabled.
Category:
Other
Cause:
The OLE2 libraries installed are incompatible with those supported by the installed version of Oracle Reports Builder. As Oracle Reports Builder cannot guarantee that the OLE2 support will function, it disabled OLE2 functionality.
Action:
Install the correct libraries.
REP-04023
There is insufficient memory available to complete the operation.
Category:
Memory
Cause:
There is not sufficient memory remaining on the system to perform the desired action.
Action:
Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
REP-04024
DOS SHARE services are required for successful operation. SHARE is not running.
Category:
Other
Cause:
The DOS SHARE utility is required, but SHARE is not running.
Action:
Verify that SHARE is running.
REP-04025
A read failure occurred.
Category:
Other
Cause:
Data cannot be read from the specified device.
Action:
Check the device to determine if it is malfunctioning, and, if so, consult the device documentation to determine the proper error recovery procedures.
REP-04026
A write failure occurred.
Category:
Other
Cause:
Data cannot be written to the specified device.
Action:
Check the device to determine if it is read-only. If not, consult the device documentation to determine the proper error recovery procedures.
REP-04027
Too many files opened. There are insufficient resources to open another file.
Category:
Other
Cause:
An attempt was made to open more files than are supported by Windows.
Action:
Close some applications. Also, check the 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 there may be more files open than expected.
REP-04028
No space is left on the device.
Category:
Other
Cause:
The device is full.
Action:
Delete unnecessary data or write to a different device.
REP-04029
Presentation of the OLE object failed. Cannot render OLE object.
Category:
Other
Cause:
An attempt was made to display an OLE2 object in a report but the display aspects defined by the OLE2 server were unavailable.
Action:
Verify that the OLE2 object has not been corrupted and that the server is correctly installed. Reinstall if necessary.
REP-04030
Restoration of original display aspects of the OLE object failed. Object content will be used.
Category:
Other
Cause:
An attempt was made 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 Builder will display the object using the default aspect.
Action:
Verify that the OLE2 server is correctly installed. Reinstall if necessary.
REP-04031
The server application cannot be found.
Category:
Other
Cause:
An attempt was made to access an OLE2 server via an OLE2 object, but the server is currently inaccessible. The server may have been deleted, renamed, or manually reinstalled in a different location.
Action:
Check the installation of the server and reinstall if necessary.
REP-04032
Connection to the linked OLE object source failed.
Category:
Other
Cause:
Oracle Reports Builder is trying to connect to the specified source of the OLE2 object boilerplate but cannot.
Action:
Verify that the OLE2 object source has not been moved or deleted, and that its file name has not been changed.
REP-04033
Connection to the linked object source failed, because it is across a network that is not connected to this machine.
Category:
Network
Cause:
An attempt was made to link to an OLE2 object that is stored on a device to which there is no established network connection.
Action:
Establish a connection to the proper device.
REP-04034
A file cannot be not found or an invalid file name is used by an OLE object.
Category:
Other
Cause:
An OLE2 object is attempting to access a file that it cannot find.
Action:
Verify that the file has not been corrupted, moved, or renamed.
REP-04035
A share violation has occurred while performing operation on OLE object.
Category:
Other
Cause:
Possible causes: an attempt was made to link to the same file via multiple OLE2 objects, or to access the same temporary file via different applications.
Action:
Verify multiple OLE2 objects are not attempting to access the same file at the same time. Also, check the intallation of the OLE2 server.
REP-04036
Access was denied while performing an operation on an OLE object.
Category:
Other
Cause:
An attempt was made to update an OLE2 object without write access.
Action:
Obtain the proper permissions to the file before trying to update it.
REP-04037
File operation on OLE object failed because disk is write-protected.
Category:
Other
Cause:
An attempt was made to save to file an OLE2 object but it failed because the disk is write-protected.
Action:
Save the object to a disk with write privileges, if possible. If not, no action is necessary.
REP-04038
Unexpected error occurred in the file system while performing an operation on an OLE object.
Category:
Other
Cause:
A non-specific file error such as a corruption of the hard disk occurred.
Action:
Refer to the operating system documentation more information.
REP-04039
An unexpected error was returned by OLE.
Category:
Other
Cause:
A non-specific OLE error occurred.
Action:
Refer to the Microsoft documentation for more information.
REP-04040
Incorrect or corrupted OLE object persistent data was encountered. The OLE object cannot be restored from this data
Category:
Data
Cause:
The information used by the OLE server to restore the OLE2 object in the report is incorrect or has been corrupted. Possible causes for this error include: Case 1: If boilerplate, the file has become corrupted. Case 2: If field, either the database has been corrupted, or the LONG RAW column referenced does not contain OLE2 objects.
Action:
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 SQL*Plus to check the table in the database and verify the contents of the column.
REP-04041
No operations are defined on this object or the object is static.
Category:
Other
Cause:
An attempt was made to take some action on an OLE2 object but no actions have been defined as applying to the object. Possibly the object was converted to a static bitmap.
Action:
No action is necessary.
REP-04042
The requested action on the OLE object is valid, but cannot be performed at this moment. The object server may be busy.
Category:
Other
Cause:
An attempt to take a valid action on an OLE2 object failed, due to lack of server resources. A possible cause is that an attempt was made to open a second instance of a single-instance application.
Action:
Check system resources (such as memory) and increase where possible, or try the operation later.
REP-04043
The operation requested on the object is invalid and cannot be performed.
Category:
Other
Cause:
The action attempted on an OLE2 object was not recognized as valid.
Action:
Verify that the proper version of the OLE server is correctly installed. Reinstall if necessary.
REP-04044
The system registry cannot be accessed.
Category:
Other
Cause:
A read or write operation in the system registry failed.
Action:
Verify that there are enough free system resources and the registry is not corrupted. Consult the Microsoft documentation.
REP-04045
A problem occurred in the system registry.
Category:
Other
Cause:
Some information about the server is missing from the registry.
Action:
Verify that the OLE server is installed correctly. Reinstall if necessary.
REP-04100
An attempt to execute data source failed.
Category:
Data
Cause:
An internal error occurred while executing the specific pluggable data source.
Action:
Look for more details in the engine trace.
REP-04101
An attempt to create conditions for pluggable data source failed.
Category:
Data
Cause:
An internal error occurred while creating conditions for the specific pluggable data source.
Action:
Look for more details in the engine trace in case of a custom PDS.
REP-04102
An attempt to fetch pluggable data source failed.
Category:
Data
Cause:
An internal error occurred when fetching the resultset of the pluggable data source.
Action:
Look for more details in the engine trace in case of a custom PDS.
REP-04103
An attempt to set up pluggable data source driver failed.
Category:
Data
Cause:
An internal error occurred.
Action:
Verify the installation. For assistance, contact Oracle Support Services.
REP-04104
Pluggable data source {0} references unknown column {1}
Category:
Data
Cause:
An invalid column is being referenced in the pluggable data source query.
Action:
Verify the PDS query.
REP-04105
An attempt to create pluggable data source factory {0} failed.
Category:
Data
Cause:
The pluggable data source factory class specification in the preference file is invalid.
Action:
Validate the specification of pluggable data source factory classes in the preference file.
REP-04106
An attempt to edit the query failied because it was created with a later version ({0}) of pluggable data source factory {1}.
Category:
Data
Cause:
Query was created with a later version of pluggable data source factory than the current Builder session's registered factory. For this to occur, the major version of the factories must be different. Major version is the value left of the decimal point in the factory version number.
Action:
Upgrade the registered Oracle Reports Builder pluggable data source factory to one with the equivalent major version number.
REP-04107
The query will be upgraded from version {0} to current factory version {1}.
Category:
Other
Cause:
The query was created with an earlier version of pluggable data source factory than the current Builder session's registered factory. For this to occur, the major version of the factories must be different. Major version is the value left of the decimal point in the factory version number.
Action:
No action is necessary. The query will be automatically upgraded to the version number of the current factory.
REP-04108
The version of the query {0} is different from the pluggable data source factory {1}.
Category:
Data
Cause:
The query was created with version of pluggable data source factory that is slightly different than the current Builder session's registered factory. For this to occur, the minor version of the factories must be different. Minor version is the value right of the decimal point in the factory version number.
Action:
No action is necessary. The Edit operation will proceed.
REP-04109
Factory {0} is not a registered factory class.
Category:
Other
Cause:
The factory class may not be specified correctly in the preference file.
Action:
Verify that the factory class is specified correctly in the preference file.
REP-04110
Query definition for query {0} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not connect to the data source referred in the query.
Action:
Check the connection information for the PDS query.
REP-04111
Pluggable data source {0} cannot be created.
Category:
Data
Cause:
Case 1: There is no JVM. Case 2: There is no Oracle Reports pluggable data source driver. Case 3: Pluggable data source class failed to return new pluggable data source object.
Action:
In Case 1: Check the Oracle Reports and Java installation on the machine. In Case 2: Check if the correct Oracle Reports jar file is in the right place. In Case 3: Check if the right pluggable data source class is in place.
REP-04112
Oracle Reports Builder can not display the image for pluggable data source {0}.
Category:
Data
Cause:
The bitmap image may be corrupted.
Action:
Verify that the bitmap image is not corrupted by confirming that it is saved in .gif format and it can be viewed in the appropriate image tool.
REP-04113
Changing the type of pluggable data source bound to this parameter may affect query behavior in the Data Model.
Category:
Data
Cause:
An attempt was made to change a query of one PDS type to another.
Action:
Verify any parameters used in the query when changing PDS type.
REP-04200
An error occurred in the Mail subsystem.
Category:
Other
Cause:
An unspecified error occurred during one of the mail operations. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: MAPI is not properly installed. Case 2: The Windows mail service provider is not properly installed.
Action:
Take the following actions to correct this error: If Case 1: For other applications using MAPI, check to see if they are functioning properly. If not, try reinstalling MAPI. If Case 2: Verify that the Windows mail service provider is installed, and a mail account exists on the system. For assistance, ask the mail administrator.
REP-04201
An error occurred while initializing the Mail subsystem.
Category:
Other
Cause:
Oracle Reports Builder tried to initialize MAPI, and could not. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: MAPI is not installed, the MAPI DLL is out of date, or the Mail entry in the WIN.INI file or registry points to the wrong location. Case 2: There is not enough memory available to perform the operation. Case 3: While logging on, an invalid service profile name, username, or password was entered.
Action:
Take the following actions to correct this error: If Case 1: Reinstall MAPI, or correct the Mail entry in the WIN.INI file or registry. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage. If Case 3: Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator.
REP-04202
An error occurred while logging on to the Mail subsystem.
Category:
Logging
Cause:
An attempt was made to log on to the Mail subsystem and an error occurred. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: An invalid service profile name, username, or password was entered. Case 2: There is not enough memory available.
Action:
Take the following actions to correct this error: If Case 1: Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
REP-04203
An error occurred while sending a mail message.
Category:
Other
Cause:
An error occurred while composing or sending a mail message. Refer to the accompanying error message for more information. Other possible causes of this error include the following: Case 1: There is not enough free space on the disk. Case 2: There is not enough memory available.
Action:
Take the following actions to correct this error: If Case 1: Free up some space on the disk. If Case 2: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
REP-04204
An error occurred while trying to validate recipient's name or address.
Category:
Other
Cause:
Oracle Reports Builder tried to validate the destination mail address, and an error occurred.
Action:
Confirm that the recipient has a valid mail account, or ask the mail administrator for assistance. Refer to the accompanying error message for more information.
REP-04220
There is a problem with the Mail subsystem.
Category:
Other
Cause:
An unspecified error occurred during one of the mail operations.
Action:
Try to free up some disk space or exit any unnecessary applications that are running. If other applications are using MAPI, check to see if they are functioning properly. If not, try reinstalling MAPI.
REP-04221
An attachment file cannot be accessed.
Category:
Other
Cause:
An error occurred while trying to access attachment file. Possible causes of this error include the following: Case 1: The attachment file cannot be found. Case 2: The attachment file could not be opened, or there was an error reading or writing it.
Action:
Take the following actions to correct this error: If Case 1: Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage. If Case 2: Free up some space on the disk.
REP-04222
There is insufficient memory to complete the operation.
Category:
Memory
Cause:
The mail operation cannot be completed, because there is not enough memory available.
Action:
Exit any unnecessary applications that are running. If that does not work, see the Microsoft documentation for suggested procedures to enhance memory usage.
REP-04223
No space is left on the device.
Category:
Other
Cause:
The mail operation cannot be completed because there is not enough free space available on the disk.
Action:
Free up some space on the disk.
REP-04224
The user name, password, or service profile name is incorrect.
Category:
Other
Cause:
The logon information entered is invalid.
Action:
Verify that the logon information is correct, and try again. If that does not work, confirm the account information with the mail administrator.
REP-04225
The operation cannot be completed because the user is not logged on.
Category:
Other
Cause:
The mail operation could not be completed.
Action:
Log on to the Mail subsystem, and try again.
REP-04226
A password is required.
Category:
Other
Cause:
An attempt was made to log on to the Mail subsystem without specifying a password.
Action:
Specify a valid password, and try again. If that does not work, contact the mail administrator.
REP-04227
The service configuration is invalid.
Category:
Configuration
Cause:
The Mail subsystem is incorrectly configured.
Action:
Contact the mail administrator.
REP-04228
MAPI does not support the service requested by Oracle Reports Builder.
Category:
Other
Cause:
The given implementation of MAPI has limited functionality.
Action:
Consider upgrading the Windows mail service provider. Contact the mail administrator.
REP-04229
The character set requested is not supported.
Category:
Other
Cause:
The default character set is not supported by MAPI.
Action:
Contact the mail administrator.
REP-04230
The size of the text string passed is too large.
Category:
Other
Cause:
The text string passed is too large for the given implementation of MAPI.
Action:
Shorten the string, and try again.
REP-04232
Too many files are opened.
Category:
Other
Cause:
The given implementation of MAPI does not support the number of files open.
Action:
Close all unnecessary documents.
REP-06004
Oracle Reports Builder failed to connect to the specified Express server.
Category:
Other
Cause:
Express server is not running.
Action:
Verify that Express server is running.
REP-06006
The Express initialization file, XPDATA.INI, cannot be found.
Category:
Other
Cause:
The Express initialization file, XPDATA.INI, was not found.
Action:
Check the existence and path of the XPDATA.INI file.
REP-06007
The Express connection file (XCF) entry cannot be found in the [Install] section of the Express initialization file, XPDATA.INI.
Category:
Other
Cause:
The Express connection file (XCF) entry was not found in the [Install] section of the Express initialization file, XPDATA.INI.
Action:
Add an XCF entry to XPDATA.INI file, or replace with a valid XPDATA.INI.
REP-06008
The path specified in ORACLE_HOME cannot be found.
Category:
Other
Cause:
The path specified in the the ORACLE_HOME variable was not found.
Action:
Check the ORACLE_HOME setting.
REP-06009
The Oracle SNAPI (OSN) entry cannot be found in the [Install] section of the Express initialization file, XPDATA.INI.
Category:
Other
Cause:
The Oracle SNAPI (OSN) entry was not found in the [Install] section of the Express initialization file, XPDATA.INI.
Action:
Add an OSN entry to XPDATA.INI, or replace with a valid XPDATA.INI.
REP-06010
The Express server description cannot be found in any Express connection files (XCFs).
Category:
Other
Cause:
The Express server description was not found in any Express connection files (XCFs).
Action:
Check the XCF files.
REP-06011
The size of the generated SQL SELECT statement exceeds the 64K limit.
Category:
Other
Cause:
The size of the generated SQL SELECT statement exceeds the 64K limit.
Action:
Modify the query to reduce the size of the SQL statement.
REP-06013
A query failed to run. The Express Query Dialog was invoked with a set of measures/dimensions from a previous query
Category:
Other
Cause:
The Express Query Dialog was invoked with a set of measures/dimensions from a previous query.
Action:
Reexamine the measures/dimensions in the query.
REP-06014
The report ID was not defined when calling the backend XPFetch[N().
Category:
Other
Cause:
The report ID was not defined before calling the backend XPFetch().
Action:
Define the report ID and resubmit the call to the backend XPFetch().
REP-06015
A duplicate report ID was used when calling the backend XPPrepare().
Category:
Other
Cause:
A duplicate report ID was used when the backend XPPrepare() was called.
Action:
Select a unique report ID and resubmit the call to the backend XPPrepare().
REP-06017
The saved query contained incorrect or missing information.
Category:
Other
Cause:
When the query was saved, it contained incorrect or missing information.
Action:
Check the query and correct the information or supply the missing information and try again.
REP-06018
The internal Oracle Express system databases were not attached.
Category:
Other
Cause:
The internal Oracle Express system databases were not attached.
Action:
Attach the internal Oracle Express system databases and try again.
REP-06019
The Oracle Express database specified in the saved query was not attached.
Category:
Other
Cause:
The Oracle Express database that was specified in the saved query was not attached.
Action:
Attach the specified Oracle Express database to the saved query and try again.
REP-06021
The Oracle Express support was not installed.
Category:
Other
Cause:
The Oracle Express support was not installed.
Action:
Install the Oracle Express support and try again.
REP-06023
An unexpected end-of-line was received while parsing the Oracle Express query.
Category:
Other
Cause:
The Oracle Express query might be missing the \s at the end of the line.
Action:
Check the Oracle Express query for a missing \s at the end of the line, add it, and try again.
REP-06026
A duplicate report ID was detected.
Category:
Other
Cause:
A duplicate report ID was used.
Action:
Select a unique report ID and try again.
REP-06027
An undefined report ID was detected.
Category:
Other
Cause:
The report ID that was used has not yet been defined.
Action:
Define the report ID and try again.
REP-06030
The XCONNECT.INI file was missing or was invalid.
Category:
Other
Cause:
This message probably occurred as the result of a missing XCONNECT.INI file. If the XCONNECT.INI file is not missing, then it probably has an invalid General section.
Action:
Check in ORACLE_HOME/OLAP/ECF620 to ensure that the XCONNECT.INI file is there. If not, then add it. If the XCONNECT.INI file is there, verify that it has a valid General section.
REP-06031
This report contains Oracle Express queries that are 6i versions. Convert these queries?
Category:
Other
Cause:
An older version of Oracle Express queries cannot be edited or run with the current version of Oracle Express.
Action:
Reply YES to converting the older version of Oracle Express queries to the newer version of Oracle Express. The queries will be automatically converted.
REP-06032
The Oracle Express query {0} failed to convert.
Category:
Other
Cause:
This error message could have occurred for one of the following reasons: Case 1: The Oracle Express 6i query was corrupted. Case 2: The Oracle Express pluggable data source malfunctioned.
Action:
Take the following actions to correct this error: If Case 1: Ensure that the query is not corrupted by editing and rerunning it in the OracleAS Reports Services environment. If Case 2: For assistance, contact Oracle Support Services.
REP-06033
This operation requires converting the {0} Oracle Express query to the newer version of Oracle Express. Proceed with this conversion?
Category:
Other
Cause:
Older versions of Oracle Express queries cannot be edited or run with the current version of Oracle Express.
Action:
Accept the conversion by replying YES to the conversion. The queries will be automatically converted.
REP-06051
The Oracle Portal connection failed.
Category:
Other
Cause:
The database server might be down or the user ID and password authentication failed.
Action:
Check that the database server is available, verify that the user ID and password are correct and try again.
REP-06052
The database requested does not contain a valid Oracle Portal definition.
Category:
Other
Cause:
This error might have occurred for one of the following reasons: Case 1: The database is not a valid version for the Oracle Portal installation. Case 2: The logged in user does not have permission to read the component definition tables.
Action:
Take the following actions to correct this error: If Case 1: Select a valid database for the Oracle Portal installation. If Case 2: Obtain permissions for the logged in user to read the component definition tables.
REP-06053
There are no components in Oracle Portal that can be imported.
Category:
Other
Cause:
This is an information only message notifying that there are no components available to be imported.
Action:
No action is necessary.
REP-06054
The requested template cannot be found.
Category:
Other
Cause:
This can occur for one of the following reasons: Case 1: The REPORTS_XSL_TEMPLATE environment variable was incorrectly edited. Case 2: The template XSL file was removed from the location where it is supposed to be located.
Action:
Take the following actions to correct this error: If Case 1: Correct the REPORTS_XSL_TEMPLATE and continue. If Case 2: Ensure the template XSL file is in the proper location and continue.
REP-06055
A template error occurred.
Category:
Other
Cause:
The XSL template file was not a well-formed template.
Action:
Verify that the XSL template file is correct. If it is, then the best solution is to restore the original one. Experienced users can edit the file to correct the problems.
REP-06056
A temporary directory was invalid.
Category:
Other
Cause:
The transformation process requires a temporary directory to write a temporary file. The temporary directory might not exist or it might not allow a temporary file to be written to it.
Action:
Look at the REPORTS_TMP environment variable and ensure that it corresponds to an existing, writable temporary directory.
REP-06057
A portal component has not been selected.
Category:
Other
Cause:
OK was clicked without selecting a portal component.
Action:
Select a portal componet or click Cancel.
REP-06058
Database client library error.
Category:
Other
Cause:
Oracle Reports cannot connect to the portal database because of a JDBC error. A common cause is a version mismatch of a database client library in the path.
Action:
Verify that the Oracle Reports bin directory is listed in the path search order before any other ORACLE_HOME/bin or other directory that could have a database client. If this does not solve the problem, check the Java classpath and verify that the correct version of the JDBC library is listed before any other library.
REP-06101
The Java Virtual Machine failed to start. Check the Java Runtime Environment setup. {0}:{1}.
Category:
Other
Cause:
The Java runtime environment in the installation is not valid.
Action:
Verify that the installation is correct. Reinstall if necessary.
REP-06102
The XML parser failed to start.
Category:
Other
Cause:
The XML parser jar files are missing in the installation.
Action:
Verify that the Oracle Fusion Middleware installation is correct. Reinstall if necessary.
REP-06103
An error occurred with the Java Runtime Environment setup.
Category:
Other
Cause:
The Java runtime environment in the installation is not valid.
Action:
Verify that the installation is correct. Reinstall if necessary.
REP-06104
The XML report definition is invalid.
Category:
Other
Cause:
The report definition is invalid.
Action:
Verify the XML report definition.
REP-06105
An error occurred in the XML report definition at line {0}.
Category:
Other
Cause:
The report definition is invalid.
Action:
Verify the XML report definition.
REP-06106
An error occurred in the XML report definition at line {0} in {1}.
Category:
Other
Cause:
The report definition is invalid.
Action:
Verify the XML report definition.
REP-06107
The URL for the XML report definition is invalid: {0}.
Category:
Other
Cause:
The report definition is invalid.
Action:
Verify the URL location / XML report definition.
REP-06108
The XML report definition cannot be applied.
Category:
Other
Cause:
This is an internal error.
Action:
For assistance, contact Oracle Support Services.
REP-06109
The report definition file {0} cannot be saved.
Category:
Other
Cause:
This is an internal error.
Action:
For assistance, contact Oracle Support Services.
REP-06110
The query {0} cannot be created.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06111
The query {0} cannot be modified.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06112
The column {0} cannot be created.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06113
The column {0} cannot be modified.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06114
The data link {0} cannot be created.
Category:
Data
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06115
The data link {0}cannot be modified.
Category:
Data
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06116
The field {0} cannot be created.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06117
The field {0} cannot be modified.
Category:
Other
Cause:
The PDS query is invalid.
Action:
Look into the trace information for more details in case of a custom PDS.
REP-06118
The layout for {0} cannot be defaulted.
Category:
Other
Cause:
This is an internal error.
Action:
Contact Oracle Support Services if the problem persists.
REP-06119
Format exception {0} for the field {1} cannot be created.
Category:
Other
Cause:
This is an internal error.
Action:
Contact Oracle Support Services if the problem persists.
REP-06120
Condition {0} in the format exception {1} for the field {2} is invalid.
Category:
Other
Cause:
This is an internal error.
Action:
Contact Oracle Support Services if the problem persists.
REP-06121
The specified layout style {0} is invalid.
Category:
Other
Cause:
An attempt was made to use an invalid layout style.
Action:
Verify the layout style for the report.
REP-06122
The specified layout style {0} in {1} is invalid.
Category:
Other
Cause:
An attempt was made to use invalid layout style.
Action:
Verify the layout style for the report.
REP-06123
Source {0} for field {1} is invalid.
Category:
Other
Cause:
The value used for the field is invalid.
Action:
Verify the value.
REP-06124
A PL/SQL compilation error occurred in {0}.
Category:
Other
Cause:
The PL/SQL procedure is invalid.
Action:
Verify the PL/SQL procedure.
REP-06200
Reports tag library directive cannot be found: {0} in report file
Category:
Other
Cause:
Reports was unable to locate the expected JSP taglib directive in the user supplied report file.
Action:
All Web-based reports must contain the tag library directive. Open any demo .JSP file and copy the taglib lines into the report.
REP-06201
Prefix attribute {0} in report file cannot be found.
Category:
Other
Cause:
The file does not contain an rw:objects tag. The tag library directive does not contain the correct prefix attribute or is otherwise corrupted.
Action:
The rw:objects tag supplies data for report blocks and charts. If this tag is not required in the file then this message can be ignored. If data is required, use the data wizard to add a data model to the report. Open any demo .jsp file and replace the taglib lines in the report with the lines from the demo file.
REP-06202
A rw:report tag in the template file cannot be found.
Category:
Other
Cause:
The file contains a taglib directive but does not contain a rw:report tag.
Action:
The template file can still be used but the rw:report tag must be added to a report before a data model can be added.
REP-06203
Template file cannot be parsed.
Category:
Other
Cause:
Reports was unable to parse the indicated file. Any attempt to execute the report will not run.
Action:
Check the JSP syntax against the documentation in the Help system.
REP-06204
The <rw:objects> tag cannot be found. Save operation aborted
Category:
Other
Cause:
The &lt;rw:objects&gt; tag was missing or invalid JSP syntax was found within the document.
Action:
Check the JSP syntax against the documentation in the Help system.
REP-06205
The ID attribute of tag {0} is not unique.
Category:
Other
Cause:
The report contains duplicate JSP ID attributes.
Action:
JSP ID attributes must be unique within a page. Change the ID of the tags that are not unique.
REP-06206
Tag {0} must be inside the rw:report tag.
Category:
Other
Cause:
A Reports JSP tag is outside the rw:report tag.
Action:
All Reports JSP tags must be inside the rw:report tag. Move the tag inside the rw:report tag. The easiest way to prevent this error is to move the &lt;/rw:report&gt; tag to the bottom of the page.
REP-06207
Tag {0} tag has an invalid scope.
Category:
Other
Cause:
A Reports JSP tag is outside of the correct context.
Action:
Move the tag to its correct scope.
REP-06208
More than one rw:report tag is found. A report page can have only one rw:report tag.
Category:
Other
Cause:
The report contains more than one set of rw:report tags.
Action:
Add &lt;rw:report&gt; after the taglib lines at the top of the page. Add &lt;/rw:report&gt; at the bottom of the page. Remove the extra rw:report tags.
REP-06209
Required Reports JSP tags are missing. The required Reports JPS tags have been added to the saved file.
Category:
Other
Cause:
When saving the JSP file, required Reports JSP tags were not found.
Action:
Click OK to add the required tags and save the file. Click Cancel to prevent Oracle Reports Builder from adding the tags, and not save the file.
REP-06210
Required Reports JSP tags are being added to the file.
Category:
Other
Cause:
If the file does not contain the required Reports JSP tags when it is first opened, Oracle Reports Builder adds the Reports JSP tags to the file loaded in memory. The original file on disk is not touched.
Action:
Click OK to continue working on the file.
REP-06211
The graph XML definition cannot be parsed.
Category:
Other
Cause:
Oracle Reports was unable to parse the XML definition of the graph.
Action:
Check the graph XML DTD against the Oracle BI Beans documentation.
REP-06212
The graph definition cannot be parsed.
Category:
Other
Cause:
Oracle Reports was unable to parse the definition of the graph.
Action:
Check the graph tag against the reports.tld.
REP-06213
A report level cursor cannot be created.
Category:
Other
Cause:
An internal error occurred when creating the report level cursor.
Action:
Contact Oracle Support Services if the problem persists.
REP-06214
A group cursor cannot be created.
Category:
Other
Cause:
An internal error occurred when creating the group cursor.
Action:
Contact Oracle Support Services if the problem persists.
REP-06215
An error occurred retrieving the next row from the cursor.
Category:
Other
Cause:
An internal error occurred when moving the group cursor to the next row.
Action:
Contact Oracle Support Services if the problem persists.
REP-06216
Unable to create related cursor
Category:
Other
Cause:
An internal error occurred when creating the related group cursor.
Action:
Contact Oracle Support Services if the problem persists.
REP-06217
No source specified for cursor
Category:
Other
Cause:
An internal error occurred. The cursor's source (that is, report for report level cursor, group for group cursor) is not specified.
Action:
Contact Oracle Support Services if the problem persists.
REP-06218
Value of unknown column {0} cannot be retrieved.
Category:
Other
Cause:
The column name is invalid.
Action:
Provide a valid column name.
REP-06219
Column {0} is not in the given cursor hierarchy.
Category:
Other
Cause:
The column does not belong to the cursor provided.
Action:
Modify the report so that the column belongs to given cursor hierarchy.
REP-06220
Value of column cannot be retrieved.
Category:
Other
Cause:
An internal error occurred when getting the value of the column.
Action:
Contact Oracle Support Services if the problem persists.
REP-06221
Column {0} cannot be found.
Category:
Other
Cause:
An internal error occurred when looking for a column.
Action:
Contact Oracle Support Services if the problem persists.
REP-06222
The column in the given cursor cannot be found.
Category:
Other
Cause:
The column does not belong to the cursor provided.
Action:
Modify the report so that column belongs to the given cursor.
REP-06223
Attempt to determine which cursor a column belongs to failed.
Category:
Other
Cause:
An internal error occurred when trying to find out to which cursor a column belongs, among a given list of cursors.
Action:
Contact Oracle Support Services if the problem persists.
REP-16500
This program can only be invoked as a CGI executable.
Category:
Other
Cause:
The Web CGI executable was invoked outside the Web Server context.
Action:
The CGI executable must be invoked by a Web server to work properly.
REP-16501
The Reports Web Agent key map file was not set up properly.
Category:
Other
Cause:
The key map file cannot be found at the location specified.
Action:
Check the file location.
REP-16504
The message subsystem cannot be initialized.
Category:
Other
Cause:
The Oracle Reports message file cannot be found or opened.
Action:
Check the installation. Verify that the Oracle Reports message file was installed properly.
REP-16505
A general error occurred during initialization.
Category:
Other
Cause:
A general error occurred.
Action:
Check the installation and availability of system resources.
REP-16506
The URL contains badly-formed escapes.
Category:
Other
Cause:
The submitted URL is badly formed.
Action:
See the URL rules in the Web Agent documentation.
REP-16507
The key is unrecognized.
Category:
Other
Cause:
The key map configuration is active, but the specified key in the URL is unrecognized, and the command line cannot be built.
Action:
Check the key value and keymap file setup and contents.
REP-16508
Key %s is unrecognized.
Category:
Other
Cause:
The key map configuration is active, but the specified key in the URL is unrecognized, and the command line cannot be built. This error may be due to bad URL syntax, or the key in the URL was not found in the key map file.
Action:
Check the key value and keymap file setup and contents.
REP-16509
Syntax errors are found in the key map file.
Category:
Other
Cause:
Syntax errors occurred in the key map file.
Action:
Check the key map file contents (see Web Agent documentation for rules). Check a definition of submitted key.
REP-16510
Usage in incorrect.
Category:
Other
Cause:
This is a generic error for a non-verbose run.
Action:
Enable verbocity and check the real message.
REP-16511
The URL contains too many parameters.
Category:
Other
Cause:
The URL contains too many parameters (it is too long).
Action:
Use a shorter URL or the key map file to shorten the URL.
REP-16512
out of memory
Category:
Memory
Cause:
There is not enough memory to perform the operation.
Action:
Verify that enough system resources are available.
REP-16513
Communication with the Reports Server is lost.
Category:
Other
Cause:
Reports Server is not answering.
Action:
Verify that Reports Server is up and the tnsnames.ora network setup has a correct entry for it.
REP-16514
The report cannot be run.
Category:
Other
Cause:
This is a generic error for a report run failure.
Action:
See the detailed error message from Reports Server.
REP-16515
The report output cannot be accessed.
Category:
Other
Cause:
The Web Agent cannot access Reports Server run output.
Action:
Check the Web Agent setup (especially WEBLOC variable).
REP-16516
The Reports Server is being shut down.
Category:
Other
Cause:
Reports Server is going down.
Action:
Try again later.
REP-16517
The Oracle Reports job is canceled upon user request.
Category:
Other
Cause:
The Oracle Reports job was canceled.
Action:
Try again if necessary.
REP-16518
The Reports Engine terminated abnormally.
Category:
Other
Cause:
The Reports Engine had problem with the report.
Action:
Contact the Reports Server administrator.
REP-16519
The Oracle Reports job has terminated with an error.
Category:
Other
Cause:
This is a generic error message for report run error.
Action:
See the detailed error message from Reports Server.
REP-16520
An error occurred while queuing a job to Reports Server.
Category:
Other
Cause:
An error occurred while enqueing report to run.
Action:
Try again later.
REP-16521
An error occurred while parsing the Reports Server command line.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator.
REP-16522
The Reports Server name is not specified.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the command line for a server name.
REP-16523
A report name is not specified.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the command line for a report name.
REP-16524
A database logon is not specified.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the command line for database logon.
REP-16525
The scheduling command cannot be interpreted.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the SCHEDULE parameter.
REP-16526
The time tolerance cannot be interpreted.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the TOLERANCE parameter.
REP-16527
The Parameter Form type is invalid.
Category:
Other
Cause:
An error occurred while attempting to run a report and process a command line.
Action:
Contact the Reports Server administrator. Check the PARAMFORM parameter.
REP-16528
An error occurred while communicating with the Reports Server.
Category:
Other
Cause:
A communication problem occurred.
Action:
Try again later.
REP-16529
The job cannot be killed.
Category:
Other
Cause:
This is a generic message for job kill failure.
Action:
Investigate why the job cannot be killed.
REP-16530
The job ID is invalid.
Category:
Other
Cause:
The ID of the Reports Server job is invalid.
Action:
Verify the ID.
REP-16531
The job is already finished.
Category:
Other
Cause:
The ID of the Reports Server job is invalid.
Action:
Verify the ID.
REP-16532
The job is not done yet. Try again later.
Category:
Other
Cause:
The ID of the Reports Server job is invalid.
Action:
Verify the ID.
REP-16533
There are insufficient privileges to perform the requested action.
Category:
Other
Cause:
The ID of the Reports Server job is invalid.
Action:
Verify the ID and privileges.
REP-16534
Report output cannot be accessed.
Category:
Other
Cause:
The Oracle Reports output directory is not accessible.
Action:
Check the directory specification and the setup (REPORTS_WEBLOC or REPORTS_WEBLOC_TRANSLATED environment is probably invalid).
REP-16535
Report output cannot be accessed.
Category:
Other
Cause:
The Oracle Reports output directory is not accessible.
Action:
Check the directory specification and the setup (REPORTS_WEBLOC or REPORTS_WEBLOC_TRANSLATED environment is probably invalid).
REP-16537
Report output cannot be saved.
Category:
Other
Cause:
Report output of the returned name already exists in the Web directory.
Action:
Check the Web Agent setup (REPORTS_WEBLOC_TRANSLATED environment probably points to the same location as a Reports Server cache).
REP-16538
Report output was successfully printed.
Category:
Other
Cause:
The report was successfully run to the printer.
Action:
No action is needed.
REP-16539
Report output was successfully mailed.
Category:
Other
Cause:
The report was successfully run to mail.
Action:
No action is needed.
REP-16540
Report output was successfully written to the requested destination.
Category:
Other
Cause:
The report was successfully run to the requested destype.
Action:
No action is needed.
REP-16541
Log on before running the report.
Category:
Other
Cause:
It is necessary to log on before running the report.
Action:
Log on again.
REP-16542
Report output was successfully written to the InterOffice repository.
Category:
Other
Cause:
The report was successfully run to the InterOffice repository.
Action:
No action is needed.
REP-16543
The report output cannot be accessed.
Category:
Other
Cause:
The Oracle Reports output directory is not accessible.
Action:
Check the directory specification. Check the setup (REPORTS_VIRTUAL_MAP, REPORTS_PHYSICAL_MAP and REPORTS_SHARED_CACHE environment is probably invalid.)
REP-16544
The report output cannot be accessed.
Category:
Other
Cause:
The Oracle Reports output directory is not accessible.
Action:
Check directory specification. Check the setup (REPORTS_VIRTUAL_MAP, REPORTS_PHYSICAL_MAP and REPORTS_SHARED_CACHE environment is probably invalid.)
REP-20091
Save the current document before disconnecting from the database?
Category:
Other
Cause:
An open document is stored in the database. If disconnected from the database, changes cannot be saved to the database.
Action:
Select Yes to save the document before disconnecting from the database; the document remains open to reconnect if desired and save it to the database again. Select No to disconnect from the database without saving the document; the document remains open. Select Cancel to remain connected to the database without saving; once again, the document remains open.
REP-20099
Printer changed while previewing. Printer font remapping could cause truncation. Continue with printing?
Category:
Other
Cause:
In the time between running the report and selecting Print from the Previewer, the default printer has changed.
Action:
Select Yes to print anyway. Select No to halt printing, then close the report and either reset the printer and run the report again, or simply run it again to format it for the current printer.
REP-20128
The report was not run with DESTYPE=PREVIEW. Screen font remapping could cause truncation. Continue with printing?
Category:
Other
Cause:
Print was selected from the Previewer, but specified Screen instead of Preview, which formats the report as though using printer fonts and provides a more accurate view of the report's printed output.
Action:
Select Yes to print anyway. Select No to halt printing. Then close the report and run it again while specifying Preview to format it for the printer.
REP-20129
Opening a report saved with a newer version of Oracle Reports Builder. Functionality may be lost. Continue?
Category:
Other
Cause:
An attempt was made to open a report with a version of Oracle Reports Builder older than the version used to create the report. If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.
Action:
To avoid losing functionality, do not open the report until after upgrading to the most recent version of Oracle Reports Builder.
REP-20135
A layout does not exist. Create a default layout?
Category:
Other
Cause:
An attempt was made to run the report after creating a data model but before creating a layout.
Action:
Select Yes to create a default layout using the Report Wizard. Select No to run the report without a layout.
REP-20136
The region chosen for the default layout is too small. Extend the region to page boundaries?
Category:
Other
Cause:
The Report Block tool was used to draw a region for a layout that was not large enough to accommodate the settings specified in the Report Block Wizard.
Action:
Select Yes to have Oracle Reports Builder extend the possible range of the layout to the boundaries of a report page, or select No and change the settings in the Report Block Wizard to shrink the size of the layout.
REP-20138
Oracle Reports Builder tables may not be installed in the database.
Category:
Other
Cause:
Oracle Reports Builder was not able to access its tables in the database.
Action:
Inform the database administrator that the Oracle Reports Builder tables were not successfully installed in the database.
REP-20139
New Parameter Form layout will not fit its current size. Increase the number of pages to fit?
Category:
Other
Cause:
The new Parameter Form is too big to fit on the number of pages specified for the Parameter Form in the Report Properties dialog box.
Action:
Either select Yes to have Oracle Reports Builder increase the number of pages in the Parameter Form, or select No and change the settings in the Report Properties dialog to enlarge the Parameter Form.
REP-20144
Opening a report saved with a newer version of Oracle Reports Builder. Functionality may be lost.
Category:
Other
Cause:
An attempt was made to open a report with a version of Oracle Reports Builder older than the version used to create the report. If the report uses functionality unavailable in the older version, that functionality will be eliminated from the report.
Action:
To avoid losing functionality, do not open the report until after upgrading to the most recent version of Oracle Reports Builder.
REP-20146
This action may invalidate references to columns in the referenced object.
Category:
Other
Cause:
Collapsing a Database Ref, Database Nested Table, or Database Varray column invalidates any external use of the referenced columns. for example, in PL/SQl Program Units or in Summary Columns.
Action:
To use the referenced columns, do not collapse the Database Ref, Database Nested Table, or Database Varray columns referencing them.
REP-20147
A column link for this detail SQL query cannot be implemented. Converting to group link.
Category:
Other
Cause:
Oracle Reports Builder can only insert column to column links into supported SQL. It defaults to a group to group link in this case.
Action:
Manually insert the required link clause into the detail SQL query.
REP-20150
Page width of report {0} was changed to fit the font for a character cell as a consequence of font-mapping.
Category:
Other
Cause:
A character font has been substituted for a bitmapped font in the report, and the page width has been adjusted accordingly. A possible cause: a bitmapped report is being opened in the character-mode runtime engine.
Action:
To map the font to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on the platform) to map the fonts to the desired ones. Otherwise, no action is necessary.
REP-20151
Some fonts have been changed according to the mapping in the font aliases file.
Category:
Other
Cause:
One or more fonts saved with the report have been mapped to different ones, due to a change in platform, display, report destination, or mode.
Action:
To map the font to a specific font, edit the font alias file (uifont.ali or Oracle Font Aliases, depending on the platform) to map the fonts to the desired ones. Otherwise, no action is necessary.
REP-20160
An AutoRecovery file was detected. Recover unsaved changes for {0}?
Category:
Other
Cause:
Oracle Reports Builder can automatically recover unsaved report changes if it stops responding or there is a power failure.
Action:
Either select Yes to have Oracle Reports Builder recover unsaved report changes, or select No to ignore.
REP-20161
Unable to save AutoRecovery file, Autosave functionality would be disabled.
Category:
Other
Cause:
Oracle Reports Builder tried to write an AutoRecovery file and could not. The possible causes of this error include the following: Case 1: Lack of necessary privileges to write the file. Case 2: The file system does not have enough room for the file. Case 3: A system error made it impossible to open the file.
Action:
Either select OK to have Oracle Reports Builder to disable Autosave, or select Cancel to take the following actions to correct this error: If Case 1: Verify the privileges necessary to write the file. If Case 2: Make more room by deleting unnecessary files or expanding storage. If Case 3: Consult the operating system documentation or contact the system administrator.
REP-20190
Quit will terminate the current report, as well as any other pending reports.
Category:
Other
Cause:
A request to exit the Reports Server or Reports Background Engine was issued while one or more reports are still executing or awaiting execution.
Action:
To finish report execution, cancel the operation. Otherwise, accept the warning dialog.
REP-20191
Cannot exit Windows when this program is running. Close the Reports Background Engine and exit Windows.
Category:
Operating System
Cause:
The Reports Background Engine requires Windows, but a request was issued to exit Windows while the Reports Background Engine is still running.
Action:
Exit the Reports Background Engine before exiting Windows.
REP-25206
Converting {0} to {1} failed.
Category:
Other
Cause:
The most likely cause of this error is that the source type specified was incorrect.
Action:
Ensure that the source file is of the specified source type.
REP-25207
Invalid conversion: stype and dtype are not of the same document type.
Category:
Other
Cause:
An attempt was made to convert a document of one type to another type; that is, an attempt to convert one of the possible report files to a PL/SQL file, or vice versa.
Action:
Ensure that the source and destination of theconversion are the same type of document.
REP-25401
User exit .DLL file {0} cannot be found.
Category:
Other
Cause:
The report attempted to execute a user exit, but the user exit .DLL file could not be located. This file typically resides in: the current directory the Windows directory (typically \\WINDOWS) the Windows system directory (typically \\WINDOWS\\SYSTEM) the directory containing the executable file for the current task the directories listed in the PATH environment variable the list of directories mapped in a network
Action:
Locate the specified .DLL file and place it in one of the directories listed above.
REP-25402
An internal error occurred attempting to locate user exit .DLL file {0} within file {1}
Category:
Other
Cause:
The 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 Builder, which should always be linked into the user exit .DLL.
Action:
Rebuild the specified user exit .DLL correctly.
REP-31681
Connecting to a different database may invalidate existing data model.
Category:
Data
Cause:
Only one connection to a database is valid at a time. If a connection is established to different database, the existing data model may not be valid afterward.
Action:
To keep the existing data model valid, do not reconnect to a different database unless the queries are compatible with the new database connection.
REP-31700
The report definition is incomplete, or the query does not have break groups. Cannot run the Web Wizard.
Category:
Other
Cause:
The report definition was not completed before running the Web Wizard. To run the Web Wizard, the report definition must contain a Data Model with multiple groups and a valid Paper Layout.
Action:
Create at least one query with multiple groups and default the layout using the Report Wizard.
REP-31800
Image file {0} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not locate one of its image files. Possible causes of this error include: Case 1: The image file does not exist Case 2: The image file is in the wrong place. Case 3: The environment is not configured properly.
Action:
Take the following actions to correct this error: If Case 1: Verify that the image file is present. If Case 2: Verify that the image file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
REP-31801
Image {0} specified in the template cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not locate the image corresponding to the chosen templage. Possible causes of this error include: Case 1: The image file does not exist Case 2: The image file is in the wrong place. Case 3: The environment is not configured properly.
Action:
Take the following actions to correct this error: If Case 1: Verify that the image file is present. If Case 2: Verify that the image file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
REP-31802
Enter a SQL statement on this page.
Category:
Other
Cause:
In order for the wizard to create the report, a valid SQL text must exist.
Action:
Enter a SQL statement.
REP-31803
SQL text cannot be checked due to no database connection.
Category:
Other
Cause:
The wizard requires a connection to a database in order to check the SQL text.
Action:
Connect to a database by typing in a login string whenever the Connect dialog is shown. Confirm logon information with the database administrator.
REP-31804
The SQL is OK.
Category:
Other
Cause:
The wizard has checked the SQL text against the database and has confirmed that it will work.
Action:
No changes are needed to the SQL text.
REP-31805
Break level {0} has no valid break columns.
Category:
Other
Cause:
Each break level must contain at least one valid break column. A break column cannot be a summary or placeholder column. Nor can it have a data type of Raw, Longraw, or Long.
Action:
Provide at least one valid break column for the break level or move all columns that are currently in this break level to another level which contains a valid break column.
REP-31806
All fields cannot be designated to be break fields.
Category:
Other
Cause:
All fields were chosen to be break fields. Each break field designated groups the data of the fields that are not break fields. With no non-break fields, this situation is invalid.
Action:
Designate at least one field to be a non-break field. For example, remove all break fields from the highest numbered break level (that is, from the bottom of the list of break fields).
REP-31807
Template file {0} cannot be found.
Category:
Other
Cause:
Oracle Reports Builder could not locate the template file with the given name. Possible causes of this error include: Case 1: The template file does not exist. Case 2: The template file is in the wrong place. Case 3: The environment is not configured properly.
Action:
Take the following actions to correct this error: If Case 1: Verify that the template file is present. If Case 2: Verify that the template file is in the proper directory. If Case 3: Verify that the environment is set correctly. On UNIX, verify that the proper environment variable is set, and on MS Windows check the file oracle.ini.
REP-31808
A SQL statement must be entered.
Category:
Other
Cause:
A SQL statement was not entered for the wizard to generate a report.
Action:
Enter a SQL statement in the wizard tab.
REP-31809
At least one field to display must be chosen.
Category:
Other
Cause:
No field has been selected to display.
Action:
Select some fields to display.
REP-31810
At least one break group must be created.
Category:
Other
Cause:
The current report style needs breaks groups.
Action:
Create some break groups.
REP-31811
At least one matrix row must be selected.
Category:
Other
Cause:
Nothing has been selected as matrix rows.
Action:
Select some columns as matrix rows.
REP-31812
At least one matrix column must be selected.
Category:
Other
Cause:
Nothing has been selected as matrix columns.
Action:
Select some columns as matrix columns.
REP-31813
At least one matrix cell must be selected.
Category:
Other
Cause:
Nothing has been selected as matrix cells.
Action:
Select some columns as matrix cells.
REP-31814
At least one matrix break must be selected.
Category:
Other
Cause:
Nothing has been selected as matrix breaks.
Action:
Create some matrix break groups.
REP-31815
At least one field must be displayed per group.
Category:
Other
Cause:
This problem is due to: 1) This field has been specified as a group field. 2) The group of this field has been defaulted, and this field is the only one that has been marked as "to be defaulted" in its group.
Action:
1) If this field has been specified as a group field, go to the group page to deselect this field. 2) If the group of this field has been default, go to the group page to deselect that group.
REP-31816
Groups to be defaulted must be selected.
Category:
Other
Cause:
No group has been selected to be defaulted.
Action:
Select groups to be defaulted.
REP-31817
At the top of the group. Cannot move up.
Category:
Other
Cause:
This column is at the top of its group.
Action:
Do not try to move this column up.
REP-31818
At the bottom of the group. Cannot move down.
Category:
Other
Cause:
This column is at the bottom of its group.
Action:
Do not try to move this column up.
REP-31819
Report level columns cannot be reordered.
Category:
Other
Cause:
Report level columns do not have the POS attribute.
Action:
Set where to display the report level columns in the Paper Layout editor.
REP-31820
Selected groups have no columns in them.
Category:
Other
Cause:
Selected groups have no columns in them, so no report can be generated.
Action:
Select some other groups.
REP-31821
There is no text specified in the text editor.
Category:
Other
Cause:
The text for a mailing label or form letter report is empty.
Action:
Type some text in the text editor.
REP-31822
One group must be selected.
Category:
Other
Cause:
No group has been selected.
Action:
Go to the group page and select one group.
REP-31823
One and only one group must be selected.
Category:
Other
Cause:
There is more than one group selected.
Action:
Select one and only one group.
REP-31824
Another group must be selected since there are no columns in the selected group.
Category:
Other
Cause:
There are no columns in the selected group.
Action:
Select another group that has columns.
REP-31825
Cancel the wizard and fix the problem in report editors.
Category:
Other
Cause:
The data model is invalid or the default region is too small.
Action:
Fix the problem in the Data Model editor or Paper Layout editor.
REP-31826
A custom template file name is not specified.
Category:
Other
Cause:
A custom template is selected, but no template file name is specified.
Action:
Type a custom template file name, or click Browse button to navigate to it.
REP-31827
Invalid print direction or illegal defaulting of page level summary column.
Category:
Other
Cause:
The print direction against one or more groups is invalid for the requested default style, or page level summary column was selected to be defaulted (page level summaries are not supported within defaulting).
Action:
Alter the print direction against the group or the default style, or deselect all page level summaries.
REP-31828
The query definition is invalid.
Category:
Other
Cause:
The query is not properly defined.
Action:
Define a valid query.
REP-31906
This type of graph requires more categories than have been selected.
Category:
Other
Cause:
The number of categories required for a graph depends on the type of graph selected. This type of graph requires more categories than were selected.
Action:
Select the minimum number of categories required by the type of graph selected in a previous panel.
REP-31907
This type of graph requires more data columns than have been selected
Category:
Data
Cause:
The number of data columns required for this graph depends on the type of graph selected. This type of graph requires more data columns than were selected.
Action:
Select the minimum number of data columns required by the type of graph selected in a previous panel.
REP-31908
The Data Model has changed. Reselect categories and data for the created graph.
Category:
Data
Cause:
The data model has been changed for an existing graph.
Action:
Reselect the categories and data for the graph.
REP-31909
This type of graph requires %s categories.
Category:
Other
Cause:
The number of categories required for a graph depends on the type of graph selected. This type of graph requires %s categories.
Action:
Select the minimum number of categories required by the type of graph selected in a previous panel.
REP-31910
This type of graph requires %s data columns.
Category:
Data
Cause:
The number of data columns required for this graph depends on the type of graph selected. This type of graph requires %s data columns.
Action:
Select the minimum number of data columns required by the type of graph selected in a previous panel.
REP-31950
An error occurred in the Oracle Reports Builder graph support.
Category:
Other
Cause:
An error occurred initializing the Graph Wizard.
Action:
Verify that all components are installed properly. Restart the product.
REP-31951
The Graph Wizard cannot be initialized.
Category:
Other
Cause:
The Graph Builder library could not be initialized.
Action:
Verify that the Graph Wizard and Graphics Runtime are properly installed and that there are enough system resources available.
REP-31952
The Graph Wizard cannot be initialized due to incorrect version of libraries.
Category:
Other
Cause:
The Graph Builder library could not be initialized.
Action:
Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
REP-31953
An error occurred in the Graph Wizard.
Category:
Other
Cause:
The Graph Builder library could not be initialized.
Action:
Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
REP-31954
An error occurred in the Graph Wizard user interface.
Category:
Other
Cause:
The Graph Wizard failed to load properly.
Action:
Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
REP-31955
An error occurred in the graph runtime executable while attempting to create a graph.
Category:
Other
Cause:
The Graph Builder failed to build the graph.
Action:
Verify that the Graph Wizard libraries are properly installed and that there are enough system resources available.
REP-31980
Incorrect field mapping is specified. The graph will not be generated.
Category:
Other
Cause:
Fields for both category and value axes were not specified in the Graph Wizard.
Action:
Reenter the Graph Wizard and specify fields for both Category and Value axes.
REP-31981
The Data Model is empty or invalid.
Category:
Data
Cause:
The Graph Wizard was invoked on an empty report.
Action:
Create report (at least a data model) and try again.
REP-32600
An unexpected error occurred. Aborting.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32601
The report already exists in a translation file.
Category:
Other
Cause:
An attempt was made to overwrite an existing translation file.
Action:
Select a different name for the translation file.
REP-32602
Oracle Reports Builder cannot be initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32603
The VGS system cannot be initialized.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32604
A fatal error occurred loading report {0}. Check version.
Category:
Other
Cause:
The specified report cannot be loaded.
Action:
Verify that the correct version of the report is being opened.
REP-32605
The report file cannot be opened for reading.
Category:
Other
Cause:
The report file is unreadable.
Action:
Check the read permission of the report file.
REP-32606
File {0} cannot be opened for reading.
Category:
Other
Cause:
The specified file cannot be opened.
Action:
Verify that the file exists and is readable.
REP-32607
The translation builder tree does not exist.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32608
Translations for that language do not exist.
Category:
Other
Cause:
The Translation Manager cannot translate into the given target language.
Action:
Verify that the target language is supported.
REP-32609
This is not a valid report tree.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32610
Source data file {0} does not match.
Category:
Data
Cause:
The translation file being merged into the report was not created from the selected report.
Action:
Merge the translation file into the original report.
REP-32612
The string for the base language cannot be merged.
Category:
Other
Cause:
An attempt was made to merge the untranslated strings back into the original report.
Action:
Translate the strings in the translation file and try again.
REP-32613
A matching VGS string in NX file cannot be found.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32614
Successfully merged strings for language {0}.
Category:
Other
Cause:
The operation was completed with no errors.
Action:
No action is necessary.
REP-32615
The merge operation failed.
Category:
Other
Cause:
The merge operation encountered errors.
Action:
Check the log file for more information.
REP-32616
Translations in NX file cannot be found.
Category:
Other
Cause:
The translation file does not contain translated strings.
Action:
Verify that the correct translation file is used for the given report.
REP-32617
The NX file is corrupt.
Category:
Other
Cause:
An abnormal condition was encountered.
Action:
For assistance, contact Oracle Support Services.
REP-32618
The NX file cannot be opened for reading.
Category:
Other
Cause:
The translation file cannot be opened.
Action:
Verify that the file exists and is readable.
REP-32750
The data of image {0} cannot be unpacked. The image has been removed.
Category:
Data
Cause:
Case 1: The image data is corrupted. Case 2: REPORTS_DEFAULT_DISPLAY is set to YES and the image format used is not supported.
Action:
Take the following actions to correct this error: If Case 1: Import the image again. If Case 2: Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
REP-32751
Some text segments are missing.
Category:
Other
Cause:
Text segments cannot be found for some boilerplate text. The report could be corrupted.
Action:
Check the boilerplate text objects in the report. Remove suspicious ones and create replacements for them.
REP-34202
A value must be entered.
Category:
Other
Cause:
No value has been entered.
Action:
Enter a value.
REP-34203
WARNING: The user modified Format Trigger will be overwritten. Continue?
Category:
Other
Cause:
Format trigger has been modified.
Action:
Click Yes to overwrite the user modified trigger. Click No or Cancel to retain the modified trigger.
REP-34205
At least one condition must be specified.
Category:
Other
Cause:
No condition was specified in the Format Exception dialog box.
Action:
Specify at least one condition.
REP-34300
No distribution list is available.
Category:
Other
Cause:
No distribution target has been specified for the report.
Action:
Create a distribution list.
REP-34301
The value for the field is invalid.
Category:
Other
Cause:
An invalid value or no value has been entered for the field.
Action:
Enter a valid value.
REP-34302
The destination format is not compatible with the runtime mode.
Category:
Other
Cause:
The destination format must be compatible with the current mode for running the report. Likewise, the destination format must be compatible with all other destination formats in the report. There is no support for mixing bitmap output with character mode output.
Action:
Ensure all the destination formats are compatible with either character or bitmap output modes.
REP-34305
The keyword setting for the destid={0} is invalid.
Category:
Other
Cause:
Keyword settings are incorrect in the distribution file.
Action:
Alter the distribution file to ensure that all entries have valid values.
REP-34306
No distribution ID has been specified for the destination.
Category:
Other
Cause:
In the distribution file, the ID for the destination is missing.
Action:
Add a destination ID to the destination line. For example: Dest1:
REP-34307
The destination ID is not unique.
Category:
Other
Cause:
In the distribution file, the ID for the destination is not unique.
Action:
Add a unique destination ID for the entry.
REP-34308
Reference parameter {0} in the distribution list is invalid.
Category:
Other
Cause:
The reference parameter in the distribution list refers to a wrong group.
Action:
Repeat on the same group as that of the reference parameter.
REP-34309
A reference parameter is not allowed in a Report-level distribution list.
Category:
Other
Cause:
A reference parameter was found in a Report-level distribution list.
Action:
Remove the reference paramter distribution item from the Report-level distribution list.
REP-34310
A reference parameter is not allowed in a distribution list for XML destination files.
Category:
Other
Cause:
An XML destination cannot have a reference parameter in the distribution list.
Action:
Remove the reference parameter for the XML file destination from the distribution list.
REP-34311
The XSL transformation file cannot be found.
Category:
Other
Cause:
The XSL transformation file distribution.xsl could not be located.
Action:
Ensure that the XSL file is placed in ORACLE_HOME/reports/conf.
REP-34312
An error occurred in XSL template.
Category:
Other
Cause:
An error occurred when applying XSL transformation. This could be due to an error in the XSL file.
Action:
Check the XSL file and ensure the transformations are correct.
REP-34313
The external file {0} specified in destination {1} cannot be found.
Category:
Other
Cause:
An external file specified in the distribution list was not found.
Action:
Verify the correct path of the external file specified.
REP-34314
The foreach tag cannot be used before both the mail and attach tags at destination {0}.
Category:
Other
Cause:
The foreach tag was used before both the mail tag and the attach tag.
Action:
Correct the entry in the XML distribution file to use a single level of foreach tag.
REP-34315
The instance attribute cannot be used without a foreach tag at destination {0}.
Category:
Other
Cause:
The instance attribute was used without an enclosing foreach tag.
Action:
Correct the entry in the XML distribution file to use a foreach tag at the appropriate level.
REP-34316
Reference parameters cannot be used without a foreach tag in destination {0}.
Category:
Other
Cause:
Reference parameters were used without a foreach tag.
Action:
Correct the entry in the XML distribution file to use a foreach tag appropriately.
REP-34317
The instance attribute cannot be used if 'srctype' is not 'report' in destination {0}.
Category:
Other
Cause:
The instance attribute was used for a body or attach tag whose source is not a report section.
Action:
Correct the entry in the XML distribution file to remove the instance attribute.
REP-34318
The foreach tag cannot be used if 'srctype' is not 'report' in destination {0}.
Category:
Other
Cause:
A foreach tag was used before an attach tag whose source is not a report section.
Action:
Correct the entry in the XML distribution file to remove the foreach tag.
REP-34319
An unknown report section {0} was specified as the source in destination {1}.
Category:
Other
Cause:
The src attribute in the include tag does not specify a valid report section.
Action:
Correct the entry in the XML distribution file to use a valid report section. The valid report sections can be any one of 'headerSection', 'mainSection', 'trailerSection', or 'report'.
REP-34320
Report sections used in destination {1} do not repeat on the same group.
Category:
Other
Cause:
The report sections used in include tags do not repeat on the same group.
Action:
Modify the report definition so that all the sections used repeat on the same group. Use only those report section combinations that repeat on the same group.
REP-34321
Only one external file can be specified in the body or attachment at destination {0}.
Category:
Other
Cause:
More than one external file was specified for the corresponding body or attach tag. Each body or attach tag whose srctype is file, can have only one include tag referring to an external file.
Action:
Correct the entry in the XML distribution file and specify only one external file for the body or attach tag.
REP-34322
Inline text for body or attach tag for destination {0} can be specified only if 'srctype' is 'text'.
Category:
Other
Cause:
Inline text was specified for a body or an attach tag whose 'srctype' is not 'text'.
Action:
Correct the entry in the XML distribution file and specify the correct 'srctype'.
REP-34323
Tag {0} specified for destination {1} cannot be empty.
Category:
Other
Cause:
An empty tag was encountered. Only the include and the property tags can be empty. All other tags must have at least one child.
Action:
Correct the entry in the XML distribution file by either removing the empty tag or inserting the appropriate child tag for it.
REP-34324
Inline text is missing when 'srctype' is 'text' at destination {0}.
Category:
Other
Cause:
Inline text was not specified for a body or an attach tag whose 'srctype' is specified as 'text'.
Action:
Correct the entry in the XML distribution file by specifying the appropriate srctype for the corresponding body or attach tag. If the 'srctype' should be 'text', replace the include tag with inline text.
REP-34325
A reference parameter is not allowed in a distribution list for DelimitedData destination files.
Category:
Other
Cause:
DelimitedData destination cannot have a reference parameter in the distribution list.
Action:
Remove the reference parameter for the DelimitedData file destination from the distribution list.
REP-34326
SPREADSHEET format is not supported in distribution.
Category:
Other
Cause:
SPREADSHEET destination cannot be used in distribution.
Action:
Remove the SPREADSHEET destination from the distribution XML file.
REP-34501
A Web design tool is not registered.
Category:
Other
Cause:
The mail destination specified is too long. Destination names must be less than 1024 characters. The PREFS.ORA file does not contain an entry for a Web design tool.
Action:
Specify a mail destination the 'To' field that is less than 1024 characters. Add an entry for the Web design tool.
REP-34502
The Web design tool registered cannot be found or run.
Category:
Other
Cause:
The Web design tool does not exist, or the file exists but cannot run.
Action:
Correct the PREFS.ORA file and move the Web design program to the correct directory.
REP-34551
Feature {0} is deprecated. See the Oracle Reports documentation for more information.
Category:
Other
Cause:
The feature is deprecated.
Action:
See the Oracle Reports documentation on the Oracle Technology Network (OTN).
REP-34552
The Oracle Graphics Graph in this document will not be saved.
Category:
Other
Cause:
There are one or more obsolete Oracle Graphics graphs in this document that will not be saved.
Action:
Replace the Oracle Graphics graphs with new graphs generated with the Graph Wizard.
REP-35000
The output image format specified is not supported.
Category:
Other
Cause:
The output image format specified on the command line is not supported by Oracle Reports.
Action:
Specify one of the supported output image formats. Refer to the Oracle Reports online help for a list of supported output image formats.
REP-35001
An interanl error occurred writing the image.
Category:
Other
Cause:
The image stream may be invalid or corrupt. A failure occurred while reading the image data from the image stream.
Action:
For assistance, contact Oracle Support Services.
REP-35002
The Reports Toolkit System is not available.
Category:
Other
Cause:
An error occurred initializing the Reports Toolkit System. The required Java classes were not found.
Action:
For assistance, contact Oracle Support Services.
REP-35003
CGM or OGD format cannot be converted to image for HTML/HTMLCSS output.
Category:
Other
Cause:
CGM or OGD is used in the report. It is not supported when Display is not available.
Action:
Remove the OGD or CGM image used in the report. Set DISPLAY and REPORTS_DEFAULT_DISPLAY to NO. Verify that the image format is one of the supported formats: GIF, JPEG, JPG, PNG, BMP.
REP-35004
The Oracle Reports Font Toolkit Subsystem is not available.
Category:
Other
Cause:
An error occurred while initializing the Oracle Reports Font Toolkit Subsystem. The required Java classes were not found.
Action:
For assistance, contact Oracle Support Services.
REP-35503
PDFOWNER and PDFUSER cannot have the same value.
Category:
Other
Cause:
PDFOWNER and PDFUSER cannot be same.
Action:
Specify different values for PDFUSER and PDFOWNER.
REP-50000
A generic error occurred while running the job.
Category:
Other
Cause:
A generic error occurred while running the job.
Action:
For assistance, contact Oracle Support Services.
REP-50001
The server is initializing.
Category:
Other
Cause:
Reports Server is initializing.
Action:
Wait until the Reports Server is ready to serve requests.
REP-50002
The server is shutting down.
Category:
Other
Cause:
The Reports Server is shutting down.
Action:
Restart the Reports Server.
REP-50003
The command line is invalid: {0}.
Category:
Other
Cause:
An invalid command line was submitted.
Action:
Refer to the Oracle Reports documentation for command-line arguments and syntax.
REP-50004
No report is specified on the command line.
Category:
Other
Cause:
There is no report name specified on the command line.
Action:
Specify the name of the report on the command line.
REP-50005
No USERID is specified on the command line.
Category:
Other
Cause:
There is no USERID keyword specified on the command line.
Action:
Specify USERID on the command line as part of the database connection information.
REP-50006
The SCHEDULE argument is invalid on the command line: {0}.
Category:
Other
Cause:
The SCHEDULE argument value on the command line is not correct.
Action:
Refer to the Oracle Reports documentation for the correct SCHEDULE argument syntax.
REP-50007
The TOLERANCE argument is invalid on the command line: {0}.
Category:
Other
Cause:
The TOLERANCE argument value on the command line is not correct.
Action:
Refer to Oracle Reports documentation for correct TOLERANCE argument syntax.
REP-50008
The report is successfully submitted.
Category:
Other
Cause:
The report is successfully submitted to the Reports Server.
Action:
No action required.
REP-50009
The report is successfully run.
Category:
Other
Cause:
The report ran successfully in the Reports Server.
Action:
No action required.
REP-50108
The job is waiting in the queue.
Category:
Other
Cause:
The job is waiting in the queue to be executed.
Action:
No action required.
REP-50109
The report is opening to run.
Category:
Other
Cause:
Opening the report to run.
Action:
No action required.
REP-50110
Report {0} is running.
Category:
Other
Cause:
Running the specified report.
Action:
No action required.
REP-50111
Report {0} finished successfully.
Category:
Other
Cause:
The report has finished successfully.
Action:
No action required.
REP-50112
The report terminated with error: {0}.
Category:
Other
Cause:
The report terminated with the stated error.
Action:
Correct the error and rerun the report.
REP-50113
The engine crashed.
Category:
Other
Cause:
The engine crashed due to an internal error.
Action:
For assistance, contact Oracle Support Services
REP-50114
The job is canceled upon user request.
Category:
Other
Cause:
The job was canceled at the user's request.
Action:
No action required.
REP-50115
The job is canceled as the server is shutting down.
Category:
Other
Cause:
The job was canceled because the Reports Server is shutting down.
Action:
No action required.
REP-50116
The job execution failed and is waiting for retry.
Category:
Other
Cause:
The job execution has failed and waiting to be retried.
Action:
No action required.
REP-50117
The job is sending output.
Category:
Other
Cause:
The job is sending output to specified destinations.
Action:
No action required.
REP-50118
Report execution is initialized.
Category:
Other
Cause:
Initializing report execution.
Action:
No action required.
REP-50119
A Before Report trigger is running.
Category:
Other
Cause:
The report is running a Before Report trigger.
Action:
No action required.
REP-50120
A Between Pages trigger is running.
Category:
Other
Cause:
The report is running a Between Pages trigger.
Action:
No action required.
REP-50121
An After Report trigger is running.
Category:
Other
Cause:
The report is running an After Report trigger.
Action:
No action required.
REP-50122
A Before Parameter Form trigger is running.
Category:
Other
Cause:
The report is running a Before Parameter Form trigger.
Action:
No action required.
REP-50123
An After Parameter Form trigger is running.
Category:
Other
Cause:
The report is running an After Parameter Form trigger.
Action:
No action required.
REP-50124
Page {0} is formatting.
Category:
Other
Cause:
Oracle Reports is formatting the specified page.
Action:
No action required.
REP-50125
An internal exception occurred: {0}.
Category:
Other
Cause:
Oracle Reports encountered an internal exception.
Action:
For assistance, contact Oracle Support Services
REP-50126
File {0} cannot be opened for writing.
Category:
Other
Cause:
Oracle Reports cannot open the specified file for writing.
Action:
Check the write permission of the file, or of the directory in which the file is stored.
REP-50127
File {0} cannot be written to.
Category:
Other
Cause:
Oracle Reports cannot write content to the specified file.
Action:
Check available disk space to verify that that there is enough space to write the file. Verify that no other applications are writing to the same file.
REP-50131
An attempt to bind to {0} failed.
Category:
Other
Cause:
Binding to Reports Server failed.
Action:
Verify that the Reports Server is running and that it is accessible from this machine.
REP-50133
The job has been transferred to {0}, the new job ID is {1}.
Category:
Other
Cause:
The job has been transferred to another server.
Action:
No action required.
REP-50134
Cache subitem {0} does not exist.
Category:
Other
Cause:
An internal error occurred. Some of the report output is deleted unexpectedly.
Action:
Rerun the job to get the correct output.
REP-50135
Class {0} cannot be located.
Category:
Other
Cause:
Oracle Reports cannot locate the specified class.
Action:
Verify that the specified class is in the CLASSPATH and REPORTS_CLASSPATH.
REP-50136
An error occurred reading the input stream: {0}.
Category:
Other
Cause:
Oracle Reports cannot read an input stream due to the stated error.
Action:
Correct the error and rerun the report.
REP-50137
The input stream cannot be closed: {0}.
Category:
Other
Cause:
Oracle Reports cannot close the input stream due to the stated error.
Action:
For assistance, contact Oracle Support Services
REP-50138
A mail server is not available.
Category:
Other
Cause:
There is no mail server specified in Reports Server configuration file.
Action:
Add a &lt;mail&gt; element with a server attribute to the Reports Server configuration file.
REP-50139
File {0} cannot be deleted.
Category:
Other
Cause:
The specified file cannot be deleted.
Action:
The file is probably being used by another application. Close that application and try again.
REP-50140
An internal error {0} occurred.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services
REP-50141
File {0} cannot be opened.
Category:
Other
Cause:
Oracle Reports cannot open the specified file.
Action:
Check whether the specified file exists.
REP-50142
File {0} cannot be read.
Category:
Other
Cause:
Oracle Reports cannot read the specified file.
Action:
Check read permission for specified file.
REP-50143
The job is submitted successfully.
Category:
Other
Cause:
The job has been submitted successfully.
Action:
No action required.
REP-50145
Duplicate parameter {0} is specified.
Category:
Other
Cause:
The parameter was specified more than once on the command line.
Action:
Remove the duplicate parameters.
REP-50148
A Base64 format error occurred.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services
REP-50149
The parameter value is invalid: {0}.
Category:
Other
Cause:
Bad parameter value specified.
Action:
Refer to the Oracle Reports documentation for the correct syntax for the parameter.
REP-50150
The Reports Server object cannot be accessed.
Category:
Other
Cause:
An incorrect signature or key to access the Reports Server object was provided.
Action:
Verify permission to access the Reports Server, and correct pair of signature keys.
REP-50151
An error occurred while sending the file to the printer: {0} - {1}.
Category:
Other
Cause:
Error while sending file to specified printer due to the stated reason.
Action:
Correct the error and try again.
REP-50152
An error occurred while sending mail: {0}.
Category:
Other
Cause:
Error while sending mail due to stated reason.
Action:
Correct the error and try again.
REP-50153
The mail to list is missing.
Category:
Other
Cause:
Missing TO or DESNAME parameter for mail. These parameters point to the recipient list of the report.
Action:
Add TO or DESNAME to the command line or the URL.
REP-50155
The job status is unknown.
Category:
Other
Cause:
Unknown job status.
Action:
No action required.
REP-50156
The scheduled job has expired.
Category:
Other
Cause:
The scheduled job has run for specified number of times or its expiration time has passed.
Action:
No action required.
REP-50157
An error occurred while sending the file to printer {0}. Exit with error code {1}.
Category:
Other
Cause:
An error occurred while sending the file to the specified printer.
Action:
Check if the printer or printer driver is correctly installed.
REP-50158
Job finished successfully but output is purged from cache.
Category:
Other
Cause:
The job has finished successfully, but the output has been purged manually or by the cache system and is no longer available.
Action:
Rerun the job to regenerate the output.
REP-50159
The report generated successfully but distribution to destinations failed.
Category:
Other
Cause:
The job has executed successfully, but there were some errors during the distribution of the output.
Action:
Check the error for each destination, fix them if possible, and rerun the job.
REP-50160
The report is distributing.
Category:
Other
Cause:
Oracle Reports is distributing the report.
Action:
No action required.
REP-50161
The database connection string {0} is invalid.
Category:
Other
Cause:
The database connection string format is not correct.
Action:
Specify a correct database connection string in the format userid=&lt;username&gt;/&lt;password&gt;@&lt;tnsname&gt;.
REP-50162
The job output is distributing.
Category:
Other
Cause:
Oracle Reports is distributing the job output.
Action:
No action required.
REP-50163
The job output is copying.
Category:
Other
Cause:
Oracle Reports is copying the job output.
Action:
No action required.
REP-50164
The job output is printing.
Category:
Other
Cause:
Oracle Reports is printing the job output.
Action:
No action required.
REP-50165
The job output is mailing.
Category:
Other
Cause:
Oracle Reports is mailing the job output.
Action:
No action required.
REP-50166
The job output is uploading.
Category:
Other
Cause:
Oracle Reports is uploading the job output.
Action:
No action required.
REP-50168
A syntax error occurred in the Reports Server configuration file {0}.
Category:
Configuration
Cause:
A syntax error occurred in the specified Reports Server configuration file.
Action:
Refer to rwserverconf.xsd for the correct syntax for the server configuration file.
REP-50169
The type of the value for attribute {0} is invalid.
Category:
Other
Cause:
The type of the value for the specified attribute in the server configuration file is not valid.
Action:
Refer to rwserverconf.xsd for correct syntax for the attribute.
REP-50170
A syntax error occurred in the Reports Server configuration XSD file {0}.
Category:
Configuration
Cause:
A syntax error occurred in the the server configuration XSD file.
Action:
Use the original rwserverconf.xsd, without any change.
REP-50171
Authentication failed.
Category:
Security
Cause:
Authentication failed.
Action:
Provide the correct authentication information.
REP-50175
File {0} cannot be found.
Category:
Other
Cause:
Oracle Reports cannot find the specified file.
Action:
Check if the file exists on the file system.
REP-50177
The naming service is not available.
Category:
Other
Cause:
The naming server is down.
Action:
Start the naming server.
REP-50180
The naming service failed to shut down.
Category:
Other
Cause:
Oracle Reports could not stop the naming server.
Action:
For assistance, contact Oracle Support Services
REP-50200
OID server cannot connect.
Category:
Other
Cause:
The OID server is probably down.
Action:
Verify that the OID server is up.
REP-50201
The user role cannot be retrieved from the OID server.
Category:
Other
Cause:
The OID server is probably down.
Action:
Verify that the OID server is up. Also check the Reports Server trace file under $ORACLE_HOME/reports/logs/&lt;server&gt;.trc for more information.
REP-50509
Destination ID {0} failed with error {1}.
Category:
Other
Cause:
Distribution to the ID failed with specified error.
Action:
Check the distribution list and correct the error.
REP-50602
Servlet config file {0} cannot be parsed. {1}.
Category:
Other
Cause:
The servlet config file could not be parsed. The XML syntax is incorrect.
Action:
Correct the servlet config file and start the server.
REP-50603
The servlet file cannot be found {0}. {1}.
Category:
Other
Cause:
The rwservlet file is not found.
Action:
Contact the system administrator.
REP-51000
The Reports Server name is not specified.
Category:
Other
Cause:
The Reports Server name is not specified on the command line or in the URL.
Action:
Specify the Reports Server name as follows: server=&lt;server_name&gt;.
REP-51002
Bind to Reports Server {0} failed.
Category:
Other
Cause:
Failed to connect to Reports Server.
Action:
Verify that Reports Server is running and that the Reports Server name is correct.
REP-51004
Get connection object failed.
Category:
Other
Cause:
Failed to get a connection object from the server. This can happen because the server has reached the maximum number of connections allowed, or the client does not have privileges to make a connection to the server.
Action:
Increase the maxConnect attribute of the connection element and verify that the client has connect privileges to the server.
REP-51015
Sending job output to the client failed due to {0}.
Category:
Other
Cause:
Failed to send job output to client.
Action:
Fix the problem related to stated reason and rerun the job.
REP-51017
The user ID is incomplete.
Category:
Other
Cause:
The value specified for the user ID was incomplete.
Action:
Specify correct syntax for the user ID: &lt;username&gt;/&lt;password&gt;@&lt;tnsname&gt;.
REP-51018
Database user authentication is missing.
Category:
Security
Cause:
No database user authentication information was provided.
Action:
Provide valid database user authentication information.
REP-51019
System user authentication is missing.
Category:
Security
Cause:
No system user authentication information was provided.
Action:
Provide valid system user authentication information.
REP-51020
Authentication for both system user and database user does not match.
Category:
Security
Cause:
The system and the database user authentication information was different.
Action:
Provide the same authentication information for the system and database user.
REP-51021
System and database user authentication is missing.
Category:
Security
Cause:
No system user and database user authentication information was provided.
Action:
Provide valid system and database user authentication information.
REP-51024
The client has not been connected to Reports Server.
Category:
Other
Cause:
An internal error occurred. The client has not connected to Reports Server before using the server.
Action:
For assistance, contact Oracle Support Services.
REP-51025
User {0} does not have the privilege to run command {1}.
Category:
Other
Cause:
An attempt to run the indicated command failed due to insufficient privileges.
Action:
Contact the Oracle Reports administrator to request the necessary privileges.
REP-51026
No output is generated for job {0}.
Category:
Other
Cause:
No output was generated for the indicated job.
Action:
Check the report and job definition and rerun the job.
REP-51027
Engine {0} cannot be killed.
Category:
Other
Cause:
An attempt was made to kill an engine in an older version of Reports Server.
Action:
This operation is not supported.
REP-52001
The key map file {0} cannot be read.
Category:
Other
Cause:
Failed to read the Reports key map file.
Action:
Verify that the Reports key map file is in ORACLE_HOME/reports/conf and that it contains valid information.
REP-52002
The key map file {0} cannot be parsed.
Category:
Other
Cause:
The Reports key map file cannot be parsed.
Action:
Verify that the Reports key map file has valid entries.
REP-52003
Read Reports template {0} failed
Category:
Other
Cause:
The Reports Servlet template cannot be read.
Action:
Verify that the Reports Servlet template is in ORACLE_HOME/reports/templates.
REP-52004
The authentication template {0} cannot be read.
Category:
Security
Cause:
Failed to read the Reports Servlet authentication template.
Action:
Verify that the Reports Servlet authentication template is in ORACLE_HOME/reports/templates.
REP-52005
The specified key {0} does not exist in the key map file.
Category:
Other
Cause:
The specified key does not exist in the Reports key map file.
Action:
Verify that the Reports key map file contains the specified key.
REP-52006
The specified URL {0} cannot be decoded.
Category:
Other
Cause:
The specified URL cannot be decoded.
Action:
Verify that the URL is a valid URL.
REP-52007
A Parameter Form format error was encountered.
Category:
Other
Cause:
The submitted Parameter Form has an invalid format.
Action:
Check if the hidden_run_parameters variable in the Parameter Form is null.
REP-52009
No such Web command ({0}).
Category:
Other
Cause:
The Web command passed in from rwservlet is not a valid command.
Action:
Check the help page for rwservlet for a valid Web command.
REP-52010
The specified key map file {0} does not exist.
Category:
Other
Cause:
The specified key map file does not exist.
Action:
Verify that the Reports key map file is in ORACLE_HOME/reports/conf.
REP-52242
The job with job ID {0} cannot be killed.
Category:
Other
Cause:
Insufficient privileges to perform this operation, or a job with the specified jobid does not exist.
Action:
Sufficient privileges are required for this operation. Either log in as administrator or as a user who has sufficient privileges. Specify a valid jobid in the command.
REP-52251
The output of job ID {0} requested on {1} cannot be retrieved.
Category:
Other
Cause:
Insufficient privileges for this operation, or invalid job ID or nonexistent output.
Action:
Sufficient privileges are required for this operation. Check if a valid job ID is provided in the command.
REP-52260
No Oracle Home is specified.
Category:
Other
Cause:
Oracle Home is not defined in the environment.
Action:
Define Oracle Home in the environment. See Configuration chapter in the Publishing Reports to the Web manual for details.
REP-52261
Parameter {0} has an incorrect value {1}.
Category:
Other
Cause:
The specified parameter has an invalid value.
Action:
Provide correct value for the parameter.
REP-52262
Diagnostic output is disabled.
Category:
Other
Cause:
Reports Server is unsecure, the DIAGNOSTIC property is set to NO in rwservlet.properties file, and a valid AUTHID is not specified in command line.
Action:
Specify a valid AUTHID in the command line or contact the system sdministrator.
REP-52265
The specified Web command {0} is not supported.
Category:
Other
Cause:
The web command is not a valid command for this utility.
Action:
Check the Publishing Reports to the Web manual for a list of valid commands for this utility.
REP-52266
The in-process Reports Server {0} failed to start.
Category:
Other
Cause:
There maybe a server with same name already existing in the network.
Action:
Verify that the server is not already started as a stand alone server.
REP-52268
The specified HTML code is not allowed: {0}
Category:
Other
Cause:
HTML tags were specified in the URL command.
Action:
Either remove the HTML tags in the URL and rerun the report, or set ALLOWHTMLTAGS in rwservlet.properties to YES and restart the OC4J container. However, note that any HTML code included as part of the report request URL may lead to a security compromise as it causes certain browsers to execute any script or code in the URL. This property is set to NO by default, disallowing any malicious HTML code to be entered in the URL when running a report.
REP-52280
An Oracle OID generic error occurred.
Category:
Other
Cause:
Failed to get resource type or resoruce values from OID.
Action:
Check the Oracle OID configuration.
REP-52281
The connection to Oracle OID using provider URL {0} cannot be established.
Category:
Other
Cause:
An attempt to connect to Oracle OID using given provider URL and user ID failed.
Action:
Check the Reports Servlet configuration file and verify that the provider URL and user ID are correct.
REP-52282
The specified resource type {0} in OID cannot be found.
Category:
Other
Cause:
The specified resource type is not created in OID
Action:
Verify that the resource type has been defined in OID.
REP-52283
The specified resource key {0} in OID cannot be found.
Category:
Other
Cause:
The specified resource key is not created in OID
Action:
Verify that the resource key has been defined in OID.
REP-52284
The create resource URL cannot be retrieved from OID.
Category:
Other
Cause:
The create resource URL is not defined in OID.
Action:
Verify that the create resource URL has been defined in OID.
REP-52285
The user name or subscriber name cannot be found in Logon Server cookie.
Category:
Other
Cause:
User is not logged on to Logon Server.
Action:
Log on to Logon Server.
REP-52286
Parameter SSOCONN requires the Reports Server to be secure and Single Sign-On turned on.
Category:
Other
Cause:
Either the Reports Server is running in non-secure mode, or the SINGLESIGNON parameter in rwservlet.properties is set to NO.
Action:
Verify that the Reports Server is running in secure mode, and the SINGLESIGNON parameter in rwservlet.properties is set to YES.
REP-52287
Parameter SSOCONN and AUTHID cannot be used together.
Category:
Security
Cause:
SSOCONN and AUTHID are both used in the command line. The AUTHID value overwrites the SSO userid, and SSOCONN requires the SSO user ID. Therefore, using the keywords together on the command line causes a conflict.
Action:
Remove either SSOCONN or AUTHID from the command line.
REP-53000
The connection is invalid.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-53053
Arguments for the function call are invalid.
Category:
Other
Cause:
Bad arguments for the function call.
Action:
Refer to the Oracle Reports help for the function arguments.
REP-53054
AUTHID is not allowed in the URL.
Category:
Security
Cause:
AUTHID was specified in the URL.
Action:
Either remove AUTHDID in the URL and rerun the report, or set ALLOWAUTHID in rwservlet.properties to YES and restart the OC4J container.
REP-54000
The cache item is not found in the cache system.
Category:
Other
Cause:
The cache item has been deleted manually or by the cache system.
Action:
Submit the request again to rerun the report.
REP-54001
The cache group item is not found in the cache system.
Category:
Other
Cause:
An internal error occurred.
Action:
Submit the request again without use cache. There is no tolerance in the command line or URL.
REP-54002
The cache item is no longer valid.
Category:
Other
Cause:
The cache item might have been cleaned up by the cache system due to resource constraints.
Action:
Submit the request again to rerun the report.
REP-54003
The syntax for the value of the time argument {0} is invalid.
Category:
Other
Cause:
The syntax for the time argument is incorrect.
Action:
Refer to the Oracle Reports documentation for the correct syntax of the time argument.
REP-54004
No cache directory is specified.
Category:
Other
Cause:
There is no cache directory specified in the server configuration file.
Action:
Specify a cache directory in the server configuration file.
REP-54005
The cache directory {0} does not exist.
Category:
Other
Cause:
The specified cache directory does not exist.
Action:
Create a cache directory before starting Reports Server.
REP-54006
The cache directory {0} cannot be created.
Category:
Other
Cause:
Unable to create a cache directory.
Action:
Ensure write permission and enough disk space for the cache directory.
REP-54007
The cacheSize value specified {0} is invalid.
Category:
Other
Cause:
The cacheSize value specified is not valid.
Action:
Correct the cacheSize value in the server config file and start the server.
REP-55005
An engine access violation occurred.
Category:
Other
Cause:
An incorrect key to access the engine object was provided.
Action:
For assistance, contact Oracle Support Services.
REP-55006
An attempt to load {0} failed.
Category:
Other
Cause:
Failed to load the specified dynamic library.
Action:
Verify that the dynamic library exists in PATH on NT or LD_LIBRARY_PATH on UNIX.
REP-55008
The report cannot be created. The command line is: {0}.
Category:
Other
Cause:
An attempt to create a report in the engine specified on the command line failed.
Action:
For assistance, contact Oracle Support Services.
REP-55009
The Report Engine failed to start. Port {0} specified in the server config file may be already in use.
Category:
Ports
Cause:
The ORB port specified in the config file is not available for the Reports Engine.
Action:
Specify a free port.
REP-55010
An incorrect value is specified for the ORBPorts element.
Category:
Other
Cause:
The ORB port specified is not in valid format.
Action:
Specify a proper integer value for the ORBPorts element.
REP-55100
The urlparameter not specified for the job.
Category:
Other
Cause:
The URL to be downloaded is not specified in the command line.
Action:
Specify the URL in the command line using urlparameter.
REP-55101
A timeout occurred in accessing the URL {0}.
Category:
Performance
Cause:
The engine cannot access the URLstream.
Action:
Check if the URL is accessible. If the engine is running behind a firewall, specify the necessary proxy settings in the server configuration file.
REP-55102
An error occurred setting the proxy information.
Category:
Other
Cause:
Proxy settings could not be set.
Action:
Check if the proxy settings file is valid.
REP-55103
API {0} is not applicable to the URL engine.
Category:
Other
Cause:
The API used is not applicable to the URL engine.
Action:
Verify the API used.
REP-55105
The distribution failed. Verify the distribution list.
Category:
Other
Cause:
The distribution file may be invalid.
Action:
Ensure that the XML distribution file conforms to the DTD.
REP-55106
The DESTYPE value is invalid.
Category:
Other
Cause:
The destination type (DESTYPE) value is null.
Action:
Specify a valid destination type (DESTYPE): FILE, PRINTER, MAIL, or CACHE.
REP-56000
Cluster {0} cannot be joined.
Category:
Other
Cause:
The Reports Server cluster was not joined because other Reports Servers could not be found.
Action:
Verify that this machine can see other Reports Servers. Use osfind to check for other Reports Server on the network.
REP-56001
LocationService cannot be found.
Category:
Other
Cause:
Unable to locate VisiBroker's LocationService.
Action:
This should not happen with VisiBroker 4.5. Report this problem to Oracle Support Services.
REP-56003
References for LocationService cannot be resolved.
Category:
Other
Cause:
References for VisiBroker's LocationService could not be resolved.
Action:
This should not happen with VisiBroker 4.5. Report this problem to Oracle Support Services.
REP-56014
The arguments for function call {0} are invalid.
Category:
Other
Cause:
The arguments for the specified function call were invalid.
Action:
Refer to jasmine.idl for the function arguments.
REP-56017
Security violation: access to job output not allowed.
Category:
Security
Cause:
An attempt was made to access job output by a non-owner.
Action:
This is security violation, and should not be attempted.
REP-56022
Engine {0} cannot be launched due to {1}.
Category:
Other
Cause:
The specified engine could not be launched for the stated reason.
Action:
Fix the problem described in the message, and restart Reports Server.
REP-56027
An internal error occurred: Engine registration failed.
Category:
Other
Cause:
An internal error occurred when registering the engine to Reports Server.
Action:
Contact Oracle Support Services if problem persists.
REP-56030
The initial engine number must be between minengine ({0}) and maxengine ({1}).
Category:
Other
Cause:
The value of initEngine is not between the minEngine and maxEngine values specified in the server configuration file.
Action:
Change the value of initEngine, minEngine, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
REP-56033
Job {0} does not exist.
Category:
Other
Cause:
The requested job does not exist.
Action:
Specify a valid ID of a job that exists in the Reports Server.
REP-56034
A job that is in current or scheduled queue cannot be resubmitted.
Category:
Other
Cause:
An attempt was made to resubmit a job that is in the current or scheduled job queue.
Action:
Kill or cancel the job in the current or scheduled queue, then resubmit it.
REP-56035
Connection object cannot be accessed.
Category:
Other
Cause:
The client did not provide the correct key to access the connection object in Reports Server.
Action:
This should not happen; ensure that the connection attempt is legitimate.
REP-56036
The job has been scheduled successfully.
Category:
Other
Cause:
This is a notification generated when a job has been scheduled successfully.
Action:
This is a job submission status. No action is needed.
REP-56040
Server {0} already exists in the network.
Category:
Other
Cause:
Another Reports Server in the network has the same name.
Action:
Specify a different name for this Reports Server.
REP-56041
Proxy server for the Reports 6i client cannot be started.
Category:
Other
Cause:
A failure occurred when attempting to start the proxy server that is used for the Reports 6i client.
Action:
Verify that the Reports Server name is defined in tnsnames.ora.
REP-56042
This function is not supported.
Category:
Other
Cause:
The invoked function is not supported.
Action:
Do not use this function.
REP-56043
No securityUserid is specified in the server configuration file.
Category:
Configuration
Cause:
The securityUserid property is missing from the security element specification in the server configuration file.
Action:
Add the securityUserid property to the security element in the server configuration file.
REP-56044
Parameter {0} has invalid value {1}.
Category:
Other
Cause:
The specified parameter has an incorrect value.
Action:
Refer to the Oracle Reports documentation for the correct parameter value syntax and type.
REP-56045
No Oracle Home is specified.
Category:
Other
Cause:
No Oracle Home is specified in the Reports Server running environment.
Action:
Verify that the ORACLE_HOME environment variable is set in the environment where Reports Server runs.
REP-56046
No method {0} is defined in class {1}.
Category:
Other
Cause:
No method is defined in the specified Java class.
Action:
Add the method into the Java class.
REP-56048
Engine {0} crashed.
Category:
Other
Cause:
Reports Server detected that the specified engine crashed.
Action:
Reports Server should restart another engine. Report the problem to Oracle Support Services with the testcase that caused the engine crash.
REP-56049
No portalUserid is specified in the server configuration file.
Category:
Configuration
Cause:
The portalUserid property is missing from the destination element for destype=oraclePortal in the server configuration file.
Action:
Add the portalUserid property to the destination element in the server configuration file.
REP-56050
Persistent file {0} in invalid or corrupted.
Category:
Other
Cause:
An attempt to read the Reports Server persistent file failed.
Action:
Delete the Reports Server persistent file &lt;server_name&gt;.dat in ORACLE_HOME/reports/server.
REP-56051
The connection to server {0} failed.
Category:
Other
Cause:
The specified server in the same cluster may be down or not ready.
Action:
Verify that the server is up and ready.
REP-56052
The connection to server {0} is dropped.
Category:
Other
Cause:
The specified server in the same cluster has been shut down.
Action:
This is for information only, no action is needed.
REP-56053
Cluster server {0} has been registered.
Category:
Other
Cause:
The specified server in the same cluster has been registered.
Action:
This is for information only, no action is needed.
REP-56054
A connection to server {0} is established.
Category:
Other
Cause:
The new Reports Server has connected to the specified Reports Server to form a cluster.
Action:
This is for information only, no action is needed.
REP-56055
The max connections allowed ({0}) is exceeded.
Category:
Other
Cause:
There are more concurrent connection attempts than the server is allowed.
Action:
Increase the value of the maxConnect attribute of the connection element in the server configuration file if desired.
REP-56062
The repositoryConn property is missing from jobStatusRepository.
Category:
Other
Cause:
The repositoryConn property is missing from the jobStatusRepository element specification in the server configuration file.
Action:
Add the repositoryConn property to the jobStatusRepository element in the server configuration file.
REP-56066
PL/SQL error {0} occurred when inserting job information into the database.
Category:
Other
Cause:
The indicated PL/SQL error occurred when inserting job information into the database.
Action:
Check the PL/SQL error manual for the appropriate action.
REP-56067
PL/SQL error {0} occurred when removing job information from the database.
Category:
Other
Cause:
The indicated PL/SQL error occurred when removing job information from the database.
Action:
Check the PL/SQL error manual for the appropriate action.
REP-56068
PL/SQL error {0} occurred when cleaning job information from the database.
Category:
Other
Cause:
The indicated PL/SQL error occurred when cleaning information from the database.
Action:
Check the PL/SQL error manual for the appropriate action.
REP-56069
An internal error occurred: No cache item for job {0}.
Category:
Other
Cause:
No cache item associated with the specified job was found.
Action:
Resubmit the job.
REP-56070
Error message for error {0} cannot be retrieved.
Category:
Other
Cause:
An attempt to retrieve the error message for the specified error code failed.
Action:
Report the problem to Oracle Support Services.
REP-56071
A security check failed with error message {0}.
Category:
Security
Cause:
A security check failed due to the stated reason.
Action:
Verify the privileges to run the report.
REP-56072
The administrator password in the secure server cannot be changed.
Category:
Other
Cause:
An attempt was made to change the Oracle Reports administrator password in secure mode.
Action:
Use Oracle Portal to change the Oracle Reports administrator password.
REP-56073
The password is invalid.
Category:
Other
Cause:
An attempt was made to change the Oracle Reports administrator password, but the old password provided was incorrect.
Action:
Provide the correct old password.
REP-56074
Additional privileges are required to perform the operation.
Category:
Other
Cause:
An attempt was made to perform an operation for which the user does not have privileges.
Action:
Only an Oracle Reports administrator can perform this operation.
REP-56075
The job cannot be reordered if not in the current queue.
Category:
Other
Cause:
An attempt was made to reorder the job in the past or scheduled job queue.
Action:
Reordering jobs can only be done in the current job queue.
REP-56079
The Oracle Portal module status cannot be updated.
Category:
Other
Cause:
An attempt to update the Oracle Portal module status failed.
Action:
Report the problem to Oracle Support Services.
REP-56081
The minEngine value ({0}) must be smaller than maxEngine ({1}).
Category:
Other
Cause:
The value of minEngine is larger than maxEngine in the server configuration file.
Action:
Change the value of minEngine or maxEngine so that minEngine &lt;= maxEngine.
REP-56082
The maxEngine value must be larger than minEngine ({0}) and initEngine ({1}).
Category:
Other
Cause:
The value of maxEngine is smaller than the values of minEngine and initEngine specified in the server configuration file.
Action:
Change the value of initEngine, minEngine, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
REP-56083
The Oracle Portal folder for job {0} cannot be created.
Category:
Other
Cause:
An attempt to create an Oracle Portal folder for job ouput failed.
Action:
Verify permission to create the folder.
REP-56084
The Oracle Portal folder has been created for job {0}.
Category:
Other
Cause:
This a notification message that the Oracle Portal folder has been created.
Action:
This is for information only, no action is needed.
REP-56085
The engineId {0} is invalid.
Category:
Other
Cause:
An invalid engineId attribute for the job element is specified in the server configuration file.
Action:
Check the engineId attribute in the server configuration file.
REP-56091
Job {0} is redirected to engine {1} on server {2}.
Category:
Other
Cause:
This a notification message that the specified job has been transferred to another server's engine.
Action:
This is for information only, no action is needed.
REP-56092
No class is defined for destination type {0}.
Category:
Other
Cause:
The class attribute is missing for the destination element in the server configuration file.
Action:
Specify the java class name for the destination element in the reports server configuration file.
REP-56093
Cached output for job {0} is no longer valid.
Category:
Other
Cause:
The cached output has been deleted and no longer valid for use.
Action:
Rerun the report.
REP-56095
Job {0} is waiting for the Oracle Portal folder to be created.
Category:
Other
Cause:
This a notification message that the specified job is waiting for the Oracle Portal folder to be created.
Action:
This is for information only, no action is needed.
REP-56096
Registration of the remote server is rejected because it does not participate in the cluster
Category:
Other
Cause:
Another Reports Server tried to register to this Reports Server, but this server does not participate in the cluster.
Action:
This is for information only, no action is needed.
REP-56097
Engine {0} callback timeout is reached.
Category:
Performance
Cause:
The Reports engine callback timeout value was reached.
Action:
Increase the value of the callbackTimeOut attribute for the engine element in the server configuration file.
REP-56098
Engine name {0} is invalid.
Category:
Other
Cause:
The engine name provided to the Reports Server is invalid.
Action:
Report the problem to Oracle Support Services.
REP-56099
The specified jobtype {0} is not supported.
Category:
Other
Cause:
The jobtype provided to the Reports Server is invalid.
Action:
Check the server configuration file to see what jobtypes are supported.
REP-56100
No engine is defined for jobtype {0}.
Category:
Other
Cause:
No engine is defined for specified jobtype in the server configuration file.
Action:
Define an engine for the specified jobtype in the server configuration file.
REP-56101
Reports Server cannot be shut down remotely when running in process mode.
Category:
Process
Cause:
An attempt was made to shut down Reports Server remotely when running in process mode.
Action:
Shut down the process in which Reports Server is running.
REP-56102
The proxy server has terminated unexpectedly.
Category:
Other
Cause:
The proxy server terminated unexpectedly.
Action:
Check whether the Reports Server tnsname is included in tnsnames.ora.
REP-56103
The proxy server callback has timed out.
Category:
Other
Cause:
The proxy server has not called back within an expected time.
Action:
Report the problem to Oracle Support Services.
REP-56104
The pluginParam element {0} is invalid due to {1}.
Category:
Other
Cause:
An invalid value for the pluginParam element is specified in the server configuration file, most likely the file or URL does not exist.
Action:
Verify that the file or URL that is specified for the pluginParam element in the server configuration file is valid.
REP-56105
Engine {0} died with error: {1}.
Category:
Other
Cause:
The specified engine died for the stated reason.
Action:
Fix the error and restart the server.
REP-56106
Engine {0} is destroyed due to timeout.
Category:
Other
Cause:
The specified Engine did not call back in the expected time.
Action:
Increase the value of the callbackTimeOut attribute of the engine element in the server configuration file if desired.
REP-56107
The specified environment ID {0} is invalid for Job Type {1} in the command line.
Category:
Other
Cause:
An invalid ENVID argument is specified in the command line.
Action:
Specify an ENVID that is already defined in the server configuration file (id attribute of environment elelemnt)or define a environment ID in the server configuration file and restart Reports Server.
REP-56108
No connStr property is defined for workflow notification in the server configuration file.
Category:
Configuration
Cause:
The connStr property is not specified for workflow nofication in the server configuration file.
Action:
Specify a valid connStr (in the format of database connection string) for workflow notification in the server configuration file.
REP-56109
Job {0} is terminated due to a connection timeout.
Category:
Other
Cause:
No activity was detected for the specified job in the timeout period. Either the client has terminated unexpectedly, the client program has hung, or the client program took too long handling other processes.
Action:
Check client program status, or if needed, increase the idleTimeOut attribute for connection element in the server configuration file.
REP-56110
The security repository Oracle Portal cannot be connected.
Category:
Security
Cause:
An attempt to connect to Oracle Portal failed. Oracle Portal is probably down, or an invalid connection string was specified.
Action:
Verify that Oracle Portal is up, and the connection string is correct.
REP-56111
Bad or damaged persist file is backed up as: {0}.
Category:
Other
Cause:
Reports Server shut down abnormally while writing to the indicated file.
Action:
Resubmit the lost current and scheduled jobs as information about past, current, and scheduled jobs might be lost. Provide the backed up file when reporting the problem to Oracle Support Services.
REP-56112
Backup of the damaged persist file {0} cannot be created.
Category:
Other
Cause:
The persist file is damaged. Reports Server encountered an error while creating a backup.
Action:
Rename the file manually, then restart Reports Server. Resubmit all current and scheduled jobs as information about past, current, and scheduled jobs will be lost.
REP-56113
The JSP report cannot be resubmitted.
Category:
Other
Cause:
JSP reports are not stored in the Reports Server persistence cache so they cannot be rerun.
Action:
Submit a new JSP report to the Reports Server.
REP-56114
The attempt to bind to the naming server failed.
Category:
Other
Cause:
The naming server may be down.
Action:
Start the naming server.
REP-56115
Engine {0} does not exist.
Category:
Other
Cause:
An attempt was made to access or kill an engine that does not exist.
Action:
Provide the correct engine name.
REP-56116
A relative path for desname {0} is not allowed when destype=file.
Category:
Other
Cause:
A relative path was specified for desname when destype=file, which is not allowed.
Action:
Specify the absolute path for desname.
REP-56117
JOBTYPE {0} is invalid.
Category:
Other
Cause:
An invalid JOBTYPE argument was specified in the command line.
Action:
Correct the JOBTYPE argument and resubmit the job.
REP-56118
The report is aborted upon user request.
Category:
Other
Cause:
This a notification message that the current job was cancelled.
Action:
No action required.
REP-56119
An invalid value {0} is specified for attribute {1}.
Category:
Other
Cause:
The specified value in the server configuration file is invalid for the attribute.
Action:
Refer to the Publishing Reports to the Web manual for information about the attribute and valid values.
REP-56120
A syntax error exists on the command line for the Reports Server.
Category:
Other
Cause:
The syntax for one or more arguments on the command line is invalid.
Action:
Refer to the Publishing Reports to the Web manual for correct command-line argument syntax.
REP-56121
Authentication failed.
Category:
Security
Cause:
The AUTHID specified was invalid.
Action:
Specify a correct AUTHID.
REP-56122
Reports Server {0} cannot be connected.
Category:
Other
Cause:
An attempt to connect to Reports Server failed.
Action:
Verify that Reports Server is running and that the Reports Server name is correct.
REP-56123
An insufficient number of ports is assigned for Reports Server and engines in the config file.
Category:
Ports
Cause:
The number of ports assigned is less than the number required to start server and engines.
Action:
Increase the number of ORB ports in the server configuration file.
REP-56124
Report Server failed to start; port {0} specified in the server config file may already be in use.
Category:
Ports
Cause:
The ORB port specified in the server configuration file is not available for the Reports Server.
Action:
Specify a free port.
REP-56125
The ORBPorts property value in the config file is invalid.
Category:
Other
Cause:
The ORB port specified in the server configuration file is not in a valid format.
Action:
Specify proper integer values for ORB ports either as a range (4000-6000), or comma separated values (4000,5000,6000).
REP-56126
The server config file {0} cannot be parsed. {1}.
Category:
Other
Cause:
An attempt to parse the server config file failed due to invalid XML syntax.
Action:
Correct the server configuration file and start the Reports Server.
REP-56127
The {0} element cannot be decrypted.
Category:
Other
Cause:
An attempt to decrypt the indicated element failed.
Action:
Verify that the encrypted property is set properly for the element in the server configuration file.
REP-56128
The {0} destination cannot be initialized. Nested exception: {1}.
Category:
Other
Cause:
An attempt to initialize the indicated destination failed.
Action:
Check and correct the destination element in the server configuration file.
REP-56129
Permission is denied for {0}.
Category:
Other
Cause:
An attempt to run the report failed due to lack of permissions.
Action:
Change the parameter values or contact the Oracle Reports administrator.
REP-56130
Permission to run Web command {0} is not granted.
Category:
Other
Cause:
An attempt to run the indicated Web command failed due to lack of permissions.
Action:
Contact the Oracle Reports administrator.
REP-56131
Permission to run Web command {0} is not granted.
Category:
Other
Cause:
An attempt to run the indicated Web command failed due to lack of permissions.
Action:
Contact the Oracle Reports administrator.
REP-56132
Access is denied to the report definition file.
Category:
Other
Cause:
An attempt to read the report definition file failed due to lack of permissions.
Action:
Contact the Oracle Reports administrator to obtain access privileges.
REP-56133
Access is denied to write to the specified location.
Category:
Other
Cause:
An attempt to write to the folder failed due to lack of permissions.
Action:
Change the desname location or contact the Oracle Reports administrator.
REP-56134
Server config file cannot be found.
Category:
Other
Cause:
The server configuration file rwserver.conf was not found.
Action:
Contact the Oracle Reports administrator.
REP-56135
Reports Server is not started using PCS.
Category:
Other
Cause:
The Reports Server was not started using PCS in the MAS environment.
Action:
Start the server using PCS.
REP-56136
An error occurred retrieving the environment required to spawn the engine.
Category:
Other
Cause:
An attempt to retrieve needed environment variables failed.
Action:
Contact the Oracle Reports administrator.
REP-56137
The minEngine value must be smaller than maxEngine {0} and initEngine {1}.
Category:
Other
Cause:
The value of minEngine is larger than maxEngine and initEngine in the server configuration file.
Action:
Change the value of initEngine, minEngin, or maxEngine so that minEngine &lt;= initEngine &lt;= maxEngine.
REP-56138
Job {0} has completed execution.
Category:
Other
Cause:
An attempt was made to kill a job that was running or scheduled.
Action:
Check the job status. Only jobs that are running or scheduled can be killed.
REP-56139
The requested operation is unauthorized.
Category:
Other
Cause:
An attempt to perform an operation failed due to lack of proper authorization.
Action:
Contact the Oracle Reports administrator.
REP-57000
An internal error occurred in the Oracle Reports API:
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-57001
The in-process server is not initialized.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-57002
An attempt to load {0} failed.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-57003
A column data type {0} is not valid.
Category:
Data
Cause:
A column in the report contains an unsupported data type.
Action:
Use only supported datatypes. Refer to the Oracle Reports documentation for supported datatypes.
REP-57004
The value of column {0} cannot be retrieved, cursor out of range in cache.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-57005
The value of column {0} cannot be retrieved in cache.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-57052
An internal error occurred in the in-process server.
Category:
Other
Cause:
An internal error occurred.
Action:
For assistance, contact Oracle Support Services.
REP-58000
Attribute value {0} for attribute name {1} in tag {2} is invalid.
Category:
Other
Cause:
The value of the attribute for the JSP tag is invalid.
Action:
Verify that the attribute value is valid. Refer to the Reference&gt;Oracle Reports JSP tags section of the Oracle Reports online Help.
REP-58001
Either tag attribute {0} or {1} must exist in tag {2}.
Category:
Other
Cause:
One of the specified two optional attributes must exist.
Action:
Specify at least one of the two attributes.
REP-58002
A cursor for group {0} cannot be created.
Category:
Other
Cause:
A cursor object cannot be created for a group in an rw:foreach or an rw:graph tag.
Action:
Verify that the group name is valid.
REP-58004
Format trigger {0} cannot be run.
Category:
Other
Cause:
Failed to run a PL/SQL format trigger in an rw:field tag.
Action:
Verify that the name of the format trigger is correct.
REP-58005
There is no current report for group {0}.
Category:
Other
Cause:
There is no report object for the rw:foreach tag.
Action:
Verify that a report object is created by enclosing the report block inside the rw:report tag.
REP-58006
There is no current report for layout object {0}.
Category:
Other
Cause:
There is no report object for the rw:include tag.
Action:
Verify that a report object is created by enclosing the report block inside the rw:report tag.
REP-58008
There is no current report for column {0}.
Category:
Other
Cause:
There is no report object for the rw:field or rw:getValue tags.
Action:
Verify that a report object is created by enclosing the report block inside the rw:report tag.
REP-58009
A cursor containing column {0} cannot be found.
Category:
Other
Cause:
The column does not belong to any of the enclosing cursors.
Action:
Verify that the column name is valid.
REP-58010
Data type {0} is not supported.
Category:
Data
Cause:
Invalid dataType attribute (NOT USED CURRENTLY) in rw:getValue.
Action:
Use any of the supported data types.
REP-58011
ID {0} in {1} tag is used in a previous {2} tag.
Category:
Other
Cause:
The value for the ID attribute is not unique.
Action:
Use a unique ID value.
REP-58012
Only one rw:report tag is allowed in a JSP report.
Category:
Other
Cause:
There is more than one rw:report tag in the JSP report.
Action:
Verify that there is only one rw:report tag in the JSP report.
REP-58013
Only one rw:objects tag is allowed in a JSP report.
Category:
Other
Cause:
More than one rw:objects tags exists in the JSP report.
Action:
Verify that there is only one rw:objects tag in the JSP report.
REP-58014
rw:objects must be the first JSP tag in rw:report body.
Category:
Other
Cause:
A JSP tag other than rw:object is the first Reports JSP tag in the body of the rw:report tag.
Action:
Verify that there is only one rw:objects tag in the body of the rw:report tag. The rw:objects tag must be the first Reports JSP tag inside the body of the rw:report tag.
REP-58015
breakLevel {0} in the rw:field tag does not match the ID of any enclosing rw:foreach.
Category:
Other
Cause:
The value of a breakLevel attribute from an rw:field tag does not match the ID of any enclosing rw:foreach tags.
Action:
Verify that the value for the breakLevel attribute is valid.
REP-58016
The formatMask {0} attribute is not valid.
Category:
Other
Cause:
The value of a formatMask attribute from an rw:field or an rw:getValue tag is invalid.
Action:
Verify that the value for the formatMask attribute is valid.
REP-58017
FormatTrigger {0} in rw:field tag is not a valid PL/SQL program unit.
Category:
Other
Cause:
The value of the formatTrigger attribute from an rw:field tag is not a program unit name, or it has an invalid signature.
Action:
Verify that the value for the formatTrigger attribute is valid.
REP-58018
Column name {0} in {1} of rw:graph is not valid.
Category:
Other
Cause:
A column name specified in one of the attributes of the rw:graph tag is not valid.
Action:
Verify that the column name is valid. Refer to the Reference&gt;Oracle Reports JSP tags section of the Oracle Reports online Help for the correct syntax of the attributes.
REP-58019
Tag {0} (ID {1}) is not in rw:report body.
Category:
Other
Cause:
A Reports JSP tag is not in a rw:report tag's body.
Action:
Add the tag in a rw:report body.
REP-58100
An error occurred starting the internal Web server at port {0}. Error: {1}.
Category:
Ports
Cause:
Errors occurred while starting the internal Web server.
Action:
Verify that the port is not in use. Also check the .log files and log directory under (docroot)/port# for more information. Unless specified from the command line, the docroot should be located at under $REPORTS_TMP/docroot.
REP-58101
An error occurred stopping the internal Web server: {0}.
Category:
Other
Cause:
Errors were encountered while stopping the internal Web server.
Action:
Check the .log files and config directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
REP-58102
An error occurred sending request {0} to the internal Web server: {1}.
Category:
Requests/Responses
Cause:
Errors were encountered when sending the JSP to the internal Web server.
Action:
Check the .log files and the log directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
REP-58103
An error occurred configuring the internal Web server: {0}.
Category:
Other
Cause:
Errors were encountered when configuring the configuration files from the internal Web server.
Action:
Check the .log files and config directory under (docroot)/port# for more information. Unless specified on the command line, the docroot is located in the $REPORTS_TMP/docroot directory.
REP-58104
Port {0} is in use.
Category:
Ports
Cause:
The port specified from the command line is in use.
Action:
Specify a different port, or allow Reports to choose a free port.
REP-58105
A free port within the {0} to {1} range cannot be automatically found for the internal Web server.
Category:
Ports
Cause:
All ports within the range appear to be in use.
Action:
Specify a free port to use from the command line.
REP-58106
Begin port {0} must be less than end port {1}.
Category:
Ports
Cause:
The begin port is greater or equal to end port.
Action:
Specify a begin port less than end port from the command line.
REP-58107
Port numbers must be within range 1-65536.
Category:
Ports
Cause:
The port used is not within the specified range.
Action:
Specify a free port in the specified range from the command line.
REP-58108
HTML tags are not allowed: {0}.
Category:
Other
Cause:
HTML tags were specified in the query string.
Action:
Remove the HTML tags in the query string and rerun the report.
REP-58109
Web server cannot be created.
Category:
Other
Cause:
A problem was encountered while attempting to create the Web server.
Action:
Contact the system administrator.
REP-60003
An error occurred retrieving the environment required to spawn the engine.
Category:
Other
Cause:
Reports Server was unable to retrieve the current environment setting prevailing on the system.
Action:
Ensure that rwu90.dll is installed and available in the system path on Windows. On UNIX, ensure that librwu90.so is installed and available in the LD_LIBRARY_PATH environment variable.
REP-62000
Connection class {0} cannot be loaded.
Category:
Other
Cause:
The connection class mentioned in the configuration file jdbcpds.conf for the selected driver is invalid.
Action:
Ensure that a valid driver connection class is specified in the configuration file jdbcpds.conf and that it is available.
REP-62001
No entry is present for the driver {0} in the jdbcpds.conf file.
Category:
Configuration
Cause:
The driver used in query is not specified in the configuration file jdbcpds.conf.
Action:
Ensure that the entry for the required driver along with the related driver information is specified in the configuration file jdbcpds.conf.
REP-62002
The data source cannot be connected.
Category:
Data
Cause:
The connection information is invalid.
Action:
Ensure that the username, password, database, and driver type are all valid.
REP-62003
Configuration file jdbcpds.conf cannot be found.
Category:
Configuration
Cause:
The configuration file jdbcpds.conf is not found in the reports/conf directory.
Action:
Ensure that the configuration file jdbcpds.conf is available in the reports/conf directory.
REP-62004
A parsing error occurred in the configuration file jdbcpds.conf. Number of errors: {0}
Category:
Configuration
Cause:
The XML section in the configuration file jdbcpds.conf does not conform with its inline DTD.
Action:
Ensure that the XML section in jdbcpds.conf refers to the correct inline DTD.
REP-62005
An error occurred on line number {0}.
Category:
Other
Cause:
An error was found on the specified line of the configuration file jdbcpds.conf.
Action:
Correct the error on the specified line.
REP-62006
The lexical parameter {0} used in the query is invalid.
Category:
Other
Cause:
The lexical parameter used in the query or procedure is invalid.
Action:
Ensure that the query or procedure uses valid lexical parameters. Create new parameters if they are not available.
REP-62007
A SQL error occurred: {0}.
Category:
Other
Cause:
The data source has reported this SQL syntax error in the specified query or procedure.
Action:
Ensure that the syntax of the query or procedure is valid. Refer to the documentation of the specific data source.
REP-62008
The query or procedure for the specified data source is invalid.
Category:
Data
Cause:
The syntax of the query or procedure is invalid for the specified data source.
Action:
Ensure that the syntax of the query or procedure is valid. Refer to the documentation of the specific data source.
REP-62009
The reference parameter value is invalid.
Category:
Other
Cause:
The value of the reference parameter is invalid.
Action:
Verify that the reference column types and values are correct.
REP-62010
A query or procedure is missing.
Category:
Other
Cause:
The query or procedure text field is empty.
Action:
Type a valid query or procedure in the text area.
REP-62011
The database URL {0} is invalid.
Category:
Other
Cause:
Invalid database URL.
Action:
Verify the specified database name and the selected driver type.
REP-62012
Either the number of columns or the types of columns does not match the query definition.
Category:
Other
Cause:
The data fetched does not match the number of columns or the column types that are specified in the query definition.
Action:
Verify that both the number of columns and the column types match the query definition.
REP-62013
The column type {0} used in the query/procedure is not supported by the Reports JDBC query.
Category:
Other
Cause:
This column type is not supported by the Reports JDBC query interface.
Action:
Ensure that only column types that are supported by the Reports JDBC query interface are used. Refer to the JDBC specification and the Reports documentation for supported types.
REP-62014
The inline DTD section of the configuration file jdbcpds.conf has been modified.
Category:
Configuration
Cause:
The format of the inline DTD section in the configuration file jdbcpds.conf has been altered.
Action:
If the DTD format is modified, ensure that the configuration file is valid as per the JDBCPDS requirement.
REP-62015
The sign-on parameter {0} is invalid.
Category:
Other
Cause:
The specified sign-on parameter for the query or procedure is invalid.
Action:
Ensure that the sign-on parameter is available and valid for the JDBC query type in the report.
REP-62016
The sign-on parameter value {0} is invalid.
Category:
Other
Cause:
The specified connect string for this sign-on parameter is invalid.
Action:
Ensure that the specified connect string for this sign-on parameter is valid for the selected driver.
REP-62017
A reference parameter of type Date is not supported by the JDBC driver used.
Category:
Other
Cause:
The driver used to connect to database does not support the Date data type as reference parameter.
Action:
Use the String data type for the reference parameter or use a different JDBC driver that supports the Date data type as reference parameter.
REP-62200
No image exists for the specified ID {0}
Category:
Other
Cause:
The image ID specified does not map to an existing image object in the store.
Action:
For assistance, contact Oracle Support Services.
REP-62201
The image source is invalid
Category:
Other
Cause:
The image source is not valid.
Action:
For assistance, contact Oracle Support Services.
REP-62202
Unsupported image format
Category:
Other
Cause:
The format of the image used is not supported.
Action:
Ensure that the report uses a supported image format as specified in the Oracle Reports documentation.
REP-62203
Internal error reading the image {0}
Category:
Other
Cause:
The image data appears to be corrupt or invalid.
Action:
Ensure that the image is valid. For assistance, contact Oracle Support Services.
REP-62204
Internal error writing the image {0}
Category:
Other
Cause:
There was an internal error writing the image to the output stream.
Action:
For assistance, contact Oracle Support Services.
REP-62205
Internal error during color reduction
Category:
Other
Cause:
An error occurred doing color reduction on GIF images.
Action:
Use a diffent GIF image with lesser colors or chose another image format.
REP-62206
The input image used is corrupt or invalid
Category:
Other
Cause:
The image data appears to be corrupt or invalid.
Action:
Ensure that the image is valid.
REP-62207
Encountered an unsupported version of GIF image
Category:
Other
Cause:
This GIF version is not supported.
Action:
Ensure that the GIF images used adhere to the standards specified in the Oracle Reports documentation.
REP-62350
URL {0} is invalid.
Category:
Other
Cause:
The location pointed to by the URL appears to be invalid.
Action:
Ensure that the location pointed to by the URL is valid.
REP-62351
The proxy setting specified in proxyinfo.xml will be not be effective.
Category:
Other
Cause:
The proxy setting was ignored due to an invalid configuration in the proxyinfo.xml file.
Action:
Ensure that the proxy setting in proxyinfo.xml is correct.
REP-62352
The FTP proxy server specified is not responding : {0}.
Category:
Other
Cause:
The proxy specified in the proxyinfo.xml file does not support SOCKS protocol.
Action:
Ensure that the proxy supports SOCKS protocol.
REP-62353
The destination file name is missing.
Category:
Other
Cause:
Destination file name missing in the desname argument.
Action:
Specify a valid destination file name.
REP-62354
The directory specified is invalid.
Category:
Other
Cause:
Invalid directory is specified in the desname argument.
Action:
Specify a valid directory path.
REP-62370
URL {0} is invalid.
Category:
Other
Cause:
The location pointed to by the URL appears to be invalid.
Action:
Ensure that the location pointed by the URL is valid.
REP-62371
The proxy setting specified in proxyinfo.xml is not be effective.
Category:
Other
Cause:
The proxy setting was ignored due to an invalid configuration in the proxyinfo.xml file.
Action:
Ensure that the proxy setting in proxyinfo.xml is correct.
REP-63000
No URL specified for {0}
Category:
Other
Cause:
There was no URL specified for either the data definition or the data source.
Action:
Specify a URL for both the data definition and the data source.
REP-63001
Invalid stream in the Data Definition URL {0}
Category:
Data
Cause:
The Data Stream pointed to by the URL appears to be invalid.
Action:
Ensure that the XML Stream pointed to by the URL is valid.
REP-63002
URL specified has an invalid XML stream: {0}
Category:
Other
Cause:
The URL appears to have invalid XML stream.
Action:
Ensure that the XML stream pointed to by the URL contains valid XML.
REP-63003
URL {0} read error
Category:
Other
Cause:
Could not access the specified URL. A timeout occurred while accessing the URL.
Action:
Ensure that the URL is accessible and check that the proxy information in the xmlpds.conf file is correct.
REP-63004
Generic error while parsing the URL stream {0}
Category:
Other
Cause:
The data stream pointed to by the URL appears to be invalid.
Action:
Ensure that the XML stream pointed to by the URL is valid.
REP-63005
The Inline DTD section of xmlpds.conf file has been modified
Category:
Configuration
Cause:
The Inline DTD section of the configuration file xmlpds.conf has been modified.
Action:
Ensure that the configuration file is still valid, per the XMLPDS requirement.
REP-63006
Invalid reference parameter value
Category:
Other
Cause:
The value of the reference parameter is invalid.
Action:
Verify that the types and values of the referenced columns are correct.
REP-63007
Configuration file xmlpds.conf not found
Category:
Configuration
Cause:
The configuration file xmlpds.conf was not found in the reports/conf directory.
Action:
Ensure that the configuration file xmlpds.conf is located in the reports/conf directory.
REP-63008
Parsing error in the xmlpds.conf configuration file Number of errors: {0}
Category:
Configuration
Cause:
The XML section in the xmlpds.conf file does not conform with the corresponding inline DTD.
Action:
Ensure the XML section in the xmlpds.conf file conforms with the corresponding inline DTD.
REP-63009
The proxy setting specified in xmlpds.conf will be not be effective
Category:
Configuration
Cause:
The proxy setting was ignored due to an invalid configuration in the xmlpds.conf file.
Action:
Ensure that the proxy setting in the configuration file xmlpds.conf is correctly specified.
REP-63500
No URL is specified for data source {0}/
Category:
Data
Cause:
There was no URL specified for the data source.
Action:
Specify a URL for the data source.
REP-63501
The specified URL {0} is not compatible with the file format {1} at line number {2}.
Category:
Other
Cause:
The URL appears to have invalid content.
Action:
Ensure that the content pointed to by the URL is a valid file format.
REP-63502
The data is invalid.
Category:
Data
Cause:
Content is not compatible with the file format selected.
Action:
Ensure that the text is valid for the file format selected.
REP-63503
Either the number of columns or the type of columns does not match the query definition.
Category:
Other
Cause:
The data fetched does not match the number of columns or the column types that are specified in the query definition.
Action:
Verify that both the number of columns and the column types match the query definition.
REP-63504
A read error occurred in accessing URL {0}.
Category:
Other
Cause:
Could not access the specified URL. A timeout occurred while accessing the URL.
Action:
Ensure that the URL is accessible and check that the proxy information in the textpds.conf file is correct.
REP-63505
The Inline DTD section of textpds.conf has been modified.
Category:
Configuration
Cause:
The Inline DTD section of the configuration file textpds.conf has been modified.
Action:
Ensure that the configuration file is still valid, per the TextPDS requirement.
REP-63506
The reference parameter is invalid.
Category:
Other
Cause:
The reference parameter is invalid.
Action:
Verify that the name, types, and values of the referenced columns are correct.
REP-63507
The configuration file textpds.conf cannot be found.
Category:
Configuration
Cause:
The configuration file textpds.conf was not found in the reports/conf directory.
Action:
Ensure that the configuration file textpds.conf is located in the reports/conf directory.
REP-63508
A parsing error occurred in textpds.conf. Number of errors: {0}.
Category:
Other
Cause:
The XML section in the textpds.conf file does not conform with the corresponding inline DTD.
Action:
Ensure the XML section in the textpds.conf file conforms with the corresponding inline DTD.
REP-63509
The proxy setting specified in textpds.conf is invalid.
Category:
Configuration
Cause:
The proxy setting was ignored due to an invalid configuration in the textpds.conf file.
Action:
Ensure that the proxy setting in the configuration file textpds.conf is correctly specified.
REP-63510
No fileFormat is specified in textpds.conf.
Category:
Other
Cause:
The entry for fileFormat in textpds.conf is missing.
Action:
Ensure that at least one fileFormat element is specified in the textpds.conf.
REP-63511
The fileFormat specification is invalid.
Category:
Other
Cause:
The entry for fileFormat in textpds.conf is invalid.
Action:
Ensure that fileFormat is specified per the DTD of textpds.conf.
REP-63512
No entry is present for fileFormat {0} in textpds.conf.
Category:
Other
Cause:
The fileFormat used in the query is not defined in textpds.conf.
Action:
Ensure that the entry for the required fileFormat along with the column information is specified in textpds.conf.
REP-63513
The Serialized XML section of the saved report is invalid.
Category:
Other
Cause:
The Serialized XML section has been modified.
Action:
Ensure that Serialized XML section is specified per the TextPDS format.
REP-63514
The column type {0} used in the query is not supported by a Text query.
Category:
Other
Cause:
This column type is not supported by the Text query interface.
Action:
Ensure that only column types that are supported by the Text query interface are used. Refer to the TextPDS specification and the Oracle Reports documentation for supported types.
REP-63515
The data in log file {0} is not according to the date pattern {1} specified in the config file.
Category:
Data
Cause:
The data in the log file is not valid according to the date pattern specified in the config file.
Action:
Ensure that data in the log file is specified according to the date pattern.
REP-64000
No Oracle Home is specified.
Category:
Other
Cause:
ORACLE_HOME is missing in the command line.
Action:
Specify ORACLE_HOME=&lt;oracle_home_dir&gt; in the command line.
REP-64001
The Oracle Reports Bridge failed to start.
Category:
Other
Cause:
The Oracle Reports Bridge failed to start.
Action:
Check log file for detailed message and take appropriate action.
REP-64002
The Oracle Reports Bridge initialization failed {0}.
Category:
Other
Cause:
The Oracle Reports Bridge initialization failed.
Action:
Check the actual message and take appropriate action.
REP-64003
The local port is not set. One-way Oracle Reports Bridge is started.
Category:
Ports
Cause:
One-way Oracle Reports Bridge is started.
Action:
No action needed. Set local port to start two-way bridge if needed.
REP-64004
AUTHID is not specified.
Category:
Security
Cause:
AUTHID argument is not specified in command line.
Action:
Specify AUTHID=&lt;username&gt;/&lt;password&gt; in the command line.
REP-64005
Authentication failed.
Category:
Security
Cause:
The AUTHID specified was invalid.
Action:
Specify a correct AUTHID.
REP-64006
The Oracle Reports Bridge shutdown failed.
Category:
Other
Cause:
An attempt to shut down The Oracle Reports Bridge failed.
Action:
Check the trace for detailed message and take appropriate action.
REP-64009
The Oracle Reports Bridge is already running.
Category:
Other
Cause:
Another Oracle Reports Bridge is already running with the same port.
Action:
Change the port in the config file and start again.
REP-64010
The local listener failed to start.
Category:
Other
Cause:
The open socket could not be opened.
Action:
Check socket is available and usable.
REP-64011
Request {0} cannot be served.
Category:
Requests/Responses
Cause:
Unable to serve the Oracle Reports Bridge request.
Action:
Check the actual message and take appropriate action.
REP-64012
A fatal error {0} occurred. Restart the Oracle Reports Bridge.
Category:
Other
Cause:
The Oracle Reports Bridge is not able to serve any request.
Action:
Restart the Oracle Reports Bridge.
REP-64013
The Oracle Reports Bridge failed to serve the request {0}.
Category:
Requests/Responses
Cause:
An internal error occurred.
Action:
Check the actual message; the Oracle Reports Bridge may recover from this error.
REP-64014
The Oracle Reports Bridge name is not specified.
Category:
Other
Cause:
The NAME=&lt;bridgename&gt; argument is missing in the command line.
Action:
Specify NAME=&lt;bridgename&gt; in the command line.
REP-64015
The command is invalid.
Category:
Other
Cause:
Invalid command-line argument.
Action:
Check command-line arguments.
REP-64016
Cannot connect to the Oracle Reports Bridge {0}.
Category:
Other
Cause:
The Oracle Reports Bridge is not running on specified port.
Action:
The Oracle Reports Bridge may be down. Or check the Bridge port in Bridge config file and try again.
REP-64017
The Oracle Reports Bridge config file is not found.
Category:
Other
Cause:
Configuration file rwbridge.conf is not found.
Action:
Contact the Oracle Reports administrator.
REP-64018
The Oracle Reports Bridge is not started using PCS.
Category:
Other
Cause:
The Oracle Reports Bridge is not started using PCS in the MAS environment.
Action:
Start the Oracle Reports Bridge using PCS.
REP-65001
Communication error {0} occurred.
Category:
Other
Cause:
A network IO error occurred.
Action:
Check the actual message and take appropriate action.
REP-65002
The communication channel {0} cannot be initialized.
Category:
Other
Cause:
Multicast initialization failed.
Action:
Check the actual message and take appropriate action.
REP-65003
The request timed out.
Category:
Requests/Responses
Cause:
Waiting for a response from the server timed out.
Action:
No action required. If all retries fail, increase the timeout value in the network config file.
REP-65004
The naming server cannot be bound.
Category:
Other
Cause:
Naming service may be down.
Action:
Start the naming service and try again.
REP-65005
The network config file cannot be found.
Category:
Network
Cause:
rwnetwork.conf is not found.
Action:
Contact the Oracle Reports administrator.
REP-67000
Creation of Reports Server instance {0} on machine {1} failed
Category:
Other
Cause:
Attempt to create reports server instance failed
Action:
Check the actual error message and take appropriate action
REP-67001
Removal of Reports Server instance {0} failed
Category:
Other
Cause:
Attempt to remove reports server instance failed
Action:
Check the actual error message and take appropriate action
REP-67002
Unable to register reports server configuration mbeans
Category:
Other
Cause:
Reports server configuration mbeans registration failed
Action:
For assistance, contact Oracle Support Services
REP-67004
Validation of component failed: {0}
Category:
Other
Cause:
Component is not successfully validated for attempted operation
Action:
Check the actual error message and take appropriate action
REP-67100
Unable to calculate checksum of file {0}
Category:
Other
Cause:
Checksum calculation of file failed
Action:
For assistance, contact Oracle Support Services
REP-67101
Error in replicating reports server configuration
Category:
Other
Cause:
Replication of configuration from AdminServer machine to managed server failed
Action:
For assistance, contact Oracle Support Services
REP-67200
Creation of Reports Tools instance {0} on machine {1} failed
Category:
Other
Cause:
Attempt to create reports tools instance failed
Action:
Check the actual error message and take appropriate action
REP-67201
Removal of Reports Tools instance {0} failed
Category:
Other
Cause:
Attempt to remove reports tools instance failed
Action:
Check the actual error message and take appropriate action
REP-67202
Unable to register reports tools configuration mbeans
Category:
Other
Cause:
Reports tools configuration mbeans registration failed
Action:
For assistance, contact Oracle Support Services
REP-67204
Validation of component failed: {0}
Category:
Other
Cause:
Component is not successfully validated for attempted operation
Action:
Check the actual error message and take appropriate action
REP-67300
Unable to calculate checksum of file {0}
Category:
Other
Cause:
Checksum calculation of file failed
Action:
For assistance, contact Oracle Support Services
REP-67301
Error in replicating reports tools configuration
Category:
Other
Cause:
Replication of configuration from AdminServer machine to managed server failed
Action:
For assistance, contact Oracle Support Services
REP-67400
Creation of Reports Bridge instance {0} on machine {1} failed
Category:
Other
Cause:
Attempt to create reports bridge instance failed
Action:
Check the actual error message and take appropriate action
REP-67401
Removal of Reports Bridge instance {0} failed
Category:
Other
Cause:
Attempt to remove reports bridge instance failed
Action:
Check the actual error message and take appropriate action
REP-67402
Unable to register reports bridge configuration mbeans
Category:
Other
Cause:
Reports bridge configuration mbeans registration failed
Action:
For assistance, contact Oracle Support Services
REP-67404
Validation of component failed: {0}
Category:
Other
Cause:
Component is not successfully validated for attempted operation
Action:
Check the actual error message and take appropriate action
REP-67500
Unable to calculate checksum of file {0}
Category:
Other
Cause:
Checksum calculation of file failed
Action:
For assistance, contact Oracle Support Services
REP-67501
Error in replicating reports bridge configuration
Category:
Other
Cause:
Replication of configuration from AdminServer machine to managed server failed
Action:
For assistance, contact Oracle Support Services
REP-67550
Component {0} already exists in domain
Category:
Other
Cause:
Component with given name already exists in domain
Action:
Provide a unique component name
REP-67551
Component {0} cannot be removed because it is in state {1}
Category:
Other
Cause:
Component is not in following states : SHUTDOWN, FAILED_NOT_RESTARTABLE, FAILED
Action:
Shutdown the component
REP-67552
Component is not configured to OID
Category:
Other
Cause:
Component is not associated to OID
Action:
Associate component to OID
REP-67600
Connect to a WebLogic server before using this command
Category:
Other
Cause:
Not connected to Weblogic server
Action:
Connect to Weblogic server using appropriate WLST command
REP-67601
createReportsServerInstance command failed
Category:
Other
Cause:
Attempt to create reports server instance failed
Action:
Check the actual error message and take appropriate action
REP-67602
deleteReportsServerInstance command failed
Category:
Other
Cause:
Attempt to remove reports server instance failed
Action:
Check the actual error message and take appropriate action
REP-67603
Argument {0} is not valid
Category:
Other
Cause:
Invalid argument provided to WLST command
Action:
Provide correct argument to WLST command
REP-67604
The following required arguments are missing :{0}
Category:
Other
Cause:
Required argument not provided to WLST command
Action:
Provide required argument to WLST command
REP-67608
associateStandaloneServer command failed
Category:
Other
Cause:
Association of reports server to OID failed
Action:
Check the actual error message and take appropriate action
REP-67610
dissociateStandaloneServer command failed
Category:
Other
Cause:
Dissociation of reports server from OID failed
Action:
Check the actual error message and take appropriate action
REP-67612
associateInprocessServer command failed
Category:
Other
Cause:
Association of reports server to OID failed
Action:
Check the actual error message and take appropriate action
REP-67614
dissociateInprocessServer command failed
Category:
Other
Cause:
Dissociation of reports server from OID failed
Action:
Check the actual error message and take appropriate action
REP-67700
Connect to a WebLogic server before using this command
Category:
Other
Cause:
Not connected to Weblogic server
Action:
Connect to Weblogic server using appropriate WLST command
REP-67701
createReportsToolsInstance() failed
Category:
Other
Cause:
Attempt to create reports tools instance failed
Action:
Check the actual error message and take appropriate action
REP-67702
deleteReportsToolsInstance() failed
Category:
Other
Cause:
Attempt to remove reports tools instance failed
Action:
Check the actual error message and take appropriate action
REP-67703
Argument {0} is not valid
Category:
Other
Cause:
Invalid argument provided to WLST command
Action:
Provide correct argument to WLST command
REP-67704
The following required arguments are missing :{0}
Category:
Other
Cause:
Required argument not provided to WLST command
Action:
Provide required argument to WLST command
REP-67800
Connect to a WebLogic server before using this command
Category:
Other
Cause:
Not connected to Weblogic server
Action:
Connect to Weblogic server using appropriate WLST command
REP-67801
createReportsBridgeInstance() failed
Category:
Other
Cause:
Attempt to create reports bridge instance failed
Action:
Check the actual error message and take appropriate action
REP-67802
deleteReportsBridgeInstance() failed
Category:
Other
Cause:
Attempt to remove reports bridge instance failed
Action:
Check the actual error message and take appropriate action
REP-67803
Argument {0} is not valid
Category:
Other
Cause:
Invalid argument provided to WLST command
Action:
Provide correct argument to WLST command
REP-67804
The following required arguments are missing :{0}
Category:
Other
Cause:
Required argument not provided to WLST command
Action:
Provide required argument to WLST command
REP-67900
Reports 12c Application not found deployed for managed server {0}
Category:
Other
Cause:
Reports 12c Application not found deployed for managed server
Action:
Start reports managed servers once so that reports 12c applications get automatically deployed. Then shutdown managed servers.
REP-67901
Component of type {0} and name {1} does not exist in 12c domain
Category:
Other
Cause:
Reports system component not found in 12c domain
Action:
Use WLST command to create reports component in 12c domain
REP-67902
Config file not found : {0}
Category:
Other
Cause:
Action:
Reports installation is corrupted
REP-67903
Topology document parsing error
Category:
Other
Cause:
Action:
Reports 11g domain is corrupted
REP-67904
Topology document not found : {0}
Category:
Other
Cause:
Reports 11g domain is corrupted or is already upgraded
Action:
Contact the system administrator
REP-80001
An internal error occurred.
Category:
Other
Cause:
Unexpected internal exception.
Action:
For assistance, contact Oracle Support Services.
REP-80002
The report object is invalid.
Category:
Other
Cause:
The report object is invalid, possibly invalid object handle, or an already deleted object.
Action:
Discard this object handle and get a new one.
REP-80003
The report object name is invalid.
Category:
Other
Cause:
The name does not follow report object naming rules; for example, it may contain an invalid character.
Action:
Follow the report object naming rules to create a valid name.
REP-80004
A dialog window not allowed at this time.
Category:
Other
Cause:
The Plugin tried to display a dialog window when it is not allowed; for example, when Reports is running in batch mode.
Action:
Plugin must not raise a dialog window when it is not allowed.
REP-80005
The dialog window location is invalid.
Category:
Other
Cause:
The requested dialog window location is invalid.
Action:
Set a valid dialog window location.
REP-80006
The dialog window size is invalid.
Category:
Other
Cause:
The requested dialog window size is invalid.
Action:
Set a valid dialog window size.
REP-80007
The help system cannot be displayed.
Category:
Other
Cause:
Failure to display online help.
Action:
Check the online help system setup.
REP-80008
The helpset ID is invalid.
Category:
Other
Cause:
Invalid helpset ID.
Action:
Correct the helpset ID.
REP-80009
The help topic is invalid.
Category:
Other
Cause:
The help topic is invalid.
Action:
Correct the help topic.
REP-80010
The trace file cannot be written to.
Category:
Other
Cause:
Fail to write to trace file.
Action:
Check the trace file setup, file write permission, and whether the disk is full.
REP-80011
Sign-on parameter {0} for {1} cannot be set.
Category:
Other
Cause:
The column is not a valid sign-on parameter of this plugin type.
Action:
Use the Property Palette to set this column as a sign-on parameter of this plugin type.
REP-80012
The link between two columns of mismatched datatypes is invalid.
Category:
Other
Cause:
The column link is formed between two columns of different data types.
Action:
Ensure the link is formed between the columns whose datatypes are compatible.