Server error messages 4200 - 4299 – Sybase 11.9.x-12.5 User Manual
Page 261

CHAPTER 6 Adaptive Server Error Messages
935
Server Error Messages 4200 - 4299
4092
10
The ’enable enterprise java beans’ configuration option needs to be set
to execute this
command.
Explanation:
Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action. Take any corrective action indicated by the message.
4093
10
SSL Plus security modules loaded successfully.\n
Explanation:
This is an informational message.
4094
16
The Enterprise Java Bean feature is not supported on this platform.
Explanation:
Command failed due to invalid or illegal request. Adaptive Server cannot
perform the requested action.
Number
Severity
Text and Explanation
Number
Severity
Text and Explanation
4201
17
DUMP TRANSACTION for database `%.*s' failed: insufficient memory to allocate
backout structure.
Explanation:
Command failed due to resource limitation. Modify the command to fit
available resources, retry when the resource is available, or contact your System
Administrator to address the resource problem.
4204
17
Unable to continue logged version of DUMP TRAN. No space left in database; use
NO_LOG option or run ALTER DATABASE. Else, an old transaction may be active; see
Syslogshold table.
Explanation:
Refer to the writeup for this error.
4205
16
Syslogs does not exist in its own segment in database `%S_DBID' with segmap `%ld'
with logical start page number of `%ld'. You cannot use DUMP TRANSACTION in this
case, use DUMP DATABASE instead.
Explanation:
A database maintenance operation failed. Take any corrective action
indicated by the message. Check the Adaptive Server error log.
4206
16
You cannot run DUMP TRANsaction WITH NO_LOG inside a user transaction.
Explanation:
Command failed due to invalid or illegal request. Check syntax,
semantics, and permissions. Take any corrective action indicated by message.
4207
16
Dump transaction is not allowed because a non-logged operation was performed on the
database. Dump your database or use dump transaction with truncate_only until you can
dump your database.
Explanation:
Refer to the writeup for this error.