DB02 statistics blank
Category: Databases | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
To make this DB02 transaction displayed correctly, implement SAP Notes 868063 – Database space statistics monitor for Oracle. Here’s the steps :
1. Run report RSORACUP.
2. Fill input parameter : CON_NAME : DEFAULT (for local system), or one of database connection as in F4 help
3. Execute 2013-1
18
SAP SPOOL Process
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
what is spool overflow ? How to troubleshoot spool overflow issue ? ——————————————————————————————– What is spool overflow ? :
Spool request that got generated are stored in a temporary sequential file called Temse. Please note that these are stored in Temse because these are not stored permanently. The size of the Temse is limited by the parameter definition.
The default size of Temse is 32,000 and it can be increased till 2 billion. However, defining very high value can effect the database performance. Due to limited storage capacity of Temse, when this file got full, this throws an SAP spool overflow error.
If this happens, customers could not print from SAP. If you check in SM21 and ST22 transactions, you may encounter some error log or dumps like
ERROR IN SPOOL call : SPOOL OVERFLOW SPOOL_INTERNAL_ERROR
System internal error in the spool system How to troubleshoot spool overflow ?
To resolve this spool issue, some of the old spools can be deleted from the sap system. Goto transaction SPAD. From the initial screen, navigate to Administration -> Clean_up_spool. Once you click this, Spool Administration : Delete old spool requests screen will be displayed.
In that screen, you will be prompted to choose requests for deletion like Old spool requests older than the maximum set age
Requests already printed All spool requests
Select the check boxes as per the requirement (eg: delete all requests already printed and minimum age in days equal to 30 days) and execute to delete old spool requests, which will clear Temse and will resolve spool over flow issue.
Apart from this there are others ways of resolving spool overflow issue. They are 1) Run the report RSPO0041 from SE38 transaction to delete old spool requests
2) Run the report RSPO0043 from SE38 transaction, which checks the Temse/spool consistency and reorganizes the spool
How to avoid spool overflow issue ?
These reports RSPO0041 and RSPO0043 should be scheduled as background jobs with proper variants on a periodic basis which avoids spool overflow issue.
You can try to increase the spool numbers from default 32000 to a bit higher value but please note donot set this too high as it may impact database performance
Proactive monitoring check can be made in RZ20 transaction to see how much is the fill level of spool numbers.
How to check spool numbers ?
To check spool numbers : Goto RZ20 transaction, navigate to SAP CCMS Monitor Templates -> Spool System.
Here you can check the status of spool servers and the used numbers percentage of spool numbers. If you find that used numbers is greater than 80%, you can manually run above mentioned reports or delete old spool requests from SPAD tcode as mentioned earlier. How to set the spool number in SAP ?
Using Transaction SNRO (Number range object maintenance) and object SPO_NUM, you can set the spool number in an SAP system.
Once you provide object as SPO_NUM, click on change icon. It displays another screen. In that screen, click on Number Ranges push button. It displays another screen “Number range for spooler numbers”. Click on change icon here and set the value of spooler(from number and to number). Please note that a change request may be generated here based on the client settings(if automatic recording of changes is set in SCC4 transaction of the client) How to define storage location (Temse) of spool requests ?
Every Temse object contains a header in TST01 table and the actual object. This can be either stored in table TST03 or in file system. You can set a parameter rspo/store_location in RZ10 to define whether to store Temse objects TST03 table or in filesystem.
If value G is set to this parameter, it will be stored in filesystem and if it is db it is stored in TST03 table.
2012-12 16
Prioritizing Class A Jobs
Category: SAP BASIS | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Use:
You can reserve any number of background processing work processes to be kept free for high-priority, or class A, jobs. Reserving work processes for class A jobs does not reserve
any particular work process in a server for class A jobs, but rather makes sure a certain number of work processes is free at all times. To set the number of class A background work processes, you’ll need to set the work process distribution and assign each work process to an
operation mode. For more information, see Prioritization Strategies for Class A Jobs. Procedure:
To set the number of work processes to keep free for high-priority jobs in the definition of an instance (SAP application server):
1. Call Transaction RZ04 or choose CCMS ® Configuration ® Operation Modes / Instances.
To review the current configuration of SAP instances and operation modes and begin defining up background processing servers, choose Instances/operation modes.
If the server you want to set up as a background processing server doesn’t appear in this list, create a new instance. Choose Instance ® Create new instance. Complete the
instance definition in this Maintain Instance Data window, then save.
Once the server you want to set up as a background processing server appears in this list, select the mode for that server then select Choose.
In the Maintain Work Process Distribution screen, set the number of work process by selecting the current number and increasing or decreasing it with the “-” or “+” buttons. Save here, return to the previous screen, and save again. These changes will take effect
when the operation mode is next activated. Numbers of Class A background work processes: 0
The default number. Use this value if you do not
have mission- or system-critical class A jobs that must always start immediately when they become eligible to start. In this case, jobs are simply run according to their priority, or “class”. Work processes are not kept free for class A jobs.
1 or more
Use this value to guarantee that mission- or system-critical jobs start immediately once they become eligible to start. One background processing work process will always be kept free for class A jobs, ensuring no class A job has to wait for a free background work process.
To keep background work processes available for jobs that aren’t class A, be sure that the number of class A work processes is less than the total number of background work processes in an application server. Otherwise, only class A jobs will be eligible to run on that server. To reserve an entire application server exclusively for class A jobs, set the number of class A work processes to the total number of background work processes. For example, if an SAP server offers 4 background work processes and the class A reservation for the server is set to 4, only class A jobs can start at that server.
The class A setting is in effect whenever the operation mode(s) in which it is defined are active. 2012-12
8
SAP Java monitoring Check list Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
SAP Java monitoring Check list
This article answers the following queries :
Ø How to perform daily monitoring of Java stack in SAP ?
Ø How to access management console in SAP ?
Ø How to perform session monitoring in JAVA stack of SAP ?
Ø How to view various java reports in JAVA stack of SAP?
Ø What are the various java reports available in Java stack of SAP and what is their significance?
Ø How to view log and traces in java stack of SAP?
Ø Where to view default trace in java stack of SAP?
Ø What is the use of management console in SAP ? ———————————————————————————————– JAVA Monitoring Contents :
2. Actioning, in case portal not accessible
3. User load analysis
4. Java Reports – Navigation and usability
5. Memory consumption and Threads report
6. Session Monitoring
7. Logs and Traces (Default trace, Server0 log etc)
8. Accessing Management Console
9. Checking System availability using Management Console(SDM, Msg server, Enqueue server, Java nodes etc)
10. Check various logs(work directory logs, jcontrol, default trace, application log etc)
Java Monitoring :
Place the link of the respective java application in the browser and check whether the java application is opening:
http://baakaprd.company.com:50000/irj/portal
If java is up and running, a screen similar to below will open.
If the page did not open,
i) Check whether there are network issues
ii) Check tablespaces occupancy levels at Oslevel and make sure sufficient space is there and if any tablespace is 100% full, action the same
iii) Check the default trace for any critical errors
iv) Check application log to determine any memory related issues
v) Check server node status at oslevel or through management console and action and bring up the java again.
To estimate the user load and to check the number of users logged onto the java portal : Navigate to User Administration -> Activity Reports
i) Check “Number of users in the last 3 hours” report
ii) To figure out most active users, Check the 10Most active users report
Java Reports :
Java Memory Consumption Report and Threads Reports :
These reports includes a chart of the memory usage of a cluster node and a chart related to the system and application thread pool.
To check this report login to nwa of the respective java stack :
Then navigate to Monitoring -> Java System Reports :
Here following reports can be taken by selecting the respective report from the drop down provided:
· Capacity Planning : This report includes a chart representing the requests sent to J2EE Engine, a chart for the number of http and security sessions, and a chart of the communication
between J2EE nodes
· Resource Consumption : This report includes a chart of the memory usage of a cluster node, and a chart related to the system and application thread pool
· Error Statistics: This report includes a chart representing a collection of counters useful for investigating problems. There are also charts that give an overview of timeouts and the size of log files
· Application Activities : This report includes a chart that represents the history of the activities of deployed applications
· Slowest requests in detail · Slowest requests · Slowest components · User activities · Current activities · Monitor Browser
However from monitoring perspective, resource consumption report is most important to analyse the memory consumption.
Select resource consumption from the dropdown to view the memory statistics as below:
Click on Go to Detailed Chart link of the respective report to view detailed chart as below
Click Hint on charts link to analyse the report better.
Select the respective Instance, Cluster node and Time period from the provided dropdown boxes to view the reports belonging to the same
Table view for Threads report:
There are 2 types of views: Chart view and Table view. You can change the view by selecting the respective radio button.
Please find below table view for Memory Consumption report Session Monitoring:
To monitor sessions, navigate to Monitoring -> Session Monitoring
To check “Logs and Traces”, navigate to System Management -> Monitoring -> Logs and Traces From the drop down box, different logs can be checked
Process list – List of processes that are currently running can be viewed here and any long running process can be identified and actioned accordingly.
Using Management Console for monitoring Java System :
To open management console for SAP systems based on Unix operating system, add 13 for the port of the portal as mentioned below
http://faqsa6.comapn.com:50013
A screen similar to below screen will appear :
You can drill down further on SID of the system to view database,Central and SCS instance details as below :
Please note that Management Console can be accessed even when java is down for a sap system.
You can check database status as below :
You can check the javanode status as below: Status should be running here if java is up
Process list – List of processes that are currently running can be viewed here and any long running process can be identified and actioned accordingly.
SDM, Dispatcher, Server0 and server1 node status can be checked here:
Various work directory logs, availability log, application log and default trace can be checked here : Availability log :
Sapstart log: Dev_jcontrol log : Dev_server0 log :
To check the status of message and enqueue servers, check the process list under scs instance as mentioned below :
To check various logs related to message server, enqueue server, jcmon check the logs under SCS instance as mentioned below :
2012-12 8 Organizational Levels
Category: SAP Security, Uncategorized | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
“Organizational Levels” (Org Levels) as opposed to authorization fields is another of the core concepts that we come across while creating roles in PFCG. We can access the organizational level values defined for a role by clicking the “org level” button in the main toolbar within PFCG. In the role below, we see Org Levels like Company Code, Purchasing Org, Purchasing Group, Sales Org, Division, Plant, etc.
PFCG – Org Levels
In the expanded view of the authorization data in PFCG, the org levels defined earlier appear side-by-side with the authorization fields. In fact, all org levels are also authorization fields but not all auth fields are org levels. For example, the org level Plant appears as an authorization field in two objects, M_LFPL_ORG and M_MATE_WRK. On the other hand the field Activity is not an org level. Once we maintain a particular value for an org level in a role, all authorization objects using the same org level as a field will automatically take the same value. Its technically feasible to break an org level, so that for a particular object, its value is different from its defined org level value but this defeats a the purpose of defining something as an org level.
Another difference between org levels and normal auth fields come to light while deriving a role from another master role. A normal auth field will be inherited by the child role with the same value as maintained in the parent but an org level can be maintained in the individual child roles.
PFCG – Org Levels vs Auth Fields
Organizational Levels in most cases are intrinsically linked to the enterprise structure of an organization and largely determined during the customizing steps for the SAP systems. The below screen-shot from the SPRO transaction shows the options for configuring different org levels like company code, controlling area, purchase org, sales org etc. So its not really the security administrator who defines the org levels. He can only use the existing org levels defined during functional configuration.
SPRO – Enterprise Structure
Its possible to change an authorization field to an org level for the purpose of security by executing the programPFCG_ORGFIELD_CREATE. However, since this program impacts all roles
which contain the org field it should only be run after a thorough analysis of all impacted roles. Also certain auth fields like Activity can never be changed to an org level.
2012-12 8
Central User Administration in SAP (CUA) Category: SAP Security | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Here is the procedure for Central user administration configuration in a landscape:
1) Create Logical systems to all clients for the landscape using BD54 or SALE as comfortable. 2) Attach Logical system to clients using Same.
3) Create RFC connection to relevant systems with the same name as logical system name . If you Logical system name is SIDCLNT100 for dev then create RFC connection to DEV with same name SIDCLNT100.
4) Let us suppose you Central system: DEVCLNT100 Child system: QUACLNT200 5) Create user CUA_DEV_100 in devclnt100 system
4. Create user CUA_QUA_200 in quaclnt200 system.
Create RFC’s to child systems from central and central to child.
5) Now logon to central system and execute tcode scua to configure cua. Enter the name of the distribution model: CUA
Press create
Enter ALL Child system RFC’s
Save your entries now result screen will appear If you expand the nodes for
each system: .ALE distribution model was saved,. .Central User Administration activated,. and .Text comparison was started.. If problem messages are displayed here, follow the procedure in SAP Note 333441:
6) Setting the Parameters for Field Distribution Enter Tcode SCUM in central system following screen will appear Now maintain your filed distribution and save it. You can use transaction SUCOMP to administer company address data. You can use transaction SCUG in the central system to perform the synchronization activities between the central system and the child systems by selecting your child system on the initial screen of transaction SCUG and then choosing Synchronize Company Addresses in the Central System
After you have synchronized the company addresses, you can transfer the users from the newly connected child systems to central administration.
This is done, as with the synchronization of the company addresses, using transaction SCUG in the central system. To do this, on the initial screen of transaction SCUG, select your child system and choose the Copy Users to the Central System button.
Use
You can use the report RSCCUSND from the central system of Central User Administration (CUA) to synchronize the master data of selected users with a child system of the CUA. The report sends the master data (including role and profile assignments) to a child system of the CUA.
If master data exists in the child system for the user sent, it is overwritten. Procedure …
1. Start report RSCCUSND (for example, using transaction SA38).
2. In the Receiving System field, specify the child system to which you want to send the user data.
3. You can use the fields User and User Group to restrict the number of users. 4. Specify the data that you want to distribute under Distribution Options.
5. Choose Execute.
2012-9 29
Schedule tasks on Linux using crontab
Category: Opertating Systems | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
If you’ve got a website that’s heavy on your web server, you might want to run some processes like generating thumbnails or enriching data in the background. This way it can not interfere with the user interface. Linux has a great program for this called cron. It allows tasks to be automatically run in the background at regular intervals. You could also use it to automatically create backups, synchronize files, schedule updates, and much more. Welcome to the
wonderful world of crontab.
Crontab
The crontab (cron derives from chronos, Greek for time; tab stands fortable) command, found in Unix and Unix-like operating systems, is used to schedule commands to be executed
periodically. To see what crontabs are currently running on your system, you can open a terminal and run:
To edit the list of cronjobs you can run: sudo crontab -e
This wil open a the default editor (could be vi or pico, if you want you can change the default editor) to let us manipulate the crontab. If you save and exit the editor, all your cronjobs are saved into crontab. Cronjobs are written in the following format:
* * * * * /bin/execute/this/script.sh Scheduling explained
As you can see there are 5 stars. The stars represent different date parts in the following order: 1. minute (from 0 to 59)
2. hour (from 0 to 23)
3. day of month (from 1 to 31) 4. month (from 1 to 12)
5. day of week (from 0 to 6) (0=Sunday) Execute every minute
If you leave the star, or asterisk, it means every. Maybe that’s a bit unclear. Let’s use the the previous example again:
* * * * * /bin/execute/this/script.sh
They are all still asterisks! So this means execute /bin/execute/this/script.sh: 1. every minute
2. of every hour
3. of every day of the month 4. of every month
5. and every day in the week.
In short: This script is being executed every minute. Without exception. Execute every Friday 1AM
So if we want to schedule the script to run at 1AM every Friday, we would need the following cronjob:
0 1 * * 5 /bin/execute/this/script.sh
Get it? The script is now being executed when the system clock hits: 1. minute: 0
2. of hour: 1
3. of day of month: * (every day of month) 4. of month: * (every month)
5. and weekday: 5 (=Friday) Execute on workdays 1AM
So if we want to schedule the script to Monday till Friday at 1 AM, we would need the following cronjob:
0 1 * * 1-5 /bin/execute/this/script.sh
Get it? The script is now being executed when the system clock hits: 1. minute: 0
2. of hour: 1
3. of day of month: * (every day of month) 4. of month: * (every month)
5. and weekday: 1-5 (=Monday til Friday)
Execute 10 past after every hour on the 1st of every month Here’s another one, just for practicing
10 * 1 * * /bin/execute/this/script.sh
Fair enough, it takes some getting used to, but it offers great flexibility. Neat scheduling tricks
0,10,20,30,40,50 * * * * /bin/execute/this/script.sh But crontab allows you to do this as well:
*/10 * * * * /bin/execute/this/script.sh
Which will do exactly the same. Can you do the the math? Special words
If you use the first (minute) field, you can also put in a keyword instead of a number: @reboot Run once, at startup
@yearly Run once a year "0 0 1 1 *" @annually (same as @yearly)
@monthly Run once a month "0 0 1 * *" @weekly Run once a week "0 0 * * 0" @daily Run once a day "0 0 * * *" @midnight (same as @daily)
@hourly Run once an hour "0 * * * *
Leave the rest of the fields empty so this would be valid: @daily /bin/execute/this/script.sh
Storing the crontab output
By default cron saves the output of /bin/execute/this/script.sh in the user’s mailbox (root in this case). But it’s prettier if the output is saved in a separate logfile. Here’s how:
*/10 * * * * /bin/execute/this/script.sh 2>&1 >> /var/log/script_output.log Explained
Linux can report on different levels. There’s standard output (STDOUT) and standard errors (STDERR). STDOUT is marked 1, STDERR is marked 2. So the following statement tells Linux to store STDERR in STDOUT as well, creating one datastream for messages & errors:
Now that we have 1 output stream, we can pour it into a file. Where > will overwrite the file, >> will append to the file. In this case we’d like to to append:
>> /var/log/script_output.log Mailing the crontab output
By default cron saves the output in the user’s mailbox (root in this case) on the local system. But you can also configure crontab to forward all output to a real email address by starting your crontab with the following line:
MAILTO="[email protected]" Mailing the crontab output of just one cronjob
If you’d rather receive only one cronjob’s output in your mail, make sure this package is installed:
aptitude install mailx
And change the cronjob like this:
*/10 * * * * /bin/execute/this/script.sh 2>&1 | mail -s "Cronjob ouput" [email protected]
Trashing the crontab output Now that’s easy:
*/10 * * * * /bin/execute/this/script.sh 2>&1 > /dev/null
Just pipe all the output to the null device, also known as the black hole. On Unix-like operating systems, /dev/nullis a special file that discards all data written to it.
2012-8 2
Enterprise Portal Administration Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
What is single sign on (SSO)
Once a user has authenticated to the SAP EP, he doesn’t need to enter his credentials again to access all the systems and backends (SAP and Non-SAP, ESS, MSS and services) integrated into the EP. SSO can be achieved in 3 ways:
- JSESSIONID: The JSESSIONID cookie is used for achieving SSO on the Server Node
- User Mapping: The user or administrator assign for a specific backend system the userid and password. These settings will be used to achieve SSO to the specified backend. If the user is using a different userid for a backend, this is the prefered solution to achieve SSO.
- SAP Logon Ticket. This is a session cookie named MYSAPSSO2 stored in the browser cache and is used to achive SSO to the backends, using the same userid for every backend system.
When talking about SSO, normally the SAP Logon Ticket is meant. What is the SAP Logon Ticket?
SAP Logon Ticket (token) is a session cookie, stored inside the browsers cache. It get’s
permanently deleted from the cache after the user logs out or the token is expired. The Logon Ticket contains:
Highest Authentication Scheme Validity
Issuing System Digital Signature
One Mapped ABAP User ID User ID
It doesn’t contain the password. What are the types of SSO? SSO with SAP Logon Ticket
SSO with User ID and password (User Mapping)
SSO using a 3rd party system (Microsoft Active Directory, Kerberos, etc, but the Issuing System for the SAP Logon Ticket is an SAP NetWeaver AS!)
What are the steps for SSO? Create RFC destination in SM59
Create JCO-RFC destination in Visual admin
login/create_sso2_ticket=2 login/accept_sso2_ticket=1
4.Export portal certificate (verify.der) 5.Import Portal certificate in STRUSTSSO2 6.Export R/3 certificate in STRUSTSSO2
7.Import R/3 certificate in keystore administration 8.Create system alias in portal
9.Check the SAPJSF user in ABAP system
10.Map the ABAP user to Portal user if it is required. 2012-7
21
JAVA bootstrap Stops Due to Database Problems in SAP.. Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Bootstrap Stops Due to Database Problems Symptom
AS Java stops with one of the following exit codes: 503, 504, 505, 506, 507, 508, 509, 511, 512, 513, 515, 516, 517, 518, 519, 520, 521, 524, 525, 526, 527, 528, 529, 530, 532, 542, 546, 548, 549, 550, 551.
Scenario Type: Error analysis
SAPNetWeaver Component: Application Server Java (AS Java) Analysis
The bootstrap module fails to synchronize the files due to problems with the connection to the database or database inconsistency.
If you get one of the exit codes listed above, take the following steps:
1. 1. Find a detailed description of the problem in the bootstrap log files, which are located in the /usr/sap/<SID>/JC<XX>/work/ folder. The log files are:
○ dev_bootstrap* – logs from the Java Startup and Control Framework that shows the parameters with which the bootstrap was started.
○ log_bootstrap* – logs from the execution of the bootstrap that show the execution flow from the last session and the possible errors.
○ jvm_bootstrap* – logs from the JVM output for the bootstrap process that show possible JVM problems during the bootstrap execution.
1. 2. Perform a database consistency check following the procedure below. If any of the steps is not completed successfully, stop the check and report the result in a CSS message.
2. a. Start the Config Tool to check if it connects to the database. 3. b. Check if you can connect to the database using an external tool.
This external tool can be DBManager for MaxDB or Enterprise Manager for MSSQL Server.
4. c. Run the integrity check tool provided with the database (for example, DBManager for MaxDB).
5. 3. Proceed depending on the particular exit code.
Exit code 503: Error while initializing the database connection. Check if the database is running. For more information, check the bootstrap logs and see SAP Note 915825.
The connection to the database cannot be initialized. Try the following steps in the order they are described:
…
1. 1. If the database is not started, start the database.
In the profile /usr/sap/<SID>/SYS/profile/<SID>_J<XX>_<HOSTNAME>, check for the
j2ee/dbdriver entry and make sure that it is correct for the database you are using. Check if the files in the entry really exist and have the correct permissions for access from <SID>adm user.
1. 3. Make sure the user name and the password for accessing the database are correct.
2. 4. Perform a database consistency check.
Exit code 504: Custom parameters mappings not found in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.
Exit code 505: Problem accessing the database. Check if the database is running and the database connection details. For more information, check the bootstrap logs and see SAP Note 915825.
These exit codes indicate problems with access to the custom parameters mappings. The parameter mappings are used when Software Deployment Archives (SDA) are deployed that contain parameterized settings. Parameterized settings contain system parameters provided by the Configuration Manager that are transparently substituted during runtime. The custom parameters are defined by the user of the system. Some parameters may be vital for the work of other system components and if they cannot be substituted, their incorrect value may cause inconsistencies in the system.
If you deployed a SDA that uses a custom parameter, which it is not found in the database, this causes the bootstrap to exit.
Proceed depending on when the problem occurred. If the problem appeared after: installation: Create a CSS message under component BC-INS.
upgrade: Create a CSS message under component BC-INS or BC-UPG-TLS-TLJ depending on the tool used (SAPInst or JINUP)
deploy: Create a CSS message under component BC-JAS-DPL In the CSS message for this problem include:
the bootstrap logs
description of the installations/deployments/upgrades you performed lately the logs of the server(s) from /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>/log. a report about any of the steps that failed during the database consistency check.
Exit codes 506 and 507: Cannot access the synchronization root. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.
The content that needs to be synchronized is located under specific location (root) in the database. The bootstrap module cannot find this root so the synchronization fails to start. These exit codes indicate problems with the:
…
Database consistency – the state can be caused by errors during installation, upgrade or deploy.
Check the database consistency and include the report for the steps that failed.
Create a CSS message depending on whether the problem occurred after installation, upgrade, or deploy under the components listed above.
Wrong or missing profile entry j2ee/instance_id, which determines the specific instance root.
Find the profile in /usr/sap/<SID>/SYS/profile/<SID>_J<XX>_<HOSTNAME>. Check if the entry is missing and if so, create a CSS message under BC-INScomponent.
Exit codes 508 and 509: Cannot access the version information in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.
The bootstrap uses special versioning to optimize the synchronization process. Without this optimization, everything from the database has to be downloaded to the file system. This
information is always present in the database. If it is not there, the bootstrap stops with an exit code.
The problem can be caused by erroneous installation, upgrade or deploy. The reason for the error may be:
Missing or improperly linked template Missing instance ID entry from the profile
Create a CSS message depending on whether the problem occurred after installation, upgrade, or deploy under the components listed above. In the CSS message for this problem include:
the bootstrap logs
description of the installations/deployments/upgrades you performed lately the logs of the server(s) from /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>/log. a report about any of the steps that failed during the database consistency check.
Exit codes 511, 512 and 513: Problem accessing the instance metadata. Check the database settings. For more information, check the bootstrap logs and see SAP Note 915825.
The instance metadata contains information about the JVM location, JVM settings (heap and perm sizes, GC options, and so on), the infrastructure (SCS host and ports). If the instance data cannot be read, the instance does not run as desired so the bootstrap exits.
Create a CSS message for this problem and attach the bootstrap logs.
Exit codes 515 and 516: Cannot find information about the native files. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.
The database contains metadata about the native files that are synchronized in
/usr/sap/<SID>/JC<XX>/j2ee/os_libs. If this metadata cannot be obtained, the bootstrap has to exit, otherwise the AS Java does not function properly.
Check the database consistency and create a CSSmessage with the consistency report and the bootstrap logs.
Exit codes 517, 518, 519, 520 and 521: Error while reading index information from the
database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825.
Bootstrap uses indexes to optimize the synchronization process. If these indexes cannot be read from the database, all the binaries have to be downloaded, which takes a lot of time. The indexes are always present in the database. If the bootstrap exits because of access problem while reading the indexes, this may be an indication of database inconsistency.
Check the database consistency and create a CSSmessage with the consistency report and the bootstrap logs.
Exit codes 524, 525 and 526: Problem accessing the cluster file system global version. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825.
The Cluster File System (CFS) is used for deploying single file system archive in multiple file systems in the whole cluster. The CFS serves as a repository for the deployed files, while the bootstrap is responsible for the synchronization of the CFS components in the FS of the cluster elements. The global version is used for optimization purposes. If it is missing this may be an indication of:
Database corruption. Check the database consistency.
Version mismatch between the bootstrap and deploy controller versions. Check the versions of the components as described above.
Create a CSS message that includes the database consistency report, the versions of the components and the bootstrap logs.
Exit codes 527 and 528: Problem accessing the versions repository of the cluster file system. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller
version. For more information, check the bootstrap logs and see SAP Note 915825.
The version’s repository of the CFS is used to optimize the synchronization time. If it is missing this may be an indication of:
Version mismatch between the bootstrap and deploy controller versions. Check the versions of the components using:
○ SystemInfo application if the engine is running
○ Version script located in the folder /usr/sap/<SID>/JC<XX>/j2ee/cluster/bootstrap/scripts if the engine cannot start
Create a CSS message, including the version information displayed by the tool you are using. The minimum information required is the bootstrap and the deploy controller components versions. You also have to include the name of the tool (“SystemInfo application” or “version script”) used to obtain the versions.
Database corruption
Check the database consistency. Create a CSSmessage that includes the database consistency report, the versions of the components and the bootstrap logs.
Exit codes 529 and 530: Problem accessing the metadata of the cluster file system. Check the database state and the Deploy Controller component version. For more information, check the bootstrap logs and see SAP Note 915825.
The CFS is used for deploying single file system archive in multiple file systems in the whole cluster. The CFS serves as a repository for the deployed files, while the bootstrap is responsible for the synchronization of the CFS components in the file system of the cluster elements. If any data required for the synchronization of the CFSarchives is missing or not accessible, the bootstrap exits. This may be an indication of:
Version mismatch between the bootstrap and deploy controller versions: Check the versions of the components as described above.
Create a CSS message that includes the database consistency report, the versions of the components and the bootstrap logs.
Exit codes 532 and 542: Index not found in the database. Check the database consistency and the version of the OfflineDeploy component. For more information, check the bootstrap logs and see SAP Note 915825.
The bootstrap uses database indexes along with the file system indexes to optimize the synchronization process. If a database index cannot be found, one or more components are unknown to the bootstrap and cannot be downloaded to the file system. This can result in the AS Java not working as expected.
The error may indicate inconsistent database. Check the database consistency and create a CSS message with the consistency report and the bootstrap logs attached.
Exit code 546: Problem reading kernel properties from the DB. For more information, check the bootstrap logs and see SAP Note 915825.
Exit codes 548, 549: Problem reading the managers’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825.
Exit codes 550, 551: Problem reading the services’ properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825. The bootstrap reads the kernel properties; the properties of the managers that compose the kernel of the AS Java; and the services’ properties from the database. All these properties are used to configure the kernel so they are vital for the work of the managers. If they cannot be obtained, the bootstrap exits.
These errors may indicate an inconsistent database. Check the database consistency and create a CSS message with the consistency report and the bootstrap logs attached.
2012-7 21
Troubleshooting: AS Java Bootstrap Stops with an Exit Code.. Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Troubleshooting: AS Java Bootstrap Stops with an Exit Code Symptom
AS Java stops with an exit code because the AS Java bootstrap module failed to synchronize the system’s files.
Scenario Type: Error analysis
SAP NetWeaver Component: Application Server Java (AS Java) Analysis
The bootstrap module collects metadata about the instance and the files it has to synchronize and then downloads the required files to the file system. It can fail to synchronize the system’s files for the following reasons:
The database was not started or is corrupted Incorrect or missing file system permissions
Wrong installation type (32 bit binaries on 64 bit machine) Errors in the bootstrap logic
Problem Areas
Depending on the kind of problem that caused the bootstrap to fail, you can have an exit code from one of the following problem areas:
Database connectivity/consistency
This category includes problems with the connection to the database and the database
consistency. The exit codes are: 503, 504, 505, 506, 507, 508, 509, 511, 512, 513, 515, 516, 517, 518, 519, 520, 521, 524, 525, 526, 527, 528, 529, 530, 532, 542, 546, 548, 549, 550, 551.
More information: Bootstrap Stops Due to Database Problems File system
The problems in this area are connected mainly with file system access permissions. The exit codes are: 514, 522, 523, 531, 541, 533, 534, 535, 536, 537, 538, 539, 540, 543, 544, 547, 552. More information: Bootstrap Stops Due to File System Problems
Configuration properties
The area includes problems with the configuration of the bootstrap module. The exit codes are: 501, 502, 510, 545.
More information: Bootstrap Stops Due to Configuration Problems
Further Information
If you are unable to identify the problem or cannot solve the problem following the suggested steps, create a CSS message under the component BC-JAS-COR with short text “Bootstrap exit code XXX”, where XXX is the exit code from the bootstrap process. The exit code can be found in dev_bootstrap file. Collect the bootstrap logs and attach them to the created CSS message. If the offline bootstrap process finished successfully, but the server process fails to start because of a problem related to the bootstrap, collect and attach the server logs too.
SAP ADMIN
SAP Experts community Home
Databases Opertating Systems SAP SAP Admin SAP BASIS SAP Portal SAP Security SAP Solman
SAP Video Tutorials SAP XI/PI
Uncategorized
Search
2012-7 5
Monitoring Background Jobs with CCMS Category: Uncategorized | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Monitoring Background Jobs with CCMS
Prerequisites
Confirm that SAPConnect (transaction SCOT) is configured correctly for both email and paging in client 000 of the monitoring system.
Background Job Failure Notification Configuration
To allow for the notification of an individual or group when a certain job does not complete successfully, additional setup is required before the job monitor can be configured.
First, make sure that a distribution list with the contact information for the individuals or groups which will require notification has been created in client 000 of the monitoring system (for information on creating SAP distribution lists see section Creating a Shared Distribution List).
Next, if an appropriate auto-response method has not yet been defined in CCMS one will need to be created. To do so, log on to the monitoring system and call transaction RZ21. In
the Methodssection, select the Method definitions radio button and click Display overview.
In the resulting list, select a method which already performs the desired function (ex.
zBT_ar_email_dl_DL_EMAIL for emailing or zBT_ar_page_dl_DL_PAGE for paging) and click the copy button.
In the resulting dialog, specify a name for the new method and confirm the copy by clicking the green checkmark.
zBT_<method type>_<notif type>_<contact type>_<contact>
Example: zBT_ar_email_dl_CCMS_AR_EM01
Method Type ar Auto-Reaction Method
Notif Type email Method sends an email Contact Type dl Notify a distribution list Contact CCMS_AR_EM01 Dist-List CCMS_AR_EM01
The newly created method is now displayed. Enter change mode and change the description for the method to an appropriate value.
On the Parameters tab and set the SENDER to a SAP user in client 000 which has an email address maintained in its user master record. For RECIPIENT enter the name of the appropriate distribution list and for RECIPIENT-TYPE enter C.
On the Release tab, check the Auto-Reaction Method checkbox to classify the new method.
Save the new auto-reaction method by clicking the save button. The new auto-reaction method has been created and is ready for use.
Add the job to be monitored to CCMS
Before a background job can be monitored by CCMS, the job name needs to be entered in table ALBTCMON. To do this, log on to the system on which the background job which needs to be monitored is scheduled and call transaction SE16. Enter table ALBTCMON and press <Enter>
On the selection screen, just click Execute to display all of the entries in the table. To add a new row, select a row which already exists and choose the menu option Table entry -> Create with Template.
For the new entry confirm that the correct system ID is displayed and enter the name of the background job which is to be monitored. To save the new entry, click the save button.
The background job will now show up in CCMS as available for monitoring after the next system restart. To make the job available for monitoring without a system restart, follow the
instructions contained in the section Restarting the Local System Monitoring Segment.
Configuring the New Monitor
Once the above steps have been completed, you are ready to configure monitoring for the job in CCMS. To start, call transaction RZ20 in the monitoring system. Activate the CCMS
maintenance functions by selecting the menu option Extras -> Activate maintenance function.
Expand the CCMS monitor sets tree until the appropriate monitor set is displayed.
Select the monitor set to which the new job should be added by single clicking on it and press the change button.
The Edit monitor definition screen is displayed. Expand the structure to locate the new job which is to be added. The job should be in the structure under Selectable MTE -> <SID> -> Background -> Background Job Monitoring
To add the job to the monitor set, expand the node with the name of the background job and select the checkbox next to the line Status. Save the changed monitor set by clicking the save button.
After saving, you will be returned to the main screen of RZ20.
Now that the job has been added to the correct monitor set the appropriate auto-reaction method needs to be associated with it. To do this, from the main screen in RZ20, double-click on the monitor set to which the job was added. A list of all jobs which are included in that monitor set will be displayed. Select the checkbox next to the newly added job and click the Propertiesbutton.
The properties screen of the background job monitor are displayed. Select the Methods tab and click the Method assignment button in the Methods effective for MTE nodes section.
The resulting screen displays the methods which are currently assigned to the job monitor. Enter change mode and select the Auto-reaction tab. In the Method
allocation section, select theMethod name radio button and enter the name of the method which was created earlier.
Save the method assignment and the monitor setup is now complete.
Note: when backing out of the method assignment screen immediately after adding the auto-reaction method the method association will not be displayed even though it exists. Back all the way out of the transaction and when you go back in, the auto-reaction method will be visible.
Confirming Open CCMS Alerts
After a background job has been set up for monitoring in CCMS, whenever the job fails a CCMS alert will be opened and the appropriate individuals will be notified via the auto-reaction method.
When a notification of job failure is received, the recipient should then confirm the open alert in CCMS to acknowledge awareness of the job failure.
To confirm an open alert in CCMS, log on to the system/client in which the job failed and call transaction RZ20. Drill down to the appropriate monitor set and select it by double-clicking.
A list of all jobs which belong to that monitor set are displayed. Select the checkbox next to the job for which the alert was received and click the Open alerts button.
The display now shows all jobs and whether they have open (unconfirmed) alerts. To display or complete the alerts for a particular job, select the checkbox next to the job name and click theDisplay alerts button.
To complete the alert, select box to the left of the alert line and click the Complete alerts button.
Upon completion, the alert should be removed from the screen and the open alerts branch for the job in the monitor set will now be green, indicating that there are no open alerts.
Restarting the Local System Monitoring Segment
Whenever a new job is added to table ALBTCMON for monitoring it will not immediately
available for monitoring in CCMS. To make the job available for immediate monitoring, without a system restart, you can manually restart the Monitoring Segment (WARNING: Manually
restarting the segment will also restart all CCMS data collection methods for the selected segment). To restart the local system monitoring segment, call transaction RZ21 and select the
menu optionTechnical infrastructure -> Display Topology
In the Display Technical Topology screen, enter into change mode and select the Local
Segmentstab. Select the line for the Appl. Server segment which should be restarted and click the Reset Segment in “WARMUP” Status. Confirm any informational messages which are displayed and the monitoring segment will be restarted.
Upon successful restart of the monitoring segment, all background jobs in table ALBTCMON will be immediately available for monitoring.
Creating a Shared Distribution List
In order to send an auto-reaction email to a group of users or send an auto-reaction page to anybody a SAP Business Workplace distribution list is required.
To create a distribution list, log on to client 000 in the monitoring system and call transaction SBWP. From the main screen, click the Distribution lists button.
In the resulting screen, to create a new distribution list, click the Create button.
Give the new distribution list a name and enter an appropriate title. In the Features section, select the drop-down help for the Folder field.
In the resulting pop-up box, enter the same name that was entered for the distribution list in theFolder name field and the title of the distribution list in the Folder title field. Make sure that theShared radio button is selected and click the Create folder button.
Confirm that the values are correct for the folder to be created and click the green checkmark.
Confirm the folder selection dialog by clicking the green checkmark.
Select the Distr. list content tab for the new distribution list and list enter all recipients which should receive the auto-reaction notification as well as the recipient type and click the save button to create the list.
2012-6
29
Transport Guide
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Tips for Different SAP Objects
Question: How can I transport certain SAP objects?
Here are tips for different objects:
LSMW: There are 2 ways for transporting LSMW data from a system to another.
1. Export/import this method gives you the opportunity to select the subprojects or objects you want to transfer. LSMW -> Extras -> Export project
2. Transport request with this method, you can transport a LSMW project in full (you can not select the objects you want). With this method, the project will be transported as any other SAP object in a transport order. LSMW -> Extras -> Create change request
Program variants
If you have several program variants in a development system that you want to transport, use the following method to transport them: Execute program ‘RSTRANSP’ (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot).
Layout In some transactions, one can save layout of the screen (sort, filter, … criteria).
These layouts can be transported: In the required transaction, when your layouts have been saved, go to Settings -> Layout -> Layout Management. Select the desired layouts and go to Layout -> Transport… There you can add your layouts in existing TO or create a new one.
Database data
In some unusual cases, you might have to transport data of a SAP table. Go to transaction SE16, select your entries and go to Table entry -> Transport entries. It’s only possible for some
tables… If you cannot do it that way,you have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list.
Go in modification mode and add a new line with:
PgmID = R3TR Obj = TABU Object name = Name of your table
Double-click on the created line and, depending on your need, put ‘*’ in the key field or double-click on it and select the key you need to transport.
Queries
Queries, datasets and user groups can be exported/imported between the systems using the ProgramRSAQR3TR.
Report template (ALV variants)
There is a button or somewhere in the menu Change/Select/Save/Manage Layout. Go to Manage Layout, than Layout menu/ Transport.
SAPSCRIPT Files Transport
Use the program RSTXSCRP to upload and Download the SAPSCRIPT files to different systems
Transport SAPSCRIPT
Use the Program RSWBO052 to create the Transport Request for a SAPSCRIPT, In the Selection screen of the program, give R3TR – FORM – Give the Form name and press Execute button, it will ask the Development Class and the transport Request No.
Standard texts
Standard texts used in SAPScript(created with transaction SO10) can be included in transport orders. You have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list. Go in modification mode and add a new line with:
PgmID = R3TR Obj = TEXT Object name = TEXT,,ST,
Example : R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,F
Database tables, that contains the Transport Requests
List of tables pertaining to Transport Requests:
TABNAME Description
E070 Change & Transport System: Header of Requests/Tasks E070A Change & Transport System: Attributes of a Request E070C CTS: Source/Target Client of Requests/Tasks
E070CREATE Change & Transport System: Creation Date of Request E070CTV Generated Table for View E070CTV
E070DEP Change & Transport System: Dependencies of Requests E070L CTS: Index for Assigning Numbers to Requests/Tasks E070M CTS: Target Package/Layer for Requests
E070TC Help Table for E070 for Client-Specific Imports E070USE Use of Current Requests by Users
E070V Generated Table for View E070V
E071 Change & Transport System: Object Entries of Requests/Tasks E071C Change & Transport System: Client-Specific Lock Flag
E071E Lang. Transport: Positive List for Generic Object Selection E071K Change & Transport System: Key Entries of Requests/Tasks E071KC Change & Transport System: Key Entries of Requests/Tasks E071KF Change & Transport System: Nametab Info. on (CHAR)Key Fields E071KFINI Change & Transport System: Nametab Info. on (CHAR)Key Fields E071K_30 Change & Transport System: Key Entries of Requests/Tasks E071K_KEY E071K Key Fields
E071S System-Specific Import Status of Objects E071V Generated Table for View E071V
E07T_OLD E07T Before TRKORR Extension
2012-6
23
Installing SAP R/3 Application server on Linux ..
Category: SAP BASIS | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on email
Installing SAP R/3 Application server on Linux
In this article, I will give you step by step for installation of application server system SAP R / 3 using the Linux OS. Why use Linux? Instead better use Windows? There are some things that a consideration to me why using Linux include:
1. Database Instance that will be used is Oracle with a platform AIX (IBM’s proprietary UNIX). Between AIX and Linux, UNIX machines are equally so compatibility will be more awake than using Windows.
2. Linux is free and open source. By nature, I was much easier to perform tuning and search for references on the Internet.
3. Communication between Linux and AIX will use NFS, while Windows and AIX will use SAMBA.
4. Linux machine is more stable, reliable, and most importantly the virus-immune.
5. Linux is also less expensive in terms of maintenance, hardware requirements, compared to using Windows (must have a license) and AIX (in terms of licensing and hardware). Selection of Linux distributions that will be used freely. I prefer the distro that can use the concept of LVM (Logical Volume Management) so I can make a logical volume space
maintenance easier. I will try to explain using Redhat machine. I personally have tried to use SuSE as well. The main difference between them is the problem of the default file system used. Redhat uses ext3, while SuSE using reiserfs. Excellence ext3 and reiserfs is the ability to manage the logical volume size online.So we can easily increase the size of logical volumes without having to unmount the logical volume.We start, yes … 1. OS InstallationWhen the OS
installation, prepare a sufficient partition for the installation of SAP. The table on the following attachment (Disk) The following will give an explanation setting partitions using LVM. 2.
Installing the Central InstanceSince we will use an existing Database Instance on AIX 64 bit machine, then we have to install the Central Instance. Installing the Central Instance package in Linux is to get the executable files from the SAP kernel for Linux. Set environment needed to run sapinst among others:LD_LIBRARY_PATH = / sapmnt / [SID] / exeSAPINST_JRE_HOME = / opt / [location of java runtime environment]DISPLAY = [IP_Address of Windows Client]: 0.0umask = 22 To test, run the xclock command on the console. If an analog clock image, it means that environment is set correctly. If not appear, review the value of each environment variable you.
Choose Install Central Instance.
Fill in the information to the SAP System ID (SAPSID) and Instance Number.Customize with existing information on the Database Instance on AIX.
Let the information by default. This we do because this server will only be used asapplication servers.
Make sure that this directory is exist.
Make sure the correct information Database Schema. And do not forget the type ofdatabase server is running on AIX is 64 bits.
Information about the group sapsys. Noteworthy is the Group ID must match the Group ID on the AIX machine (as a database server).
Information about the group dba. Noteworthy is the Group ID must match the Group IDon the AIX machine (as a database server).
Information about the group shift gears. Noteworthy is the Group ID must match the Group ID on the AIX machine (as a database server).
Information about the user [sid] adm. Must be considered is the User ID andpassword must be the same as your User ID and password on AIX machine.
Information about the user ora [sid]. Must be considered is the User ID and passwordmust be the same as your User ID and password on AIX machines.
Note the directory listing above. These directories must exist. If not exist, create itnow!. The directory must exist is / usr / sap, / usr / sap / trans, / sapmnt, / oracle, /oracle / [SID] / 920_64.
You must indicate the location of the SAP Kernel for Linux is available. You should be ready.
Information extraction of Oracle Client. Remove the check mark. We will not installOracle Client now.
Information on ports used by SAP applications. The following ports should not beused by other applications, which is 36 [system number], 33 [system number], 32[system number], 47 [system number], and 48 [system number]. Please edit the file /etc / services.
Information listener name and port used by the listener. Make sure the port is not usedby other applications.
Show location IGS_SOFT.
Summary information on the Central Instance installation. Check back and you stillcan click the back button if there is not yet appropriate.
Installing the central instance is running.
Congratulations!! Installing the central instance successfully. We’re already in half way.Please break before … enjoy hot coffee and fried bananas you …:)
3. Installing Dialog Instance
Set environment needed to run sapinst among others:
LD_LIBRARY_PATH = / sapmnt / [SID] / exe SAPINST_JRE_HOME = / opt / [location of java runtime environment] DISPLAY = [IP_Address of Windows Client]: 0.0 umask = 22
To test, run the xclock command on the console. If an analog clock image, it means that
environment is set correctly. If not appear, review the value of each environment variable you. Make sure the machine Linux and AIX machines know each other. Perform the addition of the IP Address and hostname Linux on AIX machines and vice versa.
From the AIX machine via NFS, shared directory / sapmnt / [SID] / global and /sapmnt / [SID] / profile. From the Linux machine, mount the directory with the samemount point.
Information about the Central Instance. Remember! instance number and instanceinformation are hosted on the AIX machine.
Information Database ID (DBSID) and Database Host.
Choose No if you do not use LDAP LDAP on the network.
Note the type of information Database Schema and Database servers. Do not forgetthat the database server that we use is 64 bits.
Note the directory listing above. These directories must exist. If not exist, create itnow!. The directory must exist is / usr / sap, / usr / sap / trans, / sapmnt, / oracle, /oracle / [SID] / 920_64.
You must indicate the location of the SAP Kernel for Linux is available. You should be ready.
Information used ports in the SAP. Should have been prepared at the time ofinstallation of the Central Instance.
Location IGS_SOFT.
Installing Dialog Instance is running.
From the AIX machine, change the first permissions recursively to 777, the command# chmod-R / sapmnt / [SID] / profile. Continue the installation until it met the error again.
Errors occur because the permissions on the directory NFS / sapmnt / [SID] / profileon AIX machines.
Restore permissions to its original position. Use the following commands in succession: # chmod-R 644 profile, # chmod 755 profile.
This error is a bug from SAP. Please edit the file keybd.xml. Search keyword”ERROR” and change it to OK. Save, then run back to the old installation.
