Hello,
I'm having such messages in my logs, randomly on all of my 3 distributed+redundant systems.
Systems are running on Centos 7, WinCC OA 3.14P10 and Oracle 12.
It can be repeated for several minutes or once.
There is no particular action before I get this.
WCCILdatabg (1), 2018.06.01 06:33:37.537, SYS, SEVERE, 69, Database error, RAIMA Database Error *** Code:-24 (PROGRAMMER/USER error: -24
attempt to access unlocked set/record
C errno = 0: Success)
WCCILdatabg (1), 2018.06.01 06:33:37.537, SYS, SEVERE, 69, Database error, DataBgActionManager, status record first/next-24
WCCILdatabg (1), 2018.06.01 06:33:37.537, SYS, SEVERE, 69, Database error, RAIMA Database Error *** Code:-29 (PROGRAMMER/USER error: -29
cannot free locks within a transaction
C errno = 0: Success)
WCCILdatabg (1), 2018.06.01 06:33:37.537, SYS, SEVERE, 69, Database error, RAIMA Database Error *** Code:-23 (PROGRAMMER/USER error: -23
illegal attempt to lock locked set/record
C errno = 0: Success)
What could cause this ? How to prevent it?
Regards,
RAIMA Database error
- adaneau
- Posts:310
- Joined: Tue Feb 21, 2012 9:49 am
Re: RAIMA Database error
Hi Manh-Thang,
Where is stored your project? Is the CHMOD for DB folder correct? IMHO it looks like an issue with file writing permission...
Where is stored your project? Is the CHMOD for DB folder correct? IMHO it looks like an issue with file writing permission...
- uxout
- Posts:82
- Joined: Wed Jul 20, 2016 12:07 pm
Re: RAIMA Database error
Hello Alexandre,
The projects are stored on /data/SCADA/
I have checked the chmod/chown and it seemed to be correct, but that was my first guessing too.
The projects are stored on /data/SCADA/
I have checked the chmod/chown and it seemed to be correct, but that was my first guessing too.
- kilianvp
- Posts:443
- Joined: Fri Jan 16, 2015 10:29 am
Re: RAIMA Database error
maybe a archive manager is already running?
or you hook into open() via LD_PRELOAD?
or you hook into open() via LD_PRELOAD?
- uxout
- Posts:82
- Joined: Wed Jul 20, 2016 12:07 pm
Re: RAIMA Database error
Archive manager are all removed from progs.
Can I have more detail about the "hook into open() via LD_PRELOAD"?
Can I have more detail about the "hook into open() via LD_PRELOAD"?
- mkerk
- Posts:75
- Joined: Wed Oct 20, 2010 12:25 pm
Re: RAIMA Database error
Hello,
PLease check if the lm_ip process (lock -manager) is running.
Maybe you are running the WinCC OA project with another user as the one who has installed WinCC OA. In this case you have to perform asome steps before starting the project --> check chapter "INstallation --> Linux --> Start and Stop" for further details.
BR,
Mousser
PLease check if the lm_ip process (lock -manager) is running.
Maybe you are running the WinCC OA project with another user as the one who has installed WinCC OA. In this case you have to perform asome steps before starting the project --> check chapter "INstallation --> Linux --> Start and Stop" for further details.
BR,
Mousser
- uxout
- Posts:82
- Joined: Wed Jul 20, 2016 12:07 pm
Re: RAIMA Database error
Oh yeah, that's probably a good hint because there is also some trouble when doing manual online backup ("Error while writing file").
But I have performed the steps described in "Installation" > "Linux" > "Start and Stop" but nothing changed.
FYI, WinCC OA have been installed as root user. The project is being launched as "winccuser".
How can I check if the setup is correct for lm_ip?
But I have performed the steps described in "Installation" > "Linux" > "Start and Stop" but nothing changed.
FYI, WinCC OA have been installed as root user. The project is being launched as "winccuser".
How can I check if the setup is correct for lm_ip?
- mkerk
- Posts:75
- Joined: Wed Oct 20, 2010 12:25 pm
Re: RAIMA Database error
Hello,
since you are using (only) ORACLE for history of alarms and values, you don´t really need the DATA-background Manager. that´s why please add the following config entry in the [data]-section:
[data]
dataBgName = ""
--> with this entry the Data Background Manager will not be started.
After adding this config-entries please Stop the project and all WinCC OA tasks completely. Kill any stray WinCC OA lock manager ("lockmgr") task. Restart
the complete project and check if the lm_ip is restarted correctly with the correct user.
check the behavior.
Please check also, if during ASCII Ouput (Export of data via the ASCII-Manager) errors are written to the logfiles. If this is the case, than maybe you will have to add the following config entry
[data]
lmcType = "LMC_INTERNAL"
LG;
Mousser.
since you are using (only) ORACLE for history of alarms and values, you don´t really need the DATA-background Manager. that´s why please add the following config entry in the [data]-section:
[data]
dataBgName = ""
--> with this entry the Data Background Manager will not be started.
After adding this config-entries please Stop the project and all WinCC OA tasks completely. Kill any stray WinCC OA lock manager ("lockmgr") task. Restart
the complete project and check if the lm_ip is restarted correctly with the correct user.
check the behavior.
Please check also, if during ASCII Ouput (Export of data via the ASCII-Manager) errors are written to the logfiles. If this is the case, than maybe you will have to add the following config entry
[data]
lmcType = "LMC_INTERNAL"
LG;
Mousser.
- nicole.cemeras
- Posts:2
- Joined: Thu Jan 07, 2016 1:28 pm
Re: RAIMA Database error
Hello,
we have a distributed redundant system (24 server) and 2 undistributed redundant systems.
Systems are running on RHEL 7.2, distributed on WinCC OA 3.14 P15, undistributed on WinCC OA 3.15 P9.
But we don't have oracle, we work with history DB and RAIMA alarms.
We have the same error:
WCCILdatabg (1), 2018.07.16 01:07:01.106, SYS, SEVERE, 69, Database error, PVSSStoreObj, ReadLock, ReadLock failed
WCCILdatabg (1), 2018.07.16 01:07:01.107, SYS, SEVERE, 69, Database error, RAIMA Database Error *** Code:-24 (PROGRAMMER/USER error: -24
attempt to access unlocked set/record
C errno = 0: Erfolg)
We checked all permissions, users and gid on project folder, db, wincc_oa, log and /tmp,
we checked all users at processes included lm_ip,
we did all recommended in online-help chapter installation -> linux -> start & stop
like rm -f /tmp/lockmgr, /usr/bin/killall lm_ip and chmod -t /tmp
Would you recommend to do the same and start our projects without databg and with lmc_internal ?
What would be the consequence?
Could data get lost?
Could the data manager block during ascii export?
Regards,
we have a distributed redundant system (24 server) and 2 undistributed redundant systems.
Systems are running on RHEL 7.2, distributed on WinCC OA 3.14 P15, undistributed on WinCC OA 3.15 P9.
But we don't have oracle, we work with history DB and RAIMA alarms.
We have the same error:
WCCILdatabg (1), 2018.07.16 01:07:01.106, SYS, SEVERE, 69, Database error, PVSSStoreObj, ReadLock, ReadLock failed
WCCILdatabg (1), 2018.07.16 01:07:01.107, SYS, SEVERE, 69, Database error, RAIMA Database Error *** Code:-24 (PROGRAMMER/USER error: -24
attempt to access unlocked set/record
C errno = 0: Erfolg)
We checked all permissions, users and gid on project folder, db, wincc_oa, log and /tmp,
we checked all users at processes included lm_ip,
we did all recommended in online-help chapter installation -> linux -> start & stop
like rm -f /tmp/lockmgr, /usr/bin/killall lm_ip and chmod -t /tmp
Would you recommend to do the same and start our projects without databg and with lmc_internal ?
What would be the consequence?
Could data get lost?
Could the data manager block during ascii export?
Regards,
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: RAIMA Database error
If you are using standard archiving you cannot deactivate the DataBg manager as it is needed for specific tasks in the RAIMA database.
Best Regards
Leopold Knipp
Senior Support Specialist
Best Regards
Leopold Knipp
Senior Support Specialist