ibi Data Migrator Status Codes and ibi WebFOCUS Reporting Server Messages

Error and server messages are displayed in the Message window.

The following types of messages are displayed:

  • Connector communication errors. These error conditions usually indicate a problem communicating with the server or network.
  • Internal ibi Data Migrator desktop interface errors. If these errors are self-explanatory, you are given the option of choosing OK or Cancel. If not, the error may indicate problems in memory or with the environment in which the ibi Data Migrator desktop interface is operating.
  • Messages from the Server. The most common messages are those that are sent by the Server. These are displayed in the message window of the ibi Data Migrator desktop interface. Along with descriptive text, there is a message origin and a message code.

The message typically begins with the following:

(XXXnnnn)

where:

XXX

Is the message origin.

nnnn

Is the message code.

Messages of this type may come directly from the subserver during the retrieval of catalog information or rows from a source table, or from the Server as administrative messages.

Common codes of the above three types are described in the following topics. Also, see the appropriate WebFOCUS Reporting Server documentation for your platform and the Server codes at the end of this topic.

Get More Information About Messages

The Server Error Message Report contains a list of all message numbers with a corresponding explanation. On the Workspace page, click Settings, then FOCUS Sets and Info, then Error Message Report. Select the error files that you want to see. You can show warnings or reserved message numbers, and you can enter text to search for. Then click Show Report. You can also issue a query command in the ibi Data Migrator desktop interface.

In the ibi Data Migrator desktop interface:

  • In the procedure, type a question mark (?) followed by the message number. Then click Test.

    The message text and explanation appear in the Console Log area.

ibi WebFOCUS Reporting Server Messages

Some common server messages are listed below: 

(FOC054)	EDA Security error

There is security on the synonym, and the password has not been set correctly. This should be done in the EDASPROF or the user profile for the server.

(FOC14010)	-column-name- IS NOT A VALID COLUMN NAME

ibi Data Migrator desktop interface issues a PREPARE for the SQL command, and the column name does not match the synonym. If you have edited the synonym at the source, you may need to create the Synonym with Automatic Passthru turned off.

(FOC1006)	THE DDNAME REQUESTED IS NOT ALLOCATED OR DLBL'ED : table

(FOC226)	FILEDEF OR ALLOC MISSING FOR EXTERNAL FILE: table

(FOC351)	INPUT FILE NOT ALLOWED: file

(FOC1400)	SQLCODE IS  : 1006/000003EE

(FOC1405)	SQL PREPARE ERROR

These messages, or some combination of them, can display when a synonym for a source file exists but the file it describes is not allocated on the server. These errors can occur on exiting from the Query Builder or on an attempt to run a Test Query. They can also occur when using Metadata Manager or some other tool to create a synonym.

(FOC1538)	4GL procedure doesn't exist: proc

One of the procedures required by the Server could not be found. This may indicate that a new version of the server is needed for full compatibility with the client version being used.

(ICM18986) Request application/name could not be found or accessed

This error occurs when a flow is submitted or scheduled and it cannot be found in the Application Directory specified. Check that it exists, that your user ID can see it, and that the name is in all lowercase. 

(ICM18708) 0 rows retrieved. Stop processing.

This message means that the flow execution properties Stop if 0 rows selected are checked and zero rows returned from the query or loaded to the target. This could indicate an error if no data was available or it could be that there were no rows that met a WHERE condition.

(FOC35804)	BAD STATUS CODE (-9) RECEIVED FROM SERVER subserve

The Server was unable to connect to a subserver listed in the server configuration file (ODIN.CFG).

(FOC541)  SU. CENTRAL DATABASE MACHINE ERROR: FOCSU01

The FDS service is down and the Scheduler is attempting to write in the ETTLOG.

The maximum length allowed for the Application Path is 256 characters.

An example of an application path is: baseapp/app01etl/appwarehouse/history/staging.

The following errors may occur when working with the application path:

(FOC32505) WRONG SEGMENT LENGTH DETECTED: STATS

The Log and Statistics tables are inherited from an earlier release and were not recreated. 

(FOC015) THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH

The full Application Path exceeds 256 characters.

ibi WebFOCUS Reporting Server Log Messages for Agent Termination

Server log messages for agent termination are listed below:

(ICM18175) Agent terminated by operator.

The agent was killed by an administrator or operator.

(ICM18174) Agent has been forced to terminate.

The agent was hard killed or crashed.

ibi WebFOCUS Reporting Server Log Message for a Missed Scheduled Request

The following is an example of a server message that is written if a request with a recurring schedule misses a run:

01/03/2010 18:04:37 E DM: procedure "baseapp/flow02" missed a scheduled run

To detect the run of the missed request, the Scheduler must be active and a custom routing event must be created. There is no filter needed for this event. Based on the Event Routing configuration, the server log message is written into a server log (edaprint.log) or an email message.

Connector Communications Errors

If there is a problem connecting to a Server, a message is displayed in the message window. The following are some of the more common errors: 

Error (12029) – A connection with the server could not be established.

Server is not running or the wrong port number is specified. This error commonly occurs if the server has not started up yet. It could also occur if the host name or port number was incorrect.

Error (12152) – The server returned an invalid or unrecognized response.

This error occurs when something other than the Reporting HTTP server is listening on the specified port number. For example, if a port number for a TCP or FTP server was specified.

Error (32034) – Authentication failed, password is invalid.

This error could occur if either the user ID or the password specified were incorrect.

Error (32033) -- user ID is invalid Disconnected from server

The user ID or password that you entered was invalid for the selected server.

error <NGS> failed to connect to IP address:port, 10061Connection refused
Error (32007) communication error detected

The selected server was unavailable; it may not be running. The connector configuration (ODIN.CFG) may be incorrect.