SDBUPD: Patch MaxDB 7.6.00.18 to 7.6.00.26 fails

[Former Member]

Hello.

I'm trying to patch my MaxDB from 7.6.00.18 to 7.6.00.26.

When running SDBUPD i get the error-message 'please start installation as local administrator', though i am admin. I tried it with every admin-account, every time with the same result.

My server is a I386, WinXP Prof.

Has anybody got an idea?

Thanks in advance

Knut

[Former Member · Accepted solution]

Hi Roland.

Here comes the final part of my install.log:

STDOUT: start real extraction of "E:/SAP/NW04s/Install/SAPNW2004sSneakPreviewABAP/MaxDB_7.6.0_RDBMS_Installations/MAXDB_WINDOWS_I386/SDBMSG.TGZ"

STDOUT: extracting: drwxr-xr-x 0 2005-11-30 20:26:01 msg/

STDOUT: extracting: -rw-rr 834 2005-11-30 17:29:09 msg/SDBMsg_Admin.xml

STDOUT: extracting: -rw-rr 676 2005-11-30 17:29:09 msg/SDBMsg_Backup.xml

STDOUT: extracting: -rw-rr 2279 2005-11-30 17:29:09 msg/SDBMsg_Catalog.xml

STDOUT: extracting: -rw-rr 733 2005-11-30 17:29:09 msg/SDBMsg_Converter.xml

STDOUT: extracting: -rw-rr 4044 2005-11-30 17:29:09 msg/SDBMsg_Data.xml

STDOUT: extracting: -rw-rr 333 2005-11-30 17:29:09 msg/SDBMsg_DBMCLI.xml

STDOUT: extracting: -rw-rr 5230 2005-11-30 17:29:09 msg/SDBMsg_DBMEd.xml

STDOUT: extracting: -rw-rr 328 2005-11-30 17:29:09 msg/SDBMsg_DBMLog.xml

STDOUT: extracting: -rw-rr 3179 2005-11-30 17:29:09 msg/SDBMsg_DBMScd.xml

STDOUT: extracting: -rw-rr 60258 2005-11-30 17:29:09 msg/SDBMsg_DBMSrv.xml

STDOUT: extracting: -rw-rr 1047 2005-11-30 17:29:09 msg/SDBMsg_DBMSrvTest.xml

STDOUT: extracting: -rw-rr 1263 2005-11-30 17:29:09 msg/SDBMsg_DBProc.xml

STDOUT: extracting: -rw-rr 553 2005-11-30 17:29:09 msg/SDBMsg_DIAGNOSE.xml

STDOUT: extracting: -rw-rr 4487 2005-11-30 17:29:09 msg/SDBMsg_FileDir.xml

STDOUT: extracting: -rw-rr 561 2005-11-30 17:29:09 msg/SDBMsg_IOMan.xml

STDOUT: extracting: -rw-rr 561 2005-11-30 17:29:09 msg/SDBMsg_Join.xml

STDOUT: extracting: -rw-rr 1609 2005-11-30 17:29:09 msg/SDBMsg_KernelCommon.xml

STDOUT: extracting: -rw-rr 901 2005-11-30 17:29:09 msg/SDBMsg_KSQL.xml

STDOUT: extracting: -rw-rr 801 2005-11-30 17:29:09 msg/SDBMsg_LiveCache.xml

STDOUT: extracting: -rw-rr 172 2005-11-30 17:29:09 msg/SDBMsg_Loader.xml

STDOUT: extracting: -rw-rr 3036 2005-11-30 17:29:09 msg/SDBMsg_Log.xml

STDOUT: extracting: -rw-rr 2645 2005-11-30 17:29:09 msg/SDBMsg_Messages.xml

STDOUT: extracting: -rw-rr 369 2005-11-30 17:29:09 msg/SDBMsg_ObjectContainer.xml

STDOUT: extracting: -rw-rr 3159 2005-11-30 17:29:09 msg/SDBMsg_OMS.xml

STDOUT: extracting: -rw-rr 172 2005-11-30 17:29:09 msg/SDBMsg_OPMSG.xml

STDOUT: extracting: -rw-rr 172 2005-11-30 17:29:09 msg/SDBMsg_Optimizer.xml

STDOUT: extracting: -rw-rr 301 2005-11-30 17:29:09 msg/SDBMsg_Query.xml

STDOUT: extracting: -rw-rr 308 2005-11-30 17:29:09 msg/SDBMsg_QueryRewrite.xml

STDOUT: extracting: -rw-rr 1199 2005-11-30 17:29:09 msg/SDBMsg_Recovery.xml

STDOUT: extracting: -rw-rr 2573 2005-11-30 17:29:09 msg/SDBMsg_Rst.xml

STDOUT: extracting: -rw-rr 2466 2005-11-30 17:29:09 msg/SDBMsg_RTEComm.xml

STDOUT: extracting: -rw-rr 605 2005-11-30 17:29:09 msg/SDBMsg_RTEConf.xml

STDOUT: extracting: -rw-rr 889 2005-11-30 17:29:09 msg/SDBMsg_RTEDBState.xml

STDOUT: extracting: -rw-rr 4276 2005-11-30 17:29:09 msg/SDBMsg_RTEDiag.xml

STDOUT: extracting: -rw-rr 814 2005-11-30 17:29:09 msg/SDBMsg_RTEIO.xml

STDOUT: extracting: -rw-rr 3577 2005-11-30 17:29:09 msg/SDBMsg_RTEMem.xml

STDOUT: extracting: -rw-rr 1170 2005-11-30 17:29:09 msg/SDBMsg_RTETask.xml

STDOUT: extracting: -rw-rr 528 2005-11-30 17:29:09 msg/SDBMsg_RunTime.xml

STDOUT: extracting: -rw-rr 1055 2005-11-30 17:29:09 msg/SDBMsg_SAPDBAlgo.xml

STDOUT: extracting: -rw-rr 562 2005-11-30 17:29:09 msg/SDBMsg_SAPDBMem.xml

STDOUT: extracting: -rw-rr 1209 2005-11-30 17:29:09 msg/SDBMsg_Savepoint.xml

STDOUT: extracting: -rw-rr 3388 2005-11-30 17:29:09 msg/SDBMsg_SharedSQL.xml

STDOUT: extracting: -rw-rr 9463 2005-11-30 17:29:09 msg/SDBMsg_SQLMan.xml

STDOUT: extracting: -rw-rr 7303 2005-11-30 17:29:09 msg/SDBMsg_SrvTasks.xml

STDOUT: extracting: -rw-rr 1882 2005-11-30 17:29:09 msg/SDBMsg_Table.xml

STDOUT: extracting: -rw-rr 883 2005-11-30 17:29:09 msg/SDBMsg_ToolsCommon.xml

STDOUT: extracting: -rw-rr 401 2005-11-30 17:29:09 msg/SDBMsg_Transaction.xml

STDOUT: extracting: -rw-rr 3764 2005-11-30 17:29:09 msg/SDBMsg_ZZZTest.xml

STDOUT: checking unpacked archive... MSG: check file "msg/SDBMsg_Recovery.xml": ok

MSG: check file "msg/SDBMsg_FileDir.xml": ok

MSG: check file "msg/SDBMsg_Rst.xml": ok

MSG: check file "msg/SDBMsg_Converter.xml": ok

MSG: check file "msg/SDBMsg_OMS.xml": ok

MSG: check file "msg/SDBMsg_Loader.xml": ok

MSG: check file "msg/SDBMsg_ZZZTest.xml": ok

MSG: check file "msg/SDBMsg_DBProc.xml": ok

MSG: check file "msg/SDBMsg_Table.xml": ok

MSG: check file "msg/SDBMsg_SAPDBMem.xml": ok

MSG: check file "msg/SDBMsg_RTETask.xml": ok

MSG: check file "msg/SDBMsg_RunTime.xml": ok

MSG: check file "msg/SDBMsg_KernelCommon.xml": ok

MSG: check file "msg/SDBMsg_RTEIO.xml": ok

MSG: check file "msg/SDBMsg_Transaction.xml": ok

MSG: check file "msg/SDBMsg_RTEMem.xml": ok

MSG: check file "msg/SDBMsg_DBMCLI.xml": ok

MSG: check file "msg/SDBMsg_DBMSrv.xml": ok

MSG: check file "msg/SDBMsg_DBMScd.xml": ok

MSG: check file "msg/SDBMsg_OPMSG.xml": ok

MSG: check file "msg/SDBMsg_SrvTasks.xml": ok

MSG: check file "msg/SDBMsg_Data.xml": ok

MSG: check file "msg/SDBMsg_QueryRewrite.xml": ok

MSG: check file "msg/SDBMsg_Log.xml": ok

MSG: check file "msg/SDBMsg_DIAGNOSE.xml": ok

MSG: check file "msg/SDBMsg_RTEConf.xml": ok

MSG: check file "msg/SDBMsg_DBMLog.xml": ok

MSG: check file "msg/SDBMsg_Admin.xml": ok

MSG: check file "msg/SDBMsg_IOMan.xml": ok

MSG: check file "msg/SDBMsg_Messages.xml": ok

MSG: check file "msg/SDBMsg_Catalog.xml": ok

MSG: check file "msg/SDBMsg_Optimizer.xml": ok

MSG: check file "msg/SDBMsg_Query.xml": ok

MSG: check file "msg/SDBMsg_RTEComm.xml": ok

MSG: check file "msg/SDBMsg_DBMSrvTest.xml": ok

MSG: check file "msg/SDBMsg_KSQL.xml": ok

MSG: check file "msg/SDBMsg_SAPDBAlgo.xml": ok

MSG: check file "msg/SDBMsg_RTEDiag.xml": ok

MSG: check file "msg/SDBMsg_Backup.xml": ok

MSG: check file "msg/SDBMsg_Savepoint.xml": ok

MSG: check file "msg/SDBMsg_ToolsCommon.xml": ok

MSG: check file "msg/SDBMsg_LiveCache.xml": ok

MSG: check file "msg/SDBMsg_DBMEd.xml": ok

MSG: check file "msg/SDBMsg_ObjectContainer.xml": ok

MSG: check file "msg/SDBMsg_SharedSQL.xml": ok

MSG: check file "msg/SDBMsg_RTEDBState.xml": ok

MSG: check file "msg/SDBMsg_SQLMan.xml": ok

MSG: check file "msg/SDBMsg_Join.xml": ok

STDOUT: ok

MSG: writing 16 packages

MSG: net install registry size = 112862 bytes

MSG: wrote install registry (129039 bytes)

STDOUT: installation of MaxDB Server finished successfully Sa, May 20, 2006 at 21:46:11

STDOUT: please reboot your system for the changes to take effect!

MSG: packagedata of package Base changed

MSG: packagedata of package PCR 7104 changed

MSG: packagedata of package PCR 7300 changed

MSG: packagedata of package PCR 7301 changed

MSG: packagedata of package PCR 7403 changed

MSG: packagedata of package PCR 7600 changed

MSG: packagedata of package ODBC changed

MSG: packagedata of package DB Analyzer changed

MSG: packagedata of package SQLDBC changed

MSG: packagedata of package SQLDBC 7600 changed

MSG: packagedata of package JDBC changed

MSG: packagedata of package Server Utilities changed

MSG: packagedata of package Database Kernel changed

MSG: packagedata of package Redist Python changed

MSG: packagedata of package Loader changed

MSG: packagedata of package Messages changed

MSG: writing 16 packages

MSG: net install registry size = 119471 bytes

MSG: wrote install registry (140070 bytes)

MSG: install registry successfully unlocked

For me (as a real rookie) everything looks 'fine'.

Any suggestions?

Thanks and regards

Knut

[roland_mallmann · Accepted solution]

Hi,

is there a MaxDBUpdate file aswell in the same directory? If yes, how does the end of the content look like?

Thanks & regards,

Roland

[Former Member · Accepted solution]

Hi.

The only log i get is 'MaxDBSoftware_install-31.05.2006-19.16.log' from SDBUPD in my local TEMP-directory (where i tried to start the upgrade):

-

---

CALL: SDBUPD -d NSP control,xxxx -INSTANCE -profile APO LiveCache

STDERR: please start installation as local administrator!

STDERR: installation exited abnormally at We, May 31, 2006 at 19:16:02

-

---

No MaxDBUpdate file ....

Thanks and regards

Knut

[former_member229109 · Accepted solution]

Hello Knut,

-> With which user did you start database upgrade?

-> Did you start it with 'administrator'?

Could you please run 'regedit' & check the permissions for the registry keys

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAP DBTech-*

Please update with the output of the following commands:

Dbmcli -s inst_enum

Dbmcli -s db_enum

Sdbregview -l

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia.

1. Yes, i've been working under account 'administrator' on XP, 'adminstrator' is of course member of group 'administrators'

2. Regedit says, that group 'administrators' has full rights on all entries of SAP DBTech-*

3. Dbmcli -s inst_enum

OK

7.6.00.18 e:\sapdb\nsp\db

4. Dbmcli -s db_enum

OK

NSP e:\sapdb\nsp\db 7.6.00.18 slow

NSP e:\sapdb\nsp\db 7.6.00.18 fast

5. Sdbregview -l

DB Analyzer e:/sapdb/programs 7.6.00.18 32 bit valid

Server Utilities e:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7300 e:/sapdb/programs 7.3.00.54 valid

Base e:/sapdb/programs 7.6.00.18 32 bit valid

Redist Python e:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7301 e:/sapdb/programs 7.3.01.19 valid

JDBC e:/sapdb/programs 7.6.00.16 valid

Messages e:/sapdb/programs MSG 0.3017 valid

ODBC e:/sapdb/programs 7.6.00.18 32 bit valid

Database Kernel e:/sapdb/nsp/db 7.6.00.18 32 bit valid

Loader e:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7104 e:/sapdb/programs 7.1.04.45 valid

PCR 7600 e:/sapdb/programs 7.6.00.09 32 bit valid

SQLDBC e:/sapdb/programs 7.6.00.18 32 bit valid

SQLDBC 7600 e:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7403 e:/sapdb/programs 7.4.03.40 32 bit valid

Any suggestion?

Best regards and thanks so far

Knut

[former_member229109 · Accepted solution]

Hello Knut,

his case was discussed with database developers. And at that moment it's under analysis to get clear on this issue & how to solve it.

If you are the official SAP customer, I recommend you to create the ticket to SAP on 'BC-DB-SDB' queue.

Thank you and best regards, Natalia Khlopina

[former_member229109 · Accepted solution]

Hello Knut,

could you please update your database to the 7.6.00.28 version. Please update with your results after that.

Are you the official SAP customer?

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia.

In fact, I'm employee of a SAP customer runnig SAP NW04 on ORACLE, but this installation belongs to the SAP Sneak preview NW04s, and so it is, as far as i know, not possible for me to get official SAP support or to create a ticket for that MaxDB problem.

I will try to update db to 7.6.00.28.

Thanks so far and best regards

Knut

[Former Member · Accepted solution]

Hi Natalia.

Problem solved, thanks a lot.

Best regards

Knut

[roland_mallmann]

Hi Knut,

can you please show me the last 20 lines or so from the file <drive>:\sapdb\data\wrk\MaxDBSoftware_install-<date>-<time>.log?

Thanks & regards,

Roland