My Oracle Support Banner

Wrong Result With Connect By Query On 19.16 Release Update (Doc ID 2896881.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.16.0.0.0 to 19.16.0.0.0 [Release 19]
Information in this document applies to any platform.
The wrong results are only seen on version 19.16.

Symptoms

Connect by query returns NULL column (wrong results)

SQL> CREATE TABLE t1 (
  2      id   NUMBER,
  3      name VARCHAR2(10 CHAR)
  4  );

Table created.

SQL>
SQL> INSERT INTO t1 (
  2      id,
  3      name
  4  ) VALUES (
  5      1,
  6      'chars'
  7  );

1 row created.

SQL> COMMIT;

Commit complete.

SQL> WITH w_sub AS (
  2      SELECT
  3          id,
  4          NULL        AS pid,
  5          name,
  6          'X' || name AS new_name
  7      FROM
  8          t1
  9  )
 10  SELECT
 11      *
 12  FROM
 13      w_sub
 14  START WITH
 15      pid IS NULL
 16  CONNECT BY
 17      PRIOR id = pid;

        ID P NAME       NEW_NAME
---------- - ---------- -----------
         1   chars                       <<<<<<< Wrong Result.  NEW_NAME should have a value listed.

Changes

Upgraded to 19.16

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.