Aquí tienes un buscador de mensajes
de error del sql:
http://publib.boulder.ibm.com/iseries/v5r2/ic2931/index.htm?info/rzala/rzalafinder.htm
Le pones como error el SQL7008 y te
dirá de que se queja.
De todos modos te adjunto lo que dice
el buscador:
|
SQL7008
|
| Message Text:
| &1 in &2 not valid for operation.
|
| Cause Text:
| The reason code is &3. Reason codes and their meanings
are:
- 1 -- &1 has no members.
- 2 -- &1 has been saved with storage free.
- 3 -- &1 not journaled, or no authority to the journal.
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 -- Collection 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
library.
- 8 -- A user attempted to create an object. The based-on
table resides in an ASP which is different than the ASP of the object.
- 9 -- Index is currently held or is not valid.
- 10 -- A constraint or trigger is being added to a table
that is not valid. The table is in QTEMP, has ASP's that are not the same,
or is not an externally described file, or is not write, update, or delete
capable. For a constraint, the table is a source file or the parent does
not have a member. For a trigger, maximum number of triggers reached.
- 11 -- Distributed table is being created in library 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 -- Table could not be created in a collection containing
a data dictionary. The table contains a DATALINK column or a LOB column
that conflicts with the data dictionary.
- 14 -- A DATALINK or LOB column could not be added to a
non SQL table.
- 15 -- Attempted to create or change an object using a
commitment definition in a different ASP.
|
| Recovery Text:
| 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), or get access
to the journal.
- 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 library other than QTEMP, or create the
view over only one distributed table.
- 12 -- Specify a library other than QTEMP, QSYS, QSYS2,
or SYSIBM.
- 13 -- Specify a library that does not contain a data dictionary
or remove all DATALINK and LOB columns.
- 14 -- Specify SQL table for adding the DATALINK or LOB
column.
- 15 -- Specify an object in the same ASP as the current
commitment definition or end the current commitment definition.
|
| SQLCODE or SQLCODEs:
| -7008
|
| SQLSTATE or SQLSTATEs:
| 55019 |
Un Saludo.
Jose Vicente.
"Ana Noguero"
<[EMAIL PROTECTED]>
Enviado por: [EMAIL PROTECTED]
15/03/2006 11:29
|
|
Buenos dias , estoy intentando exportar una
tabla de access al AS400, me sale el siguiente error:
[IBM ] controlador OBC de client access express832
bits)[db2/40 sql]sql7008.
Gracias
