| recovering live database to another machine [message #64643] |
Thu, 17 February 2005 10:37  |
Tony
Messages: 190
Registered: June 2001
|
Senior Member |
|
|
Hi,
We currently have a client whose database was set up some time ago, therefore, their db_block_size=2048. We encounter the error: ora-01450. We know that we have to increase db_block_size to at least 4K in the new database to rectify the error. We were just going to take the hot backups from the previous night and restore to the new machine...then take the archivelogs and recover so we could minimize downtime.
It appears our only other option is to shutdown the source database, perform an export, create the target database with at least 4K db_block_size, then perform an import. This could mean the system is down for hours as we're dealing with about 70GB of data on a Win2003 Server.
Any suggestions of how we can get around the db_block_size issue without incurring significant downtime? This client is a 24 X 7 shop.
Thanks!
|
|
|
|
|
|
| Re: recovering live database to another machine [message #110189 is a reply to message #109947] |
Thu, 03 March 2005 23:29  |
easywebtech123
Messages: 22
Registered: March 2005
Location: c
|
Junior Member |
|
|
Hi,
Since you are getting ORA-01450 error, you can't recover the hotbackup with different parameters.
This is our solution.
If you have different schemas,export schema by schema to the new DB . So the downtime will be less.One schema down while it export to new DB.Then point that new schema.
If you have few schemas and few large tables , export table by table.
redirect new database for exported tables.
Redirection can be done in many ways, simple way is create DB link to new database, use synonyms to redirect .
webmaster
http://www.easywebtech.com
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
