The Configuration and Change Database (CCDB) of the Solution Manager 7.10 contains the configuration data of the connected managed systems. All types of managed systems having a Solution Manager Diagnostics Agent installed are technically supported. In addition to the latest configuration data, the history of the configuration is available within CCDB.
The configuration data is loaded daily into the CCDB to make sure the data is up to date. Since Solution Manager 7.10 the CCDB Administration allows you to control if the configuration data of a managed system is uploaded successfully.
The configuration data of the CCDB is used by the applications Change Reporting, Change Analysis and Configuration Validation. In addition there are service sessions like the EarlyWatch Alert reading data from CCDB.
The CCDB is not a real database but just a collection of tables within the database of the Solution Manager.
Where can I find CCDB Administration ?
CCDB Administration can be found in the Workcenter ‘Solution Manager Administration’. By transaction SM_WORKCENTER there is a jump to a URL which displays all Workcenters assigned to your user.
In the Solution Manager Administration Workcenter you can either access the CCDB Administration via ‘Infrastructure’ or just for selected technical systems via ‘Landscape’.
Start via ‘Infrastructure’ (or transaction ‘CCDB’):
Starting the CCDB Administration from here provides you the status of the CCDB Infrastructure and all technical systems that have at least one CCDB extractor setup.
Start via ‘Landscape’:
Starting the CCDB Administration from here allows you to display the status of the several selected l technical systems that have at least one CCDB extractor setup.
Managing the CCDB Infrastructure
The CCDB Administration Infrastructure view allows you to get an immediate overview about the overall CCDB tasks which have to be performed.
Detailed information about the CCDB Infrastructure:
A detailed explanation about these CCDB Infrastructure tasks can be found by clicking on the help button in the above screenshot.
After an upgrade to Solution Manager 7.10 or if required after the implementation of a support package the CCDB will may be process some special tasks which are called CCDB Conversion. During such tasks the CCDB is not available for other applications.
If such tasks are running or required there is the message “CCDB Conversion running or required” displayed next to ‘Mode’ in the CCDB Infrastructure status.
For details please refer to note 1586671 “CCDB: Conversion Tasks”.
Alerting for CCDB Infrastructure
For CCDB Infrastructure there is a dedicated Alert available in the Self Monitoring of the Solution Manager. After the Alerting has been setup the assigned recipients will get a notification as soon as a problem is detected in the CCDB Infrastructure.
It is recommended to use this Alert in a productive environment.
Metric and Alert:
Name of the Metric: ‘CCDB Infrastructure Status’
Name of the Alert: ‘SELFMON: Error in CCDB Infrastructure’
The Metric and Alert can be found in transaction SOLMAN_SETUP → Technical Monitoring → Solman Self Monitoring → Template ‘Self Monitoring Solution Manager ABAP’. The Metric and Alert is assigned to the ABAP stack of the Solution Manager i.e. SI7~ABAP in the below screenshot.
After the setup of the Alert you can find the Metric ‘CCDB Infrastructure Status’ in the Alerting Directory Browser:
By default the CCDB Infrastructure is checked by the Metric every 240 minutes:
Please refer to the Diagnostics Alerting documentation for more details.
If there is a red traffic light as in the screenshot below you can refer as a first step the ‘Exception’ view.
Depending on the problem there is a message which may help you to identify the problem. Here, in this case a deeper analysis is required.
After the problem is solved you can trigger the Store Check manually by the button ‘Trigger Store Check’ to get a green traffic light.
Below the CCDB Infrastructure Status there is some statistical information.
Managing Technical System(s) in CCDB
CCDB Administration allows to either to get an overview about the status of all Technical Systems known to CCDB or about the status of selected Technical Systems.
Managing all Technical Systems
By calling the CCDB Administration via ‘Infrastructure’ and clicking on the tabstrip ‘Technical Systems’ the status of all Technical Systems known to CCDB are displayed. For administrators this view is helpful to find Technical Systems having problems.
For detailed information how to use the tabstrip ‘Technical Systems’ please refer to the description below ‘Managing selected technical Systems’.
Managing selected Technical Systems
By calling the CCDB Administration via ‘Landscape’ you can select the status of selected Technical Systems via the POWL navigation. This allows you to use the already defined POWL queries.
After the Technical Systems are selected you can directly jump to the CCDB Administration Status clicking the ‘Configuration Change Database’ button:
Technical System Overview
Each line represents the status of a Technical System in the CCDB. If there is no technical problem, system downtime or anything similar a green light in the second column for the total status of a Technical System is displayed.
You can find the below information about the columns also via the ‘Help’ button displayed.
CCDB Technical System Store Status
The overall status of a Technical System in CCDB. A green traffic light means that there is no Store or extractor problem. A red light indicates either a problem with a Store or an extractor. You can also position the cursor on the light to get a status message displayed in the tooltip.
CCDB Store Status
The number of CCDB Stores is displayed in the columns 'Technical System Stores' and 'Related Stores' which refer to related landscape objects like host and database. The columns 'Correct', 'Warning', 'Error' and 'Not relevant' group them into a status. The grey status 'Not relevant' is used for Stores which are only available internally but not visible anymore for external applications like Change Reporting and Change Analysis.
This status of a Store is also called Main State Type representing green, yellow, red or grey.
CCDB Extractor Status
The CCDB extractors run once a day, in the evening. There are columns indicating how many extractors failed, how many extractors were not performed as planned and the total number of extractors. An extractor is evaluated as not performed if it hasn't been executed since yesterday morning.
The direct link to the EFWK CCDB Extractors
Jump to the EFWK Log Viewer
One of the most powerful features of the CCDB Administration ‘Technical System Overview’ is the direct link to the EFWK extractors loading the data into the CCDB.
By clicking on the link - marked above by the blue box - there is a direct jump into the EFWK Log Viewer displaying the corresponding CCDB extractors of the Technical System:
Note: You can find the jump back in the upper left corner displayed as a link ‘Back’.
Selecting an extractor allows you to see the past runs and their individual log:
In the log you can get detailed information i.e. the number of Stores processed or in case of problem a technical error message.
Manual trigger of the CCDB Extractors
The button ‚Execute Extractors‘ triggers the corresponding extractors of the Technical System as ‘to be executed immediately’ in the EFWK. Technically it means the EFWK will process these extractors as soon as possible. If the start of the extractors is not delayed (i.e. because of other extractors with a higher priority) it may take some minutes until the extractor have been performed.
The extractor execution can be monitored by jumping to the EFWK Log Viewer and there using the ‘Refresh’ button.
As soon as you are sure the extractors have been performed you have to refresh the information displayed in the ‘Technical System Overview’ using the ‘Refresh’ button. This will update the displayed data of the selected Technical System.
Triggering the extractors manually skips the extractor run in the evening. The next automatic run will be triggered the next day.
How to use the CCDB Technical System Overview
In case of a problem you can use the CCDB Administration for a technical analysis. Here, you should always start solving extractor related problems before analyzing problems for individual Stores.
Rule: First make sure the extractors are green before analyzing Store related problems !
1. Ensure that the extractors have finished successfully
If there are extractor related problems you can analyze them by clicking on the red links in the extractor columns. The corresponding EFWK extractor(s) will be displayed. Here you can find the technical return message(s) of the extractor(s) which can be used to find the cause of the problem(s).
If the problem is solved use the 'Execute Extractors' button to trigger all CCDB extractors of the Technical System, manually. When all extractors have finished - don’t forget to use the ‘Refresh’ button in the CCDB Administration, proceed to the second step.
2. Check the CCDB Store Status
If there are red CCDB Stores, you can follow the link to display them. In the Store List you can change the view to 'Error Analysis' to get the technical error message. Alternatively, you can use the button 'Store Details'.
For details about the ‘Store List’ please refer to chapter 'The Store List'.
The column 'Fatal error' refers to Stores which could not be uploaded in the CCDB for any reason, i.e. a dump occurred. You can use the application log in the Solution Manager to analyze this error: Transaction SLG1, enter object = 'CCDB' and specify a date and time range.
Not Relevant Stores
CCDB Stores with a grey status 'Not Relevant' can be deleted, depending on their main state. Before deletion, see the help text of the Store List for the meaning of the main states. Do not delete grey Stores with an error status. If you are not sure, you can leave 'Not Relevant' Stores untouched because they are just available in the CCDB Administration but not for external applications using the CCDB data.
Deleting Technical System data in CCDB
If you want to delete all data which is available in CCDB of a Technical System you can either perform this operion online or in background. In the most cases the background deletion is the recommended option because it may take several minutes.
By deleting this data you will use the complete configuration history !
Deleting a Technical System and its Stores in CCDB does not mean that the corresponding extractors in the EFWK are removed. If you want to delete them it is recommended to use the link to the EFWK Log Viewer, delete the extractors and then subsequently delete the Technical System and its Stores in the CCDB Administration.
If you just want to start a new history you should not delete the extractors. As a result the Technical System will appear again in the CCDB Administration after an extractor has been performed again.
Alerting for CCDB Technical System Store Status
There is a dedicated Alert which allows monitoring the overall Store Status of a Technical System. After the Alerting has been setup the assigned recipients will get a notification as soon as a red CCDB Technical System Store Status is detected.
It is recommended to use this Alert in a productive environment.
Metric and Alert:
Name of the Metric: ‘Health Check of CCDB stores’
Name of the Alert: ‘Errors in CCDB Stores’
The Alert is deactivated by default which means you have to manually edit the corresponding Alerting Template belonging to the Technical System and activate it.
The Store List
The CCDB Administration provides a section called Store List which is able to display Store details. This Store List is used by the ‘Technical System Overview’ and as well by the ‘Cross Selection’ tabstrip of the CCDB Infrastructure Administration.
Here as example, it is explained how it can be used from the ‘Technical System Overview’.
As soon as a Technical system is selected, the Store List appears below.
The Main State represents the calculated status of a Store in CCDB. The color of this main state is called main state type and can be green, yellow, red and grey.
For detailed information about the Main State, please use the ‘Help’ button of the Store List.
If there are technical problems the Store List groups the Stores into the Main States. Each Main State is displayed as on/off button. By enabling a Main State, the corresponding Stores are displayed.
In the example below the system MF8~ABAP has one failed extractor and five erroneous Stores. The Store List groups these five Stores into the Main State ‘Error’ and ‘Error and Content-out-of-date’. By enabling ‘Error’ as in the screenshot below, four Stores are displayed.
To get a more detailed error message you can check if there is a more detailed error message available which is sometimes provided during the upload of a Store. Here, you can use the default View called ‘ERRORANALYSIS’. As a result you can see additional error messages per Store which can be used to find the cause of the problem.
Available Columns in the Store List
Besides the default columns you can create your own view for your own purposes. The CCDB Administration provides many additional fields which can be chosen using the menu ‘Settings’:
Via the button ‚Store Details‘ you enable the display of a Single Store below the Store List.
In the tabstrip ‘Details’ the most important information about the Store regarding its landscape relation, upload status and content is displayed. Enabling the ‘Technical Information’ as in the screenshot below will also include the technical values and the corresponding EFWK extractor information.
For Stores which are attached directly to the landscape class host i.e. the ‘saposcol’ Store there are several extractors defined. Because of this it is valid that the extractor of such Stores changes. For all other Stores which are not directly host related, the extractor information is more or less fixed.
Important events are logged here. The most popular one is of course the Store upload itself. Subsequent Store Uploads with the same ‘Text’ and ‘Details’ are aggregated after seven days to keep to log a bit smaller. Uploads containing changes cannot be aggregated.
The first column ‘Time [CET]’ refers to the Solution Manager. If the log entry is upload related, the column ‘Time of data [CET]’ contains the corresponding timestamp of the uploaded data. This timestamp is delivered by the Managed System and is used as changed date in the CCDB.
The tabstrip ‚Content‘ outputs the Store Content. The way the data is displayed is equal to the content display of the application ‘Change Reporting’.
There are a few Stores having a Store Content protection. If you do not have CCDB Administration Change authorizations there will be a message like ‘Permission denied’.
Remark: In contrary to the Change Reporting it is not possible here to display snapshots of the past.
Here some upload Statistics are displayed. In general, this tabstrip is only required in exceptional situations. By default, the initial upload and the last seven days are kept here.
The ‘Help’ buttons provides more detailed information about the single columns.
Tabstrip ‘Template Definition’
Each Store is based on a Store Template Definition which makes sure a Store is created for a matching Technical System and its setup conditions.
Via this tabstrip it is possible to have a quick view on the Template Definition of the selected Store:
The information displayed here is only required for technical analysis.
The tabstrip is only visible for Stores allowing to define a customizing which influences the content of the Store. Since Solution Manager 7.10 ST SP05 (Feature Pack) the store group 'USER-AUTHORIZATION' contains some ConfigStores which can be customized. The most common authorization ConfigStore is called 'AUTH_PROFILE_USER' which is used here as an example.
Customizing of ConfigStore 'AUTH_PROFILE_USER':
The Store Customizing is separated into two areas, the definition section and the maintenance section.
At the definition section you can define by the drop down box called 'Store Customizing' which customizing is used by the ConfigStore. The default customizing is called '000 - SAP' which is delivered by SAP. For the most ConfigStores this delivered customizing is empty which means that the content of the Store stays initial (in this example the default customizing contains an entry).
The display and maintenance section allows you to create and edit your own customizing by the buttons 'Create..' or 'Copy..'. As soon as this is done, the customizing can be edited by the buttons 'Create' for new records, 'Edit' to switch on the edit mode and 'Delete' to remove records. Finally the customizing has to be saved.
Note: A new or changed customizing is only used by the Store if it is selected in the 'Store Customizing' dropdown box !
You can maintain different customizing versions for the Store 'AUTH_PROFILE_USER' because these customizing versions are available cross landscape wide. This allows you to reuse a customizing version for another Technical System. Finally it means that all ConfigStores 'AUTH_PROFILE_USER' share the section 'Display and Maintenance' with each other, but each Store does only use the one customizing version specified at 'Store Customizing'.
By the button 'Set as default' it is possible to define a customizing version as default for new ConfigStores that are created if a new managed system is added to the Solution Manager.
If you want to use a customizing version for all managed systems you can assign the one of 'Store Customizing' by the button 'Set for all Stores..'. Attention: There is no way to revert this setting automatically as soon as you have confirmed the popup.
There is no transport connection available for the store customizing, but since Solution Manager 7.10 ST SP05 (FeaturePack) there is an import/export functionality allowing you to transfer a customizing version from development to production.
You can find a documentation about such ConfigStores here:
In the CCDB Administration Infrastructure there is the tabstrip called ‘Cross Selection’:
The Cross Selection allows you to display a Store List independent of a Technical System selection. There are various filters available like the Landscape Class, the Software Component, Store Name and also some technical filters.
A common use case is the Store Deletion without a Technical System relation. This can be necessary if there are - for any reason - old Stores which are not valid anymore for all systems.
- In general this is an export functionality for analysis tasks
- Depending on the selection criteria the amount of Store to be displayed can be very high and therefore the runtime can timeout
- Deleting Stores here is only recommended if you are absolutely sure the Stores are not valid anymore (Reason: First step is always to make sure the extractors of a Technical Systems ran successfully. You cannot see this here !)
Using the ‘Display’ button will display the Store List as described at chapter 'The Store List' in this document.