My Oracle Support Banner

Instance startup fails with ORA-32701 as incorrect IP address defined in oranfstab (Doc ID 1571205.1)

Last updated on JUNE 17, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

 - Instance startup hangs with direct NFS
 - Incorrect IP specified in oranfstab for local keyword

 - Alert Log <alert_<DB>.log

 

Instance started by oraagent
ORACLE_BASE from environment = /u01/app/oracle
Errors in file <Database Trace Directory>/test2_dia0_20742.trc  (incident=97):
ORA-32701: Possible hangs up to hang ID=1 detected
Incident details in: <Database Trace Directory>/incident/incdir_97/test2_dia0_20742_i97.trc
Wed Jul 10 17:05:56 2013
DIA0 terminating blocker (ospid: 20020 sid: 373 ser#: 1) of hang with ID = 1
     requested by master DIA0 process on instance 1
     Hang Resolution Reason: Although the number of affected sessions did not
    justify automatic hang resolution initially, this previously ignored
    hang was automatically resolved.
     by terminating session sid:373 with serial # 1 (ospid:20020)

 - Process Trace file <test2_dia0_20742_i97.trc>

========= Dump for incident 97 (ORA 32701) ========
----- Beginning of Customized Incident Dump(s) -----

..

*** 2013-07-10 17:05:56.029
Resolvable Hangs in the System
                      Root       Chain Total               Hang               
   Hang Hang          Inst Root  #hung #hung  Hang   Hang  Resolution         
     ID Type Status   Num  Sess   Sess  Sess  Conf   Span  Action             
  ----- ---- -------- ---- ----- ----- ----- ------ ------ -------------------
      1 HANG RSLNPEND    2   373     2     2   HIGH GLOBAL Terminate Process  
  Hang Resolution Reason: Although the number of affected sessions did not
    justify automatic hang resolution initially, this previously ignored
    hang was automatically resolved.
 
  inst# SessId  Ser#     OSPID PrcNm Event
  ----- ------ ----- --------- ----- -----
      1    871     7     17918    FG enq: PE - contention
      2    373     1     20020    FG Disk file operations I/O
 
Dumping process info of pid[1299.20020] (sid:373, ser#:1)
    requested by master DIA0 process on instance 1.

 Strace Ouput for process

$strace -f -tt -T -o /tmp/ss.txt -p <OSPID>

19357 14:35:50.347552 setsockopt(41, SOL_SOCKET, SO_LINGER, {onoff=0, linger=2}, 8) = 0 <0.000017>
19357 14:35:50.347613 bind(41, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("172.xxx.xx.xxx")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address) <0.000018>
19357 14:35:50.347702 close(41)         = 0 <0.000022>
19357 14:35:50.347769 socket(PF_NETLINK, SOCK_RAW, 0) = 41 <0.000020>

..

19357 14:37:53.330942 setsockopt(41, SOL_SOCKET, SO_LINGER, {onoff=0,linger=2}, 8) = 0 <0.000015>

19357 14:37:53.330994 bind(41, {sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr("172.xxx.xx.xxx")}, 16) = -1 EADDRNOTAVAIL (Cannot assign requested address) <0.000015>

<>

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.