stopdb - Terminating with error code 13

[Private_Member_19084]

Hi experts,

on a linux ASE System I get the following error on executing stopdb:

./stopdb: Terminating with error code 13

I didn't really find something regarding this, does anybody know what it is about?

Kind regards

[Private_Member_19084]

Ok I found some error in dev_sybctrl

2015 03/25 07:13:51 == file opened ==

EDbSlConnect: rc 99, SQL-error 5704 => [ASE Error SQL10351][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Server user id 6 is not a valid user in database '<DB-SID>'

[ASE Error SQL30292:HY000][SAP][ASE ODBC Driver]Attempting to read past stream EOM.[ASE Error SQL5704][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Changed client character set setting to 'utf8'.

[Private_Member_19084]

I found the following in the link below

I've executed select * from sysuser and the id from error-message (6) isn't there.

Does it mean, that I should create it with sp_adduser?
If so, which one? Because in sp_adduser I can not specify the ID..or am I wrong?

SyBooks Online (Archive)

[former_member187136]

Christian,

That is the reason I asked you to give the Database error log to get some hints, please provide me the screenshot of your Sybase install directory I will guide you where to find the log file.

Regards

Kiran K Adharapuram

[former_member187136]

Christian,

My documentation says:

10351 errors (Server user id %d is not a valid user in database ’%.*s’) indicate a permissions problem. If the database was loaded from another server, the problem may be due to an incorrect suid/uid combination in sysusers. Check syslogins entries in source and target server, respectively.

Also

If you have a copy of master..syslogins in bcp native format then restore that table too.

You may need to delete most logins except sa & probe.

Regards

Kiran K Adharapuram

[Private_Member_19084]

So you want <SID>.log right? Can I send it to you somewhere?
I don't really want to included it here. ( I think a lot of system-data is included)

[Private_Member_19084]

What I did yesterday, is to drop the DB + Devices and I did create the <SID>-DB again.

I think this is causing the problem.

Is there a kind of reset of the users or can I create the master again?

btw, don't worry it is just a testing system for things like this.

[former_member187136]

Christian,

Can you please type in few lines from the log file removing the confidential information.

If you have a recent master dump, you can bcp out the syslogin table from master database and restore it back to the current machine, also in a simple way you can restore the whole master database if you are ok

Regards

Kiran K Adharapuram

[Private_Member_19084]

These are the last lines of <sid>log.

But as said, there is not entry created on executing stopdb.

e 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Database 'sybmgmtdb', checkpoint=(2347, 24), first=(23

47, 23), last=(2347, 32).

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Completed estimating recovery log boundaries for datab

ase 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Started ANALYSIS pass for database 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Completed ANALYSIS pass for database 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Log contains all committed transactions until 2015/03/

24 19:08:10.19 for database sybmgmtdb.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Started REDO pass for database 'sybmgmtdb'. The total

number of log records to process is 10.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Roll forward transaction '$dmpxact'.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Redo pass of recovery has processed 1 committed and 0

aborted transactions.

00:0006:00000:00001:2015/03/24 20:30:30.63 server  Completed REDO pass for database 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.69 server  Timestamp for database 'sybmgmtdb' is (0x0000, 0x0000a

5b3).

00:0006:00000:00001:2015/03/24 20:30:30.69 server  Recovery of database 'sybmgmtdb' will undo incomplete

nested top actions.

00:0006:00000:00001:2015/03/24 20:30:30.69 server  Started recovery checkpoint for database 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.71 server  Completed recovery checkpoint for database 'sybmgmtdb'

.

00:0006:00000:00001:2015/03/24 20:30:30.71 server  Started filling free space info for database 'sybmgmtd

b'.

00:0006:00000:00001:2015/03/24 20:30:30.71 server  Completed filling free space info for database 'sybmgm

tdb'.

00:0006:00000:00001:2015/03/24 20:30:30.72 server  Started cleaning up the default data cache for databas

e 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.72 server  Completed cleaning up the default data cache for datab

ase 'sybmgmtdb'.

00:0006:00000:00001:2015/03/24 20:30:30.73 server  Checking external objects.

00:0006:00000:00001:2015/03/24 20:30:30.84 server  The transaction log in the database 'sybmgmtdb' will u

se I/O size of 16 Kb.

00:0006:00000:00001:2015/03/24 20:30:30.85 server  Database 'sybmgmtdb' is now online.

00:0006:00000:00001:2015/03/24 20:30:30.85 server  Recovery has restored the value of 'local async prefet

ch limit' for '128K' pool in 'default data cache' from '80' to 'DEFAULT'.

00:0006:00000:00001:2015/03/24 20:30:30.85 server  Recovery has restored the value of 'local async prefet

ch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.

00:0006:00000:00001:2015/03/24 20:30:30.95 server  Recovery has restored the original size for '128K' poo

l and '16K' pool in 'default data cache'.

00:0006:00000:00001:2015/03/24 20:30:30.95 server  Recovery complete.

00:0006:00000:00001:2015/03/24 20:30:30.96 server  ASE's default unicode sort order is 'binary'.

00:0006:00000:00001:2015/03/24 20:30:30.97 server  ASE's default sort order is:

00:0006:00000:00001:2015/03/24 20:30:30.97 server       'binary' (ID = 25)

00:0006:00000:00001:2015/03/24 20:30:30.97 server  on top of default character set:

00:0006:00000:00001:2015/03/24 20:30:30.97 server       'utf8' (ID = 190).

00:0006:00000:00001:2015/03/24 20:30:30.97 server  Master device size: 400 megabytes, or 204800 virtual p

ages. (A virtual page is 2048 bytes.)

00:0006:00000:00015:2015/03/24 20:30:31.23 kernel  Initializing Job Scheduler Task

00:0006:00000:00015:2015/03/24 20:30:31.26 kernel  Installed Job Scheduler sequencer code version 0.29 -

29 tokens

00:0006:00000:00015:2015/03/24 20:30:31.33 kernel  Job Scheduler Task started with a clean 'js_history' t

able

00:0006:00000:00015:2015/03/24 20:30:31.43 kernel  Job Scheduler Task state set to running, startcount 1.

00:0006:00000:00015:2015/03/24 20:30:32.34 kernel  Job Scheduler Task connected with Agent on port 4903

00:0006:00000:00001:2015/03/24 20:30:32.34 kernel  Warning: Cannot set console to nonblocking mode, switc

hing to blocking mode.

00:0006:00000:00001:2015/03/24 20:30:32.34 kernel  Console logging is disabled. This is controlled via th

e 'enable console logging' configuration parameter.

[Private_Member_19084]

Hello Kiran,

as it is just a temp testing db, I didn't create a master dump 😮

[former_member187136]

Christian,

I don't anything odd from DB persective, now I am moving the ball to Application court

They should help in understanding the error, however if they have any db related queries I am here to answer them once they reply.

Cheers

Kiran K Adharapuram