SQL*DBA Messages
This chapter lists messages generated by SQL*DBA. The likely cause(s) of the event(s) generating the message and recommended corrective action are also presented.
The messages listed in this chapter are displayed with the prefix DBA, signifying SQL*DBA, or LCC, signifying the command line. Refer to Oracle7 Server Utilities for more information on, and syntax for, SQL*DBA.
00001-00199: SQL*DBA Messages
DBA-00072 warning: name created with compilation errors
| Cause: | The package, package body, procedure, or function could not be created because there were code errors. | |
| Action: | Enter the SHOW ERRORS command and correct the listed compilation errors. | |
DBA-00073 warning: name created with compilation errors
| Cause: | The package, package body, procedure, or function could not be created because there were code errors. | |
| Action: | Enter the SHOW ERRORS command and correct the listed compilation errors. | |
DBA-00100 invalid SPOOL filename
| Cause: | When using the SPOOL command, the name of a file that already exists
was specified. | |
| Action: | Specify a valid name for a file that does not currently exist. | |
DBA-00101 extraneous text at end of command
| Cause: | There were unrecognized commands or other text on the command line. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00102 missing LOG keyword
| Cause: | The LOG keyword was missing from the ARCHIVE LOG command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00103 illegal ARCHIVE LOG option
| Cause: | An option specified was not LIST, STOP, START, NEXT, ALL, a number, or a filename in the ARCHIVE LOG command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00104 illegal RECOVER option
| Cause: | An option specified was not DATABASE, MANUAL, UNTIL, TABLESPACE, or DATAFILE in the RECOVER command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00105 invalid INSTANCE name
| Cause: | An invalid SQL*Net CONNECT string was specified for the instance name. | |
| Action: | Refer to the SQL*Net documentation for a complete description of SQL*Net CONNECT strings. | |
DBA-00106 invalid ECHO switch
| Cause: | An invalid option for the SET ECHO command was specified. | |
| Action: | Use either ON or OFF as an option for the SET ECHO command. | |
DBA-00107 invalid TERMOUT switch
| Cause: | An invalid option for the SET TERMOUT command was specified. | |
| Action: | Use either ON or OFF as an option for the SET TERMOUT command. | |
DBA-00108 invalid TIMING switch
| Cause: | An invalid option for the SET TIMING command was specified. | |
| Action: | Use either ON or OFF as an option for the SET TIMING command. | |
DBA-00109 invalid CYCLE value
| Cause: | An invalid value for the SET CYCLE command was specified. | |
| Action: | The SET CYCLE command must use an integer between 1 and 3600. | |
DBA-00110 illegal SET option
| Cause: | An invalid option for the SET command was specified. | |
DBA-00111 illegal SHOW option
| Cause: | An invalid option for the SHOW command was specified. | |
DBA-00113 invalid PFILE name
| Cause: | The specified PFILE name is not recognized. | |
| Action: | Specify a legal PFILE name. | |
DBA-00114 invalid database name
| Cause: | The specified database name is not recognized. | |
| Action: | Specify a legal database name. | |
DBA-00115 unexpected end of command
| Cause: | An option was specified without any arguments. For example: | |
SQLDBA> STARTUP OPEN PFILE
| Action: | Check the syntax of the command and enter the command again with the appropriate arguments for options that require values. | |
DBA-00116 illegal SHUTDOWN option
| Cause: | An option was specified that was not NORMAL, IMMEDIATE, or ABORT for the SHUTDOWN command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00117 invalid tablespace name
| Cause: | The specified tablespace name was not recognized. | |
| Action: | Specify a legal tablespace name. | |
DBA-00118 invalid process identifier or invalid statistics class
| Cause: | Something other than a number for a process identifier, or an invalid class was specified after the MONITOR STATISTICS command. | |
| Action: | Specify only numbers as process identifiers or specify a valid class for the MONITOR STATISTICS command. | |
DBA-00119 illegal STARTUP option
| Cause: | An option was specified that was not DBA, PFILE, EXCLUSIVE, SHARED, MOUNT, OPEN, RECOVER, or NOMOUNT for the STARTUP command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00120 invalid STOPONERROR switch
| Cause: | An invalid option was specified for the SET STOPONERROR command. | |
| Action: | Use either ON or OFF as an option for the SET STOPONERROR command. | |
DBA-00121 illegal MONITOR option
| Cause: | An illegal option was specified for the MONITOR command. | |
DBA-00122 invalid SET numeric parameter
| Cause: | A character or an invalid value was specified when a number was expected as a value for a SET command option. | |
| Action: | Check the syntax of the command, use an appropriate number for the option, and enter the command again. | |
DBA-00123 invalid tablespace name list
| Cause: | An invalid string was specified as one of the values in the list of tablespaces in the ARCHIVE LOG command. For example, '"' is an invalid string. | |
| Action: | Check the syntax of the command, use valid tablespace names for all names in the list, and enter the command again. | |
DBA-00124 invalid ARCHIVE destination
| Cause: | The specified ARCHIVE destination was not recognized. | |
| Action: | Specify a legal ARCHIVE destination. | |
DBA-00125 integer value overflow
| Cause: | A numeric value was specified that was too large. | |
| Action: | Use a smaller number. | |
DBA-00126 invalid VERIFY switch
| Cause: | The VERIFY switch was not recognized. | |
| Action: | Specify a legal VERIFY switch. | |
DBA-00127 invalid combination of STARTUP options
| Cause: | The specified options of the STARTUP command cannot be used simultaneously. For example, the following command is not valid: | |
SQLDBA> STARTUP MOUNT OPEN testdb
DBA-00128 invalid DEBUG switch
| Cause: | The DEBUG switch was not recognized. | |
| Action: | Specify a legal DEBUG switch. | |
DBA-00129 value out of range (1 - num)
| Cause: | The specified value was out of range. The valid range is given by the
error message. | |
| Action: | Use a number within the range specified by this error. | |
DBA-00131 invalid ARCHIVE TO device
| Cause: | The specified ARCHIVE TO device was not recognized. | |
| Action: | Specify a legal ARCHIVE TO device. | |
DBA-00132 null hostname/password specified
| Cause: | hostname/password was not specified. | |
| Action: | Specify the correct hostname/password. | |
DBA-00133 invalid datafile list
| Cause: | An invalid string was entered as one of the values in the list of datafiles in the ARCHIVE LOG command. For example, '"' is an invalid string. | |
| Action: | Check the syntax of the command, use valid datafile names for all names in the list, and enter the command again. | |
DBA-00134 invalid AUTORECOVERY switch
| Cause: | An invalid option was specified for the SET AUTORECOVERY command. | |
| Action: | Use either ON or OFF as options for the SET AUTORECOVERY command. | |
DBA-00136 bad variable specification
| Cause: | A variable was incorrectly specified using the VARIABLE command. | |
| Action: | Check the syntax of the command and issue the command again. | |
DBA-00137 syntax error in PL/SQL Block
| Cause: | The PL/SQL block contains a syntax error. | |
| Action: | Correct the syntax error. | |
DBA-00139 invalid ALTER DATABASE option
| Cause: | The specified ALTER DATABASE option was not recognized. | |
| Action: | Specify a legal option. | |
DBA-00140 invalid COMPATIBILITY switch
| Cause: | The specified COMPATIBILITY switch was not recognized. | |
| Action: | Specify a legal COMPATIBILITY switch. | |
DBA-00141 invalid RETRIES value
| Cause: | The specified RETRIES value was not recognized. | |
| Action: | Specify a legal RETRIES value. | |
DBA-00142 cannot recognize object type, owner or name
| Cause: | The specified object type, owner, or name was not recognized. | |
| Action: | Specify a legal object type, owner or name. | |
DBA-00143 variable has not been defined
| Cause: | The specified variable was not recognized. | |
| Action: | Specify an existing variable. | |
DBA-00144 invalid object type for DESCRIBE
| Cause: | The specified object type was not TABLE, VIEW, or PROCEDURE. | |
| Action: | Check that the object is a table, view, or procedure. If so, check that you specified the correct name and try again. If not, you cannot DESCRIBE
the object. | |
DBA-00145 invalid object name for DESCRIBE
| Cause: | The specified table, view, stored procedure or function was not recognized. | |
| Action: | Check spelling and specify an existing table, view, stored procedure,
or function. | |
DBA-00146 invalid HISTORY value
| Cause: | The specified HISTORY value was not recognized. | |
| Action: | Specify a legal HISTORY value. | |
DBA-00147 invalid LINES value
| Cause: | The specified LINES value was not recognized. | |
| Action: | Specify a legal LINES value. | |
DBA-00148 invalid TERM switch (use either PAGE or NOPAGE)
| Cause: | The specified value was not recognized. | |
| Action: | Specify a legal value. | |
DBA-00149 invalid SERVEROUTPUT switch
| Cause: | The specified value was not recognized. | |
| Action: | Specify a legal value. | |
DBA-00150 invalid FLAGGER switch
| Cause: | The specified value was not recognized. | |
| Action: | Specify a legal value. | |
00300-00359: DBA Execution
DBA-00300 internal error code, arguments: [num], [str]
| Cause: | An internal error was encountered. | |
| Action: | Contact customer support with the circumstances leading to the error and the complete set of error messages. | |
DBA-00301 cannot SET INSTANCE while connected to a database
| Cause: | SET INSTANCE was used while currently connected to a database. | |
| Action: | To change the current instance, DISCONNECT from the database before using SET INSTANCE. | |
DBA-00302 not connected to a database
| Cause: | The requested operation required being connected to the database. | |
| Action: | CONNECT to the database using a valid username and password before retrying the operation. | |
DBA-00304 input file I/O error num - input aborted
| Cause: | A command file used as input to SQL*DBA is corrupt or invalid. | |
| Action: | Check the file before retrying the operation. | |
DBA-00305 command size exceeds internal buffer size num
| Cause: | The size of the SQL statement exceeds SQL*DBA's buffer size. | |
| Action: | Shorten the SQL statement by removing extra blanks or by using intermediate statements or views, if necessary. | |
DBA-00306 monitor cycle interval time out of range (1 - num)
| Cause: | An invalid number was specified for the cycle interval. | |
| Action: | Enter a number between 1 and 3600 for the cycle interval. The number
indicates seconds. | |
DBA-00307 cannot open spool file name
| Cause: | SQL*DBA tried to open a spool file after the SPOOL filename was specified, but could not open the file. Possible causes are not enough disk space or inadequate privileges to create a file. | |
| Action: | Determine why SQL*DBA could not create a new file and retry. | |
DBA-00308 no spool file opened
| Cause: | SPOOL OFF was entered when not currently spooling. | |
| Action: | To capture session output, use the SPOOL command to open a file, enter the required commands, and close the file with SPOOL OFF. | |
DBA-00309 cannot close spool file name
| Cause: | SPOOL OFF could not close the currently open spool file. | |
| Action: | Check for an operating system reason that the spool file could not be closed. | |
DBA-00310 cannot open parameter file name
| Cause: | SQL*DBA cannot locate or open the file specified by the PFILE option, because either the file does not exist or SQL*DBA has insufficient privileges to open
the file. | |
| Action: | Check that the file exists in a location expected by SQL*DBA and can
be opened. | |
DBA-00311 data size exceeds internal buffer size
| Cause: | The results returned by a SQL query exceed the internal SQL*DBA buffer. | |
| Action: | Use the SET command to increase MAXDATA or decrease ARRAYSIZE. | |
DBA-00314 unable to attach to default host
| Cause: | The default host has not been set up correctly. | |
| Action: | Use the SET INSTANCE command with a valid host specification to set up a default host. | |
DBA-00315 cannot open command file name
| Cause: | SQL*DBA cannot locate the specified command file. | |
| Action: | Check the file's name and SQL*DBA's access to it before retrying. | |
DBA-00316 cannot start up while connected to a database
| Cause: | An attempt was made to start up an instance while connected to a database. | |
| Action: | To start up an instance, first DISCONNECT from the current database. | |
DBA-00318 SQL*DBA command line error num
| Cause: | A syntax or typing error was made while entering a SQL*DBA command line. | |
| Action: | Check the syntax and try again. | |
DBA-00319 cannot locate sqldba configuration file name
| Cause: | SQL*DBA cannot open the file specified by the ORA_SQLDBAINIT variable, because either the file does not exist or SQL*DBA has insufficient privilege to open the file. | |
| Action: | Check that the specified file exists and can be opened. | |
DBA-00320 cannot open sqldba configuration file name
| Cause: | File mentioned cannot be opened. | |
| Action: | Check that the specified file exists and can be opened. | |
DBA-00321 instance name too long
| Cause: | An instance name was specified that may be valid, but is too long
(exceeds 64 characters). | |
| Action: | Check the name of the desired instance and try again. | |
DBA-00322 total size of command line parameters exceeds buffer size
| Cause: | Too many command-line arguments were specified to fit in the
SQL*DBA buffer. | |
| Action: | Specify the arguments over several command lines. | |
DBA-00325 pfile too large
| Cause: | The file specified using PFILE is too large (exceeds 8K). | |
| Action: | Reduce the size of the parameter file before specifying it again using PFILE. | |
DBA-00327 command not available in this mode
| Cause: | A command was specified that is not available in this mode. | |
| Action: | Switch to a mode where the command is allowed. | |
DBA-00328 insufficient privilege for this display
| Cause: | An attempt was made to display a MONITOR display without sufficient privileges for the underlying V$ tables. | |
| Action: | Contact the database administrator to obtain the required privileges. | |
DBA-00329 insufficient privilege for SHOW SGA
| Cause: | An attempt was made to use SHOW SGA without sufficient privileges. | |
| Action: | Contact the database administrator to obtain the required privileges. | |
DBA-00330 logsource name too long
| Cause: | The specified name may be valid, but is too long (exceeds 127 characters). | |
| Action: | Use a shorter name. For example, relocate the file so that its path name
is shorter. | |
DBA-00331 cannot allocate enough memory for SQL buffer
| Cause: | There is not enough memory for the current SQL buffer. | |
| Action: | Use the SET command to reduce MAXDATA. Re-invoke MONITOR FILEIO. | |
DBA-00336 insufficient privilege for SHOW PARAMETERS
| Cause: | An attempt was made to use SHOW PARAMETERS without
sufficient privileges. | |
| Action: | Contact the database administrator to obtain the required privileges. | |
DBA-00337 missing instance name
| Cause: | The instance name was not specified in the CONNECT statement. | |
| Action: | Issue the CONNECT statement again, using the proper instance name. | |
DBA-00341 name is an undefined bind variable
| Cause: | The SQL statement refers to an undefined bind variable. | |
| Action: | Use the VARIABLE statement to define the bind variable and re-execute
the query. | |
DBA-00342 unable to complete internal login
| Cause: | Some database error occurred that prevented a successful CONNECT INTERNAL. For example, a SHUTDOWN ABORT command was issued. This message is usually followed by another message that indicates the problem. | |
| Action: | Ensure that the instance is started correctly before trying to CONNECT INTERNAL. You may need to use the STARTUP FORCE command. | |
DBA-00343 no such parameter
| Cause: | SHOW PARAMETER was given a parameter name that does not exist. | |
| Action: | Use a different argument to SHOW PARAMETER. | |
DBA-00344 no items for the requested operation currently exist
| Cause: | A mandatory list element in a dialog contained zero (0) elements. | |
| Action: | No action required. | |
DBA-00345 no user sessions exist
| Cause: | An attempt was made to see if users were connected, but no users
were connected. | |
| Action: | No action required. | |
DBA-00346 no unresolved in-doubt transactions exist
| Cause: | There were no in-doubt transactions to resolve. | |
| Action: | No action required. | |
DBA-00347 no offline tablespaces exist
| Cause: | There were no offline tablespaces to bring online. | |
| Action: | No action required. | |
DBA-00348 no online tablespaces exist
| Cause: | There were no tablespaces to take offline. You cannot take the SYSTEM tablespace offline. | |
| Action: | No action required. | |
DBA-00349 no available rollback segments exist
| Cause: | There were no offline rollback segments to drop. | |
| Action: | No action required. | |
DBA-00350 no offline rollback segments exist
| Cause: | There were no offline or partly available rollback segments to bring online. | |
| Action: | No action required. | |
DBA-00351 no online rollback segments exist
| Cause: | There were no online rollback segments to take offline. | |
| Action: | No action required. | |
DBA-00352 no online tablespaces exist for backup
| Cause: | There were no online tablespaces to backup. | |
| Action: | No action required. | |
DBA-00353 no online tablespaces being backed up exist
| Cause: | An attempt was made to end an online tablespace backup, but no tables are being backed up. | |
| Action: | No action required. | |
DBA-00354 no offline tablespaces exist
| Cause: | There were no offline tablespaces to recover. | |
| Action: | No action required. | |
DBA-00355 no offline datafiles exist
| Cause: | There were no offline datafiles to recover. | |
| Action: | No action required. | |
DBA-00356 no users exist
| Cause: | There were no named users to alter or drop. | |
| Action: | No action required. | |
DBA-00357 no roles exist
| Cause: | There were no roles to alter or drop. | |
| Action: | No action required. | |
DBA-00358 no users or roles exist
| Cause: | There were no users or roles to grant privileges and roles to or to revoke privileges and roles from. | |
| Action: | Create some users before granting roles or privileges. | |
DBA-00359 monitor already active
| Cause: | An instantiation of this monitor was already active. | |
| Action: | Cycle through the monitor windows until the monitor becomes visible. | |
00360-00369: DBA Describe Execution
DBA-00360 object to be described does not exist
| Cause: | The object in a DESCRIBE FUNCTION / PROCEDURE / PACKAGE statement did not exist. | |
| Action: | Check that the object name and owner are correct and that the object exists. | |
DBA-00361 error during describe
| Cause: | An unexpected error occurred during describe. | |
| Action: | Check the following error and correct the problem. | |
DBA-00362 object name is a package; use DESCRIBE name.<procedure>
| Cause: | The named object was a package. DESCRIBE does not currently describe an entire package specification. | |
| Action: | Specify an entire package. | |
DBA-00363 procedure or function name not found in the package
| Cause: | The named package did not contain the procedure of the function specified. | |
| Action: | Specify a procedure or function within the package. | |
DBA-00364 object name is a remote object, cannot further describe
| Cause: | The specified object name contained a database link or was a synonym
that resolved to a name with a database link. Such objects cannot currently
be described. | |
| Action: | Specify a local object. | |
DBA-00365 object name is invalid, it may not be described
| Cause: | The object must have been successfully compiled. | |
| Action: | Fix any errors in the object and recompile. | |
DBA-00366 name name is malformed, it must be of form [[a.]b.]c@dblink
| Cause: | The name may have at most three parts and a dblink. | |
| Action: | Use a well formed object name. | |
00370-00380: DBA Generic Execution
DBA-00370 mandatory field/list needs to be filled in
| Cause: | An attempt was made to execute the dialog before filling in all required items. | |
| Action: | Fill in all required items and retry. | |
DBA-00371 cannot open/locate input help file, name
| Cause: | The Help Key was pressed or an item was chosen from the Help Menu, and the help file was not in the expected location. | |
| Action: | Put the help file in the location specified. | |
DBA-00372 cannot open/locate input index file, name
| Cause: | The Help Key was pressed or an item was chosen from the Help Menu, and the help file was not in the expected location. | |
| Action: | Put the index help file in the location specified. | |
DBA-00373 cannot allocate memory of size num from toolkit
| Cause: | The Help Key was pressed or an item was chosen from the Help Menu, and SQL*DBA ran out of memory. | |
| Action: | Exit SQL*DBA, restart, and try again. | |
DBA-00374 could not set file position in name directly
| Cause: | The Help Key was pressed or an item was chosen from the Help Menu. | |
| Action: | Alternate chosen -- no action required. | |
DBA-00375 unexpected end of file, name
| Cause: | The Help Key was pressed or an item was chosen from the Help Menu, but the help file specified was not installed. | |
| Action: | Exit SQL*DBA and install the correct help file. | |
DBA-00376 mandatory field has to be filled in before navigation is possible
| Cause: | An attempt was made to navigate to the next/previous item without filling a required field. | |
| Action: | Fill in current field before proceeding to another field. | |
DBA-00377 mandatory list item has to be selected before navigation is possible
| Cause: | An attempt was made to navigate to the next/previous item without filling a required field. | |
| Action: | Select a list item before proceeding to another field. | |
DBA-00378 an item has to be selected before help can be sought for it
| Cause: | An attempt was made to obtain help before selecting an item. | |
| Action: | Select an item first and re-execute. | |
DBA-00379 variable(s) not defined
| Cause: | The SHOW VAR[IABLES] [var-name] command could not find any variables. Either no variables are defined or you specified a non-existent variable. | |
| Action: | Check the spelling of the variables that were entered or, if no variables were entered, define the necessary variables. | |
DBA-00380 procedural option required for this statement
| Cause: | The attempted statement requires the procedural option. | |
| Action: | Refrain from using this statement or contact an Oracle sales representative to purchase the procedural option. | |
DBA-00381 error in the SERVER OUTPUT option
| Cause: | Most likely the package DBMS_OUTPUT was not installed. | |
| Action: | Install the package DBMS_OUTPUT and check the accompanying messages for more information. | |
DBA-00382 value name is not a recognizable filename for name
| Cause: | The value for the SQL*DBA initialization variable, which points to the initialization file, is not a recognizable filename. | |
| Action: | Specify a valid filename or do not define the variable so that no initialization file is run. | |
DBA-00383 filename name pointed to by name could not be opened
| Cause: | The filename pointed to by the SQL*DBA initialization variable could not
be opened. | |
| Action: | Specify an available file or do not define the variable so that no initialization file is run. | |
DBA-00384 could not open SQL*DBA resource file, name
| Cause: | The file mentioned could not be opened. | |
| Action: | Make the file mentioned available for use by SQL*DBA. | |
DBA-00385 could not locate SQL*DBA resource file, name
| Cause: | The file mentioned could not be located. | |
| Action: | Check that the file exists before rerunning SQL*DBA. | |
DBA-00386 could not open toolkit resource file, name
| Cause: | The file mentioned could not be opened. | |
| Action: | Make the file mentioned available for use by SQL*DBA. | |
DBA-00387 could not locate toolkit resource file, name
| Cause: | The file mentioned could not be located. | |
| Action: | Check that the file exists before rerunning SQL*DBA. | |
DBA-00388 cannot start SQL*DBA in screen mode; check if values are legal
| Cause: | A variable was not properly set. | |
| Action: | Check the values listed by SQL*DBA to see if they are correct. | |
DBA-00389 toolkit resource file name is defined to name
| Cause: | File mentioned could not be located. | |
| Action: | Check that the file specified exists and can be accessed. | |
DBA-00390 terminal type name is defined by name
| Cause: | Terminal type specified by may not be valid. | |
| Action: | Check that the terminal specification is correct. | |
DBA-00391 value name is defined to name; legal values: name or name
| Cause: | SQL*DBA mode has been incorrectly defined. | |
| Action: | Define the value of the variable to one of the legal values. | |
DBA-00392 this field requires a numeric value
| Cause: | An attempt was made to navigate to the next/previous item with a non-numeric value in a field requiring a numeric value. | |
| Action: | Enter a numeric value in the field and repeat the operation. | |
00100-00299: LCC Messages
The following messages result from errors occurring in the parameter file. These messages occur when attempting to start an instance.
LCC-00100 internal error, argument num
| Cause: | An internal error was encountered. | |
| Action: | Call customer support with the circumstances leading to the error and the complete set of messages. | |
LCC-00111 value not in legal range range
| Cause: | The value of the parameter was outside the valid range. | |
| Action: | Check the valid range and retry using a new value. | |
LCC-00112 illegal integer radix specification character
| Cause: | An invalid character was specified. | |
| Action: | Valid characters are 'd', 'h', 'D', and 'H'. | |
LCC-00113 integer conversion error or negative integer num
| Cause: | A non-integer or negative integer was assigned to an integer parameter. | |
| Action: | Retry using a valid integer value. | |
LCC-00114 illegal boolean response character
| Cause: | A value other than TRUE or FALSE was specified. | |
| Action: | Enter a boolean value, either TRUE or FALSE. | |
LCC-00122 unrecognized keyword name
| Cause: | An invalid or misspelled keyword was specified. | |
| Action: | Re-enter the line. | |
LCC-00128 invalid positional parameter value num
| Cause: | An invalid positional parameter value was specified. | |
| Action: | Correct the value. | |
LCC-00161 Oracle error (possible syntax error) parameter name
| Cause: | A parameter was specified incorrectly, possibly with a syntax error. | |
| Action: | Correct the error as described in the accompanying message. | |
LCC-00201 could not open specified filename name
| Cause: | The specified file did not exist. | |
| Action: | Check the name of the file or create a file by that name before retrying. | |
LCC-00203 missing keyword name
| Cause: | A keyword is expected but none was found. | |
| Action: | Add a parameter keyword followed by an equal sign and a parameter value. | |
LCC-00204 left parenthesis and no parameter specified name
| Cause: | A parameter list was started but no parameter was specified. | |
| Action: | Add an appropriate list of values and close the parameter list. | |
LCC-00205 unbalanced parentheses character
| Cause: | An odd number of parentheses was found, indicating that one is missing or one is extra. | |
| Action: | Retry the statement using the correct number of parentheses. | |
LCC-00206 positional parameter entered after keyword name
| Cause: | An equal sign was missing. | |
| Action: | Retry the parameter specification using an equal sign between the parameter name and the value. | |
LCC-00207 nested parentheses encountered character
| Cause: | More than one set of parentheses was used. Only one set of parentheses
is permitted. | |
| Action: | Remove the nested parentheses and retry. | |
LCC-00208 unexpected keyword in value list name
| Cause: | A keyword was found instead of a value. | |
| Action: | Insert an appropriate value for the keyword. | |
LCC-00209 missing value for keyword at end of string str
| Cause: | A keyword was specified with no value. | |
| Action: | Specify a valid value for the keyword. | |
LCC-00210 illegal assignment operator symbol
| Cause: | An attempt was made to use a symbol other than an equal sign to assign a value to a parameter. | |
| Action: | Retry using an equal sign following the parameter name. | |
LCC-00211 unexpected delimiter symbol
| Cause: | An invalid delimiter was found between values. | |
| Action: | A comma or a space is a valid delimiter. | |
LCC-00212 runaway quoted string str
| Cause: | The parameter value was quoted on the left side but not on the right. | |
| Action: | Balance the quotation marks. | |
LCC-00215 parameter files nested too deep num
| Cause: | Too many parameter files were nested. The maximum number of files that may be nested is three. | |
| Action: | Reduce the number of nested parameter files. | |
LCC-00217 failure while processing file parameter
| Cause: | An error occurred while processing a file parameter. | |
| Action: | Other messages will follow with additional information. | |
LCC-00218 error in file name
| Cause: | An error occurred in the particular file. | |
| Action: | Other messages will follow with additional information. | |
