Before starting the Enterprise DB service,
- verify the login user account privileges (i.e., CRUD + create View)
- go into logging.properties and set the logger to DEBUG and add the additional logging properties from the troubleshooting guide (i.e., log4j.logger.com.mchange.v2.c3po=DEBUG, and the other one)
- go into lisatmp_10.1.0 and remove the enterprisedashboard.log file, if it exists so you only see the most current log entries
- start the Enterprise Dashboard service
- watch the log file
If the service starts, then do the same on Registry service.
If Registry starts, you can edit the logging.properties file back to INFO, and start the remaining services one-by-one (i.e., Broker, Portal, Coordinator, Simulator, VSE, etc.) to ensure they all come up correctly
NOTE: I believe you already know this, but the Enterprise Dashboard DB is in one schema and the Registry DB is in a different schema. They can both be in the same Oracle database, but they must be in different schemas.