Issue: An error occurs when you try to log in because the application cannot connect to the database

Resolution:

Try these steps in order, testing after each step to determine whether the issue is resolved.

Restart WebLogic using the following commands:
$ ./stopWebLogic.sh

$ nohup ./startWebLogic.sh > /dev/null &
In the WebLogic Administration Console, verify that the data source user name is set up as EMPIRICA_OPSS with the correct password. Test the connection.
In the Oracle Enterprise Manager, under System Policies, verify the codebase paths match the installation.
To check for specific permission errors, enable debugging, and examine error messages in the log file:
1. Open the WebLogic start script (startWebLogic.sh) in your domain directory, for example:
  /u01/app/oracle/Middleware/user_projects/domains/empirica/bin
2. Add the following text below the # START WEBLOGIC entry in the file:
  JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.security.debug=access,failure -Djps.auth.debug=true -Djps.auth.debug.verbose=true"
3. Restart WebLogic using the following commands:
  $ ./stopWebLogic.sh
  
  $ nohup ./startWebLogic.sh > /dev/null &
4. Examine the startWebLogic.sh output to see whether it contains the following permission error:
  java.security.AccessControlException: access denied
5. If the error exists, look below the error at the code source, such as the following text:
  CodeSource=file:/u01/app/oracle/product/Middleware/user_projects/domains/empirica/servers/SignalServer/stage/Signal/Signal/…
6. In Enterprise Manager, update the permission codebase paths in System Policies to reflect the missing permission.
7. Restart WebLogic using the following commands:
  $ ./stopWebLogic.sh
  
  $ nohup ./startWebLogic.sh > /dev/null &
8. After the permission issue is resolved, remove the debug options, and start WebLogic using the following commands:
  $ ./stopWebLogic.sh
  
  $ nohup ./startWebLogic.sh > /dev/null &