cancel
Showing results for 
Search instead for 
Did you mean: 

Error during master catalog publish

Former Member
0 Kudos

Dear Experts,

we are on SRM5. During Master catalog publishing we are getting the below error

its saying "Error when generating catalog /CCM/MASTER_CATALOG" (this is coming during publish entire catalog)

pasting the log details of the same

9.03.2009 17:08:08 (INDIA): Package 0001 is being updated locally

Error when generating catalog /CCM/MASTER_CATALOG

Catalog update was terminated

19.03.2009 17:08:10 (INDIA) ************* End Applications Log for Package 0001 ********************

19.03.2009 17:08:10 (INDIA): Package Nr. 0001 was sent

Publication in target system was discarded

Exception /CCM/CX_PUBLICATION_FAILED occurred (program: /CCM/CL_PE_PACKAGING_SERVICE==CP, include: /CCM/CL_PE_PACKAGING_SERVICE==CM00R, line: 631).

Exception /CCM/CX_PUBLICATION_FAILED occurred (program: /CCM/CL_PE_REQUEST_SERVICE====CP, include: /CCM/CL_PE_REQUEST_SERVICE====CM00F, line: 164).

19.03.2009 17:08:04 (INDIA): system is waiting for response messages

19.03.2009 17:08:10 (INDIA): >>> Start: Processing of confirmation message for package 0001

Definition scope SE_/CCM/MASTER_CATALOG 0000000001 already exists

Unable to create definition scope SE_/CCM/MASTER_CATALOG

Unable to initialize the characteristics/data types (catalog /CCM/MASTER_CATALOG)

Error when generating catalog /CCM/MASTER_CATALOG

Local update of package 0001 has failed

19.03.2009 17:08:10 (INDIA): >>> End: Processing of confirmation message for package 0001

19.03.2009 17:08:10 (INDIA): >>> Start: Processing of confirmation message for catalog

Local publication of catalog /CCM/MASTER_CATALOG has failed

Catalog update was terminated

19.03.2009 17:08:10 (INDIA): >>> End: Processing of confirmation message for catalog

19.03.2009 17:08:11 (INDIA): End of catalog publication

      • Total runtime of catalog publication: 00:00:07 ***

Please do help me

Regards

Shuban

Accepted Solutions (0)

Answers (5)

Answers (5)

jason_boggans
Active Contributor
0 Kudos

Hi,

In the catalog client, check the report /CCM/CHECK_TREX. In here you will see the relevent catalog index, if it is red or orange, even after a restart of the TREX and it is observed that trex is fully operational then the index should be deleted here by drilling into it and the catalog republished in full.

As mentioned by Laszlo, you can check the table /ccm/d_pub_st to verify there is no 'stuck' publication (use note 1092047 to clear these entries if desired) and also /ccm/d_upd_state to ensure no catalog is stuck in update mode (use report /ccm/cleanup_update_status for this) finally you should ensure catalogs are not locked in table /ccm/d_ctlg_req without a corresponding valid running job. If entries exist in field req_sender they will need to be removed by using the report /CCM/CLEANUP_CATALOG.

If you are not 100% positive of what you are doing in this case then please raise a message with SAP for clarification as this report is classified as internal and should only be operated by SAP Employees

Regards,

Jason

Former Member
0 Kudos

Some additional informations,

restart the TREX server can solve this problem only in special cases, if you have error messages regarding the TREX.

To publish the catalog again, you should clean the tables /CCM/D_CTLG_REQ and /CCM/D_PUB_ST, and after that the inactive version should be deleted with cleanup_catalog.

It isn't recomended to delete the versions yourself, this can be do by the support.

Former Member
0 Kudos

Hi,

This problem occurs many times while catalog is viewed at the same time it was published. Please make sure no body is viewing while publishing.

Regards,

Lalit

0 Kudos

Hello,

you have to restart TREX processes.

Best regards.

Former Member
0 Kudos

Hi,

you need to create an OSS-Message for the support regarding this issue.

We in support, have authorization to delete the locked process, and delete inactive versions.

This problem need to analyse in your system.

If you create a message, the following information should be maintained:

system name/client

logon data

system connection to open

catalog name

enough authorization to user (e.g.: sap_all).

Regards

Laszlo