Ansicht
Dokumentation

SQL0478 - Object &1 of type &3 cannot be dropped or altered. ( OS/400 )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.


Message : SQL0478
Object &1 of type &3 cannot be dropped or altered.

Message Long Text :

Cause . . . . . : The base object &1 in schema &2 cannot be dropped or altered because another object depends on it. The dependent object &4 in &5 is of type &6.
-- If base object type is *N, the object being dropped or altered is a function or a procedure. For other objects it may be that the dependency is indirect. That is, the named object is dependent on another object which is dependent on the object being dropped or altered.
-- If the base object is a function, the dependent object is sourced on the base object, or is a view, a materialized query table, or an SQL procedure, function, global variable, or trigger that references the function.
-- If the base object is a procedure, the dependent object is referenced in an SQL procedure, function, or trigger.
-- If the base object is a table and if there are other tables with triggers or foreign key constraints dependent on the base table, then the RESTRICT clause of the DROP statement will prevent the base table from being dropped.
-- If the base object is *LIB and if there are tables, views, functions, procedures, distinct types, aliases, global variables, or triggers in the schema, then the RESTRICT clause of the DROP statement will prevent the schema from being dropped. A trigger can be defined in one schema on a table that exists in a different schema.
-- If the base object is *SQLUDT and if there are tables, views, indexes, functions, procedures, sequences, global variables, or triggers dependent on the distinct type, then the RESTRICT clause of the DROP statement will prevent the base distinct type from being dropped.
-- If the base object is *DTAARA and if there are SQL routines, global variables, or triggers dependent on the sequence, then the RESTRICT clause of the DROP statement will prevent the base sequence from being dropped.
-- If the base object is *SRVPGM and if there are views, SQL routines, global variables, or triggers dependent on the global variable, then the RESTRICT clause of the DROP statement will prevent the base global variable from being dropped.
Recovery . . . : Drop the dependent objects first. Try the request again.

Message File : QSQLMSG
Library Message File : QSYS2924


CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by IBM.

Length: 3248 Date: 20240426 Time: 044815     sap01-206 ( 2 ms )