What is the version of the OPatch installed in the MT?
Did you source the environment correctly?
Yes, I am following this documentation.
My scenario is basically the example 4 from doc 2008451.1, where I applied all the patches and I am running again just to make sure that all patches were applied on MT.
However, after start the examining product Oracle Forms and Reports I got the error message.
| Copyright (c) 2005, 2015 Oracle and/or its affiliates. |
| All rights reserved. |
| Oracle E-Business Suite Release 12.2 |
| Middle Tier Technology Codelevel Checker |
Using context file from currently set applications environment:
Starting Middle Tier Technology Codelevel Checker, Version: 120.0.12020000.16.
Thu Oct 02 14:54:07 BST 2015
Log file for this session: ./checkMTpatch_8989.log
Bugfix XML file version: 120.0.12020000.16
This file will be used as the reference for identifying missing bugfixes.
Checking for prerequisite bugfixes in File Edition: run
Enter the password for the APPS user:
Database connection successful.
The installed AD.C.5 codelevel does not support storing the results in the database.
Oracle Forms and Reports
Now examining product Oracle Forms and Reports.
Error checking inventory. Error code:19.
Ensure Oracle Forms and Reports home is registered in oraInventory.
Please advice on what should I do next....
I downloaded on Oct 1st the latest Opatch version on patch Patch 6880880. The latest update so far is on Sept 25, 2015. So I am assuming that I am using the latest version.
Regarding the source environment I add the source environment on .profile from my applmgr user. So I am running the .VIS_myhost.env.
Is this correct ?
This is a vision instance indeed.
I checked on the documentation, since I am a beginner, could you please correct me if I misunderstood ?
Basically I need to attach all the ORACLE_HOME associated with each product from MT using the OUI?
If not, what do you mean by global oraInventory been verified ?
Thanks for your help.
1 person found this helpful
The Vision install, since it is prepackaged, does not include creating necessary oraInventory entries, as one would normally experience by installing an EBS instance from scratch. Suggest following the steps in the docs to recreate the oraInventory instance for your Vision instance and try the checkMTpatch.sh again. Does the checkMTpatch.sh script run successfully for your other instances created from EBS install media ?
The first time I run to check the missing patches, it worked fine.
I'll try to recreate oraInventory as you advice following the doc.