Tuesday, March 06, 2012

oracle.wsm.policymanager.PolicyManagerException: WSM-02106 : Cannot retrieve policy oracle/wss_username_token_service_policy

I have secured my OSB service with owsm policy oracle/wss_username_token_service_policy.
Today i started the system and checked the proxy service and i was getting following error.

An unexpected error occured accessing information about the WSDL of the service:
com.bea.wli.config.component.NotFoundException: Can not compute effective WSDL for : ProxyService CustDetails/AmwCustDetailsPS

I went to the proxy service definition and went to policy page i found the following error in the policy page.


oracle.wsm.policymanager.PolicyManagerException: WSM-02106 : Cannot retrieve policy oracle/wss_username_token_service_policy. [Possible Cause : MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00922: The ConnectionManager "oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl" cannot be instantiated.
MDS-00001: exception in Metadata Services layer
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor


I realised that the database is not up and running.Since my OWSM schema is installed in the database so i started my database.

Somehow i was getting following error while starting database from command console.


ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Process ID: 0
Session ID: 0 Serial number: 0


TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error

I tried to start the database from services and i was able to log in to DEV_MDS schema.

Once i was able to log in to the DEV_MDS schema i logged into my osb console and i was able to call the service successfully.

No comments: