The below error can happen when you run any kind of a process that uses JDBC:
ORA-28267: Invalid Namespace Value In SOA Suite 188.8.131.52
This is a bug!
The cause of the problem is when using Oracle JDBC Driver file (ojdbc6dms.jar) and calling a DB object (procedure, function etc…) that issues SQL over a DB link from 11g to 10g DB.
There is no patch for that at the moment.
I found a workaround, that was approved by oracle:
Under the below folders, replace the ojdbc6dms.jar file with ojdbc6.jar file:
You can find the ojdbc6.jar driver in the below link:
It is also suppose to be under $MID_HOME/wlserver_10.3/server/lib. You can just copy it from there.
There is one exception: No JDBC metrics will be produced. If you need it, you will have to open SR.
Read Full Post »
While trying to run a deployed composite you are getting the below error:
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-02557 oracle.wsm.policymanager.accessor.BeanAccessor The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query “&(policysets:global/%)(@appliesTo~=”WS-Client()”)” is queued for later retrieval. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:813) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:385) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:302)
This error is a bit tricky because you might consider it as a bug.
There are 2 possible reasons for this error:
- Mismatch or missing listen address in the Admin/Managed server.
- The local host(pc) name is different than the host name you’ve defined while installing SOA Suite (or other Middleware components).
You can see example for that while trying to test you process
Both reasons causes the server to NOT listen the correct address.
The solution, is to update the host name listen address under the installed Admin/Managed servers:
Go to WL console -> Environment -> Servers -> Under the configuration tab click the Admin server -> fill the Listen Address.
Repeat it for all other managed servers, and restart the servers.
Note: If there is a mismatch between your host and PC name, you might consider to fill out the local host IP address and not the DNS.
Read Full Post »
It is very problematic and annoying when you didn’t change anything on your WebLogic server (like your manage server IP), and still you get the following error:
<BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
BEA-002606> <Unable to create a server socket for listening on channel “Default”.
The address fe80:0:0:0:250:56ff:fe9e:64be might be incorrect or another process is using port 8001: java.net.BindException: Address already in use.>
<BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<BEA-000365> <Server state changed to FAILED>
<BEA-000383> <A critical service failed. The server will shut itself down>
BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Read Full Post »