go-ora: rows.Next() halts with no exceptions

On go-ora/v2 v2.4.27 got a problem. When I iterate through the sql.rows sometimes it halts with no exceptions and timeouts. I did same on v1.2.1 with no problem

The discussion was here #https://stackoverflow.com/questions/73048029/rows-next-halts-after-some-number-of-rows

The max length of field is 7000, but it doesn’t affect the time when iteration stops. It stops even when I ORDER BY length(TEXT) asc

DDL of TICKET table:

-- auto-generated definition
create table TICKET
(
    ID                   NUMBER           not null
        constraint TICKET_ID_PK
            primary key,
    APPLICANT_ID         NUMBER           not null
        constraint TICKET_APPLICANT_FK
            references USERS,
    SOLUTION_USER_PHONE  VARCHAR2(56),
    PRIORITY_ID          NUMBER
        constraint TICKET_PRIORITY_FK
            references TICKET_PRIORITY,
    STATE_ID             NUMBER           not null
        constraint TICKET_STATE_FK
            references TICKET_STATE,
    SERVICE_ID           NUMBER           not null
        constraint TICKET_SERVICE_FK
            references SERVICE,
    CHANGE_ID            VARCHAR2(255),
    GUID                 VARCHAR2(56),
    REMEDY_ID            VARCHAR2(50),
    HEADER               VARCHAR2(100)    not null,
    CREATE_DATE          NUMBER           not null,
    LAST_EDIT_DATE       NUMBER,
    SLA_DATE             NUMBER,
    FINISH_DATE          NUMBER,
    SYNC_MASK            NUMBER default 0 not null,
    TEXT                 CLOB,
    SOLUTION             CLOB,
    TEXT_COPY            CLOB,
    USER_CONTACT_ID      NUMBER
        constraint TICKET_USER_CONTACT_ID_FK
            references USER_CONTACT,
    LAST_SOLUTION_DATE   NUMBER,
    WAIT_PERIOD          NUMBER,
    STATE_REASON         VARCHAR2(255),
    IMPACT_ID            NUMBER
        constraint TICKET_IMPACT_FK
            references IMPACT,
    URGENCY_ID           NUMBER
        constraint TICKET_URGENCY_FK
            references URGENCY,
    WEIGHT_ID            NUMBER,
    REQUEST_TYPE_ID      NUMBER
        constraint TICKET_REQUEST_TYPE_FK
            references REQUEST_TYPE,
    SOURCE_ID            NUMBER
        constraint TICKET_SOURCE_FK
            references SOURCE,
    STATE_REASON_ID      NUMBER
        constraint TICKET_STATE_REASON_FK
            references TICKET_STATE_REASON,
    OPER_CAT_1           VARCHAR2(60),
    OPER_CAT_2           VARCHAR2(60),
    OPER_CAT_3           VARCHAR2(60),
    PROD_CAT_1           VARCHAR2(60),
    PROD_CAT_2           VARCHAR2(60),
    PROD_CAT_3           VARCHAR2(60),
    WORKK                VARCHAR2(255),
    WORKK_RE             VARCHAR2(255),
    SUB_WORK             VARCHAR2(255),
    SUB_WORK_RE          VARCHAR2(255),
    SOLUTION_CAT_1       VARCHAR2(60),
    SOLUTION_CAT_2       VARCHAR2(60),
    SOLUTION_CAT_3       VARCHAR2(60),
    ASSIGNED_NOTE        VARCHAR2(256),
    SOLUTION_USER_LOGIN  VARCHAR2(128),
    SOLUTION_GROUP_NAME  VARCHAR2(128),
    SOLUTION_USER_ID     NUMBER
        constraint TICKET_SOLUTION_USER_FK
            references USERS,
    SOLUTION_GROUP_ID    NUMBER
        constraint TICKET_SOLUTION_GROUP_FK
            references SUPPORT_GROUP,
    LAST_EDIT_USER_LOGIN VARCHAR2(255)
)
/

create index IDX_TICKET
    on TICKET (STATE_ID, APPLICANT_ID)
/

create index IDX_TICKET_SOL_GROUP_ID
    on TICKET (SOLUTION_GROUP_ID)
/

create index IDX_TICKET_SOL_USER_ID
    on TICKET (SOLUTION_USER_ID)
/

create index IDX_TICKET_STATE_ID
    on TICKET (STATE_ID)
/

create index IDX_TICKET_GUID
    on TICKET (GUID)
/

create index IDX_TICKET_REMEDY_ID
    on TICKET (REMEDY_ID)
/

create index IDX_TICKET_CREATE_DATE
    on TICKET (CREATE_DATE)
/