Oracle 12C upgrade and AS JAVA Upgrade Issues.

Recently we have performed Oracle 12C upgrade for our SAP EP ( NW7.3 Sp05 ) and PI ( NW 7.3 Sp05 )landscapes. Here I am listing the issues which we have experienced and the resolutions.

Oracle 12C upgrade need SSFS for ABAP, and installation ID ( Oracle ) and Oracle home Owner ( OracleHome<N> ) and they should be different than <OraSID>.

Issue 1:

DB and Listener are up after 12 C upgrade,  But when we try to connect to config tool , we received the error with cause

Caused by: oracle.net.ns.NetException: Listener refused the connection with the following error:

ORA-12505, TNS: listener does not currently know of SID given in connect descriptor

 

Solution 1:

Add the parameter:  local_listener= < SID / Service NAME from tnsnames.ora> to init<SID>.ora  and restart Database with P file.

Or execute the below sql command

Alter system set local_listener = SID / Service name from tnsnames.ora.

Issue 2:

After DB upgrade , when we start the AS Java application, Start-up frame work ended with the below error  in log_bootstrap.<n> in the work directory.

com.sap.engine.bootstrap.SynchronizationException: Storage access initialization failed due to OpenSQL error.Check if your db driver file is available on the file system or if the user has correct permissions for that file

Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported for ORACLE database.

Solution 2:

Drive:\oracle\SID\12102\jdbc\lib, replace the odbc / jdbc files with older ones and restart the Java stack.

For more info follow the note: 2241220

This is the issue for the systems on <= NW 7.3 Sp09

 

Issue 3 :

Components patch levels above 0 to 99 are shown as A1, B1, etc. Hence it shows as deviation in SUM tool

Solution 3 :

Select take over calculated level option on the same page and proceed.

 

 

Issue 4:

SUM Post Process stopped due to DDIC password changed after starting the SUM.

Solution 4:

Set the DDIC password to the same one which you supplied to SUM process and do not change it throughout the upgrade / update process.

Note : Keep the same password for DDIC/ SAPServiceSID/ System throughout the upgrade. These IDs are used to logon to SAP/ DB

Issue 5:

After Oracle 12C upgrade, Java stack is not starting and ending with an issue in JVM configuration.

Solution 5:

Update the parameter in Java instance profile

j2ee/dbdriver = Drive:\oracle\SID\12102\jdbc\lib\ojdbc6.jar

Issue 6:

SUM was not accepting the stack xml pointing the kernel version is not compatible ( Kernel is on 720 and SPS upgrade is planned for NW SPS15). Also, SUM will ask us to enter the password of SIDADM repeatedly and will not proceed further.

Solution 6:

Download and update the Kernel to 721/722 N-1 patch.

Issue 7:

Upgrade failed in SUM execution phase referring to the dependencies on other SDA files.  (This is after Oracle 12 C upgrade and even after following the note 2241220)

[ERROR CODE DPL.DCAPI.1027] DependenciesResolvingException.

Reason: ASJ.dpl_dc.006505 An unresolved dependencies error occurred while sorting the deployment batch items regarding the dependencies.

Jul 27, 2017 5:23:20 PM [Error ]: Deployment error. See log Drive:\usr\sap\SUM\SUM\sdt\log\SUM\deploy_api.0.log for details.

Solution 7:

Deploy the core java components with telnet and proceed with SUM from the point where it failed ( please note do not close / cancel / reset ( anyway not possible ) SUM when it failed in Execution phase.  Also , download the Server core and J2ee API files from the note.

Issue 9:

After GST implementation, after few days, we have received complaints from end users saying MIRO transaction is very slow and is taking 15-20 min per transaction.

Solution 9:

It was noticed from performance trace that full table scan is taking place on MSEG and is the reason for performance issue.

SAP has released a note for post GST performance issues (note 413446 ) related to MIRO and related transactions. We have created the necessary indexes and corrected the performance issues.

Issue 10 :

We have started oracle 12 C upgrade, and it has got failed in DBUA upgrade phase saying

ora-16032 : Parameter LOG_ARCHIVE_DEST  Destination string can not be translated.

ORA-09291 : saskchk : Invalid device specified for archive destination

Solution 10 :

The error will occur on DBUA while upgrade is in progress and if you click ignore / abort – in next screen it prompt you saying oracle not available.

The oracle is installed with ID Oracle

Oracle home owner is Oraclehome<N>

We are performing upgrade with SIDADM or ORASID

When Upgrade started in the initial screen it ask for password of oracle home owner , and we will provide user ID and proceed further. When upgrade is in progress , the SIDADM will bring down the running database and oraclehome owner will try to start the DB with new home to run all catdb<*>.sql files  while doing so oracle will go unavailable if the home owner is not provided with right permissions.

In our case, the user oraclehome<N> was not added to the admin groups as mentioned by SAP.

net localgroup ORA_<SID>_DBA oraclehome2 /add

net localgroup ORA_<SID>_OPER oraclehome2 /add

Note : Do not miss any step mentioned in guide while upgrading upgrade.