SAP Oracle Upgrade 11G to 12C on AIX

Summary:-

This document contains the steps that how to do the oracle upgrade 11 G to 12 C.  I have gathered the information from some SAP Notes and upgrade document from SAP site.  The following method will reduce the downtime of SAP application.First install the oracle database software only and then do the upgrade using DBUA method.

Author: Brindavan Mookaiah

Designation: SAP BASIS Consultant

Table of content:-

1) Take full backup of database ......................................................

2) Download the software required for the upgrade............................

3) Check and, if necessary, set the DISPLAY environment variable ..

4) Configure Secure Storage in File System.....................................

5) Migrate to the Oracle Database Software Owner oracle................

6) Extract the Oracle software........................................................

7) Install the Oracle database software ...........................................

8) Run the pre-upgrade scripts........................................................

9) Upgrade from 11g to 12G with using DBUA method.....................

10) Performa the post upgrades scripts...........................................

11) Perform the post upgrade steps.................................................

Oracle 12c Architecture:-

Image may be NSFW.
Clik here to view.

Information on eye :-

There are two main SAP note need to go through before upgrading oracle database.

• SAP Note :2133079 - Oracle Database 12c: Integration in SAP environment
• SAP note :1914631 provides important technical information about using Oracle 12.1 in a SAP environment, like database installation/upgrade guidelines, software download, patches, etc.

Oracle Upgrade requirements to meet the software:-

1) Database Direct upgrade 10.2.0.5.0/11.2.0.2.0 / 11.2.0.3.0/11.2.0.4.0 upgrade to 12.1.0.2.0

2) Oracle Database 12c Release 1 (12.1) is only released and certified for SAP products running with SAP BASIS 7.00 and above,

     and SAP kernel release 7.21   EXT and above

3) OS level fix required to fix during upgrade or before.

4) create filesystem like " /oracle/SID/121"

1) Take full backup of database

•    Run full backup before upgrade
•    Take back of oracle_home directory and oracle profile

2) Download the software required for the upgrade

•    Download the Oracle Database 12c Release 1 (12.1) software, required patches, and Oracle 12.1 Instant Client software from:         "support.sap.com/software/databases.html Oracle"
• Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: "support.sap.com/swdc"  BR*Tools supports the Oracle Database 12c Release 2 (12.1), as of release 7.20 (patch level 40).or Release patch level 1) . For more information, see SAP Note 2087004

3) Check and, if necessary, set the DISPLAY environment variable

•    Set the DISPLAY environment variable to Shell export DISPLAY=hostname:0:0 if you use x-mangare or x-trem

4) Configure Secure Storage in File System

•   Follow the procedure described in SAP Notes 1639578 and 1622837, which describe the configuration of SSFS in detail.
• Check that the environment variables from SSFS have been changed in the .sapenv* files.

5) Migrate to the Oracle Database Software Owner oracle

Create the directory to place the extracted software:

● Oracle software stage directory

● Oracle inventory directory

Procedure 1.

For the extraction of the software for Oracle Database 12c Release 1 (12.1.0.2)

create the staging directory:

$  mkdir -p /oracle/stage/12102

$ chmod 755 /oracle/stage/12102

Example

$ cd /oracle/stage/12102

$ SAPCAR -xvf /OR112164.SAR

$ SAPCAR -xvf /OR212164.SAR

Process Flow

1.   Back up the central Oracle inventory
2.   Update the SAP RUNINSTALLER installation scripts.
3.   Check the software installation prerequisites.
4.   Install the current Oracle database patch set.
5.   Install the current SAP bundle patch.

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

1.   Back up the central Oracle inventory

For  AIX, HP-UX, Solaris SPARC:

/var/opt/oracle/oraInst.loc ○

For  Linux: /etc/oraInst.loc

inventory_loc= <path_to_oracle_inventory>

Make a copy of the inventorty

$ cp -r oraInventory oraInventory..SAVE

Note: check the patch level of the RUNINSTALLER and check in SAP Note 1915301 whether a higher version is available. Update the higher version if required.

7)  Update the SAP RUNINSTALLER installation scripts.

Note: check the patch level of the RUNINSTALLER and check in SAP Note 1915301 whether a higher version is available. Update the higher version if required.

Login to the OS level with ora_sid or X-manager and go the directory where the media file available.Install Oracle Database Release 12.1 software, see SAP Note 1915301.

For Example:

$ cd /oracle/stage/121/database/SAP

$  ./RUNINSTALLER –version

During installation step it will ask to apply missing OS patches and OS packages and set OS kernel parameters as recommended by the OUI

On AIX, call the script rootpre.sh as user root:

$  /oracle/stage/12102/database/rootpre.sh.

You can find the oracle installation software screen shot in following link this might be same.

Oracle12c Database Installation steps

3)  You need to install the current (or latest) SAP bundle patch (SBP) into the new Oracle home once the patch done. You must install the SBP using the Oracle tool MOPatch. For more details see SAP Note 1027012. To install the generic patch, see also SAP Note 1915315.

    Procedure

•   Log on as the Oracle database software owner <ora_SID>.
•   Download the required patches.
•   Install the SBP into the new Oracle home according to the instructions in the SBP README file.

The installation of the SBP consists of these steps: 1. The installation of the SBP software into the Oracle home. 2. The change of the database structure and database properties (dictionary, parameter, properties)

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

Note : Once the installation binary done then run the Oracle pre-upgrade scripts check in SAP Note: 1915315.

Check the environmental ORACLE_HOME, ORACLE_SID and ORACLE_BASE. Make sure that ORACLE_HOME is set to the value of the current Oracle home.

8) Run the pre-upgrade scripts

Login into the OS level with ora_sid user.

For example:

$ cd /oracle//12102/sap/ora_upgrade/pre_upgrade

$ sqlplus / as sysdba

SQL> @pre_upgrade_tasks.sql

@pre_upgrade_checks.sql

Recommendation set parameter before upgrade:

remote_os_authent=TRUE.

COMPATIBLE is set to a value < 11, do not change this parameter before the upgrade from 10.2 to 12c although this is recommended by the pre-upgrade script.

Stop SAP Application

Loginto  OS level with ORA_ADM and stop SAP

$ stopsap r3

You can also stop the SAP application server with the sapcontrol tool:

$ sapcontrol -nr -function Stop

Make sure that the software owner <ora_swo> has write permissions (664) on the oratab file, which is

either /etc/oratab or /var/opt/oracle/oratab, depending on your operating system.

● Make sure that oratab contains the entry <DBSID>:<Oracle_home>:N

Example:-

Oracle 11g: OQ1:/oracle/OQ1/112_64: N

Oracle 10g: OQ1:/oracle/OQ1/102_64: N

Set the environment variables ORACLE_HOME_SRC and ORACLE_HOME_TGT, DB_SID, and ORACLE_BASE before you run the scrpit.

Set ORACLE_HOME_SRC and ORACLE_HOME_TGT.

• export ORACLE_HOME_SRC=/oracle/<DBSID>/112_64
• export ORACLE_HOME_TGT=/oracle/<DBSID>/12102
• export DB_SID=<DBSID>

9) Upgrade from 11g to 12G with using DBUA method

Start the DBUA. dbua.sap.sh is a wrapper script for 11g To 12C, once the upgrade done then run the  post-upgrade tasks.

Loginto the OS level with ora_sid user

$ ./dbua.sap.sh

Note : This is only reference screen shot.

Image may be NSFW.
Clik here to view.

1. The screen will appear to select Upgrade Oracle Database and then click -->  Next.

Image may be NSFW.
Clik here to view.

This will tell the source database and target database for upgrade. If the location path are ok then click --> Next

Image may be NSFW.
Clik here to view.

Click --> Next

Image may be NSFW.
Clik here to view.

On the Upgrade Options screen, select the following fields:

•    Recompile invalid objects
•    Upgrade Timezone Data If required, you can check the following:
•    Gather statistics before the upgrade (takes some time)
•   Set User Tablespaces to Read Only and then click --> Next

Image may be NSFW.
Clik here to view.

The next screen will ask to select the database type like EM cloud control or EM express and then click --> Next

Image may be NSFW.
Clik here to view.

Do not select any of the checkboxes for Moving database and then click -->  Next

Image may be NSFW.
Clik here to view.

The Network Configuration screen ignore and go for default selection and then click --> Next

Image may be NSFW.
Clik here to view.

The Recovery Options screen select the option “I have my own backup” and chose --> Next

Image may be NSFW.
Clik here to view.

On the Summary screen, review the Database Upgrade Summary and if you satisfied the click -->  Finish

Image may be NSFW.
Clik here to view.

8. The upgrade will start and once it finished then Click on Upgrade Results to see the results of the upgrade. 11. On the Results screen, after reviewing the upgrade results.

Image may be NSFW.
Clik here to view.

Click Close to close the DBUA.

11) Perform the post upgrade steps

1. You update the SQL*Net configuration files

     Logininto the OS level with ora_sid

"The easiest method to do this is to just copy the complete LISTENER_ entry from the file /network/admin/tnsnames.ora and add this entry unchanged to the file in /network/admin and $TNS_ADMIN/tnsnames.ora on the SAP side"

2. You check the symbolic link for the runtime Oracle home.

Create symbolic link go the directory

              $ cd /oracle/DBSID

            $  ln -s /oracle/DBSID/12102  /oracle//121

3. You adapt the environment of the adm user.

Log on as user adm and adapt the variables listed below in the .dbenv* files. 2. Set the ORACLE_HOME environment variable to new Oracle home,

$ export ORACLE_HOME=/oracle/SID/121

$ export ORACLE_BASE

Check the environment with:

$ env | grep ORACLE_HOME

$ env | grep ORACLE_BASE

$ env | grep PATH (this should no longer contain a reference to 112_64)

4. You adapt the environment of the ora user.

5. You start the database and listener process as user.

5.1. Log on as the Oracle database software owner ora, for example, oracle.

5.2. For user oracle, set the environment via oraenv or coraenv.

5.3. Start the listener and then start the database: lsnrctl start

sqlplus / as sysdba

SQL> startup

5.4. After the database upgrade, change the entry :/oracle//12102:N in /etc/oratab or /var/opt/oracle/oratab so that it now looks as follows: :/oracle//121:N

6. You perform post-upgrade checks.  Refer Note : SAP Note 1915315

1. Logon into the OS level with ora_sid .

$sqlplus / as sysdba

SQL> @?\rdbms\admin\utlu121s.sql

SQL> @post_upgrade_tasks.sql (if you have not already executed this with DBUA)

SQL> @post_upgrade_checks.sql

7. You perform post-upgrade tasks.

Login into os level with sapsid_adm user and run the below command You can perform this later if required.

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

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

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

8. You update the Oracle Instant Client.

Create the new client directory:

$ mkdir -p /oracle/client/12x

$ cd /oracle/client/12x

unpack the client software:

$ SAPCAR -xvf  <oracle_client_DVD>/OCL/OCL12164.SAR

$ cd /oracle/client/12x ln -s instantclient_12102 instantclient

Create the symbolic link for BR*Tools 7.40: 1.

$ cd /oracle/client

mv 11x_64 11x_64_save

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

9. Update BR*Tools.

You need to update the Brtool for more information see SAP Note : 2087004, 12741, and 1598594.

10. You back up the database.

Perform the full backup of database.

brbackup –u / –type offline –mode all –device disk –compress yes –language E

11. If required and not yet done, update the SAP executables.

          SAP kernel supported for Oracle 12c kernel should 7.21EXT

12. If not yet done, configure the Secure Storage in the File System (SSFS).

13. For systems with Java components – AS Java or AS ABAP+Java – update the JDBC driver references.

If your SAP software is version 7.0 or below, follows SAP Note 867976 to change the JDBC driver.     

If your SAP software is version 7.1 or higher, change the reference to the JDBC driver in the instance profile as described below.  Open the file with your text editor and search for property j2ee/dbdriver.

Replace the old driver location with the new one:

/oracle/client/<Oracle_client_major_version>x/instantclient/

<java_class_archive>.jar

Where <Oracle_client_major_version> is the major version of the Oracle client that you are using after

this upgrade. So for example, if you are now using Oracle 12.1, set the new driver location to /oracle/

client/12x/instantclient/<java_class_archive>.jar.

14. You restart the SAP system.

Stopsap r3

15. You configure the new features for Oracle Database 12c Release 1 (12.1). see SAP note : 1914631.

16. If not already done, migrate from software owner ora to software owner oracle, as described in Migrating to the Oracle Database Software Owner oracle.

17. You deinstall the old Oracle Home: SAP Note 1915314

18. You make sure that you have installed the required support packages for the SAP kernel supported for Oracle 12c. For AS Java or AS ABAP+Java, see also SAP Note 1777021.

Note : You may get some issue with Operating system like DBA groug or something please get tocuh with AIX team to fix the issue.

The instalation of SAP Netweaver products, in some situations, could be a little bit hard. Tier 3 instalations must be planned hard before installed.My mentor always says to me: spend 90% of the time planning and 10% of the time executing what you´ve been planned. Then, to help you on this phase, I built a RoadMap that may show to you the entire process of the instalation of SAP ECC EHP7 over Exadata and Oracle 11G.

Follow this map and your SAP ECC over Exadata will be installed in less than 32 hs.

Image may be NSFW.
Clik here to view.

Some Tips:

1. Save the picture on your PC and apply zoom. This map is large and zoom may turn your life easy.
2. Pay attention with the hostnames, before the instalation, check hostname, hostname -s and hostname -f results.
3. Always use the last SWPM;
4. Be aware about kernel supported by Exadata;
5. Check the availability of the exa-scan listener, ask your DBA for help;
6. Always use the Preparation phase on the instalation of the database;
7. Plan the users and PIDs (they are very important if you are installing on Linux servers).Use the same PID for the same users over your landscape
8. In the middle of the instalation, the instalation master may show you he name of one script that must be run on the Exadata. Pay attention for that. This script will install very important services for High availability on RAC.

Here some SAP notes and links that may help you.

1590515 - SAP Software and Oracle Exadata

1996481 - Using correct hostnames for Oracle Exadata Database Nodes

1619343 - SAPinst for Oracle Exadata on Oracle Linux and Solaris X86

1598868 - BR*Tools support for the Oracle Exadata Database Machine

http://www.oracle.com/us/products/database/sap-exadata-wp-409603.pdf

https://websmp210.sap-ag.de/~sapidb/011000358700000790092013

https://websmp108.sap-ag.de/~sapidb/012002523100010938582014E

See you soon!

Frederich Murador

SAP Netweaver Certified

SAP Hana SUP_1 Certified

Hi ,

Today I make a test about to use brtools to resize oracle redo log. Below are the steps:

Image may be NSFW.
Clik here to view.

my redo log is 100MB

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

seems we need to select all the redo logs

Image may be NSFW.
Clik here to view.

option 10, to give the new size, then c continue

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

redo log size changed.

Best regards,
James

Hi,

This document expains the step by step procedure to upgrade oracle client on SAP.

Platform:

Source

OS- AIX 7.1

Oracle client- 10.

Target

ORACLE Client- 11.2.0.4 V3

Media Used- 51049326 for ORACLE Client 11.2.0.4 V3

1. create a   dir 11x_64 in /oracle/client

os> mkdir -p /oracle/client/11x_64

2. dump the oracle client software to this new direcotry(only keep the directory name with 'instantclient_11204' in this new dir.)

change the permission of 'instantclient_11204' to sidadm:sapsys

3. creating soft link for this new client

os> cd /oracle/client/11x_64

os> ln -s /oracle/client/11x_64/instantclient_11204 instantclient

4. Change the entries of all env files under home dir(/home/sidadm). in these env files we have to replace the value of old client (10x_64) to new client(11x_64).

the files where change is required are:(1).dbenv_hostname.sh (2).dbenv_hostname.csh (3).dbenv.sh (4).dbenv.csh

5. check whether 11x has been reflected in the whole env files:

sidadm> env | grep 11x(it must give some output)

sidadm> env | grep 10x(output must be blank)

6. check whether soft link created or not?

go to this directory->

/oracle/client/11x_64

ls -lrt

total 8

drwxrwxrwx    2 sidadm   sapsys         4096 Dec 25 16:15 instantclient_11204

lrwxrwxrwx    1 root     system           41 Dec 25 16:18 instantclient -> /oracle/client/11x_64/instantclient_11204

**the output must be like this

7. check the version of current soft link client

sidadm> cd /oracle/client/11x_64/instantclient_11204

sidadm> ./genezi -v

Client Shared Library 64-bit - 11.2.0.4.0

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.

Extension for Period of Waived Oracle 11g Extended Support Fees New!

Oracle Database In-Memory Certified by SAP

Oracle Database 12c Certified by SAP

SAP on Oracle Development Update (November) New!

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

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

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

Image may be NSFW.
Clik here to view.

2.) Create BRT$ADM

Image may be NSFW.
Clik here to view.

3.) Change the password of BRT$ADM user

Image may be NSFW.
Clik here to view.

4.) Test it

Image may be NSFW.
Clik here to view.

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

Hello,

I had to configure this monitoring agents in Oracle RAC Nodes to show information on ST06, I was looking at different SCN discussions, SAP notes and blogs and they are confuse an not clear about the configuration. Naturally you can automatically monitor SAP Host Agent information only if there is a Application server in the same server which is not my case.

So lets start with the considerations to understand the guide:

1. CEN host is on the first application server (erpapp01)

2. CEN User (ADMIN) you can change the user if you want to.

3. RAC Nodes (erpdb01 and erpdb02).

4. SAP Host Agent is installed.

As told before when I check ST06N/OS07 info the RAC nodes does not show any information about the servers:

Image may be NSFW.
Clik here to view.

To make this configuration possible we need to use sapccmsr to push the information from SAP Host Agent to a SAP Application server gateway (erpapp01 in this case).

First check RZ21 to add erpdb01 and erpdb02 into CCMS monitoring

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

In our case we are using ADMIN user, you can use any user you want. Of course you need to assing this role to the user -> SAP_BC_CSMREG

Image may be NSFW.
Clik here to view.

The same for the next RAC node

Image may be NSFW.
Clik here to view.

When you save the SAP Application server tries to connect to the SAP Host Agent installed on the server, you should check that the agent is running. If everything is fine you should see a confirmation like this.

Image may be NSFW.
Clik here to view.

Then you need to download the ccms configuration to execute the sapccmsr command at os level.

Image may be NSFW.
Clik here to view.

Save the file and transfer it to the RAC Nodes.

Image may be NSFW.
Clik here to view.

We need to create 4 files in /sapmnt/SID/profile.

SAPCCMSR_DB01

SAPCCMSR_DB02

SAPOSCOL_DB01

SAPOSCOL_DB02

They contain this information. Make sure this directories exists and exe/saposcol path contains the saposcol binary.

SAPCCMSR_DB01

SAPSYSTEMNAME=PRD

SAPLOCALHOST=erpdb01

DIR_CCMS = /usr/sap/sapccmsr_db01

DIR_PERF=/usr/sap/sapccmsr_db01

DIR_WORK_SAPOSCOL=/usr/sap/saposcol_db01

exe/saposcol=/usr/sap/hostctrl/exe/saposcol

SAPCCMSR_DB02

SAPSYSTEMNAME=PRD

SAPLOCALHOST=erpdb02

DIR_CCMS = /usr/sap/sapccmsr_db02

DIR_PERF=/usr/sap/sapccmsr_db02

DIR_WORK_SAPOSCOL=/usr/sap/saposcol_db02

exe/saposcol=/usr/sap/hostctrl/exe/saposcol

SAPOSCOL_DB01

DIR_PERF = /usr/sap/saposcol_db01

SAPOSCOL_DB02

DIR_PERF = /usr/sap/saposcol_db02

Now we need to stop SAP Host Agent using command ./saphostexec -stop.

Image may be NSFW.
Clik here to view.

Then we log as sidadm and execute this on first RAC Node:

sapccmsr -DCCMS pf=/sapmnt/PRD/profile/SAPCCMSR_DB01 -t

This log should appear.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Then restart SAP Host Agent and saposcol

./saphostexec -restart

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Now we check ST06N and it shows full os information.

Image may be NSFW.
Clik here to view.

Do the same steps for the next node to configure the monitoring. Enjoy!

Hi ,

Today I make a test about to use brtools to resize oracle redo log. Below are the steps:

Image may be NSFW.
Clik here to view.

my redo log is 100MB

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

seems we need to select all the redo logs

Image may be NSFW.
Clik here to view.

option 10, to give the new size, then c continue

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

redo log size changed.

Best regards,
James

Hi,

This document expains the step by step procedure to upgrade oracle client on SAP.

Platform:

Source

OS- AIX 7.1

Oracle client- 10.

Target

ORACLE Client- 11.2.0.4 V3

Media Used- 51049326 for ORACLE Client 11.2.0.4 V3

1. create a   dir 11x_64 in /oracle/client

os> mkdir -p /oracle/client/11x_64

2. dump the oracle client software to this new direcotry(only keep the directory name with 'instantclient_11204' in this new dir.)

change the permission of 'instantclient_11204' to sidadm:sapsys

3. creating soft link for this new client

os> cd /oracle/client/11x_64

os> ln -s /oracle/client/11x_64/instantclient_11204 instantclient

4. Change the entries of all env files under home dir(/home/sidadm). in these env files we have to replace the value of old client (10x_64) to new client(11x_64).

the files where change is required are:(1).dbenv_hostname.sh (2).dbenv_hostname.csh (3).dbenv.sh (4).dbenv.csh

5. check whether 11x has been reflected in the whole env files:

sidadm> env | grep 11x(it must give some output)

sidadm> env | grep 10x(output must be blank)

6. check whether soft link created or not?

go to this directory->

/oracle/client/11x_64

ls -lrt

total 8

drwxrwxrwx    2 sidadm   sapsys         4096 Dec 25 16:15 instantclient_11204

lrwxrwxrwx    1 root     system           41 Dec 25 16:18 instantclient -> /oracle/client/11x_64/instantclient_11204

**the output must be like this

7. check the version of current soft link client

sidadm> cd /oracle/client/11x_64/instantclient_11204

sidadm> ./genezi -v

Client Shared Library 64-bit - 11.2.0.4.0

Hello Everyone,

We are in a project now that involves Oracle RAC (2 nodes) and SAP ERP, the oracle white papers are big and some of the commands you need to learn to administrate the RAC environment are confuse so here are the most common and useful commands for your RAC system.

Previous Info:

RDBMS: Oracle 11.2.0.4

RAC Node 1: erpdb01

RAC Node 2: erpdb02

SAP SID: PRD

DB SID:PRD

RAC Instances: PRD1 and PRD2

First log with user oracle in any node of the RAC database (first node in my case):

Image may be NSFW.
Clik here to view.

Now we check the actual status of the database. Both RAC instances (PRD1 and PRD2) are running.

     srvctl status database -d PRD

Image may be NSFW.
Clik here to view.

To stop only the instance PRD1 in the first RAC node we use this command:

     srvctl stop instance -d PRD -i PRD1

Image may be NSFW.
Clik here to view.

The same works for stopping the second RAC instance.

     srvctl stop instance -d PRD -i PRD2

Image may be NSFW.
Clik here to view.

For starting the instances separately we change the "stop" command for start like this:

     srvctl start instance -d PRD -i PRD1

Image may be NSFW.
Clik here to view.

     srvctl start instance -d PRD -i PRD2

Image may be NSFW.
Clik here to view.

Normally we use this commands to stop only one RAC instance for a schedule outage (patching for example), but when you need to stop directly both instances PRD1 and PRD2 you can use this command.

      srvctl stop database -d PRD

Image may be NSFW.
Clik here to view.

For starting both instances change the "stop" command for "start"

     srvctl start database -d PRD

Image may be NSFW.
Clik here to view.

Sometimes when the database don't start you can check if the ASM services is running with this command:

     srvctl status asm

Image may be NSFW.
Clik here to view.

With this command you can check the cluster services:

     go to the GRID path /oracle/GRID/112_64/bin

     crsctl check cluster -all

Image may be NSFW.
Clik here to view.

To check the status of the voting disks

     go to the GRID path /oracle/GRID/112_64/bin

     ./crsctl query css votedisk

Image may be NSFW.
Clik here to view.

To check the status of the scan_listener (This installation have only 3, you can have more)

     srvctl status scan_listener

Image may be NSFW.
Clik here to view.

To check the status of the nodeapps you use:

     srvctl status nodeapps -n erpdb01

     srvctl status nodeapps -n erpdb02

Image may be NSFW.
Clik here to view.

This command can be very useful too, you can check the status, running node, etc of all components in the RAC.

     crs_stat -t

Image may be NSFW.
Clik here to view.

Hope it helps you in your journey. Enjoy!

Hello,

Now we are going to show the functionality and the usage of sapctl service in RAC environments. Normally between srvctl, crsctl, sapctl you can get confuse with the commands you need to administrate the SAP HA subsystems (ASCS, ERS, DV, etc)

What does SAPCTL does?

1. You can create and remove any Oracle Clusterware configuration of the SAP HA subsystem.

2. You can start and stop the SAP HA subsystem that are created in the Oracle Clusterware, you can choose to start/stop as a whole or individual components.

3. You can check the status of any SAP HA subsystem created in the Oracle Clusterware.

4. You can relocate any SAP HA subsystem created in the Oracle Clusterware.

SAPCTL usage and commands

This working example assumes that you have completed all of this steps:

1. Oracle Clusterware is installed.

2. Oracle RAC is installed.

3. You have installed SAP and the SAPCTL package.

4. You have 2 RAC nodes.

5. Only ASCS and ERS services are installed in Oracle Clusterware, the SAP Instance is installed in a different host (No cluster service).

Previous Info:

First RAC Node:           erpdb01

Second RAC Node:      erpdb02

SAP SID:                      PRD

Oracle Version:            11.2.0.4

ASCS Instance:           ASCS01

ERS Instance:             ERS20

SAPCTL Version:          v8

First log in with sidadm to operating system level.

To check the status of all SAP HA subsystems installed in Oracle Clusterware you use this command:

     sapctl status all -sapsid PRD

Image may be NSFW.
Clik here to view.

To check the status of individual SAP HA subsystems installed in Oracle Clusterware you use this command:

     sapctl status abapvip/abapenq/abaprep -sapsid PRD

Image may be NSFW.
Clik here to view.

To check the which SAP Instace have been configured by Oracle Clusterware:

     sapctl config

Image may be NSFW.
Clik here to view.

To stop all SAP HA subsystems use this command:

     sapctl stop all -sapsid PRD

Image may be NSFW.
Clik here to view.

To stop all SAP HA subsystems use this command:

     sapctl start all -sapsid PRD

     As you can see the ERS Service will automatically started in the oposite node (erpdb02) where the ASCS service started.

Image may be NSFW.
Clik here to view.

If you need to start/stop individually any subsystem service you can use this commands:

     sapctl start/stop abapenq -sapsid PRD  

     sapctl start/stop abaprep -sapsid PRD

     sapctl start/stop abapvip -sapsid PRD (VIP IP for ASCS service)

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Now the commands to manually relocate subsytem services between the RAC Nodes

     ASCS01 service is running on erpdb01 -> relocate to erpdb02

     ERS20 service is running on erpdb02

     sapctl relocate -sapsid PRD -abapenq/-abaprep ASCS01/ERS20 -to erpdb02/erpdb01

Image may be NSFW.
Clik here to view.

After the relocation of ASCS service is done, the ERS service automatically relocates to oposite node.

Hope it helps you!, don't forget to like and rate if it was helpful.