Hello all,
What is the recommended best practice when patching OA Systems and upgrading project versions? Is there a tool to view what Version/Patch a project is currently operating at or conforms to? (I am aware you can view the version from the Diagnostic tool.. but not Patch level)
Also - what are the potential pitfalls for not applying a patch "Additional Installation Steps" procedure or applying these steps in the incorrect order?
example: Project is v3.13p1 copied to v3.13p8 server then the operator applies additional installation steps in the reverse order as follows:
[ol][*]import update_P006.dpl[*][*]import update_P005.dpl[*][*]import update_P004.dpl[*][/ol]
Cheers,
Kurk Kembel
Patching OA
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Patching OA
Hello,
the ASCII-files must be imported in the correct order of the ascending numbers.
Otherwise the structure of internal datapoint types might not be correct.
E.g. if the same dp type is updated/modified with the file for P004 and P006 the structure will not be correct if P004 is imported in the last step.
When opening the "About" panel in the project administration you get the information which patch you have installed.
Best Regards
Leopold Knipp
Senior Support Specialist
the ASCII-files must be imported in the correct order of the ascending numbers.
Otherwise the structure of internal datapoint types might not be correct.
E.g. if the same dp type is updated/modified with the file for P004 and P006 the structure will not be correct if P004 is imported in the last step.
When opening the "About" panel in the project administration you get the information which patch you have installed.
Best Regards
Leopold Knipp
Senior Support Specialist