Buffer table and Locking issues

We have a real table and a buffer table. The real table gets locked on occation for processing, at which times, incoming data is deposited into the buffer table.
I am looking for a way to dump all the information from the buffer table into the real table whenever the real table is released from its lock. I would prefer not to write and schedule a program to run based on time (i.e. every 2 seconds, a procedure is called that looks to see if the table still has a lock on it...)
Does anyone have any ideas how I can do this? I have thought about using the DBMS_ALERTS package or DBMS_AQ somehow, but I am not as familiar with the two as I'd like. I'd be happy to explain this further if required.
Thank you.

Thank you for the suggestion, but this does not look like a viable option. For this to work, the trigger would have to fire everytime a DDL event was fired, and I would have to build if...then logic into the trigger. Besides, in the documentation, I don't think table locks would be considered DDL.
Any other ideas? Again, thanks for the help. I did not previously know I could create triggers on these type of events.
RW
null

Similar Messages

InfoPack processing (PSA and data targets in parallel) data and lock issues

Good morning,
We are on BW 3.5 and contemplating changing our InfoPackages from option 1 (PSA then data targets) to option 2 (PSA and data targets in parallel) for performance reasons (test have shown a gain of 50% in load time compared to using option 1).
Issues have been raised that using option 2 may lead to data consistency and lock issues especially for SD infosources where we are dealing with multiple daily status changes for same document that need to be read in a specific order.
From what I have read, such issues were possible in BW 2.x e.g. OSS Note 384023 and 364577. However, I am under the impression that the issues may have been resolved in BW 3.x and that it is "safe" to use option 2 (PSA and data targets in parallel).
Would really appreciate if you could please share your experience when using processing option 2 (PSA // DT) especially in a BW 3.xx system.
Thank you in advance,
Catherine

Hi Amit,
The help text (vers. 3.5) for this method of loading says simply -
"A process is started to write the data from this data packet into the PSA for each data package. If the data is successfully updated in the PSA, a second parallel process is started. In this process, the transfer rules are used for the package data records, data is adopted by the communication structure, and it is finally written to the data targets. Posting of the data occurs in parallel by packet.
This method is used to update data into the PSA and the data targets with a high level of performance. The BW system receives the data from the source system, writes it to the PSA, and starts the update immediately and in parallel into the corresponding data target"
Not sure where you got your description from, but is not explained well and confusing.
Regards,
Ken

Integrated ITS: multiple sessions and locking issue

We are upgrading to ECC 6.0 from 4.6C and have Integrated ITS turned on. We have built a custom PZM3 as one entry and exit point for our ESS services. But we have issues with session management when navigating between some services like PZ14 and PZ02. The PZ14 session and the corresponding lock are not released upon going to the PZ02 service directly. But this happens for only some services. If you navigate between PZ02 and PZ12 it works fine. I followed the instructions of note# 959417, but it didn't work. Not only it is causing locking issues, but also memory usage issues as multiple user sessions are being created on the server. I did check some of posts similar to this one, but the issue still persists.
Our WAS release: 7.00; ABAP support package: SAPKB70009; Patch level: 75.
I would appreciate if anyone could shed some light on this issue. Thank you for your time and consideration.
Kshitij

Our Basis admin found out that using a parameter ~DISCONNECTONCLOSE = 1 would resolve most of this issues -- and it did. But now we are having issues with some users having popup blockers turned on. We referred to SAP notes 892250/596698-- followed it -- implemented it-- but some users
still have issues -- like today while working from home via VPN, I am having issues with session management. But working from office yesterday,
the sessions worked just fine.

Parallel (same) background jobs: Memory and locking issues

<b>Scenerio:</b> Multiple concurrent inbound asynchronous XI messages need to be processed in SAP. We have the XI proxy initiating an RFC. This RFC exports internal tables (essentially the XI payload) to a unique shared memory ID (for each XI message). RFC then submits an abap (submit..and return) in a background job. This abap reads (via IMPORT) the shared memory ID to get the data then process it.
<b>Problem:</b> : When multiple concurrent jobs/abap are running, often, but not always, one of the submitted abaps either gets a non-zero return code from the IMPORT, or the IMPORT from shared memory seems to work fine, but the table contents contains data from the other (parallel) run, even though the memory ID used is correct and unique.
I have attempted to resolve this by using various methods (memory IDs, SPA/GPA parameter, ENQUEUE) of locking in the RFC (unlocking at end of abap), so that only one background job is executed at a time. However, the best I can do is having two or three running in parallel.
So I'm wondering how to solve this memory issue and/or how to make the abap processing synchronous? Any help appreciated. Thanks.

There is a limitation on Amt of data you can store in ABAP Memory and SAP Memory .. check those limitation ..per user ..
also check for Number of external session granted by urr basis ppl...
it may be possible that only 3-4 session are allowed coz each background process create and external session ..

ALV OOps report- getting data from two tables and adding issue

Hi,
This is sales employee performance report.
I need to select all the fields from two tables based on user input ie VKorg, sales employee .
There is one field callled " Net sales"in both the tables.
Based on sales employee number, i need to add that net sales which i get from two tables.
I need to generate single report.
Can you give some inputs reg. the select query.
My idea is select all the data from both tables using join statement.
Thanks

Hi,
I have written like this:
select * from S002 as a join S006 as b
    into table ME->SS002_RAW[]
    where vkorg in me->select_parameters->SO_VKORG[] = vkorg in me->select_parameters->SO_VKORG[]
          and ZZSLSEMP01 in me->select_parameters->SO_so_empl[] = ZZSLSEMP02 in me->select_parameters->SO_so_empl[].
when i do like that,
I am getting error
Incorrect structure of FROM clause . . . .
If you give some idea on this
Edited by: Raja on Apr 22, 2009 11:19 AM

Buffer table not update

Hello all,
I tried to create a Scart for a category id meant for Classic scenario but I get an error that "Buffer Table not update " and it is resulting in a ABAP Dump.However, for the Categoryid for Ext. Classic Scenario it is working fine.
I tried SWU_OBUF also.
Any body ,Pl enlighten on how to proceed further?
Thanks & Regards,
Nagarajan
Addl Info:
1) Activated the Global settings for Extended Classic Scenario
2) Activated the BADI for control of Extended Classic Scenario

Hi,
Go to the SMQ1 and SMQ2 in both the frontend and backend systems and check for any queues of material replication still running or held.
Delete all the obsolete entries in this.
This may help you as in our system it worked once for this buffer table not uptodate issue.
Best regards,
Sridhar.

Query Builder - 2 occurrences of same table and Show Related Tables

In SQL Developer 1.5 the Query Builder still does not allow you to drag two copies of the same table onto the canvas. Additionally the Show Related Tables does not appear to do anything even after Hide Related Tables. Both of these operations sets the cursor to the hourglass although you can continue working as if the commands completed OK. Query Builder is a great time saver but with limitations like this it is really hobbled.
Additionally, in order to get join conditions you have to double-click the join in the diagram before the appropriate WHERE clause appears. I have not found any reference to how to use the Query Builder in any documentation. This forum has stated that the Query Builder is supposed to be intuitive and easy to use but this is not the case so far.
The rest of SQL Developer is a pleasure to use!

Thanks for your feedback. There are a number of things we want to do to the Query Builder. The issue about dragging 2 copies of a table onto the work surface is a logged enhancement request that we want to address. The Show Related tables and hourglass issues are bugs and need to be addressed. I'll document those.
Better documentation is also important and we can add that into the product for a future release.
In the short term, I have on previous occasion said I'd do a demo for using the Query Builder, so I'll make that a priority.
Sue

RFC calls keep old buffer tables PS and PSINFO

Hello!
I have written a BSP application for an R/3 system which is release 4.6c. For that reason, we have a stand-alone WebAS which must make RFC's to the core R/3 system to retrieve and update HR data.
Originally the RFC destination to connect to the core R/3 system from WebAS was not a trusted connection, but we ran into problems with structural authorizations where the RFC was not returning all of the data for the actual user. We found that the problem was related to the fact that the RFC destination was using a hard-coded user ID to make the connection to the R/3 HR system. That particular user ID was being used as SY-UNAME in a routine used by structural authorizations, and it wasn't finding the correct data for the User ID that was entered as the RFC user. Therefore, we made the change on the RFC destination in WebAS so that now we have the "Current User" checkbox checked, the hard-coded user ID and password has been removed, and now the "Trusted System" radio button is selected. Those changes resolved our issue with structural authorizations because now the routine has the actual user ID as SY-UNAME instead of the generic RFC user ID.
I'm not sure if the RFC trusted connection is part of this issue or not, but I wanted to provide that information.
Here is the actual issue... Several of the RFC's update different HR infotypes, and most of these use function module HR_INFOTYPE_OPERATION to insert new HR infotype records or modify existing ones, etc. We started receiving short dumps and getting strange results, and I was able to track it down to the fact that the PS and PSINFO buffer tables are not being refreshed. I was expecting that these tables would be "clean" everytime I make a new RFC call. However, this is not the case. I watched this in debugger, and I see that the PS and PSINFO tables are still filled from the last RFC whenever I make a subsequent RFC! When it finally gets to the point that dialog HR_MAINTAIN_MASTER_DATA is called, it still has the old data in these tables, so it tries to process the infotypes AGAIN. This is very bad! For one thing, the previous RFC which used HR_INFOTYPE_OPERATION might have been for an applicant number (TCLAS = 'B') and the current RFC might be for an employee number (TCLAS = 'A'). We have seen this happen, and it resulted in a short dump (it's a long story - just trust me when I say that it is causing a lot of problems!).
I was able to resolve the issue in one of my function modules by adding a call to function module HR_PSBUFFER_INITIALIZE at the beginning of the function module. However, I don't want to have to add this to the beginning of every function module that I write. Also, I think that this is a problem which needs to actually be solved instead of using a band-aid like this.
This is what I want to know - Why are these buffer tables still filled from the last RFC whenever I make the next RFC? Is this because it is set up as a "trusted" connection? Is this related to the fact that my BSP application is stateful instead of stateless? Does something need to be changed on my RFC destination configuration so that each RFC starts out with "clean" buffer tables?
Thanks in advance for whatever advice you can offer me!
Shannon

I don't think this has anything to do with the trusted connection. It is because your application is stateful. If you watch in the process overview in your system you will see that with a stateful application, no only does your BSP session state remain between calls, but also you should see a thread per user for the RFC connection.
That means that the Session state is also still alive on your R/3 4.6C system for a period of time as well (RFC keep alive time). We have used this to our advantage before when building BSP applications (caching of data in Global Data of a Function Group).
However you have the opposite problem. It sounds like you would want to call the HR_PSBUFFER_INIT at the start of each transaction. If you writting this as a Classic Dynpro Transaction would you not do the same?
You might try calling RFC_CONNECTION_CLOSE as well. This should close the connection and end the state on the R/3 side. However you will have the performance overhead of reestablishing a new connection on the next call. But RFC connections seem to be very efficient. I doubt you would notice any performance difference.

Linked tables, stored procedures, and locking

I'm working on an interface between two Oracle systems. I don't know if they're on the same server or not, but they are definitely two different database instances. The plan for this interface is that when a record is created on one of the systems, it will call a stored procedure on the other system to create the record there as well. I believe the relevant information will be passed via parameters to the stored procedure (not by querying the data in the first system). The ID number created on the second system gets passed back to the first system via an output parameter.
A concern was raised about whether something like this might cause "rev-locking". Similar issues were raised on a different interface, but that interface used a linked table between the two systems. The original design for that interface had a stored procedure initiated from the second system, and it was to update data via the linked table in the first system. But this caused some locking issues. So a different interface was written, that only used the linked table as read-only.
So the question is, do stored procedure calls between linked databases have the same issues as updates directly to linked tables? And a better question is, is there a document or white paper out there somewhere that describes the locking issues between linked databases, and presenting the "best practices" for this type of coding?
Any help is appreciated!
Christine Wolak
[email protected]

So the question is, do stored procedure calls between linked databases have the same issues as updates directly to linked tables? I'm not aware of any issues with updates across databases. can you post a more detail version of what exact issues did you encounter when updating tables across database using database links?
when you update a row in a table, from the same database or another one, a lock on that row will be placed for the duration of the transaction. Others will be able to read that row but not update it till the end of the local (or the remote) transaction.
What issue(s) did you encounter?

Unable to update, when executed table gets lock and Execution does not stop even for an hour.

Following is my Query, which unables to update. When Executed, table gets lock and Execution does not stop even for an hour.
update Employees
set Status = 'Close'
where statusid IN (select statusid
from MyView
where DownloadedDate ='2014-07-27 00:00:00.000'
here Employee contains 3,00,000 of records and Subquery return 1,50,000 Empid
i tried in various ways but not able to solve, statusid column have no index on, i tried using cursor but it does not work.
plz let me know how to solve this Issue, Its very Important to get solve as all my further work depends on Updation
, THANKS IN ADVANCE.

See also your other thread with the same question:
http://social.msdn.microsoft.com/Forums/en-US/80243625-fc3b-4ee1-bce1-4adcdbc16c14/unable-to-update-when-executed-table-gets-lock-execution-does-not-stop-execution-even-for-an-hour?forum=sqlserversamples
Olaf Helper
[ Blog] [ Xing] [ MVP]

Row locking issue with version enabled tables

I've been testing the effect of locking in version enabled tables in order to assess workspace manager restrictions when updating records in different workspaces and I have encountered a locking problem where I can't seem to update different records of the same table in different sessions if these same records have been previously updated & committed in another workspace.
I'm running the tests on 11.2.0.3. I have ROW_LEVEL_LOCKING set to ON.
Here's a simple test case (I have many other test cases which fail as well but understanding why this one causes a locking problem will help me understand the results from my other test cases):
--Change tablespace names as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
--update 2 records in a non-LIVE workspace in preparation for updating in different workspaces later
update t1 set name = name||'changed' where id in ('1', '2');
commit;
quit;
--Now in a separate session (called session 1 for this example) run the following without committing the changes:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--Now in another session (session 2) update a different record from the same table. The below update will hang waiting on the transaction in session 1 to complete (via commit/rollback):
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
I'm surprised records of different ids can't be updated in different sessions i.e. why does session 1 lock the update of record 2 which is not being updated anywhere else. I've tried this using different non-LIVE workspaces with similar results. I've tried changing table properties e.g. initrans with and still get a lock. The changes to table properties are successfully propagated to the _LT tables but not all the related workspace manager tables created for table T1 above. I'm not sure if this is the issue.
Note an example of the background workspace manager query that may create the lock is something like:
UPDATE TESTWSM.T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG.CHECKNGETLOCK(:B6 , LTLOCK, NEXTVER, :B3 , 0,'UPDATE', VERSION, DELSTATUS, :B5 ), NEXTVER = WMSYS.LT_CTX_PKG.GETNEXTVER(NEXTVER,:B4 ,VERSION,:B3 ,:B2 ,683) WHERE ROWID = :B1
Any help with this will be appreciated. Thanks in advance.

Hi Ben,
Thanks for your quick response.
I've tested your suggestion and it does work with 2 workspaces but the same problem is enountered when additional workspaces are created.
It seems if multiple workspaces are used in a multi user environment, locks will be inevitable which will degrade performance especially if a long transaction is used.
Deadlocks can also be encountered where eventually one of the sessions is rolled back by the database.
Is there a way of avoiding this e.g. by controlling the creation of workspaces and table updates?
I've updated my test case below to demonstrate the extra workspace locking issue.
--change tablespace name as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = name||'changed' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
--end of original test case, start of additional workspace locking issue:
Session 1:
rollback;
Session 2:
rollback;
--update record in both workspaces
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM2');
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = name||'changed2' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this now gets locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--update record 3 in TESTWSM2
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating LIVE
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating TESTWSM1 workspace too - so all have been updated since TESTWSM2 was created
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating every workspace afresh
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changedA' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changedB' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changedC' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;

Lock Table and permit only SELECT-Statement

Hi all,
can I lock a Table and permit only SELECT-statements on a Table?
Regards
Leonid

Hi Kamal,
I would like to configure it in such a way that if I implement the SELECT statement, another user can't insert
a data into the table.
If it is possible, I even the LOCK would like in such a way to configure the fact that the entry of the user arrives into the buffer and if the table is unlocked, all lines from the Buffer again into the table.
I make it in such a way:
SQL Script script_test.sql:
set echo off
set verify off
set pagesize 0
set termout off
set heading off
set feedback off
lock table mytable in share row exclusive mode;
spool c:\Temp\script_info.lst
select id||'|'||dae||'|'||name||'|'||name1||'|'||hiredate
||'|'||street||'|'||nr||'|'||plznum||'|'||city
||'|'||email||'|'||telephon||'|'||cddfeas||'|'||number
||'|'||why||'|'||fgldwer||'|'||wahl||'|'||adress
||'|'||las
from mytable
where las is null
spool off
spool c:\Temp\select_from_all_tables.lst
select *
from all_tables
order by owner
spool off
spool c:\Temp\select1_from_all_tables.lst
select *
from all_tables
order by owner
spool off
update mytable
set las = 'x';
commit;
set feedback on
set heading on
set termout on
set pagesize 24
set verify on
set echo on
Afterwards I start another session:
insert into briefwahl
values(38,'11.06.2003 09:37','Test','Test','01.01.1990',
'Test','12','90000','Test',
'[email protected]','12345657','test','123',
'test','test','test','test',
null);
Then I go into the first session and start script. And I go immediately into the second session and do commit; And although I have the table closed, the new entries are spent also with spool into the .lst-File. Why, I do not understand. And in the table all lines become updated.
Regadrs
Leonid
P.S. Sorry for my English. I have write with translator.

Screen problems - black screen and lock-up (plus HDMI issues)

Hi, I'm not sure if these are related to the same fundamental issue, but they are both serious problems that need resolution.
I have a new mid-2012 MBPretina. I am on all the latest updates (10.8.2).
The first problem is the most recent, and the most serious problem. Since I updated the Java a couple of days ago I've been experiencing random black screens and lock-ups. Essentially, what happens is that sometimes when I perform an action (opening an app, clicking a link on a webpage, performing other kinds of in-app actions, etc.) the computer screen will go black. About half the time I can, through my own memory, try keyboard combinations to quit or force quit the most recently used app (the one where the action was just performed), and I will get some glimpse of the underlying apps, while the menubar and other areas will remain black until I move a window on top of the black space. Sometimes no key combinations work and I am forced to perform a hard restart with the power button. This is a serious issue, obviously, since I will lose current work/progress in my apps. I'm not sure if this is because of the new Java update, or has to do with something else, but it started happening shortly thereafter, over the last 2 days. I work most of my waking day on my laptop, and this "black screen of death" has happened about 5 or 6 times a day.
The second problem I have been experiencing since I starting using my MBPr with external HDMI displays in August/September. The problem is that I will plug the MBPr into an HDMI display, the screen will temporaliy go black, and then bring me to the login screen (as if it's crashing, albeit softly). This happens about 1 out of 4 times nowadays.
How can I fix these problems, especially the first?

UPDATE:
Clearly there's a problem because a third of the way through a clean reinstallation from scratch it black screened again. Hmmmm.
Now this is not good. Problem is I can't rule out potential updates from Apple that might have caused this either.
The search for solutions continues.

How to see lock on table and query?

Hi All,
How do we see lock on table and query?
Thanks,
Rafi

Yes Rafi,
It is working fine at my end. See below:
Opened Session 1 with scott/tiger and:
update emp set ename='xx' where empno=7499;
Opened Session 2 with scott/tiger and:
update emp set ename='xx' where empno=7499;
<<Its lock here>> This session is locked by above one.
Opened Session 3 with sys/pw as sysdba and:
SQL> set serveroutput on
SQL> BEGIN
2 dbms_output.enable(1000000);
3 for do_loop in (select session_id, a.object_id, xidsqn, oracle_username, b.owner owner,
4 b.object_name object_name, b.object_type object_type
5 FROM v$locked_object a, dba_objects b
6 WHERE xidsqn != 0
7 and b.object_id = a.object_id)
8 loop
9 dbms_output.put_line('.');
10 dbms_output.put_line('Blocking Session : '||do_loop.session_id);
11 dbms_output.put_line('Object (Owner/Name): '||do_loop.owner||'.'||do_loop.object_name);
12 dbms_output.put_line('Object Type : '||do_loop.object_type);
13 for next_loop in (select sid from v$lock
14 where id2 = do_loop.xidsqn
15 and sid != do_loop.session_id)
16 LOOP
17 dbms_output.put_line('Sessions being blocked : '||next_loop.sid);
18 end loop;
19 end loop;
20 END;
21 /
Blocking Session : 139
Object (Owner/Name): SCOTT.EMP
Object Type : TABLE
Sessions being blocked : 134
PL/SQL procedure successfully completed.HTH
Girish Sharma

How to fix Action Link Issue in Table and Pivot Table when used Section

My OBIEE Version: OBIEE 11.1.1.6.5
Issue Description: Action links (Navigate to BI Content) doesn't work in PIVOT TABLE or TABLE object when used Section area (one or more columns in Section area).
If you want to recreate this issue please follow next steps:
1.     First of all you have to create one analyse with min 3 columns (for example Time.“Calendar date“, Product.Product, „Base Fact“. Revenue -> from Sample Sales Lite )
2.     From column properties -> Set value Action Link Interaction on some column for example Product.Product (choose Navigate to BI Content -> any created BI report )
3.     Click Results Tab choose Pivot Table and assigned one dimension column to Section area
4.     Click preview icon
5.     When you click on action link nothing happens
6.     If you drug and drop column from Section Area to Excluded, Table or Pivot table Area then Action Link works perfectly
How to fix this issue?
I'll be grateful for any help!

This is Bug:15922681 - ACTION LINK NAVIGATE TO BI CONTENT DOES NOT WORK WITH ATTRIBUTE IN SECTION
Upgrade to 11.1.1.6.6 will fix this issue.

Buffer table and Locking issues

Similar Messages

Maybe you are looking for