Hi Tom,

I have recently upgraded a couple of databases (12.1 -> 19.17) and remote oracle client (19.3 - 19.14 ) on application servers connecting upgraded databases.

There exist only one case where 'set feedback off' is not working as expected when I commit from sqlplus client 19.14 to only one of those upgraded 19.17 DBs.

How may I trace sqlplus to find out reason of unexpected behaviour for 'set feedback of'.

Here is the test case I produced.

#########Connect to a database ( test1 ) on the same db_host and using same db_oracle_home where "SET FEEDBACK OFF" is working as EXPECTED.

infa64@dwhsas15> sqlplus test_user@dwhpx-scan:1521/test1

SQL*Plus: Release 19.0.0.0.0 - Production on Mi Jan 25 09:47:34 2023
Version 19.14.0.0.0

Copyright (c) 1982, 2021, Oracle. All rights reserved.

Kennwort eingeben:
Letzte erfolgreiche Anmeldezeit: Mi Jan 25 2023 09:46:38 +01:00

Verbunden mit:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.17.0.0.0

SQL> commit;

Transaktion mit COMMIT abgeschlossen.

SQL> set feedback off
SQL> commit;
SQL> exit
Verbindung zu Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.17.0.0.0 beendet



#########Connect to a different database ( test2 ) on the same db_host and using same db_oracle_home where "SET FEEDBACK OFF" is NOT working as EXPECTED.

infa64@dwhsas15> sqlplus test_user@dwhpx-scan:1521/sim

SQL*Plus: Release 19.0.0.0.0 - Production on Mi Jan 25 09:48:01 2023
Version 19.14.0.0.0

Copyright (c) 1982, 2021, Oracle. All rights reserved.

Kennwort eingeben:
Letzte erfolgreiche Anmeldezeit: Mi Jan 25 2023 06:01:50 +01:00

Verbunden mit:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.17.0.0.0

SQL> commit;

Transaktion mit COMMIT abgeschlossen.

SQL> set feedback off
SQL> commit;

Transaktion mit COMMIT abgeschlossen. --<< UNEXPECTED >>--

SQL>