ASI for DV910 does not show TC UBE's

Soumen

Soumen

Reputable Poster
Checking in to see if someone can point me in the correct direction with this issue:

I am currently in the middle of the TR9.2 upgrade or our system from TR 9.1.5.5 to TR 9.2.0.3 (Application Release E9.1). I am following the required white papers and documents for the upgrade however I am stuck at a stage where when I launch the ASI to run against the DV910 environment and it reaches a stage where it shows which TC's will be run, it does not list any TC's. I was however successful in completing the ASI along with TC conversion for PS910. So there is something in DV910 which is causing this and if I could use some help that would be great.

I have already applied the required Planner ESU's and Tools Roll up ESUs to both DV910 and PS910 successfully.

I am attaching the screen shot where it shows the TC conversion window for DV910 and it's blank. Even when I click close and proceed with the ASI ofcourse it fails for the next steps.

For this upgrade, I had to perform a Deployment server migration to a new server because we wanted to be on the supported platform. Here are the platform details.

E9.1
TR 9.1.5.5
iSeries V7R1

Deployment Server: Windows 20102 R2
 

Attachments

  • DV910_TC_Not_Showing.jpg
    DV910_TC_Not_Showing.jpg
    16 KB · Views: 16
  • jde_log.txt
    8.1 KB · Views: 8
Checking in to see if someone can point me in the correct direction with this issue:

I am currently in the middle of the TR9.2 upgrade or our system from TR 9.1.5.5 to TR 9.2.0.3 (Application Release E9.1). I am following the required white papers and documents for the upgrade however I am stuck at a stage where when I launch the ASI to run against the DV910 environment and it reaches a stage where it shows which TC's will be run, it does not list any TC's. I was however successful in completing the ASI along with TC conversion for PS910. So there is something in DV910 which is causing this and if I could use some help that would be great.

I have already applied the required Planner ESU's and Tools Roll up ESUs to both DV910 and PS910 successfully.

I am attaching the screen shot where it shows the TC conversion window for DV910 and it's blank. Even when I click close and proceed with the ASI ofcourse it fails for the next steps.

For this upgrade, I had to perform a Deployment server migration to a new server because we wanted to be on the supported platform. Here are the platform details.

E9.1
TR 9.1.5.5
iSeries V7R1

Deployment Server: Windows 20102 R2

Do you have any old plan other than ASI was created with name "DV910" ?
 
Last edited:
Do you have any old plan other than ASI was created with name "DV910" ?

I did not check the custom plan app before launching the ASI but I did try to delete the DV910 plan and re-run the ASI, unfortunately that did not help either. What bothers me is this error in the jde.log for which I have checked and re-checked all the entries under P9654A, F9651 and F9650.

"Failed to find environment in F9651, Env=JDEPLAN, Rls=E910"

I did do a Deployment Server migration before starting the TR upgrade and that went well. I have made sure all the entries under F9651, F9650, F00942, F00945 are updated with the new Dep Server name in JDEPLAN and SY910.

Thanks,
Soumen
 
I did not check the custom plan app before launching the ASI but I did try to delete the DV910 plan and re-run the ASI, unfortunately that did not help either. What bothers me is this error in the jde.log for which I have checked and re-checked all the entries under P9654A, F9651 and F9650.

"Failed to find environment in F9651, Env=JDEPLAN, Rls=E910"

I did do a Deployment Server migration before starting the TR upgrade and that went well. I have made sure all the entries under F9651, F9650, F00942, F00945 are updated with the new Dep Server name in JDEPLAN and SY910.

Thanks,
Soumen

May be you can enable the jdedebug log and try to see where the SQL Statement is going wrong. If possible we will try to run the ASI on Our Local Sandbox Setup E910|9.1.5.9 and will give you the jdedebug log to compare.
 
May be you can enable the jdedebug log and try to see where the SQL Statement is going wrong. If possible we will try to run the ASI on Our Local Sandbox Setup E910|9.1.5.9 and will give you the jdedebug log to compare.


Mean while can you please verify whether you have completed all the step's mentioned in the document

E1: INST: How to Change out a Deployment Server for EnterpriseOne Releases Xe - 9.x (9.0 or 9.1) (Doc ID 659735.1)

Changing the Name of the Deployment Server
 
Last edited:
Yes I have followed all steps mentioned in that doc. My case was changing the name of the Deployment Server hence I have run the SQL to change the Dep Server name on both planner and database for the tables .. F00942, F00945, F9651, F9650, and FF983051, F9861. I have verified all entries under P9654A as well.

In addition to that I was able to perform all of the below tasks successful after Dep Server migration:

- Log in JDEPLAN
- Log in to DEP910
- Build and Deploy packages on all environments form DEP910
- Check-in & Check-out of BSFN / NERs.
- Install a FAT client
- Install and Apply the Planner, baseline ESUs.

So there is nothing which tells me that there may be something I have skipped .. atleast not that I know of at the moment.

Thanks,
Soumen
 
May be you can enable the jdedebug log and try to see where the SQL Statement is going wrong. If possible we will try to run the ASI on Our Local Sandbox Setup E910|9.1.5.9 and will give you the jdedebug log to compare.

That's a good idea ... I will try that.
 
Here is the extract from the DEBUG log where it tries to run the SQL and writes the error messages in the jde log...

Jul 01 14:05:23.033078 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBInitReq conn=4941D608 requ=51309780 127.0.0.1 (E1Local) reuse
Jul 01 14:05:23.033079 - 2764/2756 WRK:Starting jdeCallObject SELECT * FROM JDEPlan910.F9651 WHERE ( MDMCHDETTYP = '30' AND MDMCHRCDNM = 'JDEPLAN' ) ORDER BY MDMKEY ASC,MDPORTNUM ASC,MDMCHDETTYP ASC,MDMCHRCDNM ASC
Jul 01 14:05:23.033080 - 2764/2756 WRK:Starting jdeCallObject Exiting JDB_SelectKeyed with Success
Jul 01 14:05:23.033081 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBFetch conn=4941D608 requ=51309780 maxrows=79
Jul 01 14:05:23.033082 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBFetch conn=4941D608 requ=51309780 fetched=0
Jul 01 14:05:23.033083 - 2764/2756 WRK:Starting jdeCallObject No More Data found (hRequest 51450378)
Jul 01 14:05:23.033084 - 2764/2756 WRK:Starting jdeCallObject Failed to find environment in F9651, Env=JDEPLAN, Rls=E910


What I notice is right before the error "Failed to find environment in F9651, Env=JDEPLAN, Rls=E910" it runs this SQL..

SELECT * FROM JDEPlan910.F9651 WHERE ( MDMCHDETTYP = '30' AND MDMCHRCDNM = 'JDEPLAN' ) ORDER BY MDMKEY ASC,MDPORTNUM ASC,MDMCHDETTYP ASC,MDMCHRCDNM ASC

And it does not return any row because in my F9651 there is no row where MDMCHRCDNM = 'JDEPLAN'.
 
Here is the extract from the DEBUG log where it tries to run the SQL and writes the error messages in the jde log...

Jul 01 14:05:23.033078 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBInitReq conn=4941D608 requ=51309780 127.0.0.1 (E1Local) reuse
Jul 01 14:05:23.033079 - 2764/2756 WRK:Starting jdeCallObject SELECT * FROM JDEPlan910.F9651 WHERE ( MDMCHDETTYP = '30' AND MDMCHRCDNM = 'JDEPLAN' ) ORDER BY MDMKEY ASC,MDPORTNUM ASC,MDMCHDETTYP ASC,MDMCHRCDNM ASC
Jul 01 14:05:23.033080 - 2764/2756 WRK:Starting jdeCallObject Exiting JDB_SelectKeyed with Success
Jul 01 14:05:23.033081 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBFetch conn=4941D608 requ=51309780 maxrows=79
Jul 01 14:05:23.033082 - 2764/2756 WRK:Starting jdeCallObject ORACLE DBFetch conn=4941D608 requ=51309780 fetched=0
Jul 01 14:05:23.033083 - 2764/2756 WRK:Starting jdeCallObject No More Data found (hRequest 51450378)
Jul 01 14:05:23.033084 - 2764/2756 WRK:Starting jdeCallObject Failed to find environment in F9651, Env=JDEPLAN, Rls=E910


What I notice is right before the error "Failed to find environment in F9651, Env=JDEPLAN, Rls=E910" it runs this SQL..


SELECT * FROM JDEPlan910.F9651 WHERE ( MDMCHDETTYP = '30' AND MDMCHRCDNM = 'JDEPLAN' ) ORDER BY MDMKEY ASC,MDPORTNUM ASC,MDMCHDETTYP ASC,MDMCHRCDNM ASC

And it does not return any row because in my F9651 there is no row where MDMCHRCDNM = 'JDEPLAN'.

We think this error message is not an issue, because even we have the same message in our Log.

SELECT * FROM JDEPlan910.F9651 WHERE ( MDMCHDETTYP = '30' AND MDMCHRCDNM = 'JDEPLAN' ) ORDER BY MDMKEY ASC,MDPORTNUM ASC,MDMCHDETTYP ASC,MDMCHRCDNM ASC
Jul 02 04:47:31.594045 - 4496/4916 WRK:Starting jdeCallObject Exiting JDB_SelectKeyed with Success
Jul 02 04:47:31.594046 - 4496/4916 WRK:Starting jdeCallObject ORACLE DBFetch conn=54098688 requ=56F12768 maxrows=79
Jul 02 04:47:31.594047 - 4496/4916 WRK:Starting jdeCallObject ORACLE DBFetch conn=54098688 requ=56F12768 fetched=0
Jul 02 04:47:31.594048 - 4496/4916 WRK:Starting jdeCallObject No More Data found (hRequest 57527388)
Jul 02 04:47:31.594049 - 4496/4916 WRK:Starting jdeCallObject Failed to find environment in F9651, Env=JDEPLAN, Rls=E910
Jul 02 04:47:31.594051 - 4496/4916 WRK:Starting jdeCallObject Failed to find logic Server in F9651 associate with F9650, Env=JDEPLAN, Rls=E910

And we executed the query in E1local Database and got same result as like yours. ( Screenshot attached )

ASI.jpg

May be we need to Check , whether 9.2 Upgrade Tc Program is added successfully to your Deployment

We think here we need to focus on other error message in the jde.log instead of "Failed to find environment in F9651, Env=JDEPLAN, Rls=E910"
 
Last edited:
we think this error message is not an issue, because even we have the same message in our log.

Select * from jdeplan910.f9651 where ( mdmchdettyp = '30' and mdmchrcdnm = 'jdeplan' ) order by mdmkey asc,mdportnum asc,mdmchdettyp asc,mdmchrcdnm asc
jul 02 04:47:31.594045 - 4496/4916 wrk:starting jdecallobject exiting jdb_selectkeyed with success
jul 02 04:47:31.594046 - 4496/4916 wrk:starting jdecallobject oracle dbfetch conn=54098688 requ=56f12768 maxrows=79
jul 02 04:47:31.594047 - 4496/4916 wrk:starting jdecallobject oracle dbfetch conn=54098688 requ=56f12768 fetched=0
jul 02 04:47:31.594048 - 4496/4916 wrk:starting jdecallobject no more data found (hrequest 57527388)
jul 02 04:47:31.594049 - 4496/4916 wrk:starting jdecallobject failed to find environment in f9651, env=jdeplan, rls=e910
jul 02 04:47:31.594051 - 4496/4916 wrk:starting jdecallobject failed to find logic server in f9651 associate with f9650, env=jdeplan, rls=e910

and we executed the query in e1local database and got same result as like yours. ( screenshot attached )

View attachment 18317

may be we need to check , whether 9.2 upgrade tc programm is added succesfully to your deployment

we think here we need to focus on other error mesage in the jde.log instead of "failed to find environment in f9651, env=jdeplan, rls=e910"

fyi

9.2 Upgrade TC for E910 Release.jpg
 
Thanks for verifying that .. yes it has started to grow on me that the error for F9651 may not be the actual cause and may be just a non-issue.

But then again the jde.log and debug log does not show me any other error messages which could be relevant. I do see in the jdedebug that it runs this SQL just before launching the TC program. (I am attaching the logs in case if you can spot anything I missed OR if possible compare with your logs)

SELECT * FROM JDEPlan910.F98405 WHERE ( STPLNNAM = 'DV910' AND STPLNDST = '45' AND STCNVTYP = '3' ) ORDER BY STPLNNAM ASC,STPLNDST ASC,STCNVTYP ASC

But the table F98405 does not have any entries for DV910, it does have entries for PS910 which completed successfully. So I guess the 9.2 TC Upgrade program is not getting added successfully for DV910.
 

Attachments

  • jde_3812_070216.log.txt
    6.2 KB · Views: 2
  • DV910_TC_F98405.jpg
    DV910_TC_F98405.jpg
    13.6 KB · Views: 2
  • PS910_TC_F98405.jpg
    PS910_TC_F98405.jpg
    38.6 KB · Views: 3
  • jdedebug_3812_070216.log.txt.zip
    642.4 KB · Views: 2
Thanks for verifying that .. yes it has started to grow on me that the error for F9651 may not be the actual cause and may be just a non-issue.

But then again the jde.log and debug log does not show me any other error messages which could be relevant. I do see in the jdedebug that it runs this SQL just before launching the TC program. (I am attaching the logs in case if you can spot anything I missed OR if possible compare with your logs)

SELECT * FROM JDEPlan910.F98405 WHERE ( STPLNNAM = 'DV910' AND STPLNDST = '45' AND STCNVTYP = '3' ) ORDER BY STPLNNAM ASC,STPLNDST ASC,STCNVTYP ASC

But the table F98405 does not have any entries for DV910, it does have entries for PS910 which completed successfully. So I guess the 9.2 TC Upgrade program is not getting added successfully for DV910.

Main Issue is because 21 TC Record's are not Inserted into the Table F98405 in your Planner Data Source. We compared your log file with ours and found that our log file's are similar up to below SQL Query.

SELECT * FROM SPEC_E910.F98740E910 WHERE ( ELPRDTYP = 4 AND ELOBNM = 'F984052' ) ORDER BY ELPRDTYP ASC,ELOBNM ASC,ELVERS ASC,ELFMNM ASC,ELCTRLID ASC,ELWEVENT ASC,ELERID3 ASC

After that in our log file, we have the below SQL Query but its not there in your log file. Make a Note : Our Database is SQL Server 2014 , So 's the system Data Source is JDE910.SY910 , for other Database it should be SY910

Jul 03 04:15:59.180029 - 1324/3828 WRK:Starting jdeCallObject SELECT * FROM JDE910.SY910.F984052 WHERE ( SHCNVSTS = '2' AND SHCNVTYP = '3' AND SHPGM = 'R89952450A' AND SHDATP = 'Central Objects - DV910 ' AND SHTRLS = 'E910 ' )
Jul 03 04:15:59.180030 - 1324/3828 WRK:Starting jdeCallObject Entering DBPerformRequest
Jul 03 04:15:59.180031 - 1324/3828 WRK:Starting jdeCallObject ODBC:S DBPerformRequest req=54F4BCF0 con=562FE7F8 env=4B5BE2C8 dbc=4B56F5A0 spid=54 JDESQL A (JDE@JDESQL)
Jul 03 04:15:59.181000 - 1324/3828 WRK:Starting jdeCallObject Exiting DBPerformRequest
Jul 03 04:15:59.181001 - 1324/3828 WRK:Starting jdeCallObject No More Data found (hRequest 5644C920)

F984052 is Table Conversion History Log Table

We think , ASI is not able to get the information of TC History from your SY910. F984052 which is resides on your Main Database. After that none of the TC Program are inserted into JDEPlan910.F984051.

Then ASI Standalone TC Workbench was tried finding the TC using the below query and got zero record so showing the empty screen for you !

Jul 02 07:50:39.014082 - 3812/3828 eonejni: LaunchAPPL SELECT STPLNNAM, STLL, STOBNM, STDATP, STFRLS, STTRLS, STCNVTYP, STCNVS, STPGM, STVERS, STPLNDST, STDATS, STURRF, STURCD, STCNVDS, STDTAI FROM JDEPlan910.F98405 WHERE ( STCNVTYP = '3' AND STPLNNAM = 'DV910' ) ORDER BY STLL ASC,STCNVS ASC,STPLNDST ASC,STOBNM ASC
Jul 02 07:50:39.014089 - 3812/3828 eonejni: LaunchAPPL ORACLE DBFetch conn=4B44DD80 requ=52363988 fetched=0
Jul 02 07:50:39.014090 - 3812/3828 eonejni: LaunchAPPL No More Data found (hRequest 49A39FA0)

WRK:Starting jdeCallObject SELECT STPLNNAM, STLL, STOBNM, STDATP, STFRLS, STTRLS, STCNVTYP, STCNVS, STPGM, STVERS, STPLNDST, STDATS, STURRF, STURCD, STCNVDS, STDTAI FROM JDEPlan910.F98405 WHERE ( STCNVTYP = '3' AND STPLNNAM = 'DV910' ) ORDER BY STLL ASC,STCNVS ASC,STPLNDST ASC,STOBNM ASC
Jul 03 04:16:16.303000 - 1324/1232 WRK:Starting jdeCallObject ORACLE DBFetch conn=530E8958 requ=58705BB8 fetched=21
Jul 03 04:16:16.303001 - 1324/1232 WRK:Starting jdeCallObject Fetched the record (hRequest 5644EAD0)

In our case ASI Standalone TC Workbench is able to find 21 program needs to be run for E910|9.2 Tools Upgrade and showing the TC as shown in the screen shot.

Standlaone TC WorkBench.jpg

Try to see is there any problem in connection to SY910.F984052. This is Our findings and if we found some other information, we will share with you !
 
Last edited:
I see what you are saying and agree that the actual cause if the issue is that the ASI is not able to get the information of TC History from my F984052. But I do not see any connection issues to this or any SY910 tables. Note that the PS910 did complete successfully from the same Dep Server and I have all the required entries (as expected) for PS910 in those tables.

One of thing which is bothering me but I do not see a connection is that while starting the ASI for DV910 it throws me this error (screen shot attached) related to my DB being Non-Unicode.
I did not get this error for PS910 because PS910 DB is in Unicode.

Could this have an effect on why it is not able to populate the Planner tables for DV910?
 

Attachments

  • ASI_DV_Unicode_Error.jpg
    ASI_DV_Unicode_Error.jpg
    19.7 KB · Views: 6
I see what you are saying and agree that the actual cause if the issue is that the ASI is not able to get the information of TC History from my F984052. But I do not see any connection issues to this or any SY910 tables. Note that the PS910 did complete successfully from the same Dep Server and I have all the required entries (as expected) for PS910 in those tables.

One of thing which is bothering me but I do not see a connection is that while starting the ASI for DV910 it throws me this error (screen shot attached) related to my DB being Non-Unicode.
I did not get this error for PS910 because PS910 DB is in Unicode.

Could this have an effect on why it is not able to populate the Planner tables for DV910?

We are not sure whether this is the cause of your issue but we didn't get this error message and we hope even you didn't get this error message when you applied the ASI on PS910.

Refer : JD Edwards EnterpriseOne Tools Release 9.2 Upgrade

Verify Control Tables DS is Unicode:
Uses N8900950 to get the data source defined for type 'C' Control Tables. N96500 then checks the
F98611 to see if the data source has the
Unicode flag set. If not, an error occurs.
 
Just a FYI...
Oracle development has identified this as a bug and are going to provide us with a POC.
 
Back
Top