Problem with Total Recall (11gR2)
edited Sep 26, 2010 10:34PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
Hi all, I'm facing with a problem using Total Recall on 11gR2, with UNDO_MANAGEMENT = AUTO (of course!).
I've previously:
1) created a new tablespace named RECALL, segment space management AUTO
2) created a flashback archive FLA based on RECALL tablespace, retention 5 year
3) enabled flashback archiving on FLA for MYTABLE table (ALTER TABLE MYTABLE FLASHBACK ARCHIVE FLA), whose structure is
KEY NUMBER (primary key)
DESCRIPTION VARCHAR2(50)
Then, I've started with my DML activity on MYTABLE, committing every single statement:
INSERT INTO MYTABLE (KEY, DESCRIPTION) VALUES (1, 'John');
UPDATE MYTABLE SET DESCRIPTION = 'Jim' WHERE KEY = 1;
DELETE MYTABLE WHERE KEY = 1;
Finally, I've started with my check on the historical value with a SELECT ... VERSIONS BETWEEN, based both on TIMESTAMP and SCN.
1) created a new tablespace named RECALL, segment space management AUTO
2) created a flashback archive FLA based on RECALL tablespace, retention 5 year
3) enabled flashback archiving on FLA for MYTABLE table (ALTER TABLE MYTABLE FLASHBACK ARCHIVE FLA), whose structure is
KEY NUMBER (primary key)
DESCRIPTION VARCHAR2(50)
Then, I've started with my DML activity on MYTABLE, committing every single statement:
INSERT INTO MYTABLE (KEY, DESCRIPTION) VALUES (1, 'John');
UPDATE MYTABLE SET DESCRIPTION = 'Jim' WHERE KEY = 1;
DELETE MYTABLE WHERE KEY = 1;
Finally, I've started with my check on the historical value with a SELECT ... VERSIONS BETWEEN, based both on TIMESTAMP and SCN.
0