Fatal RDB Manager error when in a Project running as a service

[emaddocks]

Hi,

We are currently runing WinCC OA 3.17 P009 on RHEL 8.2. We have successfully connected to an Oracle 19c Server DB using the Oracle 19c client after carrying out the required patches detailed in the 3.17 P009 help file (and another necessary step found hiddden in a 3.16 support page)

When the Project is run 'normally' through the Project Administrator it starts up all mangers including the RDB Manager with no issues.

When the Project is registered to startup automatically as a service using the same OS user it starts up all managers except the RBD manager which fails with the following fatal error:

Code: Select all

WCCOArdb     (97), 2021.06.11 10:03:51.033, SYS,  FATAL,       2, Manager Stop, OCCI loading error. Check the Oracle Client Version and the config entry "oracleClientVersion"!, /opt/WinCC_OA/3.17/bin/OCCIWrapper_19.so

oracleClientVersion = 19 is in the config file of the project and is required for it to run 'normally'.

Are there any other steps further to those detailed in the "Oracle Client 19c Installation under Linux" page of the WinCC OA 3.17 help file and the additional symbolic link found on the 3.16 support page to get the RDB Manger to work when the project is run as a service?

[kilianvp]

We had the same issue! Here is how you solve the issue:

in /etc/systemd/system/winccoa@.service

add Environment with your Environment variables: ORACLE_HOME, ORACLE_BASE, LD_LIBRARY_PATH,

for example

Code: Select all

[Unit]
Description=WinCC OA project '%i'

[Service]

ExecStart=/opt/WinCC_OA/3.17/bin/WCCILpmon -proj %i
ExecStop=/opt/WinCC_OA/3.17/bin/WCCILpmon -proj %i -stopWait
#User=
Environment="ORACLE_HOME=/opt/oracle/product/19.0.0/client_1" 
Environment="ORACLE_BASE=/opt/oracle" 
Environment="LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/opt/oracle/product/19.0.0/client_1/lib:/opt/WinCC_OA/3.17/bin"
/bin:"

[Install]
WantedBy=multi-user.target

don't forget todo

Code: Select all

systemctl daemon-reload

to apply the changes.

Restart the service and it should work now.

[emaddocks]

Thanks for that! It's working now.

For anyone working at ETM please add this into the help file and consolidate the 3.16 and 3.17 steps.