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

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

     srvctl status database -d PRD

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

     srvctl stop instance -d PRD -i PRD1

The same works for stopping the second RAC instance.

     srvctl stop instance -d PRD -i PRD2

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

     srvctl start instance -d PRD -i PRD1

     srvctl start instance -d PRD -i PRD2

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

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

     srvctl start database -d PRD

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

     srvctl status asm

With this command you can check the cluster services:

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

     crsctl check cluster -all

To check the status of the voting disks

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

     ./crsctl query css votedisk

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

     srvctl status scan_listener

To check the status of the nodeapps you use:

     srvctl status nodeapps -n erpdb01

     srvctl status nodeapps -n erpdb02

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

     crs_stat -t

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

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

     sapctl status abapvip/abapenq/abaprep -sapsid PRD

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

     sapctl config

To stop all SAP HA subsystems use this command:

     sapctl stop all -sapsid PRD

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.

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)

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

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.

Monitor & Extend Tablespaces In SAP

Purpose:

This document describes how to monitor and extend tablespaces in SAP systems with Oracle as database. Oracle DB manages database data in logical units called table spaces. Hardware platform can be any (Unix, Linux, Windows)

Procedure:

1. 1.     Monitor tablespaces
2. a. Open SAPGUI & use t-code DB02. To get the latest data press the refresh button on the top left corner, this will schedule a job REFRESH_SPACE_STATISTICS_SID and we can monitor this job in t-code SM37. Once this job is finished the data will be updated in DB02. Go to Oracle Database administration à Space à Tablespaces à Overview. Generally we need to add space if any tablespace reaches 95% (Total used %).
3. b. Monitor tablespaces via BRTOOLS. Check below what to execute :

hostname:orasid > brtools

BR0651I BRTOOLS 7.20 (35)

BR0280I BRTOOLS time stamp: 2015-08-31 21.43.51

BR0656I Choice menu 1 - please make a selection

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

BR*Tools main menu

1 = Instance management

2 - Space management

3 - Segment management

4 - Backup and database copy

5 - Restore and recovery

6 - Check and verification

7 - Database statistics

8 - Additional functions

9 - Exit program

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

2

BR0280I BRTOOLS time stamp: 2015-08-31 21.43.53

BR0663I Your choice: '2'

BR0280I BRTOOLS time stamp: 2015-08-31 21.43.53

BR0656I Choice menu 5 - please make a selection

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

Database space management

1 = Extend tablespace

2 - Create tablespace

3 - Drop tablespace

4 - Alter tablespace

5 - Alter data file

6 - Move data file

7 - Additional space functions

8 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.43.57

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRTOOLS time stamp: 2015-08-31 21.43.57

BR0657I Input menu 81 - please enter/check input values

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

BRSPACE options for tablespace extension

1 - BRSPACE profile (profile) ...... [initSID.sap]

2 - Database user/password (user) .. [/]

3 ~ Tablespace name (tablespace) ... []

4 - Confirmation mode (confirm) .... [yes]

5 - Scrolling line count (scroll) .. [20]

6 - Message language (language) .... [E]

7 - BRSPACE command line (command) . [-p initSID.sap -s 20 -l E -f tsextend]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.44.10

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0291I BRSPACE will be started with options '-p initSID.sap -s 20 -l E -f tsextend'

BR0280I BRTOOLS time stamp: 2015-08-31 21.44.10

BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.44.11

BR0257I Your reply: 'c'

BR0259I Program execution will be continued...

###############################################################################

BR1001I BRSPACE 7.20 (35)

BR1002I Start of BRSPACE processing: abcdefg.tse 2015-08-31 21.44.12

BR0484I BRSPACE log file: /oracle/SID/sapreorg/abcdefg.tse

BR0280I BRSPACE time stamp: 2015-08-31 21.44.12

BR1009I Name of database instance: S9C

BR1010I BRSPACE action ID: abcdefg

BR1011I BRSPACE function ID: tse

BR1012I BRSPACE function: tsextend

BR0280I BRSPACE time stamp: 2015-08-31 21.44.12

BR0656I Choice menu 301 - please make a selection

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

Tablespace extension main menu

1 = Extend tablespace

2 - Show tablespaces

3 - Show data files

4 - Show disk volumes

5 * Exit program

6 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRSPACE time stamp: 2015-08-31 21.44.13

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRSPACE time stamp: 2015-08-31 21.44.14

BR0658I List menu 302 - please select one entry

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

List of tablespaces for extension

1. Pos.  Tablespace    Files/AuExt.   Total[KB] Used[%]    Free[KB]  MaxSize[KB]

  1 - PSAPSR3          41/0       614431744     89.25 66036288    614431744

  2 - PSAPSR3731        8/0        61644800     53.05 28943168     61644800

  3 - PSAPSR3USR        1/0         1048576      6.30 982528      1048576

  4 - PSAPTEMP          8/0        33062912      0.00 33062912     33062912

  5 - PSAPUNDO          2/0 40960000      0.01    40957952 40960000

  6 - SYSAUX            1/0         4055040     44.04 2269184      4055040

  7 - SYSTEM            2/0         1310720     62.40 492864      1310720

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your selection

1. 2.     Extend (OR) Increase Table space

We can extend table space by creating new data file (or) resize existing datafile using SAP provided tool BRTOOLS.

Note: Before adding space, need to check enough space in file systems

hostname:orasid> brtools

BR0651I BRTOOLS 7.20 (35)

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.26

BR0656I Choice menu 1 - please make a selection

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

BR*Tools main menu

1 = Instance management

2 - Space management

3 - Segment management

4 - Backup and database copy

5 - Restore and recovery

6 - Check and verification

7 - Database statistics

8 - Additional functions

9 - Exit program

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

2

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.27

BR0663I Your choice: '2'

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.27

BR0656I Choice menu 5 - please make a selection

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

Database space management

1 = Extend tablespace

2 - Create tablespace

3 - Drop tablespace

4 - Alter tablespace

5 - Alter data file

6 - Move data file

7 - Additional space functions

8 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.30

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.30

BR0657I Input menu 81 - please enter/check input values

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

BRSPACE options for tablespace extension

1 - BRSPACE profile (profile) ...... [initSID.sap]

2 - Database user/password (user) .. [/]

3 ~ Tablespace name (tablespace) ... []

4 - Confirmation mode (confirm) .... [yes]

5 - Scrolling line count (scroll) .. [20]

6 - Message language (language) .... [E]

7 - BRSPACE command line (command) . [-p initSID.sap -s 20 -l E -f tsextend]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.31

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0291I BRSPACE will be started with options '-p initSID.sap -s 20 -l E -f tsextend'

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.31

BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:

c

BR0280I BRTOOLS time stamp: 2015-08-31 21.51.31

BR0257I Your reply: 'c'

BR0259I Program execution will be continued...

###############################################################################

BR1001I BRSPACE 7.20 (35)

BR1002I Start of BRSPACE processing: abcdefg.tse 2015-08-31 21.51.32

BR0484I BRSPACE log file: /oracle/SID/sapreorg/abcdefg.tse

BR0280I BRSPACE time stamp: 2015-08-31 21.51.32

BR1009I Name of database instance: SID

BR1010I BRSPACE action ID: abcdefg

BR1011I BRSPACE function ID: tse

BR1012I BRSPACE function: tsextend

BR0280I BRSPACE time stamp: 2015-08-31 21.51.32

BR0656I Choice menu 301 - please make a selection

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

Tablespace extension main menu

1 = Extend tablespace

2 - Show tablespaces

3 - Show data files

4 - Show disk volumes

5 * Exit program

6 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

BR0280I BRSPACE time stamp: 2015-08-31 21.51.33

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRSPACE time stamp: 2015-08-31 21.51.34

BR0658I List menu 302 - please select one entry

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

List of tablespaces for extension

1. Pos.  Tablespace    Files/AuExt.   Total[KB] Used[%]    Free[KB]  MaxSize[KB]

  1 - PSAPSR3          41/0       614431744     89.25 66036288    614431744

  2 - PSAPSR3731        8/0        61644800     53.05 28943168     61644800

  3 - PSAPSR3USR        1/0         1048576      6.30 982528      1048576

  4 - PSAPTEMP          8/0        33062912      0.00 33062912     33062912

  5 - PSAPUNDO          2/0 40960000      0.01    40957952 40960000

  6 - SYSAUX            1/0         4055040     44.04 2269184      4055040

  7 - SYSTEM            2/0         1310720     62.40 492864      1310720

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your selection:

1

BR0280I BRSPACE time stamp: 2015-08-31 21.51.39

BR0663I Your selection: '1'

BR0280I BRSPACE time stamp: 2015-08-31 21.51.39

BR0657I Input menu 303 - please enter/check input values

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

Options for extension of tablespace PSAPSR3 (1. file)

1 * Last added file name (lastfile) ....... [/oracle/SID/sapdata1/sr3_41/sr3.data2]

2 * Last added file size in MB (lastsize) . [20000]

3 - New file to be added (file) ........... [/oracle/SID/sapdata1/sr3_42/sr3.data3]

4 ~ Raw disk / link target (rawlink) ...... []

5 - Size of the new file in MB (size) ..... [10000]

6 - File autoextend mode (autoextend) ..... [no]

7 # Maximum file size in MB (maxsize) ..... []

8 # File increment size in MB (incrsize) .. []

9 - SQL command (command) ................. [alter tablespace PSAPSR3 add datafile '/oracle/SID/sapdata1/sr3_3/sr3.data3' size 10000M autoextend off]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

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

BR0662I Enter your choice:

c

Oracle Database In-Memory Certified by SAP New!

Oracle Database 12c Certified by SAP New!

SAP on Oracle Development Update New!

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

Oracle Linux 7 Certified by SAP

Red Hat Enterprise Linux 7 Supported for SAP on Oracle

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

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>';

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.

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

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 :  Will be released soon....

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

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

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

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.

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

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

Click --> Next

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

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

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

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

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

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

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.

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.

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:

my redo log is 100MB

seems we need to select all the redo logs

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

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.

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

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