Informix Error 206 Odbc
Enterprise Gateway Manager egm 211 111 uppercase lowercase Technote (troubleshooting) Problem(Abstract) This document discusses possible causes of errors -206 and -111 while attempting to execute a select with full qualified name, create a synonym or view . Symptom You might get Errors -206 and -111 when referring to a database object (table, view, synonym) using a fully qualified name with IBM Informix Enterprise Gateway Managerâ„¢ (EGM) in SELECT, CREATE VIEW, CREATE SYNONYM statements. 206: The specified table (datasource@egmserver:user.TABLE) is not in the database. 111: ISAM error: no record found. Cause Errors -206 and -111 indicate the object does not exist in the remote target. To construct the fully qualified name, the following rules apply: 1. If the owner is in between quotes in the original statement, send the owner as specified. 2. If the original statement contains the owner, but the owner is not in between quotes, the following conditions apply: If the database logging mode is an ANSI database, convert the original owner to uppercase and send it as a quoted value. If the database logging mode is non-ANSI, convert the original owner to lower-case and sent it as a quoted value. 3. If you do not specify the owner, the following conditions apply: If the database logging mode is an ANSI database, send the UNIX user ID as a quoted value. If the database logging mode is a non-ANSI database, do not send an owner value. Example: Owner value as specified in SQL statement Owner value used by the data source ANSI database Non-ANSI database "Valau" "Valau" "Valau" Valau "VALAU" "valau" not specified "informix" "scott" In this table, informix is the Operating System user that is used to connect to the Gateway Manager. scott is the user used by informix at the data source. In
table (informix.ext_tlr_1) is not in the database Technote (troubleshooting) Problem(Abstract) Archecker table level restore returns ERROR: -206: The specified table (informix.ext_tlr_1) is not in the database. Symptom Archecker table level restore returns ERROR: -206: The specified table (informix.ext_tlr_1) is not in the database. Cause Previous restore attempts failed Resolving the problem If you repeatedly http://www-01.ibm.com/support/docview.wss?uid=swg21154756 run the same archecker table-level restore, you must clean up the archecker table-level restore working files and tables from the previous runs. These working tables refer to acu_ tables in the sysutils database that are created during an archecker table-level restore. The archecker table-level restore working files http://www-01.ibm.com/support/docview.wss?uid=swg21452434 and tables are kept after an archecker table-level restore completes in case these files and tables are needed for diagnosing problems. You can remove the working files and tables by explicitly running the command archecker -DX or by using the -d option when you run the next archecker table-level restore command. The -d option indicates that all files and tables from the previous run of archecker table-level restore are removed before the new restore begins. ontape example: archecker -tdvs -f schema_command_file onbar example: archecker -bdvs -f schema_command_file Document information More support for: Informix Servers Software version: 10.0, 11.1, 11.5, 11.7 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1452434 Modified date: 2012-09-10 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility