How to enable Diagnostic option in EBS R12.2

 

 To enable Diagnostic option in EBS R12.2  perform the following steps.

Steps 1


Navigate to System Administrator responsibility> Profile> System>



Steps 2

Enter profile name: Utilities:Diagnostics

Application User for whom you want to enable Diagnostics and tick on user option -> Find



Steps 3


Set Yes at User level and Save the Changes. You can keep Yes at Site level also if you wish to enable this setting for all other application users. Click on save.



Steps 4


Now again, navigate to System Administrator responsibilityProfileSystem

Enter profile name: Hide Diagnostics menu entry

Enter Application User for whom you do not want to hide Diagnostics menu entry



Steps 5


Set No at User level and Save the Changes. If you wish to apply the same for all other application users, you can set No at site level.



Steps 6


Once done, Log off from application and relogin. Now you would be able to see Diagnostics option







How to change APPLSYSPUB password in EBS R 12.2

 

After implementing PASSWORD_LIFE_TIME TO 30 DAYS for default profile, applsyspub user’s password was expired after 30 days.

Following error is observed after logging in to application,

 





Solution:-

We altered the profile of APPLSYSPUB user from default to EBS_APPS and rested the password of APPLSYSPUB user.

SQL> SELECT USERNAME,ACCOUNT_STATUS,EXPIRY_DATE,PROFILE FROM DBA_USERS WHERE USERNAME='APPLSYSPUB';

USERNAME             ACCOUNT_STATUS       EXPIRY_DATE     PROFILE

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

APPLSYSPUB           EXPIRED              27-MAR-21       DEFAULT

 

SQL>  ALTER USER APPlSYSPUB PROFILE EBS_APPS;

 

User altered.

 

 

·       Shutdown application service.

 

[appltest@vm1test scripts]$ cd $ADMIN_SCRIPTS_HOME

[appltest@vm1test scripts]$ adstpal.sh

 

 

·       Reset APPLSYSPUB password using FNDCPASS OR AFPASSWD .

Note:- APPLSYSPUB password must be in UPPER CASE due to internal code dependencies.

[appltest@vm1test scripts]$ AFPASSWD -c APPS -o applsyspub

Enter the ORACLE password of Application Object Library 'APPSUSER':

Connected successfully to APPS.

Enter the password for your 'SYSTEM' ORACLE schema:

Enter the password for your 'SYSTEM' ORACLE schema:

Connected successfully to SYSTEM.

Log file: AFPWD_TEST_042697.log

Enter new password for user [applsyspub]:

Verify new password for user [applsyspub]:

 

 

 

·       Make following changes in application context file.

Take a backup of application context file.

 

[appltest@vm1test scripts]$ cp $CONTEXT_FILE  TEST_vm1test.xml_bkp

[appltest@vm1test scripts]$ vi $CONTEXT_FILE

Look for following parameter s_gwyuid and s_gwyuid_pass

 

Make changes like this

From

<GWYUID oa_var="s_gwyuid">APPLSYSPUB/PUB</GWYUID>

 

To

<GWYUID oa_var="s_gwyuid">APPLSYSPUB/NEWAPPLSYSPUBPASSWD</GWYUID>

 

From

 

<password oa_var="s_gwyuid_pass">PUB</password>

 

To

<password oa_var="s_gwyuid_pass"> NEWAPPLSYSPUBPASSWD </password>

 

·       Run autoconfig on application tier

[appltest@vm1test scripts]$ sh adautocfg.sh

 

 

·       Start application  and now error should be resolved.





Various OCI CLI command for OCI Object Storage administration



·       Command to create bucket

Syntax:

oci os bucket create --compartment-id <compartment id> --name <bucket name>

 

Example:

oci os bucket create --compartment-id ocid1.compartment.oc1..aaaaaaaacgen54z6eyimw7pnp4a553425kifsq --name TESTBUCKET

 

 

 

·       Command to delete bucket

Syntax :

oci os bucket delete --name <Bucket name>

 

Example :

oci os bucket delete --name TESTBUCKET

 

 

·       Command to list out all the objects inside a bucket

Syntax:

oci os object list --bucket-name < Bucket name >             

 

Example:

oci os object list --bucket-name TESTBUCKET     

 

·       Command to upload files inside a bucket.

Syntax:

oci os object put –bn <Bucket_Name> --name <uploaded file_name > --file<source file_name>

 

Example:

oci os object put -bn TESTBUCKET --name x.sql --file x.sql

 

·       Command to upload files inside a directory created under a bucket.

Syntax:

oci os object put –bn <Bucket Name> --name <Direcotry name/uploaded file name> --file <source file name>

 

Example:

oci os object put -bn TESTBUCKET --name Backup/x.sql --file x.sql

 

·       Command to Download files inside a bucket.

Syntax:

oci os object bulk-download –bn <Bucket Name> --download-dir <Path where file would be downloaded> --prefix <File which would be downloaded>

 

 

Example:

oci os object bulk-download -bn TESTBUCKET --download-dir /home/oracle --prefix x.sql

 

·       Command to Download files from a directory which is created under a bucket.

Syntax:

oci os object bulk-download –ns <Bucket namespace> -bn <Bucket Name> --download-dir

<Path where file would be downloaded> --prefix <Directory path/file name which would be downloaded>

 

Example:

oci os object bulk-download -ns bm1uufa0a -bn TESTBUCKET --download-dir /home/oracle --prefix Backup/x.sql

 

·       Command to delete file from bucket

Syntax:

oci os object delete -bn <Bucket Name> --object-name <Name of object to delete>

 

Example:

oci os object delete -bn TESTBUCKET --object-name t1.sql

 

·       Command to delete file from a folder residing inside bucket

Syntax:

oci os object delete -bn <Bucket Name> --object-name <Location from where file to be delete>

 

Example:

oci os object delete -bn TESTBUCKET --object-name Backup/x.sql

 

How to check AD and TXK code levels in EBS

We can use following query to get AD and TXK code level in EBS environment


SQL>col ABBREVIATION for a20

SQL>set lines 300

SQL>col NAME for a40

SQL>col CODELEVEL for a20 

SQL> SELECT ABBREVIATION,NAME,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in ('txk','ad');

 

ABBREVIATION         NAME                                     CODELEVEL

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

ad                   Applications DBA                                     C.10

txk                  Oracle Applications Technology Stack     C.10


Shell script to delete applied archive log from standby database

This script will run on standby database.

It will basically check for  applied archives on standby database and it will keep last 100's number of archives present and will delete rest of the archives that have been already applied. I have personally tested this script on my environment which is running on RHEL 7 and Database Ver 11.2.0.4. 

Warning:- Before running the script directly into Production Environment , please test it on a non production environment.


#Schedule this script on standby database server.

  vi /home/oracle/archive_del.sh

#!/bin/bash

ARCHLOG_DIR=/arch/prodtest/archivelog

 LogNo=`tail -3000 /db/prodtest/db/tech_st/11.2.0.4/admin/PRODTEST_ccuine103/diag/rdbms/prdtstdr/PRODTEST/trace/alert_PRODTEST.log | grep "Media Recovery Log" | cut -d " " -f 4 | cut -d "_" -f 2 | tail -1 `

echo "Oracle applied LogNo is $LogNo"

let SecLogNo=${LogNo}-100

echo "Archivelog is present from number : $SecLogNo"

echo "*****************************"

cd $ARCHLOG_DIR

for i in `ls *.arc`

do

Newi=`echo $i | cut -d "_" -f 2`

if [ "$Newi" -lt "$SecLogNo" ]; then

echo "$i to be deleted..."

rm -r $i

fi

done

 

 

Schedule to run for every 4 hours

[oracle@ccuine103 ~]$ crontab -l

0 */4 * * * /home/oracle/archive_del.sh