E1: PKG: When Submitting a Full Package Build, the Process Does not Generate NERs (Doc ID 2755088.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

When you submit a full package build, the process cannot generate NERs. The process is having trouble with the metadata kernel that uses the JDK or JVM.

When looking at the logs, the issue is with the Generation of NERs to create the N*.c and F*.c files. These Are NOT stored in the repository, but are generated during the package build.

Buildlog.txt

If you look at the buildlog.txt, you will notice right away that there are NER issues, meaning N*.h and N*.c are missing and not building.

This is wrong because this pertains to tables with ER. F*.c.  Plus, the timestamp shows only 2 minutes to generate the NERs which is not right either; it should take one or more hours.

Then if you you look in the serverLogs\GenerateNER_logs\GenNER.log, there are no listing for all the NERs to build N* and F*. The process did not generate the NERs.

In serverLogs\SERVERNAME\text, open the CAEC.txt and CINSTALL.txt, notice that none of them have the listing for NERs. It should normally list the N* files at the bottom and there are none. There are no N* listing anywhere in these .txt files.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.