Skip to main content
IPFS powers the Distributed Web A peer-to-peer hypermedia protocol designed to preserve and grow humanity's knowledge by making the web upgradeable, resilient, and more open. The web of tomorrow needs IPFS today IPFS aims to surpass HTTP in order to build a better web for all of us. Today's web is inefficient and expensive HTTP downloads files from one server at a time — but peer-to-peer IPFS retrieves pieces from multiple nodes at once, enabling substantial bandwidth savings. With  up to 60% savings for video,  IPFS makes it possible to efficiently distribute high volumes of data without duplication. Today's web can't preserve humanity's history The average lifespan of a web page is 100 days  before it's gone forever. The medium of our era shouldn't be this fragile. IPFS makes it simple to set up resilient networks for mirroring data, and thanks to content addressing, files stored using IPFS are automatically versioned. Today's web is centralized, limit

Starting and Stopping MAXDB

 /maxdb/programs/bin





Procedure

Starting the Database (Transfer to the ONLINE Operational State)

Call Database Manager CLI, log on as operator DBM with password DBM, connect to the database DEMODB, and transfer the database to the ONLINE operational state:


[root@<Server> bin]# ./dbmcli -u superdba,Password -d SDB db_online

OK

[root@<Server> bin]#


Stopping the Database (Transfer to the OFFLINE Operational State)

Call Database Manager CLI, log on as operator DBM with password DBM, connect to the database DEMODB, and transfer the database to the OFFLINE operational state:


./dbmcli -u superdba,Password -d SDB  db_offline


OK


Displaying the Current Operational State of the Database

Call Database Manager CLI, log on as operator DBM with password DBM, connect to the database DEMODB, and display the operational state of the database:


./dbmcli -u superdba,Password -d SDB  db_state

OK

State

ONLINE

[root@<Server> bin]#



OK


OFFLINE




Comments

Popular posts from this blog

Update Apache Tomcat from 9.0.26 to 9.0.43

  Download Latest Available Version of Tomcat apache-tomcat-9.0.43.tar.gz copy in /sap/upgrades/ extract : tar zxvf apache-tomcat-9.0.43.tar.gz   Stop Data Services Take Backup of /usr/sap/IPS folder in /sap/upgrades or only Tomcat folder under /use/sap/IPS/sap_bobj/   go back to  /sap/upgrades/ mv apache-tomcat-9.0.43 tomcat cp -rp * /usr/sap/IPS/sap_bobj/tomcat/   Start Data Services

SUM Email Notification Configuration

edit MailNotifierApp.props this file under SUM folder /usr/sap/<sid>/SUM/abap/mailNotifier sum.host    = servername sum.port    = 1128 sum.user    = <SID>adm sum.pwd     = PASSWORD sum.sid     = <SID> sum.type    = sumabap sum.ssl     = false mail.host  = MAIL SERVERNAME mail.port  = 25 mail.user  = mail.pwd   = mail.from  = senderid@test.com mail.to    = receiver@test.com mail.debug = false save this and exit  then run this following command in terminal you have to keep this terminal open to run notification program. java -jar MailNotifierApp.jar properties=MailNotifierApp.props you will get test email after this

User Locked in SAP

Lock user (unlock) lock - is  a record in the field  uflag, "0" - the user is not locked, To Unlock - need to switch field  uflag to "0": Locked SQL> select uflag from sapsr3.usr02 where mandt='000' and bname='SAP*';      UFLAG ----------        128 Not locked: SQL> select uflag from sapsr3.usr02 where mandt='431' and bname='USERNAME';      UFLAG ----------          0 Unlocking: SQL> update sapsr3.usr02 set uflag='0' where mandt='000' and bname='DDIC'; 1 row updated. SQL> commit work; UNLOCK your self update sapr3.usr02 set uflag='0' where mandt='830' and bname='USER';   commit work; RESET PASSWORD PROCESS: SQL> select bcode, passcode from sapsr3.usr02 where mandt='000' and bname= 'DDIC'; BCODE            PASSCODE ---------------- ---------------------------------------- EF82F150AB6136BF 6BBFC576