hi,

i want to import data with oracle 10g/linux (machine a). then after
importing the data into oracle i want to create a dump.

it is possible to import this dump on oracle 10g/aix (machine b)? are
there any problems or known difficulties between linux/oracle 10g and
aix/oracle 10g concerning exporting/importing dumps?


thanks in advance, marton

On Sep 8, 9:06*am, marton.sz... (AT) ivz (DOT) de wrote:
If my dump you mean the result of an export (exp or expdp) then since
both instances are at 10g then you should have no problem.

It appears from your post that you are using a import to get the data
into 10g on machine A so you should be able to use the same source
file to get the data into 10g on machine B without having to load
machine A and then re-export.

You might also be able to use the transportable tablespace method of
moving the data. Look at v$transportable_platform to see if transport
between the two environments is supported (10g+).

HTH -- Mark D Powell --

On Sep 8, 9:06*am, marton.sz... (AT) ivz (DOT) de wrote:
If my dump you mean the result of an export (exp or expdp) then since
both instances are at 10g then you should have no problem.

It appears from your post that you are using a import to get the data
into 10g on machine A so you should be able to use the same source
file to get the data into 10g on machine B without having to load
machine A and then re-export.

You might also be able to use the transportable tablespace method of
moving the data. Look at v$transportable_platform to see if transport
between the two environments is supported (10g+).

HTH -- Mark D Powell --

On Sep 8, 9:06*am, marton.sz... (AT) ivz (DOT) de wrote:
If my dump you mean the result of an export (exp or expdp) then since
both instances are at 10g then you should have no problem.

It appears from your post that you are using a import to get the data
into 10g on machine A so you should be able to use the same source
file to get the data into 10g on machine B without having to load
machine A and then re-export.

You might also be able to use the transportable tablespace method of
moving the data. Look at v$transportable_platform to see if transport
between the two environments is supported (10g+).

HTH -- Mark D Powell --

On Sep 8, 9:06*am, marton.sz... (AT) ivz (DOT) de wrote:
If my dump you mean the result of an export (exp or expdp) then since
both instances are at 10g then you should have no problem.

It appears from your post that you are using a import to get the data
into 10g on machine A so you should be able to use the same source
file to get the data into 10g on machine B without having to load
machine A and then re-export.

You might also be able to use the transportable tablespace method of
moving the data. Look at v$transportable_platform to see if transport
between the two environments is supported (10g+).

HTH -- Mark D Powell --

On Mon, 8 Sep 2008 06:06:58 -0700 (PDT), marton.szabo (AT) ivz (DOT) de wrote:

Provided with 'dump' you mean exports created by exp or expdp, there
are no issues.
Be aware though, expdp and impdp can work across databases and servers
(so you don't need to expdp on one system, transfer, and impdp on the
other), provided there is sqlnet connectivity between the two affected
systems.
Also, if you decide not to follow this procedure, and choose to
transfer your export by means of ftp, you need to transfer the file in
*binary* mode.
Basically it boils down to reading the documentation, and obviously
your question was trying to prevent that.

--
Sybrand Bakker
Senior Oracle DBA

On Mon, 8 Sep 2008 06:06:58 -0700 (PDT), marton.szabo (AT) ivz (DOT) de wrote:

Provided with 'dump' you mean exports created by exp or expdp, there
are no issues.
Be aware though, expdp and impdp can work across databases and servers
(so you don't need to expdp on one system, transfer, and impdp on the
other), provided there is sqlnet connectivity between the two affected
systems.
Also, if you decide not to follow this procedure, and choose to
transfer your export by means of ftp, you need to transfer the file in
*binary* mode.
Basically it boils down to reading the documentation, and obviously
your question was trying to prevent that.

--
Sybrand Bakker
Senior Oracle DBA

On Mon, 8 Sep 2008 06:06:58 -0700 (PDT), marton.szabo (AT) ivz (DOT) de wrote:

Provided with 'dump' you mean exports created by exp or expdp, there
are no issues.
Be aware though, expdp and impdp can work across databases and servers
(so you don't need to expdp on one system, transfer, and impdp on the
other), provided there is sqlnet connectivity between the two affected
systems.
Also, if you decide not to follow this procedure, and choose to
transfer your export by means of ftp, you need to transfer the file in
*binary* mode.
Basically it boils down to reading the documentation, and obviously
your question was trying to prevent that.

--
Sybrand Bakker
Senior Oracle DBA

On Mon, 8 Sep 2008 06:06:58 -0700 (PDT), marton.szabo (AT) ivz (DOT) de wrote:

Provided with 'dump' you mean exports created by exp or expdp, there
are no issues.
Be aware though, expdp and impdp can work across databases and servers
(so you don't need to expdp on one system, transfer, and impdp on the
other), provided there is sqlnet connectivity between the two affected
systems.
Also, if you decide not to follow this procedure, and choose to
transfer your export by means of ftp, you need to transfer the file in
*binary* mode.
Basically it boils down to reading the documentation, and obviously
your question was trying to prevent that.

--
Sybrand Bakker
Senior Oracle DBA