Locked process

Hi,
Yesterday while importing the database, the import process hung up while inserting data into a large table table. On researching I found that archive log had been turned ON disks which resulted in the archive log disks running out of space. I turned OFF the archive log process, cleaned up the space and killed import process. Unfortunately since I killed the import session, Oracle is trying to rollback all the transactions that were being inserted. Even though I ran a COMMIT command (from a diiferent session) to commit all the transactions, internally it seems Oracle is still trying to flush them out of rollback segments. Even an 'Alter system kill session' wouldn't work. I guess this only marks for a session to be killed after the current process is completed internally. I researched into various Oracle forums and DBA manuals to find a way to end this process without causing any harm to the overall database. But based on what I read all indicators point that the current transaction had to end normally before any further import can be done.
Infact even a simple select statement from a smaller table gets hung up now. And I have to do this by logging in as 'connect internal' as the normal SQL session by using the userid and passwor[i]Long postings are being truncated to ~1 kB at this time.

How did you 'Turn off' archiving. If you did an ALTER SYSTEM ARCHIVE LOG STOP, Then you haven't shut off archiving, you have suspended automatic archiving, which is causing your problem. Do an ALTER SYSTEM ARCHIVE LOG START, then shutdown immediate. Do a STARTUP MOUNT then ALTER DATABASE NOARCHIVELOG;, then ALTER DATABASE OPEN;.
After this, you can do your import. After the import is complete, shutdown again then STARTUP MOUNT, ALTER DATABASE ARCHIVE LOG then ALTER DATABASE OPEN.

Similar Messages

  • Object Lock -- Process Chain --- How to Track

    Dear All...
    Working on SCM 4.1
    Daily we schedule the Process Chain , but sometime we get the Object Lock Error.
    To see this error we have to go to process chain-> Log , Steps-->right click , and display message...
    This is manual Process , and we cant keep track of many Process Chain Jobs >Steps>messages??
    Is there any process /way to Track /watch these types of Object Lock Errors automaticaly ??
    as it could reduce our manual activity??
    Thanks in advance..
    Rajesh patil

    HI Rajesh,
    You can get mail on abort of any step in Process chain.
    For that go to edit mode of existing process chain in RSPC. Right Click on Step (for which you need mail) and click on CREATE MESSAGE.
    Click on radio button "Error" so that when ever Error comes you will get mail.
    Hope this helps.
    Vishal..

  • WerFault.exe locks processes

    Hi.
    I have applications that crash very soon, we working on it... But there is another question.
    Windows exception handler WerFault.exe sometimes suspends crashed application for a long time and it totally locks. Even after sign out of user, suspended process remains. Windows Error Reporting Service disabled.
    Is there way to totally disable WerFault.exe?

    Hi Partner,
    Thank you for your post.
    From your description, I see that you want to know how to disable WerFault.exe.
    Please let me know if I have misunderstood anything.
    Based on my research, for current situation, we can take the following steps to disable WerFault.exe.
    1. Open Services console, select Windows Error Reporting Service.
    2. Double-click it with you mouse and select Disable as startup type.
    However, if we change startup type of the Windows Error Reporting Service to
    Disabled,  Windows Error Reporting begins to make problems. If we do so, and a program triggers WerFault.exe, the WerFault.exe Process won’t terminate until you kill it yourself using taskkill /IM werfault.exe or taskmanager.
    If we need to ensure that Werfault.exe will never be spawned when an unhandled exception is encountered, we can choose one of the following resolution paths.
    1) Create a software restriction policy (via local policy or Domain GPO) to disallow Werfault.exe for all users.
    Or
    2) Use Image File Executions Options to cause Werfault.exe to be executed under a non-existent debugger(NUL).  Since NUL can’t be found, the process fails to launch.
    (REG ADD “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\Werfault.exe” /v Debugger /t REG_SZ /d NUL /f)
    Hopefully the information is helpful.
    Please let me know if there is is any update. Thank you for your update.
    Best Regards,
    Sophia Sun
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • How do i determine what processes have a lock on a file?

    hi-
    i want to replicate the functionality of a program like:
    http://www.codeguru.com/Cpp/W-P/dll/article.php/c3641/
    in java, without having to use native code/JNI.
    the closest method i could find was:
    http://java.sun.com/j2se/1.5.0/docs/api/java/nio/channels/FileChannel.html#tryLock(long,%20long,%20boolean)
    however, FileChannel#tryLock doesn't identify what processes have a lock on the file.
    thanks,
    augusto.

    I don't think you can get hold of the locking process id using only Java.
    Kaj

  • Error while running the process chain

    Hi, I am getting following error while running the process chain.
    "Lock NOT set for: Deleting the data completely from a data target"
    Please suggest.
    amit

    hi,
    This is due to a lock on the objects which is being used by ur load.
    Even if master data used by this would be in a lock by an attribute change run. wait till that attribute change run finishes and then repeat.
    If this target itself is locked by someother process like rollup , compression , this error would appear. In this case also repeat the step after those locking process finish.
    some general locks during loading:
    Sometimes parallel processing in DTP might lead to this, its better set the DTP and infopackage in serial processing. In this case change the settings and then repeat the process.
    There is a specific case in which the Serial DTP gets locked by itself, in this case repeat it untill it succeeds.
    You can identify the above scenario as below. This is applicable only if the DTPs processing mode is serial.
    if u see in SM 37 this load would have three DTP processes running.
    it should have only two.
    In this case cancel the process and repeat it untill u get it right.
    hope this helps u
    regard,
    ranjith
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:44 AM
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:46 AM

  • Error while running FICO process chain

    Hi Experts,
    While monitoring the FICO related process chain.I got an error due to which the loading of the process chain stoped.
    The Error occured at DTP level and the displayed error messages are like this
    Aggregation Behaviour of InfoObjects Couldnot be read()
    Operation Could not be carried out for
    Exception xxxxxxxxxx locked.
    Can any one help me out of how to fix this problem
    Waiting for reply
    Thanks.
    Regards,
    Mohan

    hi,
    This is due to a lock on the objects which is being used by ur load.
    Even if master data used by this would be in a lock by an attribute change run. wait till that attribute change run finishes and then repeat.
    If this target itself is locked by someother process like rollup , compression , this error would appear. In this case also repeat the step after those locking process finish.
    some general locks during loading:
    Sometimes parallel processing in DTP might lead to this, its better set the DTP and infopackage in serial processing. In this case change the settings and then repeat the process.
    There is a specific case in which the Serial DTP gets locked by itself, in this case repeat it untill it succeeds.
    You can identify the above scenario as below. This is applicable only if the DTPs processing mode is serial.
    if u see in SM 37 this load would have three DTP processes running.
    it should have only two.
    In this case cancel the process and repeat it untill u get it right.
    hope this helps u
    regard,
    ranjith
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:44 AM
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:46 AM

  • User Status change problem in Process Order

    Hi,
    We are in process of upgrading our system from 4.6C to ECC 6.0. I have a problem with User status change for process Orders.
    In 4.6C we are using the profile x with settings:
    10     ZNEW     Created process order     10     90     1     1     ZSTA
    20     ZLCK     Locked process order     20     90     1     1     ZREV
    30     ZOPN     Reopened process order     20     90     1     1     ZOPN
    40     ZMST     MES order started     20     90     1     1     ZMST
    50     ZMCL     MES order closed     20     90     1     1     ZMCL
    90     ZTEC     Technically completed      20     90     1     1     ZTEC
    In ECC 6.0 we also use the same profile settings as above.
    The problem is in ECC 6.0 when I do a goods receipt the User status changes to ZTEC . The process followed is ..Create process order, Release Order, Goods issue, Phase partuial confirmations, Goods receipt and then Finla confirmations of phases. Now in 4.6C if i do the above process the User status remains at ZMST and it only changes to ZTEC when i technically complete the order but in ECC 6.0 when I do a goods recipt from above steps the User status changes to ZTEC. THis should not happen.
    Any pointers will be very helpful.

    Hi,
    The log for production order preliminiary costing is not saved. Therefore, once the order is saved, there is no log available anymore (this is by the way a question of PP; none of the logs is saved).
    Hope that helps...
    Regards,
    Declan

  • Error when locking period

    Hello Experts,
    I am trying to lock a period and I am receiving an error when I try. Error states "Cannot lock data because the validation account is not zero." I haven't had any issues with any other period except August. I noticed that there is country that would not lock. All the entities within that one country locked; however, at the parent and consolidated level, it would not. Please help if you can.
    Thanks!

    Hi,
    Please refer the below article that might help you ,
    "Cannot lock data because the validation account is not zero" when trying to lock a parent entity (Doc ID 1314837.1)
    Cause
    The cause was that there were calculated values in the <Parent Currency> Value member in the child entity. This is caused by rules, and previous periods may not have these calculated values. It is not possible to lock <Parent Currency> value member of the child entity if it is not zero in the validation account.
    When the <Entity Currency> value member of a parent entity is locked, the system also needs to lock the <Parent Currency> of the child entity in the same action. If the value of the validation account at <Parent Currency> level in the child entity is not zero, the user will not be allowed to lock the <Entity Currency> of the parent. If calculation or translation rules are writing values to this <Parent Currency> value member, they will need to be checked to ensure that this value remains zero.
    Solution:
    1) The calculation or translation rules will need to be adjusted so that numerical non-zero values are not generated in the <Parent Currency> value member of the child entity.
    2) Then the entity will be lockable at "translation" (Parent currency) value member level,
    3) If it can be locked at this level, then the parent entity will be able to be locked at <Entity Currency> level.
    4) After amending the rules, load the changed rules, and run some translations and consolidations and test the locking process again.
    Regards,
    Gunasekaran Rayar

  • How to lock a file in solaris

    Hi everyone,
    Is there a way to lock a file in Solaris ?
    Any input highly appreciated.
    Tx
    Kaushalya

    Of course. There is even a class for it. However, be forewarned, locks only work when everything "plays nice". If one program locks it, and another program doesn't bother to attempt locking it before doing something with it, it will be able to "pull the carpet out from under" the locking process.
    If you mean "lock" in the "Windoof" sense (in that absolutely nothing can do absolutely anything with a file when something else has it locked), no.

  • Help in locking

    can any body help me...I want some locking process.when I entered with some order no(AUFNR)..at the same time no one can enter at the same AUFNR.For this I have taken one ztable and first when we entered then that AUFNR I saved in ztable and at last I delete that AUFNR in ztable. But when I enterd in our report then AUFNR save in ztable and when I close that report with close button 'right top corner '(not back or exit) or in bottom tab rt click and close then our ztable entry is not deleted. pls give me any solution.
    Thanks
    Rakesh.

    hi,
    If you are updating the entries on to your ztable and wants to lock the table while updating the entries create a lock object for that table Via SE11->Lock Objects and use that FM's before and after updating the table i,.e, ENQUEUE_EZ_<ZTABLE> before updating and DEQUEUE_EZ_<ZTABLE> after updating the table ...
    Regards,
    Santosh

  • Oracle Processes

    How to see what are all the oracle backgroud processes running on the current database in unix/solaris.
    Like LGWR,PMON,SMON,ARC.
    I want to see all the processes that are running.
    Please tell the commands.
    Thanks
    Satnosh

    If you look at following sample, you can make yourself a good idea on how to proceed:
    TEST.SQL>-- Here we check V$BGPROCESS
    TEST.SQL>SELECT * FROM V$BGPROCESS;
    PADDR            NAME  DESCRIPTION                                                           ERROR
    C000000189711CF8 PMON  process cleanup                                                  ##########
    00               DIAG  diagnosibility process                                           ##########
    00               FMON  File Mapping Monitor Process                                     ##########
    00               LMON  global enqueue service monitor                                   ##########
    00               LMD0  global enqueue service daemon 0                                  ##########
    00               LMS0  global cache service process 0                                   ##########
    00               LMS1  global cache service process 1                                   ##########
    00               LMS2  global cache service process 2                                   ##########
    00               LMS3  global cache service process 3                                   ##########
    00               LMS4  global cache service process 4                                   ##########
    00               LMS5  global cache service process 5                                   ##########
    00               LMS6  global cache service process 6                                   ##########
    00               LMS7  global cache service process 7                                   ##########
    00               LMS8  global cache service process 8                                   ##########
    00               LMS9  global cache service process 9                                   ##########
    C000000189712218 DBW0  db writer process 0                                              ##########
    C000000189712C58 DBW1  db writer process 1                                              ##########
    C000000189712738 DBW2  db writer process 2                                              ##########
    C000000189713178 DBW3  db writer process 3                                              ##########
    00               DBW4  db writer process 4                                              ##########
    00               DBW5  db writer process 5                                              ##########
    00               DBW6  db writer process 6                                              ##########
    00               DBW7  db writer process 7                                              ##########
    00               DBW8  db writer process 8                                              ##########
    00               DBW9  db writer process 9                                              ##########
    00               DBWa  db writer process 10 (a)                                         ##########
    00               DBWb  db writer process 11 (b)                                         ##########
    00               DBWc  db writer process 12 (c)                                         ##########
    00               DBWd  db writer process 13 (d)                                         ##########
    00               DBWe  db writer process 14 (e)                                         ##########
    00               DBWf  db writer process 15 (f)                                         ##########
    00               DBWg  db writer process 16 (g)                                         ##########
    00               DBWh  db writer process 17 (h)                                         ##########
    00               DBWi  db writer process 18 (i)                                         ##########
    00               DBWj  db writer process 19 (j)                                         ##########
    C000000189714B18 ARC0  Archival Process 0                                               ##########
    C000000189715038 ARC1  Archival Process 1                                               ##########
    00               ARC2  Archival Process 2                                               ##########
    00               ARC3  Archival Process 3                                               ##########
    00               ARC4  Archival Process 4                                               ##########
    00               ARC5  Archival Process 5                                               ##########
    00               ARC6  Archival Process 6                                               ##########
    00               ARC7  Archival Process 7                                               ##########
    00               ARC8  Archival Process 8                                               ##########
    00               ARC9  Archival Process 9                                               ##########
    00               LNS0  Network Server 0                                                 ##########
    00               LNS1  Network Server 1                                                 ##########
    00               LNS2  Network Server 2                                                 ##########
    00               LNS3  Network Server 3                                                 ##########
    00               LNS4  Network Server 4                                                 ##########
    00               LNS5  Network Server 5                                                 ##########
    00               LNS6  Network Server 6                                                 ##########
    00               LNS7  Network Server 7                                                 ##########
    00               LNS8  Network Server 8                                                 ##########
    00               LNS9  Network Server 9                                                 ##########
    C000000189713698 LGWR  Redo etc.                                                        ##########
    00               LCK0  Lock Process 0                                                   ##########
    C000000189713BB8 CKPT  checkpoint                                                       ##########
    00               MRP0  Managed Standby Recovery                                         ##########
    00               LSP0  Logical Standby                                                  ##########
    00               LSP1  Dictionary build process for Logical Standby                     ##########
    C0000001897140D8 SMON  System Monitor Process                                           ##########
    C0000001897145F8 RECO  distributed recovery                                             ##########
    00               CJQ0  Job Queue Coordinator                                            ##########
    00               EMN0  Event Monitor Process 0                                          ##########
    00               QMN0  AQ Time Manager Process 0                                        ##########
    00               QMN1  AQ Time Manager Process 1                                        ##########
    00               QMN2  AQ Time Manager Process 2                                        ##########
    00               QMN3  AQ Time Manager Process 3                                        ##########
    00               QMN4  AQ Time Manager Process 4                                        ##########
    00               QMN5  AQ Time Manager Process 5                                        ##########
    00               QMN6  AQ Time Manager Process 6                                        ##########
    00               QMN7  AQ Time Manager Process 7                                        ##########
    00               QMN8  AQ Time Manager Process 8                                        ##########
    00               QMN9  AQ Time Manager Process 9                                        ##########
    00               DMON  DG Broker Monitor Process                                        ##########
    00               RSM0  DR Resource Manager Process                                      ##########
    00               NSV0  DR Server NetSlave Process 0                                     ##########
    78 rows selected.
    TEST.SQL>-- We can see soMe PADDR = 0. These are non running processes!
    TEST.SQL>-- Filterred:
    TEST.SQL>SELECT NAME, DESCRIPTION FROM V$BGPROCESS WHERE PADDR != '00';
    NAME  DESCRIPTION
    PMON  process cleanup
    DBW0  db writer process 0
    DBW1  db writer process 1
    DBW2  db writer process 2
    DBW3  db writer process 3
    ARC0  Archival Process 0
    ARC1  Archival Process 1
    LGWR  Redo etc.
    CKPT  checkpoint
    SMON  System Monitor Process
    RECO  distributed recovery
    11 rows selected.
    TEST.SQL>-- Then we must find a way to link to V$PROCESS... on the addr?
    TEST.SQL>DESC V$PROCESS
    Name                                                                                                  Null?    Type
    ADDR RAW(8)
    PID                                                                                                            NUMBER
    SPID                                                                                                           VARCHAR2(12)
    USERNAME                                                                                                       VARCHAR2(15)
    SERIAL#                                                                                                        NUMBER
    TERMINAL                                                                                                       VARCHAR2(30)
    PROGRAM                                                                                                        VARCHAR2(48)
    TRACEID                                                                                                        VARCHAR2(255)
    BACKGROUND                                                                                                     VARCHAR2(1)
    LATCHWAIT                                                                                                      VARCHAR2(16)
    LATCHSPIN                                                                                                      VARCHAR2(16)
    PGA_USED_MEM                                                                                                   NUMBER
    PGA_ALLOC_MEM                                                                                                  NUMBER
    PGA_FREEABLE_MEM                                                                                               NUMBER
    PGA_MAX_MEM                                                                                                    NUMBER
    TEST.SQL>SELECT BG?NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
    FRO  2  M V$BGPROCESS BG, V$PROCESS P
      3  WHERE BG.PADDR != '00'
      4  AND BG.PADDR = P.ADDR;
    SELECT BG?NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
    ERROR at line 1:
    ORA-00911: invalid character
    TEST.SQL>l1
      1* SELECT BG?NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
    TEST.SQL>c:?:.
      1* SELECT BG.NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
    TEST.SQL>/
    NAME  DESCRIPTION                                                             PID    SERIAL#
    PMON  process cleanup                                                           2          1
    DBW0  db writer process 0                                                       3          1
    DBW1  db writer process 1                                                       5          1
    DBW2  db writer process 2                                                       4          2
    DBW3  db writer process 3                                                       6          1
    ARC0  Archival Process 0                                                       11          1
    ARC1  Archival Process 1                                                       12          1
    LGWR  Redo etc.                                                                 7          1
    CKPT  checkpoint                                                                8          1
    SMON  System Monitor Process                                                    9          1
    RECO  distributed recovery                                                     10          1
    11 rows selected.
    TEST.SQL>-- But we want the O.S. pid.... this is known to be the V$PROCESS.SPID
    TEST.SQL>l
      1  SELECT BG.NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
      2  FROM V$BGPROCESS BG, V$PROCESS P
      3  WHERE BG.PADDR != '00'
      4* AND BG.PADDR = P.ADDR
    TEST.SQL>l1
      1* SELECT BG.NAME, BG.DESCRIPTION, P.PID, P.SERIAL#
    TEST.SQL>a , P.SPID
      1* SELECT BG.NAME, BG.DESCRIPTION, P.PID, P.SERIAL#, P.SPID
    TEST.SQL>/
    NAME  DESCRIPTION                                                             PID    SERIAL# SPID
    PMON  process cleanup                                                           2          1 22852
    DBW0  db writer process 0                                                       3          1 22930
    DBW1  db writer process 1                                                       5          1 23009
    DBW2  db writer process 2                                                       4          2 23099
    DBW3  db writer process 3                                                       6          1 23178
    ARC0  Archival Process 0                                                       11          1 23304
    ARC1  Archival Process 1                                                       12          1 23306
    LGWR  Redo etc.                                                                 7          1 23182
    CKPT  checkpoint                                                                8          1 23214
    SMON  System Monitor Process                                                    9          1 23281
    RECO  distributed recovery                                                     10          1 23302
    11 rows selected.
    TEST.SQL>-- We could also link to V$SESSION via V$PROCESS.ADDR -> V$SESSION.PADDR, etc...
    TEST.SQL>DESC V$SESSION
    Name                                                                                                  Null?    Type
    SADDR                                                                                                          RAW(8)
    SID                                                                                                            NUMBER
    SERIAL#                                                                                                        NUMBER
    AUDSID                                                                                                         NUMBER
    PADDR                                                                                                          RAW(8)
    USER#                                                                                                          NUMBER
    USERNAME                                                                                                       VARCHAR2(30)
    COMMAND                                                                                                        NUMBER
    OWNERID                                                                                                        NUMBER
    TADDR                                                                                                          VARCHAR2(16)
    LOCKWAIT                                                                                                       VARCHAR2(16)
    STATUS                                                                                                         VARCHAR2(8)
    SERVER                                                                                                         VARCHAR2(9)
    SCHEMA#                                                                                                        NUMBER
    SCHEMANAME                                                                                                     VARCHAR2(30)
    OSUSER                                                                                                         VARCHAR2(30)
    PROCESS                                                                                                        VARCHAR2(12)
    MACHINE                                                                                                        VARCHAR2(64)
    TERMINAL                                                                                                       VARCHAR2(30)
    PROGRAM                                                                                                        VARCHAR2(48)
    TYPE                                                                                                           VARCHAR2(10)
    SQL_ADDRESS                                                                                                    RAW(8)
    SQL_HASH_VALUE                                                                                                 NUMBER
    PREV_SQL_ADDR                                                                                                  RAW(8)
    PREV_HASH_VALUE                                                                                                NUMBER
    MODULE                                                                                                         VARCHAR2(48)
    MODULE_HASH                                                                                                    NUMBER
    ACTION                                                                                                         VARCHAR2(32)
    ACTION_HASH                                                                                                    NUMBER
    CLIENT_INFO                                                                                                    VARCHAR2(64)
    FIXED_TABLE_SEQUENCE                                                                                           NUMBER
    ROW_WAIT_OBJ#                                                                                                  NUMBER
    ROW_WAIT_FILE#                                                                                                 NUMBER
    ROW_WAIT_BLOCK#                                                                                                NUMBER
    ROW_WAIT_ROW#                                                                                                  NUMBER
    LOGON_TIME                                                                                                     DATE
    LAST_CALL_ET                                                                                                   NUMBER
    PDML_ENABLED                                                                                                   VARCHAR2(3)
    FAILOVER_TYPE                                                                                                  VARCHAR2(13)
    FAILOVER_METHOD                                                                                                VARCHAR2(10)
    FAILED_OVER                                                                                                    VARCHAR2(3)
    RESOURCE_CONSUMER_GROUP                                                                                        VARCHAR2(32)
    PDML_STATUS                                                                                                    VARCHAR2(8)
    PDDL_STATUS                                                                                                    VARCHAR2(8)
    PQ_STATUS                                                                                                      VARCHAR2(8)
    CURRENT_QUEUE_DURATION                                                                                         NUMBER
    CLIENT_IDENTIFIER                                                                                              VARCHAR2(64)HTH,
    Yoann.

  • Including a new Process Monitor Report

    Hi all
    I was wondering if by adding a new kind of report on the workbench under Process Monitor Reports (default reports are : Process Monitor, Process Monitor with Locks, Process Monitor All Categories, Process Status Period Range, Process Monitor Sorted by Location Hierarchy) I could modify the information showed by this "new report"
    For example currently if I generate the Process Monitor with Locks it will show every single location I have within my application, however I need this "new report" to show only some of those locations filtered by an attribute, I supposs the correct way to do this is to locate and modify the script being called by the adapter to publish this report. The problem is I can't find this so called script.
    Am I wrong and this publishing process is being done through an already compile library, a .dll ?? If this is the case is there anyway to override this call ??
    I hope I made my problem clear enough
    Thanks
    Edited by: HFMColUser on 26-ago-2011 15:41

    Hi,
    Login to FDQM (FDM) work bench client and click reports tab.
    Copy the report you want to modify and paste (I prefer to do this way, so we will not create any issues in the existing reports)
    change the report description.
    Right click on the report now. Clcik report definition properties, Click SQL tab on the top.
    Now add vpartcatpercartesian.partname like 'E%'. so you will get only locations starting with E in your report.
    Edited by: PadmajaV on Aug 27, 2011 3:15 AM

  • [SOLVED] xss-lock does not die on logout

    Hello,
    I am trying to find a workaround for the problem I mentioned here
    So far I have installed i3lock from the standard repository and xss-lock from the AUR. I disabled screen locking and screen blanking in Gnome. I added the following desktop files to both users ~/.config/autostart
    [Desktop Entry]
    Type=Application
    Exec=xss-lock -- 'xautolock -locknow'
    Hidden=false
    NoDisplay=false
    X-GNOME-Autostart-enabled=true
    Name[en_US]=SuspendLock
    Name=SuspendLock
    Comment[en_US]=AutoLock the screen before suspend
    Comment=AutoLock the screen before suspend
    [Desktop Entry]
    Type=Application
    Exec=xautolock -time 3 -locker 'i3lock -d -c 000000'
    Hidden=false
    NoDisplay=false
    X-GNOME-Autostart-enabled=true
    Name[en_US]=XautoLock
    Name=XautoLock
    Comment[en_US]=AutoLock the screen
    Comment=AutoLock the screen
    I also added a custom keyboard shortcut:
    xautolock -locknow
    with the accelerator set to Super+L
    So far, it seems like this will work fine. It seems to be working better than GDM locking. I have seen one problem thus far... If I log out of Gnome, xss-lock continues to run. If I log in again, I get a new xss-lock process. The original process continues to run and has one core at 100% load. If I log out again and log in again, I get yet another xss-lock process. This also runs at 100% load. This same phenomenon happens if I start the xss-lock from a terminal. xss-lock does not die on logout...
    Why does xss-lock not die on logout?
    Should I be using a systemd service file instead of xss-lock? I did try the service file, but it seems to work inconsistently because the DISPLAY variable continues to change.
    Any suggestions?
    Last edited by bnb2235 (2014-09-28 12:17:32)

    Hi bnb2235,
    I've seen the same behavior from xss-lock.  This is what I've done to set things up with i3 on my laptop:
    1) I don't use systemd and/or an autostart file for xss-lock
    2) I start xss-lock with the following line near the end of my i3 config file:
    exec --no-startup-id xss-lock -- i3lock -b -i /home/username/.config/i3/metal_grid_w_arch.png &
    3) My i3 nagbar looks like so in the i3 config file:
    # exit i3 (logs you out of your X session)
    bindsym $mod+Shift+e exec --no-startup-id "/usr/bin/paplay /usr/share/sounds/Feather/beep.wav && i3-nagbar -f pango:Arimo -t warning -m 'WHAT DO YOU WANT TO DO?:' -b 'Shutdown?' 'systemctl poweroff' -b 'Reboot?' 'systemctl reboot' -b 'Exit i3?' 'killall xss-lock && killall nm-applet && i3-msg exit'"
    So I explicitly kill xss-lock and nm-applet priot to i3 being exited. This has kept xss-lock from exhibiting the behavior you describe (as well as prevents coredumps from nm-applet when i3 exits).
    Last edited by halocaridina (2014-09-25 01:43:52)

  • Oracle VM aquire lock issues

    I have been trying to manage an Oracle VM environment (1 Master server, 3 VM servers) for several months. THe main issue we have is that every so often when we have to reboot a VM guest either when the guest is going down or coming up we will see the following error in the master server /var/log/ovs-agent/ovs_root.log file:
    "2011-06-08 22:28:44" ERROR=> OVSPolicyServer.execute_policy(): error. => errcode=00001, errmsg=CDS accquire lock /etc/ovs-agent/db/cluster.lock timeout. locker process is 14070
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSPolicyServer.py", line 38, in execute_policy
    pool_ha_enable = db_load("cluster", "pool_ha_enable", get=True)
    File "/opt/ovs-agent-2.3/OVSCDS.py", line 159, in db_load
    cds = CDS(db_name)
    File "/opt/ovs-agent-2.3/OVSCDS.py", line 119, in __init__
    raise CDSLockTimeout(ERR_CDS_LOCK_TIMOUT, {
    The only way to get the VM guest to come back online is to shutdown all other VM guests running on the assigned VM server, reboot the VM server, then try again.
    I have tried many different avenues to get a resolution:
    1. Enabled the server pool/vm servers/vmguests to have HA. This was a disaster because every time the aforementioned error occurred the Master server would be affected and bring down the entire environment.
    2. Rebuilt the Oracle VM DB (remove all files in /etc/ovs-agent/db/ and restart/add servers to server pool)
    3. Disable HA and rebuild DB again.
    Still these errors occur and is really causing many customer issues with constant maintenance reboots. Has anyone seen this and discovered a solution?

    Hi,
    is your storage repository on NFS?
    And do you expirence short neworkt outage on the NFS storage maybe, before this error occurs?
    You can try with the following workaround:
    Stop all OVS-Agents: /etc/init.d/ovs-agent stop --disable-nowayout
    Delete the locks on the master: rm /OVS/.ovs-agent/db/*.lock
    Start all OVS_Agents: /etc/init.d/ovs-agent start
    Regards
    Sebastian
    Edited by: ssolbach on Jun 9, 2011 6:06 AM

  • Light-locker core dumps

    Per this suggestion to uninstall xscreensaver and install light-locker, I decided to give this a whirl using the latest xfce4 packages.  I find light-locker core dumping when I try to use it.  Anyone else?
    % light-locker
    process 1737: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1340.
    This is normally a bug in some application using the D-Bus library.
    D-Bus not built with -rdynamic so unable to print a backtrace
    [1] 1737 abort (core dumped) light-locker
    EDIT: this has nothing to do with the xfce4 packages in [testing].  I get the same error using 4.10 from [extra].
    EDIT2: https://bugs.archlinux.org/task/44085
    Last edited by graysky (2015-03-07 16:22:41)

    I installed this and tried it on 2 separate laptops for you and got the same error on both.  One has testing and community testing repository enabled and the other doesn't but exactly the same error on both.  Newbie to linux but hope that helps.

Maybe you are looking for