MaxDB install registry locked after upgrade error

[Former Member]

Hi,

Has anyone seen this and/or got any advice on how to get around it please?

I basically tried to run two parallel MaxDB upgrades on one server and this one (BJP) failed, the other one finished successfully, but the problem is I now cannot get BJP to restart again, the upgrade script keeps bombing out with:

INFO: Checking for installation files locked by running processes...

INFO: | File | Process Id | Command Line

INFO: | /sapdb/BJP/db/pgm/kernel | 14479 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

INFO: | /sapdb/BJP/db/lib/liboms.so | 14480 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

INFO: | /sapdb/BJP/db/pgm/kernel | 14480 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: There are files locked by the following processes:

ERR: | Process Id | Command Line

ERR: | 14479 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: | 14480 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: Terminate all locking processes and rerun the installer.

ERR: Error checking Upgrade

ERR: There are files locked by the following processes:

ERR: | Process Id | Command Line

ERR: | 14479 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: | 14480 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: Terminate all locking processes and rerun the installer.

ERR: Upgrade failed

ERR: Error checking Upgrade

ERR: There are files locked by the following processes:

ERR: | Process Id | Command Line

ERR: | 14479 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: | 14480 | /sapdb/BJP/db/pgm/kernel BJP -diagpipe 8

ERR: Terminate all locking processes and rerun the installer.

INFO: Closing registry

WRN: package registry is in readonly mode

INFO: install registry successfully unlocked

I've got the other DB shutdown still and have tried restarting BJP a few times (so the PID's have changed as the processes listed above got shutdown completely), all to no avail. I have a customer message open already, but any suggestions in the meantime (if I can get any on a Sunday morning Aus time!) would be much appreciated.

Thanks,

Chaz.

[Former Member]

And before anyone suggests it I've already had the Unix server reboot, but it didnt help.

[former_member188883]

Hi Chaz,

If you are receiving the error 14479 code, it is highly likely you have problems in the Windows registry. The Windows registry is the central engine of your PC and controls all functions and programs. Problems with the Windows registry such as error 14479 can cause serious damage to your system if left unchecked.

Hope this is useful.

Regards,

Deepak Kori

[Former Member]

Deepak - Thanks for your input, but its actually a Unix server as can be seen from the paths in the error log. And I mentioned it was a Unix server when I rebooted it too.

A SAP MaxDB Support team member (Lars Bredermann) suggested to manually perform the upgrade following this Note: 1338844. There is a specific bug in the 7.8 upgrade procedure, that we are attempting to upgrade to, apparently.

I havent yet performed the manual steps, but Lars was confident this will fix it. I will update this message once the work is complete and the problem is solved or not.

[Former Member]

OK, in summary the problem has been resolved...however the note 1338844 didnt entirely resolve it as we also hit an "isDummy" error when implementing the workaround/manual instructions in the note which resulted in SAP's dev support team downporting a fix from a 7.9 upgrade package, which in turn fixed the second problem. Database is now upgraded.

SAP are creating a note for this second problem and hopefully updating the search tags for note 1338844 as well, to make it easier to find (it only contained "upgrade" and "isolation".

[thorsten_zielke]

As I was involved in this case let me add that I have created note 1666985 to briefly describe the 'IsDummy'-issue and how to workaround (use newer sdbupd, fixed with PTS 1240325).

Thorsten