Table of Contents Previous Next

To perform an abbreviated installation of Advanced Server without access to root or administrative privileges, invoke the installer from the command line and include the
--extract-only option. Invoking the installer with the --extract-only option extracts the binary files in an unaltered form, allowing you to experiment with a minimal installation of Advanced Server.
If you invoke the installer with the --extract-only options, you can either manually create a cluster and start the service, or run the installation script. To manually create the cluster, you must:
For more information about the initdb and pg_ctl commands, please see the PostgreSQL Core Documentation at:
If you include the --extract-only option when you invoke the installer, the installer steps through a shortened form of the Setup wizard. During the brief installation process, the installer generates an installation script that can be later used to complete a more complete installation. To invoke the installation script, you must have superuser privileges on Linux or administrative privileges on Windows.
./ --extract-only yes
edb-as96-meta-9.6.x.x-windows.exe --extract-only yes
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\9b32b613\Screen Shot 2016-09-25 at 6.16.31 PM.png
Click Next to continue to the Advanced Server License Agreement (shown in Figure 4.40).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\c64c1a1e\Screen Shot 2016-09-25 at 6.16.05 PM.png
After reading the license agreement, select the appropriate radio button and click Next to continue to the User Authentication window (shown in Figure 4.41).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\993ab022\Screen Shot 2016-09-25 at 6.17.10 PM.png
Enter the email address of a registered account in the Email field, and the corresponding password in the Password field, and click Next to continue.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\9b31b617\Screen Shot 2016-09-25 at 6.17.56 PM.png
The Extract Mode window (shown in Figure 4.42) serves as a reminder that this is a limited installation, and as such, Update Monitor will not be able to notify you of available updates for the software included in this installation. Click Next to continue to the Installation Directory window (shown in Figure 4.43).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\89ba81c3\Screen Shot 2016-09-25 at 6.18.34 PM.png
You can accept the default installation location, and click Next to continue to the Ready to Install window (shown in Figure 4.44), or optionally click the File Browser icon to choose an alternate installation directory.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\8931807e\Screen Shot 2016-09-25 at 6.19.01 PM.png
Click Next to proceed with the Advanced Server installation.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\0a3005f6\Screen Shot 2016-09-25 at 6.23.06 PM.png

Please enter the installation directory [ /opt/edb ] :

NOTE: If data directory exists and postgresql.conf file exists in that directory, we will not initialize the cluster.

Please enter the Write-Ahead Log (WAL) directory path:
[ /opt/edb/as9.6/data/pg_xlog ] :

Please enter database mode: [ oracle ] :
Specify oracle mode to include the following functionality:
Oracle-styled concatenation rules (if you concatenate a string value with a NULL value, the returned value is the value of the string).
Schemas (dbo and sys) compatible with Oracle databases added to the SEARCH_PATH.
Provides support for the DBMS_LOCK.SLEEP procedure.
This is not a comprehensive list of the compatibility features for Oracle included when Advanced Server is installed in Compatible with Oracle mode; more information about Advanced Server is available in the Database Compatibility for Oracle Developer’s Guide available at:
If you choose to install in Compatible with Oracle mode, the Advanced Server superuser name is enterprisedb.
Specify postgresql to install Advanced Server with complete compatibility with Postgres version 9.6.
If you choose to install in Compatible with PostgreSQL mode, the Advanced Server superuser name is postgres.

NOTE: We will not be able to examine, if port is currently used by other application.

Please enter the locale: [ DEFAULT ] :
Specify a locale for the Advanced Server installation. If you accept the DEFAULT value, the locale defaults to the locale of the host system.

Install sample tables and procedures? (Y/n): [ Y ] :
Press Return, or enter Y to accept the default, and install the sample tables and procedures; enter an n and press Return to skip this step.

Please provide password for the super-user(enterprisedb): [ ] :
Please re-type password for the super-user(enterprisedb): [ ] :
Specify and confirm a password for the database superuser. By default, the database superuser is named enterprisedb. (On Windows, there is no password validation if you are logged in as an administrator, but you may be prompted to supply a service account password.)

Please enter the server utilization: [ 66 ] :
The server utilization value is used as an initial value for the edb_dynatune configuration parameter. edb_dynatune determines how Advanced Server allocates system resources.
After the installation is complete, you can adjust the value of edb_dynatune by editing the postgresql.conf file, located in the data directory of your Advanced Server installation. After editing the postgresql.conf file, you must restart the server for the changes to take effect.

Please enter the workload profile: [ oltp ] :
The workload profile value is used as an initial value for the edb_dynatune_profile configuration parameter. edb_dynatune_profile controls performance-tuning based on the type of work that the server performs.
Specify oltp if the server will be supporting heavy online transaction workloads.
Specify mixed if the server will provide a mix of transaction processing and data reporting.
Specify reporting if the database server will be used for heavy data reporting.
After the installation is complete, you can adjust the value of edb_dynatune_profile by editing the postgresql.conf file, located in the data directory of your Advanced Server installation, and restarting the server.

NOTE: We will not be able to examine, if port is currently used by other application.
For more information about Infinite Cache and the edb-icache daemon, see the EDB Postgres Advanced Server Guide available at:

Table of Contents Previous Next