The initial discussion started along the lines of “You should investigate Transportable Tablespaces. I think they are supported across platforms in 10g.” Decent enough idea, I suppose.
Then this particular user chimes in and says:
Db upgrade accross platforms has Exp/Imp as the only option available.
Ah, here’s my chance. Those were my exact sentiments a couple years ago until somebody pointed out you could setup both databases and copy data with a database link. Another person said you could unload/load comma separated data. OK, some maybe not very practical, but still a possibility. Just for the sake of argument, I posted:
100% UNTRUE. You could unload/reload ASCII files, you could use dblinks, you could use Quest's replication product.You should be careful when dealing with absolutes.
OK, maybe a little harsh, but to the point. So Mr. Exp/Imp pipes up and says:
Sure Jeff
Following are excerpts from Metalink doc 277650.1:
Quote:
The Export and Import utilities are the only method that Oracle supports for moving an existing Oracle database from one hardware platform to another. This includes moving between UNIX and NT systems.
He thinks he as me against the ropes now. If Metalink says it, it must be true. To which I reply:
surprise, surprise, metalink is wrong.
Do I get enjoyment out of proving somebody wrong? Not usually. But there is a lot of bad information out there and I don’t like perpetuating it.
9 comments:
Sounds to me like you were just bored and needed some venting. :p
Well, it was Friday night...
Just 2 blog posts ago you were talking about the Oracle Certification and in this post you point out the difference between the correct answer on the certification test and the real world...
LOL @ Steve
I'm saying yes on both points. Metalink is wrong to say that upgrade via exp/imp is the only supported upgrade method between platforms. In fact, in the upgrade guide one of the suggested upgrade methods is via dblinks and sqlplus copy. Although I don't work for Oracle Support, I'd suspect they would support a database link across platforms & versions.
Speaking of wrong information, here is one from Datawarehousing guide, 9i, pg 6-3:
"B-tree indexes are most effective for high-cardinality data: that is, for data with _many_ possible values, such as customer_name or phone_number."
but you said in the original post that you had "proved" the other guy wrong. Now you merely "suspect" they would support a database link as an upgrade method.
Well, I'd disagree with that. The fact that it is in the upgrade guide and isn't specifically labled as "but we don't support it" would imply that it is supported.
Just for the sheer sake of argument, I created a TAR. Directly from the TAR:
QUESTION
=========
I want to upgrade a Solaris 9.2.0.7 database to 10.2.0.1 on Red Hat Linux. The database I am upgrading only has 1 table that has about 10000 rows. Because it is so simple, I want to create a database link from the 10.2 database to the 9.2 database and CREATE TABLE t1 AS SELECT * FROM t2@dblink_to_92. Would this method be supported?
ANSWER
=======
Hi Jeff,
This is a supported method. Here the 9.2 database will act as the server and the 10.2 as the c
lient. And 10.2 <--> 9.2.0.7 is a supported combination.
Reference MetaLink note: 207303.1
Sure, ML Note 207303.1 states client/server version interoperability, but in general, yes, it's supported.
Which forum ( could you supply url please ) did the original exchange of views appear in?
Thanks
Post a Comment