Here is the Link to the Exadata Pocket Reference. Click on the Link to Download the file.
Exadata Pocket Reference
Exadata Pocket Reference
0
On Exadata Database Machine you can configure the following Compute Node and Storage Cell attributes to setup the database server and Storage cells to send notifications about alerts.
- smtpServer
- smtpFrom
- smtpFromAddr
- smtpToAddr
- snmpSubscriber
- notificationMethod
- notificationPolicy
In this article we will demonstrate how to setup the database server and Storage cells to send notifications about alerts
Compute Nodes:
Configure Compute nodes SMTP email notification for alerts. This can be accomplished using dbmcli alter dbserver command
# Compute node 1
DBMCLI>alter dbserver smtpFrom=’Exadata – dm01db01′
DBMCLI>alter dbserver smtpFromAddr=’dbmadmin@dm01db01.netsoftmate.com’
DBMCLI>alter dbserver smtpToAddr=’oradba@netsoftmate.com’
DBMCLI>alter dbserver smtpServer=’smtp.server’
DBMCLI>alter dbserver snmpSubscriber=((host=192.168.10.1,port=162,community=public,type=ASR))
DBMCLI>alter dbserver notificationPolicy=’critical,warning,clear’
DBMCLI>alter dbserver notificationMethod=’mail,snmp’
DBMCLI>alter dbserver validate mail
Or you can use the following command
DBMCLI>alter dbserver smtpFrom=’Exadata – dm01db01′, smtpFromAddr=’dbmadmin@dm01db01.netsoftmate.com’, smtpToAddr=’oradba@netsoftmate.com’, smtpServer=’smtp.server’, snmpSubscriber=’host=192.168.10.1,port=162,community=public,type=ASR’, notificationPolicy=’critical,warning,clear’, notificationMethod=’mail,snmp’
DBMCLI>alter dbserver validate mail
*** Repeat the above step for all the Compute nodes in the cluster.
# verify
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpFrom”
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpFromAddr”
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpToAddr”
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep smtpServer”
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | grep notificationMethod”
or use the following command
# dcli -g ~/dbs_group -l root “dbmcli -e ‘list dbserver detail’ | egrep ‘(smtpFrom|smtpFromAddr|smtpToAddr|smtpServer|notificationMethod)'”
Storage Cells:
Configure Compute nodes SMTP email notification for alerts. This can be accomplished using cellcli alter cell command
# Storage Cell 01
CELLCLI>alter cell smtpFrom=’Exadata – dm01cel01′
CELLCLI>alter cell smtpFromAddr=’celladmin@dm01cel01.netsoftmate.com’
CELLCLI>alter cell smtpToAddr=’oradba@netsoftmate.com’
CELLCLI>alter cell smtpServer=’smtp.server’
CELLCLI>alter cell snmpSubscriber=((host=192.168.10.1,port=162,community=public,type=ASR))
CELLCLI>alter dbserver notificationPolicy=’critical,warning,clear’
CELLCLI>alter cell notificationMethod=’mail,snmp’
CELLCLI>alter cell validate mail
or you can also use the following command
CELLCLI>alter cell smtpFrom=’Exadata – dm01cel01′, smtpFromAddr=’celladmin@dm01cel01.netsoftmate.com’, smtpToAddr=’oradba@netsoftmate.com’, smtpServer=’smtp.server’, notificationMethod=’mail,snmp’
CELLCLI>alter cell validate mail
# Verify
# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpFrom”
# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpFromAddr”
# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpToAddr”
# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep smtpServer”
# dcli -g ~/cell_group -l root “dbmcli -e ‘list cell detail’ | grep notificationMethod”
or you can use the following command
# dcli -g ~/cell_group -l root “cellcli -e ‘list cell detail’ | egrep ‘(smtpFrom|smtpFromAddr|smtpToAddr|smtpServer|notificationMethod)'”
*** Repeat the above step for all the Storage Cells in the cluster.
Conclusion
In this article we have learned how to Configure Compute nodes and Storage Cell SMTP email notification for alerts.
While working on Exadata Storage cell patching, the patching failed due to failed internal USB drive on a storage cell.
Oracle uses internal USB drive to backup Exadata Storage cell automatically. We don’t have to backup Storage cell manually.
In this article I will demonstrate how to replace a failed USB drive an Exadata Storage cell
- You will receive an automated smtp alert (if configured) similar to below.
- You can also use the following command to check for USB drive failure
[root@dm01cel01 ~]# cellcli -e list alerthistory
1_1 2018-04-10T18:25:42-05:00 warning “Internal USB status is not present. Affected USB Slots : 0”
- You can also use the following ILOM command to check for USB drive failure
[root@dm01cel01 ~]# ssh dm01cel01-ilom
Password: *******
Oracle(R) Integrated Lights Out Manager
Version 3.2.10.22.a r121524
Copyright (c) 2017, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: dm01cel01-ilom
-> show /SYS/MB/USB0
- Open an SR with Oracle if an ASR is already generated
- Upload sundgia.sh and ILOM Snapshot to the SR for investigation
- Oracle confirms the that USB drive is faulted
- Oracle opens a Field task
- Oracle dispatch team contacts the SR owner with the hardware dispatch details
- Confirm the Hardware replacement schedule over email and/or SR
- Schedule the Hardware replacement
- Oracle FE arrives at the data center with the new USB drive
- Shutdown the storage cell by following the steps from the MOS below
Steps to shut down or reboot an Exadata storage cell without affecting ASM (Doc ID 1188080.1)
- Oracle FE replaces the faulty USB drive and power up the storage cell
- Confirm that the USB drive is good
-> show /SYS/MB/USB0
/SYS/MB/USB0
Targets:
Properties:
type = USB Port
fault_state = OK
clear_fault_action = (none)
Commands:
cd
set
show
->
[root@dm01cel01 ~]# cellcli -e list alerthistory
1_2 2018-04-11T02:45:49-05:00 clear “Internal USB status is back to normal. Affected USB Slots : 0”
- You will receive an automated smtp alert (if configured) similar to below that the USB status is back to normal
Conclusion
In this article we have learned how to replace a faulty USB drive in Exadata Storage cell. Oracle uses USB drive to backup Exadata Storage cell automatically. We don’t have to backup Storage cell manually.
Oracle Database Appliance stack patching is very simple and straight forward. The ODA patching process is fully automated and single patch contains updates for all system components such as OS, Firmware, BIOS, ILOM, Storage, Grid Infrastructure and Database. ODA patches are released every quarter and one should always consult the MOS note 888888.1 for recommended patches.
Oracle Database Appliance stack Patching consists of following major steps:
- Patching ODA Nodes (Includes Grid Infrastructure Patching)
- Patching Storage Shelve(s)
- Patching Database
In this article we will demonstrate the steps for patching entire Oracle Database Appliance stack to 12.2.1.2.0.
Steps for Patching Oracle Database Appliance (ODA) Stack
Step 1: ODA Nodes Patching
- As root user, note down the current version of the ODA on both nodes
# oakcli show version -detail
- As root user, Verify the shared disks status on both nodes. There shouldn’t be any bad disk.
# oakcli show disk
# oakcli show diskgroup
- As root user, Validate the ODA infrastructure on both nodes
# oakcli validate -d
- Ensure that sufficient space is available in the following file sytems on both nodes
# df -h -P / /opt /u01 /boot
- Download and stage the ODA patches on the both nodes
# mkdir -p /u01/app/oracle/software/ODA
- Ensure root user equivalence is working on both nodes
From node 1
ssh 192.168.16.25 hostname
From node 2
ssh 192.168.16.24 hostname
- Copy software to node 2
# mkdir -p /u01/app/oracle/software/ODA
# scp /u01/app/oracle/software/ODA/p* 192.168.16.25:/u01/app/oracle/software/ODA/
- Unpack software on both nodes
# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_1of3.zip
# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_2of3.zip
# /opt/oracle/oak/bin/oakcli unpack –package /u01/app/oracle/software/ODA/p27119652_122120_Linux-x86-64_3of3.zip
- Stop databases
$ srvctl stop database -d <name>
- Umount the NFS mounts if any
# umount /nsf
- Verify the patch
# oakcli update -patch 12.2.1.2.0 -verify
- Run from the patching from ILOM CLI
ssh odanode1-ilom
enter the root password when prompted
-> start /SP/console
enter y and hit return to confirm
# oakcli update -patch 12.2.1.2.0 -server -local
Note: Node will be rebooted as part of patching
- Ensure that CRS is Up and Running
# $GRID_HOME/bin/crsctl stat res -t
- Perform patching post checks
# oakcli update -patch 12.2.1.2.0 -verify
- Check the inventory looks as expected:
# oakcli show version -detail
- Check GI patches
$ $GRID_HOME/OPatch/opatch lspatches
*****Repeat the above steps on the second node before continuing…*******
Step 2: Storage patching
Once both ODA nodes are patched successfully, we can continue with the storage patching.
- As root user on node 1 only, execute the following command:
# oakcli update -patch 12.2.1.2.0 -storage
- Post Storage Patching, ensure that CRS is up and running on both nodes
# $GRID_HOME/bin/crsctl stat res -t
- Verify that the patching sucessful on both nodes.
# oakcli show version -detail
Step 3: Database Patching:
Once both ODA nodes and Storage Patching completed successfully, we can now patch databases.
- As root user on execute the following command:
# /opt/oracle/oak/bin/oakcli update -patch 12.2.1.2.0 –database –local
- Verify the versions of the databsae homes
# oakcli show databases -detail
# oakcli show dbhomes -detail
Conclusion
In this article we have learned to patch an Oracle Database Appliance. Oracle Database Appliance stack patching is very simple and straight forward. The ODA patching process is fully automated and single patch contains updates for all system components. The Patching is also known as One-Button patching process as it is fully automated with just few steps.
In previous articles Oracle DBCS: Create Virtual Image Database Deployment series we have learned how to:
Oracle DBCS : Create Virtual Image Database Deployment – Part 1
https://netsoftmate.blogspot.in/2018/02/oracle-dbcs-create-virtual-image-database-deployment.html
Oracle DBCS : Create Virtual Image Database Deployment – Part 2
https://netsoftmate.blogspot.in/2018/03/oracle-dbcs-create-virtual-image-database-deployment-part2.html
Oracle DBCS : Create Virtual Image Database Deployment – Part 3
https://netsoftmate.blogspot.in/2018/03/oracle-dbcs-create-virtual-image-database-deployment-part3.html
In this article we will learn the final step on how to Create a Database in Virtual Image Database Deployment.
Prerequisites
- Create Virtual Image Database Deployment
- Create Storage Volumes for Oracle Database Software and Database Files
- Install Oracle Database Software
Step to Create a Database in Virtual Image Database Deployment:
- Get the IP address of the Compute node you want to connect from Oracle Database Cloud Service Console. Here my Deployment Service Name is “NSM-DBaaS-VM” and the IP address is 144.21.72.128
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Enter login as “opc” user. You will be connected without prompting for the password. Switch to the “root” user and “oracle user”. Verify no database is running currently.
- Login as oracle user and set Oracle Home, Oracle Base and PATH variable. Make sure Oracle Executable dbca is set in PATH correctly.
- Start dbca in silent mode by providing the values on the command line as shown below:
- Connect to the database and verify the status
Conclusion
In this article we have learned how to create a database in Virtual Image Database Deployment.
In previous articles we have learned how to create Virtual Image deployment and Scale Up Storage Using Oracle Database Cloud Service and Create one storage volume for the Oracle Database software and one storage volume for all database files, and prepare them for use.
Oracle DBCS : Create Virtual Image Database Deployment – Part 1
https://netsoftmate.blogspot.in/2018/02/oracle-dbcs-create-virtual-image-database-deployment.html
Oracle DBCS : Create Virtual Image Database Deployment – Part 2
https://netsoftmate.blogspot.in/2018/03/oracle-dbcs-create-virtual-image-database-deployment-part2.html
In this article we will learn how to Install Oracle Database Software
Prerequisites
- Create Virtual Image Database Deployment
- Create Storage Volumes for Oracle Database Software and Database Files
Steps to Install Oracle Database Software in Virtual Image Database Deployment.
- Get the IP address of the Compute node you want to connect from Oracle Database Cloud Service Console. Here my Deployment Service Name is “NSM-DBaaS-VM” and the IP address is 144.21.72.128
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Enter login as “opc” user. You will be connected without prompting for the password. Switch to the “root” user and “oracle user”
- Login as oracle user, switch directory to /u01 and look for the zip file containing the Oracle Database software by displaying the contents of the /scratch/db directory. Extract the zip file into the current directory /u01
- Ensure that the Oracle software is extracted correctly
- Switch to root user and execute the set-up scripts as follows. Exit the session
Conclusion
In this article we have learned how to Install Oracle Database Software on a Virtual Image Database Deployment. Installing Oracle Software in VM Image deployment is very easy, you just need to locate the correct Oracle Software version and extract them in the correct directory.
In previous article “Oracle DBCS : Create Virtual Image Database Deployment – Part 1” we have learned how to Create Virtual Image Database Deployment using Create Service Wizard.
https://netsoftmate.blogspot.in/2018/02/oracle-dbcs-create-virtual-image-database-deployment.html
In this article we will Scale Up Storage Using Oracle Database Cloud Service and Create one storage volume for the Oracle Database software and one storage volume for all database files, and prepare them for use. This will be the part 2 and continuation of the previous article.
Prerequisites
Create Virtual Image Database Deployment
Steps to Scale up Storage using Oracle Database Cloud Service Console in Virtual Image Database Deployment.
Conclusion
In this article we have learned how to Scale Up Storage using Oracle Database Cloud Service console and create storage volumes for Oracle Database Software and Database files.
https://netsoftmate.blogspot.in/2018/02/oracle-dbcs-create-virtual-image-database-deployment.html
In this article we will Scale Up Storage Using Oracle Database Cloud Service and Create one storage volume for the Oracle Database software and one storage volume for all database files, and prepare them for use. This will be the part 2 and continuation of the previous article.
Prerequisites
Create Virtual Image Database Deployment
Steps to Scale up Storage using Oracle Database Cloud Service Console in Virtual Image Database Deployment.
- Open a web browser and enter the URL you received in the Welcome email to login to Oracle Cloud Account
- Enter your username and password
- On the home page, Click “Menu” under “Database” Cloud Service as shown below
- Click “Open Service Console”
- Currently the Storage is 32GB. Let’s Scale Up the Storage. Click on the Instance Name
- Click on the “Menu” icon and Select “Scale Up/Down”
- I am adding addition 30GB storage. Click “Yes, Scale Up/Down Service”Here I am adding addition 30GB storage. Click “Yes, Scale Up/Down Service”
- A message printed on the screen “Service scale up/down request is accepted”. The Instance status changed to “Service Maintenance”
- After sometime we can see that the Storage is now Scale up to 62GB. Click on Instance to add more Storage
- Click on the “Menu” icon and Select “Scale Up/Down”
- This time I am adding addition 50GB storage. Click “Yes, Scale Up/Down Service”
- A message printed on the screen “Service scale up/down request is accepted”. The Instance status changed to “Service Maintenance”
- After sometime we can see that the Storage is now Scale up to 112GB.
- Get the IP address of the Compute node you want to connect from Oracle Database Cloud Service Console. Here my Deployment Service Name is “NSM-DBaaS-VM” and the IP address is 144.21.72.128
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Enter login as “opc” user. You will be connected without prompting for the password. Switch to the “root” user
- Display the list of block devices, the two volumes created are xvdc and xvdd
- First format the volume for the Oracle Database software and mount it as /u01 as shown below
- Now format the volume for the database files, and mount it as /u02 as shown below
- Verify the mount points and display the block devices
- Update the /etc/fstab file so new mount points get mounted automatically whenever the VM is rebooted
Conclusion
In this article we have learned how to Scale Up Storage using Oracle Database Cloud Service console and create storage volumes for Oracle Database Software and Database files.
When you create an Oracle Database Cloud Service – Virtual Image Database Deployment, the following tasks are completed for you:
- Compute Allocated
- Storage Allocated
- Virtual Machine Image Installed
- Included software to create Oracle Database
You are responsible for Connecting to VM, create Database, perform maintenance operations such as Backup , Patching and Upgrade.
Note that Oracle Database 12c Release 2 (12.2) is not available for Oracle Database Cloud Service – Virtual Image service level.
When you create a database deployment on Oracle Database Cloud Service using the Virtual Image service level, Oracle Database software is not automatically installed and no database is created. You must perform these steps manually after the deployment is created.
To create a database on a Virtual Image Database Deployment, you perform these tasks:
- Create Virtual Image Database Deployment service level
- Create storage volumes for the Oracle Database software and for the database files, and then format and mount them
- Stage the Oracle Database software on the mount point you created for it
- Create a database and start the database instance
- Start the listener for the database instance
In this article we will demonstrate how to Create Virtual Image Database Deployment using Create Service Wizard.
Prerequisites
- Oracle Account
- Oracle Cloud Subscription
- SSH Public/Private Key pair
Steps to Create Virtual Image Database Deployment
- Open a web browser and enter the URL you received in the Welcome email to login to Oracle Cloud Account
https://myservices-xxxxx-xxxxxxxxxxef4b21bb7ee3b2cf4123d1.console.oraclecloud.com/mycloud/faces/dashboard.jspx
- Enter your username and password
- On the home page, Click “Menu” under “Database” Cloud Service as shown below
- Click “Open Service Console”
- Click on “Create Service”
Fill in all the details and click Next
- Service Name: Enter the service name, It only accepts hyphen (-) as special character
- Description (optional): Enter a description on the service
- Notification Email: To send the update on Instance creation
- Service level: Oracle Database Cloud Service
- Metering Frequency: Monthly or Hourly
- Software Release: 11gR2 or 12cR1
- Software Edition: Enterprise, standard, Enterprise Edition – Extreme performance or Enterprise Edition – High performance
- Database Type: Single Instance, Single Instance with Data Guard, RAC, RAC with Data Guard, Hybrid DR
- Select Compute Shape (CPU and Memory for your deployment). Click “Edit” beside “SSH Public Key” box
- Click on the radio button and click browse
- Select the Public Key from your desktop/laptop
- Click Enter button
- Click Next
- Review the details for deployment and click “Create”
- We can see that the deployment is being created. Click on the Instance name “NSM-DBaaS-VM”
- The status shows “Creating Service…”
- We can see that the status is “Ready”
- Virtual Image Database Deployment “NSM-DBaaS-VM” is now ready.
- You will also receive a confirmation email whent the service is created
- Enter the IP address of the Compute Node
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Click Yes
- Login as opc user, switch to root user, Switch to Oracle user and check if any database instance is running. With Virtual image database deployment database is not created by default
- Check the file systems. We can see that no users files systems are created. You need to allocate extra storage and create the users file systems.
Conclusion
In this article we have learned how to Create Virtual Image Database Deployment using Create Service Wizard. When you create an Oracle Database Cloud Service – Virtual Image Database Deployment, Compute Allocated, Storage Allocated Virtual Machine Image Installed and Included software to create Oracle Database. You are responsible for Connecting to VM, create Database, perform maintenance operations such as Backup , Patching and Upgrade.
You made some configuration changes to the Oracle Cloud Compute Node and it requires a restart/reboot take affect.
In this article we will demonstrate how to restart a Database Cloud Service Database Deployment.
Steps to Restart a Database Cloud Service Database Deployment.
Method 1:
Method 2
Wait for few minutes and execute steps 1 and 2 above.
Conclusion
In this article we have learned how to restart a Database Cloud Service Database Deployment.
In this article we will demonstrate how to restart a Database Cloud Service Database Deployment.
Steps to Restart a Database Cloud Service Database Deployment.
Method 1:
- Open a web browser and enter the URL you received in the Welcome email to login to Oracle Cloud Account
- Enter your username and password
- On the home page, Click “Menu” under “Database” Cloud Service as shown below
- Click “Open Service Console”
- On the this page, Click “Menu” as shown
- Click “Restart” from the list
- Click “OK” to confirm
- A message displays that the restart request is accepted. Click on Instance name “NSM-DBaaS”
- We can see that the status has changed to “Service Maintenance..”
- We can now see that the status has changed to Ready”. This completed the restart process
Method 2
- Open PuTTY session on your desktop and enter Compute Node IP address
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Login as opc user, switch to root user, check uptime and issue reboot command.
Wait for few minutes and execute steps 1 and 2 above.
- Login as opc user, switch to root user, check uptime and Verify the databsae and listener status
- Switch to oracle user and start the databsae if it not started already
- Verify the database status. This completed the restart process
Conclusion
In this article we have learned how to restart a Database Cloud Service Database Deployment.
You want to start a Database Cloud Service Database Deployment after completing your maintenance work. When you start a database deployment, you can access it again and can perform any management operations.
Steps to Start a Database Cloud Service Database Deployment.
- Open a web browser and enter the URL you received in the Welcome email to login to Oracle Cloud Account
- Enter your username and password
- On the home page, Click “Menu” under “Database” Cloud Service as shown below
- Click “Open Service Console”
- On the this page, Click “Menu” as shown
- Click “Start” from the list
- Click “OK” to confirm
- A message displays that the start request is accepted
- We can see that the status has changed to “Service Maintenance”. Click on Instance name “NSM-DBaaS”
- We can see that the status is still under “Service Maintenance..”
- We can now see that the status has changed to Ready”
Login to the Oracle Cloud Compute Node to verify that the server is not accessible.
- Open PuTTY session on your desktop and enter Compute Node IP address
- On the left pane, expand “SSH” and select “Auth”. On the right pane, click on “Browse” button. Select the Private Key that matches the Public Key for your Deployment. Click “Open”
- Login as opc user, check uptime and verify the database status
Conclusion
In this article we have learned how to start a Database Cloud Service Database Deployment. Starting a database deployment is very simple and it is similar to powering on a computer or laptop. When database deployment is started, its CPU and RAM are allocated. As a result, it consumes OCPU and memory resources and so metering and billing of these resources are started.