Error Publishing Catalog

[Former Member]

I am having a problem publishing catalogs in SRM. The exception in the parent program is /CCM/CX_PUBLICATION_FAILED. This program spawns a child Dialog process that eventually dies with a timeout exception /CCM/CX_TIMEOUT. I can connect to Trex and was able to create a test index and the Trex search functionality still works. I also looked through the table /CCM/D_PUB_ST and changed the status of several entries from A to E but the process still times out. Any suggestions or help would be appreciated.

Thanks,

Dave

[Former Member · Accepted solution]

Hi

Which SRM / CCM version, support packs are you using ?

<b>Please go through the following SAP OSS Notes and other details provided in the links, which will definitely help -></b>

Do let me know.

Regards

- Atul

[Former Member · Accepted solution]

Atul,

Thank you for the reply, unfortunately the notes that you attached either aren't relevant or did not fix the problem. I do appreciate your posting some of them were worth investigating.

[Former Member]

The problem ending up being a setting in SPRO. We are publishing to the same client so after applying a support stack we needed to check the Publish Locally field in -

Cross-application components

> SAP Catalog Content Management

>> SAP Catalog Authoring Tool

>>> Specify Settings for Publishing Catalogs

This worked with the field unchecked in our development environment but needed to be set for QA and Prod.

Dave

[Former Member]

Hi

<u>Try deleting some data from the table - /CCM/D_VALUE_H.</u>

<b>Please go through the following SAP OSS Notes -></b>

Note 973702 - Delete History Option in CAT throws Errors

Note 1039192 - Delete History Report takes too long or ends with an error

Note 909523 - Performance improvement for history deletion

Note 1020133 - Modification to the /CCM/DELETE_HISTORY_BG report

Do let me know.

Regards

- Atul

[dennis_bruder]

Hi,

how many entries has your history table /CCM/D_VALUE_H?

Maybe that's the reason for the timeout.

Regards

Dennis

[Former Member]

Hello,

I have experienced that in such cases

TREX server sizing

TREX server restarting

Updating TREX patch level

may help

You can try

BR

Dinesh

(Reward if helps)