Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2008
    Posts
    29

    Thumbs up Unanswered: Cloudscape to DB2 -data transfer failed (for Websphere Portal 6.0.1.3)

    Guys
    I have db2 server on AIX box & have created 7 databases wrt to the data move from cloudscape to db2.Websphere Portal 6.0.1.3 is installed on SOLARIS box & have all these 7 databases catalouged there.

    I am now trying to transfer all the data from cloudscape to DB2 when i received this error:

    action-add-constraints:
    Fri May 23 14:24:20 EDT 2008
    [java] Reading file /global/site/vendor/WAS/WebSphere6/PortalServer/config/DBTransfer/wps/enableConstraints.sql
    [java] Setting database autocommit to:true
    [java] Connected to jdbc:db2://53.231.196.171:12120/AWPSJCRD:returnAlias=0;
    [java] ALTER TABLE CUSTOMIZATION.APPLICATION_ROLE ADD CONSTRAINT FK2230A FOREIGN KEY (PARENT_OID) REFERENCES CUSTOMIZATION.APPLICATION_ROLE (OID) ON DELETE CASCADE

    [java] Error during statement execution!
    [java] com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: CUSTOMIZATION.APPLICATION_ROLE
    [java] at com.ibm.db2.jcc.c.fg.e(fg.java:1596)
    [java] at com.ibm.db2.jcc.c.fg.b(fg.java:1160)
    [java] at com.ibm.db2.jcc.b.gb.h(gb.java:217)
    [java] at com.ibm.db2.jcc.b.gb.b(gb.java:46)
    [java] at com.ibm.db2.jcc.b.w.b(w.java:40)
    [java] at com.ibm.db2.jcc.b.vb.f(vb.java:118)
    [java] at com.ibm.db2.jcc.c.fg.m(fg.java:1155)
    [java] at com.ibm.db2.jcc.c.fg.a(fg.java:1865)
    [java] at com.ibm.db2.jcc.c.fg.e(fg.java:737)
    [java] at com.ibm.db2.jcc.c.fg.execute(fg.java:721)
    [java] at com.ibm.wps.config.SqlProcessor.process(SqlProcess or.java:591)
    [java] at com.ibm.wps.config.SqlProcessor.process(SqlProcess or.java:146)
    [java] at com.ibm.wps.config.SqlProcessor.process(SqlProcess or.java:84)
    [java] at com.ibm.wps.config.SqlProcessor.main(SqlProcessor. java:945)
    [java] (ErrCode=-204, SqlState=42704)

    BUILD FAILED
    file:../config/actions/dbt_dbcfg.xml:481: Java returned: 4

    Total time: 25 minutes 43 seconds
    --------------------------------

    Can someone throw some light on this ? What is the SQLCODE & SQLSTATE pointing to?

    Regards
    Abhi

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    D:>db2 ? sql204


    SQL0204N "<name>" is an undefined name.

    Explanation:

    This error is caused by one of the following:

    o The object identified by "<name>" is not defined in the
    database.

    o A data type is being used. This error can occur for the
    following reasons:

    - If "<name>" is qualified, then a data type with this name
    does not exist in the database.

    - If "<name>" is unqualified, then the user's function path
    does not contain the schema to which the desired data type
    belongs.

    - The data type does not exist in the database with a create
    timestamp earlier than the time the package was bound
    (applies to static statements).

    - If the data type is in the UNDER clause of a CREATE TYPE
    statement, the type name may be the same as the type
    being defined, which is not valid.

    o A function is being referenced in one of:

    - a DROP FUNCTION statement

    - a COMMENT ON FUNCTION statement

    - the SOURCE clause of a CREATE FUNCTION statement

    If "<name>" is qualified, then the function does not
    exist. If "<name>" is unqualified, then a function of
    this name does not exist in any schema of the current function
    path. Note that a function cannot be sourced on the COALESCE,
    NULLIF, or VALUE built-in functions.



    This return code can be generated for any type of database
    object.

    Federated system users: the object identified by "<name>" is not
    defined in the database or "<name>" is not a nickname in a DROP
    NICKNAME statement.

    Some data sources do not provide the appropriate values for
    "<name>". In these cases, the message token will have the
    following format: "OBJECT:<data source> TABLE/VIEW", indicating
    that the actual value for the specified data source is unknown.

    The statement cannot be processed.

    User Response:

    Ensure that the object name (including any required qualifiers)
    is correctly specified in the SQL statement and it exists. For
    missing data type or function in SOURCE clause, it may be that
    the object does not exist, OR it may be that the object does
    exist in some schema, but the schema is not present in your
    function path.

    Federated system users: if the statement is DROP NICKNAME, make
    sure the object is actually a nickname. The object might not
    exist in the federated database or at the data source. Verify
    the existence of the federated database objects (if any) and the
    data source objects (if any).

    sqlcode : -204

    sqlstate : 42704
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •