TEMP Tablespace Users Usage

select username,sum(blocks*16384)/1048576 MB from gv$sort_usage group by username;

Table Level Privileges

Table Level Privileges

select owner, table_name, privilege, grantee from dba_tab_privs where owner='EBS_OBJ'

and table_name in ('SUBSCRIPTION_AGREEMENTS','SUBSCRIPTION_ITEMS') and grantee = 'CDS_MIGRATOR_USR';

OWNER                          TABLE_NAME                     PRIVILEGE                                GRANTEE
------------------------------ ------------------------------ ---------------------------------------- -------------------
EBS_OBJ                        SUBSCRIPTION_AGREEMENTS        SELECT                                   CDS_MIGRATOR_USR
EBS_OBJ                        SUBSCRIPTION_ITEMS             SELECT                                   CDS_MIGRATOR_USR

User Creation(Mirror Ram Account)

User Creation(Mirror Ram Account)

select username,DEFAULT_TABLESPACE,TEMPORARY_TABLESPACE,PROFILE  from dba_users where username like upper('ram');

 

USERNAME                       DEFAULT_TABLESPACE             TEMPORARY_TABLESPACE           PROFILE
------------------------------ ------------------------------ ------------------------------ ------------------------------
RAM                       USERS                          TEMP                           SECURITY

 

CREATE USER seetha IDENTIFIED BY welcome#1 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE temp quota unlimited on USERS PROFILE SECURITY;

 

 

 

nram> select * from dba_role_privs where grantee=upper('ram');

How to Determine the SQL_ID for a SQL Statement

How to identify the SQL_ID of a statement:

The SQL_ID of a statement can be found in an AWR or ASH report or by selecting it from the database data dictionary using the V$SQL view. 

If the SQL can be identified with a particular identifiable string or by some kind of unique comment such as: /* TARGET SQL */ then this will make it easier to locate. 

For Example:

SELECT /* TARGET SQL */ * FROM dual;

SELECT sql_id, plan_hash_value, substr(sql_text,1,40) sql_text  

FROM  v$sql 

WHERE sql_text like 'SELECT /* TARGET SQL */%'

SQL_ID        SQL_TEXT

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

0xzhrtn5gkpjs SELECT /* TARGET SQL */ * FROM dual

The hash_value is included here for convenience. You can also find the SQL_ID in the V$SQL view using a substitution variable:

SELECT sql_id, plan_hash_value, SUBSTR(sql_text,1,40) Text

FROM v$sql

WHERE sql_text LIKE '%&An_Identifiable_String%';

If SQL is not available in v$sql, DBA_HIST_SQLTEXT and DBA_HIST_SQLSTAT can be used:

select t.sql_id,

    t.sql_text,

    s.executions_total,

    s.elapsed_time_total

from DBA_HIST_SQLSTAT s, DBA_HIST_SQLTEXT t

where s.snap_id between 333 and 350;   <====use snapid in which the query was ran

How do you change the SYSADMIN password?

1. Keep all services running.
2. Login via the OS level by way of the applmgr user.
3. Run your environment scripts
    a. cd $APPL_TOP
    b. run APPSORA.env
    c. the above should also run <sid>_<node>.env, but you can verify by running it.
    d. cd admin
    e. run adovars.env
4. cd $FND_TOP/bin
5. Run FNDCPASS to change the SYSADMIN password 
(IMPORTANT: Change ONLY the SYSADMIN password) 
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN <New Password> 
6. Restart the Apache, Forms, Reports, 8.0.6 listener and concurrent manager services. 
7. To test, login into the applications as the SYSADMIN user and the new password. 
8. Verify that a concurrent program such as Active Users runs.

Critical Patch Updates:

Critical Patch Updates are collections of security fixes for Oracle products. They are available to customers with valid support contracts. They are released on the Tuesday closest to the 17th day of January, April, July and October. The next four dates are:

• 16 January 2018
• 17 April 2018
• 17 July 2018
• 16 October 2018

CPU Cumulative:

Oracle tries to make Critical Patch Updates cumulative; that is each Critical Patch Update contains the security fixes from all previous Critical Patch Updates. In practical terms, for those products that receive cumulative fixes, the latest Critical Patch Update is the only one that needs to be applied when solely using these products, as it contains all required fixes.

select * from sys.registry$history;

ACTION_TIME                         ACTION                         NAMESPACE                      VERSION                 ID COMMENTS

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

31-AUG-12 05.04.39.313477 PM        VIEW INVALIDATE                                                                  8289601 view invalidation

31-AUG-12 05.04.39.610749 PM        UPGRADE                        SERVER                         11.2.0.3.0                 Upgraded from 11.2.0.1.0

Thank you, Ram