Dear Experts,

I am performing the first upgrade to oracle 12c in our environment. Currently, I finished the procedure

for switching the Oracle Software owner user from oraSID to oracle, which is described in SAP note

1915317 - Migrating Software Owner to 'oracle'

There, at point 13 Configure SAP BR*Tools for user 'oracle', I wanted to check the result by launching:

OS> brconnect -u / -f check

OS> brbackup -u / -q

Unfortunately, these commands are failing:

<SID>adm 1%  brbackup -u / -q

BR0051I BRBACKUP 7.40 (15)

BR0055I Start of database backup: beqgenmx.qub 2015-04-09 15:33:23

BR0484I BRBACKUP log file: /oracle/<SID>/sapbackup/beqgenmx.qub

BR0280I BRBACKUP time stamp: 2015-04-09 15:33:23

BR0301E SQL error -1031 at location BrInitOraCreate-2, SQL statement:

'CONNECT / AT PROF_CONN IN SYSOPER MODE'

ORA-01031: insufficient privileges

BR0303E Determination of Oracle version failed

BR0056I End of database backup: beqgenmx.qub 2015-04-09 15:33:23

BR0280I BRBACKUP time stamp: 2015-04-09 15:33:23

BR0054I BRBACKUP terminated with errors

This can easily be fixed by launching the sapdba_role.sql and sapconnect_role.sql scripts, which are

contained in the BRTools 7.40.SAR file. But soon after, I found out, that things are good just in the

current session. Once I log out from the user and then switch back to it, the above error comes back

again. I have compared the environment when it works and when it doesn't, and there is no difference,

so here I am out of ideas... Please kindly help me to solve this, THANKS!

Dear All,

We are in a process of uploading some sales legacy data via background jobs..but we are facing the paging error while running the bg jobs.

We are running the background jobs in the night time with operation mode active and BG work process as 10.

when the sales uploading is process via BG all 10 work process are active but its giving an memory paging error.

where as 5 background jobs running at same time is working fine.

RAM - 250 GB (   261120 MB )

Parameter settings. -

Hi Folks,

The oracle 12c upgrade guides are available from SAP service market place:

https://websmp202.sap-ag.de/~sapidb/012002523100005235232015E/Ora_DB_Upgr_UX_121__00.pdf

https://websmp202.sap-ag.de/~sapidb/012002523100005235242015E/Ora_DB_Upgr_Win_121__00.pdf

Or you can try to access them via root:

service.sap.com/swdc
installation and upgrade
installation and upgrade guides

Database Upgrade
Oracle

Best regards,
James

Hello SAP experts,

Do you know where I can find a SAP guide to make the upgrade to the recently released Oracle 12?

Thanks & kind regards,

Luis López

Hi

We are currently upgrading BW 7.02 to NW 7.4. I got the following errro during MAIN_NEWBAS/PARCONV_UPG step:

ERROR:

Detected the following errors:

# /install/BX1/SUM/abap/log/PD990404.BX1:

3 ETP000 ALTER TABLE "/BI0/ASRSA_DS100"

3 ETP000 MODIFY ("TCTHIGH" VARCHAR2 (003999),

3 ETP000 "TCTLOW" VARCHAR2 (003999))

3 ETP000

2WETP000 15:00:09: Retcode 1: error in DDL statement for "/BI0/ASRSA_DS100 " - repeat

2EETP345 15:00:21: Retcode 1: SQL-error "1404-ORA-01404: ALTER COLUMN will make an index too large"

2EETP345 in DDL statement for "/BI0/ASRSA_DS100 "

2 ETP000 --------------- DB-ROLLBACK() ---------------

2EETP334 15:00:21: error in DDL, nametab for "/BI0/ASRSA_DS100" not activated

I checked  the table and it is empty

SQL> select count(*) from sapsr3."/BI0/ASRSA_DS100" ;

  COUNT(*)

----------

         0

I also validated the table definition and it is correct

SQL> desc sapsr3."/BI0/ASRSA_DS100"

Name                                      Null?    Type

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

TCTUSERNM                                 NOT NULL VARCHAR2(36)

TCTAUTH                                   NOT NULL VARCHAR2(36)

TCTADTO                                   NOT NULL VARCHAR2(24)

TCTIOBJNM                                 NOT NULL VARCHAR2(90)

TCTSIGN                                   NOT NULL VARCHAR2(3)

TCTOPTION                                 NOT NULL VARCHAR2(6)

TCTLOW                                    NOT NULL VARCHAR2(180)

TCTHIGH                                   NOT NULL VARCHAR2(180)

TCTOBJVERS                                NOT NULL VARCHAR2(3)

TCTSYSID                                  NOT NULL VARCHAR2(30)

RECORDMODE                                NOT NULL VARCHAR2(3)

TCTADFROM                                 NOT NULL VARCHAR2(24)

I am not sure why SUM tool trying to modify the field definition in the statement to

MODIFY ("TCTHIGH" VARCHAR2 (003999),

Did anyone see this before? Any help?

Thanks

Hi all

I need to remove entries from TP BUFFER.

Our SPAM Patch got stuck some where. I removed all the entries from PAT01, PAT02, PAT03, PAT10, TRBAT & TRJOB tables but still we are facing same problem.

I got QUEUE_NOT_EMPTY error message.

Here is the solution:

CHECK_REQUIREMENTS

In this step, various requirements for the import of the Support Package are checked.

The following messages explain why this step may be terminated:

  QUEUE_NOT_EMPTY: There are incompletely processed OCS requests in the tp buffer.

Use the following tp command to display these requests:

tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM

You can continue processing the queue as soon as these requests have been processed

completely, or deleted from the tp buffer.

I GOT MISSING PARAMETER ERROR WHILE I TRIED THIS COMMAND,

IS SOURCESTSEMS = HOST NAME?

PLZ LEMME KNOW THE RIGHT COMMAND....

Hi experts,

I’m going to describe our current scenario as detailed as possible.

The following dump is being constantly obtained in our ERP 6.0 EHP7 system (Windows 2012/Oracle 11.2.03):

Category               Installation Errors

Runtime Errors         DBSQL_SQL_ERROR

1. Except.                CX_SY_OPEN_SQL_DB

Date and Time          12.04.2015 12:47:04

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

|Short Text |

|    SQL error "SQL code: 3113" occurred while accessing table "TSPOPTIONS".                       |

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

|What happened? |

|    Database error text: "SQL message: ORA-03113: end-of-file on communication                    |

|     channel

Reviewing the developer trace in addition to the above oracle error the ora-03114 and ora-03135 are also present. Please see below>

C  *** ERROR => ORA-03135 occurred at SQL stmt (parse error offset=0)

B  ***LOG BY0=> ORA-03135: connection lost contact

C     ORA-03135: connection lost contact

C     ORA-03114: not connected to ORACLE

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-12571: TNS:packet writer failure

C     ORA-01041: internal error. hostdef extension doesn't exist

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03113: end-of-file on communication channel

C     ORA-01041: internal error. hostdef extension doesn't exist

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03135: connection lost contact

C     ORA-01041: internal error. hostdef extension doesn't exist

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03135: connection lost contact

C     ORA-01041: internal error. hostdef extension doesn't exist

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03114: not connected to ORACLE

C  DB instance  is running on  with ORACLE version 11.2.0.3.0 since APR 04, 2015, 16:57:44

C     ORA-03135: connection lost contact

Even when it’s seems to be a very common issue, almost all notes and SCN questions point me to a solution for distributed system but in my case this is a central one.

The following note describes the scenario exactly as the one we have, but again it seems to apply for distributed systems: 2064591 - work processes reconnect to Oracle database with error ORA-03135. The proposed solution has been tested but with no lack. Also the solution presented in the bellow links but with no result either:

http://www.oracle-experts.info/ora-03135-connection-lost-contact

http://www.inthebasis.com/solve-ora-03135-connection-lost-contact/

Just in case the Windows Firewall has been completely turned off and the NIPING self test is OK.

In addition, the data base library (lib_dbsl_215-10012499.sar) has been updated and we are planning to update the whole kernel and oracle instant client.

Could you please suggest what to check or what would be the recommended troubleshooting?

Thanks

Prerequisites to upgrade to ORACLE 12c

1. Your DB should have minimum release Oracle Database 10.2.0.5 or higher to upgrade to Oracle Database  12c, any other release less than Oracle Database 10.2.0.5 cannot be directly upgraded to Oracle Database 12c

2. Only Oracle Database 12c Release 1 (12.1.0.2) is supported for SAP. Release 12.1.0.1 is not supported for SAP.

3. Additional Restriction for SAP NetWeaver AS-JAVA , For SAP products based on SAP NetWeaver 7.2x, 7.3x for AS-JAVA and AS-ABAP+JAVA (Java Stack and Double Stack) only Oracle Instant Client version 11.2.0.4 is currently supported. If you upgrade your Oracle Database to 12c or if you install a new SAP system with Oracle Database 12c, you must not upgrade to or install Oracle Instant Client version 12.1.0.2.

4. In-Memory Option is currently not yet supported for SAP

5. Multitenant Option is currently not yet supported for SAP.

6. ILM/ADO Functionality is currently not yet supported for SAP

7. Free Extended Support for Instant Client version 11.2.0.4 will end in January 2016

8. Create a new OS group oinstall

9. Create a new user oracle at OS level with same groups as assigned to user ora and migrate the DB to oracle user. Reference SAP note:  1915317 - Migrating Software Owner to 'oracle'.

10. It is recommended to install the current version of SAP BR*Tools Release 7.40 before upgrading the database to 12c.

11. SAP LVM is currently not supported in an Oracle 12c based SAP NetWeaver environment. Certification pending. SAP note 2133079

12. SAP MDM is currently not supported in an Oracle 12c based SAP NetWeaver environment. Certification pending. SAP note 2133079

Upgrade checklist

1. Migrate the Oracle software from user ora to user oracle.

2. Install the Oracle database software version 12.1.0.2, including the recommended patches. For more information, see Installation of Oracle Database Software

3. If your Oracle instant client is lower than 11.2.0.4, install the version of the Oracle instant client that is currently recommended for Oracle 12c, which you can find in SAP Note 819829. When upgrading from Oracle 11g to 12c, you can perform this step before starting the actual database upgrade.

4. Update BR*Tools to the version recommended for Oracle 12c, which is BR*Tools 7.40.When upgrading from Oracle 11g to 12c, you can perform this step before starting the actual database upgrade.

5. Make sure that you have installed the SAP kernel supported with Oracle 12.1.0.2 and that you have a supported version of your operating system. In addition, 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 based systems, see also SAP Note 1777021. For more information, check the SAP requirements for your application or product in the Product Availability Matrix (PAM) at support.sap.com/pam. 6. 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. Oracle 12.1 is only released and certified for Oracle client software version 11.2.0.4 or higher. 7. Configure secure storage in file system (SSFS) for ABAP, otherwise the SAP System cannot start because it cannot connect to the database. In addition, consider the dependencies on the SAP kernel version. When upgrading from Oracle 11g to 12c, you can perform this step before starting the actual database upgrade.

Migrate the Oracle software from user ora to user oracle.

1. Stop the sap system using stopsap r3

2. Stop DB

3. Stop listener  

4.   Create Oracle Software Owner account 'oracle' Log on as 'root', create OS group 'oinstall' and the new Oracle software owner 'oracle'. Use corresponding platform-specific OS commands. Linux/Solaris/HPUX: root># groupadd oinstall root># useradd -g oinstall -G dba,oper -c "Oracle Software Owner" -m -s "/bin/sh" oracle root># passwd oracle root># su - oracle -c "id; pwd"

5.   Modify SAP administrator account 'adm' On the database server, log on as 'root' and add the 'adm' account as a member to OS group 'oinstall' (required to run SAP BR*TOOLS). In addition to the standard groups (such as sapsys, dba, oper, sapinst),adm also belongs to the OS group "oinstall" (SAP Note 1598594). Linux: [root]# groupmod -Aadm oinstall

6.   Modify Database Administrator account 'ora' If you don't need this OS account as an additional database administrator account, you can skip this step. If you continue to use this account as additional database administator account, then this step is required. Reconfigure OS account 'ora' as below:

6.1. Change user home directory from '/oracle/' to the standard user home directory '/home/ora'

6.2. Change group membership to dba (primary group), oper, oinstall

6.3. Move 'ora' profiles and scripts (.profile .login .bashrc .cshrc .sap* .dbenv* .j2eeenv* startdb stopdb) from old user home to new user home directory

6.4. Log on as 'root' and run the following commands: Linux/Solaris/AIX/HPUX: [root]# mkdir -p /home/ora[root]# chown ora:dba /home/ora[root]# usermod -d /home/ora ora[root]# usermod -g dba -G oper,oinstall ora[root]# cd /oracle/[root]# mv .profile .login .bashrc .cshrc .sap* .dbenv* .j2eeenv* /home/ora[root]# mv startdb stopdb /home/ora

6.5. When finished, log on as ora and check/verify the environment. [ora] $ env. In our Case it was already there and hence no need to perform

7. Check Oracle environment consistency. When you log on as any of the Oracle database administrator accounts  to perform an administrative task on database, the Oracle environment must be identical. Log on as 'oracle', 'adm' and 'ora' and verify that environment variables ORACLE_BASE,ORACLE_HOME and ORACLE_SID are set identical. OS account 'oracle' For this account the Oracle environment for can be set using the Oracle script 'oraenv' (see SAP Note 1554661) if the corresponding entry for exists in oratab (location of oratab: /etc or /var/opt/oracle, depending on OS). Note: ORACLE_BASE is not set when you use the 10g version of 'oraenv' script. ORACLE_BASE is set in 'oraenv' script version 11g and higher. Example for oratab entry for database::/oracle//112_64:N OS accounts 'ora' / 'adm' For these accounts the Oracle environment is set in the SAP scripts '.dbenv*'.

8. Change Ownership of Database Files and Directories In this step you change permissions and ownership of Oracle database files and directories from 'ora' to 'oracle'. Change File Permissions and Ownership with script 'orasid2oracle.sh' You find the script 'orasid2oracle.sh' attached to this SAP Note. Download the script and extract it.

8.1For help, you can run the script as './orasid2oracle.sh -help'.

8.2Option #1: Log on as 'ora[root]# export ORACLE_BASE=[root]# export DB_SID=

8.3. For help, run: [root]# ./orasid2oracle.sh -help 8.4. Perform a test run of the script: [root]# ./orasid2oracle.sh -v

8.5. Run the script with '-exec' option to perform the changes: [root]# ./orasid2oracle.sh -v -exec

8.6. Check whether you need to change the ownership of additional, non-standard directories! Note: if needed, you can revert the ownership back from 'oracle:oinstall' back to 'ora:dba' with the following command: [root]# orasid2oracle.sh -owner ora-group dba -v -exec Change Ownership Use option 2 setenv SAPDATA_HOME /oracle/SID

9. Change Ownership of Oracle Home

9.1 Detailed Steps for Approach (1) using SAP Note 1983457 Note: if sudo is configured, you can use 'sudo' to run the generated scripts from the required OS account (root or oracle). OS> sudo -u root

Hello SAP Gurus,

We have installed the below HA System in our Primary Site. 

We have same SID for SAP & DB. Due to HA, we used Virtual-Host-name/IP in our Primary Site.

Now we are in process of setting up our DR Site.

•   We planned to use the Virtual-Hostname/IP in DR.
•   We planned to use Oracle-Data-guard for DB Replication at DR Site

Our environment

OS     : Solaris 10

DB     : Oracle 11.2

SAP   : NW7.0 / ECC 6.0 Ehp3 (Abap+Java)

Host-entry of Primary Server

erpph01 10.1.1.10      #Physical Host

erpdb      10.1.1.83        # DB Instance

erpd00    10.1.1.80       # PAS

erpscs     10.1.1.81        # Java CI

erpascs   10.1.1.84        # ABAP CI

Planned Host-entry for DR Server:

erpdr01   10.2.1.10      #Physical Host

erpdb      10.2.1.83      #DB Instance

erpd00    10.2.1.80      #CI+PAS

We got below queries:

1. Can we use the same virtual host-name for SAP & DB in DR Server?
2. How to up the DR Host in the fastest way without changing manually the ip address, host name in  ABAP &JAVA parameter files, Instance Profiles ?
3. How we can synchronize from Production Site SAP Application files (Instance profiles, Java configuration files, binary files..) to Disaster Recovery Site?   

Thanks for your feedback.

Dear all,

Apologies for the lengthy message

I am preparing to create a new experimental PI 7.3  system called PIX as a copy of the already existing PI Development system PID. The database of the source system is Oracle 11.2.0.3 on Oracle RAC and ASM. I plan to be using the database specific method for the system copy.

Because of Oracle RAC and ASM, the backup in the source system is taken with brbackup calling RMAN and the restore in the target system has to happen with RMAN. I will be restoring from an full offline RMAN backup.

I am trying to put together a plan as the documentation from SAP when it comes to restoring on ASM with RMAN is scattered in many different places and not detailed enough.

The ASM disk groups in the target system differ to the ones in the source system. For example, the source system diskgroup contains the <SID> as well, so +PID_DATA while the target system diskgroup for data is called +DATA

I read that I should run brrecover in order to restore with RMAN on ASM. For that, the target database should bein mount state when brrecover runs against it.

So I understand that I have to run brrestore -d rman_util -b last -m 0,00 to restore the source controlfile in thetarget system together with the source online redo logs.

My first question is how the controlfile and online redo logs will be stored. brrestore will look to restore them in an ASM diskgroup in the target system that does not exist. They have been backed up as (example)

+PID_MLOG/pid/onlinelog/group_1.256.783443785
+PID_OLOG/pid/onlinelog/group_1.256.783443785
+PID_DATA/PID/cntrlPID.dbf
+PID_ARCH/PID/cntrlPID.dbf
+PID_RECO/PID/cntrlPID.dbf

but the target system only has disk groups +DATA, +ARCH,+RECO

The three controlfiles will need to go to one of +DATA, +ARCH,+RECO each and the PID_OLOG to +DATA and the PID_MLOG to +RECO.

Then, I will have to start the database in mount state. As there is nothing with the target system name PIX in the restored controlfile, I assume that I will have to set the environment of Unix user oracle to point to the source system PID (ORACLE_HOME,ORACLE_SID, SAPDATA_HOME) and start the database mount as if it was a PID database. Is that correct?

Then set the ORACLE_HOME, ORACLE_SID etc point to target system name PIX values and finally, following the
instructions from note 1003028

brrecover -t reset -b last -f PIX -RDG

The -RDG option will activate special parameter _remap_disk_groups which will need to be set to something like this: _remap_disk_groups=(+PID_DATA,+DATA,+PID_OLOG,+DATA,+PID_MLOG,+RECO,+PID_ARCH,+ARCH,+PID_RECO,+RECO)

Note 1003028 does not say where this parameter is set. Is it an Oracle parameter to be set in the spfile ora parameter of brrecover set in the menus? Or somewhere else?

Many thanks for your help

Andreas

Installed Oracle 12C on AIX Server.

When executing "lsnrctl start"  or "lsnrctl status"    or sqlplus / as sysdba, error occurred

“rtld: 0712-001 Symbol CreateIoCompletionPort was referenced”.

The problem is due to I/O Communication ports either  not enabled  or not installed .

To check whether  IOCP is installed run the following command

# lslpp -l bos.iocp.rte

As shown above,  IOCP module was installed and present in AIX

To check whether IOCP is enabled or not , run the following unix command

# lsdev -Cc iocp

It showed “Defined” means not enabled. The output   should show “Available” instead of “Defined”.

To change from Defined to Available is done using  unix ‘smitty’ command

Log in as root and run the following command:

# smitty iocp

Select Change / Show Characteristics of I/O Completion Ports.

Change configured state at system restart from Defined to Available.

Run the lsdev command to confirm the IOCP status is set to Available:

# lsdev | grep iocp

     iocp0      Available       I/O Completion Ports

Perform a system  restart  (means server reboot) to make the changes permanent.

After the Server reboot, check lsnrctl status or lsnrctl start command  or sqlplus / as sysdba command as shown in the screenshot below

Before installing Oracle 12C, read the installation guide properly and follow the instructions  as  mentioned in the pre-requisite check.

Dear All,

I'm scheduling oracle online/offline backup using brtools.

It's throwing error message "SQL error -1031 at location in BrSapTspGet-8, SQL Statement :

'PREPARE stmt_1 FROM' 'SELECT TABSPACE FROM "SAPSLM".TSORA UNION SELECT INDSPACE FROM "SAPSLM".TSORA ORDER BY 1'

ORA-01031: insufficient privileges

I've performed stack12 upgrade on solman 7.1. After successful completion of upgrade, I'm taking database backup as post steps. This issue is coming.

Kindly see the screenshot for more info.

Note: Archive log backup with BRtools is working fine.

Thanks & Regards

Venkatesh P

ORACLE 12C Pre Upgrade steps

1.0  Extracting Oracle Software

1. mkdir -p /oracle/stage/12102

chmod 755 /oracle/stage/12102

2. To upgrade a single instance database on the file system, you only need to extract the database software that is contained in the first 2 SAR  files OR112164.SAR and OR212164.SAR

Move these to location stage

2 Installation of Oracle Database Software

2.1 Backing Up the Central Oracle Inventory

oracle> more /etc/oraInst.loc

inventory_loc=/opt/oracle/oraInventory

inst_group=dba

2.2 Check and Update the SAP RUNINSTALLER Scripts if required

Install database

Call RUNISTALLER and follow the instructions as per the screens you are getting

Check SAP Note 1914631 to find a cross-reference to the current SAP Note with the list of required patches to be installed

oracle> unzip -z SAP12102P_1503-20012300.ZIP

Archive:

SAP12102P_1503-20012300.ZIP

SBP 12.1.0.2.2 201503 for Linux x86-64

Bundle patches

Executing Pre-Installation Instructions

Set environment variable s:

DISPLAY

OHRDBMS = /oracle/SID/121

IHRDBMS= /oracle/SID/12102

Unless otherwise stated, you can execute the following pre-installation instructionsbeforeyou shut down the
database applications or the database instances.

1. Download fileSAP12102P_1503-20012300.ZIP(this SBP) to the database host.
2. If required, update the OPatch and MOPatch utilities to OPatch version 12.1.0.1.6 and MOPatch
   version 2.1.20

   Extract OPatch and MOPatch and install them in the Oracle Home:

unzip -qd $IHRDBMS/sapbundle SAP12102P_1503-20012300.ZIP 'SBP_121022_201503/OPatch/*'

mv $IHRDBMS/OPatch $IHRDBMS/OPatch-pre-SBP_121022_201503

mv $IHRDBMS/sapbundle/SBP_121022_201503/OPatch $IHRDBMS/OPatch

unzip -qd $IHRDBMS/sapbundle SAP12102P_1503-20012300.ZIP 'SBP_121022_201503/MOPatch/*'

test -d $IHRDBMS/MOPatch && mv $IHRDBMS/MOPatch $IHRDBMS/MOPatch-pre-SBP_121022_201503

mv $IHRDBMS/sapbundle/SBP_121022_201503/MOPatch $IHRDBMS/MOPatch

mv $IHRDBMS/sapbundle/SBP_121022_201503/MOPatch $IHRDBMS/MOPatch

Installing the SAP Bundle Patch

Follow the steps below.

1. Stop all database applications, in particular all SAP applications.
2. Shut down the database instances, the listeners, and other processes running from the Oracle Home.
3. After having shut down all database processes as described in the previous step, use the fuserOS command to check
   for stale SQL*Plus sessions:

$SBPFUSER $IHRDBMS/bin/oracle

If that command reports running processes, these are stale SQL*Plus sessions, which you can safely terminate with the killcommand.

Install the SAP Bundle Patch as follows:

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

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

SQL> Startup

Listener

oracle> lsnrctl start LISTENER

2.4 Running the Pre-Upgrade Scripts

Check that the environment variables ORACLE_HOME and ORACLE_SID are set. For user oracle, you can set the environment with oraenv (sh
shell) or coraenv (csh shell). Make sure that ORACLE_HOMEis set to the value of the current Oracle home, <old_Oracle_home>.

Change to the correct directory by entering the relevant command:

cd /oracle/<DBSID>/12102/sap/ora_upgrade/pre_upgrade

Execute the following commands to perform pre-upgrade tasks, which can improve the performance of the upgrade process:

sqlplus / as sysdba

SQL>@pre_upgrade_tasks.sql

Execute the following commands to check the pre-upgrade status of your database:

sqlplus / as sysdba

SQL>@pre_upgrade_checks.sql

Check the results of pre_upgrade_checks.sql and take actions as suggested in the log.

Below were the actions suggested by run of : pre_upgrade_checks.sql

      ************************************************************

      ************************************************************

                ====>> PRE-UPGRADE RESULTS for SID <<====

ACTIONS REQUIRED:

1. Review results of the pre-upgrade checks:

/oracle/cfgtoollogs/SID/preupgrade/preupgrade.log

2. Execute in the SOURCE environment BEFORE upgrade:

/oracle/cfgtoollogs/SID/preupgrade/preupgrade_fixups.sql

3.Execute in the NEW environment AFTER upgrade:

/oracle/cfgtoollogs/SID/preupgrade/postupgrade_fixups.sql

  ************************************************************

***************************************************************************

Pre-Upgrade Checks in SID Completed.

*******************************************************************

Pre ugrade tasks

Execute in the SOURCE environment BEFORE upgrade:

/oracle/cfgtoollogs/SID/preupgrade/preupgrade_fixups.sql

Now you are done with preupgrade tasks on source Database and you can proceed to upgrade the Database to ORACLE12C

Oracle Database Upgrade

1. Backing up the Oracle Database

As per your backup strategy take the backup of DB

2. Shutting Down the SAP System

stopsap r3

3. Upgrading the Database Structure with the Database Upgrade Assistant

To upgrade the database structure, you need to start the Oracle Database Upgrade Assistant (DBUA). The DBUA is a graphical tool that leads you step-by-step through the upgrade.

Prerequisites

You have installed the database software.

Make sure that the DISPLAY environment variable is correctly set, DISPLAY Environment Variable must be set in case of unix based systems.

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

Make sure that the database and the Oracle Listener are both running.

export ORACLE_HOME_SRC=/oracle/<DBSID>/112_64

export ORACLE_HOME_TGT=/oracle/<DBSID>/12102

export DB_SID=<DBSID>

Change to the correct directory:

cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade

Run this script in query mode initially to verify that the environment for the upgrade is correct:

./dbua.sap.sh -q

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

Respond
appropriately to the DBUA dialogs (unless DBUA is started in silent mode):

Post-Upgrade Steps

1. Updating the SQL*Net Configuration Files

Copy back the content from old sqlnet file as per the parameters set in original file

2. Checking the Symbolic Link for Runtime Oracle Home

Procedure

Change to the required directory:

cd /oracle/<DBSID>

Check that the following symbolic link exists:

ls -l /oracle/<DBSID>/121

If this link does not exist, create a symbolic link to the new Oracle home:

ln -s /oracle/<DBSID>/12102/oracle/<DBSID>/121

3. Adapting the Environment of the <sapsid>adm user

Procedure

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

Set the ORACLE_HOME environment variable to new Oracle home, for example:

/oracle/<DBSID>/121

Set ORACLE_BASE to the new Oracle base /oracle/<DBSID>.

Adapt the PATH variable so that it no longer contains references to the old Oracle home.

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)

Start Listener

Oracle> lsnrctl start

Start DB

SQL> startup

4. Performing Post-Upgrade Checks

Procedure

Log on as the current Oracle database administrator <ora_dba>.

Open a command prompt and change to the directory <new_Oracle_home>/sap/ora_upgrade/post_ugprade.

From the same directory, start sqlplus.exe and enter the following commands to run the post-upgrade scripts, referring to SAP Note 1915315:

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

This provides an overview of the status of the upgraded database.

Gather Oracle optimizer statistics by executing the following commands as the administration user <sapsid>adm:

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

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

Note you can perform this step later if required.

Check the Oracle database parameters against SAP Note 1888485 and adjust them if necessary.

Check  SAP Note 1171650 to see whether an automated script for Oracle 12c is already available. This helps you check whether your SAP system complies with the database parameter recommendations at any given point in time.

Update the Oracle database statistics with BRCONNECT as follows:

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

5. Performing Post-Upgrade SBP tasks

Execute in the NEW environment AFTER upgrade:

/oracle/cfgtoollogs/SID/preupgrade/postupgrade_fixups.sql

EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

Run SBP specific post upgrade scripts as well

Post upgrade activity for bundle patch

Updating the Oracle Instant Client

After the upgrade to Oracle 12.1.0.2, it is strongly recommended to install an Oracle client supported for Oracle 12c. If it is not possible to install Oracle client 12.1.0.2 (for example, due to SAP limitations or hardware restrictions), you need at least Oracle client 11.2.0.4.

For more information on the recommended versions, see the Product Availability Matrix (PAM) at support.sap.com/pam and SAP Note 819829. A mixture of Oracle client  12.1.0.2 and Oracle client 11.2.0.4 on different application servers is supported.

Procedure

As user <sapsid>adm, update the Oracle instant client for UNIX as follows, either for the Oracle 12c client or the Oracle 11g client:

Installation of Oracle 12c Client

Create the new client directory:

mkdir -p /oracle/client/12x

Change to the new client directory:

cd /oracle/client/12x

Mount the Oracle client DVD 12.1.0.2 and unpack the client software:

SAPCAR -xvf <Oracle client DVD>/OCL<your OS>/OCL12164.SAR

Check and create the symbolic links:

cd /oracle/client/12x

ln -s instantclient_12102 instantclient

Create the symbolic link for BR*Tools 7.40:

Enter this command to change directory:

cd /oracle/client

If the link or directory 11x_64 already exists, rename it, as in this example:

mv 11x_64 11x_64_save

Create the symbolic link:

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

Set Parameters as per SAP note 1888485

SAP has certified Oracle12c for Business Suite and present DB's now can be upgraded to Oracle12c.

To upgrade to Oracle12c in your environment you need to go through below phases for smooth upgrade . Documents have been published for each phase so that it's easy to identify all the phases and plan to upgrade to Oracle12c can be smooth

1. Prerequisites and Upgrade checklist

Please refer to document on SCN:

ORACLE 12C upgrade Prerequisites and Checklist

2. Migrate the Oracle software from user ora<dbsid> to user oracle

This step is optional but make sure that Oracle12c installation is done with user oracle

Please refer to document on SCN:

ORACLE 12c Upgrade Migrate the Oracle software to oracle from orasid

3.   Preupgrade steps and preparation on Source System and Database

Please refer to document on SCN:

ORACLE12C Upgrade: Preupgrade steps

4.  Database Upgrade steps

Please refer to document on SCN:

ORACLE12C Upgrade: Database Upgrade

5.  Post Upgrade Tasks

Please refer to document on SCN:

ORACLE12C Upgrade: Post Upgrade Tasks

6. Updating the Oracle Instant Client

Please refer to document on SCN:

ORACLE12C Upgrade: Updating the Oracle Instant Client

Hi,

We are planning to upgrade Oracle from 11.2.0.3 to 11.2.0.4. We would like to test our SAP business processes for this upgrade. I would like to know what does this patch does to the database and what we need to test. We also like to know if there are any other customers who had faced any issues in SAP particularly due to this patch 11.2.0.4. Can you please provide these inputs?

Thanks

Thilip Kumar

Performed oracle database upgrade to 11.2.0.4. I was asked to analyze the database dictionary statistics that was taking long during post processing. Customer was not happy that dictionary statistics was taking long time after database upgrade.

When executing dictionary statistics using the command below

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

took 15 hours to complete  statistics.

The unix server (AIX) performance was really good.  It is Power7 Processor,  has large RAM capacity, has many CPU / cores and IP storage throughput was extremely fast.

The oracle RDBMS version was 11.2.0.4.0.

Decided to check database parameters as shown in the figure below     

As shown above  the database parameters are  found ok.

Applied latest database bundle patch as shown in the figure below.

Executed Dictionary Statistics after oracle upgrade to  SAP Bundle Patch - SBP 11.2.0.4.3 201408 containing CPUJul2014  but showed no improvement i.e. took 15 hours to complete dictionary Statistics.  I was informed that customer is going to perform BW upgrade from NW 7.00 EHP 1 to NW 7.4. So I decided to wait till BW 7.4 (ABAP) upgrade completed.

After BW upgrade to 7.4 completed . applied  latest kernel patch 742/17 as well as latest brtools patch level 740/11 , 

Then executed Dictionary Database statistics but still showing no improvement i.e. it was completed in 15 hours.

So I have realized that there is something wrong with  statistics tables  Nealy almost two  months but was showing no improvement.

Then checked in tx code db02 or st04 as shown in the figure below

Double click on the highlighted yellow colourn line  as shown above and click on Explain Plan

based on the above  very high Elapsed time per sec observed in table WRI$_OPTSTAT_HISTGRM_HISTORY

That means database dictionary spent so many hours in accessing HISTGRM$  and WRI$_OPTSTAT_HISTGRM_HISTORY tables. This could be due to poor indexes or large fragmentation on index.

The following select sql  statement shows SM/OPTSTAT occupies the most space within SYSAUX tablespace.

As shown above SM/OPTSTAT occupies 65GB. That was too much.  Storage Cost  is  very high. Is it necessary to have very large table and let the table to grow unnecessarily.

As shown above, out of 65GB , index occupies 45GB space as compared to 16.91 GB in table. This was due to large index fragmentation.

After correcting the table and index, executed dictionary statistics, now it was completed in less than 2 hours

.

Author:          A Prasad Rao

Compnay:     Tata Consultancy Services Ltd.

Eleven years experience as an Unix System and Oracle database Administration and sixteen years experience as SAP Basis Consultant.

Executed more than 10 SAP Technical Upgrade, combine upgrade and uniocde conversion (Single downtime) and SAP OS/DB Migration in different clients in geographically locations across the world.

Experience in SAP troubleshooting, SAP Oracle performance tuning.

Certified SAP OS/DB Migration, certified OCP (Oracle Certified Professional) 9i Database and certified SAP WEB AS 640.