EHP5 upgrade MAXDB version require

[Former Member]

Hello All,

we are in a process of upgrading our SAP Sandbox system from EHP3 (SP08) to EHP5.

we are on Linux (x86_64)  with database MaxDB (7.6.03.009)

is this version require to upgrade my instance to EHP5, or with system upgrade do i also need to upgrade my DATABASE.

if database upgrade is require can any one please let me know how to upgrade database on our environment.

Thanks in Advance,

Vardhan.

[nelis · Accepted solution]

Hi,

Yes, you are required to upgrade your database also. Please check service.sap.com/pam -> EHP5 FOR SAP ERP 6.0 -> Database Platforms -> MaxDB. What version you can require is dependant on your Linux distribution.

Also check service.sap.com/instguides -> Database Upgrades -> MaxDB for information on upgrading.

Nelis

[Former Member · Accepted solution]

Hi Nelis,

I have went through the upgrade guide EHP5 requires  7.7.04.028  or more.

now i need to upgrade my database from 7.6 to 7.7 ,

do i need to down load installation of maxdb software of 7.7 and start process using SDBUPD

please advice

Thanks,

vardhan.

[nelis · Accepted solution]

Hi Vardhan,

Please also read the upgrade guide for MaxDB which I gave you the path above to find it.

You do not use SDBUPD, you must use the DBUPDATE script which instructions are provided for in the update documentation.

Regards,

Nelis

[Former Member · Accepted solution]

Hi Neils,

Thanks for the reply.

I have done following steps

i am on Unicode version.

and i have downloaded the following cd from SMP  51035704_8  maxdb 7.7

in user root i have executed sh DBUPDATE.SH

after giving  "Please enter DBM user was succesfull"

and later error says

ERROR: Upgrade tool not found or not executable

--> If MaxDB RDBMS CD has been copied to disk

--> check existance and authorizations of file:

--> /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28/DATA_UNITS/MAXDB_LINUX_X86_64/../MAXDB_LINUX_X86_64/SDBUPD

--> Otherwise, please contact the SAP support team.

Please advice

thanks

Vardhan.

[nelis · Accepted solution]

To make sure your authorizations are correct, I would as root run:

chmod -R 777 /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28

Then try again.

Nelis

[Former Member · Accepted solution]

Hi Nelis

looks like my last run was failure how do i reset this to do a fresh upgrade

starting installation Mo, Apr 02, 2012 at 09:11:32

operating system: Linux X86-64 2.6.32.12 0.7-xen GLIBC 2.11.1

callers working directory: /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28/DATA_UNITS/MAXDB_LINUX_X86_64

installer directory: /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28/DATA_UNITS/MAXDB_LINUX_X86_64

install registry locked by another process (pid=12035)

MaxDB instance update exited abnormally at Mo, Apr 02, 2012 at 09:11:32

E R R O R : upgrade failure !

--> Please refer to the protocol file:

/sapdb/data/wrk/MaxDBUpgrade_install-<date>-<time>.log

Please advice

[nelis · Accepted solution]

Did you check /sapdb/data/wrk/MaxDBUpgrade_install-<date>-<time>.log for errors ?

Nelis

[Former Member · Accepted solution]

Yes it says process locked by another PID

Here is my log  MaxDBUpdate_install-02.04.2012-09.42.log

INSTALLER_INFO: Version = 7.7.04 Build 028-123-194-355IN

STALLER_INFO: Changelist = 194355

INSTALLER_INFO: MakeId = 329257

INSTALLER_INFO: Type = kit

SYS_INFO: Host name = sgmw-s-relde6

SYS_INFO: System = Linux

SYS_INFO: Architecture = X86-64

SYS_INFO: Version = 2.6.32.12

SYS_INFO: Subversion = 0.7-xen

SYS_INFO: C Runtime = GLIBC 2.11.1

CALL: SDBUPD -d DE6 -u superdba,********* -INSTANCE -profile APO LiveCache

STDOUT:

        MaxDB INSTANCE UPDATE

STDOUT:         *********************

STDOUT: starting installation Mo, Apr 02, 2012 at 09:42:00

STDOUT: operating system: Linux X86-64 2.6.32.12 0.7-xen GLIBC 2.11.1

STDOUT: callers working directory: /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28/DATA_UNITS/MAXDB_LINUX_X86_64

STDOUT: installer directory: /root/Downloads/RDBMS_MAXDB_7.7.04_Build_28/DATA_UNITS/MAXDB_LINUX_X86_64

MSG: InstallRegistry: space check ok: 89688940 kb on / (407173052 kb total) available

STDERR: install registry locked by another process (pid=12035)

STDERR: MaxDB instance update exited abnormally at Mo, Apr 02, 2012 at 09:42:00

MSG: don't need to write package registry

[nelis · Accepted solution]

Someone else may need to help here but I would check the permissions on the following files:

/etc/opt/sdb

/var/lib/sdb and sub directories

It may be that because the permissions were not correct when you ran the install the first time that it has either set or copied the incorrect permissions on the above locations. That is my educated guess from MaxDB installations, failing which hopefully someone else may help you.

Nelis

[Former Member · Accepted solution]

i was able to access sdb while up-gradation here are my permissions of sdb

-r--r--r-- 1 root sapinst   90 2012-01-03 10:46 sdb

[nelis · Accepted solution]

Do you have a /sapdb/data/config/Databases.ini_lock file or a /usr/spool/sql/ini/SAP_DBTech.ini_lock file ? What are their permissions if they exist ?

Nelis

[Former Member · Accepted solution]

Hi Neil

i dont know what crazy thing i have done after restarting  my  whole instance upgrade went fine

Thanks,

Vardhan.

[nelis · Accepted solution]

Ok, glad to hear your problem is resolved. Don't forget to patch your database too after the upgrade.

Nelis

[Former Member · Accepted solution]

Thanks Neils

for you quick response

For EHP5 upgradation this version is enough

do i need to apply patch after database upgrade, is this mandatory,

if no i would like to apply patch after my EHP up-gradation

[nelis · Accepted solution]

It is not mandatory no, just good practice and could prevent other issues during the upgrade that may be related to the database. I certainly would prefer having "peace of mind" knowing my database is up-to-date before starting a major upgrade. You should also check your parameters too after a database upgrade using the dbanalyzer(check note 1111426) before proceeding.

Good luck!

Nelis