Error upgrade from MaxDB 7.6 to MaxDB 7.7 -> ERR_SHMNOTAVAILABLE

[MarkusKlein]

Hey guys,

for a EHP5 (Rampup) upgrade i had to upgrade our Database from 7.6.06.16 to at least MaxDB 7.7.04.28. This unfortunatelly fails with the following error:

MSG: file "D:/sapdb/BIL/db/misc/create_demo_db.cmd" modified by installer
MSG: file "D:/sapdb/BIL/db/misc/drop_demo_db.cmd" modified by installer
MSG: file "D:/sapdb/BIL/db/doc/FirstSteps/maxdbenv.cmd" modified by installer
SYS: "D:\sapdb\BIL\db\bin\dbmsrvctl.exe" start
SYS: "D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: ERR
SYS: "D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: -24832,ERR_SHMNOTAVAILABLE: Shared memory not available
SYS: "D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: -24827,ERR_SHMALLOCFAILED: ID D:\sapdb\data\wrk\.M770428.dbm.shi, requested size 2600
STDERR: error occured while executing "D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg
STDERR: "D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: ERR
"D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: -24832,ERR_SHMNOTAVAILABLE: Shared memory not available
"D:\sapdb\programs\pgm\dbmcli.exe" -R "D:\sapdb\BIL\db" inst_reg: -24827,ERR_SHMALLOCFAILED: ID D:\sapdb\data\wrk\.M770428.dbm.shi, requested size 2600
STDERR: MaxDB instance update exited abnormally at Mo, Dec 27, 2010 at 13:41:07

A ".M770428.dbm.shi" does not exists in folder "D:\sapdb\data\wrk"

Has anyone an idea what could be the problem?

thx in advance and best regards

Markus

[lbreddemann · Accepted solution]

Hi there,

which Windows are you on?

If you're already use UAC, then you've to disable it and retry the upgrade.

Make sure to use an administrator account as well for the upgrade.

If this does not help, I'd propose to open a support message for this.

regards,

Lars

[MarkusKlein · Accepted solution]

>

> Hi there,
> 
> which Windows are you on?
> If you're already use UAC, then you've to disable it and retry the upgrade.
> 
> Make sure to use an administrator account as well for the upgrade.
> 
> If this does not help, I'd propose to open a support message for this.
> 
> regards,
> Lars

Hi Lars,

thx for the answer.

I am on Windows 2003 R2 x64 SP2, so no UAC - at least not that i know off

I am using <SID>adm for the upgrade which is a member of the local administrator group.

I already have opend a support message, but no answer so far

So what's the deal with the missing Shared Memory file. Shouldnt the installer/upgrade program just create it?

best regards,

Markus

[lbreddemann · Accepted solution]

>

> Hi Lars,
> 
> thx for the answer.
> 
> I am on Windows 2003 R2 x64 SP2, so no UAC - at least not that i know off 

hmm.. in that case, I believe there is also this "Run as Administrator" option just like in Windows 7... (i just don't have a Win2003/R2 Install. at hand right now...).

If so, choose this!

> I am using <SID>adm for the upgrade which is a member of the local administrator group.

Yeah, I know - but this is not the "gof mode" anymore with the more recent Windows versions.

> I already have opend a support message, but no answer so far 

What should I say? Right component? Right priority?

> So what's the deal with the missing Shared Memory file. Shouldnt the installer/upgrade program just create it?

This file should in fact be create by DBMCLI as it is the shared memory management file used for the communication between DBM-Client and the DBMServer process(es).

It should be recreated/reused whenever you access the database via DBMCLI.

regards,

Lars

[MarkusKlein · Accepted solution]

 hmm.. in that case, I believe there is also this "Run as Administrator" option just like in Windows 7... (i just don't have a Win2003/R2 Install. at hand right now...).
If so, choose this!

The "Run as Administrator" functionality is just available for Windows 7 and Windows 2008 (R2?) Server. I havent stumbled upon this functionality on a Windows 2003 Server.

Yeah, I know - but this is not the "gof mode" anymore with the more recent Windows versions.

Shall i try another user?

What should I say? Right component? Right priority?

I used the component "BC-DB-SDB-UPG". But as priority i used "middle", as a SAP Partner (Demo-System) i have my doubts i am allowed to set it to "high". Even tho for us it is really important because i just a have a tiny timeframe for applying the EHP5.

best regards,

Markus

[MarkusKlein · Accepted solution]

What about if i copy a Shared Memeory File from another MaxDB installation? Its not the exact same version tho - its 7.7.2.17

regards,

Markus

[lbreddemann · Accepted solution]

>

> What about if i copy a Shared Memeory File from another MaxDB installation? Its not the exact same version tho - its 7.7.2.17
> 
> regards,
> Markus

I doubt that this will work . The file itself really is just a little management file but it must be creatable.

Have you granted the "create global objects" privilege to the <sid>adm/SAPService<sid> user you're using?

regards,

Lars

[MarkusKlein · Accepted solution]

Hello Lars,

i just added the user <SID>adm explicit to the "Create Global Objects" policy on the server and rerun the sdbupd command - the group "administrators" where <sid>adm is a member of is already assigned to this policy. The error still occurs tho

regards,

Markus

[MarkusKlein · Accepted solution]

When i check the "dbmsrv_BILBO.prt" i get the following log entries:

2010-12-28 09:22:23 0x0000113c INF          1 DBMSrvCo A DBM Server client connection was established at 2010-12-28 09:22:23 (client process has process ID 692 on computer bilbo.abs-team.de).
2010-12-28 09:22:23 0x0000113c INF        283 DBMSrv   Command 'inst_unreg' is being executed.
2010-12-28 09:22:24 0x0000113c INF        419 DBMSrv   Command 'inst_unreg' has ended with return code 0.
2010-12-28 09:22:24 0x0000113c INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 692 on computer bilbo.abs-team.de).
2010-12-28 09:22:34 0x00000fd0 INF          1 DBMSrvCo A DBM Server client connection was established at 2010-12-28 09:22:34 (client process has process ID 4032 on computer bilbo.abs-team.de).
2010-12-28 09:22:34 0x00000fd0 INF        283 DBMSrv   Command 'inst_reg' is being executed.
2010-12-28 09:22:34 0x00000fd0 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'inst_reg' has ended and failed with return code -24832.
                    0x00000fd0 ERR     -24832 DBMSrv   ERR_SHMNOTAVAILABLE: Shared memory not available
                    0x00000fd0 ERR     -24827 DBMSrv   ERR_SHMALLOCFAILED: ID D:\sapdb\data\wrk\.M770428.dbm.shi, requested size 2600
2010-12-28 09:22:34 0x00000fd0 INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 4032 on computer bilbo.abs-team.de).

Is there any way to increase the log severity to get more details, why the registration of the new 7.7 kernel "Command 'inst_reg'" fails?

regards,

Markus

[lbreddemann · Accepted solution]

>

> Is there any way to increase the log severity to get more details, why the registration of the new 7.7 kernel "Command 'inst_reg'" fails?

Hmm.. not that I know of any option for that.

What I would do in this case (besides checking if enough filesystem freespace is available and things like that) is:

I'd use the Process Monitor (procmon) from the sysinternals suite and check on the activity of the DBMCLI/DBMServer processes.

Then we should see a return code for the failing file creation activity.

regards,

Lars

[MarkusKlein · Accepted solution]

Hmm.. not that I know of any option for that.
What I would do in this case (besides checking if enough filesystem freespace is available and things like that) is:
I'd use the Process Monitor (procmon) from the sysinternals suite and check on the activity of the DBMCLI/DBMServer processes.
Then we should see a return code for the failing file creation activity.
regards,
Lars

Ok i just did that. This is what i got from dbmsrv.exe

12:02:24,5747749,"dbmsrv.exe","5112","CreateFile","D:\sapdb\data\config\.M770428","NAME NOT FOUND","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, AllocationSize: n/a"
12:02:24,5748274,"dbmsrv.exe","5112","ReadFile","D:\sapdb\BIL\db\pgm\dbmsrv.exe","SUCCESS","Offset: 1.840.128, Length: 32.768, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O"
12:02:24,5793632,"dbmsrv.exe","5112","RegOpenKey","HKLM\SYSTEM\CurrentControlSet\Services\SAP DBTECH-.M770428\Parameters","REPARSE",""
12:02:24,5793809,"dbmsrv.exe","5112","RegOpenKey","HKLM\System\CurrentControlSet\Services\SAP DBTECH-.M770428\Parameters","NAME NOT FOUND",""
12:02:24,5793975,"dbmsrv.exe","5112","RegOpenKey","HKLM\SYSTEM\CurrentControlSet\Services\SAP DBTECH-.M770428 (QUICK)\Parameters","REPARSE",""
12:02:24,5794101,"dbmsrv.exe","5112","RegOpenKey","HKLM\System\CurrentControlSet\Services\SAP DBTECH-.M770428 (QUICK)\Parameters","NAME NOT FOUND",""
12:02:24,5794246,"dbmsrv.exe","5112","RegOpenKey","HKLM\SYSTEM\CurrentControlSet\Services\SAP DBTECH-.M770428 (SLOW)\Parameters","REPARSE",""
12:02:24,5794362,"dbmsrv.exe","5112","RegOpenKey","HKLM\System\CurrentControlSet\Services\SAP DBTECH-.M770428 (SLOW)\Parameters","NAME NOT FOUND",""
12:02:24,5794503,"dbmsrv.exe","5112","RegOpenKey","HKLM\SYSTEM\CurrentControlSet\Services\SAP DBTECH-.M770428 (TEST)\Parameters","REPARSE",""
12:02:24,5794621,"dbmsrv.exe","5112","RegOpenKey","HKLM\System\CurrentControlSet\Services\SAP DBTECH-.M770428 (TEST)\Parameters","NAME NOT FOUND",""

12:02:24,5794958,"dbmsrv.exe","5112","RegOpenKey","HKLM\Software\SAP\SAP DBTech","SUCCESS",""
12:02:24,5795127,"dbmsrv.exe","5112","RegQueryValue","HKLM\SOFTWARE\SAP\SAP DBTech\IndepData","SUCCESS","Type: REG_EXPAND_SZ, Length: 28, Data: D:\sapdb\data"
12:02:24,5795249,"dbmsrv.exe","5112","RegQueryValue","HKLM\SOFTWARE\SAP\SAP DBTech\IndepData","SUCCESS","Type: REG_EXPAND_SZ, Length: 28, Data: D:\sapdb\data"
12:02:24,5795379,"dbmsrv.exe","5112","RegCloseKey","HKLM\SOFTWARE\SAP\SAP DBTech","SUCCESS",""
12:02:24,5796555,"dbmsrv.exe","5112","CreateFile","D:\sapdb\data\config\.M770428","NAME NOT FOUND","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, AllocationSize: n/a"
12:02:24,5797143,"dbmsrv.exe","5112","RegOpenKey","HKLM\Software\SAP\SAP DBTech","SUCCESS",""
12:02:24,5797314,"dbmsrv.exe","5112","RegQueryValue","HKLM\SOFTWARE\SAP\SAP DBTech\IndepData","SUCCESS","Type: REG_EXPAND_SZ, Length: 28, Data: D:\sapdb\data"
12:02:24,5797427,"dbmsrv.exe","5112","RegQueryValue","HKLM\SOFTWARE\SAP\SAP DBTech\IndepData","SUCCESS","Type: REG_EXPAND_SZ, Length: 28, Data: D:\sapdb\data"
12:02:24,5797551,"dbmsrv.exe","5112","RegCloseKey","HKLM\SOFTWARE\SAP\SAP DBTech","SUCCESS",""
12:02:24,5797932,"dbmsrv.exe","5112","ReadFile","D:\sapdb\BIL\db\pgm\dbmsrv.exe","SUCCESS","Offset: 680.960, Length: 32.768, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O"
12:02:24,5841037,"dbmsrv.exe","5112","CreateFile","D:\sapdb\data\wrk\.M770428.dbm.shi","NAME NOT FOUND","Desired Access: Generic Read/Write, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a"
12:02:24,5841723,"dbmsrv.exe","5112","QueryOpen","C:\WINDOWS\TEMP
12:02:24,5842036,"dbmsrv.exe","5112","QueryOpen","C:\WINDOWS\TEMP
12:02:24,5843062,"dbmsrv.exe","5112","CreateFile","D:\sapdb\BIL\db\USE_BACKUP_SECURITY_DESCRIPTOR","NAME NOT FOUND","Desired Access: Generic Read/Write, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a"

...

[lbreddemann · Accepted solution]

Interesting - it doesn't even find the service instance files for the 7.7er installation.

Could you post an output of the following commands?

- sdbverify (just the final summary)

- sdbregview -l

To me it looks like something else went wrong with the software installation before the instance upgrade was tried.

So starting all over from scratch (installing the software again, manually registering the instance and updating the system tables then) might be the quickest solution here.

regards,

Lars

[MarkusKlein · Accepted solution]

>

> Interesting - it doesn't even find the service instance files for the 7.7er installation.
> 
> Could you post an output of the following commands?
> 
> - sdbverify (just the final summary)
> - sdbregview -l
> 
> To me it looks like something else went wrong with the software installation before the instance upgrade was tried.
> So starting all over from scratch (installing the software again, manually registering the instance and updating the system tables then) might be the quickest solution here.
> 
> regards,
> Lars

Before i tried to upgrade the database to 7.7 i had to apply a patch to get to > 7.6.06.10 (see note 1413628). So from 7.6.06.09 i applyed patch 7.6.06.16 using SDBSETUP. This Patch-Installation completed successfully according SDBSETUP.

After that Patch-Installation i started the upgrade to 7.7.

sdbregview:

S:\Temp\SAP_Upgrade\51035704_12\RDBMS_MAXDB_7.7.04_Build_28\DATA_UNITS\MAXDB_WIN
DOWS_X86_64>sdbregview -l
Server Utilities    d:/sapdb/programs    7.7.04.28     64 bit    valid
DB Analyzer         d:/sapdb/programs    7.7.04.28     64 bit    valid
PCR 7300            d:/sapdb/programs    7.3.00.63               valid
PCR 7301            d:/sapdb/programs    7.3.01.22               valid
PCR 7500            d:/sapdb/programs    7.5.00.52     64 bit    valid
SAP Utilities       d:/sapdb/programs    7.7.04.28     64 bit    valid
Base                d:/sapdb/programs    7.7.04.28     64 bit    valid
Redist Python       d:/sapdb/programs    7.6.06.16     64 bit    valid
JDBC                d:/sapdb/programs    7.6.05.06               valid
Messages            d:/sapdb/programs    MSG 0.8215              valid
ODBC                d:/sapdb/programs    7.6.06.16     64 bit    valid
SQLDBC 77           d:/sapdb/programs    7.7.04.28     64 bit    valid
Database Kernel     d:/sapdb/bil/db      7.6.06.16     64 bit    invalid
Loader              d:/sapdb/programs    7.6.06.16     64 bit    valid
SQLDBC              d:/sapdb/programs    7.7.04.28     64 bit    valid
Fastload API        d:/sapdb/programs    7.7.04.28     64 bit    valid
SQLDBC 76           d:/sapdb/programs    7.6.06.16     64 bit    valid
S:\Temp\SAP_Upgrade\51035704_12\RDBMS_MAXDB_7.7.04_Build_28\DATA_UNITS\MAXDB_WIN
DOWS_X86_64>

sdbverify:

VERIFICATION SUMMARY:
*********************
NUMBER OF INVALID PACKAGES:                   1
INVALID PACKAGES: Database Kernel in d:/sapdb/bil/db
NUMBER OF VALID PACKAGES:                     16
NUMBER OF INCONSISTENT PACKAGES:              0
TOTAL NUMBER OF FILES:                        294
NUMBER OF MISSED FILES:                       0
NUMBER OF MODIFIED FILES:                     0
NUMBER OF FILES WITH MODIFIED PERMISSIONS:    0

[MarkusKlein · Accepted solution]

Just to give a heads-up about the problem. SAP Dev Support found out that i might have stumbled upon an old error in the runtime environment of 7.7.04.28 which got solved in version 7.7.04.30. So basically we rolled back to our backup of the virtual machine - thank god that we have virtual systems nowadays, makes thinks way more easy - and applied 7.7.06.10 this time. This one went through without any problems - problem solved

regards,

Markus