Hello

We have a Replication Server for one database.

Sometimes the replication fail with error:

THREAD FATAL ERROR #5189 DSI EXEC(106(1) BICCONTINGENCIA.db_Bic) - /dsiutil.c(819)

        The DSI thread for the 'BICCONTINGENCIA.db_Bic' database is being shut down. DSI received Replication Server error #5185 which is mapped to STOP_REPLICATION or RETRY_STOP_REPLICATION.

When this error occurs, we skipped the transaction, with:

resume connection to BICCONTINGENCIA.db_Bic skip tran

What can i do for don't lose the transaction?

Thanks,

Rene.

I'm looking for an updated copy of the old gen_repdefs script (gen_repdef.ksh)?   It used to be in the developer's codeXchange site.   I've searched the SAP site, but to no avail.  Any idea where (if) I can get it now?

Thanks

Ben Slade

Hello Gurus,

We have installed and configured the ASE Replication for all our

production systems .We are encountering major issues on the ECC

Production system where replication of transaction logs are stopped

.This

occured when we had power shutdown and since then replication stopped

so

we tried to disable the replication and tried to enable its giving

error

hibernation mode.Also we want to know if materialization is necessary

for

this process - Currently our systems are in other location i.e. 10 KMS

away from HO and soon it will be also shifted to 500KMS AwAY.

In short -2 Issues (Logs Attached)

1.Need to fix Hibernation mode error

2.Do we need to re-materialise the database again or not required

Sybase REPL ASE Patch 135

OS : Windows 2008 R2

I am also aware that we can issue sysadmin hibernate_off once we add the partition .When I check admin disk_space its full.

I tried create partition but im not able to do as in ase database we use disk init here in rep server not sure how we can create

Appreciate if any one suggest

Regards

Asim

Hi all,

we're just starting up a project to test SAP ASE 16 SP2 here, and from the documentation of SAP ASE 16 SP2 it says that Cockpit will be the new tool to migrate to if you use SCC today. But as far as I can see, there is still no feature or possibility to monitor and/or manage SAP Replication Server from Cockpit ?

Does anybody know when Cockpit will include monitoring and manage of SAP Replication Server ?

Thanks

/Mike

Hello,

Having  Warm Standby pair  ASE to ASE I'm getting this error :

45. WARNING #7038 REP AGENT(dba.machi) - de/generic/mem/mem.c(2763)

WARNING: Memory usage is above 80 percent. Increase 'memory_limit' or reduce cache sizes to avoid repserver threads from sleeping due to lack of memory.

- This means that I should increase memory_limit in RS ? ( surely)

- What caches are supposed to be reduced .? This message is  kind of confusing..

Thanks

Regards

Jose

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          

********************* 

********

Regards

Mohammad

Hi all,

we're just starting up a project to test SAP ASE 16 SP2 here, and from the documentation of SAP ASE 16 SP2 it says that Cockpit will be the new tool to migrate to if you use SCC today. But as far as I can see, there is still no feature or possibility to monitor and/or manage SAP Replication Server from Cockpit ?

Does anybody know when Cockpit will include monitoring and manage of SAP Replication Server ?

Thanks

/Mike

corresponding record in exception log

=============================

1> rs_helpexception 2 ,'v'

2> go

        Detailed Summary of Logged Transaction # 2      on 'ServerA_rs'

Origin Site                    Origin User     Org. Commit Date  #Cmds in Xact

------------------------------ --------------- ----------------- -------------

serverA.db1               sa              Nov  2 2015  5:30             3

Dest. Site                     Dest. User      Date Logged

------------------------------ --------------- -----------------

ServerA.db2             maintuser       Nov  2 2015  5:30

This transaction was skipped due to a 'resume connection' command with the 'skip transaction' option.

                Rejected Records

textval                                                                                                                                                                                            

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

A0158 05iso_1distribute 1 ~";Nov  2 2015  5:30:43:013PM,2 ~"!,3 1 begin transaction ~"! npw ~"#sa osid 0                                                                                           

A0158 05iso_1distribute 2 ~"!,3 3 dump transaction ~!)db1 ~"620151102 17:30:43:013 0x10221d0200000000000000000000000000000032303135313130322031373a33                                         

A0158 05iso_1distribute 1 ~";Nov  2 2015  5:30:43:013PM,2 ~"!,3 1 commit transaction                                                                                                               

(return status = 0)

We're running MSA replication on ten user databases and also replicate the master database.

PDS->PRS->RRS->RDS

What we can see on the RDS is that users that for example has changed their password on PDS, is replicated to RDS as they should.

The transaction(s) however is not removed from the RDS/ASE process list. They just stay there doing nothing and has a status of "commit transaction".

And as you probably know, if you replicate the master database, a "maintenance user" is NOT used to do the work/transaction on your RDS like when you replicate a normal user database. It is the actual user that is logged on to the PDS/ASE that is also logging on to the RDS/ASE and execute the same stored procedure there.

This means that on our RDS, the number of active connections continues to grow, even if these connections has completed their processing.

What we also can see, is that if the RDS/ASE is restarted, all these connections/processes are removed.

But from my point of view, all these replicated transactions should terminate and be removed by themselves, and not remain as active in the process list ?

Does anyone recognize this phenomenon and/or have any solution for it ?

Thanks

/Mike

Hello,  I'm

Looking for the cause of the following error on a WS with RS 15.7.1 on linux:

1. E. 2015/11/04 05:10:43. ERROR #14023 REP AGENT(dba.machi) - neric/exec/execint.c(7206)

SQM had an error writing to the inbound-queue.

1. I. 2015/11/04 05:50:07. ...... connected to server 'huasco' as user 'fin700v60_maint'.
2. I. 2015/11/04 06:00:07. Connection to server 'huasco' as user 'fin700v60_maint' has been faded out (closed).
3. I. 2015/11/04 06:02:08. ...... connected to server 'huasco' as user 'fin700v60_maint'.
4. E. 2015/11/04 06:08:17. ERROR #6120 dAIO( ) - d64/sqm/rsaiolinux.c(1015)

SQM detected a failing status from an outstanding AIO (Status not set.).

1. E. 2015/11/04 06:08:17. ERROR #6026 SQM(118:1 WS_dba.fin700v60) - /generic/sqm/sqmio.c(1362)

Block write failed for queue '118:1', segment 0, block 0. OS dependent error is 'Status not set.'

1. I. 2015/11/04 06:08:17. SQM stopping due to an exception: 118:1 WS_dba.fin700v60
2. E. 2015/11/04 06:08:17. ERROR #30024 DIST(118 WS_dba.fin700v60) - /generic/exec/dist.c(6367)

The distributor for 'WS_dba.fin700v60' failed while reading a transaction from it's stable queue.

1. E. 2015/11/04 06:08:17. ERROR #14023 REP AGENT(dba.fin700v60) - neric/exec/execint.c(532)

SQM had an error writing to the inbound-queue.

Thank you

Regards

Jose

Hi Team,

I would like to know which are the benefits to use a software like SAP Replication Server versus replicate through hardware.

It could be great, If anyone has any documentation to help me demonstrate the benefits of software replication (SAP Replication Server) against hardware replication.

Thanks in advance!

Hi Team,

I have this weird error on my replication environment when applying a DDL change to primary server being replicated to MSA and Warm Standby.

Can some explain why I receive this error?

The command was

IF EXISTS

    (

    SELECT 1

    FROM sysobjects, syscolumns

    WHERE

        sysobjects.id = syscolumns.id                                                   

        AND sysobjects.name = 'SequentialValues'

        AND syscolumns.name = 'description'

        and syscolumns.status <> 0

     )

EXEC ('ALTER TABLE SequentialValues MODIFY description NOT NULL')

go

This executed successfully on the primary with no warning but brought the DSI down on the warm standby and MSA

Message from server: Message: 9502, State 9, Severity 16 -- 'Data exception - string data right truncated'

The DSI thread for database 'WSBSRV.DB' is being shutdown. DSI received data server error #9502 which is mapped to STOP_REPLICATION. See logged data server errors for more information. The data server error was caused by output command #0 mapped from input command #0 of the failed transaction.

I. 2015/10/29 14:44:30. The DSI thread for database 'WSBSRV.DB' is shutdown.

E. 2015/10/29 14:48:21. ERROR #1028 DSI EXEC(466(1) MSASRV.DB) - dsiqmint.c(4722)

        Message from server: Message: 9502, State 9, Severity 16 -- 'Data exception - string data right truncated'

The script first does the following

1. first add the field

ALTER TABLE SequentialValues ADD description varchar(100) NULL

2. update the column to make sure non of the data is null

3. then alter the table to make it not null

When I look at the primary table table the largest data length in that column is 70, which is well below the 100 defined on the table

SELECT max(char_length(description)) FROM dbo.SequentialValues

I was able to resume the DSI only after manually applying the same command on the WSB and MSA database.

On resumption of the DSI the following warning message was displayed but the transactionwas able to continue

. 2015/10/29 16:24:33. The DSI thread for database 'WSBSRV.DB' is started.

I. 2015/10/29 16:24:33. Message from server: Message: 13925, State 1, Severity 10 -- 'Warning: ALTER TABLE operation did not affect column 'description'.'.

I. 2015/10/29 16:24:33. Message from server: Message: 13905, State 1, Severity 10 -- 'Warning: no columns to drop, add or modify. ALTER TABLE 'SequentialValues' was aborted.'.

I. 2015/10/29 16:24:33. Database 'WSBSRV.DB' returns messages that are mapped to IGNORE or WARN by error action mapping. See logged data server messages for more information.

I. 2015/10/29 16:26:00. The DSI thread for database 'MSASRV.DB' is started.

I. 2015/10/29 16:26:00. Message from server: Message: 13925, State 1, Severity 10 -- 'Warning: ALTER TABLE operation did not affect column 'description'.'.

I. 2015/10/29 16:26:00. Message from server: Message: 13905, State 1, Severity 10 -- 'Warning: no columns to drop, add or modify. ALTER TABLE 'SequentialValues' was aborted.'.

I. 2015/10/29 16:26:00. Database 'MSASRV.DB' returns messages that are mapped to IGNORE or WARN by error action mapping. See logged data server messages for more information.

We have source data in ASE with “cp850” charset and “nocase_cp850” sort order.

Replication server (currently) is cp850 and “nocase”.

There is a Warm Standby pairing setup to provide DR for the cp850 source.

We want to add a UTF-8 ASE instance into the mix, which will receive replicate data from the cp850 source.
We also need a “DR” for this UTF-8 instance.  At this time, however, there is no data going in to the UTF-8 instance except from RepServer (effectively it’s read-only to clients). There will be 350+ subscriptions feeding the UTF-8 instance though – so we ideally need the UTF-8 DR to be Warm Standby or MSA so we don't have to manage double the number of subscriptions!

We have 3 options to provide this (that we can think of) :

1.  Leave RepServer at cp850 and that populates the UTF-8 instance(s).

2.  Change the RepServer to use UTF-8

3.  Setup a UTF-8 RepServer fed via a route from the cp850 RepServer: the former feeds/replicates the UTF-8 instance; the latter does DR/Standby for the cp850 source

My questions on each of these options are:

1. If all the data (source) is cp850, does it matter that the “targets” are UTF-8 (which I think contains all the cp850 characters)? How will the MSA/WS replication of the UTF-8 instance work - through a cp850 RepServer – assuming that all the character data is cp850-compatible anyway?
2. Will the cp850 WS replication be OK going through a UTF-8 RepServer?
3. Will the cp850 to UTF-8 conversion happen ok between 2 RepServers on the different charsets? Which should be the ID server (currently the cp850 one is its own ID server)? Should both RSSDs be the same charset as their respective RepServers?

The manuals advise you to have all the character sets and sort orders the same across a replication system, but that's not an option here and I'm not sure what the "correct" way to ignore that advice is

Hi

Do we have the capability to do replication FROM a DB2 on OS/400 to ASE?

If so - is this log based replication?

Many thanks

Roger

Dear Experts,

I've started Run_Container.sh after that server terminated,

sybase@saprs:/opt/sybase/REP/RAH/HANARAX/bin> ./RunContainer.sh

./RunContainer.sh: line 78: -XX:+UseConcMarkSweepGC: command not found

12:35:06.751 - SAP HANA Replication Agent Server for Unix & Windows - Runtime is Starting, Process ID is 6753

12:35:06.751 - Using Config File /opt/sybase/REP/RAH/HANARAX/config/ContainerRuntime.xml

12:35:06.751 - Using Global Bootstrap File /opt/sybase/REP/RAH/HANARAX/config/bootstrap.prop

12:35:06.751 - Using Local Bootstrap File /opt/sybase/REP/RAH/HANARAX/instances/AgentContainer/config/bootstrap.prop

12:35:07.165 - Loading Components and Services

12:35:07.331 - Initializing Services

12:35:11.216 - AgentContainer Now Accepting TDS Connections on port 7001

12:35:12.583 - AgentContainer Now Accepting Connections at service:jmx:rmi:///jndi/rmi://saprs:7000/rsng

12:35:12.583 - Runtime Container saprs::AgentContainer [a12e99cb-7de8-46f2-a920-d6f6a31aa174] is Operational

12:35:12.593 - Starting Components

12:35:12.594 - Starting HanaRAX

12:35:12.594 - Starting ContainerAgent

12:35:12.596 - SAP HANA Replication Agent Server for Unix & Windows - Startup is Complete

12:35:12.666 - Hana Replication Agent is Starting

12:35:12.741 - Container Agent is Running

12:35:12.757 - Unable to Checkout Core License, Terminating Server

12:35:12.757 - *** Server Terminating, See Log for Error Information ***

[16.481][Info][12:35:22.762][ContainerShutdownHook:16][CONTAINER] - Shutdown wait exceeded, shutting down

Hi Experts,

I have made connection with profile rs_hanadb_to_hanadb, but error

create connection to RAHDB_TEST2.SAPHTS

using profile rs_hanadb_to_hanadb;ech

set username SAPHTS

set password H***********

go

Msg 153, Level 12, State 0:

Server 'SAPRS':

Connection profile is not defined. Profile: <rs_hanadb_to_hanadb>; Version:<ech>.

Whatconnectionprofilefor replicationfrom hanatohana ?

Thanks & Regards,

Deby Afandi

While creating subscription for master database, distributor is down with following error. database subscription remains in defined state.

Tried created with defined, activate and validated command restarted distributor but no luck. I am using rep server 15,7 and ASE 15.7.

I. 2015/11/12 15:04:04. PRIMARY Replication Server: Defining subscription <repdef_master_01_to_02_sub> for database replication definition <repdef_master_01> with primary at <test_01.master> with replicate at <test_02.master>

W. 2015/11/12 15:05:01. WARNING #60026 DIST(411 test_01.master) - sub_dist.c(1463)

        No synchronization handle was found for sync element RSHRshandleInfoMutex. (3326)eneric/useful/sync.c.

E. 2015/11/12 15:05:01. ERROR #60037 DIST(411 test_01.master) - sub_dist.c(1470)

        Failed to release lock on sync element 'SubGlblMutex'. Info 19

I. 2015/11/12 15:05:01. DIST for 'test_01.master' is waiting for SQM(s) to flush to outbound queue(s).

I. 2015/11/12 15:05:01. The distributor for 'test_01.master' is shutting down

Any idea ?

Hi!

I'm setting up my first SAP Replication Server scenario, with the following landscape:

Server 1 (source): Windows Server running an 32 bit Oracle Database 11g R2. Here I installed Rep. Agent (win32) version 15.7.1 SP209.

Server 2: Windows Server running Replication Server version 15.7.1 SP301 (64bit). I choose to install the Sample Server, SAMPLE_RS as part of the installation. The server seems to be running well and is accessible with the users created (e.g. SAMPLE_RS_ra & sa) using isql. The ports for both ERSSD and server are open in FW and netstat -an shows them listening.

Server 3 (target): HANA version 97. Connection has been made and looks fine.

Currently I'm configuring my Agent instance, and my problem shows when I validate this configuration using ra_admin.bat tool (parameter: -vr):

nov 13, 2015 10:57:34 AM com.sybase.ra.RepAgentAdmin initLogging

TRACE: SAP Replication Agent for Unix & Windows/15.7.1 SP209/P/generic/JDK 7.0/rax1571sp209/62090.209/VM: SAP AG 1.7.0_25/OPT/Mon Aug 31 21:10:49 MDT 2015

nov 13, 2015 10:57:34 AM com.sybase.ra.RepAgentAdmin initLogging

TRACE: ra_admin -vr ora1.rs

nov 13, 2015 10:57:37 AM com.sybase.ra.admin.oracle.RAOResponseFileProperties verifyProperties

INFORMATION: Completed first pass of verification for resource file <ora1.rs>.

nov 13, 2015 10:57:39 AM com.sybase.ra.admin.RsRssdVerification verifyRS

TRACE: Testing connection to RepServer...

nov 13, 2015 10:57:39 AM com.sybase.ra.admin.JDBCConnectionFactory testConnection

ERROR: Failed to connect to <jdbc:sybase:Tds:10.151.20.54:11751> as <SAMPLE_RS_ra> because: JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).

I hope somebode know what this is caused by?? (The SAMPLE_RS seem to use charset cd850, and I have tried to put both iso_1, cp850 and utf8 into the rs_charset parameter in the Rep Agent conf file - with the same error as shown above).

Thanks, br Mads

corresponding record in exception log

=============================

1> rs_helpexception 2 ,'v'

2> go

        Detailed Summary of Logged Transaction # 2      on 'ServerA_rs'

Origin Site                    Origin User     Org. Commit Date  #Cmds in Xact

------------------------------ --------------- ----------------- -------------

serverA.db1               sa              Nov  2 2015  5:30             3

Dest. Site                     Dest. User      Date Logged

------------------------------ --------------- -----------------

ServerA.db2             maintuser       Nov  2 2015  5:30

This transaction was skipped due to a 'resume connection' command with the 'skip transaction' option.

                Rejected Records

textval                                                                                                                                                                                            

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

A0158 05iso_1distribute 1 ~";Nov  2 2015  5:30:43:013PM,2 ~"!,3 1 begin transaction ~"! npw ~"#sa osid 0                                                                                           

A0158 05iso_1distribute 2 ~"!,3 3 dump transaction ~!)db1 ~"620151102 17:30:43:013 0x10221d0200000000000000000000000000000032303135313130322031373a33                                         

A0158 05iso_1distribute 1 ~";Nov  2 2015  5:30:43:013PM,2 ~"!,3 1 commit transaction                                                                                                               

(return status = 0)

Hi All,

We are in a process of building SAP sybase DR.We are using same ips for both primary and DR(but diff VPNs). we are using natting IP concept. We are facing below error message which is attached Thanks in advance.

From primary to DR(nating ip)...server is pinging and vice-versa.

o perform authentication have been set.

2015-11-19 16:52:29,447 [INFO ] [model.DRExecutor                            ] [Thread-34] - Task Executor - Action - Authenticating login 'DR_admin' against host 'BIPRDDBCIDR:4901'.

2015-11-19 16:52:29,447 [INFO ] [conn.ConnectionManager                      ] [Thread-34] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:52:29,447 [TRACE] [conn.ConnectionManager                      ] [Thread-34] - Creating connection to pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (433/0/0/0/0)

2015-11-19 16:52:29,473 [TRACE] [conn.ConnectionManager                      ] [Thread-34] - Allocated connection: -1614348887(com.sybase.jdbc4.jdbc.SybConnection@4b34c007) pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (434/0/1/1/0)

2015-11-19 16:52:29,473 [INFO ] [model.DRExecutor                            ] [Thread-34] - Task Executor - Action - Successfully authenticated login 'DR_admin' against host 'BIPRDDBCIDR:4901'.

2015-11-19 16:52:29,473 [TRACE] [conn.ConnectionManager                      ] [Thread-34] - Terminate connection <-1614348887(com.sybase.jdbc4.jdbc.SybConnection@4b34c007)>: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (434/0/1/1/0)

2015-11-19 16:52:29,474 [INFO ] [model.DRExecutor                            ] [Thread-34] - Task Executor - Action - Checking that all mandatory properties have been set.

2015-11-19 16:52:29,474 [INFO ] [model.DRExecutor                            ] [Thread-34] - Task Executor - Action - Preparing to execute Task 'Set Remote Property'

2015-11-19 16:52:29,474 [INFO ] [model.DRExecutor                            ] [Thread-34] - Task Executor - Action - Preparing to execute Task 'Set Remote Property'

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Task Name - Set Remote Property

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Description - Set a configuration property at the remote host.

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - State - Initialized

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Hostname - BIPRDDBCIDR

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - State - Running

2015-11-19 16:52:29,474 [TRACE] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Pre Execution running.

2015-11-19 16:52:29,474 [TRACE] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Execution running.

2015-11-19 16:52:29,474 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Action - Successfully set property participating_databases to [master, B30].

2015-11-19 16:52:29,475 [TRACE] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - Post Execution running.

2015-11-19 16:52:29,475 [INFO ] [api.SetModelProperty                        ] [Thread-34] - Task Set Remote Property - State - Completed

2015-11-19 16:52:29,497 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-34] - TDS DISCONNECT

2015-11-19 16:52:31,988 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-35] - TDS LOGIN with User: DR_admin

2015-11-19 16:52:31,988 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-35] - Login attempt by the user 'DR_admin' from client host 'srv205'.

2015-11-19 16:52:32,010 [DEBUG] [dr.ReplicationDRPlugin                      ] [Thread-35] - TDS RPC: sp_mda

2015-11-19 16:52:32,032 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-35] - Received TDS LANGUAGE command: use 'master'

2015-11-19 16:52:32,055 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-35] - TDS DISCONNECT

2015-11-19 16:52:32,203 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-36] - TDS LOGIN with User: DR_admin

2015-11-19 16:52:32,203 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-36] - Login attempt by the user 'DR_admin' from client host 'srv205'.

2015-11-19 16:52:32,225 [DEBUG] [dr.ReplicationDRPlugin                      ] [Thread-36] - TDS RPC: sp_mda

2015-11-19 16:52:32,247 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-36] - Received TDS LANGUAGE command: use 'master'

2015-11-19 16:52:32,270 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-36] - Received TDS LANGUAGE command: sap_pre_setup_check local,dr,prim,stby

2015-11-19 16:52:32,270 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Task Name - Diagnose Environment

2015-11-19 16:52:32,270 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Description - Diagnose the environment for disaster recovery setup readiness.

2015-11-19 16:52:32,270 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Preparing to execute Task 'Diagnose Environment'

2015-11-19 16:52:32,270 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Checking that all mandatory properties required to perform authentication have been set.

2015-11-19 16:52:32,271 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Authenticating login 'DR_admin' against host 'BIPRDDBCIDR:4901'.

2015-11-19 16:52:32,271 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:52:32,271 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (434/0/0/0/0)

2015-11-19 16:52:32,363 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: -1281832210(com.sybase.jdbc4.jdbc.SybConnection@9f9676bf) pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (435/0/1/1/0)

2015-11-19 16:52:32,363 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Successfully authenticated login 'DR_admin' against host 'BIPRDDBCIDR:4901'.

2015-11-19 16:52:32,364 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <-1281832210(com.sybase.jdbc4.jdbc.SybConnection@9f9676bf)>: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (435/0/1/1/0)

2015-11-19 16:52:32,364 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Checking that all mandatory properties have been set.

2015-11-19 16:52:32,364 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Preparing to execute Task 'Diagnose Environment'

2015-11-19 16:52:32,364 [INFO ] [model.DRExecutor                            ] [Thread-36] - Task Executor - Action - Preparing to execute Task 'Diagnose Environment'

2015-11-19 16:52:32,365 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - Task Name - Diagnose Environment

2015-11-19 16:52:32,365 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - Description - Diagnose the environment for disaster recovery setup readiness.

2015-11-19 16:52:32,365 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - State - Initialized

2015-11-19 16:52:32,365 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - Hostname - BIPRDDBCIDR

2015-11-19 16:52:32,365 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - State - Running

2015-11-19 16:52:32,365 [TRACE] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - Pre Execution running.

2015-11-19 16:52:32,365 [TRACE] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - Execution running.

2015-11-19 16:52:32,366 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Task Name - Validate Local Disaster Recovery Environment

2015-11-19 16:52:32,366 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Description - Verify that the local environment is setup and ready for disaster recovery replication setup to run.

2015-11-19 16:52:32,366 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - State - Initialized

2015-11-19 16:52:32,366 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Hostname - BIPRDDBCIDR

2015-11-19 16:52:32,366 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - State - Running

2015-11-19 16:52:32,366 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Pre Execution running.

2015-11-19 16:52:32,366 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Execution running.

2015-11-19 16:52:32,369 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:52:32,369 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (435/0/0/0/0)

2015-11-19 16:52:32,401 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: -1396785945(com.sybase.jdbc4.jdbc.SybConnection@189ab3cc) pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (436/0/1/1/0)

2015-11-19 16:52:32,402 [INFO ] [operations.ASEDatabase                      ] [Thread-36] - Executing query: sp_databases

2015-11-19 16:52:32,620 [INFO ] [operations.ASEDatabase                      ] [Thread-36] - Executing query: sp_databases

2015-11-19 16:52:32,621 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Executing ASE command <sp_configure 'enable granular permissions'>

2015-11-19 16:52:32,630 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Result from command for runtime value was <0>

2015-11-19 16:52:32,859 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <-1396785945(com.sybase.jdbc4.jdbc.SybConnection@189ab3cc)>: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (436/0/1/1/0)

2015-11-19 16:52:32,859 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Connection already closed. Connection pool statistics: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (436/0/0/0/0)

2015-11-19 16:52:32,859 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Registering a connection pool for URL <proxool.BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca:com.sybase.jdbc4.jdbc.SybDriver:jdbc:sybase:Tds:BIPRDDBCIDR:4901/master>

2015-11-19 16:52:32,860 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:52:32,860 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (0/0/0/0/0)

2015-11-19 16:52:32,892 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: -1821548684(com.sybase.jdbc4.jdbc.SybConnection@6fa7f1bd) pool: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (1/0/1/1/0)

2015-11-19 16:52:32,892 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Executing ASE command <sp_configure 'enable granular permissions'>

2015-11-19 16:52:32,902 [TRACE] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Result from command for runtime value was <0>

2015-11-19 16:52:32,956 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <-1821548684(com.sybase.jdbc4.jdbc.SybConnection@6fa7f1bd)>: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (1/0/1/1/0)

2015-11-19 16:52:32,959 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:52:32,959 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (1/0/0/0/0)

2015-11-19 16:52:32,991 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: 1129692772(com.sybase.jdbc4.jdbc.SybConnection@34ad007b) pool: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (2/0/1/1/0)

2015-11-19 16:52:32,993 [INFO ] [operations.ASEDatabase                      ] [Thread-36] - Executing query: use master

2015-11-19 16:52:32,994 [INFO ] [operations.ASEDatabase                      ] [Thread-36] - Executing query: sp_helprotect

2015-11-19 16:52:34,022 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - The role 'sap_maint_user_role' was granted the set session authorization permission and was assigned to the the maintenance user 'B30_maint'.

2015-11-19 16:52:34,022 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <1129692772(com.sybase.jdbc4.jdbc.SybConnection@34ad007b)>: BIPRDDBCIDR_4901_B30_maint_6d9e1d84ad2ab01e4d51da0c82fca (s/r/a/t/o) (2/0/1/1/0)

2015-11-19 16:52:34,031 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Registering a connection pool for URL <proxool.BIPRDDBCIDR_4905_DR_admin_f33b7e285a5ed99273faf5177aa027:com.sybase.jdbc4.jdbc.SybDriver:jdbc:sybase:Tds:BIPRDDBCIDR:4905/master>

2015-11-19 16:52:34,031 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4905/master'.

2015-11-19 16:52:34,031 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4905_DR_admin_f33b7e285a5ed99273faf5177aa027 (s/r/a/t/o) (0/0/0/0/0)

2015-11-19 16:52:34,032 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Create connection failed java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: A remote host refused an attempted connect operation..

2015-11-19 16:52:34,032 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Removing an empty connection to pool, after failing to create any connection.  Pool <BIPRDDBCIDR_4905_DR_admin_f33b7e285a5ed99273faf5177aa027>.

2015-11-19 16:52:34,032 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Registering a connection pool for URL <proxool.BIPRDDBCIDR_4906_prim_6_REP_RSSD_prim_60f68a7281acb8be2bc44e6c2d816991:com.sybase.jdbc4.jdbc.SybDriver:jdbc:sybase:Tds:BIPRDDBCIDR:4906/master>

2015-11-19 16:52:34,033 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4906/master'.

2015-11-19 16:52:34,033 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4906_prim_6_REP_RSSD_prim_60f68a7281acb8be2bc44e6c2d816991 (s/r/a/t/o) (0/0/0/0/0)

2015-11-19 16:52:34,034 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Create connection failed java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: A remote host refused an attempted connect operation..

2015-11-19 16:52:34,034 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Removing an empty connection to pool, after failing to create any connection.  Pool <BIPRDDBCIDR_4906_prim_6_REP_RSSD_prim_60f68a7281acb8be2bc44e6c2d816991>.

2015-11-19 16:52:34,036 [TRACE] [plugins.dr                                  ] [Thread-36] - Testing port availability: Socket is closed, port number 4905

2015-11-19 16:52:34,036 [TRACE] [plugins.dr                                  ] [Thread-36] - Testing port availability: Socket is closed, port number 4906

2015-11-19 16:52:34,036 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Registering a connection pool for URL <proxool.10.10.11.85_4909_DR_admin_c5ea84be94455738537567dcf3b172ad:com.sybase.jdbc4.jdbc.SybDriver:jdbc:sybase:Tds:10.10.11.85:4909/master>

2015-11-19 16:52:34,038 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:10.10.11.85:4909/master'.

2015-11-19 16:52:34,038 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: 10.10.11.85_4909_DR_admin_c5ea84be94455738537567dcf3b172ad (s/r/a/t/o) (0/0/0/0/0)

2015-11-19 16:53:04,039 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Create connection failed java.sql.SQLException: JZ00M: Login timed out. Check that your database server is running on the host and port number you specified. Also, check the database server for other conditions (such as a full tempdb) that might be causing it to hang..

2015-11-19 16:53:04,039 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Removing an empty connection to pool, after failing to create any connection.  Pool <10.10.11.85_4909_DR_admin_c5ea84be94455738537567dcf3b172ad>.

2015-11-19 16:53:04,039 [WARN ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Unable to connect to remote agent '10.10.11.85:4909'

2015-11-19 16:53:04,041 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:53:04,041 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (436/0/0/0/0)

2015-11-19 16:53:04,140 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: 614398271(com.sybase.jdbc4.jdbc.SybConnection@91f71e55) pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (437/0/1/1/0)

2015-11-19 16:53:04,140 [INFO ] [operations.HADRStatus                        ] [Thread-36] - Executing query: select @@hadr_mode, @@hadr_state

2015-11-19 16:53:04,141 [INFO ] [operations.HADRStatus                        ] [Thread-36] - HADR status for ASE 'ASE_8' on host 'prim' is '[Disabled : Unknown]'.

2015-11-19 16:53:04,141 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <614398271(com.sybase.jdbc4.jdbc.SybConnection@91f71e55)>: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (437/0/1/1/0)

2015-11-19 16:53:04,142 [INFO ] [util.HADRUtil                                ] [Thread-36] - ASE HADR server is ready to be configured.

2015-11-19 16:53:04,142 [INFO ] [conn.ConnectionManager                      ] [Thread-36] - ConnectionManager: Creating connection with url= 'jdbc:sybase:Tds:BIPRDDBCIDR:4901/master'.

2015-11-19 16:53:04,142 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Creating connection to pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (437/0/0/0/0)

2015-11-19 16:53:04,185 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Allocated connection: 2062123975(com.sybase.jdbc4.jdbc.SybConnection@d410adc9) pool: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (438/0/1/1/0)

2015-11-19 16:53:04,195 [TRACE] [conn.ConnectionManager                      ] [Thread-36] - Terminate connection <2062123975(com.sybase.jdbc4.jdbc.SybConnection@d410adc9)>: BIPRDDBCIDR_4901_DR_admin_14c719163a4266b324d5f3237f6f967 (s/r/a/t/o) (438/0/1/1/0)

2015-11-19 16:53:04,203 [ERROR] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - Failed with error message - prim - DR Agent - Unable to connect to remote agent '10.10.11.85:4909'

2015-11-19 16:53:04,203 [INFO ] [tasks.ValidateLocalDREnv                    ] [Thread-36] - Task Validate Local Disaster Recovery Environment - State - Error

2015-11-19 16:53:04,203 [INFO ] [api.DiagnoseEnvironment                      ] [Thread-36] - Task Diagnose Environment - State - Error

2015-11-19 16:53:04,204 [INFO ] [tasks.GetPathStatus                          ] [Thread-36] - Elapsed execution time for 'Diagnose Environment' task: 00:00:31

2015-11-19 16:53:04,267 [INFO ] [dr.ReplicationDRPlugin                      ] [Thread-36] - TDS DISCONNECT

Thanks,

Venkat.D