This behaviour is expected for an Oracle database. If you need to increase the connections, you can change the processes limit. Using connection pooling is probably the best way of fixing this issue, which also reduces the connection acquisition time and levels-up traffic spikes.
When using Oracle with TDM Portal, you can use the below steps to resolve this issue. We highly recommend working with your company's DBA to do this.
- The solution is to get rid of all current Portal connections by stopping the TDM Web service, restarting the Oracle database, increasing the process/connection values, restarting the TDM Web Service, re-launching TDM Portal, and verifying logs that error was gone.
- Remove all currently used connections.
1. Stop the TDM Web Portal Service.
2. Verify the number of connections in Oracle manager.
- Restart the Oracle database:
1. Use the command- shutdown immediate;
2. Start the database again.
- Increase process values:
1. Use the below commands:
show parameter processes
alter system set processes=300 scope=spfile;
alter system set sessions=300 scope=spfile;
(If you get an insufficient privileges error, request a DBA to help)
- Verify the database is still up and running.
1. Restart the TDM Web Portal Service.
2. Relaunch the TDM Portal in a web browser.
- Verify the log files are free of error messages:
1. Go to C:\ProgramData\CA\CA Test Data Manager Portal\logs\
2. Open startup.log.
3. Watch and verify that the micro service start.
4. Scroll through logs and check for error messages.