on 06-30-2015 1:44 AM
There was a problem in replication in which the db in both sides are not synchronized,,, so I need to re-synch the DB. I stop the rep agent and truncate the secondary point. Drop the connections, an error encountered something like this "Database is the primary replication cannot drop the connection in it". So I install the replication server from the rs_init and I re-configure the Replication server.
I have already created a bi-directional replication , choose the dump marker option and it displays complete on my screen, however, when i check up the REP Server error log i found out that it doesn't work. I have already tested all the connections individually but still the error exists, can any one help me about this? how to continue,, I need help please
error log is:
I. 2015/06/29 08:59:11. SQM starting: 102:0 PSMBFI.psmbfi
I. 2015/06/29 08:59:11. The DSI thread for database 'PSMBFI.psmbfi' is started.
I. 2015/06/29 08:59:11. DIST for 'PSMBFI.psmbfi' is Starting
E. 2015/06/29 08:59:11. ERROR #1028 DSI(102 PSMBFI.psmbfi) - seful\cm.c(3546)
Message from server: Message: 4002, State 1, Severity 14 -- 'Login failed.
'.
E. 2015/06/29 08:59:11. ERROR #1027 DSI(102 PSMBFI.psmbfi) - seful\cm.c(3546)
Open Client Client-Library error: Error: 67175468, Severity 4 -- 'ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.'.
E. 2015/06/29 08:59:11. ERROR #13045 DSI(102 PSMBFI.psmbfi) - seful\cm.c(3550)
Failed to connect to server 'PSMBFI' as user 'psmbfi_maint'. See CT-Lib and/or server error messages for more information.
I. 2015/06/29 08:59:11. The DSI thread for database 'PSMBFI.psmbfi' is shutdown.
E. 2015/06/29 08:59:11. ERROR #1028 DSI(103 STANDBY_SVR.psmbfi) - seful\cm.c(3546)
Message from server: Message: 4002, State 1, Severity 14 -- 'Login failed.
'.
E. 2015/06/29 08:59:11. ERROR #1027 DSI(103 STANDBY_SVR.psmbfi) - seful\cm.c(3546)
Open Client Client-Library error: Error: 67175468, Severity 4 -- 'ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.'.
E. 2015/06/29 08:59:11. ERROR #13045 DSI(103 STANDBY_SVR.psmbfi) - seful\cm.c(3550)
Failed to connect to server 'STANDBY_SVR' as user 'psmbfi_maint'. See CT-Lib and/or server error messages for more information.
I. 2015/06/29 08:59:11. The DSI thread for database 'STANDBY_SVR.psmbfi' is shutdown.
I. 2015/06/29 09:03:11. REPLICATE Replication Server: Defining subscription <psmbfi_1> for database replication definition <psmbfi_1> with primary at <PSMBFI.psmbfi> with replicate at <STANDBY_SVR.psmbfi>
I. 2015/06/29 09:03:11. PRIMARY Replication Server: Defining subscription <psmbfi_1> for database replication definition <psmbfi_1> with primary at <PSMBFI.psmbfi> with replicate at <STANDBY_SVR.psmbfi>
E. 2015/06/29 09:03:11. ERROR #1028 USER(sa) - seful\cm.c(3546)
Message from server: Message: 4002, State 1, Severity 14 -- 'Login failed.
'.
E. 2015/06/29 09:03:11. ERROR #1027 USER(sa) - seful\cm.c(3546)
Open Client Client-Library error: Error: 67175468, Severity 4 -- 'ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.'.
E. 2015/06/29 09:03:11. ERROR #13045 USER(sa) - seful\cm.c(3550)
Failed to connect to server 'PSMBFI' as user 'sa'. See CT-Lib and/or server error messages for more information.
I. 2015/06/29 09:03:11. REPLICATE Replication Server: Defining subscription <psmbfi_1> for database replication definition <psmbfi_1> with primary at <STANDBY_SVR.psmbfi> with replicate at <PSMBFI.psmbfi>
I. 2015/06/29 09:03:11. PRIMARY Replication Server: Defining subscription <psmbfi_1> for database replication definition <psmbfi_1> with primary at <STANDBY_SVR.psmbfi> with replicate at <PSMBFI.psmbfi>
E. 2015/06/29 09:03:12. ERROR #1028 USER(sa) - seful\cm.c(3546)
Message from server: Message: 4002, State 1, Severity 14 -- 'Login failed.
'.
E. 2015/06/29 09:03:12. ERROR #1027 USER(sa) - seful\cm.c(3546)
Open Client Client-Library error: Error: 67175468, Severity 4 -- 'ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.'.
E. 2015/06/29 09:03:12. ERROR #13045 USER(sa) - seful\cm.c(3550)
Failed to connect to server 'STANDBY_SVR' as user 'sa'. See CT-Lib and/or server error messages for more information.
i got this error messages in originating sever/db when issued the cmd:
sp_start_rep_agent psmbfi
05:00000:00036:2015/07/01 16:03:28.75 server Started Rep Agent on database, 'psmbfi' (dbid = 4).
05:00000:00036:2015/07/01 16:03:29.67 server RepAgent(4): Received the following communications error message: Msg 05030504: ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed.
05:00000:00036:2015/07/01 16:03:29.67 server RepAgent(4): The Rep Agent Thread will retry the connection to the Replication Server every 60 second(s). (RepSvr = PSMBFI_REP).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have done all of that logins, I have synchronized their passwords and try to access using the ISQL Command in the different servers/db and it works,, it can access the db, but when I create the replication environment, the error still there ,,,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have also get this eror log in RSSD Server:
00:00000:00001:2015/06/29 08:52:23.99 server Completed cleaning up the default data cache for database 'model'.
00:00000:00001:2015/06/29 08:52:23.99 server Checking external objects.
00:00000:00001:2015/06/29 08:52:24.05 server The transaction log in the database 'model' will use I/O size of 8 Kb.
00:00000:00001:2015/06/29 08:52:24.05 server Database 'model' is now online.
00:00000:00001:2015/06/29 08:52:24.05 server The logical pagesize of the server is 4 Kb.
00:00000:00001:2015/06/29 08:52:24.05 server 0 dump conditions detected at boot time
00:00000:00001:2015/06/29 08:52:24.08 server Error: 926, Severity: 14, State: 1
00:00000:00001:2015/06/29 08:52:24.08 server Database 'sybsystemdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.
00:00000:00001:2015/06/29 08:52:24.13 server Warning: Node id initialization failed.
00:00000:00001:2015/06/29 08:52:24.13 server Clearing temp db
00:00000:00001:2015/06/29 08:52:24.20 server Processed 411 allocation unit(s) out of 4102 units (allocation page 104960). 10% completed.
00:00000:00001:2015/06/29 08:52:24.22 server Processed 821 allocation unit(s) out of 4102 units (allocation page 209920). 20% completed.
00:00000:00001:2015/06/29 08:52:24.24 server Processed 1231 allocation unit(s) out of 4102 units (allocation page 314880). 30% completed.
00:00000:00001:2015/06/29 08:52:24.25 server Processed 1641 allocation unit(s) out of 4102 units (allocation page 419840). 40% completed.
00:00000:00001:2015/06/29 08:52:24.27 server Processed 2051 allocation unit(s) out of 4102 units (allocation page 524800). 50% completed.
00:00000:00001:2015/06/29 08:52:24.28 server Processed 2462 allocation unit(s) out of 4102 units (allocation page 630016). 60% completed.
00:00000:00001:2015/06/29 08:52:24.30 server Processed 2872 allocation unit(s) out of 4102 units (allocation page 734976). 70% completed.
00:00000:00001:2015/06/29 08:52:24.31 server Processed 3282 allocation unit(s) out of 4102 units (allocation page 839936). 80% completed.
00:00000:00001:2015/06/29 08:52:24.33 server Processed 3692 allocation unit(s) out of 4102 units (allocation page 944896). 90% completed.
00:00000:00001:2015/06/29 08:52:24.34 server Processed 4102 allocation unit(s) out of 4102 units (allocation page 1049856). 100% completed.
00:00000:00001:2015/06/29 08:52:24.56 server The transaction log in the database 'tempdb' will use I/O size of 8 Kb.
00:00000:00001:2015/06/29 08:52:24.56 server Database 'tempdb' is now online.
00:00000:00001:2015/06/29 08:52:24.58 server Error: 926, Severity: 14, State: 1
00:00000:00001:2015/06/29 08:52:24.58 server Database 'sybsystemdb' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.
00:00000:00001:2015/06/29 08:52:24.66 server Recovering database 'sybsystemprocs'.
00:00000:00001:2015/06/29 08:52:24.66 server Started estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2015/06/29 08:52:24.70 server Database 'sybsystemprocs', checkpoint=(41308, 17), first=(41308, 17), last=(41308, 17).
00:00000:00001:2015/06/29 08:52:24.70 server Completed estimating recovery log boundaries for database 'sybsystemprocs'.
00:00000:00001:2015/06/29 08:52:24.70 server Started ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2015/06/29 08:52:24.70 server Completed ANALYSIS pass for database 'sybsystemprocs'.
00:00000:00001:2015/06/29 08:52:24.70 server Log contains all committed transactions until 2014/11/22 13:31:59.07 for database sybsystemprocs.
00:00000:00001:2015/06/29 08:52:24.70 server Started REDO pass for database 'sybsystemprocs'. The total number of log records to process is 1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Areston,
- Primary ASE server and Replication Server have different 'sa' password. To define a subscription with option "use dump marker", replication server needs to login the primary server as the user creating the subscription and with the password defined at the Replication Server so it can place an enable marker in the primary database.
Make sa passwords same.
- The DSIs of both connection 'PSMBFI.psmbfi' and connection STANDBY_SVR.psmbfi failed to login the database servers as maint users.
Reset their maint user passwords
isql -Usa -SPSMBFI -P<sa_password>
sp_password <sa_password>, <new_maint_user_ps>, psmbfi_maint
go
isql -Usa -SSTANDBY_SVR -P<sa_password>
sp_password <sa_password>, <new_maint_user_ps>, psmbfi_maint
go
isql -Usa -SRS -P xxxx
alter connection to PSMBFI.psmbfi
set password to '<new_maint_user_ps>
go
alter connection to STANDBY_SVR.psmbfi
set password to '<new_maint_user_ps>
go
resume connection to PSMBFI.psmbfi
go
resume connection to STANDBY_SVR.psmbfi
go
-Drop the pending subscription
drop subscription subname
for database replication definition repdefname
with primary at PSMBFI.psmbfi
with replicate at STANDBY_SVR.psmbfi
without purge
go
check subscription subname
for database replication definition repdefname
with primary at PSMBFI.psmbfi
with replicate at STANDBY_SVR.psmbfi
go
If the subscription doesn't go away, you manually delete it from RSSD
connect to RSSD
go
begin tran
delete rs_subscriptions where subname='subname>'
go
commit tran
go
disconnect
go
-Run admin who_is_down in repserver
No threads should be suspended or down
If DSI threads are down or suspended, you have to use errorlog messages to fix the problem and resume connection.
If Rep Agent for PSMBFI.psmbfi is down, start it with "sp_start_rep_agent psmbfi" in PSMBFI.
- Define subscription
define subscription subname
for database replication definition repdefname
with primary at PSMBFI.psmbfi
with replicate at STANDBY_SVR.psmbfi
subscribe to truncate table
use dump marker
go
- Dump primary database.
The DSI connection to the replicate database is suspended when the dump marker reaches the replicate Replication Server.
Therefore after the dump database command finishes and returns, run admin who_is_down in repserver and the command should show DSIs to connection STANDBY_SVR.psmbfi are suspended.
Don't resume connection to STANDBY_SVR.psmbfi at this step.
- Load replicate database from the dump files and online databases
-Prepare the replicate database as primary as well because you have created connections for bi-directional replication.
In STANDBY_SVR
use psmbfi
go
dbcc settrunc(ltm, ignore)
go
dump transaction psmbfi with truncate_only
go
dbcc settrunc(ltm,valid)
go
isql into repserver
connect to rssd
go
rs_zeroltm STANDBY_SVR, psmbfi
go
disconnect
go
- Resume connection to STANDBY_SVR.psmbfi
resume connection to STANDBY_SVR.psmbfi
go
-Start Reap Agent for STANDBY_SVR.psmbfi in STANDBY_SVR
sp_start_rep_agent psmbfi
go
-END
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
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.