ERROR: No supported release found, exiting

Infrastructure ExadataDBNodeUpdate Fails During Quarterly Full Stack Download Patch for Oracle Exadata.

Errors
=====

(*) 2016-04-08 09:04:04: Unzipping helpers (/root/dbupdate-helpers.zip) to /opt/oracle.SupportTools/dbnodeupdate_helpers
  (*) 2016-04-08 09:04:05: Initializing logfile /var/log/cellos/dbnodeupdate.log
  (*) 2016-04-08 09:04:06: Collecting system configuration settings. This may take a while...
  (*) 2016-04-08 09:04:55: Checking for DBFS mount scripts that may need updating after the Oracle Linux 5 to Oracle Linux 6 update...
  (*) 2016-04-08 09:04:56: Validating system settings for known issues and best practices. This may take a while...
  (*) 2016-04-08 09:04:56: Checking free space in /u02/iso.stage.080416090401
  (*) 2016-04-08 09:04:56: Unzipping /u02/p22277123_121221_Linux-x86-64.zip to /u02/iso.stage.080416090401, this may take a while


  ERROR: No supported release found, exiting

  (*) 2016-04-08 09:05:02: Cleaning up iso and temp mount

Check the “/var/log/cellos/dbnodeupdate.log” file for more info.

[INFO][./dbnodeupdate.sh][DiaryEntry][]  Entering PrintGenError No supported release found, exiting
[ERROR][./dbnodeupdate.sh][PrintGenError][]  No supported release found, exiting
[INFO][./dbnodeupdate.sh][DiaryEntry][]  Entering UpdateDbnodeupdateStatFile failed;
[INFO][./dbnodeupdate.sh][UpdateDbnodeupdateStatFile][]  dbnodeupdate.sh running standalone - no status file to be updated
[INFO][./dbnodeupdate.sh][DiaryEntry][]  Leaving UpdateDbnodeupdateStatFile failed;
[INFO][./dbnodeupdate.sh][DiaryEntry][]  Entering CleanupIsoAndMount
[INFO][./dbnodeupdate.sh][CleanupIsoAndMount][]  Unmounting the loop on /var/www/html/yum/unknown/EXADATA/dbserver/080416090401
[INFO][./dbnodeupdate.sh][CleanupIsoAndMount][]  umount loop successful


Solution:
======

Please download latest dbnodeupdate.sh from doc:- dbnodeupdate.sh and dbserver.patch.zip: Updating Exadata Database Server Software using the DBNodeUpdate Utility and patchmgr ( Doc ID 1553103.1 )


Comments

Post a Comment

Popular posts from this blog

Fatal agent error: Target Interaction Manager failed at Startup

Symptoms ========  $ /AGENT_INST/bin/emctl start agent Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved. Starting agent ......................................................................... failed. Fatal agent error: Target Interaction Manager failed at Startup Fatal agent error: Target Interaction Manager failed at Startup Fatal agent error: Target Interaction Manager failed at Startup EMAgent is Thrashing. Exiting watchdog $/AGENT_INST/sysman/log/emagent.nohup reports following error 2013-11-01 17:29:38,596 [1:main] WARN - Missing filename for log handler 'opsscfg' Agent is going down due to an OutOfMemoryError $/AGENT_INST/sysman/log/gcagent.log reports following error 2013-11-01 17:29:19,204 [1:3305B9] INFO - Invoking STARTUP_P1 (1) on Target Interaction Manager 2013-11-01 17:29:23,255 [1:main] FATAL - Fatal error: Target Interaction Manager failed at Startup java.lang.OutOfMemoryError: Java heap sp
Read more

[INS-40718] Single Client Access Name (SCAN): could not be resolved. ( LDOMS & Zones)

Cause The name you provided as the SCAN could not be resolved using TCP/IP host name lookup. Action-Provide name to use for the SCAN for which the domain can be resolved Global Zone : ============= # svccfg svc:> select name-service/switch svc:/system/name-service/switch> setprop config/host = astring: "files dns" svc:/system/name-service/switch> select system/name-service/switch:default svc:/system/name-service/switch:default> refresh svc:/system/name-service/switch:default> validate svc:/system/name-service/switch:default> exit # svcadm refresh name-service/switch # svcadm restart /system/name-service-cache; then, I can resolve host using telnet/ping.
Read more

CRS-2883: Resource 'ora.asm' failed during Clusterware stack start

Symptoms ======== root@oraprod02:~# /u01/app/12.1.0.2/grid/crs/install/rootcrs.pl -postpatch Using configuration parameter file: /u01/app/12.1.0.2/grid/crs/install/crsconfig_params 2017/11/05 15:57:38 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector. 2017/11/05 15:58:08 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector. 2017/11/05 15:58:13 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab' CRS-4123: Oracle High Availability Services has been started. CRS-4133: Oracle High Availability Services has been stopped. CRS-4123: Starting Oracle High Availability Services-managed resources CRS-2672: Attempting to start 'ora.evmd' on 'oraprod02' CRS-2672: Attempting to start 'ora.mdnsd' on 'oraprod02' CRS-2676: Start of 'ora.mdnsd' on 'oraprod02' succeeded CRS-2676: Start of 'ora.evmd' on 'oraprod02' succeeded CRS-2672: Attempting to st
Read more