After restart, following tracing is seen: "psdgbt: bind csid (1) does not match session csid (XX) psdgbt: session charset is WE8ISO8859P15"

After restart, following tracing is seen: "psdgbt: bind csid (1) does not match session csid (XX) psdgbt: session charset is WE8ISO8859P15"
Photo by JOHN TOWNER / Unsplash

In a situation like a server being rebooted due activities that need to be carried by system administrators and then you get the go to start the databases, you may see the alertlog showing the same trace file appearing repetitively at the alertlog.

The trace file shows the following text:

*** 2023-01-17 15:00:00.000
*** SESSION ID:(1234.12345) 2023-01-17 15:00:00.000
*** CLIENT ID:() 2023-01-17 15:00:00.000
*** SERVICE NAME:(SYS$USERS) 2023-01-17 15:00:00.000
*** MODULE NAME:(emagent_SQL_oracle_database) 2023-01-17 15:00:00.000
*** CLIENT DRIVER:(jdbcthin) 2023-01-17 15:00:00.000
*** ACTION NAME:(ha_flashrecovery) 2023-01-17 15:00:00.000
psdgbt: bind csid (1) does not match session csid (46)
psdgbt: session charset is WE8ISO8859P15

This is what is happening and how to resolve it: