16
There is already an object named '%.*s' in the database.
This error occurs when Adaptive Server tries to create an object that already exists.
Error 2714 can occur:
When you are creating procedures, triggers, tables, views, or rules, if you specify an object that already exists.
If you changed the sort order to be case-insensitive, then tried to create an object that is spelled the same way as an existing object with a different case (for example, PROC1 and proc1).
When using temporary tables:
Version pre-15.0, the first 13 bytes of the table name, including the pound sign, must be unique for the current session. Long temporary table names are truncated to 13 characters with the pound sign.
Versions 15.0 and later, if you create a temporary table with a name requiring fewer than 238 bytes, Adaptive Server adds a 17-byte suffix to ensure that table name is unique. If you create a temporary table with a name of more than 238 bytes, Adaptive Server uses only the first 238 bytes (including pound sign), then adds the 17-byte suffix.
An attempt to create a second temporary table with the same name in the same session will raise error 2714. (In contrast, temporary tables created by specifying database_name.owner.table_name may be shared among sessions, not only within one session.)
Make sure the name of the object you are trying to create does not already exist.
If you have stored procedures that create objects, make sure there is a check for the existence of the object in the stored procedure (before it is created). If you want to re-create an object within a stored procedure, drop the object before you re-create it.
Refer to the Reference Manual: Commands for information about creating and dropping objects.
All versions
