Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Option 4: Regenerate Using Scheduled Cron Job

Regenerating Noetix views using Cron, the UNIX scheduling service, requires a number of initial tasks to set up the environment and parameters to be used. After this initial setup is completed, regenerations can be run on a scheduled basis with no user input required.

If you have upgraded NoetixViews and have used the Cron earlier to regenerate your views, you need to repeat the last step in Step 1: Create UNIX User and Directory. Subsequently, you need to perform the procedures listed in Step 2: Populate Parameter File, Step 3: Populate Password File (for a standard install environment only), Step 4: Grant Permissions to APPS Objects (for an Oracle E-Business Suite On Demand Service (EBSO) environment only), Step 5: Set Up Cron Environment, and Schedule Regeneration in Cron . You should perform these procedures only after you have upgraded NoetixViews. For information about upgrading NoetixViews, see Installing NoetixViews in “Installing Noetix Views.”

This method will involve setting up a Cron job from a UNIX environment.

Initial Setup

The initial setup needs to be done once for each NOETIX SYS schema. After this setup has been done, for subsequent regenerations, go to Schedule Regeneration in Cron to start the regeneration.

Initial setup involves the following steps:

Step 1: Create UNIX User and Directory

Step 2: Populate Parameter File

Step 3: Populate Password File (for a standard install environment only)

Step 4: Grant Permissions to APPS Objects (for an EBSO environment only)

Step 5: Set Up Cron Environment

Step 1: Create UNIX User and Directory

You will need to create a user account and directory in the UNIX-based computer you would use for your regeneration tasks.

To create the UNIX user and directory

Create a UNIX user account exclusively for Noetix administrative tasks.

For the purposes of this document, this account is referred to as noetix unix, but you can name the account anything you want.

Grant this user account permissions to the crontab file. This is necessary because you will be using this account to run the Cron job.

Log on as the noetix unix account you have created.

Create a directory to be used exclusively for NoetixViews.

For the purposes of this document, this directory will be called noetix install dir.

Load the NoetixViews scripts into the noetix install dir directory following the steps described in Load the Software on UNIX in “Installing Noetix Views.”

Step 2: Populate Parameter File

This step will populate a parameter file with default values for all of the information that Noetix views regeneration will need, such as regeneration options and user names. These default values appear when setting up your scheduled regeneration jobs (if they have not been set up at the time of the previous generation). You can change them in a later step for each scheduled job you create.

The script you run in this step will gather and validate the parameters and save them to the noetix install dir/autorun/cparam.sql file. You will have to provide all the required parameters (except passwords) for a scheduled regeneration. While scheduling a regeneration, the Noetix System Administration User password will be taken from the secured cparam.sql file.

To populate the parameter file

Change the present working directory to the noetix install dir directory on the computer containing the Noetix views generation scripts.

Using SQL*Plus, connect to the database as the Noetix System Administration User:

sqlplus <username>/<password>@<dbconnectstring>

If you are using an instance that is not stored in the ORACLE SID environment variable, type @dbconnectstring.

Run the script to gather parameters:

start igetprm.sql

Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each item when prompted, and press ENTER.

Please enter the <NOETIX SYS user> password.

Please enter the name of the database where the <NOETIX SYS> user resides.

Type the Transparent Network Substrate (TNS) name of this database.

What type of unattended install environment do you operate in (STANDARD or EBSO)?

Type STANDARD or EBSO depending on your environment.

Please enter the default tablespace for the <NOETIX SYS> user.

Please enter the Noetix Administrator Installation Path.

Type the full path to the noetix install dir directory, to which the NoetixViews scripts were loaded.

Please enter the APPS user name.

Please enter the language used in the install stage 4 processing.

Should Global views be installed (if available)? Please answer Y or N.

If global form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

Should XOP views be installed (if available)? Please answer Y or N.

If Cross Operations Extension (XOP) form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

Should Standard views be installed? Please answer Y or N.

Should standard INV views be installed (if available)? Please answer Y or N.

If NoetixViews for Oracle Inventory has been purchased, should organization-specific views be generated? Valid responses are Y and N.

Should Projects Multi-currency columns be installed (if available)? Please answer Y or N.

If NoetixViews for Oracle Projects has been purchased, Oracle E-Business Suite 11.5.8 or later detected, and Oracle Projects installed, should the multi-currency columns be generated? Valid responses are Y and N. Changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.

Should Database comments be generated? Please answer Y or N.

The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must regenerate Query Tool Help only after a successful regeneration of Noetix views.

Should Microsoft Help be generated? Please answer Y or N.

Should HTML Help be generated? Please answer Y or N.

Should we run Answer Builder? Please answer Y or N.

Should we run Answer Builder if warning occur in Stage 4? Please answer Y or N.

Overwrite configuration files using previous settings from the database? (Answer Y for Yes or N for No)

This parameter value is ignored in scheduled regenerations, and the role prefixes and settings for Noetix query users will be saved.

Which stages do you want the installer to run?

Choose which type of regeneration you want to schedule, and type A, B, or H:

A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File.

B: This option will run only the Noetix Answer Builder and regenerate the answers.

H: The option will regenerate only the Noetix Help File in the formats specified earlier.

The values you typed will be populated into cparam.sql, and you can continue to the next step.

Step 3: Populate Password File

This step is relevant only if the type of your unattended install environment is standard. Skip to the Option 4: Regenerate Using Scheduled Cron Job if you have an EBSO environment at your site.

This step populates a password file with the user accounts and passwords that are required during a regeneration.

The script you run in this step will gather and validate the passwords and save them to the noetix install dir/autorun/cpw.sql file. Permissions are automatically set on this file so that the passwords are secure and accessible only to the noetix unix user.

To populate the password file

Connect to the database, and do the following:

Change the present working directory to the noetix install dir directory on the computer containing the NoetixViews scripts.

Using SQL*Plus, connect to the database as the Noetix System Administration User:

sqlplus <username>/<password>@<dbconnectstring>

If you are using an instance that is not stored in the ORACLE SID environment variable, type @dbconnectstring.

Run the script to gather passwords:

start igetpw.sql

Type the passwords for the users as required by the script, and then press ENTER. The list of users that is displayed will vary depending on the user configuration at your site. However, this list usually includes your APPS accounts.

Exit SQL*Plus.

The values you typed will be populated into cpw.sql, and you can continue to the next step.

Step 4: Grant Permissions to APPS Objects

This step is relevant only if you have an EBSO environment at your site. Skip to Option 4: Regenerate Using Scheduled Cron Job if you have a standard environment.

This step is required to grant the NOETIX SYS user the permissions to the Oracle APPS schema objects if the version of Oracle E-Business Suite has been upgraded or any patch has been applied to the APPS schema. If there has not been an upgrade, you need not perform the following steps, and you can skip to Step 5.

To grant permissions to APPS objects

Using SQL*Plus, connect to the database as the Noetix System Administration User.

Run the iappspkg.sql script.

Run scripts to grant the NOETIX SYS user the permissions to the APPS schema objects. These scripts are available with the EBSO support providers. For more information about these scripts, contactinsightsoftwareSupport.

Step 5: Set Up Cron Environment

The next step is to create an environment script required for the regeneration. The script you run creates the cronenv.sh file, which is stored in the directory containing the Noetix views generation scripts. You need to edit and test this file to ensure that it functions correctly in your environment.

To set up the Cron environment

Change the present working directory to the noetix install dir directory.

Run the script to set up the environment:

icronenv.sh

This script does not prompt you for any information.

With the UNIX editor of your choice, manually edit the cronenv.sh file to suit your environment. You need to verify that the values listed for your Oracle SID, Oracle BASE, PATH (path to SQL*Plus), and other environment variables are correct. Modify them if they are incorrect, and then save the file.

To test if the environment has been set up correctly, do the following:

Type the following at the command prompt to run the cronenv.sh file, and press ENTER:

. cronenv.sh

Type the following at the command prompt to start SQL*Plus and press ENTER:

sqlplus

If this command successfully starts SQL*Plus, then the environment has been set up correctly.

Exit SQL*Plus.

Schedule Regeneration in Cron

To schedule your NoetixViews regeneration, you need to run a script to add a regeneration job in the crontab file for your user account.

If you are scheduling a regeneration and think that variables that do not get displayed (such as passwords) may have changed since your initial setup, verify that the parameters and passwords saved in the cparam.sql and cpw.sql files are still correct. If you need to change the NOETIX SYS password or other parameters, perform Option 4: Regenerate Using Scheduled Cron Job again. To change the APPS or other administrative passwords, perform Option 4: Regenerate Using Scheduled Cron Job again.

To set up the scheduled Cron job

Change the present working directory to the noetix install dir directory.

Run the script to create the Cron job:

icrontab.sh

Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value (Y or N) for each item when prompted, and press ENTER.

Install Global Extension Roles?

Install Cross Operations Extension (XOP) Roles?

Install Standard Roles?

Install Individual Inventory Roles?

Generate Database Comments?

Generate Microsoft Help?

Generate HTML Help?

Run Answer Builder?

Continue to next stage on warnings?

Installation Option? Valid values (A,B,H)

Choose which type of regeneration you want to schedule, and type A, B, or H:

A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File.

B: This option will run only the Noetix Answer Builder and regenerate the answers.

H: The option will regenerate only the Noetix Help File in the formats specified earlier.

What are your scheduling options for your Cron Job?

Set the schedule for your regeneration by giving values for the following prompts. To indicate no preference for a prompt, type an asterisk (*). For example, if you wanted the regeneration to run every day at 11:00 P.M., you would type 23 for the hour and an * for every other value.

You must specify an appropriate numeric value for at least one of the following entries (that is, you cannot type an * for every prompt). If you have any questions about schedule options, consult the man pages for the crontab file.

What minute of the hour do you want to schedule the cron job? Valid Values (0-59, or *)

What hour of the day do you want to schedule the cron job? Valid Values (0-23, or *)

What day of the month do you want to schedule the cron job? Valid Values (1-31, or *)

What month of the year do you want to schedule the cron job? Valid Values (1-12, or *)

What day of the week do you want to schedule the cron job? Valid Values (0-6 with 0=Sunday, or *)

For more information about these prompts, see Option 4: Regenerate Using Scheduled Cron Job.

Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start this stage again. If the information is correct, press ENTER to continue.

An entry will be created in your crontab file.

#n
#n Note: all comments will be included in your cron entry harmlessly
#n use * for any value to indicate no preference
#n
#n min : minute (0-59),
#n hr : hour (0-23),
#n day : day of the month (1-31),
#n mon : month of the year (1-12),
#n dotw : day of the week (0-6 with 0=Sunday).
#n
#n Use:
#n
#n min hr day mon dotw $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A
#n
#n Sample: 30 23 * * 0 $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A
#n
#n Means 11:30 PM every Sunday
#n
#n Noetix cron entry:
#n
# The following parameters have been entered for the Noetix Automated Installer
# cron job on DDD MMM DD HH:MM:SS PDT YYYY
# Parameters
# 1 Install XOP Roles - Y
# 2 Install Ind. INV Roles - Y
# 3 Install Global INV Role - Y
# 4 Create Multi-Currency Columns (11.5.8+) - Y
# 5 Gen Database Comments - Y
# 6 Generate Microsoft Help - Y
# 7 Generate HTML Help - Y
# 8 Run Noetix Answer Builder - Y
# 9 Continue to next stage on warnings - Y
# 10 Overwrite Configuration Files in Install Dir - Y
# 11 Installation Option - B
#
0 9 24 10 5 /export/home/users/username/install dir/inst4cron.sh Y Y Y Y Y Y Y Y Y Y B

If any errors are detected during Stage 4, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present. For information about manually regenerating the Noetix Help File using scripts, see Option 4: Regenerate Using Scheduled Cron Job.

You may repeat these steps to set up additional scheduled jobs. Each time you run this script, it will add another regeneration entry to your crontab file.

View Regeneration Status

You can view the status of a regeneration job while it is running, or later, by looking at the log files. A log file is created for each job that runs, regardless of whether it is successfully completed. The log file names contain the date and time when the job started running.

After the regeneration is successful, see the ConcurrentManager output in your Oracle E-Business Suite instance to make sure that the concurrent programs are created successfully. If there are any issues with the creation of concurrent programs, see Pregeneration Considerations in “Generation of Views”.

During Stage 4, after the validation of the password for the APPS schema, a prerequisite check process will be performed to detect issues, such as missing SELECT privileges in the APPS schema and issues related to your environment or customizations. This process helps you identify and resolve the errors that may occur during the initial phase of Stage 4. If any issues are identified, Stage 4 will not continue, and the errors will be logged in the prechecker finderr.lst file. Make sure that issues are resolved before you reattempt Stage 4.

To view the regeneration logs

Navigate to the log directory under the noetix install dir directory. You can see a separate file for each job. The log files are named in the cron<YYYYMMDDhhmmss>.log format.

Open the log file corresponding to the date and time when the job started. You can view the tasks that have been completed during the run.

To view the exit status and errors, scroll to the bottom of the file.

Edit or Delete a Cron Job

If you need to edit a job you have set up (for example, rescheduling a regeneration or changing the parameters used) or delete it, you can manually edit the job entry in the crontab file.

To edit or delete a scheduled Cron job

Log on to UNIX as the user who created the job that you want to edit or delete.

Change the present working directory to noetix install dir/autorun.

Type the following to edit or delete a Cron job:

crontab -e

Press ENTER. An output of all the Cron jobs that the user has created will be displayed.

Navigate to the Noetix regeneration job you want to edit or delete. To quickly find the beginning of the first Noetix job, search for #n Noetix Cron entry. The Cron job parameters will be displayed.

Edit the job. If you want to delete the job, delete the whole entry (all lines beginning with #n, as well as the Noetix automated installer parameters).

Save the crontab file, and exit.

Published:

Option 4: Regenerate Using Scheduled Cron Job

Regenerating Noetix views using Cron, the UNIX scheduling service, requires a number of initial tasks to set up the environment and parameters to be used. After this initial setup is completed, regenerations can be run on a scheduled basis with no user input required.

If you have upgraded NoetixViews and have used the Cron earlier to regenerate your views, you need to repeat the last step in Step 1: Create UNIX User and Directory. Subsequently, you need to perform the procedures listed in Step 2: Populate Parameter File, Step 3: Populate Password File (for a standard install environment only), Step 4: Grant Permissions to APPS Objects (for an Oracle E-Business Suite On Demand Service (EBSO) environment only), Step 5: Set Up Cron Environment, and Schedule Regeneration in Cron . You should perform these procedures only after you have upgraded NoetixViews. For information about upgrading NoetixViews, see Installing NoetixViews in “Installing Noetix Views.”

This method will involve setting up a Cron job from a UNIX environment.

Initial Setup

The initial setup needs to be done once for each NOETIX SYS schema. After this setup has been done, for subsequent regenerations, go to Schedule Regeneration in Cron to start the regeneration.

Initial setup involves the following steps:

Step 1: Create UNIX User and Directory

Step 2: Populate Parameter File

Step 3: Populate Password File (for a standard install environment only)

Step 4: Grant Permissions to APPS Objects (for an EBSO environment only)

Step 5: Set Up Cron Environment

Step 1: Create UNIX User and Directory

You will need to create a user account and directory in the UNIX-based computer you would use for your regeneration tasks.

To create the UNIX user and directory

Create a UNIX user account exclusively for Noetix administrative tasks.

For the purposes of this document, this account is referred to as noetix unix, but you can name the account anything you want.

Grant this user account permissions to the crontab file. This is necessary because you will be using this account to run the Cron job.

Log on as the noetix unix account you have created.

Create a directory to be used exclusively for NoetixViews.

For the purposes of this document, this directory will be called noetix install dir.

Load the NoetixViews scripts into the noetix install dir directory following the steps described in Load the Software on UNIX in “Installing Noetix Views.”

Step 2: Populate Parameter File

This step will populate a parameter file with default values for all of the information that Noetix views regeneration will need, such as regeneration options and user names. These default values appear when setting up your scheduled regeneration jobs (if they have not been set up at the time of the previous generation). You can change them in a later step for each scheduled job you create.

The script you run in this step will gather and validate the parameters and save them to the noetix install dir/autorun/cparam.sql file. You will have to provide all the required parameters (except passwords) for a scheduled regeneration. While scheduling a regeneration, the Noetix System Administration User password will be taken from the secured cparam.sql file.

To populate the parameter file

Change the present working directory to the noetix install dir directory on the computer containing the Noetix views generation scripts.

Using SQL*Plus, connect to the database as the Noetix System Administration User:

sqlplus <username>/<password>@<dbconnectstring>

If you are using an instance that is not stored in the ORACLE SID environment variable, type @dbconnectstring.

Run the script to gather parameters:

start igetprm.sql

Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value for each item when prompted, and press ENTER.

Please enter the <NOETIX SYS user> password.

Please enter the name of the database where the <NOETIX SYS> user resides.

Type the Transparent Network Substrate (TNS) name of this database.

What type of unattended install environment do you operate in (STANDARD or EBSO)?

Type STANDARD or EBSO depending on your environment.

Please enter the default tablespace for the <NOETIX SYS> user.

Please enter the Noetix Administrator Installation Path.

Type the full path to the noetix install dir directory, to which the NoetixViews scripts were loaded.

Please enter the APPS user name.

Please enter the language used in the install stage 4 processing.

Should Global views be installed (if available)? Please answer Y or N.

If global form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

Should XOP views be installed (if available)? Please answer Y or N.

If Cross Operations Extension (XOP) form of Noetix views has been purchased, should they be generated? Valid responses are Y and N.

Should Standard views be installed? Please answer Y or N.

Should standard INV views be installed (if available)? Please answer Y or N.

If NoetixViews for Oracle Inventory has been purchased, should organization-specific views be generated? Valid responses are Y and N.

Should Projects Multi-currency columns be installed (if available)? Please answer Y or N.

If NoetixViews for Oracle Projects has been purchased, Oracle E-Business Suite 11.5.8 or later detected, and Oracle Projects installed, should the multi-currency columns be generated? Valid responses are Y and N. Changing the multi-currency option during a regeneration of views impacts reports written against the views for Oracle Projects. For information, see Changing the Multi-Currency Option While Regenerating Noetix Views.

Should Database comments be generated? Please answer Y or N.

The Query Tool Help format is ideal for advanced users who use SQL*Plus, TOAD, and similar tools. As the database comments require a large amount of Oracle tablespace, you must regenerate Query Tool Help only after a successful regeneration of Noetix views.

Should Microsoft Help be generated? Please answer Y or N.

Should HTML Help be generated? Please answer Y or N.

Should we run Answer Builder? Please answer Y or N.

Should we run Answer Builder if warning occur in Stage 4? Please answer Y or N.

Overwrite configuration files using previous settings from the database? (Answer Y for Yes or N for No)

This parameter value is ignored in scheduled regenerations, and the role prefixes and settings for Noetix query users will be saved.

Which stages do you want the installer to run?

Choose which type of regeneration you want to schedule, and type A, B, or H:

A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File.

B: This option will run only the Noetix Answer Builder and regenerate the answers.

H: The option will regenerate only the Noetix Help File in the formats specified earlier.

The values you typed will be populated into cparam.sql, and you can continue to the next step.

Step 3: Populate Password File

This step is relevant only if the type of your unattended install environment is standard. Skip to the Option 4: Regenerate Using Scheduled Cron Job if you have an EBSO environment at your site.

This step populates a password file with the user accounts and passwords that are required during a regeneration.

The script you run in this step will gather and validate the passwords and save them to the noetix install dir/autorun/cpw.sql file. Permissions are automatically set on this file so that the passwords are secure and accessible only to the noetix unix user.

To populate the password file

Connect to the database, and do the following:

Change the present working directory to the noetix install dir directory on the computer containing the NoetixViews scripts.

Using SQL*Plus, connect to the database as the Noetix System Administration User:

sqlplus <username>/<password>@<dbconnectstring>

If you are using an instance that is not stored in the ORACLE SID environment variable, type @dbconnectstring.

Run the script to gather passwords:

start igetpw.sql

Type the passwords for the users as required by the script, and then press ENTER. The list of users that is displayed will vary depending on the user configuration at your site. However, this list usually includes your APPS accounts.

Exit SQL*Plus.

The values you typed will be populated into cpw.sql, and you can continue to the next step.

Step 4: Grant Permissions to APPS Objects

This step is relevant only if you have an EBSO environment at your site. Skip to Option 4: Regenerate Using Scheduled Cron Job if you have a standard environment.

This step is required to grant the NOETIX SYS user the permissions to the Oracle APPS schema objects if the version of Oracle E-Business Suite has been upgraded or any patch has been applied to the APPS schema. If there has not been an upgrade, you need not perform the following steps, and you can skip to Step 5.

To grant permissions to APPS objects

Using SQL*Plus, connect to the database as the Noetix System Administration User.

Run the iappspkg.sql script.

Run scripts to grant the NOETIX SYS user the permissions to the APPS schema objects. These scripts are available with the EBSO support providers. For more information about these scripts, contactinsightsoftwareSupport.

Step 5: Set Up Cron Environment

The next step is to create an environment script required for the regeneration. The script you run creates the cronenv.sh file, which is stored in the directory containing the Noetix views generation scripts. You need to edit and test this file to ensure that it functions correctly in your environment.

To set up the Cron environment

Change the present working directory to the noetix install dir directory.

Run the script to set up the environment:

icronenv.sh

This script does not prompt you for any information.

With the UNIX editor of your choice, manually edit the cronenv.sh file to suit your environment. You need to verify that the values listed for your Oracle SID, Oracle BASE, PATH (path to SQL*Plus), and other environment variables are correct. Modify them if they are incorrect, and then save the file.

To test if the environment has been set up correctly, do the following:

Type the following at the command prompt to run the cronenv.sh file, and press ENTER:

. cronenv.sh

Type the following at the command prompt to start SQL*Plus and press ENTER:

sqlplus

If this command successfully starts SQL*Plus, then the environment has been set up correctly.

Exit SQL*Plus.

Schedule Regeneration in Cron

To schedule your NoetixViews regeneration, you need to run a script to add a regeneration job in the crontab file for your user account.

If you are scheduling a regeneration and think that variables that do not get displayed (such as passwords) may have changed since your initial setup, verify that the parameters and passwords saved in the cparam.sql and cpw.sql files are still correct. If you need to change the NOETIX SYS password or other parameters, perform Option 4: Regenerate Using Scheduled Cron Job again. To change the APPS or other administrative passwords, perform Option 4: Regenerate Using Scheduled Cron Job again.

To set up the scheduled Cron job

Change the present working directory to the noetix install dir directory.

Run the script to create the Cron job:

icrontab.sh

Answer the following prompts. To accept the default value, press ENTER; otherwise, type a value (Y or N) for each item when prompted, and press ENTER.

Install Global Extension Roles?

Install Cross Operations Extension (XOP) Roles?

Install Standard Roles?

Install Individual Inventory Roles?

Generate Database Comments?

Generate Microsoft Help?

Generate HTML Help?

Run Answer Builder?

Continue to next stage on warnings?

Installation Option? Valid values (A,B,H)

Choose which type of regeneration you want to schedule, and type A, B, or H:

A: This option will run Stages 2 through 4 of the generation process and regenerate answers and the Noetix Help File.

B: This option will run only the Noetix Answer Builder and regenerate the answers.

H: The option will regenerate only the Noetix Help File in the formats specified earlier.

What are your scheduling options for your Cron Job?

Set the schedule for your regeneration by giving values for the following prompts. To indicate no preference for a prompt, type an asterisk (*). For example, if you wanted the regeneration to run every day at 11:00 P.M., you would type 23 for the hour and an * for every other value.

You must specify an appropriate numeric value for at least one of the following entries (that is, you cannot type an * for every prompt). If you have any questions about schedule options, consult the man pages for the crontab file.

What minute of the hour do you want to schedule the cron job? Valid Values (0-59, or *)

What hour of the day do you want to schedule the cron job? Valid Values (0-23, or *)

What day of the month do you want to schedule the cron job? Valid Values (1-31, or *)

What month of the year do you want to schedule the cron job? Valid Values (1-12, or *)

What day of the week do you want to schedule the cron job? Valid Values (0-6 with 0=Sunday, or *)

For more information about these prompts, see Option 4: Regenerate Using Scheduled Cron Job.

Verify the information that you have entered. If the information is incorrect, exit the SQL*Plus session (usually by pressing CTRL+C), and start this stage again. If the information is correct, press ENTER to continue.

An entry will be created in your crontab file.

#n
#n Note: all comments will be included in your cron entry harmlessly
#n use * for any value to indicate no preference
#n
#n min : minute (0-59),
#n hr : hour (0-23),
#n day : day of the month (1-31),
#n mon : month of the year (1-12),
#n dotw : day of the week (0-6 with 0=Sunday).
#n
#n Use:
#n
#n min hr day mon dotw $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A
#n
#n Sample: 30 23 * * 0 $noetixdir/inst4cron.sh Y Y Y N N N N Y Y Y A
#n
#n Means 11:30 PM every Sunday
#n
#n Noetix cron entry:
#n
# The following parameters have been entered for the Noetix Automated Installer
# cron job on DDD MMM DD HH:MM:SS PDT YYYY
# Parameters
# 1 Install XOP Roles - Y
# 2 Install Ind. INV Roles - Y
# 3 Install Global INV Role - Y
# 4 Create Multi-Currency Columns (11.5.8+) - Y
# 5 Gen Database Comments - Y
# 6 Generate Microsoft Help - Y
# 7 Generate HTML Help - Y
# 8 Run Noetix Answer Builder - Y
# 9 Continue to next stage on warnings - Y
# 10 Overwrite Configuration Files in Install Dir - Y
# 11 Installation Option - B
#
0 9 24 10 5 /export/home/users/username/install dir/inst4cron.sh Y Y Y Y Y Y Y Y Y Y B

If any errors are detected during Stage 4, the Noetix Help File will not be regenerated. As a workaround, after completing Stage 4, you must first run the ifix4sts.sql script to override Stage 4 errors and then manually regenerate the Noetix Help File. The ifix4sts.sql script is located in the same directory where the install4.sql script is present. For information about manually regenerating the Noetix Help File using scripts, see Option 4: Regenerate Using Scheduled Cron Job.

You may repeat these steps to set up additional scheduled jobs. Each time you run this script, it will add another regeneration entry to your crontab file.

View Regeneration Status

You can view the status of a regeneration job while it is running, or later, by looking at the log files. A log file is created for each job that runs, regardless of whether it is successfully completed. The log file names contain the date and time when the job started running.

After the regeneration is successful, see the ConcurrentManager output in your Oracle E-Business Suite instance to make sure that the concurrent programs are created successfully. If there are any issues with the creation of concurrent programs, see Pregeneration Considerations in “Generation of Views”.

During Stage 4, after the validation of the password for the APPS schema, a prerequisite check process will be performed to detect issues, such as missing SELECT privileges in the APPS schema and issues related to your environment or customizations. This process helps you identify and resolve the errors that may occur during the initial phase of Stage 4. If any issues are identified, Stage 4 will not continue, and the errors will be logged in the prechecker finderr.lst file. Make sure that issues are resolved before you reattempt Stage 4.

To view the regeneration logs

Navigate to the log directory under the noetix install dir directory. You can see a separate file for each job. The log files are named in the cron<YYYYMMDDhhmmss>.log format.

Open the log file corresponding to the date and time when the job started. You can view the tasks that have been completed during the run.

To view the exit status and errors, scroll to the bottom of the file.

Edit or Delete a Cron Job

If you need to edit a job you have set up (for example, rescheduling a regeneration or changing the parameters used) or delete it, you can manually edit the job entry in the crontab file.

To edit or delete a scheduled Cron job

Log on to UNIX as the user who created the job that you want to edit or delete.

Change the present working directory to noetix install dir/autorun.

Type the following to edit or delete a Cron job:

crontab -e

Press ENTER. An output of all the Cron jobs that the user has created will be displayed.

Navigate to the Noetix regeneration job you want to edit or delete. To quickly find the beginning of the first Noetix job, search for #n Noetix Cron entry. The Cron job parameters will be displayed.

Edit the job. If you want to delete the job, delete the whole entry (all lines beginning with #n, as well as the Noetix automated installer parameters).

Save the crontab file, and exit.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk