Server error messages 4800 - 4899 – Sybase 11.9.x-12.5 User Manual

Page 275

Advertising
background image

CHAPTER 6 Adaptive Server Error Messages

949

Server Error Messages 4800 - 4899

4716

16

Cannot truncate table `%.*s' because it is partitioned.

Explanation:

Refer to the writeup for this error.

4717

16

Could not truncate table `%.*s' because there are referential constraints defined on it and
there are data rows in some of the referencing tables.

Explanation:

Command failed due to invalid or illegal request. Check syntax,

semantics, and permissions. Take any corrective action indicated by message.

4718

17

Failed to write the TRUNCTAB log record for the execution of truncation of table '%.*s'
in database '%S_DBID'. The 'truncate table' command is aborted.

Explanation:

4719

20

TRUNCATE TABLE aborted due to an internal error. Failed to obtain the owner name
information associated with object ID %d in database '%S_DBID'. Please contact Sybase
Technical Support.

Explanation:

Adaptive Server encountered an internal error affecting the current

process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.

4720

16

Cannot truncate table '%.*s' because there are one or more isolation level 0 scans, or
REORG command, active on the table.

Explanation:

Retry your command later.

Number

Severity

Text and Explanation

Number

Severity

Text and Explanation

4801

20

Bulk_main: opentable on BULK INSERT table failed. Dbid=%d name='%.*s'.

Explanation:

The bulk copy command failed. Adaptive Server could not open the

specified table. Check command and target table.

4802

21

Bulk_main: getindex of primary index row failed on BULK INSERT table.

Explanation:

There is a potential problem affecting the consistency of the system

catalog or the indexes on the table specified in the bcp command. Investigate with dbcc
checktable, checkcatalog and checkdb.

4804

21

Premature end-of-message while reading current row from host. Host program may have
died.

Explanation:

The bcp activity could be incomplete. Although corruption is unlikely,

some rows in the target table for bcp may need to be cleaned up using delete/truncate table
command.

Advertising