SAP Errors

Error: Export log: run_backup.sh(571) 220930-092556: Instance:ABC@localhost:30013 Schema:"ABC" Found pid file /var/log/SAPBusinessOne/BackupService/logs/ABC_localhost_30013/ABC.pid with running pid(12155). Resolution: Kill the process ID which is mentioned in your export log using below command kill -9  <enter the PID which is shown in log>

Go to below URL         https://support.sap.com/en/index.html Click on Manager User Login with Admin Suser ID Once you login Click on the user to which you want to change the expire date Click on change expire date Extend the expiry date and save    

 Issue: Gateway and Dispatcher are not starting. After checking the logs found the error in DEV_rd.log file  dev_rd log file Resolution: Stop the SAP application Execute the  ps -ef | grep <sid>adm command and kill all the running process  Execute   netstat -an | grep <gatway port>  Go to /tmp folder and delete the .sapstream3301 files and startsapsvr.log files as well Execute the  cleanipc < Instance Number of DVEBMGS>  < Instance Number of ASCS>  ( command looks like cleanipc 01 02) Now start the sap application.

A profile in the SAP system is an operating system file containing parameters and configuration information of an instance. Since a SAP system might contain from one to several instances, many profiles may also exist. Individual setup parameters can be customized to the requirements of each instance The profiles are an essential part of technical and basis settings of the system, and the values they contain play the most important role when tuning the system.  The profiles are used when starting and stopping the system since they are in charge of allocating or deallocating the necessary resources as specified in the profile parameters These individual parameters let you customize the following: The runtime environment of the instance (resources such as main memory size, shared memory, roll size) Which services are available for the instance (which work processes and how many) Where other services are located (database host, message server, etc.) The profile files are located under ...

  Transaction Code For Basis Administration. SU01 User Maintenance AL11 Display SAP Directories SU01D User Display BD54 Maintain Logical Systems SU02 Maintain Authorization Profiles OSS1 Logon to Online Service System SU03 Maintain Authorizations SALE IMG Application Link Enabling SU05 Maintain Internet users SARA Archive Management SU10 User Mass Maintenance SICK Installation Check SMLG Maintain Logon Group SM14 Update Program Administration SUPC Profiles for activity groups SM35 Batch Input Monitoring SUIM Info system Authorizations SM56 Number Range Buffer PFCG Profile Generator SM58 Asynchronous RFC Error Log PFUD User Master Data Reconciliation SM59 RFC Destinations (Display/Maintain) S002 Easy System Administration Menu SAINT SAP Add-on Installation Tool ZAUT maintenance. Requesting new users, changing authorisation, etc.   SPAM SAP Patch Manager (SPAM) Client Administration: SPAU Display modified DE objects   SPDD Display modified DDIC objects SCC3 Checking Cl...

 Login to SAP  Go to Transaction Code SE38   Enter the report name /IWFND/R_METERING_VIEW Click on execute In the next screen enter the user name and click on execute to get the specific user logs or else leave empty to get all the user logs Below mentioned are the screenshots

 Command:  chown -hR <owner name>:<group name>  <filename>

 Error:  Solution: Make sure you have selected the correct database type and entered the correct credentials. Install DI API 64 Bit as well DI API 32 Bit version.

 Press  Win+R Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters DisabledComponents  as dword and value as ffffffff

Error: Solution: Provide full permission to the Sybase setup.bin file in the Sybase database installation folder.

  Sandbox Client This client is a general test client and is initially created as a copy of the SAP reference client, but is refreshed periodically with a copy of the quality assurance-testing client. This client is used for familiarization and testing application and customization functions. Customizing/Development Client Customizing settings are made in the customizing/development client (CUST) to create a prototype system. All application customizing is performed in this client. All system development occurs in this client according to the business requirements of the CUSTOMER. Once all the settings have been created, these are transferred to the QA client for testing. The development changes are then transported using change request transport management system. Quality Assurance and Testing Client The configuration from Customizing Client is transported to this client tested and checked. When the configuration has been thoroughly tested in this client, and signed off by the Qua...

  It is the process of setting up a client with live data from production system for Testing/Training Purposes. Periodically it is required to set up clients for preproduction/quality assurance/training clients. Most of the scenarios the Remote client copy is the best method then the local client copy on the production system(to avoid client settings/accidental client copies in Production). However in some of the environments the pre production client will exist in Production system but it is only possible to test client specific scenarios because the Rep and CCC are shared between clients(set to not modifiable) It is also recommended to perform DB/System Refresh instead of Client Refresh. Note: There will be only one client in the production system apart from 000,001 and 066.but it is possible to have more than one client in the production system.

Execute SCCL on target System. Target Client is Displayed Select the Profile specify the Source Client schedule as a background job/or start immediately in the dialog mode. Profile: it specifies the type of data that need to be copied from Source Client.(SAP_CUST is mandatory profile to setup all the new clients) SAP_ALL--Copies the cust,application and usermaster(to setup training Client) sap_appl--Copies cust and applicaton sap_user--only user master sap_cust---only customizing data Client Copy Copies only the table entries from the source client and paste(copy) them in the same table with target client.(different MANDT). The Number of tables will not increase due to a client copy.The entries are copied with a target client number. Test run is used to check the resources that are required for client copy.

 Error: Solution:  Go to the ExtensionManager and enable the fore install as shown in the below screenshot.

 Error: Solution: Call transaction SECSTORE. Choose "Execute" (F8). In the entries that are displayed, delete the entry /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light. In the entries that are shown, delete the entry /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light. After the deletion of this entry, all the trust relationships to trusted systems (systems that are trusted by the current system) are invalid and, if required, have to be deleted in the current system using transaction SMT1 and then have to be recreated. In transaction SE37, execute the function module RFC_PING with the destination NONE. If the system displays an error message, execute the function module RFC_PING again; the error message cannot appear a second time in this case. 3. Solution by executing a report (as of SAP Basis Release 620): Execute the report RS_TT_CLEANUP_SECSTORE. If you cannot implement the ...

- login into sybase database Use the below command if you have more than one backup file > load database <database name> from <location path 01.dmp> > stripe on <location path 02.dmp> > stripe on <location path 03.dmp> > go

 Error: LOG BZA=> table SVERS does not exist on database   ERROR => saplikey: failed to read table SVERS after connecting to the database. [saplikey.c   834] ERROR: -1 in function CheckCodepageType (SQLExecDirect failed) [line 33630] (208) [42000] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]DBPROPERTIES not found. Specif y owner.objectname or use sp_help to check whether the object exists (sp_help ma y produce lots of output). Solution: -If you are facing the above error during the SYSTEM COPY at the create ICM user store phase. please make sure you have done the backup restore correctly. - Check dev_likey.log, saplikey logs - Try creating a temporary license manually using the saplikey command  Can also refer the below SNotes related to the issue https://launchpad.support.sap.com/#/notes/1900976 https://launchpad.support.sap.com/#/notes/530392

Error: java.net.UnknownHostException: Error during configuration - see preceding message Solution:    Check the hostname in host file it should be correctly defined

 Error:   java.io.IOException: Cannot run /backup/sybaseupdate/setup.bin - execve failed (EACCES - Permission denied)  Solution:    Locate the path of "setup.bin" file and give 777 access to the "setup.bin "   chmod 777 setup.bin   

Solution:    If you have installed Sybase database on SUSE Linux install the below library file.  Library Name: glibc-32bit   If you have installed Sybase database on Redhat Linux install the below library file   Library Name: glibc.i686 Installing that library will resolve the issue 

Issue:  In the operation system, check if the mount points are changed to read-only (ro)file system. Resolution: Need to change the mount point to read - write (rw)