File System becoming full

[Former Member]

Hi Experts,

In our production system, which is on windows 2003, the sapdata drive is becoming full (only 6.4 GB left).

One thing that can be done is to add space from other drive, but here it is not possible till next week.(sys admin on leave).

I want to know is there any way at SAP level by which I can increase the available space, by deleting dumps etc.

Please let me know what all activities can be done for the same at SAP level.

Thanks

[JPReyes · Accepted solution]

Also, if your DB growth will eat those 6.4Gb before you can add space to the drive you could check If you have free space in another local  drive and temporarely move some datafiles using brtools (SAP will need to be offline for that)

Regards, Juan

[Former Member · Accepted solution]

Hi Paul,

We are on DB2 UDB 9.7 and ECC 6.0, SP 14.

We have different drives for SAP USR, SAP DATA files, SAP Arch logs.

ex: F: for USR, D for DATA and so on...

The standard BTC jobs are running daily like BTCDEL, SNAPDEL, SPOOL etc

@Juan: how can we do the same in DB2.

Thanks

[JPReyes · Accepted solution]

I think your best shot is by using the db2relocatedb command,

Read,

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/...

Regards, Juan

[paul_power · Accepted solution]

Hi

Check the size of your db2dump directory, check if there are large FODC folders which you longer need for problem analysis (these are usually created if a crash occurs)

Check the size of your db2diag.log as this can grow quite large. If it is:

I would strongly recommend to use the feature of v9.7 where you can
control the db2diag.log size via the setting of parameter DIAGSIZE.

This will archive the db2diag.log with a timestamp and start a new one
once it reaches the filesize limit you set.

You can then move the archived db2diag.log to create space.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40436717-7a52-2c10-07b2-dcb348e5b...

Regarding moving large tables to another location, you can use the tool

DB6CONV

SAP Note 1513862 DB6: Table conversion using DB6CONV Version 5.01 or higher

Ensure to always use the latest version of the tool.

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul

I can there are many file in db2dump folder as 49244308.000, 44125612.000 etc sizes of which are upto 2 GB, can we delete those file. Also the date modified shows 2008.

Please let me know.

Thanks

[paul_power · Accepted solution]

Hi Harikrishna,

The system does not need these files, you can decide to delete or to move them to another location,. Since they date from 208 they are not related to any recent issue on the system.

This will free up alot of space on the drive where the db2dump directory. If this is the same drive you are running low on space, it should give you the tmie to add more space next week.

regards,

Paul

[Former Member · Accepted solution]

Thank you Paul.

I have moved some files from the DATA folder and got another 5 GB free.

Also I see many files with unknown formats from year 2008, 2009....

But as of now, I have 11 GB free from 6 GB previously.

Do I need to take a Back up of these file, or can I delete them straight away, any use of these files in future??

[paul_power · Accepted solution]

Hi Harikrishna,

If they are in the db2dump directory then they were created when the db encountered an error.

If they are from several years ago then they are not relevant for the current state of the system.

Only the current db2diag.log is being written to by the DB.

I will not tell you to delete the old files, but I cannot think of a need to keep them as they are from old issues that the db encountered. Do you have any auditing need to keep old dump files?

At the very least, they can be moved off to some storage device to make space.

Regards,

Paul

[Former Member · Accepted solution]

Hi Paul

These files are in db2dump folder but I wonder how these files will help in auditing or other.

These files size varies from 50KB to 3GB.

Also, the db2diag file size is 15 GB.

Thanks

[paul_power · Accepted solution]

I cant think of a case where you would still need them.

For the db2diag.log 15Gb is an enormous size and would be almost impossible to analyse.

First, run the command

db2diag -A

this will archive the current db2diag.log with a timestamp and create a new fresh db2diag (system can be up while this is done)

I would strongly recommend to use the feature of v9.7 where you can
control the db2diag.log size via the setting of parameter DIAGSIZE.

This will archive the db2diag.log with a timestamp and start a new one
once it reaches the filesize limit you set.

You can then move the archived db2diag.log to create space.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40436717-7a52-2c10-07b2-dcb348e5b...

This wlll ensure it never grows so huge again.

I suspect the db2history file might also be very large. A large history file can slow backups and even cause hang situations in certain cicumstances.

As a large history file will cause lock and performance problems during

backup, I would suggest to prune the history file frequently with db2

prune command.

This will also save space.

Regards,

Paul

[Former Member · Accepted solution]

Hey Paul,

That db2diag command I will try in the test server first and then do for the Prod.

Thanks a lot for your help

[paul_power]

Hello Harikrisha,

What database are you using?

What is your SAP release and support package level?

I would bgin by searching things like the work directory for large dump files from several months or years ago. If you dont need these any longer for investigation of issues, then they can be moved (or deleted)

Then start looking at some common tables which are known to grow large.

A useful note in SAP is

706478 -  Preventing Basis tables from increasing considerably

Also check tables like

table ARFCSDATA

See SAP Note: 375566

If a PI system check tables: XI_AF_MSG_AUDIT,XI_AF_MSG,SXMSPMAST

and SAP Note 872388

Check if your batch job logs from SM37 are taking up alot of space. If job RSBTCDEL2 being run regularly?

Hope this helps.

Regards,

Paul

[former_member375763]

Sharma,

You can try deleting the archives of the database and / or cofiles and datafiles present on the operating system.