The file named could not be opened for reading. This error can happen in several places including:
The verification that the public directory exists and is correct failed. You probably have an invalid installation or are directly using an rwloadsimNN in an unexpected way..
Your rwloadsim program terminated unexpectedly. Typical causes are:
A syntax error during parse of an integer declaration.
A syntax error during parse of a double declaration.
A syntax error during parse of a string declaration.
A syntax error after parse of an identifier. The identifier should be followed by either of:
A syntax error during parse of an expression.
The semicolon is used to terminate a statement or declaration and repeated semicolon is not allowed.
The size of an array must be at least 1.
A general parse error that often occurs when a semicolon is missing.
A local variable was used in a context where only private or public variables are allowed.
A syntax error during parse of bind in a sql declaration.
A syntax error during parse of define in a sql declaration.
A syntax error during parse of array in a sql declaration.
In a declaration of a sql variable, each specification must must be terminated with a semicolon.
The identifier you are using has not been declared.
A syntax error during parse of a loop header.
A syntax error during parse of a database declaration.
The named identifier has already been declared Note that there is only one namespace for all variables.
Attempt to write more bytes to a string variable than its declared length. Note that if you are using sprintf, the the expected number of bytes is calculated as soon as the first % conversion would exceed the maximum length.
The right operand of a / or % operation is zero, operation continues using the left operand as result.
The tmpfile(3) function returned an error.
See rwlman directive for a complete list of all directives.
Due to previous errors, the named procedure cannot be executed.
An invalid character with the value shown in hex was read during scanning.
An invalid character was read during scanning.
In declaration of a random string or procedure, all weights must be at least zero.
Ignoring errors and use of programmed error handling cannot be done with array processing. You must either set array to 1 or let rwloadsim handle errors.
In declaration of a random string or procedure, at least one weight must positive.
You have been using ‘-‘ as an argument to rwloadsim, this is not supported.
You can only use the array specification once.
The array size must be at least 1.
The username is a compulsory specification in a database declaration.
The default and results databases can only be declared once.
The facility you attempt using has not yet been implemented.
A database is either not declared or has caused error during connection.
A syntax error during parse of a regex statement.
Regular expression caused an error in regcomp(3).
When using the regextract statement, the number of matched sub-expressions is smaller than the number of variables.
The number of select list elements reported by Oracle Call Interface does not match the number of defines used in the sql declaration or the number of defines in effect for a dynamic sql.
A query used as a simple sql statement returns no errors. You can replace the simple sql by a cursor loop to prevent this error.
The facility you attempt using has not yet been implemented.
The commit or rollback has no effect as not sql has been executed.
You have been doing DML without performing explicit commit or rollback before your session was (implicitly) released or given up. If you have DML directly in main, you must wrap the DML and an associated commit with an execute block for the commit to have effect.
You have been doing DML inside PL/SQL without performing explicit commit or rollback before your session was (implicitly) released or given up. If you have PL/SQL with open transaction directly in main, you must wrap the call and associated commit with an execute block for the commit to have effect.
There was an error during initial connection of the database and the database can therefore not be used.
You have been using a database and rwloadsim has registered some dml has been executed. You therefore must perform explicit commit or rollback.
You have attempted using the syntax for a cursor loop but the sql statement is not a query.
Without an explicit array size set, array fetch will be based on memory. If this is acceptable, use $mute:50.
A syntax error during parse of a file declaration.
At runtime, the file named could not be opened. The O/S error will have further details.
When closing a file (assigning null to it), the file was not open.
At runtime, the file named could not be closed. The O/S will have further details.
Attempting to open a file that has already been opened.
The file will implicitly be closed. This may happen:
A syntax error during parse of a thread specification.
This is a generic error assoticated with unexpected conditions. The O/S error normally has further details.
When using the -c option, the start time must be zero or larger. If you are using multi process execution, too long time may have passed after the prepare call to rwloadsim with the -P option until the actual execution is done with the -M or -R option.
A control loop option can only be provided once.
A control loop must have either stop or count specified exactly once.
After executing a PL/SQL block when the client version is 11.2, you need an explicit commit or rollback.
The function you are calling should be followed by an empty argument list. Omitting () will be desupported in a future release.
In an if statement, the condition was null. Processing continues using false.
You have somehow managed to find the legacy syntax for control loops. Change your code to use the documented syntax.
When a pipeline was closed, the return value from pclose() was non zero.
Creation of a pipeline failed with the O/S error shown.
At runtime, the pipeline named could not be closed. The O/S will have further details.
There have been previous errors that prevent further processing.
When saving histogram statistics, the bucket was larger than allowed.
When saving histogram statistics, the bucket was smaller than allowed. This error is no longer used.
You have attempted using the $mute directive for an error number that does not exist.
You have attempted muting an error or severe error. To allow this, first include $mute:73.
Saving of per second counts for seconds beyond the value shown is suppressed. This is mostly a result of database activity taking much longer than expected, causing procedures to finish much after the expected time given via the -Z option or the default of 2 hours.
The fixed array for storing your declared procedures and functions has been exhausted. You can use either of these methods to increase the size:
The fixed array for storing your variable names has been exhausted. You can use either of these methods to increase the size:
A syntax error during parse of bindout in a sql declaration.
The OCIThreadInit call did not succeed.
Executing the sql at the file and line shown caused an Oracle error. Processing will continue unless you have used $oraerror:stop.
Executing some database operation caused an Oracle error. Processing will continue unless you have used $oraerror:stop.
Executing the sql at the file and line shown caused an Oracle warning. Processing will continue unless you have used $oraerror:stop.
Executing some database operation caused an Oracle warning. Processing will continue unless you have used $oraerror:stop.
Executing the sql at the file and line shown caused an Oracle Call Interface error. Processing will continue unless you have used $oraerror:stop.
Executing some database operation caused an Oracle Call Interface error. Processing will continue unless you have used $oraerror:stop.
Executing the sql at the file and line shown caused an unspecified Oracle Call Interface error. Processing will continue unless you have used $oraerror:stop.
Executing some database operation caused an unspecified Oracle Call Interface error. Processing will continue unless you have used $oraerror:stop.
The Oracle error shown was located at a specific line and position in the sql statement. The actual line an position will be marked with an asterisk.
You must have at least one define and you cannot use bindout when using ‘array define’ to have rwloadsim handle the array for a query.
An attempt was done at modifying a static sql. The ‘modify sql’ statement can only be used with dynamic sql.
A syntax error during parse of random string.
The random string was declared, but cannot be used due to errors. You must fix the random string declaration.
A syntax error during parse of random procedure.
The results database must be declared dedicated, drcp or sessionpool. In most cases, using a session pool 0..2 is fine.
In order to save statistics, you must have a results database, and the results database must be accessible.
The value provided for the length of a string variable must be at least 1. If you omit an actual length, the default will be 128. The length is in bytes.
You must use the -P option in separate call of rwloadsim followed by call using either -M or -R option.
The clock offset sets the control loop common start time as a number of seconds after start of rwloadsim. The value you have chosen is too high.
A syntax error during parse of modify sql or modify database.
At least one input file must be provided to rwloadsim.
A variable of some type was found when a variable of a different type was expected. This is a generic error used in several contexts.
The keyword ‘end’ was followed by an unexpected keyword or identifier.
The count of threads started in each group of threads in the run statement cannot be negative. Additionally the total count must be positive.
The count of threads started in each group of threads in the run statement cannot be negative. Additionally the total count must be positive.
During parse of a sql declaration, the expected ‘end’ keyword was not found.
During scan for sql text, a terminator was not found. SQL is terminated by a line with potential white space followed by a single ‘.’ or ‘/’ at the end of the line, or by a ‘;’ and the end of a line.
A syntax error during parse of a function or procedure declaration.
The names of the gamma and gamma2 functions have been changed to erlang/erlang2. The old names will be removed in a future release.
In rwloadsim versions before 3.1, the modulus operator (%) was handled as in C and it did not handle double values. This is no longer the case, and this error is no longer used.
During scan for the terminator for sql or pl/sql, the terminator was found followed by white space.
In rwloadsim, the maximum length of identifiers is 30 characters.
When scanning for options to rwloadsim, an option that is neither known as an ordinary short or long option, nor known as an option from $useroption or $userswitch.
You can only used $include when a program element is complete. As an example, you cannot use $include while declaring a procedure. See the rwlprogram(1rwl) rwlman page for details.
Using ctrl-c will normally cause a termination within a few seconds. You can repeat the ctrl-c a number of times if termination does not occur. If you have $ora01013:continue, ORA-01013 will be treated like any other error and not cause rwloadsim to stop.
The filename is either empty or has illegal characters. As an example, an include file using < > delimiters cannot begin with . or /.
The limit on depth of $include has been reached. You must recompile rwloadsim from source to increase the limit.
You have attempted including some file using the $include directive from within the file itself. This is not supported.
The database used with an at clause must support pooling such as sessionpool or drcp.
The ‘at default’ clause only has an impact when done inside a procedure.
The $startseconds or $clockstart directive must be used before declaring the results database.
The new value for $dformat is too limited to properly output some double. This is a warning; continue at your own risk.
The new value for $iformat is too limited to properly output some integer. This is a warning; use at your own risk.
The single quote limiter is not used by rwloadsim.
A syntax error during parse of the at clause.
The number of arguments in the call to a procedure or function is larger than the number of declared arguments.
The number of arguments in the call to a procedure or function is smaller than the number of declared arguments.
A function must have at least one return statement. The behavior is undefined if you return from a function by other means than via return.
Attempt to return more bytes from a string function than its declared length.
In functions, the return statement must include an expression.
In procedures, the return statement cannot include an expression.
A syntax error during parse of procedure call.
Please replace the deprecated isnull() function by the is null operator. The isnull() function will be removed in a later release.
A syntax error during parse of a function declaration.
A semicolon was found at a place where it is not expected. It is used to terminate a statement or declaration.
The scanner has found a high number of invalid characters and all further processing is stopped.
A private variable is given the same name as an already existing public variable. The private variable will be used during the rest of the source file.
A local or private variable is given the same name as an already existing public variable. The public variable will not be accessible.
Please include the comma between the identifier and the following arguments.
The exit statement is only available directly in your main program. If you need a procedure or function to cause an exit, you must code it such that the wanted exit value is provided to your main program, where an exit can take place.
The password that was read was unreasonably long (The limit is probably too short, but requires recompile.
The password that was read was shorter than two characters .
When the -e flag is used, neither procedures nor sql are being executed.
A syntax error during parse of a clob declaration.
There are not sufficient arguments for the value of the -A or -F option.
The use of array when dealing with clob data is not supported by Oracle Call Interface.
You cannot declare local variables or arguments to procedures or functions with this data type.
You cannot write 0 bytes to a lob. This is a bug in rwloadsim that should do a truncate of the lob in this case.
You can only use a lob locator that has been read from the database. This can be doing using a query or a returning into.
The lower end of the range is larger than the higher end of the range.
You are on your own! This may be reasonable if you understand the source code.
The startup file such as ~/.rwloadsim.rwl and the RWLOADSIMINIT environment variable may only contain directives.
The directive can only be used in a startup file such as ~/.rwloadsim.rwl.
The threads sum/global attribute is only valid for private or public variables.
To provide key or komment in a multiprocess run, do so in the prepare run where the -P option is used.
The type of the database connection can only be provided once.
Do not provide a connection class for this database.
As sessions are implicitly acquired at the start of a procedure, request for a specific connection class must take place before calling the procedure that acquires the session.
The maximum length of a connection class in rwloadsim is 128 bytes.
Your connection class must have a name that does not include this character.
The valid escapes in a string constant are \\ \” \t \n \e \r or a \ prefixing a newline causing the newline to be excluded from the string.
An attempt at parsing a control loop while another control loop is being parsed.
An attempt at starting a control loop recursively while another control loop is being executed.
In a counter loop using .. the variable named after the for keyword should be of type integer, as the variable is incremented by the integer value 1 in each iteration.
A shift statement was attempted after all posistional arguments have been shifted and $# is zero.
A parameter is provided both at the command line and in a startup file such as ~/.rwloadsim.rwl.
Comments are limited in length to the size of the varchar2 column ‘komment’ in the rwlrun repository table.
The file you are opening using a $include directive was found in the public directory and has been read from there. You should not give your own include files the same name as those found in the public directory.
All procedures named in a random procedure must have the same number and types of arguments.
All procedures named in a random procedure must have the same number and types of arguments.
You have attempted using a string constant with a line longer than allowed.
Procedures or functions that take no arguments must include an empty set of brackets. This will be enforced in a future release.
You cannot use the return statement directly in main. The exit statement is a possible alternative.
This error is returned when OCIThreadCreate returns an OCI_NO_DATA error. There is no O/S error associated with this, but the typical cause is that the user is unable to start a new thread due to a too low value for ulimit -u.
A local variable is given the same name as an already existing private or public variable. The private/public variable will not be accessible.
The file named that should contain the text of a sql statement cannot be opened. The O/S error has details.
The file named that should contain the text of a sql statement cannot be read. The O/S error has details.
The -x option to rwloadsim takes one argument that must be a rwl program element including the terminating semicolon.
The Oracle error shown was located at a specific line and position in the sql statement read from a file. The actual line an position will be marked with an asterisk.
You cannot provide both the number of input files as the -F option and the number of user arguments as the -A option.
During parse of some declaration, the keyword ‘end’ was followed by an unexpected identifier or keyword.
During execution of the event handler for OCIEvents, an unexpected event was returned. You should report the value such that the rwloadsim code can be fixed to deal with it.
Oracle Call Interface was setup to handle events, and the event handler was called. The entries in the error text contain the following information (if available):
Rwloadsim was unable to open a file for writing; the O/S error has details The error is used in several places such as when creating the multiprocess file given as the -P option.
The error returned is assumed to be a recoverable error causing a session to fail. Due to the nature of the error, an attempt at re-creating the session will be done.
During parsing another keyword than the expected was found.
You have been hitting ctrl-c a number of times and rwloadsim terminates using SIGTERM.
Your PATH environment variable does not include the expected rwloadsimNN executable built for the client identified via LD_LIBRARY_PATH.
The LD_LIBRARY_PATH environment is not set. It should include the library with liblcntsh.so.
The LD_LIBRARY_PATH environment is not set properly. It should include the library with liblcntsh.so.
The error returned is assumed to be a recoverable error causing a database failure. In some circumstances, an attempt at reconnecting the database will be done.
When using the -l option to create a default database, you cannot use the -Y option without the -X option.
The database you are using has terminated due to an error.
You can only use this statement with an explicitly named database, or in some cases a default database.
A syntax error during parse of a write, writeline or fprintf statement.
The period used for automatic flush of per second statistics is too short and statistics flushing has been turned off.
The period between flushes of per second statistics must be at least 1s.
When period flushing of per second statistics is in use, the results database must be using a session pool.
A syntax error during parse of an fflush statement.
You are calling a function that currently is implemented as a more simple function. As an example, this is used when string functions handle strings a sequence bytes.
The minimum allowed value for k in erlangk is 1.
The maximum allowed value for k in erlangk is 20.
You have asked for a define array, but no explicit defines are found.
Use can only use define arrays with variables of type integer, double or string.
The size of a define array can only be specified at declaration time.
Although rwloadsim does have similarities with C, this is not one of them! The equality comparison operator is ‘=’.
A syntax error during parse of the sql_id function.
Your rwloadsim executable was compiled in a different Oracle Call Interface version than the one being found via LD_LIBRARY_PATH during execution. To mute the error, put $mute:206 in your .rwloadsim.rwl startup file.
During scan for environment variables in a file name fails. This can happen if ${ } expansion does not match, if the environment variable starts with anything but an upper case letter or is too long.
The named environment variable does not exist. If this is acceptable, use the getenv() function in stead.
You have been using the abort statement. It should only be used when no other possibilities exist. Consider using exit in stead.
The expression in the $if $then directive is using a feature that is not available for conditional compilation.
The $if $then $else $endif must be matched within each .rwl source file.
The $if $then $else $endif directives must be matched within each .rwl source file.
A thread has returned more ORA- errors and saving has been stopped. If this happens frequently and you need to save more errors, use the -O option or the $oerstatistics:N directive to increase the limit.
Although rwloadsim does have similarities with C, the operation you attempt using is not available.
The array for storing local variables in procedures or functions has been exhausted. You can use either of these methods to increase the size:
Attempt to write more bytes as output from the system function than the declared length of the string variable.
A syntax error during parse of the system function; a second argument must be a variable.
The second argument to the access function must contain ‘f’ or ‘d’ to check for a file or directory and must contain a combination of ‘rwx’ to check for read, write or execute permission. It may further contain ‘p’ to search in RWLOADSIM_PATH, ‘u’ to search in public directory or ‘c’ to not check in the current directory.
A syntax error during parse of the named database function. The argument must identify a database.
Only seen when executing test.sh as the syntax is not documented. If you use the deprecated syntax, please change your code.
The $if and $then directives must be on the same input line.
A syntax error during parse of the expression in an $if $then directive.
The formal argument of a procedure or function, and the return if a function must be one of integer, double or string.
You are using a feature that requires a higher Oracle Client release than the one you have.
The sql text for a dynamic sql statement must be provided exactly once. If you need to provide a new sql text, you must first do ‘modify sql release’.
Dynamic sql statement can only use the implicit fetch array in Oracle Call Interface and not a define array.
You cannot modify a dynamic sql that is currently being used in a cursor loop.
The experimental use of raw does not currently work with array bind, which prevents array dml. You could write the code and submit a pull request.
When prompting the user for a password, rwloadsim was unable to open /dev/tty.
A syntax error during parse of a readline statement.
When reading a line from a file, the line was longer than the buffer size. You can use either of these methods to increase the buffer:
The instrb2 function does not currently support reverse searching.
You have somehow found the now deprecated syntax for control loops, and have mixed that with the documented syntax. Note that the previous syntax will be desupported in some future release.
Files that are opened in the main thread must also be closed in the main thread. Note that files opened for read in the main thread including stdin) will be automatically closed in threads.
The operation you attempted cannot be done directly in main. You need need to wrap it with execute/end. Operations on LOB can be done directly in main, if you have a default database declare dedicated.
All of the directives $useroption, $userswitch, $longoption, $userhelp can only be used in the first .rwl file named on the command line.
An attempt was made at using $useroption or $userswitch with an option name that already exists as an ordinary option.
You have already used $useroption or $userswitch with the same name.
You can only use $useroption or $userswitch with variables declared as private or public.
You have provide a $useroption or $userswitch that does not have a variable associated with it.
After expansion of one or more environment variables, the resulting file name is unreasonably long.
After expansion of one or more environment variables, the resulting file name is unreasonably long.
As connection pools do not have a session associated with them, they cannot be used to execute any sql. As a consequence, cursorcache has no effect.
When using the ‘connect connectionpool’ option during a database declaration, the database named by the option must be declared as a connectionpool.
You cannot use a connection pool for this database.
Only (threads) dedicated databases can connect using a connection pool.
A database declaration can have at most one specification for connect string or connection pool.
As connection pools do not have a session associated with them, they cannot be used to execute any sql.
You are attempting to modify session pool parameters, but the database is not declared as a sessionpool database.
The value for some parameter is outside the allowed range and it has been adjusted to the new value shown. You should correct your program such that a proper value is used.
The scan for option directives that is performed in the first rwl file cannot be excluded using $if/$then/$else/$endif directives, and they will therefore always be used.
You cannot use the break statement directly in main. The exit statement is a possible alternative.
The break statement can only be used inside loop or execute block.
You are running rwloadsim on a platform that has not been thoroughly tested. If you complete full testing, please report using github.
A connection attempt failed due to a temporary error, and a retry will be attempted as specified by the $dbfailures directive.
The number of failures set via the $dbfailures directive has been exhausted. Investigate your environment and potentially set a higher value in $dbfailures.
Between $if and $then, only expressions are allowed. If you need nested $if $then, each $if … $then directive must be on a separate line.
You have somehow found the now deprecated syntax for while loops; replace ‘execute’ with ‘loop’. Note that the previous syntax will be desupported in some future release.
The implicit bind or define should only be provided once; in each sql declaration.
To use bindout as an implicit bind, the syntax :variable is needed in the bindout specification.
The implicit define can only be used with pre-fetch and not with array defines.
While doing implicit define for the named SQL statement, OCI_ATTR_PARAM_COUNT was returned as 0. Your SQL must be a query.
While doing implicit define for the named SQL statement, a select list element cannot be used as the name of a variable and it needs to have an alias.
While doing implicit bind for the named SQL statement, a placeholder that is not a valid variable was found. One such example is using numbered placeholders.
While doing implicit bind for the named SQL statement, a placeholder does not match any declared variable. You must change the placeholder or declare the variable.
While scanning the printf format, there was not enough expressions available to satisfy the format. Verify the printf format and provide the appropriate number of expressions.
While scanning the printf format, an unsupported conversion character was found and replaced by another supported character.
While scanning the printf format, end of string was reached before an appropriate conversion character was found.
While scanning the printf format, some other character than a valid conversion character was found. Supported characters include ‘i’, ‘f’, ‘e’, ‘s’.
While scanning the printf format, some non ascii character was found. Supported characters include ‘i’, ‘f’, ‘e’, ‘s’.
Each expression provided as an argument to printf must have a corresponding output format elements in the format string.
A syntax error during parse of sprintf statement.
You are using an identifier that in a future version of rwloadsim will be used as a keyword starting a SQL statement. You should change your code to use a different identifier.
You have attempted using the modify sql array execute statement with a sql statement that is not using array bind for a dml operation.
The sql statement text does not depend on any calculations done inside a procedure or anonymous execution block such as a loop. This is a legacy from the original rwloadsim design, and you are suggested one of these alternatives:
The sql statement text for this sql is dynamically set which means it could change for every execute and therefore cannot use an array. This is only relevant for dml, and if you expect to execute a query, you can do so in a cursor loop without this restriction.
During scan for pl/sql text, a terminator was not found. PL/SQL is terminated by a line with potential white space followed by a single ‘.’ or ‘/’ at the end of the line.
A syntax error was found during parsing by bison at the character position shown; the error may include the unexpected symbol and/or a list of expected symbols to help identify the actual error. It is followed by another error showing the rwloadsim error.
The valid escapes in a string constant are \\ \” \t \n \e \r or a \ prefixing a newline causing the newline to be excluded from the string.
An invalid character with the value shown in hex was read during scanning.
An invalid character was read during scanning.
To connect using sys authentication, ‘as’ must be followed by one of ‘sysdba’, ‘sysoper’, ‘sysasm’, ‘sysbackup’, ‘sysdg’, ‘syskm’ sysrac’.
To connect using sys authentication such as sysdba, the database must be declared as dedicated’.
Each specification should only provided once when you declare a database, and the one shown in the error has already been provided.
When calling an executable with direct execution of rwl scripts, you cannot use the feature or option shown.
When generating an executable for direct execution of rwl scripts, you cannot use the feature or option shown.
When generating an executable with direct execution of an rwl script, the command to compile and link has failed.
ORACLE_HOME or LD_LIBRARY_PATH environment is not set properly. Either should contain liblcntsh.so to use by gcc -L option for linking the generated binary.
The –generate option was used to create an executable from rwl scripts, and the named executable was successfully generated.
During scan of the rwl files for generating an executable, one or more sensitive keywords (including ‘database’, ‘password’ and others) was found. You are recommended making sure no sensitive information is included in the generated executable. Note that rwloadsim cannot complete verify no sensitive information is put in the executable.
In version 3.1, you need to change your syntax for opening files to use either of these assignment operators: >=, »=, <=, >|=, <|= in stead of using similar characters as part of the text string assigned to the file variable.
You are using one of the operators used to open a file or pipeline to close a file by assigning null to it. You should use the := operator.
You are using an identifier that in some future release will be a keyword. You should change your code and use a different identifier as it otherwise will cause a syntax error in the future.
The threads sum attribute can only be used with variables of type integer or double.
The expression being assigned to a threads global variable includes the same variable. Each individual access to threads global variables is protected by a mutex, and the assignment therefore has a race condition.
You have been using the abort statement and $abortnice is in effect. It should only be used when no other possibilities exist. Consider using exit in stead.
When generating an executable for direct execution of rwl scripts, all arguments are rwl files during generation, and are positional at execution.
The at clause must refer to a threads dedicated database.
When registering for query notification, the active time must be positive, and therefore stop time must be after both of start time and of current time.
The break querynotification is breaking a query notification before the stop time expires, but the statement is executed outside of the notification callback. The call must be executed in the ‘then’ clause of query notification.
The second argument to the normalrandom function is the standard deviation, which must be a positive number.
The statisticsonly attribute can only be used with procedures that do not perform any sql or other database calls. You need to either remove database activity from the procedure or remove the statisticsonly attribute.
debug arguments must be a comma separated list of debug options without spaces; each option either a hexadecimal number (potentially prefixed by 0x or 0X) or one of the text values exec, var, eval, bison, or sql .
You cannot use this command inside a procedure, function, or inside any compound statement such as if or loop.
When waiting for a session in a session pool, no available entry was available within the timeout of set for the pool.
The $sqllogging: directive is used to output all SQL being executed.
The $sqllogging: directive is used to output all SQL being executed. The sql_id is typically unknown if the sql had an error or if the database or client version is not at least 12.2.
During handling of sqllogging from option or directive, sqllogging was already enabled. You can turn off sqllogging via the $sqllogging:off directive.
Ampersand replacement can only be used in sql text directly embedded in your rwl file and the sql provided appears to have & used for replacement. You can use dynamic sql as an alternative, unless the & actually is part of your sql statement in which case the warning can be ignored. To prevent the check for &, use the $ampersand:off directive.
To be able to fit the potential contents of all ampersand replacement variables, a sufficiently large buffer will be allocated. This warning means this buffer will be larger than reasonably expected. If possible, you should use shorter replacement variables or alternatively simply mute this warning using the $mute:310 directive.
In embedded sql, the ampersand character must either be followed by the name of a string variable and a decimal point or by another & character. &varname. will be replaced by the actual variable contents when the sql is executed and && is used to include a single & in your sql statement.
When scanning for options to rwloadsim, a long option name is followed by an = sign but the option does not take an argument.
When scanning for options to rwloadsim, an option letter or long option name requiring an argument is found, but there are no further arguments.
When scanning for options to rwloadsim, an abbreviated long option name is found, but the abbreviation has multiple potential matches. You need to include more characters to make it unique.
You have attempted using a feature that is not supported on your platform. You may want to exclude this part of your code using $if not $windows $then