Database Services (DBS) messages (21100 through 21141)
SQL 21100
21100 File system error error was returned on operation request to $ZSMP.#SPI.
-
Where,
-
error is the file system error.
Cause
An unexpected file system error occurred during SPI communication with Safeguard.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 21101
21101 SPI error error was returned from operation request to $ZSMP.#SPI.
-
Where,
-
error is SPI error code.
Cause
An unexpected SPI error was returned from Safeguard.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 21102
21102 Safeguard error error was returned from operation request.
-
Where,
-
error is Safeguard error code.
Cause
An unexpected Safeguard error was returned from Safeguard.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 21103
21103 Details: details.
-
Where,
-
details is the free-form text.
Cause
Depends on the accompanying error.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 21104
21104 DBS has not been installed.
Cause
DBS has not been installed.
Effect
The operation fails.
Recovery
Run InstallDBS, and then retry the operation.
SQL 21105
21105 DBS has been installed already.
Cause
DBS has already been installed.
Effect
The operation fails.
Recovery
If the current installation is not satisfactory, run InstallDBS using the
–cleanup option, and then retry the command.
SQL 21106
21106 DBS type-of-resource, name-of-resource already exists.
-
Where,
-
type-of-resource is the type of the offending resource; for example: volume.
Cause
The resource has already been configured.
Effect
The operation fails.
Recovery
N/A.
SQL 21107
21107 attribute number must be an integer between lower-bound and higher-bound.
-
Where,
-
attribute is the name of the affected attribute; for example: CPU.
Cause
The resource attribute has a wrong value.
Effect
The operation fails.
Recovery
Correct the attribute value, and then retry.
SQL 21108
21108 The table-name metadata table must be empty.
-
Where,
-
table-name is the ANSI name of one of the DBS metadata tables.
Cause
The named table must be empty at cleanup time, but the table is not empty.
Effect
The operation fails.
Recovery
-
If table-name is ALL_DATABASES, delete all the databases from the system before cleaning up the DBS metadata.
-
For any other table name, contact your service provider.
SQL 21109
21109 DBS metadata inconsistency: explanation.
-
Where,
-
explanation is the brief description of the inconsistency.
Cause
This is an internal unexpected error.
Effect
The operation fails.
Recovery
Contact your service provider.
SQL 21113
21113 Database name database-name is not available.
Cause
You specified either an existing database name or a database name that is unavailable in the system.
Effect
The mxdbs command fails.
Recovery
Specify a different database name and retry the operation.
SQL 21114
21114 Not enough volumes are configured for DBS to accommodate the requested database size size.
-
Where,
-
size is the size requested for the database.
Cause
There are unassigned data volumes from the configured volumes for DBS but is not sufficient for the requested database size.
Effect
The command fails.
Recovery
Configure more data volumes for DBS and retry the operation.
SQL 21115
21115 There are no free data volumes available for DBS.
Cause
You specified the configured volumes for DBS that are consumed or in use by other databases on the system. There are no free data volumes available on the system.
Effect
The command fails.
Recovery
Configure DBS with additional data volumes on the system and retry the operation.
SQL 21116
21116 There are no free platform users available for DBS.
Cause
All the configured Guardian users for DBS are in use. There are no free Guardian users available on the system.
Effect
The command fails.
Recovery
Configure the system with additional Guardian users and retry the operation.
SQL 21117
21117 There are no free Safeguard file-sharing groups available for DBS.
Cause
All the configured Safeguard file-sharing groups are in use. Hence, there are no free Safeguard file-sharing group available on the system.
Effect
The command fails.
Recovery
Configure the DBS with additional Safeguard file-sharing group and retry the operation.
SQL 21119
21119 The database database-name does not exist.
-
Where,
-
database-name is the name of the database.
Cause
You specified a database name for the command that does not exist in the system.
Effect
The command fails.
Recovery
Specify the name of an existing database to the mxdbs command and retry the operation.
SQL 21120
21120 MXCS service cannot be obtained or configured for DBS.
Cause
The MXCS service for database application access cannot be obtained or configured for DBS.
Effect
The mxdbs command fails.
Recovery
Contact your service provider.
SQL 21121
21121 Port range configured for MXCS service service-name is in use.
-
Where,
-
service-name is the MXCS service name configured for database application access.
Cause
The MXCS service configured for DBS is not running.
Effect
The mxdbs command fails.
Recovery
Contact your service provider.
SQL 21122
21122 The MXCS service process-name configured for DBS is not running.
-
Where,
-
process-name is the name of the MXCS service process configured for DBS application access.
Cause
The configured MXCS service for DBS is not running.
Effect
The command fails.
Recovery
Start the service manually by using the following command from TACL, scf start generic-process-name.
-
Where,
-
generic-process-name is the name of the service configured for DBS application access.
SQL 21123
21123 User user-name already exists in the database database-name.
-
Where,
-
database-name is the name of the database.
-
user-name is the name of the user to be added to the database.
Cause
You specified an existing user in the database.
Effect
The command fails
Recovery
Specify an external user that is not associated with the database to the mxdbs command and retry the operation.
SQL 21124
21124 External username or password specified is incorrect.
Cause
You specified an invalid external user name or old password.
Effect
The command fails.
Recovery
Specify a valid external username or old password to the mxdbs command and retry the operation.
SQL 21125
21125 User user-name is not associated with database database-name.
-
Where,
-
database-name is the name of the database.
-
user-name is the external name of the user.
Cause
You specified an external user that does not belong to the database.
Effect
The command fails.
Recovery
Specify an external user that is existing in the database to the mxdbs command and retry the operation.
SQL 21126
21126 User user-name cannot be removed from the database database-name.
-
Where,
-
database-name is the name of the database.
-
user-name is the external name of the user to be removed from the database.
Cause
-
You specified an external username who is the only user with CREATE access level in the database.
-
The user owns a schema in the database.
Effect
The command fails.
Recovery
-
If the user to be removed is the only user with CREATE access level in the database, add another user to the database with CREATE access level and retry the operation.
-
If the user needs to remove own schemas in the database, the schemas must be dropped before attempting to remove the user from the database.
SQL 21127
21127 The name value is invalid.
-
Where,
-
name is either database name or external user name.
-
value is the value passed to the database_name or external_username command-line arguments in the mxdbs commands.
Cause
You specified a value to the mxdbs arguments that contains blank spaces or has characters more than the maximum allowed length.
Effect
The command fails.
Recovery
Specify a value to the mxdbs arguments without blank spaces or within the maximum allowed limits on the arguments and retry the operation.
SQL 21128
21128 The password is invalid.
Cause
You specified a value to the password in the mxdbs command that contains blank spaces or has characters more than the maximum allowed length.
Effect
The command fails.
Recovery
Specify a valid password and retry the operation.
SQL 21129
21129 The access level for user-name cannot be changed for database database-name.
-
Where,
-
database-name is the name of the database to which the user is associated.
-
user-name is the external name of the user whose access level to the database is to be changed.
Cause
There must be at least on user in the database with create access-level.
Effect
The command fails.
Recovery
Add another external user to the database with create access level and retry the operation.
SQL 21130
21130 User user-name already has the access level access-level in database database-name.
-
Where,
-
external-user is the name of the external user whose access level to the database is to be changed.
-
access-level is the access level requested for the database user.
-
database-name is the name of the database to which the user belongs.
Cause
You specified a user who already has the requested access level in the database.
Effect
The command fails.
Recovery
Retry the operation with another access level.
SQL 21131
21131 One or more MACL error(s) occurred during the DBS operation.
Cause
An error occurred while performing implicit MXCS operations.
Effect
The command fails.
Recovery
See the accompanying errors returned by the mxdbs command. Retry the mxdbs command after rectifying them. If problem persists, contact your service provider.
See “Contacting your service provider” (page 12).
SQL 21132
21132 Error error was returned by function.
-
Where,
-
error is the error number returned by the system call function.
-
function is the system call that returned the error.
Cause
An error is returned by the system call function.
Effect
The command fails.
Recovery
None. Contact your service provider.
See “Contacting your service provider” (page 12).
SQL 21133
21133 schema-name cannot be initial schema of the database.
-
Where,
-
schema-name is either INFORMATION_SCHEMA or name with DEFINITION_SCHEMA_VERSION_ prefix.
Cause
You specified either INFORMATION_SCHEMA or name with DEFINITION_SCHEMA_VERSION_ as prefix is specified as initial schema to the db-create command.
Effect
The command fails.
Recovery
Specify a different schema name to the schema-name argument and retry the operation.
SQL 21134
21134 OSS root directory dir-name configured for DBS does not exist.
-
Where,
-
dir-name is an OSS root directory configured for DBS.
Cause
OSS root directory configured for DBS does not exist.
Effect
The command fails.
Recovery
Check if the OSS root directory configured for DBS exists. If it does not exist, create the directory as SUPER user and then retry the operation. If problem persists, contact your service provider.
SQL 21135
21135 OSS directory dir-name for the database database-name already exists.
-
Where,
-
dir-name is OSS directory to be created for the database.
-
database-name is name of the database to be created.
Cause
OSS directory to be created for the database exists.
Effect
The command fails.
Recovery
Remove the OSS directory and retry the operation.
SQL 21136
21136 Database database-name has privileges granted to one or more grantee of other databases.
-
Where,
-
database-name is name of a database.
-
grantee is either users or privilege groups.
Cause
You are attempting to unshare a database but one or more users/privilege groups of other databases have been granted privileges on objects in the shared database.
Effect
The operation fails.
Recovery
Revoke all the privileges granted to the users/privilege groups of other database before unsharing the database.
SQL 21137
21137 User user-name has privileges on the database objects granted explicitly by other users of the database database-name.
-
Where,
-
user-name is the external name of the user.
-
database-name is name of a database.
Cause
There are privileges granted to the user by other users of the database.
Effect
The operation fails.
Recovery
Before removing the user from the database, revoke all explicitly granted privileges from the user and retry the mxdbs operation.
SQL 21138
21138 One or more errors occurred when recovering a previously failed MXDBS operation.
Cause
One or more SQL errors occurred while performing implicit recovery of a previously failed mxdbs operation.
Effect
The mxdbs operation fails.
Recovery
Correct the errors reported in the accompanying SQL errors. If problem persists, contact your service provider.
SQL 21140
21140 OSS directory oss-path of database database-name does not exist.
-
Where,
-
oss-path is OSS directory path for the database.
-
database-name is name of the database specified in the operation.
Cause
The OSS directory for the database does not exist.
Effect
The mxdbs operation fails.
Recovery
None.
SQL 21141
21141 Database database-name is already shared-option.
-
Where,
-
database-name is name of the database specified in the operation.
-
shared-option is either shared or unshared.
Cause
The database is either already shared or unshared and you are attempting to share or unshare it again.
Effect
The mxdbs operation fails.
Recovery
None.