Need to move the database from Linux to Windows server 2012, version also have updated, from 11.2.0.1.0 to 11.2.0.4.0; Data about 1 t,

You can use rman? Or Imp/exp or other ways?

CodePudding user response:

You can write a small program from oracle and then insert the MSSQL

CodePudding user response:

Rman doesn't seem to support heterogeneous system, the network works with impdp + network_link, but this way if your database is running, the data gap is not good

CodePudding user response:

1, the original library upgrade to 11.2.0.4.0 (but suggest or create the new PSU patch);
2, the new machine installation 11.2.0.4.0 software version (consistent with the first step);
3, rman convert the database migration

CodePudding user response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

CodePudding user response:

reference 4 floor wmxcn2000 response:

exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

CodePudding user response:

reference 5 floor minsic78 reply:

Quote: refer to 4th floor wmxcn2000 response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If the application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

Expdp good server generally one hour, in about 120 g, for more than a lob, also slowly, not so fast

CodePudding user response:

reference 5 floor minsic78 reply:

Quote: refer to 4th floor wmxcn2000 response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If the application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

I mean imp/exp to 3 to 5 days,

Expdp to 3-5 hours,

CodePudding user response:

It is ok that I think the kettle, I often use it to migrating data between different databases, efficiency is very high, you can have a try,

CodePudding user response:

Upstairs said can be 1 t kettle of data for migration, but should stop business

CodePudding user response:

refer to 7th floor wmxcn2000 response:

Quote: refer to fifth floor minsic78 response:

Quote: refer to 4th floor wmxcn2000 response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If the application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

I mean imp/exp to 3 to 5 days,

Expdp to 3-5 hours,

This is what I mean...

The speed is too conservative, especially the speed of imp/exp

CodePudding user response:

If we do, downtime can control in 1 hour or so, the physical migration + upgrade

CodePudding user response:

refer to 6th floor baidu_36457652 response:

Quote: refer to the 5 floor minsic78 response:

Quote: refer to 4th floor wmxcn2000 response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If the application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

Expdp good server generally one hour, in about 120 g, for more than a lob, also slowly, not so fast

Can only say that the server is still poor - maybe or disk problem, maybe there are some other problems, work 8 hours a day, you get a 4 ~ 5 T enough

CodePudding user response:

refer to 6th floor baidu_36457652 response:

Quote: refer to the 5 floor minsic78 response:

Quote: refer to 4th floor wmxcn2000 response:

Exp sure no, 1 t data, no 3, 5 days after too,

Expdp is a scheme can be considered, if the server can work, 3-5 hours to end,

Rman do cross-platform recovery, well well, once encountered problems, may be stuck,


How long is the original poster can stop the time?

Really don't need transplanting, concrete is really want to see the disk performance...
If the application has enough down time, impdp + dblink was really a solution, can consider to premises or disk performance dope, database configuration no obvious bottleneck (switch redo not less than, for example), 1 t data two hours is enough

Expdp good server generally one hour, in about 120 g, for more than a lob, also slowly, not so fast

If light on export, exp in 10 years ago under the condition of hardware can achieve this speed,
, of course, to deal with the lob, export import tool does have trouble ~ ~nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull