MaxDB 7.6 to 7.9 DBMCLI executable program not accessible

[brandon_yick2]

Hi,

I am currently trying to migrate our MaxDB 7.6 system on AIX to MaxDB 7.9 on LINUX. In trying to export the data one of the documents I read said that the LOADER program needed to be on at least the same level as the loader on the target system. I downloaded the MaxDB 7.9 software from SAP marketplace and attempted to upgrade just that component. In doing so it appears that all of the components were upgraded at the same time to 7.9 as well.

At some point I also lost Database Studio connectivity to the database. When trying to connect on the default port it refuses to connect. I tried to start x_server but even though I've specified the default port it still refuses to connect with "Server or DB Unknown message".

I tried to stop the system using the DBMCLI but it only gives me the following message:

executable program not accessible

When I run sdbregview from a working system as well as the faulty system I get the following outputs:

Working system

./sdbregview

Global    /sapdb/programs       7.9.08.23

CDB       /sapdb/CDB/db         7.9.08.23

CL_SDB    /sapdb/clients/SDB    7.9.08.39

SDB       /sapdb/SDB/db         7.9.08.23

Faulty system

sdbregview

Global           /sapdb/programs         7.9.08.39

Legacy           /sapdb/programs         7.6.03.09

CL_MAXDB         /sapdb/clients/MAXDB    7.9.08.39

/sapdb/CDB/db    /sapdb/CDB/db           7.9.08.39

/sapdb/SDB/db    /sapdb/SDB/db           7.9.08.39

It looks like when I ran the upgrade I mistakenly entered the incorrect installation name (should have been SDB instead of /sapdb/SDB/db).

I also made the mistake of not backing up the system before the change.

At this point my only option is to attempt the upgrade of the system again to 7.9 with a full upgrade. The problem is that I cannot even put the database into admin state to perform the upgrade.

Has anyone else encountered this issue before?

[brandon_yick2]

Hi

The issue has been resolved. Besides the wrong installation media installed, some of the files were also missing. SAP removed and installed the correct software and reregistered them with the databases. It can now be seen by Database Studio.

Thank you for your assistance!

Regards,

Brandon

[yashwanthkumar_kethineed]

Hello Brandon,

It's hard to provide you with any definitive answer here without looking at the system.

If you are an SAP customer, please open a incident and attach the diagpkg and the upgrade logs to the message. We will look into it.

Regards, Yashwanth

[brandon_yick2]

Good day Yashwanth

Thank you, I did open an incident at SAP and it was escalated.

They are busy assisting but the basic issue was that the DB software was removed while (accidentally) running the upgrade software. The solution essentially is to reinstall the old DB software. We need to be careful at there is none of the old software currently and SAP has warned that the DB is in a critical state.

Regards,

Brandon

[yashwanthkumar_kethineed]

Hi Brandon,

Yes I remember this incident. You db is in critical state at the moment but usable, and you decided to wait until my colleague is back in the office to help you with the installation. The problem might have caused due to the wrong installation media used to upgrade. Let us know in the incident if you need any help.

Regards, Yashwanth