BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation








EnterpriseDB Memory Tuning

Oracle Tips by Burleson Consulting

Figure 2.10: EnterpriseDB Memory Tuning

You will be able to modify this setting later.  I will cover this runtime setting, edb_dynatune, later in this chapter.  This is just one of the many runtime optimizations you can set to tune your database.  This is a nice feature because it eases the amount of tuning you must do.

Under Advanced Options, Figure 2.11, unless you are installing to a production server, you should probably just accept the defaults.  When you install your production server, you won’t need the sample tables and procedures but we will be using them for the rest of the book. 

Figure 2.11: Advanced Options

For security reasons, you also may want to change the default port on your production server.  EnterpriseDB provides many authentication and access controls and not using a standard port is just one of those.

Choose the next button to continue.

The Summary screen, Figure 2.12, is just that: a summary of the features installed and the locations where you install them.

Figure 2.12: Installation Summary

Press the Install button to begin the installation. 

While the installation program runs, you will see a status bar, Figure 2.13.

Figure 2.13: Installing

You need do nothing on this screen.

While EnterpriseDB is installing, you may see a shell console screen popup, Figure 2.14.  This particular screen is showing the initial EnterpriseDB database being created.  Don’t worry about these screens; they will close automatically when complete.

Figure 2.14: Shell Command (Creating the database)

When the installation is complete, you will get a Summary screen (Figure 2.15) with any success, warning or failure messages.  If you had a failure, this screen will direct you to the log file where you can read the exact error.

Figure 2.15: Installation Success

To verify your installation, leave the Launch Developer Studio checkbox checked.  Hit finish to end the installation and launch Developer Studio, Figure 2.16).

Figure 2.16: Test the Installation with Developer Studio

If Developer Studio launches and connects to your database, you should see something much like the above screenshot.  If you do see this, you have successfully installed EnterpriseDB.

This is an excerpt from the book "EnterpriseDB: The Definitive Reference" by Rampant TechPress.

Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.



Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software







BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.

Hit Counter