Server Log: Could not get next sequence for client_stats?

Classic Servoy
1

Since a week or so I get this in the Servoy-Admin Server Log:

2017-02-16 12:32	pool-2-thread-2	ERROR	com.servoy.j2db.util.Debug	Could not get next sequence for client_stats (using unsupported db-identity for client_stats?)	 	 
2017-02-16 12:32	RMI TCP Connection(554)-192.168.15.103	ERROR	com.servoy.j2db.util.Debug	Could not get next sequence for client_stats (using unsupported db-identity for client_stats?)

How can I fix this?

Server Information:
Servoy version 7.4.9 -releaseNumber 2047
JVM Information:
java.vm.name=Java HotSpot™ 64-Bit Server VM
java.version=1.8.0_121
Operating System Information:
os.name=Mac OS X
os.version=10.11.6
os.arch=x86_64

DB: PostgreSQL 9.6.2

Regards

2

Thomas,

Do you have a client_stats table in your logserver?
If yes, what is the sequence type of column pk_id?

If it is db-identity, then this is a combination we do not support (hence the log message)

Rob

3

Hi Rob,

I have nothing changed or set to db-identity. Have a look at the current setting:
[attachment=0]client_stats.png[/attachment]

client_stats.png
client_stats.png759×173 21 KB

4

That looks completely standard.
When I run a client with a standard setup it works as expected.
For some reason it can’t generate a new id for the clientstats.pk_id column.

If you also see this in your dev environment, you could try dropping/recreating the client-stats table (from server editor, the log-server has a create-client-stats button).

Rob

5

Hi Rob,

I have dropped/deleted the client_stats table on the customers SQL Server.
After a new import of the solution the client_stats table is recreated and I get no more error log about the unsupported db-identity.
Now all is looking good and it seems to be working as it should.

Thomas