SOLVED WL-OPC SQL data change is not permitted for a read-only connection, user or database problem

[wlcommunityusers]

Hi,
Could help us with this error, is appearing errors at the time of inserting in the bd of OPC according to what you can review, emails are not arriving, as well as I can not create users.

2019-04-04 11:17:05.979 ERROR 24454 --- [http-nio-10.4.65.147-8080-exec-8] c.wlsdm.opc.managers.DatabaseOperation   : An SQL data change is not permitted for a read-only connection, user or database.

SQL Statement:

	
	INSERT INTO PERFORMANCE_HEALTH_MAIL_DATA (
		FULL_DOMAIN_NAME,
		TYPE, 
		SUBJECT,
		
		DOMAIN_NAME,
		METRIC_NAME,
		INNER_TYPE,
		
		INSTANCE_TYPE_NAME,
		TOTAL_RECORD,
		WARNING_LABEL,
		
		NOTIFICATION_TYPE,		
		MAIN_HEADER,
		MAIN_MESSAGE,
		
		HEALTH_NAME,	
		SERVER_NAME,
		INSTANCE_NAME,
		STATE_NAME	
	) VALUES (
		?,?,?,
		?,?,?,
		?,?,?,
		?,?,?,
		?,?,?,?
	)
java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeLargeUpdate(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source) ~[derby-10.14.1.0.jar!/:na]
	at com.wlsdm.opc.managers.DatabaseOperation.insert(Unknown Source) [classes!/:v1.1.0]
	at com.wlsdm.opc.managers.NotificationSaveManager.A(Unknown Source) [classes!/:v1.1.0]
	at com.wlsdm.opc.managers.NotificationSaveManager.save(Unknown Source) [classes!/:v1.1.0]
	at com.wlsdm.opc.controller.provider.ExternalServices.notify(Unknown Source) [classes!/:v1.1.0]
	at com.wlsdm.opc.controller.ExternalServicesController.notify(Unknown Source) [classes!/:v1.1.0]
	at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) ~[na:na]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_191]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_191]
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:209) [spring-web-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136) [spring-web-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:102) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:877) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:783) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:991) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:925) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:974) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:877) [spring-webmvc-5.0.5.RELEASE.jar!/:5.0.5.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:661) [tomcat-embed-core-8.5.29.jar!/:8.5.29]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:851) [spring-webmvc-5.0.5.RELEASE.jar!

[wlsdmsupport]

Hi,

It looks like the database is not started properly.

Maybe not enough space left on the disk.

Please check your disk usage and restart the OPC by using “./opc stop” command.

Please let us know the result.

Regards.

[wlsdmsupport]

Hi,

It looks like the database is not started properly.

Maybe not enough space left on the disk.

Please check your disk usage and restart the OPC by using “./opc stop” command.

Please let us know the result.

Regards.

[wlcommunityusers]

Thanks

We checked the space in the database and it was without problems, what we did was to restart the opc application, thank you very much