Newbie in 9i replication

Hi all,
i have to build a replication architecture for one of my databases, due to a disaster recovery implementation .
Database A must be fully replicated/syncronized to Database B.
Database B is in another physical location , and i have an connetion between the two servers.
how can i achieve this ? can you point some basic documentation for a beginner like me ?
My environment:
Hp Proliant dl 580 servers
Oracle database 9i
Windows 2000 server
Best regards
Rui Madaleno

Hi Rui,
The best thing it would have to analyze the bandwidth and to decide on syncronous or asyncronous replication, after it to analyze if he will be feasible to talk back all the partial form or data base since one will be due to have special well-taken care of in not degrading the performance.
I replicate for four years with a 700k in asyncronous mode in win NT over a netfinity, now migrate to ora9i over dl385 opteron with linux inside, over the same bandwith, and oracle run fine. The numer of transactions is close to 5000 rows per day, and oracle is strong, and no data lost, but the first step por build a model is know all tables involved and decide: replicated all tables or a part vital of system, in this case you can pause the replica and push all transaction the end of week or a hour with less activity. the guides show in above reply's is ok.
Best regards,
Martin Sarmiento Narro.

Similar Messages

Multimaster replication error

Hi,
Well I am a newbie to multimaster replication. I tried to replication few tables and indexes of hr schema to other database but I am receiving the following errors:
ID REQUEST ERRNUM MESSAGE
43 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.EMPLOYEES does not exist or is inv
121 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.DEPARTMENTS does not exist
41 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.DEPARTMENTS does not exist or is i
141 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.DEPARTMENTS does not exist
161 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.EMPLOYEES does not exist or
21 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
22 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
123 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.EMPLOYEES does not exist or
24 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
25 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
26 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
ID REQUEST ERRNUM MESSAGE
27 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
28 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
29 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
30 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
31 CREATE_MASTER_REPOBJECT -942 ORA-00942: table or view does not exist
47 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.JOB_HISTORY does not exist or is i
127 GENERATE_INTERNAL_PKG_SUPPORT -23308 ORA-23308: object HR.JOB_HISTORY does not exist
Kindly, help me regarding this issue.
Thank you for your cooperation.
Kind Regards,
Adnan Hamdus Salam

You will see "replica busy" errors from time to time. The replication protocol is "one at a time" - if a consumer has more than 1 supplier, only 1 supplier may update the consumer at a time - the other suppliers get a busy signal during the update. Note that updates to 1 supplier may be sent to another supplier and then to the consumer if the first supplier gets a busy signal, so all of your updates should get through pretty quickly.
The most important thing is - do your updates get through to all consumers? Do they get through quickly?

Unable to start extract

Hi all,
Iam a newbie in Goldengate replication.
When iam trying to start EXTRACT process it failed with following error:
GGS ERROR 500 Could not open checkpoint file /oracle/10.4/dirchk/ELOAD01.cpe, mode 1 (error 2, No such file or directory).
GGS ERROR 190 PROCESS ABENDING.
Please help.
Thanks,
Sandy

user12941120 wrote:
When iam trying to start EXTRACT process it failed with following error:
GGS ERROR 500 Could not open checkpoint file /oracle/10.4/dirchk/ELOAD01.cpe, mode 1 (error 2, No such file or directory).
GGS ERROR 190 PROCESS ABENDING.Just after installing GG (i.e., after unzipping it), there's a single command that has to be run to "finish" the installation in ggsci: "create subdirs". Was this command run? That command creates the required subdirectories "dirprm", "dirchk", "dirdat", "dirdef", ...etc.
After that, you have to create the prm file (ggsci => edit param eload01), then "add" the extract (ggsci => add extract eload01 ....). The "edit param" command creates a file eload01.prm inside dirprm, the command "add extract eload01" creates a file "eload01.cpe" inside of dirchk. Then, when you start the process (ggsci => start eload01), the prm file will be read to determine what should be done, and the checkpoint file (dirchk/eload01.cpe) will be periodically updated with the progress of the process; upon restart, the process will use the files in dirchk to start from where the process left off...
Hope it helps,
-Mike

Newbie questions about Database replication, "backups", and sql version

Just created my first Sql Database using the "SQL Database Management Portal". A blast but three questions come to mind:
1. Is this DB automatically
"replicated"? (In other words, is DB "failover" or clustering, a feature of all newly created Azure databases?)
2. Our on-premise model is to make a daily DB backup which is saved to a nightly tape. If needed, we can restore a two-month old database backup under a new name to compare it with the current one. Does Sql Azure support this capability
or not? Can it be requested?
3. Which on-premise version of sql is "Sql Azure" closest to? (2014?)
TIA,
edm2
P.S. My database was created using the "web" edition.

Hi edm,
According to your description, you create a SQL Azure database in Azure platform. The replication feature is not supported by Microsoft Azure SQL database. If you want to sync the SQL Azure database and local database, you can use SQL Azure Data Sync service.
For more information, see:
http://blogs.technet.com/b/the_cloud_pilot/archive/2011/10/24/your-first-sql-azure-data-sync-step-by-step.aspx
In addition, if you have Web or Business Edition databases, you must create your own backup strategy. You can use database copy or Import and Export services to create copies of the data and export the file to an Microsoft Azure storage account. Meanwile,
Windows Azure SQL Database provides a mechanism for automating the process for exporting a database to BACPAC files on a set interval and frequency. For more information, see:
Schedule an Automated Export:
http://msdn.microsoft.com/en-us/library/hh335292.aspx#automate
Windows Azure SQL Database Backup and Restore strategy:
http://www.mssqltips.com/sqlservertip/3057/windows-azure-sql-database-backup-and-restore-strategy/
Currently, Azure uses a special version of Microsoft SQL Server as its backend. It provides high availability by storing multiple copies of databases, elastic scale and rapid provisioning, when we check the version of SQL Server, it shows as follows.
Microsoft SQL Azure (RTM) - 11.0.9216.62
Regards,
Sofiya Li
If you have any feedback on our support, please click
here.
Sofiya Li
TechNet Community Support

Replication from CRM to ECC and vice versa

Hi,
I am a newbie and would really appreciate any of your advice and help. I was given a task to replicate business partner from CRM to ECC. I was advised to go through a building block in SAP Best practices for CRM called C03:CRM Master and Data Replication. I've read through the materials and found out that there are some prerequisites. Do I need to installed all of the prerequisites before I can proceed with the steps given in the building block. I hope anyone could reply to me as soon as possible.
Regards,
Julianna

Hi,
Thats right! C03 best practices would be certainly helpful to you.
Few important steps for BP repllication from CRM to ECC would be
In CRM , First define your Logical destination in BD54 .
1) SU01 Transaction to create users : create user in CRM & R/3
2) Transaction code SM59 : Create RFC DESTINATION .. here u use the users created for reaching into R/3 from CRM
3) transaction code: SMOEAC: ADMINISTRATION CONSOLE:-
here define Publication, subscription and site ( OLTP) , and define replication objects ( like BUPA_MAIN, BUPA_REL)
4) define Queue: SMQR and SMQS - inbound and outbound queue /
Que registration .
5) check entry in R/3 side tables:- Make the proper entry into R/3 side tables in SM30
a)CRMRFCPAR
b)CRMPAROLTP
c)CRMSUBTAB
d) CRMCONSUM
These are important steps for Middleware settings between CRM & R/3
In addition to this , you need to correctly define your
1) in CRM ,BP GROUPINGS with Internal Number range
2) in R/3 define "Account Group" with "External Number Range" for BUSINESS PARTNER
3) In R/3 , Mapping of CRM CLASSIFICATION with R/3 account group...e.g. Classification B for customer with ACCOUNT group of R/3
You need to also map in CRM correctly the partner functions and R/3 Partner functions.
regards,
PD
Reward points if it helps...

Replication from an OSGI bundle - help

I am an OSGI newb!
I create a custom WorkflowProcess that is called from a WorkflowLauncher when a certain node gets created on the Author instance. The WorkflowProcess needs to replicate the node structure onder this node to the publisher.
I am having problems using the Replicator from the WorkflowProcess in the OSGI bundle. I am not about to instantiate an instance of com.day.cq.replication.Replicator. I have tried using the @Reference annotation, but at runtime the replicator is null. I have seen suggestions of using the Sling on the front end but that is not what I am looking for.
So my questions are:
1.) How do I get an instance of com.day.cq.replication.Replicator from inside a WorkflowProcess (WorkflowSession)?
2.) Can I use Sling in the bundle?
3.) Is there an easier way to do this?
4.) Can I programmatically connect to the Publish server from my WorkflowSession and create the nodes with jcr?
Thanks.

The code to manually trigger replicator would look somewhat like this:
import javax.jcr.Session;
import com.day.cq.replication.Replicator;
import org.apache.sling.jcr.api.SlingRepository;
@Reference
private Replicator replicator;
@Reference
private SlingRepository repository;
try{
     Session session = repository.loginAdministrative(null);
     replicator.replicate(session, ReplicationActionType.ACTIVATE, path);
finally{
     if (session != null){
          session.logout();
          session = null;

Transactional Replication - SQL Server 2012

Newbie to Replication.
Configured transactional replication on a database and everything run's fine, but out of all the tables one of the table with couple of columns as VARCHAR(MAX) and with about 3 million records takes 80% of replication duration.
on bit of research and recommendations, I did configured the server with following
EXEC sp_configure 'max text repl size', -1 ;
but still the table take around 80% of the replication time.
Can someone point me to other areas / best practices / articles to improve Replication performance?
Sreedhar

You need to determine why it is taking so long to replicate.
If it during snapshot application? If so use the initialize from backup option. Is it after the snapshot has been deployed?
Then you need to use tracer tokens to see if it is the log reader agent or the distribution agent. There is not a lot you can do with the log reader agent and it is not normally the bottleneck. It is likely with the distribution agent.
If so, I would first try to factor out the network. Replicate this table locally and see if you still have the same latency. if you don't it is the network and you need to try to minimize the network impact. Use a pull subscription and use a WAN accelerator.
These will have more impact than setting the network packet size.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Replication and AD Domain sevices errors between 2 Domain Controllers

Hi,
I've a 2 Domain Controllers (NJ-DC1-2K8 and NJ-DC2-2K8) setup in VMware Workstation 10. Recently, I've run into different errors in regards to Replication, DNS and AD Domain services. Both of my DC are setup with static IP pointing to each other for fault
tolerance. Initially, One of my DC had a lingering object error which I was able to fix after spending some time. The next day, when I tried to replicate 2 DC, the number of errors grew. Ran dcdiag, it produced a list of crazy errors that I never saw before.
I'm a newbie to the server environment, trying to gain knowledge so I can't get those errors sort out even I tried a lot. I read a lot of online articles on different forums like here Microsoft TechNet trying to overcome this problem but didn't work. I even
removed DNS role and re-added it but same problem. I guess removing the DNS role doesn't remove everything related to DNS. I'm going to upload pictures here of the different errors through the commands I got. I would appreciate if someone can help me to get
it fixed.
Other than that, I also would like to know what is the best way to remove DNS, AD Domain Services and then reinstall them without demoting the server. What are some of the things I would have to keep in mind before doing that. How can I make sure that doing
this wouldn't impact in AD data loss like user account, GP Policies, Computer account and etc....?
Errors are as follows:
1) C:\Users\Administrator>repadmin /syncall
    CALLBACK MESSAGE: The following replication is in progress:
    From: 66803610-2817-4853-ad3b-70c32a78c04a._msdcs.Fleet.local
    To : 9736b2e5-a75e-4991-a481-08c0226ed1c5._msdcs.Fleet.local
    CALLBACK MESSAGE: Error issuing replication: 8451 (0x2103):
    The replication operation encountered a database error.
    From: 66803610-2817-4853-ad3b-70c32a78c04a._msdcs.Fleet.local
    To : 9736b2e5-a75e-4991-a481-08c0226ed1c5._msdcs.Fleet.local
    CALLBACK MESSAGE: SyncAll Finished.
    SyncAll reported the following errors:
    Error issuing replication: 8451 (0x2103):
    The replication operation encountered a database error.
    From: 66803610-2817-4853-ad3b-70c32a78c04a._msdcs.Fleet.local
    To : 9736b2e5-a75e-4991-a481-08c0226ed1c5._msdcs.Fleet.local
2) C:\Users\Administrator>repadmin /showrepl
Repadmin: running command /showrepl against full DC localhost
NewJersey\NJ-DC1-2K8
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
DSA invocationID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
==== INBOUND NEIGHBORS ======================================
DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        30 consecutive failure(s).
        Last success @ 2014-07-06 16:16:49.
CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        29 consecutive failure(s).
        Last success @ 2014-07-06 16:06:25.
CN=Schema,CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        10 consecutive failure(s).
        Last success @ 2014-07-06 15:49:54.
DC=DomainDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        30 consecutive failure(s).
        Last success @ 2014-07-06 15:49:54.
DC=ForestDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        19 consecutive failure(s).
        Last success @ 2014-07-06 16:10:47.
Source: NewJersey\NJ-DC2-2K8
******* 30 CONSECUTIVE FAILURES since 2014-07-06 16:16:49
Last error: 8456 (0x2108):
            The source server is currently rejecting replication requests.
3) C:\Users\Administrator>dcdiag /replsum
Invalid Syntax: Invalid option /replsum. Use dcdiag.exe /h for help.
C:\Users\Administrator>repadmin /replsum
Replication Summary Start Time: 2014-07-06 21:03:28
Beginning data collection for replication summary, this may take awhile:
Source DSA          largest delta    fails/total %%   error
NJ-DC1-2K8        09d.22h:06m:34s    5 /   5 100 (8457) The destination server is currently rejecting replication requests.
NJ-DC2-2K8            05h:13m:34s    5 /   5 100 (8456) The source server is currently rejecting replication requests.
Destination DSA     largest delta    fails/total %%   error
NJ-DC1-2K8            05h:13m:34s    5 /   5 100 (8456) The source server is currently rejecting replication requests.
NJ-DC2-2K8        09d.22h:06m:34s    5 /   5 100 (8457) The destination server is currently rejecting replication requests.
4) C:\Users\Administrator>dcdiag /test:DNS
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = NJ-DC1-2K8
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: NewJersey\NJ-DC1-2K8
      Starting test: Connectivity
         ......................... NJ-DC1-2K8 passed test Connectivity
Doing primary tests
   Testing server: NewJersey\NJ-DC1-2K8
      Starting test: DNS
         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... NJ-DC1-2K8 passed test DNS
   Running partition tests on : ForestDnsZones
   Running partition tests on : DomainDnsZones
   Running partition tests on : Schema
   Running partition tests on : Configuration
   Running partition tests on : Fleet
   Running enterprise tests on : Fleet.local
      Starting test: DNS
         Summary of test results for DNS servers used by the above domain controllers:
            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
         ......................... Fleet.local passed test DNS
5) C:\Users\Administrator>dcdiag
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = NJ-DC1-2K8
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: NewJersey\NJ-DC1-2K8
      Starting test: Connectivity
         ......................... NJ-DC1-2K8 passed test Connectivity
Doing primary tests
   Testing server: NewJersey\NJ-DC1-2K8
      Starting test: Advertising
         ......................... NJ-DC1-2K8 passed test Advertising
      Starting test: FrsEvent
         ......................... NJ-DC1-2K8 passed test FrsEvent
      Starting test: DFSREvent
         There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... NJ-DC1-2K8 failed test DFSREvent
      Starting test: SysVolCheck
         ......................... NJ-DC1-2K8 passed test SysVolCheck
      Starting test: KccEvent
         ......................... NJ-DC1-2K8 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... NJ-DC1-2K8 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... NJ-DC1-2K8 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... NJ-DC1-2K8 passed test NCSecDesc
      Starting test: NetLogons
         ......................... NJ-DC1-2K8 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... NJ-DC1-2K8 passed test ObjectsReplicated
      Starting test: Replications
         [Replications Check,NJ-DC1-2K8] A recent replication attempt failed:
            From NJ-DC2-2K8 to NJ-DC1-2K8
            Naming Context: DC=ForestDnsZones,DC=Fleet,DC=local
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2014-07-06 20:49:06.
            The last success occurred at 2014-07-06 16:10:47.
            19 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.
         [Replications Check,NJ-DC1-2K8] A recent replication attempt failed:
            From NJ-DC2-2K8 to NJ-DC1-2K8
            Naming Context: DC=DomainDnsZones,DC=Fleet,DC=local
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2014-07-06 21:04:16.
            The last success occurred at 2014-07-06 15:49:54.
            31 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.
         [Replications Check,NJ-DC1-2K8] A recent replication attempt failed:
            From NJ-DC2-2K8 to NJ-DC1-2K8
            Naming Context: CN=Schema,CN=Configuration,DC=Fleet,DC=local
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2014-07-06 20:49:06.
            The last success occurred at 2014-07-06 15:49:54.
            10 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.
         [Replications Check,NJ-DC1-2K8] A recent replication attempt failed:
            From NJ-DC2-2K8 to NJ-DC1-2K8
            Naming Context: CN=Configuration,DC=Fleet,DC=local
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2014-07-06 20:49:06.
            The last success occurred at 2014-07-06 16:06:25.
            29 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.
         [Replications Check,NJ-DC1-2K8] A recent replication attempt failed:
            From NJ-DC2-2K8 to NJ-DC1-2K8
            Naming Context: DC=Fleet,DC=local
            The replication generated an error (8456):
            The source server is currently rejecting replication requests.
            The failure occurred at 2014-07-06 20:49:06.
            The last success occurred at 2014-07-06 16:16:49.
            30 failures have occurred since the last success.
            Replication has been explicitly disabled through the server options.
         ......................... NJ-DC1-2K8 failed test Replications
      Starting test: RidManager
         ......................... NJ-DC1-2K8 passed test RidManager
      Starting test: Services
         ......................... NJ-DC1-2K8 passed test Services
      Starting test: SystemLog
         A warning event occurred. EventID: 0x000003F6
            Time Generated: 07/06/2014   20:17:29
            Event String: Name resolution for the name 2.5.16.172.in-addr.arpa timed out after none of the configured DNS servers responded.
         An error event occurred. EventID: 0x0000168E
            Time Generated: 07/06/2014   20:18:05
            Event String:
            The dynamic registration of the DNS record '9736b2e5-a75e-4991-a481-08c0226ed1c5._msdcs.Fleet.local. 600 IN CNAME NJ-DC1-2K8.Fleet.local.'
failed on the following DNS server:
         A warning event occurred. EventID: 0x000003F6
            Time Generated: 07/06/2014   21:04:01
            Event String: Name resolution for the name 1.0.0.127.in-addr.arpa timed out after none of the configured DNS servers responded.
         ......................... NJ-DC1-2K8 failed test SystemLog
      Starting test: VerifyReferences
         ......................... NJ-DC1-2K8 passed test VerifyReferences
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : Fleet
      Starting test: CheckSDRefDom
         ......................... Fleet passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Fleet passed test CrossRefValidation
   Running enterprise tests on : Fleet.local
      Starting test: LocatorCheck
         ......................... Fleet.local passed test LocatorCheck
      Starting test: Intersite
         ......................... Fleet.local passed test Intersite
6) C:\Users\Administrator>repadmin /showrepl NJ-DC1-2K8
NewJersey\NJ-DC1-2K8
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
DSA invocationID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
==== INBOUND NEIGHBORS ======================================
DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        30 consecutive failure(s).
        Last success @ 2014-07-06 16:16:49.
CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        29 consecutive failure(s).
        Last success @ 2014-07-06 16:06:25.
CN=Schema,CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        10 consecutive failure(s).
        Last success @ 2014-07-06 15:49:54.
DC=DomainDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 21:04:16 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        31 consecutive failure(s).
        Last success @ 2014-07-06 15:49:54.
DC=ForestDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC2-2K8 via RPC
        DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
        Last attempt @ 2014-07-06 20:49:06 failed, result 8456 (0x2108):
            The source server is currently rejecting replication requests.
        19 consecutive failure(s).
        Last success @ 2014-07-06 16:10:47.
Source: NewJersey\NJ-DC2-2K8
******* 31 CONSECUTIVE FAILURES since 2014-07-06 16:16:49
Last error: 8456 (0x2108):
            The source server is currently rejecting replication requests.
7) C:\Users\Administrator>repadmin /showrepl NJ-DC2-2K8
NewJersey\NJ-DC2-2K8
DSA Options: IS_GC DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL
Site Options: (none)
DSA object GUID: 66803610-2817-4853-ad3b-70c32a78c04a
DSA invocationID: 3e8ee380-a165-4cef-b311-dadcf30f8406
==== INBOUND NEIGHBORS ======================================
DC=Fleet,DC=local
    NewJersey\NJ-DC1-2K8 via RPC
        DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
        Last attempt @ 2014-07-06 21:04:22 failed, result 8457 (0x2109):
            The destination server is currently rejecting replication requests.
        53 consecutive failure(s).
        Last success @ 2014-06-26 23:01:29.
CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC1-2K8 via RPC
        DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
        Last attempt @ 2014-07-06 20:52:11 failed, result 8457 (0x2109):
            The destination server is currently rejecting replication requests.
        10 consecutive failure(s).
        Last success @ 2014-06-26 22:56:54.
CN=Schema,CN=Configuration,DC=Fleet,DC=local
    NewJersey\NJ-DC1-2K8 via RPC
        DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
        Last attempt @ 2014-07-06 20:52:11 failed, result 8457 (0x2109):
            The destination server is currently rejecting replication requests.
        7 consecutive failure(s).
        Last success @ 2014-06-26 22:56:56.
DC=DomainDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC1-2K8 via RPC
        DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
        Last attempt @ 2014-07-06 20:52:11 failed, result 8457 (0x2109):
            The destination server is currently rejecting replication requests.
        7 consecutive failure(s).
        Last success @ 2014-06-26 22:57:01.
DC=ForestDnsZones,DC=Fleet,DC=local
    NewJersey\NJ-DC1-2K8 via RPC
        DSA object GUID: 9736b2e5-a75e-4991-a481-08c0226ed1c5
        Last attempt @ 2014-07-06 20:52:11 failed, result 8457 (0x2109):
            The destination server is currently rejecting replication requests.
        23 consecutive failure(s).
        Last success @ 2014-06-26 22:57:03.
Source: NewJersey\NJ-DC1-2K8
******* 53 CONSECUTIVE FAILURES since 2014-06-26 23:01:29
Last error: 8457 (0x2109):
            The destination server is currently rejecting replication requests.
Please someone go through these different errors and walk me through exactly what I got to do to fix them.
Thanks

Hi,
Actually, I made copies of those VMs to my external usb 3.0 hdd, so I can load up some of the VMs from it than from my internal hdd since it would freeze on my internal one sometimes. Copied ones worked fine for few days until recently when I started having
these different issues. I did look at USN rollback and applied the fix, didn't work. For the past few days, I been spending endless hours on fixing them but it doesn't look like they are going to be fixed. It's driving me crazy and the bad news is that I've
no backup of my data. I got 2 DC and both have these issues.
Building new domain controllers in VMs won't be a problem for me but I'm worried about losing my AD database in both DCs which includes user and computer accounts and a bunch GPOs.
I'm a newbie to the server environment. Can you please walk me through on exactly how can I save AD database if possible before I start doing the cleanup process on both of my DCs. I read some articles online which provide instructions on how can I cleanup
the AD with Metadata and take both DCs offline but it's all confusing to me. They don't explain anything about saving AD database rather demoting bad DCs. If you know a fix for my DCs that I can apply, so I won't have do it all over and save time. Please let
me know step by step process or whatever you could help me to bring those 2 DCs backup.
Thanks

BDB replication samples

Hello
I am BDB newbie, I want to use BDB replication in our project,and where can I find BDB replication sample source code?
The samples attached to BDB installation package is too simple , I need very detailed source code.
thanks
Kevin An

As the replication group contains one master and two clients, so I just tested the
DB_REPMGR_ACKS_ONE policy.
Compare the DB_REPMGR_ACKS_ONE and DB_REPMGR_ACKS_ALL policy,
the throughput is same, 200 transactions/s, but the average response time improves a lot, 3ms/transactions.
But I should strictly guarantee the database consistency, so DB_REPMGR_ACKS_ALL is preferred.

Connectivity for SAN replication

I am a newbie in the SAN world so hope am asking the right questions.
We are looking into replacing our aging SAN. As part of the replacement, managemnt is thinking of placing a secondary SAN at one of our remote locations for backup & DR purposes.
My question revolves around providing connectivity between the two SANS. I have been asked to look into a dedicated point-to-point connection for the SAN replication. Not counting the actual SAN hardware, what other hardware would I need? Am I bacically building an independent network for this? Why this route instead of over our corporate WAN? Any good recommended reading for learning about the SAN world?
Brent

Hi, Brent,
I agree with Mike. I originally posted this before I saw his reply.
Here are a couple of good Cisco-specific document to start with:
http://www.cisco.com/en/US/solutions/ns340/ns517/ns224/ns378/net_design_guidance0900aecd800ed146.pdf
http://www.cisco.com/go/storage
Your options are either native FC over some sort of fiber transport (dark fiber, CWDM, DWDM, SONET) or FCIP over a WAN link. Native FC is usually for synchronous replication for distances up to 200 km for large bandwidth requirements. FCIP is usually for asynchronous replication at longer distances with less bandwidth. The transport largely dictates the hardware. FCIP is generally cheaper.
If you go the FCIP route, a dedicated link is preferable to make sure replication traffic has predictable latency and bandwidth, but you can share an existing link if you have to. Basic QOS is available in this case. Also, FCIP on Cisco devices has special capabilities to help you get the most out of your bandwidth (TCP optimizations, compression, write acceleration, etc.).
Regards,
Phil Lowden

Error while creating MV replication group object

Hi,
I am getting error while creating replication group object. I tried to create using OEM and SQLPlus
OEM error
This error while creating M.V. rep. group object
There is a table or view named SCOTT.EMP.
It must be dropped before a materialized view can be created.
In SQLPLUS
SQL> CONNECT MVIEWADMIN/MVIEWADMIN@SWEET
Connected.
SQL>
SQL> BEGIN
2 DBMS_REPCAT.CREATE_MVIEW_REPOBJECT (
3 gname => 'SCOTT',
4 sname => 'KARTHIK',
5 oname => 'emp_mv',
6 type => 'SNAPSHOT',
7 min_communication => TRUE);
8 END;
9 /
BEGIN
ERROR at line 1:
ORA-23306: schema KARTHIK does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 2840
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 773
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 5570
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 82
ORA-06512: at "SYS.DBMS_REPCAT", line 1332
ORA-06512: at line 2
Please not already I have created KARTHIK schema.

Arthik,
I think I know what may have happened.
As I can see you are trying to create support for an updateable materialized view.
You have to make sure the name of the schema that owns the materialized view is the same as the schema owner of the master table (at master site).
From the code you have shown, I bet the owner of table EMP is SCOTT.
From the other hand, you want to create materialized view EMP_MV under schema KARTHIK that refers to table SCOTT.EMP at master site.
According to the documentation, the schema name used in DBMS_REPCAT.CREATE_MVIEW_REPOBJECT must be same as the schema that owns the master table.
Please check the documentation at the link below
http://download.oracle.com/docs/cd/B19306_01/server.102/b14227/rarrcatpac.htm#i109228
I tried to reproduce your example in my environment, and I got exactly the same error which actually confirms my assumption that the reason for the error is the fact that you tried to create the materialized view in a schema with different name than the one where master table exists.
I'll skip some of the steps that I used to create the replication environment.
I have two databases, DB1.world and DB2.world
On DB2.world I will generate replication support for table EMP which belongs to user SCOTT
SQL> conn scott/*****@DB2.world
Connected.
SQL>create materialized view log on EMP with primary key;
Materialized view log created.
SQL>
SQL>conn repadmin/*****@DB2.world
Connected.
SQL>BEGIN
2       DBMS_REPCAT.CREATE_MASTER_REPGROUP(
3         gname => 'GROUPA',
4         qualifier => '',
5         group_comment => '');
6*   END;
PL/SQL procedure successfully completed.
SQL>BEGIN
2       DBMS_REPCAT.CREATE_MASTER_REPOBJECT(
3         gname => 'GROUPA',
4         type => 'TABLE',
5         oname => 'EMP',
6         sname => 'SCOTT',
7         copy_rows => TRUE,
8         use_existing_object => TRUE);
9*   END;
10 /
PL/SQL procedure successfully completed.
SQL> BEGIN
2       DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT(
3         sname => 'SCOTT',
4         oname => 'EMP',
5         type => 'TABLE',
6         min_communication => TRUE);
7    END;
8 /
PL/SQL procedure successfully completed.
SQL>execute DBMS_REPCAT.RESUME_MASTER_ACTIVITY(gname => 'GROUPA');
PL/SQL procedure successfully completed.
SQL> select status from dba_repgroup;
STATUS
NORMAL                                                                          Now let's create updateable materialized view at DB1. Before that I want to let you know that I created one sample in DB1 user named MYUSER. MVIEWADMIN is Materialized View administrator.
SQL>conn mviewadmin/****@DB1.world
Connected.
SQL>   BEGIN
2       DBMS_REFRESH.MAKE(
3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
4         list => '',
5         next_date => SYSDATE,
6         interval => '/*1:Hr*/ sysdate + 1/24',
7         push_deferred_rpc => TRUE,
8         refresh_after_errors => TRUE,
9         parallelism => 1);
10    END;
11 /
PL/SQL procedure successfully completed.
SQL>   BEGIN
3       DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP(
5         gname => 'GROUPA',
7         master => 'DB2.wolrd',
9         propagation_mode => 'ASYNCHRONOUS');
11    END;
12 /
PL/SQL procedure successfully completed.
SQL>conn myuser/*****@DB1.world
Connected.
SQL>CREATE MATERIALIZED VIEW MYUSER.EMP_MV
2    REFRESH FAST
3    FOR UPDATE
4    AS SELECT EMPNO, ENAME, JOB, MGR, SAL, COMM, DEPTNO, HIREDATE
5*      FROM   [email protected];
Materialized view created.
SQL>conn mviewadmin/******@DB1.world
Connected.
SQL> BEGIN
2       DBMS_REFRESH.ADD(
3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
4         list => 'MYUSER.EMP_MV',
5         lax => TRUE);
6    END;
7 /
PL/SQL procedure successfully completed.And now lets run CREATE_MVIEW_REPOBJECT.
SQL>   BEGIN
2       DBMS_REPCAT.CREATE_MVIEW_REPOBJECT(
3         gname => 'GROUPA',
4         sname => 'MYUSER',
5         oname => 'EMP_MV',
6         type => 'SNAPSHOT',
7         min_communication => TRUE);
8    END;
9 /
BEGIN
ERROR at line 1:
ORA-23306: schema MYUSER does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 2840
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 773
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 5570
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 82
ORA-06512: at "SYS.DBMS_REPCAT", line 1332
ORA-06512: at line 3 I reproduced exactly the same error message.
So the problem is clearly in the schema name that owns the materialized view.
Now lets see if what would happen if I create the MV under schema SCOTT which has the same name as the schema on DB2.world where the master table exists.
SQL>conn scott/****@DB1.world
Connected.
SQL>CREATE MATERIALIZED VIEW SCOTT.EMP_MV
2    REFRESH FAST
3    FOR UPDATE
4    AS SELECT EMPNO, ENAME, JOB, MGR, SAL, COMM, DEPTNO, HIREDATE
5*      FROM   [email protected];
Materialized view created.
SQL>conn mviewadmin/******@DB1.world
Connected.
SQL> BEGIN
2       DBMS_REFRESH.ADD(
3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
4         list => 'SCOTT.EMP_MV',
5         lax => TRUE);
6    END;
7 /
PL/SQL procedure successfully completed.And now lets run CREATE_MVIEW_REPOBJECT.
SQL>   BEGIN
2       DBMS_REPCAT.CREATE_MVIEW_REPOBJECT(
3         gname => 'GROUPA',
4         sname => 'SCOTT',
5         oname => 'EMP_MV',
6         type => 'SNAPSHOT',
7         min_communication => TRUE);
8    END;
PL/SQL procedure successfully completed.As you can see everything works fine when the name of the schema owner of the MV at DB1.world is the same as the schema owner of the master table at DB2.world .
-- Mihajlo
Message was edited by:
tekicora

Replication of a BP in CRM as a FI Vendor in ECC for Grants Management

Hi,
We are implenting SAP CRM 7 with SAP ECC for Grants Management, integrated with FI AP (we're not using PSCD).
For BP replication we followed the next steps, however something looks it is incorrect because my BDOC still shows errors:
The middleware settings had been completed between the CRM and the ECC system.
- Site, Suscription and replication from CRM to SAP ECC are in placed
   -The next replication object are activated:
    -All Business Partners (MESG)   (BUPA_MAIN)
    -All Busines Partner Relationships (MESG) (BUPA_REL)
    -All Business Transactions (MESG)
    -Grantor Program Management
Also we implemented the next steps:
1) Define the number ranges for BP groupings in CRM: This number range would be internal in CRM and External in ECC.
CRM (IMG) -> Customer Relationship Management -> Cross-Application Components -> SAP Business Partner -> Basic Settings ->
Number Ranges and Groupings
2) Since the BP would be replicated as a BP in ECC we define the same number ranges in ECC too:
ERP (IMG) -> Customer Relationship Management -> Cross-Application Components -> SAP Business Partner -> Basic Settings ->
Define Groupings and Assign Number Ranges
3) Activate the post-processing framework: (Business processes CVI_02 and CVI_04 in Component AP-MD)
ERP (IMG) -> Cross-Application Components -> General Application Functions ->Postprocessing Office -> Business Processes->
Activate Creation of Postprocessing Orders
4) Activate PPO Requests for Platform Objects in the Dialog:
ERP (IMG) -> Cross-Application Components -> Master Data Synchronization -> Synchronization Control -> Synchronization
Control -> Activate PPO Requests for Platform Objects in the Dialog
Edited by: Lyda Osorio on Oct 9, 2009 7:25 AM

For CRM I had the following FM activated:
BPOUT     BUPA     100000     CRM_BUPA_OUTB_RENTED_ADDRESS     X
BPOUT     BUPA     200000     BUPA_MWX_BDOC_CREATE_MAIN     X
BPOUT     BUPA     300000     CRM_BUPA_OUTB_MARKETING_ATTR     X
BPOUT     BUPA     400000     VEND_MWX_CREATE_MAIN_BDOC     X
BPOUT     BUPA     1000000     BUPA_OUTBOUND_MAIN     X
BPOUT     BUPR     100000     BUPA_MWX_BDOC_CREATE_REL     X
BPOUT     BUPX     1000000     MDS_BUPA_OUTBOUND     X
CLEAR     BUPA     1000000     BUPA_OUTBOUND_CLEAR_FLAGS     X
CRMIN     BUAG     100000     CRM_BUAG_MWX_PROCESS_EXT_STRUC     X
CRMIN     BUPA     90100     CRM_BUPA_INBOUND_SET_BUAG_FLAG     X
CRMIN     BUPA     1000000     BUPA_INBOUND_MAIN_CENTRAL     X
CRMIN     BUPA     1100000     CRM_BUPA_INBOUND_MAIN_MD     X
CRMIN     BUPA     1200000     CRM_BUPA_BDOC_MAP_MAIN     X
CRMIN     BUPA     1400000     CRM_BUPA_KOREA_INBOUND_MAP     X
CRMIN     BUPA     2000000     ABA_FSBP_INBOUND_MAIN     X
CRMIN     BUPR     1000000     BUPA_INBOUND_REL_CENTRAL     X
CRMIN     BUPR     1100000     CRM_BUPA_INBOUND_REL_MD     X
CRMIN     BUPR     1200000     CRM_BUPA_BDOC_MAP_REL     X
CRMOU     BUAG     100000     CRM_BUAG_MWX_FILL_EXT_FROM_MEM     X
CRMOU     BUPA     1000000     BUPA_OUTBOUND_BPS_FILL_CENTRAL     X
CRMOU     BUPA     1200000     CRM_BUPA_OUTB_BPS_FILL_MD     X
CRMOU     BUPR     1000000     BUPA_OUTBOUND_BPR_FILL_CENTRAL     X
CRMOU     BUPR     1200000     CRM_BUPA_OUTB_BPR_FILL_MD     X
CRMOU     BUPR     1300000     CRM_BUPA_BDOC_BPR_FILL_DATA     X
EXTR     BUAG     100000     CRM_BUAG_MAIN_GET_ID_LIST     X
MERGE     BUPA     1000000     MERGE_BUPA_CENTRAL     X
MERGE     BUPA     2000000     MERGE_BUPA_FINSERV     X
MERGE     BUPR     1000000     MERGE_BUPR_CENTRAL     X
PXYIN     BUPA     1000000     BUPA_INBOUND     X
R3AOU     BUPA     100000     BUPA_MWX_BDOC_UP_CURRSTATE_SET     X
XIIN     BUPA     1000000     ABA_BUPA_MAP_PROXY_TO_DDIC     X
XIIN     BUPA     2000000     ABA_FSBP_MAP_PROXY_TO_DDIC     X
XIIN     BUPA     2100000     ABA_FSBP_MAP_PROXY_TO_DDIC_1     X
XIIN     BUPR     1000000     ABA_BUPR_MAP_PROXY_TO_DDIC     X
XIOUT     BUPA     1000000     ABA_BUPA_MAP_DDIC_TO_PROXY     X
XIOUT     BUPR     1000000     ABA_BUPR_MAP_DDIC_TO_PROXY     X

ISE 1.2 CWA with Multiple PSNs - SessionID Replication / Session Expired

Hi all.
I have a (2) Policy Services Nodes (PSNs) in an ISE 1.2 deployment running patch 1. We are using Wireless MAB and CWA on 5760 Wireless LAN Controllers running v3.3.3.
We are hitting an issue wherein a client first passes MAB and then gets redirected to a CWA custom portal. The client then receives a Session Expired message. This seems to be related to the fact that CWA is technically a 2-stage authentication (MAB by the WLC and then CWA by the client). Specifically, it seems to happen when the WLC makes its MAB RADIUS access-request to PSN-1 and then the client comes in to PSN-2 to complete the CWA. This issue does not happen when only one PSN is in use and all authentication traffic (both MAB RADIUS and CWA) is directed at a single PSN.
Clients resolve the FQDN in the redirect URL using public DNS and a public DNS zone file (call it cwa-portal.example.com). cwa-portal.example.com has two A records for the two PSN nodes. DNS is responding to queries using DNS round-robin.
I have the PSNs configured in a Node Group for session information replication between PSNs, but this doesn't seem to make a difference in behavior.
So I ask:
What is the recommended architecture for CWA when using more than one PSN? It seems that you would need to keep the two authentication flows pinned together so that they both hit the same PSN when using more than one PSN in a deployment. A load balancer balancing on the SessionID string comes to mind (both the RADIUS MAB request and the CWA URL contain this unique per-client SessionID), but that seems terribly overbuilt for a seemingly simple problem. On the other hand, it also seems like using a Node Group setup should easily be able to replicate client SessionIDs to all nodes in the deployment so that this isn't an issue. I.e., if the WLC authenticates MAB on PSN-1, then PSN-1 should tell the Node Group about it such that when the client CWA's on PSN-2, PSN-2 doesn't respond with a Session Expired message.
Is there any Cisco documentation that talks about this?
Possibly related:
https://supportforums.cisco.com/discussion/12131531/ise-12-guest-access-session-expired
Justin

Tim,
Thanks for your reply and confirming my suspicion. Hopefully a future version of ISE will provide automated SessionID synchronization among PSNs so that front-end finagling in a multi-PSN environment won't be necessary.
For anyone else with this issue who for whatever reason can't implement a load balancer(s), I built an automated EEM applet running on a "watchdog" switch (3750 running 12.2(55)SEE9) using IPSLA tracking that senses when PSN1 is down and then
modifies an ASA to change its client-facing NAT statement for PSN1 to PSN2
modifies the primary and HA wireless LAN controllers to change its MAB RADIUS aaa server group to use PSN2
reverts the ASA and WLCs to using PSN1 when PSN1 is detected up and running again
The applet ensures the SessionID authentications stay "glued" together so that both WLCs and the client hit the same PSN for both stages of authentication. It's failover only, not a load balancing solution, but it meets our current project's need for an automated HA environment.
PM me if you want the code. I'm have a little too much going on ATM to sanitize and post it. :)
Justin

MYSQL 55 to Oracle 11gr1 replication(oneway) - can not replicate

I have setup golden gate replication between mysql 55 and oracle 11gr1. While trying to setup the initial load, I do'nt see any data push to oracle from mysql.
What could be wrong in my setup.? has anyone tried this kind of setup? i see the the report for replicat and it says data is not replicated. while extract shows that 4 rows from table are taken for insert.

Hi Stev
I am trying to do the initial load process
On source (MYSQL 55)
database (ggtest and table test)
table test has
TEST(COL1 INT)
manager is running on default port 7809
manager parameter file is defined with (PORT 7809)
There is initial load extract (EINI01) -->
ADD EXTRACT EINI01
param file
EXTRACT EINI01
SOURCEDB [email protected], USERID ggsdev, PASSWORD ggsdev
RMTHOST 192.168.75.116, MGRPORT 7809
RMPTTASK REPLICAT, GROUP RINI01
TABLE ggtest.TEST
On target oracle 11gr1 (11.1.0.6)
Database in archive log mode, with minimum supplemental logging.
replicat process
ADD REPLICAT RINI01
Parameter file for replicat
REPLICAT RINI01
USERID ggs_owner, PASSWORD ggs_owner ( added in target database)
ASSUMTARGETDEFS
SETENV (NLS_LANG="AMERICAN_AMERICA.WE8MSWIN1252")
MAP ggtest.TEST , TARGET GGTEST.TEST;
-- to start the initial load ( mysql side has 4 rows, oracle has no row )
on source, i ran the command
ggsci> start extract eini01
I can see on report, extract has picked 4 rows for insert, but on replicat side no replication done. No error reported in gserr.log and there was a communication between source side of extract with traget side manager and sunsequently repliacat on target was started by manager and stopped normally. but no rows replicated.
Between oracle-to-oracle there is no problem. But my actual project is to setup from mysql to oracle (one way replication).
let me know if you need any other info.
Thanks
rafey

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

Newbie in 9i replication

Similar Messages

Maybe you are looking for