Option 5: Incremental Regeneration
The incremental regeneration process generates only new custom views and those views that have been modified since the last run of Stage 4 or incremental regeneration. Incremental regeneration requires the NoetixViews Workbench and generates only the global form of the views. The process can incrementally regenerate all the customizations that are created through the NoetixViews Workbench and is run and monitored through the Noetix Metabuilder (Noetix MetaBuilder) of the Noetix Enterprise Manager (Noetix Enterprise Manager). When compared to Stage 4 process, the incremental regeneration process can regenerate views faster regardless of whether they are new or customized.
The incremental regeneration process can also support customizations to global views through the legacy hook script method. However, these legacy customizations should be captured and managed through the NoetixViews Workbench.
As a part of the incremental regeneration process, the Noetix Answer Builder is also run so that subsequent runs of the Noetix generators and the Noetix Search Builder for Noetix Enterprise Manager (Noetix Search Builder for Noetix Enterprise Manager) for can pick the latest changes from NoetixViews.
Additionally, you can also run incremental regeneration manually from NoetixViews on a UNIX-based computer. However, you must mange your view customizations through the NoetixViews Workbench.
Some of the view customizations that are supported by the incremental regeneration feature are as follows:
Add, modify, or suppress a column
Add, modify, or suppress a table
Add, modify, or suppress a where clause
Modify view properties
Add, modify, or suppress a view for an existing role
Add, modify, or suppress rowid column-based or standard column-based master keys
Add, modify, or suppress rowid column-based or standard column-based joins
However, in the following scenarios, you will need a complete regeneration of views:
Creation or suppression of custom roles
Addition or modification of key flexfield structures
Changes to the Noetix views generation scripts
Role prefix modifications
Addition or modification of profile options
Changes to the AOL% and XXNAO% views
Changes to the QA Plan Rslt template view
Changes to the XXHIE% template views (However, new and modified joins among the XXHIE% views and other views will be picked up through incremental regeneration.)
New Special Information Types (SITs) or Extra Information Types (EITs) in your Oracle
E-Business Suite instance
You can incrementally regenerate the views for the new SITs and EITs by modifying the template views for SITs and EITs in the NoetixViews Workbench. A modification to the template views, such as adding a keyword or modifying the view description, will allow the views for the new information types to be incrementally regenerated.
A failed incremental regeneration process
For more information about the limitations of the incremental regeneration feature , see the Article Number: 000014262 (INFO: Limitations of Incremental Regeneration).
Prerequisites
The prerequisites for using the incremental regeneration feature are as follows:
NoetixViews 6.5 must be used with NoetixViews Workbench 2.2.
A single NoetixViews Workbench package with all view customizations must have been staged.
Stage 4 should have been completed successfully before the first run of incremental regeneration.
None of the following processes should be running:
The Stage 4 process should not be in progress.
The organization refresh process should not be in progress.
The generation of Noetix answers, Noetix Search (Noetix Search), or any Noetix generator should not be in progress.
Another instance of the incremental regeneration process should not be in progress.
Running Incremental Regeneration Using Noetix MetaBuilder
After you customize a view and add it to a package in the NoetixViews Workbench, when you stage the package, the Noetix Enterprise Manager. Link Service will automatically extract the package into the NOETIX SYS user directory where the incremental regeneration must take place. Thereafter, you can use the Noetix MetaBuilder to run the incremental regeneration process. For more information, see the Noetix Metabuilder Help.
insigihtsoftwarerecommends that you run the incremental regeneration process using the Noetix MetaBuilder for your convenience.
Running Incremental Regeneration Using Script
If you have installed NoetixViews on a UNIX-based computer, and if you want to use the incremental regeneration feature, you need to initiate the process manually using a script. Before you can run the incremental regeneration process, you must stage a NoetixViews Workbench package and manually extract the package to the directory on the UNIX-based computer in which the NoetixViews generation scripts are available. Thereafter, you can run the script for the incremental regeneration process using SQL*Plus.
To run incremental regeneration process
Extract the NoetixViews Workbench package contents to the directory that contains the NoetixViews generation scripts.
Navigate to the directory that contains the NoetixViews generation scripts.
At the command prompt, use the following command to connect to the database as the Noetix System Administration User.
sqlplus <username>/<password>@<dbconnectstring>
At the SQL prompt, run the install incr.sql script to initiate the incremental regeneration process.
When prompted for the APPS user password, type the password, and press ENTER.
During the incremental regeneration process, you will see messages displayed on the SQL*Plus window similar to those displayed in the following screen shot.
To verify the changes for the recently run incremental regeneration, connect to the NOETIX SYS schema using an SQL query tool, and use the following SQL query to view the detailed messages from the N INSTALLATION MESSAGES table:
SELECT Message from N INSTALLATION MESSAGES a
WHERE a.Creation Date >=
(SELECT max(nvo.Creation Date) FROM N VIEW PARAMETERS nvo
WHERE nvo.Install Stage=4.2)
AND Script Name = 'instincr'
Order by Message Seq;
The result of the query will display messages similar to those displayed in the following screen shot.