"psdgbt: bind csid (1) does not match session csid (873)" and "psdgbt: session charset is AL32UTF8"

After restart of the server and starting the database you can notice a lot of generated trace files:

Fri Aug 25 10:18:48 2017 Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Fri Aug 25 10:18:59 2017 Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Fri Aug 25 10:19:10 2017 Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Fri Aug 25 10:19:23 2017 Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc: Fri Aug 25 10:19:50 2017 Errors in file /oracle/orcldb/base/diag/rdbms/orcldb_dc1/orcldb/trace/orcldb_ora_2131.trc:

Each trace file contains information with error:

psdgbt: bind csid (1) does not match session csid (873) psdgbt: session charset is AL32UTF8

Reason: The base problem is that there is a session that connected too early (before the the database was fully open) and is now stuck with AL32UTF8. There is no problem with the database.
Related bugs:

• Bug 9329749 - TB: FAN: PSDGBT: BIND CSID (1) DOES NOT MATCH SESSION CSID (178)
• Bug 13010721 : "PSDGBT: BIND CSID (1) DOES NOT MATCH SESSION CSID (873)" FROM OMS

Solution:
Restart OMS agent:

/oracle/product/12.1/agent12c/agent_inst/bin/emctl stop agent /oracle/product/12.1/agent12c/agent_inst/bin/emctl start agent

In case that problem still persists:

1. stop the listener for this database instance.
2. then restart the database instance.
3. then restart the listener.