Article ID: 120985, created on Apr 9, 2014, last review on Jun 17, 2016

  • Applies to:
  • Plesk Automation 11.1
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix
  • Plesk 11.0 for Windows

11.5 applications: psa, apsc database dependencies and descriptions of tables.

The following dumps for 'psa' and 'apsc' databases only contain records for one application. They were created in the following way: create a dump of the 'psa' and 'apsc' databases before and after application installation, then diff these dumps.

diff psa.sql_before psa.sql_after
diff apsc.sql_before apsc.sql_after

psa dump

apsc dump

psa <=> apsc dependencies scheme


apsResources, apsResourcesParameters

Contains information about all application resources:

  1. urlPrefix, isSiteRoot, phpMinVersion

  2. Information about application paths:

    • application root
    • '/blogs/media'
    • '/wp-content'
    • '/tmp'
  3. Information about databases

  4. Information about database users

apsContextsApplications, apsContexts

These two tables connect the 'Subscription' and 'domains' tables and the 'apsc.aps_registry_object' table.

smb_apsInstances, smb_apsContexts, smb_serviceInstances, smb_apsMetas, smb_serviceEntryPoints, smb_servicePermissions, smb_userServicePermissions

These tables contain information about:

  • The package from which the application was installed
  • URL links to the CMS administrative interface, blogs, upload theme and upload plugin
  • User permissions


Contains information about the package: id, name, version, release, registryUid and others.



Contains information about the application:

  • The registry_object_id of this application
  • The package_id from which this application was installed
  • package_config_id


Contains the UID for applications, packages, application resources and creation time.
The resource UID connects (3 resource records for one application):

  • psa.smb_apsInstances
  • psa.apsResources (two records with pleskType = 'hosting' and 'urlMapping')
  • psa.apsResources (two records with pleskType = 'db' and 'db_user')

aps_registry_object_setting, aps_package_resource_setting

Contains information about this application (a CMS), made up of 5 records:

  • admin_email
  • admin_name
  • admin_password
  • locale
  • title


Two records with the same value. This connects the two aps_registry_object records: aps.application with aps.resource. It is easy to find required APS resources by selecting the 3-4 lines after aps.application in the aps_registry_object table.


Contains a description of these resources:

  • wordpress
  • aps.environment
  • aps.database


Contains full information about the application package: id, registry_object_id, name, version, content_root_path, etc. =

Useful MySQL queries

Get the application_id, application_registry_object_id, package_id, package_name by the domain:

select as application_id, as application_registry_object_id, app.package_id, as package_name 
from apsc.aps_application app, apsc.aps_package pack, apsc.aps_registry_object regob  
where = app.registry_object_id and  
app.package_id = and
regob.uid = ( select conapp.registryApplicationId 
from psa.apsContextsApplications conapp, psa.apsContexts cont, dom
where and and like 'domain.tld');

Get all records that are present in the psa.smb_apsInstances but which are absent in the apsc.aps_registry_object:

select smb_apsInstances.registryResourceId from  smb_apsInstances left JOIN apsc.aps_registry_object on apsc.aps_registry_object.uid = smb_apsInstances.registryResourceId where  apsc.aps_registry_object.uid is NULL;

Search Words

dumps for 'psa' and 'apsc'

Cannot find service with id:

application error

Unable to find instance with id * in database

psa apsc dependecies


Automatic emails

database dependencies

Call to a member function getInstallationUrl() on a non-object in /usr/local/psa/admin/plib/api-common/cuAps.php


Invalid parameter number: no parameters were bound

apsc inconsistency

internal error in plesk

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f e0aff7830fa22f92062ee4db78133079 c1ecc6010feff26cb42d1d14a7881dd6 85a92ca67f2200d36506862eaa6ed6b8 514af229ae32522202a910a2649c80fb bd7fc88cf1b01f097749ae6f87272128 aea4cd7bfd353ad7a1341a257ad4724a caea8340e2d186a540518d08602aa065 e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7

Email subscription for changes to this article
Save as PDF