WG: AW: Re: convert big endian to medium endian

From: <ahmed.fikri_at_t-online.de>
Date: Fri, 7 Feb 2020 19:11:41 +0100 (CET)
Message-ID: <1581099101215.372302.3c3a88c8ffbbb74e73f2adecbaefa63b23d6c2f2_at_spica.telekom.de>




Gesendet mit der Telekom Mail App
<https://kommunikationsdienste.t-online.de/redirects/email_app_android_sendmail_footer>
  • Original-Nachricht --- Von: ahmed.fikri_at_t-online.de Betreff: AW: Re: convert big endian to medium endian Datum: 07.02.2020, 19:09 Uhr An: gogala.mladen_at_gmail.com

hi mladen,

the important things is the source is aix (big endian) and target db is linux with whatever coding but not a big endian. We have different encoding from src and trgt. And I thinks all this available tools like RMAN etc. just prevent a better understanding of Oracle db.

So I know what endian format is and their history (I claim) And I know the Oracle architecture (I claim)

so from my understanding I want to know why can I not migrate a database from aix to linux without using XTTS or RMAN.

By using XTTS I should export the metadata and this takes for some reason that I don't know 3 days and 4 hours.
So for me the most important things must I for this task use datapump?

If the export of the metadata would take only 4 or 8 hours I will be very happy and I would never do this research (and I will not learn new things)

Thanks and Regards
Ahmed



Gesendet mit der Telekom Mail App
<https://kommunikationsdienste.t-online.de/redirects/email_app_android_sendmail_footer>
  • Original-Nachricht --- Von: Mladen Gogala Betreff: Re: convert big endian to medium endian Datum: 07.02.2020, 18:53 Uhr An: Clay.Jackson_at_quest.com Cc: oracle list

Medium endian? Does that mean that the most significant bit is in the middle of the word? I am always keen to fight the battle of the Little Big Endian.

Mladen Gogala
Oracle Consultant
Tel:(347) 321-1217

On Fri, Feb 7, 2020, 11:56 AM Clay Jackson (cjackson) < Clay.Jackson_at_quest.com <mailto:Clay.Jackson_at_quest.com> > wrote:

  AFAIK:   The only way this would work would be with transportable tablespaces;   either using the tablespaces, or RMAN (MOS 2013271.1).

  There’s no “silver bullet” for this…    

  IMHO, your best choice is export/import with some sort of replication   solution to help minimize downtime.    

  Clay Jackson

  Database Solutions Sales Engineer

  clay.jackson_at_quest.com <mailto:clay.jackson_at_quest.com>

  office 949-754-1203 mobile 425-802-9603    

  From: oracle-l-bounce_at_freelists.org
  <mailto:oracle-l-bounce_at_freelists.org> <oracle-l-bounce_at_freelists.org
  <mailto:oracle-l-bounce_at_freelists.org> > On Behalf Of 
  ahmed.fikri_at_t-online.de <mailto:ahmed.fikri_at_t-online.de>   Sent: Friday, February 7, 2020 6:02 AM   To: oracle list <oracle-l_at_freelists.org <mailto:oracle-l_at_freelists.org>   >
  Subject: convert big endian to medium endian    

  CAUTION: This email originated from outside of the organization. Do not   follow guidance, click links, or open attachments unless you recognize   the sender and know the content is safe.    

  Hi all,

  I want to test (I hope this weekend) following:   1 from 12c Db on AIX (big endian) I will create a cold backup   2 on Oracle linux (medium endian) I will create a new db using the cold   backup from point 1
  3 somehow I should convert the files from point 1 in medium endian

  is this possible?

  I don't want to use XTTTS and exporting the metadata using data pump.

  Kind Regards
  Ahmed


  Gesendet mit der Telekom Mail App
  <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkommunikationsdienste.t-online.de%2Fredirects%2Femail_app_android_sendmail_footer&data=02%7C01%7Cclay.jackson%40quest.com%7C64f783c590674021465708d7abd6f65f%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637166812055140872&sdata=bZxDwMzcr4BMw4sNtCgEmIJQZaxyW%2FmdgLwvGevKm%2Bc%3D&reserved=0>



--
http://www.freelists.org/webpage/oracle-l



Received on Fri Feb 07 2020 - 19:11:41 CET

Original text of this message