sybsystemprocs corrupted in Adaptive Server Enterprise 16.0 when running SAP Identity Management 8.0

[former_member584332]

Hi IdMExpert,

We are facing a problem in our development IdM system. We have an Adaptive Server Enterprise 16.0 SP02 PL04 EBF 26122 where the sybsystemprocs was corrupted when the Identity Managament 8.0 was apparently ok. This problem does not allow us to start up the database after its VM was rebooted.

Our system is a SAP Identity Management 8.0 on Adaptive Server Enterprise 16.0 SP02 PL04 EBF 26122 running in Red Hat Enterprise Linux Server release 6.9 (Santiago). We know the first versions of SAP IdM was available in Oracle and MS SQL database, but the Sybase is allowed in our version by PAM. We have doubt if it is recommended for us to move our system to one of these databases instead of continuing to use Sybase.

Best regards,

João Paulo.

[madhvi_pai]

Hi João Paulo,

ASE 160 SP02 PL04 is supported for use with SAP IDM 8.0 - it is perfectly fine to continue with SAP ASE as the database of choice for SAP IDM. It is advisable to use the latest available version of SAP ASE though - which would be ASE 160 SP02 PL07.

Corruption of the sybsystemprocs system db is an untoward occurrence and is not expected under normal circumstances - can you please let me know if there was any ASE/system update/modification, after which this db was possibly rendered corrupt? Was it an IDM update or any such?

Thanks and Regards,

Madhvi Pai

SAP Product Support

[former_member584332]

Hi Madhvi Pai,

We updated the SP to ASE 160 SP03 PL04 as available in the SDK FOR SAP ASE 16.0 (software download SP) and updated the SAP Identity Management 8.0 SP05.

However, after the update we now have a problem with the dispatcher. Everytime it starts, it stays running during 300 seconds, and then the dispatcher get stopped.

We checked in another thread in SCN that it occurs because the dispatcher can't determine if the last started dispatcher was shuted down succesfully.

Check the thread below.

https://archive.sap.com/discussions/thread/3680352

Best regards,

João Paulo.

[madhvi_pai]

Hi João Paulo

Thanks - this is a separate and distinct problem..Is ASE db up and running during this time? We may need to check with the BC-CST team as to why disp+work terminates.

Thanks,

Madhvi

[former_member584332]

Hi Madhvi Pai,

We identified the problem was on the JDBC driver used to connect SAP IdM dispatcher to DB ASE, and to solve this issue, we applied the early version and re-running the schema of database.

Thank you.

João Paulo.

[madhvi_pai]

Thanks for the update.

Regards,

Madhvi