SAP XI server0 stopping after trying to start

[Former Member]

Hi All ,

I'm really new to SAP , recently my SAP XI development server (Java Stack) stopped and when i check the log It gives this error when it try to start services , anyone has any idea on this ?

service dbpool ================= ERROR =================

Core service dbpool failed. J2EE Engine cannot be started.

java.lang.NoClassDefFoundError: com.sap.sql.trace.cpt.impl.SQLTraceCptRecordImpl

at java.lang.Class.initialize(Class.java:307)

at com.sap.sql.trace.cpt.impl.CPTHelperImpl.isCptTraceActive(CPTHelperImpl.java:83)

at com.sap.sql.trace.cpt.CPTHelper.isCptTraceActive(CPTHelper.java:50)

at com.sap.sql.trace.SQLTrace.isOnCPT(SQLTrace.java:392)

at com.sap.sql.trace.SQLTrace.isOn(SQLTrace.java:386)

at com.sap.sql.jdbc.direct.DirectPreparedStatement.setLong(DirectPreparedStatement.java:481)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.getConfiguration(DBAccessDefault.java:603)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:77)

at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:60)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)

at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.getCachedConfiguration(ConfigurationHandlerImpl.java:373)

at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getData(ReadAccessConfiguration.java:84)

at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getMetaData(ReadAccessConfiguration.java:211)

at com.sap.sql.connect.OpenSQLConfiguration.syncConnProperties(OpenSQLConfiguration.java:349)

at com.sap.sql.connect.OpenSQLConfiguration.syncRootProperties(OpenSQLConfiguration.java:329)

at com.sap.sql.connect.OpenSQLConfiguration.<init>(OpenSQLConfiguration.java:147)

at com.sap.sql.connect.OpenSQLConfiguration.getInstance(OpenSQLConfiguration.java:160)

at com.sap.sql.connect.OpenSQLConnectionFactory.dataSourceStateChanged(OpenSQLConnectionFactory.java:271)

at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1536)

at com.sap.engine.services.dbpool.deploy.ContainerImpl.createDefaultDataSource(ContainerImpl.java:760)

at com.sap.engine.services.dbpool.PoolFrame.start(PoolFrame.java:94)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

[desiree_matas · Accepted solution]

Hello,

Try the following, it should resolve the problem:

Rename these folders:

- ./cluster/dispatcher/temp/cpt

- ./cluster/server0/temp/cpt

for example as follows

- ../cluster/dispatcher/temp/cpt -> ./cluster/dispatcher/temp/cpt_temp

- ../cluster/server0/temp/cpt -> ./cluster/server0/temp/cpt_temp

Then restart your system.

The cpt directory is automatically recreated. And this should fix the issue.

Regards,

Désiré

[Former Member]

thanks for the clarification as well this is really worth ..

[desiree_matas]

Hi,

That's good news!

This issue occurs only in rare cases where the cpt data is left in a specific state that the system cannot parse correctly.

If you encounter problems again with the startup of the dbpool service with the exception:

java.lang.NoClassDefFoundError: com.sap.sql.trace.cpt.impl.SQLTraceCptRecordImpl

you only have to move or delete the CPT data. But this is quite rare and it should not occur anymore.

Regards,

Désiré

[Former Member]

Hi Désirée,

Thanks sooooooooooooooooooo much it's ok now... thanks again for the help ...method u said worked well. As this is something new for me can you please tell me why it happened so ?

Thanks Ahamed tooo for the help and quick reply thanks both of you soo much

[desiree_matas]

Hi,

You have to rename the folders so that they can be recreated. So the one you have find:

/usr/sap/XID/DVEBMGS01/j2ee/cluster/server0/temp/cpt

shold be renamed, for example, to /usr/sap/XID/DVEBMGS01/j2ee/cluster/server0/temp/cpt_bak

Do the same for the dispatcher node and for any other server node.

And then restart the system.

Regards,

Désiré

[Former Member]

Hi Désirée,

Thanks soo much for your reply

There's folder wchich is having the same name as the one you mentioned here in the below directory

/usr/sap/XID/DVEBMGS01/j2ee/cluster/server0/temp/cpt

so doest it still needs to be restarted ?

Ahamed I'll follow the process you asked and let you know.....

Thanks Both for the replies

[Former Member]

Hi,

- Check whether the profile is available and try to start the with <sidadm> user.

- Restart after cleaning the memory if its a Unix based OS (cleanipc <instno> remove)

- Check the dispatcher and SDM is running.

- Post the log available at homedirectory of user <sidadm>, dev_server0

Thanks

Ahamed