Analyzing Data for Infosphere Federation Server Data Source Configuration Errors

Technote (troubleshooting)


Problem(Abstract)

This is a problem determination document to assist in the analysis of data source configuration problems in the Infosphere Federation Server product.

Symptom

The following symptoms may present:

1) Cannot create federated objects (wrapper, server, user mapping, nickname)
2) Cannot select from data source using set passthru command
3) Cannot select from data source using nickname.


Resolving the problem

To investigate the configuration problem, the traces from the Collecting Data document are needed.

  1. Review db2diag.log output

The db2diag.log may display related information that will assist in resolving the problem. This should be the first place you look for information that may be useful .
    Example db2diag.log excerpt:
    2009-06-15-15.31.33.321781-300 I49624A607         LEVEL: Error
    PID     : 319722               TID  : 1           PROC : db2sysc
    INSTANCE: db2x                 NODE : 000         DB   : XDB
    FUNCTION: <0>, <0>, <44>, probe:20
    DATA #1 : String, 16 bytes
    ODBC native err:
    DATA #2 : String with size, 6 bytes
    -30082
    DATA #3 : String, 16 bytes
    ODBC sqlstate:  
    DATA #4 : String with size, 6 bytes
    08001.
    DATA #5 : String, 16 bytes
    ODBC error txt:
    DATA #6 : String with size, 127 bytes
    [IBM][CLI Driver] SQL30082N  Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001
    In the above example, customer reported problem executing "create server" command. The error indicates the user name and password used are not correct.

2. Confirm data source type, version, client software and operating system are support
Verify that you are using supported data source server and client version.
3. Diagnosing wrapper problems
4. Diagnosing user mapping problems
5. Diagnosing server problems
    If create server definition fails:
    • Confirm wrapper was created successfully
    • Ensure correct syntax is used. Userid and password may be case-sensitive and should be placed inside double quotes. The following error may be returned when the aforementioned problem exists:
      create server  <name> type DB2/UDB version 9.1.0  wrapper DRDA authorization <userid>  password <pw>  options  ( node '<nodename>', dbname '<dbname' )
      DB21034E  The command was processed as an SQL statement because it was not a valid Command Line Processor command.  During SQL processing it returned:
      SQL1101N  Remote database "<dbname>" on node "<unknown>" could not be accessed with the specified authorization id and password.  SQLSTATE=08004
    • If data source server folds/changes user and password from lowercase to uppercase enter option https://www-304.ibm.com/support/docview.wss?uid=swg21066743" you should use options fold_pw and fold_id 'U'. Default is not to fold uppercase.
    • Refer to "Registering server definitions for <data source>" topic for relevant data source in Information Center for details:
      http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.swg.im.iis.db.prod.fed.nav.doc/topics/iiyvfed_config_config_ds.html

6. Diagnosing nickname problems:
    If create nickname definition fails, ensure client software is installed and configured correctly using following steps:
    a) Create user mapping definition if user name and password for data source is different than user name and password used to connect to federated database. If the local username and password on the federated database is the same as the username and password on the remote data source a user mapping may not be necessary. See following links:

    b) Connect to federated database
    c) Issue set passthru and issue select command on a table at the data source
    • DB2 LUW example,
      SET PASSTHRU server_definition_name
      SELECT count(*) FROM syscat.systables
      SET PASSTHRU RESET
    • ORACLE example:
      SET PASSTHRU server_definition_name
      SELECT count(*) FROM sys.all_tables
      SET PASSTHRU RESET
    If unsuccessful proceed to next step. If successful proceed to item e.

    d) Confirm that you can connect to the data source using the client software outside of federated server. As example,
    • DB2 command line " connect to"
    • ORACLE sqlplus
    • ODBC demo or example program

    If native client software connection is successful proceed to next step; otherwise, correct client software problem.

    e) Confirm the table schema, table name and case at the data source; for example, if case-sensitive abc.name may not be same as ABC.NAME on some data sources. If case matters, define nickname using double quotes around schema and table name.
      Example:
      CREATE NICKNAME nickname FOR server_definition_name."remote_schema"."remote.table " ;

If problem still persists send all output collected to IBM Support for analysis as explained in Collecting Data document.

Related information

Collecting Data
DRDA Wrapper Knowledge Collection
ODBC Wrapper Knowledge Collection
ORACLE Wrapper Knowledge Collection

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Federation Server
Configuration

Software version:

9.1, 9.5

Operating system(s):

AIX, HP-UX, Linux, Linux Red Hat - zSeries, Linux SUSE - zSeries, Solaris, Windows

Reference #:

1389055

Modified date:

2009-06-29

Translate my page

Machine Translation

Content navigation