TimesTen replication problem

Similar Questions

• Upgrade of Windows 2003 to 2012 r2 DC replication problem

  Hello

  I added R2 2012 Windows server to windows 2003 sp2 (primary DC) DC and promotes as DC. After the promotion, I run dcdiag and it shows errors.

  Each of the servers have three NICs connected to different networks.

  Please help me with your expertise since I have to raise this Monday.

  Thank you

  Kind regards

  Charaf-eddine

  Here the dcdiag output new DC

  Directory Server diagnosis

  Perform the initial configuration:

  Trying to find the server at home...

  Home Server = CADPDC1

  * Identified AD forest.
  Made the initial collection of information.

  Make the required initial tests

  Test server: Default-First-Site-Name\CADPDC1

  Commencement of the trial: connectivity

  CADPDC1.engineer.com host name resolution error by

  IPv6 stack.

  WARNING: could not confirm the identity of this server in the

  Directory and names returned by DNS servers. Host name

  fixed error 0x2af9 "host is known."

  ......................... CADPDC1 passed test connectivity

  Primary testing

  Test server: Default-First-Site-Name\CADPDC1

  Commencement of the trial: advertising

  WARNING: DsGetDcName returned information for

  \\cadpdc. Engineer.com, when we tried to reach CADPDC1.

  SERVER IS NO ANSWER or IS NOT considered AS APPROPRIATE.

  ......................... CADPDC1 was not able to test advertising

  Beginning of the test: FrsEvent

  There are warning or error events in the last 24 hours after the

  SYSVOL is shared.  Don't not SYSVOL replication problems can cause

  The Group of political problems.
  ......................... CADPDC1 test FrsEvent

  Commencement of the trial: DFSREvent

  ......................... CADPDC1 test DFSREvent

  Commencement of the trial: SysVolCheck

  ......................... CADPDC1 test SysVolCheck

  Beginning of the test: KccEvent

  ......................... CADPDC1 test KccEvent

  Beginning of the test: KnowsOfRoleHolders

  [CADPDC] DsBindWithSpnEx() failed with the error-2146893022,

  The name main target is incorrect...
  ATTENTION: CADPDC is the owner of the schema, but does not meet the DS RPC

  Bind.

  [CADPDC] LDAP bind failed with error 8341,

  A directory service error has occurred...
  ATTENTION: CADPDC is the owner of the schema, but does not respond to LDAP

  Bind.

  ATTENTION: CADPDC is the owner of the domain, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of the domain, but does not respond to LDAP

  Bind.

  ATTENTION: CADPDC is the owner of PDC, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of PDC, but does not respond to the LDAP bind.

  ATTENTION: CADPDC is the owner of RID, but does not meet the DS RPC

  Bind.

  ATTENTION: CADPDC is the owner of RID, but does not respond to the LDAP bind.

  ATTENTION: CADPDC is the owner of Infrastructure Update, but is not

  meet DS RPC Bind.

  ATTENTION: CADPDC is the owner of Infrastructure Update, but is not

  respond to LDAP Bind.

  ......................... CADPDC1 failed test KnowsOfRoleHolders

  Beginning of the test: MachineAccount

  ......................... CADPDC1 test MachineAccount

  Beginning of the test: NCSecDesc

  ......................... CADPDC1 passed test NCSecDesc

  Beginning of the test: NetLogons

  Cannot connect in the NETLOGON share. (\\CADPDC1\netlogon)

  [CADPDC1] An net use or LsaPolicy operation failed with error 67.

  The network name was not found...

  ......................... CADPDC1 failed test NetLogons

  Commencement of the trial: ObjectsReplicated

  ......................... CADPDC1 test ObjectsReplicated

  From test: Replications

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = ForestDnsZones, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = DomainDnsZones, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: CN = Schema, CN = Configuration, DC = engineering, DC = com

  The replication generated an error (1727):

  The remote procedure call failed and did not execute.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:06.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: CN = Configuration, DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:07.

  1 failures have occurred since the last success.

  [Check the replications, CADPDC1] A recent replication attempt failed:

  From CADPDC to CADPDC1

  Naming context: DC = engineering, DC = com

  The replication generated an error (-2146893022):

  The name main target is invalid.

  The failure occurred at 2014-06-27 17:05:59.

  The last success occurred at 2014-06-27 17:01:21.

  1 failures have occurred since the last success.

  ......................... CADPDC1 failure test replications

  Beginning of the test: RidManager

  ......................... CADPDC1 failed test RidManager

  Commencement of the trial: Services

  ......................... CADPDC1 test passed Services

  Beginning of the test: SystemLog

  A warning event occurred.  Event ID: 0x000727A5

  Generated time: 27/06/2014-17:01:38

  The event string:

  The WinRM service is not listening to the WS-Management requests.

  A warning event occurred.  Event ID: 0 x 80050004

  Generated time: 27/06/2014-17:05:03

  The event string:

  HP 1 GB 2 332T adapter ports Ethernet: the network link is down.  Check that the network cable is connected correctly.

  A warning event occurred.  Event ID: 0xA004001B

  Generated time: 27/06/2014-17:05:06

  The event string: HP NC112T PCIe Gigabit Server Adapter

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:39

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was LDAP/cadpdc.engineer.com/*** Email address is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:39

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was ldap/cadpdc.engineer.com/*** address email is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:41

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was of cadpdc$. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:43

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was GC/cadpdc.engineer.com/engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  A warning event occurred.  Event ID: 0x000727AA

  Generated time: 27/06/2014-17:05:43

  The event string:

  The WinRM service could not create the following SPNS: WSMAN/CADPDC1.engineer.com; WSMAN/CADPDC1.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:55

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was cifs/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  A warning event occurred.  Event ID: 0 x 84350444

  Generated time: 27/06/2014-17:05:58

  The event string:

  Information System Officer: health: Post errors have been detected.  One or more errors of Power-On-Self-Test were detected when the server starts.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:59

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name was E3514235-4B06-11D1-AB04-00C04FC2DCD2/5122bd13-c8ac-4265-a879-3a6831224994/*** Email address is removed from the privacy *. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:05:59

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was ldap/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000410B

  Generated time: 27/06/2014-17:05:59

  The event string:

  The request for a new account identifier pool failed. The operation will be retried until the request succeeds. The error is

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:06:07

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was LDAP/cadpdc.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 27/06/2014-17:06:30

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041D

  Generated time: 2014/06/27 17:07:07

  The event string:

  The processing of Group Policy failed. Windows could not resolve the user name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 2014/06/27 17:11:32

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 27/06/2014-17:16:33

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  An error event occurred.  Event ID: 0 x 40000004

  Generated time: 27/06/2014-17:16:38

  The event string:

  The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server of cadpdc1$. The target name used was LDAP/5122bd13-c8ac-4265-a879-3a6831224994._msdcs.engineer.com. This indicates that the target server could not decrypt the ticket provided by the customer. This can occur when target server principal name (SPN) is registered on one different account that the target service uses. Ensure that the target THAT SPN is registered only on the account used by the server. This error can also occur if the password service target account is different from what is set up on the Kerberos key for this service target Distribution Center. Make sure that the service on the server and the KDC are configured to use the same password. If the server name is not complete, and the target domain (ENGINEER.COM) is different from the customer area (ENGINEER.COM), check if it is the same name of server accounts in these two areas, or use the fully qualified name to identify the server.

  An error event occurred.  Event ID: 0x0000041F

  Generated time: 2014/06/27 17:21:35

  The event string:

  The processing of Group Policy failed. Windows could not resolve the computer name. This can be caused by one or more of the following:

  ......................... CADPDC1 failed test SystemLog

  Commencement of the trial: VerifyReferences

  ......................... CADPDC1 test VerifyReferences

  Running partition tests: ForestDnsZones

  Beginning of the test: CheckSDRefDom

  ......................... ForestDnsZones passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... ForestDnsZones passed test

  CrossRefValidation

  Running partition tests: DomainDnsZones

  Beginning of the test: CheckSDRefDom

  ......................... DomainDnsZones passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... DomainDnsZones passed test

  CrossRefValidation

  Running partition tests: schema

  Beginning of the test: CheckSDRefDom

  ......................... Schema passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... Schema passed test CrossRefValidation

  Running partition tests: Configuration

  Beginning of the test: CheckSDRefDom

  ......................... Configuration test past CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ......................... Configuration test past CrossRefValidation

  Running partition tests: engineer

  Beginning of the test: CheckSDRefDom

  ... engineer passed test CheckSDRefDom

  Beginning of the test: CrossRefValidation

  ... engineer passed test CrossRefValidation

  Running tests of the company: engineer.com

  Commencement of the trial: LocatorCheck

  ... engineer.com passed test LocatorCheck

  Commencement of the trial: cross-site

  ... engineer.com passed test intersite

  Hi Chamarasi,

  I suggest that you post the application on Microsoft TechNet forum because we have experts working on these issues. You can check the link to post the same query on TechNet:

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  Please do not hesitate to contact us if you have other questions related to Windows.

• ACS 3.2 (2) Build 5 replication problem

  Hi all

  There are two ACS servers, sits inside an ASA 5510 at Headquarters and the other is inside an ASA 5510 on the hot site.

  These 5510 s ASA have been developed to replace two 515Es PIX and the claim is that since the ASAs went replication has stopped working. Of course, it makes no sense to me because there is communication between the ACS server and the firewall is down not anything whenever "replicate now" is issued.

  Unfortunately, I dunno much about ACS then is there something I can look for to help troubelshoot it ACS newspapers say

  WARNING cannot replicate to '4' Server - server does not

  That doesn't help us much, this is a way to get more detailed info journal which could indicate a problem? Thank you.

  Hello

  ACS uses the port TCP/2000 for replication. This port is also used by the skinny Protocol, making the port used by the ACS replication process.

  Fails replication of the ACS from the primary to the secondary, primary school reported that he cannot contact the secondary, and secondary shows any replication of the primary activity.

  A firewall between the two servers, ACS is configured to inspect the skinny Protocol, which uses the same port (TCP/2000) that the ACS replication process.

  If you do not have a call manager behind your firewall, please disable

  Skinny inspect if it is enabled.

  #Under overall policy, take the skinny inspection out of the inspection_default #class.

  don't inspect skinny

  You need to do this on both sides.

  HTH

  JK

  Please evaluate the useful messages-

• V3.3.4 replication problems

  I just upgraded to 3.3.4, and I see a problem with replication. I have two ACS servers and they are authenticating with a server CrytoCard. So I configured the external DB on both servers to point to it. I created the users and they are underlined as external DB. Everything works perfectly, even failover if I close the services on the main server.

  However when I replicate the failover doesn't work anymore. What I see is if I look at a user on the server to backup the password for all users authentication section is 'unknown Radius server. I choose the CryptoCard server and everything works fine again.

  Any ideas how I can fix/fix this?

  Any help would be appreciated. TAC also works on this subject, but I wanted to see if someone else has experianced this problem.

  BTW this forum works on a windows server...

  I think we can delete the old entry from the database that ACS will not re-index numbers but am not very sure about this one.

  Kind regards

  Vivek

• ACS replication problem

  I have two ACS with replication configured. Manual replication works fine, but when setting up scheduled replication, server said "preliminary checks indicate a unnecessary outgoing replication - completed cycle. Even if the new features have been added to the main server, replication is irrelevant.

  Any thoughts?

  Please check this bug,

  CSCsd02854 : automatic replication has not triggered after changing the config

  components

  Symptom: When it is configured for automatic replication, only the changes to the users/groups/SPC are replicated automatically. Changes to the configuration of NAS, Admin, PAN, external databases

  components do not replication trigger.

  Conditions: This is seen when the automatic replication (intermittently or at a specific time) is configured.

  Solution: Start the replication manually after configuration changes for the affected

  components have been made.

  http://Tools.Cisco.com/support/BugToolKit/action.do?hdnAction=searchBugs

  Please make sure that the secondary ACS server, we have all the replicated network devices

  from the primary ACS server successfully. If they are not, and we have configured replication scheduled to take place, then we are hitting this bug.

  Kind regards

  ~ JG

  Note the useful messages

• GoldenGate Bidirectional replication problem

  Hello
  
  I followed the below post for two-way replication with GoldenGate
  http://vishaldesai.WordPress.com/2011/02/24/Golden-Gate-bidirectional-replication-Oracle-to-Oracle-example/
  I am not able to do two-way.
  Although I have tested the two streams (from the source to the target and vice-verse) separately (they work well)
  
  my user to
  source side ggs
  ggs1 target side
  
  
  constraint unique error, certainly because of parameter TRANLOGOPTIONS EXCLUDEUSER
  but I mentioned this setting in my respective extracts.
  
  in the snippet next to the source, I used TRANLOGOPTIONS EXCLUDEUSER ggs1
  in the snippet next to the target, I used TRANLOGOPTIONS EXCLUDEUSER ggs
  
  is this correct. If yes then could you help me why my replicat is abending.
  
  
  Details of my scenario:
  
  source side1_
  
  extract
  extract soext119
  SetEnv (ORACLE_SID = GGDB)
  GGS ID USER, PASSWORD ggs12345
  RMTHOST localhost, mgrport 7810
  TRANLOGOPTIONS EXCLUDEUSER ggs1
  -GETAPPLOPS +.
  -IGNOREREPLICATES +.
  RMTTRAIL ./dirdat/rt
  -The DOF INCLUDE ALL THE +.
  TABLE ggs.stocksrc.
  
  replicat
  REPLICAT sorep119
  SetEnv (ORACLE_SID = GGDB)
  ASSUMETARGETDEFS
  GGS ID USER, PASSWORD ggs12345
  -The DOF INCLUDE ALL THE +.
  -HANDLECOLLISIONS +.
  CARD ggs1.stocksrc, ggs.stocksrc of the TARGET.
  
  face 2 source_
  
  replicat
  REPLICAT trep119
  SetEnv (ORACLE_SID = GGDB)
  ASSUMETARGETDEFS
  Ggs1 username, PASSWORD ggs12345
  -The DOF INCLUDE ALL THE +.
  CARD ggs.stocksrc, ggs1.stocksrc of the TARGET.
  
  extract
  EXTRACT text119
  SetEnv (ORACLE_SID = GGDB)
  Ggs1 username, PASSWORD ggs12345
  RMTHOST localhost, 7809 MGRPORT
  TRANLOGOPTIONS EXCLUDEUSER ggs
  -GETAPPLOPS +.
  -IGNOREREPLICATES +.
  RMTTRAIL ./dirdat/rs
  -The DOF INCLUDE ALL THE +.
  TABLE ggs1.stocksrc.
  
  
  
  
  Thank you
  Vikas

  Hello

  1. Why do you use user GG (ggs) at end of replication? Have you tried with another user?

  2. you must exclude the transaction user "ggs" in the source database and exclude ggs1 user transaction in the target database during extraction.

  If you use tables user gg for replication in bi directional certainly, you'll get the constraint violation error.

  Try the below test facility

  1. create the new user next to the source like CBC and create the stocksrc table in the schema of the CBC,

  2. create the new user in the target tgt database and create the stocksrc of the table under schema tgt.

  3 use user ggs for gg admin only in the source also ggs1 for target gg admin and exclude the user transaction gg on the two parameters of the extract.

  side source extracted:

  extract
  extract soext119
  SetEnv (ORACLE_SID = GGDB)
  GGS ID USER, PASSWORD ggs12345
  RMTHOST localhost, mgrport 7810
  TRANLOGOPTIONS EXCLUDEUSER ggs
  -GETAPPLOPS
  -IGNOREREPLICATES
  RMTTRAIL ./dirdat/rt
  -The DOF INCLUDE ALL
  TABLE src.stocksrc.

  replicat
  REPLICAT sorep119
  SetEnv (ORACLE_SID = GGDB)
  ASSUMETARGETDEFS
  GGS ID USER, PASSWORD ggs12345
  -The DOF INCLUDE ALL
  -HANDLECOLLISIONS
  CARD tgt.stocksrc, src.stocksrc of the TARGET.

  Side of the target:

  replicat
  REPLICAT trep119
  SetEnv (ORACLE_SID = GGDB)
  ASSUMETARGETDEFS
  Ggs1 username, PASSWORD ggs12345
  -The DOF INCLUDE ALL
  CARD src.stocksrc, tgt.stocksrc of the TARGET.

  extract
  EXTRACT text119
  SetEnv (ORACLE_SID = GGDB)
  Ggs1 username, PASSWORD ggs12345
  RMTHOST localhost, 7809 MGRPORT
  TRANLOGOPTIONS EXCLUDEUSER ggs1
  -GETAPPLOPS
  -IGNOREREPLICATES
  RMTTRAIL ./dirdat/rs
  -The DOF INCLUDE ALL
  TABLE tgt.stocksrc.

  HTH

• Replication problem

  Hello
  
  I have a very weird and one urgent problem.
  
  (My Source database is 10gR2(10.2.0.3/RedHat4) and my target database is 11gR2(11.2.0.3/RedHat4)
  
  Database of source:* _
  
  extract E_DPRD
  Ogg@OSIRIS1 username, password xxx
  exttrail/oracle/product/goldengate/data/PD
  PURGEOLDEXTRACTS
  DBOPTIONS ALLOWUNUSEDCOLUMN
  TRANLOGOPTIONS ASMUSER sys@ASM_OSIRIS, ASMPASSWORD xxxx
  dynamic wildcardresolve
  TABLE OSIRIS.*;
  OSIRIS TABLEEXCLUDE. TOAD_PLAN_TABLE
  
  extract P_DPRD
  PassThru
  rmthost 10.206.30.129, mgrport 7840
  rmttrail/app/oracle/product/goldengate/data/PD
  table OSIRIS.*;
  
  Target databases:+ _
  
  extract P_DPRD
  PassThru
  rmthost 10.206.30.xxx, mgrport 7840
  rmttrail/app/oracle/product/goldengate/data/PD
  table OSIRIS.*;
  
  All processes are runing and it seems that the 2 databases are synchronized, but the problem is for 4 tables GG replicate all columns! It replicates just the PK and some columns...
  
  Kind regards
  
  Published by: vittel on June 7, 2012 16:53
  
  Published by: vittel on June 7, 2012 16:54

  Keep TABLEEXCLUDE OSIRIS. TOAD_PLAN_TABLE on top of TABLE OSIRIS.* in params.

  If you have enabled trandata now, there will be inconsistency of data on the target database.you need to go to the initial charge once more.

• Active replication Timesten Active

  Hi all

  I have a question about replication with timesten.

  I have two different sites. On each DB server I installed timesten and activated the replcation.

  Now, if the network goes down for 5 h, replication will not occur, and after 5 h, the link comes up.

  Now, after this timesten replication lies in memory, these 5 hours data may have been emptied to the memory database. So, how can I replicate that data to another site?

  Is this possible?

  Kind regards.

  A naïve thought.

  If you require a replication between two 'standards' Oracle databases, you can walk away TimesTen and therefore reduce the complexity of your system?

  Kind regards

  Zlatko

• TimesTen database and replication

  Hello gurus,
  
  I want to know how robust is the transactional replication in real time of TimeTen.
  
  We currently have RDBMS Oracle and using streams and we are planing to use TimesTen in memory DB.
  
  In the current configuration we have challenges with replication using streams and knowing that Oracle is more interested in the development of Golden Gate as replication solution, I wonder how good or robust TimesTen real-time transactional replication is and Oracle is committed to provide the upgrades and updates to the solution of replication of the ot.
  
  You will appreciate your opinion on this.
  
  Thank you
  Solene

  Hi Eric,.

  I'm not biased, because I do not work for Oracle :).

  First of all, what type of replication that we are talking about? Oracle DB-> TimesTen to TimesTen-> Timesten?

  For TimesTen-> Timesten replication, there is only one way - to use the predefined settings. This replication is working very well, unfortunately I did not performance testing, but I trust Chris in this issue. I tested the replication of Active-Standby pair (works with Oracle Clusterware) and it works fine as well.

  For Oracle DB-> TimesTen replication, you have a few options. Will what type of cache group you use? How many operations per second of your DB Oracle is the treatment?
  You can use the predefined TimesTen mechanism or Golden Gate (recommended for high load).

  Hope this helps.

  Best regards
  Gena

• XLA using as a mechanism of replication - Client DSN cannot be used

  Hello
  
  I want to use JMS/XLA for replication, as described in the "of the Java Reference Guide and database developer' for TimesTen version 7.0 (I use Timesten 7.0.2.0.0).
  I create the object data for the target data store with for example:
  
  TargetDataStore myTargetDataStore = new TargetDataStoreImpl ("DSN = sampleDSN");
  
  The "sampleDSN" is a client DSN, configured in sys.odbc.ini:
  
  [sampleDSN]
  TTC_SERVER = lab04
  TTC_SERVER_DSN = tt
  UID = account
  PWDCrypt = 0ad87ad971dc8e4870347b50af54372429a3bbf3
  
  The problem; When the TargetDataStore object is created in the line of code above, I always get this Exception:
  
  Exception in thread "Thread-2" javax.jms.JMSException: failure of SQLDriverConnect (XlaCommon.c, line 48): 01 S 00 0 [TimesTen] [driver ODBC of TimesTen 7.0.2.0.0] Undefined connection attribute "TTC_Server" at line 358 of the /opt/TimesTen/tt70/info/sys.odbc.ini file
  at com.timesten.dataserver.jmsxla.TargetDataStoreImpl.xlaInit (Native Method)
  to com.timesten.dataserver.jmsxla.TargetDataStoreImpl. < init >(Unknown Source)
  to net.kapsch.ngin.timesten.replication.JmsReplication$ MyListener.onMessage (JmsReplication.java:249)
  at com.timesten.dataserver.jmsxla.MessageConsumerImpl.onMessage (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.handleRecord (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.onXlaUpdate (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.waitAndProcessEvents (Native Method)
  to com.timesten.dataserver.jmsxla.MessageConsumerImpl$ XlaSubscriberThread.run (unknown Source)
  javax.jms.JMSException: impossible to extract the XLA error message
  at com.timesten.dataserver.jmsxla.TargetDataStoreImpl.xlaInit (Native Method)
  to com.timesten.dataserver.jmsxla.TargetDataStoreImpl. < init >(Unknown Source)
  to net.kapsch.ngin.timesten.replication.JmsReplication$ MyListener.onMessage (JmsReplication.java:249)
  at com.timesten.dataserver.jmsxla.MessageConsumerImpl.onMessage (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.handleRecord (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.onXlaUpdate (unknown Source)
  at com.timesten.dataserver.jmsxla.XlaSubscriber.waitAndProcessEvents (Native Method)
  to com.timesten.dataserver.jmsxla.MessageConsumerImpl$ XlaSubscriberThread.run (unknown Source)
  
  
  Is there something to change for customer DSN, or can customer THAT DSN is not possible to be used at all...?
  
  Thanks in advance for the help
  Gerald

  That is right. TimesTen replicaiton only woks between homogeneous hosts (same OS, same CPU architecture). You can ask why when you can build with XLA replication that can run heterogenously. The short answer is that replication is a set of features that can easily be built with much broader XLA and also it is much faster than replication based XLA. We watched in the past to support heterogeneous replication. It is certainly not impossible to do, but do it in a way that does not significantly affect performance is more difficult. It might be something we do at some point (who knows), but so far, demand for the functionality of our customer base has been quite low.

  Chris

• Questions about replication configuration

  Hello
  
  We currently have the configuration of the following replication to a backup Timesten hot facility:
  
  CREATE REPLICATION REP1
  A store of DATA of ELEMENT
  MASTERS ds on "host1".
  SUBSCRIBED ds on "host2".
  RETURN TWOSAFE
  ELEMENT b DATASTORE
  MASTERS ds on "host2".
  SUBSCRIBED ds on "host1".
  RETURN TWOSAFE
  STORE ftappttprd on "host1" PREMISES COMMETTRE ACTION COMMETTRE
  RETURN SERVICES OFF WHEN REPLICATION STOPPED
  SUSTAINABLE COMMITMENT ON
  RESUME BACK 300
  Ftappttprd on "host2" LOCAL STORE COMMIT ACTION COMMITTING
  RETURN SERVICES OFF WHEN REPLICATION STOPPED
  SUSTAINABLE COMMITMENT ON
  CVS BACK 300;
  
  1)
  (a) only the part of the sentence 'COMMIT LOCAL ACTION VALIDATION' implies whenever replication fails on the Subscriber, so the update will be hired locally on master? that is, it is actually becomes a commit sustainable.
  (b) only apply to the timeout for replication scenario? What about other cases where commit at the Subscriber cannot be done.
  (2) if we do not have the expression of DISABLE RETURN as above, would be 'SUSTAINABLE ON COMMETTRE' and 'SUMMARY BACK' always to news?
  in other words, if we decide to stop the replication agent after failover mode standby
  -service back end
  -txn on master will commit sustainable
  -the return service will resume automatically when the replication agent is started again (after the replication problem is fixed)
  
  Thank you
  
  Mike

  Here are the answers:

  1)
  (a) only the part of the sentence 'COMMIT LOCAL ACTION VALIDATION' implies whenever replication fails on the Subscriber, so the update will be hired locally on master? that is, it is actually becomes a commit sustainable.

  CJ > if there is a timeout of servcie to return for a transaction twosafe the default behavior is that the transaction state remains "pending" and the appl; ication must include logic to keep retrying the validation until it succeeds or the application decides to abandon. By configuring LOCAL ACTION COMMIT ENTER, when a timeout occurs the transaction committed locally the band except manipulation (or ignore) the return servcie timeout warningf application has no need to make special anythnin.

  (b) only apply to the timeout for replication scenario? What about other cases where commit at the Subscriber cannot be done.

  CJ > it applies to delays. If you get a different kind of validation error then the application must decide what to (force a local commit or rollback).

  (2) if we do not have the expression of DISABLE RETURN as above, would be 'SUSTAINABLE ON COMMETTRE' and 'SUMMARY BACK' always to news?

  CJ > COMMETTRE SUSTAINABLE can be valid deoending on other factors, RETIURN RESUME is not valid (or useful)

  in other words, if we decide to stop the replication agent after failover mode standby
  -service back end
  -txn on master will commit sustainable
  -the return service will resume automatically when the replication agent is started again (after the replication problem is fixed)

  CJ > I guess you mean "failure" of the day before. Yes, with this configuration, you should see the behavior that yopu described above. The curriculum VITAE of RETURN should not be necessary.

• replication of cache stanby group active on the same machine

  Hello
  
  To validate a design of replication, I'm putting in place a pair of active standby of a cache on a group my portable linux (ubuntu). I have installed two data warehouses on the same instance of TT - cgdsn and master2
  
  I created a group of active usermanaged on DS TT cache and began an active standby replication using the following sql:
  
  command > create the pair of Eve active cgdsn on "simulation-t61', master2 on"simulation-t61' acknowledgement STORE cgdsn PORT 21000 TIMEOUT 30 STORE master2 PORT 20000 TIMEOUT 30;
  
  I read in a thread earlier that replication on the same machine will require ports to be expressly provided for in the replication command.
  Here the result to check the status of the main data store:
  < output >
  Oracle@SIMU-T61: ~ $ ttrepadmin showstatus - cgdsn_tt70
  Enter the password for "ora":
  
  State of replication Agent as: 2010-03-14 20:22:43
  
  DSN: cgDSN_tt70
  Process ID: 18496 (started)
  Strategy of replication agent: manual
  Host: Simulation-T61
  RepListener Port: 21000
  Last LSN write time: 0.19340024
  Last LSN forced to disk: 0.19340024
  Replication hold LSN: 0.19320752
  
  Peers in replication:
  Name: MASTER2
  Host: Simulation-T61
  Port: 0 (not connected)
  Replication status: STARTED
  Communication protocol: 24
  
  ISSUER or the threads:
  For: MASTER2
  Start/number: 1
  Send LSN: 0.19320752
  Sent transactions: 0
  Total packets sent: 0
  Check packets sent: 0
  The packets received total: 0
  < / output >
  
  I then tried to reproduce the day before but got following error
  < output >
  Oracle@SIMU-T61: ~ $ ttRepAdmin-duplicate - of cgdsn_tt70 - host "simulation-t61" - keepCG - cacheUid ora - cachePwd ora - localhost "simulation-t61" - verbosity 2 "dsn = master2_tt70; UID =; PWD ="
  Password for "ora":
  * 20:27:02 how to contact remote main demon to the 127.0.1.1 port 17000 *.
  * 20:27:02 double operation ends *.
  TT12039: Could not get port number of TimesTen replication agent on the remote host. The replication agent has not been started or it has just started and has not communicated his port number on the demon TimesTen
  < / output >
  
  Log file
  < output >
  00:30:33.20 Info: 8143: had pid 20405 Hello, type utility (/ usr/lib/oracle/xe/TimesTen/tt70/bin/ttRepAdminCmd - duplicate - of cgdsn_tt70 - host simulation-t61 - keepCG - cacheUid ora - cachePwd ora - localhost simulation-t61-verbosity 2 dsn = master2_tt70;) UID =; PWD =)
  00:30:33.20 Info: 8143: accepts the incoming message from 127.0.1.1 with remote Protocol (we're TimesTen 7.0.5.0.0.tt70, they are 7.0.5.0.0.tt70 TimesTen remote)
  00:30:33.20 Info: 8143: 20405 -: utility program registration
  00:30:33.20 Info: 8143: labour: with request #1336.4606
  00:30:33.20 Info: 8143: labour 1336: socket closed, call for recovery (last cmd was 4607)
  00:30:33.20 Info: 8143: from daRecovery to 20405
  00:30:33.20 Info: 8143: finished daRecovery for pid 20405.
  00:30:33.20 Info: 8143: labour got 20405, not in the restaurant #1335.4608: path = / tmp/master2
  * 00:30:33.20 Err: 8143: TT14000: internal error of TimesTen daemon: Got notInRestore command with data store unknowns "/ tmp/master2."
  00:30:33.20 Info: 8143: labour: with request #1335.4608
  00:30:33.20 Info: 8143: labour 1335: socket closed, call for recovery (last cmd was 4608)
  00:30:33.20 Info: 8143: from daRecovery to 20405
  00:30:33.20 Info: 8143: 20405 -: process is released
  00:30:33.20 Info: 8143: finished daRecovery for pid 20405.
  00:30:34.14 Info: REP: 20246: CGDSN:transmitter.c (1358): TT16114: connect to the MASTER2 on Simulation-T61 (127.0.1.1); Port: 20000
  00:30:35.14 Info: REP: 20246: CGDSN:transmitter.c (1358): TT16114: connect to the MASTER2 on Simulation-T61 (127.0.1.1); Port: 20000
  00:30:36.14 Info: REP: 20246: CGDSN:transmitter.c (1358): TT16114: connect to the MASTER2 on Simulation-T61 (127.0.1.1); Port: 20000
  0
  < / output >
  
  Output of netstat
  < output >
  Oracle@SIMU-T61: ~ $ netstat - a | grep 21000
  TCP 0 0 *: 21000 *: * LISTEN
  < / output >
  I am supposed to provide the port number of my Active ds in order somehow duplicate?
  
  Thank you
  REDA
  
  Published by: user8936481 on March 14, 2010 21:41

  What is the DSN definition for cgdsn_tt70?

  It could be a problem with the - from clause in the - duplicate order. Assuming that your dsn definition is defined with the attribute of DATA store to be similar to the following:

  [mydsn]
  Data store = / tmp/storeds

  And your ttRepAdmin-double command is similar to the following:

  ttRepAdmin-double - mydsn...

  You need the value of the parameter for - the option to reflect the prefix of the file name of the data store. The ttRepAdmin command above should be:

  ttRepAdmin-double - storeds

  That is to say - of mydsn

  becomes

  -of storeds

• Windows Server 2012R2 replication errors

  Hi, just work through exams 2012R2 if it is in a lab environment, but would like some help on this one that I had trouble finding a solution on this one.

  Just to give you a little history, until recently, I had a single DC 2012R2 environment on my lab. About 6 months ago I had to follow the nets below to retrieve my DC after what can't that assume was an unclean shutdown of my host.

  http://blog.Shiraj.com/2014/10/how-to-fix-c00002e2-directory-services-could-not-start-blue-screen/

  https://support.Microsoft.com/en-us/KB/2751452

  I'm working through scenarios without problem until recently.

  I added a 2nd DC to the existing successful domain although while they inspected the State of replication I seem to come through a few questions in relation to the folder sysvol replica don't properly on the additional domain controller.

  The folder and subfolders are but empty during the 2nd DC.

  I run DCDiag on the original domain controller today, the majority of the tests pass ok (some have failed, but I transfer the roles, closing the vms on and outside, as I used it, but the below was obvious as I promoted the 2nd DC):

  There are warning or error events in the last 24 hours after the
  SYSVOL is shared.  Don't not SYSVOL replication problems can cause
  The Group of political problems. (from DCDIAG)

  I ran the monitor of the replication on the original domain controller health and get the 2 outputs following.

  1. the DFS replication service failed to recover from an internal database error on the C: volume. Replication stopped for all folders replicated on this volume until the database is automatically rebuilt. If the database is rebuilt successfully, replication will resume once the reconstruction is complete. If the database cannot be rebuilt, a separate event is generated. If you see this error more than twice in seven days, we recommend that you run Chkdsk on the volume that contains the database. Event ID: 2104

  2. the service stopped DFS replication on the C: volume replication. This failure can occur because the disk is full, the disc is a failure or a quota limit has been reached. Event ID: 2004

  I followed the discussions to try and resolve this problem without a bit of luck, I can also confirm that the disk is not full or failed.

  On the 2nd DC health is:

  This member is waiting for initial replication for replicated folder SYSVOL share and does not currently participate in replication. This delay can occur because the Member is waiting for the replication service DFS retrieve the settings from Active Directory Domain Services replication. After the Member detects that it is part of the replication group, the Member will start the initial replication.

  Where papers on the original domain controller I was also picking up the following event logs:

  Log name: Application
  Source: ESENT
  Date: 16/04/2016 13:51:57
  Event ID: 516
  Task category: registration/recovery
  Level: error
  Keywords: Classic
  User: n/a
  Computer: server.domain

  Description:
  \\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db SRBHT (1388): database \\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db: Page 46 (0x0000002e) due to a timestamp mismatch verification failure.  The timestamp "before" persisted in the paper of record was 0x10fbb, but the current timestamp on page 0 x 11004.  The update 'after' timestamp 0 11017 x which would have updated the time stamp on the page.  Recovery/restore will fail with the error-567.  If this condition persists then please restore it from a previous backup. This problem is probably due to a defective material 'lose' one or more colors on this page in the past. For further assistance diagnosing the problem, contact your hardware vendor.
  The event XML:
  
   
     
      516
      2
      3
      0 x 80000000000000
     
      7033
      Application
      Server
     
   
   
      SRBHT
      1388
      \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db:
      \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db
      46 (0x0000002e)
      0x10fbb
      0 x 11004
      -567
      0 x 11017
   
  

  Log name: Application
  Source: ESENT
  Date: 16/04/2016 13:51:57
  Event ID: 454
  Task category: registration/recovery
  Level: error
  Keywords: Classic
  User: n/a
  Computer: server.domain
  Description:
  \\.\C:\System Volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db SRBHT (1388): database recovery/restore failed with the error unexpected-567.
  The event XML:
  
   
     
      454
      2
      3
      0 x 80000000000000
     
      7034
      Application
      Server
     
   
   
      SRBHT
      1388
      \\.\C:\System volume Information\DFSR\database_6A02_9B3F_29B_F67\dfsr.db:
      -567
   
  

  I think that these are related to my original question, but any advice would be appreciated.

  Thank you

  Please post your query to:

  https://social.technet.Microsoft.com/forums/

  Server issues are better addressed there.

• Failover of applications TimesTen

  I want to know how Timesten application failover.

  If my apps are on the other host with Oracle Clusterware and TimesTen, can my unalterable standby applications link and my access request in writing to actvie link? But I read the paper, it seems that applications must reside on the same host as Oracle Clusterware and TimesTen, right?

  TimesTen supports two mechanisms for connection; direct mode and client/server. With doe directly applications must run on the same computer as the TimesTen database access (which gives by far the best performance). With client/server, it can run on any computer with a TCP/IP connection to the machine hosting the database TimesTen. For client/server applications, TimesTen supports automatic failover of clients that can be used with active replication / standby pair TimesTen if you use Clusterware to manage failover of replication.

  When you use live view, you don't obviously the application regardless of the failover database (because they are strongly coupled). So for this operating mode you failover the database and the application as a whole. Start a new instance of the application to the new active database after failover. Clusterware can be used to automate (see the discussion on 'Advanced availability' in the TimesTen replication guide in the section on the Clusterware).

  With c/o pair replication applications can connect to assets (to perform reads and writes) and forward (for reading only). The watch is "hot".

  Chris

• Replication of VSphere marked as non-active

  Dear all,

  I configured the SRM connection between two sites. I have them paired with success and set up the connection to VR.

  Problem is when I put a replication for certain one VM, once the wizard is finished, vsphere replication monitor displays status - not Active. The events and tasks of the VM, I found the following warning:

  No connection to the server of VR: do not answer

  I am able to ping/telnet port 80 two of these machines of this virtual machine replication.

  Could you please help me solve this problem.

  Thank you

  Aleksandar Aleksandrov

  Hi again,

  OK, here's the problem.

  Basically when pair you it with DR site both VR servers are to exchange information between them for example VRS server target. So in this case you end up with the following situation:

  (1) VRS on the DR site has different IP address than the Production site

  (2) production site ESXi tries to connect to VRS IP at the Dr site not directly through your port transfer machine

  (3) what makes the replication to go to idle state

  Please check the messages in the vmkernel.log file located in your source ESXi machine. Here's a useful KB KB VMware: VMware vSphere troubleshooting replication problems that might be useful.

  Thank you

  Dzhem