InfoSphere Optim

 View Only
Expand all | Collapse all

Optim Distributed Will No Longer Write to a Specific SQL Table

  • 1.  Optim Distributed Will No Longer Write to a Specific SQL Table

    Posted Fri October 22, 2021 01:58 PM
    Hi, all.

    I have an issue where a table that I've used for 5+ years to stage my Start table data no longer allows Optim to perform any actions on it.  My normal procedure is to extract data from some source and load it to this table.  Now during the Load process, Optim terminates abruptly and gives the error message, "can not create file."  I also tried using an Insert request instead and this gives me an error message that says my user id is not valid for a database that has nothing to do with this process.

    I've tried dropping and rebuilding the table, but I get the same error messages when I run the processes.  If I use the table's DDL to create a copy of the table with a different name, the processes are able to run against this new table.  I don't want to move forward with the new table at this time because it would require me to create/update hundreds of relationships based on the original table name.

    Thank  you,
    Trong

    ------------------------------
    Trong Bo
    Senior Environment Administrator
    HealthNow New York
    ------------------------------

    #InfoSphereOptim
    #Optim


  • 2.  RE: Optim Distributed Will No Longer Write to a Specific SQL Table

    Posted Wed October 27, 2021 02:18 PM
    We have not seen this exact issue, but we have hit some random issues with the SQL loader process via Optim after the DBMS was upgraded. We found using the latest SQL ODBC driver as well as the current version of the SQL loader tended to resolve our issues. You could also try purging that DB alias completely and then rebuilding it from scratch in the event the Registry entry somehow got corrupted. 

    Your option to use an INSERT request may have some default DB Alias in the definition itself. Optim prefills many DB Alias fields with default values or last-used DBs (usually unrelated to the one you're working on now). It's an annoying feature and you may never know it if you don't use that particular function. If you take a closer look at all the pieces in the Insert Request, you may find the issue with that unrelated DB error. Good luck!

    ------------------------------
    Keith Tidball
    Progressive Insurance
    ------------------------------