Skip to Content
author's profile photo Former Member
Former Member

SAPDB upgrade error .. sharing violation with ../pgm/sapni.dll

Hello,

I am trying to upgrade the SAPDB 7.3.00 Build 20 to 7.3.00 Build 53.

I have 4 instances in my Content Server. As it was complaining I have more than one instance when I run the SDBUPD.EXE, I deleted the registration of 3 instances and kept only one instance ie CPD.

When I start the import as per the note 530567 it's quiting abnormally saying there is a sharing violation in opening the file .../pgm/sapni.dll

I stopped all services, no dbmcli, no dbmgui,XServer is stopped and all the databases are stopped. It's funny I can even rename the sapni.dll. I don't know what is running behind and what is causing the sharing violation of this file.

Can some one help me with this.. below is the error what I am getting.

*********************************************************

F:\temp>sdbupd -d CPD -u control,<password>

SAP DB INSTANCE UPDATE

**********************

starting installation Th, Feb 10, 2005 at 09:18:35

operating system: Windows I386 NT 5.0 Service Pack 3

callers working directory: F:/temp

installer directory: F:/temp

archive directory: F:/temp

beginning to check sap db instances

resume broken instance update

finding instance type...

finding starting release...

finding migration strategy...

looking for running instances...

checking paramfile modifications...

looking for domain user...

checking data consistency for database migration...

checking SAP DB instance "CPD" successfully Th, Feb 10, 2005 at 09:18:46

starting preparing phase of package Base 7.3.00.53 32 bit

-


update release check... ok

update binary magic check... ok

checking interferences to other packages... ok

collecting data finished:

independent data path: C:/sapdb/data

independent program path: C:/sapdb/programs

start extraction test run of "F:/temp/SAPDBBAS.TGZ"

test run failed: cannot extract pgm/sapni.dll: sharing violation during open of

existing file - no file(s) of "F:/temp/SAPDBBAS.TGZ" extracted!

maybe any sap db software is running... please stop all

SAP DB instance update exited abnormally at Th, Feb 10, 2005 at 09:18:48

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Feb 10, 2005 at 03:18 PM

    Hi Guru,

    I must really ask you to open an OSS message for your issue.

    One of your main problems will be the fact that your 4 SAP DB instances are probably all based on the same software installation. That makes it a little more challenging to update all single instances (as you already noticed).

    You probably have to rename a few more files (sapni.dll, serv.exe, sqltcp.dll etc.) to be able to get further with the update of your first instance. But, as I wrote you at the start of my answer, this really needs to be handled the normal way (i.e. an OSS message for queue BC-DB-SDB).

    Kind regards,

    Roland

    P.S.: when you open the OSS message, be sure to include a working OS connection to the Content Server machine, that would make the supporter's work the fastest.

    Message was edited by: Roland Mallmann

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Roland,

      Finally it works!!! A simple tweak in the note 530567.

      It fails if we execute the SDBUPD.EXE from ..\temp or from any other directory where ever you uncar the files.

      Istead copy all the files (the patch files which need to import) to the folder ..\sapdb\Programs\ and then execute the SDBUPD.EXE (In our case C:\sapdb\Programs)

      The error what we found was, it was failing while extracting all the *TGZ files and writing to the respective folders bin, pgm, env etc..irrespective of having the correct path in environmental varaibles.

      Thanks

      Guru

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.