Error during configuration of SAP Replication server.

[Former Member]

Dear All,

I am in the process of building the DR for our PRD system.

System Details are as follows:

SAP ERP 6.0 EhP 6 on SAP Sybase ASE 15.7 Patch 110 on Linux 6.2 OS.

I did the steps to build the Replication Server as mentioned in the Installation guide.

1. Applied patch 110 in The production system.

2. Installed a new Database system (Standby system), as mentioned in the installation guide.

3. Before going ahead with the installation of Replication server software in the production server, I started the installation in the standby system.

This is where I get the error.

The error is that, during installation, @ step 8 (Verify Replication Server version), it throws an assertion error, which is as follows:

FCO-00011 The step syb_step_verify_rs_version with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_prepare|ind|ind|ind|ind|id_c_syb_rep_prepare|0|syb_step_verify_rs_version was executed with status ERROR (Last error reported by the step: Assertion failed: unable to verify the replication server version. Refer to trace file sapinst_dev.log for further information.).

I do not find any other error message in the entire sapinst_dev.log

The replication Installation software version that I am currently using is :REPSERVER1570110_0-20011160.TGZ

As mentioned in the installation guide, I am getting the same error message even for REPSERVER1570111_0-20011160.TGZ

I tried re-installing the software too, but am always held up at the same place.

How do I proceed further?

Any help is appreciated.

Thanks & Regards,

Dino

[Former Member]

Hopefully, this issue might be the last 1 in configuring SAP SRS:

The contents of table master..sysloginroles are different in primary and standby.

The number of rows are 22 in primary and 21 in secondary

The materialization of master is failing.

Current issue is as follows:

ERROR 2014-01-10 01:09:59.754

MUT-03025  Caught ESAPinstException in module call: .

ERROR 2014-01-10 01:10:00.102

FCO-00011  The step syb_step_mat_master with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_materialize|ind|ind|ind|ind|id_c_syb_rep_materialize|0|syb_step_mat_master was executed with status

ERROR ( Last error reported by the step: Assertion failed: </i><br><br>The materialization status is unexpected.<br><br>The DR agent reports the following:<br><br><pre>

1> sap_status path

Path               Name          Value                    Info

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

                    Start Time    2014-01-10 01:09:58.192  Time command started executing.

                    Elapsed Time  00:00:01                 Command execution time.

SID                Hostname      ggsapepSID               Logical host name.

SID                HADR Status   Disabled : Unknown       Identify the primary and standby sites.

SIDREP             Hostname      ggsapr3dbb               Logical host name.

SIDREP             HADR Status   Disabled : Unknown       Identify the primary and standby sites.

SID.SIDREP.SID     State         Defined                  Path is defined and ready for materialization.

SID.SIDREP.SID     Latency       Unknown                  No latency information for database 'SID'.

SID.SIDREP.SID     Commit Time   Unknown                  No last commit time for the database 'SID'.

SID.SIDREP.master  State         Defined                  Path is defined and ready for materialization.

SID.SIDREP.master  Latency       Unknown                  No latency information for database 'master'.

SID.SIDREP.master  Commit Time   Unknown                  No last commit time for the database 'master'.

SIDREP.SID.SID     State         Suspended                Path is suspended. Transactions are not being replicated.

SIDREP.SID.SID     Latency       Unknown                  No latency information for database 'SID'.

SIDREP.SID.SID     Commit Time   Unknown                  No last commit time for the database 'SID'.

SIDREP.SID.master  State         Suspended                Path is suspended. Transactions are not being replicated.

SIDREP.SID.master  Latency       Unknown                  No latency information for database 'master'.

SIDREP.SID.master  Commit Time   Unknown                  No last commit time for the database 'master'.

(18 rows affected)</pre><br>Refer to trace file sapinst_dev.log for further information.<br><br><i>).

INFO 2014-01-10 01:10:00.525

Creating file /tmp/sapinst_instdir/GENERIC/SYB/REPENV/SETUP/__instana_tmp.xml.

PerformMasterMaterialization  Failing Command Error Message  The row count in the Master database does not match between source and target systems.  Table 'master..sysloginroles' has source row count '22' but target row count '21'

Materialize                   Start Time                     2014-01-10 01:03:53.474                                                                                                               

Materialize                   Elapsed Time                   00:00:33                                                                                                                              

Materialize                   Task Name                      Materialize                                                                                                                           

Materialize                   Task State                     Error                                                                                                                                 

Materialize                   Short Description              Materialize database                                                                                                                  

Materialize                   Long Description               Starting materialization of the master database from source 'QAS' to target 'QASREP'.                                                 

Materialize                   Hostname                       ggsapepqas                                                                                                                            

PerformMasterMaterialization  Task Name                      Materialize the Master database                                                                                                       

PerformMasterMaterialization  Task State                     Error                                                                                                                                 

PerformMasterMaterialization  Short Description              Materializes the Master database by using a bulk copy utility to copy necessary tables.                                               

PerformMasterMaterialization  Long Description               Comparing the rows counts after the bulk copy operations for the 'master' database between source host 'QAS' and target host 'QASREP' 

PerformMasterMaterialization  Failing Command Error Message  The row count in the Master database does not match between source and target systems.  Table 'master..sysloginroles' has source row count '22' but target row count '21'.

PerformMasterMaterialization  Corrective Action              Verify no user or security request are being performed on the source system and retry materialization.                                

PerformMasterMaterialization  Current Task Number            5                                                                                                                                     

PerformMasterMaterialization  Total Number of Tasks          7                                                                                                                                     

PerformMasterMaterialization  Hostname                       ggsapepqas 

insert into master..sysloginroles (suid, srid, status, predid)

values (5, 0, 1, NULL)

How to resolve this issue?

Thanks & Regards,

Dino

[Former Member]

Dear All,

Even we have same issue as above , any idea ....

SAP SYBASE Experts need you inputs here ....

sap_status path

Path                  Name          Value                    Info                                                      

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

                       Start Time    2014-01-26 14:52:47.306  Time command started executing.                           

                       Elapsed Time  00:00:01                 Command execution time.                                   

sybpr1                Hostname      sap-dr-pr1               Logical host name.                                        

sybpr1                HADR Status   Disabled : Unknown       Identify the primary and standby sites.                   

sybdr2                Hostname      sap-DR-RP                Logical host name.                                        

sybdr2                HADR Status   Disabled : Unknown       Identify the primary and standby sites.                   

sybdr2.sybpr1.TSN     State         Suspended                Path is suspended. Transactions are not being replicated. 

sybdr2.sybpr1.TSN     Latency       Unknown                  No latency information for database 'TSN'.                

sybdr2.sybpr1.TSN     Commit Time   Unknown                  No last commit time for the database 'TSN'.               

sybdr2.sybpr1.master  State         Suspended                Path is suspended. Transactions are not being replicated. 

sybdr2.sybpr1.master  Latency       Unknown                  No latency information for database 'master'.             

sybdr2.sybpr1.master  Commit Time   Unknown                  No last commit time for the database 'master'.            

sybpr1.sybdr2.TSN     State         Defined                  Path is defined and ready for materialization.            

sybpr1.sybdr2.TSN     Latency       Unknown                  No latency information for database 'TSN'.                

sybpr1.sybdr2.TSN     Commit Time   Unknown                  No last commit time for the database 'TSN'.               

sybpr1.sybdr2.master  State         Defined                  Path is defined and ready for materialization.            

sybpr1.sybdr2.master  Latency       Unknown                  No latency information for database 'master'.             

sybpr1.sybdr2.master  Commit Time   Unknown                  No last commit time for the database 'master'.           

Regards

[Former Member]

Hi,

The sap_status path information shows the environment is ready for materialization:

sybpr1.sybdr2.master  State         Defined                 "Path is defined and ready for materialization."

What error are you getting when attempting to perform materialziation?  The same error as Dino with sysloginroles row count not matching?

Before applying the rows from the primary, the standby copy of syslogins is cleared of duplicate rows using the following delete command:

"delete from master..sysloginroles where srid != 0 and srid != 1"

(srid 0 and 1 are sa and sso roles - we don't delete those becuase it could leave the system inoperable if those roles do not exists).   Examp,e sysloginroles definition can be found here:

http://infocenter.sybase.com/archive/index.jsp?topic=/com.sybase.help.ase_15.0.tables/html/tables/ta...

What this means is that sa and sso roles do not participate in the copy / materialization process.

And as a result, in your environment, you have more users with 'sa' or 'sso' role in one environment than you do in the other.  To resolve the issue, remove the grant or extra login that exists in only one environment, or add the same role / user combination in the other environment - however you would like to change the two so that the have the same # of logings that have been granted sa and sso roles.

Regards,
Stephen

[Former Member]

Hi Stephan,

As per below resolution I did a cross check of # of logins and roles assigned to login in both environment , Everything seems to be fine .

""To resolve the issue, remove the grant or extra login that exists in only one environment, or add the same role / user combination in the other environment - however you would like to change the two so that the have the same # of logings that have been granted sa and sso roles.""

any other suggestion please ..

Thanks

Mohammad

[Former Member]

Hi Mohammad,

If you can execute this query on both hosts, and get the same results, materialization of the sysloginroles table should succeed ( you are just querying the rows that materialization process is skipping)

select suid, srid from master..sysloginroles where srid = 0 or srid = 1

If you still have a difference ebtween the two systems, you can identify the login involved with the following query:

select name from master..syslogins where suid = ?

where ? is the suid value from the sysloginroles query.

Regards,
Stephen

[Former Member]

Hello Stephen,

I have executed both queries on both nodes and attached is output.

extra login is there  1002 0 , but when I am trying to delete this it gives error... I did tried with sa and sso logins

delete from master..sysloginroles where suid != 1002 and srid != 0

*****

msg 10321, Level 14, State 1:
Server 'TSN', Line 1, Status 0, TranState 1:
Ad-hoc updates to system catalogs not enabled. A user with System Security Officer (SSO) role must reconfigure system to allow this.

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

please suggest.

Thanks

Mohammad

[Former Member]

ello,

I have moved on with this error.. by executing below commands on

secondary node.

sp_configure 'allow updates',1

delete from master..sysloginroles where suid = 1002

however I received same error. Attached logs

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

sap_status path

Path                  Name                           Value

            Info

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

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

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

                       Start Time                     2014-01-29

12:05:50.838        Time command started executing.

                       Elapsed Time                   00:00:03

            Command execution time.

sybpr1                Hostname                       sap-dr-pr1

            Logical host name.

sybpr1                HADR Status                    Disabled : Unknown            Identify the primary and standby sites.

sybdr2                Hostname                       sap-DR-RP

            Logical host name.

sybdr2                HADR Status                    Disabled : Unknown            Identify the primary and standby sites.

sybdr2.sybpr1.TSN     State                          Suspended

            Path is suspended. Transactions are not being replicated.

sybdr2.sybpr1.TSN     Latency                        Unknown

            No latency information for database 'TSN'.

sybdr2.sybpr1.TSN     Commit Time                    Unknown

            No last commit time for the database 'TSN'.

sybdr2.sybpr1.master  State                          Suspended

            Path is suspended. Transactions are not being replicated.

sybdr2.sybpr1.master  Latency                        Unknown

            No latency information for database 'master'.

sybdr2.sybpr1.master  Commit Time                    Unknown

            No last commit time for the database 'master'.

sybpr1.sybdr2.TSN     State                          Suspended

            Path is suspended. Transactions are not being replicated.

sybpr1.sybdr2.TSN     Failing Command Error Message  Failing Command

Error Message  The connection in the Replication Server on the sybdr2

host to 'TSN_sybdr2.TSN' is not configured.

sybpr1.sybdr2.TSN     Latency                        Unknown

            No latency information for database 'TSN'.

sybpr1.sybdr2.TSN     Commit Time                    Unknown

            No last commit time for the database 'TSN'.

sybpr1.sybdr2.master  State                          Active

            Path is active and replication can occur.

sybpr1.sybdr2.master  Latency                        Unknown

            No latency information for database 'master'.

sybpr1.sybdr2.master  Commit Time                    2014-01-29

11:41:08.460        Time last commit replicated

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

Regards

Mohammad

[Former Member]

Hi Mohammad,

The materialization of the master database appears to have been successful!  The state shows:

sybpr1.sybdr2.master  State                          Active

            Path is active and replication can occur.

So replication should not be occuring from sybpr1 to sybdr2 for database master.

So you may have an error, but it is not the same error.

It appears the TSN database materialization is not complete.

sybpr1.sybdr2.TSN     State                          Suspended

            Path is suspended. Transactions are not being replicated.

sybpr1.sybdr2.TSN     Failing Command Error Message  Failing Command

Error Message  The connection in the Replication Server on the sybdr2

host to 'TSN_sybdr2.TSN' is not configured.

Can you share information about this error (no logs are attached).

Regards,
Stephen

[Former Member]

HI Stephen,

I was able to complete replication configuration with manual materialization , however I have doubt on Failover steps and Installation guide provided by SAP doesn't cover this area and Sybase documentation as well. I can say Sybase documentation is pointing no where ......

I must admit confused which document to follow on Sybase replication

however below is out put of SAP_status path , it gives me feeling replication is working fine ,

1> sap_status path
2> go
1> sap_status path
Path                  Name          Value                    Info

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

                      Start Time    2014-02-03 11:29:45.129  Time command started executing.

                      Elapsed Time  00:00:04                Command execution time.

sybpr1                Hostname      sap-dr-pr1              Logical host name.

sybpr1                HADR Status  Primary : Active        Identify the primary and standby sites.

sybdr2                Hostname      SAP-DR-RP                Logical host name.

sybdr2                HADR Status  Standby : Inactive      Identify the primary and standby sites.

sybdr2.sybpr1.TSN    State        Suspended                Path is suspended. Transactions are not being replicated.

sybdr2.sybpr1.TSN    Latency      Unknown                  No latency information for database 'TSN'.

sybdr2.sybpr1.TSN    Commit Time  Unknown                  No last commit time for the database 'TSN'.

sybdr2.sybpr1.master  State        Suspended                Path is suspended. Transactions are not being replicated.

sybdr2.sybpr1.master  Latency      Unknown                  No latency information for database 'master'.

sybdr2.sybpr1.master  Commit Time  Unknown                  No last commit time for the database 'master'.

sybpr1.sybdr2.TSN    State        Active                  Path is active and replication can occur.

sybpr1.sybdr2.TSN    Latency      Unknown                  No latency information for database 'TSN'.

sybpr1.sybdr2.TSN    Commit Time  2014-02-03 11:29:33.220  Time last commit replicated

sybpr1.sybdr2.master  State        Active                  Path is active and replication can occur.

sybpr1.sybdr2.master  Latency      Unknown                  No latency information for database 'master'.

sybpr1.sybdr2.master  Commit Time  2014-02-02 10:54:11.034  Time last commit replicated

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

now when I wish to do switch over I have installed ASCS instance and during PAS installation it stop at start instance phase with saplikey error.... and when I had check R3trans below is output

PS C:\Users\tsnadm> R3trans.exe -x
This is E:\usr\sap\TSN\SYS\exe\uc\NTAMD64\R3trans.exe version 6.24 (release 740 - 19.03.13 - 20:13:03 ).
unicode enabled version
sizeof(Selection_t) = 272
2EETW169 no connect possible: "DBMS = SYBASE --- "
E:\usr\sap\TSN\SYS\exe\uc\NTAMD64\R3trans.exe finished (0012).
PS C:\Users\tsnadm> R3trans.exe -x
This is E:\usr\sap\TSN\SYS\exe\uc\NTAMD64\R3trans.exe version 6.24 (release 740 - 19.03.13 - 20:13:03 ).
unicode enabled version
sizeof(Selection_t) = 272
2EETW169 no connect possible: "DBMS = SYBASE --- "
E:\usr\sap\TSN\SYS\exe\uc\NTAMD64\R3trans.exe finished (0012).
PS C:\Users\tsnadm>

Attached Trans.log

further when I try to bring database TSN online  it gives error as below

2> go
1> online database TSN
Unable to obtain exclusive access to database 'TSN'.

Appreciate your kind help ...... I have raised SAP Incident as well but yet to hear from them

Regards
Mohammad

trans1.txt.zip

[Former Member]

Hi Mohammad,

This topic probably deserves a different thread, now that you have replication configured.

And sorry about the documentation confusion - we hope to improve it.

For your current issues, I am not intimately familiar with the tools you are using, but I understand the R3trans program is used for copying data between systems.  But if you have already materialized the two systems, no further copy should be required.

The error from the log file indicates the utility is attempting to connect to the standby database.  Which we would not want and do not allow by default - since all activity should be applied to the primary and replication copies it to the standby automatically.

From your log file: 

4 ETW000 [ dblink ,00000] ***LOG BY0=>[ASE Error SQL9665]Adaptive Server is running in 'Standby' mode. The user does not have 'allow hadr login' privilege.

Regards,
Stephen

[Former Member]

Hello Stephen,

Thanks.... I have open another Thread with Sybase replication Switch over method

http://scn.sap.com/thread/3495576

Regards

Mohammad

[Former Member]

Even this issue is resolved.

Regards,

Dino

[Former Member]

Hello,

Now, a new issue in the configuration.

Phase: Apply replication configuration:

Diagnose Environment  Start Time	2014-01-08 17:07:50.960
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	primary
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  <Primary Location> - Adaptive Server Enterprise - Error connecting to Adaptive Server Enterprise 'primary:4901' as 'QAS_maint'

<Primary Location> - Adaptive Server Enterprise - Error connecting to Adaptive Server Enterprise 'primary:4901' as 'QAS_maint'

ValidateLocalDREnv

Hostname

primary

(11 rows affected)

ERROR 2014-01-08 17:07:51.893

CJS-00030  Assertion failed: Verification of replication environment failed. Refer to trace file sapinst_dev.log for further information.

ERROR 2014-01-08 17:07:51.894

MUT-03025  Caught ESAPinstException in module call: .

ERROR 2014-01-08 17:07:52.121

FCO-00011  The step syb_step_prepare_rep_env with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_config|ind|ind|ind|ind|id_c_syb_rep_config|0|syb_step_prepare_rep_env was executed with status ERROR ( Last error reported by the step: Assertion failed: Verification of replication environment failed. Refer to trace file sapinst_dev.log for further information.).

INFO 2014-01-08 17:07:52.445

Creating file /tmp/sapinst_instdir/GENERIC/SYB/REPENV/SETUP/__instana_tmp.xml.

Thanks & Regards,

Dino

[former_member258142]

Dinakar,

Will you verify your ASE is running and if you can log into the ASE using the "QAS_maint" user? If you can log in, will you provide sapinst_dev.log?

Chris

[Former Member]

Hello Chris,

yes, I am now able to login with QAS_maint user.

The step completed successfully.

The issue is now in "Apply replication configuration" phase.

As suggested by you, I updated the ticket with sapinst_dev.log and also sapinst.log.

Thanks & Regards,

Din0

[Former Member]

Atlast, the current issue is resolved.......

I assigned the following authorizations to sapsso user in primary and standby:

	sa_role (default ON)
	sso_role (default ON)
	sybase_ts_role (default ON)
	sap_adm (default OFF)

Thanks & Regards,

Dino

[Former Member]

Hello,

I changed the password of SID_maint in primary and standby systems.

The issue with SID_maint seems to be resolved.

But, the issue is when sapsso user in the primary system is trying to enable encryption in the target system.

INFO 2014-01-08 15:59:10.131

Output of isql64 -e -w999 -Usapsso -Sprimary:4901 -X is written to the logfile isql64.log.

INFO 2014-01-08 15:59:10.506

Execution of the command "isql64 -e -w999 -Usapsso -Sprimary:4901 -X" finished with return code 0. Output:

Password:

1> use master

1> EXEC sp_configure 'net password encryption reqd', 1

Parameter Name                 Default     Memory Used Config Value                                                                                                                                                                                                                                                    Run Value                                                                                                                                                                                                                                                       Unit                 Type

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

net password encryption reqd             0           0            1                                                                                                                                                                                                                                                               1                                                                                                                                                                                                                                                    switch               dynamic

(1 row affected)

Resulting configuration value and memory use have not changed from previous values: new configuration value 1, previous value 1.

(return status = 0)

INFO 2014-01-08 15:59:11.467

Creating file /tmp/sapinst_instdir/GENERIC/SYB/REPENV/SETUP/isql64.log.

INFO 2014-01-08 15:59:11.512

Output of isql64 -e -w999 -Usapsso -Sstandby:4901 -X is written to the logfile isql64.log.

INFO 2014-01-08 15:59:11.735

Execution of the command "isql64 -e -w999 -Usapsso -Sstandby:4901 -X" finished with return code 0. Output:

Password:

1> use master

1> EXEC sp_configure 'net password encryption reqd', 1

Msg 10330, Level 14, State 1:

Server 'SID', Procedure 'sp_configure':

EXECUTE permission denied on object sp_configure, database master, owner dbo

(return status = -4)

ERROR 2014-01-08 15:59:11.737

CJS-00030  Assertion failed: Execution of SQL script reports an unexpected error. Refer to trace file sapinst_dev.log for further information.

ERROR 2014-01-08 15:59:11.738

MUT-03025  Caught ESAPinstException in module call: .

ERROR 2014-01-08 15:59:12.141

FCO-00011  The step syb_step_force_password_encryption with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_config|ind|ind|ind|ind|id_c_syb_rep_config|0|syb_step_force_password_encryption was executed with status ERROR ( Last error reported by the step: Assertion failed: Execution of SQL script reports an unexpected error. Refer to trace file sapinst_dev.log for further information.).

What should I do now to resolve this issue?

Thanks & Regards,

Dino

[Former Member]

Hello,

Issue is still in pending state.

But, when I further analyzed this issue, I found that, during the configuration of SRS, i.e., during "Ensure password encryption for Database logins" step, it is unable to login to the database as SID_maint user.

I tried connecting from Primary to Standby and from Standby to Primary. The connection was working fine., except for SID_maint user.

[sybsid@primary ~]$ isql64 -w999 -USID_maint -Sprimary:4901 -X

Password:

Msg 4002, Level 14, State 1:

Server 'SID':

Login failed.

CT-LIBRARY error:

    ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.

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

sybsid@standby 9> isql64 -w999 -USID_maint -Sstandby:4901 -X

Password:

Msg 4002, Level 14, State 1:

Server 'SID':

Login failed.

CT-LIBRARY error:

        ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.

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

1> use master

1> EXEC sp_configure 'net password encryption reqd', 1

Msg 10330, Level 14, State 1:

Server 'SID', Procedure 'sp_configure':

EXECUTE permission denied on object sp_configure, database master, owner dbo

(return status = -4)

isql64 -w999 -Usapsa -Sprimary:4901 -X is written to the logfile isql64.log.

Execution of the command "isql64 -w999 -USID_maint -Sstandby:4901 -X" finished with return code 255. Output:

Password:

Msg 4002, Level 14, State 1:

Server 'SID':

Login failed.

CT-LIBRARY error:

    ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.

Execution of the command "isql64 -e -w999 -Usapsso -Sstandby:4901 -X" finished with return code 0. Output:

Password:

1> use master

1> EXEC sp_configure 'net password encryption reqd', 1

Msg 10330, Level 14, State 1:

Server 'SID', Procedure 'sp_configure':

EXECUTE permission denied on object sp_configure, database master, owner dbo

(return status = -4)

ERROR 2014-01-08 13:07:46.151

CJS-00030  Assertion failed: Execution of SQL script reports an unexpected error. Refer to trace file sapinst_dev.log for further information.

ERROR 2014-01-08 13:07:46.153

MUT-03025  Caught ESAPinstException in module call: .

ERROR 2014-01-08 13:07:46.516

FCO-00011  The step syb_step_force_password_encryption with step key |SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_config|ind|ind|ind|ind|id_c_syb_rep_config|0|syb_step_force_password_encryption was executed with status ERROR ( Last error reported by the step: Assertion failed: Execution of SQL script reports an unexpected error. Refer to trace file sapinst_dev.log for further information.).

Login Password Encryption type is SHA-256 in both primary and standby for SID_maint user.

Not finding any way out.

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

Primary:

1> sp_helpuser dbo

Users_name                               ID_in_db                         Group_name                               Login_name

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

dbo                                             1                         public                                   sa

(1 row affected)

Users aliased to user.

Login_name

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

SID_maint

(return status = 0)

Standby:

1> sp_helpuser dbo

Users_name                               ID_in_db                         Group_name                               Login_name

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

dbo                                             1                         public                                   sa

(1 row affected)

Users aliased to user.

Login_name

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

SID_maint

(return status = 0)

Thanks & Regards,

Dino

[Former Member]

Hello,

I uninstalled the Replication Environment in the primary database.

When the uninstallation was in progress, I received the following error message:

The installer was unable to remove replication markers for database objects. Remove the markers after the uninstallation manually.

Confirm with OK or abort with cancel

The installaer was unable to remove replication related database users. The users are named DR_admin and QAS_maint. Drop the users after the uninstallation manually. Confirm with OK or abort with cancel.

Please help.

Thanks & Regards,

Dinakar

[Former Member]

Hello,

Can sp_encryption help me in creating the encryption?

I tried sp_encryption help, and it displayed the following error message:

There are no encryption keys (key copies) like '%' in 'master'.

(return status = 1)

Tried SAP Note. 1942379 -> No progress

Tried updating DB Client to the latest version -> No progress

What else can be tried is a big question now.

Thanks & Regards,

Dino

[Former Member]

Now, I am getting the following error message:

ERROR 2014-01-01 21:55:24.649

  CJSlibModule::writeError_impl()

MUT-03025 Caught ESAPinstException in module call: .

TRACE 2014-01-01 21:55:24.650 [JSExtension.hpp:1064]

  CallFunctionBase::call()

Member function 'Installer.invokeModuleCall() has thrown unknown

exception. Rethrowing.

TRACE 2014-01-01 21:55:24.933 [syuxctask.cpp:237]

  CChildApplicationImpl::doStart() lib=syslib module=syslib

A child process has been started. Pid = 30347

TRACE 2014-01-01 21:55:24.993 [syuxctask.cpp:600]

  CUnixProcessManager::sap_waitpid(pid_t pid, int * pStatus,

int

options)

  lib=syslib module=syslib

Child process 30347 returned 0

TRACE 2014-01-01 21:55:25.32 [syuxctask.cpp:237]

  CChildApplicationImpl::doStart() lib=syslib module=syslib

A child process has been started. Pid = 30348

TRACE 2014-01-01 21:55:25.88 [syuxctask.cpp:600]

  CUnixProcessManager::sap_waitpid(pid_t pid, int * pStatus,

int

options)

  lib=syslib module=syslib

Child process 30348 returned 0

ERROR 2014-01-01 21:55:25.103 [sixxcstepexecute.cpp:899]

FCO-00011 The step syb_step_force_password_encryption with step key

|SYB_REP_ENV|ind|ind|ind|ind|0|0|c_syb_rep_config|ind|ind|ind|ind|id_c_syb_rep_config|0|syb_step_force_password_encryption

was executed with status ERROR ( Last error reported by the step:

Assertion failed: Execution of SQL script reports an unexpected error.

Refer to trace file sapinst_dev.log for further information.).

Error occured in phase:

Ensure Password encryption for Database login.

Thanks & Regards,

Dino

[former_member258142]

Dino,

Looks like your ASE Password encryption is not enable. Please enable:

1> sp_configure 'net password encryption reqd', 1

2> go

[Former Member]

Dear Chris,

I already tried this query, but that did not help me in going any further.

1> use master

2> go

1> sp_configure 'net password encryption reqd', 1

2> go

Parameter Name                 Default     Memory Used

         Config Value                                                                                                                                                                                                                          

         Run Value                                                                                                                                                                                                                             

         Unit                 Type

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

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

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

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

net password encryption reqd             0           0

                    1                                                                                                                                                                                                                          

                    1                                                                                                                                                                                                                          

         switch               dynamic

(1 row affected)

Resulting configuration value and memory use have not changed from previous

values: new configuration value 1, previous value 1.

(return status = 0)

1>

Thanks & Regards,

Dinakar

[former_member258142]

Dinakar,

Looks like ASE Password encryption is enabled as req'd. Please contact with the support team by updating the Note. In parallel I will make sure they know your are again stuck.

chris

[Former Member]

Already updated the incident Chris.

[Former Member]

Dear Chris,

The passed smoothly after I uninstalled the failed installation and started the re-installation with the following tools:

REPSERVER1570111_0-20011160.TGZ

SWPM10SP04_3-20009701.SAR

Will Keep the post open for some more time to post any other issues that occur during the setup.

Thanks & Regards,

Dino

[former_member258142]

Dino,

I have contacted the owners of the two tickets and asked them to get back to you asap. Please add the control.xml and sapinst_dev.log to the ticket #001311307

Thanks.

Chris

[Former Member]

Thanks Chris,

Updated the info. in the ticket.

Regards,

Dino

[former_member258142]

Dino,

Please open a ticket with SAP support to address this issue. In parallel we (Replication Server Dev/QA) have begun our investigation of  it and will provide status update when possible.

Chris Huston

SAP Replication Server Dev

[Former Member]

Dear Chris,

Thanks for responding.

I already did that about a week ago.

I did not receive any response from them till now.

Thanks & Regards,

Dino

[former_member258142]

Dino,

What is the ticket #? I will follow up with the support team.

Secondly, will you provide the section of the "control.xml" same location as sapinst_dev.log that does Replication Server version check, similar to the below. I want to se the version that will be "ok":

Example from control.xml:

if (repversion >= "15.7.1.102") {

     installer.writeTrace(stepname + ": rep server version is ok");

} else {

installer.writeTrace(stepname + ": rep server version is not ok");

installer.abortInstallation("ind-rel.ind-os.ind-db.assertionFailed",

"Unable to verify the replication server version. Refer to trace file sapinst_dev.log for further
information.");

  }

}

[Former Member]

Hello,

Ticket numbers are as follows:

0001311307

0001143289

Thanks & Regards,

Dino