Sap Basis Activities

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. Heres 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
Category: SAP BASIS | No Comments

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
and enter value for minimum age (in days) text box.
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

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,
youll 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 doesnt 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:
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 arent 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
SAP Java monitoring Check list
Category: SAP Portal | No Comments

email
SAP Java monitoring Check list
This article answers the following queries :
How to perform daily monitoring of Java stack in SAP ?
What are the daily checks for Java applications of 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 :
1. Checking the java stack/portal accessibility

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:
For example:
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
Organizational Levels
Category: SAP Security, Uncategorized | No Comments

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
Central User Administration in SAP (CUA)
Category: SAP Security | No Comments

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 RFCs 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 RFCs
Save your entries now result screen will appear
If you expand the nodes for
the individual systems, you normally see the following messages 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

email
If youve got a website thats 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:
sudo crontab -l
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 thats a bit unclear. Lets 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
Heres 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
What if youd want to run something every 10 minutes? Well you could do this:
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 users mailbox (root in
this case). But its prettier if the output is saved in a separate logfile. Heres how:
*/10 * * * * /bin/execute/this/script.sh 2>&1 >> /var/log/script_output.log
Explained
Linux can report on different levels. Theres 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:
2>&1
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 wed like to to append:
>> /var/log/script_output.log
Mailing the crontab output
By default cron saves the output in the users 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="yourname@yourdomain.com"
Mailing the crontab output of just one cronjob
If youd rather receive only one cronjobs 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"

yourname@yourdomain.com
Trashing the crontab output
Now thats 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
Enterprise Portal Administration

email
Enterprise Portal Administration

What is single sign on (SSO)
Once a user has authenticated to the SAP EP, he doesnt 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 gets
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 doesnt 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
Maintain the profile parameters for single sign on in RZ10
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..

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.
Solution
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.
2. 2. Check if database drivers are correctly set in the instance profiles.

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
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 versions 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.
DB corruption: Check the database consistency.

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
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..

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
systems 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 systems
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
Monitoring Background Jobs with CCMS
Category: Uncategorized | No Comments

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.
Recommended naming convention for auto-reaction methods:

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

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. Its 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 Change & Transport System: Short Texts for Requests/Tasks

E07T_OLD E07T Before TRKORR Extension
2012-6
23
Installing SAP R/3 Application server on Linux ..

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 (IBMs 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.
Go to the directory sapinst. Sapinst Run command on the console.

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.
Fill in the information database ID (DBSID) and Database Host.

Let the information by default. This we do because this server will only be used asapplication
servers.
Choose No if you do not use LDAP LDAP facilities on your network.

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. Were 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.
Screen installation election. Select Non-Unicode_Install Dialog Instance.

Information about the Central Instance. Remember! instance number and instanceinformation
are hosted on the AIX machine.
Information Database ID (DBSID) and Database Host.
Information hosted instance of parameters. Leave the default.

Choose No if you do not use LDAP LDAP on the network.
Location SAP Mount Directory is on / sapmnt. Make sure this directory exists.
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.
Now is the time for us to install Oracle Client. Tick the option extract oracle client.
Information used ports in the SAP. Should have been prepared at the time ofinstallation of the
Central Instance.
Setting name of the listener and the listener port name.

Location IGS_SOFT.
Installation Summary Dialog Instance.

Installing Dialog Instance is running.
Error will be out due to lack of permissions on the directory NFS / sapmnt / [SID] /profile.
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 keywordERROR and
change it to OK. Save, then run back to the old installation.
Congratulations! Dialog Instance installation has been completed.
4. Next run the dialog instance. Previous sure central instance and database server is running
on the AIX machine.
Now we already have a Linux application servers are cheap, reliable and stable.There is more to
be dituning, later we went on again.
2012-6
14
Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 5 on 32-bit x86

email
References
Applies to:
Oracle Server Enterprise Edition Version: 11.2.0.0
Linux x86
Red Hat Advanced Server
Oracle Enterprise Linux 4.0
Purpose:
This note explains the requirements that need to be met for a successful installation of RDBMS
release 11.2.0.x (a 1 DVD set) on RedHat 5.2 or greater, 32-bit (x86).
You can download the 11.2.0.1 from following URL. But you require a valid OTN account for
download.
http://www.oracle.com/technology/software/products/database/oracle11g/112010_linuxsoft.
html
Scope and Application:
This procedure is meant for those planning/trying to install Oracle Server 11.2.0.1.0 (or above)
on Red Hat Server 5.2 (or greater) on the 32-bit (x86) platform. Since it is the expressed goal to
keep Oracle Enterprise Linuxfunctionally IDENTICAL to RHEL, this NOTE is also completely
applicable to 32-bit (x86) OEL 5.2 (or greater)
Requirements for Installing 32-bit Oracle 11gR2 RDBMS on RHEL or OEL 5.2 (or greater) 32-bit
(x86)
I. Hardware:
===========
1. Minimum Hardware Requirements
a.) At least 1.0 Gb (1024 MB) of physical RAM
b.) Swap disk space proportional to the systems physical memory as follows:
RAM Swap Space

1024 Mb to 2048 Mb 1.5 x RAM
2049 Mb to 16 Gb 1 x RAM
greater than 16 Gb 16 Gb
c.) 1024 Mb of disk space (and less than 2Tb of disk space) in the /tmp directory.
d.) approximately 4 Gb of local disk space for the database software.
e.) approximately 1.7 Gb of disk space for a preconfigured database that uses file system
storage (optional)
II. Software:
============
1. As is specified in section 1.3.2 of the Oracle Database Installation Guide for 11gR2 on Linux
(part number E10840-02), Oracle recommends that you install the Linux operating system with
the default software packages (RPMs) and do not customize the RPMs during installation.
2. Red Hat Enterprise Linux Server 5.2 (or greater), which is Kernel 2.6.18-92 or newer.
3. Required OS Components (per Release Notes, and Install Guide)

a.) The exact version number details of this list are based upon 32-bit (x86) RHEL Server 5.2.
When a higher update level is used, the RPM release numbers (such as 4.1.2-42) may be
slightly higher (such as 4.1.2-57 or 4.1.3-10). Since update 2 and greater of RHEL 5 are
certified, this is fine so long as you are still using 32-bit Linux (x86) RHEL Server 5 RPMs.
b.) Some of the Install Guide requirements will already be present from the default-RPMs
foundation of Linux that you started with:
1.) binutils-2.17.50.0.6-2.el5
2.) compat-libstdc++-33-3.2.3-61
3.) elfutils-libelf-0.125-3.el5
4.) glibc-2.5-24
5.) glibc-common-2.5-12
6.) ksh-20060214-1.7
7.) libaio-0.3.106
8.) libgcc-4.1.2-42.el5
9.) libstdc++-4.1.2-42
10.) make-3.81-1.1
c.) The remaining Install Guide requirements will have to be installed:

1.) elfutils-libelf-devel-0.125-3.el5.i386.rpm
a.) requires elfutils-libelf-devel-static-0.125-3.el5.i386.rpm as a prerequisite.
b.) elfutils-libelf-devel and elfutils-libelf-devel-static each depend upon the other.
Therefore, they must be installed together, in one (1) rpm -ivh command as follows:
rpm -ivh elfutils-libelf-devel-0.125-3.el5.i386.rpm elfutils-libelf-devel-static-0.125-
3.el5.i386.rpm
2.) kernel-headers-2.6.18-92.el5.i386.rpm
3.) glibc-headers-2.5-24.i386.rpm
4.) glibc-devel-2.5-24.i386.rpm
5.) libstdc++-devel-4.1.2-42.el5.i386.rpm
6.) libgomp-4.1.2-42.el5.i386.rpm
7.) gcc-4.1.2-42.el5.i386.rpm
8.) gcc-c++-4.1.2-42.el5.i386.rpm
9.) libaio-devel-0.3.106-3.2.i386.rpm
10.) sysstat-7.0.2-1.el5.i386.rpm
11.) unixODBC-2.2.11-7.1.i386.rpm
12.) unixODBC-devel-2.2.11-7.1.i386.rpm
4. Additional Required OS Components (per the runInstaller OUI)

a.) intentionally blank
5. Additional Required OS Components (per this NOTE)

a.) Please do not rush, skip, or minimize this critical step. This list is based upon a default-
RPMs installation of 32-bit (x86) RHEL Server 5. Additional RPMs (beyond anything known to
Oracle) may be needed if a less-than-default-RPMs installation of 32-bit (x86) RHEL Server 5 is
performed. For more information, please refer to Note 376183.1, Defining a default RPMs
installation of the RHEL OS
b.) intentionally blank
6. Oracle Global Customer Support has noticed a recent trend with install problems that
originates from installing too many RPMs. For example:
a.) installing your own JDK version (prior to beginning the Oracle Software runInstaller) is
not needed on Linux, and is not recommended on Linux. A pre-existing JDK often interferes
with the correct JDK that the Linux Oracle Software runInstaller will place and use.
b.) installing more than the required version of the gcc / g++ RPMs often leads to accidentally
using (aka enabling or activating) the incorrect one. If you have multiple RDBMS versions
installed on the same Linux machine, then you will likely have to manage multiple versions of
gcc /g++ . For more information, please see Note 444084.1, Multiple gcc / g++ Versions in
Linux
7. All of the RPMs in section II. are on the Red Hat Enterprise Linux 5 32-bit (x86) distribution
media.
Create Oracle user and groups
# groupadd oinstall
# groupadd dba
# useradd -g oinstall -G dba oracle
# passwd oracle
Create the required directories for Oracle database and change the ownership
For example
# mkdir -p /u01/app/oracle
# chown -R oracle:oinstall /u01/app/oracle
III. Environment:
================
1. Modify your kernel settings in /etc/sysctl.conf (RedHat) as follows. If the current value for
any parameter is higher than the value listed in this table, do not change the value of that
parameter. Range values (such as net.ipv4.ip_local_port_range) must match exactly.
kernel.shmall = physical RAM size / pagesize For most systems, this will be the value
2097152. See Note 301830.1 for more information.
kernel.shmmax = 1/2 of physical RAM, but not greater than 4GB. This would be the value
2147483648 for a system with 4Gb of physical RAM.
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 512 x processes (for example 6815744 for 13312 processes)
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
2. To activate these new settings into the running kernel space, run the sysctl p command
as root.
3. Set Shell Limits for the oracle User. Assuming that the oracle Unix user will perform the
installation, do the following:
a.) Add the following settings to /etc/security/limits.conf

oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
b.) Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:
session required pam_limits.so
c.) Add the following lines to /etc/profile:

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -u 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
4. The gcc-4.1.2 and gcc-c++-4.1.2 RPM items above will ensure that the correct gcc / g++
versions are installed. It is also required that you ensure that these correct gcc / g++ versions
are active, and in-use. Ensure that the commands gcc version and g++ version each
return 4.1.x.
5. The hostname command should return the fully qualified hostname as shown
below:
% hostname
hostname.domainname
6. If any Java packages are installed on the system, unset the Java environment variables, for
example JAVA_HOME.
7. The oracle account used to install Oracle 11.2.0.1, should not have the Oracle install related
variables set by default. For example setting ORACLE_HOME, PATH, LD_LIBRARY_PATH to
include Oracle binaries in .profile, .login file and /etc/profile.d should be completely avoided.
a.) Setting $ORACLE_BASE (not $ORACLE_HOME) is recommended, since it eases a few
prompts in the OUI runInstaller tool.
b.) following the succesful install, it is recommended to set $ORACLE_HOME, and to set
$PATH to include $ORACLE_HOME/bin at the beginning of the $PATH string.
8. By default, RHEL 5 x86 Linux is installed with SELinux as enforcing. This is fine for the
11gR2 installation process. However, to subsequently run sqlplus, switch SELinux to the
Permissive mode.
9. Log in as Oracle user and start the installation as follows:

./runInstaller
a.) It is best practice not to use any form of su to start the runInstaller, in order to avoid
potential display-related problems.
b.) When performing the 11.2.0.1 installation, make sure to use the runInstaller version
that comes with 11.2.0.1 software.
c.) When performing any subsequent 11.2.0.x patchset, make sure to use the runInstaller
version that comes with the patchset.
ADDITIONAL NOTES
-
1. Supported distributions of the 32-bit (x86) Linux OS can run on on AMD64/EM64T and Intel
Processor Chips that adhere to the x86_64 architecture
a.) Oracle 32-bit running on AMD64/EM64T with 32-bit OS is supported, and is covered by this
NOTE.
b.) Oracle 32-bit running on AMD64/EM64T with 64-bit OS is not certified and is not
supported.
2. Asynchronous I/O on ext2 and ext3 file systems is supported if your scsi/fc driver supports
that functionality.
3. No extra patch is required for the DIRECTIO support for x86.
4. No LD_ASSUME_KERNEL value should be used with the 11gR2 product.
You might also like:
2012-6
14
Manual Upgrade Database from Oracle 10.2.0.4 to Oracle 11.2.0.2

email
Introduction:
This document applies for Oracle 10.2.0.4 Ent. Edition on Red Hat Linux 5. This document will
guide you how to upgrade Oracle 10.2.0.4 Ent Edition single Instance to Oracle 11.2.0.2 Ent.
Edition.
The following topics guide you through the process of performing a manual upgrade. They
assume that you have previously run the Pre-Upgrade Information Tool
Backing up the Database
Preparing the New Oracle Home

Manually Upgrading the Database
Troubleshooting the Upgrade
Cancelling the Upgrade
Backing Up the Database
After running the Pre-Upgrade Information Tool and cleanly shutting down the instance, Oracle
recommends that you back up the database as described in this section. If you encounter
problems with the upgrade and wish to abandon the upgrade completely, then you must
restore the database from this backup. Therefore, Oracle recommends that you back up your
database now as a precaution.
There are two ways to take backup:
1. Cold Backup
2. Rman Backup
Cold Backup:
Copy all the datafiles, control files and Redo log files to a different location.
Rman Backup:
Sign on to RMAN:
1. rman target / nocatalog
2. Issue the following RMAN commands:
RUN
ALLOCATE CHANNEL chan_name TYPE DISK;
BACKUP DATABASE FORMAT some_backup_directory%U TAG before_upgrade;
BACKUP CURRENT CONTROLFILE FORMAT controlfile location and name;
}
Preparing the New Oracle Home
After backing up the database to be upgraded, prepare the new Oracle home in a new location.
Do this for any release of Oracle Database for which you are upgrading, whether the database
is release 11.2 or earlier.
To prepare the new Oracle home
1. Copy configuration files from the Oracle home of the database being upgraded to the
new Oracle Database 11gRelease 2 (11.2) Oracle home:
2. If your parameter file resides within the old environments Oracle home, then copy it to the
new Oracle home. By default, Oracle looks for the parameter file in the ORACLE_HOME/dbs
directory on Linux or UNIX platforms. The parameter file can reside anywhere you wish, but it
should not reside in the old environments Oracle home after you upgrade to Oracle Database
11g Release 2 (11.2).
Note: It might be necessary to create a text initialization parameter file (PFILE) from the
server parameter file (SPFILE) so that you can edit the initialization parameters.
Sql> CREATE pfile FROM spfile;
3. If you have a password file that resides within the old environments Oracle home, then
move or copy the password file to the new Oracle Database 11g Release 2 (11.2) Oracle
home.The name and location of the password file are operating system-specific. On Linux or
UNIX platforms, the default password file is orapwsid, located in the ORACLE_HOME/dbs
directory. In both cases, sid is your Oracle instance ID.
4. The Pre-Upgrade Information Tool displays any deprecated parameters and obsolete
parameters it finds in the Deprecated Parameters and Obsolete Parameters sections. Make
sure the COMPATIBLE initialization parameter is properly set for Oracle Database 11g Release 2
(11.2). The Pre-Upgrade Information Tool displays a warning in the Database section if
COMPATIBLE is not properly set.
5. Adjust the values of the initialization parameters to at least the minimum values indicated
by the Pre-Upgrade Information Tool.
6. Make sure all path names in the parameter file are fully specified. You should not have
relative path names in the parameter file.
7. Make sure you save all of the files you modified after making these adjustments.
Manually Upgrading the Database
After preparing the new Oracle home, you are ready to proceed with the manual upgrade.
To manually upgrade the database
Shut down the instance:
Sql> SHUTDOWN IMMEDIATE
On Linux or UNIX operating system perform the following checks:
Your ORACLE_SID is set correctly. The oratab file points to your Oracle Database 11g Release 2
(11.2) Oracle home
The following environment variables should point to the Oracle Database 11g Release 2
(11.2) directories:
ORACLE_HOME, PATH
Any scripts that clients use to set the ORACLE_HOME value must point to the new Oracle home.
Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2) Oracle home
directory.
At a system prompt, change to the ORACLE_HOME/rdbms/admin directory.
[oracle@ ~]$ cd $ ORACLE_HOME/rdbms/admin
Start SQL*Plus.
[oracle@ ~]$ export ORACLE_SID=[instance_name]

[oracle@ ~]$ sqlplus sys as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Fri Apr 29 10:29:11 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter password:
Start the instance by issuing the following command:
Sql> STARTUP UPGRADE
ORACLE instance started.

Total System Global Area 1000189952 bytes
Fixed Size 1337492 bytes
Variable Size 708839276 bytes
Database Buffers 285212672 bytes
Redo Buffers 4800512 bytes
Database mounted.
Database opened.
Note: The UPGRADE keyword enables you to open a database based on an earlier Oracle
Database release. It also restricts logons to AS SYSDBA sessions, disables system triggers, and
performs additional operations that prepare the environment for the upgrade. You might be
required to use the PFILE option to specify the location of your initialization parameter file.
Once the database is started in upgrade mode, only queries on fixed views execute without
errors until after the catupgrd.sql script is run. Before running catupgrd.sql, queries on any
other view or the use of PL/SQL returns an error.
Common Error & Solution for Database Upgrade:
The following are common errors that might occur when attempting to start the new Oracle
Database 11g Release 2 (11.2) database. Some of these errors are written to the alert log and
not to your session. If you receive any of these errors, then issue the SHUTDOWN ABORT
command to shut down the database and correct the problem.
ORA-00401: the value for parameter compatible is not supported by this release
Solution: The COMPATIBLE initialization parameter is set to a value less than 10.0.0.
ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE
Solution: The CLUSTER_DATABASE initialization parameter is set to TRUE instead of FALSE.
ORA-39700: database must be opened with UPGRADE option
Solution: The STARTUP command was issued without the UPGRADE keyword.
ORA-00336: log file size xxxx blocks is less than minimum 8192 blocks
Solution: A redo log file size is less than 4 MB:

If errors appear listing obsolete initialization parameters, then make a note of the obsolete
initialization parameters and continue with the upgrade. Remove the obsolete initialization
parameters the next time you shut down the database.
Sql> SPOOL upgrade.log
Run the Pre-Upgrade Information Tool by executing the utlu112i.sql script:
Sql> @utlu112i.sql
Run the catupgrd.sql script:
Sql> @catupgrd.sql
Note: If you did not run the Pre-Upgrade Information Tool, the catupgrd.sql script
terminates with one of the following errors:
RA-00942: table or view does not exist
ORA-00904: TZ_VERSION: invalid identifier
ORA-01722: invalid number
If you receive any of these errors, issue the SHUTDOWN ABORT statement, revert to the
original Oracle home directory, and run the Pre-Upgrade Information Tool (utlu112i.sql)
The catupgrd.sql script determines which upgrade scripts must be run, runs them, and then
shuts down the database. You must run the script in the Oracle Database 11g Release 2 (11.2)
environment.
Restart the instance to reinitialize the system parameters for normal operation.
Sql> STARTUP
This restart, following the database shutdown performed as part of the catupgrd.sql script,
flushes all caches, clears buffers, and performs other housekeeping activities. These measures
are an important final step to ensure the integrity and consistency of the newly upgraded
Oracle Database software.
Note: If you encountered a message listing obsolete initialization parameters when you
started the database, then remove the obsolete initialization parameters from the parameter
file before restarting. If necessary, convert the SPFILE to a PFILE so you can edit the file to
delete parameters
Run utlu112s.sql, the Post-Upgrade Status Tool, which provides a summary of the upgrade at
the end of the spool log. You must run utlu112s.sql only immediately after running
catupgrd.sql. Run utlu112s.sql to display the results of the upgrade as follows:
Sql> @utlu112s.sql
If the Post-Upgrade Status Tool returns errors or shows components that are not VALID or not
the most recent release, then see Troubleshooting the Upgrade for more information.
Run utlrp.sql to recompile any remaining stored PL/SQL and Java code.
Sql> @utlrp.sql
Verify that all expected packages and classes are valid:
Sql> SELECT count(*) FROM dba_invalid_objects;
Sql> SELECT distinct object_name FROM dba_invalid_objects;
Note: If the pre-upgrade information tool detected INVALID objects and populated the
registry$sys_inv_objs and registry$nonsys_inv_objs tables, then execute
ORACLE_HOME/rdbms/admin/utluiobj.sql to display only those objects which are newly invalid
because of the upgrade process. The utluiobj.sql script only displays objects that are now
INVALID but which were VALID before the upgrade.
Exit SQL*Plus.
Your database is now upgraded to the new Oracle Database 11g release. You are ready to
complete the procedures described in Chapter 4, After Upgrading to the New Release.
WARNING:
If you retain the old Oracle software, then never start the upgraded database with the old
software. Only start the database with the executables in the new Oracle Database installation.
Also, before you remove the old Oracle environment, make sure you relocate any data files in
that environment to the new Oracle Database environment. See the Oracle Database
Administrators Guide for information about relocating data files.
About the Post-Upgrade Status Tool
The Post-Upgrade Status Tool, which is the utlu112s.sql script, displays the status of the
database components in the upgraded database and the time required to complete each
component upgrade. Any errors that occur during the upgrade are listed with each component
and must be addressed. The utlu112s.sql script must only be run immediately after catupgrd.sql
The Post-Upgrade Status Tool displays a report similar to the following output:
Oracle Database 11.2 Post-Upgrade Status Tool 10-18-2010 22:48:55
Component Status Version HH:MM:SS
Oracle Server. VALID 11.2.0.2.0 00:17:31
JServer JAVA
Virtual Machine. VALID 11.2.0.2.0 00:02:32
Oracle Application Express. VALID 3.2.1.00.12 00:23:25
Gathering Statistics. 00:05:12
Total Upgrade Time: 01:29:03
Note: Any time after utlrp.sql is run instead of using utl112s.sql to determine the STATUS of a
component, run this query:
SELECT COMP_NAME,VERSION,STATUS FROM DBA_REGISTRY;
This will return the most up-to-date information.
Troubleshooting the Upgrade:
This section explains what to do if something goes wrong with your upgrade. This section
contains the following topics:
Resource Limits
Edition Session Startup Error
Manual Workaround for ORA-01408
Running the DBMS_DST Package After Upgrade Can Result in ORA-01822

DBUA May Mark Invalid Components with an X Before Entire Upgrade is Done
Component Status
Rerunning the Upgrade
Resource Limits
If you run out of resources during the upgrade, then increase the resource allocation. After
increasing the resource allocation, you should perform a SHUTDOWN ABORT and restart the
instance (in UPGRADE mode) before rerunning the catupgrd.sql script or restarting DBUA.
The resources that generally require increases for a new Oracle Database release are as follows:
SYSTEM and SYSAUX tablespaces
Typically you receive one of the following messages during the upgrade if your SYSTEM
tablespace size is insufficient:
ORA-01650: unable to extend rollback segment string by string in tablespace string
ORA-01651: unable to extend save undo segment by string for tablespace string
ORA-01652: unable to extend temp segment by string in tablespace string
ORA-01653: unable to extend table string.string by string in tablespace string
ORA-01654: unable to extend index string.string by string in tablespace string
ORA-01655: unable to extend cluster string.string by string in tablespace string
To avoid these errors, set AUTOEXTEND ON MAXSIZE UNLIMITED for the SYSTEM and SYSAUX
tablespaces.
ORA-04031: unable to allocate string bytes of shared memory

(string,string,string,string)
You might require larger shared memory pool sizes in some cases. The error message indicates
which shared memory initialization parameter must be increased.
If you are using an undo tablespace, then be sure it is at least 400 MB.
Rerunning the Upgrade
You can rerun the upgrade with the catupgrd.sql script as described in the following steps.
To rerun the upgrade
1. Shut down the database as follows:
2. Sql> SHUTDOWN IMMEDIATE
3. Restart the database in UPGRADE mode:
4. Sql> STARTUP UPGRADE
5. Set the system to spool results to a log file for later verification of success:
6. Sql> SPOOL upgrade.log
7. Rerun catupgrd.sql:
Sql> @catupgrd.sql
Note: You can rerun the catupgrd.sql script as many times as necessary. The first time you run
the script, there should be no error messages returned. If you rerun the script, then the ORA-
00001 message is displayed. You can safely ignore this message.
If you completed the steps in Backing Up the Database to back up your database, then the
easiest way to cancel the upgrade is to restore that backup as described in the following
procedure.
To cancel the upgrade by restoring the previous backup
Restore Usingin RMAN:
1. Log in to the system as the owner of the Oracle home directory of the previous release.
2. Sign on to RMAN:
3. rman target / nocatalog
4. Issue the following RMAN commands:
5. STARTUP NOMOUNT
RUN
RESTORE CONTROLFILE FROM save_controlfile_location;
ALTER DATABASE MOUNT;
RESTORE DATABASE FROM TAG before_upgrade
ALTER DATABASE OPEN RESETLOGS;
Restore Using Cold Backup:
Copy database backup files to original location and database is restored.
2012-6
14
Step By Step Manual Oracle Database Upgrade to 11.2.0.2

email
Minimum Version of the database that can be directly upgraded to Oracle11g Release 2Source
Database Target Database
9.2.0.8 or higher 11.2.x
10.1.0.5 or higher 11.2.x
10.2.0.2 or higher 11.2.x
11.1.0.6 or higher 11.2.x
The following database version will require an indirect upgrade path.
Source Database > Upgrade Path for Target Database>Target Database

7.3.3 (or lower)> 7.3.4 > 9.2.0.8 ->11.2.x
8.0.5 (or lower)-> 8.0.6 > 9.2.0.8 ->11.2.x
8.1.7 (or lower)-> 8.1.7.4> 10.2.0.4->11.2.x
9.0.1.3 (or lower)-> 9.0.1.4 ->10.2.0.4->11.2.x
9.2.0.7(or lower)->9.2.0.8->11.2.x
Here I am upgrading my Oracle 10.2.0.4 database to Oracle 11.2.0.2
1. Copy Pre upgrade Information gathering Script:
Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2) Oracle
home directory.
Copy the Pre-Upgrade Information Tool (utlu112i.sql) and utltzuv2.sql from the Oracle
Database 11g Release 2 (11.2) ORACLE_HOME/rdbms/admin directory to a directory
outside of the Oracle home, such as the temporary directory on your system.
$ORACLE_HOME/rdbms/admin/utlu112i.sql
2. Execute Pre Upgrade Script:
Should be change to the directory where utlu112i.sql had been copied in the previous
step.
Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges.
Then run and spool the utlu112i.sql file. Please note that the database should be started
using the Source Oracle Home.
$ sqlplus / as sysdba
SQL> spool upgrade_info.log
SQL> @utlu112i.sql
SQL> spool off
SQL>
Check the spool file and examine the output of the upgrade information tool.3. Check for the
integrity of the source database:
Check for the integrity of the source database prior to starting the upgrade by downloading and
running dbupgdiag.sql script from below My Oracle Support article
Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)

(Avoid this step if dont have support access)
If the dbupgdiag.sql script reports any invalid objects, run
$ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the
database, until there is no change in the number of invalid objects.
$ cd $ORACLE_HOME/rdbms/admin
SQL> @utlrp.sql
After validating the invalid objects, re-run dbupgdiag.sql in the database once again and make
sure that everything is fine.
4. Check that National Characterset:
Check that National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 and AL16UTF16.select

value from NLS_DATABASE_PARAMETERS where parameter = NLS_NCHAR_CHARACTERSET;
If this is UTF8 or AL16UTF16 then no action is needed.

If is not UTF8 or AL16UTF16 then refer the following article
Note 276914.1 The National Character Set in Oracle 9i and 10g.
5. Optimizer Statistics:
When upgrading to Oracle Database 11g Release 2 (11.2), optimizer statistics are collected for
dictionary tables that lack statistics. This statistics collection can be time consuming for
databases with a large number of dictionary tables, but statistics gathering only occurs for
those tables that lack statistics or are significantly changed during the upgrade
$ sqlplus /as sysdbaSQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
6.Ensure that no files need media recovery:
Sql> SELECT * FROM v$recover_file;
7. Stop the listener for the database:

Make pfile from spfile;
$ lsnrctl stop
8. Suhtdown the Database:
Shutdown the database.
$ sqlplus /as sysdba

SQL> shutdown immediate;
9. Back Up the Database:1- Perform Cold Backup

(or)
2- Take a backup using RMAN
Connect to RMAN:rman target / nocatalog
RUN
{
ALLOCATE CHANNEL chan_name TYPE DISK;
BACKUP DATABASE FORMAT %U TAG before_upgrade;
BACKUP CURRENT CONTROLFILE TO ;
}
10 Backup and change pfile:
Make a backup of the init.ora file.

Comment out obsolete parameters
* The DIAGNOSTIC_DEST initialization parameter replaces the USER_DUMP_DEST,

BACKGROUND_DUMP_DEST.
Note: Once the Parameter file is modified as per your requirement, copy the file to
$ORACLE_HOME/dbs (11g Oracle Home )
11 Set Environment Variables:
If your operating system is UNIX then complete this step, else skip to next Step.1. Make sure
the following environment variables point to the Oracle 11g Release directories:
- ORACLE_BASE
- ORACLE_HOME
- PATH
$ export ORACLE_HOME=
$ export PATH=$ORACLE_HOME/bin:$PATH
$ export ORACLE_BASE=
Note : If ORACLE_BASE is not known, after setting Path towards 11g Oracle Home, execute
orabase, which will point the location of base.
$ orabase
/uo1/app/oracle
2. Update the oratab entry, to set the new ORACLE_HOME pointing towards ORCL and disable
automatic startup
Sample /etc/oratab#orcl:/opt/oracle/product/10.2/db_1:N
orcl:/opt/oracle/product/11.2/db_1:N
Note : After /etc/oratab is updated to have sid and Oracle Home (11.2), you can execute oraenv
(/usr/local/bin/oraenv) and set the environment. The input has to be the sid which is entered in
/etc/oratab against 11g home.
for Instance,[oracle@localhost ~]$ . oraenv

ORACLE_SID = [orcl] ? orcl
The Oracle base for ORACLE_HOME=/opt/oracle/product/11.2/db_1 is /u01/app/oracle
[oracle@localhost ~]$
12 Upgrade Database:
At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of

11gR2 Oracle Home.
$ cd $ORACLE_HOME/rdbms/admin
SQL> startup UPGRADE
Set the system to spool results to a log file for later verification after the upgrade is completed
and start the upgrade script.
SQL> set echo on

SQL> SPOOL upgrade.log
SQL> @catupgrd.sql
SQL> spool off
These measures are an important final step to ensure the integrity and consistency of the newly
upgraded Oracle Database software. Also, if you encountered a message listing obsolete
initialization parameters when you started the database for upgrade, then remove the obsolete
initialization parameters from the parameter file before restarting. If necessary, convert the
SPFILE to a PFILE so you can edit the file to delete parameters.
Post Upgrade Steps
13 Post Upgrade:
Start the database and run the Post-Upgrade Status Tool

$ORACLE_HOME/rdbms/admin/utlu112s.sql which provides a summary of the upgrade at the
end of the spool log. It displays the status of the database components in the upgraded
database and the time required to complete each component upgrade. Any errors that occur
during the upgrade are listed with each component and must be addressed
$ sqlplus /as sysdba

SQL> STARTUP
SQL> @utlu112s.sql
14 Recompile Invalid Objects:
This script can be run concurrently with utlrp.sql. Run utlrp.sql to recompile any remaining
stored PL/SQL and Java code in another session.
SQL> @utlrp.sql
15 Check for the integrity of the source database:
Check for the integrity of the upgraded database by running dbupgdiag.sql script from below
Metalink article
Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)
If the dbupgdiag.sql script reports any invalid objects, run

$ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the
database, until there is no change in the number of invalid objects.After validating the invalid
objects, re-run dbupgdiag.sql in the upgraded database once again and make sure that
everything is fine.
16 Configure & Start Listener.ora :Modify the listener.ora file:
For the upgraded instance(s) modify the ORACLE_HOME parameter to point to the new
ORACLE_HOME. Start the listener :
lsnrctl start
17 Crosscheck Environment Variables:

Set Environment Variables1. Make sure the following environment variables point to the Oracle
11g Release directories:
- ORACLE_BASE
- ORACLE_HOME
- PATH
Also check that your oratab file and any client scripts that set the value of ORACLE_HOME point
to the Oracle Database 11g Release 2 (11.2) home.
Note : If you are upgrading a cluster database, then perform these checks on all nodes in which
this cluster database has instances configured.
2. Modify /etc/oratab entry to use automatic startup
SID:ORACLE_HOME:YFor Instance,
orcl:/opt/oracle/product/11.2/db_1:Y
18 Spfile from Pfile:
Edit init.ora:- If you changed the CLUSTER_DATABASE parameter prior the upgrade set it back
to TRUE
- Migrate your initialization parameter file to a server parameter file.
Create a server parameter file with a initialization parameter file
SQL> create spfile from pfile;
This will create a spfile as a copy of the init.ora file located in $ORACLE_HOME/dbs (UNIX) &
%ORACLE_HOME%database (Windows).
19 Start the Database with spfile:
Shutdown the database:
Sql> shutdown immediate
Now start the database it will user spfile
Sql> startup
Check the Alert log file for any Error.

Database is ready to use now.
==============================================================================
=========================================
Upgrading 10g to 11g R 2 with DBUA
1. Install Oracle 11gR2 software only (enterprise or standard to match the source db. This blog
is on standard version. More on metalink note 870814.1).
2. In order to downgrade Oracle Enterprise Manager Database Control after upgrading to the
new Oracle Database 11g release save Database Control files and data before upgrade. The
emdwgrd utility resides in the ORACLE_HOME/bin directory in the new Oracle
Database 11g release.
3. Follow these steps to save your Database Control files and data:
1. Install the new Oracle Database 11g release.
This step is not required for an inplace patchset upgrade.
2. Set ORACLE_HOME to your old Oracle home.
This step is not required for an inplace patchset upgrade.
3. Set ORACLE_SID to the SID of the database being upgraded.
4. Set PATH, LD_LIBRARY_PATH, and SHLIB_PATH to point to the Oracle home
from which the database is being upgraded.
5. Go to the Oracle home of the new Oracle Database 11g release.

6. Execute one of the following:
if Single DB
emdwgrd -save -sid old_SID -path save_directory
for RAC
setenv EM_REMCP /usr/bin/scp
emdwgrd -save -cluster -sid old_SID -path save_directory
If the release 10g Oracle home is on a shared device, add -shared to the
previous command line.
create a TNS name entry in the 10g Oracle Home (network/admin) with the same name as the
SID before running the above command
[oracle@server110 std]$ emdwgrd -save -sid std1 -path /home/oracle/emdu
Enter sys password for database std1?
Mon Sep 14 19:14:24 2009 - Verify EM DB Control files ... pass
Mon Sep 14 19:14:24 2009 - Validating DB Connection to std1 ... pass
ENV var EM_REMCP not defined, check if rcp or scp is configured.
RCP = /usr/bin/rcp -rp, REMSH = /usr/bin/rsh
shared = 0
Mon Sep 14 19:14:28 2009 - Creating directory ... created
Mon Sep 14 19:14:29 2009 - Stopping DB Control ... stopped
Mon Sep 14 19:14:34 2009 - Saving DB Control files
... saved
Mon Sep 14 19:14:50 2009 - Recompiling invalid objects ... recompiled
Mon Sep 14 19:14:57 2009 - Exporting sysman schema for std1 ... exported
Mon Sep 14 19:15:56 2009 - DB Control was saved successfully.
Mon Sep 14 19:15:56 2009 - Starting DB Control ... started
Mon Sep 14 19:17:33 2009 - Dump directory was dropped successfully.
7. Copy the Pre-Upgrade Information Tool (utlu112i.sql) from the Oracle Database 11g Release
2 (11.2) ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle home.
8. run above script and examin the output
SQL> SPOOL upgrade_info.log
SQL> @utlu112i.sql
SQL> SPOOL OFF
9. Gather statistics on schemas instructed by utlu111i.sql
EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; EXEC

DBMS_STATS.GATHER_SCHEMA_STATS(user_name);
10. Grant privileges revoked from public to resolve invalid objects

11. If the timezone warning is
Database is using a timezone file older than version 11.
then check the timezone with
select * from v$timezone_file;
if it is not 11 then to fix the problem use the DBMS_DST PL/SQL package and follow the
instructions in Steps to Upgrade Time Zone File and Timestamp with Time Zone Data in Oracle
Database Globalization Support Guide.
if the timezone warning is
Database is using a timezone file greater than version 11.
then before upgrading the database, patch the 11gR2 $ORACLE_HOME/oracore/zoneinfo/ with
a timezone data file of the same version as the one used in the source release database.
12. Create a listener for the new 11g R2 Oracle home

13. Run DBUA from new 11g Home
14. set the compatible parameter.
alter system set compatible='11.2.0.0.0' scope=spfile ;
15. To upgrade the timezone
shutdown the database and start in upgrade mode
startup upgrade;
exec DBMS_DST.BEGIN_UPGRADE(11);
After PL/SQL executes start the database in normal mode and truncate timezone trigger tables
truncate table sys.dst$error_table;
truncate table sys.dst$trigger_table;
VAR numfail number
BEGIN
DBMS_DST.UPGRADE_DATABASE(:numfail,
parallel => TRUE,
log_errors => TRUE,
log_errors_table => 'SYS.DST$ERROR_TABLE',

log_triggers_table => 'SYS.DST$TRIGGER_TABLE',
error_on_overlap_time => TRUE,
error_on_nonexisting_time => TRUE);
DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail);
END;
after finishes
BEGIN
DBMS_DST.END_UPGRADE(:numfail);
END;
2012-6
14
SDM,JSPM AND VISUAL ADMIN, CONFIG TOOL in enterprise portal

email
We have many different tools (12 tools )available in Enterprise Portal.
SDM, JSPM, Visual Admin tool, Config Tool are one of them.
SDM :- Software Deployment Manager is been replaced with JSPM tool for more intelligent
work.
It is a tool from where we can apply the support packages, but now it is outdated and we are
using JSPM tool to deploy the support packages.
For SDM tool we need to manually feed the support packages.

With SDM tool we can also undeploy the support packages.
It is initialized with remotegui.bat (Windows) or remotegui.sh (Unix)
JSPM:- Java support package manager is initialized by go.bat (WIndows) or go.sh (Unix).
It uses the SDM password.
It is an intelligent tool
it will check the patch levels at market place with the existing patch levels.
it will read the SPs from inbox automatically.
we can even upgrade the kernel here.
Config tool : It is a configuration tool which works offline.
it does not require java engine to be up and running to open.
it is initialized by configtool.bat or configtool.sh
it is used to configure the ldap to populate the user information.
it is used to increase and decrease the server processes.
it is used to change the password of superuser when all the users got locked.
Visual Admin Tool : It is online tool requires java engine to be start.
remote login is possible with this tool.
it is initialized by go.bat or go.sh
Most of the parameters are dynamic and does not require restart of engine.
it requires user id and password to login
2012-6
14
How to add a new Server Process to a Java Instance

email
A server process is added to scale up your Java Instance. In an ABAP+JAVA stack combined (java
add-on to ABAP stack) installation, it is not possible to install java stack (individually, without
ABAP stack) in any instance or in any host. So any additional instance of Java Stack can only be
installed as an add-on to a fresh ABAP stack .i.e. both have to be installed together. For scaling
up java stack a further server process can be added, BUT ABAP stack alone, without JAVA Add-
on, can be installed.
Start the SAPs Config Tool

Identify the instance where you have to add Current Instance -> Select the Option Server ->
Add
2012-6
13
How to setup operation modes in SAP ?
Category: SAP Admin | No Comments

email
How to setup operation modes in SAP ?
This article answers the following queries :
What are operation modes and its advantages?
How to setup operation modes ?
How to configure operation modes to switch operation mode automatically ?
How to change workprocesses without restarting the SAP system ?
What are operation modes and its advantages
In SAP we have memory limitations. So, we cannot define very high number of dialog or
background workprocesses. Usually in SAP system, dialog activity will be more during day time
and batch activity will be more in the night time. Operation modes are a concept provided by
SAP to take advantage of this fact. In SAP, we can define operation modes like day and night
and configure more dialog workprocesses and less background workprocesses during day time
and more background workprocesses and less dialog workprocesses during night time. We can
define duration for day and night operation modes so that operation mode switch will happen
at defined time and dialog workprocesses will be converted to background workprocesses in
the night and vice versa and thus improves performance of the system.
Please note for this operation mode switch restart of the SAP system is not required and system
automatically does this at the mentioned time.
How to setup operation modes ?
Goto RZ04 transaction code as shown in below screen.
Click on create button to create an operation mode. It prompts to enter the operation mode
name and short description as shown below. Please provide the same
After providing the details and saving, you will get the below screen
Create one more operation mode for night. Please provide details same for day and click on
save to confirm
It leads to the below screen. Here we can view 2 operation modes day and night which we have
created
Now Click Instances/Operation Modes. Another screen will be displayed.
Navigate to Settings ->Based on Current status -> New Instances -> Generate
as shown below and click generate.

After that profile will get generated as shown below
Place the cursor on respective operation mode and double click to get the work process
distribution screen. In the below screen, work process distribution of day operation mode is
shown :
Similarly doubleclick night operation mode to view workprocess distribution of it.
In the above screen of night operation mode there are 10 dialog and 3 background
workprocesses. Incase you would like to change keep the cursor in the respective box and click
plus or minus button in the screen to change workprocesses accordingly.
In the below screen, background processes are increased to 6 by keeping cursor on the text box
and pressing plus button thrice. So accordingly dialog workprocesses gets reduced from existing
10 to 7 to maintain total of 13 workprocesses overall.
Please find below workprocess distribution after the changes done
To maintain operation mode switch timings, goto transaction SM63 as shown below and select
normal operation (24hr) mode
Click on change button in the above screen to goto below screen.
In the below screen set the operation mode intervals for day and night.
First let us set for day operation mode by clicking on the start time of the day interval and then
navigating to Operation mode -> Select interval. Then start interval is marked. After this place
cursor at the end interval and again navigate to Operation mode -> Select interval and confirm
to mark the entire interval of day operation mode
In the above screen, you can figure the interval marked is highlighted in different colour. Now
assign operation mode as below for the highlighted area by clicking on assign button in the
below screen
Then as shown below day operation mode is assigned to the selected area
Similarly repeat the same process for Night operation mode and select the interval, assign the
operation mode and save as per below screenshots.
So, now day operation mode is set form 8am to 8pm and other interval is set for night
operation mode as shown below
This completes the operation mode creation, workprocess allocation and configuring operation
mode switch.
2012-6
13
How to configure Early Watch Alert report
Category: SAP Solman | No Comments

email
To configure Early watch alert some specific settings to be done at managing system (Solution
manager system) and satellite system( or managed system for which EWA report to be
generated)
Following are the steps to configure EWA in a satellite system :
1) Check whether latest versions of ST-A, ST-PI, ST-A/PI packages are installed in the
managed/satellite system
(This check can be done going to system->status -> Component information display in any sap
screen)
2) If they are installed, run RTCCTOOL report from SE38 transaction code of satellite
system.
Check the output of the report. If there are some errors or warnings in the output of the
report, please take corrective actions and run the report again and ensure there are no errors
3) Setup RFC connection between your satellite system and the solution manager system
An RFC connection can be made between 2 systems using Transaction code SM59
4) Setup RFC connection between your solution manager and the SAP service market place
5) Assign the solution monitoring roles to the users
6) Setup your satellite system in a solution landscape of the solution manager(SMSY)

7) Make sure SLD is configured and working fine for satellite system (using Rz70 and
SLDCHECK transactions)
8) Activation of SDCCN in satellite system (Goto SDCCN transaction. Then click on Utilities -
> Activate) then confirm for SDCC_OSS destination creation
9) In satellite system, goto SDCCN transaction and navigate to Goto -> Settings -> Task
specific.
In the resulted screen, select RFC destination and provide the solution manager RFC from the
satellite system and set solution manager RFC as the master system.
10) Addition of satellite system in solution manager system in SDCCN :
Goto SMSY transaction in solman system and then navigate to Environment -> Solution
Manager Operations -> Adminstration SDCCN to add the new service data control centre to
the solution manager.
Click on add system button to add the new SDCC to the solution manager. When prompted,
please select the respective system and client from the resulting screen and confirm
11) Early watch service session activation for satellite system:
In the solution manager system, execute transaction code solution_manager and navigate to
operations -> Earlywatch Alert and press create button. This prompts you to confirm the date
and time to run the report. Please provide the details and confirm to trigger the generation of
the report
12) Login to satellite system, goto transaction code SDCCN and press create button which
displays a screen to select a task to be executed. Select request session data task and click
continue. You will be prompted to enter the schedule time to run the report. Click now to
execute it immediately. After that you can see an early watch session running in SDCCN.
13) After completion of this session run successfully, an Earlywatch Alert will be generated
and this can be viewed in Solution_manager of Solution manager system.
Older Entries
Newer Entries
UTC: 2013-01-21 06:25
IST: 2013-01-21 11:55
Gtranslate
Donate to SAP Admin
SAP ADMIN
is a technology help website. Our experts are real people with real-world technology experience
from around the globe, SAP, Database and Network , Operating system s consultants and many
more.
"If this blog information useful for you, please consider to donation to help me maintain and
update this blog regularly".

Sap Basis Activities

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sap Basis Activities

Transféré par

Droits d'auteur :

Formats disponibles

DB02 statistics blank

Category: Databases | No Comments

More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on

1. Run report RSORACUP.

SAP SPOOL Process

Category: SAP BASIS | No Comments

what is spool overflow ? How to troubleshoot spool overflow issue ?

What is spool overflow ? :

ERROR IN SPOOL call : SPOOL OVERFLOW

System internal error in the spool system

How to troubleshoot spool overflow ?

Old spool requests older than the maximum set age

Requests already printed

All spool requests

How to check spool numbers ?

How to set the spool number in SAP ?

How to define storage location (Temse) of spool requests ?

Prioritizing Class A Jobs

Category: SAP BASIS | No Comments

More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on

1. Call Transaction RZ04 or choose CCMS

Configuration Operation Modes / Instances.

Numbers of Class A background work processes:

The default number. Use this value if you do

SAP Java monitoring Check list

Category: SAP Portal | No Comments

More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on

SAP Java monitoring Check list

This article answers the following queries :

How to perform daily monitoring of Java stack in SAP ?

What are the daily checks for Java applications of SAP ?

How to perform session monitoring in JAVA stack of SAP ?

How to view various java reports in JAVA stack of SAP?

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 ?

1. Checking the java stack/portal accessibility

3. User load analysis

4. Java Reports Navigation and usability

5. Memory consumption and Threads report

7. Logs and Traces (Default trace, Server0 log etc)

8. Accessing Management Console

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

iii) Check the default trace for any critical errors

iv) Check application log to determine any memory related issues

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 Memory Consumption Report and Threads Reports :

To check this report login to nwa of the respective java stack :

Then navigate to Monitoring -> Java System Reports :

Slowest requests in detail

However from monitoring perspective, resource consumption report is most important to

Click Hint on charts link to analyse the report better.

To monitor sessions, navigate to Monitoring -> Session Monitoring

From the drop down box, different logs can be checked

Using Management Console for monitoring Java System :

A screen similar to below screen will appear :

You can check the javanode status as below:

Status should be running here if java is up

Category: SAP Security, Uncategorized | No Comments

/10 * * * /bin/execute/this/script.sh 2>&1 >> /var/log/script_output.log

/10 * * * /bin/execute/this/script.sh 2>&1 | mail -s "Cronjob ouput"

/10 * * * /bin/execute/this/script.sh 2>&1 > /dev/null