Update rule dead lock

I need to reload an ODS to an infocube. I've erased the whole infocube (fact table and dimensions) and then i launched init with all data from ODS to infocube. All informations are getting stuck at the level of update rules. It ends after a while wih TIME OUT error.
I've verified in Runtime Errors(st22) and the loading stops at an update rule for Material Group:
SELECT MATL_GROUP FROM /BI0/PMATERIAL INTO RESULT WHERE MATERIAL =
COMM_STRUCTURE-MATERIAL.
ENDSELECT.
I've commented the routine and it loads withou any problem.. But I really need the material group in the infocube. What could I do.
Please help... I will assingn valuable points.
Thank you and Merry Christmas,
Gabriel

Load your material master from the source system and the Material Group is generally the navigational attribute of the 0MATERIAL. Hence you just have to switch on the Navigational attribute in your InfoCube.
Hope it solves your problem.
Regards
Gajendra

Similar Messages

  • Dead lock error while updating data into cube

    We have a scenario of daily truncate and upload of data into cube and volumes arrive @ 2 million per day.We have Parallel process setting (psa and data targets in parallel) in infopackage setting to speed up the data load process.This entire process runs thru process chain.
    We are facing dead lock issue everyday.How to avoid this ?
    In general dead lock occurs because of degenerated indexes if the volumes are very high. so my question is does deletion of Indexes of the cube everyday along with 'deletion of data target content' process help to avoiding dead lock ?
    Also observed is updation of values into one infoobject is taking longer time approx 3 mins for each data packet.That infoobject is placed in dimension and defined it as line item as the volumes are very high for that specific object.
    so this is over all scenario !!
    two things :
    1) will deletion of indexes and recreation help to avoid dead lock ?
    2) any idea why the insertion into the infoobject is taking longer time (there is a direct read on sid table of that object while observed in sql statement).
    Regards.

    hello,
    1) will deletion of indexes and recreation help to avoid dead lock ?
    Ans:
    To avoid this problem, we need to drop the indexes of the cube before uploading the data.and rebuild the indexes...
    Also,
    just find out in SM12 which is the process which is causing lock.... Delete that.
    find out the process in SM66 which is running for a very long time.Stop  this process.
    Check the transaction SM50 for the number of processes available in the system. If they are not adequate, you have to increase them with the help of basis team
    2) any idea why the insertion into the infoobject is taking longer time (there is a direct read on sid table of that object while observed in sql statement).
    Ans:
    Lie item dimension is one of the ways to improve data load as well as query performance by eliminationg the need for dimensin table. So while loading/reading, one less table to deal with..
    Check in the transformation mapping of that chs, it any rouitne/formula  is written.If so, this can lead to more time for processing that IO.
    Storing mass data in InfoCubes at document level is generally not recommended because when data is loaded, a huge SID table is created for the document number line-item dimension.
    check if your IO is similar to doc no...
    Regards,
    Dhanya

  • FOR UPDATE cursor is causing Blocking/ Dead Locking issues

    Hi,
    I am facing one of the complex issues regarding blocking / dead locking issues. Please find below the details and help / suggest me the best approach to ahead with that.
    Its core Investment Banking Domain, in Our Day to day Business we are using many transaction table for processing trades and placing the order. In specific there are two main transaction table
    1)     Transaction table 1
    2)     Transaction table 2
    These both the tables are having huge amount of data. In one of our application to maintain data integrity (During this process we do not want other users to change these rows), we have placed SELECT …………….. FOR UPDATE CURSOR on these two table and we have locked all the rows during the process. And we have batch jobs (shell scripts ) , calling this procedure , we will be running 9 times per day 1 hrs each start at 7:15AM in the morn finish it up in the eve 5PM . Let’s say. The reason we run the same procedure multiple times is, our business wants to know the voucher before its finalized. Because there is a possibility that order can be placed and will be updated/cancelled several times in a single day. So at the end of the day , we will be sending the finalized update to our client.
    20 07 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 08 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 09 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 10 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 11 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 12 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 13 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 14 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 15 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 16 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    20 17 * * 1-5 home/bin/app_process_prc.sh >> home/bin/app1/process.out
    Current Program will look like:
    App_Prc_1
    BEGIN
    /***** taking the order details (source) and will be populate into the table ****/
    CURSOR Cursor_Upload IS
    SELECT col1, col2 … FROM Transaction table1 t 1, Source table 1 s
    WHERE t1.id_no = t2.id_no
    AND t1.id_flag = ‘N’
    FOR UPDATE OF t1.id_flag;
    /************* used for inserting the another entry , if theres any updates happened on the source table , for the records inserted using 1st cursor. **************/
    CURSOR cursor_update IS
    SELECT col1, col2 … FROM transaction table2 t2 , transaction table t1
    WHERE t1.id_no = t2.id_no
    AND t1.id_flag = ‘Y’
    AND t1.DML_ACTION = ‘U’,’D’ -- will retrieve the records which are updated and deleted recently for the inserted records in transaction table 1 for that particular INSERT..
    FOR UPDATE OF t1.id_no,t1.id_flag;
    BLOCK 1
    BEGIN
    FOR v_upload IN Cursor_Upload;
    LOOP
    INSERT INTO transaction table2 ( id_no , dml_action , …. ) VALUES (v_upload.id_no , ‘I’ , … ) RETURNING v_upload.id_no INTO v_no -- I specify for INSERT
    /********* Updating the Flag in the source table after the population ( N into Y ) N  order is not placed yet , Y  order is processed first time )
    UPDATE transaction table1
    SET id_FLAG = ‘Y’
    WHERE id_no = v_no;
    END LOOP;
    EXCEPTION WHEN OTHER THEN
    DBMS_OUTPUT.PUT_LINE( );
    END ;
    BLOCK 2
    BEGIN -- block 2 starts
    FOR v_update IN Cursor_Update;
    LOOP;
    INSERT INTO transaction table2 ( id_no ,id_prev_no, dml_action , …. ) VALUES (v_id_seq_no, v_upload.id_no ,, … ) RETURNING v_upload.id_no INTO v_no
    UPDATE transaction table1
    SET id_FLAG = ‘Y’
    WHERE id_no = v_no;
    END LOOP;
    EXCEPTION WHEN OTHER THEN
    DBMS_OUTPUT.PUT_LINE( );
    END; -- block2 end
    END app_proc; -- Main block end
    Sample output in Transaction table1 :
    Id_no | Tax_amt | re_emburse_amt | Activ_DT | Id_Flag | DML_ACTION
    01 1,835 4300 12/JUN/2009 N I ( these DML Action will be triggered when ever if theres in any DML operation occurs in this table )
    02 1,675 3300 12/JUN/2009 Y U
    03 4475 6500 12/JUN/2009 N D
    Sample output in Transaction table2 :
    Id_no | Prev_id_no Tax_amt | re_emburse_amt | Activ_DT
    001 01 1,835 4300 12/JUN/2009 11:34 AM ( 2nd cursor will populate this value , bcoz there s an update happened for the below records , this is 2nd voucher
    01 0 1,235 6300 12/JUN/2009 09:15 AM ( 1st cursor will populate this record when job run first time )
    02 0 1,675 3300 12/JUN/2009 8:15AM
    003 03 4475 6500 12/JUN/2009 11:30 AM
    03 0 1,235 4300 12/JUN/2009 10:30 AM
    Now the issues is :
    When these Process runs, our other application jobs failing, because it also uses these main 2 tranaction table. So dead lock is detecting in these applications.
    Solutin Needed :
    Can anyone suggest me , like how can rectify this blocking /Locking / Dead lock issues. I wants my other application also will use this tables during these process.
    Regards,
    Maran

    hmmm.... this leads to a warning:
    SQL> ALTER SESSION SET PLSQL_WARNINGS='ENABLE:ALL';
    Session altered.
    CREATE OR REPLACE PROCEDURE MYPROCEDURE
    AS
       MYCOL VARCHAR(10);
    BEGIN
       SELECT col2
       INTO MYCOL
       FROM MYTABLE
       WHERE col1 = 'ORACLE';
    EXCEPTION
       WHEN PIERRE THEN
          NULL;
    END;
    SP2-0804: Procedure created with compilation warnings
    SQL> show errors
    Errors for PROCEDURE MYPROCEDURE:
    LINE/COL                                                                          ERROR
         12/9        PLW-06009: procedure “MYPROCEDURE” PIERRE handler does not end in RAISE or RAISE_APPLICATION_ERROR
         :)

  • DB dead lock during update

    Hello,
    In our R/3 Enterprise 4.7 Production system running on Windows NT/MSSQL, I saw update errors in t-code SM13.
    Error details:
    Date : 07/19/2009
    No. of errors : 24
    All errors are for background user BATCH-ID
    Function Module    :    RKE_WRITE_ACT_LINE_ITEM_OP01
    Status     :      DB dead lock during update
    SM12 doesnt have any locks currently, not sure about status when these update errors occured.
    I didnt find any SAPnotes related to this F-module or similar.
    Can you please tell whether it is a serious issue and how to handle such errors?
    Regards,
    Roshan

    Hi,
    can u please let us know how many time u have seen this error in SM13. Also from how many days.
    If its only once u have seen, then no need to worry.
    Function Module : RKE_WRITE_ACT_LINE_ITEM_OP01
    Status : DB dead lock during update
    From above lines its clear that,  Function Module : RKE_WRITE_ACT_LINE_ITEM_OP01 was locked, so the update has failed to access that module. Since it had faield to update, so is the error in sm13 with reason DB dead lock during update.
    Can u please refer to the logs in SM21 and also to the trace files(of related work process) related to the same error(red color errors), Try to analyze from there, If u find any difficulties in doing so. Paste the same here  along with ur system verion/DB/OS/Patch level
    Regards,
    Ravi

  • What are dead locks in BW

    hI,
       What are dead locks in BW

    Hi ,
    The concept of dead lock is as similar as in Oracle. If Process P1 is using resource A (locked by P1)) and waiting for B and Process P2is using resouce B(locked by P2) and waiting for resouceA. This creates dead lock as both can not proceed further.
    In BW deadlock usually occur in delta load. As, far as my observance deadlock usually occurs during processing of update rules. This may be because more than one package will be processing same record as in delta load, data moves from changelog of below level to next level.
    Regards
    Sushma

  • Frequenet dead locks in SQL Server 2008 R2 SP2

    Hi,
    We are experiencing frequent dead locks in our application. We are using MSSQL Server 2008 R2 SP2 version. When our application is configured for 5-6 app servers, this issue is occurring frequently.
    But, when the same application is used with the MSSQL Server 2008 R2 or SQL Server 2012, we don't see the dead lock issue. From the error lock and sql trace, the error message is thrown for the database table JobLock. We have a stored procedure to insert/update
    for the above table when the job moves from one service to other. The same procedure works fine when used with the 2008 R2 and SQL Server 2012 Version.
    Is the above issue related to the hotfix from the below url?
    http://support.microsoft.com/kb/2703275
    Following error message is seen frequently in the log file.
    INFO : 03/24/2014 10:26:30:290 PM: [00007900:00005932] [Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction] System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 62) was deadlocked on lock resources with another process and has been
    chosen as the deadlock victim. Rerun the transaction.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
       at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand command, DbTransaction transaction)
       at Xerox.ISP.DataAccess.Data.Utility.ExecuteNonQuery(TransactionManager transactionManager, DbCommand dbCommand)
       at Xerox.ISP.DataAccess.Data.SqlClient.SqlActivityProviderBase.ActivityReady(TransactionManager transactionManager, Int32 start, Int32 pageLength, Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1
    CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName, Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
       at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
    Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS, Int32 start, Int32 pageLength)
       at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
    Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
       at Xerox.ISP.Workflow.ManagedActivity.<>c__DisplayClass2f.<ActivityReady>b__2d()
       at Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction(Boolean createNew, PersistMethod persist)
    ClientConnectionId:9e44a64f-5014-4634-9cee-4581e1b9c299
    I look forward to the suggestions to get the issue resolved. Your input is much appreciated.
    Thanks,
    Keshava.

    If you are having deadlock trouble in your SQL Server instance, this recipe demonstrates how to make sure deadlocks are logged to the SQL ServerManagement Studio SQL log appropriately using
    the DBCC TRACEON, DBCC TRACEOFF, and DBCC TRACESTATUS commands. These functions enable, disable, and check the status of trace flags.
    To determine the cause of a deadlock, we need to know
    the resources involved and the types of locks acquired and requested. For this kind of information, SQL Server provides
    Trace Flag 1222 (this flag supersedes 1204, which was frequently used in earlier versions of SQL Server.)
    DBCCTRACEON(1222,
    -1);
    GO
    With this flag enabled, SQL Server will provide output in the form of a deadlock graph, showing the executing statements
    for each session, at the time of the deadlock; these are the statements that were blocked and so formed the conflict or cycle that led to the deadlock.
    Be aware that it is rarely possible to guarantee that deadlocks will never occur. Tuning for deadlocks
    primarily involves minimizing the likelihood of their occurrence. Most of the techniques for minimizing the occurrence of deadlocks are similar to the general techniques for minimizing blocking problems.

  • Transporting Update Rules

    Hi,
    I am transporting update rules for a Cube.
    The InfoSource has been generated from a DSO and created update rules to the above said Cube.
    In the transports I am getting the below error.
    Start of the after-import method RS_UPDR_AFTER_IMPORT for object type(s) UPDR (Activation Mode)     
    Update rules 46H2HBH6BRHP9R29L0XREHQP3 read in version M                                            
    Update rules 46HK9D48LBRIH89ZBZVTZERTZ read in version M                                            
    Error when activating update rule 46H2HBH6BRHP9R29L0XREHQP3                                         
    Activation of the update rules for ZICUBE01 8ZDSO1                                              
    IC=ZICUBE01  IS=8ZDSO1 error when checking the update rules                                       
    Error when activating update rule 46HK9D48LBRIH89ZBZVTZERTZ                                         
    Activation of the update rules for ZICUBE04 8ZDSO04                                               
    IC=ZICUBE04  IS=8ZDSO04 error when checking the update rules                                       
    The InfoCube(It is already there in Q apd P) has been locked in a different user transport as he added a field to it and not yet transported.
    Is this the problem?
    Thans in advance..
    Message was edited by:
            Indira SR

    Hi indira,
    make neccessary changes to the request if u created earlier i.e u can delete the original request or change the discrption to "Dont delete" and release it, if u unable to delete each task in that particular request.
    Second step is activate all the infosources and cubes and Update rules.
    Then create transport request individually i.e One for IS and One IC and another for Update rules..It would be easier to trace in case of any error.
    Release the requests 4m DEV, and important thing is import these requests in Q or P in hierachiel manner i.e
    1. IS
    2. IC
    and the Update rules request.

  • Dead Locks

    Gurus,
    Please clarify me the three questions which I am posting below
    1) What's the deadlock situation ? How oracle treats the dead lock situation
    2) Disadvantages of having index
    3) I have two tables A and B .. In table A, I have two columns (say col1, col2) .. Col1 is a primary key column .. In table B, I have two columns (say col3, col4) .. Col3 is a primary key column .. Col2 of A has a referrential integrity to Col3 of B ..And Col4 of B has a referrential integrity to col2 of A .. Now if I am inserting a values in table A ...it is showing error "parent value doesnt exist" .. like wise, if I am inserting values in table B, the above mentioned error is comming ..
    How to overcome this error
    Please advice
    Regards

    Hi.
    1) A dead lock is a situation where two or more sessions acquire locks which then prevent each other from moving on. ie session one updates a row aaa in a table and session two updates row bbb (no commits). Session one then attempts to update row bbb and session two attempts to update row aaa and both wait for the locks to clear (default behaviour). Oracle monitors for these situations and will automatically kill one of the sessions and allow the other to complete.
    2) Indexes are used to speed up access to data in the database and if associated with a Primary or Unique Key, enforce uniqueness. They have the disadvantages of taking up space and slowing down updates and inserts.
    3) This is not a deadlock. It is a circular reference. You cannot insert into one table because the other table is expected to have a parent value and vice versa. From a data modelling point of view a circular reference is unsupportable and meaningless. Like trying to be your father's son and your father's father at the same time.
    Regards
    Andre

  • Adobe flash updater appears to lock user profile files in Windows 7

    Hello All,
    I don't own any Adobe products, but I wanted to put this up so that others who run into this issue can find it, and hopefully Adobe will look into it if it's common.
    This evening, I had just restarted my computer (Windows 7 RC), and after an usually long load time, I found myself loading into a profile other than my own.  Windows informed me that it has been unable to access my user profile and so had booted me into a temporary profile.  I noticed that the reason for being unable to access the profile was that it was being accessed (locked) by another program.  I rebooted.
    This time when I logged in, I was taken to my own profile, but before it loaded, I received a message from windows stating that it has been unable to open the user profile, and at the same time I saw a prompt from the Adobe Updater asking me if I wanted to upgrade to the next version of Adobe Flash.  After closing the dialogs, my profile contained everything for my desktop, but my windows settings appeared to have all been disabled (meaning Windows Aero was turned off and everything looked...odd--like an older version of windows squeezed into the updated Windows 7 interface).
    Taking a guess that the prompt from the Adobe updater may have been responsible for locking the profile while it was awaiting a response (somehow I guess it was running BEFORE windows loaded the user profile), I uninstalled all my adobe products and rebooted.
    Issue solved. Presumably, installing the update when you first see the prompt and not waiting for another time after a reboot would also bypass this issue.
    So it appears that the Update prompt locks the Windows user profile in Windows 7, which causes a problem because (maybe only on machines that don't auto login?) it appears to run before the profile loads: so it has a user profile file locked waiting for a response from the user, which can't come because the profile hasn't been loaded by Windows (so the user can't see the prompt), but Windows can't load the profile because the file is locked...sort of a soft dead lock (since I was sort of able to get in eventually).
    Wanted to get this out, and was also wondering if anyone else has seen this issue.
    Cheers,
    -jfc

    Trying to install FB 4.5 - comes up with this error on my machine - anyone have any concrete ideas on how to overcome this...
    I've tried rebooting, removing activex plugins etc but of no help....
    WARNING: DW031: Payload:{650C9D09-D5BD-4532-8BEE-01DBC1DF5537} Adobe Flash Builder 4.5 4.5.0.0 has been updated and has been selected for repair. The patch {CEAC4FFA-E7DE-4434-890A-F0AC7792DE5E} Adobe Flash Builder 4.5_4.5.1_AdobeFlashBuilder-mul 4.5.1.0 will be uninstalled now.
    WARNING: DW031: Payload:{650C9D09-D5BD-4532-8BEE-01DBC1DF5537} Adobe Flash Builder 4.5 4.5.0.0 has been updated and has been selected for repair. The patch {CEAC4FFA-E7DE-4434-890A-F0AC7792DE5E} Adobe Flash Builder 4.5_4.5.1_AdobeFlashBuilder-mul 4.5.1.0 will be uninstalled now.
    ----------- Payload: {551D0A52-5E4A-4898-9FFF-FEAA5E89585A} Adobe Flash Player 10 ActiveX 10.0.0.0 -----------
    ERROR: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\DOCUME~1\nanunh\LOCALS~1\Temp\InstallAX.exe, command: -install activex -msi
    ERROR: Install MSI payload failed with error: 1603 - Fatal error during installation.
    MSI Error message: Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\DOCUME~1\nanunh\LOCALS~1\Temp\InstallAX.exe, command: -install activex -msi
    ERROR: DW050: The following payload errors were found during install:
    ERROR: DW050:  - Adobe Flash Player 10 ActiveX: Install failed
    Please search the above error/warning string(s) to find when the error occurred.
    These errors resulted in installer Exit Code mentioned below.
    Exit Code: 6 - Silent workflow completed with errors.
    [    1460] Mon Aug 15 17:52:20 2011  INFO
    *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

  • Sessions were still active eventhough Dead lock detected

    Hi all,
    Yesterday I saw very odd oracle behaviour.When oracle finds Dead lock it should kill those sessions automatically.In my case those two sessions were still trying to run the same update command and were casuing dead locks again and again for 1 Hour.I had to kill those sessions manually to avoid these dea lock.
    How can those sessions were still trying eventhough dead lock detected and causing deadlocks.My logfile filled with this dead lock error.When I killed those sesions it end up with snap shot too old error.
    Please suggest me
    Thanks

    hi
    just ROLLBACK or COMMIT any one session. you will out of dead lock.
    and one more thing is in dead lock situation the sessions were not terminated
    and session wating for releasing locks aquire by another session
    try this one if not work plz reply
    have a nice time
    best luck

  • AQ subscription (dead)locks

    Hi,
    I posted a question in the OCCI forum (Subscribing/unsubscribing call is blocking (lock?) but now I'm starting to suspect that this is a general AQ problem.
    We have a AQ queue with multiple subscribers, where the subscribing clients are implemented in OCI/OCCI. At the startup of the client program, we subscribe to the queue trough a stored procedure, and creates a callback in the OCCI implementation of the client.
    The problem is that sometimes the subscription query / callback creation seems to block. Could this be because a lock has been put on the subscriber/queue? There is no explicit locking in our code, as far as I know.
    The stored procedure for subscribing basically does this:
    DBMS_AQADM.ADD_SUBSCRIBER(queue_name => v_queue_name,
    subscriber => subscriber,
         rule => p_rule);
    I'm an experienced programmer, but not too familiar with Oracle/AQ, so it would be great if someone could point me in the right direction of debugging this. I have access to Toad.
    EDIT: We are running three threads simultanously, all calling add_subscriber. Could this be a problem, creating some sort of deadlock?
    Thanks,
    Sverre

    Hi,
    do the clients have the same subcription name?
    In the documentation see this link:
    http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10785/jm_create.htm#i1005628
    EDIT (Sorry i assumed that you use JMS ;-(
    Can you tell me, what is the statement which shows up in the dbconsole in the top activity when the (dead)lock appears? (I hope you use 10g)
    Message was edited by:
    HEWizard

  • DEAD LOCKS on table ARFCSSTATE

    Please help!
    Essentially the problem is that anything that updates the customer master (T/C BP) causes DEAD LOCKS on table ARFCSSTATE and the queues either slow down terrible or they hang (stop).  When one tries to delete an entry in the queue a screen dump takes place – DBIF_RSQL_SQL_ERROR in ARFC_RUN.
    We are using: CRM 3.0 with the following service packs:
    SAP Basis release 610 level 38
    SAP ABA Release 50A level 38
    BBPCRM Release 300 level 17
    Points will be given.
    Thank you.

    Hi Surendra,
    I was expirenced with the error, Basis people had resolved that for me,
    better to post this issue to them,
    this problem for all data sources or any perticulat data source when scheduling infopackage.
    Regards
    Vijay

  • DEAD LOCK ERROR

    When we are using our oracle application, our session hang every time the user update records. the DBA said that we have a dead lock error... the only thing he did is to reset sa database every time we in counter this problem. but we have this error every day, and i don't have an ideal regarding what is dead lock.

    you don't have a deadlock problem, because a deadlock will be "solved" as oracle simply kills the blocking session and rollbacks the changes.He is right. you might have blocking problem not dead lock problem. Find out the blocker and waiter and kill the blocker session.
    Following query would give you an idea about who is blocking and who is waiting for :
    select /*+ ordered */
    a.sid blocker_sid,
    -- c.sql_text,
    a.username blocker_username,
    a.serial#,
    -- a.logon_time,
    b.type,
    b.lmode mode_held,
    b.ctime time_held,
    c.sid waiter_sid,
    c.request request_mode,
    c.ctime time_waited
    from v$lock b, v$enqueue_lock c, v$session a, v$sqltext c
    where c.address=a.prev_sql_addr and
    a.sid = b.sid
    and b.id1 = c.id1(+)
    and b.id2 = c.id2(+)
    and c.type(+) = 'TX'
    and b.type = 'TX'
    and b.block = 1
    order by time_held, time_waited
    Look for blocker_id and waiter_id. If possible, kill blocker using following command.
    select sid,serial# from v$session where sid = blocker_sid;
    alter system kill session 'sid,serial#'';
    Jaffar

  • ORA-00060 dead lock happen on R12 demo database

    We have EBS R12 (12.0.4) on Redhat Linux system when I check alert.log file and found demo database (VIS) have ORA-00060 dead lock. The dead lock happen on statement:
    UPDATE FND_CONCURRENT_REQUESTS SET PP_END_DATE = SYSDATE, POST_REQUEST_STATUS = 'E' WHERE REQUEST_ID = :B1
    Do I need do anthing relate to this ORA- error or just ignore it?
    Thanks.

    Thank you for answer. I checked CM log and did NOT find any error.
    I also read document 153717.1 and compare FND_CONCURRENT_REQUESTS table definition. The initial number of trnasaction is 10 and max is 255. I try to use OEM to change "initial transaction number" and it don't allow to.
    Any ideal???

  • Dead lock handling

    Hi
    I am running a little test that runs two threads that update the same table. Each thread tries to update several documents in the within a single transaction. The update is done by retrieving the document, modifying it, adding the updated document and deleting the existing document.
    I have enable dead lock detection and when a dead lock exception is thrown I abort the current transaction.
    However after a few iteration, deleteDocument causes a core dump and DBXML prints to stderr : "Previous deadlock return not resolved".
    Is there anything else to resolve when a dead lock occurs other than abort the transaction?
    This is the relevant stack trace:
    #0 0x00421780 in Dbc::get () from /u/yoava/dbxml-2.2.13/install/lib/libdb_cxx-4.3.so
    (gdb) where
    #0 0x00421780 in Dbc::get () from /u/yoava/dbxml-2.2.13/install/lib/libdb_cxx-4.3.so
    #1 0x00934289 in DbXml::SyntaxDatabase::updateStatistics (this=0x2000001c,
    context=@0x8641c34, key=@0x8628070, statistics=@0x8628088) at Cursor.hpp:48
    #2 0x00901d10 in DbXml::StatisticsWriteCache::updateContainer (this=0x8641bcc,
    context=@0x8641c34, container=Internal: global symbol `Container' found in Container.cpp psymtab but not in symtab.
    Container may be an inlined function, or may be a template function
    (if a template, try specifying an instantiation: Container<type>).
    ) at /usr/include/c++/3.2.3/bits/stl_tree.h:202
    #3 0x0093bacf in DbXml::KeyStash::updateIndex (this=0x8634df8, context=@0x8641c34,
    container=0x8630e68) at KeyStash.cpp:210
    #4 0x008c72b7 in DbXml::Container::deleteDocument (this=0x8630e68, txn=0x86417f8,
    document=@0x8671f38, context=Internal: global symbol `UpdateContext' found in UpdateContext.cpp psymtab but not in symtab.
    UpdateContext may be an inlined function, or may be a template function
    (if a template, try specifying an instantiation: UpdateContext<type>).
    ) at Container.cpp:679
    #5 0x008d3475 in DeleteDocumentFunctor2::method (this=0x2000001c, container=@0x8630e68,
    txn=Internal: global symbol `Transaction' found in Transaction.cpp psymtab but not in symtab.
    Transaction may be an inlined function, or may be a template function
    (if a template, try specifying an instantiation: Transaction<type>).
    ) at TransactedContainer.cpp:121
    #6 0x008d3149 in DbXml::TransactedContainer::transactedMethod (this=0x8630e68,
    txn=0x3d71c8, flags=0, f=@0xb176b470) at TransactedContainer.cpp:217
    #7 0x008d2fe8 in DbXml::TransactedContainer::deleteDocument (this=0x8630e68,
    txn=0x86417f8, document=Internal: global symbol `Document' found in Document.cpp psymtab but not in symtab.
    Document may be an inlined function, or may be a template function
    (if a template, try specifying an instantiation: Document<type>).
    ) at TransactedContainer.cpp:26
    #8 0x00906940 in DbXml::XmlContainer::deleteDocument (this=0xbfff8c94, txn=@0xb176b5a0,
    document=Internal: global symbol `XmlDocument' found in XmlDocument.cpp psymtab but not in symtab.
    XmlDocument may be an inlined function, or may be a template function
    (if a template, try specifying an instantiation: XmlDocument<type>).
    ) at /u/yoava/dbxml-2.2.13/dbxml/include/dbxml/XmlDocument.hpp:72
    #9 0x0804a5c0 in DoUpdates (arg=0xbfff8c90) at dbxml_test_6.cpp:99
    #10 0x003dedec in start_thread () from /lib/tls/libpthread.so.0
    #11 0x0037ea2a in clone () from /lib/tls/libc.so.6
    thanks

    I have applied them. When applying patch 6 I got an error:
    compile3.server 46% patch < patch.2.2.13.6
    patch.2.2.13.6: No such file or directory.
    compile3.server 47% patch < patch.2.2.13.6
    (Stripping trailing CRs from patch.)
    can't find file to patch at input line 3
    Perhaps you should have used the -p or --strip option?
    The text leading up to this was:
    |*** NsEventGenerator.cpp.orig Thu Dec 8 14:50:50 2005
    |--- dbxml/src/dbxml/nodeStore/NsEventGenerator.cppThu Sep 28 17:24:57 2006
    File to patch: dbxml/src/dbxml/DbWrapper.hpp
    patching file dbxml/src/dbxml/DbWrapper.hpp
    Hunk #1 FAILED at 357.
    1 out of 1 hunk FAILED -- saving rejects to file dbxml/src/dbxml/DbWrapper.hpp.rej
    However this patch does not seem to be lock related.

Maybe you are looking for