Feedback on /eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx

[david-olivari]

HI,
A customer complained that the documentation is unclear
https://techsupport.enterprisedb.com/rt/ticket/89888/
And I tend to concur.
On both this page
https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_linux/
and once I asked the customer to refer to this [page] (https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/)
More confusion arose.
From tests , it seems you can just use the command yum upgrade ppas-xdb and follow the steps regarding backing up conf files and the likes.
BUt, can we have any ambiguity stripped off the documentation please?

[david-olivari]

Also, I tried the upgrade process myself , and looks like it doesn't really matter what package is specified in the upgrade.
But the customer requires clarity from the docs (Understandably)

Current installation

ppas-xdb-publisher-6.2.19-1.rhel8.x86_64
ppas-xdb-console-6.2.19-1.rhel8.x86_64
ppas-xdb-libs-6.2.19-1.rhel8.x86_64
ppas-xdb-6.2.19-1.rhel8.x86_64
ppas-xdb-subscriber-6.2.19-1.rhel8.x86_64

Upgrade

using

yum upgrade ppas-xdb

This is what will be carried out

Installing:
 edb-xdb                   x86_64        7.4.0-1.rhel8         edb         10 k
     replacing  ppas-xdb.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-console.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-libs.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-publisher.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-subscriber.x86_64 6.2.19-1.rhel8
Installing dependencies:
 edb-xdb-console           x86_64        7.4.0-1.rhel8         edb        1.6 M
 edb-xdb-libs              x86_64        7.4.0-1.rhel8         edb         13 M
 edb-xdb-publisher         x86_64        7.4.0-1.rhel8         edb         43 k
 edb-xdb-subscriber        x86_64        7.4.0-1.rhel8         edb         11 k

using
yum upgrade edb-xdb*

root@pg_stdby ~]# yum upgrade edb-xdb*
Last metadata expiration check: 3:43:09 ago on Wed 01 Feb 2023 08:06:58 EST.
Dependencies resolved.
================================================================================
 Package                   Architecture  Version               Repository  Size
================================================================================
Installing:
 edb-xdb                   x86_64        7.4.0-1.rhel8         edb         10 k
     replacing  ppas-xdb.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-console.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-libs.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-publisher.x86_64 6.2.19-1.rhel8
     replacing  ppas-xdb-subscriber.x86_64 6.2.19-1.rhel8
Installing dependencies:
 edb-xdb-console           x86_64        7.4.0-1.rhel8         edb        1.6 M
 edb-xdb-libs              x86_64        7.4.0-1.rhel8         edb         13 M
 edb-xdb-publisher         x86_64        7.4.0-1.rhel8         edb         43 k
 edb-xdb-subscriber        x86_64        7.4.0-1.rhel8         edb         11 k

[drothery-edb]

@david-olivari I don't have permission to view that ticket. Are there any details there that you could share here that sheds more light on what exactly is causing the customer's confusion? I believe if they are upgrading to 7.x they should use edb-xdb*. @zahid75 can you confirm?

[david-olivari]

Hi Dee, That's the same conclusion I came to. But if you read the procedural steps in the documentation, some confusion may arise. I will attach the transcript of the conversation with the customer on the issue for you to verify the customer concerns and what has been done I think the Customer wants to see the documentation removed of ambiguity, and some is present I suggest someone install the legacy package and tries to upgrade using the online documentation and verify if it clear enough or not David *Ticket Start * - xDB 6.2.18, RHEL 8.5 - Controller / Publisher, Oracle 19.13 - Subscriber, PostgreSQL 12.9 Wanting to upgrade xDB to 7.4. Your documentation includes the following : 1. yum upgrade ppas-xdb* <https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_linux/#:~:text=yum%20upgrade%20ppas%2Dxdb*> 2. And, yum update edb-xdb* <https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/#:~:text=by%20the%20following%3A-,yum%20update%20edb%2Dxdb*,-Be%20sure%20to> 3. And, , in the example immediately following, yum update ppas-xdb* <https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/#:~:text=yum%20update%20ppas%2Dxdb*> Which is correct? Thank you! *My REPLY #1 * Hello Alex, We have seen the issue with the documentation, and I have requested some clarification to development. However, we went on reading and doing some tests locally, and based on those, you may want to go ahead with the upgrade anyway. If you have installed version 6 using `yum` , you can verify using the command shown below. ``` # yum list installed | grep xdb ppas-xdb.x86_64 6.2.19-1.rhel8 @EDB ppas-xdb-console.x86_64 6.2.19-1.rhel8 @EDB ppas-xdb-libs.x86_64 6.2.19-1.rhel8 @EDB ppas-xdb-publisher.x86_64 6.2.19-1.rhel8 @EDB ppas-xdb-subscriber.x86_64 6.2.19-1.rhel8 @EDB ``` then, following the detailed instructions [here]( https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/) is all you need. This has been tested at our end locally with success. I hope this helps and looking forward to your feedback David *CUSTOMER REPLY #2 * David, I did not make it clear when originally submitting this ticket, please bear in mind that this request is **not** urgent. At this time, we're in the *planning* phases,with our **goal** being to upgrade all of our xDB environments (*Development, Test and Production*) prior to the date which xDB 6.2.x loses Standard Support (*May 25th, 2023*). All that to say, while I thank you for sharing the link, I am afraid that I remain confused as to *which* packages to update. In Step 6, the document recommends to execute [`yum update edb-xdb*`]( https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/#:~:text=by%20the%20following%3A-,yum%20update%20edb%2Dxdb*,-Be%20sure%20to) while just a couple of sentences later, the document shows an `example`, updating **different** packages, via [`yum update ppas-xdb*`]( https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/#:~:text=yum%20update%20ppas%2Dxdb*). # When upgrading from xDB 6.2.x to xDB 7.x, which are the correct packages to `update` via `yum`, `ppas-xdb*` or `edb-xdb*`? Thank you. *MY REPLY #3 * Which tries to confirm that using edb-xdb is all that's required Hi Alex, I have raised an internal asking explicitly to strip out any ambiguity from the documentation. I will freeze the ticket for a week, and follow up events. I will keep you informed. Regards David P.S. For your information: As part of the support is to test and reproduced, looks like the upgrade commands are interchangeable as the demo below shows. But , we agree that if this so, it has to be reflected in the docs. # Current installation ``` ppas-xdb-publisher-6.2.19-1.rhel8.x86_64 ppas-xdb-console-6.2.19-1.rhel8.x86_64 ppas-xdb-libs-6.2.19-1.rhel8.x86_64 ppas-xdb-6.2.19-1.rhel8.x86_64 ppas-xdb-subscriber-6.2.19-1.rhel8.x86_64 ``` # Upgrade using `yum upgrade ppas-xdb` This is what will be carried out ``` Installing: edb-xdb x86_64 7.4.0-1.rhel8 edb 10 k replacing ppas-xdb.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-console.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-libs.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-publisher.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-subscriber.x86_64 6.2.19-1.rhel8 Installing dependencies: edb-xdb-console x86_64 7.4.0-1.rhel8 edb 1.6 M edb-xdb-libs x86_64 7.4.0-1.rhel8 edb 13 M edb-xdb-publisher x86_64 7.4.0-1.rhel8 edb 43 k edb-xdb-subscriber x86_64 7.4.0-1.rhel8 edb 11 k ``` using `yum upgrade edb-xdb*` ``` ***@***.***_stdby ~]# yum upgrade edb-xdb* Last metadata expiration check: 3:43:09 ago on Wed 01 Feb 2023 08:06:58 EST. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: edb-xdb x86_64 7.4.0-1.rhel8 edb 10 k replacing ppas-xdb.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-console.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-libs.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-publisher.x86_64 6.2.19-1.rhel8 replacing ppas-xdb-subscriber.x86_64 6.2.19-1.rhel8 Installing dependencies: edb-xdb-console x86_64 7.4.0-1.rhel8 edb 1.6 M edb-xdb-libs x86_64 7.4.0-1.rhel8 edb 13 M edb-xdb-publisher x86_64 7.4.0-1.rhel8 edb 43 k edb-xdb-subscriber x86_64 7.4.0-1.rhel8 edb 11 k ``` *----- END of thread *

…

On Thu, 2 Feb 2023, 16:14 Dee Dee Rothery, ***@***.***> wrote: @david-olivari <https://github.com/david-olivari> I don't have permission to view that ticket. Are there any details there that you could share here that sheds more light on what exactly is causing the customer's confusion? I believe if they are upgrading to 7.x they should use edb-xdb*. @zahid75 <https://github.com/zahid75> can you confirm? — Reply to this email directly, view it on GitHub <#3599 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2RVGHZ7WHPLGECW2ZBKG5DWVPMONANCNFSM6AAAAAAUOWITTM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[drothery-edb]

Thanks, @david-olivari. I see where the confusion arose now. @zahid75 can you assign someone from the team to help us straighten out the upgrade instructions? If someone can answer the following questions we could probably put together a draft that the SME could then review?

• Was the intent to have two topics in the v7 docs:
  • one for an in place upgrade if upgrading from a 7.x version (using the upgrade command)
  • one for upgrading from 6.2 using "update"?
• should both be referencing the edb-xdb* package?

Another change that I think is needed, but not directly related to this issue, is to add dnf, apt-get, and zypper commands for the various OSs the different package managers support. Do you agree?

cc: @mlewandowski-edb

[david-olivari]

Yes, I agree. Everyone should find what they need on the docs David

…

On Tue, 7 Feb 2023, 13:11 Dee Dee Rothery, ***@***.***> wrote: Thanks, @david-olivari <https://github.com/david-olivari>. I see where the confusion arose now. @zahid75 <https://github.com/zahid75> can you assign someone from the team to help us straighten out the upgrade instructions? If someone can answer the following questions we could probably put together a draft that the SME could then review? - Was the intent to have two topics in the v7 docs: - one <https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_linux/> for an in place upgrade if upgrading from a 7.x version (using the upgrade command) - one <https://www.enterprisedb.com/docs/eprs/latest/installing/upgrading_replication_server/upgrading_with_xdb_rpm_package/> for upgrading from 6.2 using "update"? - should both be referencing the edb-xdb* package? Another change that I think is needed, but not directly related to this issue, is to add dnf, apt-get, and zypper commands for the various OSs the different package managers support. Do you agree? cc: @mlewandowski-edb <https://github.com/mlewandowski-edb> — Reply to this email directly, view it on GitHub <#3599 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2RVGH3PHPMYQJIG2IAAVZTWWJCZ5ANCNFSM6AAAAAAUOWITTM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[david-olivari]

Hi Dee, Just to let you know, I have requested for you to be able to view support portal tickets. That should make things easier for you in the future. Regards David P.S. You could try with this link https://techsupport.enterprisedb.com/rt/ticket/89888/

…

On Thu, 2 Feb 2023 at 16:14, Dee Dee Rothery ***@***.***> wrote: @david-olivari <https://github.com/david-olivari> I don't have permission to view that ticket. Are there any details there that you could share here that sheds more light on what exactly is causing the customer's confusion? I believe if they are upgrading to 7.x they should use edb-xdb*. @zahid75 <https://github.com/zahid75> can you confirm? — Reply to this email directly, view it on GitHub <#3599 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2RVGHZ7WHPLGECW2ZBKG5DWVPMONANCNFSM6AAAAAAUOWITTM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[david-olivari]

Hi,
Customer has asked for an update. They need to know as part of their project.
If nobody is going to take the ticket on , can I confidently tell the customer that all is required is
yum upgrade edb-xdb*
And disregard the docs altogether?

[drothery-edb]

Hi Dee, Just to let you know, I have requested for you to be able to view support portal tickets. That should make things easier for you in the future. Regards David P.S. You could try with this link https://techsupport.enterprisedb.com/rt/ticket/89888/
…
On Thu, 2 Feb 2023 at 16:14, Dee Dee Rothery @.> wrote: @david-olivari https://github.com/david-olivari I don't have permission to view that ticket. Are there any details there that you could share here that sheds more light on what exactly is causing the customer's confusion? I believe if they are upgrading to 7.x they should use edb-xdb. @zahid75 https://github.com/zahid75 can you confirm? — Reply to this email directly, view it on GitHub <#3599 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2RVGHZ7WHPLGECW2ZBKG5DWVPMONANCNFSM6AAAAAAUOWITTM . You are receiving this because you were mentioned.Message ID: @.*>

Thank you so much! Appreciate it.

[drothery-edb]

Hi, Customer has asked for an update. They need to know as part of their project. If nobody is going to take the ticket on , can I confidently tell the customer that all is required is yum upgrade edb-xdb* And disregard the docs altogether?

@zahid75 @mlewandowski-edb can you confirm, please?

[drothery-edb]

@david-olivari the doc clarifications are now live.