Unable to start SAP Portal 640 after Oracle Upgrade to 11G

[Former Member]

Dear All,

We have upgraded the oracle database from 9i to 11G and also as per pre-requisite, we have upgraded the kernel to 640_EX2 as per below.

Our kernel version :

kernel release 640

kernel make variant 640_EX2

As per the Oracle upgrade guide, we have made the changes to rdbms.driverLocation on several locations.

Now we are unable to start portal system.

-

---

ipsadm> startsap

Checking IPS Database

-

---

J2EE Database is not available via test

See logfile JdbcCon.log

Starting SAP Instance SCS01

-

---

Startup-Log is written to /home/ipsadm/startsap_SCS01.log

Instance on host ussapsie01 started

Starting SAP-Collector Daemon

-

---

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

• This is Saposcol Version COLL 20.95 640 - AIX v11.16 5L-64 bit 080318

• Usage: saposcol -l: Start OS Collector

• saposcol -k: Stop OS Collector

• saposcol -d: OS Collector Dialog Mode

• saposcol -s: OS Collector Status

• The OS Collector (PID 2781346) is already running .....

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

saposcol already running

Running /usr/sap/IPS/SYS/exe/run/startj2eedb

Trying to start IPS database ...

Log file: /home/ipsadm/startdb.log

/usr/sap/IPS/SYS/exe/run/startj2eedb: Terminating with error code 12

DB startup failed

-

---

ipsadm> R3trans -d

This is R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'IPS'"

R3trans finished (0012).

Can some one please help me to resolve this issue.

Thanks...

Regards,

Sreenivas

[former_member509448]

Hello

I have the same issue. How did you solve it???

Thanks

Regards

[Former Member]

Hello Sreenivas,

Funny issue. Anyways oracle upgrade has couple of steps around Listener. Ideally if listener would have been the problem portalshould not have started up . But can you still check if the correct listener is running and that you have completed all steps regarding the listener? I have a feeling that it has something to do with the listener

Regards.

Ruchit Khushu.

[TomCenens]

Hello Sreenivas

Did you update your Oracle client also according to the upgrade procedure?

Did you update the classes12.jar and ojdbc.jar that are in the filesystem structure of the SAP system?

Kind regards

Tom

[Former Member]

Please check the j2ee profile parameter in default or instance profile

[Former Member]

Dear All,

Please find below startdb.log

==========

ipsadm> more stopdb.log

-

---

Tue Feb 22 17:00:50 CUT 2011

LOGFILE FOR STOPPING ORACLE

Trying to stop IPS database ...

-

---

Tue Feb 22 17:00:50 CUT 2011

checking required environment variables

ORACLE_HOME is >/oracle/IPS/112_64<

ORACLE_SID is >IPS<

-

---

Tue Feb 22 17:00:50 CUT 2011

Connect to the database to check the database state:

R3trans check finished with return code: 12

There is no database connect possible -

Database is probably already stopped.

-

---

Tue Feb 22 17:00:50 CUT 2011

checking V2 connect

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

And have checked for default and instance profiles, they are pointing to correct values.

Please suggest on this.

Thanks...

Regards,

Sreenivas

[Former Member]

Hi All,

Sorry the previous one is stopdb.log

Please find below the startdb.log..

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

ipsadm> more startdb.log

-

---

Tue Feb 22 16:56:22 CUT 2011

LOGFILE FOR STARTING ORACLE

Trying to start IPS database ...

-

---

Tue Feb 22 16:56:22 CUT 2011

checking required environment variables

ORACLE_HOME is >/oracle/IPS/112_64<

ORACLE_SID is >IPS<

-

---

Tue Feb 22 16:56:22 CUT 2011

check initora

-

---

Tue Feb 22 16:56:22 CUT 2011

check initora

-

---

Tue Feb 22 16:56:22 CUT 2011

checking V2 connect

TNS Ping Utility for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production on 22-FEB-2011 16:56:22

Copyright (c) 1997, 2009, Oracle. All rights reserved.

Used parameter files:

/oracle/IPS/112_64/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = ussapsie01)(PORT = 1527)) (CONNECT_DATA = (SERVER = DEDICATED)

(SERVICE_NAME = IPS)))

OK (130 msec)

tnsping: V2 connect to IPS

-

---

Tue Feb 22 16:56:23 CUT 2011

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

-

---

Tue Feb 22 16:56:23 CUT 2011

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

-

---

Tue Feb 22 16:56:24 CUT 2011

starting database

SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 22 16:56:24 2011

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to an idle instance.

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 1570082816 bytes

Fixed Size 2207088 bytes

Variable Size 721420944 bytes

Database Buffers 838860800 bytes

Redo Buffers 7593984 bytes

Database mounted.

Database opened.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

-

---

Tue Feb 22 16:56:38 CUT 2011

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

• ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/IPS/SYS/exe/run/startj2eedb: Terminating with error code 12

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

Can some one please clear me... Do we have same Kernel for Portal systems also as like sap R3 or any other path to download kernel 640_EX2 for portal systems.

Thanks...

Regards,

Sreenivas

[sunny_pahuja2]

Hi,

Check SAP Note 1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade. Whether you have performed all steps or not.

Thanks

Sunny

[sunny_pahuja2]

Hi,

First of all R3trans -d does not work in portal as it used JDBC connection to connect to database. Could you please try to start the database manually (i.e. from sqlplus) instead of starting from startsap ? then check whether database is getting started or not. If not, then please check oracle alert log file. Also, paste the error log here.

Thanks

Sunny

[Former Member]

Hello Sunny,

Thanks for your info.

We could able to start and stop the DB from SQL level.

One more intesting tihng is .... When we first give startsap, it is starting oracle db and not able to proceed with j2ee.

And again if we give startsap R3(with DB up and running), it is starting all java services and able to loginto portal with out any issues. Here I could observe that either issue with communication between SAP and Oracle in starting up or the Kernel files are not correct.

Do we have any other kernel 640_EX2 for portal systems, I am just following the below files.

My Company's Application Components" SAP KERNEL 64-BIT" SAP KERNEL 6.40_EX2 64-BIT

SAPEXE_327-10004775.SAR

SAPEXEDB_327-10004770.SAR

Kindly have a look and help me on this.

Thanks...

Regards,

Sreenivas

[sunny_pahuja2]

Hi,

Could you please paste /home/ipsadm/startdb.log log here ?

Thanks

Sunny