MaxDB Data Area Full

[ChadRichardson]

Our development PI system is out of commission. The MaxDB that it runs on is locked up solid with Data Area Full (100%). Menu option Instance / Configuration / Volume is of no help since the options to add another volume are grayed out. I am logging on with the admin user so I do have the proper authorization.

Any ideas???

Thanks in advance,

Chad

[ChadRichardson]

We were able to use command line to add another volume.

[Former Member]

Hi,

For MAXDB Database, you can login into Database Manager and you can add one more volume.

I guess here the only solution is we have to add a data volume.

Thanks

Thirumal

[ChadRichardson]

Hi, Thiru

That's the first thing that I tried, but once you get to the menu options that allow you to Add a New Volume those menu options are grayed out. My guess is because the database is at 100% some of the options now are inaccessible.

I'm thinking we need to restore from backup to a point where the database was running and then move forward. We'd lose some development but that's all I'm coming up with.

Ideas???

[Former Member]

Hi Chad,

First the check is there any error message on the `knldiag" File. paste the same error log.

Step 1:

1.Check the Database wether the Database is online or offline.

If the DB is online, go to configuration and add the volume.,

Make sure that your system has enough space to add a new datavolume.

Suppose if your DB is offline.

go to dbmcli -U c

Check the DB Status.

enter the cmd : db_State

If its offline .

enter the cmd : db_online to bring the database online.

first bring database in state online then add the new data volume

(you can create little bit space like moving some old lolg files (Which is not active log) to other folder).

(Make sure that you have a backup)

Paste the Knldiag.log. (Provide the Operating system details)

Thanks

Thirumal

[Former Member]

Hi Chad

FYI..

Please find the below Knldiag.log and old log files path

Log files are usually stored in the rundirectory of the database.

On Unix/Linux this is typically '/sapdb/data/wrk/<DBSID>'

On Windows it's similar, e.g. 'c:\sapdb\data\wrk\<DBSID>'.

Paste the erorr log..

Thanks

Thirumal