I wanted to post the solution to the above said problem as it might help others directly or indirectly.
Mr. Justin Miller worked with me offline and helped in troubleshooting this problem. The problem I faced is documented in the following KG document.
5467623 XU6 - SPECS MISSING TO CREATE TABLES IN THE R98700 TO PD EN SystemH96
Document Detail Show detailed information.
Call Number 05467623
Status 900 - Closed / Complete
Product OneWorld Technical > Package Build & Software Updates
Queue 111147 - OW Tech Upgrade/Object Mgt 111
Reference Call (none)
Taken by Ard, Cliff 5710685
SAR Number (none)
System Code H96 - Deployment
Program ID OTUASU - ASU Software Update
Release Xe
Cum Level C06
Service Pack SP18.1
Operating System OS/400ƒ‡
Platform AS/400ƒ‡
Call Reason N - Client Environment/Data
Call From DAVID LUSH
Customer 868889 - Ainsworth Inc.
Business Partner -
Date Received 2003-01-22
Date Returned 2003-01-22
Date Completed 2003-02-03
Description <Q>
I am trying to run the R98407, but I am getting alot of errors. All of the
new tables are not created.
This worked fine for the other environments, but not for PD.
What is wrong?
These are the error messages in the jde.log before you run the R98407:
173/253 Thu Jan 23 16:30:27 2003jdb_rst.c2294
JDB9900318 - Failed to find table information in TAM using RDB
173/253 Thu Jan 23 16:30:27 2003jdb_rst.c329
JDB9900299 - Failed to create global table specs for F96407
173/253 Thu Jan 23 16:30:27 2003jdb_rst.c1099
JDB9900307 - Failed to find table specifications
173/253 Thu Jan 23 16:30:27 2003jdb_rq1.c1451
JDB3100007 - Failed to get valid table specifications
173/253 Thu Jan 23 16:30:27 2003tcinit.c1075
TCE009101 - Couldn't open F96407.
173/253 Thu Jan 23 16:30:28 2003jdb_rst.c2294
JDB9900318 - Failed to find table information in TAM using RDB
<A>
The client had refreshed the spec and bin 32 folders on the deployment server between when he applied Update 6 to DV and PY and when he applied to to PD.
There is a process that runs only the 1st time an ESU that has new tables in it, is applied. It is the TAM to TAM merge. This updates the PLANNER specs with the specs it needs to create the new tables.
To get this to run, you need to take the Advanced Setup Row exit in the Work with Software Updates Screen.
This takes you to the Advanced Software Update Setup Screen.
There you have to UNCHECK the TAM to TAM Merge check-box. This will allow
the TAM to TAM merge to run again, and correct this problem.
This list is a great source and even though I am an active participant, I want to thanks all those who are.