Record locked

Similar Questions

• How to warn the user of record locking?

  Hello
  I updated optmistic locking mode. Wil PESSIMIST not allow me to change the data if another user's lock top. So I changed an OPTIMIST.
  Is there a way Warn (do not deny) my user that another user changes the current record, during validation?
  
  Thank you
  Jose Tuttu

  Hello

  Use as below

          BindingContainer bindings = getBindings();
          OperationBinding operationBinding = bindings.getOperationBinding("Commit");
          Object result = operationBinding.execute();
          if (!operationBinding.getErrors().isEmpty()) {
              FacesMessage facesMessage = new FacesMessage(FacesMessage.SEVERITY_ERROR, "Save operation failed", "Save operation failed");
              FacesContext.getCurrentInstance().addMessage(null, facesMessage);
  
          } else {
              FacesMessage facesMessage = new FacesMessage(FacesMessage.SEVERITY_INFO, "Successfuly saved", "Successfuly saved");
              FacesContext.getCurrentInstance().addMessage(null, facesMessage);
  
          } 
  

• record lock after the backup

  Hi all
  I want to lock specific record no insert, update, and delete data, is it possible?
  
  
  Sarah

  you need not encode this in a trigger on the lock.
  If you ask a record to the database and change an element in the
  your block on lock trigger is executed and the record is locked automatically (it is by default).

  Just to test, you can create a non-basetable checkbox in your building, named «record_locked "with Y/N values.»
  When you check this box a statemend of lock_record:
  {code} begin
  If
  : your_block.record_locked = 'Y '.
  then
  lock_record;
  on the other
  forms_ddl ('restore'); --> This going to records all locked in the block and the shape of the hole...
  end if;
  end; {code}

  If you are able to lock individual records, BUT you cannot unlock the separate records.
  You must submit a restore and all locked records are to be released.
  It is therefore absurd to use this test in a multi-record block!

• Check if the recording is locked

  Hi, I was wondering just that if anyone would be able to tell me if there is a method to check if a specified record locked?
  
  Any guidance is welcome.
  
  Thank you.

  You can use SELECT... FOR UPDATE NOWAIT. and catch the ORA-00054 exception.

  DECLARE
    v_temp VARCHAR2(1);
  
    CURSOR c_get_rows_to_lock IS
    SELECT 'X'
      FROM YourTable
     WHERE some_pk = :YourBlock.some_pk
     FOR UPDATE NOWAIT;
  
  BEGIN
  
      IF :YourBlock.seq_no IS NOT NULL THEN
           OPEN c_get_rows_to_lock;
           FETCH c_get_rows_to_lock INTO v_temp;
           CLOSE c_get_rows_to_lock;
      END IF;
  
  EXCEPTION
      WHEN OTHERS THEN
       IF SQLCODE = '-54' THEN
         MESSAGE('Record currently in use');
       -- Otherwise, show the message code and message
       ELSE
          MESSAGE(SQLCODE||':'||SQLERRM);
       END IF;
  
  END;
  

  See also, at the end of the link below.

  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:2247028425532

  I hope that helps!

  Published by: 301800 on November 24, 2010 10:59

• Free application locked?

  Hi, is there a way to release an application locked from any user who got him forcefully? Or maybe, just who has the request open on their detailed request so that we can contact to tell them to close the request view in the meantime?

  I'm not aware of any other method that the definition of the scope of the query REQUEST_LOCK = 0.

  Not sure if the disconnection of the forced user can help to release the records locked by him.

  To view the person who locks the record simply add the 'Locked By' field to your customer form (right panel Info might be very appropriate for this).

• Total locking DB

  Could someone explain to me how the DB handles record locking when an aggregate function is called? For example:

  ...
  select count(*)
  into   v_count
  from   x;
  ...

  Is there a lock held on the table x for the duration of the transaction, so no lines can be inserted or deleted?

  Hello

  crottyan wrote:
  Could someone explain to me how the DB handles record locking when an aggregate function is called? For example:

  ...
  select count(*)
  into   v_count
  from   x;
  ...
  

  Is there a lock held on the table x for the duration of the transaction, so no lines can be inserted or deleted?

  No, a request in itself never prevents anyone from changing table. If the query uses an aggregate function is not change that.

  The output you get reflects the content of the table at the time you started the application. This is called the Coherence of reading , and this is a feature of Oracle since version 4.

  Published by: Frank Kulash on July 17, 2012 12:37
  You can use "SELECT... * FOR UPDATE *"If you really want to keep the other sessions of changing rows in your query, but the only reason for this is that if you can change yourself. " You cannot use aggregate and UPDATES all functions.

• Locking hard... Settings lock system wait?

  Hello! I sought an answer to my problems for the past two weeks, but I'm not able to find another that a type solution work around very manual so I am here!
  To stop the pager to jump to 3:00, so I can investigate matters, I hope that you geniuses will be able to help.
  
  
  I have a problem where a solution out-of-box is built to manage locks very badly.
  I don't have the source code, so I can't change the application.
  What happens is:
  
  (1) a user accesses the application and changes a record.
  The application crashes the record in the database and this line lock does not expire.
  
  (2) criticism of the process starts and creates another lock who waits indefinitely for record locked in 1 free.
  
  Use of tables of $ v I found that I can see the lock created in 1 and I see the lock created 2 waits for the lock 1.
  I built a process to contact the offending user ([email protected]), and also support page to address the issue because it will be very, very quickly lost productivity if the lock is not resolved. It is a very temporary solution, but is not the answer!
  
  The first lock to expire (I hope) maybe offering an ORA-return error to the application. I tried to kill the sid and it works too, but the application responds a bit funny. What about lock wait timeout values? It seems that they are session based so I can't edit the session that we have not the source code, or what I can? Anyone of you geniuses have ideas?

  Decklyn Dubs wrote:
  ^ Yes. Wish I had something to say. Instead, I have to 'bolt' logical to address deficiencies.
  The seller wants to hire me because I have all these small ingenious hacks to treat problems in enforcement XD works very well for us.

  Change sides, sign a contract, becoming a 3rd third party provider to them and then start all locking :)

• Cleaning StoredSortedMap, DeadlockException - without explicit locks asked

  I fill a temporary StoredSortedMap with data that could not hold in memory, iteration on it for report purposes, then throw this card. I want to permanently delete the database, it comes out - but that the operation of removeDatabase is hitting a DeadlockException, waiting for a lock held by the same thread:
  
  Caused by: com.sleepycat.je.DeadlockException: (I 3.3.87) lock has expired. Locker 3854386 - 1_btpool3-8_BasicLocker: waited for lock on the database = _jeNameMap LockAddr:20625165 = 2334291 type = WRITING grant WAIT_PROMOTION timeoutMillis = node = 5000 startTime = endTime 1254530088437 = 1254530093437
  Owners: [< LockInfo locker = "" 12116138 - 1_btpool3-8_BasicLocker "type ="READ"/ >, < LockInfo locker =" "3854386 - 1_btpool3-8_BasicLocker ' type = 'READ' / >]
  [Server:]
  Transaction 3854386 - 1_btpool3-8_BasicLocker has LockAddr:20625165 < LockInfo locker = "" 3854386 - 1_btpool3-8_BasicLocker "type ="READ"/ >"
  Transaction 3854386 - 1_btpool3-8_BasicLocker waiting for LockAddr:20625165
  
  I did not intentionally take something that would hold a lock. I guess that put magic cursor cache for transparent support iterator might be persistent, but:
  
  -J' I iterates over all entries in the map only once - and I would have liked to close properly at the end of
  
  -J' tried to ask an explicit iterator, then using StoredIterator.close ()-, but still have an impasse
  
  I also tried to make an explicit clear() on the StoredSortedMap before attempting to remove the underlying database - but still got the impasse.
  
  What could explain a persistent read lock and is it possible for me to delete that I can delete the database entirely?
  
  Thank you
  
  -Gordon @ AI
  
  Edited by: Gojomo October 2, 2009 17:52

  Hi Gordon,.

  Trying to remove a database will cause a deadlock if a database instance is still open, so you can probably fix this by closing the database first. What may be confusing, it is that this is not a record lock, is an internal lock on the database 'name '. We use it to ensure that an open database cannot be deleted, truncated or renamed. The BasicLocker named the tip of message on this problem too, so I think that's it.

  But if it does not help, please post the complete stack trace and I'll think again.

  -mark

• cleaner to lock timeout - when it needs to be increased?

  The 'Locks management' section in the documentation
  http://www.Oracle.com/technology/documentation/Berkeley-DB/je/TransactionGettingStarted/jelock.html in detail the conditions when the transaction timeouts must be increased. If the default lock time seems to be a problem in the application (and set the time-out to a reasonable value transaction solves the problem), would also be advisable to increase the cleaner lock wait timeout?
  
  Is the cleaner also on a real timer lock timeout?
  
  Thank you.

  Hi Bertold,

  By cleaner lock timeout, I guess you mean EnvironmentConfig.CLEANER_LOCK_TIMEOUT ("je.cleaner.lockTimeout").

  This config param is not relevant for the purposes of record locking. It is currently used only for the database handles locking, so it would only matter if you often called Environment.removeDatabase or truncateDatabase.

  -mark

• ORA-00060: Deadlock detected while you wait the cursor CLOSE resource

  Hello
  
  I am a new Member of this forum. I work with a problem that we have obtained a few weeks ago. It runs in the lot C Pro executable on 10 threads dealing with > 800 data accessed from more than one table. The error, such as reported was a package.function call.
  
  This is the error I encountered:
  process_item ~ G *, D * ~-60 ~ ORA-00060: Deadlock detected while you wait resources ~ PACKAGE ERROR = cursor CLOSE C_ * in the R package *. I * 7641
  
  The slider is a simple SELECT without Table or record locking.
  
  My questions are:
  * During the occurrence of this error, execution is already in the line of the CLOSE cursor or did the error has occurred between the OPEN and the CLOSE slider? There are several lines of code between the OPENING and CLOSING:
  -one who calls to a package.function that simply stores the values of parameter to a variable
  -another one that retrieves the cursor. The group that contains the values of the cursor is used only by a single function in the package
  
  * Is it possible for this CLOSE cursor cause a deadlock? What could have caused this?
  
  * From what I know, Oracle treats blocks by abandoning the blocking process, while others continue, but this impasse caused our program to hang. How is that possible? The origin of the impasse might be our Threading program? This is a rare event and has past that twice this year.
  
  Thank you
  RAF

  RAF Serrano wrote:
  I see, so it be that blocking has occurred before the CLOSE cursor or it occurred during CLOSING? The cause could be executable ProC

  first cause is NOT ProC

  or is it really an error in PL/SQL

  first cause is NOT PL/SQL.

  cause of ORA-00060 is DML (INSERT, UPDATE, or DELETE)

• Impossible to compile menudef_10g menu

  Hi friends,
  
  I downloaded menudef_10g menu but when I compile it he throws error
  
  during the compilation of the following procedure
  
  procedure enable_disable_regular_items is
  Start
  disable_item ('Query', 'Last_criteria');
  disable_item ('Query', 'Cancel');
  enable_item ('Action', 'Save');
  enable_item ('Action', 'Exit');
  enable_item ('Block', 'Previous');
  enable_item ('Block', 'Next');
  enable_item ('Record', 'Previous');
  enable_item ('Record', 'Next');
  enable_item ('Record', 'Scroll_up');
  enable_item ('Record', 'Scroll_down');
  enable_item ('Record', 'Insert');
  enable_item ('Record', 'Duplicate');
  enable_item ('Record', 'Lock');
  end;
  identifier "disable_item" must be declared.

  disable_item is deprecated it seems...

  You must use the FMA execution for this menu or use built-in SET_MENU_ITEM_PROPERTY

• Problem sending event with Classes

  I have a custom Timer class that displays an alert of inactivity after 3 minutes. The user can then choose 'Yes' if they're still edit a document or a "' if they are done. If they do not respond to 2 minutes of the alert it considers 'no '.
  
  A 'yes' refreshes the timer and closes the alert.
  A 'no' kicked out of the State of change in the component that is called from the timer.
  
  The logic of the timer works fine, but it doesn't seem to be sending the event to the element that so called by clicking 'no' (or is idle) does nothing. I feel I'm missing something really simple or just misunderstand the function of eventDispatcher. Advice please?
  
  Code Timer class:
  
  Timer/public class extends Sprite
  {
  private var threeMinuteTimer:Timer;
  private var twoMinuteTimer:Timer;
  
  public void LockTimer()
  {
  creates a new three Timer
  threeMinuteTimer = new Timer(1000, 180);
  twoMinuteTimer = new Timer(1000, 120);
  
  designates earphones for the period of integration and completion events
  threeMinuteTimer.addEventListener (TimerEvent.TIMER, __ontick__);
  threeMinuteTimer.addEventListener (TimerEvent.TIMER_COMPLETE, onTimerComplete);
  
  twoMinuteTimer.addEventListener (TimerEvent.TIMER, __ontick__);
  twoMinuteTimer.addEventListener (TimerEvent.TIMER_COMPLETE, onTimerCompleteB);
  
  starts the timer ticking
  threeMinuteTimer.start ();
  }
  
  public void refresh (): void {}
  Restart (threeMinuteTimer);
  twoMinuteTimer.reset ();
  }
  private void onTick(evt:TimerEvent):void {}
  
  private void onTimerComplete(evt:TimerEvent):void {}
  trace ("first timer");
  Alert.Show ("you've been idle for several minutes. You always edit this record? ","Inactivity Alert", Alert.YES |" Alert.NO, alertListener, null, null, Alert.YES);
  twoMinuteTimer.start ();
  }
  
  private void onTimerCompleteB(evt:TimerEvent):void {}
  trace ("second timer'");
  Alert.Show ("TIME of ', 'Inactivity alert', Alert.OK");
  dispatchEvent (new Event ("timeUp", true));
  }
  
  private void restart(tim:Timer):void {}
  Tim.Reset ();
  Tim.Start ();
  }
  
  
  private void alertListener(eventObj:CloseEvent):void {}
  Check if the YES button was pressed.
  If {(eventObj.detail is Alert.YES)
  Refresh();
  } else {}
  leave edit mode
  Alert.Show ("TIME of ', 'Inactivity alert', Alert.OK");
  dispatchEvent (new Event ("timeUp", true));
  }
  }
  }
  
  The component code:
  
  private var theTimer:LockTimer;
  private void initializeHandler(event:Event):void {}
  addEventListener ("timeUp", timeUpHandler);
  }
  private void timeUpHandler(event:Event):void {}
  Alert.Show ("TIME of ', 'Inactivity alert', Alert.OK");
  editDone();
  }

  So here's what I had to do to make this work:

  1. I had to fix the theTimer rather than the component listener
  2. I had to launch the manufacturer outside the service timer
  3. I had to call the Manager of the MXML component initialization function

  Here's the code revised (with excess cutting)

  
  http://www.Adobe.com/2006/mxml"width ="780"height ="515"liveDragging ="true"creationComplete =" initializeHandler () ">"
  ......
  ......
  ......
  
  Import mx.controls.Text;
  Import mx.rpc.events.FaultEvent;
  Import mx.rpc.events.ResultEvent;
  Import mx.controls.Alert;
  import classes. Timer;

  public static millisecondsPerMinute:int const = 1000 * 60;
  public static millisecondsPerHour:int const = 1000 * 60 * 60;
  public static millisecondsPerDay:int const = 1000 * 60 * 60 24;

  IMPORTANT! ////////////////
  private var theTimer:LockTimer = new LockTimer();
  private function initializeHandler (): void {}
  theTimer.addEventListener ("timeUp", timeUpHandler);
  }
  private void timeUpHandler(event:Event):void {}
  editDone();
  }

  private void refreshLock(theLock:int):void {}

  var theTime:Date = new Date();
  {if(theLock==1)}
  theTimer.refresh ();
  theTime.setTime (theTime.getTime () + (millisecondsPerMinute * 5));
  } else {if(theLock==0)
  theTime.setTime (theTime.getTime ());
  } else {}
  return;
  }
  Form1.request.firmlockedTime = String (theTime.valueOf ());
  Form1.request.firmisLocked = String (theLock);
  }

  private function editIt (): void {}
  see if it is edited
  {if (checkLock ())}
  If its being edited to send a message
  Alert.Show ("this disc is currently being edited by another user. Please try again later.', "Record locked", mx.controls.Alert.OK);
  } else {}
  theTimer.startMe ();
  refreshLock (1);
  Form1.send ();
  currentState = "AdminEdit;
  }
  }
  private function editDone (): void {}
  refreshLock (0);
  Form1.send ();
  currentState = "Admin";
  }

  ]]>
  
  ......
  ......
  ......
  

• Newspapers of vacuum/underutilized files not deleted

  I have an application that runs at the vacuum cleaner and checkpointer explicitly (instead of rely on the database to do so).
  Here's the relevant environment settings: je.env.runCheckpointer = false, je.env.runCleaner = false, je.cleaner.minUtilization = 5, je.cleaner.expunge = true.
  
  When you run the application, I noticed that a few dozen logs were removed, but later (even vacuuming was performed at regular intervals), no more logs were deleted.
  
  I have run the utility of DbSpace environmental and found the following result:
  
  Used execute% file size (KB)
  -------- --------- ------
  00000033 97656 0
  00000034 97655 0
  00000035 97656 0
  00000036 97656 0
  00000037 97656 0
  00000038 97655 2
  00000039 97656 0
  0000003a 97656 0
  0000003b 97655 0
  0000003c 97655 0
  97655 0000003d 0
  0000003E 97655 0
  97656 0000003F 0
  00000040 97655 0
  00000041 97656 0
  00000042 97656 0
  00000043 97656 0
  00000044 97655 0
  00000045 97655 0
  00000046 97656 0
  ...
  
  This continues for a long time. I got database monitoring activated at the level of the CONFIG. Here are the last lines of the newspaper, just before the last logfile (0x32) is deleted:
  
  2009-05-06 08:41:51:111:CDT INFO CleanerRun 49 file 0 x 30 starts back = 2
  2009-05-06 08:41:52:181:CDT SERIOUS CleanerRun 49 on file 0 x 30 invokedFromDaemon = false finished = true = false nEntriesRead = nINsObsolete 206347 fileDeleted = 6365 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 199971 = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:41:52:182:CDT INFO CleanerRun 50 on file 0 x 31 starts back = 1
  2009-05-06 08:41:53:223:CDT SERIOUS CleanerRun 50 on file 0 x 31 invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 205475 = 6319 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 199144 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:41:53:224:CDT INFO CleanerRun 51 file 0 x 32 starts back = 0
  2009-05-06 08:41:54:292:CDT SERIOUS CleanerRun 51 of file 0 x 32 invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 205197 = 6292 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 198893 = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:42:24:300:CDT INFO CleanerRun 52 file 0 x 33 starts back = 1
  2009-05-06 08:42:24:546:CDT CONFIG Checkpoint 963: source = api success = true nFullINFlushThisRun = 13 nDeltaINFlushThisRun = 0
  2009-05-06 08:42:24:931:CDT cleaner SEVERE deleted file 0 x 32
  2009-05-06 08:42:24:938:CDT cleaner SEVERE deleted file 0 x 31
  2009-05-06 08:42:24:946:CDT cleaner SEVERE deleted file 0 x 30
  
  Here are a few lines of newspaper just after the last log message with cleaner deletion (until the next control point):
  2009-05-06 08:42:25:339:CDT SERIOUS CleanerRun 52 on file 0 x 33 invokedFromDaemon = false finished = true = false nEntriesRead = nINsObsolete 204164 fileDeleted = 6277 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 197865 = 11 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 11 nLNQueueHits = 9 nLNsLocked = 0
  2009-05-06 08:42:25:340:CDT INFO CleanerRun 53 of file 0 x 34 starts back = 0
  2009-05-06 08:42:26:284:CDT SERIOUS CleanerRun 53 on file 0 x 34 invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 203386 = 6281 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 197091 = 2 nLNsDead = 2 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:42:56:290:CDT INFO CleanerRun 54 file 0 x 35 starts back = 4
  2009-05-06 08:42:57:252:CDT SERIOUS CleanerRun 54 on file 0 x 35 invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 205497 = 6312 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 199164 nLNsCleaned = 10 nLNsDead = 3 nLNsMigrated = 0 nLNsMarked = 7 nLNQueueHits = 6 nLNsLocked = 0
  2009-05-06 08:42:57:253:CDT INFO CleanerRun 55 on file 0 x 39 starts back = 4
  2009-05-06 08:42:58:097:CDT SERIOUS CleanerRun 55 on file 0 x 39 invokedFromDaemon finished = false = true = false nEntriesRead = nINsObsolete 204553 fileDeleted = 6301 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 198238 nLNsCleaned = 2 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 2 nLNQueueHits = 1 nLNsLocked = 0
  2009-05-06 08:42:58:098:CDT INFO CleanerRun 56 on file 0x3a starts back = 3
  2009-05-06 08:42:59:261:CDT SERIOUS CleanerRun 56 on file 0x3a invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 204867 = 6270 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 198586 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:42:59:262:CDT INFO CleanerRun 57 file 0 x 36 starts back = 2
  2009-05-06 08:43:02:185:CDT SERIOUS CleanerRun 57 on file 0 x 36 invokedFromDaemon finished = false = true fileDeleted = false nEntriesRead = nINsObsolete 206158 = 6359 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 199786 = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:43:02:186:CDT INFO CleanerRun 58 file 0 x 37 starts back = 2
  2009-05-06 08:43:03:243:CDT SERIOUS CleanerRun 58 on invokedFromDaemon file 0 x 37 = false finished = true = false nEntriesRead = nINsObsolete 206160 fileDeleted = 6331 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 199817 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:43:03:244:CDT INFO CleanerRun 59 0x3b file starts back = 1
  2009-05-06 08:43:04:000:CDT SERIOUS CleanerRun 59 on file 0x3b invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 206576 = 6385 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned 200179 = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:43:04:001:CDT INFO CleanerRun 60 on file 0 x 38 starts back = 0
  2009-05-06 08:43:08:180:CDT 0 x 38 invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 205460 = SERIOUS CleanerRun 60 on file 6324 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = nLNsCleaned = 194125 4999 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 4999
  2009-05-06 08:43:08:224:CDT INFO CleanerRun 61 on file 0x3c starts back = 0
  2009-05-06 08:43:09:099:CDT SERIOUS CleanerRun 61 on file 0x3c invokedFromDaemon = false finished = true fileDeleted = false nEntriesRead = nINsObsolete 206589 = 6343 nINsCleaned = 0 nINsDead = 0 nINsMigrated = 0 nLNsObsolete = 200235 nLNsCleaned = 0 nLNsDead = 0 nLNsMigrated = 0 nLNsMarked = 0 nLNQueueHits = 0 nLNsLocked = 0
  2009-05-06 08:43:24:548:CDT CONFIG Checkpoint 964: source = api success = true nFullINFlushThisRun = nDeltaINFlushThisRun-12 = 0
  
  I couldn't see something fundamentally different between the log messages when log files have been deleted, and when they were not. The DbSpace utility has confirmed that there are a lot of logs under minimum usage, so I can't explain everything so that deleting files of newspaper stopped all of a sudden.
  
  Any help would be appreciated (I version: 3.3.75).

  Hi Bertold,

  My first guess is that the one or more operations are accidentally not completed (committed or aborted) not the sliders closed.

  A clue is nLNsLocked = 4999 in the second series of trace messages. This means that 4999 records were locked by your application and do not have be migrated by vacuuming. Vacuuming will wait until these records locks are released before you remove the log files. Records locks are maintained by transactions and cursors.

  If is not ring a Bell, and you need to look further, one thing you can do is to print the EnvironmentStats periodically (System.out.println (Environment.getStats (null))). Take a look at the nPendingLNsProcessed and nPendingLNsLocked. The first is the number of records in the cleaner tries to migrate because they were locked earlier. This last is the number that are still blocked and cannot be migrated.

  -mark

• In the EIS, error in saving the metaoutline

  Hi all
  
  When Ii do any change in EIS Metaoutline and when I try to save, it throws ERROR as.
  
  "*" _The metaoutline OLAP is already locked Please use Save as or save at a later date. » *_
  
  How to unlock the metaoutline that has been locked?
  
  Thaks in advance
  Shiv

  In IST, go to "Connections" > "OLAP metadata catalog" > "remove locks...". "and select the metaoutline why you get the error and check"Read locks"and"Write locks", then click on 'OK '. This should remove the record locking of the relational database.

• Whenever I try to share a recording file it shows as locked.

  When I make a record with sound recorder and save the file, it is locked - I can't share it.  I can open it manually by right-clicking on the file and share it, but I wish that the default value should be set to share with everyone.  I can't find the right button to push... Thanks for any help!

  Original title: default sharing settings Sound Recordings

  Thanks for the reply.

  I did some additional checking and it seems that it is limited to the records.  I made a folder with paint and saved in the same folder that I'm having problems of locking with and it wasn't locked - I could access the homegroup from another computer.

  I think that I followed all the instructions of sharing that I found that have been proposed in the response e-mail, but nothing helps.

  Thank you once again.