My Oracle Support Banner

Table Column Resizes With JDK 11 & 17 after Some Operations/Refresh. It Works Ok On JDK 8 (Doc ID 2862113.1)

Last updated on APRIL 11, 2022

Applies to:

Oracle SQL Developer - Version 21.4.3 and later
Information in this document applies to any platform.

Symptoms

On  : SQL Developer 21.4.3 latest version
JDK : JDK 11 & JDK 17

This issue should be customizable feature. If one opens the data tab in the table view (double click on the table in the navigation tree and then go to the second tab) and then resizes the widths of the columns here, it looks perfect first. But after some combination of operations with the data (commit, rollback or refresh the data; with some sorting of the data by any column by double click on the arrows in the header) in the random order the sizes are lost. It will be returned to the default sizes in the beginning or to some of the previous width states.

It isn’t important if the widths were changed by simply dragging the column separator (custom size) or double click on the separator (the size of the biggest content in this column). After some operation the size would be changed to the other state.

This issue does not happen with Java 8 (8u322 version). It occurs with Java 11 (11.0.14_9) and Java (17.0.2.x). Also the same behavior could be observed, If we use the view instead of table.

ERROR

No errors but issue with GUI

STEPS

The problem can be reproduced at will with the following steps:

1. Open any table and sort it according to the last column. Important: The width of the column is not enough to show the whole content of the database field.

2. Now resize/minimize the second column so it also will not show the whole content. You can do a refresh afterward or add records to database, but this is not important.

3. Now maximize the second column by double clicking the separator so one could see the whole content of the database field. It could be any other column then the sorted one from the first step.

4. Now just press refresh – the whole layout is changed by this operation.

This is not the only one scenario to reproduce it. One can mix & match the steps, replace or add commits and rollbacks instead of the refresh. The main parts are change the sizes and then change the data by sorting it differently or do the refresh / commit / rollback operation.

Changes

 Using SQL Developer with Java 11 & Java 17

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.