How to generate Context File on the R12.2 Database -Tier

By -

 Step 1: The following environment variables must be set in order to run adbldxml.pl.

ORACLE_HOME

export ORACLE_HOME=<Physical Path, where the Oracle DB is installed>

ORACLE_SID

export ORACLE_SID=<name of the SID selected when you installed the DB>

PATH

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH

ORA_NLS10

export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

Ensure that the LD_LIBRARY_PATH environment variable is set correctly.

PERL5LIB needs to be set

export PERL5LIB=/u02/app/oracle/product/12.1.0/dbhome_3/perl/lib/5.16.3:/u02/app/oracle/product/12.1.0/dbhome_3/perl/lib/site_perl/5.16.3:/u02/app/oracle/product/12.1.0/dbhome_3/appsutil/perl

Finally set the TNS_ADMIN variable to point to $ORACLE_HOME/network/admin/<SID>_<hostname> :

export TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname>

Generating DB Context file

[oracle@vtebs1-lqhjl3 bin]$ perl adbldxml.pl jtop=/u02/app/oracle/product/12.1.0/dbhome_3/jdk/jre

Starting context file generation for db tier..

Using JVM from /u02/app/oracle/product/12.1.0/dbhome_3/jdk/jre/bin/java to execute java programs..

APPS Password:

The log file for this adbldxml session is located at:

/u02/app/oracle/product/12.1.0/dbhome_3/appsutil/log/adbldxml_06180709.log

AC-20010: Error: File - listener.ora could not be found at the location:

/u02/app/oracle/product/12.1.0/dbhome_3/network/admin/eraps1p/listener.ora

indicated by TNS_ADMIN. Context file can not be generated.

Could not Connect to the Database with the above parameters, Please answer the Questions below

Enter Hostname of Database server: vtebs1-lqhjl3

Enter Port of Database server: 1521

Enter SID of Database server: PROD

Enter the value for Display Variable:

Invalid input, reenter the value for Display Variable: ::1

The context file has been created at:

/u02/app/oracle/product/12.1.0/dbhome_3/appsutil/PROD_vtebs1-lqhjl3.xml

[oracle@vtebs1-lqhjl3 bin]$

Comments

Post a Comment

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

By -
We frequently encounter issues with concurrent programs running long and concurrent requests not picking up jobs. These problems are often expected from the development and functional team we need to address this issue To solve this, we should take the following steps: Collect below basis level of information to development team 1 Oracle seeded program/Custom program? 2 How much time it used earlier? 3 Is there any recent code change done in concurrent program? 4 Is this program fetching higher data compare to last run? 5 Does this job running any specific time/ It can be run any time? 6 Does this job fetching data using DB link? 7 Does the problem happen on both the test and production instance?   Troubleshooting Steps for Concurrent Requests Check for Locks and Blocking sessions Identify if the request is running but blocked by database locks/Blocking sessions. Use DBA tools or queries to identify and release locks if necessary. Review Parameters and Data ...
Read more

How to run Gather Schema Statistics in R12.2

By -
Image
What is Gather Schema Statistics? Gather Schema Statistics program generates statistics that quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. The cost-based optimization (CBO)  uses these statistics to calculate the selectivity of prediction and to estimate the cost of each execution plan. Why Run the Gather Schema Statistics? When Data is update, insert, delete in table of user end Like (Technical User ,Finance User ,Ect) It become necessary to run the Gather Schema Statistics It’s recommended to Run GSS in Weekly Once or twice. How to run Gather Schema Statistics? Login application with sysadmin user Submit Request Window Navigate to: Concurrent > Requests Enter the parameters This can be run for specific schemas by specifying the schema name or enter ‘ALL’ to gather statistics for every schema in the database Submit the Gather Schema Statistics program Parameters: S...
Read more

How to clear weblogic stuck threads in R12.2

By -
Web logic stuck threads Overview   What is stuck threads in weblogic server? Stuck threads are  long running threads and It means thread has been running longer predefined timeout.   What stuck threads will do? A thread might get stuck for various reasons.   Example :  When an SQL query is running and the time it takes to complete is say 800 seconds, then, as the default stuck thread timing is 600 seconds in WebLogic Server, the thread allocated for that query waits for 600 seconds and goes to stuck state. Then managed server status showing waning state   How to troubleshoot the stuck threads in EBS instance? Stuck threads will reduce the ebs performance and it’s very important activity to DBA’s Step 1: Go to the weblogic console and check for managed server status like oacore Step 2: if It will show the oacore server in “warning state” then we need to check   Scenario 1: Every alert we need to check the log file and investigate based on the log ...
Read more