SIMATIC WinCC Open Architecture Forum

often the DataBackground-manager reports an error.
But I couldn't identifiy the fault.
Any help is appreciated. Thank you.


Here's a copy/paste from the log:

WCCILdatabg (1), 2013.03.26 14:16:28.952, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:16:28.952, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 1
WCCILdatabg (1), 2013.03.26 14:18:10.972, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:18:10.972, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 2
WCCILdatabg (1), 2013.03.26 14:19:52.993, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:19:52.993, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 3
WCCILdatabg (1), 2013.03.26 14:21:35.026, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:21:35.026, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 4
WCCILdatabg (1), 2013.03.26 14:23:17.047, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:23:17.047, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 5
WCCILdatabg (1), 2013.03.26 14:24:59.066, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2013.03.26 14:24:59.067, PARAM,FATAL, 54, Unexpected state, DataBgDpIntern, init, Datenbank konnte nicht geoeffnet werden, bitte lm_ip pruefen!

System info:
WinCC OA 3.11 , no patches,
Linux CentOS,
distributed system

Hello,

we have this problem as well on a RHEL V.311 SP1 p062 machine. Had there been any solution provided?

Sabine Walitzi

Does the lm_ip process run ? It should have been started by the pmon.
And there should be a local socket as /tmp/lockmgr with all users having rw rights

Same problem here, WinCC OA 3.14 P24 under CentOS 7.

Somehow, the socket /tmp/lockmgr existed but was owned by user root (OA project runs with another user).

Deleting the /tmp/lockmgr file, and restarting the project, seemed to solve the problem.

Same problem with v3.18 P003 under RHEL 8.2 - After continuous run of the project from 20 hours.
Checked lm_ip it was stopped. May we know the reason why it stopped after 20 hours of test.


WCCILdatabg (1), 2021.11.18 08:48:53.998, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:48:53.998, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 1
WCCILdatabg (1), 2021.11.18 08:50:36.014, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:50:36.015, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 2
WCCILdatabg (1), 2021.11.18 08:52:18.031, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:52:18.031, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 3
WCCILdatabg (1), 2021.11.18 08:54:00.047, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:54:00.047, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 4
WCCILdatabg (1), 2021.11.18 08:55:42.062, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:55:42.063, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 5
WCCILdatabg (1), 2021.11.18 08:57:24.079, SYS, SEVERE, 69, Database error, DbDirDb, open
WCCILdatabg (1), 2021.11.18 08:57:24.079, PARAM,FATAL, 54, Unexpected state, DataBgDpIntern, init, Datenbank konnte nicht geoeffnet werden, bitte lm_ip pruefen!
WCCILdatabg (1), 2021.11.18 08:57:24.079, SYS, INFO, 181, Closing connection to (SYS: 2 Data -num 0 CONN: 1)
WCCILdata (0), 2021.11.18 08:57:24.082, SYS, INFO, 39, Connection lost, MAN: (SYS: 2 Data -num 1 CONN: 1), Connection closed
WCCILdatabg (1), 2021.11.18 08:57:24.083, SYS, INFO, 39, Connection lost, MAN: (SYS: 2 Data -num 0 CONN: 1), Connection closed
WCCILdatabg (1), 2021.11.18 08:57:24.083, SYS, SEVERE, 39, Connection lost, (SYS: 2 Data -num 0 CONN: 1), exiting ...
WCCILdatabg (1), 2021.11.18 08:57:24.083, SYS, INFO, 0, , DataBgDpIntern, closeDatabases, Databases closed.

A check if the lm_ip is running when starting the process monitor. If it is not running it will be started.
In WinCC OA there is no functionality to stop the lm_ip. Even if the project is stopped the lm_ip will remain running.
Possibly the lm_ip was stopped by another application.

Best Regards
Leopold Knipp
Senior Support Specialist

The socket /tmp/lockmgr existed but was owned by the user root. Thats the reason another user can not restart it.

After deleting the socket using sudo commands, the project restarted and seems to be working.

Thanks for your support Leoknipp. Problem resolved.