Select File System for maintenance:
As pre-12.2 Oracle E-Business Suite releases has one file system, there was no choice about where maintenance activities had to be carried out from.
Use of a dual file system in Release 12.2 has required the introduction of a Configuration Change Detector, which automatically detects when changes are made to one file system and replicates them to the other.
Patching cycle is in progress:
During this time maintenance tasks should be performed on the patch file system. If for some reason you need to perform such tasks on the run file system, you must either complete or abort the patching cycle first.
No patching cycle is in progress:
Maintenance tasks should be performed on run file system, then clone the run file system to the patch file system using the adop fs_clone command OR adop will run this command automatically in the prepare phase of the next patching cycle, which could increase time for patching cycle.
Generating Files:
File Types - form, report, message, and JAR (Java archive) files. Need to generate files - file is missing, license additional product.
Note: AD utilities can't be run in parallel with each other. For example, adadmin should not be run when adop is running on any of the nodes in the system.
In addition, parallel sessions of the same utility should not be run. For example, two parallel adadmin sessions can't be run either on the same node or different nodes in the system. The only exception to this is adop, which can safely be run in parallel on multiple nodes.
Setting the Environment:
Remember that there are two file systems in Release 12.2, run and patch. The environment must be set correctly on both.
1. Log in as applmgr (Applications file system owner).
2. Run the environment file for the current APPL_TOP and database.
File is typically APPL_TOP/APPS<CONTEXT_NAME>.env
$ APPS<CONTEXT_NAME>.env
3. If you have made any changes to the environment, check environment
$ echo $TWO_TASK
$ echo $ORACLE_HOME
$ echo $PATH4. Ensure that there is 50 MB in the temporary directories denoted by $APPLTMP and, /tmp.
5. If you are running an AD utility to relink or update Oracle EBS product files or modify Oracle EBS DB objects, shut down the concurrent manager, Web server listeners, forms server listeners if the files are on a node that contains the associated servers.
If the files are on the node that contains the concurrent processing server, shut down the concurrent managers.
Starting a Utility:
Start AD Administration
$ adadmin
Exiting Utility:
When menu-driven utilities complete a processing task, they return you to the main menu, where you either choose another process or Exit.
adop, AD Merge Patch, and File Character Set Converter exits automatically when processing is complete.
Stopping Utility:
Before it begins processing tasks, you can stop a utility by entering abort at any prompt.
Restarting a Utility:
You can restart a utility by entering the executable name on the command line.
The utility prompts you to do one of the following:
• Continue Session (the default)
The utility checks the progress of the previous session in the restart files, and begins processing at the point where your last session stopped.
• Start New Session
The utility asks you to confirm your choice if you choose not to continue the previous session. It starts the process from the beginning.
As pre-12.2 Oracle E-Business Suite releases has one file system, there was no choice about where maintenance activities had to be carried out from.
Use of a dual file system in Release 12.2 has required the introduction of a Configuration Change Detector, which automatically detects when changes are made to one file system and replicates them to the other.
Patching cycle is in progress:
During this time maintenance tasks should be performed on the patch file system. If for some reason you need to perform such tasks on the run file system, you must either complete or abort the patching cycle first.
No patching cycle is in progress:
Maintenance tasks should be performed on run file system, then clone the run file system to the patch file system using the adop fs_clone command OR adop will run this command automatically in the prepare phase of the next patching cycle, which could increase time for patching cycle.
Generating Files:
File Types - form, report, message, and JAR (Java archive) files. Need to generate files - file is missing, license additional product.
Note: AD utilities can't be run in parallel with each other. For example, adadmin should not be run when adop is running on any of the nodes in the system.
In addition, parallel sessions of the same utility should not be run. For example, two parallel adadmin sessions can't be run either on the same node or different nodes in the system. The only exception to this is adop, which can safely be run in parallel on multiple nodes.
Setting the Environment:
Remember that there are two file systems in Release 12.2, run and patch. The environment must be set correctly on both.
1. Log in as applmgr (Applications file system owner).
2. Run the environment file for the current APPL_TOP and database.
File is typically APPL_TOP/APPS<CONTEXT_NAME>.env
$ APPS<CONTEXT_NAME>.env
3. If you have made any changes to the environment, check environment
$ echo $TWO_TASK
$ echo $ORACLE_HOME
$ echo $PATH4. Ensure that there is 50 MB in the temporary directories denoted by $APPLTMP and, /tmp.
5. If you are running an AD utility to relink or update Oracle EBS product files or modify Oracle EBS DB objects, shut down the concurrent manager, Web server listeners, forms server listeners if the files are on a node that contains the associated servers.
If the files are on the node that contains the concurrent processing server, shut down the concurrent managers.
Starting a Utility:
Start AD Administration
$ adadmin
Exiting Utility:
When menu-driven utilities complete a processing task, they return you to the main menu, where you either choose another process or Exit.
adop, AD Merge Patch, and File Character Set Converter exits automatically when processing is complete.
Stopping Utility:
Before it begins processing tasks, you can stop a utility by entering abort at any prompt.
Restarting a Utility:
You can restart a utility by entering the executable name on the command line.
The utility prompts you to do one of the following:
• Continue Session (the default)
The utility checks the progress of the previous session in the restart files, and begins processing at the point where your last session stopped.
• Start New Session
The utility asks you to confirm your choice if you choose not to continue the previous session. It starts the process from the beginning.
Comments
Post a Comment