Skip to main content

Patch 26834480: adgrants.sql execution gives WARNINGS

Patch 26834480: adgrants.sql execution gives WARNINGS

 For the patch 26834480, we have to run the adgrants.sql , after comparing the highest version of this file present in $APPL_TOP/admin and the patch directory. 

 The highest version of adgrants.sql has to be copied to database home

  $ORACLE_HOME/appsutil/admin directory

 The script will give the necessary grants and permissions and in the end, it will show warnings.

SQL> @adgrants.sql apps
Connected.

.
.
.
.
...........

.........



The following ERRORS and WARNINGS have been encountered during this adgrants session:
TIME_STAMP           SESSION_ID LOG_MODULE                                 LOG_LEVEL
-------------------- ---------- ------------------------------------------ ----------
LOG_MESSAGE
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2019/12/17 16:07:17          75 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/12/17 16:07:17          75 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/12/17 16:07:22          75 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/12/17 16:07:22          75 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"

Grants given by this script have been written to the ad_zd_logs table.
You can run $AD_TOP/sql/ADZDSHOWLOG.sql to produce a report showing these grants.
Commit complete.



SOLUTION:

These warnings can be ignored when running adgrants.sql.  If receiving these warnings system likely does not have dbvault enabled, which is not an EBS requirement. 
Reference:

Comments

Post a Comment

Popular posts from this blog

12.1.0 Grid Installation on Solaris 11.3 fails with ASM failed to start

Issue Description  We faced one issue, while installing the GI 12.1.0.1.0 on Solaris 11.3  ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM061908.log for details. 2020/12/02 18:19:17 CLSRSC-184: Configuration of ASM failed 2020/12/02 18:19:17 CLSRSC-258: Failed to configure and start ASM Died at /u01/app/12.1.0/grid_1/crs/install/crsinstall.pm line 1976. The command '/u01/app/12.1.0/grid_1/perl/bin/perl -I/u01/app/12.1.0/grid_1/perl/lib -I/u01/app/12.1.0/grid_1/crs/install /u01/app/12.1.0/grid_1/crs/install/rootcrs.pl ' execution failed This error is coming during root.sh execution on primary node. After checking the asmca logs, the error seen is as below: ========================== [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:156] SEVERE:method oracle.sysman.assistants.usmca.backend.USMInstance:configureLocalASM [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:157] ORA-27122: unable to protect memory [main] [ 2020-1...
Post a Comment
Read more

Health Check Script

Oracle Database Health Check Script Run this script has sysdba user or any user having DBA Role Change the spool file patch to correct directory. In this example it is set to  /export/home/oraprod/ $ cat Health_Check_Script.sql set pagesize 1100 SET MARKUP HTML ON SPOOL ON spool /export/home/oraprod/health_check_new.html set feedback off set linesize 200; set pages 50 set lines 1000 set pages 70 set heading on PROMPT================================================================ prompt PROMPT PROMPT Daily_Monitoring Checkup Report prompt ================================================================================================================================================= PROMPT REPORT DATE select to_char(sysdate,'DD-MON-YYYY:HH:MI:SS') "Report Run Date" from dual; prompt DATABASE NAME PROMPT ============== select instance_name,host_name,version,status from gv$instance ,v$database a; PROMPT DATABASE INFO PROMPT =============...
1 comment
Read more

12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory

 12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory While creating the stage area for 12.2 Installation, we face issue while running the buildstage.sh ....startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory Solution:  Please go to the path provided in the error log and check if the java is working fine with below command: java -version Generally this java is having some issues.   Install the jre 7 or jre 8 and copy the the jre at the same path by renaming old folder. It should work fine.  Now if your run the build command again, it should succeed.  Running command: /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java -classpath /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/emocmutl.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/ewt-3_4_22.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/share-1_1_18.jar:/u01/soft/ebs/star...
Post a Comment
Read more