Full Package Build Problem

[Sunil Rana]

HI ALL
i am facing an issue with Full package Build,the ube R9621 and R9622 and showing "Build Completed with Errors", when i checked the logs it is related to DDTABL, i am attachhing the logs with this post,below are the lines which is related to Error
***********************************************************
Spec file DDTABL begun.
03.03.2009 17:11:08 0 RDB record count in DDTABL : 2541
03.03.2009 17:11:10 0 ERROR: Could not convert RDB specification record to TAM for table DDTABL. See jde.log for more information.
03.03.2009 17:11:11 0 Number of TAM records fetched: 2541.
03.03.2009 17:11:11 0 Number of TAMAdds Attempted: 2540.
03.03.2009 17:11:11 0 Number of TAMAdds succeeded: 2540 failed: 0.
03.03.2009 17:11:11 0 Number of records TAM says it has: 2540.
03.03.2009 17:11:11 0 WARNING: Number of TAM records added does not equal number of RDB records read for "DDTABL".
03.03.2009 17:11:11 0 The cause might be from duplicate or NULL records in database that were not counted.
03.03.2009 17:11:11 0 Number of PAK records fetched: 2541.
03.03.2009 17:11:11 0 Number of PAK Adds Attempted: 2540.
03.03.2009 17:11:11 0 Number of PAK Adds succeeded: 2540 failed: 0.
03.03.2009 17:11:11 0 Creating Indexes for table DDTABL.
03.03.2009 17:11:12 0 Finished creating Indexes for table DDTABL.
03.03.2009 17:11:12 0 Spec file DDTABL finished
***********************************************************

Please suggest me how i can get rid of this error.

Regards
Sunil Rana

 

[Sunil Rana]

HI
I was able to solve the issue after browsing JDelist and found a topic related to this, it was to compare the records in F9860 and F98710, all those records which are present in F98710 must be there in F9860, means F98710 should not have records which are not in Object librarian and if there are some extra records delete these and then it will be solved.
Regards
Sunil Rana

 

[CC_CNC]

Hi Guys,

I had a similar issue, but with no errors showing in the logs. It turns out that the disk on which the package was created was full (for some reason our near-capacity alerts didn't kick in to warn us in time).

In case anyone wants the SQL to compare the two files spoken of in the previous post, I thought I'd include it to save you the typing. You may need to change the schemas to those appropriate for your setup.

select thobnm
from prodb733.f98710
where not exists
(
select 1
from objb733.f9860
where siobnm=thobnm
);

Cheers.