12 Replies Latest reply on Dec 9, 2016 5:18 AM by Beauty_and_dBest

    Wrong FNDFS_NODENAME in EBS R12.1.3

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.1.3

      11gR2

      OL6

       

      We have cloned our PROD to TEST instance. We expected that fndfs_prod  will be changed to fndfs_test in the TEST instance.

      Some reports can print with no errors, but there is one program that can not open its output log

      The error is >

      An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_EBIZPROD. There may be a network configuration problem, or the TNS listener on node FNDFS_EBIZPROD may not be running. Please contact your system administrator

       

      Why is that it is pointing to the old nodename? The new nodename should be FNDFS_EBIZTEST.

      But why is that other reports ok?

       

       

      Please help...

       

       

      Kind regards,

      jc

        • 1. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
          Shaik

          Hi JC

           

          check FND_NODES is your test server appearing or not

           

          select node_name from fnd_nodes;

           

          if non existing nodes exists clear it as per below steps

          EXEC FND_CONC_CLONE.SETUP_CLEAN;

          Commit;

           

           

          Run autoconfig on db tier and application tier

           

          Regards

          Shaik

           

           

           

          • 2. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
            Shaik

            Hi JC

             

            check the below document

            Concurrent Processing - After Cloning all the Concurrent Managers do not start for the cloned Instance (Doc ID 555081.1)

             

             

            Regards

            Shaik

            • 3. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
              Beauty_and_dBest

              Hi Shaik,

               

              I run the command :

               

              SQL> select node_name from fnd_nodes;

               

               

              NODE_NAME

              ------------------------------

              AUTHENTICATION

              EBIZTEST

               

               

              I can see that is it correct and good

               

              I checked the $ORACLE_HOME/bin, and I see some executable files using the old  OracleHome.

               

               

              Kind regards,

              • 4. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                Shaik

                Hi JC

                Is autoconfig completed while clone process?

                 

                change the ownership of the files which you mentioned run autoconfig and check the issue

                 

                Regards

                Shaik

                • 5. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                  Beauty_and_dBest

                  Hi Shaik and ALL,

                   

                  Yes autoconfig on apps and db tiers completed successfully. I also run it again and it is all successful.

                  But still I can see in bin programs with old oracle home PROD, which is to be TEST.

                   

                  Below is the list of the programs affected in bin folder:

                   

                  < aqxmlctl:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < bndlchk:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < chopt:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < chopt.ini:enable=run:/usr/bin/make -f /oracle/PROD/oranprod/db/tech_st/11.2.0/rdbms/lib/ins_rdbms.mk lbac_on ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0;run:/usr/bin/make -f /oracle/PROD/oranprod/db/tech_st/11.2.0/rdbms/lib/ins_rdbms.mk ioracle ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < chopt.pl:my $ohome = '/oracle/PROD/oranprod/db/tech_st/11.2.0';

                  < dbca:OH=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < dbua:OH=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < diagsetup:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < dropjava:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < emagentdeploy.pl:$EMDROOT='/oracle/PROD/oranprod/db/tech_st/11.2.0';

                  < EMDeploy:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < emtgtctl:#!/oracle/PROD/oranprod/db/tech_st/11.2.0/perl/bin/perl

                  < emutil:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk

                  < eusm:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < extusrupgrade:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < lbuilder:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre

                  < ldifmigrator:   ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < loadjava:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < mkstore:#JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < netca:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < netmgr:JREDIR=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre

                  < odisrvreg:export ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < oidca:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < oidprovtool:   ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < ojvmjava:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < ojvmtc:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < olsadmintool:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < olsoidsync:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < onsctl:#!/oracle/PROD/oranprod/db/tech_st/11.2.0/perl/bin/perl

                  < orapki:#JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < ott:JAVA_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk

                  < owm:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < platform_common:OH=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < racgwrap:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < rconfig:OH=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < repo_mig:ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < schemasync:   ORACLE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < srvctl:OHOME=/oracle/PROD/oranprod/db/tech_st/11.2.0

                  < targetdeploy.pl:#!/oracle/PROD/oranprod/db/tech_st/11.2.0/perl/bin/perl

                  < trcasst:JREDIR=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre

                  < trcsess:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  < umu:JRE_HOME=/oracle/PROD/oranprod/db/tech_st/11.2.0/jdk/jre/

                  • 6. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                    Beauty_and_dBest

                    Tha ownership of the above files are correct. They are owned by test instance.

                     

                     

                    Kind regards,

                    • 7. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                      Shaik

                      Hi JC

                       

                      which file are you checking for this entries.

                       

                       

                       

                      Regards

                      Shaik

                      • 8. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                        Shaik

                        Hi JC

                         

                        Change the profile RRA: Enabled to Yes  in Site Level

                        and recheck the issue

                         

                         

                        Regards

                        Shaik

                        • 9. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                          Shaik

                          Hi JC

                           

                          R12: Tools -> Copy Function fails with FNDFS Error after a fresh installation (Doc ID 419142.1)

                           

                          Regards

                          Shaik

                          • 10. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                            BlakGeek

                            Go into the Manager Definitions and see if the nodes are incorrect, you can manually change them to the correct node. Concurrent -- Managers -- Define.

                            • 11. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                              Beauty_and_dBest

                              Hi ALL,

                               

                              We have successfully cloned the database and apps tier. All concurrent programs have correct reports output. The only problem is viewing concurrent program logs. Why is it pointing to a wrong node?

                               

                               

                              Kind regards

                              • 12. Re: Wrong FNDFS_NODENAME in EBS R12.1.3
                                Beauty_and_dBest

                                Issue resolve, the report log being viewed are old ones carried out from the source instance.