Natural System Error Messages 3150-3199

#### Search Results

Search

# Natural System Error Messages 3150-3199

#### NAT3150: Too many nuclei used in parallel. DB/FNR/Max :1:/:2:/:3:.

    Text
    Too many nuclei used in parallel. DB/FNR/Max .../.../....
    Explanation
    Too many database nuclei have been used in parallel.
    The Max field shows the maximum number of nuclei allowed in parallel.
    Action
    Contact your database administrator.

#### NAT3151: A command queue overflow occurred. DB/FNR :1:/:2:.

    Text
    A command queue overflow occurred. DB/FNR .../....
    Explanation
    The database administrator may increase the value for the NC parameter,
    and/or the command may be issued when a lower level of command activity
    is in effect.
    Action
    Contact your database administrator.

#### NAT3152: Internal user buffer too small. DB/FNR :1:/:2:.

    Text
    Internal user buffer too small. DB/FNR .../....
    Explanation
    The internal user buffer was not large enough to contain the user
    buffer areas. The database administrator should increase the value
    of the LU parameter.
    Action
    Contact your database administrator.

#### NAT3153: Previous Adabas call still in process. DB/FNR :1:/:2:.

    Text
    Previous Adabas call still in process. DB/FNR .../....
    Explanation
    A "CALL Adabas" was issued by a user while a previous call for
    the user was still being processed.
    Action
    Contact your database administrator.

#### NAT3154: Adabas call has been cancelled. DB/FNR :1:/:2:.

    Text
    Adabas call has been cancelled by the user. DB/FNR .../....
    Action
    No action required.

#### NAT3162: No space for Adabas buffer pool header blocks. DB/FNR :1:/:2:.

    Text
    No space for Adabas buffer pool header blocks. DB/FNR .../....
    Explanation
    No additional space was available for Adabas buffer pool header
    blocks.
    Action
    Contact your database administrator.

#### NAT3165: Descriptor :3: invalid or non-existent. DB/FNR :1:/:2:.

    Text
    Descriptor ... invalid or non-existent. DB/FNR .../....
    Explanation
    A descriptor name was either invalid or did not exist in the
    Descriptor Value Table. This error may occur during ADAREC
    regenerate if
     - a file was loaded with an incorrect FDT, or
     - ADAINV was not re-executed following a stop at a
       SYNP checkpoint.
    Action
    Check program and correct error, or contact your database
    administrator. If the problem is not a handling error, run the
    INDEX option of ADAVFY and contact technical support.

#### NAT3166: Error in inverted list index. DB/FNR/Descriptor :1:/:2:/:3:.

    Text
    Error in inverted list index. DB/FNR/Descriptor .../.../....
    Explanation
    An error was detected in an inverted list index; a descriptor
    value was not found during a delete operation.
     - The message shows the name of the descriptor that caused the error.
     - Run the VERIFY option of ADAINV for this descriptor and save
       the output.
     - Reinvert the descriptor.
     - If necessary, restart the database (if this is possible).
     - Send the following information to your nearest support center:
       -  the output of the VERIFY option of ADAINV;
       -  all available PLOGs;
       -  the FDT of the file containing the error;
       -  if the nucleus crashed, the crash directory.
    Action
    See explanation.

#### NAT3167: Error in inverted list index. DB/FNR/Descriptor :1:/:2:/:3:.

    Text
    Error in inverted list index. DB/FNR/Descriptor .../.../....
    Explanation
    An error was detected in an inverted list index; a descriptor
    value was already present during an insert operation.
     - The message shows the name of the descriptor that caused the error.
     - Run the VERIFY option of ADAINV for this descriptor and save
       the output.
     - Reinvert the descriptor.
     - If necessary, restart the database (if this is possible).
     - Send the following information to your nearest support
       center:
       -  the output of the VERIFY option of ADAINV;
       -  all available PLOGs;
       -  the FDT of the file containing the error;
       -  if the nucleus crashed, the crash directory.
    Action
    See explanation.

#### NAT3170: Adabas RABN for the command could not be found. DB/FNR :1:/:2:.

    Text
    Adabas RABN for the command could not be found. DB/FNR .../....
    Explanation
    The Adabas RABN required for the command could not be found.
    Action
    Contact your database administrator.

#### NAT3172: Maximum possible ISN reached. DB/FNR :1:/:2:.

    Text
    Maximum possible ISN reached. DB/FNR .../....
    Explanation
    The maximum possible ISN of the file was reached and no more can be
    allocated.
    Action
    Check program and correct error, or contact your database administrator.

#### NAT3173: An invalid data storage RABN was detected. DB/FNR :1:/:2:.

    Text
    An invalid data storage RABN was detected. DB/FNR .../....
    Action
    Contact your database administrator.

#### NAT3176: Inconsistency detected in an inverted list. DB/FNR :1:/:2:.

    Text
    Inconsistency detected in an inverted list. DB/FNR .../....
    Explanation
    An inconsistency was detected in an inverted list.
    For more information, please refer to the Adabas documentation.
    Action
    Check program and correct error, or contact your database administrator.

#### NAT3177: Record not found in indicated DATA storage block. DB/FNR :1:/:2:.

    Text
    Record not found in indicated DATA Storage block. DB/FNR .../....
    Explanation
    A record could not be found in the Data Storage block which should
    have contained it as indicated by the Address Converter.
    Action
    Contact your database administrator.

#### NAT3182: Necessary ET data was not found in WORK block. DB/FNR :1:/:2:.

    Text
    Necessary ET data was not found in WORK block. DB/FNR .../....
    Explanation
    The necessary ET data was not found in the appropriate WORK block.
    Action
    Correct error or contact your database administrator.

#### NAT3196: Referential integrity violated. DB/FNR/Sub/Con :1:/:2:/:3:/:4:.

    Text
    Referential integrity violated. DB/FNR/Sub/Con .../.../.../....
    Explanation
    The command has been rejected by Adabas.
    Referential integrity has been violated. The error message shows
    the database ID, file number, subcode and constraint name of the
    violated constraint.
    Action
    Handle the referential integrity violation;
    for example, by issuing an appropriate error message.