Updating snapshots

Hello, We will be using basic replication as we just need the
data to go from our master tables to our snapshots. The thing is
we need to then update some of the snapshots from the snapshot
database and not send it back to the master tables.
I was thinking of moving the data from the snapshot to a
updatable table and then we could add our new data to the
updatable table. I would just need to move the changed data to
the new table. Any ideas.
Craig

It's a READ-ONLY snapshot for a reason :)
One thing you could do is create a snapshot, create a separate
table with you "changes" and then create a view on top of those
two tables to join the data. Obviously, this only works if you
are inserting data and not updating existing rows.

Similar Messages

(V8.1 REPLICATION) UPDATABLE SNAPSHOT환경 구축을 위한 초기 작업

제품 : ORACLE SERVER
작성날짜 : 2001-07-19
(V8.1 REPLICATION) UPDATABLE SNAPSHOT환경 구축을 위한 초기 작업
=============================================================
1. 개요
=======
Symmetric Replication의 한 종류인 updatable snapshot환경의 구축을 위해서는
replication manager를 사용하도록 한다. 이 문서는 replication manager사용을
통해 snapshot group및 object 등을 등록하고 관리하기 이전에 master및 snapshot
site에서 미리 설정되고 수행되어야 하는 작업들을 정리한다.
이중 일부 작업은 replication manager를 통해서도 구현이 되지만, 정확한
수행이 요구되어 지는 작업에 대해서는 이 문서에서와 같이 직접 SQL command를
통해 수행되어지는 것이 권고된다.
Oracle 8.1.x부터는 snapshot과 materialized view가 동의로 사용되어지나, 이
문서에는 snapshot으로 표시한다.
2. Init.ora parameters
======================
아래와 같은 initialisation parameter들이 추가되거나 수정되어져야 한다.
아래의 설정은 master site와 snapshot site모두 설정이 필요하며, master site가
하나뿐인 경우는 job_queue부분과 parallel_ parameter의 경우는 설장할 필요가
없다.
Parameter 이름 권장되는 초기 값
COMPATIBLE 8.1.5.0.0 이상
SHARED_POOL_SIZE 20M ~ 40M 정도가 추가로 요구
PROCESSES 현재 값에서 12정도 추가
GLOBAL_NAMES 반드시 TRUE
OPEN_LINKS 4, 추가되는 master site당 2 증가
DISTRIBUTED_TRANSACTIONS 최소 5 이상 (기본값은 trsactions/4)
가되는 master site당 2 증가
REPLICATION_DEPENDENCY_TRACKING TRUE
아래의 값은 상황에 맞게 조정하여 사용한다.
JOB_QUEUE_INTERVAL 10 초
JOB_QUEUE_PROCESSES 3, 추가되는 master site당 1씩 증가
PARALLEL_MAX_SERVERS 10
PARALLEL_MIN_SERVERS 2, max server의 갯수와 동일한것이 권장
parallel propagation을 사용하지 않고자
하면 설정하지 않는다.
SNAPSHOT_ 로 시작하는 parameter나 JOB_QUEUE_KEEP_CONNECTIONS parameter는
Oracle 8.1에서는 없어졌으므로 지정하지 않도록 한다.
3. Tablespace 요구 사항
=======================
다음은 replication을 사용하기 위해 추가적으로 필요한 tablespace용량이다.
Tablespace 권장사항
SYSTEM 최소 40 Mb free space
ROLLBACK SEGMENTS 최소 30 Mb free space
TEMPORARY 최소 20 Mb free space
4. Replication Catalogue 설치
==============================
database생성시에 replication catalog를 설치하지 않았다면, Database
Configuration Assistant 를 이용하여 Advance Replication Option부분을
database에 추가하도록 하거나, 아니면 다음과 같이 작업한다.
cd $ORACLE_HOME/rdbms/admin
sqlplus internal
SQL>spool rep.log
SQL>@catrep
SQL>spool off
이 script는 약 1시간 정도 수행되며, spool을 받아 수행에 문제가 있었는지
이후에 확인하도록 한다.
[주의] 이 script를 수행하게 되면, replication관련 table과 queue등이 system
owner로 생성되게 된다.
그러므로 이후에 replication작업이 일시 중단되어 queue가 커지게 되면,
system user의 default tablespace에 부담이 되므로 system owner의
default tablespace를 tools나 그외 replication관리를 위한 별도의
table로 일시 지정하도록 한다.
SQL>ALTER USER sysem DEFAULT TABLESPACE REPTBS;
catrep의 수행이 끝나면 spool로 생긴 rep.log도 확인하여 보고, 아래 문장을
통해 invalid상태인 object를 확인하고 재 compile을 시도한다.
SQL> SELECT OWNER, OBJECT_NAME FROM ALL_OBJECTS
WHERE STATUS = 'INVALID';
이때 만약 SYS나 SYSTEM package의 body가 invalid로 나타나면 다음과 같이 재
compile을 시도한다. package body만 invalid인데 aler package문장에서 compile
body대신 compile이라고만 하면 그 package에 대한 definition이 변경되어,
이 package와 dependency관계에 있는 다른 object도 invalid상태가 되도록 한다.
작업이 성공적으로 끝났으면, system user의 default tablespace의 원래대로,
tool나 system으로 수정한다.
SQL> alter user system default tablespace system;
5. Setup NET8
=============
Replication환경에 포함된 모든 server는 listener를 구동하도록 하며, snapshot
site에서는 master site를 가리키는 service alias를 tnsnames.ora file에 등록하
도록 한다.
또한, replication manager를 사용하는 client도 tnsnames.ora file에 master와
snapshot site와 연결가능하도록 service alias를 net8 easy configuration등을
통하여 등록하도록 한다.
6. Replication Manager Setup Wizard
===================================
위의 작업이 모두 끝났으면 앞으로의 작업은 replication manager를 통해서도
수행 가능하다.
그러나 이 문서에 포함된 내용은 replication환경 설정시 한번만 필요한 작업이며,
이 부분에 대한 사소한 실수도 이후 사용에 문제를 야기하기 때문에, 여기에 포함된
작업만큼은 sql command를 통해 직접 작업하기를 권고한다.
Replication manager가 포함되어 있는 OEM version은 1.4부터이며, Oracle8.1의
경우는 2.1이 최적화되어 있다. 그러나 그 이전 version도 사용가능하다.
7. Replication Users
=====================
일반적으로, multi-master환경보다는 updatable snapshot환경이 더 보안이 문제시
된다. multi-master의 경우는 일반적으로 중앙에서 같은 db admin에 의해 관리
되는것이 일반적이나 snapshot의 경우는 지역적으로 떨어져 별개로 관리되는 경우가
많아 그 snapshot에서 master site의 database에 손상을 주는 일을 막는것이
중요하여, user구성은 multi-master환경보다 복잡하다.
Snapshot Site Master Site
Replication administrator
Snapshot replication administrator ---> Proxy snapshot administrator
Propagator ---> Receiver
Refresher ---> Proxy refresher
Snapshot Owner(s) ---> Proxy refresher
- Replication administrator: master site에서, master group들의 구성과
관리를 책임진다.
- Snapshot administrators: snapshot site에서 snapshot replication group을
구성하고 관리하는 책임을 지며, master site의 Proxy administrator가
master group의 최소한의 access만 허용하게 된다.
- Propagators: deferred transaction을 master site에 전달하면, master site의
Receiver가 전달받은 data를 master table에 적용시킨다.
- Refreshers: snapshot site에서 master site의 변경된 data를 snapshot
site로 끌어오는 역할을 하며, master site의 Proxy refresher는 master
site의 table에 대한 최소한의 acess만을 허용한다.
이러한 user들의 생성하고 이용하는 방법은 여러가지로 가능하다. 아래에서는,
그중 가장 일반적으로 사용되는 방법을 기술한다.
8. Replication user 생성 및 권한 부여
=====================================
Oracle 8.1부터 updatable snapshot 환경 구축시 trusted와 untrusted두가지
방법이 가능하다. untrusted의 경우 snapshot site가 master site와 같은 관리자
아래에 포함되지 않아 보안을 더 강화해야 하는 model이다.
하나의 master site에 snapshot group이 여러개이고, 각 snapshot별로, 이
snapshot group을 공유하는것이 아니고, 별개로 사용하는 경우 서로 다른
snapshot이 사용하는 group에 대해 보안을 유지하려면 untrusted model을 사용해야
하나 실제 이러한 환경으로 구성되는 일은 거의 없고, 작업의 번거로움으로 이
문서에는 trusted model에 대해서는 설명한다.
8.1 Master Site user와 권한
(1) Replication Administrator (REPADMIN)
SQL>CONNECT system/<password>
SQL>CREATE USER repadmin IDENTIFIED BY <password>
DEFAULT TABLESPACE <tablespace name>
TEMPORARY TABLESPACE <tablespace name>;
SQL>GRANT connect, resource TO repadmin;
SQL>EXECUTE dbms_repcat_admin.grant_admin_any_schema('repadmin');
SQL>GRANT comment any table TO repadmin;
SQL>GRANT lock any table TO repadmin;
만약 replication group이 어느 특정 schema에만 한정된다면,
grant_admin_any_schema대신 grant_admin_schema를 사용하여도 된다.
(2) Proxy snapshot administrator / Receiver / Proxy refresher (SNAPPROXY)
master site의 proxy snapshot administrator, receiver, proxy refresher는
하나의 user로 관리하는 것이 일반적이다. 이러한 SNAPPROXY user를 생성하지
않고 REPADMIN user가 이러한 역할도 수행하도록 설정할 수 있으나, 그렇게
되면 snapshot site에 너무 많은 권한을 부여하게 되어 바람직하지 않다.
replication manager를 이용해 이러한 user를 생성하면 master site에 연결된
snapshot site마다 각각의 snapproxy_n과 같은 형태로 user를 생성하나,
같은 snapshot group에 대하여 이렇게 각각의 user를 생성하는 것은 의미가
없으므로 권장되지 않는다.
SQL>CONNECT system/<password>
SQL>CREATE USER snapproxy IDENTIFIED BY <password>
DEFAULT TABLESPACE <tablespace name>
TEMPORARY TABLESPACE <tablespace name>;
(3) Proxy snapshot administrator privileges
SQL>CONNECT system/<password>
SQL>BEGIN
dbms_repcat_admin.register_user_repgroup(
username => 'snapproxy',
privilege_type => 'proxy_snapadmin',
list_of_gnames => NULL);
SQL>END;
SQL>/
register_user_repgroup procedure를 통해 권한을 부여한다. 이때, "create
session" 과 dbmsobjgwrapper / dbms_repcat_untrusted package에 대한
"execute"권한이 부여된다.
Replication group에 table을 add하게 되면 그 table에 대한 "select" 권한이
부여된, master objects에 대한 DML권한은 이 user에게 부여되지 않는다.
(4) Receiver privileges
SQL>CONNECT system/<password>
SQL>BEGIN
dbms_repcat_admin.register_user_repgroup(
username => 'snapproxy',
privilege_type => 'receiver',
list_of_gnames => NULL);
SQL>END;
SQL>/
이 문장을 통해 "create session" 과 dbms_defer_internal packages,
dbms_defer package에 대한 "execute"권한이 부여된다. 그러나 이것도
마찬가지로 master object에 대한 DML권한을 부여하지 않는다.
또한 receiver는 replication object를 추가한 후 replication support시에
생성되는 <schema>.<object name>$RP (LOB table에 대해서는 $RL)에 대한
execute권한을 부여 받아 master site에 변경사항을 적용하게 된다.
(5) Proxy refresher privileges
SQL>CONNECT system/<password>
SQL>GRANT create session TO snapproxy;
SQL>GRANT select any table TO snapproxy;
(6) Schema Owner(s) (여기에서는 REPUSER로 명시)
SQL>CONNECT system/<password>
SQL>CREATE USER repuser IDENTIFIED BY <password>
DEFAULT TABLESPACE <tablespace name>
TEMPORARY TABLESPACE <tablespace name>;
SQL>GRANT connect, resource TO repuser;
8.2 Snapshot Site user와 권한
(1) Snapshot administrator / Propagator / Refresher (SNAPADMIN)
snapshot administrator, propagator, refresher에 대해서 하나의 user로
관리하는것이 일반적이다.
SQL>CONNECT system/<password>
SQL>CREATE USER snapadmin IDENTIFIED BY <password>;
DEFAULT TABLESPACE <tablespace name>
TEMPORARY TABLESPACE <tablespace name>;
(2) Snapshot administrator 권한
SQL>CONNECT system/<password>
SQL>EXECUTE dbms_repcat_admin.grant_admin_any_schema('snapadmin');
SQL>GRANT comment any table TO snapadmin;
SQL>GRANT lock any table TO snapadmin;
(3) Propagator 권한
SQL>EXECUTE DBMS_DEFER_SYS.REGISTER_PROPAGATOR('snapadmin');
(4) Refresher 권한
SQL>GRANT create any snapshot TO snapadmin;
SQL>GRANT alter any snapshot TO snapadmin;
refresher와 대응하는 master site의 proxy refrsher에 의해 master site의
table에 대한 "select any table" 권한을 가지게 된다.
(5) Schema Owner(s) (여기에서는 REPUSER로 명시)
replicate되고자 하는 table에 대한 master site의 schema와 동일한 이름의
shema가 snapshot site에서도 필요하다. 단 password는 같을 필요는 없다.
만약 다른 schema에 대해서 updatable snapshot을 생성하면, snapshot생성시는
오류없이 만들어지지만, create_snapshot_repobject 수행시에 아래와 같이
오류가 발생할 것이다.
ORA-23306: schema <schema name> does not exist
ORA-23308: object <schema name>.<object name> does not exist or is invalid
아래 문장과 같은 schema owner생성시 주의할 점은 이 권한을 role을 통해
부여하지 말고 직접 주어야 한다는것이다. 즉, 이미 connect, resource등을
통해 create table과 같은 권한은 부여된 상황임에도 불구하고, 이후에
procedure나 package등에서 이 권한이 필요한 경우 role을 통해 부여된 것은
인식이 되지 않고 ORA-1031이 발생하기 때문에 아래와 같이 직접 권한을
부여하여야 한다.
SQL>CONNECT system/<password>
SQL>CREATE USER repuser IDENTIFIED BY <password>
DEFAULT TABLESPACE <tablespace name>
TEMPORARY TABLESPACE <tablespace name>;
SQL>GRANT connect, resource TO repuser;
SQL>GRANT create table TO repuser;
SQL>GRANT create snapshot TO repuser;
이 user가 master site에 대해서 수행할 수 있는 권한에 대해서는 이 user에서
master site로 생성하는 database link를 어느 user로 connect하느냐에 달려
있으며 이것은 9.4에서 설명한다.
(6) End Users
snapshot schema에 있는 snapshot을 이용하는 user가 별도로 존재할 수
있으며, 이 경우 특별한 권한이 추가적으로 필요하지는 않고, snapshot
object에 대한 필요한 권한을 부여하면 된다.
9. Database Link
================
database link를 생성하기 전에 중요한 것은 replication 환경에 포함된 모든
database는 고유한 global name을 가지고 있어야 한다. default global name은
<db_name>과 동일하나 다음과 같이 문장을 통해 global name을 수정가능하다.
그러므로 db_name이 같더라도 이렇게 global name을 수정하여 replication
환경을 구성할 수 있다.
SQL>ALTER DATABASE RENAME GLOBAL_NAME TO <new global name>;
SQL>SELECT * FROM GLOBAL_NAME;
updatable snapshot환경에서 database link가 제대로 구성되지 않으면 이후
작업에 계속 문제가 생기므로 주의하여야 한다. 이 database link는 snapshot
site에서 master site로만 구성하면 되며, 반대로 master site에서 snapshot
site로 구성할 필요는 없다.
(1) Public Database Links
Net8 connection alias를 이용하여 다음과 같이 public database link를
만든다. 이후 생성되는 private link는 using절을 포함하지 않게 되며,
모두 public database link와 동일한 이름의 db link이름을 가져야 한다.
(global_names=true이기 때문)
SQL>CONNECT system/<password>
SQL>CREATE PUBLIC DATABASE LINK <remote databases global name.world>
USING 'Net8 alias';
여기에서 표현한 Net8 alias는 snapshot site의 tnsnames.ora file에 정의
되어 있어야만 한다.
(2) Snapshot Administrator / Snapshot propagator / refresher
snapshot administrator와 proxy snapshot administrator 다음과 같이 private
database link가 필요하다.
SQL>CONNECT snapadmin/<password>
SQL>CREATE DATABASE LINK <remote databases global name.world>
CONNECT TO snapproxy IDENTIFIED BY <password>;
(3) Schema Owner (여기에서는 REPUSER로 명시한다)
snapshot을 가지고 있는 모든 schema는 master site에 private database
link를 생성해야 한다. 이때, "Schema to Schema" 와 "Schema to Proxy
Refresher" 두가지를 고려할 수 있다.
만약 link를 schema to schema방식으로 생성하게 되면, snapshot owner는
쉽게 master site로 연결하여, master table에 DDL이나 DML을 수행가능하다.
이것은 일반적으로 바람직하지 않으므로 master의 proxy refresher로
private database link를 만들도록 권고된다. master에서 proxy refresher와
proxy administrator가 동일한것이 일반적으로 결국 proxy administrtor에게
연결하면 된다.
이렇게 되면 snapshot의 schema owner는 proxy refresher user에 의해,
master table에 대한 "select any table"권한은 가지게 되지만, DDL이나,
DML은 허용되지 않으므로 더 안정적이다.
SQL>CONNECT repuser/<password>
SQL>CREATE DATABASE LINK <remote databases global name.world>
CONNECT TO snapproxy IDENTIFIED BY <password>;
(5) End User
database link가 필요하지 않다.
9.6 Testing Database Links
database link생성 작업이 끝나면 다음과 같이 하여, 각 user별로 database
link 생성이 올바로 되었는지 확인하도록 한다.
SQL>CONNECT user/<password>
SQL>SELECT * FROM DUAL@<database link name>
10. schedule설정
================
1 ~ 9번까지 성공적으로 수행되었다면 이제 replication manager를 이용하여,
replication/snapshot group과 object를 추가할 수 있다.
replication manager를 이용시 master site는 repadmin user로 접속하고,
snapshot site는 snapadmin user로 접속하도록 한다.
snapshot site의 변경 작업을 master site로 주기적으로 push시키고, 이렇게
push된 data를 또 다른 주기로 purge시키는 scheduling이 필요하다.
이것은 replication manager를 이용하려면, 아래 menu를 이용하면 된다.
- Scheduling --> Scheduled Links
- Database Information --> Purge Job Tab
이 작업을 sql문으로 수행하려면 다음과 같은 문장을 snapshot site에서
수행한다.
SQL>CONNECT snapadmin/<password>
SQL>BEGIN
dbms_defer_sys.schedule_push(
destination => '<destination databases global name>.WORLD',
interval => '/*10:Mins*/ sysdate + 10/(60*24)',
next_date => sysdate,
stop_on_error => FALSE,
delay_seconds => 0,
parallelism => 1);
SQL>END;
SQL>/
SQL>BEGIN
dbms_defer_sys.schedule_purge(
next_date => sysdate,
interval => '/*1:Hr*/ sysdate + 1/24',
delay_seconds => 0,
rollback_segment => '');
SQL>END;
SQL>/

Adpatch 9239089 taking time for Updating Snapshot Tables

Hi,
I am upgrading Apps R12.1.1 to Apps R12.1.3 . Applying patch 9239089 as prerequisite of patch 9239090.
This patch is taking much time and Updating Snapshot Tables as below
No of records processed =205032 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:04:15
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:04:17
No of records processed =210033 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:06:37
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:06:38
No of records processed =215033 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:08:57
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:08:58
No of records processed =220034 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:11:17
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:11:18
No of records processed =225034 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:13:36
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:13:37
No of records processed =230035 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:15:56
Done Updating Snapshot Tables for the above rows...End Time:Sun Nov 20 2011 11:15:57
No of records processed =235035 Updating Snapshot Tables...Start time:Sun Nov 20 2011 11:18:16
Done Updating Snapshot Tables
Please see if there is any issue or how can avoid to updating snapshot tables.
Regards,
Raj

Hi Raj,
I am using shared appl_top on NFS file system , and this patch is using the NFS file system . So this issue could be NFS file system.
when I am performing any write intensive operation on NFS file system it is taking huge time. adadmin utility is also taking muchtime to invoke.I also applied the same patch on a shared APPL_TOP but never had any performance issue.
So I need some oracle recommendation to use NFS file system or how performance can be tune of nfs file system.?Have you tried to maintain snapshot via adadmin before applying the patch and see how it behaves?
Oracle Applications Maintenance Utilities
http://www.oracle.com/technetwork/documentation/applications-167706.html
Thanks,
Hussein

Update snapshot encountered errors

Hi All,
We encountered errors when updating snapshot using adadmin.
About to attempt instantiating the current-view snapshot: Fri Jul 20 2012 21:55:22
Invalid Release :
Error in calling adphistRlseExists for
AD Administration error:
Error calling adusnapInstCurrVwSnapshot
AD Administration error:
Error calling adusnapGetSnapshotId
AD Administration error:
Error calling adusnapGetCurViewSnapshotId
Failed to store APPL_TOP Snapshot to tables
adusnapMaintainSnapshot() : Error calling adusnapUpdateCurrentView2()
Error calling adusnapPartialCurVw()
Error calling adusnapMaintainSnapshot
Time is: Fri Jul 20 2012 21:55:22
It seems some records are missing.
SQL> select APPL_TOP_ID,name from ad_appl_tops;
APPL_TOP_ID NAME
1 tan
2 tfw
45 GLOBAL
47 adela501p
21 PRESEEDED
1048 adela500p
6 rows selected.
SQL> col SNAPSHOT_NAME for a20
SQL> select snapshot_name,appl_top_id from ad_snapshots;
SNAPSHOT_NAME APPL_TOP_ID
CURRENT_VIEW 1
CURRENT_VIEW 2
CURRENT_VIEW 47
Is there any way to re-create the snapshot if we are lose some records.
Thanks,
Kevin
Edited by: Kevin on Jul 23, 2012 10:49 AM

1. Check if AD_APPL_TOPS has the right entry for APPL_TOP.
-- Take a backup of AD_APPL_TOPS, remove the entry of the invalid apl_top_id.Can you update the forum with the contents of AD_APPL_TOPS and the backup of AD_APPL_TOPS table?
-- modify the XML file in appl_top/admin to have APPL_TOP_NAME correct. (if its not correct).Is this correct?
-- Run adconfig.sh (only needed if appl_top_name is not correct).Did it complete successfully?
2. Take a backup of AD-SNAPSHOTS table, modify to have the entry of the corrcet APPL_TOP_ID.
3. Run adadmin,
-- This will create the snapshot for the correct appl_top_id can cross check it from ad_snapshots table.Have you verified this?
Thanks,
Hussein

Occurs "AD Administration error" when i update snapshot

ours is upgraded to EBS R12.0.6.
then,apply patch 7665691 and 7533081.all above is successful!
next ,when i execute "adadmin" -->2.Maintain Applications Files menu-->4.Maintain snapshot information-->2.Update current view snapshot-->1.Update Complete APPL_TOP
after running about 8 minutes,the errors occurs like this below:
==========================
AD Administration error:
Error while executing statement
AD Administration error:
ORA-00600: internal error code, arguments: [kdddgb5], [4294967295], [0], [], [], [], [], []
ORA-06512: at "APPS.AD_FILE_UTIL", line 1357
ORA-06512: at line 3
==========
can somebody help me ? i can't resolve the problem
Edited by: user515977 on Apr 26, 2009 10:25 PM
Edited by: user515977 on Apr 26, 2009 10:27 PM
Edited by: user515977 on Apr 26, 2009 10:27 PM

Hi,
Have a look at the following document.
Note: 153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=153788.1
If this does not help, please log a SR.
Regards,
Hussein

Update Snapshot?

Would anyone know a keyboard shortcut for "Update with Current Settings" with the active Snapshot? It would be wonderful for my workflow to not have to go up and right click the Snapshot to access it. I have found nothing in any shortcut list so far.

I know of no off-the-shelf way to do it, but an autohotkey script could be used to do it if you're clever (or similar mac technique). Also a short plugin could do it on Windows (but not Mac - since it doesn't support keyboard shortcuts to plugins).
One fly in the ointment: There is no such thing as an "Active Snapshot", they are arranged alphabetically, and none is "selected" whilst editing, so you would have to come up with a scheme for targeting the correct snapshot.

Snapshot with update on both sides

Hi,
I've created a snapshot with the for update clause, but when I
use the dbms_snapshot.refresh procedure, the server looses
everything made in the point B.
Point A -> master
Point B -> snapshot
Sequence:
1) Create a simple table in the master an populate it
2) create snapshot log on master
3) create database link on B to A
4) create snapshot on B
5) update the table on A
6) dbms_snapshot.refresh on B =====> ok!!!
7) update the table on A and on B
8) commit on A and B
9) dbms_snapshot.refresh on B ===> the server just applies the
changes made in A, it looses the changes in B
I need help.
Best regards,
Ari
null

Ari Arantes (guest) wrote:
: Hi,
: I've created a snapshot with the for update clause, but when I
: use the dbms_snapshot.refresh procedure, the server looses
: everything made in the point B.
: Point A -> master
: Point B -> snapshot
: Sequence:
: 1) Create a simple table in the master an populate it
: 2) create snapshot log on master
: 3) create database link on B to A
: 4) create snapshot on B
: 5) update the table on A
: 6) dbms_snapshot.refresh on B =====> ok!!!
: 7) update the table on A and on B
: 8) commit on A and B
: 9) dbms_snapshot.refresh on B ===> the server just applies the
: changes made in A, it looses the changes in B
: I need help.
: Best regards,
: Ari
Ari,
You need to generate replication support for the updatable
snapshot using the dbms_repcat.create_snapshot_repobject
procedure.
2 way replication is pretty complex to set up. You will need
correctly configured database links, snapshot logs at the master
site and replication support for all your updatable snapshots at
the snapshot site.
There are quite a few ways of setting up updatable snapshot
replication. My best advice is to get hold of the "replication
bible" from Oracle Documentation.
Oracle7 Server Distributed Systems Replicated Data or equivalent
for 8. This is essential.
good luck,
Dave.
null

Snapshot replication slow during purge of master table

I have basic snapshot/materialized view replication of a big table (around 6 million rows).
The problem that I run into is that when I run a purge of the master table at the master site (delete dml), the snapshot refresh time becomes slower. After the purge the snapshot refresh time goes back to the normal time interval.
I had thought that the snapshot does a simple select so any exclusive lock on the table should not hinder the performance.
Has anyone seen this problem before and if so what has been the workaround?
The master site and the snapshot site both are 8.1.7.4 and are both unix tru64.
I don't know if this has any relevence but the master database is rule based while the snapshot site is cost based.
thanks in advance

Hello Alan,
Your problem is, to know inside a table-trigger if the actual DML was caused
by a replication or a normal local DML.
One way (I'm practising) to solve (in Oracle 8.1.7) this is the following:
You can use in the trigger code the functions DBMS_SNAPSHOT.I_AM_A_REFRESH(),
DBMS_REPUTIL.REPLICATION_IS_ON() and DBMS_REPUTIL.FROM_REMOTE()
(For details see oracle documentation library)
For example: a trigger (before insert of each row) at the master side
on a table which is an updatable snapshot:
DECLARE
     site_x VARCHAR2(128) := DBMS_REPUTIL.GLOBAL_NAME;
     timestamp_x      DATE;
     value_time_diff     NUMBER;
BEGIN
IF (NOT (DBMS_SNAPSHOT.I_AM_A_REFRESH) AND DBMS_REPUTIL.REPLICATION_IS_ON) THEN
IF NOT DBMS_REPUTIL.FROM_REMOTE THEN
IF inserting THEN
     :new.info_text := 'Hello table; this entry was caused by local DML';
END IF;
END IF;
END IF;
END;
By the way: I've got here at work nearly the same configuration, now in production since a year.
Kind regards
Steffen Rvckel

Update patches vs re-downloading application

I understand with 'major' new releases, we may need to redownload the application in order to upgrade.But in the past, with its 'minor' updates (small bug fixes etc), Apple has forced us to re-download the application every single time.
This is not a small application. It's 35mb! It hardly seems an efficient way to do things, considering how long this product has been around and what competing products offer. The fact that iTunes and iPods (which are not exactly cheap) are so highly integrated should also be reason enough for Apple to get its act together.

873768 wrote:
Hi:
I encounter the same error while running the patch wizard. I am going to following your advice to run adadmin. First I want to know if its okay (now I test on a DEV instance) to run update snapshot? There are 1. update complete APPL_TOP, 2. Update JAVA_TOP only, 3. Update a product_top. Which one do I pick?
Update a current view snapshot (full or partial APPL_TOP and global) -- Oracle E-Business Suite Maintenance Utilities
Thanks,
Hussein

About adpatch and Attempting to instantiate the current-view snapshot...

when we install any patch 1st time with adpatch utility.
it start gathring snapshot information with following message
Attempting to instantiate the current-view snapshot...
how can I force to adpatch utility to do above?
Regards
Chirag Patel

Thanks Fadi,
1)
i tried what u said.
but still it is the same error.
AutoPatch error:
Error while executing statement
AutoPatch error:
ORA-06550: line 3, column 10:
PLS-00302: component 'IS_PATCH_APPLIED2' must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored
AutoPatch error:
adppdepIsPatchApplied() returned FALSE
See messages above for details.
You should check the file
/home/appldev1/dev1appl/admin/dev1/log/adpatch.6502082.log\
2) it means every time when we apply patch, then adpatch update snapshot automatically ?
Regards
Chirag
Nairobi

ICloud backups failing due to Safari bookmarks DB being locked

iCloud backups are failing to complete on my iPhone 4 (CDMA), iOS 5.0.1. I successfully completed a backup on November 9, but haven't been able to get a backup to complete since then. When I manually invoke the "Back Up Now" function, it starts backing up, then says "There was a problem completing the backup. Please try again later."
Looking in the console logs (below), it appears the problem is that the Safari bookmarks DB is locked (corrupted?). Indeed, I am unable to add additional bookmarks in Safari, I get the message: "Bookmarks are being synced. Please add the bookmark once syncing has completed."
I've tried restarting the iPhone to no avail; I've also looked at Apple's iCloud backup troubleshooting doc, and none of the cases there seemed to match this problem.
Any suggestions ar every much appreciated!
Here is what the iPhone console says:
Nov 29 15:47:01 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
Nov 29 15:47:02 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
Nov 29 15:47:04 unknown backupd[7416] <Warning>: INFO: Added batch of 4 files of size 15.2 KB in 2.155 s at 0.01 MB/s (6.6%)
Nov 29 15:47:04 unknown backupd[7416] <Warning>: INFO: Finished adding files in 7.103 s at 13.20 MB/s
Nov 29 15:47:05 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
Nov 29 15:47:09 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
Nov 29 15:47:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:47:33 unknown lockdownd[21] <Error>: 016b4000 copy_basebandRegionSKU: MobileGestalt failed to provide an BasebandRegionSKU
Nov 29 15:47:33 unknown lockdownd[21] <Error>: 016b4000 special_case_get_domain: NN: checking BT MAC Address reported back 24:ab:81:ec:bf:37
Nov 29 15:47:33 unknown kernel[0] <Debug>: lockbot[7436] Builtin profile: gputoolsd (sandbox)
Nov 29 15:47:36 unknown lockdownd[21] <Error>: 01632000 copy_basebandRegionSKU: MobileGestalt failed to provide an BasebandRegionSKU
Nov 29 15:47:36 unknown lockdownd[21] <Error>: 01632000 special_case_get_domain: NN: checking BT MAC Address reported back 24:ab:81:ec:bf:37
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: Found paths:
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /usr/lib/dyld
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /System/Library/Caches/com.apple.dyld/dyld_shared_cache_armv7
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/CFDataFormatters.dylib
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/libdebugnub.dylib
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/usr/lib/libXcodeDebuggerSupport.dylib
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/GPUTools.framework/libglInterpose.dylib
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/GPUToolsCore.framework/GPUToolsCore
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/PrivateFrameworks/DevToolsBundleInjection.framework/DevTools BundleInjection
Nov 29 15:47:37 unknown DTFetchSymbols[7448] <Notice>: /Developer/Library/Frameworks/SenTestingKit.framework/SenTestingKit
Nov 29 15:47:56 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
Nov 29 15:48:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:48:29 unknown backupd[7416] <Warning>: INFO: Scanned in 79.680 s
Nov 29 15:48:30 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.995 s
Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 6 files of size 182.2 MB)
Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.651 s
Nov 29 15:48:33 unknown backupd[7416] <Warning>: INFO: Adding 6 files of size 182.2 MB
Nov 29 15:49:11 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 88.7 MB in 24.837 s at 3.57 MB/s (29.4%)
Nov 29 15:49:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:49:45 unknown backupd[7416] <Warning>: ERROR: Error starting transfer of items with MMCS: Error Domain=com.apple.mmcs Code=30 "The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested)" UserInfo=0xf9d5bf0 {NSDescription=All items in the request have failed. Put authorization will not be requested}
Nov 29 15:49:45 unknown backupd[7416] <Warning>: INFO: Not retrying after unrecoverable error: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
Nov 29 15:49:51 unknown backupd[7416] <Warning>: ERROR: Backup failed: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
Nov 29 15:49:52 unknown lockdownd[21] <Error>: libMobileGestalt copyInternationalMobileEquipmentIdentity: No IMEI in CT mobile equipment info dictionary - <CFBasicHash 0x2254b0 [0x3f5f5630]>{type = mutable dict, count = 6,
          entries =>
                    1 : <CFString 0x250530 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentSubscriberId"} = <CFString 0x224740 [0x3f5f5630]>{contents = "2062760895"}
                    2 : <CFString 0x225480 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentMobileId"} = <CFString 0x24f4d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                    3 : <CFString 0x240100 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMEID"} = <CFString 0x24f4d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                    4 : <CFString 0x255a70 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMIN"} = <CFString 0x224740 [0x3f5f5630]>{contents = "2062760895"}
                    7 : <CFString 0x258a10 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoPRLVersion"} = <CFNumber 0x250de0 [0x3f5f5630]>{value = +52341, type = kCFNumberSInt64Type}
                    8 : <CFString 0x250570 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoERIVersion"} = <CFNumber 0x240050 [0x3f5f5630]>{value = +6, type = kCFNumberSInt32Type}
Nov 29 15:49:52 unknown lockdownd[21] <Error>: 01632000 copy_imei: MobileGestalt failed to provide an IMEI
Nov 29 15:49:52 unknown lockdownd[21] <Error>: 01632000 copy_iccid: invalid ICCID from CT/no ICCID available
Nov 29 15:49:53 unknown backupd[7416] <Warning>: INFO: Scheduling next backup at 11/29/11 3:50:23 PM
Nov 29 15:50:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:50:26 unknown backupd[7416] <Warning>: INFO: Backup starting
Nov 29 15:50:26 unknown backupd[7416] <Warning>: INFO: DeviceID="8e00a6a6d8e93337321c17ba679894a5ac80ddb1", DeviceName="Blake Scholl's iPhone", ProductType="iPhone3,3", BuildVersion="9A405"
Nov 29 15:50:30 unknown profiled[7458] <Notice>: (Note ) profiled: Service starting...
Nov 29 15:50:32 unknown wifid[25] <Error>: WiFi:[344303432.585437]: Client itunesstored is background application
Nov 29 15:50:38 unknown backupd[7416] <Warning>: INFO: Refreshed cache in 4.024 s
Nov 29 15:50:38 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
Nov 29 15:51:15 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
Nov 29 15:51:16 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences
Nov 29 15:51:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences/com.apple.itunesstored.plist
Nov 29 15:51:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Preferences
Nov 29 15:51:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:51:31 unknown profiled[7458] <Notice>: (Note ) profiled: Idled.
Nov 29 15:51:31 unknown profiled[7458] <Notice>: (Note ) profiled: Service stopping.
Nov 29 15:51:50 unknown backupd[7416] <Warning>: INFO: Scanned in 71.803 s
Nov 29 15:51:52 unknown backupd[7416] <Warning>: INFO: Found 1 deleted files in 1.279 s
Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 11 files of size 93.8 MB)
Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.424 s
Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: Adding 11 files of size 93.8 MB
Nov 29 15:51:55 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
Nov 29 15:51:56 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
Nov 29 15:52:00 unknown backupd[7416] <Warning>: INFO: Added batch of 9 files of size 3.8 KB in 4.011 s at 0.00 MB/s (0.0%)
Nov 29 15:52:01 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 0 B in 0.492 s at 0.00 MB/s (0.0%)
Nov 29 15:52:01 unknown backupd[7416] <Warning>: INFO: Finished adding files in 6.141 s at 15.27 MB/s
Nov 29 15:52:03 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
Nov 29 15:52:09 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
Nov 29 15:52:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:52:25 unknown atc[7384] <Warning>: ATC|__block_global_22|ATController.m:1182| Assertion check - link <ATLink: 0x1862d0> held: 0, idle: 0
Nov 29 15:52:46 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
Nov 29 15:53:19 unknown backupd[7416] <Warning>: INFO: Scanned in 69.028 s
Nov 29 15:53:19 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.693 s
Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 4 files of size 93.8 MB)
Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 3.972 s
Nov 29 15:53:24 unknown backupd[7416] <Warning>: INFO: Adding 4 files of size 93.8 MB
Nov 29 15:53:25 unknown backupd[7416] <Warning>: INFO: SQLite file is locked: /var/mobile/Library/Safari/Bookmarks.db (d1f062e2da26192a6625d968274bfda8d07821e4)
Nov 29 15:53:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:53:25 unknown backupd[7416] <Warning>: WARNING: Error checkpointing copied SQLite file: disk I/O error (10) (MBErrorDomain/16): /var/mobile/Library/AddressBook/AddressBookImages.sqlitedb (cd6702cea29fe89cf280a76794405adb17f9a0ee)
Nov 29 15:53:28 unknown backupd[7416] <Warning>: INFO: Added batch of 2 files of size 1.6 KB in 2.274 s at 0.00 MB/s (0.0%)
Nov 29 15:53:28 unknown backupd[7416] <Warning>: INFO: Finished adding files in 3.440 s at 27.26 MB/s
Nov 29 15:53:28 unknown backupd[7416] <Warning>: WARNING: Retrying after hard error: Files modified while backing up (MBErrorDomain/9)
Nov 29 15:53:34 unknown backupd[7416] <Warning>: INFO: Snapshot 85 is uncommitted
Nov 29 15:54:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard
Nov 29 15:54:18 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard/applicationstate.plist
Nov 29 15:54:20 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/SpringBoard
Nov 29 15:54:20 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Safari/Bookmarks.db
Nov 29 15:54:23 unknown backupd[7416] <Warning>: INFO: Modified while scanning: /var/mobile/Library/Mail
Nov 29 15:54:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:54:53 unknown backupd[7416] <Warning>: INFO: Scanned in 78.753 s
Nov 29 15:54:53 unknown backupd[7416] <Warning>: INFO: Found 0 deleted files in 0.857 s
Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Updated snapshot 85 (added 9 files of size 182.2 MB)
Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Created backup and snapshot in 2.897 s
Nov 29 15:54:56 unknown backupd[7416] <Warning>: INFO: Adding 9 files of size 182.2 MB
Nov 29 15:55:00 unknown backupd[7416] <Warning>: INFO: Added batch of 2 files of size 31.3 KB in 3.679 s at 0.01 MB/s (0.0%)
Nov 29 15:55:25 unknown atc[7384] <Warning>: ATC|__20-[ATController init]_block_invoke_0831|ATController.m:1164| Checking timeout inactive=0, timeout disabled=1
Nov 29 15:55:33 unknown backupd[7416] <Warning>: INFO: Added batch of 1 files of size 88.7 MB in 22.235 s at 3.99 MB/s (24.3%)
Nov 29 15:56:08 unknown backupd[7416] <Warning>: ERROR: Error starting transfer of items with MMCS: Error Domain=com.apple.mmcs Code=30 "The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested)" UserInfo=0xf950f60 {NSDescription=All items in the request have failed. Put authorization will not be requested}
Nov 29 15:56:08 unknown backupd[7416] <Warning>: INFO: Not retrying after unrecoverable error: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
Nov 29 15:56:13 unknown lockdownd[21] <Error>: libMobileGestalt copyInternationalMobileEquipmentIdentity: No IMEI in CT mobile equipment info dictionary - <CFBasicHash 0x255a30 [0x3f5f5630]>{type = mutable dict, count = 6,
          entries =>
                    1 : <CFString 0x250530 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentSubscriberId"} = <CFString 0x2439f0 [0x3f5f5630]>{contents = "2062760895"}
                    2 : <CFString 0x227350 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoCurrentMobileId"} = <CFString 0x2506d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                    3 : <CFString 0x258a10 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMEID"} = <CFString 0x2506d0 [0x3f5f5630]>{contents = "A100001AEF8D32"}
                    4 : <CFString 0x24ca60 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoMIN"} = <CFString 0x2439f0 [0x3f5f5630]>{contents = "2062760895"}
                    7 : <CFString 0x225640 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoPRLVersion"} = <CFNumber 0x255930 [0x3f5f5630]>{value = +52341, type = kCFNumberSInt64Type}
                    8 : <CFString 0x250570 [0x3f5f5630]>{contents = "kCTMobileEquipmentInfoERIVersion"} = <CFNumber 0x240050 [0x3f5f5630]>{value = +6, type = kCFNumberSInt32Type}
Nov 29 15:56:13 unknown lockdownd[21] <Error>: 01632000 copy_imei: MobileGestalt failed to provide an IMEI
Nov 29 15:56:13 unknown lockdownd[21] <Error>: 01632000 copy_iccid: invalid ICCID from CT/no ICCID available
Nov 29 15:56:13 unknown backupd[7416] <Warning>: ERROR: Backup failed: Error putting items into chunk store (MBErrorDomain/400). Underlying error: Error putting items into MMCS (MBErrorDomain/400). Underlying error: The operation couldn’t be completed. (com.apple.mmcs error 30 - All items in the request have failed. Put authorization will not be requested) (com.apple.mmcs/30)..
Nov 29 15:56:15 unknown backupd[7416] <Warning>: INFO: Scheduling next backup at 11/29/11 7:33:26 PM

Had same problem, the solution lies with having your original apple ID associated email address "verified".
I may not have all the steps down correctly, but open your apple ID account manager and go to the your listing for email and "verify" the email address. This association then seems to allow the use of your email address when you are trying to set up this new apple ID that they are requiring for iCloud.
Be aware that this new apple ID has a far reach and apparently cannot be undone, that is you can't change the name, characters, numbers or whatever you have for an email address that becomes your apple ID---even if you can no longer use the email address to receive email.
Lots of luck.
I have been trying to get the iCloud features to work for over a week now, including a visit to a genius bar, and still not fully functioning.

Error in upgrading SharePoint Server 2013 with SP1 : "Task upgradebootstrap has failed with an unknown exception"

I has successfully setup new Dev ENV of SarePoint server 2013 in VMware with 2 servers running om OS: win server 2008 R2 Ent SP1, AD + Central Admin Application Server.
After that the configuration of SharePoint App and WorkFlow Manager completed as well and many projects run perfectly,
And after installing SP1 of SharePoint server 2013, and running the SharePiont Configuration wizard to complete the configuration of the SharePoint Farm the Upgrade has fialed on Step2 with the following Error from the Log file:
Task upgradebootstrap has failed with an unknown exception
01/04/2015 00:43:30 11 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
Also after that I was not able to create like before a new site , and this creating end with error message as follows:
Failed to call GetTypes on assembly Microsoft.Office.TranslationServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Method not found: 'Microsoft.Office.Web.Common.ProcessImageInfo.
Is there any solution to my problem with SharePoint server 2013 SP1, this supposed not to cause any bug in stable environment.
Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

Hi Daniel,
Thanks for replying on my post, actually I have downloaded the kb2880552 sp1 for
enterprise edition from the link
https://support.microsoft.com/kb/2880552 , and this has been experienced with me before since I had my Standalone Dev machine first installation, and the issue only occurred when the SP1 installed though.
Anyway, I've tried to install CU Nov 2013 http://support.microsoft.com/kb/2889944
but still facing the same issue,
I run the Setup of SP2013 from the CD to repair the SharePoint and error message appears,
The issue related to "Microsoft.Office.TranslationServices" is also related to running
the repair successfully which leads to the same error message above.
The Version of SP 2013 from the program file is : 15.0.4571.1502
The Update snapshot is as below:
Is there a problem with my sharepoint media file?
Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

DEFERRED TRANSACTION QUEUE의 내용을 지우는 여러가지 방법 (replication)

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
PURPOSE
advanced replication 환경에서, 특정 master site나 updatable snapshot
site은 다른 remote의 master site로 데이타를 propagation시키기 위해서
해당 local site에 deferred transaction queue를 유지한다.
remote site로 잘 전달된 데이타는 주기적으로 dbms_defer_sys.purge job에
의해 deferred transaction queue인 DEFCALL에서 지워지게 되는데, 경우에
따라 문제가 발생하면서 DEFCALL의 내용이 remote site로 전달이 안되면서
계속해서 지워지지 않고 남게 될 수 있다.
이러한 경우 다음 트랜잭션의 진행이나 전달에도 방해가 될 수 있어
강제로 지우고자 하는 상황이 발생하는데 그러한 경우의 조치 방법에 대해서
자세히 설명한다.
SCOPE
Advanced Replication Feature는 8~10g Standard Edition에서는 지원하지
않는다.
Explanation
1. 특정 deferred transaction id를 지우는 경우
기본적으로 deferred transaction queue에 쌓인 트랜잭션을 지우는
방법은 다음과 같다.
dbms_defer_sys.delete_tran(deferred_tran_id, destination)
즉 다음 예와 같다.
SQL>exec dbms_defer_sys.delete_tran('2.7.10', 'rep2.world');
이때, 해당 destination에 대한 모든 트랜잭션인경우는 앞의 argument를
null로 하고, 특정 transaction id에 대한 모든 destination에 대해서인
경우는 뒷부분의 argument를 null로 한다.
결국 저장된 모든 deferred transaction이라면, 다음과 같다.
SQL>exec dbms_defer_sys.delete_tran(null,null);
2. 특정 table에 관한 내용만 지우는 경우
예를 들어 특정 table, 여기서는 DEPT table에 관한 사항을 DEFCALL에서
지우고자 한다면 다음과 같이 조치하면 된다.
SQL>connect repadmin/repadmin
SQL>set pagesize 1000
SQL>set head off
SQL>spool purgedefcall.sql
SQL>select 'exec dbms_defer_sys.delete_tran('''
|| deferred_tran_id || ''', null);'
from defcall
where packagename like 'DEPT%';
SQL>spool off
spool에 의해 만들어진 purgedefcall.sql을 깨끗하게 편집한 후 다시 save한다.
SQL>connect repadmin/repadmin
SQL>@purgedefcall.sql
이때 만약 특정 site로의 전달만을 막고자 한다면, null대신 MS_B.WORLD와 같이
해당 site를 가리키는 database link이름을 직접 지정하면 된다.
3. 전체 queue의 내용을 모두 지우는 경우
DEFCALL의 내용을 모두 지우는 경우라면 기본적으로는 앞에서 사용한
DBMS_DEFER_SYS.DELETE_TRAN을 이용하면 된다.
SQL>connect repadmin/repadmin
SQL>exec dbms_defer_sys.delete_tran(null,null);
DEFERROR의 내용을 모두 지우는 경우에는 DBMS_DEFER_SYS.DELETE_ERROR를
사용한다.
SQL>exec dbms_defer_sys.delete_error(null,null);
그런데 이 delete_tran과 delete_error의 경우는 내부적으로 delete문장을
사용하면서 undo record를 위해 rollback을 사용하면서 지워야 하는 데이타가
매우 많은 경우 속도도 문제가 되고 rollback space오류도 발생 가능하다.
이러한 경우에는 다음과 같이 truncate command를 이용하여 간단하고 빠르게
deferred transaction queue의 내용을 정리할 수 있다.
(1) Oracle7의 경우
DEF$_CALL, DEF$_CALLDEST, DEF$_ERROR 를 모두 truncate시킨다.
단 이때 DEF$_CALLDEST가 DEF$_CALL을 reference하는 constraint가 있는 관계로,
DEF$_CALLDEST를 모두 truncate하여 데이타가 전혀 없는 상태에서도,
DEF$_CALL이 truncate가 되지 않는다.
delete operation의 경우 child table이 비어 있다면 master table의 데이타를
지우는데 오류가 없지만, truncate의 경우는 데이타 확인 없이 바로 지우는
것이기 때문에 child table에 데이타가 없다하더라도 그러한 check없이,
무조건 자신을 reference하는 child table의 constraint가 enable되어 있는한은
master table이 truncate가 불가능하게 된다.
SQL>connect as system/password
SQL>alter table system.DEF$_CALLDEST disable constraint
DEF$_CALLDEST_CALL;
SQL>truncate table system.DEF$_CALL;
SQL>truncate table system.DEF$_CALLDEST;
SQL>truncate table system.DEF$_ERROR;
SQL>alter table system.DEF$_CALLDEST enable constraint DEF$_CALLDEST_CALL;
(2) Oracle8의 경우
Oracle8에서는 DEF$_CALLDEST가 더이상 DEF$_CALLDEST_CALL constraint를
가지지 않으므로 이 부분에 대한 고려는 필요없이 다음과 같이 해당 table들을
truncate시키면 된다.
SQL>truncate table system.DEF$_AQCALL;
SQL>truncate table system.DEF$_CALLDEST;
SQL>truncate table system.DEF$_ERROR;
SQL>truncate table system.DEF$_AQERROR;
4. deferror의 내용을 지우는 방법
deferred transaction이 remote로 전달되어 반영되다가 오류가 발생하면
source가 되는 데이타베이스의 queue에서는 해당 내용이 사라지고,
반영되던 destination 데이타베이스의 deferror와 defcall/deftran에
해당 내용이 쌓이게 된다.
이러한 경우 error의 내용을 다시 반영을 시도하거나 아니면 내용을
확인 후 지우게 된다.
다음과 같이 지우면 된다.
SQL>exec dbms_defer_sys.delete_error(null,null);
참고로 다시 수행하는 것은
SQL>exec dbms_defer_sys.execute_error(null,null);
Reference Documents
<Note:190885.1> How to Clear Down the Deferred Queue and DBMS_DEFER_SYS.
DELETE_TRAN

Replicate Table with spatial columns

I'd like to know how to
replicate (updatable snapshot) a table
with spatial columns.
when i try to create a master repobject
i've got ORA-23318 error.
What can i do?
null

Hi Vincent,
Oracle does not support replication of object in 8.1.6 or 8.1.7. I believe replication support is expected for the version after.
Sorry,
Dan

ORACLE ENTERPRISE EDITION VERSION 별 주요 특징

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
오라클 서버의 version 별 주요 특징은 다음과 같습니다
Oracle 7.1
===========
- 병렬 SQL 오퍼레이션 제공:
     . Parallel Scan, Parallel Join, Parallel Sub-query 등
     . Parallel loading
     . Parallel Index Creation
- Synchronous Distributed Database
     . Global Optimization for Distributed Query/Update
- Asynchronous
     . Deferred Remote Procedure Call
     . Updatable Snapshot
- Advanced Replication
     . Asymmetric Replication
Oracle 7.2
===========
- No logging option (CREATE INDEX)
     . 예) create index 시 norecovery option
- Parallel Insert
- Star Query Optimization
     . Data Warehousing 에서 성능향상을 위해 사용
- Union All view
- Resizable data files
- Cursor Variable Data-type
Oracle 7.3
===========
- Partition view 제공
     . Parallel UNION,UNION ALL
- Hash Join
     . Hash table 을 사용하여 Join processing 에 효과적임
- Asynchronous Read-ahead
- Parallel Load Balancing in OPS
- Dynamic system configuration
     . Oracle 초기화 parameter 중 일부를 db shutdown 없이 변경할 수
     있음
- Updatable view
     . Primary Key 를 유지하는 view 에 대해서 update 가 가능함
- Oracle Enterprise manager
     . client 에서 Oracle server monitoring 이 가능하게 해 주는 Tool
Oracle 8
=========
- Data Warehousing 을 위한 기능 개선을 및 추가
     . 테이블과 인덱스 분할(partitioning)
     . 64 비트 화일 시스템을 지원(Oracle7 에서는 옵션)
- OLTP 를 위한 기능 개선 및 추가
     . Connection Pooling 을 이용한 대량의 사용자 지원
     . Oracle Parallel Server(OPS)와 Distributed Lock Manager 의 통합
     . Advanced Queuing Mechanism 지원
     . System Change Number 생성의 최적화 (10-15 % 의 OPS 성능향상)
     . Global Fixed View 를 제공하여 OPS 에서 여러 노드의 instance
     관리를 가능
     . Transparent Application Fail Over in OPS
     . TP monitor 지원 개선
     - Dynamic Registration
     - Loosely-Coupled Transaction
     - No need to session cache
     - 모든 플랫폼에서 OPS 용 XA library 제공
     . Multi-level, Incremental Backup in Recovery manager
- Replication
     . Parallel Propagation
     . Replication Manager Wizard
     . Primary key snapshot
- Object-Relational Database
     . application 중심으로 서버를 확장하기 위한 객체 타입(Object type)          지원
     . 객체 메쏘드로서 외부 프로시저 (external procedure) 사용
     . 빠른 클라이언트-사이드 객체 검색 지원
     . Multi-Data(이미지, 비디오, 텍스트 등) 지원
     . JDBC/JSQL 을 통한 자바 지원
     . 객체형 데이타에 대한 Object view 제공

Hi;
1. Patch can be download only from metalink
2. All related patch number can be found:
NOTE:430449.1 - How to find DB Patches for the Microsoft Windows platforms My Oracle Support
11.2.0.x Oracle Database and Networking Patches for Microsoft Platforms [ID 1114533.1]
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Updating snapshots

Similar Messages

Maybe you are looking for