EBS R12 is supported in Multitenant mode for Oracle Database 19c. If you try to generate a tkprof to report explain plan generation on the Database, you will receive errors for the Invalid username /password in the trace file generated
tkprof test.trc test.txt sys=no explain=apps/apps sort=prsela,exeela,fchela
The reason for this is that the apps is the user in the PDB only. It is not a user in the CDB
If you try to set ORACLE_PDB_SID to remove this error, it will still give the same issues.
export ORACLE_PDB_SID=EBS
tkprof test.trc test.txt sys=no explain=apps/apps sort=prsela,exeela,fchela
The reason for that is ORACLE_PDB_SID supports login for sysdba only.
The correct way to do that would be to source the PDB environment or set the TNS_ADMIN to the PDB tnsnames
cd $ORACLE_HOME
. ./EBS_TECH.env
tkprof test.trc test.txt sys=no explain=apps/apps@EBS sort=prsela,exeela,fchela
or you can just set the TNS_ADMIN to that directory which has the PDB name in tnsnames.ora
export TNS_ADMIN=$ORACLE_HOME/network/admin/pdb_techgo
tkprof test.trc test.txt sys=no explain=apps/apps@EBS sort=prsela,exeela,fchela
or you can use the Easy Connect Syntax
tkprof test.trc test.txt sys=no explain=apps/apps@<hostname>:1521/EBS sort=prsela,exeela,fchela
I hope you find this useful. Please do provide feedback on this article on How to generate tkprof in EBS in 19c
Related Articles
How to enable trace in Oracle apps R12
sql tuning advisor: How to run sql tuning advisor for SQL_ID in the Cursor cache, how is the sql tuning task created and executed to get the recommendation
SQL trace: SQL trace or 10046 event is being used to trace the session activity in Oracle.
Autotrace in Oracle: Autotrace in Oracle, What is autotrace, how to set up it, Understanding Autotrace Output, Autotrace options, statistics displayed by autotrace
Hanganalyze: check out how to take system state dump in Oracle, hanganalyze in Oracle, what is v$wait_chains, and how it can help find the blocking
How to generate FRD trace in Oracle Apps: How to generate Forms runtime diagnostics trace in Oracle apps 11i/R12