Why Oracle Export/Import Not Supported?

[Zumba]

Hi,

I had a number of cases in which I needed to copy systems from Win/Ora 32 bit to 64 bit
as well as across different Oracle releases.

Although a database copy might have been feasible (Maybe using startup migrate, etc..),
it did not work in some cases, so I used an Oracle export/import (These are small
test systems, and I had alternate plans as the procedure is unsupported), and the procedure worked
well.

My question is why the Oracle export/import process is not supported for copying systems.

For example, I think that the supported way of copying a system from Win32 to Win64 is
to do a migration, though an export/import works.

Put it another way:

Suppose that Oracle supports cloning a database from environment A to environment B
(A and B being different Oper. Systems, Oracle versions, etc..) using an export/import.
Why would SAP not support the same thing for cloning SAP databases in the same
environments?

Sure, there might be adjustment needed of export/import parameters, but it seems to
me, from a technical standpoint, that the export/import procedure is sound for SAP.

Thanks,
Zumba

[Portal]

I do not know why SAP does not support EXP/IMP. but...

to convert 32-bit to 64-bit with Windows, refer to https://www.sdn.sap.com/irj/sdn/weblogs ... /wlg/10930

[Micro]

Hello,
Process not "supported by SAP" means that support of the process is not included in the maintenance contract.
So SAP can refuse to help you if you post an OSS message reporting problem during execution of this not supported process.