Skip to main content

How to find Exadata components version


<<Back to Exadata Main Page

Listing Exadata storage cells and their configuration info

login to your Exadata Cell Server and execute below command
# imageinfo
Kernel version: 2.6.39-400.284.1.el6uek.x86_64 #1 SMP Mon Sep 12 19:26:25 PDT 20                                                                                                             16 x86_64
Cell version: OSS_12.1.2.3.3_LINUX.X64_161013
Cell rpm version: cell-12.1.2.3.3_LINUX.X64_161013-1.x86_64
Active image version: 12.1.2.3.3.161013
Active image kernel version: 2.6.39-400.284.1.el6uek
Active image activated: 2016-10-25 14:54:29 +0200
Active image status: success
Active system partition on device: /dev/md5
Active software partition on device: /dev/md7
Cell boot usb partition: /dev/sdm1
Cell boot usb version: 12.1.2.3.3.161013
Inactive image version: 12.1.2.3.2.160721
Inactive image activated: 2016-09-13 16:03:45 +0200
Inactive image status: success
Inactive system partition on device: /dev/md6
Inactive software partition on device: /dev/md8
Inactive marker for the rollback: /boot/I_am_hd_boot.inactive
Inactive grub config for the rollback: /boot/grub/grub.conf.inactive
Inactive kernel version for the rollback: 2.6.39-400.281.1.el6uek.x86_64
Rollback to the inactive partitions: Possible
You can query similar information from v$cell_config  view as well
SQL>
  SELECT
  cellname cv_cellname
  , CAST(extract(xmltype(confval), '/cli-output/cell/releaseVersion/text()') AS VARCHAR2(20))  cv_cellVersion
  , CAST(extract(xmltype(confval), '/cli-output/cell/flashCacheMode/text()') AS VARCHAR2(20))  cv_flashcachemode
  , CAST(extract(xmltype(confval), '/cli-output/cell/cpuCount/text()')       AS VARCHAR2(10))  cpu_count
  , CAST(extract(xmltype(confval), '/cli-output/cell/upTime/text()')         AS VARCHAR2(20))  uptime
  , CAST(extract(xmltype(confval), '/cli-output/cell/kernelVersion/text()')  AS VARCHAR2(30))  kernel_version
  , CAST(extract(xmltype(confval), '/cli-output/cell/makeModel/text()')      AS VARCHAR2(50))  make_model
 FROM
   v$cell_config  -- gv$ isn't needed, all cells should be visible in all instances
    WHERE
       conftype = 'CELL'
 ORDER BY
    cv_cellname;

Listing Database Server Image and Version/PSU

login into your Exadata database Server and execute Imageinfo command. If you want to find some historic information execute imagehistory command
# imageinfo
Kernel version: 2.6.39-400.284.1.el6uek.x86_64 #1 SMP Mon Sep 12 19:26:25 PDT 2016 x86_64
Image kernel version: 2.6.39-400.284.1.el6uek
Image version: 12.1.2.3.3.161013
Image activated: 2016-10-26 11:58:58 +0200
Image status: success
System partition on device: /dev/mapper/VGExaDb-LVDbSys1
# imagehistory
Version                              : 12.1.2.3.1.160411
Image activation date                : 2016-07-12 18:23:54 +0200
Imaging mode                         : fresh
Imaging status                       : success
Version                              : 12.1.2.3.2.160721
Image activation date                : 2016-09-29 09:02:40 +0200
Imaging mode                         : patch
Imaging status                       : success
Version                              : 12.1.2.3.3.161013
Image activation date                : 2016-10-26 11:58:58 +0200
Imaging mode                         : patch
Imaging status                       : success

To List the database Version and path detail execute opatch lsinventory from $ORACLE_HOME/OPatch location as oracle user
$ opatch lsinventory
Oracle Interim Patch Installer version 12.2.0.1.7
Copyright (c) 2017, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/product/12.1.0.2/dbhome_1
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/12.1.0.2/dbhome_1/oraInst.loc
OPatch version    : 12.2.0.1.7
OUI version       : 12.1.0.2.0
Log file location : /u01/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/opatch/opatch2017-10-05_11-13-19AM_1.log
Lsinventory Output file location : /u01/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/opatch/lsinv/lsinventory2017-10-05_11-13-19AM.txt
--------------------------------------------------------------------------------
Local Machine Information::
Hostname:
ARU platform id: 226
ARU platform description:: Linux x86-64
Installed Top-level Products (1):
Oracle Database 12c                                                  12.1.0.2.0
There are 1 products installed in this Oracle Home.

Interim patches (4) :
Patch  24315824     : applied on Thu Oct 27 13:31:52 CEST 2016
Unique Patch ID:  20676808
Patch description:  "Database PSU 12.1.0.2.161018, Oracle JavaVM Component (OCT2016)"
   Created on 21 Sep 2016, 07:44:21 hrs PST8PDT

to provide better readability output is trimmed

Listing IB (Infiniband) Version info

Connect to Infiniband switch with ilom-operator or ilom-admin account, and runversion comman
Oracle(R) Integrated Lights Out Manager
Version ILOM 3.0 r47111
Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
->
-> version
SP firmware 2.1.8-1
SP firmware build number: 47111
SP firmware date: Thu Feb 19 12:16:50 IST 2015
SP filesystem version: 0.1.22

Listing PDU (Power Distribution Unit) info

Connect to PDU and execute help PDU-SystemInfo command for help menu
pducli->help PDU-SystemInfo
Command 'get' with parameters:
  get pdu_name  => response xxxxx (with xxxxx is PDU Name)
  get pdu_product_id  => response xxxxx (with xxxxx is PDU Product-ID)
  get pdu_rack_serial_number  => response xxxxx (with xxxxx is PDU Rack-SerialNumber)
  get pdu_location  => response xxxxx (with xxxxx is PDU Location)
  get pdu_part_number  => response xxxxx (with xxxxx is PDU PartNumber)
  get pdu_serial_number  => response xxxxx (with xxxxx is PDU SerialNumber)
  get pdu_date_of_manufacture  => response xxxxx (with xxxxx is PDU Date-of-Manufacture)
  get pdu_product_description  => response xxxxx (with xxxxx is PDU Product-Description)
  get pdu_hardware_version  => response xxxxx (with xxxxx is PDU Hardware-Version)
  get pdu_firmware_version  => response xxxxx (with xxxxx is PDU Firmware-Version)
  get pdu_bootloader_version  => response xxxxx (with xxxxx is PDU Bootloader-Version)
  get pdu_mac_address  => response xxxxx (with xxxxx is PDU MAC-Address)
  get pdu_display_info_time  => response xx (with xx is seconds: 1-60 allowed)
  get pdu_web_gui_refresh_interval  => response xx (with xx is seconds: 1-60 allowed)
Command 'set' with parameters:
  set pdu_name=xxxxx (with xxxxx is PDU Name)
  set pdu_product_id=xxxxx (with xxxxx is PDU Product-ID)
  set pdu_rack_serial_number=xxxxx (with xxxxx is PDU Rack-SerialNumber)
  set pdu_location=xxxxx (with xxxxx is PDU Location)
  set pdu_display_info_time=xx (with xx is seconds: 1-60 allowed)
  set pdu_web_gui_refresh_interval=xx (with xx is seconds: 1-60 allowed)
pducli->get pdu_hardware_version
pducli->pdu_hardware_version=V2/C
pducli->get pdu_firmware_version
pducli->pdu_firmware_version=V2.04 - 27.05.2015
pducli->get pdu_bootloader_version
pducli->pdu_bootloader_version=V0.01 - 15.10.2013

Listing ILOM config info

Connect to ILOM server with root user and execute version command
Oracle(R) Integrated Lights Out Manager
Version 3.2.7.26.a r112579
Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: xxxxxxx
-> version
SP firmware 3.2.7.26.a
SP firmware build number: 112579
SP firmware date: Wed Sep 28 14:24:25 CST 2016
SP filesystem version: 0.2.10

Comments

Post a Comment

Popular posts from this blog

DataPump Import Of Object Types Fails With Errors ORA-39083 ORA-2304 Or ORA-39117 ORA-39779

<<Back to Oracle DATAPUMP Main Page ORA-39083: Object type TYPE:"TEST_QA01"."LOG_RECORD" failed to create with error: ORA-02304: invalid object identifier literal Import: Release 12.1.0.2.0 - Production on Tue May 29 07:59:12 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security, OLAP, Advanced Analytics and Real Application Testing options Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/********@TEST_QA parfile=import_TEST.par Processing object type SCHEMA_EXPORT/USER Processing object type SCHEMA_EXPORT/SYSTEM_GRANT Processing object type SCHEMA_EXPORT/ROLE_GRANT Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Pr
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

How to Create Pfile from Spfile and Vice Versa

<<Back to DB Administration Main Page There are instances when a DBA need to start the database using pfile, for example to trouble an instance startup error or to validate init file post parameter changes etc. In such situations you can create a pfile from spfile and once you are done with your changes you can create spfile from updated/modified pfile to start the database. How to Create Pfile from Spfile As sysdba execute following command  SQL> create pfile='/tmp/initOrcl.ora' from spfile; How to Create SPfile from Pfile As sysdba execute following command  SQL> create spfile from  pfile='/tmp/initOrcl.ora'; You can also create the pfile directly from memory How to Create Pfile from Memory As sysdba execute following command  SQL> create  pfile='/tmp/initOrcl.ora' from memory;
3 comments
Read more

How to export only data or only metadata using expdp

<<Back to Oracle DATAPUMP Main Page CONTENT parameter of expdp let you select whether you want to export only data or only metadata or both Default : ALL Syntax and Description CONTENT=[ALL | DATA_ONLY | METADATA_ONLY] DATA_ONLY exports only table row data; no database object definitions are exported. METADATA_ONLY exports only database object definitions; no table row data is exported. Exporting metadata only  $ cat exp_full_pdb01.par directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=METADATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par Exporting data only directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=DATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par
Post a Comment
Read more

Step by Step How to Configure Software Keystore/ Oracle Wallet

<<Back to Oracle DB Security Main Page How to Configure a Software Keystore A software keystore is a container that stores the Transparent Data Encryption master encryption key. To configure a software Keystore follow the steps below. Step 1: Set the Keystore Location in the sqlnet.ora File You can store the software keystore (also known as wallet) in file system or in ASM Diskgroup. Does not matter where you want to store the keystore you have modify the sqlnet.ora and make an entry accordingly Make an entry as shown below in $ORACLE_HOME/network/admin/sqlnet.ora file Example1: If Storing the Wallet in ASM ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= +DG_TST_DATA/$ORACLE_SID/wallet )    )  )   Example2: If Storing the Wallet in File System ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= /u01/dbatst1/admin/wallet/$ORACLE_SID)    )  ) NOTE: Ensure that the path you entered in  DIREC
7 comments
Read more

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i
2 comments
Read more

ORA-28365: wallet is not open while starting the database

<<Back to DB Administration Main Page ORA-28365: wallet is not open Encountered while Starting the Database $ srvctl start instance -d CDB001 -i CDB0011 PRCR-1013 : Failed to start resource ora.cdb001.db PRCR-1064 : Failed to start resource ora.cdb001.db on node node1.oracle.com CRS-5017: The resource action "ora.cdb001.db start" encountered the following error: ORA-28365: wallet is not open . For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/node1.oracle.com/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.cdb001.db' on 'node1.oracle.com' failed Solution : Start the instance in mount mode SQL> startup mount; ORACLE instance started. Total System Global Area 2147483648 bytes Fixed Size                  2926472 bytes Variable Size            1392511096 bytes Database Buffers          738197504 bytes Redo Buffers               13848576 bytes Database mounted. Check Wallet status set linesiz
3 comments
Read more