Thursday, January 12, 2017

How to solve pluggable problem in 'Continuous Query Notification'?

A required feature for CQN registration of store procedure is that the database where is creating objects should be not pluggable an error will appear like below:

65131. 00000 -  "The feature %s is not supported in a pluggable database."
*Cause:    An attempt was made to use a feature that is not supported in a
           pluggable database.
*Action:   Do not use this feature in a pluggable database.

The solution is to create a new database with not PDB configurate that make enable pluggable parameter not appear in ora file.

Another problem is when you are doing a registration of a store procedure via CQN a problem will occur with other DML executed after by CQN registration, the error will be as the follow text:

ORA-29973: Unsupported query or operation during change notification registration


Important links:

Friday, December 23, 2016

How to solve common error on Oracle Weblogic using Spring Websocket?

The fooling error clarify the handshake use in Spring Websocket as it is said in the folling line:

registry.addEndpoint("/portafolio").setAllowedOrigins("*").withSockJS();

Error:


The solution to this error should be review Spring Messaging and Websocket version to charge 4.3.5.RELEASE version, there are somes changes from version 4.1.2.RELEASE to 4.3.5.RELEASE specially in Tyrus container and application server distribution.

Error:
Error during WebSocket handshake: Unexpected response code: 500

Solution: Add handshakehandler.-
registry.addEndpoint("/portafolio").setHandshakeHandler(new DefaultHandshakeHandler(new WebLogicRequestUpgradeStrategy()))
    .setAllowedOrigins("*").withSockJS();



Best regards,