ORACLE UPGRADE STEPS FROM 11g TO 12c FOR SAP SYSTEMS ON LINUX - PART I

Document creation date:   10th OCT 2015 | 09:30 AM INDIA

Document Part                :  1st

Document Author            :  Gaurav Rana

Referred SAP Guide        :  Database Upgrade Guide to Oracle database 12c Release 1 (12.1.0.2 ) UNIX

Referred SAP NOTES      :  1. NOTE : 1914631 - Starting point for info about oracle 12c .

                                           2. NOTE :  1915317-Migrating Software owner to 'oracle' 

                                           3. NOTE : 1915323 - OS User Concept for database release 12c.

STEPS TO FOLLOW    :

PREREQUISITES

a) Source release must be Oracle DB 10.2.0.5,11.2.0.2,11.2.0.3 or 11.2.0.4 (Check your database version with command, SQL>select version from v$instance;)

b) Only 12.1.0.2 release 1 is supported for SAP platforms instead of 12.1.0.1 .

c) For SAP environments, Oracle Instant Client versions 11.2.0.4 and 12.1.0.2 are supported.

RESTRICTIONS

a) In order to run the SAP system with Oracle Instant Client version 12.1.0.2 ,you'll have to apply the SAP support packages from SAP Note 1777021.

b) SAP Kernel release must be >= 7.21 EXT.

c) SAP BR*Tools minimum version for 12.1: BR*Tools 7.40 Patch Level 14.

d) Mandatory to apply the appropriate SAP Support package according to SAP Note 2157904.

e) Must be applied before or immediately after a database upgrade to Oracle release 12c or after a new installation with Oracle release 12c.

f) Secure Storage on File System (SSFS) must be configured and enabled to run SAP with Oracle Database 12c.

CHECKLIST BEFORE STARTING SAP SYSTEM OF UPGRADED SYSTEM

a). Migration of oracle software owner from ora<sid> to 'oracle'.

b). Installation of database 12.1.0.2 with Patches.

c). Install the latest Oracle client (12.1.0.2) for the database 12.1.0.2 .

d). Update BR*Tools with version 7.40 .

e). SSFS database connection configurations (SAP Notes 1639578 & 1622837) .

PREPARATION

a). Download the Oracle 12c software with patches from http://service.sap.com

b). Download latest version of DBATOOLS (BR*Tools) which we need to be used after the upgrade .

c). Set the display parameters <host_name>:0.0 or use command xhost + .

CHECKLIST STEPS IN DETAIL

a)Migration of database user ora<sid> to 'oracle' user .

    For the step i recommends to refer SAP NOTE 1915317-Migrating Software owner to 'oracle'  or can follow steps as below :

1.Shutdown the running SAP System & the database with use of command stopsap all or can stop the SAP System & Database individually along with listener with command lsnrctl stop .

2.Creation of oracle software owner account 'oracle' from the root account

# groupadd oinstall

# useradd -g oinstall -G dba,oper -c "Oracle Software Owner" -m -s "/bin/sh" oracle

# passwd oracle

# su - oracle -c "id;pwd"

3.Modification of SAP Admin account <sapsid>adm

Add the <sapsid>adm account as OS group 'oinstall' (Required to run BR*TOOLS)

# groupmod -A <sapsid>adm oinstall or execute

# usermod -G sapsys,sapinst,dba,oper,oinstall <sid>adm

4.Modification of Database Admin account 'ora<dbsid>

Log on as 'root' and run the commands ...

# mkdir -p /home/ora<dbsid>

# chown orasbx:dba /home/ora<dbsid>

# usermod -d /home/orasbx ora<dbsid>

# usermod -g dba -G oper,oinstall ora<dbsid>

From the root account :

# cd /oracle/<SID>

# mv .profile .login .bashrc .cshrc .sap* .dbenv* .j2eenv* /home/ora<dbsid>

# mv startdb stopdb /home/ora<dbsid>

# chown -R ora<dbsid>:dba /home/ora<dbsid>

Oracle Environment consistency

Note : If Oracle env for <SID> set for user 'oracle' differs from the oracle env for user <SID>ADM then system will not connect to the database.

To check, logon with user account <sid>adm & oracle to verify variables ORACLE_BASE,ORACLE_HOME & ORACLE_SID which should be set identical .

Ownership changes for data files & directories

Permissions & ownerships can be changed with help of script 'orasid2oracle.sh' (Script is attached with SAP Note 1915317 named orasid2oracle.zip)

On unzip the file, a directory will be created with name sapnote_1915317, contains executable script orasid2oracle.sh.

Parameters to be set before execution of the script :

1.Log on with root account

#export SAPDATA_HOME=/oracle/<SID>

#export ORACLE_BASE=/oracle/<SID>

#export DB_SID=<SID>

2.To test run

#./orasid2oracle.sh -v

3.To perform changes

#./orasid2oracle.sh -v -exec

Ownership change of Oracle Home

Under this step we’ll change the software owner of Oracle Home from ‘ora<sid>’ to ‘oracle’ and samecan be achieved with the help of oracle cloning tool from SAP Note 1983457 (Recommended).

You can find the clone tool script named clone_oh-1.7-005.zip as an attachment with the SAP Note 1983457,& on extraction of the zip file a new directory will be created as sapnote_1983457.

From the directory we need to execute clone_assistant.sh .

Steps to execute clone_assistant.sh

Log on as ora<dbsid> & execute clone_assistant.sh script to generate the scripts.This script will ask some questions for further execution steps, For help sample answers can be find from the same SAP Note 1983457.

To save generated scripts from clone_assistant.sh we can provide our own location on the system. For ex. /oracle/<SID>/ora_clone/pkg_clone_oh/change_sw_owner/

Scripts generated by the execution of clone_assistant.sh will be as follows :

config00_settings.sh

config01_show_env.sh

config02_detach_oh.sh

config03_set_swowner.sh

config04_clone_oh.sh

config05_run_rootsh.sh

config06_cleanup.sh

From the script directory execute the generated Oracle Home configuration scripts as per steps

From the old software owner ora<dbsid>

su -  ora<dbsid>

>./config01_show_env.sh

>./config02_detach_oh.sh

As a root user

# ./config03_set_swowner.sh

From the new software owner ‘oracle’

>./config04_clone_oh.sh

As a root user

#./config05_run_rootsh.sh

For cleanup action, login as a old software owner

su – ora<dbsid>

>./config06_cleanup.sh

STARTING OF DATABASE LISTENER AS A NEW SOFTWARE OWNER ‘oracle’

During startup of listener from new software owner ‘oracle’ i experienced troubles in terms of environment variable settings for same.

As shell of new owner ‘oracle’ by default was /bin/sh & unable to execute commands lsnrctl status / lsnrctl start & was getting message command not found.(More obviously it’s an issue related with wrong environment settings).

WORKAROUND TO OVERCOME THE ISSUE. (WILL UPDATE SOON WITH DEFAULT SHELL ENVIRONMENT SETTINGS TO AVOID TO FOLLOW ANY WORKAROUND).

Changed the shell from /bin/sh to /bin/bash under system file /etc/paaswd for new database software owner ‘oracle’

Insertion of environment variables ORACLE_SID,ORACLE_HOME,ORACLE_BASE & PATH under .bash_profile file of new software owner ‘oracle’

su – oracle

ls –a

After saving the values under file .bash_profile ,re login with user as ‘oracle’ & check to execute command lsnrctl start for starting the database listener.

su – oracle

Next step is to start the database with new software owner ‘oracle’

su – oracle

If any issues (ORA-01033) occurs during the startup of database instance kindly refer troubleshooting part of SAP Note 1915317 .Mainly the issue happens only when oracle environment (ORACLE_HOME,ORACLE_SID,ORACLE_BASE) is not identical to the Oracle environment of <sapsid>adm..

DATABASE CONNECTIVITY CHECK from account <sapsid>adm

su - <sid>adm

>R3trans –d

Hope after following all steps you’ll be able to get R3trans finish code result 0000.If any issue happens you can refer trans.log file for analysis.

Configuration of Secure Storage in File System  :

To configure SSFS database connection configurations in detail for the system you can follow SAP Notes 1639578 & 1622837 & some good documents on SCN http://scn.sap.com/docs/DOC-49333 .

INSTALLATION OF ORACLE DATABASE SOFTWARE

Pre-Steps

Before installation of Oracle Database software we need to take the backup of central oracle inventory.

Location of inventory for Linux could be found in file oraInst.loc under /etc .

Create directory to place the extracted Oracle database 12c software.

Updating the SAP RUNINSTALLER Scripts

Check the patch level of RUNINSTALLER & check with SAP Note 1915301 for a higher version is available.

Latest available RUNINSTALLER version at SAP NOTE 1915301 is

So we can upgrade existing i.e from Patch level 058 up to 059 by following the SAP Note 1915301.

Installation of a new SAP RUNINSTALLER version :

1. Download the latest RUNINSTALLER package from the SAP NOTE as 12cinstall-12102-059-complete-201506021232.zip.

2. Extract the zip file under /oracle/stage/12102/database/SAP .

3.After extraction a new directory with similar name of SAP will get created under /oracle/stage/12102/database/SAP/ .You can replace the newly created SAP directory with old directory SAP.

On re-checking the RUNINSTALLER version we’ll get the latest version i.e patch level 059.

DATABASE SOFTWARE INSTALLATION PREREQUISITES

Procedure:

1.Log on as Oracle database software owner ‘oracle’

2.Set environment variable DB_SID,ORACLE_STAGE

Execute the below commands in dialog mode

Fix the above warning by executing the script runfixup.sh which is generated by selecting tab Fix & check again.

Oracle 12c database Installation:

Logon with new software owner ‘oracle’ to execute RUNINSTALLER .Before execution of RUNINSTALLER don’t forget to set two environment variables (DB_SID,ORACLE_STAGE).

Provide relevant information as required by the software to proceed further.

Execute the root.sh script from the location /oracle/<SID>/12102 & click on OK to finish the installation of 12c database.

INSTALLATION OF CURRENT SAP BUNDLE PATCH

Download the latest available SAP latest Bundle patch (SAP12102P_1509-20012300.ZIP) from https://support.sap.com/software/databases.html .

Refer README.html file from the software extraction to follow steps or follow steps as below :

Download the latest patch available (SAP12102P_1509-20012300.ZIP) from the service marketplace & save it under directory /oracle/stage by changing permissions & ownerships from root user to new database software owner.

Setting of environment variables IHRDBMS & OHRDBMS

Before proceeding we need to set the parameters IHRDBMS & OHRDBMS for the env of user ‘oracle’

>su – oracle

>env

>export IHRDBMS=/oracle/<SID>/121

>export OHRDBMS=/oracle/<SID>/12102

INSTALLING THE SAP BUNDLE PATCH

Before installation of SAP Bundle Patch need to follow the steps.

Stop all database applications, in particular all SAP applications.

Shut down the database instances, the listeners, and other processes running from the Oracle Home.

Install the SAP Bundle Patch as follows:

env ORACLE_HOME=$IHRDBMS $IHRDBMS/MOPatch/mopatch.sh -v -s SAP12102P_1509-20012300.ZIP

After successful installation we’ll be able to get screen as similar

     Start up the database instances, the listeners, and other processes running from the Oracle Home

PRE-UPGRADE SCRIPT RUNNING

Pre-steps before the upgrade :

1.Pre-Upgrade scripts always execute as the current Oracle DB admin ora<sid>/oracle.

2.Copy the listener.ora,tnsnames.ora & other from /oracle/<SID>/112_64/network/admin to /oracle/<SID>/12102/network/admin

3.Edit listener.ora & change the ORACLE_HOME with value /oracle/<SID>/12102

4.Execute the pre upgrade script from location /oracle/<SID>/12102/sap/ora_upgrade/pre_upgrade

Execute the script pre_upgrade_checks.sql to check the status of your database.

ORACLE DATABASE UPGRADE

NOTE : Recommends to take a complete offline database backup to restore if upgrade fails.

Steps to consider :

1.Stop the SAP system with stopsap r3 or sapcontrol –nr <SAP_Instance_Number> -function stop

2.Oracle software owner must have write permissions on oratab file .

3.ORATAB file would contain entry similar <DBSID>:<ORACLE_HOME>:N

4.Database & listener should be in running state.

Procedure :

1 .Log on with ‘oracle’

2.Save the administration directory of existing DB(Old ORACLE_HOME/network/admin)

3.Before starting DBUA environment variable must be set ORACLE_HOME_SRC,ORACLE_HOME_TGT,DB_SID & ORACLE_BASE

4.Change to the directory cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade

5.Test the DBUA script to verify correct env variable for upgrade.

6.Run script ./dbua.sap.sh to perform the upgrade in interactive mode.

Due to restrictions of uploading of images,i'll publish the Part-2 as well as troubleshooting for the same document very soon and requests all experts/SCN Members to guide me or hand me to make this document more informative & helpful for others by denoting any misstep in it.Hope you guys will find it helpful for your future references of database upgrades from Oracle 11g to 12c.

Part 2nd :  Refer SCN document at SAP ORACLE UPGRADE STEPS FROM 11g TO 12c FOR SAP SYSTEMS ON LINUX - PART II

Regards,

Gaurav Rana

ORACLE UPGRADE STEPS FROM 11g TO 12c FOR SAP SYSTEMS ON LINUX- PART II

Document creation date:   10th OCT 2015 | 09:30 AM INDIA

Document Part                :   2nd

Document Author            :   Gaurav Rana

Referred SAP Guide        :  Database Upgrade Guide to Oracle database 12c Release 1 (12.1.0.2 ) UNIX

Referred SAP NOTES      :  1. NOTE : 1914631 - Starting point for info about oracle 12c .

                                           2. NOTE :  1915317-Migrating Software owner to 'oracle' 

                                           3. NOTE : 1915323 - OS User Concept for database release 12c.

                                           4.NOTE  : 819829 - Oracle Instant Client Installation and Configuration on Unix

Document in continuation : SAP ORACLE UPGRADE STEPS FROM 11g TO 12c FOR SAP SYSTEMS ON LINUX

Select Upgrade Oracle Database & proceed further.

During the Pre - upgrade activities i got warning related with invalid objects exists.

Troubleshooting for the issue (INVALID OBJECTS EXISTS :

You can find the invalid objects, package body by execution of script pre_upgrade_checks.sql or with SQL query SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';

Resolution : To recompile invalid objects use SAP Transaction SE14 to reactive the views into database.In addition consider SAP Note 648203 - Database objects with status INVALID& suggests to consider SAP Note 1598594 - Br*Tools configurations for Oracle Installation using user "oracle" for successful generation of stats before the procedure at OS level.

You can Gather stats by opting Gather stats before upgrade,but recommends to check the proper database connectives,executions of database tools without any issue through new database software owner 'oracle' (Consider SAP Note 1598594 - Br*Tools configurations for Oracle Installation using user "oracle" ) & re verify the BR*tools configurations before the upgrade.

Deselect the EM database express from the Management Options

Do not select any options under Move database files.

Opt to migrate the LISTENER from source Oracle Home.

Recommends to have complete backup of the system for which we're going to perform the upgrade to avoid any type of issues during the upgrade in case of failures.I've my own backup strategy to choose.

POST UPGRADE STEPS

1.SQL*Net Configuration Files Update

Check for the following entries under tnsnames.ora file at <ORACLE_HOME>/network/admin or copy the tnsnames.ora,listener.ora files from the old ORACLE_HOME to verify or amend as per below if required.(If changes are already reflected with old tnsnames.ora & listener.ora files,then no need to amend.)

TNSNAMES.ORA File entries :

LISTENER.ORA file entries : Check for parameters SID_LIST_LISTENER & ADR_BASE_LISTENER are maintained under the file .

NOTE :ORACLE_HOME should be set for <NEW_ORACLE_HOME> (/oracle/<SID>/12102)

SYMBOLIC LINK FOR RUNTIME ORACLE HOME

STEPS :

1.Change to the directory cd /oracle/<DBSID>

2.Check for symbolic link with command  ls -l /oracle/<DBSID>/121

3.If links not exists issue command ln -s /oracle/<DBSID>/12102  /oracle/<DBSID>/121

ENVIRONMENT OF <sapsid>adm  & ora<dbsid> USER

We need to make environment variables permanent changes under profiles .dbenv_hostname.csh,.dbenv_hostname.sh & .dbenv.csh or .dbenv.shwith updated values of parameters ORACLE_HOME,ORACLE_BASE,PATH & oracle client.

You could check the variable values by following commands

env | grep ORACLE_HOME Result for the command should be ORACLE_HOME=/oracle/<SID>/12102

env | grep ORACLE_BASE  Result for the command ORACLE_BASE=/oracle/<SID>

env | grep PATH                  Result for the command 

PATH=/oracle/<SID>/12102/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/sap/<SID>/SYS/exe/uc/linuxx86_64:/usr/sap/<SID>/SYS/exe/run:/home/<sapsid>adm:.

MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles

RSEC_SSFS_DATAPATH=/usr/sap/<SID>/SYS/global/security/rsecssfs/data

RSEC_SSFS_KEYPATH=/usr/sap/<SID>/SYS/global/security/rsecssfs/key

LD_LIBRARY_PATH=/usr/sap/<SID>/SYS/exe/run:/usr/sap/<SID>/SYS/exe/uc/linuxx86_64:/oracle/client/12x/instantclient

NOTE : PATH should not contain any reference to 112_64

STARTING THE DATABASE LISTENER & DATABASE

1.Logon with new database software owner 'oracle' & start the listener with command lsnrctl start .

2.After successful startup of listener start the database with SQL command 'startup'

POST UPGRADE CHECKS

Refer SAP Note  : 1915315  to execute the scripts utlu121s.sql, post_upgrade_tasks.sql & post_upgrade_checks.sql from the location <new_oracle_home>/sap/ora_upgrade/post_upgrade

POST UPGRADE TASKS

1.Gathering of Oracle optimizer stats as admin user <sapsid>adm :

brconnect -u / -c -f stats -t system_stats

brconnect -u / -c -f stats -t oradict_stats

2.Update database stats

brconnect -u / -c -f stats -t all -f collect -p 4

UPDATE OF ORACLE INSTANT CLIENT

After upgrade to 12c,recommends to install oracle client supported for Oracle 12c. Refer SAP Note 819829 - Oracle Instant Client Installation and Configuration on Unix or best to follow steps from Upgrade Guide to 12c .

Steps :

1.# mkdir -p /oracle/client/12x

2.# cd /oracle/client/12x

3.# Mount Oracle client DVD 12.1.0.2 and unzip the client software :

SAPCAR -xvf <client DVD>/OCL<AS per OS>/OCL12164.SAR

4.Create symbolic links

cd /oracle/client/12x

ln -s instantclient_12102  instantclient

5.Symbolic link for BR*Tools 7.40

# cd /oracle/client

# mv 11x_64 11x_64_save

6.Create symbolic link

# ln -s /oracle/client/12x  /oracle/client/11x_64

UPDATE OF SAP KERNEL

Refer SAP Note 1716826 for supported SAP Kernel 7.21EXT  & for SAP 7.41 downward compatible kernel refer Note 1994690 .

STARTING OF SAP

After completion of the upgrade steps it's time to start the SAP System

Steps to start the SAP

1.Logon with admin user <sapsid>adm

su - <sid>adm

> R3tarns -d

NOTE : If any issue persists refer trans.log file from the system to rectify (Sometimes issue could be as of non supported kernel usage with 12c.

On successful startup of sap (with command startsap r3) you could check the upgrade status from SAP System Status.

Thanks folks for referring the document & i hopethe document will be helpful for other SCN members.Request experts to help me to make this document more responsive for up gradation of database from 11g to 12c.

Best Regards,

Gaurav Rana

Here you can find entries that were recently shown in http://scn.sap.com/community/oracle but have been removed.

Red Hat Enterprise Linux 7 Supported for SAP on Oracle

Oracle Exadata X5 Certified by SAP

Oracle Database 11g Release 2 Patchset 3 (11.2.0.4) Now Available

Support for SAP Applications with Oracle Databases in Microsoft Azure Environments

Structural Changes in SAP Bundle Patches

Oracle Virtual Compute Appliance (VCA) Certified by SAP

Virtual Exalogic Certified by SAP

Introduction

The main goal of this document is serving as a base for SAP Basis Administrator who work with Oracle Databases and want to perform simple checks.

I will try to improve this document as much as I can.

Of course, do not hesitate to collaborate by adding more SQL queries.

Considerations

DBSID: SAP

SAPSID: SAP

System variables

SPOOL <filename>

SET LINESIZE 32767

SET WRAP OFF

SPOOL OFF

Check SQL*Plus User's Guide and Reference.

Database

Show Oracle Database version

SQL> SELECT * FROM v$version;

BANNER

--------------------------------------------------------------------------------

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

PL/SQL Release 11.2.0.3.0 - Production

CORE    11.2.0.3.0      Production

TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production

NLSRTL Version 11.2.0.3.0 - Production

Show database details

SQL> SELECT NAME, LOG_MODE, OPEN_MODE, DATABASE_ROLE, PLATFORM_NAME FROM  v$database;

 

NAME      LOG_MODE     OPEN_MODE            DATABASE_ROLE    PLATFORM_NAME

--------- ------------ -------------------- ---------------- --------------------------

SAP       NOARCHIVELOG READ WRITE           PRIMARY          AIX-Based Systems (64-bit)

Show database size

SQL> SELECT SUM(BYTES)/1024/1024/1024 AS "DBSIZE(GB)" FROM dba_data_files;

 

DBSIZE(GB)

----------

5312.59766

Show Oracle Instant Client Version

SQL> select distinct client_version from v$session_connect_info where sid = sys_context('userenv', 'sid');

 

 

CLIENT_VERSION

--------------

11.2.0.3.0

For a list of all possibilities to check and identify Oracle Instant Client Version check this document.

Instance

Show database instance details

SQL> SELECT INSTANCE_NAME, HOST_NAME, VERSION, STARTUP_TIME, STATUS, INSTANCE_ROLE FROM v$instance;

INSTANCE_NAME  HOST_NAME      VERSION     STARTUP_TIME    STATUS       INSTANCE_ROLE   

-------------  ---------      -------     ------------    ------       -------------   

SAP            SAPSERVER     11.2.0.3.0  26-MAR-15      OPEN         PRIMARY_INSTANCE

Tablespaces

Show tablespaces details

SQL> SELECT TABLESPACE_NAME, STATUS, CONTENTS, SEGMENT_SPACE_MANAGEMENT FROM dba_tablespaces;

TABLESPACE_NAME                STATUS    CONTENTS  SEGMEN

------------------------------ --------- --------- ------

SYSTEM                         ONLINE    PERMANENT MANUAL

PSAPUNDO                       ONLINE    UNDO      MANUAL

SYSAUX                         ONLINE    PERMANENT AUTO

PSAPTEMP                       ONLINE    TEMPORARY MANUAL

PSAPSR3                        ONLINE    PERMANENT AUTO

PSAPSR3USR                     ONLINE    PERMANENT AUTO

TOOLS                          ONLINE    PERMANENT AUTO

PSAPSR3731                     ONLINE    PERMANENT AUTO

List of datafiles for tablespace

SQL> select file_name from dba_data_files where tablespace_name='<TABLESPACE_NAME>';

Find tables being used by tablespace

SQL> select table_name from dba_tables where tablespace_name='PSAPSR37XX';

Check autoextend

SQL> select TABLESPACE_NAME,SEGMENT_SPACE_MANAGEMENT from dba_tablespaces;

Users

Show database users

SQL> SELECT USERNAME, ACCOUNT_STATUS, AUTHENTICATION_TYPE FROM dba_users;

USERNAME                       ACCOUNT_STATUS                   AUTHENTI

------------------------------ -------------------------------- --------

SAPSR3                         OPEN                             PASSWORD

SYSTEM                         OPEN                             PASSWORD

SYS                            OPEN                             PASSWORD

MGMT_VIEW                      OPEN                             PASSWORD

OPS$SAPSERVICESAP              OPEN                             EXTERNAL

OPS$ORASAP                     OPEN                             EXTERNAL

NAGIOS                         OPEN                             PASSWORD

DUMMY                          OPEN                             PASSWORD

ADMIN                          OPEN                             PASSWORD

PERFSTAT                       OPEN                             PASSWORD

APPQOSSYS                      OPEN                             PASSWORD

USERNAME                       ACCOUNT_STATUS                   AUTHENTI

ORACLE_OCM                     OPEN                             PASSWORD

OPS$SAPADM                     OPEN                             EXTERNAL

DIP                            OPEN                             PASSWORD

OUTLN                          OPEN                             PASSWORD

SYSMAN                         EXPIRED(GRACE)                   PASSWORD

DBSNMP                         EXPIRED(GRACE)                   PASSWORD

Unlock user account

SQL> ALTER <USERNAME> ACCOUNT UNLOCK;

Create user

SQL> CREATE USER <USERNAME> IDENTIFIED BY <PASSWORD> [PROFILE <PROFILE_NAME>]

Password complexity

Execute script sap_utlpwdmg.sql from SAP Note 1522952 in SQL Plus:

SQL> @sap_utlpwdmg.sql

Activate complexity in profiles:

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_VERIFY_FUNCTION verify_function_sap;

SQL> ALTER PROFILE SAPUPROF LIMIT PASSWORD_VERIFY_FUNCTION verify_function_sap;

Deativate complexity in profiles:

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_VERIFY_FUNCTION NULL;

SQL> ALTER PROFILE SAPUPROF LIMIT PASSWORD_VERIFY_FUNCTION NULL;

Datafiles

Check datafiles

SQL> SELECT FILE#, STATUS, ENABLED FROM  v$datafile;

     FILE# STATUS  ENABLED

---------- ------- ----------

       375 ONLINE  READ WRITE

       376 ONLINE  READ WRITE

       377 ONLINE  READ WRITE

       378 ONLINE  READ WRITE

       379 ONLINE  READ WRITE

       380 ONLINE  READ WRITE

List of datafiles

SELECT FILE_NAME AS Datafile, BYTES/1024/1024 AS "Size(MB)" FROM DBA_DATA_FILES WHERE TABLESPACE_NAME LIKE '%<TABLESPACE_NAME>%';

 

Datafile                                          Size(MB)

------------------------------------------ ---------------

[...]

/oracle/SAP/sapdata9/sr3731_3/sr3731.data3           20000

/oracle/SAP/sapdata9/sr3731_4/sr3731.data4           20000

/oracle/SAP/sapdata9/sr3731_5/sr3731.data5           20000

/oracle/SAP/sapdata9/sr3731_6/sr3731.data6           20000

/oracle/SAP/sapdata9/sr3731_7/sr3731.data7            3500

/oracle/SAP/sapdata5/sr3_348/sr3.data348             31744

Resize datafile until size

SQL> ALTER DATABASE DATAFILE '<PATH_TO_DATAFILE>' RESIZE <SIZE>M;

 

Database altered.

Redologs

List of redologs groups and files belonging to each group

SELECT a.group#, a.member, b.bytes FROM v$logfile a, v$log b WHERE a.group# = b.group#;

 

    GROUP# MEMBER

---------- -----------------------------------

        26 /oracle/SAP/origlogB/log_g26_m1.dbf

        26 /oracle/SAP/mirrlogB/log_g26_m2.dbf

        25 /oracle/SAP/origlogA/log_g25_m1.dbf

        25 /oracle/SAP/mirrlogA/log_g25_m2.dbf

        24 /oracle/SAP/origlogB/log_g24_m1.dbf

        24 /oracle/SAP/mirrlogB/log_g24_m2.dbf

        23 /oracle/SAP/origlogA/log_g23_m1.dbf

        23 /oracle/SAP/mirrlogA/log_g23_m2.dbf

        22 /oracle/SAP/origlogB/log_g22_m1.dbf

        22 /oracle/SAP/mirrlogB/log_g22_m2.dbf

        21 /oracle/SAP/origlogA/log_g21_m1.dbf

        21 /oracle/SAP/mirrlogA/log_g21_m2.dbf

Active Redolog groups

SQL> select group#, status from v$log;

 

    GROUP# STATUS

---------- ----------------

        21 INACTIVE

        22 INACTIVE

        23 CURRENT

        24 INACTIVE

        25 INACTIVE

        26 INACTIVE

SAP Queries

system in upgrade, no import possible

SQL> update SAPSR3.uvers set PUTSTATUS='+';

SQL> commit;

BRBACKUP error

When you are getting follwing error:

BR0051I BRBACKUP 6.40 (43)

BR0055I Start of database backup: bebchpaa.anf 2014-01-16 01.00.34

BR0484I BRBACKUP log file: /oracle/SAP/sapbackup/bebchpaa.anf

BR0071E BRBACKUP currently running or was killed

BR0072I Please delete file /oracle/SAP/sapbackup/.lock.brb if BRBACKUP was killed

BR0073E Setting of BRBACKUP lock failed

BR0056I End of database backup: bebchpaa.anf 2014-01-16 07.00.04

BR0280I BRBACKUP time stamp: 2009-07-26 07.00.05

BR0054I BRBACKUP terminated with errors

BR0280I BRBACKUP time stamp: 2009-07-26 07.00.05

BR0291I BRARCHIVE will be started with options '-U -jid ALLOG20090607070000 -d util_file -c force -p initSAP.sap -cds'

Connect to database:

sqlplus /nolog

SQL> connect /as sysdba

End backup:

SQL> ALTER DATABASE END BACKUP;

Then check if lock exists the lock file and delete it. If not found then run the backup again.

Make sure you read these key SAP notes for SAP on Oracle (you need SAP Service Marketplace access):

• Recent Hot News
• Top Notes for Oracle 12c
• Top Notes for Oracle 11g
• Top Notes for Oracle 10g
• Top Notes for BR*Tools
• Top Notes for SAP Database Interface on Oracle
• Top Notes for SAP Installation / Upgrade / System Copy
• Miscellaneous Notes

Recent Hot News

Top Notes for Oracle 12c

Top Notes for Oracle 11g

I just set up TDE for tablespace encryption based on note 974876 and want to share the guide with you guys.
For a complete list of prerequisites and steps, please refer to note.

KBA 2126230 contains a PDF document with more details.

Steps in Nutshell:

1. Prerequisites
2. Preparation
3. Execution

Steps in Detail:

1. Prerequisites
   - ASO license. The Oracle Database Software ASO is always installed by default during an SAP installation. which means you can use TDE immediately without any additional installation tasks. If you bought the license from Oracle Corporation, please consult with Oracle first.
   - Oracle Database 10.2.0.4 or higher
   - SAP Kernel Release 6.40 and higher
   - SAP Basis Release 6.40 Support Package 22
   - SAP Basis Release 7.00 Support Package 16
   - SAP BR*Tools 7.00 patch 24 and higher
   
   
2. Preparation
   - create a backup of sqlnet.ora (for sake of security make sure every single sqlnet.ora is modified, not just in TNS_ADMIN,
   but in $ORACLE_HOME/network/admin as well)
   cp $TNS_ADMIN/sqlnet.ora $TNS_ADMIN/sqlnet.ora.SAVE
   cp $ORACLE_HOME/network/admin/sqlnet.ora $ORACLE_HOME/network/admin/sqlnet.ora.SAVE
   - supplement sqlnet.ora files with below entry (make sure the syntax is correct, otherwise database can not recognize it):
   ENCRYPTION_WALLET_LOCATION =(SOURCE = (METHOD = FILE)(METHOD_DATA =(DIRECTORY = /oracle/OL1/112_64/dbs)))
   - check if above path (specified in DIRECTORY) can be written by ORacle user (ora<sid> or 'oracle')
   - restart database
   - check if Wallet Directory was recognized by the database (below statement should show DIRECTORY in column WRL_PARAMETER)
   SQL> select WRL_PARAMETER,STATUS from V$ENCRYPTION_WALLET;
   - create encryption wallet (specify password in 'point 6' of BR*Tools menu, twice)
   OS> brspace -u / -f mdencr -a create
   - now check enryption wallet again (now, result should show you 'OPEN', if not check steps before and the syntax in sqlnet.ora)
   OS> brspace -u / -f mdencr -a show
   SQL> select WRL_PARAMETER,STATUS from V$ENCRYPTION_WALLET;
   - save encryption wallet
   OS> brspace -f mdencr -a save
   
   
3. Execution
   - Stop and start database
   SQL> shutdown immediate;
   SQL> startup;
   - open database with encryption wallet
   SQL> alter system set encryption wallet open identified by "<password specified in point 2 while creating wallet>";
   - create encrypted tablespace either in SQLPLUS or with BR*Tools
   If using BR*Tools, don't forget to specify "Tablespace encryption (encrypt) [yes]"
   OR
   SQL> create tablespace <encrypted tablespace following SAPs recomendations, like PSAPSR3....> extent management
   local autoallocate segment space management auto encryption default storage (encrypt) datafile '<location of datafile>' size 20M;
   - transfer tables and indexes to the new tablespace with BR*tools
   - check if there are no more objects,segments,extents in old unencrypted tablespace
   - delete old unencrypted tablespace and datafiles

UPDATE: There is a PDF document with all steps uploaded to Oracle - SAP on Oracle - SCN Wiki under 'Best Practice Documents'

Regards,
János

Hi,

I am sharing with you the steps I made.

0.) Don't forget the use the latest version of BR*Tools, as SSFS connection method is supported as of BR*Tools 7.20 (27)!

1.) First, we have to create the SSFS directories for BR*Tools (note, this can be anywhere. In my case, it is only an Oracle installation without SAP system on it.,so I used SAPDATA_HOME a the source location.)

2.) Create BRT$ADM

3.) Change the password of BRT$ADM user

4.) Test it

After you have set up the SSFS BR*Tools database user (BRT$ADM), you can call all BR*Tools executables with the option "-u //" to connect to the database using the data that you have stored in the secure storage.

5.) Change DBACOCKPIT/DB13 settings.

You can also use the new connection method for BR*Tools calls in the CCMS transaction DBACOCKPIT/DB13. For this, you must replace the option "-u /"

manually (for example with transaction SE16) with the option "-u //" in the SAP  table SDBAC in the field PSTRING.
UPDATE: There is a script attached to SAP note 1764043, that changes the entries automatically for you. Very handy.

That's all.

Regards,

János

Oracle Database 12c Automatic Data Optimization (ADO) Certified by SAP New!

Extension for Period of Waived Oracle 11g Extended Support Fees

Oracle Database In-Memory Certified by SAP

Oracle Database 12c Certified by SAP

SAP on Oracle Development Update (November 2015)

New BR*Tools Patch Now Available (with support for Oracle 12c)

Oracle Linux 7 Certified by SAP

New Secure Connect Method 

SAP on Oracle Presentations

Optimized Loading into the F-Fact Table

Here are some presentations from previous DOAG conferences:

• New Features in Software Provisioning Manager for SAP & Oracle
• Evolution of Oracle Software Installation in SAP Environments
• Cloning of Oracle Homes on Oracle RAC 11.2 Cluster Nodes After Linux Upgrade
• Configuration Overview Command
• Oracle LGWR Analysis

Recently Featured Content

Here you can find information on database security for the Oracle database running SAP systems. General information on Oracle security as well as information related to specific Oracle security products such as Advanced Security Option (ASO) is included here.

Oracle Database Vault for SAP NetWeaver

This presentation discusses Oracle Database Vault 12c Release 1 for SAP NetWeaver.

High Security for SAP Data with Oracle Database Vault and Transparent Data Encryption

This paper from the German Oracle Users Conference (DOAG) discusses security issues affecting Oracle databases in an SAP environment, including Transparent Data Encryption (TDE) and Data Vault (DV).

Oracle Database Vault for SAP

This presentation from Oracle World 2008 gives an overview of Oracle Database Vault, including SAP certification, best practices, and performance.

Database Security for Oracle

A thorough security plan at your site must include securing application databases. This SAP whitepaper explains how best to secure SAP applications running on Oracle. Specifically, you'll learn about securing the OPS$ mechanism and securing DBA tools for Oracle including RMAN, BRBACKUP, and BRRECOVER.

Here you can find resources and guides to help you install or upgrade your SAP on Oracle application environment. Please note - technical documentation of this type resides on the SAP Support Portal in the SAP Service Marketplace (SMP). An SMP login is required to access these guides and SAP Notes.

Tools

MOPatch version 1.9 is now available for SAP customers running Oracle 10.2.0.4. This tool simplifies the task of installing multiple Oracle database patches into an Oracle Home. It automates the process of unpacking the patches and calling "opatch apply" for each of them. You can download MOPatch from SAP Note 1027012, which also tells you how to use the tool.

General

Getting Started

Upgrade to Oracle Database 12c Release 1 (12.1): UNIX  (SMP login required)

Upgrade to Oracle Database 12c Release 1 (12.1): Windows  (SMP login required)

System Copy

These presentations are from the 2013 German Oracle Users Conference (DOAG):

• New Features in Software Provisioning Manager for SAP & Oracle

• SAP System Copy on Oracle

• SAP System Copy with Oracle: What to Look Out For

Homogenous Database Copies With BR*Tools 
This presentation from the German Oracle users Conference (DOAG) shows how to make homogeneous database copies using the new BR*Tools procedure.

Miscellaneous

Here are some presentations:

• SAP Bundle Patches - Patch Management with Oracle 12c
• Evolution of Oracle Software Installation in SAP Environments
• Cloning of Oracle Homes on Oracle RAC 11.2 Cluster Nodes After Linux Upgrade

Introduction

The main goal of this document is serving as a base for SAP Basis Administrator who work with Oracle Databases and want to perform simple checks.

I will try to improve this document as much as I can.

Of course, do not hesitate to collaborate by adding more SQL queries.

Considerations

DBSID: SAP

SAPSID: SAP

System variables

SPOOL <filename>

SET LINESIZE 32767

SET WRAP OFF

SPOOL OFF

Check SQL*Plus User's Guide and Reference.

Database

Show Oracle Database version

SQL> SELECT * FROM v$version;

BANNER

--------------------------------------------------------------------------------

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

PL/SQL Release 11.2.0.3.0 - Production

CORE    11.2.0.3.0      Production

TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production

NLSRTL Version 11.2.0.3.0 - Production

Show database details

SQL> SELECT NAME, LOG_MODE, OPEN_MODE, DATABASE_ROLE, PLATFORM_NAME FROM  v$database;

 

NAME      LOG_MODE     OPEN_MODE            DATABASE_ROLE    PLATFORM_NAME

--------- ------------ -------------------- ---------------- --------------------------

SAP       NOARCHIVELOG READ WRITE           PRIMARY          AIX-Based Systems (64-bit)

Show database size

SQL> SELECT SUM(BYTES)/1024/1024/1024 AS "DBSIZE(GB)" FROM dba_data_files;

 

DBSIZE(GB)

----------

5312.59766

Show Oracle Instant Client Version

SQL> select distinct client_version from v$session_connect_info where sid = sys_context('userenv', 'sid');

 

 

CLIENT_VERSION

--------------

11.2.0.3.0

For a list of all possibilities to check and identify Oracle Instant Client Version check this document.

Installed components in Database

SQL> SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;
 
 
CLIENT_VERSION
--------------
11.2.0.3.0

Is Database of type OLAP?

SQL> SELECT * FROM V$OPTION WHERE PARAMETER = 'OLAP';
CLIENT_VERSION
--------------
11.2.0.3.0

Instance

Show database instance details

SQL> SELECT INSTANCE_NAME, HOST_NAME, VERSION, STARTUP_TIME, STATUS, INSTANCE_ROLE FROM v$instance;

INSTANCE_NAME  HOST_NAME      VERSION     STARTUP_TIME    STATUS       INSTANCE_ROLE   

-------------  ---------      -------     ------------    ------       -------------   

SAP            SAPSERVER     11.2.0.3.0  26-MAR-15      OPEN         PRIMARY_INSTANCE

DB Schema for SAP

SQL> SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'T000';

OWNER
------------
SAPSR3
 

Tablespaces

Show tablespaces details

SQL> SELECT TABLESPACE_NAME, STATUS, CONTENTS, SEGMENT_SPACE_MANAGEMENT FROM dba_tablespaces;

TABLESPACE_NAME                STATUS    CONTENTS  SEGMEN

------------------------------ --------- --------- ------

SYSTEM                         ONLINE    PERMANENT MANUAL

PSAPUNDO                       ONLINE    UNDO      MANUAL

SYSAUX                         ONLINE    PERMANENT AUTO

PSAPTEMP                       ONLINE    TEMPORARY MANUAL

PSAPSR3                        ONLINE    PERMANENT AUTO

PSAPSR3USR                     ONLINE    PERMANENT AUTO

TOOLS                          ONLINE    PERMANENT AUTO

PSAPSR3731                     ONLINE    PERMANENT AUTO

List of datafiles for tablespace

SQL> select file_name from dba_data_files where tablespace_name='<TABLESPACE_NAME>';

Find tables being used by tablespace

SQL> select table_name from dba_tables where tablespace_name='PSAPSR37XX';

Check autoextend

SQL> select TABLESPACE_NAME,SEGMENT_SPACE_MANAGEMENT from dba_tablespaces;

Users

Show database users

SQL> SELECT USERNAME, ACCOUNT_STATUS, AUTHENTICATION_TYPE FROM dba_users;

USERNAME                       ACCOUNT_STATUS                   AUTHENTI

------------------------------ -------------------------------- --------

SAPSR3                         OPEN                             PASSWORD

SYSTEM                         OPEN                             PASSWORD

SYS                            OPEN                             PASSWORD

MGMT_VIEW                      OPEN                             PASSWORD

OPS$SAPSERVICESAP              OPEN                             EXTERNAL

OPS$ORASAP                     OPEN                             EXTERNAL

NAGIOS                         OPEN                             PASSWORD

DUMMY                          OPEN                             PASSWORD

ADMIN                          OPEN                             PASSWORD

PERFSTAT                       OPEN                             PASSWORD

APPQOSSYS                      OPEN                             PASSWORD

USERNAME                       ACCOUNT_STATUS                   AUTHENTI

ORACLE_OCM                     OPEN                             PASSWORD

OPS$SAPADM                     OPEN                             EXTERNAL

DIP                            OPEN                             PASSWORD

OUTLN                          OPEN                             PASSWORD

SYSMAN                         EXPIRED(GRACE)                   PASSWORD

DBSNMP                         EXPIRED(GRACE)                   PASSWORD

Unlock user account

SQL> ALTER <USERNAME> ACCOUNT UNLOCK;

Create user

SQL> CREATE USER <USERNAME> IDENTIFIED BY <PASSWORD> [PROFILE <PROFILE_NAME>]

Delete SAP* user (or another user)

First we check if user exists. Then delete it.

SQL> SELECT MANDT, BNAME FROM <DB_SCHEMA>.USR02 WHERE MANDT = 'XXX' AND BNAME = 'SAP*';
SQL> DELETE FROM <DB_SCHEMA>.USR02 WHERE MANDT = 'XXX' AND BNAME = 'SAP*';

(change <DB_SCHEMA> and MANDT)

Password complexity

Execute script sap_utlpwdmg.sql from SAP Note 1522952 in SQL Plus:

SQL> @sap_utlpwdmg.sql

Activate complexity in profiles:

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_VERIFY_FUNCTION verify_function_sap;

SQL> ALTER PROFILE SAPUPROF LIMIT PASSWORD_VERIFY_FUNCTION verify_function_sap;

Deativate complexity in profiles:

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_VERIFY_FUNCTION NULL;

SQL> ALTER PROFILE SAPUPROF LIMIT PASSWORD_VERIFY_FUNCTION NULL;

Datafiles

Check datafiles

SQL> SELECT FILE#, STATUS, ENABLED FROM  v$datafile;

     FILE# STATUS  ENABLED

---------- ------- ----------

       375 ONLINE  READ WRITE

       376 ONLINE  READ WRITE

       377 ONLINE  READ WRITE

       378 ONLINE  READ WRITE

       379 ONLINE  READ WRITE

       380 ONLINE  READ WRITE

List of datafiles

SELECT FILE_NAME AS Datafile, BYTES/1024/1024 AS "Size(MB)" FROM DBA_DATA_FILES WHERE TABLESPACE_NAME LIKE '%<TABLESPACE_NAME>%';

 

Datafile                                          Size(MB)

------------------------------------------ ---------------

[...]

/oracle/SAP/sapdata9/sr3731_3/sr3731.data3           20000

/oracle/SAP/sapdata9/sr3731_4/sr3731.data4           20000

/oracle/SAP/sapdata9/sr3731_5/sr3731.data5           20000

/oracle/SAP/sapdata9/sr3731_6/sr3731.data6           20000

/oracle/SAP/sapdata9/sr3731_7/sr3731.data7            3500

/oracle/SAP/sapdata5/sr3_348/sr3.data348             31744

Resize datafile until size

SQL> ALTER DATABASE DATAFILE '<PATH_TO_DATAFILE>' RESIZE <SIZE>M;

 

Database altered.

Redologs

List of redologs groups and files belonging to each group

SELECT a.group#, a.member, b.bytes FROM v$logfile a, v$log b WHERE a.group# = b.group#;

 

    GROUP# MEMBER

---------- -----------------------------------

        26 /oracle/SAP/origlogB/log_g26_m1.dbf

        26 /oracle/SAP/mirrlogB/log_g26_m2.dbf

        25 /oracle/SAP/origlogA/log_g25_m1.dbf

        25 /oracle/SAP/mirrlogA/log_g25_m2.dbf

        24 /oracle/SAP/origlogB/log_g24_m1.dbf

        24 /oracle/SAP/mirrlogB/log_g24_m2.dbf

        23 /oracle/SAP/origlogA/log_g23_m1.dbf

        23 /oracle/SAP/mirrlogA/log_g23_m2.dbf

        22 /oracle/SAP/origlogB/log_g22_m1.dbf

        22 /oracle/SAP/mirrlogB/log_g22_m2.dbf

        21 /oracle/SAP/origlogA/log_g21_m1.dbf

        21 /oracle/SAP/mirrlogA/log_g21_m2.dbf

Active Redolog groups

SQL> select group#, status from v$log;

 

    GROUP# STATUS

---------- ----------------

        21 INACTIVE

        22 INACTIVE

        23 CURRENT

        24 INACTIVE

        25 INACTIVE

        26 INACTIVE

SAP Queries

system in upgrade, no import possible

SQL> update SAPSR3.uvers set PUTSTATUS='+';

SQL> commit;

BRBACKUP error

When you are getting follwing error:

BR0051I BRBACKUP 6.40 (43)

BR0055I Start of database backup: bebchpaa.anf 2014-01-16 01.00.34

BR0484I BRBACKUP log file: /oracle/SAP/sapbackup/bebchpaa.anf

BR0071E BRBACKUP currently running or was killed

BR0072I Please delete file /oracle/SAP/sapbackup/.lock.brb if BRBACKUP was killed

BR0073E Setting of BRBACKUP lock failed

BR0056I End of database backup: bebchpaa.anf 2014-01-16 07.00.04

BR0280I BRBACKUP time stamp: 2009-07-26 07.00.05

BR0054I BRBACKUP terminated with errors

BR0280I BRBACKUP time stamp: 2009-07-26 07.00.05

BR0291I BRARCHIVE will be started with options '-U -jid ALLOG20090607070000 -d util_file -c force -p initSAP.sap -cds'

Connect to database:

sqlplus /nolog

SQL> connect /as sysdba

End backup:

SQL> ALTER DATABASE END BACKUP;

Then check if lock exists the lock file and delete it. If not found then run the backup again.

This document show some step to do for change the default port to Oracle Listener "1521"

First that all, check the port. Use the command "lsnrctl status".

Stop SAP with the database too, change the port onthe "tnsnames.ora" file.

That's all

                                                            Oracle 12c Upgrade

This document describes the process of executing Oracle 12c Database upgrades, from the source 11g.

In addition, this manual provides information about compatibility, upgrading applications, and important changes in the new Oracle Database release.

1 Preparations/Prerequisites Step’s

The following activities can be executed with the system up and running.

1. The software Packages can be placed at a specific location as per your understanding. Like we have kept at the following location /net/hnfssap/sap/infra/install/ORACLE12

1. Oracle Stage /net/hnfssap/sap/infra/install/ORACLE12/stage_12
2. Oracle Client  12c à /net/hnfssap/sap/infra/install/ORACLE12/instantclient_12
3. DBA Tools 7.40 (pl17) à /net/hnfssap/sap/infra/install/ORACLE12/brtools
4. MOPatch à /net/hnfssap/sap/infra/install/ORACLE12/MOPatch
5. OPatch à /net/hnfssap/sap/infra/install/ORACLE12/OPatch

    2. Request Unix team to create additional Logical Volume

1. /dev/mapper/sap<sid>db-vol<nn>
2. /oracle/<SID>12102
3. 15 GB

   3. Create directory /etc/oracle and make it 777. It will avoid the issue faced during the oracle upgrade later on.

     4. Check the free space in our HNFS stage. Minimum free space 10GB

1.     #df -h |grep hnfssap:/sap/infra/Install

     5. Backup of current oracle_home and oraInventory (position to the proper source location)

            a.    #tar -cvf /net/hnfssap/sap/infra/install/ORACLE12/oraInventory.tar oraInventory

            b. #tar -cvf /net/hnfssap/sap/infra/install/ORACLE12/11204.tar 11204

     6. Create SPFILE for backup

1. @sqlplus /as sysdba
2. #create pfile from spfile;
3. Save the new spfile: cp init<SID>.ora init<SID>.ora.orig

     7. Check the patch inventory, and save the extract to a txt file.

1. #./opatch lsinventory

     8. Check the oraInst.loc file. Outcome expected is the correct  oraInventory Location

1. #more /etc/oraInst.loc

     9. Prepare the export display. Open two sessions, one will be used with the Oracle 11g variables and the second one with the 12c Variables:

1. Open exceed X11
2. #xhost+
3. #sudo su – ora<sid>
4. #export DISPLAY=<your_ip>:0.0
5. #xclock (to check if it works)

    10. Set the 12c Variables

        a.    export ORACLE_HOME=/opt/oracle/<SID>/product/12102

        b.    export ORACLE_HOME_SRC=/opt/oracle/<SID>/product/11204

        c.    export ORACLE_HOME_TGT=/opt/oracle/<SID>/product/12102

    11. Link the new stage located in HNFS. The Oracle 12c Stage contains the latest scripts for the RUNINSTALLER (Patch Level 059 - 02062015). Check                 OSS note 1915301 in case a new script is available

1. #cd /oracle
2. # ln –s /net/hnfssap/sap/infra/install/ORACLE12/stage_12 stage

    12. Launch the RunInstaller Check

1. #cd /net/hnfssap/sap/infra/install/ORACLE12/stage_12/database/SAP
2. #RUNINSTALLER –check
3. Request Unix to fix the warning and install the missing packages

2 Installation of new Oracle_Home 12.1.0.2

1. With the 12c Variables, launch the RUNINSTALLER

Click Next

Click Yes

Select Install Database software, then click Next

Select Single instance database installation, then click Next

Select English ---  Click Next

Select the Database Edition then Click Next

Hidden the <SID>

Select the correct Oracle Base and Oracle_Home locations, then click Next

Ignore the WARNING and click YES

Click Next

If already checked with Unix and the warning are still there, click Ignore All then click Next

Click Yes

Check and then click Install

Run the script as suggested

Click on Close

3. Install the Sap Bundle Patch (still with variables 12c)

1. a. Upgrade the MOPatch and OPatch executables
2. b. Position the zip file in the MOPatch directory
3. c. #./ mopatch.sh -v -s SAP12102P_1511-20012300.zip

Link Status:

  Link script “./link.hostname.sh” executed successfully

Orasid>

4.  Launch the pre_upgrade script from the new Oracle_Home 12c

a.       sqlplus / as sysdba @pre_upgrade_status.sql

5. Launch the dbua.sh –qand check the warning (in this case, the display variables were not properly set)

User is -- ora<SID>

6. Launch the upgrade script dbua.sh

Check if the DB is up and running, then click Next

Select Upgrade Oracle Instance, then click Next

Prerequisite Checks will run automatically

Click Next, hidden the <SID>

Un-check and then click Next

Un-check andthen click Next, hidden the<SID>

clickNext, hidden the<SID>

Select the own backup strategy then clickNext, hidden the<SID>

Check the details then click Finish

Hostname:/etc # ll |grep oracle

Drwxrwxrwx     2 root        root             4096     oracle

Hostname:/etc #

Refer to this link, if required-:

https://community.oracle.com/thread/3696552?start=0&tstart=0

                                                  Post Activities

1. Update the SQL*Net configuration files:

            a. Copy the listener.ora, sqlnet.ora and tnsnames.ora from the Oracle 11 to the 12c $ORACLE_HOME/network/admin

            b. Adjust the files with the new oracle12 locations

2. Check the symbolic link for the runtime Oracle home.

            a. # cd /oracle/<SID>

            b. # ln -s /oracle/DBSID/12102 121

3. Adapt the environment of the <sid>adm user.

            a. Log on as user adm and adapt the variables listed below in the .dbenv* files.

            b. Set the ORACLE_HOME environment variable to new Oracle home

4. Adapt the environment of the ora user.

5. Edit the /etc/oratab file including the following line:

     a. <SID>:/opt/oracle/<SID>/product/12102:N

6. Start the database and listener process as <ora>sid user.

7. Perform post-upgrade checks.  Refer Note : SAP Note 1915315

8. Perform post-upgrade tasks

     a. $brconnect -u / -c -f stats -t system_stats

     b. $ brconnect -u / -c -f stats -t oradict_stats

     c. $ brconnect -u / -c -f stats -t all -f collect -p 4

9. Update the Oracle Instant Client.

     a. Copy the oracle client from the HNFS location

     b. #cd /oracle/client/12x

     c. #ln -s instantclient_12102 instantclient

10.  Update BR*Tools.

     a. Copy the executables from the HNFS location

11.  Backup the database.

12.  Unistall the old Oracle_Home 11g

       a. # ./runinstaller -deinstall -home <path_of_Oracle_home_to_be_deinstalled>

End of Document

Index storage capacity analysis

&

Re-build

Introduction:

Indexes are the vital component in database to search data in most optimal way using filter. By continuous changes in the data due to Insert, Update and Delete operations, the index stored on the database gets fragmented thus increasing Application response time and consuming hardware resources like disk space and CPU. Index rebuild is considered as one of the important activity in performance optimization.

1. Index storage capacity analysis

Execute report RSORAISQ/RSORAISQN through T-code SE38.

Provide any ID to distinguish it from others.

Provide the Index, Table and Tablespace name as shown. (Currently we are analyzing the PSAPSR3 Tablespace so it is provided).

Choose "Start workingset" option with Analyze (Fast) option and execute the report in background.

Check the job status from SM37 --> job name RSORAISQN.

Upon successful completion of job execute the report again. And choose the option “Show History” to get the results.

The report will provide us the list of indexes with their size, storage capacity and other details.

Sort the details in the report by index size and storage capacity and extract the details in sheet.

2. Index Re-build Methods

Method 1: Execute the report RSANAORA (Recommended)

Execute the report RSANAORA.

Select the Index option --> Enter Index names that are to be rebuilt from the extracted sheet.

(To avoid the system load it’s recommended to choose indexes batch wise for rebuild)

After copying the list of Indices through clipboard, select ALTER INDEX REBUILD ONLINE option

Execute the program in Background

This method is recommended as it does the index rebuild by online method.

Method 2: Transaction code – DBACOCKPIT/ DB02OLD

Execute the Transaction Code DB02OLD

Choose the option current sizes

Choose Tables/Indexes option.

Select the index and choose for detailed analysis option.

In the detailed analysis it will show the size of the index which is 192 KB in the current case.

From the menus choose Alter index --> Rebuild

Transaction Code – DBACOCKPIT

Execute the T-code DBACOCKPIT and navigate as space --> segments --> detailed analysis.

From the main screen select the Index.

Main Data tab you can validate / Rebuild index

Storage tab provides the current size and storage quality of selected index

Method 3: Brtools

You can use brtools for rebuild indexes

Launch the brtools by ora<SID> user and choose the following options to traverse.

Method 4: By executing Oracle query

Connect to oracle by

Sqlplus / as sysdba

And execute the query as

Syntax: alter index <tablesapace_name>.<index_name> REBUILD ONLINE

E.g. alter index SAPSR3.CRM_ACE2_OBJ_WL~0 REBUILD ONLINE

3. Result/Observation:

The usable memory capacity of the tablespace is increased. The increased system response time can also be observed.

This can be checked by T-code ST04 --> space --> Tablespace --> Overview.

Before index rebuild:

After index rebuild:

4. Reference Notes:

332677 – Alternatives to rebuild indexes

682926 – Problems with Create/rebuild index with the solutions.

712098 - RSORAISQ: Index Storage Quality Management, in order to fix authorization problem.