on 05-08-2014 8:57 AM
Hi Experts,
We have a below error during materialize phase. I have already check this commands and it seems fine
select suid , srid from master..sysloginroles
select suid, srid from master..sysloginroles where srid = 0 or srid = 1
sp_configure 'allow updates',1
1> sap_status path
Path Name Value Info
--------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------
Start Time 2014-05-08 10:14:46.807 Time command started executing.
Elapsed Time 00:00:03 Command execution time.
sappr1 Hostname drsys01 Logical host name.
sappr1 HADR Status Primary : Active Identify the primary and standby sites.
sapdr2 Hostname drsys02 Logical host name.
sapdr2 HADR Status Standby : Inactive Identify the primary and standby sites.
sapdr2.sappr1.TSD State Suspended Path is suspended. Transactions are not being replicated.
sapdr2.sappr1.TSD Latency Unknown No latency information for database 'TSD'.
sapdr2.sappr1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
sapdr2.sappr1.master State Suspended Path is suspended. Transactions are not being replicated.
sapdr2.sappr1.master Latency Unknown No latency information for database 'master'.
sapdr2.sappr1.master Commit Time Unknown No last commit time for the database 'master'.
sappr1.sapdr2.TSD State Suspended Path is suspended. Transactions are not being replicated.
sappr1.sapdr2.TSD Failing Command Error Message Failing Command Error Message The connection in the Replication Server on the sapdr2 host to 'TSD_sapdr2.TSD' is not configured.
sappr1.sapdr2.TSD Latency Unknown No latency information for database 'TSD'.
sappr1.sapdr2.TSD Commit Time Unknown No last commit time for the database 'TSD'.
sappr1.sapdr2.master State Active Path is active and replication can occur.
sappr1.sapdr2.master Latency Unknown No latency information for database 'master'.
sappr1.sapdr2.master Commit Time 2014-05-07 15:53:22.692 Time last commit replicated
*********************
suid srid | suid srid |
----------- ----------- | ----------- ----------- |
1 0 | 1 0 |
1 1 | 1 1 |
1 2 | 1 2 |
1 3 | 1 3 |
1 10 | 1 10 |
1 32 | 1 32 |
3 11 | 3 11 |
3 14 | 3 14 |
4 34 | 4 34 |
4 3 | 4 3 |
5 1 | 5 1 |
6 33 | 6 33 |
1000 1 | 1000 1 |
1000 5 | 1000 5 |
1000 3 | 1000 3 |
1000 0 | 1000 0 |
1001 5 | 1001 5 |
1001 35 | 1001 35 |
1001 0 | 1001 0 |
(19 rows affected) | (19 rows affected) |
********
Regards
Mohammad
Hi Mohammed,
The error "The connection in the Replication Server on the sapdr2 host to 'TSD_sapdr2.TSD' is not configured." indicates a problem with the Rpelication Server connection named 'TSD_sapdr2.TSD'.
Either this connection does not exist, or it is in an error state.
Since you have succesfully setup replication, the more likley answer is an error state.
Please log into the Replication Server on sapdr2 and verify the DSI thread (the apply thread) for the connection named 'TSD_sapdr2.TSD' is up and operational.
If that thread is down, you can 'resume' it using the following Replication Server command:
>resume connection to TSD_sapdr2.TSD
>go
The recheck the state of the thread. If the state returns to a 'down' or error condition, you will need to review the Replication Server log to determine the detail of the error.
Regards,
Stephen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohammed,
The same user and password that you use to connect to the DR Agent can be used to connect to the Replication Server.
The default port number assigned to your Replication is typically 4 less than the DR Agent port.
So - if I use isql to log into my DR Agent on port 4909:
isql -UDR_admin -Pmypass -Ssapdr2:4909
I can likely log into the Replication Server on the same host at port 4905
isql -UDR_admin -Pmypass -Ssapdr2:4905
Once logged on, command 'admin version' will return the version string of the Replication Server.
1> admin version
2> go
Version
-------------------------------------------------------------------------------------------------------------------------------
Replication Server/15.7.1/EBF ..../Linux 2.6.18-128.el5 x86_64/1/OPT64/Fri May 2 08:56:36 2014
Comamnd 'admin who' lists the main threads in the Replication Server
1> admin who
2> go
Spid Name State Info
---- --------------- -------------------- ------------------------------------------------------------
21 DSI EXEC Awaiting Command 101(1) RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
15 DSI Awaiting Message 101 RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
14 SQM Awaiting Message 101:0 RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
DSI EXEC Suspended 102(1) UDBPrimary.SDM
DSI Suspended 102 UDBPrimary.SDM
192 DIST Awaiting Wakeup 102 UDBPrimary.SDM
193 SQT Awaiting Wakeup 102:1 DIST UDBPrimary.SDM
25 SQM Awaiting Message 102:1 UDBPrimary.SDM
24 SQM Awaiting Message 102:0 UDBPrimary.SDM
45 REP AGENT Awaiting Command UDBPrimary.SDM
In the example above, the "DSI" and "DSI EXEC" threads that are 'Awaiting...' are in a natural state.
The "DSI" and "DSI EXEC" threads that are 'Suspend' are not. In your env, I am expecting the DSI threads for 'TSD_sapdr2.TSD' may have a state of 'Down'.
If you issue command 'admin log_name', Replication Server will display the name of the log file for the Replication Server.
Regards,
Stephen
Hello Stephen,
It seems something went wrong with materialization. below is error log ...
I executed command resume connection to TSD_sapdr2.TSD
output of admin who
************
1> admin who
2> go
Spid Name State Info
---- ---------- -------------------- ------------------------------------------------------------
32 DSI EXEC Awaiting Command 102(1) TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
19 DSI Awaiting Message 102 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
23 DIST Awaiting Wakeup 102 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
30 SQT Awaiting Wakeup 102:1 DIST TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
13 SQM Awaiting Message 102:1 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
11 SQM Awaiting Message 102:0 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
35 REP AGENT Awaiting Command TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
36 NRM Awaiting Message TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
DSI EXEC Suspended 106(1) TSD_sapdr2.TSD
DSI Suspended 106 TSD_sapdr2.TSD
24 DIST Awaiting Wakeup 106 TSD_sapdr2.TSD
29 SQT Awaiting Wakeup 106:1 DIST TSD_sapdr2.TSD
17 SQM Awaiting Message 106:1 TSD_sapdr2.TSD
16 SQM Awaiting Message 106:0 TSD_sapdr2.TSD
REP AGENT Down TSD_sapdr2.TSD
NRM Down TSD_sapdr2.TSD
33 DSI EXEC Awaiting Command 104(1) TSD_sapdr2.master
20 DSI Awaiting Message 104 TSD_sapdr2.master
25 DIST Awaiting Wakeup 104 TSD_sapdr2.master
31 SQT Awaiting Wakeup 104:1 DIST TSD_sapdr2.master
15 SQM Awaiting Message 104:1 TSD_sapdr2.master
14 SQM Awaiting Message 104:0 TSD_sapdr2.master
REP AGENT Down TSD_sapdr2.master
NRM Down TSD_sapdr2.master
18 RSI Awaiting Wakeup TSD_REP_sappr1
12 SQM Awaiting Message 16777317:0 TSD_REP_sappr1
34 RSI USER Active TSD_REP_sappr1
21 dSUB Active
7 dCM Awaiting Message
9 dAIO Awaiting Message
26 dREC Sleeping dREC
10 dDELSEG Awaiting Message
37 USER Active DR_admin
6 dALARM Awaiting Wakeup
27 dSYSAM Sleeping
1>
***********
I. 2014/05/08 00:28:38. Logging messages in file 'E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2.log '.
I. 2014/05/08 00:28:38. Using interfaces file 'E:\sybase\TSD_REP\ini\sql.ini '.
I. 2014/05/08 00:28:38. Server name is 'TSD_REP_sapdr2'.
I. 2014/05/08 00:28:38. Replication Server memory model: 64bit.
I. 2014/05/08 00:28:39. Reading 'E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2.cfg ' for configuration information.
I. 2014/05/08 00:28:39. Using config file encrypted password for the RSSD primary user.
I. 2014/05/08 00:28:39. Using config file encrypted maintenance password for the RSSD maint user.
I. 2014/05/08 00:28:39. Using config file encrypted password for the ID user.
I. 2014/05/08 00:28:39. ERSSD start command: E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbspawn.exe -f -q E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbsrv12.exe -ti 0 -x "tcpip(PORT=4906;DOBROAD=NO;BLISTENER=NO)" -o E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD\TSD_REP_sapdr2_RSSD.out E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD\db\TSD_REP_sapdr2_RSSD.db
I. 2014/05/08 00:28:39. The Principal name of 'ID Server' 'TSD_REP_sappr1' is 'TSD_REP_sappr1'.
I. 2014/05/08 00:28:39. The Principal name of 'RSSD Server' 'TSD_REP_sapdr2_RSSD' is 'TSD_REP_sapdr2_RSSD'.
I. 2014/05/08 00:28:39. SySAM: Using licenses from: E:\sybase\TSD_REP\SYSAM-2_0\licenses\SYBASE.lic
I. 2014/05/08 00:28:39. SySAM: Checked out license for 4 REP_SERVER (2014.1231/permanent/1F3B 226B 2C3B 26C8).
I. 2014/05/08 00:28:39. This product is licensed to: SAP, for use with SAP Business Applications.
I. 2014/05/08 00:28:39. Checked out license REP_SERVER.
I. 2014/05/08 00:28:39. Using the 'utf8' character set.
I. 2014/05/08 00:28:39. Using the 'us_english' language.
I. 2014/05/08 00:28:39. Using the 'binary' sort order.
I. 2014/05/08 00:28:39. Using the 'binary' unicode sort order.
I. 2014/05/08 00:28:39. Using server 'TSD_REP_sappr1' for an ID Server.
I. 2014/05/08 00:28:39. Using config file password for the ID user.
I. 2014/05/08 00:28:39. Using user 'TSD_REP_sappr1_id' for the ID Server.
I. 2014/05/08 00:28:39. Using config file maintenance password for the RSSD maint user.
I. 2014/05/08 00:28:39. RSSD maintenace user is 'TSD_REP_sapdr2_RSSD_maint'.
I. 2014/05/08 00:28:39. Using config file password for the RSSD primary user.
I. 2014/05/08 00:28:39. RSSD primary user is 'TSD_REP_sapdr2_RSSD_prim'.
I. 2014/05/08 00:28:39. RSSD database is 'TSD_REP_sapdr2_RSSD'.
I. 2014/05/08 00:28:39. RSSD server is 'TSD_REP_sapdr2_RSSD'.
I. 2014/05/08 00:28:39. Reading 'TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD..rs_config' for system configuration parameters.
I. 2014/05/08 00:28:39. Environment variable 'PATH' is set to 'E:\sybase\TSD_REP\REP-15_5\ASA12\win32;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;E:\sybase\TSD\ASE-15_0\jobscheduler\bin;E:\sybase\TSD\ASE-15_0\bin;E:\sybase\TSD\ASE-15_0\dll;E:\sybase\TSD\DBISQL\bin;E:\sybase\TSD\OCS-15_0\bin;E:\sybase\TSD\OCS-15_0\dll;E:\sybase\TSD\OCS-15_0\lib3p64;E:\sybase\TSD\OCS-15_0\lib3p'.
I. 2014/05/08 00:28:39. Environment variable 'SALANG' is set to 'us_english'.
I. 2014/05/08 00:28:39. Environment variable 'SACHARSET' is set to 'utf8'.
I. 2014/05/08 00:28:39. Environment variable 'ASLANG' is set to 'us_english'.
I. 2014/05/08 00:28:39. Environment variable 'ASCHARSET' is set to 'utf8'.
I. 2014/05/08 00:28:39. Environment variable 'SQLLOCALE' is set to 'Charset=utf8;Language=us_english'.
I. 2014/05/08 00:28:39. Environment variable 'SALOGDIR' is set to 'E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD'.
I. 2014/05/08 00:28:39. Environment variable 'ASLOGDIR' is set to 'E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD'.
I. 2014/05/08 00:28:43. Command failed: E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbping.exe -q -c "eng=TSD_REP_sapdr2_RSSD;Language=us_english;CommLinks=tcpip(DOBROAD=NONE;HOST=localhost;PORT=4906)". Operating System returned: The system could not find the environment option that was entered.
I. 2014/05/08 00:28:43. Starting embedded RSSD: E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbspawn.exe -f -q E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbsrv12.exe -ti 0 -x "tcpip(PORT=4906;DOBROAD=NO;BLISTENER=NO)" -o E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD\TSD_REP_sapdr2_RSSD.out E:\sybase\TSD_REP\TSD_REP_sapdr2\TSD_REP_sapdr2_RSSD\db\TSD_REP_sapdr2_RSSD.db
I. 2014/05/08 00:28:46. Value of the 'memory_limit' config parameter is: 2047 megabytes.
I. 2014/05/08 00:28:46. Auditing is off. Destination: log
I. 2014/05/08 00:28:46. AUDIT: incoming command (issued by none): Repserver started
I. 2014/05/08 00:28:46. Maximum outbound connections allowed: 144.
I. 2014/05/08 00:28:46. System outbound connection fadeout time: '30'.
I. 2014/05/08 00:28:46. System table cache size: 1000 rows.
I. 2014/05/08 00:28:46. Maximum number of Open Server threads allowed: 150.
I. 2014/05/08 00:28:46. Maximum number of Open Server mutexes allowed: 1024.
I. 2014/05/08 00:28:46. Maximum number of incoming client connections allowed: 30.
I. 2014/05/08 00:28:46. Maximum number of Open Server message queues allowed: 300.
I. 2014/05/08 00:28:46. Maximum number of Open Server messages allowed: 91136.
I. 2014/05/08 00:28:46. Maximum number of stable queues allowed: 32.
I. 2014/05/08 00:28:46. Block size for stable queues: 256.
I. 2014/05/08 00:28:46. Using encrypted password for outgoing connections.
I. 2014/05/08 00:28:46. Use SSL service is set to 'off'.
I. 2014/05/08 00:28:46. Default for connection ha_failover is set to 'on',
I. 2014/05/08 00:28:46. Default directory service provider is: 'InterfacesDriver'.
I. 2014/05/08 00:28:46. Using the value for entry 'RS_random' in config file.
I. 2014/05/08 00:28:46. System configuration complete.
I. 2014/05/08 00:28:46. SMP capability is set to : 'on'
I. 2014/05/08 00:28:46. Server using Open Server version Sybase Server-Library/15.7/P-EBF21949-21948 SP111/X64/BUILD1570-034/OPT/Tue Oct 29 08:15:48 2013
I. 2014/05/08 00:28:46. Server using Open Client version Sybase Client-Library/15.7/P-EBF21948 SP111/X64/BUILD1570-034/OPT/Tue Oct 29 08:14:17 2013
I. 2014/05/08 00:28:46. Server using Express Connect Library version Sybase ExpressConnect-Library/15.7.1/EBF 21882 SP111 rs1571sp110/RCI 4.1/X64/Windows 2008 R2/1/OPT64/Tue Nov 05 16:40:56 2013
I. 2014/05/08 00:28:46. Server site id is '16777318'.
I. 2014/05/08 00:28:46. Embedded database id is '102'.
I. 2014/05/08 00:28:47. SySAM: Checked out license for 4 REP_HVAR_ASE (2014.1231/permanent/1F3B 226B 2C3B 26C8).
I. 2014/05/08 00:28:47. Checked out license REP_HVAR_ASE.
I. 2014/05/08 00:28:47. Checked out license REP_HVAR_ASE as OK.
I. 2014/05/08 00:28:47. The sqm_seg_prealloc option is deprecated.
I. 2014/05/08 00:28:47. Opening partition 'E:\sybase\TSD_REP\repdata_1\partition1.dat'.
W. 2014/05/08 00:28:49. WARNING #5059 GLOBAL RS(GLOBAL RS) - dsiqmext.c(380)
The DSI thread for 'TSD_sapdr2.TSD' is not started, because the connection to the database has been suspended or the connection has not been completed.
I. 2014/05/08 00:28:49. Loaded Connector [ase.ctlib] for connection to [TSD_sapdr2.master]. Version: [Sybase ExpressConnect CTLibConnector/15.7.1/EBF 21882 SP111 rs1571sp110/RCI 4.1/X64/Windows 2008 R2/1/OPT64/Tue Nov 05 16:40:56 2013].
I. 2014/05/08 00:28:49. Replication Server 'TSD_REP_sapdr2' is started.
I. 2014/05/08 00:28:49. SQM starting: 102:1 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
I. 2014/05/08 00:28:49. SQM starting: 106:1 TSD_sapdr2.TSD
I. 2014/05/08 00:28:49. DIST for 'TSD_sapdr2.master' is Starting
I. 2014/05/08 00:28:49. SQM starting: 102:0 TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD
I. 2014/05/08 00:28:49. SQM starting: 104:0 TSD_sapdr2.master
I. 2014/05/08 00:28:49. SQM starting: 104:1 TSD_sapdr2.master
I. 2014/05/08 00:28:49. RSI: Trying to connect to 'TSD_REP_sappr1'.
I. 2014/05/08 00:28:49. SQM starting: 16777317:0 TSD_REP_sappr1
I. 2014/05/08 00:28:49. The DSI thread for database 'TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD' is started.
I. 2014/05/08 00:28:49. DIST for 'TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD' is Starting
I. 2014/05/08 00:28:49. SQM starting: 106:0 TSD_sapdr2.TSD
I. 2014/05/08 00:28:49. The DSI thread for database 'TSD_sapdr2.master' is started.
I. 2014/05/08 00:28:49. DIST for 'TSD_sapdr2.TSD' is Starting
I. 2014/05/08 00:28:49. RSI: connection to 'TSD_REP_sappr1' is established and the route is active.
I. 2014/05/08 00:30:51. Executing command: move E:\sybase\TSD_REP\TSD_REP_sapdr2\\TSD_REP_sapdr2_RSSD_ra.cfg E:\sybase\TSD_REP\TSD_REP_sapdr2\\TSD_REP_sapdr2_RSSD_ra.bak
I. 2014/05/08 00:30:52. Starting embedded RSSD Replication Agent by dREC.
I. 2014/05/08 00:30:52. Executing command: "E:\sybase\TSD_REP\REP-15_5\ASA12\win32\dbltm.exe" -S TSD_REP_sapdr2_RSSD_ra -C E:\sybase\TSD_REP\TSD_REP_sapdr2\\TSD_REP_sapdr2_RSSD_ra.cfg -ot E:\sybase\TSD_REP\TSD_REP_sapdr2\\TSD_REP_sapdr2_RSSD_ra.out -I E:\sybase\TSD_REP\ini\sql.ini
I. 2014/05/08 00:30:52. Replication Agent for TSD_REP_sapdr2_RSSD.TSD_REP_sapdr2_RSSD connected in language mode.
I. 2014/05/08 03:10:02. Connection to server 'TSD_REP_sapdr2_RSSD' as user 'TSD_REP_sapdr2_RSSD_maint' has been faded out (closed).
I. 2014/05/09 03:00:03. ...... connected to server 'TSD_REP_sapdr2_RSSD' as user 'TSD_REP_sapdr2_RSSD_maint'.
I. 2014/05/09 03:10:03. Connection to server 'TSD_REP_sapdr2_RSSD' as user 'TSD_REP_sapdr2_RSSD_maint' has been faded out (closed).
I. 2014/05/10 03:00:03. ...... connected to server 'TSD_REP_sapdr2_RSSD' as user 'TSD_REP_sapdr2_RSSD_maint'.
I. 2014/05/10 03:10:03. Connection to server 'TSD_REP_sapdr2_RSSD' as user 'TSD_REP_sapdr2_RSSD_maint' has been faded out (closed).
I. 2014/05/11 00:00:20. The DSI thread for database 'TSD_sapdr2.TSD' is started.
I. 2014/05/11 00:00:22. A grouped transaction of 14 individual transactions has failed in database 'TSD_sapdr2.TSD'. It will be broken into smaller groups and retried.
E. 2014/05/11 00:00:22. ERROR #1028 DSI EXEC(106(1) TSD_sapdr2.TSD) - dsiqmint.c(4696)
Message from server: Message: 2601, State 6, Severity 14 -- 'Attempt to insert duplicate key row in object 'TBTCO' with unique index 'TBTCO~0'
'.
I. 2014/05/11 00:00:22. Message from server: Message: 3621, State 0, Severity 10 -- 'Command has been aborted.
'.
H. 2014/05/11 00:00:22. THREAD FATAL ERROR #5189 DSI EXEC(106(1) TSD_sapdr2.TSD) - \dsiutil.c(891)
The DSI thread for the 'TSD_sapdr2.TSD' database is being shut down. DSI received Replication Server error #5185 which is mapped to STOP_REPLICATION or RETRY_STOP_REPLICATION. See the Replication Server log for more information.
T. 2014/05/11 00:00:22. (39): Last command(s) to 'TSD_sapdr2.TSD':
T. 2014/05/11 00:00:22. (39): 'update SAPSR3."TBTCS" set "JOBGROUP"=? where "JOBNAME"=? and "JOBCOUNT"=? '
W. 2014/05/11 00:00:22. WARNING #5185 DSI EXEC(106(1) TSD_sapdr2.TSD) - \dsiexec.c(19025)
Row count mismatch for the command executed on 'TSD_sapdr2.TSD'. The command impacted 0 rows but it should impact 1 rows.
I. 2014/05/11 00:00:22. The error was caused by output command #2 of the failed transaction on table 'SAPSR3.TBTCS'.
I. 2014/05/11 00:00:22. The DSI thread for database 'TSD_sapdr2.TSD' is shutdown.
I. 2014/05/11 00:04:14. The DSI thread for database 'TSD_sapdr2.TSD' is started.
I. 2014/05/11 00:04:14. A grouped transaction of 14 individual transactions has failed in database 'TSD_sapdr2.TSD'. It will be broken into smaller groups and retried.
E. 2014/05/11 00:04:14. ERROR #1028 DSI EXEC(106(1) TSD_sapdr2.TSD) - dsiqmint.c(4696)
Message from server: Message: 2601, State 6, Severity 14 -- 'Attempt to insert duplicate key row in object 'TBTCO' with unique index 'TBTCO~0'
'.
I. 2014/05/11 00:04:14. Message from server: Message: 3621, State 0, Severity 10 -- 'Command has been aborted.
'.
H. 2014/05/11 00:04:15. THREAD FATAL ERROR #5189 DSI EXEC(106(1) TSD_sapdr2.TSD) - \dsiutil.c(891)
The DSI thread for the 'TSD_sapdr2.TSD' database is being shut down. DSI received Replication Server error #5185 which is mapped to STOP_REPLICATION or RETRY_STOP_REPLICATION. See the Replication Server log for more information.
T. 2014/05/11 00:04:15. (41): Last command(s) to 'TSD_sapdr2.TSD':
T. 2014/05/11 00:04:15. (41): 'update SAPSR3."TBTCS" set "JOBGROUP"=? where "JOBNAME"=? and "JOBCOUNT"=? '
W. 2014/05/11 00:04:15. WARNING #5185 DSI EXEC(106(1) TSD_sapdr2.TSD) - \dsiexec.c(19025)
Row count mismatch for the command executed on 'TSD_sapdr2.TSD'. The command impacted 0 rows but it should impact 1 rows.
I. 2014/05/11 00:04:15. The error was caused by output command #2 of the failed transaction on table 'SAPSR3.TBTCS'.
I. 2014/05/11 00:04:15. The DSI thread for database 'TSD_sapdr2.TSD' is shutdown.
************
Regards
Mohammad
It seems that you have a typical replication problem:
- 'Attempt to insert duplicate key row in object 'TBTCO' with unique index 'TBTCO~0'
You have to check how looks like transaction that makes that problem.
The simplest way is:
# using isql connected to RS
>sysadmin log_first_tran, TSD_sapdr2, TSD -- write first tran to exception log located in RSSD database
>go
>connect -- connect to RSSD
>go
>rs_helpexception -- list all trans in exception log and find the maximum ID of last tran (eg. 101)
>go
>rs_helpexception 101, v
>go
Then you will se which record is wrong.
So you can decide next or to skip transaction using:
>resume connection to TSD_sapdr2.TSD skip transaction
or you can correct data directly on target database and the resume replication with:
>resume connection to TSD_sapdr2.TSD
Hi Mohammed,
Tomasz explanation is correct. However, it only addresses the 'current' data error. We don't know how many additional errors exist after this point. If the primary and standby databases are not in-sync, these types of errors are likely to continue.
Somehow, the materialization of the TSD database was either not done, or was either not performed or failed some how. My recommendation is that it may be easier to re-try at this point.
Using the DR Agent, I would execute the following:
// Disable replication - removes replication from sapdr1 for the TSD database
sap_disable_replication sapdr1, TSD
go
// Enable replication - Prepares replication from sapdr1 for the TSD database (ready fort materialization)
sap_enable_replication sapdr1, TSD
go
// Check state - replication for TSD database should be 'Defined"
sap_status path
go
//Then perform materialization of the TSD database again.
sap_materialize auto, sapdr1, sapdr2, TSD
go
// Verify materialization completed without error (execute this command to check the status of materialization is complete or in error)
sap_status task
go
Regards,
Stephen
Hi Tomasz Hi Stephen,
Thanks for inputs, really appreacite and I am learning SYBASE REPLICATION.. Thanks again guys.
for the issues i have followed Tomasz recommdation but i ended up in again same error.
nothing seems to be working out. so as recommended by Stephen I have started again from scratch uninstalled replicaiton software on both systems.
set up replication on node 2 is done and on node 1 in process Materlize DB phase.
will keep you posted.
One more thing which I notice despite giving 30 mins delay in replication it is will show up error and then retry will proceed.
Regards
Mohammad
Hello Stephen,
I have restarted all again and end up in different error. attached log as well. I have setup this couple of time , at few occasions very smooth but sometime it makes you .....
1> sap_status path
Path Name Value Info
--------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------
Start Time 2014-05-14 10:51:26.526 Time command started executing.
Elapsed Time 00:00:03 Command execution time.
prsap1 Hostname drsys01.ksa.tog Logical host name.
prsap1 HADR Status Disabled : Unknown Identify the primary and standby sites.
drsap1 Hostname drsys02.ksa.tog Logical host name.
drsap1 HADR Status Disabled : Unknown Identify the primary and standby sites.
drsap1.prsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
drsap1.prsap1.TSD Latency Unknown No latency information for database 'TSD'.
drsap1.prsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
drsap1.prsap1.master State Suspended Path is suspended. Transactions are not being replicated.
drsap1.prsap1.master Latency Unknown No latency information for database 'master'.
drsap1.prsap1.master Commit Time Unknown No last commit time for the database 'master'.
prsap1.drsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
prsap1.drsap1.TSD Failing Command Error Message Failing Command Error Message The connection in the Replication Server on the drsap1 host to 'TSD_drsap1.TSD' is not configured.
prsap1.drsap1.TSD Latency Unknown No latency information for database 'TSD'.
prsap1.drsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
prsap1.drsap1.master State Active Path is active and replication can occur.
prsap1.drsap1.master Latency Unknown No latency information for database 'master'.
prsap1.drsap1.master Commit Time 2014-05-13 18:40:16.838 Time last commit replicated
Regards
Mohammad
Rs has problem whit DSI to target database TSD_drsap1.TSD
'Attempt to insert duplicate key row in object 'BTCJOBEPP' with unique index 'BTCJOBEPP~0'
You can solve this by:
- repair this one transaction that blocks replication
- by resynchronize table BTCJOBEPP
So it seems you have not synchronized objects between your source database and target database.
Maybe you have some database sessions that make some changes on target database but in case of replication they should not do this.
In case of replication of specyfic table/tables on target database, you should avoid any changes on that target table/tables from other users then repication server (DSI thread).
Hi Mohammed,
It looks like the materialization process should have just finished when this error ocurred. Can you tell us which materialization option from the SAP sinatller you chose? It appears it was not successful, but we don't have enough information from this log to know why.
Perhaps knowing your steps would help us narrow down the possible issues.
Regards,
Stephen
Hello Stephen,
below are detail steps which I followed
Installation of SAP NW 7.4 ABAP system on drsys01
Installation of DB node {Distributed system} as mentioned in installation guide on drsys02
Setup of replication environment on node 2 .. without replication configuration
Setup of replication environment on node 1 with replication configuration
materialzation method Manual dump/load database
Sapinst stop and request to load database on node 2 {drsys02}
steps : on node 1
sp_dboption TSD, 'trunc log on chkpt', 'false'
sp_dboption TSD, 'full logging for all', 'true'
sp_dboption TSD, 'enforce dump tran sequence', 'true'
backup of saptools and TSD database
dump database TSD using config = 'TSDDB1'
dump database saptools using config = 'TSDDB1'
dump transaction TSD using config = 'TSDLOG1'
load saptools and TSD on node 2
load database saptools from 'E:\Backup\DB\saptools.DB.20140515.123556.000'
go
online database saptools
load database TSD from 'E:\Backup\DB\TSD.DB.20140515.122421.000'
go
load transaction TSD from 'E:\Backup\DB\TSD.TRAN.20140515.140439.000'
go
online database TSD
then on Node 1 click ok to proceed with materialize database phase .
below is error and attached is log file of node2
Server 'TSD_REP_drsap1':
Application 'isql' is using character set 'iso_1', but the Replication Server is using character set 'utf8'. Because
character sets are different, character set conversion problems may occur.
1> admin version
2> admin who
3> go
Version
-----------------------------------------------------------------------------------------------------------
Replication Server/15.7.1/EBF 21882 SP111 rs1571sp110/X64/Windows 2008 R2/1/OPT64/Tue Nov 05 16:44:18 2013
Spid Name State Info
---- ---------- -------------------- ------------------------------------------------------------
33 DSI EXEC Awaiting Command 102(1) TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
19 DSI Awaiting Message 102 TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
24 DIST Awaiting Wakeup 102 TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
31 SQT Awaiting Wakeup 102:1 DIST TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
13 SQM Awaiting Message 102:1 TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
11 SQM Awaiting Message 102:0 TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
43 REP AGENT Awaiting Command TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
44 NRM Awaiting Message TSD_REP_drsap1_RSSD.TSD_REP_drsap1_RSSD
DSI EXEC Suspended 106(1) TSD_drsap1.TSD
DSI Suspended 106 TSD_drsap1.TSD
25 DIST Awaiting Wakeup 106 TSD_drsap1.TSD
30 SQT Awaiting Wakeup 106:1 DIST TSD_drsap1.TSD
17 SQM Awaiting Message 106:1 TSD_drsap1.TSD
16 SQM Awaiting Message 106:0 TSD_drsap1.TSD
REP AGENT Down TSD_drsap1.TSD
NRM Down TSD_drsap1.TSD
48 DSI EXEC Awaiting Command 104(1) TSD_drsap1.master
47 DSI Awaiting Message 104 TSD_drsap1.master
26 DIST Awaiting Wakeup 104 TSD_drsap1.master
32 SQT Awaiting Wakeup 104:1 DIST TSD_drsap1.master
15 SQM Awaiting Message 104:1 TSD_drsap1.master
14 SQM Awaiting Message 104:0 TSD_drsap1.master
REP AGENT Down TSD_drsap1.master
NRM Down TSD_drsap1.master
18 RSI Awaiting Wakeup TSD_REP_prsap1
12 SQM Awaiting Message 16777317:0 TSD_REP_prsap1
37 RSI USER Active TSD_REP_prsap1
22 dSUB Active
7 dCM Awaiting Message
9 dAIO Awaiting Message
27 dREC Sleeping dREC
10 dDELSEG Awaiting Message
80 USER Active DR_admin
6 dALARM Awaiting Wakeup
28 dSYSAM Sleeping
1> resume connection to TSD_drsap1.TSD
2> go
Connection to 'TSD_drsap1.TSD' is resumed.
1>
***********
1> sap_status path
Path Name Value Info
--------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------
Start Time 2014-05-15 14:52:13.193 Time command started executing.
Elapsed Time 00:00:02 Command execution time.
prsap1 Hostname drsys01 Logical host name.
prsap1 HADR Status Primary : Active Identify the primary and standby sites.
drsap1 Hostname drsys02 Logical host name.
drsap1 HADR Status Standby : Inactive Identify the primary and standby sites.
drsap1.prsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
drsap1.prsap1.TSD Latency Unknown No latency information for database 'TSD'.
drsap1.prsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
drsap1.prsap1.master State Suspended Path is suspended. Transactions are not being replicated.
drsap1.prsap1.master Latency Unknown No latency information for database 'master'.
drsap1.prsap1.master Commit Time Unknown No last commit time for the database 'master'.
prsap1.drsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
prsap1.drsap1.TSD Failing Command Error Message Failing Command Error Message The connection in the Replication Server on the drsap1 host to 'TSD_drsap1.TSD' is not configured.
prsap1.drsap1.TSD Latency Unknown No latency information for database 'TSD'.
prsap1.drsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
prsap1.drsap1.master State Active Path is active and replication can occur.
prsap1.drsap1.master Latency Unknown No latency information for database 'master'.
prsap1.drsap1.master Commit Time 2014-05-15 12:22:23.620 Time last commit replicated
Regards
Mohammad
Hi Mohammed,
Thank you for providing the details. I think the issue is a timing related issue.
When a 'dump' is executed in ASE, a 'marker' is recorded in the transaction loog indicating the point where the dump is complete. Replication Server is sent this 'marker' and will use the marker to determine when to apply data. Activity prior to the marker is assumed to be in the dump, and is not applied by Replication Server. Everything after the 'marker' is assumed to NOT exist in the dump and will be applied.
The timing challenge - the marker is created for both dump 'database' and 'transaction'. And Replication Server will process the 'first' marker is sees. So I think the issue is Replication is starting after the 'database' dump, and not waiting for the 'transaction' dump.
To change the timing, you need to perform you database dump 'before' you request manual materialization.
1) Dump database
2) Wait to ensure this dump's marker has been skipped by Replication Server - a few minutes should be OK.
3) Select manual dump/load database (will process 'next' dump marker seen).
4) Dump tran
5) Load both database and tran
6) OK to proceed.
Regards,
Stephen
Hello Stephen,
tried as you mentioned again ended up in same error.
this installation was from the scratch
errors..
> sap_delay_replication drsap2, on
TaskName Type Value
------------------ ------------------------------ -----------------------------------------------------------------------
Delay Replication Start Time 2014-05-19 02:35:42.639
Delay Replication Elapsed Time 00:00:00
DelayReplication Task Name Delay Replication
DelayReplication Task State Error
DelayReplication Short Description Toggle delayed replication to the ERP database.
DelayReplication Failing Command Error Message When turning delayed replication on, the delay minutes cannot be zero.
DelayReplication Corrective Action Use sap_set to set the minutes for delayed replication.
DelayReplication Hostname drsys01.ksa.tog
TaskName Type Value
-------------------- ------------------------------ --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Materialize Start Time 2014-05-19 12:05:02.203
Materialize Elapsed Time 00:00:01
Materialize Task Name Materialize
Materialize Task State Error
Materialize Short Description Materialize database
Materialize Failing Command Error Message prsap1 - DR Agent - Disaster recovery environment is ready for setup replication
Diagnose Environment - Start Time - 2014-05-19 12:05:02.929
Diagnose Environment - Elapsed Time - 00:00:00
DiagnoseEnvironment - Task Name - Diagnose Environment
DiagnoseEnvironment - Task State - Error
DiagnoseEnvironment - Short Description - Diagnose the environment for disaster recovery setup readiness.
DiagnoseEnvironment - Hostname - drsys02
ValidateLocalDREnv - Task Name - Validate Local Disaster Recovery Environment
ValidateLocalDREnv - Task State - Error
ValidateLocalDREnv - Short Description - Verify that the local environment is setup and ready for disaster recovery replication setup to run.
ValidateLocalDREnv - Failing Command Error Message - drsap2 - Adaptive Server Enterprise - User 'TSD_maint' is not aliased to dbo for database 'TSD'
ValidateLocalDREnv - Hostname - drsys02
Materialize Hostname drsys01.ksa.tog
DiagnoseEnvironment Task Name Diagnose Environment
DiagnoseEnvironment Task State Error
DiagnoseEnvironment Short Description Diagnose the environment for disaster recovery setup readiness.
DiagnoseEnvironment Hostname drsys01.ksa.tog
(11 rows affected)
*************
1> sap_status path
Path Name Value Info
--------------------- ------------- ------------------------ ----------------------------------------------------------
Start Time 2014-05-19 13:13:46.334 Time command started executing.
Elapsed Time 00:00:02 Command execution time.
prsap1 Hostname drsys01.ksa.tog Logical host name.
prsap1 HADR Status Disabled : Inactive Identify the primary and standby sites.
drsap2 Hostname drsys02.ksa.tog Logical host name.
drsap2 HADR Status Disabled : Unknown Identify the primary and standby sites.
drsap2.prsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
drsap2.prsap1.TSD Latency Unknown No latency information for database 'TSD'.
drsap2.prsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
drsap2.prsap1.master State Suspended Path is suspended. Transactions are not being replicated.
drsap2.prsap1.master Latency Unknown No latency information for database 'master'.
drsap2.prsap1.master Commit Time Unknown No last commit time for the database 'master'.
prsap1.drsap2.TSD State Defined Path is defined and ready for materialization.
prsap1.drsap2.TSD Latency Unknown No latency information for database 'TSD'.
prsap1.drsap2.TSD Commit Time Unknown No last commit time for the database 'TSD'.
prsap1.drsap2.master State Active Path is active and replication can occur.
prsap1.drsap2.master Latency Unknown No latency information for database 'master'.
prsap1.drsap2.master Commit Time 2014-05-19 09:24:07.892 Time last commit replicated
(18 rows affected)
what could be possible error and where i went wrong
please advise
Regards
Mohammad
**************
Hi Mohammad,
Regarding sap_delay_replication. The error message is:
"Failing Command Error Message When turning delayed replication on, the delay minutes cannot be zero."
The reason the command failed is that the current delay time is zero. Meaning there would be no delay if this feature is turned on since the delay time is not greater than 0. To provide the number of minutes of delay you wish to maintain, execute:
sap_set drsap2, delay, <minutes>
You can see the current delay setting by just executing:
sap_set
Once you have a 'delay' configuration value greater than zero, the command should succeed.
Regarding the materialization error:
ValidateLocalDREnv - Failing Command Error Message - drsap2 - Adaptive Server Enterprise - User 'TSD_maint' is not aliased to dbo for database 'TSD'
It seems odd, but somehow the maintenance user was not granted (or has lost) 'dbo' alias permission for the TSD database.
You can manually grant this permission in the ASE database as follows:
use TSD
go
sp_addalias TSD_maint, dbo
go
Is it possible the master database has not been materialized yet? The master database (since it contains all of the users, roles and permissions) should be materialized before the SAP_SID database, so that the needed roles and permissions already exists at the standby.
Regards,
Stephen
Hello Stephen,
Few points
a) I have given delay time during installation of primary node 1but stil it ended up in error.
b) though sapinst materlize master database , shall i do again load it manually ?
regrading below dbo issue, if I do manuall assignment it says it already exist
use TSD
go
sp_addalias TSD_maint, dbo
go
please suggest
Regards
Mohammad
Hi Mohammad,
Please note that each node can have a unique delay setting. You indicated a delay time was provided for the 'primary' node. But is logical host 'sapdr2' identified in the sap_delay_replication command the primary or standby?
No - would not re-execute materialization of the master if it has already been performed. Obviously, if you know it failed we should redo it. But if there was no failure.....I would first try to simply add the missing permission.
Please verify which node sp_addalias is executed against. If drsap2 is the standby, you may need to verify you are really connected to that node, and not redirected to the 'primary' server.
When I need to execute a command specifically at the standby and not the primary, I often start by exeuctin ASE command "select asehostname()" to verify I am connected to the desired host.
Regards,
Stephen
Hi Stephen,
Again I have restrted from scratched and now in "setup replication environment phase " i got below error , a retry will take me forward but doubt is this is causing materialize phase issue ?
During replication setup i have given replication delay as 10 mins where in sap_set it is shows as '0'.
1> sap_delay_replication drsap1, on
TaskName Type Value
------------------ ------------------------------ -----------------------------------------------------------------------
Delay Replication Start Time 2014-05-19 19:54:47.663
Delay Replication Elapsed Time 00:00:00
DelayReplication Task Name Delay Replication
DelayReplication Task State Error
DelayReplication Short Description Toggle delayed replication to the ERP database.
DelayReplication Failing Command Error Message When turning delayed replication on, the delay minutes cannot be zero.
DelayReplication Corrective Action Use sap_set to set the minutes for delayed replication.
DelayReplication Hostname drsys01.ksa.tog
1> sap_set
2> go
Property Value
------------------------------- ----------------------------
sap_sid TSD
maintenance_user TSD_maint
participating_databases [master, TSD]
prsap1, sybase_dir E:\sybase\TSD_REP
prsap1, ase_port 4901
prsap1, ase_user DR_admin
prsap1, ase_backup_server_port 4902
prsap1, ase_hostname drsys01.ksa.tog
prsap1, db_dump_dir E:\sybase\TSD_REP
prsap1, delay 0
prsap1, ase_instance TSD_prsap1
prsap1, replication_port 4905
prsap1, rssd_port 4906
prsap1, rssd_ra_port 4907
prsap1, replication_user DR_admin
prsap1, device_buffer_dir E:\sybase\TSD_REP\repdata_1
prsap1, rs_hostname drsys01.ksa.tog
prsap1, device_buffer_size 56320
prsap1, rs_instance TSD_REP_prsap1
prsap1, internal_name prsap1
prsap1, dr_plugin_port 4909
drsap1, sybase_dir E:\sybase\TSD_REP
drsap1, ase_port 4901
drsap1, ase_user DR_admin
drsap1, ase_backup_server_port 4902
drsap1, ase_hostname drsys02.ksa.tog
drsap1, db_dump_dir E:\sybase\TSD_REP
drsap1, delay 0
drsap1, ase_instance TSD_drsap1
drsap1, replication_port 4905
drsap1, rssd_port 4906
drsap1, rssd_ra_port 4907
drsap1, replication_user DR_admin
drsap1, device_buffer_dir E:\sybase\TSD_REP\repdata_1
drsap1, rs_hostname drsys02.ksa.tog
drsap1, device_buffer_size 56320
drsap1, rs_instance TSD_REP_drsap1
drsap1, internal_name drsap1
drsap1, dr_plugin_port 4909
(39 rows affected)
1> sap_set prsap1, delay 10
2> go
TaskName Type Value
----------------- ------------------------------ ----------------------------------------------------------------------
----------------------------
Set Property Start Time 2014-05-20 00:30:12.163
Set Property Elapsed Time 00:00:00
SetModelProperty Task Name Set Property
SetModelProperty Task State Error
SetModelProperty Short Description Set a configuration property.
SetModelProperty Failing Command Error Message The property delay cannot be changed because a replication system is a
ctive.
SetModelProperty Corrective Action Use the command 'sap_teardown' to remove the replication system and re
-issue the sap_set command.
SetModelProperty Hostname drsys01.ksa.tog
PLease advise
Regards,
Mohammad
Hi Mohammad,
Both issues look like bugs to me. The value given to the SAP installer should have been used, and you should be able to manually change the setting.
The message:
"The property ? cannot be changed because a replication system is active." is valid for some properties - but I think for 'delay' you should be able to change this value even if the system has already been created.
And I agree - these errors should not impact materialization.
My recommendation would be to continue setup and materialization without adding the delay. Once the system is established and operating properly, as a work-around you could manually add the desired delay value in the Replication Server.
The manual Replication Server commands would be:
// Suspendactivity on the standby connection to the TSD database
suspend connection to TSD_drsap2.TSD
go
// Set the delay time to 10 minutes
alter connection to TSD_drsap2.TSD set dsi_timer to '00:10'
go
// Resume replicationon the standby connection to the TSD database
resume connection to TSD_drsap2.TSD
go
Regards,
Stephen
Hi Stephen,
still iam facing same issue during materlie phase... no idea where it is going wrong..
**********
1> admin who
2> go
Spid Name State Info
---- ---------- -------------------- ------------------------------------------------------------
33 DSI EXEC Awaiting Command 102(1) TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
19 DSI Awaiting Message 102 TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
24 DIST Awaiting Wakeup 102 TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
31 SQT Awaiting Wakeup 102:1 DIST TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
13 SQM Awaiting Message 102:1 TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
11 SQM Awaiting Message 102:0 TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
43 REP AGENT Awaiting Command TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
44 NRM Awaiting Message TSD_REP_drsap2_RSSD.TSD_REP_drsap2_RSSD
48 DSI EXEC Awaiting Command 104(1) TSD_drsap2.master
47 DSI Awaiting Message 104 TSD_drsap2.master
25 DIST Awaiting Wakeup 104 TSD_drsap2.master
30 SQT Awaiting Wakeup 104:1 DIST TSD_drsap2.master
15 SQM Awaiting Message 104:1 TSD_drsap2.master
14 SQM Awaiting Message 104:0 TSD_drsap2.master
REP AGEN Down TSD_drsap2.master
NRM Down TSD_drsap2.master
DSI EXEC Suspended 106(1) TSD_drsap2.TSD
DSI Suspended 106 TSD_drsap2.TSD
26 DIST Awaiting Wakeup 106 TSD_drsap2.TSD
32 SQT Awaiting Wakeup 106:1 DIST TSD_drsap2.TSD
17 SQM Awaiting Message 106:1 TSD_drsap2.TSD
16 SQM Awaiting Message 106:0 TSD_drsap2.TSD
REP AGEN Down TSD_drsap2.TSD
NRM Down TSD_drsap2.TSD
18 RSI Awaiting Wakeup TSD_REP_prsap1
12 SQM Awaiting Message 16777317:0 TSD_REP_prsap1
37 RSI USER Active TSD_REP_prsap1
22 dSUB Active
7 dCM Awaiting Message
9 dAIO Awaiting Message
27 dREC Sleeping dREC
10 dDELSEG Awaiting Message
219 USER Active DR_admin
6 dALARM Awaiting Wakeup
28 dSYSAM Sleeping
1>
************
I have even raised OSS let see there response as well
Regards
Mohammad
Hi Mohammad,
For some reason, materialization has not completed.
In the Rep Server log for the standby, we can see the subscription was created:
I. 2014/05/21 13:29:16. REPLICATE Replication Server: Defining subscription <TSD_prsap1_TSD_sub> for database replication definition <TSD_prsap1_TSD_repdef> with primary at <TSD_prsap1.TSD> with replicate at <TSD_drsap2.TSD>
And when the dump marker is seen by the 'outbound' queue, the DSI thread is suspended.
I. 2014/05/21 13:43:16. The DSI thread for database 'TSD_drsap2.TSD' is shutdown
This is all expected. The shutdown of the DSI allows replication to stop until the dump has been loaded to the standby. Once the dump has been loaded, the DSI would be resumed to start applying the activity from the primary that occurred after the dump was taken (after the dump marker).
If you chose 'automatic' materialization of the database, this should all occur automatically.
If you chose to manually perform the dump and load, the process may be waiting for you to indicate the load is complete and the database has been brought on-line.
If you have access to the DR Agent, I suggest you issue command 'sap_status task' and see the status of the last asynchronous task that was executed (should be the materialization task in your case).
If the status shows an error, we need to resolve the error. If the status shows the task is still running, we may need to inspect other logs to see why it is still running.
Regards,
Stephen
Hello Stephen,
below is output node 1 prsap1
1> sap_status task
2> go
TaskName Type Value
-------------------- ------------------------------ ------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------
Materialize Start Time 2014-05-22 02:17:54.561
Materialize Elapsed Time 00:00:01
Materialize Task Name Materialize
Materialize Task State Error
Materialize Short Description Materialize database
Materialize Failing Command Error Message prsap1 - DR Agent - Disaster recovery environment is ready for setup replication
Diagnose Environment - Start Time - 2014-05-22 02:17:55.197
Diagnose Environment - Elapsed Time - 00:00:00
DiagnoseEnvironment - Task Name - Diagnose Environment
DiagnoseEnvironment - Task State - Error
DiagnoseEnvironment - Short Description - Diagnose the environment for disaster recovery setup readiness.
DiagnoseEnvironment - Hostname - drsys02
ValidateLocalDREnv - Task Name - Validate Local Disaster Recovery Environment
ValidateLocalDREnv - Task State - Error
ValidateLocalDREnv - Short Description - Verify that the local environment is setup and ready for disaster recovery replication setup to run.
ValidateLocalDREnv - Failing Command Error Message - drsap2 - Adaptive Server Enterprise - User 'TSD_maint' is not aliased to dbo for database 'TSD'
ValidateLocalDREnv - Hostname - drsys02
Materialize Hostname drsys01.ksa.tog
DiagnoseEnvironment Task Name Diagnose Environment
DiagnoseEnvironment Task State Error
DiagnoseEnvironment Short Description Diagnose the environment for disaster recovery setup readiness.
DiagnoseEnvironment Hostname drsys01.ksa.tog
(11 rows affected)
1>
below is output node 2 -drsap2
1> sap_status task
2> go
Type Class Value
------------------- -------------------- ----------------------------------------------------
Configure local RS Start Time 2014-05-21 01:35:13.380
Task Name ConfigureLocalRSAPI Configure local RS
Task State ConfigureLocalRSAPI Completed
Short Description ConfigureLocalRSAPI Configure local of Replication Server.
Long Description ConfigureLocalRSAPI Configuring a local instance of Replication Server.
Hostname ConfigureLocalRSAPI drsys02
(6 rows affected)
1>
on node 2 tsd_maint
PS C:\Users\sybtsd> isql -Usa -STSD -w1000 -Dmaster -X
Password:
1> use master
2> go
1> use TSD
2> go
1> sp_addalias TSD_maint, dbo
2>
3> go
Msg 17234, Level 16, State 1:
Server 'TSD', Procedure 'sp_addalias', Line 243:
The specified user name is already aliased.
(return status = 1)
1>
regards
Mohammad
Hi Mohammad,
I would encourage you to use command "select asehostname()" to verify the host you are connected to and to verify the needed alias has been granted on both nodes.
The code executed by the DR Agent to verify the alias has been granted is:
sp_helpuser 'dbo'
And verify the TSD_maint user is shown in the Login_name alias list.
I would again encourage you to peform this validation on both nodes.
Regards,
Stephen
Hi Stephen/Dale
output of commands
Node 1 Primary
****************
1> use master
2>
3> go
1> select asehostname()
2> o
3> go
o
-------------------------------
drsys01
(1 row affected)
1> sp_helpuser 'dbo'
2> go
Users_name ID_in_db Group_name Login_name
---------------------------------------- -------------------------------- ---------------------------------------- ----------------------------------------
dbo 1 public sa
(1 row affected)
Users aliased to user.
Login_name
----------------------------------------
TSD_maint
(return status = 0)
1>
************
1> select asehostname()
2> go
-------------------------------
drsys02
(1 row affected)
1> sp_helpuser 'dbo'
2> go
Users_name ID_in_db Group_name Login_name
---------------------------------------- -------------------------------- ---------------------------------------- ----------------------------------------
dbo 1 public sa
(1 row affected)
Users aliased to user.
Login_name
----------------------------------------
TSD_maint
(return status = 0)
1>
***********
still to ensure I run below sql statements on drsys02 as suggested by Dale.
sp_dropalias TSD_maint, dbo
sp_addalias TSD_maint, dbo
but still same error
> sap_status path
Path Name Value Info
--------------------- ------------------------------ ------------------------------ ---------------------------------------------------------------------------------------------------
Start Time 2014-05-23 00:40:00.954 Time command started executing.
Elapsed Time 00:00:02 Command execution time.
prsap1 Hostname drsys01.ksa.tog Logical host name.
prsap1 HADR Status Disabled : Inactive Identify the primary and standby sites.
drsap2 Hostname drsys02.ksa.tog Logical host name.
drsap2 HADR Status Disabled : Inactive Identify the primary and standby sites.
drsap2.prsap1.TSD State Suspended Path is suspended. Transactions are not being replicated.
drsap2.prsap1.TSD Latency Unknown No latency information for database 'TSD'.
drsap2.prsap1.TSD Commit Time Unknown No last commit time for the database 'TSD'.
drsap2.prsap1.master State Suspended Path is suspended. Transactions are not being replicated.
drsap2.prsap1.master Latency Unknown No latency information for database 'master'.
drsap2.prsap1.master Commit Time Unknown No last commit time for the database 'master'.
prsap1.drsap2.TSD State Suspended Path is suspended. Transactions are not being replicated.
prsap1.drsap2.TSD Failing Command Error Message Failing Command Error Message The connection in the Replication Server on the drsap2 host to 'TSD_drsap2.TSD' is not configured.
prsap1.drsap2.TSD Latency Unknown No latency information for database 'TSD'.
prsap1.drsap2.TSD Commit Time Unknown No last commit time for the database 'TSD'.
prsap1.drsap2.master State Active Path is active and replication can occur.
prsap1.drsap2.master Latency Unknown No latency information for database 'master'.
prsap1.drsap2.master Commit Time 2014-05-21 13:28:33.972 Time last commit replicated
(19 rows affected)
Refer to trace file sapinst_dev.log for further information.
Regards
Mohammad
Hi Mohammad,
Thank you for sharing the result of the queries - they clearly show TSD_maint has the required alias.
If the same error is occurring "... User 'TSD_maint' is not aliased to dbo for database 'TSD'..." then I can only think of a couple other possibilities.
1) It's a bug in the DR Agent
2) The DR_admin user does not get the same result as you for command "sp_helpuser 'dbo'"
3) The DR Agent is connecting to a different server.
If you have capacity to share a copy if the DR Agent log file that contains the error, I can take a look and see if I find anything else useful.
Regards,
Stephen
Hi Stephen,
really tough time and no end for this Issues , I had SAP experts look into it but still we are working
it is said is known error CR# 765455 SYNC_REP: DR Agent duplicate error when adding AGENT on setHost command
however I have started from scratch and agin ended up in same issues
tried uploading file some limitaitons on size and type , any other way out to send you files
Regards
Mohammad
Hi Mohammad,
I don't want to circumvent the efforts of our support team. But if you would share with me the incident # assigned by support, maybe I can help.
For CR# 765455 - this issue occurred in an environment when the Windows machines have a "Primary Dns Suffix" that is not reachable between machines, but the machines instead communicate via a "Connection-specific DNS Suffix" assigned to the ethernet adapter (and the domain names are not the same).
Is this the case in your env? (You can check the results of 'ipconfig /all' executed from a windows cmd window).
If this domain name mismatch does match your env, there are a couple of possible corrections.
You can change the "Primary Dns Suffix" (so that the same domain name as the ethernet adapter is used), or you can override the domain name lookup by adding an entry to your C:\Windows\System32\drivers\etc\hosts file, mapping the machines IP address to the ethernet domain name.
In either solution, the DR Agent instance and possible the SAP installer needs to be restarted to pick up the change. And the change is required on both hosts.
Regards,
Stephen
Hello Stephen,
I have maintained basic entries at all level hosts , manul entries in DNS in case of resolutin problem ...etc
I too agree not to interfere in SAP experts but as you know it is pending since long almost 45 days.
appreacite your inputs as always.
incident number 477665/2014
Regards
MOhammad
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.