system crash during database extension

[Former Member]

Hello!

Unfortunatly we experienced a system crash during database extension. The new datafile (DISKD0013) was only partly (1,4GB of 9GB) created, when the server went down.

These are the error messages we get when trying to start the database:

2008-01-22 13:59:26 7246 ERR 11000 page0io_ Illegal file format

2008-01-22 13:59:26 7246 ERR 11000 page0io_ blocksize wanted: 8192, blocksize found: 0

2008-01-22 13:59:26 7214 ERR 11000 vattach dev0_vattach returned FALSE

2008-01-22 13:59:26 7214 ERR 20027 IOMan Attach error on data volume 13: Could not open volume

2008-01-22 13:59:26 7214 ERR 3 Admin Database state: OFFLINE

2008-01-22 13:59:26 7214 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2008-01-22 13:59:26 7214 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2008-01-22 13:59:28 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)

2008-01-22 13:59:28 ___ Stopping GMT 2008-01-22 12:59:28 7.6.01 Build 012-123-145-275

Is there a manual way to correct this problem by removing the "corrupted" DISKD0013?

Regards,

Fredrik

[roland_mallmann · Accepted solution]

Hi Fredrik,

you can either:

a) remove all necessary parameters from the paramfile using the relevant dbmcli commands (param_directdel)

b) perform a parameterfile recovery using dbmcli (param_restore)

You're okay as long as nothing was written on the new volume.

When using a) you need to make sure you delete all necessary parameter entries belonging to the datavolume (size, type etc.).

When you're restoring to an old parameterfile, you need to make sure the parameterfile's only difference is the datavolume extension as the last change, otherwise you'd possibly reset more than you'd like. To check the parameterhistory, you can for example take a look at the <DBSID>.pah file in the /sapdb/data/config directory.

If you're unsure what to do, i.e. if it's a productive system and you're an SAP customer: open an OSS message.

Regards,

Roland

[Former Member · Accepted solution]

Thank you very much Roland!

Option (a) helped me removing the datafile from the meta data. Just by performing these statements:

param_directdel DATA_VOLUME_NAME_0013

param_directdel DATA_VOLUME_TYPE_0013

param_directdel DATA_VOLUME_SIZE_0013

param_directdel DATA_VOLUME_MODE_0013

Best Regards,

Fredrik