Search This Blog

Wednesday, July 16, 2014

afadmprf.sh and afcpctx.sh failed during autoconfig

Error:

[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /data02/erpval/oracle/valcomn/admin/install/VAL_s603914se2sl196
      afadmprf.sh             INSTE8_PRF         1
      afcpctx.sh              INSTE8_PRF         1


AutoConfig is exiting with status 2

Solution: followed below steps 
1. removed the log files from $APPLCSF
[applval@S603914SE2SL196 log]$ find . -type f -mtime +7 -exec rm -rf {} \;
2. cd $APPL_TOP

3. Source the APPSORA.env file.

4. Run relink as follows:
adrelink.sh force=y ranlib=y "AD all"

4a. Then run the following:
adrelink.sh force=y ranlib=y "fnd FNDCPUCF"

5. Run adadmin

6. Select option 2 "Maintain Applications Files Menu".

7. Select option 2 "Relink Applications Programs".

8. Relink all modules' programs.

9.then re-run the autoconfig and update the status
Reference: Autoconfig Failing On Concurrent Node At Afadmprf.sh & Afcpctx.sh INSTE8_PRF 1 (Doc ID 1634846.1)
After Appling 11i.ATG_PF.H.Delta.7 Error On afadmprf.sh & afcpctx.sh (Doc ID 943614.1)

Concurrent services not coming up after services restart/server reboot

Concurrent services not coming up after services restart/server reboot

Error in ICM log file:
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /data02/erpval/oracle/valappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 16-JUL-2014 13:27:05
Starting STANDARD Concurrent Manager               : 16-JUL-2014 13:27:05
Service Manager FNDSM_S603914SE2SL196_VAL could not initialize. The Service Manager has been unable to verify its environment and create its log file.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /data02/erpval/oracle/valappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 16-JUL-2014 13:27:06
Starting STANDARD Concurrent Manager               : 16-JUL-2014 13:27:06
Service Manager FNDSM_S603914SE2SL196_VAL could not initialize. The Service Manager has been unable to verify its environment and create its log file.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /data02/erpval/oracle/valappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 16-JUL-2014 13:27:06
Starting STANDARD Concurrent Manager               : 16-JUL-2014 13:27:06
Service Manager FNDSM_S603914SE2SL196_VAL could not initialize. The Service Manager has been unable to verify its environment and create its log file.
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /data02/erpval/oracle/valappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system admin : 16-JUL-2014 13:27:06

Solution: followed the below steps as part of resolutions.

1.ran cmclean.sql
2.exec FND_CONC_CLONE.SETUP_CLEAN;
3. execute autoconfig on db nodes
4. execute autoconfig on apps nodes
5. started the services
 


 

Transportable tablespace refresh

  1.check tablespace for the user which need to refresh -------------------------------------------------------------------  SQL> select ...