Automic Workload Automation

VERSI_PATCH is not valid in the context where it is used. SQLSTATE=42703

  • 1.  VERSI_PATCH is not valid in the context where it is used. SQLSTATE=42703

    Posted 03-07-2017 11:59 PM

    VERSI_PATCH field has been removed from UC_VERSI table starting in version 11.
    When running DB Load utility in version 12.0, DB Load may complete but in the log file, you may see the error below. 

    UCUDB - Status: '42S22' Native error: '-206' Msg: ' SQL0206N "VERSI_PATCH" is not valid in the context where it is used. SQLSTATE=42703' 
    20170307/092900.418 - U00003594 UCUDB Ret: '3590' opcode: 'SLUC' SQL Stmnt: 'select VERSI_DBVersion from UC_VERSI order by VERSI_Major desc, VERSI_Minor desc, VERSI_Patch desc' 
    20170307/092900.418 - U00003590 UCUDB - DB error: 'SQLNumResultCols', 'ERROR ', '42S22', ' SQL0206N "VERSI_PATCH" is not valid in the context where it is used. SQLSTATE=42703' 

    If this is the only error you see in DB Load log and DB Load actually shows that it finished, then you can safely ignore this error.

    This will be fixed in 
    Automation Engine 12.1
    Automation Engine 11.2.5
    Automation Engine 12.0.2