Ansicht
Dokumentation

SQL7008 - &1 in &2 not valid for operation. ( OS/400 )

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


Message : SQL7008
&1 in &2 not valid for operation.

Message Long Text :

Cause . . . . . : The reason code is &3. Reason codes are:
1 -- &1 has no members.
2 -- &1 has been saved with storage free.
3 -- &1 not journaled, no authority to the journal, or the journal state is *STANDBY. Files with an RI constraint action of CASCADE, SET NULL, or SET DEFAULT must be journaled to the same journal.
4 and 5 -- &1 is in or being created into production library but the user has debug mode UPDPROD(*NO).
6 -- Schema being created, but user in debug mode with UPDPROD(*NO).
7 -- A based-on table used in creation of a view is not valid. Either the table is program described table or it is in a temporary schema.
8 -- Based-on table resides in a different ASP than ASP of object being created.
9 -- Index is currently held or is not valid.
10 -- A constraint or trigger is being added to an invalid type of table, or the maximum number of triggers has been reached, or all nodes of the distributed table are not at the same release level.
11 -- Distributed table is being created in schema QTEMP, or a view is being created over more than one distributed table.
12 -- Table could not be created in QTEMP, QSYS, QSYS2, or SYSIBM because it contains a column of type DATALINK having the FILE LINK CONTROL option.
13 -- The table contains a DATALINK, LOB, or XML column that conflicts with the data dictionary.
14 -- A DATALINK, LOB, XML, or IDENTITY column cannot be added to a non SQL table.
15 -- Attempted to create or change an object using a commitment definition in a different ASP.
16 -- Sequence &1 in &2 was incorrectly modified with a CL command.
17 -- The table is not usable because it contains partial transactions.
Recovery . . . : Do one of the following based on the reason code:
1 -- Add a member to &1 (ADDPFM).
2 -- Restore &1 (RSTOBJ).
3 -- Start journaling on &1 (STRJRNPF), get access to the journal, or change the journal state to *ACTIVE (CHGJRN).
4, 5, or 6 -- Perform a CHGDBG command with UPDPROD(*YES).
7 -- Remove table names which identify files in QTEMP or program described files.
8 -- Use tables in the same ASP.
9 -- Use the EDTRBDAP command to change the sequence of the access path from HELD to 1-99 or *OPN, or rebuild or delete the unique index or constraint.
10 -- Specify tables that are valid for constraints or triggers.
11 -- Specify a schema other than QTEMP, or create the view over only one distributed table.
12 -- Specify a schema other than QTEMP, QSYS, QSYS2, or SYSIBM.
13 -- Specify a schema that does not contain a data dictionary or remove all DATALINK, LOB, and XML columns.
14 -- Specify an SQL table.
15 -- Specify an object in the same ASP as the current commitment definition or end the current commitment definition.
16 -- Specify a different sequence, or delete the data area associated with sequence &1 in &2 and recreate the sequence.
17 -- See previous message in the job log.

Message File : QSQLMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.

Length: 3277 Date: 20240420 Time: 060129     sap01-206 ( 3 ms )