On WebLogic 12.2.1, DB Leasing Failing When Configured With MSSQL DB Server
(Doc ID 2407117.1)
Last updated on MARCH 12, 2021
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Environment configured to have server migration in WLS Cluster based on DB Leasing. With MS SQL database server to host the leasing table <DBLEASING_ACTIVE>
With configuration 'Migration Policy' is Always on, JMS Topic do not work. No errors are seen in WebLogic server logs, but the Health/Monitoring of the Persistent Store / JMSServer shows blank on Console.
Test to Connect to MS SQL DB from WebLogic DataSource is Success. User configured to connect to DB has read write access to DB table.
Debug on Database side show INSERT come in from WebLogic but fails to write to 5th column (timestamp column) of table <DBLEASING_ACTIVE>
declare @p1 int
exec sp_prepexec @p1 output,N'@P0 nvarchar(4000),@P1 nvarchar(4000),@P2 int',N'INSERT INTO DBLEASING_ACTIVE ( SERVER, INSTANCE, DOMAINNAME, CLUSTERNAME, TIMEOUT ) VALUES ( @P0 , @P1 , ''mydomain'' , ''mydomainCluster'' , DATEADD(second, @P2 ,GETDATE()) ) ',N'service.SINGLETON_MASTER',N'-1494341451235512321/ManagedServer-0ggOVF',30
Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.
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