How to see view script from SQL Prompt?

SQL> set long 5000 

SQL> select text from user_views 
         where view_name='VW_INBOX_PO_GENERATED' ;

Remove Oracle table row lock

STEP 1:  To identify the SID for the table with the lock, you will use this system ID in a later query to get the serial number for the table row lock:

SQL> select * from dba_dml_locks;

SQL> select
   session_id
from
   dba_dml_locks
where
   name = 'EF_AP_BALANCE';

Output :

SID
___
607

STEP 2:  The next step is a script to find the Serial# for the table row lock :

SQL> select
   sid,
   serial#
from
   v$session
where
   sid in (
   select
      session_id
   from
      dba_dml_locks
   where
      name = 'F_AP_BALANCE');

Output :

SID SERIAL#
---- -------
607 1402

STEP 3:  Finally, we can use the "alter system" command to kill the session that is holding the table lock:

alter system kill session 'SID,SERIALl#';

SQL> alter system kill session '607,1402';

Clean FND_NODES table after cloning in Oracle APPS R11/R12

Why we need to clean FND_NODES table post cloning by firing

 EXEC FND_CONC_CLONE.SETUP.CLEAN ?

Ans
-----
Because this table contains the IP Addresses of the source servers (apps and db) and when you clone your target servers have different IP Addresses that need to be populated in FND_NODES table.

Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES 

How to Clean :
------------------

SQL> select node_name, node_mode, support_cp, support_web, support_admin,support_forms from FND_NODES;

NODE_NAME              N S S S S
-----------------------------------------------
TARGET                     O Y Y Y Y
SOURCE                     O Y Y Y Y


1) Always apply the latest cloning patches, to avoid all the bugs and fixes

2) SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
    COMMIT;
    EXIT;


3) Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,to repopulate the required system tables.



Note that step two will delete all data from system tables such as
FND_NODES, FND_OAM_CONTEXT_FILES, etc.


The correct information for the current system will be repopulated when AutoConfig is run.

Query for active users with v$session

select sesion.sid,
sesion.username,
optimizer_mode,
hash_value,
address,
cpu_time,
elapsed_time,
sql_text
from v$sqlarea sqlarea, v$session sesion
where sesion.sql_hash_value = sqlarea.hash_value
and sesion.sql_address = sqlarea.address
and sesion.username is not null


SQL> select a.sid, a.serial#, b.sql_text 2 from v$session a, v$sqlarea b 3 where a.sql_address=b.address 4 and a.username='APPS';

 SID         SERIAL#                     SQL_TEXT

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

 122         61521     select count(*) from gen_person where gen_person_id=95000

R12: Create Accounting Program Failed With xla_accounting_pkg.ValidateAAD. ORA-0000 Error Message

(Doc ID 1227207.1)

APPLIES TO:

Oracle Assets - Version 12.0.0 and later
Information in this document applies to any platform.
XLAACCUP - Create Accounting Program

SYMPTOMS

When attempting to run Create Accounting - Assets, the Accounting Program request (XLAACCUP) ends with the following error in the log file:-

ERROR
-----------------------
An internal error occurred. Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.ValidateAAD.

ORA-0000: normal, successful completion.
.
The application accounting definition Assets Standard Accounting* owned by Oracle is not validated. Please validate the application accounting definition or update the application accounting definitions contained in the subledger accounting method Standard Accrual*.
---------

*The names may vary from these standard names where a customer is using a different Subledger Accounting Method / Application Accounting Definition.

CAUSE

The Application Accounting Definition for Assets is invalid.

SOLUTION

1. Validate the AADs via the concurrent request XLAABACR Validate Application Accounting Definitions for module = Assets.

Note xlaapeng.pkb requires that all AADs on the application be valid, even if they aren't used.  

2. Confirm all Asset AADs are validate (view output in #1)

3.  Re-run Create Accounting - Assets.