PDA

View Full Version : ODBC Fehler beim Exportieren auf AS400



Langesv
31-08-04, 15:02
Hallo

ich versuche eine Access2000-Tabelle auf die AS400 per ODBC
(iSeries-Acces) zu exportieren. Folgende Fehlermeldung erhalte ich:
[IBM][iSeries Access ODBC-Treiber][DB2 UDB]SQL7008 - "Dateiname" in Bibliothek für Operation ungültig. (#-7008)
Kann mir hier jemand näheres über diesen Fehler erklären, und wie ich die ganze Sache beheben kann?

Danke schon mal

Langesv

TARASIK
02-09-04, 15:57
Hallo,
vielleicht hilft Dir das weiter:

MSGSQL7008 &1 in &2 not valid for operation. The reason code is 3.

The AS/400 implements commitment control by journaling. Any ODBC application that takes advantage of commitment control will require that the files used be journaled. See APAR SA49616 for detailed information. SA49616 specifically addresses coexistence issues with COGNOS Impromptu. It also provides general information on commitment control and how it relates to journaling.

Application Specific Errors

Conformance Errors with Microsoft Access

-7711
Router not started.
Incorrect naming convention used (see SQL5016).
A library specified in the ODBC Data Source does not exist on the AS/400. Use the ODBC administration program to reconfigure the driver.
Duplicate EHNAPPC dll's or mixed versions of connectivity code. See "Dynalink Error".
If using the Client Access for Windows 3.1 ODBC driver with the Client Access for extended DOS router, verify that Client Access has been configured for Windows coexistence: i.e. the PCSWIN TSR is loaded before loading windows.
-7716
If this occurs when using an OEM router or the Client Access for Extended DOS router, then obtain the latest ODBC host server PTF.
If using Client Access for Windows 3.11 or later ODBC driver, then verify that the ODBC driver manager (ODBC.DLL) is at version 2 of the ODBC specification. The size and date of ODBC.DLL and ODBCADM.DLL in your windows system directory should match those in the AS/400 directory \QPWXCWN.
-7738
If this error occurs when accessing a physical file with logical files built over it, try copying the physical file to a new library and querying that file. If this works, there is a problem with with the logical files built over the physical file. See apar SA45547 for the latest ODBC host server PTF and contact AS/400 technical support for any additional PTFs that may be required to run with it.
If the latest PTFs are applied, and you still get the -7738 error, it is possible that an index over the physical file is corrupted and will need to be rebuilt. If accessing a physical file that has a join logical file over it, the join logical file may not be keyed.
-7761
The Client Access for Windows R311 ODBC driver was updated to return full support ("F") for left outer join support. This value was added in the R2 ODBC specification. Older versions of the MS Jet Engine included with MS ACCESS report this as a 7761 conformance error: "valid values are only Y or N". Obtain the latest Jet Engine fix pack from microsoft support.

Missing data or Incorrect Data
ACCESS may not display all fields if the total number exceeds 200 fields. Contact Microsoft support for further information on record size limitations with MS ACCESS 2.0.
ACCESS may implement left outer joins by splitting the statement into two separate selects, downloading all the data, and then joining the two temporary tables. This can potentially lead to EXTREMELY large temporary files and unpredictable results. Contact Microsoft for information on how ACCESS can take advantage of full left outer joins which the AS/400 supports.

Desweiteren: