Install the platform
Steps 5–8 of the installation sequence. First complete host preparation, package extraction and configuration review.
Run each command separately as Linux user dbaasnow. Read its result before moving to the next command.
Enter the working directory
whoami
cd /opt/software/dbaasnow_v3_0_2026
pwd
Confirm whoami reports dbaasnow and the directory contains install_dbaasnow.
Step 5: check host prerequisites
./install_dbaasnow --precheck dbaasnow
--precheckruns the prerequisite checker and then exits.dbaasnowselects the Lifecycle Manager installation-host checks.- It reviews OS, architecture, capacity, tools, account/sudo, DNS, time, security settings and directories.
- This command does not install components.
Continue when: the results contain no unresolved failures. Review warnings even if the final message says All checks passed successfully!.
If it fails: resolve the named problem using host preparation, then repeat this command. Skipping it allows avoidable host problems to surface during installation; full-install mode does not automatically repeat this prerequisite stage.
Step 6: download required installation files
./install_dbaasnow --download-binaries
- Reads the package's file manifest and stages required installation files.
- Uses already present files where available and downloads missing files with configured sources.
- Checks a download's checksum when a checksum is supplied in the manifest.
- Exits after staging; it does not install components.
Continue when: the command succeeds and reports All required release binaries are downloaded..
If it fails: read the missing file or download error. Check download access, permissions and the matching package. A missing file without a download source must be obtained through the approved distribution process.
You can avoid downloading a file again when it is already staged, but must still verify the complete file set in step 7.
Step 7: check the staged file set
./install_dbaasnow --check-binaries
This checks that required files or extracted directories are present and non-empty. It exits after checking and does not install components.
Continue when: it reports All required release binaries are present..
If it fails: resolve every Missing: entry, repeat the download/staging step as appropriate, then repeat this check. The full installer also checks selected required files before component work begins.
This is a presence/completeness check. Download checksum checks and an independently supplied archive checksum serve separate purposes.
Step 8: install all components
./install_dbaasnow --components all
--componentsselects what the installer installs.allselects the complete standard Lifecycle Manager installation.- The installer reads the three Repository password settings in
installation_config.yml, requests missing or blank values twice, and separately validates the Linux sudo credential. - It runs Repository database installation → Repository configuration → Broker → Coordinator → Plugin → Monitor → Gateway. See What the installer establishes for each stage's result.
Review the credential prompts before entering values. The Linux sudo password, the three Repository passwords and the fresh-install Broker console login serve different purposes. No customer setup-administrator username, email or password is requested.
Use full installation for the standard deployment. A selected-component installation needs an agreed placement and dependency plan; omitting a required component can leave console access, operations or monitoring incomplete.
Follow progress and retain the log
The installer prints the installation log location at startup. The default directory is:
~/.dbaasnow/logs/installation/
Long tasks print progress or a still-running message. Allow them to finish; avoid launching a second installation while the first is running.
If a component fails, the installer reports the failed task and stops. Preserve the first error and the full log, then use installation troubleshooting. Some earlier components may already be installed.
Check completion
At the end of a successful full installation, the installer prints its completion message, elapsed time and a console URL.
Copy the complete URL as printed. For the new Broker console, log in with admin/admin, then change the password immediately.
Next: Verify completion and console access, then complete post-installation readiness before creating your first target database project.