Page-4
46: What is adsplice utility ?
A: adsplice in oracle apps is utility to add a new product.
47: Can you enable diagnostics for EBS?
A: Yes. Enable profile option FND: Diagnostics.
48: adident utility is used for what ?
A: adident utility in oracle apps is used to find version of any file . AD Identification. for ex. "adident Header
49: Why do you need GUEST/ORACLE To connect to database?
A: The GUEST user account is used in the application internally (it is an application user). One of the major needs of this account is when there is a need to decrypt the APPS password (which is stored in an encrypted format in the apps tables). In order to decrypt the APPS password, the GUEST username/password is used to accomplish this task (using “Guest User Password” profile option). GUEST account is used to obtain the decrypted value of the apps password for internal processes (i.e. when there is a need to connect as apps internally). when the account gets locked/end dated then you will see a blank page when you try to login to the instance.In that scenario you will have to correct this situation from the backend as you will not be able to login to the application. You will not find much details about the GUEST account documented anywhere ( may be coz of security reasons).
50: Does the Internal manager schedule requests to be run or does it put requests into queues to be run by other managers?
A: This is a very common misconception. The ICM really does not have any such scheduling responsibilities. It has NOTHING to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run 'queue control' requests, which are requests to startup or shutdown other managers. It is responsible for startup and shutdown of the whole concurrent processing facility, and it also monitors the other managers periodically, and restarts them if they should go down. It can also take over the Conflict Resolution manager's job, and resolve incompatibilities. If the ICM itself should go down, requests will continue to run normally, except for 'queue control' requests. You can restart it with 'startmgr', you do not need to kill the other managers first.
51: I hit the Restart button to start the Standard manager, but it still did not start?
A: Telling a manager to restart just sets the status to Restart. The ICM will start it the next process monitor session or the next time the ICM starts. Use Activate to start a manager immediately. When a manager is deactivated manually, the ICM will not restart it, you will need to set it to Restart, or activate it manually
52: What is your day to day activity as an Apps DBA?
A: As an Apps DBA we monitor the system for different alerts (Enterprise Manager or third party tools used for configuring the Alerts) Tablespace Issues, CPU consumption Database blocking sessions..etc Regular maintenance activities like cloning,patching,custom code migrations (provided by developers) Working with user issues.
53: How often Do you patch?
A: Usually for non-production the patching request comes around weekly 4-6 and the same patches will be applied to Production in the outage or maintenance window. Production has weekly maintenance window (Eg Sat 6PM to 9PM) where all the changes (patches) will applied on production.
54: How often Do you clone?
A: Cloning happens biweekly or monthly depending on the organization requirement.
55: What is the meaning QA,CRP,SIT,DEV,UAT,PRE-PROD,PROD Instance?
A:
QA - Testing Instance
CRP - Conference Room Pilot
SIT - System Integration Testing
DEV - Development
UAT- User Acceptance Testing
STAGE - Pre-production Instance
Prod - Production/actual instance where the business is running
55: What do we have in FND_NODES?
A: FND_NODES table contains information about node_names and services enabled on a node. In multinode instance if you want to know which node is running what services, You can query the fnd_nodes and get that information.
56: when do we run FND_CONC_CLONE.SETUP_CLEAN ?
A: FND_NODES table contains node information, If you have cloned test instance from production still the node information of production will be present after clone in the test instance. we use FND_CONC_CLONE.SETUP_CLEAN to cleanup FND_NODES table in the target to clear source node information as part of cloning.
Below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.This will delete all the entries in the fnd_nodes table, to populate it with target system node information, Run autoconfig on DB node and Applications node.
57: What is contex t file?
A: Contex t file is a central repository , which stores all application configuration information. The name is like _ .xml
<< page-3 >>
A: adsplice in oracle apps is utility to add a new product.
47: Can you enable diagnostics for EBS?
A: Yes. Enable profile option FND: Diagnostics.
48: adident utility is used for what ?
A: adident utility in oracle apps is used to find version of any file . AD Identification. for ex. "adident Header
49: Why do you need GUEST/ORACLE To connect to database?
A: The GUEST user account is used in the application internally (it is an application user). One of the major needs of this account is when there is a need to decrypt the APPS password (which is stored in an encrypted format in the apps tables). In order to decrypt the APPS password, the GUEST username/password is used to accomplish this task (using “Guest User Password” profile option). GUEST account is used to obtain the decrypted value of the apps password for internal processes (i.e. when there is a need to connect as apps internally). when the account gets locked/end dated then you will see a blank page when you try to login to the instance.In that scenario you will have to correct this situation from the backend as you will not be able to login to the application. You will not find much details about the GUEST account documented anywhere ( may be coz of security reasons).
50: Does the Internal manager schedule requests to be run or does it put requests into queues to be run by other managers?
A: This is a very common misconception. The ICM really does not have any such scheduling responsibilities. It has NOTHING to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run 'queue control' requests, which are requests to startup or shutdown other managers. It is responsible for startup and shutdown of the whole concurrent processing facility, and it also monitors the other managers periodically, and restarts them if they should go down. It can also take over the Conflict Resolution manager's job, and resolve incompatibilities. If the ICM itself should go down, requests will continue to run normally, except for 'queue control' requests. You can restart it with 'startmgr', you do not need to kill the other managers first.
51: I hit the Restart button to start the Standard manager, but it still did not start?
A: Telling a manager to restart just sets the status to Restart. The ICM will start it the next process monitor session or the next time the ICM starts. Use Activate to start a manager immediately. When a manager is deactivated manually, the ICM will not restart it, you will need to set it to Restart, or activate it manually
52: What is your day to day activity as an Apps DBA?
A: As an Apps DBA we monitor the system for different alerts (Enterprise Manager or third party tools used for configuring the Alerts) Tablespace Issues, CPU consumption Database blocking sessions..etc Regular maintenance activities like cloning,patching,custom code migrations (provided by developers) Working with user issues.
53: How often Do you patch?
A: Usually for non-production the patching request comes around weekly 4-6 and the same patches will be applied to Production in the outage or maintenance window. Production has weekly maintenance window (Eg Sat 6PM to 9PM) where all the changes (patches) will applied on production.
54: How often Do you clone?
A: Cloning happens biweekly or monthly depending on the organization requirement.
55: What is the meaning QA,CRP,SIT,DEV,UAT,PRE-PROD,PROD Instance?
A:
QA - Testing Instance
CRP - Conference Room Pilot
SIT - System Integration Testing
DEV - Development
UAT- User Acceptance Testing
STAGE - Pre-production Instance
Prod - Production/actual instance where the business is running
55: What do we have in FND_NODES?
A: FND_NODES table contains information about node_names and services enabled on a node. In multinode instance if you want to know which node is running what services, You can query the fnd_nodes and get that information.
56: when do we run FND_CONC_CLONE.SETUP_CLEAN ?
A: FND_NODES table contains node information, If you have cloned test instance from production still the node information of production will be present after clone in the test instance. we use FND_CONC_CLONE.SETUP_CLEAN to cleanup FND_NODES table in the target to clear source node information as part of cloning.
Below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.This will delete all the entries in the fnd_nodes table, to populate it with target system node information, Run autoconfig on DB node and Applications node.
57: What is contex t file?
A: Contex t file is a central repository , which stores all application configuration information. The name is like _ .xml
<< page-3 >>
