Lost replication updates

          Hi.
          I have a web app in a .war format running on two nodes in a WLS6.0sp2 cluster
          (round-robin). When I try to access the JSP's that access session data, I get
          the following error.
          Can somebody tell me what the stack trace I have posted below means? (This is
          from one of the nodes, altough I see the same thing on the other node). The symptom
          of the exception seems to be that some of the data seems to be replicated while
          some is not.
          Thanks in advance,
          Saman
          <Mar 18, 2002 1:16:12 PM EST> <Error> <Kernel> <ExecuteRequest failed
          weblogic.cluster.replication.NotFoundException: Lost 2 updates of 5509919717493478763
          at weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)
          at weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationManager_WLStub.java:316)
          at weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationManager.java:426)
          at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:398)
          at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
          at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1535)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.utils.NestedError: Could not find secondary on remote server - with nested
          exception:
          [weblogic.cluster.replication.NotFoundException: Lost 2 updates of 5509919717493478763]
          at weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessionData.java:405)
          at weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSessionContext.java:147)
          at weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.java:1535)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1310)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Mar 18, 2002 1:16:12 PM EST> <Info> <Cluster> <Got stale replication request
          for object 5509919717493478763>
          <Mar 18, 2002 1:16:12 PM EST> <Info> <Cluster> <Got stale replication request
          for object 5509919717493478763>

          You didn't tell if you were using a proxy in front of the cluster. If you are not,
          that's a problem. Make sure that there are no problems with multicast.
          Cheers,
          -- Prasad
          "Kumar Allamraju" <[email protected]> wrote:
          >Have you applied any rolling patches?
          >if not, can you upgrade to the latest SP and see if that solves the problem.
          >
          >If you still see the problem, contact support and reference CR045425
          >
          >--
          >Kumar
          >
          >"Saman Aria" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi.
          >>
          >> I have a web app in a .war format running on two nodes in a WLS6.0sp2
          >cluster
          >> (round-robin). When I try to access the JSP's that access session data,
          >I
          >get
          >> the following error.
          >> Can somebody tell me what the stack trace I have posted below means? (This
          >is
          >> from one of the nodes, altough I see the same thing on the other node).
          >The symptom
          >> of the exception seems to be that some of the data seems to be replicated
          >while
          >> some is not.
          >>
          >> Thanks in advance,
          >>
          >> Saman
          >>
          >> <Mar 18, 2002 1:16:12 PM EST> <Error> <Kernel> <ExecuteRequest failed
          >> weblogic.cluster.replication.NotFoundException: Lost 2 updates of
          >5509919717493478763
          >> at
          >weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRe
          >quest.java:90)
          >> at
          >weblogic.cluster.replication.ReplicationManager_WLStub.update(ReplicationMan
          >ager_WLStub.java:316)
          >> at
          >weblogic.cluster.replication.ReplicationManager.updateSecondary(ReplicationM
          >anager.java:426)
          >> at
          >weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessi
          >onData.java:398)
          >> at
          >weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSe
          >ssionContext.java:147)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.
          >java:1535)
          >> at
          >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >ntext.java:1310)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >:1631)
          >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >> --------------- nested within: ------------------
          >> weblogic.utils.NestedError: Could not find secondary on remote server
          >-
          >with nested
          >> exception:
          >> [weblogic.cluster.replication.NotFoundException: Lost 2 updates of
          >5509919717493478763]
          >> at
          >weblogic.servlet.internal.session.ReplicatedSessionData.sync(ReplicatedSessi
          >onData.java:405)
          >> at
          >weblogic.servlet.internal.session.ReplicatedSessionContext.sync(ReplicatedSe
          >ssionContext.java:147)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.syncSession(ServletRequestImpl.
          >java:1535)
          >> at
          >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >ntext.java:1310)
          >> at
          >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >:1631)
          >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >> >
          >> <Mar 18, 2002 1:16:12 PM EST> <Info> <Cluster> <Got stale replication
          >request
          >> for object 5509919717493478763>
          >> <Mar 18, 2002 1:16:12 PM EST> <Info> <Cluster> <Got stale replication
          >request
          >> for object 5509919717493478763>
          >
          >

Similar Messages

HT204053 I have a big problem in my account in Game Center .. I have been an account before in the game center and i change it to another one ...when i play any game its change by itself to the last account not still to the new one and i lost my update in

I have a big problem in my account in Game Center ..
I have been an account before in the game center and i change it to another one ...
when i play any game its change by itself to the last account not still to the new one and i lost my update in my game
How can i keep the new account in my game center and didn't change again ?
My new account is :[email protected] ............Thats i wanna to keep it
The old one is :michael-adel [email protected]
Thank you

I have a big problem in my account in Game Center ..
I have been an account before in the game center and i change it to another one ...
when i play any game its change by itself to the last account not still to the new one and i lost my update in my game
How can i keep the new account in my game center and didn't change again ?
My new account is :[email protected]. ............Thats i wanna to keep it
The old one is :michael-adel [email protected]
Thank you

5300 Dead after connection was lost during update

5300 Dead after connection was lost during update. Won't turn on, power up-nothing. Help?

It is now dead.
Take to a nokia care point.
Care points:
UK
http://www.nokia.co.uk/A4228006
Europe:
http://europe.nokia.com/A4388379
Elsewhere:
http://www.nokia.com and select your country.

Contacts lost after updating my 4s to ios6-how can I retrieve them?

Contact were lost after updating-this didn't occur on another 4s we have-is there an easy way to retrieve them?

What were you syncing them to? Are they still there?

Certified expired lost my updates?

I have a big problem, on the certificate renewel the id of my air app has change and with that i lost my updates ca+ability, almost every client that have the software installed have the air 1.5.2 and the old aplication only was searching for updates on namespace 1.5 i have a solution that pass to doing migrate of the old certificate via adt using the command line but for that to work i need my clients to have the air 1.5.3 installed so this is not a solution, i simple can't ask my clients to reinstall the aplication.ideias anyone???
Thanks in advance
Alex

Yes, I have the same problem. See my post here:
http://forums.adobe.com/thread/546660?tstart=0
Since your users probably need certain admin rights to update the app, it may not be a problem to install AIR 1.5.3 at the same time. It depends on your user's restrictions. Just watch out for the trap I fell into using ADT 1.5.3. Your users can get caught with a "damaged application" error if you don't update the app namespace to 1.5.3.

Macbook upgraded from 10.5.8 to mountain lion. I lost the update when I tried to restore my old information. How can I get my update back without paying again?

I took my mac to an iStore in South Africa however my country does not have an iStore. Macbook upgraded from 10.5.8 to mountain lion. I lost the update when I tried to restore my old information. How can I get my update back without paying again?

Ok, that sounds like a valid approach...but now the question is, when you say you lost the upgrade when you tried to restore, exactly what do you mean? Restore from a Time Machine backup, or another kind of backup? What happened to the operating system when you did that?
If it damaged the operating system, you should be able to recover it by restarting your computer holding either the Option key (should result in a grey screen that shows the macintosh hard drive and a recovery hard drive), or by holding the Command and R keys while starting.
You can use the recovery hard drive to reinstall Mac OS X either way. If the Option key restart, click on the recovery hard drive to boot from that.
Then with either approach you will have a screen with a drop-down that gives you choices, such as install Mac OS X, Disk Utility, Terminal. You will want to use Install (or Reinstall) Mac OS X...note, you must be connected to the internet from this point on.

(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>/

HT4623 notes lost after updating

Notes lost after updating ipad. Can they be retrieved from the device ?

They cannot be retrieved unless you have a iTune or iCloud backup.

Data back up taken in 2.1 is lost while updating to 2.3

It is compulsory to lose backup while upgrading from 2.1 to 2.3. Its really big big disappointing feature of the update. No care is taken by even google to restore sbf type back up by putting support software in market.
I want to restore some of important sms back up. I need help from Sony Ericsson. I am sure that so many people have lost their back up while updating to 2.3.
It is compulsory to put such a notice display while updating to 2.3 that you will loose the back up and will not be able to restore back of 2.1 in 2.3. I want to file a case against the company for the valuable data loss and for not to inform such an important data lose.
Solved!
Go to Solution.

Hi, download the following apk file from link provided and install it to your phone, http://www.elita-clan.com/downloads/backup_and_restore_v010935.apk.
Download it to PC/Laptop, then transfer it to phone SD Card. Make sure you have a File Manager app to search and install the apk file.

Lost January Update and I am Pi$$ed

After reading the horror stories about the version 2 update, I elected not to update. I received the prompt then to update to 1.15 which I did. Shortly after I did, all of my files on the Ipod were transferred due to some kind of a glitch to "other", and as a result things such as music were not accessible on the Ipod....
So.... stupid me, I restore the Ipod. And in the process, the January Update is now lost and was not reinstalled on my Ipod and no longer appears in the software version on the Itunes summary....
Now what really has me pi$$ed is that I had a number of important items stored in notes.... and when the January Update vanished, so did my notes.
Now what do I do other than steam....
How could anyone consider this crappy little device as a plausable replacment to a Personal Organizer when your next sync could be the end of your data. A note pad and pencil is more reliable.

Since last night I have installed 2.0.2 and it is working and it also kept all of my old data which is a relief....
However I am still angered as I bought and paid for the update in January. Apple accepted my payment without hesitation, then because they stopped offering or supporting the upgrade, I am up the creek without a paddle? Don't even if they opt not to sell it anymore, shouldn't they offer support to those who originally bought it for a reasonable length of time?
If I buy a car and decide to have the radio upgraded, then two months later the car company stops offering that model of radio, does that mean if my radio quits it is reasonable to accept that the car company can just leave me high and dry? I think not, but only my opinion.

Some metadata lost in update to 9.6

When I updated to the version 9.6 of iPhoto that would run under Yosemite, apparently random metadata has been lost in many of the photos. This includes rotation, places, faces, etc. I have not figured out the rhyme or reason, has anybody had this issue, and how does one correct it?
Thanks,
-FreeBeef

Try Back up your iPhoto library, Depress and hold the option (alt) and command keys and launch iPhoto - from the resulting first aid window repair permissions and if necessary rebuild your database
LN

Replication update statement takes long time

Hi Replication experts,
I have a issue and please suggest if my understanding and solution is correct.
We have a transactional replication setup for data warehouse, from today morning replication got huge latency so when I looked into it I saw the "sp_MSupd_< tablename >" was running for very long time and by this time it was running for 9 hours
still no data was updated, Latency went very high. What we feel is that the index maintenance was not done in subscriber also it was not replicated too. So due to high fragmentation the update statement could take very long.
As there was no error message or blocks found all we see is the update taking very long. So to avoid this we are planning to remove the index, as this is just data warehouse index maintenance is not required by removing we can gain some space too. Is this a
good Idea to implement?
When we ran profiler nothing was found, no error or alert logged.
Please let me know your suggestions
Thanks
Best Regards Moug

Hi All,
The Issue we found to be is that a day before, new column was added to the table and 9000 rows were updated ... This caused the distributor to slow down the update operation as the index in subscriber(15 million rows) was updating every time a row
is updated.. So we suspect that adding a new column and updating it at the same time is the culprit..
But still am not convinced as per my understanding the distributor operates by comparing the primary key of publisher that was changed with the primary key of the subscriber and apply those change.. If that is the case why should it worry about the new column
added or the number of updates..
Also one strange thing is another table was also lagging behind in its operation ,though that table was updated with just 18 rows.. So in a nutshell the update operation was totally down by distributor operation on that day..
Can someone please shed some light on this, Replication is my favorite topic but now I got fear of it.. after failing to know what could be issue...
Best Regards Moug

Favourites lost when updating TomTom app

I have a 16GB iPhone 4 with about 650MB of storage. TomTom released a new version of their app this week, and in order to update the app, I first sync'ed and backed up my iPhone with iTunes. I then downloaded the update in iTunes before trying to sync again. The app didn't sync, probably because of lack of storage on the iPhone, so I deleted the app from the phone and re-sync'ed. The updated app sync'ed correctly after that, but I lost all of my favourites and app settings in the process. I contacted TomTom support about this and there's no way to retrieve them, they're essentially washing their hands off the problem, saying it's an Apple issue.
I can restore my iPhone using the back up I did before deleting the app, but that doesn't really help me in updating the app. Does anybody know whether it's possible to export the favourites from the app, and re-import them after deleting the app and installing the updated version?
Note: I don't want to delete my music and put it back after updating the app. Updating to iOS 7 was a disaster, resulting in my music not sync'ing properly. I could never fix it using iTunes and in the end, I had to use CopyTransManager to manually copy the albums one by one. It took me almost 2 months of manually copying songs from computer to iPhone to get my music back as it was prior to updating to iOS 7 (minus a few albums for which I didn't have enough space), so I am not touching it again ever! (I don't sync it through iTunes anymore).

Well, it looks like I can't restore the backup either because "there's not enough storage"
Anyway, I browsed through various internet forums and found a solution:
With iPhone Backup Extractor, I extracted mapsettings.cfg from my last manual backup (to my PC), which I did before deleting the TomTom app and installting the updated version. You need to go in "Expert Mode" to Application\com.tomtom.WEurope\Documents\Western_Europe.
Once you have found it, click "Extract" and save it somewhere on your PC.
Now, using iExplorer, I copied the file to the corresponding location on my iPhone (Apps\W. Europe\Documents\Western_Europe)
Launched TomTom on my iPhone et voila! My favourites are all there and I am running the latest version of the app.
Don't know why Apple/TomTo, have to make it so hard...

Originals of photos lost when updated to 9.3

I've just installed the iPhoto 9.3 update, and found that I can no longer access edits to any photos more than two years old – which is 80% of my library. Most of those older photos had been cropped or adjusted in some way, and I often need to undo a crop or readjust an edit.
The message I get is "Image Cannot Be Edited. This photo was previously edited with another application or with an earlier version of iPhoto. Duplicate this photo to edit it."
Has the iPhoto library upgrade deleted the originals and replaced them with the final edits? Can I retrieve the originals?

Excellent – thank you.
It's a bit of a faff, but it works. The original is in there, and it opens with preview, but iPhoto won't accept it into the library (because it thinks it's already there). I duplicated it and saved it under a different name, and it imported correctly into iPhoto with its original date and metadata.
So all that's lost, it seems, are the settings I used to edit it from the original to the final edit, should I want to recreate most but not all of that editing process. Seems unfortunate (and somewhat needless) but I can cope with that. Thanks for your help.

Transactional replication update causing deadlock

Hello,
I am using sql server 2012 SE. I am using Transactional replication and noticed that we have been receiving deadlocks lately. The select statement that is inserting data into a temptable is getting deadlocked by the transactionalreplication update statement.
I am in the process of avoiding this deadlock. Is adding any missing index is the only solution here? PLease find the deadlock information below:
3/13/2015 11:03:17,spid3s,Unknown,waiter id=process85b6b2928 mode=IX requestType=wait
03/13/2015 11:03:17,spid3s,Unknown,waiter-list
03/13/2015 11:03:17,spid3s,Unknown,owner id=process505246558 mode=S
03/13/2015 11:03:17,spid3s,Unknown,owner-list
03/13/2015 11:03:17,spid3s,Unknown,pagelock fileid=1 pageid=8285871 dbid=6 subresource=FULL objectname=PaigahDB.dbo.EmailLogs id=lock73c690280 mode=S associatedObjectId=72057594176077824
03/13/2015 11:03:17,spid3s,Unknown,waiter id=process505246558 mode=S requestType=wait
03/13/2015 11:03:17,spid3s,Unknown,waiter-list
03/13/2015 11:03:17,spid3s,Unknown,owner id=process85b6b2928 mode=IX
03/13/2015 11:03:17,spid3s,Unknown,owner-list
03/13/2015 11:03:17,spid3s,Unknown,pagelock fileid=1 pageid=8286764 dbid=6 subresource=FULL objectname=PaigahDB.dbo.EmailLogs id=lock3d4201500 mode=IX associatedObjectId=72057594176077824
03/13/2015 11:03:17,spid3s,Unknown,resource-list
03/13/2015 11:03:17,spid3s,Unknown,Proc [Database Id = 6 Object Id = 323532236]
03/13/2015 11:03:17,spid3s,Unknown,inputbuf
03/13/2015 11:03:17,spid3s,Unknown,[FullName] = case substring(@bitmap<c/>2<c/>1) & 8 when 8 then @c12 else [FullName] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[LastName] = case substring(@bitmap<c/>2<c/>1) & 4 when 4 then @c11 else [LastName] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[FirstName] = case substring(@bitmap<c/>2<c/>1) & 2 when 2 then @c10 else [FirstName] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[AddressOrder] = case substring(@bitmap<c/>2<c/>1) & 1 when 1 then @c9 else [AddressOrder] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[EmailType] = case substring(@bitmap<c/>1<c/>1) & 128 when 128 then @c8 else [EmailType] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[AddressContactAttempts] = case substring(@bitmap<c/>1<c/>1) & 64 when 64 then @c7 else [AddressContactAttempts] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[Address] = case substring(@bitmap<c/>1<c/>1) & 32 when 32 then @c6 else [Address] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[Timestamp] = case substring(@bitmap<c/>1<c/>1) & 16 when 16 then @c5 else [Timestamp] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[LogStatus] = case substring(@bitmap<c/>1<c/>1) & 8 when 8 then @c4 else [LogStatus] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[JobID] = case substring(@bitmap<c/>1<c/>1) & 4 when 4 then @c3 else [JobID] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,[EmailAddressID] = case substring(@bitmap<c/>1<c/>1) & 2 when 2 then @c2 else [EmailAddressID] end<c/>
03/13/2015 11:03:17,spid3s,Unknown,update [dbo].[EmailLogs] set
03/13/2015 11:03:17,spid3s,Unknown,frame procname=PaigahDB.dbo.sp_MSupd_dboEmailLogs line=52 stmtstart=4900 stmtend=8184 sqlhandle=0x03000600ccb54813d9b8250031a4000001000000000000000000000000000000000000000000000000000000
03/13/2015 11:03:17,spid3s,Unknown,executionStack
03/13/2015 11:03:17,spid3s,Unknown,process id=process85b6b2928 taskpriority=0 logused=793868 waitresource=PAGE: 6:1:8285871 waittime=1805 ownerId=591093165 transactionname=user_transaction lasttranstarted=2015-03-13T11:03:07.047 XDES=0x8fbb7cd28 lockMode=IX
schedulerid=2 kpid=1496 status=suspended spid=70 sbid=0 ecid=0 priority=0 trancount=2 lastbatchstarted=2015-03-13T11:03:15.870 lastbatchcompleted=2015-03-13T11:03:15.867 lastattention=1900-01-01T00:00:00.867 clientapp=webapp_rep_10032014 hostname=DBServer
hostpid=3112 loginname=dom\user isolationlevel=read committed (2) xactid=591093165 currentdb=6 lockTimeout=4294967295 clientoption1=671156320 clientoption2=128056
03/13/2015 11:03:17,spid3s,Unknown,Proc [Database Id = 17 Object Id = 853578079]
03/13/2015 11:03:17,spid3s,Unknown,inputbuf
03/13/2015 11:03:17,spid3s,Unknown,where el.[Timestamp] between ji.LastExportTime and @currentExportTime;
03/13/2015 11:03:17,spid3s,Unknown,join PaigahDB.dbo.EmailLogStatuses es on el.LogStatus = es.EmailLogStatusID
03/13/2015 11:03:17,spid3s,Unknown,join PaigahDB.dbo.EmailLogs el on el.JobID = ji.EmailJobId
03/13/2015 11:03:17,spid3s,Unknown,from #JobIds ji
03/13/2015 11:03:17,spid3s,Unknown,select 'EMAIL'<c/> el.EmailLogID<c/> el.ImportPersonId<c/> el.JobID<c/> el.Timestamp<c/> es.Details<c/> es.Name<c/> el.AddressContactAttempts<c/> null<c/> null<c/>
el.LogStatus<c/> es.Details<c/> el.EmailLogIdentity
03/13/2015 11:03:17,spid3s,Unknown,(MessageType<c/> LogId<c/> ImportPersonId<c/> JobId<c/> [Timestamp]<c/> Details<c/> Name<c/> NumberContactAttempts<c/> Number<c/> PatientResponse<c/> LogStatusID<c/>
LogStatus<c/> LogIdentity)
03/13/2015 11:03:17,spid3s,Unknown,insert into #LogFlexes
03/13/2015 11:03:17,spid3s,Unknown,frame procname=PlazaDB.dbo.GetJobResults line=111 stmtstart=7788 stmtend=9074 sqlhandle=0x030011005f91e032b241de0050a4000001000000000000000000000000000000000000000000000000000000
03/13/2015 11:03:17,spid3s,Unknown,executionStack
03/13/2015 11:03:17,spid3s,Unknown,process id=process505246558 taskpriority=0 logused=0 waitresource=PAGE: 6:1:8286764 waittime=7082 ownerId=591097183 transactionname=INSERT lasttranstarted=2015-03-13T11:03:10.667 XDES=0x8f5b68d28 lockMode=S schedulerid=1
kpid=5128 status=suspended spid=188 sbid=0 ecid=0 priority=0 trancount=2 lastbatchstarted=2015-03-13T11:03:10.397 lastbatchcompleted=2015-03-13T11:03:10.397 lastattention=2015-03-13T10:52:07.350 clientapp=.Net SqlClient Data Provider hostname=GW-W hostpid=5468
loginname=abc\admin isolationlevel=read committed (2) xactid=591097183 currentdb=17 lockTimeout=4294967295 clientoption1=673185824 clientoption2=128056
03/13/2015 11:03:17,spid3s,Unknown,process-list
03/13/2015 11:03:17,spid3s,Unknown,deadlock victim=process505246558
03/13/2015 11:03:17,spid3s,Unknown,deadlock-list
Experts I need your valuable inputs.
Thanks a ton

This is what I would do.
Check when update statistics were ran last time?
Check for any fragmentation on tables?
Turn on trace flag 1204, 1222
Use deadlock graph, deadlock chain and narrow down the statements and tune them.
See below link which might be useful.
https://www.simple-talk.com/sql/performance/sql-server-deadlocks-by-example/

Lost replication updates

Similar Messages

Maybe you are looking for