SAP ADMIN
9. Back Up the Database:1- Perform Cold Backup (or)
$ 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
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.
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);
SDM,JSPM AND VISUAL ADMIN, CONFIG TOOL in enterprise portal Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on 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 SP’s 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 Category: SAP Portal | No Comments
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on 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 SAP‘s “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
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on 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
More Sharing ServicesShare|Share on linkedinShare on facebookShare on twitterShare on 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