problem via load_systab

[elena_abramova]

Hello.

II need to import a Data Backup into Another Database instance. MaxDb version 7.6.04.16

(http://help.sap.com/erp2005_ehp_04/helpdata/EN/43/d5ebc2c9ed3ab3e10000000a422035/frameset.htm).

db_activate RECOVER media and db_online commands have performed without any problems. Database started.

But when I try to perform command load_systab, I get such error:

dbmcli on PSL>load_systab -u superdba,admin

ERR

-24967,ERR_SYSTEM: system call error

2,ENOENT : no such file or directory

0,""E:\sapdb\PSL\db\bin\x_python" "E:\sapdb\PSL\db\env\lsystab.py" -R "E:\sapdb\

PSL\db" -d PSL -u superdba,admin en ENG" 1>\s5rg..DBM 2>&1

All these files and directories exist.

What can I do?

Thanks!

[markus_doehr2 · Accepted solution]

> But when I try to perform command load_systab, I get such error:

> dbmcli on PSL>load_systab -u superdba,admin

This would be

load_systab -u superdba,<password> -ud <domainpassword>

Markus

[elena_abramova · Accepted solution]

Hello Markus.

I have tried such command too. But result is the same.

dbmcli on PSL>load_systab -u superdba,admin -ud domain

ERR

-24967,ERR_SYSTEM: system call error

2,ENOENT : no such file or directory

0,""E:\sapdb\PSL\db\bin\x_python" "E:\sapdb\PSL\db\env\lsystab.py" -R "E:\sapdb\

PSL\db" -d PSL -u superdba,admin en ENG" 1>\s33c..DBM 2>&1

Elena

[markus_doehr2 · Accepted solution]

Hi Elena,

> 2,ENOENT : no such file or directory

That is your problem - the system doesn't find the file.

What's the output of

dir E:\sapdb\PSL\db\bin

Markus

[elena_abramova · Accepted solution]

Markus,

required files exist, output of this command is:

C:sapdbprogramspgm>dir E:sapdbPSLdb in

Volume in drive E is SAP Disk 2

Volume Serial Number is C0A7-03D5

Directory of E:sapdbPSLdb in

25.08.2009 17:32

.
25.08.2009 17:32

..
08.08.2008 16:56 274 432 backint.exe
08.08.2008 16:58 798 720 dbmevtdisp.exe
08.08.2008 16:58 552 960 dbmevthndl_display.exe
08.08.2008 16:58 565 248 dbmevthndl_winlog.exe
08.08.2008 16:55 290 816 dbmsrvctl.exe
08.08.2008 15:30 41 705 ireport.py
08.08.2008 16:57 245 760 pipe2file.exe
08.08.2008 16:57 1 224 704 sdbfill.exe
08.08.2008 18:05 356 352 sqlrun.dll
08.08.2008 15:34 53 248 sqlver.exe
08.08.2008 15:34 53 248 sqlwhat.exe
08.08.2008 18:05 40 960 xkernprot.exe
08.08.2008 18:05 40 960 xservice.exe
08.08.2008 18:05 40 960 xtracesort.exe
08.08.2008 18:05 40 960 x_diagnose.exe
08.08.2008 16:58 327 680 x_python.exe
16 File(s) 4 948 713 bytes
2 Dir(s) 3 521 445 888 bytes free

C:sapdbprogramspgm>

Elena

[markus_doehr2 · Accepted solution]

This is indeed a strange problem.

Can you execute x_python manually?

x_python -V

Markus

[elena_abramova · Accepted solution]

Markus,

this command has such output:

C:\sapdb\programs\pgm>x_python -V

W32/INTEL 7.6.04 Build 016-123-191-583 (Application startup program)

Python 2.3.3

Elena

[markus_doehr2 · Accepted solution]

So it work...

I must admit I'm out of ideas. I suggest you create an OSS call and let the support have a look on the system if nobody else has a clue what's wrong. This is indeed pretty strange.

Markus

[Former Member · Accepted solution]

Did you check the note 1089778

https://service.sap.com/sap/support/notes/1089778

[markus_doehr2 · Accepted solution]

Hey Danny,

> Did you check the note 1089778

> https://service.sap.com/sap/support/notes/1089778

That note is for "unixish" operating system when the user executing load_systab has a wrong shell. Here we have Windows and only one choice for "shell" - which is cmd.exe.

Markus

[elena_abramova · Accepted solution]

Denny,

We have Windows system.

Elena

[Former Member · Accepted solution]

Thanks for remind that's windows box.

however, it still calls system(), probably you can use tools like filemon to trace the x_server process, to see which file it attemp to open .

Cheers,

Denny

[Former Member · Accepted solution]

also this post might help

[lbreddemann · Accepted solution]

Hi Elena,

as discussed in your support message you're hitting an old/already fixed bug:

http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1159684

The problem is solved after installing the current patch.

regards,

Lars

[elena_abramova]

Thanks to all.

The problem is decided.