SAP BW on HANA is nothing but SAP’s existing NetWeaver BW data warehouse, running on SAP HANA. SAP now supports SAP HANA as the underlying database for the NetWeaver BW Data Warehouse. Because SAP HANA is much faster than regular relational databases like Oracle or Microsoft SQL Server, the data warehouse performs much faster. The purpose of SAP BW on HANA is to combine the power of both
2. What are the benefits of Sap BW on HANA?
Customer value of SAP BW on HANA:
Excellent query performance for improved decision making
Performance boost for Data Load processes for decreased data latency
Accelerated In-Memory planning capabilities for faster planning scenarios
Flexible – combine EDW with HANA-native data for real-time insights and decision making
Data persistency layers are cut off and reduced administration efforts
Simplified data modeling and remodeling
· Faster decision-making – Having the right information when you need it In today’s business world, fast access and manipulation is required on top of massive data stores. This is beyond the capabilities of traditional disk-based systems. Lower Total Cost of Ownership (TCO):· When you take into account the cost of hardware, software licenses, maintenance, performance tuning and project development, SAP BW is always cheaper in terms of TCO when running on HANA. Simplified configuration and operational management: · Non-disruptive innovation and advanced administrative tools. · The current business processes inside BW can stay as they are and will mesh perfectly with HANA. System operation stays as it is, and process chains do not need to be remodeled.
3. What is native hana modeling in sap BW on HANA?
HANA Modeling is done on the top of tables available in Catalog tab under Schema in HANA Studio and all views are saved under the Content table under Package.You can create a new Package under the Content tab in HANA Studio using right-click on Content and New. All Modeling Views created inside one package comes under the same package in HANA Studio and is categorized according to the View Type.
4. What are the transaction codes used in SAP BW on HANA?
Following are the key transaction codes to be used in BW on HANA system.· RSA1 − To open BW workbench· RSMIGRHANADB − To convert in-memory optimized BW· SM59 − To configure RFC connection for SLT· Ltr − To configure Trusted RFC· RSPCM − To monitor periodic process chains· RSPC − To view the log for runs of a process chain· RSLIMO − BW Lean Modeler Test UI
5. What is migration to SAP BW on HANA?
The migration to SAP BW on HANA is quite simple and requires no additional modeling or adaptation of existing information assets. BW is the first SAP application to be re-architected and rewritten to take full advantage of the enhanced capabilities of HANA. Processing that would traditionally be done at the application (ABAP) layer is pushed down into the database where it can be optimally executed with the various calculation and aggregation engines.
6. What do we need to do after migration to SAP HANA?
Remove SAP BW aggregates (they’re only overheads in SAP HANA and this is done automatically for you). Convert your SAP BW cubes and DSOs to SAP HANA cubes and DSOs (a simple process that improves performance and reduces space).
7. Do we need to rewrite all the code and stuff after SAP BW migration to HANA?
Absolutely not! All your models will run just like they did before. There are definitely instances where you may choose to optimize your models to run better on SAP HANA but this is not a requirement.
8. What are the migration tools in sap BW on HANA?
Software Provisioning Manager:
Software Provisioning Manager allows you to perform various provision tasks and covers a broad range of platforms with different productions. Software Provisioning Manager can be used to set up a standalone engine, for migration of systems, or to copy a NetWeaver system.
SAP BW Migration Cockpit for SAP HANA:
This tool is used to get an easy access to the most used and useful tools for migrating your SAP BW systems to and optimizing it for SAP HANA.The SAP BW Migration Cockpit for SAP HANA combines several tools to make the migration of an existing SAP BW deployment to the SAP HANA platform smooth and easy to perform.
9. What is infocube in sap BW on HANA?
A Basic InfoCube is a type of InfoCube that physically stores data. It is filled with data using BW Staging. Afterwards, it can be used as an InfoProvider in BEx Reporting. Infocubes are the central objects on which reports and analysis are based in SAP BW. … They are stored in master data tables.
10. What is infoprovider in sap BW on HANA?
InfoProviders are BW objects that data is loaded into or which display views of data. You analyze this data in BEx queries. There are InfoProvider types in which the data is stored physically and InfoProvider types that are only views on the data. In BEx Query Designer, they are seen as uniform objects however.
11. What is SAP HANA Modeler option?
SAP HANA Modeler is used to create information views on the top of schemas → tables in HANA database. These views are consumed by JAVA/HTML based applications or SAP Applications such as SAP Lumira, Office Analysis, or third party software like MS Excel for reporting purposes to meet business logic and to perform analysis and extract information.
12. What are the components needed to install BW modeling tools?
Install BW modeling tools, you need the following components −· Operating System Windows 7 or Windows 8 or Apple Mac OS X 10.8 or higher, or Linux distribution.· Internet Explorer 7.0 or higher or Firefox 4.0 or higher has to be installed.· SAP GUI for Windows 7.3 or SAP GUI for Windows 7.4 has to be installed on your local drive. You can download this from SAP Marketplace.· To communicate with the backend system, you need Microsoft Runtime DLLs VS2010 (for Windows OS) is installed on your local system.· SAP HANA Studio (32-Bit or 64-Bit for Windows) SP08 or higher.
13. What is hana optimized infocubes in sap BW on HANA?
When you use SAP BW on HANA, you can create your existing InfoCubes to HANA Optimized InfoCubes. When InfoCubes are moved to HANA database, they become column-based tables and act like BWA Indexed InfoCubes.When SAP HANA optimized InfoCubes are used, characteristics and key figures are assigned to dimensions. To improve the system performance, Surrogate IDs (SIDs) are used in fact tables.When you convert standard InfoCubes to HANA optimized InfoCubes, the layout changes at the time of conversion and it has to be adjusted manually.To view InfoCubes in the BW system, you can use Transaction: LISTSCHEMA
14. What is composite provider in sap BW on HANA?
Composite Providers are used to combine multiple InfoProviders using Join or Union operations. When you use SAP BW on HANA, one of the InfoProvider should use in-memory database and the data in composite providers can be used for reporting and analysis.When you use SAP BW with non-HANA database, then BWA is a prerequisite to create Composite Providers. The primary advantage of Composite Providers is that you can create new complex business scenarios by combining InfoProviders using Join operation.You can create Composite Providers in Administration workbench using Transaction: RSLIMOBW
15. What are the object and package privileges to access SAP HANA views that are generated from SAP BW?·
Object privilege − SELECT on _SYS_BI· Object privilege − EXECUTE on REPOSITORY_REST(SYS)· Package privilege − REPO.READ on the content package where generated SAP HANA views are stored.
16. What is the DIM ID?
DIM ID: are used to connect fact tables and dimension tables
17. What is an info source?
A structure consisting of InfoObjects without persistence for connecting two transformations
18. What is an info object?
InfoObjects are known as the smallest unit in SAP BI and are used in InfoProviders, DSOs, Multi providers, etc. Each InfoProvider contains multiple InfoObjects.InfoObjects are used in reports to analyze the data stored and to provide information to decision makers. InfoObjects can be categorized into the following categories −· Characteristics like customer, product, etc.· Units like quantity sold, currency, etc.· Key figures like total revenue, profit, etc.· Time characteristics like year, quarter, etc.
19. What is info area?
Info Area in SAP BI is used to group similar types of objects together. InfoArea is used to manage InfoCubes and InfoObjects. Each InfoObject resides in an InfoArea and you can define it in a folder which is used to hold similar files together.
20. What is advanced DSOs in sap BW on HANA?
Using HANA optimized objects, you can achieve better performance for analytical reporting and data analysis. DSOs of SAP BW are automatically optimized for activation in SAP HANA database. When you migrate SAP BW on HANA, all standard DSOs are moved to SAP HANA database in a column storage.To use advanced DSOs, you should have SAP HANA database support pack 08 or higher version and in the backend you should have SAP BW 7.4 SPS9.
21. What is the time distribution option in update rule?
This is to distribute data according to time; for example if the source contains calendar week and the target contains calendar day, the data is spit for each calendar day. Here you can select either the normal calendar or the factory calendar.
22. Can you partition a cube which has data already?
No; the cube must be empty to do this; one work around is to make a copy of the cube A to cube B; export data from A to B using export data source; empty cube A; create partition on A; re-import data from B; delete cube B
Here i am explaining about SAP Printers Configuration and what are the transaction codes we have in SAP.
SP01 – Output Controller Basis – Print and Output Management
SPAD – Spool Administration Basis – Print and Output Management
OMJ4 – printer Determ: Plant/SLoc./User Grp MM – Inventory Management
OMMC – printer Assignment per WM Mov.Type Logistics Execution – Other Functions
OMNT – printer Pool for SU Management Logistics Execution – Other Functions
TBZ13 – printer Override Function Financials – Transaction Manager
Create Printer Enter the T Code -SPAD.
In Spool Administration screen, click on Display against Output devices. This will list out all output devices configured in SAP system.
Click on Create button to add new printer.
In Device Attribute Screen below, put name of Output device, Device type, Device Class, Model and Location of Printer.
In Access method screen, select Host Spool Access Method and Host Printer.
In Host Printer you can attach default printer of the machine where user has logged in, by writing “__DEFAULT”.
Check or uncheck “No Device Selection at Frontend” as per requirement.
Click on save button to save settings.
If you have not selected short name in device attribute screen then system will show below message. Click yes to go ahead.
System will show below Message.
In Spool Administration screen, click on Display against Output devices. This will list out all output devices configured in SAP system Select the printer you want to delete and click on delete button.
Delete Old Spool Log
Enter the T Code -SPAD.
In Spool Administration screen, go to admin tab.
Click on Delete Old Spool requests.
Check “Old Spool requests older than the maximum set age”. Enter the minimum age. And press Enter. It will delete the old spool requests.
Objective : We want to know the owner of HANA schema. If you need access to user defined schema then you need to ask the SCHEMA owner to grant you authorization.
Prerequisite: You need read access to “SYS” schema. .
Steps :How to check SAP HANA Schema Owner.
In HANA Studio open the SQL console and enter following query.
SELECT * FROM “SYS”.”SCHEMAS”;
This output has following three columns : SCHEMA_NAME : Name of the Schema. SCHEMA_OWNER : User ID of the Schema Owner. HAS_PRIVILEGES : Shows if user is schema owner or has any privilege for the schema or any object within the schema: ‘TRUE’, ‘FALSE’. It will show TRUE for the user(who is executing this SQL) has privilege for that Schema.
In our example the user has privilege for following schema(s).
Here i am explaining about SAP HANA DB Locks. What are the types of SAP HANA DB Locks and how we can resolve if we get any issues
1. Present lock situations
Check the Alerts Monitor in HANA Studio for alerts indicating lock situations, which may serve as a starting point for the following investigations: Check for blocked transactions (“Performance -> Load”, “Performance -> Blocked Transactions”, “Performance -> Threads”) to determine the number of blocked transactions. When transactions are blocked, identify the session that blocks other transactions from (“Performance -> Sessions”)or (“Performance -> Blocked Transactions”).
To resolve the blocking situation, the following actions can be taken.
1. Check the application logic of the currently blocking session to see if the application logic can be changed to avoid the blocking situation.
2. Consider changing the schedule or parameterization of the application modifying those database objects and thereby blocking those transactions.
3. You can terminate the blocking session manually if you need to resolve the situation immediately.
4. When further analysis is needed to find out the root cause of the blocking transaction, follow the instructions in later part of this SAP Note and collect diagnosis information and send the information to SAP Support.
The following “System Information” views provide additional information on blocked transactions, locks and sessions: “Open Transactions”, “Blocked Transactions”, “Table locks”, “Record Locks”, “Sessions”. A possible root cause for a temporary increase of internal locks are contentions on system resources. background processes. A possible root cause for a temporary increase of internal locks are contentions on those system resources. To determine temporal coincidences of deteriorated performance with increasing lock contention caused by background jobs, use the HANA Studio monitors “Performance -> Load”, and “Performance -> Job Progress” and the “System Information” views to check the status of “(Delta) Merge Statistics”, “Failed Backups”, “Backup catalog” “MVCC blocker transaction”, “MVCC blocker connection”.
To find the times when savepoints have been written, submit a query on the system view “SYS”.”M_SAVEPOINTS”. The view SYS”.”M_CS_UNLOADS” logs phases of intensive column data unloads from memory.
To find wait situations at a thread level, open the HANA Studio monitor “Performance -> Threads”, select “Create call stacks”, and repeatedly refresh the current page every few minutes. Check which threads do not change their call stacks even after many repetitions. Unchanged call stacks can have many other root causes than lock contention, e.g., long running queries, open sessions waiting for a user action, or background processes. To find out the root cause of a long running query, the following checks can be performed.
Number of row store version is over 1,000,000: 1. Check number of row store versions using the following query:
select * from m_mvcc_tables
If the number of versions is over 1 million, it might affect overall system performance. Therefore, we need to find out which transaction blocks garbage collection, possibly by long-running or unclosed cursors, long-running serializable/repeatable read isolation mode transactions, or hanging threads.
2. From “System Information” views, identify the transaction and connection information that is blocking the garbage collection by checking “MVCC blocker transaction” and “MVCC blocker connection”.
3. Identify Query String of the problemaic cusror or query using the following query:
select * from m_prepared_statements where statement_id = (select current_statement_id from m_connections where connection_id = (select connection_id from m_transactions where min_mvcc_snapshot_timestamp = (select min(Value) from m_mvcc_tables where name = ‘MIN_SNAPSHOT_TS’) and connection_id > 0))
4. Get more information on the session context:
select * from m_session_context where connection_id = (select connection_id from m_transactions where min_mvcc_snapshot_timestamp = (select min(Value) from m_mvcc_tables where name = ‘MIN_SNAPSHOT_TS’) and connection_id > 0)
You can get more detailed information on the session such as application program, application user from this query.
5. Analyze the query why it takes long
Check application and solve the problem. For example, application program has to be changed if there is any unclosed cursor or uncommitted transaction.
6. If a persistent sequence is used with “NO CACHE” option, then please check SAP Note 1977214 SAP HANA: Growing number of rowstore table versions when a persistent sequence is used.
7. If the problem is not resolved, then follow the instructions in later part of this SAP Note and collect diagnosis information and send the information to SAP Support.
Number of row store version is less than 1000000, but still a performance is not good and need further investigation, then follow the instructions in later part of this SAP Note and collect diagnosis information and send the information to SAP Support. When further analysis is needed to find out the root cause of the wait situation at a thread level, follow the instructions in later part of this SAP Note and collect diagnosis information and send the information to SAP Support. 2. Past lock situations Identify the exact time frame when the performance temporarily decreased. For example, by using the “Performance -> Load” monitor, status of resource consumption such as CPU or memory usage or SQL workloads such as number of active connections, statements, blocked transactions, versions, active read / write requests, column unload status can be checked. HANA trace files also can be used to identify the time frame of problematic situation by checking alerts or warning / error messages. The time frame is a valuable filter for further analysis.
When HANA database is not restarted after the performance downgrade, the “System Information” views can be checked further. If the performance issue is resolved without a database restart, then it indicates that the database was not in a hang situation, but the database performance was temporarily decreased.
If HANA database has been restarted after a hang situation, the history of database status can be found in “_SYS_STATISTICS” schema:
To check if a savepoint was written during a pre-defined time period, submit a query on the view “SYS”.”M_SAVEPOINTS” and specify a suitable time window for the corresponding attribute(s). A longer history can be found in “_SYS_STATISTICS”.”HOST_SAVEPOINTS”. Similarly, the view “SYS”.”M_CS_UNLOADS” saves time information when column data is unloaded from memory. To search for lock messages in trace files, open the HANA DB Studio “Diagnosis Files” view and primarily examine the indexserver alert trace files. In a scale-out environment, there is one such file for each host. Search for the strings “lock”, “wait”, and “transaction”. Check if the messages refer to lock situations and the timestamps match the period of performance deterioration. 3. Collect Diagnosis Information for SAP Support To collect Diagnosis Information (“runtimedump”) including configurations and trace files, follow the SAP Notes 1837439 “Activating the Emergency Support Package for DB support” and 1732157 “SAP HANA: Howto get system dump”. Send the system dump archive to SAP Customer Support who will provide you an SAPMATS container link for the upload. Small dump archives can be directly attached to OSS messages.
This collection of Diagnosis information is helpful for both present and past lock situations.
If the HANA DB System currently shows a serious hang situation, repeat the collection of Diagnosis files again after a few minutes and additionally send the second dump archive to SAP Customer Support.
2. SAP HANA locking issues?
You suffer from terminations and short dumps due to SQL errors 131 or 133:
SQL error 131: transaction rolled back by lock wait timeout SQL error 133: transaction rolled back by detected deadlock SQL error 146: resource busy and NOWAIT specified The mvcc_anti_ager reports in a trace file:
There are too many lock items on this system.
3. Types of locks exist?
We can distinguish the following SAP HANA lock types:
wait thread state
Exclusive locks on record level, typically
caused by concurrent changes of the same records by different transactions
Shared locks (INTENTIONAL EXCLUSIVE): Set in case of DELETE, INSERT, MERGE, SELECT FOR UPDATE, UPDATE and UPSERT operations on table
Exclusive locks (EXCLUSIVE): Set in case of DDL operations on table and in case of an explicit LOCK TABLE operation
Read / write lock
Read / write lock waits, e.g. waits during
critical savepoint phase
Low level locks based on semaphores, e.g.
waits for a critical delta merge phase
Low level locks based on mutexes
Low level locks similar to mutexes
Speculative Lock Retry backoff
Low level transactional memory locks (SAP
HANA >= Rev. 122)
Speculative Lock Wait for fallback
Locks related to integrated liveCache (if
The nameserver topology is locked based on
a file (/tmp/.hdb_<sid>_<inst_id>_lock)
Record and object locks are mainly linked to the application transactions while read / write locks, semaphores, mutexes and barriers are managed by SAP HANA internally.
Be aware that the table above concludes from a lock type to a thread state. The opposite way is not generally valid. For example, there can be “ConditionalVariable Wait” situation that are not linked to a record lock or object lock
4. To check if my SAP HANA database suffers from lock waits?
On a very elementary level you can identify lock waits based on the thread states.
Current threads can be displayed via:
Transaction DBACOCKPIT: Performance –> Threads SAP HANA Studio: Performance –> Threads SQL: “ HANA _Threads_CurrentThreads” (SAP Note 1969700) Historic thread activities can be determined via:
SQL: “HANA_Threads_ThreadSamples_FilterAndAggregation” and “HANA_Threads_ThreadSamples_AggregationPerTimeSlice” (SAP Note 1969700) The following thread states indicate lock wait situations:
Barrier Wait ConditionalVariable Wait ExclusiveLock Enter Mutex Wait Semaphore Wait SharedLock Enter Sleeping
Not every occurrence of these states is critical. It happens frequently that a thread submits a request to another thread and waits for a related semaphore until the called thread has returned the result.
5. Do timeouts for lock waits exist?
Transactional lock waits are terminated when the time limit defined with the following parameter is exceeded:
indexserver.ini -> [transaction] -> lock_wait_timeout Its default value 1800000 which represents 1800000 ms / 1800 s / 30 minutes. This means that a lock wait is terminated after 30 minutes and the following error message is issued:
SQL error 131: transaction rolled back by lock wait timeout This behavior is different from other databases like Oracle where no timeout for exclusive lock waits exist and transactions will wait for the lock until the lock is available or the transaction is manually terminated.
For internal lock waits no timeout is implemented.
6. How long certain types of locks are held?
Normally it is most important to analyze lock wait situations, i.e. the concurrent access to the same resources. For transactional locks you can additionally see how long locks are held (even if no transaction is waiting) by using the following approaches:
In one of the previous blogs we explained how you can perform analysis on your system as preparation for the S4HANA upgrade. This blog will explain how to run detailed analysis on your custom code as preparation for S4HANA upgrade. Pre-condition is that you have installed 7.52 netweaver system and done the configuration for remote ATC as described in this blog.
Questions that will be answered in this blog are:
What do I need to do in order to set up the remote S4HANA readiness check in ATC?
How to run the remote S4HANA readiness check?
How to handle the results of the remote S4HANA readiness check?
How to set up remote ATC for S4HANA readiness check?
To run the remote ATC for S4HANA readiness check you must install a netweaver 7.52 system and configure the remote ATC. Instructions can be found in this blog.
In the SAP code inspector (for details see this blog) you can now find the S4HANA readiness variants:
How to run the S4HANA readiness in ATC?
To run the S4HANA readiness variant create in the ATC tool (for all details see this blog) a special S4HANA readiness run series:
In this run it is important to put your analysis system object provider into the variant!
Now start the ATC run and be patient. The run might take a few hours pending on your system size and Z code base sizing.
You can monitor the progress in the ATC run monitor:
You can also see here if any tool issues were reported. If tool issues are present, click on the underlined number and see if you can solve them. Most issues are SAP bugs and you need to apply an OSS note. Before creating new message for SAP make sure you have applied all recent notes for the S4HANA readiness check (2436688 – Recommended SAP Notes for using S/4HANA custom code checks in ATC) and all the remote ATC notes as explained in the remote ATC blog.
How to handle the results?
If the ATC run is finished you can look at the results in the central system:
The results consist of a code point where a potential issue is. If you click on the code point you jump to the analyzed systems code.
There is also a note number which explains what you need to check.
Now basically 3 things can happen:
You can fix the issue directly: nice, the next run the issue is gone.
You read from the OSS note the function has changed or is no longer present in S4HANA. Read the OSS note for alternatives or check with your functional consultant on functional alternatives. Example of change is the way output and pricing is done. You know now it will be changed, but you cannot prepare in the current system. Use the list as input for project management for work estimation.
You read from the OSS note the potential issue and conclude it is not relevant for your situation. Example is material number length handling. If you use material numbers properly this is not relevant for you, but the tool will generate massive amounts of alerts. But maybe in some cases you need to intervene.
To distribute the results, apply OSS note 2499684. This enables you to download the ATC results into xls spread sheet. From here it is easier to follow up if action is needed for long list (like material number length) or not.
If you have done your first round of check, you want to rerun. But some notes you might have detected as not relevant and you want to exclude them.
To do this copy the SCI S4HANAREADINESS variant to your own variant. Then change the SCI variant to exclude the OSS notes you don’t want to see any more:
Now rerun the ATC with the new variant. The list you get will be smaller. Repeat this iterations as long as needed.
Don't change the originally SAP delivered SCI variants. New features and bug fixes by SAP will update this variant. If you have an updated SAP variant, simply copy it again to your Z variant and redo the exclusion of OSS notes.
S4HANA 1809 update
If you previously installed remote ATC for a 1709 check and want to run now for S4HANA 1809 there are a few update steps to follow.
Activating the Emergency User in SAP Java only system Why SAP* user activation required
Sometime we end up in a situation when none of the user are able to log in into SAP or even Administrator user is locked or not working. In this scenario you have to activate the emergency user SAP* .
Please note : This method is only for Java Only system , for dual stack systems you can activate SAP* or lock unlock user via SU01. (Will provide a link shortly to unlock SAP* in ABAP stack).
Once SAP* is activated all other users will be deactivated until SAP* is disabled again. How to activate SAP* 1.Launch Configtool – Go to to /usr/sap/<SID>/JC*/j2ee/configtool/ and execute configtool.sh (On UNIX like environment , please setup DISPLAY as per X11 /Reflection application).2.Go to Global Server Config > Services > com.sap.security.core.ume.services node.3. Change the following UME parameters.
4.Select the property and enter the Value as shown in step 3 and save it by pressing “Set” button.
5.SAP* will get activated after Java restart.
6.Now you can log in with SAP* and unlock Administrator or any other desired user.
Before starting the Conversion Process, BASIS consultant has to find out if the system can be converted to S4 HANA. There are dependencies which might make the current system incompatible to S4 HANA and stop the conversion. For example, the client might be using some add-on products which are not yet supported in S4 HANA system. Maybe the current system cannot be directly upgraded to S4 HANA, and you might need to upgrade the current system to a minimum support package before you can actually start the conversion. For your information, the system needs to be a Unicode system as a Prerequisite for conversion to S/4 HANA. Once the Basis consultant declares that the system can be converted and give their green signal, the actual process of conversion can be commenced.
The entire task of the Conversion to S/4 HANA can be broadly categorized into three segments.
1. Pre-Conversion Activities
The basis consultant should create a Sandbox System where we should perform the dry run. The Sandbox should be the copy of Production System where “Realistic” tests can be executed.
Basis consultant needs to apply necessary notes to enable the functional consultants do the consistency check.
Functional consultants do the consistency check and rectify all the errors found.
ABAPers change the custom code and make it compatible to HANA system.
2. System Conversion
Once all the errors are rectified and custom codes are changed, then starts the actual process of the system conversion. Basis consultants start the conversion with the help of SAP Provided tool SUM ( Software Update Manager ) with DMO (Database Migration Operation)
This tool will help the Basis consultant to convert the ECC system to HANA system and migrate the data from the legacy database to Hana Database.
3. Post-Conversion Activities
Once the Conversion is done, functional consultants have to check the impact of the conversion and they might need to perform some additional activities.
We would need one user with the Administrator access for stopping and starting the HANA database. Normally it will be <SID>ADM. (here SID is the HANA Database Instance Name).
Below steps would guide you to stop/start the HANA database from the operating system level using the <sid>adm user.
Login to the server where the HANA database is running with <sid>adm user using any of the SSH client.
Go to the path /usr/sap/<SID>/<Instance_Number> and execute the command HDB info ( This command will show the list of services that are currently running).
3. Execute the command HDB stop to stop all the HANA service all at once, which means the entire database will be stopped.
4. Check the process running with HDB info. It will show only sapstartsrv process, which will not stop automatically. If required, you can kill it and while starting the database, it will start automatically.
5. Start the database services using the command HDB start
6. Check the process using the HDB start and verify all the process are running or not.
This is all I wanted to share in my first post at SAPYard. I know, this genre of post is not something SAPYard’s patrons see that often. SAP Basis/Security and Admins would appreciate this article more. But others can also have a look and feel of what work the SAP HANA Admins do. That way you have a sneak peek to HANA Admin’s responsibilities.
If you like this, I would like to share more articles on HANA which would help the HANA Database Admins and also educate other consultants who are always curious to learn new things and always open to gain knowledge.