79 PRCD-01000 to PRCD-01133

PRCD-01000: Database {0} already exists: Cause: The specified database resource was already registered in Oracle Clusterware.; Action: No action is needed.

PRCD-01001: Database {0} does not exist: Cause: The specified database resource was not registered in Oracle Clusterware.; Action: Register the database resource using 'srvctl add database'.

PRCD-01002: Database {0} is dependent upon server pool {1}: Cause: An attempt to remove the specified server pool failed because the server pool is in use.; Action: Remove the specified database before removing the server pool.

PRCD-01003: Service {0} already exists: Cause: The specified service was already created and registered in Oracle Clusterware.; Action: No action is needed.

PRCD-01004: Service {0} is dependent upon server pool {1}: Cause: An attempt to remove the specified server pool failed because the server pool is in use.; Action: Remove the specified service before removing the server pool.

PRCD-01005: Server pool {0} for the database {1} does not exist: Cause: The specified server pool used by the database was removed by force.; Action: Create the server pool using 'srvctl create srvpool'.

PRCD-01007: Failed to retrieve the database name: Cause: Failed in retrieving the DB_NAME resource attribute.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.

PRCD-01008: Server parameter file does not exist for database {0}: Cause: Failed in retrieving the SPFILE resource attribute.; Action: Review the accompanying error messages for details about the failure. Retry after resolving those issues.

PRCD-01009: Failed to retrieve server parameter file of database {0}: Cause: Cannot retrieve the server parameter file for the specified database.; Action: Retry the request after ensuring that the CRS stack is running, the database resource has been configured, and the user has read permission on the database resource.

PRCD-01010: Failed to update server parameter file {0} of database {1}: Cause: Unable to update the server parameter file for the specified database.; Action: Retry the request after ensuring that the CRS stack is running, the database resource has been configured, and the user has update permission on the database resource.

PRCD-01011: Failed to identify whether this database {0} is a multi-instance database: Cause: Failed in retrieving the CLUSTER_DATABASE resource attribute.; Action: Examine the accompanying error messages for details.

PRCD-01012: Failed to retrieve disk group list for database {0}.: Cause: Failed to retrieve the diskgroups from the start dependencies of the specified database.; Action: Examine the accompanying error messages for details. Create the diskgroup using sqlplus if the specified diskgroup does not exist. Mount the diskgroup in database which registers the diskgroup with Oracle Clusterware.

PRCD-01014: Failed to retrieve database domain of database {0}: Cause: Failed to get the domain of the specified database from its USR_ORA_DOMAIN attribute.; Action: Examine the accompanying error messages for details.

PRCD-01015: Combination of service cardinality {0} and TAF {1} is not allowed for service {2}: Cause: The specified service cardinality can not be used with the specified TAF policy.; Action: Change the cardinality or find a matching TAF policy. PRECONNECT can only be used with SINGLETON cardinality.

PRCD-01016: Failure encountered while accessing server pool {0} for database {1}: Cause: An attempt to look up the server pools referenced by the database SERVER_POOLS attribute failed.; Action: Examine the accompanying error messages for details.

PRCD-01019: Failed to retrieve Oracle home of database {0}: Cause: An attempt to retrieve the TAF_POLICY attribute of the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01020: Failed to retrieve TAF policy for service {0}: Cause: An attempt to retrieve the ORACLE_HOME attribute of the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01021: Failed to update TAF policy {0} for service {1}: Cause: An attempt to set the TAF_POLICY attribute of the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01022: Cannot add a second instance to a single instance database: Cause: Unable to add an instance to a single instance database.; Action: Multiple instances are not supported for a single instance database. Convert to a RAC database if multiple instances are desired.

PRCD-01023: An Instance has already been added to node {0} for database {1}.: Cause: Unable to add an instance to the database on the specified node because another instance has already been added to the node.; Action: Use srvctl modify instance command to change the instance name on the specified node.

PRCD-01024: Failed to retrieve instance list for database {0}: Cause: An attempt to get the list of the instances for the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01025: Failed to create database {0}: Cause: An attempt to create Clusterware resources for the specified database failed. Either the request was issued by the wrong OS userid or a problem was detected inside Oracle Clusterware.; Action: Examine the accompanying error messages for details. Login in as the user of the Oracle Home to issue the command 'srvctl add database'.

PRCD-01026: Failed to create service {0} for database {1}: Cause: An attempt to create the specified service failed because the command 'srvctl add service' was not issued by the Oracle Home owner.; Action: Examine the accompanying error messages for details. Login in as the user of the Oracle Home to issue the command 'srvctl add service'.

PRCD-01027: Failed to retrieve database {0}: Cause: An attempt to get the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01028: Failed to retrieve service resource {0} for database {1}: Cause: An attempt to get the specified service failed.; Action: Examine the accompanying error messages for details.

PRCD-01029: Disk group {0} for database {1} does not exist: Cause: The disk group for the specified database does not exist.; Action: Use 'srvctl add diskgroup' to add the specified disk group.

PRCD-01030: Failed to determine whether the database {0} has cardinality: Cause: Failed to determine whether the specified database is cardinality based or not based on its VERSION attribute.; Action: Examine the accompanying error messages for details.

PRCD-01031: Failed to determine whether the service {0} has cardinality: Cause: Failed to check whether the specified service is cardinality based or not.; Action: Examine the accompanying error messages for details.

PRCD-01032: Failed to remove database resource {0}: Cause: Failed to remove the specified database.; Action: Examine the accompanying error messages for details.

PRCD-01033: The server pool of service {0} is different from the server pool of database {1}: Cause: The specified server pool is not the child of the database's server pool.; Action: Use a server pool which is the child of the database's server pool.

PRCD-01034: {0} is the database unique name of a cluster database, not a single instance database: Cause: The specified database is not a single instance database.; Action: Provide a database name for a single instance database.

PRCD-01035: {0} is the database unique name of a single instance database, not a cluster database: Cause: The specified database is not a cluster database.; Action: Provide a database name for a RAC database.

PRCD-01036: Failed to set Oracle home {0} for database {1}: Cause: An attempt to update Oracle home for the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01037: Failed to set Oracle home {0} for database {1} on node {2}: Cause: An attempt to update Oracle home for the specified database on the specified node failed.; Action: Examine the accompanying error messages for details.

PRCD-01038: Cannot create a RAC database {0} in a non cluster environment: Cause: Failed to create the specified RAC database because Oracle Clusterware is not installed and configured.; Action: Install and configure Oracle Clusterware before creating the RAC database.

PRCD-01039: Failed to retrieve database for service {0}: Cause: An attempt to get the database that the specified service depended on failed. This is an internal error.; Action: Contact Oracle Support Services.

PRCD-01040: Specified server pool {0} for {1} is already hosting an administrator-managed configuration for databases {2} and services {3}: Cause: Server pool is hosting administrator-managed databases and service.; Action: Specify a server pool that is not hosting an administrator-managed database and service.

PRCD-01041: The administrator-managed database {1} can have only one server pool {0}: Cause: Multiple server pools cannot be configured for an administrator-managed database; Action: Contact Oracle Support.

PRCD-01042: The database {1} is administrator-managed and a policy-managed service {0} cannot be created on it.: Cause: The specified database does not support policy-managed services.; Action: Provide a database which supports policy-managed services.

PRCD-01043: The service {0} is not a uniform or a singleton service and therefore it cannot be created as policy-managed service. This service can only be created as administrator-managed service using preferred, and optionally available instance lists.: Cause: The service to be created was an administrator-managed service and the database that the service depended on was a policy-managed database.; Action: Use perferred and available instance lists to create an adminstrator-managed service for an adminstrator-managed database.

PRCD-01044: Failed to retrieve the list of nodes where instances have been configured for database {0}: Cause: An attempt failed to get the list of nodes where the instances of the specified database were configured.; Action: Examine the accompanying error messages for details.

PRCD-01045: Database {0} is policy managed and does not support add instance option: Cause: The specified database does not support add instance option; Action: 1) Provide an administrator-managed database. -or- 2) For policy-managed database, add a server to a server pool which manages the database using 'srvctl modify srvpool' or 'srvctl relocate server'.

PRCD-01046: Database {0} is policy managed and does not support the remove instance option: Cause: The specified database does not support the remove instance option.; Action: 1) Provide an administrator-managed database. -or- 2) For policy-managed database, stop the database on a server and then remove that server from the server pool which manages the database using 'srvctl modify srvpool' or 'srvctl relocate server'.

PRCD-01047: Failed to retrieve list of services for database {0}: Cause: An attempt to get the list of services for the specified database failed.; Action: Examine the accompanying error messages for details.

PRCD-01048: Cannot remove instance from the single instance database {0}: Cause: An attempt to remove the instance from the single instance database failed.; Action: Remove the database using 'srvctl remove database'.

PRCD-01049: Failed to update server pool {0} for database {1}: Cause: An attempt to update the specified server pool failed.; Action: Examine the accompanying error messages for details.

PRCD-01050: Failed to update auto start value of service {0}: Cause: An attempt to update the auto start value for the specified service failed.; Action: Examine the accompanying error messages for details.

PRCD-01051: Failed to add instance to database {0}: Cause: An attempt to add an instance to the specified database failed because the node of the instance is not a node of the cluster or other errors.; Action: Examine the accompanying error messages for details.

PRCD-01052: Failed to remove instance from database {0}: Cause: An attempt to remove the specified instance failed because the services depended on the instance or other errors.; Action: Examine the accompanying error messages for details.

PRCD-01053: Failed to retrieve the database instances providing service {0}: Cause: An attempt to get the database instances that provide the specified service failed.; Action: Examine the accompanying error messages for details.

PRCD-01054: Database name is null: Cause: The database name given by the user is null.; Action: Provide a valid database name that is not a null string.

PRCD-01055: Instance name is null: Cause: The instance name given by the user is null.; Action: Provide a valid instance name that is not a null string.

PRCD-01056: Database name {0} contains invalid characters: Cause: The supplied database name contains invalid characters.; Action: Supply a valid database name. The valid character set for database name is [a-zA-Z0-9$#_].

PRCD-01057: Instance name {0} is not valid: Cause: The supplied instance name is not of the correct format.; Action: Supplied a valid instance name. The valid character set for instance name is [a-zA-Z0-9_-].

PRCD-01058: Invalid server pool list {0} supplied for single instance database {1}: Cause: The server pool size was not one when creating a single instance database on a cluster.; Action: Use one server pool with only one server when creating the single instance database.

PRCD-01060: Server pool has not been supplied for creating cluster service {0} for database {1}: Cause: No server pool argument has been supplied when configuring a cluster database.; Action: Supply an existing server pool when configuring a cluster database.

PRCD-01061: No database exists: Cause: No database has been configured.; Action: Configured database and retry.

PRCD-01062: Invalid service cardinality {0}: Cause: The service cardinality supplied is not valid.; Action: Supply a valid service cardinality.

PRCD-01063: Invalid service taf policy {0}: Cause: The service taf policy supplied is not valid.; Action: Supply a valid service taf policy.

PRCD-01064: Invalid database role {0}: Cause: The database role supplied is not valid.; Action: Supply a valid database role.

PRCD-01065: Invalid managment policy {0}: Cause: The management policy supplied is not valid.; Action: Supply a valid management policy. The management policy should be automatic or manual.

PRCD-01066: Invalid start option {0}: Cause: The start option supplied is not valid.; Action: Supply a valid start option.

PRCD-01067: Invalid stop option {0}: Cause: The stop option supplied is not valid.; Action: Supply a valid stop option.

PRCD-01068: Failed to modify instance {0} on node {1} for database {2}: Cause: The instance for the specified node does not exist on the database.; Action: Use srvctl add instance to add the per-X instance.

PRCD-01069: Failed to modify instance {0} on node {1} for database {2}: Cause: The instance for the specified node cannot not be updated.; Action: Make sure that the crs stack is up and running; the oracle user has the permission to modify the instance; and then retry.

PRCD-01070: Failed to retrieve startup options for database {0}: Cause: Unable to retrieve the startup options for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01071: Failed to update startup options for database {0}: Cause: Unable to update the startup options for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01072: Failed to retrieve stop options for database {0}: Cause: Unable to retrieve the stop options for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01073: Failed to update stop options for database {0}: Cause: Unable to update the stop options for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01074: Failed to retrieve the database role for database {0}: Cause: Unable to retrieve the database role for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01075: Failed to set the database role {1} for database {0}: Cause: Unable to update the database role for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01076: Failed to retrieve the management policy for database {0}: Cause: Unable to retrieve the management policy for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01077: Failed to update the management policy for database {0}: Cause: Unable to update the managment policy for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01078: Failed to update the db name {0} of database {1}: Cause: Unable to update the db name for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01079: Failed to update pullup for service {0}: {1}: Cause: Failed to update pullup modifier for the service.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01080: Failed to get attributes for service {0}: Cause: Failed to get attributes for the service.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01081: Failed to set attributes for service {0}: Cause: Failed to set attributes for the service.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01082: Failed to modify service {0}: Unsupported attribute {1}: Cause: Operation doesn't support modification of attribute.; Action: Fix your application.

PRCD-01083: Failed to modify service {0}: Cause: Failed to modify service.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01084: Failed to start service {0}: Cause: Failed to start the service.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01085: Failed to stop service {0}: Cause: Failed to stop the service.; Action: Make sure that the crs stack is up, the service is running and then retry.

PRCD-01086: Invalid rlb goal {0}: Cause: The rlb goal supplied is not valid.; Action: Supply a valid rlb goal.

PRCD-01087: Invalid failover type {0}: Cause: The failover type supplied is not valid.; Action: Supply a valid failover type.

PRCD-01088: Invalid connection load balancing goal {0}: Cause: The clb goal supplied is not valid.; Action: Supply a valid clb goal.

PRCD-01089: Invalid failover method {0}: Cause: The failover method supplied is not valid.; Action: Supply a valid failover method.

PRCD-01090: Failed to retrieve Oracle home of database {0} on node {1}: Cause: No Oracle home of the database has been set on the specified node.; Action: Set the Oracle home of the database on the specified node.

PRCD-01091: Failed to create database instance {0} for database {1}: Cause: Unable to create database instance for the specified instance name.; Action: Make sure that the local node can be used for creating a database instance; the instance name provided is valid. The valid character set for instance name is [a-zA-Z0-9_-].

PRCD-01092: Failed to create database instance {0} for database {1} on node {2}: Cause: Unable to create database instance for the specified instance name and node name.; Action: Make sure that the specified node can be used to create a database; the instance name provided is valid. The valid character set for instance name is [a-zA-Z0-9_-].

PRCD-01093: Failed to update the domain {0} of database {1}: Cause: Unable to update the domain for the database.; Action: Make sure that the crs stack is up and running and then retry.

PRCD-01094: Failed to create start dependency for database {0} on the asm filesystem where oracle home {1} is residing: Cause: Unable to modify the database resource to include a start dependency on the ASM filesystem for the database's Oracle home.; Action: Make sure that the asm instance is running; the OFS driver exists in the driver directory and the underlying ofs devices are accessible.

PRCD-01095: Failed to retrieve databases for version 11.1 and earlier: Cause: Unable to read OCR configuration to get databases for version 11.1 and earlier; Action: Make sure that the Oracle clusterware is up and running and the primary group of the user running srvctl is the same as the primary group of the user who installed the Oracle clusterware home. Also, run 11.1 srvctl config to verify that the database configuration exists in OCR.

PRCD-01096: Failed to retrieve the database unique name: Cause: Unable to read the attribute value for database unique name.; Action: Make sure that the Oracle clusterware is up and running and then retry.

PRCD-01097: Failed to retrieve the active servers of server pool {0} for database {1}: Cause: Unable to read the active servers attribute value for the database underlying server pools.; Action: Make sure that the Oracle clusterware is up and running; the database underlying server pools exist; the user has the permission to access the database underlying server pools and then retry.

PRCD-01098: Failed to retrieve the configured servers of server pool {0} for database {1}: Cause: Unable to read the servers attribute value for the database underlying server pool.; Action: Make sure that the Oracle clusterware is up and running; the database underlying server pool exists and then retry.

PRCD-01099: {0} enum member has a constant value that cannot be changed to given value {1}: Cause: An attempt was made to change value of read-only valued enum member.; Action: Contact Oracle Support Services.

PRCD-01100: Invalid relocate option {0}: Cause: Supplied relocate option is unknown.; Action: Contact Oracle Support Services.

PRCD-01101: Failed to remove running instance {0} for database {1}: Cause: Unable to remove the instance configuration for the database because the instance was still running.; Action: Stop the running instance using srvctl stop instance command and then retry.

PRCD-01102: Failed to create preconnect service for service {0}: Cause: An attempt to register service failed due to failure to register its corresponding preconnect service.; Action: Contact Oracle Support Services.

PRCD-01103: Failed to retrieve the maximum cardinality for database {0}: Cause: Unable to query the number of servers in the server pool used to manage the database.; Action: Make sure that the Oracle clusterware is up and running; the database underlying server pool exists and then retry.

PRCD-01104: A source server must be specified to relocate cluster database {0}: Cause: Cluster database cannot be relocated without specifying source server to relocate instance from.; Action: Supply source and target servers for database relocation.

PRCD-01105: A source server must be specified to relocate service {0}: Cause: Cluster database service cannot be relocated without specifying source server to relocate service member from.; Action: Supply source and target servers for service relocation.

PRCD-01106: Failed remove service {0}: could not get data for its underlying server pool: Cause: Server pool data is not found.; Action: Make sure that the Oracle clusterware is up and running; the service underlying server pool exists.

PRCD-01107: Removed service {0} but failed to remove its underlying server pool {1}: Cause: Failed to remove the server pool.; Action: Make sure that the Oracle clusterware is running and remove the server pool manually.

PRCD-01108: Failed to identify whether database {0} is an administrator-managed database: Cause: Failed to get database attributes.; Action: Make sure that the Oracle clusterware is up and running; the database exists.

PRCD-01109: Failed to find administrator-managed service {0} of database {1} because the database is a policy-managed database.: Cause: The database does not support administrator-managed services.; Action: Provide an administrator-managed database and make sure that the service exists within that database.

PRCD-01110: Database {0} does not have instances {1}: Cause: The database does not have instances mentioned in the message.; Action: Make sure that database name is correct and the database has requested instances.

PRCD-01111: The type of service cardinality for this operation should be {1}, not {0}: Cause: This is an internal error.; Action: Contact Oracle Support Services.

PRCD-01112: Failed to get preferred instances of service {0}: Cause: The service does not exist or the Oracle clusterware is down.; Action: Make sure that the Oracle clusterware is up and running and the service exists.

PRCD-01113: Failed to modify service {0}: Cause: The service does not exist or the Oracle clusterware is down.; Action: Make sure that the Oracle clusterware is up and running and the service exists.

PRCD-01114: Failed to enable service {0} on one or more instances: Cause: The service does not exist or enabled on all database instances. The Oracle clusterware is down.; Action: make sure that the Oracle clusterware is up and running; the service exists and disabled on at least one database instance.

PRCD-01115: Failed to disable service {0} on one or more instances: Cause: The service does not exist or disabled on all database instances. The Oracle clusterware is down.; Action: Make sure that the Oracle clusterware is up and running; the service exists and enabled on at least one database instance.

PRCD-01116: Failed to get available instances of service {0}: Cause: The service does not exist or the Oracle clusterware is down.; Action: Make sure that the Oracle clusterware is up and running and the service exists.

PRCD-01117: Failed to modify service {0}, the service should have at least one preferred instance: Cause: An attempt was made to remove all preferred instances of the service.; Action: Make sure that there is at least one instance provided in the service preferred instance list.

PRCD-01118: Failed to set service {0} to {1} because it runs on more than one node: Cause: The service was running on more than one node.; Action: Make sure that the service is not running or running on one node only.

PRCD-01119: Failed to create database {0} because the database unique name matches that of database {1} in the first 8 characters: Cause: The database unique name is not unique in the first 8 characters. It is a requirement because the name is used to generate ORACLE_SID.; Action: Ensure that the name supplied to either DBCA or srvctl during database creation is sufficiently unique, and retry the command.

PRCD-01120: The resource for database {0} could not be found.: Cause: The resource for the specified database name could not be found. Either the database name was misspelled or the database has not been created.; Action: Correct the database name spelling or use the 'srvctl add database' command to create the database configuration.

PRCD-01121: Specified server pool {0} for {1} is already hosting an administrator-managed configuration for database(s) {2}: Cause: Server pool is hosting administrator-managed databases.; Action: Specify a server pool that is not hosting an administrator-managed database.

PRCD-01122: Specified server pool {0} for {1} is already hosting an administrator-managed configuration for service(s) {2}: Cause: Server pool is hosting administrator-managed services.; Action: Specify a server pool that is not hosting an administrator-managed service.

PRCD-01123: Oracle Clusterware resource does not exist for ACFS filesystem of volume device {0}. A filesystem resource is required for the filesystem containing Oracle home {1}.: Cause: ACFS filesystem resource does not exist for the database which has its Oracle home stored on an ACFS filesystem. An ACFS filesystem resource is required for database homes on ACFS filesystems so that Oracle Clusterware can track the database's dependency on the filesystem. Database homes cannot be mounted via the ACFS registry.; Action: Add the ACFS filesystem resource with 'srvctl add filesystem'.

PRCD-01124: Failed to stop database {0} and its services: Cause: Attempt to stop the database has failed.; Action: Ensure that user attempting to stop the database has execute privileges on the database resource. Also, review the accompanying error messages for details about failure to stop database. Retry after resolving those issues or contact Oracle Support Services.

PRCD-01125: Failed to create dependency from database {0} to its Oracle home {1} that is located on the ASM cluster filesystem: Cause: An attempt to modify the database resource to include a stop dependency on the ASM cluster filesystem for the database's Oracle home failed.; Action: Make sure that the asm instance is running; the ACFS driver exists in the driver directory and the underlying ACFS devices are accessible.

PRCD-01126: Instance {0} cannot be removed because it is the only preferred instance for service(s) {1} for database {2}: Cause: An attempt was made to remove the instance which is the only preferred instance for specified services.; Action: Make sure that specified services have more than one preferred instance or modify services to not have the instance as a preferred instance.

PRCD-01127: Failed to verify if instance {0} is the only preferred instance for any service: Cause: An attempt to verify if the instance is the only preferred instance for any service failed.; Action: Make sure that the Oracle clusterware is up and running. Also, review the accompanying error messages for details about failure. Retry after resolving those issues.

PRCD-01128: Failed to remove all services configured for database {0}: Cause: An attempt to remove all services configured for database.; Action: Review the accompanying error messages for details about failure. Retry after resolving those issues.

PRCD-01129: Failed to start instance {0} for database {1}: Cause: An attempt to start an instance with the specified name failed.; Action: Review the accompanying error messages for details about failure. Retry after resolving those issues.

PRCD-01130: Failed to convert administrator-managed database {0} into a policy-managed database to use server pool {1}: Cause: An attempt to convert the database from an administrator-managed configuration to a policy-managed configuration failed.; Action: Review the accompanying error messages for details about failure. Retry after resolving those issues.

PRCD-01131: Failed to stop database {0} and its services on node(s) {1}: Cause: Attempt to stop the database on given nodes has failed.; Action: Ensure that user attempting to stop the database has execute privileges on the database resource. Also, review the accompanying error messages for details about failure to stop database. Retry after resolving those issues or contact Oracle Support Services.

PRCD-01132: Database {0} doesn't have defined service(s) {1}: Cause: An attempt to start/stop services on the given database failed.; Action: Make sure that every service you want to start or stop is configured for the given database.

PRCD-01133: Failed to start services for database {0}: Cause: An attempt to start given services on the given database failed because those service(s) are not configured for the database.; Action: Review the accompanying error messages for details about failure. Retry after resolving those issues.