20017 IOMan error while database start

[Former Member]

Hello,

today in the morning we had a strange behaviour of our database (maxdb 7.5.38 on 64bit opensuse).

We monitored that the log devspace was rapidly increasing its filling level, even if autolog was set to "on".

I decided to create a second log device (also 400MB), but the log devspace remains on its original size (400MB). Is a db restart needed to permit this additional log devspace ?

At the filling level of 97% I decided to restart the database, because I had no idea why the autolog functionality isn't working anymore.

At startup I got an error, telling me "emergency shutdown...".

About one minute after that error I tried it again and now the database came back to state online.

Thereby I have to open questions:

- why was the log devspace getting filled up, even the enabled autolog ?

- what happened at the first attempt of starting the database ?

- are there some dependencies to the knldiag.err-entry of 2008-12-08 "...BD Primkey..." ?

knldiag.err shows us:

.....

2008-12-03 08:19:21 ___ Stopping GMT 2008-12-03 07:19:21 7.5.0 Build 038-123-133-420

2008-12-03 08:19:42 --- Starting GMT 2008-12-03 07:19:42 7.5.0 Build 038-123-133-420

2008-12-08 08:14:56 6359 ERR 51080 SYSERROR -9049 BD Primkey from inv in primtree no

2008-12-10 10:30:37 ___ Stopping GMT 2008-12-10 09:30:37 7.5.0 Build 038-123-133-420

2008-12-10 10:30:43 --- Starting GMT 2008-12-10 09:30:43 7.5.0 Build 038-123-133-420

2008-12-10 10:30:59 7436 ERR 20017 IOMan EMERGENCY SHUTDOWN

2008-12-10 10:30:59 7436 ERR 20010 Admin ERROR '' CAUSED EMERGENCY SHUTDOWN

2008-12-10 10:31:00 ___ Stopping GMT 2008-12-10 09:31:00 7.5.0 Build 038-123-133-420

2008-12-10 10:32:01 --- Starting GMT 2008-12-10 09:32:01

any help appreciated.....GERD....

[lbreddemann · Accepted solution]

> today in the morning we had a strange behaviour of our database (maxdb 7.5.38 on 64bit opensuse).

Pretty old MaxDB ...

> We monitored that the log devspace was rapidly increasing its filling level, even if autolog was set to "on".

> I decided to create a second log device (also 400MB), but the log devspace remains on its original size (400MB). Is a db restart needed to permit this additional log devspace ?

> At the filling level of 97% I decided to restart the database, because I had no idea why the autolog functionality isn't working anymore.

Why didn't you try to perform a manual log backup?

Whenever a autosave fails due to some error (let's say, the target filesystem is full) it won't be rescheduled automatically even if the root cause has been resolved.

> At startup I got an error, telling me "emergency shutdown...".

That's never good...

> About one minute after that error I tried it again and now the database came back to state online.

> Thereby I have to open questions:

> - why was the log devspace getting filled up, even the enabled autolog ?

Don't know - you did not provide enough information to answer that (e.g. KNLDIAG or x_cons show all output from the moment when the problem was present).

> - what happened at the first attempt of starting the database ?

Again - we don't have enough information. What was in the KNLDIAG for that start?

> - are there some dependencies to the knldiag.err-entry of 2008-12-08 "...BD Primkey..." ?

Possible but not necessary and also not very likely.

> any help appreciated.....GERD....

Perform a check data as soon as possible and provide some more information (see above).

Just the story of the problem is not enough here.

regards,

Lars

[Former Member · Accepted solution]

Hello Lars, Hello Natalia,

thanks for answering.

Yes, you're right, its a pretty old version, but we didn't have time to check the upgrade process in the past. I know that there were some manual steps while upgrading from 7.3 to 7.5.....

Is there a general "how-to" for rpm-based upgrade from 7.5 to 7.7 (I think it's best to upgrade to latest 7.7 ..?!?!)

The hint with the manual log backup sounds good, but in the time of that emergency I didn't realize that option, damn....

Here comes the additional info:

1.) output from knldiag.old:

2008-12-10 10:30:57 7450 12821 TASKING Thread 7450 starting

2008-12-10 10:30:57 7450 11597 IO Open '/devspace/data/TISYS/DISKD0003' successfull, fd: 17

2008-12-10 10:30:57 7450 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0003' devno 3 T99 succeeded

2008-12-10 10:30:57 7451 12821 TASKING Thread 7451 starting

2008-12-10 10:30:57 7451 11597 IO Open '/devspace/data/TISYS/DISKD0004' successfull, fd: 19

2008-12-10 10:30:57 7451 11565 startup DEVi started

2008-12-10 10:30:57 7452 12821 TASKING Thread 7452 starting

2008-12-10 10:30:57 7452 11597 IO Open '/devspace/data/TISYS/DISKD0004' successfull, fd: 20

2008-12-10 10:30:57 7452 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0004' devno 4 T99 succeeded

2008-12-10 10:30:57 7453 12821 TASKING Thread 7453 starting

2008-12-10 10:30:57 7453 11597 IO Open '/devspace/data/TISYS/DISKD0005' successfull, fd: 22

2008-12-10 10:30:57 7453 11565 startup DEVi started

2008-12-10 10:30:57 7454 12821 TASKING Thread 7454 starting

......

2008-12-10 10:30:59 7432 WNG 11900 VDETACH Ignoring pending self I/O operation UKT3 on device 11

2008-12-10 10:30:59 7432 12822 TASKING Thread 7468 joining

2008-12-10 10:30:59 7468 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKL001' devno 12 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7469 joining

2008-12-10 10:30:59 7469 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7470 joining

2008-12-10 10:30:59 7470 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKL002' devno 13 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7471 joining

2008-12-10 10:30:59 7471 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7472 joining

2008-12-10 10:30:59 7472 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11560 COMMUNIC Releasing T100

2008-12-10 10:30:59 7440 12827 COMMUNIC wait for connection T100

2008-12-10 10:30:59 7436 WNG 20010 IOMan The data volume 4 is offline.

2008-12-10 10:30:59 7436 ERR 20017 IOMan EMERGENCY SHUTDOWN

2008-12-10 10:30:59 7436 ERR 20010 Admin ERROR '' CAUSED EMERGENCY SHUTDOWN

2008-12-10 10:30:59 7436 12696 DBSTATE Change DbState to 'SHUTDOWN'(25)

=> data volume 4 offline ? but at the top it says that the data devspaces were successfully started

2.) param_getvolsall

OK

LOG_MIRRORED NO

MAXLOGVOLUMES 3

MAXDATAVOLUMES 20

LOG_VOLUME_NAME_001 51200 F /devspace/data/TISYS/DISKL001

LOG_VOLUME_NAME_002 51200 F /devspace/data/TISYS/DISKL002

DATA_VOLUME_NAME_0001 500000 F /devspace/data/TISYS/DISKD0001

DATA_VOLUME_NAME_0002 500000 F /devspace/data/TISYS/DISKD0002

DATA_VOLUME_NAME_0003 500000 F /devspace/data/TISYS/DISKD0003

DATA_VOLUME_NAME_0004 500000 F /devspace/data/TISYS/DISKD0004

DATA_VOLUME_NAME_0005 500000 F /devspace/data/TISYS/DISKD0005

DATA_VOLUME_NAME_0006 500000 F /devspace/data/TISYS/DISKD0006

DATA_VOLUME_NAME_0007 500000 F /devspace/data/TISYS/DISKD0007

DATA_VOLUME_NAME_0008 500000 F /devspace/data/TISYS/DISKD0008

DATA_VOLUME_NAME_0009 500000 F /devspace/data/TISYS/DISKD0009

DATA_VOLUME_NAME_0010 500000 F /devspace/data/TISYS/DISKD0010

DATA_VOLUME_NAME_0011 500000 F /devspace/data/TISYS/DISKD0011

3.) medium_getall

OK

myrecover /opt/sdb/datasave_full_maxdb_2007-05-19 FILE DATA 0 8 YES NO 20070519211947 20070519211947

inc_recover /opt/sdb/datasave_incremental_maxdb_2007-05-19_21_15_07 FILE PAGES 0 0 NO NO 20070519213514 20070519213514

data datasave FILE DATA 0 8 YES NO 20070519213518 20070519213518

auto /devspace/autolog/autosave FILE AUTO 0 0 NO NO 20070519213518 20070519213518

incrF /devspace/backup_temp/datasave_incremental_maxdb_2008-12-11_04_22_01 FILE PAGES 0 0 NO NO 20070520001001 20081211042402

mybackup /devspace/backup_temp/datasave_full_maxdb_2008-12-06 FILE DATA 0 8 YES NO 20081116000404 20081206042402

4.) param_directget LOG_SEGMENT_SIZE

OK

LOG_SEGMENT_SIZE 17066

5.) info log

OK

END

Name | Value

Log Mirrored = NO

Log Writing = ON

Log Automatic Overwrite = OFF

Max. Size (KB) = 816280

Backup Segment Size (KB) = 136528

Used Size (KB) = 28816

Used Size (%) = 4

Not Saved (KB) = 28816

Not Saved (%) = 4

Log Since Last Data Backup (KB) = 0

Savepoints = 85523

Checkpoints = 0

Physical Reads = 23246

Physical Writes = 3499157

Queue Size (KB) = 400

Queue Overflows = 0

Group Commits = 16151

Waits for Logwriter = 3502429

Max. Waits = 49

Average Waits = 0

and last, but not least, no, we're no SAP customer.

Since this is a heavy used production database I'm going to plan the "check database extended" at weekend.

regards...GERD....

[former_member229109 · Accepted solution]

Hello Gerd,

1) Please post more entries from the knldiag old file beetween the lines:

2008-12-10 10:30:57 7454 12821 TASKING Thread 7454 starting

......

2008-12-10 10:30:59 7432 WNG 11900 VDETACH Ignoring pending self I/O operation UKT3 on device 11

As I see the detaching of the log and data volumes started before 2008-12-10 10:30:59.

Please post the dbm commands listed in dbm.prt file beetween 10AM and 2008-12-10 10:32:01 .

May be somebody run db_offline or db_stop command & the data volume no 4 was already DETACHed

=> 2008-12-10 10:30:59 7440 12827 COMMUNIC wait for connection T100

2008-12-10 10:30:59 7436 WNG 20010 IOMan The data volume 4 is offline.

And the database was SHUTDOWN, when the task was trying to access the data volume, which was

already detached.

2) "Is there a general "how-to" for rpm-based upgrade from 7.5 to 7.7 (I think it's best to upgrade to latest 7.7 ..?!?!)"

For rpm-based database upgrade for the versions 7.5/7.6 the documentation "Installation/Update with the Red Hat Package Manager"

available at < http://maxdb.sap.com/doc/7_6/default.htm >

SAP MaxDB Library 7.6 ->Installation -> Installation Manual ->

Installation, Upgrade and Uninstallation on the Command Line ->

Installing and Updating the Database Software -> Installing/Updating Software on Linux

And I don't know if the rpm-based upgrade from 7.5 to 7.7 is currently released. I will check this questions with my colleagues.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hello Natalia,

I recently finished the task "check data extended" (took 2 hours btw..) and the database is online again.

Here's the output from dbm.prt of your requested timespan.

2008-12-10 09:50:29 0x00006c0e 0 DBM command backup_start auto

2008-12-10 09:50:29 0x00006c73 0 DBM command autolog_on

2008-12-10 10:00:34 0x0000795d 0 DBM command autolog_off

2008-12-10 10:00:39 0x00007c56 0 DBM command backup_start auto

2008-12-10 10:00:40 0x00007ccc 0 DBM command autolog_on

2008-12-10 10:06:31 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:06:31 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:24 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:24 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:26 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:26 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:27 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:27 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:32 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:32 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:33 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:33 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:08:55 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:08:55 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:10:02 0x00006b88 0 DBM command db_adddevice LOG "/devspace/data/TISYS/DISKL002" F 51200

2008-12-10 10:10:07 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:10:07 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:10:16 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:10:16 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:10:18 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:10:18 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:10:45 0x00000ee4 0 DBM command autolog_off

2008-12-10 10:10:50 0x000011b9 0 DBM command backup_start auto

2008-12-10 10:10:50 0x00001215 0 DBM command autolog_on

2008-12-10 10:12:32 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:12:32 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:12:57 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:12:57 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:13:10 0x000067eb 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:13:10 0x000067eb ERR -24988 DBM ERR_SQL: sql error

0x000067eb ERR -24988 DBM 100,Row not found

2008-12-10 10:13:39 0x000078fe 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:13:39 0x000078fe ERR -24988 DBM ERR_SQL: sql error

0x000078fe ERR -24988 DBM 100,Row not found

2008-12-10 10:14:03 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:14:03 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:14:16 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:14:16 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:15:37 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:15:37 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:16:19 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:16:19 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:16:23 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:16:23 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:16:43 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:16:43 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:17:52 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:17:52 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:17:55 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:17:55 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:17:57 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:17:57 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:18:12 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:18:12 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:18:34 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:18:34 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:18:55 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:18:55 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:19:45 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:19:45 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:20:55 0x00002f69 0 DBM command autolog_off

2008-12-10 10:20:59 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:20:59 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:21:00 0x000032d8 0 DBM command backup_start auto

2008-12-10 10:21:01 0x00003336 0 DBM command autolog_on

2008-12-10 10:21:14 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:21:14 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:21:23 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:21:23 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:21:35 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:21:35 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:22:02 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:22:02 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:22:08 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:22:08 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:22:34 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:22:34 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:22:49 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:22:49 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:23:08 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:23:08 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:24:10 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:24:10 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:24:14 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:24:14 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:24:36 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:24:36 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:24:43 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:24:43 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:25:37 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:25:37 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:25:42 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:25:42 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:26:21 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:26:21 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:26:48 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:26:48 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:26:55 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:26:55 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:27:20 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:27:20 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:28:09 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:28:09 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:28:30 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:28:30 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:28:47 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:28:47 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:29:01 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:29:01 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:29:45 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:29:45 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:29:47 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:29:47 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:29:48 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:29:48 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:29:50 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:29:50 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:07 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:07 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:09 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:09 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:11 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:11 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:12 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:12 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:18 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:18 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:20 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:20 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:21 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:30:21 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:30:31 0x00006b88 0 DBM command db_offline

2008-12-10 10:30:42 0x00006b88 0 DBM command db_online -f

2008-12-10 10:31:00 0x00006b88 ERR -24895 DBM ERR_SHUTDOWN: shutdown of database occured

0x00006b88 ERR -24895 DBM -71,connection broken server state 6

2008-12-10 10:31:12 0x00001d54 0 DBM command autolog_show

2008-12-10 10:31:12 0x00001d54 ERR -24988 DBM ERR_SQL: sql error

0x00001d54 ERR -24988 DBM 1,database not running: no request pipe

2008-12-10 10:31:12 0x00001d57 0 DBM command util_connect

2008-12-10 10:31:12 0x00001d57 ERR -24988 DBM ERR_SQL: sql error

0x00001d57 ERR -24988 DBM 1,database not running: no request pipe

2008-12-10 10:32:01 0x00006b88 0 DBM command db_online -f

2008-12-10 10:32:01 0x00001db1 0 DBM command sql_connect

2008-12-10 10:32:03 0x00001db1 ERR -24988 DBM ERR_SQL: sql error

0x00001db1 ERR -24988 DBM 1,database not running: no request pipe

2008-12-10 10:32:17 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:32:17 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:33:06 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:33:06 0x00006b88 ERR -24988 DBM ERR_SQL: sql error

0x00006b88 ERR -24988 DBM 100,Row not found

2008-12-10 10:33:10 0x00006b88 0 DBM command db_execute SELECT ID,CREATEDATE,USEDSIZE

2008-12-10 10:33:10

and the missing output from knldiag.old:

2008-12-10 10:30:57 7454 11597 IO Open '/devspace/data/TISYS/DISKD0005' successfull, fd: 23

2008-12-10 10:30:57 7454 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0005' devno 5 T99 succeeded

2008-12-10 10:30:57 7455 12821 TASKING Thread 7455 starting

2008-12-10 10:30:57 7455 11597 IO Open '/devspace/data/TISYS/DISKD0006' successfull, fd: 25

2008-12-10 10:30:57 7431 11561 COMMUNIC Connecting T100 192.168.0.186 13316

2008-12-10 10:30:57 7440 12929 TASKING Task T100 started

2008-12-10 10:30:57 7440 11561 COMMUNIC Connected T100 192.168.0.186 13316

2008-12-10 10:30:57 7455 11565 startup DEVi started

2008-12-10 10:30:57 7458 12821 TASKING Thread 7458 starting

2008-12-10 10:30:57 7458 11597 IO Open '/devspace/data/TISYS/DISKD0006' successfull, fd: 26

2008-12-10 10:30:57 7458 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0006' devno 6 T99 succeeded

2008-12-10 10:30:57 7459 12821 TASKING Thread 7459 starting

2008-12-10 10:30:57 7459 11597 IO Open '/devspace/data/TISYS/DISKD0007' successfull, fd: 28

2008-12-10 10:30:57 7459 11565 startup DEVi started

2008-12-10 10:30:57 7460 12821 TASKING Thread 7460 starting

2008-12-10 10:30:57 7460 11597 IO Open '/devspace/data/TISYS/DISKD0007' successfull, fd: 29

2008-12-10 10:30:57 7460 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0007' devno 7 T99 succeeded

2008-12-10 10:30:57 7461 12821 TASKING Thread 7461 starting

2008-12-10 10:30:57 7461 11597 IO Open '/devspace/data/TISYS/DISKD0008' successfull, fd: 31

2008-12-10 10:30:57 7461 11565 startup DEVi started

2008-12-10 10:30:57 7462 12821 TASKING Thread 7462 starting

2008-12-10 10:30:57 7462 11597 IO Open '/devspace/data/TISYS/DISKD0008' successfull, fd: 32

2008-12-10 10:30:57 7462 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0008' devno 8 T99 succeeded

2008-12-10 10:30:57 7463 12821 TASKING Thread 7463 starting

2008-12-10 10:30:57 7463 11597 IO Open '/devspace/data/TISYS/DISKD0009' successfull, fd: 34

2008-12-10 10:30:57 7463 11565 startup DEVi started

2008-12-10 10:30:57 7464 12821 TASKING Thread 7464 starting

2008-12-10 10:30:57 7464 11597 IO Open '/devspace/data/TISYS/DISKD0009' successfull, fd: 35

2008-12-10 10:30:57 7464 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0009' devno 9 T99 succeeded

2008-12-10 10:30:57 7465 12821 TASKING Thread 7465 starting

2008-12-10 10:30:57 7465 11597 IO Open '/devspace/data/TISYS/DISKD0010' successfull, fd: 37

2008-12-10 10:30:57 7465 11565 startup DEVi started

2008-12-10 10:30:57 7466 12821 TASKING Thread 7466 starting

2008-12-10 10:30:57 7466 11597 IO Open '/devspace/data/TISYS/DISKD0010' successfull, fd: 38

2008-12-10 10:30:57 7466 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0010' devno 10 T99 succeeded

2008-12-10 10:30:57 7467 12821 TASKING Thread 7467 starting

2008-12-10 10:30:57 7467 11597 IO Open '/devspace/data/TISYS/DISKD0011' successfull, fd: 40

2008-12-10 10:30:57 7467 11565 startup DEVi started

2008-12-10 10:30:57 7468 12821 TASKING Thread 7468 starting

2008-12-10 10:30:57 7468 11597 IO Open '/devspace/data/TISYS/DISKD0011' successfull, fd: 41

2008-12-10 10:30:57 7468 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKD0011' devno 11 T99 succeeded

2008-12-10 10:30:57 7469 12821 TASKING Thread 7469 starting

2008-12-10 10:30:57 7469 11597 IO Open '/devspace/data/TISYS/DISKL001' successfull, fd: 43

2008-12-10 10:30:57 7469 11565 startup DEVi started

2008-12-10 10:30:57 7470 12821 TASKING Thread 7470 starting

2008-12-10 10:30:57 7470 11597 IO Open '/devspace/data/TISYS/DISKL001' successfull, fd: 44

2008-12-10 10:30:57 7470 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKL001' devno 12 T99 succeeded

2008-12-10 10:30:57 7471 12821 TASKING Thread 7471 starting

2008-12-10 10:30:57 7471 11597 IO Open '/devspace/data/TISYS/DISKL002' successfull, fd: 46

2008-12-10 10:30:57 7472 12821 TASKING Thread 7472 starting

2008-12-10 10:30:57 7471 11565 startup DEVi started

2008-12-10 10:30:57 7472 11597 IO Open '/devspace/data/TISYS/DISKL002' successfull, fd: 47

2008-12-10 10:30:57 7472 11565 startup DEVi started

2008-12-10 10:30:57 7436 11000 vattach '/devspace/data/TISYS/DISKL002' devno 13 T99 succeeded

2008-12-10 10:30:57 7436 12 Pager Start Read Converter

2008-12-10 10:30:58 7440 11560 COMMUNIC Releasing T100

2008-12-10 10:30:58 7440 12827 COMMUNIC wait for connection T100

2008-12-10 10:30:58 7436 13 Pager Stop Read Converter, Pages: 1851 IO: 1851

2008-12-10 10:30:58 7436 54003 dynpool DATA_CACHE_REGIONS : 64

2008-12-10 10:30:58 7436 54003 dynpool B20_DATACACHE_HEAD : 183152

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE head num item: 11447

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE head item siz: 16

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE task queue : 9648

2008-12-10 10:30:58 7436 54003 dynpool US + SV + DW + 8 : 402

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE taskq elem : 24

2008-12-10 10:30:58 7436 54003 dynpool B20_DATACACHE_TASKQ : 192800

2008-12-10 10:30:58 7436 54003 dynDATA DATA_CACHE_PAGES : 2861

2008-12-10 10:30:58 7436 54003 dynpool B20_DATACACHE_CB : 320432

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE num cblocks : 2861

2008-12-10 10:30:58 7436 54003 dynpool DATACACHE cblock size : 112

2008-12-10 10:30:58 7436 54003 dynpool DYNP_B20_DATACACHE : 32846848

2008-12-10 10:30:58 7436 54003 dynDATA DYND_B20_DATACACHE : 183104

2008-12-10 10:30:58 7436 53000 B*TREE Restart FileDir finished successfully

2008-12-10 10:30:58 7436 54003 dynpool DYNP_K51_LOCK_LIST :3914544

2008-12-10 10:30:58 7436 54003 dynpool LOCK maxlocks : 13280

2008-12-10 10:30:58 7436 54003 dynpool LOCK items : 42300

2008-12-10 10:30:58 7436 54003 dynpool LOCK Regions : 24

2008-12-10 10:30:58 7436 54003 dynpool LOCK TransRegions : 8

2008-12-10 10:30:58 7436 54003 dynpool LOCK RegionGlob+Space : 3456

2008-12-10 10:30:58 7436 54003 dynpool LOCK TransGlob : 768

2008-12-10 10:30:58 7436 54003 dynpool LOCK SupplyItemsPerRgn : 100

2008-12-10 10:30:58 7436 54003 dynpool LOCK SupplySize : 192000

2008-12-10 10:30:58 7436 54003 dynpool LOCK RowHash entries : 13280

2008-12-10 10:30:58 7436 54003 dynpool LOCK TabHash entries : 2656

2008-12-10 10:30:58 7436 54003 dynpool LOCK Row+Tab hash size : 127488

2008-12-10 10:30:58 7436 54003 dynpool LOCK Trans entries : 1328

2008-12-10 10:30:58 7436 54003 dynpool LOCK trans_list size : 297472

2008-12-10 10:30:58 7436 54003 dynpool LOCK TransPtrList : 10624

2008-12-10 10:30:58 7436 54003 dynpool LOCK TransHash entries : 1328

2008-12-10 10:30:58 7436 54003 dynpool LOCK TransHash size : 10624

2008-12-10 10:30:58 7436 54003 dynpool LOCK SupplyPoolSegments: 399

2008-12-10 10:30:58 7436 54003 dynpool LOCK SupplyPoolSize :3201584

2008-12-10 10:30:58 7436 54003 dynpool LOCK ObjColl_list size : 42496

2008-12-10 10:30:58 7436 54003 dynpool LOCK ObjReq_list size : 21248

2008-12-10 10:30:58 7436 20011 Log LogVolume was added: adjust size from 51198 to 102397

2008-12-10 10:30:58 7436 20006 Log 1 queues, flushmode is 'MinimizeSpace', devstate is 'Okay'

2008-12-10 10:30:58 7436 20007 Log Oldest not saved is ioseq 1186665700 @ off 9348

2008-12-10 10:30:58 7436 20008 Log First known on LogVolume is ioseq 1185765075 @ off 12071

2008-12-10 10:30:58 7436 20005 Log Restart from ioseq 1186720528 @ off 12070 to ioseq 1186720528 @ off 12070

2008-12-10 10:30:58 7436 20010 Log Result after checking the log device: 'Ok'

2008-12-10 10:30:58 7437 3 Restart recovering log from log_volume from IOSeq: '1186720528'

2008-12-10 10:30:58 7437 20042 Log normal end of log found at off 12070 lastseq 1186720528.

2008-12-10 10:30:58 7437 20012 Log last-redo-read#1:TR4294967295(85391)[1186720528]@12070.3928'SavepointEntry':20081210:103031

2008-12-10 10:30:58 7436 20056 Log Savepoint requested by T99 reason 'Restart' (started).

2008-12-10 10:30:58 7437 4 Pager SVP(1) Start Write Data

2008-12-10 10:30:58 7437 5 Pager SVP(1) Stop Data IO, Pages: 0 IO: 0

2008-12-10 10:30:58 7437 6 Pager SVP(2) Wait for last split, TaskId: 92

2008-12-10 10:30:58 7437 7 Pager SVP(2) Stop Wait for last split, Pages: 0 IO: 0

2008-12-10 10:30:58 7437 53070 SAVPOINT B20PREPARE_SVP: 232820

2008-12-10 10:30:58 7437 8 Pager SVP(3) Start Write Data

2008-12-10 10:30:58 7437 9 Pager SVP(3) Stop Data IO, Pages: 1 IO: 1

2008-12-10 10:30:58 7437 10 Pager SVP(3) Start Write Converter

2008-12-10 10:30:58 7437 11 Pager SVP(3) Stop Converter IO, Pages: 2 IO: 2

2008-12-10 10:30:58 7437 53071 SAVPOINT B20SVP_COMPLETED: 232820

2008-12-10 10:30:58 7436 20037 Admin Kernel state: 'REDO LOG' finished

2008-12-10 10:30:58 7436 54003 dynpool DYNP_A42_PARSEID : 3600

2008-12-10 10:30:58 7436 54000 OBJECT /opt/sdb/7500/lib/liboms

2008-12-10 10:30:58 7431 11561 COMMUNIC Connecting T100 local 7474

2008-12-10 10:30:58 7440 12929 TASKING Task T100 started

2008-12-10 10:30:59 7440 11561 COMMUNIC Connected T100 local 7474

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0001' devno 1 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7445 joining

2008-12-10 10:30:59 7445 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7446 joining

2008-12-10 10:30:59 7446 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0002' devno 2 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7447 joining

2008-12-10 10:30:59 7447 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7448 joining

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0003' devno 3 T100

2008-12-10 10:30:59 7448 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7449 joining

2008-12-10 10:30:59 7449 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7450 joining

2008-12-10 10:30:59 7450 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0004' devno 4 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7451 joining

2008-12-10 10:30:59 7451 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7452 joining

2008-12-10 10:30:59 7452 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0005' devno 5 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7453 joining

2008-12-10 10:30:59 7453 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7454 joining

2008-12-10 10:30:59 7454 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0006' devno 6 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7455 joining

2008-12-10 10:30:59 7455 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7458 joining

2008-12-10 10:30:59 7458 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0007' devno 7 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7459 joining

2008-12-10 10:30:59 7459 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7460 joining

2008-12-10 10:30:59 7460 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0008' devno 8 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7461 joining

2008-12-10 10:30:59 7461 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7462 joining

2008-12-10 10:30:59 7462 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0009' devno 9 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7463 joining

2008-12-10 10:30:59 7463 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7464 joining

2008-12-10 10:30:59 7464 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0010' devno 10 T100

2008-12-10 10:30:59 7432 12822 TASKING Thread 7465 joining

2008-12-10 10:30:59 7465 11566 stop DEVi stopped

2008-12-10 10:30:59 7432 12822 TASKING Thread 7466 joining

2008-12-10 10:30:59 7466 11566 stop DEVi stopped

2008-12-10 10:30:59 7440 11000 vdetach '/devspace/data/TISYS/DISKD0011' devno 11 T100

2008-12-10 10:30:59 7432 WNG 11900 VDETACH Ignoring pending self I/O operation UKT3 on device 11

2008-12-10 10:30:59 7432 12822 TASKING Thread 7467 joining

2008-12-10 10:30:59

We're looking forward for some information about the rpm upgrade....

kind regards...GERD...

[former_member272632]

Hi Gerd,

Natalia asked me to answer.

From the dbm.prt entries we could see, that the database was stopped and several seconds after it was started again:

2008-12-10 10:30:31 0x00006b88 0 DBM command db_offline

2008-12-10 10:30:42 0x00006b88 0 DBM command db_online -f

I think there was a synchronization problem. form the one side the kernel reported shutdown completed, from the other side the volumes were not really released. I think this was the reason.

Regarding rpm Upgrade I'm sorry, there is no way for rpm Upgrade starting with MaxDB 7.6 anymore. we will probably need to clarify this and to remove the corresponding information from the documentation site.

It is not necessary to change the MaxDB version if there are no special requirements from the application side or if the SAP stops this version supporting. MaxDB 7.5 is still supported. The MaxDB 7.5.00.50 was released in 2008.

From the other side I would suggest to use the recent version of MaxDB 7.6 (7.6.05.09 is recently on the SDN download page). This Version is activelly supported and has a wide customer use.

Our developer suggested to use following way to transform the rpm based installation into SDB-Tool based installation:

1. Backup the database

2. uninstall the MaxDB software

3. Install MaxDB software using SDBINST

4. Initialize the Database

5. Recover the data

I personally could Upgrade the rpm-based 7.5 database in my test environment using the Tool SDBUPD. to MaxDB 7.6. The only thing I needed to do is to create the <IndepData>/config/install directory. (to find IndepData, do "cat /etc/opt/sdb"). But in this case the rpm registration is still existing on the system, this could lead to an automatically started upgrade and can damage the database.

So I would suggest the way with backup and recovery.

best regards,

Alexander

Edited by: Alexander Kaiser on Dec 17, 2008 3:29 PM

[Former Member]

Hello all,

sorry for the delay, since I got ill the last weeks it took some time to get back here.

thanks again for your immediate help, but there's one question open at Alexander Kaiser:

Are there no improvements,enhancements in the latest 7.6,7.7 version versus the 7.5, because you mentioned that there's no need to upgrade ?

regards...GERD...

[former_member229109]

Hello Gerd,

1) "I decided to create a second log device (also 400MB), but the log devspace remains on its original size (400MB).

Is a db restart needed to permit this additional log devspace ?"

As you know, if the database has log full status, this cannot be resolved by enlarging the log area, e. g. adding the log volume, as you did. The logging information is written sequentially. If the new log volume is added, this new volume is not described until the current write position from the last page of the preceding volume is changed.

Please review the information at "SAP MaxDB Library 7.6" : http://maxdb.sap.com/doc/7_6/default.htm -> Glossary

-> Log Area -> Volumes (Permanent Storage)

2) "why was the log devspace getting filled up, even the enabled autolog ? "

May be you had the high loading to the database & loging was written faster to compare with writing the log backup. Please check that "AUTOSAVE ON" was set in dbm.prt & dbm.utl file. May be you run out of space in the directory where the lob backups has to be written.

Please update with output of the dbm commands "medium_getall", "param_directget LOG_SEGMENT_SIZE", "info log" & "param_getvolsall".

"what happened at the first attempt of starting the database ?"

Did you have the LOG_FULL when you decided to restart the database? Please post the knldiag.old file with more information entries before the "ERR 20017 IOMan EMERGENCY SHUTDOWN" occurred.

" are there some dependencies to the knldiag.err-entry of 2008-12-08 "...BD Primkey..." ? "

The database error '-9049' was reported in knldiag.err in the past.

You could delete and recreate the affected index after it was identified.

If several indexes exist in this table, or another tables, you can use a vtrace for error -9049 to identify which index is affected.

Please review the information at Wiki :

My Home > MaxDB > Main > Tuning SAP® MaxDB > Primary Keys and Indexes

Perform a check data EXTENDED in database first, as recommended by Lars.

3) Are you SAP customer?

Thank you and best regards, Natalia Khlopina