NL-08014: Failed to initialize Diagnosability framework, falling back to old network tracing/logging

Issue:

[oracle1@oracle ~]$ lsnrctl start

LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 03-APR-2019 15:49:56

Copyright (c) 1991, 2016, Oracle.  All rights reserved.

Starting /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 12.2.0.1.0 - Production
System parameter file is /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/network/admin/listener.ora
Log messages written to /u01/Installations/Oracledb_12c/product/12.2.0/dbhome_1/network/log/humint.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle)(PORT=1521)))
Error listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
TNS-12555: TNS:permission denied
 TNS-12560: TNS:protocol adapter error
  TNS-00525: Insufficient privilege for operation
   Linux Error: 1: Operation not permitted
    NL-08014: Failed to initialize Diagnosability framework, falling back to old network tracing/logging

     NL-08002: Diagnosability  context creation failed

Listener failed to start. See the error message(s) above...

Cause:

1.
OCI client running a script is unable to write a file to the ADR_BASE:

/u01/app/oracle:


oracle $ pwd
/u01/Installations/Oracledb_12c
oracle $ userid touch a.txt
user1 is executing touch a.txt as userid in /u01/Installations/Oracledb_12c
touch: cannot touch `a.txt': Permission denied <===User can not write to ADR_BASE destination directory

2. Also Problem with IPC PRotocal after changing ownership oracle to another.

Solution:

Give the correct owner permission to write to the directory specified in the parameter ADR_BASE in the sqlnet.ora file.
Alternatively, change the value for ADR_BASE to a directory where the same user has write permissions.
Change ownership to correct user.