Caused by: java.sql.SQLException: ORA-28040: No matching authentication protocol

jvmbootstrap.ou0  


As Java process getting failed  after oracle upgrade to 12c..


INFO: Loading tool launcher...
   INFO: [OS: Windows Vista] [VM vendor: SAP AG] [VM version: 1.5.0_14] [VM type: SAP Java 64-Bit Server VM]
   INFO: Main class to start: "com.sap.engine.bootstrap.Bootstrap"
   INFO: Loading 23 JAR files: [D:\usr\sap\GPQ\SYS\global\security\lib\tools\iaik_smime.jar, D:\usr\sap\GPQ\SYS\global\security\lib\tools\iaik_jsse.jar, D:\usr\sap\GPQ\SYS\global\security\lib\tools\iaik_jce.jar, D:\usr\sap\GPQ\SYS\global\security\lib\tools\iaik_ssl.jar, D:\usr\sap\GPQ\SYS\global\security\lib\tools\w3c_http.jar, .\bootstrap\iaik_jce.jar, .\bootstrap\jdbc.jar, .\bootstrap\jperflib.jar, .\bootstrap\sap.com~tc~bl~config~impl.jar, .\bootstrap\sap.com~tc~bl~deploy~offline~impl.jar, .\bootstrap\sap.com~tc~bl~iqlib~impl.jar, .\bootstrap\sap.com~tc~bl~jdsr~jdsr.jar, .\bootstrap\sap.com~tc~bl~offline_launcher~impl.jar, .\bootstrap\sap.com~tc~bl~opensql~implStandalone.jar, .\bootstrap\sap.com~tc~exception~impl.jar, .\bootstrap\sap.com~tc~je~bootstrap~impl.jar, .\bootstrap\sap.com~tc~je~cfs~container~standalone_impl.jar, .\bootstrap\sap.com~tc~je~extramile.jar, .\bootstrap\sap.com~tc~je~flightrecorder.jar, .\bootstrap\sap.com~tc~je~offlineconfiguration~impl.jar, .\bootstrap\sap.com~tc~logging~java~impl.jar, .\bootstrap\sap.com~tc~sapxmltoolkit~sapxmltoolkit.jar, .\bootstrap\sap.com~tc~sec~secstorefs~java~core.jar]
   INFO: Start
 * Configuring bootstrap...
      Found bootstrap properties file [D:\usr\sap\GPQ\DVEBMGS00\j2ee\cluster\bootstrap\bootstrap.properties]
 * Done for 140 ms
 * Memory available to the bootstrap JVM: 2 GiB / 2863333376 bytes
-----[Bootstrap Module started]--------[Wed Jun 26 16:59:42 GST 2019]-------
+------------[Bootstrap synchronization activities information]-----------+
| Runtime Binaries: [X]        Native files: [X] Instance Properties: [X] |
|  Nodes Structure: [X] Cluster File System: [X]    Online bootstrap: [ ] |
+-------------------------------------------------------------------------+
None of the startup parameters passed: [-DSAPSTART=1, -DSAPSYSTEM=00, -DSAPSYSTEMNAME=GPQ, -DSAPMYNAME=GEEPASPIQUA_GPQ_00, -DSAPPROFILE=D:\usr\sap\GPQ\SYS\profile\GPQ_DVEBMGS00_GEEPASPIQUA, -DFRFC_FALLBACK=ON, -DFRFC_FALLBACK_HOST=localhost] is known to the bootstrap. Activating the default mode - synchronize all (-all).
 * Properties used for initialization: {element.resynch=detect, Logging properties = {log[defaultTrace]=FileLog, .logs=log[defaultTrace],log[consoleLog], log[defaultTrace].pattern=..\..\work\log_bootstrap.log, /.severity=Info, log[consoleLog].formatter=formatter[ConsoleFormatter], formatter[ConsoleFormatter]=TraceFormatter, log[consoleLog]=com.sap.engine.bootstrap.logging.BootstrapConsoleLog, log[defaultTrace].cnt=3, formatter[BootstrapFormatter]=TraceFormatter, log[defaultTrace].formatter=formatter[BootstrapFormatter], formatter[ConsoleFormatter].pattern=%m, log[defaultTrace].limit=5242880, .severity=Info, formatter[BootstrapFormatter].pattern=[%24d] %m}, debug=no, Watchdog properties = {watchdog.timeout=90000, watchdog.check_interval=2000}}
 * Bootstrap initialized for 203 ms
 * Watchdog [90000 ms] checking every [2000 ms] started.
 * Initializing DB connection...
SecStoreFS object initialized.
setDefaultFilenames () called, filename = "D:\usr\sap\GPQ\SYS\global/security/data/SecStore.properties".
File version = "7.00.000.001", software version = "7.00.000.001".
File version = "7.00.000.001", software version = "7.00.000.001".
setDefaultKeyFilename () called, filename = "D:\usr\sap\GPQ\SYS\global/security/data/SecStore.key".
Check record okay.
Existing store opened.
File version = "7.00.000.001", software version = "7.00.000.001".
Entering setDefaultsFromProperties()
com.sap.sql.trace.j2ee.cnt is 10
com.sap.sql.trace.j2ee.limit is 10000000
Exiting setDefaultsFromProperties()
Component: [internal/unkown] of type [unkown]
Message: [Exception occurred:]
com.sap.engine.bootstrap.SynchronizationException: Database connection initialization failed. Check if the database is running and the database properties.
 at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:114)
 at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:74)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:229)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:156)
----------==[ Caused by: ]==----------
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:432)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:178)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:48)
 at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:127)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:262)
 at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:39)
 at com.sap.engine.bootstrap.HelperImpl.getConfigurationHandlerFactory(HelperImpl.java:38)
 at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:111)
 at com.sap.engine.bootstrap.Bootstrap.initializeSynchronizer(Bootstrap.java:74)
 at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:229)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:156)
Caused by: java.sql.SQLException: ORA-28040: No matching authentication protocol
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:113)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
 at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:295)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:359)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:463)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:802)
 at com.sap.sql.connect.factory.DriverPooledConnectionFactory.createVendorConnection(DriverPooledConnectionFactory.java:50)
 at com.sap.sql.connect.factory.DriverPooledConnectionFactory.getPooledConnection(DriverPooledConnectionFactory.java:37)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:674)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.newPooledConnection(DBDataSourceImpl.java:624)
 at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:164)
 at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:208)
 at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:376)
 ... 14 more

[Bootstrap]> Problem occurred while performing synchronization. For more details see the logs above.



Solution:


Add the following entries to the SQLNETora file in


<ORA_HOME> NETWORK /ADMIN  and
usr/sap/sys/profile/oracle


SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8

Thanks
Yoonus

1EETQ399Xcouldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process

1 ETQ201 Entering upgrade-phase "MAIN_SHDRUN/START_SHDI_FIRST" ("20190413235215")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSR3
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/START_SHDI_FIRST'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'START_SERVICE'
2 ETQ399 Arg[1] = 'DEVTRACE.LOG'
2 ETQ399 Starting shadow instance
4 ETQ399 Set database connect to shadow.
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ399 Requirement for tp maps to 'exe'
4 ETQ383 translates to path "D:\SPUPGRADE\SUM\abap\exe"
4 ETQ399 Set tool parameters for shadow connect with TPPARAM 'SHADOW.TPP'.
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'
1 ETQ359 RFC Login to: System="GED", AsHost="ECCDEV-HOST" Nr="01", Client="000", GwHost="ECCDEV-HOST", GwService="sapgw01"
2EETQ231 RFC Login failed
2 ETQ353 Starting system
1 ETQ399 SYSTEM MANAGER: Instance list contains type: CI_YES.
1 ETQ399 SYSTEM MANAGER: instance found.
1 ETQ399 SYSTEM MANAGER: STARTSAP on Windows.
1 ETQ399 SYSTEM MANAGER: STARTSAP with SAPCONTROL.
1 ETQ399 SYSTEM MANAGER: Prestart on Windows.
1 ETQ399 SYSTEM MANAGER: StartService on Windows (this is actually a restart).
1 ETQ399 SYSTEM MANAGER: Getting state of service: SAPGED_01.
1 ETQ399 SYSTEM MANAGER: Restarting the service.
1 ETQ399 Make sure the service could reread profiles.
1 ETQ399 SYSTEM MANAGER: Calling getInstanceByNumberHost. Instance Number: 01, Instance Host: ECCDEV-HOST.
1 ETQ399 SYSTEM MANAGER: Instance list contains number: 01, host: ECCDEV-HOST
1 ETQ399 SYSTEM MANAGER: instance found.
1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTROL action PARAMETER VALUE for instance 01 and host ECCDEV-HOST.
1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 01 on host ECCDEV-HOST.
2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 1 for used ports on host 'ECCDEV-HOST'.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3201 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3301 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3601 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3901 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 8101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 30101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 50119 appears to be unused.
1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc.
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'
1 ETQ359 RFC Login to: System="GED", AsHost="ECCDEV-HOST" Nr="01", Client="000", GwHost="ECCDEV-HOST", GwService="sapgw01"
2EETQ231 RFC Login failed
1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: ECCDEV-HOST and instance: 01
3 ETQ120 20190413235225: PID 1248 execute '~\exe\sapcontrol.exe -format script -prot PIPE -host ECCDEV-HOST -nr 01 -function GetProcessList', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3WETQ123 20190413235225: PID 1248 exited with status 4 (time    0.00 real)
1 ETQ399 SAPCONTROL MANAGER: get parameter value with host: ECCDEV-HOST, instance: 01.
3 ETQ120 20190413235225: PID 8156 execute '~\exe\sapcontrol.exe -prot PIPE -host ECCDEV-HOST -nr 01 -function ParameterValue SAPSYSTEMNAME', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20190413235225: PID 8156 exited with status 0 (time    0.00 real)
1 ETQ399 SYSTEM HEALTH MANAGER: running postCheck for instance 01 on host ECCDEV-HOST
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'
1 ETQ359 RFC Login to: System="GED", AsHost="ECCDEV-HOST" Nr="01", Client="000", GwHost="ECCDEV-HOST", GwService="sapgw01"
2EETQ231 RFC Login failed
2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 1 for used ports on host 'ECCDEV-HOST'.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3201 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3301 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3601 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3901 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 8101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 30101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 50119 appears to be unused.
1 ETQ399 SAPCONTROL MANAGER: restartService with kernelstate: 0
3 ETQ120 20190413235245: PID 5304 execute '~\exe\sapcontrol.exe -prot PIPE -host ECCDEV-HOST -nr 01 -function RestartService', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20190413235246: PID 5304 exited with status 0 (time    0.00 real)
1 ETQ399 SYSTEM MANAGER: Start all instances.
1 ETQ399 SYSTEM MANAGER: Calling getInstances.
1 ETQ399 SYSTEM MANAGER: found instance for action START : Instance Number: 01
1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTROL action START for instance 01 and host ECCDEV-HOST.
1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 01 on host ECCDEV-HOST.
2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 1 for used ports on host 'ECCDEV-HOST'.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3201 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3301 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3601 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 3901 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 8101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 30101 appears to be unused.
3 ETQ399 SYSTEM HEALTH MANAGER: Port 50119 appears to be unused.
1 ETQ399 SYSTEM HEALTH MANAGER: call test rfc.
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'
1 ETQ359 RFC Login to: System="GED", AsHost="ECCDEV-HOST" Nr="01", Client="000", GwHost="ECCDEV-HOST", GwService="sapgw01"
2EETQ231 RFC Login failed
1 ETQ399 SYSTEM HEALTH MANAGER: check for instance processlist.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: ECCDEV-HOST and instance: 01
3 ETQ120 20190413235254: PID 6868 execute '~\exe\sapcontrol.exe -format script -prot PIPE -host ECCDEV-HOST -nr 01 -function GetProcessList', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3WETQ123 20190413235254: PID 6868 exited with status 4 (time    0.00 real)
1 ETQ399 SYSTEM HEALTH MANAGER: System is down, go on with start action
1 ETQ399 SAPCONTROL MANAGER: StartSystem with host: ECCDEV-HOST and instance: 01
3 ETQ120 20190413235254: PID 7012 execute '~\exe\sapcontrol.exe -prot PIPE -host ECCDEV-HOST -nr 01 -function StartWait 300 10', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3WETQ123 20190413235334: PID 7012 exited with status 2 (time    0.00 real)
1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 01 ('SAPCONTROL MANAGER: call (sapcontrol.exe) failed with return code '-1'
').
1 ETQ399 SYSTEM MANAGER: CheckSystemStatus.
1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: ECCDEV-HOST and instance: 01
3 ETQ120 20190413235334: PID 5460 execute '~\exe\sapcontrol.exe -format script -prot PIPE -host ECCDEV-HOST -nr 01 -function GetProcessList', output written to 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO'.
3 ETQ123 20190413235334: PID 5460 exited with status 0 (time    0.00 real)
1EETQ399 SYSTEM MANAGER: START of mandatory instance 01 on server ECCDEV-HOST has failed
2EETQ399 Starting shadow instance failed
1EETQ399 Last error code set is: Shadow instance
1EETQ399Xcouldn't be started, check 'STARTSFI.LOG' and 'DEVTRACE.LOG': Process D:\SPUPGRADE\SUM\abap\exe/sapcontrol.exe exited with 2, see 'D:\SPUPGRADE\SUM\abap\log\SAPup.ECO' for details
1EETQ204 Upgrade phase "START_SHDI_FIRST" aborted with severe errors ("20190413235334")


Solution:

Increase the page memory size and restart the server , then start the upgrade again








 

SAP on Oracle Database Upgrade 10g to 11g..

 

This blog is step by step guide to upgrade Oracle  10g to Oracle 11g. We cannot do patch upgrade kind of things since 11g is not a patch set of Oracle. We have to install 11g home as a separate ORACLE_HOME in parallel to 10g Oracle Home and follow the steps to upgrade. For the SAP we have to download Oracle 11g from SAP service marketplace. Download the latest version from SMP.

Pre-requisites :

• Existing data base should be highest patch level  (oracle 10g  10.2.0.5.0) (OPatch not mandatory)
• Check the Memory , swap and Disk Space.
• SYSAUX  and  SYSTEM table-space should have minimum 200 MB free space.
• Check the oracle home directory’s  OS  level permission.
• Stop the SAP Instances and services(don’t stop oracle services)
• Need 5- to 7 GB free space on new oracle directory (where software going to install)

 

Installing the Oracle 11g Server Software

 

As of now Oracle 11.2.0.3 is Oracle database patch sets are full installations of the Oracle database software. For more information about identifying and installing the correct Oracle database software version, see SAP note 1431799.

Make sure that you have enough space for the Oracle inventory and that you have full access to the directories (inventory, installation location, temp directory). Otherwise, the Oracle Universal Installer cannot perform installation prerequisite checks.

Login to the system as <DBSID>ADM.

Start the Oracle Universal Installer (OUI) by double-clicking the file sapserver.cmd.

If a command prompt window appears, specify the drive letter of the local disk where you want to install the Oracle software, and the <DBSID>. The command prompt window only appears if you perform a new installation (under a different user), or if the ORACLE_HOME and <DBSID> are not set.

In the Oracle Universal Installer, enter the information as shown in the following table:

Window	Task
Download Software Updates	Select Skip software updates, and then Next.
Select Skip software updates, and then Next.Select Installation Option	Confirm the default selection Install database software only and then choose Next.
Grid Installation Options	Confirm the default selection Single instance database installation and then choose Next.
Select Product Languages	Confirm the default option English and then choose Next.
Select Database Edition	Confirm the default option Enterprise Edition and then choose Next.
Specify Installation Location	This window displays the value for ORACLE_BASE, which must be set in the environment to <drive_containing_oracle_home>:\oracle. It also displays the value for ORACLE_HOME, which is\oracle\<DBSID>\1120<x> (where 1120<x> is the Oracle version number, for example, 11202 for Oracle 11.2.0.2, 11203 for Oracle 11.2.0.3, and so on). Choose Next.
Perform Prerequisite Checks	This window checks if all the required system prerequisites for the installation of the database software have been met. If some of the checks are displayed as Failed, you can fix these problems and run the check again by choosing Check Again. RECOMMENDATION We strongly recommend you to make sure that there are no failed checks before starting the software installation.
Summary	Review the information displayed in this window and choose Finish or Install.
Install Product	This window shows the progress of the installation. You can monitor the installation progress details in an additional window.
Finish	After the installation has finished successfully, choose Finish and close the Oracle Universal Installer.

Screen Shot of Installation:::

Installing Required Patches ( not necessary )

After the database software installation, you need to install all required Oracle database patches, which on Windows include one patch collections and one or more additional (generic) patches.

For Oracle 11.2.0.3, check SAP Note 1631931 for the patches to be installed.

You can download the patches from:http://service.sap.com/oracle-downloadOracle 11.2.0.<x>

Prerequisites

Use an up-to-date version of OPatch to install the patches. Check SAP Note 839182 for instructions on how to use OPatch.

Copying and Adapting the SQL*Net Files

• After the database software installation, you must copy and modify the old SQL*Net files, that is, listener.ora, sqlnet.ora, and tnsnames.ora.(from old 10g oracle home)

• Log on as user <dbsid>adm.

• copy <old_Oracle_home>/database/init<SID>.sap to <new_Oracle_home>/database/init<SID>.sap

• copy <old_Oracle_home>/database/init<SID>.utl to <new_Oracle_home>/database/init<SID>.utl

• Copy the SQL*Net parameter files from the directory <old_ORACLE_HOME>\network\admin to the directory <new_ORACLE_HOME>\network\admin.

• Edit the TNSNAME.ora & listener.ora add the new oracle home path <new_ORACLE_HOME>\network\admin directory.

       Identify the parameter ORACLE_HOME that belongs to the database you want to upgrade (SID_NAME in section SID_LIST) 

• If not available, add the following entry to the filelistener.ora:ADR_BASE_<listener_name> = <full_path_to_saptrace_directory>

Note that this is the same value as set in the database profile parameter diagnostic_dest.

Since your database is still running in the old environment, do not start the listener with the new listener.ora file at this point.

Backing Up the Oracle Database

You must have a complete and usable database backup otherwise you might lose data

Procedure

1. Create a complete database and operating system backup, and back up any archive logs from Oracle 10g.

1. Check that the backup is usable. If for any reason you have problems during the upgrade you must be able to restore the database from this backup.

Changing the Environment for User <dbsid>adm

 

• ORACLE_HOME( map to new oracle home)
• TNS_ADMIN (if it exists)

EXAMPLE

Rrename ORACLE_HOME into ORACLE_HOME_before_upgrade, and TNS_ADMIN into TNS_ADMIN_before_upgrade.

Run the Pre-upgrade script…. one by one as below…

 

Note 1431793 – Oracle 11.2.0: Upgrade Scripts

=============================================

A detailled description and instructions how to use the scripts can be found in SAP note 1431793.

https://service.sap.com/sap/support/notes/1431793

 

create_restore_point.sql

pre_upgrade_checks.sql

pre_upgrade_status.sql

pre_upgrade_tasks.sql

utlu112i_sap.sql

Performing the Database Upgrade

• To upgrade the database, use the Oracle Database Upgrade Assistant (DBUA).

• StartAll ProgramsOracle – <NEW_ORACLE_HOME_NAME>Configuration and Migration ToolsDatabase Upgrade Assistant

Note:

     Note that if you use this method, you do not automatically run the SAP-specific DBUA upgrade scripts, and you have to run them after the upgrade      manually.

• If not yet stopped, stop the SAP system.
• Do not stop the database instance. The database instance must be running in the current (old) environment.
• Change the registry entry of ORA_<DBSID>_AUTOSTART by entering the command:<new_Oracle_Home>\bin\oradim -edit –sid <dbsid> –startmode manual  Ignore the error message: Unable to start service, OS Error 1056.
• Alternatively, use regedit.exe to change the registry key to value FALSE. The registry key is available at HKLM:\Sofware\Oracle\KEY_<DBSID>11203

DBUA steps:

SCREEN	Input
DBUA: Welcome	Start DUBA from 11g  home >>Choose Next.
DBUA: Select Database	1. Select the database that you want to upgrade. 2. Choose Next. The DBUA analyzes the database to be upgraded and performs pre-upgrade checks. 3. If the DBUA warns you of issues that need to be fixed before the upgrade, you need to analyze and act on these warnings. The most common warning or information messages are as follows:=W�Q& Database is using an old timezone file version Upgrade of TSTZ data is done automatically if the DBUA was started using dbua.sap.ps1. Database contains schemas with stale optimizer statistics See SAP Note 1431793, section 4. Running the Pre-Upgrade Scripts.Database contains INVALID objects prior to upgrade See SAP Note 1431793, section 4. Running the Pre-Upgrade Scripts. If there is not enough space for the SYSTEM tablespace, increase the space.˘EóÈv° If you are prompted to resize the rollback segment SYSTEM, choose Continue. 4.Choose Yes to continue with the upgrade.
DBUA: Upgrade Options	The following options are available: Recompile invalid objects at the end of the upgrade Leave this selection unchanged. The option lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. If the database server has multiple CPUs, the DBUA automatically proposes the number of parallel processes to be used for the recompilation. Backup database Since you have already performed the Oracle database backup [page 23], you do not need to select this option. Choose Next.
DBUA: Move Database Files	Leave the default setting Do Not Move Database Files as Part of Upgrade and choose Next.
DBUA: Recovery and Diagnostic Location	1.Do not select Specify Flash Recovery Area. 2.If you opened the DBUA with the Start menu, in the Diagnostic Destination field you have to specify the location of the saptrace directory using the Browse button. 3.Choose Next.
DBUA: Management Options	Deselect Configure the Database with Enterprise Manager, if selected, and choose Next.
DBUA: Summary	Review the summary of changes to be made. This includes the warnings that you ignored or did not fix, components to be upgraded, parameters to be added, removed, and changed after the upgrade. Choose Back to make any final adjustments, if required. Otherwise, leave the default settings and choose Finish to start the upgrade. The upgrade process itself runs for some time, depending mainly on the size of the database and the capacity of the hardware. You can ignore the warning ORA-32004 obsolete or deprecated parameter(s) specified for RDBMS instance. When the DBUA has completed successfully, the results of the

Screen shot of DBUA

If you started the DBUA from the Start menu, you must perform additional steps to perform the post-upgrade script (see below).

Additional Steps When Starting the DBUA from the Start Menu

If you started the DBUA from the Start menu, you have to check the upgraded database and perform the post-upgrade script manually.

To do this perform the following steps of SAP note 1431793:

“6.1 Checking the upgraded database ”

“6.2 Running post-upgrade scripts manually ”

 

 

Post-Upgrade Steps

1. You set the user environment variables
2. You create the Oracle TNSListener service 
3. You change the registry value of Oracle Autostart 
4. You check the start up type of the Oracle services
5. You perform post-upgrade tasks 
6. You delete the old Oracle software

After the Oracle database upgrade, you need to perform the steps described here.

 

You set the user environment variable.

 

       In the user environment and system environment <DBSID>adm, check the PATH variable and, if required, remove all parts referring to the old Oracle                 version. 

          When you modify the user environment, you must be logged on as the corresponding <DBSID>adm user.

• In the user environment of <DBSID>adm, set the ORACLE_HOME variable to the correct value for Oracle 11g, for example to: <DRIVE>:\ORACLE\<DBSID>\11203.

• Copy tnsnames.ora and sqlnet.ora from %ORACLE_HOME%\network\admin to \\<sapglobalhost>\sapmnt\<DBSID>\SYS\profile\oracle.

       (This information is required for all ABAP application servers you install on a separate host to find the correct location of these files.) 

• Set the user environment variable TNS_ADMIN to point to the directory \\<sapglobalhost>\sapmnt\<DBSID>\SYS\profile\oracle.

          Set TNS_ADMIN on all ABAP application servers.

• Log off and log on again to activate the environment changes in your user session.

 

Creating the Oracle TNSListener Service

• Stop the old Oracle listener before you create the Oracle TNSListener Service.( from ms service or command prompt: LSNRCTL STOP

          Create New listener service use command prompt or run commad:

          <complete_path_to_new_Oracle_Home>\bin\lsnrctl start

          This will start the listener from the new Oracle home. As the listener service does not yet exist, you will get the following error message: Failed to           open service <Oracle<SID>11202TNSListener>, error 1060. Then the service will be created and started.

 

 

 

Changing the Registry Value of Oracle Autostart

Change the registry value of ORA_<DBSID>_AUTOSTART. Open a command prompt and enter the following command:<new_Oracle_Home>\bin\oradim -edit -sid <dbsid> -startmode manual

Ignore the error message: Unable to start service, OS Error 1056.

Alternatively, use regedit.exe to change the registry key to value FALSE. The registry key is available at HKLM:\Sofware\Oracle\KEY_<DBSID>11202

 

Checking the Start Up Type of the Oracle Services

 

        Start the Oracle services (Database and Listener), if not yet started. 

Also, if not yet started, start the Distributed Transaction Coordinator Service.

In a standard configuration, set the startup type of OracleService<DBSID> and Oracle<ORACLE_HOME_NAME>TNSListener to automatic to ensure that they are automatically restarted after booting.

Performing Post-Upgrade Tasks (Follow the SAP NOTE 1431793)

Example :Open a command prompt and change to the directory <new_oracle_home>\sap\ora_upgrade\post_ugprade.

From this directory start sqlplus.exe and enter the following commands:SQL>connect / as sysdbaSQL>@post_upgrade_status.sql

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

 

Run the below scripts one by one

 

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

       You can find an automated script in SAP Note 1171650 to help 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

Deleting the Old Oracle Software

• Do not delete the old software, if it still has to be accessed by another database instance running with this version.
• Before you delete the old Oracle software, you can perform a backup of your database
• To deinstall the Oracle 10.2 software, you use the Oracle Universal Installer (OUI) from older home.
• To delete a service, open a command prompt and enter:sc delete <service_name>

Above Details will help only for the standalone SAP on Oracle upgrade . And I did the upgraded as per  above mentioned steps .For  Cluster environment   download the standard document from sap. Database Upgrade Guide