Monday, September 9, 2019

AC-50480: Internal error occurred: java.sql.SQLException: ORA-28112: failed to execute policy function during Autoconfig

My Environment

DB - 12.1.0.2.0
Apps - R12.2.5
Type - Single Instance

Both DB and Apps resides in the same box.

Issue:
While running autoconfig on both DB and APPS faced the below issue.

AC-50480: Internal error occurred: java.sql.SQLException: ORA-28112: failed to execute policy function


We checked the autoconfig log of both the tiers and found the similar issue issues recorded in both the log files.

DB Tier Autoconfig Log:

                   Generate Tns Names
##########################################################################
                Classpath                   : :/ebstst/oracle/SMOKETST/12.1.0/jdbc/lib/ojdbc6.jar:/ebstst/oracle/SMOKETST/12.1.0/appsutil/java/xmlparserv2.jar:/ebstst/oracle/SMOKETST/12.1.0/appsutil/java:/ebstst/oracle/SMOKETST/12.1.0/jlib/netcfg.jar:/ebstst/oracle/SMOKETST/12.1.0/jlib/ldapjclnt12.jar

Loading ORACLE_HOME environment from /ebstst/oracle/SMOKETST/12.1.0
Logfile: /ebstst/oracle/SMOKETST/12.1.0/appsutil/log/SMOKETST_r12smokedb/05111507/NetServiceHandler.log
AC-50480: Internal error occurred: java.sql.SQLException: ORA-28112: failed to execute policy function

Error generating tnsnames.ora from the database, temperory tnsnames.ora will be generated using templates
Instantiating templates
tnsnames.ora instantiated

WARNING: [CVM Error Report]
The following report lists errors encountered during CVM Phase
      <filename>  <return code where appropriate>
  /ebstst/oracle/SMOKETST/12.1.0/appsutil/bin/adgentns.pl  2

 No. of scripts failed in CVM phase: 1



WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /ebstst/oracle/SMOKETST/12.1.0/appsutil/install/SMOKETST_r12smokedb
      afdbprf.sh              INSTE8_PRF         1                                                                                            


Application Log:

Updating s_tnsmode to 'generateTNS'
UpdateContext exited with status: 0
AC-50480: Internal error occurred: java.sql.SQLException: ORA-28112: failed to execute policy function
ORA-06512: at "APPS.FND_MESSAGE", line 536
ORA-06512: at "APPS.FND_MESSAGE", line 576
ORA-06512: at "APPS.FND_MESSAGE", line 665
ORA-06512: at "APPS.FND_MESSAGE", line 644
ORA-06512: at "APPS.FND_CP_FNDSM", line 218
ORA-06512: at "APPS.FNDSM", line 6
ORA-04088: error during execution of trigger 'APPS.FNDSM'
ORA-06512: at "APPS.FND_APP_SYSTEM", line 1368
ORA-06512: at "APPS.FND_NET_SERVICES", line 1734
ORA-06512: at line 1                                                                                                                               


With this issue we could not find much details on the reported issue and the solutions available also not worked for us. So we tail through the alert log to find if any record of this issue addressed there. While doing so, we noticed a particular trace file from the alert log and checked the trace file which actually contains the error/cause for this issue.

Content of the trace file

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
and Real Application Testing options
ORACLE_HOME = /ebstst/oracle/SMOKETST/12.1.0
System name:    Linux
Node name:      r12smokedb.sify.net
Release:        4.1.12-37.4.1.el6uek.x86_64
Version:        #2 SMP Tue May 17 07:23:38 PDT 2016
Machine:        x86_64
Instance name: SMOKETST
Redo thread mounted by this instance: 1
Oracle process number: 53
Unix process pid: 44187, image: oracle@r12smokedb.sify.net


*** 2019-05-11 22:43:37.967
*** SESSION ID:(47.53264) 2019-05-11 22:43:37.967
*** CLIENT ID:() 2019-05-11 22:43:37.967
*** SERVICE NAME:(SYS$USERS) 2019-05-11 22:43:37.967
*** MODULE NAME:(JDBC Thin Client) 2019-05-11 22:43:37.967
*** CLIENT DRIVER:(jdbcthin) 2019-05-11 22:43:37.967
*** ACTION NAME:() 2019-05-11 22:43:37.967

Incident 14146 created, dump file: /ebstst/oracle/SMOKETST/12.1.0/admin/SMOKETST_r12smokedb/diag/rdbms/smoketst/SMOKETST/incident/incdir_14146/SMOKETST_ora_44187_i14146
.trc
ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted
], [], [], [], [], [], [], [], [], [], [], []

*********START PLSQL RUNTIME DUMP************
***Got internal error Exception caught in pl/sql run-time while running PLSQL***
***Got ORA-600 while running PLSQL***
ANONYMOUS BLOCK:
library unit=c1922a70 line=1 opcode=191 static link=0 scope=0
FP=0x7fa44003af30 PC=0xc2825288 Page=0 AP=(nil) ST=0x7fa44003c000
DL0=0x7fa43f64ffe0 GF=0x7fa43f650038 DL1=0x7fa43f650000 DPF=0x7fa43f650028
HS=0xc28253f8 AR=0x7fa43f64ff98 DS=0xc28253c8
PB_PC=(nil) SV_PC=(nil)
DS pkg desc :
0C28252D0                   02920314 00000050          [....P...]
0C28252E0 00020004 00000000 00000000 00000001  [................]
0C28252F0 00C80000 00000005 00E80000 00000204  [................]
0C2825300 00000000 00000000 00000000 00000000  [................]                                                     


ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted. -à This particular issue leads us to the document Doc ID : 1625010.1 which provides the solution.


Cause:
If /dev/shm is mounted with "noexec" such an error occurs.


Solution for the error :


After performing this change, autoconfig completed successfully in both the tiers.


Ref : ORA-600 [pesldl03_MMap: Errno 1 Errmsg Operation Not Permitted] (Doc ID 1625010.1)


                       ****************************நன்றி****************************

1 comment:

  1. Excellent Mr.Davis .. I have checked lot of Oracle Documents and website too .. But in your block it shows clear steps to fix the issue.

    Thanks for sharing the fix..

    Keep going !!

    Regards,
    Ravi Ganesh GTR.

    ReplyDelete

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...