Results 1 to 4 of 4

Thread: Database has less columns than Specs

  1. #1
    New Member
    Join Date
    Feb 2017
    Location
    Indiana
    Posts
    9

    Database has less columns than Specs

    In a recent project, I added a few columns to a table. Generated the table in every environment as it was promoted, everything worked in our development and prototype environments. When we promoted to Production, we found that fetches to the table would not work. If the table was in a business view on a grid, the records would populate, but would not when the value was populated in a form control by way of Select and FetchNext. We ran logs and they said that the table in our database has 18 physical columns, while our specs has 25 logical columns.

    The table has been generated multiple times, in every environment. Thoughts?

  2. #2
    Member craig_welton's Avatar
    Join Date
    Oct 2000
    Location
    Litchfield, CT
    Posts
    923
    Changing table specs (adding columns) can be a pain with the web environments. Don't know your release/SP (include in your signature) but we had to restart web instances to sync the specs with actual table layout. Cache clearing did not help.
    Craig Welton
    PatWel Group Inc.
    http://www.patwel.com
    Home of the FREE JDE Object Browser, JDETrace and NERDup Tools

    E1 9.0 8.98.4.2 Wintel SQL 2008
    E1 9.2 9.2.1.4 iSeries

  3. #3
    New Member
    Join Date
    Feb 2017
    Location
    Indiana
    Posts
    9
    Rebooting the web server fixed the problem. Of course we find a solution right after posting the thread!

  4. #4
    Senior Member
    Join Date
    Mar 2004
    Location
    Fort Worth, Texas
    Posts
    1,482
    I can second what Craig is saying. We 100% confirmed that you have to bounce the JAS servers when you change a table spec. In fact I think Craig help confirm for us that you have to do this. I will go one further. When we change a table spec we almost always do a full build. If there is any C code that references the table it may very well need to be recompiled even if the business logic of the C code is not effected by the new field(s) (or in very rare instances if we delete field(s)). The only way to force a full recompile is with a full build.
    Brian Oster
    Application Development Manager
    E1: 9.0 (TR9.1.5.1) / 9.2 (TR9.2.2.2)
    JAS/BSSV: Weblogic 12.1.2 / Weblogic 12.2
    ES: Win2008 / Win2016
    DB: MSSQL 2014 / 2016
    WebDev Client: Win7Pro / Win10Pro

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.