Skip to main content

Hello,

 

This error occurs when a new employee is about to be created or when a terminated employee is being reactivated. 

  • Ifs.Fnd.FndSystemException: Unexpected error while calling server method AccessPlsql/Invoke ---> Ifs.Fnd.FndServerFaultException: ORA-28759: failure to open file

     

    ORA-28759: failure to open file
    ORA-06512: at line 18
    ORA-06512: at "SYS.UTL_HTTP", line 380
    ORA-06512: at "SYS.UTL_HTTP", line 1148
    ORA-06512: at "ZETE1APP.WEB_SERVICES_UTIL_API", line 169
    ORA-06512: at "ZETE1APP.WEB_SERVICES_UTIL_API", line 331
    ORA-06512: at "ZETE1APP.PLSQLAP_SERVER_API", line 120
    ORA-06512: at "ZETE1APP.PLSQLAP_SERVER_API", line 129
    ORA-06512: at "ZETE1APP.PLSQLAP_SERVER_API", line 151
    ORA-06512: at "ZETE1APP.PLSQLAP_SERVER_API", line 161
    ORA-06512: at "ZETE1APP.FND_LICENSE_SYS", line 13
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 1831
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 1838
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 2045
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 2064
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 1656
    ORA-06512: at "ZETE1APP.EMPLOYEE_STATUS_DETAILS_API", line 1664
    ORA-06512: at "ZETE1APP.EMP_WIZARD_UTIL_API", line 1789
    ORA-06512: at "ZETE1APP.EMP_WIZARD_UTIL_API", line 1789
    ORA-06512: at "ZETE1APP.EMP_WIZARD_UTIL_API", line 2627
    ORA-06512: at line 12
    at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)
    at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions)
    at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody)
    at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync)
    --- End of inner exception stack trace ---
    at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync)
    at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommandCollection.Invoke()
    at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommand.ExecuteNonQuery()
    at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLSelectCommandReader.Read(Boolean prepare)
    at Ifs.Fnd.Data.ADONetProvider.FndAPCommand.ExecuteDbDataReader(CommandBehavior behavior)

 

 

Previously, the process worked as intended. 

Approximately a week ago, we upgraded our Oracle DB to 19.15.

IFS 9 is used by our organization.

 

Any suggestions would be greatly appreciated.

 

Regards,

JL

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hi @ZTC ZTC JGOTA 

 

Do You have configured HTTPS? If yes check WALLET_DIR:

select * from plsqlap_environment_tab

Hello,

This error is usually related to oracle wallet. The IFS standard installation process creates the wallet and set the path to it in the plsql environment table. When making outbound calls (any calls to outbound bizapi/activity), the url, user, password and wallet path are retrieved from the plsql environment table. If the wallet was not found in this path or if it is corrupted or the session user has no access to this path, then you will get such error.

Thanks,
Jagath

Hi @ZTC ZTC JGOTA,

As the other have mentioned above, this appears to be a problem with the PL/SQL Access Provider. The easiest way to check whether the PL/SQL Access Provider is configured properly is to check it’s status from Application Monitoring Console window in IEE. 

If the PL/SQL Access Provider is configured correctly, the above entry should show a green dot. If red, there is a problem. 

As a quick and easy fix, you can attempt a reconfiguration of the application server in order to fix this. Since the error message mentions FND_LICENSE_SYS, check whether the license is valid as well. If that does not work, a more in depth investigation would have to be done.

Hope this helps!

 

I would like to say hello to @Jagath Kandambi   and @knepiosko 

 

Thank you so much for your assistance!

 

I was able to resolve the issue. 

Our problem was that we replaced the Oracle Home with the new Oracle version and it did not have the Oracle Path.

@knepiosko has provided the following SQL path which shows the following =>

 select * from plsqlap_environment_tab

file:/oracle/product/12.1.0.2/owm/wallets/oracle

 

Where may I find the variable SSL_WALLET_PATH to change the Oracle path there?

 

Thanks,

JL

Hi @ZTC ZTC JGOTA,

Where may I find the variable SSL_WALLET_PATH to change the Oracle path there?

 

Please find the attached document from F1 documentation and refer to the “Update Database” section. You need to update the PLSQLAP_ENVIROMENT_TAB with correct SSL_WALLET_PATH as mentioned in the documentation. 

Hope this helps!

Reply


Terms & ConditionsCookie settings