Preparation: Oracle Upgrade
1) Checking the Correct UNIX Users, Groups, and Authorizations
-> You want to check that the ora client has compose approval for the/prophet catalog, since the ora client plays out the information base establishment.
contact/prophet/write_test
rm/prophet/write_test
-> On the off chance that the client ora doesn’t have compose approval, sign on to your framework with the client root and enter the order:
chgrp dba/prophet
chmod 775/prophet
-> Enter the accompanying order with the client ora:
umask 022
2) Checking the Directory Structure
You want to check the accessibility and accuracy of the accompanying Prophet indexes:
a) stage
b) prophet stock registry
c) home registry
a) For the move up to Prophet Information base 10g Delivery 2 (10.2) make the organizing registry/prophet/stage/102_64.
-> At the point when the RDBMS Cds have been mounted, utilize the SAP instrument SAPCAR to remove every one of the RDBMS Discs to/prophet/stage/102_64 as client ora.
SAPCAR – xvf OR110264.SAR
-> After extraction of the Prophet programming to/prophet/stage/102_64 do the accompanying:
Rename the first SAP organizer by performing
mv/prophet/stage/102_64/data set/SAP/prophet/stage/102_64/information base/SAP_ORIG
-> Download the document RDBMS_SAP_64.zip (for 64-bitplatforms) appended to Drain Note
819830 and duplicate it to a transitory area, for example,/tmp.
-> Extricate the compress record by performing
compact disc/prophet/stage/102_64/information base
unfasten/tmp/RDBMS_SAP.zip
b)- > Check the Prophet stock index.
The Prophet stock catalog keeps up with the stock of all Prophet programming introduced on the framework. The way to the Prophet stock catalog is referenced in the document oraInst.loc, which you can view as under
/var/select/prophet or under/and so forth.
-> One of the sections of oraInst.loc or inventory_location focuses to the area of the Prophet stock. At the point when you execute the OUI interestingly on the framework, the OUI prompts you for the way to theinventory index. The
default area for the Prophet stock is
$ORACLE_BASE/oraInventory.
c)- > Make the unfilled Prophet home registry prior to beginning the OUI.
You really want to make the Prophet home registry before you can begin the Prophet programming establishment. The Prophet Home catalog is ordinarily
/prophet//102_64.
3) Running the Pre-Upgrade Script
–> Execute the following commands:
sqlplus /nolog
SQL> connect / as sysdba
SQL> spool /tmp/pre_upgrade.log
SQL> @/oracle/stage/102_64/database/SAP/utlu102i.sql
4)Checking the Prerequisites for the Oracle Universal Installer
–> Log in as the Oracle user ora.
cd /oracle/stage/102_64/database
./runInstaller –executeSysPrereqs
5) Checking the SAP System Prerequisites
-> Download the most recent variant of dbsl (dboraslib.so, dboraslib.sl, or dboraslib.o) for your delivery from the SAP Administration Commercial center at:
www.service.sap.com/swdc.
6) Migrating to Automatic Undo Management
–> Refer note:- 600141
7) Checking the SYSTEM and SYSAUX Tablespace for Freespace
-> You can check this by executing one of the accompanying orders as the ora client:
brspace –f dbshow –c tsinfo –s SYSTEM
brspace –f dbshow –c tsinfo –s SYSAUX
8) Checking for Invalid Database Objects
-> This discretionary step allows you to check in the event that there are any invalid data set objects before the data set move up to Prophet data set 10g beginnings. After the update It assists you with recognizing information base articles that have become invalid because of the overhaul cycle from those that were at that point invalid to begin with.
-> Execute following orders
SQL> spool invalid_objects
SQL> select remarkable object_name, object_type, proprietor from dba_objects
where status =’INVALID’;
SQL> @?/rdbms/administrator/utlrp.sql
SQL> select remarkable object_name, object_type, proprietor from dba_objects
where status = ‘INVALID’;
SQL> spool off
-> Actually take a look at the rundown of invalid items after the overhaul.
9) Installing the Oracle Instant Client
–> Refer note 819829.
Oracle Database Upgrade
1) –> To install the database software you need to check and set the environment variables of user ora because this user installs the Oracle software.
-> You set the climate factors underneath by altering the documents
.dbenv_.sh and .dbenv_.csh in the home catalog of ora.
-> Ensure the accompanying climate factors are not set:
TWO_TASK
ORA_NLS
ORA_NLS32
ORA_NLS33
–> Set the following environment variables:
DISPLAY
ORACLE_BASE /oracle
ORACLE_SID
ORACLE_HOME /oracle/SID/102_64
NLS_LANG /oracle/stage/102_64/database/SAP
ORACLE_NLS10 $ORACLE_HOME/nls/data
SAPDATA_HOME /oracle/
-> Set the comparing climate variable for the library way:
LD_LIBRARY_PATH $ORACLE_HOME/lib:$LD_LIBRARY_PATH
-> Incorporate $ORACLE_HOME/container in your Way or way factor,
2) Backing Up the Oracle Inventory
-> In the event that the Prophet stock exists, actually take a look at its area by checking out at the passage in one of the accompanying documents:/var/select/prophet/oraInst.loc/and so forth/oraInst.loc The area is displayed as follows: inventory_loc=
-> Make a reinforcement of your current Prophet stock before you start the Prophet Information base 10g Delivery 2 (10.2) programming establishment.
3) Running the Oracle Universal Installer
–> cd /oracle/stage/102_64/database/Disk1/SAP
./RUNINSTALLER
4) Installing the Current Patch Set
–> Refer note 871735. Install as ora user.
5) Installing Required Interim Patches via OPatch
–> Refer note 871096.
6) Copying and Adapting the SQL*Net Files
After the information base programming establishment, you should duplicate and alter the old SQL*Net records, or at least, listener.ora, sqlnet.ora, and tnsnames.ora.
-> Logon as ora client.
In the event that ora has climate variable TNS_ADMIN set, do the accompanying:
a) Pick another area for the new SQL*Net boundary records and set TNS_ADMIN to highlight the new area .
b) Duplicate the SQL*Net boundary documents from the old area to
c) Alter the new SQL*Net records by adjusting all document ways for the new index. Make certain to adjust the worth of ORACLE_HOME in the listener.ora record.
-> The SQL*Net boundary documents are situated in/network/administrator:
a) Duplicate the SQL*Net boundary records from to.
b) Alter the new SQL*Net documents by adjusting all record ways for the new index. Make certain to adjust the worth of ORACLE_HOME in the listener.ora record.
7) Backing Up the Oracle Database
-> Make a total information base reinforcement.
8) Shutting Down the SAP System and Oracle Listener Process
—>You want to close down the SAP framework and the Prophet audience running cycle running in the old ORACLE_HOME, for instance, in/prophet//920_64.
9) –> Stop the SAP application server by entering the following command as user sapsid>adm:
stopsap r3
Stop the Prophet audience by entering the accompanying order as client ora:
lsnrctl stop
10) Checking the oratab Entry
-> Ensure that the oratab record contains the accompanying section:
::N
Where old_ORACLE_HOME represents the way to the old prophet programming Establishment.
-> There is no such thing as on the off chance that this section, embed it utilizing a word processor.
11) Starting the Database Upgrade Assistant
-> Ensure that you start the DBUA in the Prophet 10.2 client climate. To do this, cautiously look at the primary point beneath.
Affirm that the accompanying climate factors highlight Prophet 10.2 indexes:
ORACLE_HOME focuses to/prophet//102_64
Way
ORA_NLS10
LD_LIBRARY_PATH orSHLIB_PATH or LIBPATH
-> Before you start the DBUA ensure that the Showcase climate variable is accurately set
-> You start the DBUA:
disc $ORACLE_HOME/canister
./dbua
Answer properly to the DBUA discoursed:
The Welcome screen gives data about the update right hand
a) Decide Close to proceed.
The Data sets screen allows you to choose the information base to be updated.
b) Select the right data set and pick Straightaway.
The DBUA currently examines the information base to be redesigned, performs pre-update checks, and issues alerts if essential. You can overlook alerts about the accompanying:
Flat streamlining agent insights
Changes to the Prophet Interface job
-> Make the accompanying passages:
Datafile Way: $SAPDATA_HOME/sapdata1/sysaux_1/sysaux.data1
-> Select Reuse Existing Record Name.
Enter 1000 MB in Size.
Select AUTOEXTEND ON.
Enter 100 MB in Augmentation.
Enter 2000 MB in Greatest Size.
->Acknowledge the default values, select Recompile invalid items after the overhaul, switch off chronicling for the span of the redesign, and pick Straightaway
-> Since you have proactively supported the data set, select I have previously upheld my data set and pick Straightaway.
-> Ensure that Arrange the information base with Big business Supervisor isn’t chosen and pick Straightaway.
->Audit the rundown of changes and decide Back to make any last changes, whenever required.
-> Begin the data set update by picking Finish.
-> Audit the progressions made and leave the DBUA.
Post-Upgrade Steps
1)–> Finalizing the Environment of the oraUser
You want to ensure that the progressions you made to the Prophet client climate are for all time put away in the profiles (.cshrc, .dbenv_.csh, etc).
-> Ensure that the climate contains no factors that actually allude to the old information base delivery.
2) Checking the Upgraded Database
-> Make sure that the information base is presently running with Prophet Data set 10g Delivery 2
(10.2) programming in a Prophet Data set 10g Delivery 2 (10.2) climate by entering the accompanying orders:
a) Sign onto the information base as the ora client.
b) Enter the accompanying order to begin SQLPLUS:
sqlplus/as sysdba
c) Enter the accompanying SQL orders:
-> Enter the accompanying order to decide the arrival of the introduced programming:
SQL> select variant from V$INSTANCE;
-> Enter the accompanying order to decide the delivery and status of the introduced information base parts:
SQL> select comp_id, form, status from dba_registry;
Ensure that the order returns the status Substantial.
-> Make sure that the rendition returned in the past two orders is indistinguishable.
3) –> Check that the value for the version returned from the above command is the same level as the installed patchset.
For instance, if the introduced patchset is Prophet 10.2.0.2, the above order ought to likewise report the rendition for the Index and CATPROC parts as 10.2.0.2.
4)–> After the upgrade check that the following document is created:
$ORACLE_HOME/associates/dbua/doc/help/DefaultBehaviorChangesin10g.html
5) Updating BR*Tools
-> Download the latest service.sap.com/swdc.
-> After you have extricated the most up to date BRTools, you likewise need to duplicate the BRTools design documents init.sap and init.utl from the old $ORACLE_HOME/dbs index to the enhanced one (init.utl is just accessible in the event that you are utilizing an outsider reinforcement
arrangement):
disc/dbs
cp init.sap $ORACLE_HOME/dbs
cp init.utl $ORACLE_HOME/dbs
-> Execute the accompanying orders as the ora client to refresh the SAPDBA job:
cp/usr/sap//SYS/exe/run/sapdba_role.sql $ORACLE_HOME/dbs
compact disc $ORACLE_HOME/dbs.
sqlplus/nolog @sapdba_role .
6) Backing Up the Database
–> You want to back up your overhauled Prophet Data set 10g information base.
Perform a full database backup.
7) Performing Post-Upgrade Tasks
–> Change data set similarity by executing the accompanying SQL order as the ora client:
SQL> change framework set compatible=’10.2.0′ scope = spfile;
–> Restart the Oracle database
–> Deactivate the Oracle recycle bin by executing the
SQL> purge dba_recyclebin;
SQL> alter system set recyclebin = ‘off’
For more information, see SAP Note 838982.
–> Gather Oracle optimizer statistics as follows:
a) Execute the following commands as the ora user:
SQL> spool $ORACLE_HOME/cfgtoollogs/dbstats.log
SQL> execute dbms_scheduler.disable(‘GATHER_STATS_JOB’);
SQL> execute dbms_stats.gather_system_stats;
SQL> execute dbms_stats.gather_dictionary_stats
(ESTIMATE_PERCENT => NULL,
METHOD_OPT => ‘FOR ALL COLUMNS SIZE AUTO’,
GRANULARITY => ‘ALL’,
CASCADE => TRUE,
OPTIONS => ‘GATHER’,
NO_INVALIDATE => FALSE);
SQL> execute dbms_stats.gather_fixed_objects_stats;
b) Check the log document dbstats.log made at $ORACLE_HOME/cfgtoollogs for any blunders during the get-together of measurements
–> Identify the objects that are invalid after the upgrade as follows:
a) Execute the following commands as the ora user:
SQL> @?/rdbms/admin/utlrp.sql;
SQL> spool $ORACLE_HOME/cfgtoollogs/invalid_post.log
SQL> select count(*) from dba_objects where status = ‘INVALID’;
SQL> select substr(owner,1,12) owner, substr(object_name,1,30)
object, substr(object_type,1,30) type, status from
dba_objects where status <>’VALID’ order by owner;
SQL> spool off;
b) Check the log file invalid_post.log. created at $ORACLE_HOME/cfgtoollogs/invalid_post.log to compare the invalid objects before the start of the upgrade..
–> Check the Oracle database parameters against SAP Note 830576 and adjust them if necessary.
–> Make sure that the following database parameters, if set, are removed;
COMMIT_WRITE
CURSOR_SPACE_FOR_TIME
DB_FILE_MULTIBLOCK_READ_COUNT
HASH_JOIN_ENABLED
LOG_ARCHIVE_START
OPTIMIZER_INDEX_COST_ADJ
OPTIMIZER_MODE
STATISTICS_LEVEL
TIMED_STATISTICS
TRACE_ENABLED
–> Restart the database to activate the changes:
a) Sign on to the information base with SQL*Plus
b) Execute the accompanying orders:
sqlplus/as sysdba
closure quick
startup
–> Gather statistics for SAP schemas:
a)With Prophet Data set 10g all tables have measurements, and that implies that you want to refresh a few passages in the DBSTATC table prior to beginning BRCONNECT, as follows:
sqlplus/nolog
SQL> interface/as sysdba
SQL> @/prophet/stage/102_64/data set/SAP/updDBSTATC10.sql
b)Update the DBCHECKORA control table after the overhaul as follows:
compact disc/prophet/stage/102_64/information base/SAP
sqlplus sap/@dbcheckora10upgr
c) Update the Prophet data set insights with BRCONNECT as follows:
brconnect – c – u/ – f details – t all – f gather – p 4
–> Installing Oracle Critical Patch Updates via OPatch
Refer note 850306 and 871096
–> Checking the oratab entry
a) You check the entry for the oratab file.
b) Make sure that there is an entry like the following in your oratab file:
::N
new_ORACLE_HOME indicates the path to the Oracle Database 10g
software.
c) If the entry does not exists insert it using a text editor.
–> Starting the Listener Process
Start the listener:
lsnrctl start
Check that you can remotely connect to sqlplus SAP/pwd@SID
–> Renaming the Old $ORACLE_HOME/bin Directory
Rename the old Prophet home registry container with the accompanying order:
mv/receptacle/canister old
–> Checking the Read Authorization of the adm User
Ensure that the adm client has perused approval for the index $ORACLE_HOME.
In the event that this isn’t accurate, enter the accompanying order as the ora client:
chmod 755 $ORACLE_HOME
–> Changing the Environment for the adm user
You need to change the climate for the adm client, however just on the information base server.
1.On the information base server set the ORACLE_HOME climate variable to highlight the area of the Prophet Data set 10g programming establishment, for instance:
/prophet//102_/
2.Make sure that the change to the client climate is forever put away in the profiles (.cshrc, .dbenv_.csh, etc).
3.Log out and sign on again as the adm client.
4.Check whether R3trans can associate with the information base:
R3trans – d
–>Checking SAP Profile Parameters
You have to check the following SAP profile parameters:
DIR_ORAHOME
DIR_CLIENT_ORAHOME
DIR_SERVER_ORAHOME
1.Set DIR_ORAHOME and DIR_CLIENT_ORAHOME in the example profiles to the relating upsides of the ORACLE_HOME climate variable of the adm client.
These factors highlight the ORACLE_HOME utilized by the application server.
2.Set DIR_SERVER_ORAHOME in the default profile to the worth of the ORACLE_HOME climate variable of the ora client on the data set server.
–> Starting the SAP System
1. If R3trans connects without problems, start the SAP system:
Startsap
3. Check the new Oracle version using SAP transaction ST04.
–> Configuring the New Features for Oracle Database 10g
Release 2 (10.2)
Refer note 828268
YOU MAY LIKE THIS
SAP consulting services USA vs India companies: A Comparative Analysis
WhatsApp us