R3load cannot export more than 100 mount points for Oracle?

[Former Member]

We have a DB with more than 390 sapdata### mount points (HPUX-PARISC). They are truly mount points, NOT directories under some other mount points.

After export using R3load (i.e NO DB-specific ), the keydb.xml generated for import has only from sapdata1 to sapdata100.

Is there any limit here for R3load?

Thanks!

[indra_gunalan · Accepted solution]

Hi,

I think that it is limitation with sapinst. You need to run export using migmon manually. After successful export, you need to run sapinst with option system copy and manual start migmon. Sapinst will stop and ask to migmon manually.

Regards,

[markus_doehr2]

R3load doesn't copy the filesystem structure but unloads the content of the database after having checked the size of it and then distributes it across the files.

Why do you have so many different mountpoints? Is there a technical reason behind? Just curious...

Markus

[Former Member]

I believe that is because we use a snap backup tech which requires that each mount point is no more than 47GB.

Please advise.

Thanks!