Unable to create routine 'SAPTOOLS.DBH_PKGCACHE_COLLECT'

[Vivek_Hegde]

Hello All,

Background:

SAP SM 7.1 SP03

Managed System Configuration - Automatic Configuration

Issue:

Getting below error in DB Extractor Setup step:

Error in RDI back-end setup occured!

Unable to create routine 'SAPTOOLS.DBH_PKGCACHE_COLLECT'

Any idea on how to resolve this error?

Regards

Vivek

[Vivek_Hegde]

Resolved the error by DEIMPLEMENTING following notes:

0001638865 DB6: High Number of Messages in SAPTOOLS.SP_MSG_LOG

0001738557 Hosts not filled in Host Service Memory extractor

0001745035 DB6: DBA Cockpit Back-End Is Under Forced Ownership

0001745270 DB6: Dump During Data Collector Implementation

0001746808 DB6: SQL0456N When Setting Up Data Collectors

0001747260 DB6: Package Cache Data Collector Causes SQL0433N

0001756380 DB6: Lange Transaktionslaufzeiten bei REORGCHK_ALL

0001757131 DB6: Data Collectors Cause Full Transaction Log

These notes were part of following central correction note:

0001456402 DB6: DBA Cockpit Corrections for SAP Basis 7.02/7.30/7.31

It is strange that now-a-days deimplementation of SNOTEs are solving more problem than implementing them

Hope this helps someone !!

[steffen_siegmund]

Dear customers,

the provided "solution" by Vivek Hegde is highly risky! It deimplements very critical patches and as result you implement a data collector successfully, which might cause a transaction log full situation on the managed system.

Instead, you should always keep SAP Note 1456402 up to date and always check, if the linked SAP Notes have updated correction instructions.

If you still have issues, open an OSS message.

Best regards,

Steffen Siegmund

[Vivek_Hegde]

Hello Steffen,

We started getting dumps in DB extractor setup only after implementing SAP Note 1456402 on 24.09.2012. This had not occurred earlier.  May be this collective note had a bug or something. Now I see the latest version of above note released on 26.09.2012. Hope the issue is being taken care in the newer version.

Best Regards

Vivek

[steffen_siegmund]

Hi Vivek,

probably you hit the issue described in SAP Note 1769246 (created on 28.09.2012). This one is now referenced in the central SAP Note 1456402. So if you just download latest version and also reload all implemented SAP Notes, you should not have any issues.

If you still have issues, please open an OSS message.

Best regards,

Steffen Siegmund

[anc13n7]

Hi Steffen,

im having almost same kind of issues.

I was trying to schedule the data collector for LOCK EVENTS. The error message is the same as above. But drilling down i came across following message

Database: <SID>

caused by

Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT

Kernel Error ID:

DB Error: Yes

SQL Code: 204-

SQL Message: SQL0204N "SAPTOOLS.LOCK_EVENT" is an undefined name. LINE NUMBER=298. SQLSTATE=42704

DB Object Exists: No

Duplicated Key: No

Internal Error: 5

Invalid Cursor: No

Unknown Connection: No

Connection Closed: No

Ive got no clue whatsoever how to overcome this problem. 1456402 is already implemented and the ones mentioned by vivek were not in the system. So the opportunity to try out the deimplementation could not be availed.

Apart from that following notes are also in the system

1598074

1654250

1816097

1817052

1817567

1820785

1824256

1828601

1833064

System specs

SAP SOLUTION MANAGER 7.1 SP 08

Managed System:EHP6 FOR SAP ERP 6.0

Both of them are running with DB6 : 09.07.0007 on RHEL6.

Regards,

Haroon

[steffen_siegmund]

Hi Haroon,

could you open a customer call for the affected system at BC-DB-DB6-CCM? I need HTTP and R/3 connection to the SAP Solution Manager system.

Best regards,

Steffen

[anc13n7]

Hi Steffen,

well thats the tricky part.[ very long corridors] I'll have to get an approval for that. But as soon as its done. Would let you know.

Regards,

Haroon