Database Error 54
Business WarehouseWhere is this place located?All Places Data Warehousing SAP Business Warehouse 7 Replies Latest reply: Jun 5, 2014 8:58 AM by Yves KERVADEC Tweet System Log Database error 54 at EXE sunil kumar Jul 26, 2011 2:03 PM Currently Being Moderated Hi Experts,I am getting the following system log during the master data load.Database error 54 at EXEORA-00054: resource busy and acquire with NOWAIT specifiedThis log is generated daily when the master data load is running. But we are not facing any load failures due to this log in SM21.Please help me to avoid this error.Thanks & Regards,Sunil 5988Views Re: System Log Database error 54 at EXE Durgesh Gandewar Jul 26, 2011 2:19 PM (in response to sunil kumar) Currently Being Moderated Hi, Check following thread,[Database error 54 in EXE;Regards,Durgesh. Alert Moderator Like (0) Re: System Log Database error 54 at EXE sunil kumar Jul 26, 2011 2:29 PM (in response to Durgesh Gandewar) Currently Being Moderated Hi Durgesh,We are not getting any short dumps except the SM21 message. As mentioned there are also no load failures occurring.Please suggestSunil Alert Moderator Like (0) Re: System Log Database error 54 at EXE Suman Chakravarthy K Jul 26, 2011 2:33 PM (in response to sunil kumar) Currently Being Moderated Hi,Check the table space settings in DB02 t-code.In RSA1->Administration Tab->Current Settings->Batch ProcessRegards,Suman Alert Moderator Like (0) Re: System Log Database error 54 at EXE sunil kumar Jul 26, 2011 2:41 PM (in response to Suman Chakravarthy K) Currently Being Moderated what are the exact values you want me to look in?Sunil Alert Moderator Like (0) Re: System Log Database error 54 at EXE Suman Chakravarthy K Jul 26, 2011 2:53 PM (in response to sunil kumar) Currently Being Moderated Hi,Generally we will not be given access to change the Table space settings. You have to contact BASIS to know more about DB02.Regards,Suman Alert Moderator Like (0) Re: System Log Database error 54 at EXE sunil kumar Jul 26, 2011 3:01 PM (in response to Suman Chakravarthy K) Currently Being Moderated Hi Sanjay,BASIS team had reported this issue to BW team Let me know of any other options to dig the route cause.Regards,Sunil Alert Moderator Like (0) Re: System Log Database error 54 at EXE Yves KERVADEC Jun 5, 2014 8
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What is the reason for ORA-00054 error? up vote 0 down https://scn.sap.com/thread/2003935 vote favorite From Oracle's documentation:- ORA-00054 resource busy and acquire with NOWAIT specified Cause: Resource interested is busy. Action: Retry if necessary. In our code we issue a SELECT FOR UPDATE NOWAIT command to lock the row we are about to update. Right now the logic is if it returns SQL error 54 then it is assumed that another user is trying to update that same record. Is http://stackoverflow.com/questions/10350821/what-is-the-reason-for-ora-00054-error this logic valid? From Oracle's documentation it looks more like if the DB is overwhelmed then this might also cause this error to be thrown. What are the possible reasons for this error, when we are only using the above SQL command? oracle oracle11g ora-00054 share|improve this question edited May 1 '12 at 18:58 Ben 32.7k216398 asked Apr 27 '12 at 12:43 AppleGrew 3,179114487 1 Does the error return immediately, or as a timeout? –skaffman Apr 27 '12 at 12:45 I cannot debug or put sops there, so I am not sure if it returns immediately. The code is running in a standalone server. –AppleGrew Apr 27 '12 at 12:48 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted The SELECT ... FOR UPDATE attempts to acquire an RS (Row Share) lock on the table and an X (eXclusive) lock on the row. If another session has an exclusive lock on the table (eg creating an index) or an exclusive lock on the row (update, delete, or select for update) then the query will wait for the other transaction to release the lock (commit or rollback generally) unless you have specified NOWAIT. So one po
shut down suddenly before you have a chance to close NEO normally.Resolution for NEO 2.5 Users This problem can be fixed by rebuilding the NEO catalog. The catalog contains all the http://www.emailorganizer.com/kb/T1007.php information used to organize your messages (but does not contain the messages themselves). When you rebuild the catalog all your configuration settings (e.g., folder names, preferences) are preserved, and of course your email is not https://docs.google.com/document/d/1_FU6Y9o16MxTP_lH0FeSpq0tW-dfddp_HP2o7qGvLpk/edit affected. It will take as long as it took to create the catalog in the first place.To rebuild the catalog, perform these steps: Close all email-aware applications (e.g., NEO, Outlook).Double-click icon RebuildCatalog that is located database error in the folder you installed NEO into (probably c:\Program Files\Nelson Organizer).To rebuild a catalog for NEO Pro 3 or later: see next section. Please contact support@caelo.com if you need further assistance.Resolution For NEO Find or NEO Pro 3.0 (or higher) users NEO Pro 5 users: Click the Application Button where in the following the 'File menu' is mentioned. This problem can be fixed by rebuilding the NEO catalog. The catalog contains database error 54 all the information used to organize your messages (but does not contain the messages themselves). When you rebuild the catalog all your configuration settings (e.g., folder names, preferences) are preserved, and of course your email is not affected. It will take as long as it took to create the catalog in the first place.To rebuild the catalog, perform one of the following methods - Method 1: If you can access the File menu - Go to 'File | Catalog | Rebuild catalog…' and rebuild the current catalog by hitting the Rebuild Now button. You may also choose the 'other catalog' option and pick the appropriate catalog from the list if the rebuild does not relate to the current catalog. The rebuild will start up and continue for some time, depending on your Outlook message store size. Method 2: If you cannot access the File Menu because the error is preventing you then - close all email-aware applications (e.g. NEO, Outlook).Restart NEO in the no-catalog state. To do this, start the Task Manager (Ctrl-Shft-Del or right click the System Tray date area and select Task Manager from the dialog box), and on the Applications tab highlight the NEO application and press the 'End Process' button. Once NEO is closed, wait 1 minu
changesAccessibilityView onlyToggle screen reader support