Bug of the week: Cloning Oracle IAS 10g Forms Standalone – Error "Forms OID integration failed"
The bug of the week this time was found while consulting Orange / Partner.
Thanks to Henrik and Vlad who got stuck while doing a clone of their Oracle Application Server 10g.
It all began easily enough when I sent the the documentation on how to perform a IAS clone 
Cloning Oracle Application Server Instances and told them to pay particular attention to 10.5.9 Considerations for Cloning OracleAS Forms Services and 10.5.11 Considerations for Cloning OracleAS Forms and Reports Services Stand alone. Basically you must check the ias.properties file in the source Oracle home, before you run the prepare_clone.pl script to make sure:
- DatabaseManagedClusterSupport=true
- installType=Business
They did just as the Oracle documentation above requested but when they got to the command:
perl clone.pl ORACLE_HOME=<currentOracle Home> ORACLE_HOME_NAME=OraHome_clone -instance ias-clone -ias_admin_old_pwd <old_password> -ias_admin_new_pwd <new_password>
First they happily got the message
[INFO] The cloning of OraHome_clone was successful.
But no celebrating yet … About 2 minutes later they got errors:
[ERROR] Error occured invoking the FileFixer. Error code -1 was returned
[INFO] An error has occured. Aborting the clone operation.
[INFO] Please refer to the error log file <Directory>/OraHome_clone/clone/logs/error1<numbers>.log for details.
Then in the log file they sent me we saw
[INFO] Error creating forms application entity
[INFO] Forms OID integration failed
[ERROR] Error occured invoking the Forms Specific Clone operation. Error code 256 was returned.
[INFO] An error has occured. Aborting the clone operation.
I thought this error makes no sense. Of course the OID integration should fail. We do not have OID since our installation is stand alone! Then lo and behold we found the full solution in this note on Metalink: Cloning a Standalone Forms and Reports installation [ID 368727.1] on Metalink
In general you will need to first:
1. Apply Patch 4386413 10.1.2.0.2 IAS CLONING FAILS AFTER APPLYING A ONE-OFF PATCH
2. Apply Patch 4711967 FORMS AND REPORTS STANDALONE INSTALL CLONING FAILS WHEN CLONING FORMS TO THE SOURCE
and then mannually change some of the files as described in the note ID 368727.1
This note was also helpful – Forms/Reports Standalone Clone Procedure Fails From Command line [ID 729783.1]
Hope this saves all my readers the time and effort it cost poor Vlad 🙂
Let us know if this was helpful …
Mia
The full Error Log you get is …
[INFO] Forms configuration started at: Fri Apr 07 08:51:49 UTC 2006
[INFO] Container Name = forms
[INFO] Error creating forms application entity
[INFO] oracle.ias.repository.directory.DirectoryReader.connectSsl(DirectoryReader.java:96)
[INFO] oracle.ias.repository.directory.DirectoryReader.connect(DirectoryReader.java:106)
[INFO] oracle.ias.repository.IASSchema.getOIDVersion(IASSchema.java:341)
[INFO] oracle.ias.repository.SchemaManager.getOIDVersion(SchemaManager.java:279)
[INFO] oracle.ias.forms.config.CreateAppEntity.makeOidEntry(CreateAppEntity.java:40)
[INFO] oracle.ias.forms.config.FormsConfig.startOIDIntegration(FormsConfig.java:360)
[INFO] oracle.ias.forms.config.FormsConfig.enableConfigWithOID(FormsConfig.java:612)
[INFO] oracle.ias.forms.config.FormsConfig.main(FormsConfig.java:1088)
[INFO] Forms OID integration failed
[INFO] Starting file instantiation
[INFO] Error while instantiating
[INFO] Forms configuration ended at: Fri Apr 07 08:51:49 UTC 2006
[INFO]
_________ ABORTING CLONE OPERATION ________
[INFO] An error has occured. Aborting the clone operation.
