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:
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