Reconnect to portal database after database restart

[Former Member]

Hi,

After having seen a 24/7 EP system in production for a while, there is one contributing factor which is causing more downtime than we would like (even though the downtime is very small).

When ever the portal database is restarted or we loose the network connection, the SAP J2EE (and hence EP) is not able to reconnect to the database (as you would expect from such a mature product). The forces us to take down the entire cluster (yes the cluster is big and takes a lot of time to restart) and then take it up again.

An OSS has been open (and been through development) and the verdict is that it cannot be done.

However, I don't believe them. Some of you SAP expert here must know of some very cleaver hack to get this working.

If you have any ideas or experience with this, please do not hesitate to post it.

[former_member182060]

Hi Parnas,

as of PL13 of SAP J2EE, the reconnection feature has been implemented in J2EE/DBPool.

Could you please send me the CSN msg, so that I can get the details and follow up, please.

Regards

Bernhard

[Former Member]

I've sent you an email on your sap mail with the OSS number

[Former Member]

Managed to find some undocumented command that did the trick.

1. Telnet to the administration console (port 50008 is standard ?)

2. Login as administrator

3. Run the lsc command in order to get the cluster id of an application node

4. Change the active node to an application node

>jump <clusterId>

5. Add the dbpool command set

>add dbpool

6. Close the database pool

>close_pool <poolname> -force

7. Open the database pool

>open_pool <poolname>

From the SAP J2EE administration console in the dbpool there seems to be a functionality for closing and opening the pool, but this doesn't work, at least not in PL21 (maybe it doesn't force the connections to close)

Message was edited by: Dagfinn Parnas

[Former Member]

new post in order to get the status answered

[Former Member]

Hello Dagfinn,

We do not have this problem in J2EE 6.2 PL23 + MSSQL combination (EP6 SP2).

The problem must have been resolved in DBPool service between PL21 and PL23....

Regards

[Former Member]

Yes, or it is an oracle specific problem

[Former Member]

I am running EP6 SP2 Patch 5 J2EE PL26 with Oracle on Unix. Is it really necessary to manually get into the Administration Console to make the reconnection work? Are there parameters I can set to automate this?

Thanks

[former_member209154]

Hello Kmanw,

No manual steps should be necessary to make the Portal reconnect to the database again.

If the reconnect should not work then please check the logs and create an appropriate OSS message.

Regards,

Stephan

[Former Member]

We haven't had this problem lately when the database have been restarted (same version still). Since the problems with reconnecting has mainly been with the database we use for various components (and not the PCD) it could be connected to changes we've done in this code.

[Former Member]

Is this oracle or MSSQL?

If oracle then there should be minimal startup....

The oracle instance once it is mounted and open (which takes a couple seconds) the portal app should be able to connect....

Is your DB on a separate box?

John

[Former Member]

It is an oracle database which is running on a clustered environment separate of the portal.

We've seen this problem 3-4 time now, and even if the database is only restarted(meaning it is down for about 2 minutes) the portal still doesn't reconnect. Even restarting the sapep pool has had no effect (it has worked a couple of minutes after the pool restart, but then it has stopped working again).

We're going to have a restart of the DB tuesday and I have found an undocumented feature which I might think works. Will let you know how it works out.