Hi Michael,
If there is no transaction-to-cache mapping configured for the app, either statically or dynamically, the application will make direct connections from the application client, which is stored at the client side, in the script, or in the application INI files. I guess your application is making direct connections from the application client and it is using the net service name configured in Oracle net manager which thus causes the issue.
Please note PowerSever does not support net service name configured in Oracle net manager, please use database server IP + service name to solve the issue, for example, SQLCA.ServerName = "172.16.3.98/pdborcl", please refer to the article below for details.
https://docs.appeon.com/ps2021/Making_database_connections_from_the_app_client.html
Although it is still supported to connect to the database using the database connection information specified in PowerScript, you have securer options. That is, implement the connection via connection caches:
• Create the database caches, and then specify which cache each transaction object shall use for connecting to the database in the PowerServer project. Or,
• Create the database caches, and then specify which cache each transaction object shall use for connecting to the database in PowerScript.
Please refer to the article below for details.
https://docs.appeon.com/ps2021/working_with_database_connections.html
Using database caches, you can well protect the sensitive database connection information, because it is no longer necessary to keep the database connection information (including user ID, password, and DB connection string, etc.) at the client side.
If the issue remains, please provide a simple PB case to reproduce the issue for more study, thanks.
Regards,
ZhaoKai
