Former Member

May 05, 2010 at 09:35 AM

Maxdb refuses connection

129 Views

Hi experts,

Yesterday, dababase went down reporting itself as full and 'no connections possible'.

I tried to add x1 datavolume and x1 logvolume to my 7.5 Maxdb on Debian, resulting in a disaster I need to debug and recover in some way.

I checked knldiag as advised, and found:

2010-05-04 17:29:32 15 ERR 15 Admin RestartFilesystem failed

with 'I/O error'

2010-05-04 17:29:32 15 ERR 8 Admin ERROR 'disk_not_accessibl'

CAUSED EMERGENCY SHUTDOWN

2010-05-04 17:29:34 ___ Stopping GMT 2010-05-04

15:29:34 7.5.0 Build 031-123-104-253

2010-05-04 17:50:03 --- Starting GMT 2010-05-04

15:50:03 7.5.0 Build 031-123-104-253

2010-05-04 17:50:09 33 ERR 11000 d0_vatta Cannot open volume, No such

file or directory

2010-05-04 17:50:09 33 ERR 11000 d0_vatta Volume name 'DISKD0007'

2010-05-04 17:50:09 15 ERR 11000 vattach dev0_vattach returned FALSE

2010-05-04 17:50:09 15 ERR 14 IOMan Attach error on Data volume

7: Could not open volume

2010-05-04 17:50:09 15 ERR 15 Admin RestartFilesystem failed

with 'I/O error'

2010-05-04 17:50:09 15 ERR 8 Admin ERROR 'disk_not_accessibl'

CAUSED EMERGENCY SHUTDOWN

so decided to check datafiles. Log:

$ dbmancli -n localhost -d dbname -u dbman,dbman param_getvolsall LOG

OK

LOG_MIRRORED NO

MAXLOGVOLUMES 2

LOG_VOLUME_NAME_001 40960 F /home1/maxdb/dbname/DISKL001

data:

$ dbmancli -n localhost -d dbname -u dbman,dbman param_getvolsall DATA

OK

MAXDATAVOLUMES 10

DATA_VOLUME_NAME_0001 65535 F /home1/maxdb/dbname/DISKD0001

DATA_VOLUME_NAME_0002 65535 F /home1/maxdb/dbname/DISKD0002

DATA_VOLUME_NAME_0003 65535 F /home1/maxdb/dbname/DISKD0003

DATA_VOLUME_NAME_0004 65535 F /home1/maxdb/dbname/DISKD0004

DATA_VOLUME_NAME_0005 65535 F /home1/maxdb/dbname/DISKD0005

DATA_VOLUME_NAME_0006 65535 F /home1/maxdb/dbname/DISKD0006

DATA_VOLUME_NAME_0007 65535 F DISKD0007

I then 'created' /home1/maxdb/dbname/DISKD0007, /home1/maxdb/dbname/DISKL002, and re-checked:

$ dbmancli -n localhost -d dbname -u dbman,dbman param_getvolsall DATA

OK

MAXDATAVOLUMES 10

DATA_VOLUME_NAME_0001 65535 F /home1/maxdb/dbname/DISKD0001

DATA_VOLUME_NAME_0002 65535 F /home1/maxdb/dbname/DISKD0002

DATA_VOLUME_NAME_0003 65535 F /home1/maxdb/dbname/DISKD0003

DATA_VOLUME_NAME_0004 65535 F /home1/maxdb/dbname/DISKD0004

DATA_VOLUME_NAME_0005 65535 F /home1/maxdb/dbname/DISKD0005

DATA_VOLUME_NAME_0006 65535 F /home1/maxdb/dbname/DISKD0006

DATA_VOLUME_NAME_0007 65535 F /home1/maxdb/dbname/DISKD0007

$ dbmancli -n localhost -d dbname -u dbman,dbman param_getvolsall LOG OK

LOG_MIRRORED NO

MAXLOGVOLUMES 3

LOG_VOLUME_NAME_001 40960 F /home1/maxdb/dbname/DISKL001

LOG_VOLUME_NAME_002 40960 F /home1/maxdb/dbname/DISKL002

...this time seemed fine to me - am I wrong? I must be, as db_restart returns

$ dbmancli -n localhost -d dbname -u dbmanan,manpwd db_restart

ERR

-24895,ERR_SHUTDOWN: shutdown of database occured

-71,connection broken server state 6

Could please someone help/advice? I'm missing something.

max

Edited by: MMemory on May 5, 2010 2:07 PM