I write this email from an other email box(I'm in the train and the other
app doesn't work now)
Thanks a lot Lewis not only for your technical explanation but also for
reading between the lines and understanding my real problem. (Even my
broken English)
Thanks and Regards
Ahmed
Jonathan Lewis <jonathan@xxxxxxxxxxxxxxxxxx> schrieb am Fr., 7. Feb. 2020,
19:15:
Your approach will not work because Oracle Corp. has not implemented an
"in situ" mechanism for reading and updating a system tablespace and data
dictionary that is in the wrong endian format. If they had produced such a
mechanism they would have been shouting about it because it would make it
much easier to migrate to Exadata from any alien platform.
If your dba is an expert then they might have mentioned which version of
Oracle (11g is not a version, it's a marketing term), and which bug. There
are many known bugs relating to slow metadata export and many of those bugs
have patches. If your dba is a really expert expert they may even be able
to work out WHY the export is slow (if there isn't a patch to fix their
problem) and hack the data dictionary or supply SQL Patches to speed it up.
Regards
Jonathan Lewis
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of ahmed.fikri@xxxxxxxxxxx <ahmed.fikri@xxxxxxxxxxx>
Sent: 07 February 2020 17:16
To: Clay.Jackson@xxxxxxxxx
Cc: oracle list
Subject: AW: RE: convert big endian to medium endian
thanks for this information. But when I hear the only one way to do
something, I need to know why there is only one way. And why my approach
will not work.
My problem is when using XTTS I should (from my understanding) export the
metadata using datapump and the problem this takes 3 days and 4 hours. And
from my understanding why should I export the metadata. Our DBA is an
expert and he told me the export takes long time because of known bug in
11g. In the past I could copy databases using only cold backup, I could
copy the data files in parallel using several processes. I'm not a DBA (I
am from the application vendor installed on the db) but I read D. Kuhn book
from the beginning to the end. So I need to understand how to to do this
task: upgrading 11g on aix to 12g on linux in less than one weekend without
using the buggy datapump.
this should be possible or not?The db is only 16tb big.
regards
Ahmed
Gesendet mit der Telekom Mail App
--- Original-Nachricht ---
Von: Clay Jackson (cjackson)
Betreff: RE: convert big endian to medium endian
Datum: 07.02.2020, 17:55 Uhr
An: oracle list
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@xxxxxxxxx
office 949-754-1203 mobile 425-802-9603

From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On
Behalf Of ahmed.fikri@xxxxxxxxxxx
Sent: Friday, February 7, 2020 6:02 AM
To: oracle list <oracle-l@xxxxxxxxxxxxx>
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
