Adpatch seems to be hanged?
Many times, while applying a patch to a cloned environment, adpatch seems to hang on the following line:
Attempting to instantiate the current-view snapshot...
Solution :
There is couple of reasons for this particular problem. One reason is that the AD module level is lower than the required version for the patch. Second reason is that it could be a temp tablespace issue.
First of all we need to know, what is a snapshot?
There are two types of snapshosts, APPL_TOP and global. APPL_TOP snapshots contain version of files and patches applied within that APPL_TOP. A global snapshot contains the same information but for the entire environment, ie. all APPL_TOPS.
The global view snapshot is used when you use Patch Wizard to determine whether or not a patch has been applied. APPL_TOP snapshots are using by autopatch (adpatch) to determine if all prerequisite patches have been applied. Each time we apply a patch AutoPatch updates the current view snapshot.
Additionally there are two types of snapshots, current view and named. A named snapshot is just a copy of the current view snapshot at a given point in time. Patch wizard and AutoPatch use current view snapshots.
To access snapshot information ,run adadmin, select option 2 - Maintain Applications Files menu, select 4 - Maintain snapshot information and you will see the menu below:
Maintain Snapshot Information
-------------------------------------------
1. List snapshots
2. Update current view snapshot
3. Create named snapshot
4. Export snapshot to file
5. Import snapshot from file
6. Delete named snapshot(s)
7. Return to Maintain Applications Files menu
Since our system is a cloned environment, a snapshot doesn't exist yet for the APPL_TOP. So before AutoPatch can check if prerequistite patches have been applied, it must create a snapshot. This process may take 1-2 hours depending on how fast our servers are. We can avoid this by running "Update current view snapshot" via adadmin after clonning.
Many times, while applying a patch to a cloned environment, adpatch seems to hang on the following line:
Attempting to instantiate the current-view snapshot...
Solution :
There is couple of reasons for this particular problem. One reason is that the AD module level is lower than the required version for the patch. Second reason is that it could be a temp tablespace issue.
First of all we need to know, what is a snapshot?
There are two types of snapshosts, APPL_TOP and global. APPL_TOP snapshots contain version of files and patches applied within that APPL_TOP. A global snapshot contains the same information but for the entire environment, ie. all APPL_TOPS.
The global view snapshot is used when you use Patch Wizard to determine whether or not a patch has been applied. APPL_TOP snapshots are using by autopatch (adpatch) to determine if all prerequisite patches have been applied. Each time we apply a patch AutoPatch updates the current view snapshot.
Additionally there are two types of snapshots, current view and named. A named snapshot is just a copy of the current view snapshot at a given point in time. Patch wizard and AutoPatch use current view snapshots.
To access snapshot information ,run adadmin, select option 2 - Maintain Applications Files menu, select 4 - Maintain snapshot information and you will see the menu below:
Maintain Snapshot Information
-------------------------------------------
1. List snapshots
2. Update current view snapshot
3. Create named snapshot
4. Export snapshot to file
5. Import snapshot from file
6. Delete named snapshot(s)
7. Return to Maintain Applications Files menu
Since our system is a cloned environment, a snapshot doesn't exist yet for the APPL_TOP. So before AutoPatch can check if prerequistite patches have been applied, it must create a snapshot. This process may take 1-2 hours depending on how fast our servers are. We can avoid this by running "Update current view snapshot" via adadmin after clonning.
No comments:
Post a Comment