RDB specification record to TAM for table DDTABL

[sunnyind]

SetUp details : OneWorld XE (B7333) SP20 and applied update 6
I am building a full package after Update 6.
In my BuildError.log I get this
5/7/03 13:03:26 0 Spec file DDTABL begun.
5/7/03 13:03:26 0 RDB record count in DDTABL : 2618
5/7/03 13:04:08 0 ERROR: Could not convert RDB specification record to TAM for table DDTABL. See jde.log for more information.
5/7/03 13:04:09 0 ERROR: Could not convert RDB specification record to TAM for table DDTABL. See jde.log for more information.
5/7/03 13:04:09 0 ERROR: Could not convert RDB specification record to TAM for table DDTABL. See jde.log for more information.
5/7/03 13:04:10 0 Number of TAM records fetched: 2618.
5/7/03 13:04:10 0 Number of TAMAdds Attempted: 2615.
5/7/03 13:04:10 0 Number of TAMAdds succeeded: 2615 failed: 0.
5/7/03 13:04:10 0 Number of records TAM says it has: 2615.
5/7/03 13:04:10 0 WARNING: Number of TAM records added does not equal number of RDB records read for "DDTABL".
5/7/03 13:04:10 0 The cause might be from duplicate or NULL records in database that were not counted.
5/7/03 13:04:10 0 Number of PAK records fetched: 2618.
5/7/03 13:04:10 0 Number of PAK Adds Attempted: 2615.
5/7/03 13:04:10 0 Number of PAK Adds succeeded: 2615 failed: 0.
5/7/03 13:04:11 0 Creating Indexes for table DDTABL.
5/7/03 13:04:15 0 Finished creating Indexes for table DDTABL.
5/7/03 13:04:15 0 Spec file DDTABL finished.


Is there any way to correct it? I saw a coupkle of post in KG, but then again I am not able to find the missing records.
In case there aren't any other errors can I deploy the package to ES and other clients?

please help...
thanks in advance

 

[sunnyind]

there were 3 records which were not there in F9860 but existed in F98710.Finally after a bit of fight got it through

 

[felipecorrea]

hi, i have the same problem but how do you no wich records
were not there in F9860? and how do you solve this problem?. thanks

 

[sashton]

To fix this problem you need to compare the OL733x/F9860 and COxx733x/F98710. Whichever records exist in the F98710 that don't exist in the F9860 need to be deleted. I used SQL and ran this command
SELECT thobnm FROM copd7334/f98710 WHERE thobnm not in
(select siobnm from ol7334/f9860)

This yielded one record so I used this command to delete it.

delete from copd7334/f98710 where thobnm ='F55865D6'

 

[eagleralph]

Thanks.

sashton <[email protected]> wrote:To fix this problem you need to compare the OL733x/F9860 and COxx733x/F98710. Whichever records exist in the F98710 that don't exist in the F9860 need to be deleted. I used SQL and ran this command
SELECT thobnm FROM copd7334/f98710 WHERE thobnm not in
(select siobnm from ol7334/f9860)

This yielded one record so I used this command to delete it.

delete from copd7334/f98710 where thobnm ='F55865D6'
Steven Ashton ERP 8.0 Update 1 SP22_L_1 AS/400 V5R2 Enterprise Citrix MetaFrame Thin Client WebSphere 4.01 HTML Thin Client [email protected]

 

[CNC - HK]

Hi guys,

I have the same problem. But by using the SQL command, I got nothing returned. Any idea?

Regards,
Alvin
Xe SP23_A1 WinNT Citrix SQL Server

 

[Alex_Pastuhov]

Then it's probably not "the same" ;-)

What logs do you get?

 

[CNC - HK]

Looks similar to the problem posted here. Here are my logs.

JDE.LOG
=======
2572/2432 Tue Mar 13 08:51:10 2007 newmda.cpp1081
The registry entries for jdeocx.ocx were removed successfully.

2572/2432 Tue Mar 13 08:51:10 2007 newmda.cpp1019
The registry entries for jdeocx.ocx were created successfully.

2572/2432 Tue Mar 13 08:51:11 2007 jdb_ctl.c2763
Starting OneWorld

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c2295
JDB9900318 - Failed to find table information in TAM using RDB

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c329
JDB9900913 - Failed to create global table specs for F570101

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c1099
JDB9900307 - Failed to find table specifications

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rq1.c1471
JDB3100007 - Failed to get valid table specifications

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c2295
JDB9900318 - Failed to find table information in TAM using RDB

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c329
JDB9900913 - Failed to create global table specs for F5725

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rst.c1099
JDB9900307 - Failed to find table specifications

2572/2432 Tue Mar 13 08:51:24 2007 jdb_rq1.c1471
JDB3100007 - Failed to get valid table specifications

2572/2432 Tue Mar 13 08:51:25 2007 combined.c344
RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c2295
JDB9900318 - Failed to find table information in TAM using RDB

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c329
JDB9900913 - Failed to create global table specs for F570101

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c1099
JDB9900307 - Failed to find table specifications

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rq1.c1471
JDB3100007 - Failed to get valid table specifications

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c2295
JDB9900318 - Failed to find table information in TAM using RDB

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c329
JDB9900913 - Failed to create global table specs for F5725

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rst.c1099
JDB9900307 - Failed to find table specifications

2600/2716 Tue Mar 13 09:11:34 2007 jdb_rq1.c1471
JDB3100007 - Failed to get valid table specifications

2600/2716 Tue Mar 13 09:11:35 2007 combined.c344
RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

BuildError.txt
==============
13/03/2007 19:24:15 0 Spec file DDTABL begun.
13/03/2007 19:24:16 0 RDB record count in DDTABL : 2545
13/03/2007 19:24:17 0 ERROR: Could not convert RDB specification record to TAM for table DDTABL. See jde.log for more information.
13/03/2007 19:24:31 0 Number of TAM records fetched: 2545.
13/03/2007 19:24:31 0 Number of TAMAdds Attempted: 2544.
13/03/2007 19:24:31 0 Number of TAMAdds succeeded: 2544 failed: 0.
13/03/2007 19:24:31 0 Number of records TAM says it has: 2544.
13/03/2007 19:24:31 0 WARNING: Number of TAM records added does not equal number of RDB records read for "DDTABL".
13/03/2007 19:24:32 0 The cause might be from duplicate or NULL records in database that were not counted.
13/03/2007 19:24:32 0 Number of PAK records fetched: 2545.
13/03/2007 19:24:32 0 Number of PAK Adds Attempted: 2544.
13/03/2007 19:24:32 0 Number of PAK Adds succeeded: 2544 failed: 0.
13/03/2007 19:24:32 0 Creating Indexes for table DDTABL.
13/03/2007 19:24:53 0 Finished creating Indexes for table DDTABL.
13/03/2007 19:24:53 0 Spec file DDTABL finished.

 

[Alex_Pastuhov]

Try working the other way around - what's in F9860, but not in F98710.

 

[CNC - HK]

I tried that. It gave me a long list.

 

[CNC - HK]

I also tried to get the table spec of F570101 and F5725 in OMW. No problem.

 

[CNC - HK]

Hi all,

Can anyone tell me what is copd7334? I am using SQL Server, not AS/400.

Alvin

 

[Sebastian Sajaroff]

Hi,

That would be JDE_PD7334.PD7334.Fxxxx tables

 

[CNC - HK]

Hi all,

The problem is fixed. I used the SQL:
select thobnm from jde_PY7333.PY7333.F98710 where thobnm not in (select siobnm from jde7333.OBJ7333.F9860 where sifuno = 'TBLE')

I tried to build the package on deployment server with debug mode and I found that the system is reading the F9860 using the SIFUNO = 'TBLE' in the where clause. The above SQL then yield the entry that has some null fields. After putting back the correct values, the package build completed.