Wednesday, April 30, 2014

Error:
Autoconfig could not process the following files:
    Directory: /u01/app/oracle/inst/apps/SVRPRD_svrprdebsal1/ora/10.1.3/Apache/Apache/bin
      .apachectl              BINCPY
      .apachectl              BINCPY

AutoConfig is exiting with status 2

(Or)

AC-00429: Binary copy failed for source file: .../apps/tech_st/10.1.3/Apache/Apache/bin/.apachectl
to destination file: .../ora/10.1.3/Apache/Apache/bin/.apachectl

Raised by oracle.apps.ad.autoconfig.InstantiateProcess
setting permissions: .../ora/10.1.3/Apache/Apache/bin/.apachectl 700

AC-00425: Setting permissions failed for file: .../ora/10.1.3/Apache/Apache/bin/.apachectl

Raised by oracle.apps.ad.autoconfig.InstantiateProcess...

Solution :

The workaround for this is simply to change the permissions on .apachectl, run AutoConfig, and then put them back:

1. As applmgr, stop the web tier services (adopmnctl.sh stop).

2. Switch to the root user (su root)

3. Run the following commands (assumes applmgr environment and that "applmgr" is your actual applmgr user name):
    a.  ls -l $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    b.  chown applmgr $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    c.  chmod 0700 $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    d.  ls -l $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl

4. Switch back to the applmgr user (exit)

5. Run AutoConfig

6. Reverse step 3 so that the result looks like step 3a:
    a. su root
    b. chown root .apachectl
    c. chmod 6750 .apachectl
    d. exit


Monday, April 28, 2014

Autoconfig Failed with Error: FsCtxFileException: Start of Root Element Expected


Error :

ERROR: FsCtxFile.XMLParseException
oracle.xml.parser.v2.XMLParseException: Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:306)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)

( or )

ERROR: FsCtxFile.XMLParseException
oracle.xml.parser.v2.XMLParseException: Unexpected EOF
…….....

Or
Caused by: oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsDiscoveryException

Solution :

To implement the solution, please execute the following steps:

1. Backup the fnd_oam_context_files table in the EBS env:

sqlplus applsys/pwd

SQL> create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files;

2. Truncate this table:

SQL> truncate table fnd_oam_context_files;

3. Run autoconfig in the DB tiers to populate fnd_oam_context_files table with the database information;

4. Run autoconfig in each Apps tier to populate fnd_oam_context_files with the application tier information;

5. From the EBS agent home, run:

./emctl upload

This will upload the information from the EBS system to Grid Control.

Note:
By running the following sql query, it will help you identify if there are duplicate node_name entries in the FND_OAM_CONTEXT_FILES table.
  If duplicates are listed, the older entry should be removed only leaving the most current entry.

SQL> select * from FND_OAM_CONTEXT_FILES where status in ('S','F') and name not in
('METADATA','TEMPLATE') and ctx_type='A';

++++++++++++Manjunatha+++++++++++++

Sunday, April 27, 2014

RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

Error :

[oracle@svrtrnebsdl1 bin]$ perl adcfgclone.pl dbTechStack

 0% completed       RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

ERROR while running Apply...
Wed Apr 16 10:29:58 2014

 ERROR: Failed to execute /d02/oracle/svrtrndb/11.2.0.3/appsutil/clone/bin/adclone.pl

 Please check logfile......

Solution :
[oracle@svrtrnebsdl1 bin]$ perl /d02/oracle/svrtrndb/11.2.0.3/appsutil/clone/bin/adclone.pl java=/d02/oracle/svrtrndb/11.2.0.3/appsutil/clone/bin/../jre mode=apply stage=/d02/oracle/svrtrndb/11.2.0.3/appsutil/clone component=dbTechStack method=CUSTOM dbctxtg=/d02/oracle/svrtrndb/11.2.0.3/appsutil/SVRTRN_svrtrnebsdl1.xml showProgress contextValidated=true

APPS Password : apps

Note: The above will solve the RC-00110 Fatal error ...