Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  SQL Server  [ 1000 result(s) ]
CISCO IOS IBM IBM DB2 MICROSOFT ORACLE SAP SYBASE SQL Server 
-55227  - Value of DBSERVERNAME configuration parameter retrieved from reserved pages ('server-name') differs from value returned by SQL DBSERVERNAME function ('server-name'), INFORMIXSERVER 'server-name'. IBM
Using information about the specified INFORMIXSERVER in the $INFORMIXDIR/etc/.infos.DBSERVERNAME file, onprobe attaches directly to the database server shared memory. After onprobe attaches, it reads reserved pages from the initial chunk of the root dbspace, based on the information in shared memory. Then onprobe, as a regular SQL client, uses information in the $INFORMIXDIR/etc/sqlhosts file to connect to the specified INFORMIXSERVER. This message indicates that information in $INFORMIXDIR/etc/.infos.DBSERVERNAME and $INFORMIXDIR/etc/sqlhosts regarding the specified INFORMIXSERVER does not match. One possible cause is that the definition of the specified INFORMIXSERVER in $INFORMIXDIR/etc/sqlhosts has been changed after initialization to values that refer to another database server instance.
INFORMIX
Comments
 
-904  - Authorization file not on licensed INFORMIX-SQL server. IBM
This message indicates that the installation of the Informix networking software was not completed correctly. Review the installation steps on the workstation and on the network server(s) to make sure that it was completed without error.
INFORMIX
Comments
 
-1376  - SQL, database server, or program variable mismatch warning. IBM
The program set WHENEVER WARNING STOP, and a warning condition arose. If the statement that is involved is a DATABASE or CREATE DATABASE statement, the condition is that the database server opened the database. On any other statement, the condition is that a SELECT statement returned more values than there were program variables to contain them.
INFORMIX
Comments
 
-439  - Database server is currently processing an SQL task. IBM
You attempted to call an SQL routine or attempted to execute an SQL statement within a signal handling function/routine or a callback function/procedure. Use only the sqldone() and sqlbreak() library functions inside your INFORMIX-ESQL/C callback function. Use only the ECO-SQD and ECO-SQB library routines inside your ESQL/COBOL callback procedure. In addition, if you want to unregister your callback function in INFORMIX-ESQL/C, you can invoke the sqlbreakcallback() callback registration function within your callback procedure. If you want to unregister your callback procedure in ESQL/COBOL, you can invoke the ECO-SQBCB callback registration routine within your callback procedure.
INFORMIX
Comments
 
-2999  - SQL server terminated. IBM
The application has lost contact with the database server. Someone might have shut down the database server, or an internal error might have damaged a pipe between the application and the database server. In a local area network system, the database server process or thread in the file server might have been terminated, or the file server might be down. Look for other messages, especially operating-system messages, that might give more detail.
INFORMIX
Comments
 
-483  - SQL descriptor's name is too long. Limit is 128 characters. IBM
The maximum length for SQL descriptor names depends on the database server. In Informix Dynamic Server 2000, the maximum length is 128 characters. In other Informix database servers, the maximum length is 18 characters.
INFORMIX
Comments
 
-253  - Identifier length exceeds the maximum allowed by this version of the server. IBM
An SQL identifier exceeded the maximum number of characters. In Informix Dynamic Server 2000, the maximum length for identifiers in SQL statements is 128 characters. In other Informix database servers, the maximum length for identifiers in SQL statements is 18 characters. Check that no identifier in the statement is longer than the maximum length and that no punctuation error, such as a missing space or comma, combines two identifiers into one.
INFORMIX
Comments
 
-956  - Client client-name or user is not trusted by the database server. IBM
The desired database server does not consider the client computer or your user ID trusted. Ask the system administrator to include the client computer as a trusted host and/or your user id as a trusted user in the /etc/hosts.equiv file on the server computer or in the .rhosts file in your home directory on the server computer. See the UNIX manual pages on HOSTS.EQUIV(5) for more information. Alternatively, you can explicitly specify your user name and password in the USER clause of a CONNECT statement or in the .netrc file in your home directory on the client computer. See the Informix Guide to SQL: Syntax for information on the CONNECT statement, and the UNIX manual pages regarding NETRC(5) for information on the .netrc file. This message appears with Version 6.0 and later.
INFORMIX
Comments
 
-751  - Remote procedure execution disallowed with pre-5.01 server. IBM
The action clause of the trigger contains an SPL routine that is not called in a data manipulation statement, and an external database server before Version 5.01 will execute the procedure. This action is not allowed. An SPL routine that is called within a data manipulation statement cannot execute certain SQL statements, including transaction-related statements. Transaction-related statements are not allowed within an SPL routine that is a triggered action. A database server before Version 5.01 cannot check for this condition, so the procedure is not allowed. If possible, execute the procedure on a Version 5.01 or later database server.
INFORMIX
Comments
 
-29068  - A field value received from the EDA Server could not be decoded. IBM
In the row that is being fetched, a field value could not be decoded and converted into an Informix data value. Usually this situation occurs because the EDA/SQL Server could not convert the field value from its actual value in the underlying data source to its specified Master File Description (MFD) usage format. For example, if the usage format in the table MFD is I2 (integer value with a maximum field length of 2 characters), and the value of the field is 300, then the EDA/SQL Server cannot fit 300 into the specified 2-character field length. In this case, the Gateway issues the error because the EDA/SQL Server has sent a sentinel value in place of the real field value. Check that the usage format field-length specifications in the MFD are long enough to hold the actual field values that your data contains. If this action does not solve the problem, contact Informix Technical Support for assistance in tracing the data that is received from the EDA/SQL Server.
INFORMIX
Comments
 
 

 
SQL Server Analysis Services (SSAS) (10)
SQL Server Enterprise Manager Error Messages (125)
INFORMIX (33)
SQL Server System Error Messages  (295)
SQL Server Embedded SQL for C Error Messages (ESQL/C)  (48)
C# .Net Compiler Errors and Warnings (1)
Crystal Reports Print Engine (1)
SQL Server DB-Library Error Messages  (19)
SQL Server Integration Services (SSIS) (151)
SQL Server Reporting Services (SSRS) (29)
Cisco IOS (1)
SQL Server Distributed Queries Error Messages  (1)
 
  Prev   1  2  3  4  Next