Oracle APPS DBA

1. DB Components:

Oracle_Home
Oracle Home contain oracle softwre binaries , Database utilities (SQLPLUS,TNSPING,EXPDP,IMPDB,DBCA,LSNRCTL
etc).
Configuration files: Networkfiles (listener.ora,tnsnames.ora,sqlnet.ora)
Patching utilities (Opatch utilities)
Log and Diagnostic files
Java and PL/SQL componens
Libraries and modules ( which supports oracle specific functionalities)
Directory structure inside Oracle_Home:
Bin/ executables like>>lsnrctl,sqlplus
Network/admin/: tnsnme.ora,listener.ora
Dba/:db initialisation parameters
Rdbms/:core db engine files and libraries
Lib/:shred libraries
Log/:log from oracleinstaller or tools.
Opatch/:tools for applying patches.

CDB & PDB

1.Difference between 12c vs 19c?
A: Oracle provided several enhancement feature compare with 12c.
1.Automtic indexing 2. High frequency statistic gathering 3. Performance enhancement 4. Automatic flashback of
standby 5.data guard enhancement 6. Multitenant improvement like (3 pdbs without licensing) 7. Enabled Dataguard
for individual pdb instead of entire CDB.

2.Difference between 8i, 9i, 10g, 11g and 12c databases as per your experience.
A: Differences Between Oracle Versions:
8i: Introduced Internet features, Java in the database, and Query Cache.
9i: Added Real Application Clusters (RAC), XML support, and automated undo management.
10g: Introduced Grid computing, Automatic Storage Management (ASM), and AWR/ADDM.
11g: Added Active Data Guard, SQL Plan Management, and better compression techniques.
12c: Introduced Multitenant Architecture (PDB/CDB), In-Memory Option, and JSON support.
Each version enhanced scalability, performance, and manageability, with 12c focusing on cloud readiness and
multitenancy.

3.What is CDB? Relation with Instance?

A: CDB is container database architecture introduced in 12c. It allows multiple pluggable databases to reside within
single physical database.
Instance is a set of memory structure and Backgroup processes. Instance provides the compute engine to for
manging CDB and pdb operations.
1.A single CDB contain multiple pdbs. All of them share same resources of CDB.
2.One instance serves one CDB in Non-Rac environment. But in RAC environment multiple instances serve single CDB.
CDB And Instance.
3.One instance can have only one CDB.

4. Instance and its components?

A: Instance is a set of memory and background processes.
Instance: Memory (SGA, PGA) Background processes (SMON, PMON, DBWr, LGWr, CKPT, ARC)
SGA: This a shared memory region allocated when an oracle instance starts. This is essential for ensuring fast and
concurrent access to data by multiple users and processes.
This SGA is shared to all the oracle processes.
It improves the performance by caching frequently used data, reduce disk I/O, facilitate efficient memory sharing
among processes.
PGA: This a memory region used by oracle database to store specific data. PGA is private to a single session and is not
shared among other sessions. It is used to manage memory for a specific user process. It enables efficient execution
of SQL queries and other database operation.
These are managed by AMM (automatic memory management). The PGA size is adjusted based on the number of
sessions and workload.
We can use PGA_AGGREGATE_TRGET parameter to manage the memory.
Background processes:
DBWR: This is an important background process of oracle database for writing modified data blocks (also called dirty
blocks) from the database buffer cache to datafiles. Helps buffer cache to free up the space.
When the changes are made to the DB they are first written to the redo log buffer and then flushed to the disk by
LGWR. The actual data changed are written by DBWR.
Checkpoint: It is responsible for manging the checkpoint operation, which ensures that the data in the databse files is
synchronised with the information in the redo log files. This is a critical operation in ensuring data consistency and
durability during recovery process. It inform the DBWR to flush the modified blocks from buffer cache to data files.
Maintain the synchronization between datafiles and redologfiles.

Checkpoint & SCN:

Checkpoint process record a SCN (system change number) in the data file header, which indicates the point in time
when the checkpoint occure.
Crash recory:
It helps in crash recovery. Oracle uses SCN from the lst checkpoint to determine which changes need to be rolled
back.
ARC: This is responsible for the archiving online redolog file to the disk. Once the logfile is full it switches to the next
logfile. It ensure the changed made to the database are saved for recovery. This is only enabled when the DB
running on ARCHIVELOG mode.
In Data guard or RAC, the ARC process helps to transfer redo logs between primary and standby database, ensure the
stndby database always synchronization with primary and can take over in case of failure.
LGWR: This writes the redo log entries from the redo log buffer in memory to the online redolog files on disk. This
ensures durability properties of ACID (Atomicity, consistency, isolation, durability principles).

Why LGWR writes before DBWR writes? (imp)

In general, transaction recording is more important than transaction execution. Lets take, if we have redo entries
on disk and suddenly power failure happens (the dirty blocks are not yet written to disk). Then oracle can still
recover the transactions by reading the redologs on disk. This way first redo logs are made permanent and then dirty
blocks are written to disk.

Difference between PFILE and SPFILE?

Initialization parameters required by the oracle instance to control the various aspects of the db such as memory
allocation, logging, file location and other important configurations.
Pfile: This file commonly used for starting up an oracle instance in environment where a spfile is not available or
manual configuration are required.
1.Content in pfile is human readable. We can manually edit the file.
2. it is located in the $ORACLE_HOME/dba directory.
3.It needs db restart to apply changes.
Key Parameters in pfile:
DB_NME:
SGA_TARGET:
PGA_AGGREGATE_TARGET:
CONTROL_FILE:
UNDO_TABLESPACE:
LOG_ARCHIVE_DESTINTION:
SPFILE:
 This is a server parameter file. It is a binary file that stores initialization parameters.
 Spfile acts as the primary configuration source for the oracle instance start.
 We can dynamically do the changes to spfile when running with Alter System command
 When db restarted it automatically read the spfile.
 In RAC it is shared among all the oracle instances which running on the same host or in RAC. It ensure all the
nodes have same parameter file.
 It can be easily backup using RMAN.

Physical files : Control file , datafiles , redolog files

Logical storage structure
Type of DB status (Nomount, Mount, Open)
Types of startup (Immediate, Normal, Abort)
Network components (listener.ora, tnsnames.ora)
User creation (types of privileges, etc)
Tablespace creation
Types of default tablespace (system,sysaux,temp,user)
SCOP parameter
Types of log files (redo log, alerts logs, aarchive logs)
Backup and restore (senarious, retention concept)
Data guard concept
Standby setup
DR Setup
SQL & Performance issue

2. Cloning (DB & APPL):

7.What is fs_clone and how is it used? (Imp)

A: fs_clone is a utility used in Oracle E-Business Suite (EBS) 12.2 to synchronize the run file system and the
patch file system. It ensures both file systems are identical, which is crucial for online patching to function
correctly.
How It Is Used:
1. Run fs_clone: Execute the adop phase=fs_clone command after an online patching cycle.
2. Purpose: Copies changes from the run file system to the patch file system or vice versa to
maintain consistency.
3. When to Use: Typically after completing a patching cycle (e.g., after cleanup).
This maintains the dual-file system model necessary for online patching.
r
17.Explain the cloning process? (both application and database)?
A: DB Cloning:
1.prepare the target db : run adpreclone.pl on source system
2.Take backup of Target db
3.Copy the backup and perform the restore and recovery process.
4.run adcfgclone.pl on target DB
 5. If we have EBS integration, we have to run autoconfig.sh after the cloning

Application cloning:
1. Stop the application server
2. Run adpreclone.pl on source application tier. (it create necessary cloning
template)
3. Backup the application tier – filesystem and database.
4. Restore the application files on the target.
5. Run adcfgclone.pl on target system
6. Run autoconfig to apply configurations.
7. Start the application
8. Run gather stat schema
9. Do the application validations.

44. What is autoconfig? (imp)

Autoconfig is a utility that is used to maintain the application environment and configuration files.
1. It stores configuration files in a context file .xml
2. Automaticlly apply them to relevant configurations (.conf, .env, .xml)
3. Ensure consistency in multimode environment
4. During patching : It adjust the the cloned environment by updating configuration files with target
specific vlues.
5. We can use after cloning and EBS environment.
6. We can use after patching that require configuration updates.

45. What are the parameters autoconfig will ask for?

Context file name and apps password

46. What is a context file?

Context file is a central repository, which stores all application configuration information.
The name is like _ .xml

47. How you will find auto-config is enabled/not for u r applications?

Open any env / configuration files, the first `few lines will tell u that these files are maintained by
autoconfig.2. If contextname.xml file is there in APPL_TOP/admin

48. How autoconfig will create env and configuration files? imp
Autoconfig will go to each and every top template directory take the templates from there and fill the
values from the XML file and create the required files.

49. In how many phases autoconfig will run?

Autoconfig will run in 3 phases.
1. INIT – Instantiate the drivers and templates
2. SETUP – Fill the templated with values from XML and create files
3. PROFILE – Update the profile values in the database.

50. What is the location of adconfig log file?

APPL_TOP/admin//log/

51. Is it possible to restore an auto-config run? (imp)

Adconfig will create a restore.sh script at $APPL_TOP/admin//out/. This restore.sh will copy the backed-up
files before autoconfig run to its original locations.
But the profile values updated in the database can’t be restored back.

Purpose of Txkcggutlfildir.pl when coning?

A:

52. How to run auto-config in test mode?

adchkcfg.sh script at AD_TOP/bin. This script will run auto-config in test mode and create the difference
file which tells us what is going to change when u actually run autoconfig.

53. How to find auto-config is enabled or not for the database?

Ans: If we have appsutil directory under RDBMS_ORACLE_HOME

In how many phases autoconfig will run? (Imp)

A: AutoConfig in Oracle E-Business Suite runs in four phases:

1. Pre-configure Phase: Prepares the environment and checks for required settings.
2. Configure Phase: Configures various system components (e.g., database, application, etc.).
3. Post-configure Phase: Completes the configuration and applies the changes.
4. Clean-up Phase: Cleans up temporary files and restores the environment.

What are the parameters autoconfig will ask for? (imp)

When running AutoConfig, it will ask for several key parameters based on your environment. These parameters
typically include:

1. SID (System Identifier): The database instance name.

2. Hostname: The name of the server where the application is running.
3. Oracle Home: The directory where Oracle software is installed.
4. Apps Password: The password for Oracle Applications.
5. Context File: The name and location of the context file (typically named appsprefix_.xml).
6. Listener Name: The listener for connecting to the database.
7. DB Name: The name of the Oracle database.
8. Application Tier: Whether it’s an application server or database server.
9. File System Locations: For logs, temporary directories, and configuration files.

These parameters allow AutoConfig to configure the Oracle E-Business Suite environment according to your specific
setup.

19.When do we run FND_CONC_CLONE.SETUP_CLEAN?

A: You run the FND_CONC_CLONE.SETUP_CLEAN script after cloning an Oracle E-Business Suite instance to
clean up and reset any residual configurations or settings related to concurrent managers.
This script is typically used after performing a clone and is necessary to ensure that the cloned
environment is correctly set up for new configurations and to avoid issues with running concurrent
requests.
It should be executed on the target system after the clone process is completed.
EXEC FND_CONC_CLONE.SETUP_CLEAN

4. You are cloning an Oracle EBS environment, and AutoConfig fails. How do you diagnose
and fix this issue?
A: Reason for autoconfig.sh failure
1.Missing environment variables
2. incorrect path and permissions in configuration files
3. Chances of context file.xml may not generate properly.
Diagosis:
1.chack autoconfig.log for error
2. I will check the contect file is properly generated or not
3. will check the template file consistency

After checking these all, add missing paths and proper permissions: again, will rerun autoconfig.sh

What is invalid object in Oracle? (Imp)

A: An invalid object in Oracle refers to database objects (like views, triggers, or procedures) that are not
compiled or executed successfully.
This can happen after schema changes, database upgrades, or missing dependencies. Invalid objects can
be identified with DBA_OBJECTS and need recompilation using ALTER or utlrp.sql.
To check for invalid objects in Oracle, you can use the following query:
-------------------------------------------------------------------------
SELECT object_name, object_type, status
FROM all_objects
WHERE status = 'INVALID';

One of the concurrent server node is not running after cloning? How to check and resolve the issue?

3. Patching (DB & APPL):

1. How you apply a patch? ADPATCH & Online patching(ADOP)
Using Adpatch , ADOP (12.2 plus)
ADPATCH (12.1 ) ADOP (12.2+)
2. Login as a apps user Online patching so no need to stop any services
3. Stop all appl services 1.Download the patch and ready to place in
4. Use adadmin.sh for changing the pplication patch_top
mode to maintenance mode (5) 2. adop phase = prepare or run prepare.sh
 5. Enable it 2. Now run :patch]$ cd 123456
6. Now check invalid object. 123456] adop phase = apply patches = 123456
7. Download and unzip the patch file Apps psw, wbl psw, sys psw
8. Cd 123456 After successful apply second one
9. 123456] adpatch (it will apply patch) 3.adop phase = finalize or finalize.sh (Ensure patch
10. Now 123456] adadmin edition is complete and ready for cutover)
11. Disable the maintenance mode 4.adop phase = cutover (Convert patch to run)
12. Recheck invalids 5.adop phase = cleaanup (Delete obsoletes)
13. Start the services 5. start services.
Use
ps -ef | grep appledev Do the validation
Ps -ef | grep tns
Ps -ef | grep PMON
Ps -ef | grep FNDLIBR

1. I am applying a patch, can I open another session and run adadmin?

Yes, We can run unless you are running a process where workers are involved

2. I am applying a patch, can I open another session in another node and run adpatch?
(imp)
No, because it will create tables while running the first session when you start the 2nd session it will fail
due to the first
5. How to find opatch Version? For DB patch
Opatch is a utility to apply database patch, In order to find opatch version
execute”$ORACLE_HOME/OPatch/opatch version”
You can check OPatch -lsinventory

8. What is a patch?
A patch can be a solution for a bug/it can be a new feature.

AD and TXK Patches?

10. How do you determine the pre-requisite patches before applying a patch?
A: Determining Pre-Requisite Patches Before Applying a Patch:
• Patch Documentation: Review the patch README and Oracle support documentation to
identify prerequisite patches.
• Oracle Support (My Oracle Support): Use Patch Wizard on Oracle Support to find
recommended and required patches for your environment.
• AD Check: Run adpatch or adadmin to check the current patch level and identify any
missing prerequisite patches.
• Patch Dependency Check: Verify dependencies in the patch README file, including
minimum versions for Oracle EBS, database, and OS versions.

25. How do you resolve patch conflicts in EBS?

A: Resolving Patch Conflicts in EBS:
• Review README: Check the patch documentation for known conflicts.
 • AD Utilities: Use ADPatch and ADAdmin utilities to identify patch conflicts before applying
them.
• Patch Sequence: Follow the patching order suggested by Oracle and resolve any issues in
staging before applying in production.
Login as APPS user
$ $AD_TOP/admin/scripts/adpatch =check

$ $AD_TOP/ADMIN_TOP/dmin/scripts/ADAdmin
Choose : patch conflict check option
This generate report. review the report for any conflict.

What is a consolidated patch?

It is a collection of multiple patches bundle together into a single patch
Combines fixes for different bugs, security patches etc
Reduce the need to apply multiple patches individually saving time and effort.

17. How you will find whether a patch is applied/not? Iin 12.2.9 (imp)
SELECT bug_number FROM ad_bugs WHERE bug_number = “Patch number”;

18. What is the other table where you can query what are the patches applied? (IMP)
A: SELECT patch_name, applied_date FROM ad_applied_patches ORDER BY applied_date DESC;

19. What is the difference between ad_bugs and ad_applied_patches?

A patch can deliver a solution for more than one bug, so ad_applied_patches may not give u the perfect
information as in the case of ad_bugs.

22. What is the table you are ad patch will create and when? (imp) in adptch
A patch will create FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table when it will apply d,g, and u
drivers

23. What is the significance of the FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table? (imp)
FND_INSTALL_PROCESSES table will store the worker information like what job is assigned to which worker
and its status.
AD_DEFERRED_JOBS will come into the picture when some worker is failed, it will be moved to
AD_DEFERRED_JOBS table, from where again adpatch will take that job and try to resign, after doing this 3
times if still that worker is failing, then adpatch will stop patching and throw the error that particular
worker has failed. We need to troubleshoot and restart the worker.

25. While applying an application patch is that necessary that your database and listener should be up?
(imp)
Yes. why because adpatch will connect to the database and update so many tables etc…..

26. While applying a patch if that patch is failing because of a pre-req then how you will
apply that pre-req patch and resume with the current patch? (Imp)
We need to take the backup of FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS tables and restart the
directory at APPL_TOP/admin/SID and then use adctrl to quit all the workers. Then apply the pre-req
patch, after that rename u r restart directory to its original name, and create FND_INSTALL_PROCESSES
and AD_DEFERRED_JOBS tables from the backup tables. Start adpatch session and take the options want
to continue the previous session.

24. If it is a multinode installation which driver we need to apply on which node?

c,d,g on concurrent node and c, g on web node. If it is a u-driver we need to apply it on all nodes.

27. What is adctrl?

Adctrl is one of the adutilities, which is used to check the status of workers and to manage the workers.

What is worker in terms of Oracle EBS?

Worker is a background processes used during patching and this is managed by adpatch utility.

28. Can you name some of the menu options in adctrl?

Check the status of workers, tell the manager that the worker has quieted, restart a failed worker, etc….

29. How to skip a worker and why?

We can skip a worker using option 8 in actual which is hidden. We will go for skipping a worker when we
have executed the job which the worker is supposed to do.

30. How adpatch knows what are the pre-reqs for the patch to which it is applying? (imp)
With every patch a file called b.ldt file will be delivered which contains the pre-req information. adpatch
load this into the database using FNDLOAD and check, whether those pre-req patches were applied or not.

31. What is FNDLOAD?

FNDLOAD is a utility that is similar to SQL loader but loads code objects into the database, whereas SQL
LOADER loads data objects into the database.

32. What c-driver will do?

C-drive copies the files from the patch unzipped directory to the required location in your application file
system. Before copying it will check the file version of the existing file at the file system with the file version
of the file in the patch. If the patch file version is higher than what it is at the file system level then only the
c-driver will copy that files.

33. How adpatch will know the file versions of the patch delivered files? Imp
With each patch, a file with the name f.ldt is delivered, which contains the file versions of the files
delivered with the patch. Adpatch will use this file to compare the file versions of files it delivering with the
file on the file system.

Explore Latest Article on Oracle Performance Tuning Interview Questions that help you grab high-paying
jobs
34. What is the adpatch log file location? Imp
APPL_TOP/admin/SID/log

35. What are the worker log file name and its location?
adwork01,adwork02…… and location is APPL_TOP/admin/SID/log
36. How you will know what are files the patch is going to change just by unzipping the patch?
When u unzip a patch it will keep all the files related to a particular product under that directory inside u r
patch directory for example if the patch derectory files related to the FND product then it will create a
subdirectory under the patch directory with the name FND in which it will put all related files to that
product

37. What is the significance of the backup directory under your patch directory?
When we apply a patch it will keep the copy of the files which it's going to change in the file system.

38. What are the different modes you can run your adpatch?
1. Pre install mode– default mode – used to update AD utilities. – adpatch preinstall=y
2. Non-interactive – Use defaults files to store prompt values -
(adpatch defaultsfile= interactive=no)
3.Test – Without actually applying a patch just to check what doing. (adpatch apply=no)

3. Is there any downtime in Online Patching? (imp)

A: Yes, Oracle patching may require downtime depending on the type of patch and the system
Adpatch – entire patching
ADOP – Only during cutover

4.Does Online Patching require the 11gR2 Oracle Database Edition Based Redefinition
(EBR) feature?
AA: Yes, Online Patching in Oracle E-Business Suite 12.2 requires the 11gR2 Oracle Database Edition-Based
Redefinition (EBR) feature.
EBR enables the use of multiple editions in the database, allowing patching to occur in a separate edition
while the current edition remains available for users.
This capability is fundamental to Oracle’s online patching model, as it minimizes downtime by isolating
changes until they are ready for deployment during the cutover phase.

5. How do I apply Oracle Fusion Middle-ware patches in Oracle E-Business Suite Release
12.2?
A: To apply Oracle Fusion Middleware (FMW) patches in Oracle E-Business Suite Release 12.2, follow these
general steps:

1. Review Documentation: Check the patch README for prerequisites and instructions.
2. Backup: Take a complete backup of your environment, including FMW and the database.
3. Prepare Environment: Stop services and set up environment variables for patching.
4. Apply Patches: Use the OPatch utility to apply the patches to the FMW components.
5. Verify and Restart: Verify the patch application, restart services, and check functionality.

Always consult the official patch documentation for specific guidance.

8. How do I apply or patch my customizations in Oracle E-Business Suite Release 12.2?

(imp) ?
A: we are using online patching in 12.2
1. Package your customization into a patch (like forms,report,workfloe etc) using adtools.
2. Ensure file should placed at appropriate custom top directory. $CUSTOM_TOP
3. It should compliance with EBR.
4. always try to test non production env
5. Now start the patching: ADOP
ADOP PHASE = PREPARE
ADOP PHASE = APPLY PATCH =
ADOP PHASE = FINALIZE
ADOP PHASE = CUTOVER
Start the application
ADOP PHASE = CLEANUP

9.If custom code is installed on a separate database schema, do I have to edition-enable

my custom database schema? (IMP)
A: Yes, if custom code resides in a separate database schema and the schema contains objects modified
during patching, it must be edition-enabled to support Oracle E-Business Suite’s Edition-Based Redefinition
(EBR). This ensures smooth online patching.

20.what are the tables were created when you run adpatch?
A: When you run adpatch in Oracle E-Business Suite, several key tables are created or updated to manage
patching activities:
1. FND_CONCURRENT_REQUESTS – Tracks concurrent requests.
2. FND_CONCURRENT_PROGRAMS – Stores information about concurrent programs.
3. FND_LOAD_FILES – Manages files loaded during patches.
4. FND_PRODUCT_GROUPS – Defines product groupings.
5. FND_PATCH_HISTORY – Records patch history.
These tables help manage and log patching activities and ensure consistency throughout the process.

22. what are the tables were created when we run adop?
A: After running adop (Oracle E-Business Suite online patching), several important tables are created or
updated to support the patching process:
1. FND_PATCHES – Tracks patches applied to the system.
2. FND_INSTALLATIONS – Stores installation details and configurations.
3. FND_ADOP_FILES – Manages files used during the patching process.
4. FND_ADOP_PUTS – Tracks the patching status.
These tables help in managing and tracking the online patching process, ensuring smooth application and
rollback of patches.

7. You need to apply a critical patch to an Oracle EBS environment. What is your patch
application process, and how do you minimize downtime?

A: TO minimize the downtime of application server I will prefer ADOP Online patching method.
1. Always first try to apply patches on staged environments which are cloned from production.
2.Ensure have full backup before you continue patching
3. Use shared file system for multimode system to avoid apply patches separately on each node.
4. Increase the workers(Backgroud processes)
5.Automate post patching steps. Run autoconfig.sh
6. schedule downtime for only cutover.

8. During the application of a patch, you encounter the error “The patch cannot be
applied because one of the required files is missing.” How would you resolve this? (imp)
A: 1. Always ensure you apply pre req patches as per README file.
2.Chech patchlog file and try to understand the issue.
3. Run adadmin
4. Choose ‘ Maintain Application files  ‘Generate missing file’.
5 Now gain try to apply patch.
If you face same error, raise SR with oracle.

17. After a failed patch application, your EBS system is not starting. What steps would you
follow to bring it back online?
A: To bring an Oracle EBS system back online after a failed patch application:
1. Check Logs:
• Review ad.log* and install.log* files to identify any specific errors during the patch
application.
2. Rollback the Patch:
• Use the AD Administration utility to rollback the patch:
adadmin
• Select “Rollback” option to undo the failed patch.

3. Check for Incomplete Patch:

• Run adchkpatch to verify if the patch was applied partially and resolve any inconsistencies.
4. Check for Database Issues:
• Verify the database is up and running. If not, restart the database services.
• Apply any rollback for database-related patches using RMAN if necessary.
5. Re-run Post-Installation Steps:
• Re-run the post-patching steps if the patch rollback is successful to ensure the system is in a
clean state.
6. Reapply the Patch (Optional):
• If rollback resolves the issue, try reapplying the patch, ensuring no errors occur.
7. Test the Environment:
• Validate the application by checking for any functionality or performance issues before fully
bringing it back online.

These steps should help bring the system back online after a failed patch application.

5. What is the significance of the “run” and “patch” file systems in EBS 12.2?
A: In Oracle EBS 12.2, the “run” and “patch” file systems are crucial for online patching (ADOP), enabling
minimal downtime during patch application.

Run File System:

 • Active Environment: Contains the files currently in use by Oracle EBS, supporting live user
interactions and business transactions.
• Unchanged During Patching: Remains unaffected while patches are applied to the patch file
system.
• Continuous Availability: Ensures that users can access the system without disruptions
during patching.

Patch File System:

• Staging Area: The patch file system is used to apply the patches without affecting the active
environment.
• Post-Apply Switch: Once patches are applied, the patch file system becomes the active one
during the cutover phase.
• Rollback Option: Allows easy rollback if there are issues, as the previous run file system can
be reverted.

Benefits:
• Zero Downtime: Ensures business continuity during patching.
• Efficient Recovery: Enables rapid rollback to the previous stable environment if necessary.

6. How would you troubleshoot an issue if the ADOP prepare phase fails?
A: To troubleshoot an ADOP prepare phase failure in Oracle EBS 12.2:
1. Check Logs: Review error logs in $AD_TOP/logs/ for detailed messages.
2. Verify Patch Directory: Ensure the patch is staged correctly and check for permission issues.
3. System Resources: Check disk space and memory using df -h and free -m.
4. Permissions: Confirm that the user has appropriate permissions on run and patch file
systems.
5. Database Connectivity: Validate database access using tnsping.
6. Retry: After resolving issues, rerun the prepare phase:

adop phase=prepare

Patching in Oracle E-Business Suite (EBS)

1. Patching in Oracle EBS keeps the system up-to-date, secure, and optimized by applying bug
fixes, security updates, and enhancements to ensure smooth operation.
2. Types of Patches:
• One-off patches: Fix specific issues.
• Cumulative patches: Include multiple patches combined.
• RUP: Collection of bug fixes and new features.
• CPU: Security updates released quarterly.
• PSU: Includes fixes and updates with security patches.
3. Difference Between Oracle DB Patch and EBS Patch: Oracle DB patches focus on database
fixes, while EBS patches update application-level components like modules and workflows.
4. ADPATCH Utility: It applies patches to both the database and application tiers. It reads patch
driver files, executes them, and provides progress tracking.

Patching Tools and Utilities

 6. adpatch Utility: Primarily used to apply patches in Oracle EBS, with key parameters like
apply, rollback, and validate.
7. adctrl Utility: Controls the worker processes during patching. It can pause, resume, or abort
patching if required.
8. adadmin Utility: Handles post-patching activities like recompiling invalid objects, validating
the system status, and ensuring completeness.
9. adsplice Utility: Merges schema changes during patching. It’s used when database schemas
are modified.
10. opatch Utility: Used for database patching, while adpatch is for EBS-specific patches.

Patching in R12.2
11. Online Patching in R12.2: Allows patches to be applied without downtime by maintaining
two environments: one for running and one for patching.
12. Phases of Online Patching:

• Prepare: Prepares for patch application.

• Apply: Applies the patch to the PATCH edition.
• Finalize: Finalizes changes to the database.
• Cutover: Switches from the RUN edition to the PATCH edition.
• Cleanup: Removes unneeded files.

13. Patch Edition (PATCH) vs Run Edition (RUN): PATCH holds the changes during patching, and
RUN is the live, operational environment.
14. Hotpatch: A type of patch that applies changes to the system without taking it offline.
15. Checking Patch Environment: Use tools like adadmin to ensure that the patch environment
is properly set up.

Troubleshooting Patching Issues

16. Failed Worker Processes: Managed by adctrl to restart and recover the patching process.
17. Patch Driver Failures: Recheck the driver file and logs for dependencies and system
compatibility before retrying the patch.
18. Invalid Database Objects After Patching: Use adadmin to recompile invalid objects in the
system.
19. Rolling Back a Patch: Use adpatch with the rollback option to undo the changes made by a
patch.
20. Common Errors: Address missing prerequisites, database issues, and log errors by reviewing
logs and reapplying fixes as needed.

Critical Patch Updates (CPU) and Security Patching

21. Critical Patch Update (CPU): A collection of security fixes, applied using adpatch.
22. CPU vs PSU: CPU includes only security patches, while PSU includes bug fixes and other
updates.
23. Verifying Successful CPU Application: Check logs and verify patch application using system
queries or adadmin.

Patch Planning and Best Practices

 24. Analyzing Patch Impact: Review README files, dependencies, and test in a non-production
environment to assess the impact.
25. Applying Patches in Non-Production: Always test patches in non-production environments
to ensure compatibility before applying them to production.
26. Ensuring Minimal Downtime: Use online patching to minimize downtime, and schedule
patching during off-peak hours.
27. Patching in Multi-Node Environment: Apply patches sequentially across nodes, ensuring the
database and application tiers are updated correctly.
28. Identifying Pre-requisites for Patches: Check the README file and verify against Oracle
support for any necessary pre-patching steps.

Patching Documentation and Validation

29. Validating Patch Application: Use logs and system checks to confirm that patches have been
successfully applied.
30. Logs During Patching: Logs track patch progress and errors. Reviewing these helps in
diagnosing issues.
31. Maintaining Patch History: Use ad_patch_history or ad_bug tables to track which patches
have been applied.
Real-Time Scenarios
32. Unexpected Errors in Test Environment: If errors occur, resolve them in the test
environment first before retrying in production.
33. Invalid Dependent Objects: Recompile invalid objects using adadmin and check for any
unmet dependencies.
34. Managing Patch Activities in a 24/7 Environment: Apply patches using online patching,
ensuring minimal disruption by choosing off-peak times and monitoring the system during the process.
Weblogic

4.Upgrade (DB & APP)

5.GRID, ASM, RAC:

1. What is the role of Oracle Grid Infrastructure in an Oracle RAC environment?

Answer:
Oracle Grid Infrastructure is the foundational software layer for Oracle RAC and ASM. It provides the
necessary services for cluster management, automatic failover, and storage management. Key components
include:
• Cluster ware: Manages the cluster nodes and resources.
• ASM: Manages storage, offering striping and mirroring for performance and redundancy.
It also ensures high availability for Oracle EBS environments running on RAC.

2. How do you monitor and troubleshoot RAC node failures in an Oracle Apps environment?
Answer:
• Use Clusterware logs (e.g., alert.log, ocssd.log, crsd.log) to investigate node failures.
• Run the crsctl status command to check the cluster and resource status.
• Use the Oracle Cluster Registry (OCR) to validate node details and configuration.
 • Check the VIP (Virtual IP) status and interconnects using tools like oifcfg and olsnodes.
• Perform root cause analysis by identifying network, hardware, or storage issues causing the
node to fail.

3. What are ASM disk groups, and how are they used in Oracle EBS?
Answer:
ASM disk groups are logical groupings of storage devices managed by ASM for striping, mirroring, and
redundancy. In Oracle EBS, ASM is used to store:
• Database files, control files, and redo logs.
• RAC instances in a shared storage environment to ensure data consistency.
ASM offers simplified storage management and improves I/O performance for high-demand systems like
EBS.

4. What is the difference between RAC and ASM, and how do they complement each other in Oracle
EBS?
Answer:
AC (Real Application Clusters): Enables multiple nodes to access a single database, providing scalability and
high availability for Oracle EBS.
ASM (Automatic Storage Management): Manages storage resources for Oracle databases, offering features
like striping, mirroring, and dynamic resizing.
RAC nodes rely on ASM for shared storage, ensuring consistent data access across all nodes. Together, they
enhance EBS performance and resilience.

5. How do you add a new ASM disk to an existing disk group in Oracle RAC?
Answer:
Use the asmcmd utility or Oracle Enterprise Manager (OEM) to identify existing disk groups.
Validate the availability of the new disk using the lsblk or fdisk commands on the operating system.
Add the disk using the ALTER DISKGROUP SQL command:
ALTER DISKGROUP <disk_group_name> ADD DISK '<disk_path>';
Confirm the addition using:
SELECT * FROM V$ASM_DISK;
Monitor the rebalance process using the v$asm_operation view.

6. Troubleshooting
6. After a clone, your Application tier cannot connect to the Database tier. What would
you check first?
A: If the application tier cannot connect to the database tier after a clone, check the following:
1. Database Listener:
Ensure the listener is running and configured correctly on the database tier.
lsnrctl status
2. TNS Configuration:
Verify the tnsnames.ora file on the application tier points to the correct database hostname, port,
and service name.
3. Network Connectivity:
Test connectivity between the application and database tiers using ping and tnsping.
tnsping <db_service_name>
 4. Database Status:
Ensure the database is open and available for connections.
SELECT status FROM v$instance;
5. Apps Password:
Verify the APPS schema password is correct by testing a manual connection.
These checks will identify and help resolve the connection issue.

4. A critical EBS service is down. How would you go about troubleshooting the
issue?

A:
Check Service Status: Use adstpall.sh and adstrtal.sh to verify service status.(AD_T0P)
2. Review Logs: Check EBS, Web, and Database logs for errors.
3. Verify DB Connection: Test connection with tnsping and sqlplus.
4. Check Listener: Ensure Oracle Listener is running (lsnrctl status).
5. Resource Check: Verify server resource usage (top, df -h).
6. Check Database Errors: Review Oracle alert logs.
7. WebLogic Logs: Check WebLogic server logs (if applicable).
8. Verify Oracle Services: Ensure all Oracle services are running.
9. Restart Services: Restart EBS services if no cause is found.
10. Check Disk Space: Ensure sufficient disk space (df -h).
11. Review Configurations: Check context files for misconfigurations.

2. How do you investigate and resolve database-related performance bottlenecks?

A: Investigating and Resolving Database-Related Performance Bottlenecks:
• Identify Issues: Use AWR, ASH, and SQL trace to identify long-running queries, high wait
events, or resource contention.
• Optimize Queries: Review execution plans, add necessary indexes, or rewrite inefficient
queries.
• Tune Database Parameters: Adjust memory settings (e.g., SGA, PGA) and ensure optimal
disk I/O configuration.
• Resolve Locking: Investigate and resolve lock contention by analyzing v$session and v$lock
views. GV$SESSION

7.Performance tuning & Monitoring

How you will monitor your applications as well as a database?

A: To monitor both the application and database, I would take the following steps:

Application Monitoring:
1. Oracle Application Manager (OAM): Monitor the overall health of the Oracle E-Business
Suite.
2. Log Files: Regularly check logs like AD logs, Concurrent Manager logs, and Oacore logs for
errors or performance issues.
 3. Performance Metrics: Monitor response times, CPU utilization, and memory usage using
tools like Oracle Enterprise Manager (OEM).
4. Alerting: Set up alerts in Oracle Application Monitoring to notify of failures or issues.

Database Monitoring:

1. Oracle Enterprise Manager (OEM): Monitor database health, resource usage, and SQL
performance.
2. Automatic Workload Repository (AWR): Analyze performance over time by capturing
system statistics.
3. Active Session History (ASH): Monitor real-time sessions and identify resource contention or
expensive queries.
4. SQL Tuning Advisor: Regularly run the SQL tuning advisor to identify slow queries and
optimize them.
5. Alert Logs & Trace Files: Check database alert logs and diagnostic files for issues.

Combining these methods ensures proactive monitoring and issue detection for both the application and
database.

13. What are the common performance tuning tasks in an EBS environment?
A: Common Performance Tuning Tasks in an EBS Environment:
• SQL Query Optimization: Analyze and optimize slow-running SQL queries using AWR, ASH,
and SQL Trace.
• Database Tuning: Adjust memory settings (SGA, PGA) and optimize disk I/O configurations.
• Index Management: Rebuild or create missing indexes to improve query performance.
• Resource Allocation: Adjust system resources like CPU and memory for application and
database tiers.
• Session Management: Monitor and manage database sessions and connections to avoid
resource contention.
• WebLogic Tuning: Adjust Java heap size, thread pools, and connection pools to optimize
application performance.

10. You are experiencing slow SQL execution in Oracle EBS. Walk us through the steps you
would take to tune the query and resolve the issue. (Imp)
A: If you are experiencing slow SQL execution:
1.check query with EXPLAIN PLAN for <query>
2.Check costly operations like full tables scans, missing indexes and inefficient joins.
3. check system resources like CPU, MEMORY Usages.
4. use AWR and ASH reports for proper diagnosis.
Resolve:
1.Gather stat gather scheme for better query optimization.
2.Optimise the query by adding missing indexes, using proper joins, by avoiding full table
scans.
3.Use parallel execution for long queries.
4. improve system resources.
12. How do you use Oracle AWR and ASH reports to resolve performance
issues in Oracle EBS? (Imp)
A: To resolve performance issues in Oracle EBS using AWR and ASH reports:
AWR (Automatic workload repository): It provide snapshot of db performance over time and used
for performance tuning and diagnostics.
@?/sqlplus/admin/awrrpt.sql
• Analyze the Top SQL section for high resource-consuming queries, and review wait events
for potential bottlenecks (e.g., I/O, CPU, or locking issues).
ASH (Active session History)
• Run the ASH report to examine real-time active session history:
@?/sqlplus/admin/ashrpt.sql
• Look for sessions with high wait times, blocking sessions, or inefficient queries.
Resolve query performances by:
1.Gather stat gather scheme for better query optimization.
2.Optimise the query by adding missing indexes, using proper joins, by avoiding full table scans.
3.Use parallel execution for long queries.
4. improve system resources.

13. A user reports slow performance when running reports in Oracle EBS. How
do you identify the cause and resolve it?
A: Diagnose:
1.check application logs
2.check system resources its bottlenecks using top, vmstat
3.revire AWR and ASH reports.
4. Identify db locks and blocking sessions.
5. Review concurrent manger logs
6.Use EXPLAIN PLAN for execution plan.
Resolve:
1.Kill blocking locks
2.optimize query perforce using missing indexes and using relevant joins
3. Monitor system resources: CPU, Memory. Kill highly CPU consuming processes if it is not required to run.
4. Avoid full table scans for better query execution.

Explain stats gathering and how it impacts database performance? (Imp)

A: Statistics Gathering for Schema involves collecting data on table sizes, indexes, and data distribution to
help the optimizer create efficient execution plans. Here’s how it impacts database performance:
 Improved Query Execution: Accurate stats allow the optimizer to choose the best plan.
 Reduced Resource Usage: Helps avoid inefficient joins, sorts, or full table scans.
 Timely Updates: Regular gathering keeps stats in sync with data growth or changes.
 Automatic vs. Manual: Can use DBMS_STATS.GATHER_SCHEMA_STATS for precise control or
rely on automated tasks.
 Impacts Complex Queries: Beneficial for joins and partitioned tables.
 Always gather stats during low-usage periods to minimize performance impact.
  Explain about TKPROF utility and when do you use it? (Imp)
A: TKPROF Utility in Oracle:

• Purpose: TKPROF (Trace Kernel PROFiler) formats raw SQL trace files into
readable output for performance analysis.
• Key Features: Provides detailed insights into query execution time, CPU usage, disk
reads, and execution plans.
Usage Scenarios:
• Identifying slow SQL statements.
• Debugging performance issues in applications.
• Analyzing resource-intensive queries.
• Comparing execution plans for tuning.
How to Use:
1. Enable SQL trace using ALTER SESSION SET SQL_TRACE = TRUE;.
2. Run TKPROF to format the trace file:

tkprof tracefile outputfile explain=user/password

8.EBS Security Concepts

1. Explain the process of configuring SSL, SSO, OID, and OAM in Oracle EBS?
A: Configuring SSL, SSO, OID, and OAM in Oracle EBS:
• SSL Configuration: Configure Oracle HTTP Server (OHS) for SSL by setting up SSL certificates
and enabling HTTPS in the httpd.conf file.
• SSO Configuration: Integrate Oracle EBS with Oracle Access Manager (OAM) for Single Sign-
On (SSO) by updating the SSO profile options and configuring OID for user synchronization.
• OID Setup: Set up Oracle Internet Directory (OID) for centralized user management and
authentication, syncing with EBS users.
• OAM Setup: Configure Oracle Access Manager (OAM) to manage authentication policies,
enabling users to authenticate via SSO.

2. How would you set up and configure a Load Balancer for Oracle EBS?
A: 2. Setting Up and Configuring a Load Balancer for Oracle EBS:
• Install Load Balancer: Deploy a hardware or software-based load balancer (e.g., F5, Oracle
SLB).
• Configure VIPs: Set up Virtual IPs (VIPs) for the web and application tiers.
• Sticky Sessions: Enable session persistence (sticky sessions) to maintain user sessions on the
same server.
• SSL Offloading: Configure SSL offloading on the load balancer for improved performance.
• Context Files: Update EBS context files with load balancer details and run AutoConfig to
propagate the changes.

16. What steps do you take to ensure the security of the EBS environment?
A: 1. Steps to Ensure the Security of the EBS Environment:
 • User Authentication & Authorization: Implement strong authentication methods like SSO
(Single Sign-On) and manage user roles and privileges using Oracle Identity Management.
• Patch Management: Regularly apply critical security patches and updates for Oracle EBS and
underlying systems.
• Data Encryption: Enable data encryption for sensitive information both at rest (file system,
database) and in transit (using SSL/TLS).
• Network Security: Use firewalls, intrusion detection/prevention systems, and ensure proper
network segmentation.
• Audit Logging: Enable auditing and logging to track user activities and security events within
the system.
• Backup Security: Implement encrypted backups and store them in secure locations.

17. How do you implement data masking in Oracle EBS?

A: Implementing Data Masking in Oracle EBS:
• Use Oracle Data Masking: Utilize Oracle Data Masking and Subsetting to create a sanitized
version of production data for non-production environments.
• Define Masking Policies: Set policies to mask sensitive data such as personal information,
credit card details, etc.
• Apply Masking: Execute the masking process on tables and columns with sensitive
information.
• Test: Verify the integrity and usability of the masked data in test environments, ensuring no
sensitive data is exposed.

What is data masking?

18. What is the use of TLS/SSL configuration in Oracle EBS?

A: 3. Use of TLS/SSL Configuration in Oracle EBS:
• TLS/SSL Encryption: Ensures secure communication between clients, web servers, and the
Oracle EBS application tier by encrypting HTTP traffic.
• Data Protection: Protects sensitive data in transit from eavesdropping and tampering,
especially when accessing EBS over the internet.
• Server Authentication: Verifies the identity of the EBS server to clients, preventing man-in-
the-middle attacks.
• SSL Certificates: Configures SSL certificates on the Oracle HTTP Server (OHS) to enable
encrypted HTTPS communication.

What is SSL?

SSL (Secure Sockets Layer) is a protocol that provides secure communication over a computer network,
especially the internet. It ensures that data transmitted between a client (such as a browser) and a server
(such as a web server) remains private and integrity is maintained.
Key Features:
Encryption , Authentication , Data Integrity
How It Works:
• SSL Certificate: A website uses an SSL certificate to establish a secure connection. This
certificate contains the server’s public key and is issued by a trusted Certificate Authority (CA).
 • HTTPS: When SSL is implemented, URLs start with “https://” instead of “http://”, indicating
that the connection is secure.
Modern Evolution:
• SSL is now largely replaced by TLS (Transport Layer Security), which is a more secure
version of SSL. However, the term SSL is still commonly used to refer to secure HTTPS connections.

16. You need to configure Single Sign-On (SSO) between Oracle EBS and a third-party
application. How would you go about it? (Imp)
A: To configure Single Sign-On (SSO) between Oracle EBS and a third-party application:
1. Set Up Identity Provider (IdP):
• Configure an Identity Provider (IdP), such as Oracle Identity Federation (OIF), ADFS, or a
third-party IdP, to handle authentication.
2. Configure Oracle EBS for SSO:
• Enable and configure Oracle Internet Directory (OID) or Oracle Identity Management (OIM)
as the authentication mechanism for EBS.
• Set the profile option “ICX: Authentication Type” to SSO in the system to use SSO for user
login.
3. Integrate IdP with Oracle EBS:
• Configure the IdP to recognize Oracle EBS as a Service Provider (SP) using SAML (Security
Assertion Markup Language) or OAuth.
• Modify Oracle EBS configuration files (e.g., appltop/admin), enabling communication
between EBS and the IdP.
4. Configure Third-Party Application for SSO:
• Ensure the third-party application supports SSO via SAML or OAuth and is configured to
recognize the same IdP.
5. Test the SSO Integration:
• Test SSO by attempting to access Oracle EBS and the third-party application. After a
successful login to one, you should be automatically authenticated in the other.

This process enables a seamless authentication experience for users across Oracle EBS and the third-party
application.

14. You are configuring SSL in Oracle EBS, and the application is not loading over HTTPS.
How do you troubleshoot?

A: To troubleshoot SSL issues in Oracle EBS not loading over HTTPS:

1. Verify SSL Configuration:
• Ensure that SSL is properly configured in Oracle EBS by checking httpd.conf or ssl.conf files
in the Apache configuration directory.
2. Check Certificates:
• Confirm that the correct SSL certificates (server and CA) are installed and valid. Ensure they
are properly imported into the WebLogic server and the Oracle wallet.
3. Review Apache and WebLogic Logs:
• Check the Apache error logs and WebLogic logs for any SSL-related errors or warnings (e.g.,
certificate issues, port binding errors).
4. Verify Port Configuration:
 • Ensure that the HTTPS port (typically 443) is correctly configured and open in the firewall,
and WebLogic is listening on that port.
5. Check Redirects and URL:
• Ensure there are no conflicting redirects from HTTP to HTTPS and that the correct URLs are
being used for the application.
6. Test SSL Connection:
• Use a browser or tools like openssl to test the SSL connection and verify the certificate
chain:
openssl s_client -connect <hostname>:443
These steps help identify and resolve SSL configuration issues preventing Oracle EBS from loading over
HTTPS.

Workflow and Concurrent Programs:

19. How do you troubleshoot workflow-related issues in EBS?
A: Troubleshooting Workflow-Related Issues in EBS:
• Workflow Monitor: Check the status of workflows and see if they are stuck or failed.
• Logs: Inspect WF_LOG for errors and review background process logs for troubleshooting.
• Workflow Queue: Use the Workflow Queue Monitor to see if any items are pending,
aborted, or in error state.
• Notifications: Check WF_NOTIFICATIONS for issues with workflow notifications.
IF EVERYTHING IS GOOD, RE RUN THE WORKFLOW.

20. Explain the steps to register a custom concurrent program in Oracle EBS?
A: Registering a Custom Concurrent Program in Oracle EBS:
• Define Program: Go to Concurrent Program and define the program by providing necessary
details such as the program name and short name.
• Attach Executable: Link the executable (PL/SQL procedure, script, etc.) to the concurrent
program.
• Define Parameters: If the program has input parameters, define them.
• Assign to Request Group: Attach the concurrent program to a request group to allow users
to access and run the program.

9.Weblogic & Middlware

11. What is FUSION MIDDLEWARE? (imp)

A: it is comprehensive suite of all tools and services that connects applications, database and users.
It includes:
1. Application servers: weblogic.
2. Integration tools: SOA Suite and ODI for app and data integration
3. Identity management: OIM, OAM for secure access and user management.
4. Business intelligence: For dashboard and oracle business intelligence Oracle Bi.
5. Middleware infrastructure: EM for monitoring and OHS as a webserver. (apache)
1. What is Oracle Middleware in the context of Oracle E-Business Suite (EBS)?
Answer:
Oracle Middleware refers to a set of software tools and services that facilitate communication between
Oracle E-Business Suite and various components of the system, such as databases, application servers, and
third-party applications. It includes technologies like Oracle WebLogic Server, Oracle HTTP Server (OHS),
Oracle Fusion Middleware, and Oracle Application Server (OAS). These middleware components are
critical for enabling integration, scalability, and high availability in Oracle EBS environments.

2. What is Oracle WebLogic Server, and why is it important for Oracle EBS?
Answer:
Oracle WebLogic Server is an application server that hosts and runs Oracle E-Business Suite’s Java-based
applications. It provides a platform for deploying, managing, and securing EBS’s business logic and user
interfaces, making it a critical component in the middleware layer. WebLogic Server supports the scalability,
clustering, and high availability of Oracle EBS.
3. What is Oracle HTTP Server (OHS), and how does it work with Oracle EBS?
Answer:
Oracle HTTP Server (OHS) is a web server that acts as the front-end interface to Oracle E-Business Suite. It
handles HTTP requests from users and forwards them to the appropriate backend services (e.g., Oracle
Application Server or WebLogic Server). OHS also performs tasks like SSL encryption, load balancing, and
proxying for the Oracle EBS system, ensuring efficient communication and high availability.

4. Explain the role of Oracle Fusion Middleware in Oracle EBS.

Answer:
Oracle Fusion Middleware is a collection of tools and services that enable integration, automation, and
management of Oracle E-Business Suite. It includes technologies such as Oracle SOA Suite, Oracle Service
Bus, Oracle WebLogic Server, and Oracle Identity Management. These components provide essential
services like security, messaging, business process automation, and integration across different Oracle EBS
modules and external systems.
5. What is Oracle E-Business Suite’s Single Sign-On (SSO), and how does it work with middleware?
Answer:
Oracle Single Sign-On (SSO) is a middleware component that allows users to authenticate once and gain
access to all Oracle E-Business Suite applications without having to log in multiple times.
It integrates with Oracle Access Manager (OAM) to provide centralized authentication and authorization
services, reducing the need for multiple passwords and improving security across the Oracle EBS
environment.

6. What is the purpose of Oracle Internet Directory (OID) in Oracle EBS?

Answer:
Oracle Internet Directory (OID) is used for centralized management of users, roles, and policies in Oracle
E-Business Suite. It is an LDAP-based directory service that stores user credentials, application-specific
roles, and configuration data. OID helps with user authentication, authorization, and identity management,
and it integrates seamlessly with Oracle SSO and Oracle EBS for centralized security management.

7. What is the difference between Oracle Application Server and Oracle WebLogic Server in Oracle EBS?
Answer:
Oracle Application Server (OAS) was used in earlier versions of Oracle EBS, and it includes components such
as Oracle HTTP Server, Oracle Forms, and Oracle Reports. However, in more recent versions, Oracle
WebLogic Server has replaced OAS as the primary application server for hosting Java-based applications.
WebLogic provides advanced features like clustering, improved scalability, and better support for web-
based applications, making it the preferred server in Oracle EBS versions R12 and later.

8. How do you monitor and troubleshoot Oracle Middleware components (e.g., WebLogic, OHS)?
Answer:
 Monitoring and troubleshooting Oracle Middleware components involve several steps:
o Use Oracle Enterprise Manager (OEM) to monitor WebLogic Server, Oracle HTTP Server, and
other components.
o Check the log files for errors and warnings (e.g., weblogic.log, nohup.out, OHS logs).
o Use WebLogic Diagnostic Framework (WLDF) to gather real-time diagnostic data.
o Review performance metrics such as thread usage, memory utilization, and response times.
o Use Fusion Middleware Control for centralized monitoring and configuration.
o Use tools like WebLogic Server Administration Console to troubleshoot application issues
and server configurations.
o
9. What are the common issues faced in Oracle EBS Middleware, and how do you resolve them?
Answer:
Common issues include:
• Performance issues: Check for resource bottlenecks (CPU, memory) in WebLogic Server or
OHS. Increase the heap size or adjust the number of threads in WebLogic.
• Connection failures: Verify the database connections, listener configurations, and ensure no
firewall or network issues are blocking communication between middleware and the database.
• Application downtime: Ensure the OHS, WebLogic, and other components are running.
Restart services using the opmnctl or emctl utilities.
• SSO authentication errors: Check the integration with Oracle Identity Management and
ensure the correct user roles and permissions are configured.

10. How do you perform a patching process for Oracle Middleware components (e.g., WebLogic, OHS)?
Answer:
Patching Oracle Middleware involves:
• Identifying the patch required from Oracle support (e.g., WebLogic patches, OHS patches).
• Applying the patch in a test environment first, following Oracle’s patching guidelines.
• Use tools like opatch to apply patches for WebLogic Server or Oracle HTTP Server.
• Monitor the patching process and ensure that all services are correctly restarted after the
patch application.
• Validate the environment by running health checks and verifying application functionality.
• Document the patch application process and maintain logs for future reference.

11.Where are the log file located in R12.2 Apache and Weblogic?
A: In Oracle E-Business Suite R12.2, log files for Apache and WebLogic are typically located as
follows:
1. Apache Logs:
• Access logs: $APACHE_HOME/logs/access_log
• Error logs: $APACHE_HOME/logs/error_log
2. WebLogic Logs:
• Domain logs: $DOMAIN_HOME/servers/servername/logs/server.log
 • Managed server logs: $DOMAIN_HOME/servers/Managed_server1 logs/Managed_server1.
log
These log files help in diagnosing issues related to web server performance and application errors.

12.What is domain in Web Logic? (vIMP)

A: In WebLogic Server, a domain is a logically grouped collection of resources for running
applications.
It includes the server configuration, deployment data, and
system resources such as managed servers, clusters, and security configurations.
A domain can contain multiple WebLogic servers (e.g., Admin Server, Managed Servers) and is the
fundamental unit for managing and monitoring WebLogic resources.

13. What is Administration Server? (Imp)

A: An Admin Server in WebLogic Server is the central management point for the domain.
It manages configurations, deployment, and monitoring of applications and resources.
It also handles tasks like domain creation, user authentication, and manages communication with
Managed Servers.
The Admin Server runs a web-based Console and provides command-line tools for domain
administration.

Where weblogic server is installed: It is installed in the FMW_Home which reside in fs1 and fs2
filesystem in 12.2.
/u01/app/EBSapps/fs1/FMW_HOME/wlserver. = Weblogic server home
$EBS_DOMAIN_HOME/config. = Weblogic configuration files

14.What is Managed Server? (Imp)

A: A Managed Server in WebLogic Server is a server that hosts applications and is part of a WebLogic
domain. Unlike the Admin Server, which is responsible for configuration and management,
Managed Servers handle the actual business logic, processing requests, and running applications.
Multiple Managed Servers can be configured for load balancing and clustering to ensure high
availability and scalability. They rely on the Admin Server for initial configuration and management
tasks.

15.What is Cluster in WebLogic? (Imp)

A: A cluster in WebLogic Server is a group of managed servers that work together to provide
scalability, load balancing, and high availability for applications.
It enables requests to be distributed across multiple servers, ensuring that if one server fails, another
can take over.
Clustering also facilitates session replication, ensuring that user sessions are maintained across
multiple servers. The Admin Server manages the configuration of the cluster, while the Managed
Servers in the cluster handle the actual processing.

16. can we have our application in administration server?

 A: Technically, you can deploy applications to the Admin Server in WebLogic, but it is not
recommended for production environments.
The Admin Server is primarily used for configuration and management tasks, not for hosting
applications.
In production, applications should be deployed to Managed Servers to ensure scalability, load
balancing, and high availability.
The Admin Server is responsible for managing the configuration of these Managed Servers, but it
shouldn’t handle application traffic directly.

11.WebLogic is showing errors related to insufficient heap memory. How would you
address this?
A: To address insufficient heap memory errors in WebLogic:
1. Increase Heap Size:
• Edit the setDomainEnv.sh (Unix/Linux) or setDomainEnv.cmd (Windows) file in the
WebLogic domain directory.
• Modify the -Xms (initial heap size) and -Xmx (maximum heap size) values.
Example:
export JAVA_OPTIONS="-Xms1024m -Xmx4096m"
2. Restart WebLogic Server:
• After saving the changes, restart the WebLogic server to apply the new memory settings.
3. Monitor Memory Usage:
• Check WebLogic logs and monitor memory usage to ensure the new settings resolve the
issue without causing further problems.

A WebLogic server in an Oracle EBS environment is slow. How do you diagnose and
resolve the performance issue?
A: Diagnosis:
1.Check WebLogic server logs for any warnings and error.
2.Chech all the system resources like CPU and memory
3.Use top and vmstart for monitoring system resources
4.check heap size
5. check all the service status.
Resolving:
2. I Will increase heap memory
3. Kill unnecessary CPU bottlenecks
4. Restart the WebLogic
5. Adjust garbage collection

What is garbage collector and its purpose? (IMP)

A garbage collector (GC) is a Java component responsible for automatically managing memory by
reclaiming unused or unreferenced objects in the heap.
“Its main function is to free up the memory that is no longer needed, preventing memory leaks and
optimizing memory usage.” By doing so, it ensures efficient use of resources and helps improve application
performance.
Different types of garbage collectors (e.g., Serial, Parallel, G1GC) are used depending on the application’s
memory requirements and performance needs.

What is heap memory? (IMP)

Heap memory is a region of memory used by applications to store dynamically allocated objects and data
during runtime. It is managed by the garbage collector in languages like Java.

Why It Is Needed:
• Dynamic Memory Allocation: It allows objects to be created at runtime, with memory
allocated and deallocated as needed.
• Variable Storage: Stores objects, arrays, and other large data structures that have an
unpredictable lifetime.
• Flexibility: Unlike stack memory, heap memory can grow or shrink dynamically during the
program’s execution.

In summary, heap memory is essential for managing memory that requires dynamic allocation and
deallocation during application execution.

Relation between APCHE and WEBLOGIC?

In an Oracle E-Business Suite environment, Apache and WebLogic work together to serve web applications.
Here’s their relationship:
1. WebLogic is the application server that hosts the Oracle EBS application logic, such as forms,
reports, and web services.
2. Apache acts as the web server that handles incoming HTTP requests and serves static
content like HTML, images, and CSS. It acts as a reverse proxy for WebLogic, forwarding requests for
dynamic content to WebLogic.

Key Functions:
• Apache:
• Handles client requests for static content.
• Serves as a reverse proxy, forwarding dynamic requests (e.g., forms, reports) to WebLogic for
processing.
• WebLogic:
• Processes business logic and generates dynamic content (e.g., EBS pages, reports).
• Responds to Apache by sending back dynamic content over HTTP/HTTPS.

Interaction:
• Apache listens for client requests on standard ports (e.g., 80 for HTTP, 443 for HTTPS).
• For dynamic content, Apache forwards the request to WebLogic using the mod_wl_ohs
module.
• WebLogic handles the request, executes the business logic, and returns the response to
Apache, which then sends it to the client.

Thus, Apache and WebLogic work together to provide a seamless experience for Oracle EBS users, with
Apache handling static content and WebLogic processing dynamic requests.
10. How to find
11. 3. How to determine Oracle Apps 11i Version?
12.select RELEASE_NAME from fnd_product_groups;
13. 4. How to find the Database version?
SQL> select * from v$version;
14.How to find out invalid objects in the database? (imp)
select object_name, object_type status from dba_objects where status =’INVALID’
15. How you will see hidden files in Linux/Solaris? (imp)
ls -la

16. How to find that the database is 64-bit/32-bit?

$RDBMS_ORACLE_HOME/bin/file oracle

10. DB Backup/restore - real time issues

2. I lost redo log file and have no multiplexed copy or archive log. How can I recover
the database? (IMP)
Scenario 2: Lost Current or Active Redo Log File

If the lost redo log file belongs to the current or active redo log group, you cannot recover
committed transactions up to the point of failure. However, you can attempt incomplete recovery.
Steps:
1. Shutdown the Database:
SHUTDOWN ABORT;
2. Start the Database in Mount Mode:
STARTUP MOUNT;
3. Restore and Recover the Database:
Perform an incomplete recovery up to the last available SCN or timestamp before the redo log file
loss:
RECOVER DATABASE UNTIL CANCEL;
When prompted, type CANCEL to stop recovery when no more logs are available.
4. Open the Database with Resetlogs:
After incomplete recovery, open the database in resetlogs mode:
ALTER DATABASE OPEN RESETLOGS;

Scenario 3: Lost All Redo Logs

If all redo logs are lost and you don’t have multiplexed copies or archived logs, you can perform a
recovery that involves potential data loss.
Steps:
1. Shutdown and Mount the Database:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
2. Recreate Redo Logs:
Use the following command to drop and recreate redo log files:
 ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP <group_number>;
Repeat for all groups.
3. Open Database with Resetlogs:
ALTER DATABASE OPEN RESETLOGS;
Key Notes:
• Risk of Data Loss: Incomplete recovery or clearing unarchived logs will result in losing
uncommitted and some committed transactions.
• Prevention:
- Always multiplex redo log files across different disks.
- Enable archive logging for safer recovery options.
- Regularly back up the database.
-
 A user is complaining DB is running slow. What could be the issue? (Imp)
A: Below are the several potential causes:
1. CPU Over utilization
2. Memory consumtion
3. DISK I/O
4. Unoptimizes queries
5. SGA,PGA, Redo log sizes
6. Network latency
7. Sudden increase in user connections
8. Long running BGP
How to troubleshoot:
9. Analyse logs , check alert logs and server logs check for errors and wrning
10. Use AWR,ADDR for diagnose issue
11. Check blocking sessions – inactive sessions. and locks – kill if needed
12. Use top command to check high consuming CPU.
13. Use EXPLAIN_PLAN , DBMS_XPLAN.DISPLAY

 There are 50 random email alerts for multiple databases. How will you prioritize the
alerts and solve them? imp
A: To prioritize and resolve 50 random email alerts for multiple databases, follow these steps:
1. Categorize Alerts:
• Severity: Identify critical, high, medium, and low alerts. Critical alerts (e.g., database
downtime, performance degradation) should be prioritized.
• Type of Alert: Categorize by type—e.g., security issues, database availability, backups,
or performance-related alerts.
2. Assess Impact:
• Evaluate how each alert affects business operations. For example, if an alert indicates
that a production database is down, it should be resolved first.
• Use monitoring tools (e.g., Oracle Enterprise Manager) to get more context on each
alert.
3. Immediate Actions:
• Critical Alerts: Resolve immediately (e.g., restart services, apply patches, fix security
vulnerabilities).
• Non-Critical: Investigate further, but address after high-priority issues.
4. Troubleshooting and Resolution:
 • Gather logs and trace files for detailed analysis.
• Follow documented procedures for common issues, escalating to senior team
members for complex problems.
5. Post-Incident Review:
• After resolving, ensure to document the solution for future reference and implement
preventive measures.

 Temp tablespace utilization is 100% full. What you will do? Imp (IQ)
A: If the temporary tablespace utilization is 100% full, follow these steps:

1. Identify the Root Cause: Query v$tempseg_usage or v$sort_usage to identify large

sessions consuming temp space. If specific queries or users are responsible, optimize those queries
(e.g., by adding indexes or reducing complex sorts).
2. Add Space: Add a datafile to the temp tablespace:
ALTER TABLESPACE temp ADD DATAFILE '/path/to/temp02.dbf' SIZE 2G;
ALTER DATABASE DATFILE ‘PATH’ RESIZE=10G;

Before adding SPACE to datafile: (IQ)

1.Take backup of it
2.check disk size

3. Ping is working but tnsping is not working. What could be the issue?
A: When ping works but tnsping (Oracle listener test) does not, it usually indicates that the Oracle
listener is not running or there is a configuration issue. Here are possible causes:
1. Listener not running: Ensure the Oracle listener is up. Check with lsnrctl status and
start the listener if needed with lsnrctl start.
2. Listener Configuration: Verify the listener.ora file for correct hostname and port
settings, and ensure the service name matches the database.
3. Firewall/Network Issues: The network might block specific ports (e.g., 1521) used by
Oracle listeners, while ICMP (ping) packets are allowed.
4. TNS Configuration: Ensure the tnsnames.ora file is correctly configured with the right
service name and address.

4. I am not able to add data file to tablespace. What could be the issue?
A: If you’re unable to add a datafile to a tablespace, potential issues include:
1. Insufficient Disk Space: Ensure enough free space is available on the disk.
2. File System Permissions: Verify proper write permissions on the directory.
3. Tablespace Quotas: Check if the tablespace has reached its allocated size limit.
4. File Name Conflicts: Ensure the file name or path is not already in use.
5. Incorrect Syntax: Verify the correct command syntax, such as using ALTER
TABLESPACE. You can check the database logs for more specific errors.
5. How to take cold backup using rman? (IMP)
1. SHUTDOWN IMMEDIATE;
2. STARTUP MOUNT;
3. TARGET CONNECT /
4. RMAN> BACKUP DATABASE;
5. RMAN> BACKUP DATABASE PLUS ARCHIVELOG;
6. RMAN> LIST BACKUP;
7. ALTER DATABASE OPEN;
6. Backup file format?

7. What are the ways to improve rman backup / recovery performance in terms of
time? (IMP)
A: To improve RMAN backup and recovery performance, consider the following techniques:
Backup Performance Optimization
1. Parallelism:
Configure multiple channels to utilize system resources effectively:
---------------------------------------------------------------------------
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
----------------------------------------------------------------------------

2. Compression:
Use RMAN compression (BASIC or HIGH) to reduce I/O, especially for slow networks.
3. Incremental Backups:
Leverage block change tracking for faster incremental backups:
-------------------------------------------------------------------------------------------
ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;
-----------------------------------------------------------------------------------

4. Tape Configuration:
Optimize tape usage with parallelism and dedicated drives for tape backups.
5. Disk Staging:
Backup to disk first, then copy to slower media like tape.
6. I/O Configuration:
Use multiple I/O channels to distribute load across disks or network devices.

Recovery Performance Optimization

1. Parallel Recovery:
Use multiple RMAN channels during restore and recovery.
2. Pre-staged Backup Sets:
Place backup files on fast storage or local disks for faster access.
3. Incremental Recovery:
Apply incremental backups instead of full backups during recovery.
4. Use Fast File Systems:
Use ASM or high-speed file systems for RMAN operations.
 5. Tune Redo Apply:
Use the FAST_START_MTTR_TARGET to control crash recovery time.

Regular monitoring and tuning of RMAN configurations ensure optimal performance.

8. How to do perform PITR recovery?

A: To perform a Point-in-Time Recovery (PITR), follow these steps:
1. Shutdown and Mount the Database:
RMAN> SHUTDOWN IMMEDIATE;
RMAN> STARTUP MOUNT;
2. Set the Desired Time/SCN:
RMAN> SET UNTIL TIME 'YYYY-MM-DD HH24:MI:SS';
3. Restore and Recover the Database:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;
4. Open the Database with RESETLOGS:

RMAN> ALTER DATABASE OPEN RESETLOGS;

PITR is used to recover the database to a specific point, avoiding unwanted changes. Ensure
required backups and logs are available.

 Your production database is running in NOARCHIVELOG mode, what could be the

issue?
A: Running a production database in NOARCHIVELOG mode poses serious risks:

• No Point-in-Time Recovery: You can only restore from the last consistent backup; all
changes since the backup are lost.
• Data Loss Risk: In case of failure, transactions not backed up are irretrievable.
• No Incremental Backups: Only full backups can be performed, increasing downtime.
• Compliance Issues: May not meet data retention or recovery policies required by
regulations.
To resolve, switch to ARCHIVELOG mode using:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;

This enables online backups and point-in-time recovery.

9. I have taken L0 backup on 1st and L1 everyday till 15th. The recovery window is of
only 7 days. So how will you recover database as L0 is OBSOLETE backup? (IMP)
A: If the Level 0 (L0) backup taken on the 1st has become obsolete due to the 7-day recovery
window, you cannot directly use it for recovery. However, RMAN retains all backups needed to
recover the database within the recovery window. Here’s how you can recover the database:
1. Understand Backup Retention
 RMAN marks a backup obsolete based on the recovery window policy, but the physical backup
might still exist on disk/tape. Verify with:
----------------------------------
RMAN> LIST BACKUP;
----------------------------------------
2. Check Dependencies
RMAN uses the latest L0 backup and all L1 incremental backups to recover the database. If the L0
backup is obsolete but not deleted, it will still be used in recovery.

3. Recover the Database

Perform the recovery:
RMAN> STARTUP MOUNT;
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;
RMAN> ALTER DATABASE OPEN;
4. Deleted L0 Backup Case
If the L0 backup is physically deleted:
• Restore it from the secondary storage (e.g., tape or offsite copy).
• Recreate an L0 backup for future restores.

10.What is the RMAN command to take controlfile and spfile backup? (IMP)
A: To back up the control file and spfile using RMAN, use the following command:
Command
------------------------------------------------------------
BACKUP CURRENT CONTROLFILE SPFILE;
-----------------------------------------------------------------
BACKUP CURRENT CONTROLFILE;
BACKUP SPFILE;
--------------------------------------
2. Including in Full Database Backup:
---------------------------------------------------------------
BACKUP DATABASE PLUS ARCHIVELOG;
----------------------------------------------------------------------
RMAN> LIST BACKUP;

1. What is the command to delete all the backup older than 30 days?
A: To delete all RMAN backups older than 30 days, use the DELETE command with the RECOVERY
WINDOW criteria:

Command
-----------------------------------------------------------------------
DELETE BACKUP COMPLETED BEFORE 'SYSDATE-30';

11.I have a reporting database of 2 TB. What backup strategy will you recommend?
A: For a 2 TB reporting database, implement the following backup strategy:
 1. Full Backup (Level 0): Weekly, using RMAN to back up the entire database, including
datafiles, control files, and spfile.
2. Incremental Backup (Level 1): Daily, capturing changes since the last backup,
leveraging block change tracking for efficiency.
3. Archive Log Backup: Hourly to ensure point-in-time recovery.
4. Backup to Disk: Perform backups to fast local disk, then copy to tape for offsite
storage.
5. Retention Policies: Use RMAN’s retention policies and automate cleanup.
6. Backup Verification: Regularly validate backups with RMAN to ensure recoverability.

12.What happens when you type recover database?

A: When you type RECOVER DATABASE in RMAN, the following actions occur:
1. Apply Archive Logs: RMAN applies archived redo logs to bring the database up to
the desired point in time, ensuring consistency and data integrity.
2. Manage Missing Logs: If any required logs are missing, RMAN may prompt you to
provide them. If no logs are missing, it applies all available logs.
3. End of Recovery: The recovery process ends once all necessary logs are applied, and
the database is synchronized with the latest changes.
4. Open Database: After recovery, you can open the database with ALTER DATABASE
OPEN.

RMAN> CONNECT TARGET /;

RMAN> STARTUP MOUNT;
RMAN> RECOVER DATABASE;
RMAN> ALTER DATABASE OPEN;

13.I lost my entire database. Tell me the steps you will follow to recover the database?
A: To recover a lost database:
1. Restore the Latest Backup:
Use RMAN to restore the most recent full backup of the database.
RMAN> RESTORE DATABASE;
2. Apply Archive Logs:
Restore all missing archive logs to bring the database to the point of failure.
RMAN> RECOVER DATABASE;
3. Open the Database:
Once recovery is complete, open the database.
RMAN> ALTER DATABASE OPEN;
4. Perform Post-Recovery Checks:
Verify data consistency and perform necessary checks to ensure the database is functioning
properly.

14.My controlfile retention is 30 days. I want to recover my database from a backup 45

days old. How will you perform the activity when the backup details are not there
in the controlfile?
A: If the backup details are not in the control file due to a 30-day retention policy, follow these steps
to recover the database using a 45-day-old backup:
 1. Locate the Backup: Identify the backup files and archived redo logs from the storage
location.
2. Catalog the Backup in RMAN:
RMAN> CATALOG START WITH '/path_to_backup_files/';
3. Restore and Recover the Database:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;
4. Open the Database:
RMAN> ALTER DATABASE OPEN RESETLOGS;
This process ensures RMAN recognizes the older backup and uses it for recovery.

15.Why you will not recommend catalog scripting over shell scripting for backups?
A: Reasons to Avoid Catalog Scripting for Backups:
• Dependency on Catalog: Requires RMAN catalog availability, creating risks if the catalog is
corrupted or inaccessible.
• Limited Flexibility: Cannot integrate with OS-level tools or external monitoring systems.
• Lack of Advanced Error Handling: Catalog scripts have limited options for custom error handling
and notifications.
• Portability Issues: Difficult to reuse across different environments or databases.
• Limited Scheduling Options: Cannot integrate directly with cron or other scheduling tools.
• Less Versatile: Shell scripts offer more control, customization, and integration capabilities.

For robust backup management, shell scripting is more reliable and adaptable.

16.Restoring database without controlfile? Using trace file.

A: 1. Restore datafiles , undo files, user tablespaces from old backup.
2.start the db in nomount state :startup nomount;
3.recreate the controlfile from trace file
Alter database backup controlfille to trace;
recover database using backup controlfile;
Alter database open resetlogs;

17.Archives are not arriving at the standby. What will you check?(IMP)
A: If archives are not arriving at the standby, follow these checks:
1. Network Connectivity: Ensure the primary and standby databases can communicate over the
network (ping, tnsping).
2. ARCH Process on Primary: Verify the ARCH process is running on the primary and actively shipping
logs:
SQL> SELECT process, status FROM v$managed_standby;
3. Log Shipping Settings: Check if log shipping is enabled (log_archive_dest_2 on primary and
log_archive_dest on standby).
4. Standby Redo Log Availability: Ensure standby redo logs are configured and available.
5. Archive Log Space: Check for space in the archive destination on the primary and standby.
 6. Log Transfer Errors: Use alert.log and v$archive_dest for errors.
7. Configuration on Primary: Ensure LOG_ARCHIVE_CONFIG is set correctly on the primary database.
Resolve any issues and restart the log shipping if necessary.

1. Tell me the steps to configure physical standby? imp

A: To configure a physical standby database:
1. Prepare Primary Database:
• Enable archiving:
ALTER SYSTEM SET LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf' and ALTER SYSTEM SET
LOG_ARCHIVE_DEST_1='LOCATION=...';
• Enable force logging: ALTER DATABASE FORCE LOGGING;
2. Backup Primary Database:
• Take an RMAN full backup: BACKUP DATABASE PLUS ARCHIVELOG;
3. Set up Standby Database:
• Restore the backup on the standby server.
• Configure the init.ora or spfile to include standby_file_management=auto.
4. Configure Data Guard:
• On the primary, configure LOG_ARCHIVE_DEST_2 for standby.
• On the standby, configure LOG_ARCHIVE_DEST_1 for receiving logs.
5. Start Managed Recovery on Standby:
• ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE
DISCONNECT FROM SESSION;
Ensure both databases are synchronized and in sync.

18.Explain the difference between flashback database and database PITR?

A: Flashback Database:
• Restores the entire database to a specific point in time.
• Uses undo and redo data to revert database changes.
• Faster recovery for recent mistakes or user errors.
• Requires flashback logs to be enabled.
Database PITR (Point-in-Time Recovery):
• Recovers the database to a specific time or SCN.
• Typically used when the database is corrupted or data is lost.
• Involves restoring backups and applying archived redo logs.
• More time-consuming than Flashback Database.

Difference: Flashback Database is quicker and simpler for recent errors, while PITR involves
restoring backups and is useful for more severe recovery situations.

 How do you migrate database from windows to Linux?

A: To migrate an Oracle database from Windows to Linux, follow these steps:
1. Prepare the Environment:
• Install Oracle on the Linux server with the same version as the Windows server.
• Ensure the same directory structure for Oracle binaries and data files on both
systems.
 2. Backup the Database on Windows:
• Use RMAN to take a full backup or perform an exp/imp (Data Pump) export of your
database:
RMAN> BACKUP DATABASE;
3. Transfer the Backup to Linux:
• Use FTP, SCP, or another file transfer method to move the backup files from Windows
to the Linux server.
4. Restore the Backup on Linux:
If using RMAN, restore the backup on Linux:
RMAN> RESTORE DATABASE;
RMAN> RECOVER DATABASE;
• If using Data Pump, import the dump files:
impdp system/password@linuxdb DIRECTORY=dp_dir DUMPFILE=expdat.dmp LOGFILE=import.log
5. Adjust Configuration Files:
• Modify init.ora or spfile parameters if needed (e.g., file paths, network configurations).
• Update tnsnames.ora, listener.ora, and sqlnet.ora as necessary for Linux.
6. Start the Database:
• After restoring and configuring, start the database:
sqlplus / as sysdba
startup
7. Test the Database:
• Verify that everything is running properly by checking logs and running queries.

1. You have a database in ARCHIVELOG mode, and a tablespace is corrupted. How do you
recover it without affecting the rest of the database?
A: To recover a corrupted tablespace in an ARCHIVELOG mode database without affecting the rest of the
database:
1. Take the Tablespace Offline:
ALTER TABLESPACE tablespace_name OFFLINE;
2. Restore the Datafiles:
Restore the corrupted tablespace’s datafiles from the most recent backup:
RMAN> RESTORE TABLESPACE tablespace_name;
3. Recover the Tablespace:
Apply the archive logs to bring the tablespace up-to-datet
RMAN> RECOVER TABLESPACE tablespace_name;
4. Bring the Tablespace Online:
ALTER TABLESPACE tablespace_name ONLINE;
This ensures minimal impact to the rest of the database while recovering the corrupted tablespace.

2. Your RMAN backup fails due to a lack of disk space. How would you resolve the issue
without affecting the backup schedule?
A: To resolve an RMAN backup failure due to a lack of disk space without affecting the backup schedule:
1. Free Up Disk Space:
• Delete old or obsolete backups using RMAN:
RMAN> DELETE OBSOLETE;
• Crosscheck and delete expired backups:
RMAN> CROSSCHECK BACKUP;
RMAN> DELETE EXPIRED BACKUP;
2. Use Compression:
Enable RMAN backup compression to reduce the size of backups:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
3. Redirect Backups to Another Disk:
Change the backup destination to a disk with sufficient space:
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/new_disk/backup_%U';

3. After restoring a database from a backup, you notice missing archive logs. How do you
proceed to apply the missing logs?
A: To handle missing archie logs after restoring a database:
1. Check if the Logs Are Truly Missing:
Use RMAN to list the required archive logs:
RMAN> LIST ARCHIVELOG ALL;
2. Locate Logs on Backup:
If the logs are backed up, restore them:
RMAN> RESTORE ARCHIVELOG FROM SEQUENCE start_seq TO end_seq;
3. Use Redo Logs for Recovery:
If archive logs are unavailable but redo logs contain the changes, recover using:
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
Apply the available logs and cancel when prompted for the missing logs.
4. Open the Database with Data Loss (if unavoidable):
If logs cannot be recovered:
ALTER DATABASE OPEN RESETLOGS;

18. The database is running out of space, and you need to add a new datafile to a
tablespace. How do you do this using RMAN or SQL?
A: To add a new datafile to a tablespace using SQL or RMAN, follow these steps:
Using SQL:
1. Add the Datafile:
ALTER TABLESPACE giri
ADD DATAFILE '/path/to/datafile/<datafile_name>.dbf' SIZE <size_in_MB>M;
Using RMAN:
1. Use RMAN to Add Datafile:
rman target /
SQL 'ALTER TABLESPACE <tablespace_name> ADD DATAFILE ''/path/to/datafile/<datafile_name>.dbf'' SIZE
<size_in_MB>M';

2. What are the differences between hot, cold, and incremental backups in Oracle, and
when would you use each?
A: 2. Differences Between Hot, Cold, and Incremental Backups:
• Hot Backup: Database remains online. Used when high availability is required (e.g., using
RMAN with ARCHIVELOG mode).
• Cold Backup: Database is offline. Ideal for simpler recovery scenarios but requires
downtime.
 • Incremental Backup: Backs up only changed data since the last full or incremental backup.
Reduces backup time and space usage.

11. Concurrent managers

1. What is the role of the Concurrent Manager in Oracle E-Business Suite?

The Concurrent Manager controls and manages the execution of concurrent requests (background jobs) submitted by
users. It ensures efficient processing by scheduling, prioritizing, and executing the requests.

2.What is concurrent request?

A: In oracle EBS concurrent requests are background tasks that perform operations like reports, data update or batch
jobs. These are managed by concurrent manager execute synchronously, allowing users to work without delay.
Each request generates a logfiles and follows a life cycle. Pending, Running, Completed or failed for troubleshoot.

2. What are the different types of Concurrent Managers in Oracle EBS?

Internal Concurrent Manager (ICM): Manages all other Concurrent Managers.
Standard Manager: Processes requests not assigned to any specific manager.
Conflict Resolution Manager (CRM): Resolves request conflicts (e.g., programs that cannot run simultaneously).
Custom Managers can also be defined to handle specific request types.

3. How do you check the status of the Concurrent Managers?

Use the Concurrent Manager Administer form in Oracle Applications.
From the command line:
adcmctl.sh status apps/<password>

4. Where are the log and output files of Concurrent Requests stored?
They are stored in:
$APPLCSF/$APPLLOG (for logs)
$APPLCSF/$APPLOUT (for outputs)
The exact file names can be retrieved from the Concurrent Request Details screen.

5. What are common reasons for a Concurrent Request to fail?

 Database issues like invalid objects or insufficient tablespace.
 File system issues (e.g., insufficient disk space).
 Permissions or configuration errors in the Concurrent Manager.
 Errors in the program logic, such as unhandled exceptions.

6. How do you troubleshoot a failed Concurrent Request?

 Check the Request Log File for detailed error messages.
 Review the Concurrent Manager Log for system-level issues.
 Look for database errors in the alert log.
 Identify conflicts using the Administer Concurrent Manager form.

7. How do you handle a hung or stuck Concurrent Manager?

Verify the status using:
adcmctl.sh status apps/<password>
Stop and restart the manager:
adcmctl.sh stop apps/<password>
adcmctl.sh start apps/<password>
 If it still hangs, check for issues in the ICM log and database.

8. What is the purpose of the Conflict Resolution Manager (CRM)?

CRM ensures that conflicting programs (e.g., programs requiring exclusive access) do not run simultaneously by
resolving such conflicts automatically.

9. How do you increase the number of Concurrent Processes?

Navigate to System Administrator → Concurrent → Manager → Define.
Select the manager and update the “Processes” field to increase the number.
Bounce the manager for the changes to take effect.
adcmctl.sh stop apps/<password>
adcmctl.sh start apps/<password>

10. What is the significance of the FND_CONCURRENT_REQUESTS table?

This table stores details of all concurrent requests, including their status, start time, end time, and logs.
Key columns:
REQUEST_ID: Unique ID of the request.
PHASE_CODE/STATUS_CODE: Indicates the status (e.g., PENDING, COMPLETED).
LOGFILE_NAME/OUTFILE_NAME: Paths to the request’s log and output files.