Hi @NZCNESOSE,

This error might be caused due to several issues.
However you could have a look at the following points,
1. You are able to login with username "IFSPLSQLAP" to oracle.
2. IFSPLSQLAP user account is not locked.

You can further verify if the PL/SQL Access Provider is configured properly by having a look at the below documentation,
Configure PL/SQL Access Provider

You might might need to check the below article on how to convert the above link to your customer specific f1doc URL,
How to access wit.ifsworld or docs.ifs links on this site

SELECT t.*
FROM   plsqlap_environment_tab t
;

Cheers !
Dhananjaya.

Thanks for answer. 

I already checked IFSPLSQLAP user, it is active and I can log on to Oracle with that user.

We are using IFS10 UPD6.

Neno

Hi

I know that I’ve seen that error, the PLSQLAP implementation has had a redesign since UPD6.

Hi @NZCNESOSE,

Have a look at the below article,
Tip: Things to check when PL/SQL Access Provider is RED

Cheers !
Dhananjaya.

Hi @NZCNESOSE,
Incase you don’t have access to the mentioned URL above please refer the KBA on this which contain the same information in detail: What should I verify when PL/SQL Access Provider is RED and how to make it GREEN ?
Best Regards,
Yasas

For app10 upd5 and onwards it has change from http calls from the database to jms messages executed by an batch processor in the mainserver. Look at the oracle queue BATCH_PROC_QUEUE_MAIN and verify that it is enabled for enqueuing. (Search for the the screen Oracle Queues in IFS EE navigator) Try right click on the queue, stop and start the queue, you could also try to purge the queue table. 

Ok, I remembered it as was for UPD7.

I checked  oracle queue BATCH_PROC_QUEUE_MAIN and there was a lot of messages in queue. I did purge, stop and start and tested again but still same issue. 

After  Plsqlap_Server_API.Ping_Result__ number of messages increased so apparently, messages are not picked from the queue. I will try to restart Main server during the service window and try to test again.

Look into the server.log for the mainserver1.log se if you get log entries for the batchprocessor. (often lots of errors messages i logged) It could also be that it has got stucked and a restart of the mainserver1 is needed. It hard to say without access to the server logs….

After restart of MainServer1 PING works fine (and it is possible to order Business Report from IFS client). Thank you for support!