How to disable Transaction log on Sybase ASE

During Execution phase of an upgrade, when you ae performing archiving activities on Development or Quality system but you don't have enough space for keeping transaction data or because of some specific reason if you want to disable the trans log on your Sybase system you can follow this option.

This is not recommended on Production systems because as the transaction log is used for performing a complete restoration of data. 

1. Log in on your server with user SYBSID 

2. Launch with a command line tool to connect to ASE database

> isql -Usapsa -P< password > -S< SID > -X

3. On the SQL interface, enter the statements to change log mode

1> use master

2> go

1> sp_dboption <SID>, 'trunc',true

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.
Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take
effect.
(return status = 0)

1> checkpoint

2> go

Use below commands to change the Setting "true" to "false".

1> use master

2> go

1> sp_dboption <SID> , 'trunc',false

2> go

Database option 'trunc. log on chkpt.' turned OFF for database ''.
Running CHECKPOINT on database '' for option 'trunc. log on chkpt.' to take
effect.
(return status = 0)

1> checkpoint

2> go

Delete SAP Client from OS Level

Instead of delete SAP client from SAP application level we can do the same from OS level as well. It is bit faster than application level. This may useful at sometime.

1. Login to application server OS level with SIDADM User

2. Go to location /usr/sap/trans/bin directory

3. Create a file with  .CTL format which includes following content,

client=<Client Number>
select  

clientremove

Example :-
clientremove
client=300
select  *

File Name Format Example - Client_<SID><CLNT NO>_Delete.CLT

For our example , System ID = ECP and CLIENT = 300 , so the file should be look like ;
Client_ECP600_Delete.CLT

4. Let’s realized the operation via R3trans command

R3trans -w <Log file name> <Script name>

Example :-
R3trans -w Client_ECP600_LOG.log Client_SID600_Delete.ctl

Wait until it complete,

5. After successful completion of the execution, check the log file for more details.

Log File - Client_ECP600_LOG.log 

Login to SAP system & delete Client entries from table T000 or from SCC4 

Also Read,

How to delete client in SAP system

Creating System Track in SAP Maintenance Planner

 A system track is a logical grouping of related systems, and contains two or more systems in your landscape on the same target software level. A system track helps you to update or upgrade all the systems at once.

• To create a system track in MP , two or more SAP systems, such as Dev, QA, and Production required.

You can put two or more systems in a track in the following scenarios:

• They have the same product versions. For example, three SAP ERP systems or four SAP HCM systems.

• They have different SP levels, but should be on the same level.

  You can put systems with the same start level in a track with the same target level.

  You can put systems with different start levels in a track with the same target level.

Here 3 System we are using to create track.

Development - ES1

Quality - ES2

Production - ES3

1. Go to https://apps.support.sap.com/sap/support/mp

Click on 'Explore System'

2. Select the Development System,

 

3. Check all the status showing Green, then click on the SID on the Center

4. Select 'Tracks' option on the left side,

5. If 'No System tack found' message appear below, it means currently the system is not included in any tracks.

Then click on 'Create Track' option on the right side,

6. You can set any name to the track, which help to identify the track easily,

Then click on the + sign on the System Displayed

7.  Source system will be the system which you selected to create track.

You can set the System Role also,

Then Click on the Target system.

Drop down the list, Select the Quality system which you want to add on the track

Select System Role as Quality (We are using 3 system so Quality selected, if you have some other landscape select appropriate Role)

Then click  'OK'

8. Then click on the + sign on the 2nd system which we have added in above step,

Follow the Step 7 and add the next system & role to the track. 

If you have more number of system on you landscape follow the same step to add them into track.

8. Once it is completed click on 'Save' option on the right side,

9.To visible the track to all users, Verify the Track using 'Verify' Option 

10. Check the systems included in track & Click on 'Next'

11. Click on 'Next'

12. Click on 'Activate' 

Confirm the activation by clicking 'Yes'

13. Track has activated, its visible in MP now

Go to MP Home, Click on 'Explore System Tracks' option,

Check the track & status here. Also you can delete the track.

Related Post - Maintenance Planner in SAP

Thanks for reading, Please share your valuable feedback.  

Maintenance Planner in SAP

Ø What is Maintenance Planner

Maintenance planner is a solution hosted by SAP that helps you plan and maintain systems in your landscape. You can plan complex activities like installing a new system or updating existing systems. All changes can be scheduled to be deployed at a convenient time, to minimize downtime. 

Maintenance planner is the successor of Maintenance Optimizer, Landscape Planner and Product System Editor. It simplifies the maintenance process by consolidating critical tasks such as definition of product maintenance dependencies, implementing changes by generating stack configuration, downloading archives, and so on, in one tool.

With maintenance planner, you can plan system installation, update, upgrade or system conversion. You can analyze the impact of dependent systems or create dependencies in the form of system tracks. Additionally, you may also use the maintenance planner for creating an integration plan for cloud or hybrid landscapes, which can then be executed by Cloud Integration Automation Service. 

Ø Pre-requisites to access Maintenance Planner 

1. You have Google Chrome, Mozilla Firefox, or Microsoft Edge browser in your system. 

2. Your SAP Solution Manager system has release 7.1 SP05 or above

3. Ensure that you have an S-user for the SAP Support Portal.

4. Your user in SAP Solution Manager must be assigned to your s-user for the SAP Service Marketplace

Ø Architecture of Maintenance Planner

1. For SAP System Data is sent to the System Landscape Directory (SLD). 

2. Data from SLD is synchronized with the Landscape Management Database (LMDB). 

3. Data from LMDB is uploaded to SAP Support Portal.

4. The SID of the uploading SAP Solution Manager is stored with the data.

Ø How to access Maintenance Planner

1. Go to https://apps.support.sap.com/sap/support/mp or go to ONE Support Launchpad, choose the Maintenance Planner tile under the On Premise section. 

2. Log in with your SAP credentials (S user) 

3. One customer number can be assigned to multiple S-users. Use the S-user with the same customer number on SAP Solution Manager and SAP Service Marketplace.

Ø Some major Limitations of Maintenance Planner

1. Maintenance Planner currently only supports English as a language.

2. The undeployment of Java product Instance Adobe Document Services is not supported as of now

3. In some situations, the result of auto-correction measures are incorrect

4. The product maintenance dependencies created in Maintenance Planner are currently overwritten by the product system definition uploaded from LMDB.

5.For distributed JAVA environment, only the database host is displayed in Explore Systems view, in column HOST, which should show up the central instance host.

6. The technical systems which are ramp down or deleted from LMDB need to be deleted manually in Maintenance Planner. Currently, there is no automatic synchronizations between LMDB and MP for removing deleted systems.

7. Limitation in recognizing systems with unassigned product instances

8. Limitation in using tracks, and copy stack XML for SAP S/4HANA conversion/upgrade planning

9. Limitation in using screen reader for Maintenance Planner user interface

Thanks for reading, Please share your valuable feedback.  

SLT (SAP Landscape Transformation Replication Server) in SAP

This blog will give you step by step procedure for Trigger-Based Data Replication from ECC/S4Hana to HANA system using SAP Landscape Transformation (SLT) also called Real time data Replication.

What is SLT ?

SLT allows you to load and replicate data in real-time or schedule data from the source system into SAP HANA Database.
The source system maybe ECC, S4H & Non SAP as well.

SAP SLT Architecture between SAP System and SAP HANA (Showing 3 System Connetion)

As showing like the above image the landscape contain 3 Systems

Source System :- The above picture will give an overview idea about the SLT Architecture.

Here the source system showing SAP with Hana DB but we can use any other DB & Non-sap system as well.

SLT :- The system 7.5 With DIMS (SLT Component Name - DMIS)

DMIS Version should be same in SLT & Target systems.

We can use SLT System as NW version 7.4 SP 08 onward.

All the SLT Connection configuration we are going to do in this system. 

Target System :- This system should be in Hana DB. Here HANA 2.0 SP 03 Version is using.

Below are the Installed Software products in SLT System

To Upgrade the system with SLT Component (DMIS) we need to Generate the Stack file from Maintenance Planner & Upgrade the system using SUM Tool.

DMIS Version should be same in all the 3 systems, from S/4HANA 1610 System onward's the DIMS component is integrated with S4Core Layer. So need to upgrade the Source & Target system if it required.

DIMS Comparability in S/4HANA - https://launchpad.support.sap.com/#/notes/2572945

To configure SLT, Login to the SLT system and execute the Tcode LTR / LTRC

The below screen showing the LTRC Screen. We can Create, Edit, Monitor the SLT Configuration here,

Click on 'Create' option (Red Marked Option)

Give the Configuration Name & Description,

While Creating a SLT Configuration to replicate the tables system will create one Schema on the target DB.

The configuration name should be the Schema name,

From SLT system to the source system we need to create a RFC to catch the data. If it is SAP System we can create abap connection & if it is non sap other connection type.

This step we need to select the RFC name to the source system

Also if you are planning to take the data from p particular client  select the 'Read from Single Client' option otherwise deselect it,

 Here Select the Target DB Name First,

Then Give the Target System User Name, Password & Port Number

If the HANA DB server is multi-tenant, then we should carefully give tenant DB Port Number

(This step onward i'm attaching LTR screen. LTR & LTRC Configuration screen are same, one is browser based & the other is GUI)

Set the number of jobs & select the Replication option as 'Real Time',

Review all the given data here, if any changes revert it.

Once the Configuration Completed. Again LTRC T-code and Click your configuration Name,

Click on 'Data Provisioning' on the opened screen,

You will get the below Screen,

Select Start Replication option & Enter the Table names that you want to replicate.

The data replication may take some time, all the status of the data replication you can see under
LTRC ---> Configuration Name Screen

You can see the over all status at the top & Table status at 'Current Action' Column

If you are only using Source & Target system then SLT System is not required.

Thanks for reading, Please share your valuable feedback.  

FAIL: process hdbxscontroller HDB XS Controller not running

HANA DB startup failed & shows below error.

FAIL: process hdbxscontroller HDB XS Controller not running

While checking the xscontroller.out for greater detail shows the following:

com.sap.hana.mdc.MdcException: Failed to start mdc process group: Cannot run /usr/sap/<SID>/HDB00/exe/mdc/hdbmdcdispatcher - execve failed (EACCES - Permission denied)

Solution :-

Basically this problem related to  hdbmdcdispatcher permission, you can follow the below points to resolve this issue.

1. Check the permissions the user (typically <sid>adm) has on this folder: /usr/sap/<SID>/HDB00/exe/mdc/hdbmdcdispatcher

2. Correct as needed for read, write, execute permissions.

Thanks for reading, Please share your valuable feedback.