Hi
I am currently testing a product update from a PVSS 3.7 project (redundant, distributed, CentOS 4.7) to the current version 3.16 patch 3 (CentOS 7.4).
I have been following the instructions given in the manual regarding updating projects.
I have set chown -R root:root :/ and chmod -R 777 ./ on the project folder as well as started the project administration with root privileges. The old project is recognised in project administration and I am able to kick off the update via the UI.
The update runs smoothly for a while and for a number of DB files when suddenly (after 56k lines of success log) the following happens:
[sub]
########################################################
/opt/WinCC_OA/3.16/bin/WCCOAtoolRevise -proj YYYYYY /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901 Started at : 2018.11.07;14:26:07:969
########################################################
WCCOAtoolRevise(1), 2018.11.07 14:26:07.970: "3.7" does not match with manager version: "3.16" !!
[2018.11.07;14:26:07:985 ] Copy from /opt/WinCC_OA/3.16/dbdfiles/version_3.16/AlertHist.dbd to /home/XXXXXX/XXXXXX/XXXXXX/db/wincc_oa/al1247439901/ rc: 1
[2018.11.07;14:26:07:986 ] ------------------------------------------------------
[2018.11.07;14:26:07:986 ] /opt/WinCC_OA/3.16/bin/initdb -y /home/XXXXXX/XXXXXX/XXXXXX/db/wincc_oa/al1247439901/AlertHist
[2018.11.07;14:26:07:986 ] ------------------------------------------------------
Raima Database Manager 4.5 [Build 1]
Database Initialization Utility
Copyright (C) 1984-1996, Raima Corporation, All Rights Reserved
/home/XXXXXX/XXXXXX/XXXXXX/db/wincc_oa/al1247439901/AlertHist initialized
[2018.11.07;14:26:08:144 ] ------------------------------------------------------
[2018.11.07;14:26:08:144 ] /opt/WinCC_OA/3.16/bin/dbrev -q /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/AlertHist /home/XXXXXX/XXXXXX/XXXXXX/db/wincc_oa/al1247439901/AlertHist
[2018.11.07;14:26:08:144 ] ------------------------------------------------------
Raima Database Manager 4.5 [Build 1]
Database Restructure Utility
Copyright (C) 1984-1996, Raima Corporation, All Rights Reserved
dbrev compilation complete
Processing file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/alertrec.db containing 581957 records
dbrev terminated due to errors, db_status = 3
WCCOAtoolRevise(1), 2018.11.07 14:26:09.032, SYS, SEVERE, 54, Unexpected state, An error occurred , RecordSet /home/XXXXXX/XXXXXX/XXXXXX/db/wincc_oa/al1247439901/ creation aborted! at:209 file:/opt/workspaces/workspace/Exe/DataTools/Revise/Revise.cxx
-------------------------------------------------------
WCCOAtoolConvertDb(1), 2018.11.07 14:26:09.034, SYS, SEVERE, 54, Unexpected state, DoConvertDb, systemCall, /opt/WinCC_OA/3.16/bin/WCCOAtoolRevise -proj YYYYYY /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901 exitCode: 4
[2018.11.07;14:26:09:034 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/AlertHist.dbd
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/alertrec.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/alertrg.key
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/alertrd.key
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/alertpr.key
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/abitvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/abit32va.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/acharvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/aintvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/auintvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/afltvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/atxtvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/atimvar.db
[2018.11.07;14:26:09:036 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/adynvar.db
[2018.11.07;14:26:09:037 ] remove converted file /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901/adpidvar.db
WCCOAtoolConvertDb(1), 2018.11.07 14:26:09.037, SYS, WARNING, 54, Unexpected state, DoConvertDb, convertDbSubDir, /home/XXXXXX/XXXXXX/XXXXXX/db/old/al1247439901 not converted
WCCOAtoolConvertDb(1), 2018.11.07 14:26:09.037, SYS, SEVERE, 54, Unexpected state, DoConvertDb, createNewDbs, can NOT copy & initialise
WCCOAtoolConvertDb(1), 2018.11.07 14:26:09.037, DBG, -------------------------------------------------------
-------------------------------------------------------
WCCOAtoolConvertDb(1), 2018.11.07 14:26:09.037, DBG, DB conversion error. Aborted!
DB conversion error (-1). Aborted at: 2018.11.07;14:26:09:037
[/sub]
Unfortunately, I was not able to find useful hints about the issue anywhere on the forums, documentation or the net and would appreciate anyone pointing me in the right direction.
Cheers
Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
- weirdal
- Posts:34
- Joined: Thu Mar 12, 2015 11:37 am
Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
For a more detailed analysis the database directories are needed. Only with the log entreis the cause cannot be seen. If you need assistance please get in contact with your common WinCC OA support.
The alert archive which gives the error was created at 2009.07.13 01:05 and therefore contains data for historical alerts which occurred in July 2009.
Is this (old) data needed after the upgrade?
Best Regards
Leopold Knipp
Senior Support Specialist
The alert archive which gives the error was created at 2009.07.13 01:05 and therefore contains data for historical alerts which occurred in July 2009.
Is this (old) data needed after the upgrade?
Best Regards
Leopold Knipp
Senior Support Specialist
- weirdal
- Posts:34
- Joined: Thu Mar 12, 2015 11:37 am
Re: Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
Thank you for your quick reply!
Data has to be kept for either 5 or 10 years, I guess. I'll find out.
How can I determine the creation date of an archive, is it the number in the folder name in ticks since 1.1.1970?
So I would remove all the old data (just delete the folders?) that is probably not needed and then try again?
Will file an additional support request on Monday.
Data has to be kept for either 5 or 10 years, I guess. I'll find out.
How can I determine the creation date of an archive, is it the number in the folder name in ticks since 1.1.1970?
So I would remove all the old data (just delete the folders?) that is probably not needed and then try again?
Will file an additional support request on Monday.
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
Yes, the timestamp saved in the folder name is seconds since 1970.01.01.
You can convert it to a time by using the following web page: https://www.epochconverter.com/
Alert archives which are not needed anymore you can remove from the filesystem and try to do the conversion again (based on the original database).
Best Regards
Leopold Knipp
Senior Support Specialist
You can convert it to a time by using the following web page: https://www.epochconverter.com/
Alert archives which are not needed anymore you can remove from the filesystem and try to do the conversion again (based on the original database).
Best Regards
Leopold Knipp
Senior Support Specialist
- weirdal
- Posts:34
- Joined: Thu Mar 12, 2015 11:37 am
Re: Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
Thanks a lot!
I did:
rm -rf al12*
rm -rf al13*
Which basically removes all historic data before Tuesday, May 13, 2014.
Then restarted the update... Works like a charm now, says update was finished successfully!
So in case I need the historical data I would have to contact the support about the issue, right?
Anyway, have a nice weekend!
I did:
rm -rf al12*
rm -rf al13*
Which basically removes all historic data before Tuesday, May 13, 2014.
Then restarted the update... Works like a charm now, says update was finished successfully!
So in case I need the historical data I would have to contact the support about the issue, right?
Anyway, have a nice weekend!
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Question about DB error during Upgrade from PVSS 3.7 to WinCC OA 3.16
If you need historical data please get in contact with your common WinCC OA support.
Probably there are some solutions to restore historical data by doing manual operations in the database (while the project is stopped).
Best Regards
Leopold Knipp
Senior Support Specialist
Probably there are some solutions to restore historical data by doing manual operations in the database (while the project is stopped).
Best Regards
Leopold Knipp
Senior Support Specialist