1. How to Install Oracle 19c on Linux 7
2. How to create Oracle Database using DBCA?
3. How to Drop Database Manually?
4. How to start database?
5. How to Shutdown Database?
6. How to connect as SYSDBA?
7. How to connect to database remotely in SQL Developer?
8.Install Oracle 19c database software in silent mode
9. Create database in silent mode.
Contents
___________________________________________________________________________________________________
1. Hardware Requirements
2. Verify OS version
3. Unzip 18c Binaries
4. Set the DISPLAY Environment
5. Invoke ./runInstaller
6. Verify
___________________________________________________________________________________________________
1. Hardware Requirements
The first thing we need to verify the hardware requirements for an Oracle 18c Release 3 — Check Physical RAM. # grep MemTotal /proc/meminfo We need at least 8192 MB of physical RAM. <---- — Check Swap Space. # grep SwapTotal /proc/meminfo/* RAM up to 1024MB then swap = 2 times the size of RAM RAM between 2049MB and 8192MB then swap = equal to the size of RAM RAM more than 8192MB then swap size = 0.75 times the size of RAM We need at least 8192 MB of swap <---- -– Check space available in /tmp # df -h /tmp/* You need to have at least 2048 MB of space in the /tmp directory. <--- -– Check space for Oracle Software and pre-configured database. # df -h Space requirement for Oracle 18c Software: Enterprise Edition 14G <---- —- To determine whether the system architecture can run the software, enter the following command: # grep "model name" /proc/cpuinfo This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install. If you do not see the expected output, then you cannot install the software on this system.
[oracle@rac1 product]$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.8 (Santiago) [oracle@rac1 product]$
NOTE: You can't edit oracle home location while installation using OUI. It will pickup automatically ORACLE HOME location, where you have unzipped database binaries. Hence directly unzip in ORACLE HOME location and then start ./runInstaller After unzip, it will NOT keep all files in single directory. [oracle@rac1 ]cd /u02/app/oracle/product/18c [oracle@rac1 18c]$ ls -ltr total 4457672 -rw-r--r--. 1 oracle dba 4564649047 Jul 25 20:26 LINUX.X64_180000_db_home.zip [oracle@rac1 18c]$ [oracle@rac1 18c]$ unzip LINUX.X64_180000_db_home.zip [oracle@rac1 18c]$ ls -ltr total 4457972 -rw-r--r--. 1 oracle dba 852 Aug 18 2015 env.ora -rw-r--r--. 1 oracle dba 2927 Oct 14 2016 schagent.conf -rwxr-x---. 1 oracle dba 1783 Mar 8 2017 runInstaller <---- drwxr-x---. 7 oracle dba 4096 Feb 7 23:11 xdk drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 wwg drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:11 usm drwxr-xr-x. 5 oracle dba 4096 Feb 7 23:11 suptools drwxr-xr-x. 6 oracle dba 4096 Feb 7 23:11 srvm drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 sqlj drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 slax -rw-r-----. 1 oracle dba 10 Feb 7 23:11 root.sh.old.1 drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 relnotes drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:11 racg drwxr-xr-x. 5 oracle dba 4096 Feb 7 23:11 R drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:11 owm drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 oss drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 ordim drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:11 oracore drwxr-xr-x. 5 oracle dba 4096 Feb 7 23:11 olap drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:11 mgw drwxr-xr-x. 2 oracle dba 4096 Feb 7 23:11 log drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 has drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 dv drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 diagnostics drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 dbjava drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 data drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:11 css drwxr-xr-x. 6 oracle dba 4096 Feb 7 23:12 plsql drwxr-xr-x. 2 oracle dba 4096 Feb 7 23:12 dbs drwxr-xr-x. 2 oracle dba 4096 Feb 7 23:12 utl drwxr-xr-x. 2 oracle dba 4096 Feb 7 23:12 instantclient drwxr-xr-x. 13 oracle dba 4096 Feb 7 23:12 dmu drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:12 ucp drwxr-xr-x. 3 oracle dba 4096 Feb 7 23:12 jdbc drwxr-xr-x. 2 oracle dba 4096 Feb 7 23:12 QOpatch drwxr-xr-x. 4 oracle dba 4096 Feb 7 23:12 ords drwxr-xr-x. 5 oracle dba 4096 Feb 7 23:13 sdk drwxr-xr-x. 6 oracle dba 4096 Feb 7 23:13 apex drwxr-xr-x. 22 oracle dba 4096 Feb 7 23:13 sqldeveloper drwxr-xr-x. 8 oracle dba 4096 Feb 7 23:13 odbc drwxr-xr-x. 11 oracle dba 4096 Feb 7 23:14 ctx -rwx------. 1 oracle dba 786 Feb 7 23:14 root.sh.old drwxr-x---. 14 oracle dba 4096 Jun 4 03:20 OPatch drwxr-xr-x. 6 oracle dba 4096 Jul 18 19:17 sqlplus -rwx------. 1 oracle dba 638 Jul 18 19:18 root.sh drwxr-xr-x. 2 oracle dba 4096 Jul 18 19:39 jlib drwxr-xr-x. 5 oracle dba 4096 Jul 18 19:41 sqlpatch drwxr-xr-x. 7 oracle dba 4096 Jul 18 19:44 jdk drwxr-xr-x. 13 oracle dba 4096 Jul 18 19:44 rdbms drwxr-xr-x. 6 oracle dba 4096 Jul 18 19:44 precomp drwxr-xr-x. 5 oracle dba 4096 Jul 18 19:44 perl drwxr-xr-x. 7 oracle dba 4096 Jul 18 19:44 ord drwxr-xr-x. 7 oracle dba 4096 Jul 18 19:44 opmn drwxr-xr-x. 5 oracle dba 4096 Jul 18 19:44 nls drwxr-xr-x. 10 oracle dba 4096 Jul 18 19:44 network drwxr-xr-x. 9 oracle dba 4096 Jul 18 19:44 md drwxr-xr-x. 10 oracle dba 4096 Jul 18 19:44 ldap drwxr-xr-x. 8 oracle dba 4096 Jul 18 19:44 javavm drwxr-xr-x. 5 oracle dba 4096 Jul 18 19:44 hs drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:44 drdaas drwxr-xr-x. 3 oracle dba 4096 Jul 18 19:44 demo drwxr-xr-x. 7 oracle dba 4096 Jul 18 19:44 cv drwxr-xr-x. 6 oracle dba 4096 Jul 18 19:44 crs drwxr-xr-x. 9 oracle dba 4096 Jul 18 19:44 assistants drwxr-xr-x. 8 oracle dba 4096 Jul 18 19:44 oui drwxr-xr-x. 3 oracle dba 16384 Jul 18 19:44 lib drwxr-x---. 13 oracle dba 4096 Jul 18 19:44 inventory drwxr-xr-x. 5 oracle dba 4096 Jul 18 19:44 deinstall drwxr-xr-x. 4 oracle dba 4096 Jul 18 19:44 clone drwxr-xr-x. 2 oracle dba 4096 Jul 18 19:44 bin drwxr-xr-x. 2 oracle dba 4096 Jul 18 19:44 addnode drwxr-xr-x. 10 oracle dba 4096 Jul 18 19:53 install -rw-r--r--. 1 oracle dba 4564649047 Jul 25 20:26 LINUX.X64_180000_db_home.zip [oracle@rac1 18c]$
4. Set the DISPLAY Environment
Log into the oracle user. If you are using X emulation then set the DISPLAY environmental variable.
export DISPLAY=192.168.2.3:0.0;
Start the Oracle Universal Installer (OUI) by issuing the following command. [oracle@rac1 ~]$ cd /u02/app/oracle/product/18c/ [oracle@rac1 18c]$ ./runInstaller <----- Launching Oracle Database Setup Wizard...
[oracle@rac1 bin]$ export ORACLE_HOME=/u02/app/oracle/product/18c [oracle@rac1 bin]$ ./sqlplus SQL*Plus: Release 18.0.0.0.0 - Production on Fri Jul 27 13:16:55 2018 Version 18.3.0.0.0 Copyright (c) 1982, 2018, Oracle. All rights reserved. Enter user-name:
Caution: Your use of any information or materials on this website is entirely at your own risk. It is provided for educational purposes only. It has been tested internally, however, we do not guarantee that it will work for you. Ensure that you run it in your test environment before using.
Thank you,
Rajasekhar Amudala
Email: br8dba@gmail.com
Critical Patch Update (CPU):
CPU patch are released quarterly and only includes security-related fixes.
CPUs are usually cumulative, so a later CPU will contain all of the fixes from an earlier CPU for the same patchset.
CPUs are “molecular” which means groups of related fixes (“molecules”) can be excluded if they conflict with existing patches.
Patch Set Updates (PSU):
PSU contains critical bug fixes for its intended patchset and also security fixes.
PSU are cumulative, so they contain all fixes from previous PSUs for the same patchset – they also include the CPU released on the same date. So for example PSUApr2010 includes CPUApr2010.
PSU will increment the last digit of the release number. e.g., 11.2.0.3.0 to 11.2.0.3.9
Security Patch Update (SPU):
Security Patch Update (SPU) terminology is introduced in the October 2012 Critical Patch Update as the term for the quarterly security patch.
SPU patches are the same as previous CPU patches, just a new name.
Bundle Patches:
Bundle Patches are the quarterly patches for Windows and Exadata which include both the quarterly security patches as well as recommended fixes.
Label:
The name for a set of changes (e.g. the fixing of a bug) in the source code; the output of a label is a set of C files (*.c, *.h etc)
Conflict:
Two or more bugfixes which modify the same source code files; if this is the case then only one can be applied, otherwise the code for the fixes will need to be “merged” to produce a new label
Interim Patch:
This is the official name for a one-off patch. Single bug fix.
Merge Patch:
This is combination of labels; if for example you have two bugfixes which touch the same files then you would need to have those fixes merged together, producing one new patch with a new label
Overlay Patch:
When a one-off interim patch conflicts with a PSU, an overlay patch is required. This is basically a merge of the patch you want and the PSU.
Overlay PSU:
During the lifecycle of a patchset, PSUs will normally be released every quarter.
As the patchset reaches maturity it would be expected that there are less critical bugs which can be considered as candidates for inclusion in PSUs.
At some point the number of bug fixes included in each PSU will reach a low enough number that it is no longer considered worthwhile to make the PSU cumulative.
At this point the previous PSU becomes a baseline and all future PSUs are released as “overlay PSUs”.
An example of this is 10.2.0.4.4 which is the last base PSU for the 10.2.0.4 patchset.
From 10.2.0.4.5 all PSUs are overlay PSUs, which means that in order to install, for example, 10.2.0.4.10, the user must first install 10.2.0.4.4 and then install 10.2.0.4.10 on top.
The overlay PSU is cumulative down to the base PSU, which means that by installing 10.2.0.4.4 the user automatically gets all of the fixes in 10.2.0.4.3 and below,
then by installing 10.2.0.4.10 all of the fixes in 10.2.0.4.9 down to 10.2.0.4.5 are also included.
If a conflict were to occur between an interim patch and the overlay PSU then a merge of the overlay PSU would be required.
For example, if patch 999999 conflicted with 10.2.0.4.10 then the user would install 10.2.0.4.4 as usual and then require a merge overlay patch of 10.2.0.4.10 merged with 999999.
References:
New Patch Nomenclature for Oracle Products [ID 1430923.1]
http://flashdba.com/database/all-about-patching/
Caution: Your use of any information or materials on this website is entirely at your own risk. It is provided for educational purposes only.
1. ASMLIB commands
2. Start/Stop CSSD (Non-RAC)
1. ASMLIB commands
Most commonly used asmlib commands
/etc/init.d/oracleasm start
/etc/init.d/oracleasm stop
/etc/init.d/oracleasm restart
/etc/init.d/oracleasm configure
/etc/init.d/oracleasm status
/etc/init.d/oracleasm enable
/etc/init.d/oracleasm disable
/etc/init.d/oracleasm deletedisk
/etc/init.d/oracleasm createdisk DATA /dev/sdb1
/etc/init.d/oracleasm querydisk /dev/sdb1
/etc/init.d/oracleasm querydisk DATA
/etc/init.d/oracleasm renamedisk /dev/sdb1 VOL1
/etc/init.d/oracleasm force-renamedisk DATA NEW_DATA_DISK1
/etc/init.d/oracleasm scandisks
/etc/init.d/oracleasm listdisks
Manually start CSSD (Non-RAC) /etc/init.d/init.cssd start Manually stop CSSD (Non-RAC) /etc/init.d/init.cssd stop
still page under construction !!!
Remote DBA services from an independent senior Oracle and PostgreSQL consultant: monitoring, backup, patching, tuning, high availability and migration, with a DBA you can talk to directly.
One person responsible for availability, performance and recoverability, so problems are caught before your users notice them.
Continuous checks on availability, space, sessions, locks, replication lag and slow queries, with alerts that reach a person.
Backup strategy, verification and regular restore tests with RMAN, pgBackRest and point-in-time recovery.
Planned patching and version upgrades with rollback plans and minimal downtime.
Find and fix slow SQL, tune statistics, memory and I/O, and keep performance steady as data grows.
Data Guard, RAC, Patroni and repmgr, designed, built and tested with switchover drills.
Zero-downtime migrations with GoldenGate, between versions and platforms, including Oracle to PostgreSQL.
RAC, Data Guard, GoldenGate, Exadata, multitenant, RMAN backup and recovery, patching, upgrades and performance tuning.
View Oracle DBA services →Patroni, repmgr, HAProxy and pgBackRest, streaming replication, point-in-time recovery, tuning and version upgrades.
View PostgreSQL DBA services →Cut licence costs by moving to PostgreSQL. We assess, plan and migrate your databases with minimal downtime.
Learn more →A WhatsApp or Slack channel for quick questions and updates, so you talk to the DBA, not a ticket queue.
When something critical breaks, we join a live call on Zoom or Meet and work the problem with your team.
A clear report on performance, capacity, backups and risks, with recommendations.
Regular checks of users, privileges and patch levels to keep your databases safe.
Your procedures documented, so recovery and routine tasks do not depend on one person.
Response times are agreed per plan, matched to how critical each database is.
Every plan is scoped to your environment. Pricing is a custom quote, and response targets are agreed per plan.
For smaller environments that need regular attention.
For production systems that cannot go down.
For critical, high-availability databases.
“Paste client feedback here.”
Name, Role, Company
“Paste client feedback here.”
Name, Role, Company
“Paste client feedback here.”
Name, Role, Company
Tell us about your databases and what worries you.
We review your databases and agree the scope and plan with you.
We set up monitoring, access and runbooks, then take over.
We watch, maintain and report on your databases every month.
Depending on the plan: monitoring, backup checks, patching, performance tuning and regular reports. We agree the exact scope with you before we start.
Response targets are agreed per plan, based on how critical your databases are to your business.
Oracle (including RAC, Data Guard, GoldenGate and Exadata) and PostgreSQL.
Yes. We assess your Oracle databases, plan the move and carry it out with minimal downtime, using the tools that suit your case.
We set up and monitor backups, for example RMAN for Oracle and pgBackRest for PostgreSQL, and we test restores regularly so recovery is proven, not assumed.
Access is agreed up front, through your VPN or bastion host, with named accounts and the least privileges needed. Confidentiality terms are part of the agreement.
We can manage databases running on cloud servers. Tell us your setup and we will confirm what we can support.
Book a call or send us a message. We begin with an assessment of your environment and then propose a plan.
Book a call, or tell us what you run and what keeps you up at night. We will get back to you soon with a proposal.