Undo retention is set as too less makes flaskback query fails, why?
Hi All,
I got a email that some important records has benn deleted. I tried to use flaskback query to see those deleted records.
I did not found image of table 2 hours older.
query I am using is
select * from bd_owner.sales as of timestamp systimestamp - interval '120' minute;Now my question is that why I am not able to see back in time 2 hours before.
my flaskback setting is
db_flashback_retention_target integer 1440 (24 hours)
db_flash_cache_file string
db_flash_cache_size big integer 0so does this really mean that i can look back old image of data for last 24 hours.
This db is not very active. Undo tablespace is of 2GB size . It was mostly 90% free
Please correct me here..
error i am getting is ora-1555 snapshot too old
ORA-01555: snapshot too old: rollback segment number 26 with name "_SYSSMU26$" too small
Is it due to undo setting not proper
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
undo tablespace RETENTION is NOGUARANTEEquestion
1) shall i set undo retention to GUARANTEE.
Is any perfomance impact of this on database?
2) shall increase the undo_retention (15 minutes) equal to DB_FLASHBACK_RETENTION_TARGET ie 1440 (24 hour)
db details
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for HPUX: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - ProductionThanks In Advance
for answering these questions
Hi,
I think you are hitting the bug
Bug 9212103 Flashback version query omits deleted rows
Versions confirmed as being affected
11.2.0.1
11.1.0.7
Issue fixed in
This issue is fixed in
12.1 (Future Release)
11.2.0.2 (Server Patch Set)
Kind Regards,
Rakesh jayappa
Similar Messages
-
We have a three node 11.1.0.6 RAC.
Each node has a different undo tablespace specified...these parms:
INST_ID NAME VALUE DISPLAY_VALUE
1 db_flashback_retention_target 1440 1440
2 db_flashback_retention_target 1440 1440
3 db_flashback_retention_target 1440 1440
1 undo_management AUTO AUTO
2 undo_management AUTO AUTO
3 undo_management AUTO AUTO
1 undo_retention 64800 64800
2 undo_retention 64800 64800
3 undo_retention 64800 64800
1 undo_tablespace UNDOTBS1 UNDOTBS1
2 undo_tablespace UNDOTBS2 UNDOTBS2
3 undo_tablespace UNDOTBS3 UNDOTBS3
space in each tablespace is plentiful...each at about 11G expandable to 16G. Only 3GB used in one tablespace...100MB in the other two.
retention guarantee is not set on.
notice undo_retention is at 18 hours.
I do the following
SELECT COUNT(*) FROM MYTABLE as of TIMESTAMP to_timestamp(sysdate - 1/24); --- 1 hour ago.
ORA-01555 snapshot too old.
This appears to be a bug....the UNDO tablespaces are never stressed...not even close. undo retention is set to 16 hours....my query only asks for a measly 1 hour ago.
Why snapshot too old?! Why unexpired undo info gone?!
I wonder if undo info is getting spread across the RAC and when I do the flashback query, it only looks at the session's local node and can't find it. But thats not how RAC is supposed to work......Just shooting in the dark.
does db_flashback_retention_target have to be set higher?....doesn't seem from DOCs like that deals with flashback query, just flashback DB.
Anyone know why this is happening...Remember the UNDO tablespaces never get close to their capacity...never have to auto-expand.
I should not have to (and don't want to) set RETENTION GUARANTEE on...don't suggest that....I want to know why this failed without it.
I expect all undo info from 1 hour ago to have been kept if retention is set to 16 hours and the tablespace is not stressed...correct?
Thanks for any Help you can give.
Edited by: user3233984 on Mar 30, 2011 2:50 PMThe big problem with flashback archive tablespaces that I see is that once you place a table into the archive tablespace you cannot alter the table. We have added hundreds of new data columns to our tables over the last couple of years. Some of them have history tables or archived data associated with them.
The new columns are just null in the history and when archived data is retrieved. I see not being able to alter archived tables as a big problem.
As for the OP problem. Delayed block clean up is supposed to no longer be a problem in 11g though we all know how past statements from Oracle on like claims have played out (that is, sometimes what Oracle says is fixed turns out to be only partially fixed or the fix introduced a new problem).
Another possible issue is if Oracle automatic undo managment offlined or dropped any of the undo segments since the segment was not needed. I believe that undo managment is written to the alert log so it should be worth a look.
IMHO -- Mark D Powell -- -
We are noticing some of these snapshot too old errors 01555 errors and we are not making use of any of the flashback functionality so I believe we are only interested in the undo table keeping the undo data while the transaction itself is active to ensure read consistency.
Previously we had undo_retention set to 10800 (3 hours) and I am thinking I should shrink this so that we only keep data as long as the transaction is active. If I set the undo retention length to a value like 300 (5 minutes) and a transaction takes 20 minutes am I going to get snapshot too old errors?
I am hoping the behavior is to keep the transaction data in the undo segment as long as the transaction is active for a minimum of undo_retention time and it would keep making use of space until it runs out of space that is not being used by some other transaction and not being held because of the 5 minutes retention. Is this how it will behave or after the 5 minutes will other transactions be able to overwrite this undo data causing an error even if there is other free space?
Some of the documentation seemed to say the undo_retention is a minimum recommendation to oracle. So if I don't care about flashback at all would a setting like 1 be reasonable assuming it would keep stuff as long as the transaction lasts +1 second(suggesting 1 since 0 means use the default of 900 aka 15 minutes)? I saw some other documentation suggesting setting it to the value of your longest transaction but I surely don't want to keep data from shorter transactions as long as my longest transaction as that would require a much larger undo tablespace so I am trying to figure out the most efficient setting to ensure consistency while being as space efficient as possible.
Thanks,
JaredThank you for all the replys on this thread those plus some stuff I have read in metalink have been very helpful. Have some follow up related questions.
From what I have read when a block is modified it goes into the undo in one of the segments and has an associated SCN number for each change.
1. If one DB connection does a series of updates to a given block and then disconnects (assume each update autocommits) and then the process is restarted and does more updates to the same block would it re-use the existing undo segment? (assuming that no select statements reference this block and cause it to be flushed) Does a new transaction on a given block imply a segment switch is a new select intersecting with a datablock the only thing that would cause it to change segments?
2. In the same scenario as above with a select happening between the two passes I am assuming that the select would cause it to flush the block (update the actual data) and that the second pass of updates on the same block would do the updates in a different undo segment? Does having a higher retention setting make it more likely to keep rotating segments as opposed to overwriting a previous one? In other words if I have my retention set to some very high amount of time like 10 days would it rotate all of the segments for that block before overwriting the first change?
My application currently has one process that does large queries that could last 5 hours or so at worst(all read only). And another process that does only new inserts.
Trying to figure out the exact behavior of how the undo retention manages switching undo segments to determine what is causing our problems. I have noticed on 10g2 that the number of undo segments is 10 and on 9.2.0.5 it was more like 108 or so and it seems like 10 is more likely to get 1555 errors and I am wondering if this is because it is more likely to cycle all segments and start overwriting blocks that are needed for a long running queries consistency.
Thanks,
Jared -
Hi Friends,
Just clarification on undo (11g)
I set undo retention to 15 mins.
user A performs transaction without commit and the old data is in undo for read consistency.
when user B performs select query on user A's transaction it gives old data for read consistency from undo.
The time has excedded 15 mins (say 20 mins) without commit so the data in undo is ready for overwrite
user c performs DML statement and it requires space on undo and the user A transaction's old snapshot in undo is overwritten.
Now user D perform's select query on user A's transaction ( i believe he gets snapshoot too old error as the old data is overwritten) pls confirm?
Now when user A perform's roll back what will happen since the old data is already overwritten in undo (by user c's transaction) how the roll back is performed (or) will he get snap shot too old error?
My question:
if the users's are getting snapshot too old because the data is not available in undo then from where the data is rolled back if the user who initiated the DML(beyond undo retention) performs rollback?
Regards,
DBRead consistency is achieved for committed data by undo_retention parameter exclusively which is specified in seconds ,it determines how much committed's undo data to keep in undo tablespace.Undo retention period mark two state (expired and unexpired) on committed's undo data.Old (committed) undo information that is older than the current undo retention period is said to be expired.Old undo information with an age that is less than the current undo retention period is said to be unexpired.
if (Undo committed data age)< undo_retention then
Undo committed data:='Unexpired'
else
Undo committed data:='Expired'
end if;Whenever there is shortage of undo space then Oracle will first overwrite expired committed's undo data , if the space issue still persist then oracle will start to overwrite unexpired committed's undo data.If yours long running query does not find expired or unexpired committed's undo data then an old snapshot error pop out during the execution of this query.
To safeguard unexpired committed's undo data is called to govern undo_retention,to guarantee the success of long-running queries you can enable retention guarantee.If retention guarantee is enabled, the specified minimum undo retention is guaranteed; the database never overwrites unexpired undo data no matter others transactions fail due to lack of space in the undo tablespace.
Do not relate undo retention period to un committed data.Un committed undo will never overwrite during the life span of yours database instance.
Khurram -
제품 : ORACLE SERVER
작성날짜 : 2004-05-17
PURPOSE
이 문서는 Oracle 10g 에서 자동화된 UNDO RETENTION 기능에 대하여
소개하는 자료이다.
Explanation
- Automatic tuning of undo retention in 10g.
Oracle 9i 에서는 ORA-1555 error가 가끔 발생하여 DBA가 이에 대한
조정을 해줄 필요가 있었다. 그러나, Oracle 10g 부터는 UNDO_RETENTION
에 대한 자동 튜닝 기능을 제공하게 되었다. 따라서, ORA-1555 에러가
발생하지 않도록 자동으로 UNDO RETENTION을 튜닝한다.
- Mandatory setting
1) UNDO_RETENTION=0 (10g: 이 파라미터 값을 0으로 해야 자동 활성화됨)
2) 반드시 SMU(System Managed Undo)를 사용해야 함.
- 자동 튜닝의 방식
UNDO_RETENTION을 0으로 셋팅하면 UNDO_RETENTION의 최소값은 900초가 된다.
즉 15분이다. MMON process가 매 30초마다 query duration을 계산한다.
MAXQUERYLEN 이라는 값을 계산하는데 이 값에 따라서 MMON은
TUNED_UNDORETENTION 이라는 수치를 결정한다. 이것은 새로운 UNDO
RETENTION 값이 TUNED_UNDORETENTION 로 셋팅이 됨을 의미한다.
계산 공식은 다음과 같다.
TUNED_UNDORETENTION = MAXQUERYLEN + 300 Sec.
Example
테스트를 위한 작업 순서는 다음과 같다.
1. 다음 SQL을 이용하여 TB1과 TB2 라는 두 개의 테이블을 생성한다.
create table tb1
(col1 number not null,
col2 number,
col3 number,
col4 number,
col5 char(10),
col6 date,
col7 char,
col8 real,
col9 float,
col10 float(10))
tablespace test1;
begin
for i in 1..250 loop
insert into tb1 values (6,1,3,1,'afdfaa','10-SEP-91','g',11.11,10.11,.11);
insert into tb1 values (7,34,1,23,'faaaa','12-AUG-91','h',11.1,1.11,1.1);
insert into tb1 values (8,91,17,1,'alkaa','10-AUG-87','i',6.11,31.11,0);
insert into tb1 values (9,0,8,1,'adfda','12-AUG-91','j',11.11,11.11,11.11);
insert into tb1 values (10,5,1,1,'advfaa','17-AUG-91','k',1.11,1.11,1111);
insert into tb1 values (11,5,67,1,'acva','13-AUG-91','l',1.11,13.11,13.11);
insert into tb1 values (12,7,1,3,'aadfa','14-AUG-90','m',11.11,11.11,11.11);
insert into tb1 values (13,9,4,1,'ajhka','10-AUG-55','n',11.11,11.41,31.11);
insert into tb1 values (14,1,1,3,'sdda','10-AUG-91','o',11.11,11.11,11.11);
insert into tb1 values (15,6,1,3,'sdd332','10-AUG-91','o',11.11,11.11,11.11);
end loop;
end;
create table tb2
(col1 number not null,
col2 number,
col3 number,
col4 number,
col5 char(10),
col6 date,
col7 char,
col8 real,
col9 float,
col10 float(10))
tablespace test2;
begin
for i in 1..250 loop
insert into tb2 values (16,100,100,100,'aaaa','10-AUG-95','a',111.11,11.11,11.11);
insert into tb2 values (27,200,200,200,'bb','11-AUG-95','b',221.22,22.22,22.22);
insert into tb2 values (38,300,300,300,'ccccccc','12-AUG-99','c',31.333,333.33,3333.3);
insert into tb2 values (40,400,400,400,'dddddddd','12-AUG-99','d',111.11,11.11,11.11);
insert into tb2 values (50,33,10000,1000,'aaa','10-AUG-94','f',11.11,111.11,321.11);
insert into tb2 values (60,1000,3000,10000,'afdfaa','10-SEP-97','g',111.11,144.11,.11);
insert into tb2 values (70,341,10,2310,'fghfgaaaa','12-AUG-98','h',11.1,11.11,1.1);
insert into tb2 values (80,0910000,1780,100,'aallkaa','10-AUG-89','i',611.11,311.11,0);
insert into tb2 values (90,0,80,1000,'adfda','12-AUG-96','j',11.11,11.11,111.11);
insert into tb2 values (100,51,10,1000000,'advfaa','17-AUG-97','k',11.11,11.11,1111);
end loop;
end;
2. 같은 test schema에서 다른 세션을 open한다.
3. test schema에게 DBA 권한을 부여한다.
4. 첫번 째 SESSION에서 다음 SELECT 문장을 수행한다.
SELECT TB1.*, TB2.*
FROM TB1, TB2
WHERE TB1.COL1 > TB2.COL1;
5. 두번 째 SESSION에서 위 4단계 수행후 2~5초 정도 후에 다음 명령을 수행한다.
alter system set "_smu_debug_mode" = 45;
set transaction use rollback segment "_SYSSMU3$";
set echo on;
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
set transaction use rollback segment "_SYSSMU3$";
update tb1 set col1 = col1;
commit;
6. "_SYSSMU3$" 의 사용량을 보기 위해 세번 째 SESSION을 OPEN한다.
7. 세번 째 SESSION에서 다음 query를 수행한다.
select tuned_undoretention, maxquerylen, maxqueryid from v$undostat;
결과는 다음과 같은 형태일 것이다.
===================================
TUNED_UNDORETENTION MAXQUERYLEN MAXQUERYID
2300 2000 gpxxh7pysj4fs
900 1 25z699hs9r3wy
900 1 2syxvjbg8d6s4
900 44 5scq3kj3rm7tz
MAXQUERYLEN 값과 계산된 TUNED_UNDORETENTION 값을 살펴보아야 한다.
(참고) 만약 관련된 query 문을 조회하려고 한다면 다음 SELECT 문을
수행하면 된다.
SQL> Select sql_text from v$sqltext
where sql_id = 'gpxxh7pysj4fs' /* MAXQUERYID value */
8. 다음 SQL 문을 이용하여 SMU 의 증가량을 확인한다.
SQL> select USN, RSSIZE, HWMSIZE, OPTSIZE, SHRINKS, segment_name
from v$rollstat, dba_rollback_segs
where usn=segment_id and segment_name like '%SMU3$';
USN RSSIZE HWMSIZE OPTSIZE SHRINKS SEGMENT_NAME
3 260096 522240 6 _SYSSMU3$
9. Step 5 아래에 있는 script를 반복해서 수행하고, step 8 의 SQL을
다시 반복 수행하면 SMU3 의 증가량을 확인할 수 있을 것이다.
(참고) 이와 같은 Automatic Undo Retention의 튜닝은 ORA-1555 ERROR
발생을 예방해준다. 그러나 undo tablespace가 autoextend off 이면
DML 수행 시 UNDO SPACE 부족과 같은 상황에 처할 수 있다.
UNDO tablespace의 사이즈가 부족하면 UNDO RETENTION 값이 줄어들 수 있다.
어떤 UNDO RETENTION을 가능하게 하기 위해서는 그 만큼의 UNDO 공간이
필요하다. Oracle 9i에서는 DBA가 직접 해주어야 했던 이런 고려를
Oracle Database 10g에서는 Oracle 서버가 대신 해준다.
Reference Documents
<Note:240746.1>Flashback Drop uses recycle bin...
make sure:
- you didn't create table on SYSTEM + SYSAUX tablespaces.
- You didn't use "purge" when you drop table " drop table xxx purge"
Example:
SQL> show parameter undo_retention
NAME TYPE VALUE
undo_retention integer 0
SQL> select table_name,tablespace_name from user_tables where table_name='TT';
TABLE_NAME TABLESPACE_NAME
TT USERS
SQL> drop table TT;
Table dropped.
SQL> desc TT
ERROR:
ORA-04043: object TT does not exist
SQL> FLASHBACK TABLE TT TO BEFORE DROP;
Flashback complete.
SQL> desc TT
Name Null? Type
OWNER NOT NULL VARCHAR2(30)
OBJECT_NAME NOT NULL VARCHAR2(30)
SUBOBJECT_NAME VARCHAR2(30)
Edited by: Surachart Opun (HunterX) on Aug 3, 2009 12:56 PM -
Dear Experts,
Oracle 9.2.0.6 (Hp-ux 11.11).
How undo retention and snapshot too old error are related to each other ?
As per my understanding undo retention is only a request and if a transaction is running out of space, it will use space secured by undo retention.
Thanks & Regards
Sunil Kumaruser13151642 wrote:
Dear Experts,
Oracle 9.2.0.6 (Hp-ux 11.11).
How undo retention and snapshot too old error are related to each other ?
As per my understanding undo retention is only a request and if a transaction is running out of space, it will use space secured by undo retention.
Yes, that's why oracle never said in 9i, where this parameter came into existence for the first time that setting it would completely remove the ora1555 issue. If the space is not there and there are incoming transactions requiring the space for their Undo, Oracle can and will overwrite the previously stored Undo leading to the error. That's the reason, you have the Undo Retention guarantee from 10g onwards which ensures that for the time period mentioned, there won't be any overwriting of the Undo data. But, this comes with an issue as well because since now, there is no overwriting of the previosuly written Undo data. the incoming transactions would fail because they won't be able to log their Undo data anymore.
Aman.... -
UNDO RETENTION is Guarenteed ?
what it means
UNDO RETENTION is Guarenteed
any specific answers appreciatable....
ThanksNot really. You might get ORA-1555 Snapshot Too Old with guaranteed undo retention as well. The cause for ORA-1555 is different.
The guaranteed undo retention guramtees the undo to be available for the duation of time. So it might reduce the chance of ORA-1555; but does not eliminate it.
On the other hand, guanrateed undo also demands more undo space. So if you don't expand the undo tablespace datafile or make it autoextend, the transactions will fail. So, watch out.
HTH.
Arup Nanda -
WAD : Result set is too large; data retrieval restricted by configuration
Hi All,
When trying to execute the web template by giving less restiction we are getting the below error :
Result set is too large; data retrieval restricted by configuration
Result set too large (758992 cells); data retrieval restricted by configuration (maximum = 500000 cells)
But when we try to increase the number of restictions it is giving output. For example if we give fiscal period, company code ann Brand we are able to get output. But if we give fical period alone it it throwing the above error.
Note : We are in SP18.
Whether do we need to change some setting in configuration? If we yes where do we need to change or what else we need to do to remove this error
Regards
KarthikHi Karthik,
the standard setting for web templates is to display a maximum amount of 50.000 cells. The less you restrict your query the more data will be displayed in the report. If you want to display more than 50.000 cells the template will not be executed correctly.
In general it is advisable to restrict the query as much as possible. The more data you display the worse your performance will be. If you have to display more data and you execute the query from query designer or if you use the standard template you can individually set the maximum amount of cells. This is described over [here|Re: Bex Web 7.0 cells overflow].
However I do not know if (and how) you can set the maximum amount of cells differently as a default setting for your template. This should be possible somehow I think, if you find a solution for this please let us know.
Brgds,
Marcel -
Hi All,
I've inherited and Exchange 2010 SP3 UR4 environment that has UM but no Retention Policy has been set. As a result, I have MP3s filling up disk space. Adding to that is that I'm a N00b when it comes to Exchange. I've more or less created
User and Room Mailboxes, etc.
This Retention Policy should address it:
New-RetentionPolicyTag "Voice Mail 60 Day Retention" -Type All -MessageClass voicemail -Comment "Untagged messages removed after 60 days." -RetentionEnabled $true -AgeLimitForRetention
60 -RetentionAction DeleteAndAllowRecovery
Thing is, just like any "set" cmdlet, I prefer to first query like everyone else with a "get" cmdlet.
Do you know if there's a way to query this first?
Thank you very much for your time,
Mr MisterYou mean you want to see if it actually works as expected? In that case I would create the policy and then apply only to one mailbox and see how that goes.
http://technet.microsoft.com/en-us/library/dd298052(v=exchg.141).aspx
Apply a Retention Policy to Mailboxes
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
UNDO retention causing excessive I/O ?
New DBA here.
Quick Summary:
We have an oracle 10gR2 DB on AIX 5.3. OS runs from the box, Database runs from a san. Aside from the DB, there is a web based application running on the box, which uses the DB.
System is dedicated to this application.
We have a consulting company that is making suggestions, and I am not sure about some of them.
When we set up the software, the vendor told us to set up the database with undo retention to 10800. So we did.
Our consulting group is telling me that Undo I/O represents 34% of the total database I/O, and that I should reduce the retention time to 1080. *(they also tell me that the longest running query is 100s; I don't quite understand how this is relevent).
Why would reducing the UNDO retention lenght reduce the UNDO I/O ?First you need to check the concept of UNDO, the main purpose of undo are:
Rollback an active transaction
Recover a terminated transaction
Provide read consistency
Recovery from logical corruptions
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/logical.htm#sthref449
also check undo retention,
The undo retention period indicates the amount of time that must pass before old undo information—that is, undo information for committed transactions—can be overwritten.
As you can see, there's no direct relationship between undo retention and database I/O. Reduce undo retention will not reduce database I/O.
Besides, the UNDO_RETENTION initialization parameter is ignored unless retention guarantee is enabled.
*(they also tell me that the longest running query is 100s; I don't quite
understand how this is relevent).The relevant here is your undo retention should be longer than longest running query (and undo space is big enough to hold the undo data of longest query) , so that you don't have out-of-space conditions in the undo tablespace and ORA-1555 error for consistent reading.
However again, it's relevant to undo setting not database IO. -
Hi All,
I am getting following ORA-01555 error for following sql
ORA-01555 caused by SQL statement below (SQL ID: 9hwwvxc0aa70n, Query Duration=3787 sec, SCN: 0x0001.a84d4a15):
Tue Mar 17 11:38:28 2009
SELECT MSI.SEGMENT1 PART_NUMBER ,REPLACE(MSI.DESCRIPTION,',','.') DESCRIPTION ,MSI.PRIMARY_UOM_CODE UOM ,MSI.UNIT_LENGTH LENG
TH ,MSI.UNIT_WIDTH WEIDTH ,MSI.UNIT_HEIGHT HEIGHT ,MSI.UNIT_VOLUME VOLUME ,MSI.UNIT_WEIGHT NETWEIGHT ,MSI.ATTRIBUTE14 PRICE_C
LASS ,MSI.INVENTORY_ITEM_STATUS_CODE ITEM_STATUS ,( SELECT MSI1.SEGMENT1 FROM MTL_RELATED_ITEMS MRI ,MTL_SYSTEM_ITEMS MSI1 WH
ERE 1=1 AND MRI.RELATIONSHIP_TYPE_ID =2 AND MRI.RELATED_ITEM_ID=MSI1.INVENTORY_ITEM_ID AND MRI.ORGANIZATION_ID=MSI1.ORGANIZAT
ION_ID AND MRI.INVENTORY_ITEM_ID=MSI.INVENTORY_ITEM_ID AND MRI.ORGANIZATION_ID=MSI.ORGANIZATION_ID AND ROWNUM=1 ) SUBSTITUTE_
PNO ,MSI.ATTRIBUTE8 REGISTRATION_DATE ,XXJPM.FOB FOB ,( SELECT QLL.OPERAND FROM QP_LIST_HEADERS QLH ,QP_LIST_LINES QLL ,QP_PR
ICING_ATTRIBUTES QPA WHERE 1=1 AND QLH.NAME='EKK PARTS RETAIL PRICE LIST' AND QLH.LIST_HEADER_ID=QLL.LIST_HEADER_ID AND QLL.L
IST_LINE_ID=QPA.LIST_LINE_ID AND NVL(QLL.PRODUCT_UOM_CODE,'Ea')='Ea' AND NVL(QLL.CONTEXT,'SPARES')='SPARES' AND QLH.LIST_HEAD
ER_ID=QPA.LIST_HEADER_ID
The Query Duration=3787 sec.
My undo retention value is 6000 and my undo tablespace have enough space.
Still I am getting this error,
Can someone help me on this.
Thankshere is some more information on "Retention Guarantee" from the Oracle documentation in case it helps.
Retention Guarantee
To guarantee the success of long-running queries or Oracle Flashback operations, you can enable retention guarantee. If retention guarantee is enabled, the specified minimum undo retention is guaranteed; the database never overwrites unexpired undo data even if it means that transactions fail due to lack of space in the undo tablespace. If retention guarantee is not enabled, the database can overwrite unexpired undo when space is low, thus lowering the undo retention for the system. This option is disabled by default.
WARNING:
Enabling retention guarantee can cause multiple DML operations to fail. Use with caution.
You enable retention guarantee by specifying the RETENTION GUARANTEE clause for the undo tablespace when you create it with either the CREATE DATABASE or CREATE UNDO TABLESPACE statement. Or, you can later specify this clause in an ALTER TABLESPACE statement. You disable retention guarantee with the RETENTION NOGUARANTEE clause.
You can use the DBA_TABLESPACES view to determine the retention guarantee setting for the undo tablespace. A column named RETENTION contains a value of GUARANTEE, NOGUARANTEE, or NOT APPLY (used for tablespaces other than the undo tablespace).
see http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm -
How to change too less than 4seconds...
I have more recordings,
they are less than 4 seconds,
When i want to make a cd of it, it doesn't work,
Because these recordings have to be more than 4 seconds in length.
How can i change this?Many thanks for the useful info from both, Bob Howes & Ryclark
Date: Thu, 4 Nov 2010 09:22:05 -0600
From: [email protected]
To: [email protected]
Subject: How to change too less than 4seconds...
Ryclark is, alas, spot on.
In the bad old days I used to use CD to playback sound effects in the theatre and many of these were less than 4 seconds duration. I used to have to edit in a few seconds silence at the end of all the short effects to keep the CD format happy.
Bob
> -
Essbase Error:Set is too large to be processed. Set size exceeds 2^64 tuple
Hi,
we are using obiee 11.1.1.6 version with essbase 9.3.3 as a data source . when I try to run a report in obiee, I am getting the below error :
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Internal error: Set is too large to be processed. Set size exceeds 2^64 tuples (HY000)
but if I run the same query in excel add in, I am just getting 20 records . wondering why I am getting this error in obiee . Does any one encountered the same issue ?
Thanks In advance,Well if you want to export in I think you have to manually do it.
The workaround it to open your aperture library by right clicking it and show contents...
Then go into your project right click show contents...
In here there are sub folders on dates that the pictures were added to those projects. If you open the sub folder and search for your pictures name it should be in that main folder.
You can just copy it out as you would any normal file to any other location.
Voila you have manually exported out your file.
There is a very similar post that has been close but again you can't export the original file that you are working on - FYI http://discussions.apple.com/thread.jspa?threadID=2075419 -
Query Error Information: Result set is too large; data retrieval ......
Hi Experts,
I got one problem with my query information. when Im executing my report and drill my info in my navigation panel, Instead of a table with values the message "Result set is too large; data retrieval restricted by configuration" appears. I already applied "Note 1127156 - Safety belt: Result set is too large". I imported Support Package 13 for SAP NetWeaver 7. 0 BI Java (BIIBC13_0.SCA / BIBASES13_0.SCA / BIWEBAPP13_0.SCA) and executed the program SAP_RSADMIN_MAINTAIN (in transaction SE38), with the object and the value like Note 1127156 says... but the problem still appears....
what Should I be missing ?????? How can I fix this issue ????
Thank you very much for helping me out..... (Any help would be rewarded)
David CortéYou may ask your basis guy to increase ESM buffer (rsdb/esm/buffersize_kb). Did you check the systems memory?
Did you try to check the error dump using ST22 - Runtime error analysis?
Edited by: ashok saha on Feb 27, 2008 10:27 PM -
SAP Note: 1127156 Result set is too large
Hi,
The note 1127156 explains how to resolve the issue with removing the message "Result Set is too large." I want to check the settings in the template and it gives the following steps but i cannot find the settings on the Analysis web item of the data provider.
Can someone pls help.
Query View
The following steps describe how to change the "safety belt" for Query Views:
1. Use the context menu Properties / Data Provider in a BEx Web Application to maintain the "safety belt" for a Query View.
2. Choose the register "Size Restriction for Result Sets".
3. Choose an entry from the dropdown box to specify the maximum number of cells for the result set.
The following values are available:
Maximum Number
Default Number
Custom-Defined Number
Behind "Maximum Number" and "Default Number" you can find the current numbers defined in the customizing table RSADMIN (see below).
4. Save the Query View and use it in another Web Template.
Many thanksHi,
I was facing the same issue in BEx analyzer 7.0. The query was working fine in BW 3.5 analyzer but gave error in BEx 7.0.
When executed in web, it gave error result set is too large.
The maximum no of cells that can be displayed is 750000.
Please check the result set returned by the query. Also check note Note 1040454 - Front-end memory requirement of the BEx Analyzer.
Some enhancement are planned to be delivered in enhancement package 1.
Regards,
Niraj
Maybe you are looking for
-
Problem with Query Print Layout
Hi, i have this type of problem. I have create a query with 5 fields,i have saved it, and ,after, i have created a report on this query (Query Print Layout). So, i have manipulated the report based on the preferences of the customer. After this opera
-
Import directly to Audio books folder
Hello is there a way to import directly to an assigned folder.( audio books) For example I imported a cd book all the tracks were imported as tracks and could I not sort them out. Is there a purpose for the audio books folder. Thanks to all that help
-
Intra-Discussions URLs = intermittently awry? ("little gray squares")
Hi, Friends! This may be a very naïve question — or it may have been answered 10x over. I've had no success finding a solution after searching herein, so I'm asking for help... Intermittently, "intra-Discussions links" — "text URLs" I've written as l
-
Counting records after a query
I am running a query and I want to display the number of records retrieved during the query. I have researched the COUNT_QUERY built-in and tried to assign the value returned by this built-in to a variable. (It doesn't work.) I have used the the foll
-
How to achieve BPM functionalities in Business Connectors
Hi I would like to ask how BC scenario implements the corresponding BPM scenario in XI. I had to present a white paper on this topic. thanx in advance Prateek