Exadata- mismatch in the list of switches provided

Mismatch in the list of switches provided ( hw-inf01 hw-inf02) and the output of the command ibswitches ( ). Are you sure you want to continue? (y/n) [n]: y

# ./patchmgr -ibswitches ibswitches_gr -upgrade -ibswitch_precheck

2017-10-17 16:55:45 +0200 [INFO] Disabling /var/log/cellos cleanup on this node for the duration of the patchmgr session.
2017-10-17 16:55:49 +0200 1 of 1 :SUCCESS: DO: Initiate pre-upgrade validation check on InfiniBand switch(es).
----- InfiniBand switch update process started 2017-10-17 16:55:49 +0200 -----
[NOTE     ] Log file at /u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/upgradeIBSwitch.log
[INFO     ] List of InfiniBand switches for upgrade: ( hw-inf01 hw-inf02 )
[PROMPT   ] Mismatch in the list of switches provided ( hw-inf01 hw-inf02) and the output of the command ibswitches ( ). Are you sure you want to continue? (y/n) [n]: y

Note:- Since we are perfoming prechecks only there is no harm to proceed with y

[SUCCESS ] Verifying Network connectivity to hw-inf01
[SUCCESS ] Verifying Network connectivity to hw-inf01
[INFO     ] Switch hw-inf01 is already at target version
[INFO     ] Switch hw-inf01 is already at target version
[FAIL     ] Validating verify-topology output

[ERROR ] Failed to run ibnetdiscover

/u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/upgradeIBSwitch.sh: line 2788: [: -eq: unary operator expected
[ERROR    ] Failed to run ibnetdiscover
/u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/upgradeIBSwitch.sh: line 2788: [: -eq: unary operator expected
[INFO     ] Master Subnet Manager is set to "hw-inf02" in all Switches
[INFO     ] ---------- Starting with InfiniBand Switch hw-inf01
[WARNING ] Infiniband switch meets minimal version requirements, but rollback is only available to 2.1.6-2 with the current package.
     To rollback to other versions:
     - Manually download the InfiniBand switch firmware package to the patch directory
     - Set export variable "EXADATA_IMAGE_IBSWITCH_ROLLBACK_VERSION" to the appropriate version
     - Run patchmgr command to initiate rollback.
[ERROR    ] Failed to run ibnetdiscover
[INFO     ] Switch hw-inf01 already at target version 2.1.8_1
[INFO     ] ---------- Starting with InfiniBand Switch hw-inf02
[WARNING ] Infiniband switch meets minimal version requirements, but rollback is only available to 2.1.6-2 with the current package.
     To rollback to other versions:
     - Manually download the InfiniBand switch firmware package to the patch directory
     - Set export variable "EXADATA_IMAGE_IBSWITCH_ROLLBACK_VERSION" to the appropriate version
     - Run patchmgr command to initiate rollback.
[ERROR    ] Failed to run ibnetdiscover
[INFO     ] Switch hw-inf02 already at target version 2.1.8_1
[FAIL     ] Overall status
----- InfiniBand switch update process ended 2017-10-17 16:56:46 +0200 -----
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[FAIL     ] Validating verify-topology output
[FAIL     ] Overall status
SUMMARY OF ERRORS:
[FAIL     ] Validating verify-topology output
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[ERROR    ] Failed to run ibnetdiscover
[FAIL     ] Overall status

2017-10-17 16:56:46 +0200 1 of 1 :FAILED: Details in files /u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/upgradeIBSwitch.log /u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/patchmgr.stdout, /u01/app/oracle/product/11.2.0.4/dbhome_1/PSU/Infrastructure/12.1.2.3.6/ExadataStorageServer_InfiniBandSwitch/26027499/patch_12.1.2.3.6.170713/patchmgr.stderr
2017-10-17 16:56:46 +0200 1 of 1 :FAILED: DONE: Initiate pre-upgrade validation check on InfiniBand switch(es).

I noticed that I executed the patchmgr from one of database server and as soon as I switched to compute node DOM server and executed the patchmgr from there, it resolved my issue.

There could be other possible reasons too

worth checking following

/etc/resolv.conf and make sure reverse lookup is working

check if all the recommended OS packages are installed

I hope you will find the article help full to resolve this issue

Comments

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 serve...

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...

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:

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME STATUS -------------------- --------------------------- PDB$SEED NORMAL TEST_CLON UNUSABLE Solution: Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P Protection Mode: MaxPerformance Members: ORCL1PP - Primary database ORCL1PS - Physical standby database (disabled) ORA-16905: The member was not enabled yet. Fast-Start Failover: Disabled Configuration Status: SUCCESS (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL> show configuration; Configuration - DG_ORCL1P Protection Mode: MaxPerformance Members: ORCL1PP - Primary database ORCL1PS - Physical standby database Fast-Start Failover: Disabled Configuration Status: SUCCESS (status updated 38 seconds ago)

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE; System altered.

Starting RMAN and connecting to Database

<<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that you have proper TNS sentry...

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 ...

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected SQL> alter session set container=PDB02; Session alt...

Online DBA

Search This Blog