Snapshot log

how do i know how many shapshots and snapshot log are present in perticular schema so i can delete them
does this snapshots takes physical space????

SQL> select name from all_snapshots;
NAME
MV_TBL
SQL> drop snapshot mv_tbl;
Materialized view dropped.
SQL> select master from all_snapshot_logs;
MASTER
SOURCE_TBL
SQL> drop snapshot log on source_tbl;
Materialized view log dropped.
SQL>you can add where owner=<some_user> to the all_snapshots query
you can add where log_owner=<some_user> to the all_snapshot_logs
what ever you do, don't drop the snapshot log using a regular 'drop table' command!
Amiel.

Similar Messages

Import error with snapshot logs

I have an export that is a full from our production database. I'm trying to import a small subset of tables from a user to a different user. One of the tables has a snapshot log against it I believe due to the error msg in the import file. I don't care about the snapshot log I just want to get the table imported. How can I tell import to avoid the snapshot log. If this is not possible, how do I figure out what table it's says can't be found to import into.
IMP log:
. importing TYUADM's objects into DWADM
. . importing table "ZONE" 10583 rows imported
IMP-00017: following statement failed with ORACLE error 942:
"BEGIN SYS.DBMS_REPUTIL.SYNC_UP_REP('TYUADM','ZONE'); END;"
IMP-00003: ORACLE error 942 encountered
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 79
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 157
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 201
ORA-06512: at "SYS.DBMS_REPUTIL", line 616
ORA-06512: at line 1
"BEGIN SYS.DBMS_SNAPSHOT_UTL.SYNC_UP_LOG('TYUADM','ZONE'); END;"
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
ORA-06512: at "SYS.DBMS_ISNAPSHOT", line 108
ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1666
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully

Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.2 - Release: 8.1.7 to 11.2
Oracle Server - Personal Edition - Version: 8.1.7.0 to 11.2.0.2 [Release: 8.1.7 to 11.2]
Oracle Server - Standard Edition - Version: 8.1.7.0 to 11.2.0.2 [Release: 8.1.7 to 11.2]
Information in this document applies to any platform.
Symptoms
You have created a snapshot log:
SQL> connect system/manager
SQL> grant create snapshot to scott;
SQL> connect scott/tiger
SQL> create snapshot my_snap as select * from emp;
SQL> create snapshot log on scott.emp;
You run a user level export:
% exp system/manager file=exp_s.dmp log=exp_s.log owner=scott
Export: Release 9.2.0.6.0 - Production on Tue Dec 28 08:06:12 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
Export terminated successfully without warnings.
You run a user level import, e.g. in a different database:
SQL> connect system/manager
SQL> create user hugo identified by hugo default tablespace
users temporary tablespace temp
quota unlimited on users;
SQL> grant create session, create table, create snapshot
to hugo;
% imp system/manager file=exp_s.dmp log=imp_s.log fromuser=scott touser=hugo
Import: Release 9.2.0.6.0 - Production on Tue Dec 28 08:08:16 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
. importing SCOTT's objects into HUGO
. . importing table "BONUS" 0 rows imported
. . importing table "DEPT" 4 rows imported
. . importing table "EMP" 14 rows imported
. . importing table "MLOG$_EMP" 0 rows imported
. . importing table "MY_SNAP" 14 rows imported
. . importing table "SALGRADE" 5 rows imported
IMP-00017: following statement failed with ORACLE error 942:
"BEGIN SYS.DBMS_SNAPSHOT_UTL.SYNC_UP_LOG('SCOTT','EMP'); END;"
IMP-00003: ORACLE error 942 encountered
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1589
ORA-06512: at line 1
Note that the line number in the first ORA-6512 error my differ between versions:
- in 8.1.7.4.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1033
- in 9.2.0.6.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1589
- in 10.1.0.3.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1599
- in 10.2.0.4.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1666
Also note that the same errors occur when the export was done with a table level export.
If the user SCOTT (FROMUSER) does not exist in the target database, import aborts with:
"CREATE SNAPSHOT LOG ON "SCOTT"."EMP" WITH PRIMARY KEY EXCLUDING NEW VALUES"
"USING ("MLOG$_EMP", (...left_out...))"
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
IMP-00000: Import terminated unsuccessfully
Changes
The information in this article applies to:
- Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.x
- Oracle Server - Personal Edition - Version: 8.1.7.0 to 11.2.0.x
- Oracle Server - Standard Edition - Version: 8.1.7.0 to 11.2.0.x
This problem can occur on any platform.
Cause
Snapshots, snapshot logs, and related items are exported with the schema name explicitly given in the DDL statements, therefore, snapshots and their related items cannot be imported into a different schema.
If you attempt to use FROMUSER and TOUSER to import snapshot data, an error will be written to the Import log file and the items will not be imported.
Solution
It is expected behavior that the snapshot log cannot be imported with a FROMUSER and TOUSER import. Therefore the errors should either be prevented from happening, or be ignored:
1. Either delete the snapshot logs before the export takes place. Then run the export and import. After import completes, re-create the snapshot logs manually, and if necessary, perform a refresh of the snapshot.
2. Or ensure that the FROMUSER (SCOTT in this example) exists in the target database, so the import session does not abort with the IMP-0 error (Import terminated unsuccessfully). During the import, ignore the errors that are related to the snapshot logs. After import completes, re-create the snapshot logs manually, and if necessary, perform a refresh of the snapshot.

CREATE MATERIALIZED VIEW LOG ON / SNAPSHOT LOG ON

HI,
Is there any difference between create materialized view log on and creat snapshot on.
Did some googling, found out that: A snapshot log is a table associated with
the master table of a snapshot and Is used for refresh the master table\'s snapshots.
Materialized view log is a table associated with the master table of a materialized view. Seem like the same.
By the way, are these tables important? Will my database function as normal without these view log.
regards,
becks

Where did you pick up this syntax from ?
The MV Log that will be created on DOCUMENT will be called MLOG$_DOCUMENT.
So, the correct syntax is :
create materialized view log on DOCUMENT with primary key;this will create a "table" called MLOG$_DOCUMENT which serves as the Materialized View Log on the real table called DOCUMENT. This will allow you to create one or more Materialized Views based on DOCUMENT, which can be fast refreshed because of the presence of the MV Log. For example :
create materialized view MV_DOCUMENT refresh fast on demand as select DOC_ID, DOC_DATE from DOCUMENT;(i.e. assuming you want an MV that has only two columns from the table DOCUMENT.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Exporting snapshot logs...and terminates with unsuccessfull

Hi all,
i'm getting this error when i try to export a user in oracle 10g.
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
EXP-00008: ORACLE error 1455 encountered
ORA-01455: converting column overflows integer datatype
EXP-00000: Export terminated unsuccessfully.
i have one materialized view inside the user. the snapshot table having more than 500 rows of data.
when i drop the materialized view, i can able to export successfully.
how can i export a user having a materialized view. help me.

thanks robert...thanks for ur timely reply....
i had a very rough time with this export since today morning.......
can i use this format....
expdp username/password FULL=y INCLUDE=GRANT INCLUDE=INDEX DIRECTORY=dpump_dir1 DUMPFILE=dba.dmp CONTENT=ALL
in the database there's no directory. can i use dpump_dir1 as dirrectory.....
Edited by: 887268 on Dec 6, 2011 5:06 AM

Snapshot Logs not being purged

Hi All,
I have a problem where my snapshot logs are not being purged due to materlized veiw dropped from the remote site.
I have looked at DBMS_SNAPSHOT.PURGE_SNAPSHOT_FROM_LOG porcedure to remove the orphaned entries in materialized view logs.
I want to execute this procedure based on the snapshot ID from SYS.SLOG$ using the snapshot_id parameter. Since the target snapshot is not listed in the list of registered snapshots (DBA_REGISTERED_SNAPSHOTS).
Please find the results of the below query to determine which entries in SYS.SLOG$ at the master site are no longer being used.
SELECT NVL (r.NAME,'-') snapname
, snapid
, NVL (r.snapshot_site, 'not registered') snapsite
, snaptime
FROM SYS.slog$ s
, dba_registered_snapshots r
WHERE s.snapid = r.snapshot_id(+) AND r.snapshot_id IS NULL;
SNAPNAME     SNAPID     SNAPSITE     SNAPTIME
-     435     not registered     27/09/2010 22:11
-     456     not registered     27/09/2010 22:11
Please let me know if there is any other method to purge the logs safely?

DBMS_MVIEW.PURGE_MVIEW_FROM_LOG is overloaded.
If you have the MVIEW_ID, you do not hvae to specify the (MVIEW_OWNER, MVIEW_NAME, MVIEW_SITE) parameters.
Check the PLSQL Procedures documentation on DBMS_MVIEW.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Queries about snapshots and snapshot logs in Oracle Ebusiness Suite

Hi ,
We are running Oracle E-business Suite 11.5.8, and have noticed some on-demand snapshots with associated snapshot logs.
The reason we have noticed them is that the snapshot logs have grown large in size (up to 20GB).
What we need to know is why are they growing. As they are on-demand snapshots, something need to refresh them manually, but we do not know what.
Can we purge these logs and reclaim the space, or is there a process involved that we are not doing?
The snapshot details are as follows:
Snapshot log: INV.MLOG$_MTL_SYSTEM_ITEMS_B
Sanpshot table: INV.MTL_SYSTEM_ITEMS_B
Snapshot: INV.MTL_SYS_ITEMS_SN
Snapshot log: INV.MLOG$_MTL_DEMAND
Sanpshot table: INV.MTL_DEMAND
Snapshot: INV.MTL_DEMAND_SN
Snapshot log: INV.MLOG$_MTL_SUPPLY
Sanpshot table: INV.MTL_SUPPLY
Snapshot: INV.MTL_SUPPLY_SN
Regards.

HI,
Please go through below MOS docs:-
When do Snapshot Logs get Purged [ID 35217.1]
SNAPSHOT LOGS GROWS DUE TO MISSING/INVALID SNAPSHOT [ID 1031924.6]
How To Improve the Performance of the Refresh Collection Snapshots When Running Very High Volumes [ID 550005.1]
MLOG$_ENI_OLTP_ITEM_STAR is Growing too Large, can it be Truncated? [ID 367693.1]
Materialized View Refresh : Log Population and Purge [ID 236233.1]
Refresh Collection Snapshots Performance - Managing MLOG$ Tables and Snapshots for Data Collections [ID 1063953.1]
Thanks,
JD

SNAPSHOT LOG의 데이타가 지워지지 않는 이유와 강제로 지우는 방법 (V7 ~ V8I)

제품 : ORACLE SERVER
작성날짜 : 2002-05-09
SNAPSHOT LOG의 데이타가 지워지지 않는 이유와 강제로 지우는 방법
(V7 ~ V8I)
====================================================
PURPOSE
사용하고 있는 snapshot의 refresh에는 이상이 없는데 master table의
sanpshot log가 지워지지 않고 계속 늘어만 가는 경우가 있을 수 있다.
이러한 경우 master site의 snapshot log가 증가하면서 space문제를
발생시킬 수도 있고, log의 내용을 refresh해가는 속도도 문제가 될 수
있으므로 여기에서는 그 원인과 조치 사항을 정리한다.
Explanation
1. snapshot log의 데이타가 지워지는 원리
snapshot log의 데이타가 지워지는 순간은 snapshot의 refresh time 때,
refresh 후, 해당 데이타에 대해서 MLOG$_<table_name>내의 SNAPTIME과
SYS.SLOG$의 해당 master table에 대한 snapshot들의 SNAPTIME을 비교해 보아
SYS.SLOG$.SNAPTIME이 MLOG$_<table_name>.SNAPTIME보다 미래이거나 같으면
그때 해당 데이타를 지우게 되는 것이다.
즉 다음 조건을 만족하는 때이다.
SYS.SLOG$.SNAPTIME >= MLOG$_<table_name>.SNAPTIME
그 이유는 snapshot log의 각 데이타는 master table에 연결된 여러 snapshot 중
첫 snapshot의 refresh시에만 refresh해당 시간이 SNAPTIME에 설정되고,
그 이후에 같은 데이타를 다른 snapshot 이 refresh해가도 값이 변경되지
않는다.
아무도 refresh하지 않은 경우는 default로 Oracle7의 경우 null이고,
Oracle8의 경우는 4000년 1월 1일로 설정된다.
SYS.SLOG$의 경우는 master table에 대해 연결된 모든 fast refresh로
refresh해가는 snapshot의 정보가 포함되어 있는데 각 snasphot이 refresh해
갈때마다 해당 snapshot에 대한 SNAPEIME이 변경된다.
그러므로 모든 snapshot이 snapshot log의 해당 레코드를 refresh해가는 경우
SYS.SLOG$의 SNAPTIME은 해당 MLOG$_<table_name>의 해당 레코드의 SNAPTIME
보다 미래이거나 같게 된다.
만약 SYS.SLOG$의 특정 snapshot의 SNAPTIME이 과거인채로 계속 refresh를
안해간다면 그래서 이 값이 snapshot log의 SNAPTIME보다 더 과거라면,
결국 해당 데이타를 refresh해가지 않은 snapshot이 존재하지 않는다는
것이므로 snapshot log의 데이타는 지워질 수 없는 것이다.
이러한 현상이 발생하는 경우는 master table에 연결되어 있는 하나의
snapshot site가 snapshot을 drop하지 않은 상태에서 장기간 데이타베이스
자체를 down시켜 둔 채 사용하지 않거나 아예 database를 remove시킨 경우이다.
그외에도 해당 master table에 snapshot을 test하다가 지우지 않고
그대로 둔 경우 등 이러한 문제는 실제 자주 발생하는 편이다.
2. snapshot log의 데이타를 강제로 지우는 방법
이렇게 사용하지 않는 snapshot으로 인해 비정상적으로 snapshot log의 크기가
커지는 경우, 가장 쉽게는 해당 snapshot을 찾아 drop해주면 문제는 바로
해결된다.
(1) snapshot 확인하는 방법
많은 경우 이러한 방치된 snapshot이 존재하는지 자체를 몰라 snapshot log가
계속 증가하게 되는데 이때는 다음과 같이 master site에서 snapshot 정보들을
확인할 수 있다.
- Oracle7의 경우:
Oracle7에서는 해당 master table에 걸려있는 모든 fast refresh의 snapshot의
정보를 확인할 수 있는 view는 SYS.SLOG$뿐이었다. 예를 들어 master table
이름이 DEPT인 경우 조회 방법은 다음과 같다.
SQL>connect sys/manager
SQL>select * from sys.slog$ where master = 'DEPT';
이 경우 snapshot을 나타내는 column은 SNAPSHOT으로 날짜로 표시된다.
이 snapshot을 실제 snapshot site에서 확인하려면 예상되는 snapshot
site에서 다음과 같이 조회하여 확인할 수 있다.
SQL>select * from sys.snap$ where master = 'DEPT';
- Oracle8의 경우
Oracle7에서는 위와 같이 snapshot의 정보를 master site에서 확인하는
것이 번거로운 문제점이 있어서 Oracle8부터는 snapshot을 나타내기 위한
snapshot id라는 개념이 추가되었고,
DBA_REGISTERED_SNAPSHOTS view가 생성되어 이 view를 통해 쉽게 snapshot를
찾는것이 가능해 졌다.
SQL>select snapid from sys.slog$ where master = 'DEPT';
SQL>select * from dba_registered_snapshots
where snapshot_id=위에서 확인한 번호;
이렇게 확인하면 해당 snapsot이 어느 site에 존재하는지에 대한 master
site의 database link이름 등도 확인 가능하다.
(2) 강제로 snapshot정보를 master site에서 제거하는 방법
위와 같이 확인하였는데도 snapshot을 snapshot site에서 직접 drop할 수
없는 환경이라면, master site에서 해당 snapshot에 대한 정보를 아예 지워
과거의 SNAPTIME을 가지는 snapshot이 SYS.SLOG$에 남지 않게 하면 된다.
SLOG$는 dictionary table이므로 바로 delete문장을 이용하여 해당 정보를
지워서는 안되며 다음과 같은 package를 이용한다.
- Orcle7의 경우:
SQL>exec DBMS_SNAPSHOT.PURGE_LOG('DEPT',2);
해당 master table에 걸려 있는 snapshot중 가장 과거의 SNAPTIME을 가지는
몇개의 snapshot정보를 지울 것인가를 지정하는 방식이다.
이 예의 경우는 DEPT table에 걸려있는 snapshot중 가장 이전에 refresh해간
두개의 snapshot의 정보를 master site의 SYS.SLOG$ 에서 제거한다.
- Oracle8의 경우:
Oracle7에서도 앞에서 설명한 DBMS_SNAPSHOT.PURGE_LOG는 여전히
사용가능하다.
그 외에 Oracle8에서 새로 추가된 snapshot id를 이용한 다음과 같은
package를 사용가능하다.
PROCEDURE PURGE_SNAPSHOT_FROM_LOG
Argument Name Type In/Out Default?
SNAPSHOT_ID BINARY_INTEGER IN
SNAPOWNER VARCHAR2 IN
SNAPNAME VARCHAR2 IN
SNAPSITE VARCHAR2 IN
예를 들어 다음과 같이 사용하면 된다.
SQL>exec DBMS_SNAPSHOT.PURGE_SNAPSHOT_FROM_LOG
(10, 'SCOTT', 'DEPT_SNAP', 'SNP8I.WORLD');

Snapshot log and unused space

I have a snapshot log that is big in size, yet empty. How can i shrink the shapshot log smaller ? Looking for the comparable command for a snapshot that we use for a table - by truncating the table. How do we do it in the snapshot/materialized view world ? I don't want to drop and recreate the snapshot log either.......at least not, if i can help it.
Using Oracle 9.2 here on unix platform.

Question: Do you understand why the table, without an index, has 32KB assigned and 4KB used?
Answer: ASE will allocate an extent (8x 4KB pages = 32KB) when the table is created, and then assign (ie, 'use') one of those pages for immediate use by the table
Question: What happens when an index is created?
Answer: ASE will also allocate an extent (8x 4KB pages = 32KB) when the index is created, and then assign (ie, 'use') one of those pages for immediate use by the index
If you run 'sp_spaceused tmp,1' you'll get a detailed breakdown of allocated/used/unused space for each index.
NOTE: If you're running ASE 15.7 ESD#2 (or higher), the 'create table' command has a 'deferred_allocation' option that delays the allocation of an extent (for the table and each index) until the first row is inserted.

How Oracle process Snapshot log?

Hello,
we are updating a column in a very large table that will result in a very large mlog$.
The column is not a part of the snapshot.
We have only one simple snapshot that references this table.
The testing proved that even this column is not a part of the snapshot Oracle will have to process the mlog$ file anyway.
Just wonder what will be the process in this case?
We need to know this to anticipate possible problems with long refresh.

Make a
desc your_Mlo$_table
You will this table has a column CHANGE_VECTOR$$ of type RAW
I found no documentation of the content of this column.
Probably it contains only the changes coded in a binary format. That's probably a very perfomant solution in general, but in your specific case maybe a hand-made special replication-solution could be better.
The hand-made solution can be done like this: A Trigger in the primary-database fires only changes you would to propaged, that is changes on columns you also have on the replication site. The trigger inserts the changes in a self-made log-table. This log table could have the column that should be replicated. Just insert new:column. You must also have the ability to replicated deleted. On the replication site you can create a stored-procedure, which makes a select on your log-table, makes the changes on the replication-site an deletes the replicated records on the primary-site.

10g Refresh Snapshot log question

Hi,
I need to run complete refresh on a materialized view log.
BEGIN
DBMS_SNAPSHOT.REFRESH(
LIST => 'XYZ_DETAIL'
,METHOD => 'C'
,PUSH_DEFERRED_RPC => TRUE
,REFRESH_AFTER_ERRORS => FALSE
,PURGE_OPTION => 1
,PARALLELISM => 0
,ATOMIC_REFRESH => TRUE
,NESTED => FALSE);
END;
I would like to Refresh it with PARALLELISM => 8 , and after the rebuild will finish
i want to set it back to serial (e.g: PARALLELISM => 0).
Is there an ALTER command that i can use ?
Please explain how to do that.
Thanks.

For the specific 10g case of
BEGIN
DBMS_SNAPSHOT.REFRESH(
LIST => 'XYZ_DETAIL'
,METHOD => 'C'
,PUSH_DEFERRED_RPC => TRUE
,REFRESH_AFTER_ERRORS => FALSE
,PURGE_OPTION => 1
,PARALLELISM => 0
,ATOMIC_REFRESH => TRUE
,NESTED => FALSE);
END;
and using PARALLELISM of 8 for a specific refresh
can you tell us what are the differences in Materialized Views , say between
10gR1 and 10gR2 if you can't tell us the differences between 8i and 10g ?
Message was edited by:
Hemant K Chitale

Can not refresh snapshot changes after importing data of master site

Hello !
I have two database computer,one as master site,one as snapshot site.Because the error of the hard disk of master computer,I use the exporting data file to recover my database.after importing ,I found I can't refresh the refreshgroup on snapshot,who can tell me why?
thinks in advance!
(exp system/manager full=y inctype=complete file='/home/save/backdata/xhsdcomp.dat')
(imp system/manager inctype=system full=Y file='/home/save/backdata/xhsdcomp.dat'
imp system/manager inctype=restore full=Y file='/home/save/backdata/xhsdcomp.dat')
null

You haven't listed the errors that you're receiving when attempting to refresh your refresh group, but if your snapshots are attempting to fast refresh, I suspect it's because the creation timestamp of the snapshot log on the master site is newer than the creation timestamp of the snapshot. In this case you will need to do a complete refresh of the snapshot (or drop and recreate the snapshot) before you will be able to fash refresh it again.
If this is not the case, please post the errors you are receiving when you attempt to refresh the refresh group.
HTH,
-- Anita
Oracle Support Services
null

New rows become deleted from snapshot sites after refresh

Hi buddy
I am facing problem in snapshot at snapshot sites.
I have oracle 8.0.5 4 database server machines.
all servers machines have O.S windows 2000 advance server
all servers machine have same oracle version ( 8.0.5 ).
there is Site A ( Master site ) site B ( snapshot site ) Site C ( snapshot site).
snapshot has been created at all snapshots sites ( B,C and at D)
snapshot log against each table are also present at master site ( Site A )
refresh group is present at snapshot site.
these are working since feb-2002 successfully. now problem occur in these sites if some miner issues comes then it has been resolved successfully.
Replication parameter in init.ora all all sites are as follows
global_names = true
job_queue_processes = 2
job_queue_interval = 60
job_queue_keep_connections = false
distributed_lock_timeout = 60
distributed_transactions = 16
open_links = 4
snapshot_refresh_interval = 60
snapshot_refresh_keep_connections=false
snapshot_refresh_processes = 2
few days ago one problem occurs in master site A. it become crashed. we did its recovery from previous night backup ( cold backup).
Now all branches are working. but my current problem is that we have 20 tables in replication.It is a snapshot replication old version of materialized view.
when site B start refresh procedure then it show message procedure successfully completed.
it show no error message.
but when we check no of rows at snapshot site ( site b )
all new rows which were inserted at snapshot ( site b ) after previous refresh has been deleted.
mean all data which is inserted after previous refresh command has been finished. but data which is inserted at master site is present at snapshot site after refresh.
this problem is present at all the snapshot sites ( site B, Site C and site D).
database link is also present from master to snapshot site anf from snapshot to master. but problem is still suspended.
i have checked at all snapshot site and master site there is no invalid procedure or package.
there is no error message in alert file at all site.
if any body has its solution kindly told me.
thanks in advance
Abdul Hameed
[email protected]

This is still going on when the page fails the call to getCurrentRow().refresh(Row.REFRESH_REMOVE_NEW_ROWS) goes out to lunch and stops processing for the rest of the function. I tried adding a try catch around it but nothing is caught and the function still fails.
getSiteMealLogsV().getCurrentRow().refresh(Row.REFRESH_REMOVE_NEW_ROWS);
---Stops working here -----
getSiteMealLogsV().clearCache();
getDBTransaction().commit();
Jim

Why??? Simple snapshot can not refresh automatically, but can refresh manually.

Server 1 : Oracle 7.3.4 (as a Master site)
Server 2 : Oracle 7.3.4 (as a Snopshot site)
Client PC: SQL*Plus (Oracle 7.3.4 Client)
Step 1: on Client PC, start 2 SQL*Plus dialog Windows,
one(Window A) for <Server 1> , another(Window B) for <Server 2>;
Step 2: on <Window A> do:
SQL>connect scott/tiger@Server1
SQL>CREATE SNAPSHOT LOG ON scott.dept ;
SQL>select * from dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
Step 3: on <Window B> do:
SQL>connect scott/tiger@Server2
SQL>CREATE DATABASE LINK oracle USING 'Server1';
SQL>CREATE SNAPSHOT all_dept REFRESH fast
start with sysdate NEXT SYSDATE+1/(24*60)
AS SELECT * FROM scott.dept@oracle;
-- refresh interval: 1 minute
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
Step 4: on <Window A> do:
SQL>insert into dept values (50,'MMMMMM','NNNNN');
SQL>commit;
SQL>select * from dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
50 MMMMMM NNNNN
<one or two minutes later ... ... >
Step 5: on <Window B> do:
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
conclusion: Simple snapshot can not refresh automatically ???????
SQL>exec DBMS_SNAPSHOT.REFRESH( list => 'all_dept',method => 'F');
SQL>select * from all_dept;
DEPTNO DNAME LOC
10 AAAAAA AAAAA
20 BBBBBB AAAAA
30 CCCCCC AAAAA
50 MMMMMM NNNNN
conclusion:Simple snapshot can refresh manually.
How to solve this problem?????
Thank you very much
Zhang Ming-an

When you are manually refreshing the snapshot as scott/tiger, and your database link was defined with a 'connect to/identified by ' clause, your login credentials will be scott/tiger. When the refresh happens from the job queue, it does not use those credentials, It uses some default set. What you should probably do is:
1. create public database link Oracle using 'server1';
2. as scott/tiger, create database link Oracle connect to scott identified by tiger;
3. your automatic refresh should work now.

Query on Materialized view and materialized view log

I am creating a materialized view something like this.but getting following error:
ERROR at line 1:
ORA-12032: cannot use rowid column from materialized view log on "SCOTT"."EMP"
SQL> create snapshot log on scott.emp;
Materialized view log created.
SQL> create materialized view scott_emp refresh fast on demand as select deptno,sum(sal) sum_sal from scott.emp group by deptno;
ERROR at line 1:
ORA-12032: cannot use rowid column from materialized view log on "SCOTT"."EMP"
Note when i have my query in materialized view as "select * from emp;" in place of
"select deptno,sum(sal) sum_sal from scott.emp group by deptno;" This code works fine.
How do i have a materialized with with a group by clause.
Thanks in Advance

Got the answer myself.
I wasnt adding all the required columns.
CREATE MATERIALIZED VIEW LOG ON scott.emp
WITH SEQUENCE, ROWID (<all the required columns>)
INCLUDING NEW VALUES;
Anyways,
Thanks guys...

Snapshot fast refresh performance

I have a master table with a snapshot log
on the primary database (8.1.6 Oracle and
AiX). There are 20,000 rows in the snapshot
log which take about 6 hrs to perform a fast
refresh to a snapshot database on the same
set up.
i am looking for some ways to tune the snapshot to decrease the time of the refresh.

The refresh time is primarily dependent upon the speed of the remote connection. Also it is not so much the number of rows as it is the size of the rows. As far as tuning the refresh you can check to see if the master snapshot log HWM has grown very large. The refresh will perform a full table scan when it determines which rows it needs to refresh.

Snapshot log

Similar Messages

Maybe you are looking for