Advertisement

Migrating Databases to Exadata

  • David Fitzjarrell
  • Mary Mikell Spence
Chapter

Abstract

An Exadata system, freshly installed and configured, has but one database, normally named DBM. As you might expect, it’s a RAC database, so it exists on all available database servers. Exadata can run more than one database (either clustered or non-clustered), which is why you bought the system in the first place. Creating new databases isn’t difficult, if you’ve built RAC databases before, and if you haven’t, we’ll provide instructions and guidance in this chapter, to help you along. However, you won’t always be building truly “new” databases, because your goal is to migrate existing application databases to Exadata. There are a number of ways to accomplish this task. Some, such as the logical methods, require an empty database to work with, while others (the physical methods) will require only an init.ora file and the control files to get the process started. The aim of this chapter is to make migrating databases to Exadata as painless a task as possible.

Keywords

Golden Gate Source Database Type Disk External Storage Control File 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© David Fitzjarrell 2013

Authors and Affiliations

  • David Fitzjarrell
    • 1
  • Mary Mikell Spence
    • 1
  1. 1.ColoradoUS

Personalised recommendations