7 Replies Latest reply on Feb 19, 2019 7:46 AM by Beauty_and_dBest

    Applying the Latest AD and TXK

    Beauty_and_dBest

      EBS 12.2.7

      12c

      OL6

       

      Hi ALL,

       

      I am apply patches for lates AD and TXK.

      Since we are already 12.2.7,  I chosed:

      3 Path C — Existing Release 12.2 customers (at AD-TXK Delta 10 codelevel)

       

      I already run adgrants.sql as what was instructed, but still it says I need to run it?

       

      I applied first AD patches using:

       

      $ adop phase=apply patches=27254132,28394214,27638770,28714940,27868573,28986462,28882245,28426427 merge=yes patchtop=/u01/PATCH/AD_TXK

       

      But I got error below:

       

      Enter the APPS password:

      Enter the SYSTEM password:

      Enter the WLSADMIN password:

       

      Validating credentials.

       

      Initializing.

          Run Edition context  : /u02/appv1228/V1228/fs1/inst/apps/V1228_trnsrvr/appl/admin/V1228_trnsrvr.xml

          Patch edition context: /u02/appv1228/V1228/fs2/inst/apps/V1228_trnsrvr/appl/admin/V1228_trnsrvr.xml

          Patch file system free space: 140.32 GB

       

      Validating system setup.

          Node registry is valid.

          [WARNING]   ETCC: The following required database fixes have not been applied to node trnsrvr:

                        24589081

                        25099339

                        25919622

                      Refer to My Oracle Support Knowledge Document 1594274.1 for instructions.

       

      Checking for existing adop sessions.

          Continuing with existing session [Session ID: 61].

       

      ===========================================================================

      ADOP (C.Delta.10)

      Session ID: 61

      Node: trnsrvr

      Phase: apply

      Log: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/61/20190218_230727/adop.log

      ===========================================================================

       

      Starting patch merge.

          Merging patches where applicable.

          Log: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/61/20190218_230727/apply/trnsrvr/admrgpch.log -console off

       

      Executing the merge of the patch drivers

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28882245

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28882245/u28882245.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28882245/u28882245.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28882245

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27638770

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27638770/u27638770.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27638770/u27638770.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27638770

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28714940

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28714940/u28714940.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28714940/u28714940.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28714940

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28394214

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28394214/u28394214.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28394214/u28394214.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28394214

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28986462

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28986462/u28986462.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28986462/u28986462.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28986462

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27254132

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27254132/u27254132.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27254132/u27254132.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27254132

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28426427

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28426427/u28426427.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28426427/u28426427.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/28426427

       

      -- Processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27868573

      -- Processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27868573/u27868573.drv

      -- Done processing file: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27868573/u27868573.drv

      -- Done processing patch: /u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494/src/27868573

       

       

       

      Copying files...

       

      5% complete. Copied 5 files of 84...

      10% complete. Copied 9 files of 84...

      15% complete. Copied 13 files of 84...

      20% complete. Copied 17 files of 84...

      25% complete. Copied 21 files of 84...

      30% complete. Copied 26 files of 84...

      35% complete. Copied 30 files of 84...

      40% complete. Copied 34 files of 84...

      45% complete. Copied 38 files of 84...

      50% complete. Copied 42 files of 84...

      55% complete. Copied 47 files of 84...

      60% complete. Copied 51 files of 84...

      65% complete. Copied 55 files of 84...

      70% complete. Copied 59 files of 84...

      75% complete. Copied 63 files of 84...

      80% complete. Copied 68 files of 84...

      85% complete. Copied 72 files of 84...

      90% complete. Copied 76 files of 84...

      95% complete. Copied 80 files of 84...

      100% complete. Copied 84 files of 84...

       

      Character-set converting files...

       

        8 unified drivers merged.

       

      Patch merge completed successfully

       

      Please check the log file at /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/61/20190218_230727/apply/trnsrvr/admrgpch.log.

       

      Applying patch ADOP_MRG_20190218_1550502494:u_ad_2559622005.drv.

          Log: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/61/20190218_230727/apply/trnsrvr/ADOP_MRG_20190218_1550502494/log/u_ad_2559622005.log

       

      AutoPatch error:

      Please apply adgrants.sql file in database tier before applying this patch

       

      You should check the file

      /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/61/20190218_230727/apply/trnsrvr/ADOP_MRG_20190218_1550502494/log/u_ad_2559622005.log

       

      for errors.

       

          [UNEXPECTED]Error occurred executing "adpatch  workers=4      console=no interactive=no  defaultsfile=/u02/appv1228/V1228/fs2/EBSapps/appl/admin/V1228_patch/adalldefaults.txt patchtop=/u02/appv1228/V1228/fs1/EBSapps/appl/admin/V1228/log/ADOP_MRG_20190218_1550502494 driver=u_ad_2559622005.drv logfile=u_ad_2559622005.log"

          [UNEXPECTED]Refer to the log files for more information.

          [UNEXPECTED]Apply phase has failed.

       

       

      [STATEMENT] Please run adopscanlog utility, using the command

       

      "adopscanlog -latest=yes"

       

      to get the list of the log files along with snippet of the error message corresponding to each log file.

       

       

      adop exiting with status = 1 (Fail)

       

       

      Please help....

       

      Kind regards,

      jc

        • 1. Re: Applying the Latest AD and TXK
          mdtaylor

          Hi jc,

           

          Please review step 5 in section C: Apply Patch 27254132:R12.AD.C (plus any additional critical patches – see note box).

           

          Patch 27254132:R12.AD.C is applied separately from the critical AD patches and cannot be merged together in the same adop apply session.

           

          Regards,

          Michael

          • 2. Re: Applying the Latest AD and TXK
            Beauty_and_dBest

            Thanks Michael,

             

            I am just confused with note 1617461.1

             

            In

            3.3 Path C — Existing Release 12.2 customers (at AD-TXK Delta 10 codelevel)

             

             

            It says above it can be merged?

             

             

            Kind regards,

            • 3. Re: Applying the Latest AD and TXK
              mdtaylor

              Hi jc,

               

              No.  In step 5, you apply Patch 27254132:R12.AD.C  alone, then apply the next AD critical patches in the same adop session but in a second adop phase=apply session.

               

              Regards,

              Michael

              • 4. Re: Applying the Latest AD and TXK
                Beauty_and_dBest

                Thanks Michael

                 

                for bearing and being patient with my poor reading compre

                 

                I will that  again....brb

                • 5. Re: Applying the Latest AD and TXK
                  Beauty_and_dBest

                  Hi Micheal,

                   

                  I was able to apply patches 1 by 1  starting with 27254132,

                  the next below

                  28394214,

                  27638770,

                  28714940,

                  27868573,

                  28986462,

                  28882245,

                   

                  But on the last one below, it failed

                  28426427

                   

                  Applying patch 28426427.

                      Log: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/62/20190219_130935/apply/trnsrvr/28426427/log/u28426427.log

                   

                  AutoPatch error:

                  Please apply adgrants.sql file in database tier before applying this patch

                   

                  You should check the file

                  /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/62/20190219_130935/apply/trnsrvr/28426427/log/u28426427.log

                   

                  for errors.

                   

                      [UNEXPECTED]Error occurred executing "adpatch  workers=4      console=no interactive=no  defaultsfile=/u02/appv1228/V1228/fs2/EBSapps/appl/admin/V1228_patch/adalldefaults.txt patchtop=/u01/PATCH/AD_TXK/28426427 driver=u28426427.drv logfile=u28426427.log"

                      [UNEXPECTED]Refer to the log files for more information.

                      [UNEXPECTED]Apply phase has failed.

                   

                   

                  [STATEMENT] Please run adopscanlog utility, using the command

                   

                  "adopscanlog -latest=yes"

                   

                  to get the list of the log files along with snippet of the error message corresponding to each log file.

                   

                   

                  adop exiting with status = 1 (Fail)

                   

                  AutoPatch error:

                  Please apply adgrants.sql file in database tier before applying this patch

                   

                  You should check the file

                  /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/62/20190219_130935/apply/trnsrvr/28426427/log/u28426427.log

                   

                   

                   

                  I have already run adgrants for patch Patch 27868573:R12.AD.Cwhich includes the latest version of adgrants.

                   

                  But this patch has the latest adgrants contrary to 27868573

                   

                  Is it okay to run adgrants and restart  this patch? I have one more patch to go

                  I  run its adgrant but I have error:

                   

                  The following ERRORS and WARNINGS have been encountered during this adgrants session:

                   

                   

                  TIME_STAMP           SESSION_ID LOG_MODULE                                 LOG_LEVEL

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

                  LOG_MESSAGE

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

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_CURRENT_STATUS" to "SYSTEM" with grant option

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_CURRENT_STATUS" to "APPS"

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_DEBUG" to "SYSTEM" with grant option

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_DEBUG" to "APPS"

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS" to "SYSTEM" with grant option

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS" to "APPS"

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS$" to "SYSTEM" with grant option

                   

                  2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS$" to "APPS"

                   

                  2019/02/19 13:36:22         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on "DBMS_SCHEMA_COPY" to "SYSTEM" with grant option

                   

                  2019/02/19 13:36:22         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on "DBMS_SCHEMA_COPY" to "APPS"

                   

                  2019/02/19 13:36:23         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant WRITE on "DIRECTORY FND_DIAG_DIR" to "APPS"

                   

                  2019/02/19 13:36:23         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                  ORA-00942: table or view does not exist, SQL: grant READ on "DIRECTORY FND_DIAG_DIR" to "APPS"

                   

                   

                  12 rows selected.

                   

                   

                  Grants given by this script have been written to the ad_zd_logs table.

                   

                   

                  Please help....

                   

                   

                  Kind regards,

                  • 6. Re: Applying the Latest AD and TXK
                    Beauty_and_dBest

                    Hi Micheal,

                     

                    I was able to apply all AD and TXK patches even if there is error in adgrants.sql

                     

                    Now I am in CUTOVER phase, but I got error again below

                     

                    ================

                    Running stored cutover DDLs.

                        Log: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/62/20190219_142039/cutover/trnsrvr/log/cutover.log

                     

                    Loading JAR files into database.

                        No JAR files found to load

                     

                    Performing database cutover.

                        Log: @ADZDSHOWLOG.sql "2019/02/19 14:27:25"

                     

                    Reference of statement-handler is not-valid.

                     

                    DB-Handle Error Code: 28

                    DB-Handle Error Message: ORA-00028: your session has been killed (DBD ERROR: OCIStmtExecute/Describe)

                    Reference of statement-handler is not valid, attempting database reconnect

                    getConnNExec: Getting db-handler

                    getConnNExec: reattempting sql statement

                    getConnNExec: Returning 0E0

                    Statement Handler Error Code: 20001

                    Statement Handler Error Message: ORA-20001: Error while calling ad_zd_log.message(ad.bin.adop,WARNING,).ORA-01400: cannot insert NULL into ("APPLSYS"."AD_ZD_LOGS"."MESSAGE_TEXT")

                    ORA-06512: at line 6 (DBD ERROR: OCIStmtExecute)

                    Reference of statement-handler is valid, not attempting database reconnect.

                    Failed to execute SQL statement:

                                     declare

                                     begin

                                        ad_zd_log.message('ad.bin.adop','WARNING','','trnsrvr');

                                     exception

                                        when others then

                                           raise_application_error(-20001,'Error while calling ad_zd_log.message(ad.bin.adop,WARNING,).' || sqlerrm);

                                     end;

                     

                    Error Message:

                    ORA-20001: Error while calling ad_zd_log.message(ad.bin.adop,WARNING,).ORA-01400: cannot insert NULL into ("APPLSYS"."AD_ZD_LOGS"."MESSAGE_TEXT")

                    ORA-06512: at line 6 (DBD ERROR: OCIStmtExecute)

                    Error calling ad_zd_log.message to log messages to the database.

                    Please check if database is up

                     

                    [STATEMENT] Please run adopscanlog utility, using the command

                     

                    "adopscanlog -latest=yes"

                     

                    to get the list of the log files along with snippet of the error message corresponding to each log file.

                     

                     

                    adop exiting with status = 1 (Fail)

                     

                    ADOP (C.Delta.10)

                    Session Id: 62

                    Command: status

                    Output: /u02/appv1228/V1228/fs_ne/EBSapps/log/adop/62/20190219_145220/adzdshowstatus.out

                    ===============================================================

                    Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

                    trnsrvr         master     PREPARE         COMPLETED       2019/02/19 12:02:03  2019/02/19 12:07:00  0:04:57

                                               APPLY           COMPLETED       2019/02/19 12:39:47  2019/02/19 13:53:13  1:13:26

                                               FINALIZE        COMPLETED       2019/02/19 12:50:59  2019/02/19 14:16:28  1:25:29

                                               CUTOVER         RUNNING         2019/02/19 14:21:34                       0:30:51

                                               CLEANUP         NOT STARTED

                     

                     

                     

                    Cutover phase is pending running....

                     

                     

                    Please help.....

                     

                    Kind regards,

                    • 7. Re: Applying the Latest AD and TXK
                      Beauty_and_dBest

                      Hi Michael and ALL,

                       

                      I shutdown apps, and run again cutover and it all went successful

                      I completed my patching cycle up to fs_clone.

                       

                       

                      Many Thanks!!!

                       

                      By the way please help  how to resolve adgrants error below:

                       

                      TIME_STAMP           SESSION_ID LOG_MODULE                                 LOG_LEVEL

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

                      LOG_MESSAGE

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

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_CURRENT_STATUS" to "SYSTEM" with grant option

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_CURRENT_STATUS" to "APPS"

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_DEBUG" to "SYSTEM" with grant option

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_DEBUG" to "APPS"

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS" to "SYSTEM" with grant option

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS" to "APPS"

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS$" to "SYSTEM" with grant option

                       

                      2019/02/19 13:36:20         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant SELECT on "DBMS_UPG_STATUS$" to "APPS"

                       

                      2019/02/19 13:36:22         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on "DBMS_SCHEMA_COPY" to "SYSTEM" with grant option

                       

                      2019/02/19 13:36:22         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-04042: procedure, function, package, or package body does not exist, SQL: grant EXECUTE on "DBMS_SCHEMA_COPY" to "APPS"

                       

                      2019/02/19 13:36:23         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant WRITE on "DIRECTORY FND_DIAG_DIR" to "APPS"

                       

                      2019/02/19 13:36:23         153 ad.plsql.ad_zd_sys.GIVE_PRIVILEGE          WARNING

                      ORA-00942: table or view does not exist, SQL: grant READ on "DIRECTORY FND_DIAG_DIR" to "APPS"

                       

                       

                      12 rows selected.