Advertise at FreeMegaZone
Give tremendous boost to your business by advertising at FreeMegaZone. Contact webmaster@freemegazone.com
|
|
|
|
|
Author: Steve Callan
Page: 1 2
Consider a scenario where your new server is up and running. Your Oracle RDBMS is installed and a new instance is running with all of the new features. All that's left is to migrate the source database to the new/target database. In this article I will discuss some factors that come into play during a migration and make database migration as painless as possible.
Planning:
Below are some guidelines that you must follow during planning phase.
- Diagram the workflow and work schedule
- Assign responsibilities among team members by establishing roles and responsibilities. Maintain a contact list among team members.
- Establish a transfer point on the file system and ensure there is enough disk space for the export
- Acquire a complete understanding of schema changes about how and when key tables get altered/modified, to include data transformation processes.
Functional Groups:
- Breaking up export into functional groups like support tables, main tables, altered tables, and historical/static tables enables you to intersperse export and import.
- Once the export of a group is complete, you can start its corresponding import.
- Export and import are not one to one. Export will run quite a bit faster than import, and both can run faster if optimized a bit.
- Indexes will be re-built after the data is loaded in the target database.
Shell scripts:
- Shell scripts should have an interview process, feedback or a summary of what was entered, existence checks and bail out mechanisms after key steps or operations
Schema Migration:
- If a schema migration is taking place as opposed to a full database migration then look for names/items such as build_manager, process_logger, and stag.
- Build_manager contain common or public functions, procedures and packages.
- Process_logger may be the owner of process logs for all schemas in the text of a source.
- Unless the new schema incorporates these external or associated schemas, some or all of otherwise left behind schemas need to be accounted for in the target database.
- You may need to disable connections, change passwords, disable other processes, and suspend crons while the export is taking place. An effective way of stopping them is to change a password.
Page: 1 2
More Database Articles
Database Security: Step by step guideline
Inside default Oracle users!!
Efficiently handle Tricky Data Guard Failures!!
Oracle DBMS: Fundamental Security Precautions
The Power of Oracle 11g Sequence Enhancements!
|
