SXMB_MONI : Error in Persistence Layer : XML Message Not Found

Hi Team,
There are some messages in our Production system and is in Scheduled state in SXMB_MONI and when we try to re-process those messages, we are getting message : Error in Persistence Layer and when we double click on message, we are getting the error : XML Message Not Found.
Any help on this is highly appreciated.
Thanks & Regards,
C V Jayachandra

Hi,
Please refer the below discussion
SXMB_MONI - Error accessing persistence layer
regards,
Harish

Similar Messages

SXMB_MONI - Error accessing persistence layer

Hi,
In SXMB_MONI there are messages with status "system error manual restart possible" and "scheduled". when i try opening those messages it says "XML message not found". I no longer need those messages and want to delete them. But when i try to cancel those messages it says " Error accessing persistence layer".
Is there any way by which I can delete those messages?
Regards,
Mateen.

Hi Meetan
refer these thread for the same may be helpful for you
IS_Retry and RSXMB_RESTART_MESSAGES
release queue
BPM error
/people/krishna.moorthyp/blog/2005/11/28/inactive-integration-process-ip-at-run-time
Thanks!!

BPM error : Message pipeline PE_ADAPTER unknown XML message not found. Help

Hello All,
I have done 3 steps in BPM
RFC --- BPM --- RFC
RECEIVE step ==> Opens SYNCH ASYNCH bridge and receives RFC request message
SEND synchronous ==> to send RFC request and get the RFC response.
SEND ==> Closes SYNCH ASYNCH bridge and Send's response back to the RFC.
In my last send step (response back) I am getting message
"Message pipeline PE_ADAPTER unknown XML message not found" .
Pls help

Hi Rick,
check out this SAP Note: 1087532
Regards
Dominic

Package org.apache.axis.message not found in import.

Hi,
I am using axis to give response to another bpel process after any operation is completed of a BPEL process.I am using JDeveloper to deploy my bpel process.It has succesfully deployed process without any error but when bpel server is unpacking it and deploying it to oc4j,it get error:
Package org.apache.axis.message not found in import.
06/02/08 12:40:40 import org.w3c.dom.Element;import java.util.Calendar;import java.util.Date;import com.collaxa.cube.engine.ext.process;
import com.oracle.services.bpel.task.*;import com.oracle.bpel.client.BPELFault;import com.collaxa.cube.xml.schema.XMLSchemaUtils;import com.
oracle.bpel.client.util.WhereCondition;import com.oracle.bpel.client.Locator;import com.oracle.bpel.client.delivery.IDeliveryService;import
com.oracle.bpel.client.NormalizedMessage;import com.oracle.bpel.client.IInstanceHandle;import com.oracle.bpel.client.ServerException;import
com.oracle.services.bpel.Process.*;import org.apache.axis.message.*;import javax.xml.soap.Name;
I have manually copied all axis jars to
1)OraBPEL\integration\orabpel\system\appserver\oc4j\j2ee\home\applib
2)OraBPEL\integration\orabpel\lib
But no use.
Can anybody help!

I've put a lot og jar files in the bpel-inf/lib but it looks as if they are not in the class path when I need them. The result is a ClassNotFoundException? Do I have to specify anything else? I've put a class in the bpel-inf/classes and it looks to me as if it is found by the BPM.

UIXJSP App built off BC4J Project JBO Excep XML File not found for the Container

Running JDEV 9.0.3 build 960
Created a new project in folder "UIX JSP"
"UIX JSP" note the space!
Create a default UIX JSP Application based on existing BC4J Project
When running a JSP - Get a JBO Error complaining that the XML File not found for the Container
If I recreate the project with name UIX_JSP problem does not occur.

I logged a bug on this.

Client Proxy: XML message not well-formed unexpected symbol 'target

Hi,
I'm trying to get a client proxy to work based on several blogs (1387,1672)
The error I'm getting now is:
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'" p2="" p3="" p4="">PARSING.GENERAL</SAP:Code>
<SAP:Text language="EN">Parsing error: XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'</SAP:Text>
</SAP:ErrorHeader>
The proxy has been generated successfully
in SXMB_ADM R/3 role is application system and uses dest://rfc_dest
The rfc destination does not accept ?type=entry but apparently also does not need it. When I test the connection it gives a statuscode 200 (not 500)
SLDCHECK works fine.
Not sure where to look for this error?
Any ideas?
Thanks
Tom

Hello Smitha,
I forgot to mention that the message is still in R/3, it has not arrived in XI yet, so the error is visible in SXMB_MONI in R/3.
Also it is just a dummy message, It only contains one node and that is called differently:
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:IF021_HTTP_MSG xmlns:ns1="http://oce.com/xi/eu1/R3CCSEU/IF021_Ordrsp_TD_to_Ordrsp_CCS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<IF021_DT>GetOrdRsp</IF021_DT>
</ns1:IF021_HTTP_MSG>
Any mappings only take place in XI itself, and even there I have no node called target.
Regards
Tom

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

SMD uninstallation error "ORADBPAR.XML" file not found.

Hello Experts,
I was doing System preparation in solution manager through Solman_setup.In step 6.5 I came across Install Diagonostic agent .I checked in my system that older version of SMD is installed that may cause problem in future so I decided to uninstall it and install newer version of SMD7.3.I downloaded the SMD file and started sapinst with sudo access to uninstall it.Now I am getting an error saying ORADBPAR.XML file not found.I checked for this file but I could not find .Plz help me out to find this file and resolve the issue.
Thanks
Aditya Roushan

Hi Carole,
I had older version of SMD(7.01) installed in my system.I tried uninstalling this with sapinst downloaded with SMD7.2 so i got this error.I had to download the SMD7.01 from market place (you willl get this in archive) and then uninstall the SMD using this sapinst (which came with 7.01 version).i could do this successfully.Hope this will help you
@Jose:Thanx for ur reply but using sudo had no problem.I uninstalled older SMD7.01 and installed SMD7.2 using sudo privilege only.
Thanks
Aditya Roushan

IN FB Mafia Wars getting this message Unexpected Error has occurred. Requested URL not found: 400 What do I do?

These errors only appear on my laptops. Running FBMW Add Ons with grease money on 1 laptop , and the other laptop does not have these installed. The problem started 3 days ago.
From Firefox Error Console:
Warning: Error in parsing value for 'background-image'. Declaration dropped.
Source File: https://support.mozilla.com/en-US/questions/new?product=beta&category=b2&search=IN+FB+Mafia+Wars+getting+this+message+++Unexpected+Error+has+occurred.+++Requested+URL+not+found%3A++400+++What+do+I+do%3F&showform=1
Line: 0
These types of errors appear whenever I try doing any new actions in Mafia Wars.

Hello everyone with AVG, I have the simple solution. 1) Open your AVG Antivirus File 2) Under Tools, Open Advance Settings 3) On the left side, Click on LinkScanner 4) On the Box on the right-hand side... Unclick "ENABLE SURF-SHIELD" Click OK on the bottom of the page. PROBLEM FIXED

Brrestore give error termination message not found

Dear all
i have try to restore offline backup to test system bcaz while database upgrade it got crashed it shows error ora-01157 and ora-01110 i have the backup of system
while i am trying to restore the backup it throws error terminated message not found d:\oracle\SID\sapbackup\beojggvh.afd log file incomplete
i used following command
brrestore -b beojggvh.afd -m full -c
i copied backSID.log and beojggvh.afd file from offline backup folder to target system /oracle/sid/sapbackup suggest i went wrong
i am on windows
Regards

Hi,
Share the complete error log file and make sure data file using for restore should be a successful one complete offline backup.In addition share alert_<SID>.log file also.
Regards,
Gaurav

Error: [129]: transaction rolled back by an internal error: [129] transaction rolled back by an internal error: exception 141000274: exception 141000274: TRexUtils/ParallelDispatcher.cpp:275 message not found; $message$=

Hello Gurus,
I have a couple of calculation views in HANA and each of them has text fields (like Employee Name, Country Name etc.).
As part of my project requirement, I have join those two views and get all the fields that exist in them.
When I am doing so, I am getting a weird error as shown below.
Error: [129]: transaction rolled back by an internal error: [129] transaction rolled back by an internal error: exception 141000274: exception 141000274:
TRexUtils/ParallelDispatcher.cpp:275
message not found; $message$='TSR HTKD JFSDFM'
Please check lines: 59,
Upon, researching further, I could see that the value 'TSR HTKD JFSDFM' is the value in text field of Employee Name.
I did try to increase the length of the field and change the data types but nothing has worked.
Could you please help me in getting this one resolved.
Thanks,
Raviteja

Hi,
I am exactly facing the same issue:
Error: [129]: transaction rolled back by an internal error: [129] transaction rolled back by an internal error: exception 141000274:
But i found a fix :-) .....
This may be a very late reply but it would help people who desperately searching for an answer for this issue.
I used CAST function .. The problem is, we are selecting data from table and of course we dont know the size of the data (attribute) @ runtime. We assign the length by looking at the table attr length or view op attr length. But what happens is the junk data which exceeds the limit of the allocated space hence we get this error.
So i used CAST function to truncate the excess junk values (may be spaces).
Example:
I have a ATTR view of date in the format YYYY-MM-DD which means 10 char size.
In my CALC view I have created date OP column of VARCHAR(10) but I get the above error for no reason. Eventhoug i am 100% sure about my ATTR date would be max of 10 char my CALC view is failing @ runtime.
So i did a CAST on date as CAST(my_date as varchar(10)) and the magic happend. It works .......
But you need to be careful in using this because if you use CAST you may lose data. Careful. In my case i dont.
Somebody from HANA team should look at this issue from SAP and solve this. I am sure it is a serious bug from HANA (eventhough i am using SAP HANA SP09 Rev 92 the most latest as of today !!!!!!!!!! )
Enjoy....
Thanks & Regards
Prakash K

Error -: AIP-50904: ReferTo message not found

Hi,
We have 3 windows system acting as TP's (TP1, TP2 and TP3).
When the message is fired from TP1, it reaches TP2 and TP2 sends back an acknowledgement to TP1.
But when the message is fired from TP3, the acknowledgement is being sent back to TP1 instead of TP3 and the error appearing in TP1 is "Error -: AIP-50904: ReferTo message not found".
The configuration on TP2 for TP1 and TP3 are as follows:-
1) The DUNS IDs of TP1 and TP3 are the same.
2) The Delivery channel names in TP1 and TP3 are different.
3) The transport server names are the same, but their IP addresses are different.
4) The agreement names are different, but their Agreement IDs are the same.
Can you please treat this issue on priority and look into it ASAP?
Regards,
Vishal
+919881737231

Hi Prasanna,
Thanks a lot for your reply.
The solution given by you worked.
But now iam getting different error at the TP2.
The ACk shows the status as complete but the request PO show error and it takes 20-30 min to process the ack.
The error it shows is as follows:-
rror -: AIP-50903: Message "AC1F755611E2AA4AEA80000017749090-1" retry count is zero
 at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:375)
 at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:325)
 at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:650)
 at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:474)
 at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:403)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2042)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2554)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2424)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2379)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
 at java.lang.Thread.run(Thread.java:534)
2008.12.12 at 15:31:23:938: Thread-16: B2B - (ERROR) Error -: AIP-50903: Message "AC1F755611E2AA4AEA80000017749090-1" retry count is zero
 at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:375)
 at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:325)
 at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:650)
 at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:474)
 at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:403)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2042)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2554)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2424)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2379)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
 at java.lang.Thread.run(Thread.java:534)
2008.12.12 at 15:31:23:938: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2008.12.12 at 15:31:23:938: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
2008.12.12 at 15:31:23:938: Thread-16: B2B - (DEBUG) Engine:notifyApp Enter
2008.12.12 at 15:31:23:938: Thread-16: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = null
2008.12.12 at 15:31:23:938: Thread-16: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>AC1F755611E2AA4AEA80000017749090-1</b2bMessageId>
<errorCode>AIP-50903</errorCode>
<errorText>Message "AC1F755611E2AA4AEA80000017749090-1" retry count is zero</errorText>
<errorDescription>
<![CDATA[Machine Info: (PUNIN1879164449)
Message "AC1F755611E2AA4AEA80000017749090-1" retry count is zero ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Can you please help me on this.
Regards,
Rakesh

Error 906 message not found on compiling form in forms builder

When compiling a form in forms builder 6i I get the message: error 906: message not found. No message file for product=plsql80 facility=PCM
What should I do?

Is your PLSQL80 environment variable set? - Should point to the PLSQL80 directory as well.
If this is the only missing error that you have I wouldn't worry about it. 906 just means that PL/SQL could not compile the program unit.

Crs_stat errors out with "message not found"

hi gurus
After patching patch 8705958, crs_stat errors out with "message not found" ,what could be the problem?
Thank you!

Never faced such issue...
please search on metalink or raise an SR with Oracle Support..
Cheers !
Rajesh

Anyone know why I got this Terminal Error? [ERROR] CPPathUtils.c:526 The device-file for this operating system, 'osx-12.1.0.xml', was not found.

Here is the full text:
[ERROR] <CPPathUtils.c:526> The device-file for this operating system, 'osx-12.1.0.xml', was not found. An attempt to revert to a previous revision of the OS device-file: 'osx-12.0.0.xml' has been made. Please file a Radar report with Apple, on the 'CoreProfile' component, version 'X'.
Appeared after 10.8.1 Friday update while troubleshooting USB/FW issues w/ Mountain Lion.

OK. To recap:
1. Open Terminal.app
2. Type at cursor:
cd /System/Library/PrivateFrameworks/CoreProfile.framework/Versions/A/Resources/De vices/
3. Press Return
4. Type at cursor:
ls
5. Press Return
6. Type at cursor:
sudo ln -s osx-12.0.0.xml osx-12.1.0.xml
7. Press Return
8. Enter password if asked
9. Done.
Can I then type ls again to verify the change?

SXMB_MONI : Error in Persistence Layer : XML Message Not Found

Similar Messages

Maybe you are looking for