Natural System Error Messages 3250-3299

#### Search Results

Search

# Natural System Error Messages 3250-3299

#### NAT3250: The ACBX validation failed. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    The ACBX validation failed. DB/FNR/Subcode .../.../....
    Explanation
    The ACBX validation failed.
    Possible subcodes:
    Subcode Description
       1    Unsupported ACBX version.
       2    ADACBX provided without UBE.
       3    ACBX file number > 65,535.
       4    Reserved field not zero.
       5    ACBX length incorrect.
    Action
    Contact your database administrator.

#### NAT3251: Error in cluster processing. DB/Net-Work ID/Subcode :1:/:3:/:2:.

    Text
    Error in cluster processing. DB/Net-Work ID/Subcode .../.../....
    Explanation
    Under certain conditions, the Adabas cluster SVC (SVCCLU) component
    of ADASVC returns response code 251 in the ACB"s response code field,
    along with a hexadecimal subcode in the low-order (rightmost)
    two bytes of the additions 2 field.
    If the local SVCCLU detects the condition, the subcode will be
    from 2 to 30.
    If a remote SVCCLU detects the condition, the subcode will be
    from 102 to 130.
    If you are using Entire Net-Work, the leftmost two bytes
    of the additions 2 field may also contain the ID of the Entire
    Net-Work node that issued this response code.
    For an explanation of this response code for non-mainframe databases,
    see the Adabas documentation.
    Action
    Contact your Adabas administrator.

#### NAT3252: Error in Adabas SVC processing. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Error in Adabas SVC processing. DB/FNR/Subcode .../.../....
    Explanation
    A post error occurred during Adabas SVC processing.
    See the Adabas documentation for the explanation of the subcode.
    Action
    Contact your database administrator.

#### NAT3253: Error in buffer processing. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Error in buffer processing. DB/FNR/Subcode .../.../....
    Explanation
    See the Adabas documentation for the explanation of the subcode.
    Action
    Contact your database administrator.

#### NAT3254: Error during command completion. DB/FNR/NW/Subc :1:/:2:/:4:/:3:.

    Text
    Error during command completion. DB/FNR/NW/Subc .../.../.../....
    Explanation
    A validation error occurred during command completion processing while
    attempting to return results to the caller.
    The message shows the DBID, FNR, Net-Work ID and subcode.
    See the Adabas documentation for the explanation of the subcode.
    Action
    Contact your database administrator.

#### NAT3255: Attached buffers exhausted. DB/FNR/Net-Work ID :1:/:2:/:3:.

    Text
    Attached buffers exhausted. DB/FNR/Net-Work ID .../.../....
    Explanation
    All attached buffers were allocated at the time the command was
    processed.
    Action
    Contact your database administrator.

#### NAT3275: PROCEDURE name in CALLDBPROC statement must be alpha.

    Text
    PROCEDURE name in CALLDBPROC statement must be alpha.
    Explanation
    The PROCEDURE name in the CALLDBPROC statement must have
    alphanumeric format. Specify either an alphanumeric
    constant or an alphanumeric variable.
    Action
    Correct the PROCEDURE name specification in the CALLDBPROC
    statement.

#### NAT3276: Result set and SQLCODE variables must have format (I4).

    Text
    Result set and SQLCODE variables must have format (I4).
    Explanation
    Result set and SQLCODE variables must have format (I4).
    Action
    Correct the format definition of the result set and SQLCODE
    variables.

#### NAT3277: CALLMODE parameter has to be either Natural or NONE.

    Text
    CALLMODE parameter has to be either Natural or NONE.
    Explanation
    The CALLMODE parameter of the CALLDBPROC statement
    must either be NONE or Natural. If omitted, it is set
    to NONE.
    Action
    Correct the CALLMODE specification.

#### NAT3278: Invalid parameter specified in CALLDBPROC statement.

    Text
    Invalid parameter specified in CALLDBPROC statement.
    Explanation
    One of the parameters specified in the CALLDBPROC statement
    is invalid.
    Action
    Correct the parameter specification in the CALLDBPROC
    statement.

#### NAT3279: The CALLDBPROC statement is invalid.

    Text
    The CALLDBPROC statement is invalid.
    Explanation
    The CALLDBPROC statement contains an unexpected keyword.
    Action
    Correct the CALLDBPROC statement.

#### NAT3280: :1: occurred in stored procedure :2:.

    Text
    :1: occurred in stored procedure :2:.
    Explanation
    The natural error message :1: was issued during the processing of
    the SQL stored procedure :2:.
    Action
    Analyze the error and correct stored procedure.

#### NAT3281: Stored procedure :1: number of parameters differ :2:,:3:.

    Text
    Stored procedure ... number of parameters differ ...,....
    Explanation
    The stored procedure control block contains a number of parameters
    different from the number of parameters passed
    to the stored procedure. This is an internal error, which
    "should not occur". The first number is the expected
    number of parameters, the second number the received parameters.
    Action
    Contact Software Ag customer service center and provide
    LISTSQL of program.

#### NAT3282: Stored procedure :2: got an invalid parameter description.

    Text
    Stored procedure :2: got an invalid parameter description.
    Explanation
    The stored procedure :2: received, in its control block, an
    invalid parameter description. This is an NDB internal
    error.
    Action
    Contact Software Ag customer service center.

#### NAT3283: Stored procedure :1: GETMAIN of DB2SIZE1 failed. RC :2:.

    Text
    Stored procedure ... GETMAIN of DB2SIZE1 failed. RC ....
    Explanation
    The GETMAIN of the DB2SIZE1 buffer failed with return code :2.
    The DB2SIZE1 buffer is used to copy the passed data into the
    Natural storage area before the stored procedure is invoked.
    It also contains the Natural internal format description of the
    passed parameters.
    Action
    Either increase the Natural thread size or reduce the number of
    parameters passed to the stored procedure or decrease the amount
    of data passed to the stored procedure.

#### NAT3284: Stored procedure :1: misses DB2SIZE1 before return.

    Text
    Stored procedure ... misses DB2SIZE1 before return.
    Explanation
    The DB2SIZE1 buffer contains a copy of the parameters passed by
    the caller. When the stored procedure has modified the data, it
    copies them back to the DB2SIZE1 buffer and then returns them to
    the caller. Unfortunately, the buffer disappeared.
    This is an internal error.
    Action
    Contact Software Ag customer service center.

#### NAT3285: Stored procedure :1: FREEMAIN of DB2SIZE1 failed rc :2:.

    Text
    Stored procedure :1: FREEMAIN of DB2SIZE1 failed rc :2:.
    Explanation
    The FREEMAIN of the DB2SIZE1 buffer which hold the data
    passed to the stored procedure failed with return code :2:.
    This is an internal error.
    Action
    Contact Software Ag customer service center.

#### NAT3286: Stored procedure :1: CB version mismatch :2: , :3:.

    Text
    Stored procedure :1: CB version mismatch :2: ,  :3:.
    Explanation
    The stored procedure detected an unexpected control identifier.
    It expected the identifier :2: but received :3:
    This indicates a version mismatch between NDB software on the
    client or caller side and the NDB software on the server side.
    Action
    Upgrade to matching software levels on both sides.

#### NAT3287: Duplicate specification of clause in SELECT statement.

    Text
    Duplicate specification of clause in SELECT statement.
    Explanation
    One of the following clauses has been specified twice in the SELECT
    statement: OPTIMIZE FOR clause, ISOLATION clause, FETCH FIRST clause,
    QUERYNO clause, SKIP LOCKED DATA clause.
    Each of these clauses may be specified only once.
    Action
    Remove one of the duplicate clauses.

#### NAT3288: Invalid column name list of correlation clause.

    Text
    Invalid column name list of correlation clause.
    Explanation
    The column name list of the correlation clause has to be enclosed
    in round brackets and the column names have to be separated by comma.
    Each column name is a long identifier and has to be unique within
    the column name list.
    Action
    Correct the column name list.

#### NAT3289: Invalid table locator reference in FROM clause.

    Text
    Invalid table locator reference in FROM clause.
    Explanation
    A table locator reference has to conform to the following syntax:
    TABLE ( table̲locator̲variable LIKE table̲name )
    The table̲locator̲variable has to be of format I4.
    The table̲name has to be the name of a valid Db2 DDM.
    Action
    Correct the table locator reference in the FROM clause.

#### NAT3290: Invalid table function reference in FROM clause.

    Text
    Invalid table function reference in FROM clause.
    Explanation
    A table function reference has to conform to the following syntax:
    TABLE ( function̲name ( expr , ... )) correlation̲clause
    Check for matching opening and closing parentheses.
    Table function references must have a correlation clause.
    The function̲name is a long identifier; it can be qualified by a
    schema̲name, which is a short identifier.
    Action
    Correct the table function reference in the FROM clause

#### NAT3291: Invalid CAST expression.

    Text
    Invalid CAST expression.
    Explanation
    A CAST expression has to conform to the following syntax:
    CAST ( expression AS data̲type )
    Check the correct setting of parentheses and keywords. The data̲type
    can be either a built-in data type or a distinct̲type, which is
    a long identifier that can be qualified by a schema name (short
    identifier).
    Action
    Correct the CAST expression.

#### NAT3292: Invalid value specified as QUERYNO.

    Text
    Invalid value specified as QUERYNO.
    Explanation
    The QUERYNO has to be specified as a non-negative integer number.
    Action
    Specify a non-negative integer number as QUERYNO.

#### NAT3293: Content of scroll variable is invalid at offset :1:.

    Text
    Content of scroll variable is invalid at offset ....
    Explanation
    The content of a scroll variable has to conform to the following
    rule: <sensitivity> <direction> <integer>
    - <sensitivity> is optional and can be either INSENSITIVE or SENSITIVE.
    - <direction> can be one of the following: NEXT, PRIOR, FIRST, LAST,
      CURRENT, BEFORE, AFTER, RELATIVE, ABSOLUTE. The default is NEXT.
    - <integer> has to specified if <direction> is RELATIVE or ABSOLUTE.
      It has to be a integer number, like -5 or 0 or 6. It cannot be
      specified with any <direction> other than RELATIVE or ABSOLUTE.
    The specifications of <sensitivity> <direction> <integer>
    have to be separated from one another by one or more spaces.
    Action
    Correct the content of the scroll variable.

#### NAT3294: SENSITIVE STATIC not allowed for READ-ONLY cursors.

    Text
    SENSITIVE STATIC not allowed for READ-ONLY cursors.
    Explanation
    SENSITIVE STATIC SCROLLABLE cursors are only allowed if the associated
    query is not READ-ONLY.
    Queries are READ-ONLY if they contain UNION, GROUP BY, HAVING, or
    nested TABLE expressions, and if they are used in a READ RESULT SET
    statement.
    Action
    Either change the query, or change to INSENSITIVE STATIC SCROLL
    cursors.

#### NAT3295: Conversion of DATE/TIME string :1: failed with error :2:.

    Text
    Conversion of DATE/TIME string ... failed with error ....
    Explanation
    The conversion of a Db2 DATE/TIME string failed with the Natural error
    indicated in this message, because the DATE/TIME string received from
    Db2 could not be converted to a Natural date/time variable.
    This could happen if, for example, a date prior to 01.01.1582
    stored in Db2 is to be placed into a Natural date variable.
    This also occurs if a Db2 TIME string is retrieved which is
    either "00:00 AM" or "24.00.00".
    See the Natural error code for further information.
    Action
    Do not use DATE/TIME strings which cannot be handled by Natural.

#### NAT3296: Limit of successive "not found" conditions exceeded.

    Text
    Limit of successive "not found" conditions exceeded.
    Explanation
    The limit of successive "not found" (SQLCODE +1oo) conditions has been
    exceeded. This occurs if, within a processing loop involving
    scrollable cursors, the number of "not found" conditions exceeds
    its limit. The limit is 5. The processing loop is closed.
    The counter of successive "not found" conditions is reset when a
    condition other than "not found" occurs, or when a terminal I/O occurs.
    The limit check is performed to avoid undesired database loops.
    Action
    Change program logic to avoid this condition.

#### NAT3297: NDB :1: conversion failed with FC :2: / RC :3: :4: :5:

    Text
    NDB :1: conversion failed with FC :2: / RC :3: :4: :5:
    Explanation
    NDB Stored Procedures encoded with UNICODE using Natural alphanumeric
    fields (A) receive UTF8 encoded data which have to be converted to
    EBCDIC. This conversion failed with the specified function and reason
    code. :4: is the destination length, and :5: is the destination length
    necessary to fully convert the UTF8 data to EBCDIC.
    Action
    Contact technical support.

#### NAT3298: Error during Multifetch: :1:.

    Text
    Error during Multifetch: ....
    Explanation
    During creation of the NDB Multifetch buffer (DB2SIZE6) an error
    has occurred; the error message indicates which kind of error.
    Usually, this is a getmain error or an internal error.
    Action
    In the case of a getmain error, either increase the thread size or
    decrease the multifetch factor specified in the program.
    In the case of an internal error, contact Natural support.

#### NAT3299: Rowset positioning requires integer value or variable.

    Text
    Rowset positioning requires integer value or variable.
    Explanation
    The Rowset positioning clause requires the specification of an integer
    value or variable which determines the size (number of rows) of the
    multi-fetch buffer.
    The Rowset positioning clause has the following syntax:
    WITH ROWSET POSITIONING FOR int ROWS
    where "int" can be an integer numeric constant or a variable of
    format/length I4.
    Action
    Correct the Rowset positioning clause accordingly.