Error 1801, 3804

[chad77]

Hello,

I use the database engine SQLBASE 12 on a 64bit windows 2012r2 virtual server the size of the database is 2,3GO with 70 connected users. I very often the message error 1801 or 3804

here's my config ini file


NamedPipes = LocalOnly
tempdir = D: \ BASEARLEQUIN \
dbdir = D: \ BASEARLEQUIN \
ipv4listenaddress = 10.10.28.6 : 2261
servername = SERVER9 , sqlws32
oracleouterjoin = 0
partitions = 0
secureapi = 0
autolocktable = 2
batchpriority = 0
Sortcache = 1000
Users = 800

cache = 768000

Please you have an idea of the problem ?

ps : I'm french sorry for my english

Thank you

[chad77]

hello,

nobody has an idea ?

[EwaldP]

Hi,

at first I would turn on the audit in order to get much more information where and when the problem happens. The easiest way is to configure the audit from SQLBase Command Center.

Ewald

[chad77]

Hi

thanks for reply i go to try but I do not find command center in SQLBASE 12

but i have systematically this error message 3806 3804 1801...

Chad

[EwaldP]

You have to install the command center (32 bit).

[chad77]

its ok installed i see database, table.....

but What information can I have in command center ?

[EwaldP]

- on the TAB Locks you can see whick tables are locked.
- you can start/stop audits (also possible with SQLTalk --> see documentation SQL Language Start/Stop Audit) --> this will help you

[chad77]

thank you very much

i go try

[Mike Vandine]

Hi,

Put a line in the sql.ini file:

log=c:\logs\log.txt

Now change the display level on the SQLBase Console (dbsrvgui.exe) to be 2. After you get one of these errors, stop the server, comment out the line, restart the server and change the display level back to 0.

And for God's sake, remove the sortcache=1000 line.

Best regards,

[FRBhote]

Why don't the new SBs ignore the sortcache?

[chad77]

Hi Mike,

i remove the line sortcache

we found maybe the solution , there were two virtual machine that had the same SID we made the change and users that logged in both places ...

two days it is stable

Sorry for my english

[Mike Vandine]

Yes, that would cause the 3804 error.

[RainerE]

If you create a new virtual machine by copying an old one, it is a good idea to run sysprep.exe. This e.g. will create a new SID.

Regards,
Rainer

[chad77]

Hello,

I set up the logs. the report is not explicit.

84> Database Process terminated
82> Stack Usage For Database Process 82: Total 11000 Used 1000 Free 10000
82> Database Process terminated
60> Stack Usage For Database Process 60: Total 11000 Used 1000 Free 10000
60> Database Process terminated
60> Database process created
82> Database process created
39> Stack Usage For Database Process 39: Total 11000 Used 1000 Free 10000
39> Database Process terminated
82> Stack Usage For Database Process 82: Total 11000 Used 1000 Free 10000
82> Database Process terminated
39> Database process created
82> Database process created
54> Stack Usage For Database Process 54: Total 11000 Used 1000 Free 10000
54> Database Process terminated
54> Database process created
60> Stack Usage For Database Process 60: Total 11000 Used 1000 Free 10000
60> Database Process terminated
60> Database process created
75> Stack Usage For Database Process 75: Total 11000 Used 1000 Free 10000
75> Database Process terminated
81> Stack Usage For Database Process 81: Total 11000 Used 1000 Free 10000
81> Database Process terminated
60> Stack Usage For Database Process 60: Total 11000 Used 1000 Free 10000
60> Database Process terminated
82> Stack Usage For Database Process 82: Total 11000 Used 1000 Free 10000
82> Database Process terminated
60> Database process created
75> Database process created
81> Database process created
81> Stack Usage For Database Process 81: Total 11000 Used 1000 Free 10000


is this normal ?? Thanks

[Mike Vandine]

I think you missed the bit:

"Now change the display level on the SQLBase Console (dbsrvgui.exe) to be 2. "