cancel
Showing results for 
Search instead for 
Did you mean: 

file systems not evenly populated in homogeneous copy

Former Member
0 Kudos

After using export_monitor to generate a dump, we use import monitor to do a homogeneous copy.

During the import, half target file systems (unix mount points) are 100%, while half of other file systems are <10% full.

As whole system, the target files systems have enough space to hold the exported data. It is ONLY a matter of uneven distribution.

How to manage it so that we can import the entire DB without adding disk space?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

How to manage it so that we can import the entire DB without adding disk space?

You have 2 choices...

1. Adjust DBSIZE.XML in System Export Folder according to SAPDATA<x> free space.

(May be hard to understand how to do the same...)

2. You can "REVISE" the Advance DB configuration on SUMMERY Page. There is page where you can distribute the datafiles across the SAPDATA directories. Just you need to do some easy calculations considering max datafile size.

(you can do this calculation in EXCEL...)

Regards.

Rajesh Narkhede

Answers (2)

Answers (2)

Former Member
0 Kudos

In the stage you are right now you can manually extend the tablespaces with sqlplus. Just add more datafiles in the sapdata's that still have space. If you don't know the syntax google for "alter tablespace add datafile" and "alter database datafile resize". I also suggest you get a clear impression on where your files are right now and on their sizes and if they autoextend or not.

But you should have properly set up the database with sapinst in the first place. Sadly there is quite a bunch of sources to cause your error, for example your new filesystem layout is not equal to the source system. Or something is wrong with your dbsize.xml, or you manually specified something in sapinst etc. etc.

Cheers Michael

Former Member
0 Kudos

I think you can mange the database import by specifying the filesystems. Have you given the correct filesystem while importing the database?