installation problem creating instance

[Former Member]

Hello,

i am installing maxdb version 7.6.03.02 on a Debian Linux with kernel 2.6.18.4, when the setup it is creating the database instance i have this problem, here i reproduce it with dbmcli to paste here.

-

---

/opt/sdb/programs/bin/dbmcli on oteros>load_systab

ERR

-24964,ERR_EXECUTE: error in program execution

1,can not generate temporary file name

-

---

what can be the problem? Thanks in advance.

[steffen_schildberg · Accepted solution]

Hi Soraya,

did the dbmcli show a longer stackback trace upon error? Could you post it here. Actually loading system tables is done by a python script which in turn is called by the dbm server. This seems to fail when creating a temporary file name to store some data for import. Is the tmp directory empty when calling load systab? Please check for the files dbm.prt and dbm.ins in wrk directory - I would be interested in those.

Regards,

Steffen

[Former Member · Accepted solution]

ok i have found the problem, the /tmp directory in this machine was not writable to sdb system user, sorry for annoy you Steffen, i think i had perms problems in this machine some time ago because an admin put 777 on all the files in the harddisk and i had to reset perms, i think i leave /tmp with a non-correct 755, now works ok. Thanks.

[Former Member · Accepted solution]

hi!

can you help me?

can you explane to me how i can install maxdb on debian?

thank you.

steve

[markus_doehr2 · Accepted solution]

- download MaxDB

- start ./SDBINST

Markus

[Former Member · Accepted solution]

like Markus has said you should not have problem with the maxdb installer, in debian etch you have to do a symlink to the correct libpng version, i have forget the exact file version but it is the only problem you can have i think.

[markus_doehr2]

What´s the environment variable for TEMP (and/or TMP) set to? Does it point to a valid directory?

Additionally, the load_systab must be called as

load_systab -u

Markus

[Former Member]

i have the same error with "load_systab -u , -ud" and TEMP variable is pointing "/tmp" that is valid

[markus_doehr2]

Check the knldiag file, maybe we get a hint there what is failing.

Markus

[Former Member]

i cant find any util info, only this:

2007-12-27 17:45:11 3874 12827 COMMUNIC wait for connection T209

2007-12-27 18:13:47 3857 11561 COMMUNIC Connecting T217 local 4660

2007-12-27 18:13:47 3874 12929 TASKING Task T217 started

2007-12-27 18:13:47 3874 11007 COMMUNIC wait for connection T217

2007-12-27 18:13:47 3874 11561 COMMUNIC Connected T217 local 4660

2007-12-27 18:13:47 3874 11560 COMMUNIC Releasing T217

2007-12-27 18:13:47 3874 12827 COMMUNIC wait for connection T217

2007-12-27 18:13:47 3857 11561 COMMUNIC Connecting T214 local 4660

2007-12-27 18:13:47 3874 12929 TASKING Task T214 started

2007-12-27 18:13:47 3874 11007 COMMUNIC wait for connection T214

2007-12-27 18:13:47 3874 11561 COMMUNIC Connected T214 local 4660

2007-12-27 18:13:47 3857 11561 COMMUNIC Connecting T218 local 4660

2007-12-27 18:13:47 3874 12929 TASKING Task T218 started

2007-12-27 18:13:47 3874 11007 COMMUNIC wait for connection T218

2007-12-27 18:13:47 3874 11561 COMMUNIC Connected T218 local 4660

2007-12-27 18:13:47 3874 11560 COMMUNIC Releasing T218

2007-12-27 18:13:47 3874 12827 COMMUNIC wait for connection T218

2007-12-27 18:13:47 3857 11561 COMMUNIC Connecting T220 local 4660

2007-12-27 18:13:47 3874 12929 TASKING Task T220 started

2007-12-27 18:13:47 3874 11007 COMMUNIC wait for connection T220

2007-12-27 18:13:47 3874 11561 COMMUNIC Connected T220 local 4660

2007-12-27 18:13:47 3874 11560 COMMUNIC Releasing T220

2007-12-27 18:13:47 3874 12827 COMMUNIC wait for connection T220

2007-12-27 18:13:47 3857 11561 COMMUNIC Connecting T221 local 4660

2007-12-27 18:13:47 3874 12929 TASKING Task T221 started

2007-12-27 18:13:47 3874 11007 COMMUNIC wait for connection T221

2007-12-27 18:13:47 3874 11561 COMMUNIC Connected T221 local 4660

2007-12-27 18:13:47 3874 11560 COMMUNIC Releasing T221

2007-12-27 18:13:47 3874 12827 COMMUNIC wait for connection T221

2007-12-27 18:13:47 3874 11560 COMMUNIC Releasing T214

2007-12-27 18:13:47 3874 12827 COMMUNIC wait for connection T214

-

---

current write position -

---

and knldiag.err is empty, any other way to debug the problem?