PANIC: fatal region error detected

i encoutered this error for stress testing.
in the project, we used the transaction and cursor. when the application is runing for a long time, i will receive the err about "PANIC: fatal region error detected". i change the max numbers of transaction, the same error also occurs. when this error occurs, the application can't create any transaction and open any cursor.
somebody can solve this problem? any suggestion appreciated.
thanks

This error should only occur after some message is sent to the error stream (configured with DB_ENV->set_errfile). Can you please post that output?
What operation causes the error (is it during open, or on some read/write)?
Have you tried looking at the output from running "db_stat -e" to see whether some resource is being exhausted?
Are multiple processes (including the Berkeley DB utilities) accessing the environment when the error occurs? Is it possible that any of those processes are using a different version of Berkeley DB than your application?
Regards,
Michael Cahill, Oracle Berkeley DB.

Similar Messages

Help with Error: PANIC: fatal region error detected; run recovery

Here's what I'm trying to do:
I am trying to us BDBXML in a webapp using tomcat 5.5. I have a class that is responsible for opening and closing the db. This class is accessed by a servlet for some AJAX RCP stuff and it also serves as an access point for a Web Service (Apache Axis). This class looks like this:
public class DG implements Serializable {
private javax.xml.datatype.DatatypeFactory datatypeFactory;
private Environment environment;
private EnvironmentConfig environmentConf;
private XmlContainer xmlContainer = null;
private XmlManager xmlManager = null;
private XmlManagerConfig xmlManagerConfig;
public DG() {
try {
File envHome = new File("C:\\bdbxml\\database");
environmentConf = new EnvironmentConfig();
environmentConf.setAllowCreate(true);
environmentConf.setInitializeCache(true);
environmentConf.setInitializeLocking(true);
environmentConf.setInitializeLogging(true);
environmentConf.setRunRecovery(true);
environmentConf.setTransactional(true);
environmentConf.setLockDetectMode(LockDetectMode.MINWRITE);
     //tried the following with default and 10000
     environmentConf.setMaxLockers(100000);
environmentConf.setMaxLockObjects(100000);
environmentConf.setMaxLocks(100000);
environmentConf.setTxnMaxActive(100000);
environment = new Environment(envHome, environmentConf);
CheckpointConfig cpc = new CheckpointConfig();
cpc.setKBytes(500);
environment.checkpoint(cpc);
xmlManagerConfig = new XmlManagerConfig();
xmlManagerConfig.setAdoptEnvironment(true);
xmlManager = new XmlManager(environment, xmlManagerConfig);
XmlContainerConfig xmlContainerConfig = new XmlContainerConfig();
xmlContainerConfig.setIndexNodes(true);
xmlContainerConfig.setTransactional(true);
xmlContainerConfig.setNodeContainer(true);
xmlContainer = xmlManager.openContainer("container.dbxml", xmlContainerConfig);
xmlContainer.sync();
datatypeFactory = javax.xml.datatype.DatatypeFactory.newInstance();
} catch (FileNotFoundException e) {
     e.printStackTrace();
} catch (DatabaseException e) {
     e.printStackTrace();
} catch (DatatypeConfigurationException e) {
     e.printStackTrace();
public void close() {
try {
if (xmlContainer != null) {
xmlContainer.close();
if (xmlManager != null) {
xmlManager.close();
} catch (DatabaseException e) {
e.printStackTrace();
public String getDocument(String docId) {
try {
XmlDocument doc = xmlContainer.getDocument(docId);
String docString = doc.getContentAsString();
doc.delete();
return docString;
} catch (XmlException e) {
e.printStackTrace();
public Result[] search(Search search) {
try {
     //normally I construct the query string using the Search object
StringBuffer q = new StringBuffer("subsequence(collection('container.dbxml')/metadata[contains(./idinfo//title, 'Ecology')], 1,10)");
XmlQueryContext xqc = xmlManager.createQueryContext();
XmlQueryExpression xqe = xmlManager.prepare(q.toString(), xqc);
XmlResults xr = xqe.execute(xqc);
int i = 0;
Vector<Result> vec = new Vector<Result>();
while (xr.hasNext()) {
XmlValue xv = xr.next();
XmlDocument xd = xv.asDocument();
Result r = new Result();
r.setMetadata(xd.getContentAsString());
r.setDocumentId(xd.getName());
XmlValue groupVal = new XmlValue(XmlValue.STRING);
xd.getMetaData("", "group", groupVal);
r.setGroup(groupVal.asString());
XmlValue ownerVal = new XmlValue(XmlValue.STRING);
xd.getMetaData("", "owner", ownerVal);
r.setOwner(ownerVal.asString());
XmlValue createdVal = new XmlValue(XmlValue.DATE_TIME);
xd.getMetaData("", "created", createdVal);
r.setCreated(createdVal.asString());
XmlValue updatedVal = new XmlValue(XmlValue.DATE_TIME);
xd.getMetaData("", "updated", updatedVal);
r.setModified(updatedVal.asString());
r.setPosition(search.getStartPosition() + i);
updatedVal.delete();
createdVal.delete();
ownerVal.delete();
groupVal.delete();
xd.delete();
xv.delete();
vec.add(r);
i++;
xr.delete();
xqe.delete();
xqc.delete();
return vec.toArray(new Result[vec.size()]);
} catch (XmlException e) {
e.printStackTrace();
// PLUS SOME OTHER METHODS, BUT USING ONLY THESE TO TEST
The Servlet looks like this:
public class DGServlet extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet {
private DG dg;
private final XPathFactory xpf = XPathFactory.newInstance();
private final XPath xp = xpf.newXPath();
private final SimpleDateFormat df = new SimpleDateFormat("EEE MMM d HH:mm:ss z yyyy");
public DGServlet() {
super();
@Override
public void destroy() {
try {
dg.close();
} catch (Exception e) {
log(e.getMessage());
e.printStackTrace();
super.destroy();
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
String action = request.getParameter("action");
if (action != null && !action.equals("")) {
if (action.equals("search")) {
response.setContentType("text/xml");
Result[] result = null;
try {
result = dg.search(constructSearch(request));
} catch (Exception e1) {
log(e1.getMessage());
e1.printStackTrace();
if (result==null || result.length==0) {
response.getWriter().print("0");
return;
StringBuffer sb = new StringBuffer("<results>");
for (int i = 0; result != null && i < result.length; i++) {
try {
sb.append("<result"
+ " title='"
+ xp.evaluate("/metadata/idinfo//title", new InputSource(new StringReader(result[i]
.getMetadata()))));
sb.append("' northbc='"
+ xp.evaluate("//northbc", new InputSource(new StringReader(result.getMetadata())))
+ "' southbc='"
+ xp.evaluate("//southbc", new InputSource(new StringReader(result[i].getMetadata())))
+ "' eastbc='"
+ xp.evaluate("//eastbc", new InputSource(new StringReader(result[i].getMetadata())))
+ "' westbc='"
+ xp.evaluate("//westbc", new InputSource(new StringReader(result[i].getMetadata())))
+ "' docid='" + result[i].getDocumentId() + "' group='" + result[i].getGroup()
+ "' owner='" + result[i].getOwner() + "' position='" + result[i].getPosition()
+ "' modified='" + result[i].getModified() + "' created='" + result[i].getCreated()
+ "'>");
NodeList nodes = (NodeList) xp.evaluate("//digform", new InputSource(new StringReader(result[i]
.getMetadata())), XPathConstants.NODESET);
for (int j = 0; j < nodes.getLength(); j++) {
sb.append("<resource download='"
+ StringEscapeUtils.escapeXml(xp.evaluate("//networkr", new InputSource(
new StringReader(XMLUtil.printDOMTree(nodes.item(j)))))));
sb.append("' format='"
+ StringEscapeUtils.escapeXml(xp.evaluate("//formname", new InputSource(
new StringReader(XMLUtil.printDOMTree(nodes.item(j)))))));
sb.append("'></resource>");
sb.append("</result>");
} catch (XPathExpressionException e) {
e.printStackTrace();
log(e.getMessage());
} catch (TransformerConfigurationException e) {
e.printStackTrace();
log(e.getMessage());
} catch (TransformerFactoryConfigurationError e) {
e.printStackTrace();
log(e.getMessage());
} catch (TransformerException e) {
e.printStackTrace();
log(e.getMessage());
sb.append("</results>");
response.getWriter().print(sb.toString());
else if (action.equals("details")) {
response.setContentType("text/html");
String str = "";
try {
str = dg.getDocument(request.getParameter("docId"));
response.getWriter().print(
setTranslatePage(str, new java.net.URL(
"http://localhost:8080/datastream/stylesheets/fgdc/fgdc_classic.xsl")));
} catch (Exception e) {
e.printStackTrace();
log(e.getMessage());
public void init() throws ServletException {
super.init();
dg = new DG();
It seems to work fine for a while, but then I get errors like the following:
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
com.sleepycat.dbxml.XmlException: Error: DB_RUNRECOVERY: Fatal error, run database recovery, errcode = DATABASE_ERROR
at com.sleepycat.dbxml.dbxml_javaJNI.XmlManager_prepare__SWIG_0(Native Method)
at com.sleepycat.dbxml.XmlManager.prepare(XmlManager.java:586)
at edu.washington.cev.datastream.api.DG.search(DG.java:935)
at edu.washington.cev.datastream.servlets.DGServlet.doGet(DGServlet.java:83)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:619)
I've set this up on a Window XP machine using tomcat 5.5 and java 5 as well as a Redhat Linux machine with tomcat 5.5 and java 5. I'm using the Web Service point for other servers to access the database. Everything starts up and runs for a little while, but I can't seem to pin down what causes the errors. I've run recovery multiple times as well as started new databases. Any help is appreciated.

There's a bug in your use of DB XML somewhere. Are you committing or aborting every transaction that you start, and calling delete() explicitly on all the DB XML objects that you use?
Those errors mean your database has become corrupted somehow.
John

Db_verify: PANIC: fatal region error detected; run recovery

We have an application that is using bdb. On one of the instances it frequently hits a panic condition. db_verify reports the following:
# db_verify -o file.db
db_verify: PANIC: fatal region error detected; run recovery
db_verify -VSleepycat Software: Berkeley DB 4.3.29: (June 16, 2006)
Quitting the application and removing the __db.001 file will allow a clean restart. How do I debug where this problem might be coming from?
thanks,
kevin

Hi Kevin,
user11964780 wrote:
# db_verify -o file.db
db_verify: PANIC: fatal region error detected; run recoveryThis is a generic error message that means the region files are corrupted. This is most often a problem in the application.
user11964780 wrote:
How do I debug where this problem might be coming from?Reference Guide - Chapter 24: [ Debugging Applications|http://www.oracle.com/technology/documentation/berkeley-db/db/programmer_reference/debug.html]
Bogdan Coman

PANIC: fatal region error detected; run recovery - How Can I resolve it?

PANIC: fatal region error detected; run recovery
Error loading files into container null.dbxml
Message: DB_RUNRECOVERY: Fatal error, run database recovery
com.sleepycat.db.RunRecoveryException: DB_RUNRECOVERY: Fatal error, run database recovery: DB_RUNRECOVERY: Fatal error, run database recovery
     at com.sleepycat.db.internal.db_javaJNI.DbEnv_open(Native Method)
     at com.sleepycat.db.internal.DbEnv.open(DbEnv.java:240)
     at com.sleepycat.db.EnvironmentConfig.openEnvironment(EnvironmentConfig.java:714)
     at com.sleepycat.db.Environment.<init>(Environment.java:30)
     at dbxml.gettingStarted.CopyOfexampleLoadContainer.createEnv(CopyOfexampleLoadContainer.java:144)
     at dbxml.gettingStarted.CopyOfexampleLoadContainer.loadXmlFiles(CopyOfexampleLoadContainer.java:157)
     at dbxml.gettingStarted.CopyOfexampleLoadContainer.main(CopyOfexampleLoadContainer.java:78)
     at dbxml.gettingStarted.Imagem.actionPerformed(Imagem.java:174)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
     at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
     at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1778)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

You will need to know about recovery. I suggest you read up on it in the Berkeley DB reference guide:
http://www.oracle.com/technology/documentation/berkeley-db/xml/ref/transapp/put.html
http://www.oracle.com/technology/documentation/berkeley-db/xml/ref/transapp/recovery.html
John

How can I localize the alert "error: PANIC: fatal region error detected..."

My application may corrupt and the operations therefore may fail and post the alert "error: PANIC: fatal region error detected; run recovery ...", and this alert is directly printed in the main process's window.
My question is how can I do to localize this alert in my thread which just deals with the Berkeley DB database?
Thanks

Hi,
You can configure an error callback function. See the run-time error configuration section of the Reference Guide here:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/debug/runtime.html
It sounds like DB_ENV->set_errcall is what you want:
http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_errcall.html
Regards,
Alex Gorrod, Oracle

Problem sqlite+berkeley PANIC: fatal region error detected.

Excuse for my English and if this wrong place to explain the problem
I'm checking to replace Berkeley DB and SQLite for testing the stability against involuntary interruptions of program I have encountered the following error:
Berkeley DB trust in knowing his rnedimiento and stability with Subversion, but I doubt the API bridge SQLITE
I'm testing the Berkeley DB database using the API Berkeley DB SQLITE and I did a small test program:;
/* Open database. */
sqlite3 *db;
sqlite3_open("data/basedatos.db", &db);
sqlite3_exec(db,"CREATE TABLE [test] ([key] INTEGER, [dat] varchar(64), PRIMARY KEY ([key]))",NULL,0,NULL);
err_code = SQLITE_BUSY;
while (err_code != SQLITE_OK ) {
     sqlite3_exec( db, "delete from test", NULL, 0, NULL );
     err_code = sqlite3_errcode( db );
sqlite3_exec( db, "BEGIN", NULL, 0, NULL );+
for( int i=0; i<_numCartones; i++ ) {
     char buf[1024];
     sprintf_s( buf, sizeof(buf), "insert into test( key, dat) values ( %d, 'test%d' )", i, i );
     sqlite3_exec( db, buf, NULL, 0, NULL );
sqlite3_exec( db, "COMMIT", NULL, 0, NULL );
sqlite3_close(db);I launched the program and insert about 150000 records in 17 seconds. Perfect!
I created a file basedatos.db and basedatos.db-journal subdirectory with files: log.0000000016, __db.001, __db.002, __db.003, __db.004, __db.005, __db.006 and __db.register.
Open it and prove the usefulness dbsql
c: dbsql basedatos.db
select count(*) from test;
150000          ← Ok.
Without closing the program again dbsql run the test program and this will get stuck in the call:
sqlite3_exec( db, "delete from test", NULL, 0, NULL );I close dbsql and automatically releases the "delete from" and the test program again inserted 150,000 records
While this by inserting 150,000 records run it again
c: dbsql basedatos.db
select count(*) from test; [WAIT]
and select count (*) remains locked until you finish the test program, normal thing locks.Once you finish the select TEST responds to 150,000
150000          ← Ok.Without closing the program again dbsql run the test program and this will get stuck in the call:
sqlite3_exec( db, "delete from test", NULL, 0, NULL );I close dbsql and automatically releases the "delete from" and the test program again inserted 150,000 records
while inserting test rerun:
c: dbsql basedatos.db
select count(*) from test;
Error: database disk image is malformed
and in my test program : PANIC: fatal region error detected; run recovery.
Reviewing the files are only: badatos.db, log.0000000031, log.0000000032, log.0000000033, log.0000000034, log.0000000035, log.0000000036, __db.register.
and __db*.* files?

Had accidentally opened the program dbsql.exe while doing speed tests data insertion.
While in a shell to make a select count (*) and I realized that was blocked waiting for the COMMIT release, normal thing in a process BEGIN / COMMIT.
In one test was corrupt database which reduced the test software and simplify the test to repeat the problem.
Today I repeated the test and the situation has changed
1) Run test (all OK, inserted in 18 seconds 150000 entries)
2) DBSQL run and I make a select count (*) (All Ok)
3) DBSQL unsealed test run and stay lock on DELETE FROM
4) DELETE FROM I close DBSQL and not released as yesterday.Repeat several times and I have the same behavior
Move in the test code from "delete from..." begin and commit
sqlite3_exec( db, "BEGIN", NULL, 0, NULL );
err_code = sqlite3_errcode( db );
err_code = SQLITE_BUSY;
while (err_code != SQLITE_OK ) {
sqlite3_exec( db, "delete from test", NULL, 0, NULL );
err_code = sqlite3_errcode( db );
for( int i=0; i<_numCartones; i++ ) {Repeat tests
1)Test run, everything ok in 25 seconds. While inserting test this, I run realizao dbsql and a select count (*) and remains lock until test ends. Everything ok, 150000 records
2)Dbsql unsealed test run it again and stay lock on delete until you close the program dbsql.
3)I close dbsql and releasing the lock of seconds to delete the test the error "PANIC ..." like yesterdayRepeat several times and the behavior is the same, except that no desparencen db files.
If I can not run dbsql test run multiple times without problems.
Could be the problem dbsql and simultaneous access to the database?
I'm going to migrate an application in production since SQLITE to Berkeley DB for testing.
I have confidence in the performance of Berkeley DB and I know the proper functioning it does with subversion, but the subversion server on a server is protected with uninterrupted power.
If I avoid using dbsql while the test software that I have that theoretical security operation will be correct when using Berkeley DB SQLITE layer and especially with unexpected off the machine?
Thanks again for your help

Berkeley db fatal region error detected run recovery

Hi,
I have initiated d Berkeley DB object.
Then, I am using multithreading to put data into the DB.
Here is how I open the one data handler.
ret = dbp->open(dbp, /* Pointer to the database */
NULL, /* Txn pointer */
db_file_name, /* File name */
db_logical_name , /* Logical db name (unneeded) */
DB_BTREE, /* Database type (using btree) */
DB_CREATE, /* Open flags */
0644); /* File mode. Using defaults */
each threads would put data into the same handler when it needs to.
I am getting "berkeley db fatal region error detected run recovery".
What is the problem? Does it have anything to do with the way the handler is created or whether multiple threads can put data into the DB?
jb

Hi jb,
user8712854 wrote:
I am getting "berkeley db fatal region error detected run recovery".This is a generic Berkeley DB panic message that means something went wrong. When do you get this error? Did you enable the verbose error messages? Are there any other warning/error messages reported? By just posting the way you open the database doesn't help much at all. I reviewed the other questions you asked on the forum, and it seems that you are not following the advices and consult the documentation, but you prefer to open new threads. I advice you to first work on configuring Berkeley DB for your needs and read the following pages in order to understand which Berkeley DB Product best suits your application and how it should be configured for a multithreaded application:
[The Berkeley DB products|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/intro/products.html]
[Concurrent Data Store introduction|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/intro.html]
[Multithreaded applications|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/program/mt.html]
[Berkeley DB handles|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/program/scope.html]
On the other hand, if the code that's calling the Berkeley DB APIs is not too big and is not private, you can post it here so we can review it for you and let you know what's wrong with it.
The procedures you should follow in order to fix a "run recovery" error are described here:
[Recovery procedures|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/recovery.html]
Thanks,
Bogdan Coman

Fatal region error detected; run Recovery

I try include 2600 documents 1,06 GB and I have the message (Fatal region error detected; run Recovery ). I executed db_recover.exe to try resolve the problem without sucess. I did this test in 3 differents computers and I had the same problem. I am use a free version , I am studyng berkeley db xml and need test performance with a big collection of document xml. Why am I have problem if berkeley db xml is able to support terabyte in size.

This message indicates that you are probably setting your Berkeley DB cache size too large. MapViewOfFile is the Windows API used to map the cache file. It will fail if Windows cannot find enough contiguous VM for the mapping.
Regards,
George
I have about 30 documents ~10MB and I get this all
the time.
MapViewOfFile: Not enough storage is available to
process this command.
PANIC: Not enough space
com.sleepycat.db.RunRecoveryException:
DB_RUNRECOVERY: Fatal error, run database recovery:
DB_RUNRECOVERY: Fatal error, run database recovery
at
t
com.sleepycat.db.internal.db_javaJNI.DbEnv_open(Native
Method)
at
t
com.sleepycat.db.internal.DbEnv.open(DbEnv.java:262)
at
t
com.sleepycat.db.EnvironmentConfig.openEnvironment(Env
ironmentConfig.java:908)
at
t
com.sleepycat.db.Environment.<init>(Environment.java:3
0
This is under WinXP with BDXML 2.3.10.

929-Fatal MCA Error detected CPU 0

We have a Z420 that will not boot. It returns: 929-Fatal MCA error.CB0/LLC0 error detected CPU 0Memory hierachy error The Manual has no suggested fix. Any Ideas? Thanks!

This could either be a memory failure (try reseating it, moving it to a different slot, or removing or replacing the memory), or a possible CPU failure. (The system is reporting a CPU machine check error, but it could be caused by memory issues). Go into Computer Management, then click on Event Viewer, Windows Logs, and System. Are there any WHEA warnings listed under Source? An easier way to find them is to Filter Current Log, and select Critical, Warning, Verbose, and Error to filter out the (many) Information entries. If the memory is OK, reseating the CPU might help, but this can be tricky. The CPU socket pins are very easily bent during the removal or install process, and extrememly difficult or impossible to repair if damaged. Also, when the CPU heatsink is removed, clean off the thermal paste on both the CPU and heatsink, and use new paste. The paste hardens, and does not give good thermal conductivity if the heatsinks is removed and the paste is not replaced. The CPU operating temperature can increase by 10 deg. C or more. FYI. If the system is under warranty, contact HP so they can fix it.

PANIC: fatal region detected, run recovery

Hello
I have a 20GB database file which I just created by adding around 10,000+ XML documents having the same schema.
I wrote a Python script which traverses thru my directory for XML files and inserts it. It works fine till 1000s of document and then suddenly the process dies. I dont kill it or anything.
Anyway, after that I try to query the database using:
query 'collection("smt.dbxml")/benchmark[@logic= "QF_IDL"]'
and the only thing I get is the above error.
I think I get something more in the beginningbut the number of errors are so much that my terminals window is full and I cant see the first line of message. No logs seems to be created too too.
I run db_recovery on the same path as the DBXML database and all I get is:
[rnadhani@craig exthd]$ /usr/local/dbxml/bin/db_recover -c -v -h .
Finding last valid log LSN: file: 1 offset 28
The DBFILE is created on an external 250GB USB disk formatted using ext3.
What might be the problem? Where can I get logs so I can give you more info.

How many files actually get inserted? It looks like recovery works so you can look at the container. Is the error always in the same place (same number of files)?
Is your environment on the same file system as the container?
If you create a transacted container, the putDocument() call will automatically create a transaction for you if you don't pass it one, so you are using transactions. It doesn't really matter if you create/use your own. I suspect you'll have the same problem, but I don't yet know what that is.
Regards,
George

Mail Panics every Friday morning with Region error

Every Friday morning around 8:00, Mail dies with the following error and I have to reboot the server. Could someone tell me why this happens?
PANIC: fatal region error detected; run recovery

Bryan Kennedy wrote:
Every Friday morning around 8:00, Mail dies with the following error and I have to reboot the server. Could someone tell me why this happens?
PANIC: fatal region error detected; run recovery
sounds like your mail db is hosed. get a copy of mailbfr at http://downloads.topicdesk.com/mailbfr/mailbfr-1.0.6.pkg.tar.gz
first i would backup everything to another drive.
I always have mail stores not on the primary OS drive, so you can swap out the OS when it gets funky,
run repair/reconstrcut db on your system.( using mailbfr ) gui tools don't work. their for looking.

Uncorrectable error detected by pci0... during DVMA read transaction

hi people... at first, sorry for my english. I hava a Sun Fire 280R with Solaris 8 and today it boot aparently without a reason, it boot 5 or 6 times. The error before the fall is:
WARNING: Uncorrectable error detected by pci0 (safari id 00000000.00000008) during DVMA read transaction
panic[cpu0]/thread = 2a10001fd20: Fatal PCI UE Error
syncing file systems... 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 done (not all i/o completed)
dumping to /dev/dsk/c1t0d0s1, offset 429588480
I can not make a backup and sometimes I can not logon because it cause the boot. I have reading something of this error and I have puting the machine in diagnostic mode:
auto-boot? = false
diag-device = disk
diag-level = max
diag-switch? = true
After this, power-off and after this I have igniting the machine... I have almost one hour waiting and no notice... the screen continue black :-(
Can somebody help me?
THANKS! Ceci.

Ceci,
First off, <font color="firebrick">WRONG FORUM</font>.
This forum is for discussions of the <u>Live Upgrade procedure</u> of installing Solaris.
Period.
Having said that...
Diagnostic mode sends all console output to the TTYa port.
You will never see the diag results on your monitor.
Particularly for such a system as a 280R that was
never intended to run with a graphics card and keyboard/mouse.
Set up a TIP session and start the diag boot all over again.
Capture all the output to a file
You appear to have a hardware issue.
We can only guess what the real root cause might be
(third party adapter card? Solaris not patched?)
You would get the best guidance and analysis if you open a service case with Sun techsupport.
These forums are user-to-user discussions. This is NOT Sun techsupport.

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

Cat c6509 E with Supervisor vs-s720-10g reload and Cache error detected!

Can you help me Cat c6509-E reload
connect console I see :
Initializing ATA monitor library...
Self extracting the image... [OK]
Self decompressing the image : ############################# [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXI1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Sat 28-Mar-09 10:48 by prod_rel_team
Image text-base: 0x40101328, data-base: 0x421FFA10
Cache error detected!
CPO_ECC (reg 26/0): 0x000000B6
CPO_CACHERI (reg 27/0): 0x84000000
CP0_CAUSE (reg 13/0): 0x00004800
Real cache error detected. System will be halted.
Error: Primary data cache, fields: , 1st dword
Actual physical addr 0x00000000,
virtual address is imprecise.
Imprecise Data Parity Error
Imprecise Data Parity Error
22:12:30 UTC Tue Mar 24 2015: Interrupt exception, CPU signal 20, PC = 0x413EB310
Possible software fault. Upon reccurence, please collect
crashinfo, "show tech" and contact Cisco Technical Support.
-Traceback= 414EDA90
$0 : 00000000, AT : 42510000, v0 : 00000000, v1 : 00000001
a0 : 43757CC4, a1 : 00040110, a2 : 45762ECE, a3 : 00000000
t0 : 44997CF0, t1 : 00000000, t2 : D5303A40, t3 : 00003A40
t4 : 0000004F, t5 : 0000005F, t6 : 68C8F600, t7 : 00000000
s0 : BEDA4010, s1 : 00000000, s2 : 00000000, s3 : 44086D60
s4 : 45762ECC, s5 : 00000001, s6 : 00000080, s7 : 44080000
t8 : 45762ECC, t9 : 00000000, k0 : 841E6970, k1 : 02951800
gp : 4250FC60, sp : 44997D48, s8 : 4499848E, ra : 413EB310
EPC : 414EDA90, ErrorEPC : 413EB310, SREG : 3400F105
MDLO : 00159DC0, MDHI : 00000000, BadVaddr : 00000000
DATA_START : 0x421FFA10
Cause 00004800 (Code 0x0): Interrupt exception
File bootflash:crashinfo_20150324-221230 Device Error :No such device
%Software-forced reload
22:12:30 UTC Tue Mar 24 2015: Breakpoint exception, CPU signal 23, PC = 0x4171F5E0
Possible software fault. Upon reccurence, please collect
crashinfo, "show tech" and contact Cisco Technical Support.
-Traceback= 4171F5E0 4171D184 40F4F26C 40F4F450 40F4F670 4171282C
$0 : 00000000, AT : 42510000, v0 : 441D0000, v1 : 424C0000
a0 : 00000000, a1 : 00008100, a2 : 00000000, a3 : 00000000
t0 : 0000FF00, t1 : 3401FF01, t2 : 41712918, t3 : FFFF00FF
t4 : 41712918, t5 : 73206265, t6 : 65746563, t7 : 20546865
s0 : 00000000, s1 : 424C0000, s2 : 00000000, s3 : 08000000
s4 : 42380000, s5 : 42380000, s6 : 41D90000, s7 : 00000001
t8 : 506D5CC4, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 4250FC60, sp : 50012420, s8 : 41D90000, ra : 4171D184
EPC : 4171F5E0, ErrorEPC : 413EB310, SREG : 3401FF03
MDLO : 00000000, MDHI : 00000003, BadVaddr : 00000000
DATA_START : 0x421FFA10
Cause 00000024 (Code 0x9): Breakpoint exception
=== Flushing messages (22:12:30 UTC Tue Mar 24 2015) ===
Buffered messages:
Queued messages:
*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
Firmware compiled 19-Feb-09 20:18 by weizhan Build [100]
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Error address Lo=0x4010
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Error address Hi=0x1EDA
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Interrupt Hi reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: Interrupt lo reg=0x8000000
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-DUMP: System controller Global Registers Dump
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: global hazard reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: soft reset cfg reg=0x10FFFF
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: global cfg reg=0x20
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: init status reg=0x8
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl cfg reg=0xE
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: prio map cfg reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ecc error log reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: parity error log reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: jtag idcode reg=0x5013102F
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: work status reg hi=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: work status reg lo=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc rxstat reg=0x11FE
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc txstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: eobc mac cfg reg=0xE24
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: inbound rxstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: inbound txstat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: io int stat reg=0x408
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: pcmcia cfg reg=0x1A0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: pcmcia stat reg=0x3C
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: bist go stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: bist done stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 0=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 1=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: ibl debug reg 2=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: obl debug reg 0=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: obl debug reg 1=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: rxq debug reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: txq debug reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: gigmac cfg reg=0x1001
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-INFO1: gigmac stat reg=0x0
*Mar 24 22:12:30.667: %SYSTEM_CONTROLLER-3-FATAL: An unrecoverable error has been detected. The system is being reset.
*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
*Mar 24 22:12:30.695: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
*Mar 24 22:12:30.695: %OIR-6-CONSOLE: Changing console ownership to switch processor
*** System received a Cache Parity Exception ***
signal= 0x14, code= 0x84000000, context= 0x441ce024
PC = 0x4171295c, Cause = 0x820, Status Reg = 0x34018002
System Bootstrap, Version 8.5(3)
Copyright (c) 1994-2008 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
Autoboot: failed, BOOT string is empty
Autoboot executing command: "boot "

Hello Abubaker,
It crashed due to a parity error.
Imprecise Data Parity Error
Imprecise Data Parity Error
Which in other words means, a temporary error in memory. On single occurence adivice is to monitor the supervisor for re-occurence of such failure again. You can monitor it for 24 - 48 hours and if its a hard failure , the likelyhood of issue coming again is more and you need to replace supervisor. If it does not repeat you can consider this as a one time issue and contnue using it.
Hope this helps and please always rate useful posts.
Thanks,
Madhu

ORA-01280: Fatal LogMiner Error in DBA_CAPTURE.

I setup a downstream real time apply replication with oracle instructions. It works fine for a few days. I changed the mount point (file system) of the database files and redo log files for source database, with a regular shutdown and startup. After that, I got error message at DBA_CAPTURE of downstream database:
ORA-01280: Fatal LogMiner Error
And corresponding error in alert log file:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [242], [37], [16], [], [], []
Thu Apr 2 00:39:02 2009
TLCR process death detected. Shutting down TLCR
Thu Apr 2 00:39:04 2009
Streams CAPTURE C001 with pid=35, OS id=21145 stopped
Thu Apr 2 00:39:04 2009
Errors in file /oracle/admin/hcarp/bdump/hcarp_c001_21145.trc:
ORA-01280: Fatal LogMiner Error.
I am not sure if the source db reboot can cause this. I will appreciate if anybody can let me know
1. What cause of this?
2. How to prevent this from happening?
3. What to do to recover/fix?
====================================
Here is major part of the trace file /oracle/admin/hcarp/bdump/hcarp_c001_21145.trc:
(source DB: DXP1P. Downstream DB: HCARP)
Unix process pid: 21145, image: oracle@fx1db01 (C001)
*** 2009-03-25 17:56:58.472
*** SERVICE NAME:(SYS$USERS) 2009-03-25 17:56:58.453
*** SESSION ID:(413.68) 2009-03-25 17:56:58.453
*** 2009-04-02 00:39:02.554
knlc.c:2619: KRVX_CHECK_ERROR retval 205
*** 2009-04-02 00:39:02.566
Begin knlcDumpCapCtx:*******************************************
Error 1280 : ORA-01280: Fatal LogMiner Error.
Capture Name: REAL_TIME_CAPTURE : Instantiation#: 1
*** 2009-04-02 00:39:02.566
++++ Begin KNST dump for Sid: 413 Serial#: 68
Init Time: 03/25/2009 17:55:35
++++Begin KNSTCAP dump for : REAL_TIME_CAPTURE
Capture#: 1 Logminer_Id: 1 State: CAPTURING CHANGES [ 04/02/2009 00:38:59]
Capture_Message_Number: 0x0003.8ae9479a [15215445914]
Capture_Message_Create_Time: 04/02/2009 00:32:46
Enqueue_Message_Number: 0x0003.8ae27ad3 [15215000275]
Enqueue_Message_Create_Time: 01/01/1988 00:00:00
Total_Messages_Captured: 116442
Total_Messages_Created: 118344 [ 04/02/2009 00:38:59]
Total_Messages_Enqueued: 1457 [ 03/27/2009 12:33:08]
Total_Full_Evaluations: 471
Elapsed_Capture_Time: 55956708 Elapsed_Rule_Time: 17
Elapsed_Enqueue_Time: 141 Elapsed_Lcr_Time: 864
Elapsed_Redo_Wait_Time: 6937736 Elapsed_Pause_Time: 0
++++End KNSTCAP dump
++++ End KNST DUMP
+++ Begin DBA_CAPTURE dump for: REAL_TIME_CAPTURE
Capture_Type: DOWNSTREAM
Version: 10.2.0.4.0
Source_Database: DXP1P
Use_Database_Link: YES
Logminer_Id: 1 Logfile_Assignment: IMPLICIT
Status: ENABLED
First_Scn: 0x0003.8adf5aa5 [15214795429]
Start_Scn: 0x0003.8adf5aa5 [15214795429]
Captured_Scn: 0x0003.8ae8f942 [15215425858]
Applied_Scn: 0x0003.8ae8f942 [15215425858]
Last_Enqueued_Scn: 0x0003.8ae27ad3 [15215000275]
Capture_User: STRMADMIN
Queue: STRMADMIN.STREAMS_QUEUE
Rule_Set_Name[+]: "STRMADMIN"."RULESET$_11"
Checkpoint_Retention_Time: 60
+++ End DBA_CAPTURE dump
+++ Begin DBA_CAPTURE_PARAMETERS dump for: REAL_TIME_CAPTURE
PARALLELISM = 1 Set_by_User: NO
STARTUP_SECONDS = 0 Set_by_User: NO
TRACE_LEVEL = 0 Set_by_User: NO
TIME_LIMIT = -1 Set_by_User: NO
MESSAGE_LIMIT = -1 Set_by_User: NO
MAXIMUM_SCN = 0xffff.ffffffff [281474976710655] Set_by_User: NO
WRITE_ALERT_LOG = TRUE Set_by_User: NO
DISABLE_ON_LIMIT = FALSE Set_by_User: NO
DOWNSTREAM_REAL_TIME_MINE = TRUE Set_by_User: YES
+++ End DBA_CAPTURE_PARAMETERS dump
+++ Begin DBA_CAPTURE_EXTRA_ATTRIBUTES dump for: REAL_TIME_CAPTURE
+++ End DBA_CAPTURE_EXTRA_ATTRIBUTES dump
++ LogMiner Session Dump Begin::
SessionId: 1 SessionName: REAL_TIME_CAPTURE
Start SCN: 0x0000.00000000 [0]
End SCN: 0x0000.00000000 [0]
Processed SCN: 0x0003.8ae947a7 [15215445927]
Prepared SCN: 0x0003.8ae94897 [15215446167]
Read SCN: 0x0003.8ae948b1 [15215446193]
Spill SCN: 0x0000.00000000 [0]
Resume SCN: 0x0000.00000000 [0]
Branch SCN: 0x0000.00000000 [0]
Branch Time: 01/01/1988 00:00:00
ResetLog SCN: 0x0003.8a502ab3 [15205411507]
ResetLog Time: 03/06/2009 23:58:56
DB ID: 1669710455 Global DB Name: DXP1P
krvxvtm: Enabled threads: 1
Current Thread Id: 1, Thread State 0x02
Current Log Seqn: 243, Current Thrd Scn: 0x0003.8ae948b1 [15215446193]
Current Session State: 0x0, Current LM Compat: 0xa200400
Flags: 0x3fa102d0, Real Time Apply is On
+++ Additional Capture Information:
Capture Flags: 325
Logminer Start SCN: 0x0003.8adf5aa5 [15214795429]
Enqueue Filter SCN: 0x0003.8adf5aa5 [15214795429]
Low SCN: 0x0003.8ae9479a [15215445914]
Capture From Date: 01/01/1988 00:00:00
Capture To Date: 01/01/1988 00:00:00
Restart Capture Flag: NO
Ping Pending: YES
Buffered Txn Count: 0
-- Xid Hash entry --
-- LOB Hash entry --
-- No TRIM LCR --
Unsupported Reason: 14
--- LCR Dump not possible ---
End knlcDumpCapCtx:*********************************************
*** 2009-04-02 00:39:02.569
error 1280 in STREAMS process
ORA-01280: Fatal LogMiner Error.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01280: Fatal LogMiner Error.
=====================================================
Thanks!

Look up Bug 6022014 at metlink.

PANIC: fatal region error detected

Similar Messages

Maybe you are looking for