Fail to install OAS10g Metadata Repository

I'm trying to install a OAS10g Metadata Repository in the database 10.1.0.4 on Solaris 8 . I meet a error :
Loading Repository for OracleAS Portal using the specification file /u/app/oracle/product/bi/portal/repca/ptlload.xml
Repository Loader actionStarting
[CustomExternalProcessAction] Command line: /u/app/oracle/product/bi/jdk/bin/java -cp /u/app/oracle/product/bi/assistants/opca/jlib/opca.jar:/u/app/oracle/product/bi/portal/jlib/ptlshare.jar:/u/app/oracle/product/bi/jdbc/lib/classes12.jar:/u/app/oracle/product/bi/jdbc/lib/nls_charset12.jar oracle.webdb.config.PortalConfigAssistant
[CustomExternalProcessAction] Process exited abnormally
[CustomExternalProcessAction] Action failed due to: oracle.ifs.utils.action.ActionFailedException: Some of the operations have failed during this OracleAS RepCA session. Please see the log file at /u/app/oracle/product/bi/assistants/repca/log/repca_2005-07-06_05-32-40_PM.log for further details.
ERROR - Some of the operations have failed during this OracleAS RepCA session. Please see the log file at /u/app/oracle/product/bi/assistants/repca/log/repca_2005-07-06_05-32-40_PM.log for further details.
oracle.ifs.utils.action.ActionFailedException: Some of the operations have failed during this OracleAS RepCA session. Please see the log file at /u/app/oracle/product/bi/assistants/repca/log/repca_2005-07-06_05-32-40_PM.log for further details.
     at oracle.ias.repca.actions.CustomExternalProcessAction.perform(CustomExternalProcessAction.java:153)
     at oracle.ifs.utils.action.ActionQueue.performActions(ActionQueue.java:303)
     at oracle.ifs.utils.action.ActionQueue.run(ActionQueue.java:229)
     at java.lang.Thread.run(Thread.java:534)
Please help me. Thans.

I met the same problem ... at 60% of the installation procedure.
Did you solve the problem ... ?
Cause I'd built a 10gR2 RAC.. and I wanna store the AS's metadata into
RAC. I'd trace the class, and convert to the original code. But it's very hard to understand how it works.
It was located under oracle/ias/repca/actions/CustomExternalProcessAction.class
Any body can help me ? Please !

Similar Messages

Error in Installing SSO Metadata Repository Creation Assistant (10.1.4.3.1)

I am trying to Install Portal Forms Reports 11, so I had to Install all prerequisites
My Machine Specifications:-
1- Oracle Enterprise Linux 5.5 x86-64
2- DB 11g R2
3- WebLogic 10.3.3 (X64)
4- Oracle Identity Management 11.1.1.2.0
I was executed the inspre11.pl with -op1
than I was trying to Install SSO Metadata Repository Creation Assistant (10.1.4.3.1)
in the last step (Step 7 - Loading Repository)
http://lh3.ggpht.com/_bMH90GEkTL4/SwW1jlNHzFI/AAAAAAAABjE/ZZm55usPKu0/s1600-h/clip_image054%5B3%5D.jpg
I encountered this error :-
ERROR - Unable to connect to the database. See the log file for details. Check that you have provided the proper service name for the database, that the database is running, the database connection information is valid, and that the database is set up for password file authentication. For more information, click the Help button.:ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_IAS_VERSION.SET_COMPONENT_LOADING' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
what can I do ? my Database is start up and the connection is OK !!!!!!!!!!!
I followed the oracle documentation:-
Installation Guide for Oracle Identity Management 11g Release 1 (11.1.1) E12002-02 October 2009
now we are going to 2011 !!!!!!!!!!!!!!!!!!!
Is there another newer Installation guide from oracle?
thank you

Good question, rozester.
I encountered this problem also, while trying to install the SSO MRCA 10.1.4.3.1 on 64-bit RHEL5 (though it's at version 5.7 but I'm positive that won't make any difference to the result).
This may or may not match your situation, but when I looked in the log file $ORACLE_HOME/assistants/repca/log/repca_<datestamp>.log, I saw what was probably the reason behind the error:
<$ORACLE_HOME>/bin/sqlplus: error while loading shared libraries: libclntsh.so.9.0: cannot open shared object file: No such file or directory
I think I remember seeing that the link operation during installation had failed, but I hoped it would be OK. And it possibly would have been, if I'd remembered to specify the destination database Oracle home rather than the SSO MRCA Oracle home when prompted (on the page where it asks for database home and log file path). Perhaps then it would have used the sqlplus binary from the database oracle home, and since that one definitely works, it might have worked. But before I thought of that, I did a workaround; I installed the SSO MRCA on a 32-bit RHEL5 box (using the same directory paths) and copied the shared library files to the 64-bit box's shared library directory via scp as follows:
cd $ORACLE_HOME/lib; scp -pr * oracle@rhel64box:$PWD/
When I re-ran $ORACLE_HOME/runRepca, it then worked without error. Another thing I could have tried is just running runRepca on the 32-bit RHEL5 box, and that probably would have worked too, but it probably would have been a lot slower compared to running it locally on the destination server; it's takes quite a while as it is.
Hope this helps. I'm sure it'll help me if next time I do this I forget what I did before and go searching again ;-)

Problems Installing Oracle Metadata Repository into Existing Database

Folks,
I'm slowly going through the process of installing the Metadata Repository into a 10g database, using RepCA I've managed to determine all the DB parameters required for setting etc. The only thing RepCA now reports is missing is the Ultrasearch schema & packages.
I've copied the ultrasearch dirs from the RepCA distribution and placed them in my $ORACLE home dir, I've also attempted to run the admin install script 'wk0setup.sql' which throws out several errors listed below. If anyone has successfully gone through this process on Solaris I would love to hear your about your experience & advice.
Error 1. =================================================
User is WKSYS
... loading ultrasearch_db.jar
call sys.dbms_java.loadjava('-v -f -r -s -g PUBLIC $ORACLE_HOME/ultrasearch/lib/ultrasearch_db.jar', '((* wksys) (* public))')
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception:
oracle.aurora.server.tools.loadjava.ToolsError: Error during loadjava: Failures
occurred during processing. Check trace file for details
Error 2 (File Doesn't exist at all) ==============================
SP2-0310: unable to open file "/oracle/1020a/ultrasearch/admin/wk0launchq.pkh"
Error 3 (Again the file doesn't exist at all) ========================
SP2-0310: unable to open file "/oracle/1020a/ultrasearch/admin/wk0launchq.plb"
===========================================================
Regards
Austin

Hi guys,
I have used copy of that package from Oracle Identity Management installation, version 10.1.4.0.1 and have been able to complete manual Ultra Search installation. It's valid in dba_registry. After that I did run RepCA and metadata schemas have been created successfully in existing database, version 10.2.0.2. Be careful about database version, only 10.2.0.2 is certified with Oracle Identity management, so you need to run patch for upgrade to 10.2.0.2.
Hope this helps.
Dali
Message was edited by:
dallyz7

Metadata Repository Creation Assistant fails with ORA-01119


Hi All,
My DB version is 10.1.0.2 and I've upgraded the same to
10.1.0.4.2
In order to install B2B, I started off by installing the
Metadata Repository Creation Assistant.
After the initial steps, I got the following message:
<h5>
OracleAS RepCA was not able to find the Oracle Text Supplied
Knowledge Base in the database specified. </h5>
<h5>If you are planning to use this repository for installing
OracleAS Portal, you have to install Oracle Text Supplied Knowledge Base.
Oracle Text Supplied Knowledge Base can be installed in the database using
Oracle Database 10g Companion CD.</h5>
<h5>
If you are not planning to use this repository for
installing OracleAS Portal, you may continue further. Continue? Yes/No?</h5>
I continued with "Yes" and I chose the storage option as
"Regular or Cluster File system". In the next step -<strong>Specify Tablespace
information</strong>, I chose to install it in the C:\ , where there was approx 18GB
of free space. Yet, I encountered the following error:
<h5>
Unable to create tablespace. Please see the OracleAS RepCA
log file for more details.</h5>
<h5>ORA-01119 error in creating database file 'string'</h5>
<h5>Cause: Insufficient space on device or invalid database file
path.</h5>
<h5>Action:</h5>
<h5>a) Verify the database file path specified.</h5>
<h5>b) Decrease the size of the requested file or allocate a
file on another device with more available space. If a file size was not
specified in the statement, then specify a file size smaller than the available
space on the device.</h5>I have verified the database file path. I also tried
decreasing the size. I further tried using another directory where there was
11GB of free space. It still didn't work.
Please HELP!
-Suhas.

Hi Suhas,
Can you please do the following?
1. Please try pointing to C:\b2b.dbf file during installation and see if the installation goes fine or not.
Regards
Vipin R.S

Metadata Repository for OC4J Forms.

Hullo
i'd like to install the Metadata repository without the farm's infrastructure. but i did'nt find the good options.
Good morning friends
Sacha H

Hi Niten,
May be this weblog by Roberto will be helpful..
/people/sap.user72/blog/2005/09/05/sap-bw-and-business-content-datasources-in-pursuit-of-the-origins
Ashish....

Can not start opmn after change OracleAS Metadata Repository Listener Port

Hello,
I installed OracleAS metadata Repository Listener Port, And i change the port of the listener, then flowwoing the manual was needed start teh OID component
But I won´t start

Roberto,
The tail of OIDCTL.log is:
09/02/23 19:14:44 Start process
oidctl:oidmon is not running on u47.un.mx, waiting for a few seconds...
09/02/23 19:58:44 Start process
oidctl:oidmon is not running on u47.un.mx, waiting for a few seconds...
09/03/02 16:02:43 Start process
09/03/04 15:57:21 Start process
And the tail for oidmon.log:
2009/03/02:16:02:43 * oidmon_u47pacrm01.unitec.mx:0 *
Updating Process Table...
2009/03/04:14:52:11 * Killed process pid = 1345
2009/03/04:14:52:11 * Monitor Process id = 1345 Terminated
2009/03/04:14:52:11 * Sent SIGTERM to process id = 1374
2009/03/04:14:52:11 * ODISRV Instance 1 deleted from registry
2009/03/04:14:52:11 * Updating Process Table...
2009/03/04:14:52:11 * Sent SIGTERM to process id = 1370
2009/03/04:14:52:11 * OIDLDAPD Instance 1 deleted from registry
2009/03/04:14:52:11 * Updating Process Table...
2009/03/04:15:57:21 * Connecting to database, connect string is te04as
2009/03/04:15:57:21 * [gsdsiConnect] ORA-0,
2009/03/04:15:57:21 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:57:23 * [gsdsiConnect] ORA-0,
2009/03/04:15:57:41 * Connecting to database, connect string is te04as
2009/03/04:15:57:41 * [gsdsiConnect] ORA-0,
2009/03/04:15:57:41 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:58:01 * Connecting to database, connect string is te04as
2009/03/04:15:58:01 * [gsdsiConnect] ORA-0,
2009/03/04:15:58:01 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:58:21 * Connecting to database, connect string is te04as
2009/03/04:15:58:21 * [gsdsiConnect] ORA-0,
2009/03/04:15:58:21 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:58:41 * Connecting to database, connect string is te04as
2009/03/04:15:58:41 * [gsdsiConnect] ORA-0,
2009/03/04:15:58:41 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:59:01 * Connecting to database, connect string is te04as
2009/03/04:15:59:01 * [gsdsiConnect] ORA-0,
2009/03/04:15:59:01 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:59:21 * Connecting to database, connect string is te04as
2009/03/04:15:59:21 * [gsdsiConnect] ORA-0,
2009/03/04:15:59:21 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:15:59:41 * Connecting to database, connect string is te04as
2009/03/04:15:59:41 * [gsdsiConnect] ORA-0,
2009/03/04:15:59:41 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:16:00:01 * Connecting to database, connect string is te04as
2009/03/04:16:00:01 * [gsdsiConnect] ORA-0,
2009/03/04:16:00:01 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:16:00:21 * Connecting to database, connect string is te04as
2009/03/04:16:00:21 * [gsdsiConnect] ORA-0,
2009/03/04:16:00:21 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:16:00:41 * Error connecting database. -1
2009/03/04:16:00:41 * Error : Guardian Process terminated
2009/03/04:16:50:45 * Connecting to database, connect string is te04as
2009/03/04:16:50:45 * [gsdsiConnect] ORA-0,
2009/03/04:16:50:45 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:16:50:47 * [gsdsiConnect] ORA-0,
2009/03/04:17:18:36 * Connecting to database, connect string is te04as
2009/03/04:17:18:36 * [gsdsiConnect] ORA-0,
2009/03/04:17:18:36 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:18:38 * [gsdsiConnect] ORA-0,
2009/03/04:17:18:56 * Connecting to database, connect string is te04as
2009/03/04:17:18:56 * [gsdsiConnect] ORA-0,
2009/03/04:17:18:56 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:19:16 * Connecting to database, connect string is te04as
2009/03/04:17:19:16 * [gsdsiConnect] ORA-0,
2009/03/04:17:19:16 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:19:36 * Connecting to database, connect string is te04as
2009/03/04:17:19:36 * [gsdsiConnect] ORA-0,
2009/03/04:17:19:36 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:19:56 * Connecting to database, connect string is te04as
2009/03/04:17:19:56 * [gsdsiConnect] ORA-0,
2009/03/04:17:19:56 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:20:16 * Connecting to database, connect string is te04as
2009/03/04:17:20:16 * [gsdsiConnect] ORA-0,
2009/03/04:17:20:16 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:20:36 * Connecting to database, connect string is te04as
2009/03/04:17:20:36 * [gsdsiConnect] ORA-0,
2009/03/04:17:20:36 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:20:56 * Connecting to database, connect string is te04as
2009/03/04:17:20:56 * [gsdsiConnect] ORA-0,
2009/03/04:17:20:56 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:21:16 * Connecting to database, connect string is te04as
2009/03/04:17:21:16 * [gsdsiConnect] ORA-0,
2009/03/04:17:21:16 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:21:36 * Connecting to database, connect string is te04as
2009/03/04:17:21:36 * [gsdsiConnect] ORA-0,
2009/03/04:17:21:36 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
2009/03/04:17:21:56 * Error connecting database. -1
2009/03/04:17:21:56 * Error : Guardian Process terminated
-----

Can I install Metadata Repository for 10.1.2.0.2 on Oracle 10.2.0 database

Does any one know if the Metadata Repository of OracleAS 10.1.2.0.2 can be install on an existing Oracle 10.2.0 database ?
The MRCA tool is giving me this message "Oracle Metadata Repository cannot be loaded into this version of the database. Please see the installation guide for more information on supported database versions ...."
Kim

According to the Installation Guide, Oracle9i Release 2 (9.2.x) and Oracle Database 10g Release 1 (10.1.x) are supported. See the following for more specific information:
http://download-west.oracle.com/docs/cd/B14099_19/sol.1012/repca.1012/repca/intro.htm#CHDEAJFB

Rdbms patchset problem in installing metadata repository

hi ,
i m facing this problem while installing metadata repository for Oracle Application Server10g(9.0.4.0.0)
the error is ,
"the catalog objects stored in this database donot have the same version as the database software.
please review the post-installation steps of the RDBMS patchset and make sure that you have run
all required SQL scripts."
plz help

Hello,
You can login to the Metadata database and execute:
select * from dba_registry;
This will give you the version numbers for database components.
Vlad

Metadata Repository install to existing db

Hello,
I am trying to install and configure a Metadata Repository to a 10.2.0.1 database, I know that you must use the Repository creation assistant, but i am having trouble locating this tool. I already have the db installed and set up. Does the repCA ship with the database, or do I need to install the application server next to access it?
Cheers!
Jordan

Would I be able to accomplish the same task using the Repository Administration Utility that ships with Developer Suite? There're no such utility for Metadata Repository in Developer Suite!!! There are however a tool to create a Designer Repository, but that's something quite different.
Please note that if you're going to use a 10.2 database, then you must download the version I wrote! There's a version that comes on the AS10g Disk set, but that doens't support 10.2.
Regards,
Martin

Applying 10.1.2.3 Metadata Repository update in 10.1.4.3 distributed IDM

Hi there, I seem to have a unique issue.
I have the following config of 10.1.4.3 IDM :
SSO in a separate Oracle home
OID in a separate Oracle home
DB (10.2.0.50) in a separte OH and metadata repository installed in this DB
and this is set up in ASR replication mode with other similer setup.
Task : Apply 10.1.2.3 OracleAS patchset.
The story:
To be fully compliant according to Orcale we ned to apply 10.1.2.3 patch. This patch has two components - a software update and a Metadata Repository (MR) update.
I have applied software update to all the Oracle homes above (with the exception of DB ofcourse).
But to apply MR update I have to do it from a mid-tier OH that also has MR installed, I have none.
I tried installing MR update from SSO and OID oracle home but it would not allow me , I got this message :
The Metadata Repository Update cannot be run from the selected ORACLE_HOME.
The Update must be run from either an Identity Management with Metadata
Repository installation ...
But we have no middle-tier using this MR, and from this metalik note, it seems applying MR update is not mandatory, only a desirable housekeeping execrcise . :
Understanding How AS 10g Patch Sets Update the AS Metadata Repository [ID 795143.1]
Exract from that note :
a. apply the binary update to each AS Oracle Home in the AS Farm.
b. finally, if possible apply the MR update exactly once from any home that allows it to be run.
also from the same note :
Scenario 6: Applying the 10.1.2.3 AS patch set to a 10.1.4.3 Identity Management home.
The 10.1.2.3 AS patch set is a required patch set, as documented in :
Note: 465847.1 Oracle Identity Management 10g (10.1.4.0.1) Release Notes Addendum.
In this case, the MR Product schemas will not be directly accessed. It is however good practice/ housekeeping to apply the MR update in order to keep the MR in line with the binary patch sets.
My question :
I am correct in my understanding that apply 10.1.2.3 software update only is neccessary, applying the MR update is only desirable house keeping and not mandatory ?
Would you say this is the correct assessment. if not how would you go about applying the MR update ?
Thanks in advance for your answers.
Narsimha

TooManyOracleToysToLearn wrote:
Upgraded OPatch to 1.0.0.0.64
Attempted to apply 10.1.2.3 patchset 5983622
Encountered 2 issues, 1 has prevented us from continuing
Issue 1: Received following on stdout ...
failed to get the ias-instance ...
Error: no ias instance to append to
Val: 3Did you source the correct env file before applying the patch? --> $INST_TOP/ora/10.1.3/<CONTEXT_NAME>.env
Issue 2: When running the Configuration Assistants, it fails right away on step "Run One-Off Patches".
It's looking for the ocm.rsp. Received the following:
Oracle Configuration Manager (OCM) is included with this release of OPatch.
This is a OCM patch.
EBS environment: no OCM installation and configuration.
To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).
Run /u04/app/ebupg/ebupgora/10.1.2/OPatch/ocm/bin/emocmrsp to generate an OCM response file. The generated response file can be reused on different platforms and
in multiple OPatch silent installs.
To regenerate an OCM response file, rerun /u04/app/ebupg/ebupgora/10.1.2/OPatch/ocm/bin/emocmrsp.
ERROR: OPatch failed because of cmd. args. problem.Error Applying Patch Using OPatch "This version of OPatch is obsolete", "OPatch failed because of cmd. args. problem" [ID 762403.1]
10.1.4.3 Patch Set Pre Installation Step: dcmctl updateconfig FAILS: Fatal Relocation Error [ID 849474.1]
Getting Error 'OPatch requires a response file for Oracle Configuration Manager (OCM)' while Running OPatch [ID 727991.1]
Thanks,
Hussein

Is 10.1.4.3 Metadata Repository Certified With 10.1.4.1 IM installation?

We have IM 10.1.4.3 and OracleAS 10g R2 10.1.2.3 on RedHat 4.6 with non-colocated metadata repository.
Plan is to upgrade RedHat to newest version 5.5. RedHat does not support upgrade with major version and Oracle said that OS vendor is responsible for package compatibility and there is no need for relink Oracle software.
So, only solution is to do fresh install OS, IM and OracleAS.
My question: is it possible to install IM 10.1.4.1 against higher version of metadata repository? Is there any workaround?
tnx in advance
Matej

"# Error: Already exists" suggests that schema at AD side is already extended. You mentioned that automatic schema upload process stopped abruptly. There is likely chance that AD schema might be extended partially or fully.
2nd thing is you can apply BP05 patch once you have identity server running. BP05 does not need to be applied before.
Also there is option to manually extend schema directly in AD. There is one folder in installation directory which has .ldif files with schema objectclasses.
At the start of identity server , it is not able to find the configuration DN & seach base to read configuration data , therefore it is failing.
You have two options here: 1. Reinstall 2. Manually extend schema and then install identity server.
You can refer to Atul's blog : &raquo; OAM 10.1.4.3 Installation Part II &#8211; Indentity Server Installation Online Apps DBA: One Stop Shop…
Hope this helps.
Regards
Aakash

Fail to install oracle infrastructure in separating mode

When I install oracle infrastrure in Redhat 4.0 update 1, at first install the OracleAS Metadata Repository in a computer, then I try to install the Oracle Identity Management Components on another machine also redhat 4.0 update 1, the installer fail to locate the OracleAS Metadata Repository, database info, it pop up window said it can not locate the database server in that machine, but I already confirm the OracleAS Metadata Repository has been installed successfully, and started. the version is 10.1.4.01 linux platform.
Thanks in advance!

I have solve the problem, in the Database schema field I fill long name Global Space name then it pass the form.
Thanks for your attentions

Error in installing a new Repository in OWB 10g Release 2

Hi,
I am facing a consistent problem in creating a new repository, even after uninstalling and re-installing the OWB client many times. While creating a repository, I get the following three errors, after which the Repository Assistant automaticlly shuts down:
1. The wizard noticed that the installation parameter 'enqueue_resources' of the database GRUSIT is set to 968. The recommended value for Warehouse Builder is 3000.
2.The Warehouse Builder repository owner installation failed on user REPOWNER.
java.sql.SQLException: ORA-04031: unable to allocate 4080 bytes of shared memory ("shared pool", "BEGIN
DECLARE
PROCEDURE brow...", "PL/SQL MPCODE", "pl/sql DS pg")
3.INS0029: Error occured during installation. Check the log file
F:\OraHome_1\owb\UnifiedRepos\log_070504_115828.000.log
for details.
Could you pls help me in resolving this issue?
Thanks in advance,
Tanvi

Does this mean, ... we have to install the OWB 64 bit and install a new repository in the 64 bit server?In my opinion you don't need to create new repository.
After migrating database to 64bit perform steps from Metalink note 434272.1 "How To Update Warehouse Builder 10.2 After A Database Cloning".
It is better to save the same path for new OWB 64bit software. If you install OWB into different path you need to update OWBRTPS table with new path to OWB software (look at metalink note 550271.1).
Regards,
Oleg

Windows Server 2012 R2 - ALL HF's Failing to install as "Does Not Apply to this computer"

Hi,
A general question about hot fix installs.
I have multiple servers that are all Windows 2012 R2. They do not have internet connections, so I have to install the Hotfixes manually. I download the HF's from the ISO download page (https://support.microsoft.com/en-us/kb/913086) every month. I collect them and install in a bulk install during a release cycle ( a couple times a year). I just realized that NO HF's have installed since JUNE 2014. Every HF that shows up in WindowsServer2012R2 directory fail to install with a message of "The update is not applicable to your computer". Which is fine if that was true, but.... I get this message for every HF from the ISO's since June 2014. NOT one HF thinks it is applicable to my computer. Could that be the case? No HF's apply to my Server 2012 systems since June of 2014?
This is my system info, and below that is the results from attempting to install 95 HF's.
C:\TEMP>systeminfo
Host Name: MYHOST
OS Name: Microsoft Windows Server 2012 R2 Datacenter
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 00252-80025-36226-AA727
Original Install Date: 6/13/2014, 8:04:39 AM
System Boot Time: 3/16/2015, 2:34:45 PM
System Manufacturer: Dell Inc.
System Model: PowerEdge R720
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
[02]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
BIOS Version: Dell Inc. 2.2.2, 1/16/2014
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 262,099 MB
Available Physical Memory: 249,337 MB
Virtual Memory: Max Size: 301,011 MB
Virtual Memory: Available: 288,015 MB
Virtual Memory: In Use: 12,996 MB
Page File Location(s): C:\pagefile.sys
Domain: mydomain.sgn
Logon Server: \\MYHOST
Hotfix(s): 25 Hotfix(s) Installed.
[01]: KB2862152
[02]: KB2868626
[03]: KB2876331
[04]: KB2888505
[05]: KB2892074
[06]: KB2893294
[07]: KB2893984
[08]: KB2898785
[09]: KB2898868
[10]: KB2898871
[11]: KB2900986
[12]: KB2901125
[13]: KB2901128
[14]: KB2909210
[15]: KB2909921
[16]: KB2912390
[17]: KB2916036
[18]: KB2919442
[19]: KB2922229
[20]: KB2923392
[21]: KB2925418
[22]: KB2930275
[23]: KB2931358
[24]: KB2931366
[25]: KB2936068
Network Card(s): 6 NIC(s) Installed.
[01]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: ISCSI
DHCP Enabled: No
IP address(es)
[01]: 192.168.1.30
[02]: fe80::38c9:e59c:5ac2:e0a1
[02]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: NIC3
Status: Hardware not present
[03]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: MGMT
DHCP Enabled: No
IP address(es)
[01]: 7.48.64.32
[02]: 7.48.64.30
[03]: fe80::f14e:9339:9326:c7fd
[04]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 1_swport_VMRepwan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[05]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: NIC2
Status: Hardware not present
[06]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 2_swport_VMOpswan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.
I have a script that runs each HF install.. If I run them manually without the tool I get the same results so it is not the script..
Installing 95 patches
for Microsoft Windows Server 2012 R2 Datacenter x64
Repository path: U:\Patch Repository_4_1\2012_R2_HFs\
1. Windows8.1-KB2894852-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
2. Windows8.1-KB2894856-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
3. Windows8.1-KB2920189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
4. Windows8.1-KB2926765-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
5. Windows8.1-KB2928120-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
6. Windows8.1-KB2931358-x64.msu patch status: ALREADY INSTALLED - SKIPPING
7. Windows8.1-KB2931366-x64.msu patch status: ALREADY INSTALLED - SKIPPING
8. Windows8.1-KB2933826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
9. Windows8.1-KB2939576-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
10. Windows8.1-KB2953522-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
11. Windows8.1-KB2957151-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
12. Windows8.1-KB2957189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
13. Windows8.1-KB2957689-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
14. Windows8.1-KB2961072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
15. Windows8.1-KB2961887-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
16. Windows8.1-KB2962872-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
17. Windows8.1-KB2964718-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
18. Windows8.1-KB2964736-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
19. Windows8.1-KB2965788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
20. Windows8.1-KB2966072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
21. Windows8.1-KB2966826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
22. Windows8.1-KB2966828-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
23. Windows8.1-KB2971850-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
24. Windows8.1-KB2972213-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
25. Windows8.1-KB2972280-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
26. Windows8.1-KB2973114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
27. Windows8.1-KB2973201-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
28. Windows8.1-KB2973351-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
29. Windows8.1-KB2974008-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
30. Windows8.1-KB2976627-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
31. Windows8.1-KB2976897-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
32. Windows8.1-KB2977292-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
33. Windows8.1-KB2977629-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
34. Windows8.1-KB2978668-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
35. Windows8.1-KB2982794-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
36. Windows8.1-KB2982998-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
37. Windows8.1-KB2987107-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
38. Windows8.1-KB2987114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
39. Windows8.1-KB2988948-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
40. Windows8.1-KB2992611-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
41. Windows8.1-KB2993651-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
42. Windows8.1-KB2993958-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
43. Windows8.1-KB3000061-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
44. Windows8.1-KB3000483-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
45. Windows8.1-KB3000869-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
46. Windows8.1-KB3001237-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
47. Windows8.1-KB3002657-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
48. Windows8.1-KB3002885-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
49. Windows8.1-KB3003057-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
50. Windows8.1-KB3003381-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
51. Windows8.1-KB3003743-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
52. Windows8.1-KB3004150-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
53. Windows8.1-KB3004361-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
54. Windows8.1-KB3004365-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
55. Windows8.1-KB3005607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
56. Windows8.1-KB3006226-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
57. Windows8.1-KB3008923-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
58. Windows8.1-KB3008925-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
59. Windows8.1-KB3010788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
60. Windows8.1-KB3011780-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
61. Windows8.1-KB3013126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
62. Windows8.1-KB3013455-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
63. Windows8.1-KB3014029-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
64. Windows8.1-KB3018943-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
65. Windows8.1-KB3019215-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
66. Windows8.1-KB3019978-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
67. Windows8.1-KB3020393-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
68. Windows8.1-KB3021674-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
69. Windows8.1-KB3021952-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
70. Windows8.1-KB3023607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
71. Windows8.1-KB3036197-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
72. Windows8.1-KB3021953-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
73. Windows8.1-KB3022777-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
74. Windows8.1-KB3023266-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
75. Windows8.1-KB3023562-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
76. Windows8.1-KB3024663-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
77. Windows8.1-KB3029944-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
78. Windows8.1-KB3030377-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
79. Windows8.1-KB3031432-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
80. Windows8.1-KB3032323-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
81. Windows8.1-KB3032359-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
82. Windows8.1-KB3040335-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
83. Windows8.1-KB3033408-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
84. Windows8.1-KB3033889-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
85. Windows8.1-KB3034196-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
86. Windows8.1-KB3034344-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
87. Windows8.1-KB3035017-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
88. Windows8.1-KB3035034-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
89. Windows8.1-KB3035126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
90. Windows8.1-KB3035131-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
91. Windows8.1-KB3035132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
92. Windows8.1-KB3037634-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
93. Windows8.1-KB3039066-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
94. Windows8.1-KB3044132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
95. Windows8.1-KB3046049-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
Thanks,
Dave

Hi Dave,
Would you please check CBS lg file and other relevant event logs if find more clues? On current situation, please refer to following article and check if can help you.
Update is not applicable to your computer- but it is
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Can OID/IM components be moved to a new Metadata Repository?

Hi
I've looked around on Metalink but can't find any document that suggests this can be done, but I thought I would ask the question anyway (two iin fact):
1. Can an existing OID/IM setup be configured so as to oint to a new metadata repository? Is it possible to install a new MR and then associate the IM components away from it's existing MR to a new MR?
2. In an OracleAS Cold Failover Cluster (IM) topology, I've read contradictory notes (or I've misunderstood). Do the OID and MR components have to be on the same box? Or can they be on different boxes?
Regards
Andy

#1, refer this:
http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/chginfra.htm#BGBDDDBE
#2, refer following note on MetaLink:
368688.1 Master Note:How to Split AS10G Infrastructure Components Including the Metadata Repository and Identity Management
Hope this helps.
Thanks
Shail

Fail to install OAS10g Metadata Repository

Similar Messages

Maybe you are looking for