Failed to acquire exclusive lock on client session ClientSession

HI all.
when I login the Portal as a MSS role,I want to see about the data of employee(about 20000 employee).
some page can't open succeed.The error:
500   Internal Server Error
  SAP NetWeaver Application Server 7.00/Java AS 7.00 
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_27 failed to acquire exclusive lock on client session ClientSession(id=(DSAPBPRD_DPP_01)ID2006199550DB11722229503911854949End_53412655). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_27, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_29), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/pb/PageBuilder).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.
    at java.lang.Throwable.<init>(Throwable.java:56)
    at com.sap.exception.BaseException.<init>(BaseException.java:145)
    at com.sap.tc.webdynpro.services.exceptions.WDException.<init>(WDException.java:61)
    at com.sap.tc.webdynpro.services.exceptions.WDException.<init>(WDException.java:54)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1511)
    ... 20 more
Edited by: cui joe on Jun 16, 2009 5:36 AM

HI,thanks very much.
Because our data is very huge,so some leader login the system will get the error.I check the st22,It realy found the error:
Time limit exceeded.
The program "SAPLRHDB" has exceeded the maximum permitted runtime without
interruption and has therefore been terminated.
If I should increase the system profile parameter "rdisp/max_wprun_time"?
Can else I should turn other parameter?

Similar Messages

  • Failed to acquire exclusive lock on client session - Webdynpro

    Anyone experience this below intermittent error on Webdynpro - e.g. Display Leave Summary functions ?  If user retry/revisit the same screen again. it will be working fine.
    Having some hard to to get thread dump at those short and intermittent moment.
    Any suggestions are welcome.
    Found this note below but doubt it will help at this moment.
    Web Dynpro error page, known error situations, error codes
    SAP Note Number: 1113811 
    NW/EP 7.0 SPS13
    #2#sap.com/pb/PageBuilder#com.sap.tc.webdynpro.services.session.LockException: Thread SAPEngine_Application_Thread[impl:3]_21 failed to acquire exclusive lock on client session ClientSession(id=(J2EE11441500)ID1662520351DB00529024001059157699End_1898143411). Existing locks: LockingManager(ThreadName:SAPEngine_Application_Thread[impl:3]_21, exclusive client session lock: ClientSessionLock(SAPEngine_Application_Thread[impl:3]_16), shared client session locks: ClientSessionSharedLockManager([]), app session locks: ApplicationSessionLockManager([]), current request: sap.com/pb/PageBuilder).Hint: Take a thread dump of the server node to find the blocking thread that causes the problem.
         at com.sap.tc.webdynpro.clientserver.session.ClientSession$LockingManager.lock(ClientSession.java:1511)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:233)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Hi,
    Check this,
    ESS SC Import Problem
    Thanks and Regards,
    gopal.sattiraju

  • Error : MDSConfig failed to acquire write lock??

    Hi,
    Changes that I know used to flow, don't flow anymore, and I was suspecting something was wrong with the changelog followup.
    I guess I was right, cause I see this in the meta-.xxx.log:
    MDSConfig failed to acquire write lock 'MDS_E_FAILED_TO_ACQUIRE_WRITE_LOCK' (80042212), wlock=(fe3f1c40), rlock
    =(fe3f1c10), readlocks=4, writelockstate=0
    No mention in the admin guide obvioiusly.
    Anyone knows what this might mean? The config is on a dedicated DS instance, and no errors found there.
    MDS = 5.0SP1
    DS = 5.1SP1
    Thanks,
    Wim

    i sometimes see such messages on startup
    normally they go away a few minutes later.
    another solution is to stop everything (meta directory processes, and the LDAP's containing the MV and the NetscapeRoot), then start only the LDAP's, wait a few minutes, start the join-engine,
    it seems some objects in the ldap still/already have a write lock on them (myabe from a previous connection), when the join-engine tries to write to them

  • What if we acquired a UoW with client session in JTS env?

    Dear all,
    According to the application developer guide, session 7.5.2.5 - Using a Unit of Work When No External Transaction Exists,
    ======
    When getActiveUnitOfWork returns a null Unit of Work, there is no existing external transaction. You must start a new external transaction.
    Do this either by starting an external transaction explicitly using the UserTransaction interface, or by acquiring a new Unit of Work using the acquireUnitOfWork method on the server session.
    ======
    What if the application acquire the UoW with client session instead?
    Thanks and regards,
    William

    William,
    Acquiring the UnitOfWork from a client session or Server session will accomplish the same thing.
    One thing I would caution you on is that if your application is using JTA then I typically avoid having TopLink ever start the transaction. In this scenario the transactions should always be started by a container managed method on an EJB or through a UserTransaction. TopLink starting a JTA transaction would be an atypical usage.
    Doug

  • Error: Acquire running lock failed: 256 with HA after upgr. to 2.1.5

    Hello,
    after upgrading the 2 servers in server pool from 2.1.2 to 2.1.5 using yum, all vms throw:
    Error: Acquire running lock failed: 256
    when trying to start them. HA-infrastructure-check works well from OVMM 2.1.2 (not upgraded yet) and if we disable HA for the server pool, the vms come up. Shared storage is on NFS
    We have the following in /var/log/xen/xend.log:
    [2009-06-26 14:52:21 2649] DEBUG (XendDomainInfo:87) XendDomainInfo.create(['vm', ['name', '470_vm215'], ['memory', '1024'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['uuid', '14205f6a-12cc-42da-a32e-06f30b6288d4'], ['bootloader', '/usr/bin/pygrub'], ['bootloader_args', '-q'], ['image', ['linux']], ['device', ['vbd', ['uname', 'file:/OVS/running_pool/470_vm215/system.img'], ['dev', 'sda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3E:32:CD:FC'], ['type', 'netfront']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['vncpasswd', 'XXXXXXXX'], ['vnclisten', '0.0.0.0'], ['type', 'vnc'], ['display', 'localhost:11.0'], ['xauthority', '/root/.Xauthority']]]])
    [2009-06-26 14:52:21 2649] ERROR (XendDomainInfo:452) VM start failed
    Traceback (most recent call last):
    File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 430, in start
    self.acquire_running_lock();
    File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2891, in acquire_running_lock
    raise XendError('Acquire running lock failed: %s' % status)
    XendError: Acquire running lock failed: 256
    [2009-06-26 14:52:21 2649] DEBUG (XendDomainInfo:1881) XendDomainInfo.destroy: domid=None
    [2009-06-26 14:52:21 2649] ERROR (XendDomainInfo:92) Domain construction failed
    Traceback (most recent call last):
    File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 90, in create
    vm.start()
    File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 430, in start
    self.acquire_running_lock();
    File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2891, in acquire_running_lock
    raise XendError('Acquire running lock failed: %s' % status)
    XendError: Acquire running lock failed: 256
    [2009-06-26 14:52:21 2649] DEBUG (XendDomainInfo:1881) XendDomainInfo.destroy: domid=None
    and in /var/log/xen/xend-debug.log:
    ha_set_dlm_lock ['14205f6a-12cc-42da-a32e-06f30b6288d4', '470_vm215'] =>
    failed: <Exception: create lock('/dlm/ovm/4205f6a12cc42daa32e06f30b6288d4') failed. <OSError: [Errno 26] Text file busy: '/dlm/ovm/4205f6a12cc42daa32e06f30b6288d4'>
    StackTrace:
    File "/opt/ovs-agent-2.2/OVSXHA.py", line 371, in ha_set_dlm_lock
    fd = os.open(lock_path, os.O_CREAT | os.O_NONBLOCK)
    >
    StackTrace:
    File "/opt/ovs-agent-2.2/OVSXHA.py", line 379, in ha_set_dlm_lock
    raise Exception("create lock('%s') failed. %s" % (lock_path, errmsg))
    Any ideas?
    Thanks, Olaf

    suk wrote:
    1. To delete the database, which database are you referring to? I'm referring to the ovs-agent database:
    1. Stop the agent: # /etc/init.d/ovs-agent stop 2. Delete the database: # rm -f /etc/ovs-agent/db 3. Start the agent: # /etc/init.d/ovs-agent start If you have Oracle VM Manager v2.1.5 (which you should have upgraded before your servers, btw), you can now try using the "Restore" option for the server pool. Click on the Server Pool in the manager and hit "Restore" -- this will send the configuration data back down to the agents in the pool. Alternatively, you may need to de-register the servers in your pool and re-register them.
    2. To re-imported the guests, how?In Oracle VM Manager -- if you recreate the pool, you have the option of "Importing" both VM Templates and VM Guests. Deleting the pool in the Manager does not delete your guests as long as you ensure that you DO NOT select "Remove Working Directories".

  • Error: Acquire running lock failed: 256

    Can anyone help me? I did everthing that documentation says,but can't start my Virtual Machine .The error below picks up
    Error: Acquire running lock failed: 256

    VM server and VM manager both on virtual box
    Oracle VM 3.1.1

  • Could not acquire a lock

    Hello,
    I'm trying to activate and smartform but every time I'm getting this dump:
    Error Text of the Database: "[ASE Error SQL12205]Could not acquire a lock
    within the specified wait period. SERVER level wait period=2400 seconds,
    spid=259, lock type=exclusive row, dbid=4, objid=1260735642, pageno=5821264,
    rowno=5. Aborting the transaction.#"
    I've checked the LWM and HWM, and this paramteres have default value 2147483647.

    I don't think the LWM an HWM values will be relevant to this situation.  It sounds like some other process is holding an incompatible lock on this row for a long time, and your client is choosing to time out rather than continue to block.
    Use a query against master..syslocks (or wade through the output of sp_lock) to look for such a process.
    -bret

  • IllegalStateException thread tries to release exclusive lock LockingManager

    Hello,
    I'm having this error,
    java.lang.IllegalStateException: Illegal state: thread tries to release exclusive lock on ApplicationSession which it hasn't acquired! Details: LockingManager(ThreadID:89, threadName: HTTP Worker @1298613650, session lock: null, current request: company.com.pe/wd_hrsolmovpil_v1/Wdhrsolmovpilv1)
    Any of my web dynpros, even the uwl doesn't work.
    This happened after I tried to deploy project. Everything was working fine, but now ... I have this. I've restarted the server, but nothing happens.
    Please, anyone knows how to solve this? Any ideas?
    Regards
    SU

    Hello,
    The problem was because the WAS has the parameter DefaultExpirationTime seted in -1 of all the Web Dynpros (sap.com/tcwddispwda). It only accepts positive values. I had to login through Telnet and execute the parameter,
    add webdynpro
    MANAGE_WD_APP_PROPS sap.com/tcwddispwda
    Thanks & Regards
    SU

  • Continuous messages *dtlArpTask: osapi_sem.c:1179 Failed to acquire ..

    Client have recently upgraded from 4402 WLC to 5508. They are now receiving a large number (100 000s a day) of warnings. Software Version is
    7.5.102.0
    2013-09-09 00:00:02 Local0.Warning 10.61.183.17 ausowlc1: *rmgrMain: Sep 09 00:00:02.769: #OSAPI-4-MUTEX_LOCK_FAILED: osapi_sem.c:1179 Failed to acquire a mutual exclusion object. invalid(NULL) pointer passed.
    I have found related bug CSCui55350/ CSCuh41790
    CSCui55350/ CSCuh41790
    Continuous messages *dtlArpTask: osapi_sem.c:1179 Failed to acquire ..
    Symptom:
    Continuous messages:
    -Traceback: 0x10c31374 0x10c8a6a4 0x10c9ea08 0x10c94748 0x10c402d8 0x12283850 0x122f634c
    *rmgrMain: Aug 08 09:49:21.902: #OSAPI-5-MUTEX_UNLOCK_FAILED: osapi_sem.c:1036 Failed to release a mutual exclusion object. invalid(NULL) pointer passed.
    -Traceback: 0x10c30d9c 0x10c8a7f4 0x10c9ecf8 0x10c95d4c 0x10c402d8 0x12283850 0x122f634c
    *rmgrMain: Aug 08 09:49:21.902: #OSAPI-4-MUTEX_LOCK_FAILED: osapi_sem.c:1179 Failed to acquire a mutual exclusion object. invalid(NULL) pointer... more
    Conditions:
    AP in flex mode, 7.5 in use
    Workaround:
    None
    Further Problem Description:
    Details:
    Known Affected Releases: (3)
    7.5(102.0) | 7.5(1.69) | 7.4(100.0)
    Known Fixed Releases: 0
    Release Pending
    Product: Cisco 5500 Series Wireless Controllers
    Status of this bug is fixed but known fixed releases are 0. Please advise if this software bug and/or hardware failure and what is best workaround ?
    Any help would be appreciated.

    Hi Michael,
    This error is seen due to a setting the dev team has disabled on the WLC and are expected to be fixed in 7.6. These messages are just cosmetic and have no impact.
    Workaround at this point is :
    These are warning messages displayed on the console. Instead of enabling warnings, errors can be enabled. So that it does not flood the console.
    Kunal

  • Shared lock vs exclusive lock

    Hello
    I have a question.
    If we have two scott sessions. I am updating a table EMP in session 1. It means it is exclusively locked.It cannot be used by session 2. Then can we use select command on table EMP in session 2.?? This command shoul not work according to me. But it is working.
    Reply me.
    Thanks in anticipation.

    984426 wrote:
    But in shared / exclusive lock, we have a property that we can't acquire shared lock on data if it is exclusively locked and vice versa. that means readers block writers and vice versa.
    E.g. if T1 is updating a row then how T2 can read that row? If T2 is reading then that is inconsistent data as it will pick the non-updated value of that row until T1 commits.
    Please explain.
    I am having doubts in this topic.
    ThanksYou need to check back again the basic concepts from the Concepts guide. Your understanding about the Oracle's working is completely wrong.
    In Oracle, the Transaction Isolation Level is set to Read Committed . This means any kind of inconsistent data is not possible to be read by you and for that data , Oracle would create for you a consistent image using the Undo Blocks in which the old image is going to be stored till the time that transaction is not over( and even after that too for some time with conditions apply) . So if T1 is updating a row, T2 can't lock the same row as it would be locked exclusively and the S1 (another select) would be seeing an old and consistent image of that change only as long as it's not committed. What you said doesn't and won't work ever in Oracle.
    Read the first link that's given to you already.
    Aman....

  • Exclusive locks on IFS tables

    We have a servlet application that accesses IFS 9.0.1.1 via the IFS API.
    We are having a problem where sessions are putting an exclusive lock on certain SYS_LOBnnnnnnnnn objects which (in turn) prevents other sessions from gaining an exclusive lock on the ODM_DOCUMENT table.
    Today, the following statement (issued by some IFS API call) was causing an exclusive lock which was never released:
    update odm_document set READBYOWNER := 1 where id = :2
    This statement put an exclusive lock on the SYS_LOB0000046893C00006$$ object and that lock was never released and we had to kill the session.
    Any guidance would be appreciated. Thanks.

    The mappings when run does acquire an exclusive lock on the target table and yes it does only when it is run in set based mode, this is absolutely true. If you run a mapping in set based mode and loading some data in millions it takes an exclusive lock on the target table. You can verify it by querying the v$lock table, or by using the session browser in any of SQL querying tools.
    The problem can be overcome by running in row based mode as suggested by you, but when data volume is huge I dont think the row based mode gives a satisfactory preformance.
    Anyways, thanks for all your suggestions. Lets see if I can find any other way out.

  • I have email on my phone as well as PC. Thunderbird gives me an error message most times when I want to get mail that acct is locked by another session.

    The full message is
    "Sending of password did not succeed. Mail server pop-server.roadrunner.com responded: [IN-USE] account is locked by another session or for maintenance, try again."
    Then I get
    "Login to server pop-server.roadrunner.com failed."
    When I enter the correct password as requested I get the same messages again.
    The email accounts are active, both through MyMail and the webserver site for Roadrunner.
    Any suggestions?
    This started after I started using MyMail app for Android. When I re-enter

    Turn off your phone. Then figure out how to keep it from causing problems.

  • GTT table getting Row Exclusive lock

    I have a procedure which loads a table which is used for reporting.
    Currently it is a single process which picks up most of the data after joining 2-3 big tables(around 70-80GB) and then loading the main table.
    The joins are on PI and also partitions are also being used. Then a lot of updates are done on the main table to update other columns which are being picked from different tables.
    As the processing is happening on huge amount of data(around 1M), so processing is taking a lot of time.
    This process is taking around 40-45 minutes.
    I am planning to use parallelism to run it in 75 sessions. So the initial big insert will be faster and later on all the updates will be done on smaller chunks which will benefit the performance.
    I planned to use GTT table so that i dont have to create 75 temp tables for each sessions.
    But while using GTT table(ON COMMIT DELETE ROWS) in parallel sessions, i am seeing that the GTT table is getting Row Exclusive lock and the time taken by overall process is increasing by lot.
    So i tested by using 75 temp tables. There i saw that the performance has increased by lots as assumed initially.
    Please let me know if there is any other way or how to remove the locks on GTT table.

    First you should question why you think you need 75 GTT.
    Also your question contains no useful information
    (no four digit version of Oracle, no OS, no number of processors) , this paragrah
    Currently it is a single process which picks up most of the data after joining 2-3 big tables(around 70-80GB) and then loading the main table.
    The joins are on PI and also partitions are also being used. Then a lot of updates are done on the main table to update other columns which are being picked from different tables.
    As the processing is happening on huge amount of data(around 1M), so processing is taking a lot of time.
    This process is taking around 40-45 minutes.tells nothing,
    so basically your questions boils down to
    - Hey I come from a sqlserver background (this is just an educated guess), how can I find a workaround to wreck Oracle to make it work like sqlserver.
    75 parallel sessions on say 4 to 8 processors is a very bad idea, as these sessions will be simple competing for resources.
    Also a row exclusive lock is just that: a row level lock. This isn't a problem, usually.
    Sybrand Bakker
    Senior Oracle DBA

  • PMON failed to acquire latch, see PMON dump

    Hi,
    Database alert log show the following errors.
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    PMON failed to acquire latch, see PMON dump
    During this time we excuting query,
    'exec sys.utl_recomp.recomp_parallel(8)' two session,
    One session hanged , another session running background,
    Kindly guide to us to find this issue
    Thanks and Regards
    Perumal Swamy.R

    Hi I have the same problem on a windows 2003 server, and in my alert log file there is that message :
    Wed Aug 10 11:20:40 2005
    kwqiclode: Error 1403 happened during loading of queue
    ORA-1403 encountered when generating server alert SMG-3503
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:21:43 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:22:46 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:23:49 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:24:49 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:25:52 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:26:55 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:27:55 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:28:58 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:29:40 2005
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:30:01 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:31:04 2005
    kwqiclode: Error 1403 happened during loading of queue
    ORA-1403 encountered when generating server alert SMG-3503
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:32:07 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    Wed Aug 10 11:33:10 2005
    kwqiclode: Error 1403 happened during loading of queue
    kwqiclode: Error 1403 happened during loading of queue
    and in my pmon trace file d:\syges\bdump\syges_pmon_240.trc there is the above message :
    *** 2005-08-09 19:27:50.312
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.343
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.359
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.375
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.390
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.406
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.421
    PMON unable to acquire latch 2f0b508 process allocation
    possible holder pid = 17 ospid=2216
    *** 2005-08-09 19:27:50.437
    PMON unable to acquire latch 2f0b508 process allocation
    *** 2005-08-09 19:27:50.453
    version on my database :
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Prod
    PL/SQL Release 10.1.0.4.0 - Production
    CORE 10.1.0.4.0 Production
    TNS for 32-bit Windows: Version 10.1.0.4.0 - Production
    NLSRTL Version 10.1.0.4.0 - Production

  • Loadjava hangs - exclusive lock on sys.javasnm$

    We upgraded from Oracle 9.2.0.4 to 9.2.0.5 (using export then import of the entire database) and have found that our user java classes that compiled fine in 9.2.0.4 aren't as lucky in 9.2.0.5. When we use "loadjava" to recompile the jar files, some compiles are successful and others hang. When we investigate the "hanging" ones we find an exclusive lock on sys.javasnm$. The only session doing a loadjava compile is mine. We kill the Oracle session, the exclusive lock goes away, we compile a few more jars successfully, then the "hanging" begins again. Can anyone explain what is going on? Thanks in advance.

    Solution - We were missing the DROP SYNONYM permission for the Oracle User we were importing the java code for. Once that was in place the locks were no longer an issue.

Maybe you are looking for