=========================
The file adconfig.sh and all of its supporting scripts are located in the
$AD_TOP/bin directory.
Patches to the Rapid Install product, also known as
ADX, update the templates and the parameters in the XML file. All application
processes should be shut down prior to executing adconfig.sh.
As of version 11.5.10, Oracle introduced the
adautocfg.sh script in the $COMMON_TOP/admin/scripts/$CONTEXT_NAME directory
to serve as a wrapper to adconfig.sh. When executing adautocfg.sh, the
location of the context file is not required.
The log file for the execution of adconfig.sh on the application tier is
located here, where MM is the month, DD is the day, hh is the hour, and mm is the
minute when adconfig.sh was executed:
$APPL_TOP/admin/$CONTEXT_NAME/log/MMDDhhmm/adconfig.log
The log file for the execution of adconfig.sh on the database tier located
here, with MMDDhhmm having the same meaning:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDhhmm/adconfig.log
Location of adconfig.sh Backup Files:
$APPL_TOP/admin/$CONTEXT_NAME/out/MMDDhhmm
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/out/MMDDhhmm
If you want to restore configuration files from the backup of an adconfig.sh run,
you can execute the $APPL_TOP/admin/$CONTEXT_NAME/out/MMDDhhmm/restore.sh
script. On the database server, this script will be found in the $ORACLE_HOME/
appsutil/out/$CONTEXT_NAME/MMDDhhmm directory.
In order to migrate any customization tags from the manual
configuration files to the custom template, the adcustomizer.sh script
should be run on the node where the customizations have been made. The
AD Configuration utility will then apply customizations that are in the custom
template upon subsequent executions.
apachejserv logs from frontend.txt
===================================
http://xxxx.us.oracle.com:8010/apachelogs .
http://xxxx.us.oracle.com:8010/jservlogs .
building xml file.txt
=====================
If the application context file does not exist, it can be created by executing the adbldxml.sh script:
$ ./$AD_TOP/bin/adbldxml.sh
Change a charset set on Oracle 8i.txt
=====================================
uppose you have Oracle 8.1.x installed on Unix.
1. Check the database NLS settings:
select * from nls_database_parameters;
Note: The character set changing does not affect an existing data, it changes the character set declaration. If the new character set is a binary subset of the old one, then you do not need to worry about the data conversion. Otherwise, use export/import utilities.
In our case the old character sets is US7ASCII, the new one is WE8ISO8859P1.
2. Set the PARALLEL_SERVER parameter in the init.ora file to false. Or do not set it at all.
3. Shutdown the database:
$ svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown
4. Mount the database:
startup mount
5. Issue the following commands:
alter system enable restricted session;
alter system set job_queue_processes=0;
alter system set aq_tm_processes=0;
6. Open the database:
alter database open;
7. Change the database character set
alter database character set WE8ISO8859P1;
Also you might change the national character set:
alter database national character set WE8ISO8859P1;
8. Shutdown and startup the database
check aol jdbc pool status.txt
=================================
http://xxxx.us.oracle.com:8010/OA_HTML/jsp/fnd/AoljDbcPoolStatus.jsp
chk if jtf page is working.txt
==============================
Please run http://machine.name:port/OA_HTML/jtfqalgn.htm
Copy an open database.txt
=========================
Suppose you have Oracle 7 or Oracle 8 installed on Unix.
To make the copy of a existing database PROD_DB without shutting it down, follow these steps:
1. Create the init.ora file for your new database PROD_DB_COPY by making the copy of the parameter file of the PROD_DB database.
2. Make the following modifications in this copy of the init.ora file. Replace all references of PROD_DB on PROD_DB_COPY. Change all directories to point to the new locations.
3. Prepare the SQL script to recreate the control files for your new database. Make the backup of the control file on the PROD_DB database. Run the following command using SQL*Plus or Server Manager:
$ svrmgrl
SVRMGR> connect internal
SVRMGR> alter database backup controlfile to trace resetlogs;
SVRMGR> exit
This command generates the trace file in the user dump directory, see the USER_DUMP_DEST parameter in the init.ora file. Modify this trace file:
- remove header
- replace the old database name by the new one
- replace the next line:
CREATE CONTROLFILE REUSE ...
on
CREATE CONTROLFILE SET DATABASE ... RESETLOGS ...
- replace the contents of the LOGFILE section on the list of the redo logs with the new locations
- replace the contents of the DATAFILE section on the list of the datafiles with the new locations
- comment out the other commands, except CREATE CONTROLFILE.
4. Make the online backup of all tablespaces on PROD_DB. For each tablespace, bring it to the backup mode:
ALTER TABLESPACE tablespace_name BEGIN BACKUP;
Copy all datafiles that constitute the tablespace to the new location.
Bring the tablespace back to the normal mode:
ALTER TABLESPACE tablespace_name END BACKUP;
5. On PROD_DB run the following command:
ALTER SYSTEM ARCHIVE LOG CURRENT;
Copy all archived redo logs to the new location.
6. Change your ORACLE_SID to PROD_DB_COPY, start Server Manager and issue the following command:
STARTUP NOMOUNT;
After the database is mounted run the script to recreate the control files using the trace file that you modified before.
7. To begin the recovery your database, issue the following command:
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;
reapply all archived redo logs.
8. Open the database:
ALTER DATABASE OPEN RESETLOGS
Copy database;
Suppose that you have Oracle 7 installed on Unix and you don't use remote logins.
The name of the existing database is PROD_DB.
You want to create the new database TEST_DB - the exact copy of PROD_DB.
This is the short description of your actions:
· Make cold backup of PROD_DB database,
· shutdown it,
· copy its data and log files to a new location,
· create a new database based on the just copied files.
Here is the datailed explanation:
1. Create list (df_prod_db.lst) of the data files on PROD_DB. You can get it from DBA_DATA_FILES system view.
2. Create new list (df_test_db.lst) for TEST_DB database using file that you got at previous step (df_prod_db.lst).
3. Create script (cr_control.sql) to compose control files for the new database TEST_DB.
o Set environment variable ORACLE_SID to PROD_DB;
o Run svrmgrl and execute the next command:
$ svrmgrl
SVRMGR> connect internal
SVRMGR> alter database backup controlfile to trace resetlogs;
SVRMGR> exit
o Find our trace file ora_*.trc, it should be the latest at USER_DUMP_DEST directory (see parameter file).
o Copy ora_*.trc to cr_control.sql
o Edit cr_control.sql file:
- remove header
- replace old sid on a new one: PROD_DB on TEST_DB
- replace the next line:
CREATE CONTROLFILE REUSE ...
on
CREATE CONTROLFILE SET ...
- replace contents of LOGFILE section on the new (set new location, check space)
- replace content of DATAFILE section on the list the datafiles with new a locations, which was created earlier
- comment the next line:
RECOVER DATABASE USING BACKUP CONTROLFILE
4. Make a cold backup of the source database - PROD_DB.
5. Shutdown source database (PROD_DB).
$ svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown immediate
SVRMGR> exit
6. Copy data files (df_prod_db.lst) of PROD_DB to a new location (df_test_db.lst), for TEST_DB database.
7. Create parameter file for TEST_DB, you may copy it from PROD_DB or create a new one.
8. Set environment variable ORACLE_SID to TEST_DB;
Attention: if you set a wrong value, you may corrupt existing database.
9. Create new database TEST_DB.
$ svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown immediate
SVRMGR> @cr_control.sql
ATTENTION!
If the database was not created:
- make shutdown abort
$ shutdown abort
- fix errors
- depending on the error you may have to remove just created control and log files
- try to create a new database (TEST_DB) again
In case of success:
10. Change the GLOBAL_NAME of the database.
$ svrmgrl
SVRMGR> connect internal
SVRMGR> ALTER DATABASE RENAME GLOBAL_NAME TO TEST_DB;
SVRMGR> exit
current patchset level of applications.txt
=============================================
Technology Stack Binaries inclusive Database :
1. Source the 9i ORACLE_HOME Environment
2. Execute the script $ORACLE_HOME/appsutil/install/adlnkoh.sh
3. Source the iAS ORACLE_HOME Envrionment
4. Execute the script $ORACLE_HOME/bin/adlnkiAS.sh
5. Source the APPS Environment
6. Execute the script $ORACLE_HOME/bin/adlnk806.sh
Oracle E-Business-Suite Binaries :
1. Source the APPS Environment
2. Execute following command : adrelink.sh force=y "ad adadmin"
3. Execute adadmin
select --> '2. Maintain Applications Files menu'
select --> '1. Relink Applications programs'
--> select all modules to relink
database is 32 bit or 64 bit.txt
==================================
execute "file $ORACLE_HOME/bin/oracle" , you should see output like
/u01/db/bin/oracle: ELF 64-bit MSB executable SPARCV9 Version 1
which means you are on 64 bit oracle
If your oracle is 32 bit you should see output like
oracle: ELF 32-bit MSB executable SPARC Version 1
Now you know what should be bit of patch to download
db in restrict mode.txt
========================
. When the database is in restricted mode, only users, with CREATE SESSION and RESTRICTED SESSION system privileges, can connect to it.
To bring an instance in restricted mode, use the next command in SQLPlus:
ALTER SYSTEM ENABLE RESTRICTED SESSION;
If someone (user without RESTRICTED SESSION system privilege) was connected to the database before, when restricted mode was activated, all his/her session will stay alive, but all attempts to establish a new connection will fail.
To bring the database back in normal mode:
ALTER SYSTEM DISABLE RESTRICTED SESSION;
To bring the databas in restricted mode during startup, issue the next command from SVRMGRL:
STARTUP RESTRICT
The instance starts up in normal mode, by default.
disable maintainace mode.txt
=============================
sqlplus -s &un_apps/***** @/dmdf1i/applmgr/11510/ad/11.5.0/patch/115/sql/adsetmmd.sql ENABLE
enabling f60cgi login access.txt
==================================
PURPOSE
-------
How to enable the ability to login directly via the f60cgi.
SCOPE & APPLICATION
-------------------
The distribution of this note is set to 'Limited.' These steps are
intended for to enable DBAs to login to forms directly only for
troubleshooting purposes with guidance from Oracle Support.
Accessing f60cgi is disabled in 11.5.10
----------------------------------------
With increased security in Oracle EBusiness Suite 11.5.10, the ability to
connect directly to forms via f60cgi has been disabled. By default, a user will
see the following error after entering their username and password:
APP-FND-01542: This Applications Server is not authorized to access this database.
This is expected functionality.
Enabling f60cgi direct login
------------------------------
It is possible to login however this method should only be used when
debugging problems.
1. Backup and open $APPL_TOP/admin/
2. Update the context variable:
s_appserverid_authentication
By default in 11.5.10, this is set to SECURE.
In previous 11i versions, this was set to OFF.
For debug purposes, you can use ON or OFF.
Modes:
- ON : Partial
- SECURE : activates full server security (SECURE mode)
- OFF : deactivates server security
3. Run Autoconfig to instantiate the change.
You should now be able to access forms directly again using the f60cgi call.
4. After you have finished your Forms debugging, please reset
s_appserverid_authentication to SECURE and re-run Autoconfig.
Alternative option
---------------------
Running Autoconfig is the preferred method of updating
s_appserverid_authentication.
If you are unable to run Autoconfig during troubleshooting, you can run the
the following commands instead from $FND_TOP/secure directory:
Disable:
java oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION OFF DBC=host_visdemo1.dbc
Enable:
To activate basic server security, from the command line, enter:
jre oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION ON DBC=
To activate full server security (SECURE mode), from the command
line, enter:
jre oracle.apps.fnd.security.AdminAppServer apps/apps \
AUTHENTICATION SECURE DBC=
Check the status:
java oracle.apps.fnd.security.AdminAppServer apps/apps \
STATUS DBC=host_visdemo1.dbc
enabling jtf trace level.txt
=============================
Set up a standalone Apache listener on a standalone port
• Add the following line to jserv.properties
wrapper.bin.parameters=-DJTF_TRACE_LEVEL=7
• Shutdown listener after performing activity,
so that the session gets closed
JTF Trace Level Tracing Mode
3 Off
7 Normal Sql Tracing
11 Sql Tracing with bind
19 Sql Tracing with wait
35 Sql Tracing with binds and waits
for jtf issue chec.txt
=======================
+ In $OA_HTML/bin/appsweb.cfg and check the heartbeat parameter in minutes,
Search for the section that starts with
"3) Values for the Forms applet parameters:"
here look in for parameter heartbeat and share its value
3.In $APACHE_TOP/Apache/Jserv/etc/zone.properties and share the session.timeout
in miliseconds):
4. Login into Oracle Applications as SYSADMIN and search for profile options
- ICX:Session Timeout
- ICX: Session Timeout
- ICX:Limit Time
- ICX:Limit connect
imp factors for ICM tuning.txt
==============================
Sleep Time — The sleep time parameter indicates the seconds that the ICM should wait between checking for requests that are waiting to run. The default sleep time is 60, but you can lower this number if you see you have a lot of request waiting (Pending/Normal). However, reducing this number to a very low value many cause excessive cpu utilization.
PMON cycle — This is the number of sleep cycles that the ICM waits between the time it checks for concurrent managers failures, which defaults to 20. You should change the PMON cycle to a number lower than 20 if your concurrent managers are having problems with abnormal terminations.
Queue Size — The queue size is the number of PMON cycles that the ICM waits between checking for disabled or new concurrent managers. The default for queue size of 1 PMON cycle should be used
All of the concurrent managers, with the exception of the ICM and CRM, can be configured to run as many processes as needed, as well as the time and days a manager can process requests.
When the space in FND_CONCURRENT_PROCESSES and FND_CONCURRENT_REQUESTS exceed 50K, you can start to experience serious performance problems within your Oracle Applications. When you experience these space problems, a specific request called "Purge Concurrent Requests And/Or Manager Data" should be scheduled to run on a regular basis. This request can be configured to purge the request data from the FND tables as well as the log files and output files on accumulate on disk.
Cache Size
Concurrent manager performance can also be enhanced by increasing the manager cache size to be at lease twice the number of target processes. The cache size specifies the number of requests that will be cached each time the concurrent manager reads from the FND_CONCURRENT_REQUESTS table. Increasing the cache size will boost the throughput of the managers by attempting to avoid sleep time.
Analyzing Oracle Apps Dictionary Tables for High Performance
It is also very important to run the request Gather Table Statistics on these tables:
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_QUEUES.
Run the request "Analyze All Index Column Statistics" on the indexes of these tables. Since the APPLSYS user is the owner of these tables, so you can also just run the request Analyze Schema Statistics for APPLSYS.
Another popular way to troubleshoot the Concurrent Managers is to generate a trace file. This is done by setting the OS environment variable FNDSQLCHK to FULL, and running the request from the command line.
When you get a backlog of pending requests, you can first allocate more processes to the manager that is having the problem in order to allow most of the requests to process
Increase the number in the Processes column. Also, you may not need all the concurrent managers that Oracle supplies with an Oracle Applications install, so you can save resources by identifying the uneeded managers and disabling them
If the request remains in a phase of RUNNING and a status of TERMINATING after allocating more processes to the manager, then shutdown the concurrent managers, kill any processes from the operating system that won't terminate, and execute the following sqlplus statement as the APPLSYS user to reset the managers in the FND_CONCURRENT_REQUESTS table:
update fnd_concurrent_requests
set status_code='X', phase_code='C'
where status_code='T';
Changing Dispatching Priority within the Concurrent Manager
If there are requests that have a higher priority to run over other requests, you can navigate to Concurrent --> Program --> Define to change the priority of a request. If a priority is not set for a request, it will have the same priority as all other requests, or it will be set to the value specified in the user's profile option Concurrent:Priority.
Also, you can specify that a request run using an SQL optimizer mode of FIRST_ROWS, ALL_ROWS, RULE, or CHOOSE, and this can radically effect the performance of the SQL inside the Concurrent request. If several long running requests are submitted together, they can cause fast running requests to have to wait unnecessarily. If this is occurring, try to schedule as many long running requests to run after peak business hours. Additionally, a concurrent manager can be created to run only fast running requests
afcmstat.sql Displays all the defined managers, their maximum capacity, pids, and their status.
afimchk.sql Displays the status of ICM and PMON method in effect, the ICM's log file, and determines if the concurrent manger monitor is running.
afcmcreq.sql Displays the concurrent manager and the name of its log file that processed a request.
afrqwait.sql Displays the requests that are pending, held, and scheduled. afrqstat.sql Displays of summary of concurrent request execution time and status since a particular date.
afqpmrid.sql Displays the operating system process id of the FNDLIBR process based on a concurrent request id. The process id can then be used with the ORADEBUG utility.
afimlock.sql Displays the process id, terminal, and process id that may be causing locks that the ICM and CRM are waiting to get. You should run this script if there are long delays when submitting jobs, or if you suspect the ICM is in a gridlock with another oracle process.
JDK USED BY UR APACHE.txt
===========================
$MY_JAVA=`awk -F= '$1 ~ /^JSERVJAVA.*$/ {print $2}' \ $IAS_ORACLE_HOME/Apache/Apache/bin/java.sh`; \ $MY_JAVA -version
jvm pool monitor.txt
===================
Pool Monitor can be used to monitor the resource utilization
Application Module Pool
Memory Utilization
JVM JVM Properties
Pre 11i10: https://
11i10: Login->Diagnostics->Show Pool Monitor.
obtain formatted explain plan.txt
===================================
1. Create a Plan Table
----------------------------
Use the utlxplan.sql script to create the table as instructed below.
SQL> @?/rdbms/admin/utlxplan
Note that the plan table format can change between versions so ensure that you create it using the utlxplan script from the current version.
2. To Populate the Plan Table
--------------------------------------
SQL> explain plan for
Explained.
3. Displaying The Execution Plan
------------------------------------------
Version 9.2
--------------
With Oracle 9i version 9.2, Oracle supplies a utility called dbms_xplan. It is created by dbmsutil.sql which is called by catproc.sql. As such it should already be installed on most 9.2 databases.
To generate a formatted explain plan of the query that has just been 'explained':
SQL> set lines 130
SQL> set head off
SQL> spool
SQL> alter session set cursor_sharing=EXACT;
SQL> select plan_table_output from
table(dbms_xplan.display(‘PLAN_TABLE’, Null,’ALL’));
SQL> spool off
Version 10.2
----------------
In addition to the standard explain plan option, you can pull execution plans from the library cache if the SQL has already been executed.
a) To get the plan of the last executed SQL issue the following:
SQL> set linesize 150
SQL> set pagesize 2000
SQL> select * from table(dbms_xplan.display_cursor(null,null,
'ALL'));
b) If you know the hash value of the SQL, you can use
dbms_xplan.display_cursor as follows:
SQL> set linesize 150
SQL> set pagesize 2000
SQL> select * from TABLE(dbms_xplan.display_cursor('&SQL_ID',
&CHILD));
c) We can also get run time statistics with some additional
options and if we use the gather_plan_statistics hint.
e.g:
SQL> select /*+ gather_plan_statistics */ col1, col2 etc.....
SQL> set linesize 150
SQL> set pagesize 2000
SQL> select * from TABLE(dbms_xplan.display_cursor('&SQL_ID',
&CHILD,'ALL IOSTATS LAST'))
sql_id: specifies the sql_id value for a specific SQL statement, as shown in V$SQL.SQL_ID, V$SESSION.SQL_ID or V$SESSION.PREV_SQL_ID. If no sql_id is specified, the last executed statement of the current session is shown.
cursor_child_no: specifies the child number for a specific sql cursor, as in V$SQL.CHILD_NUMBER or in V$SESSION.SQL_CHILD_NUMBER, V$SESSION.PREV_CHILD_NUMBER. If not specified, all child cursors for the specified sql_id are displayed.
Note that to use the DISPLAY_CURSOR functionality, the calling user must have SELECT privilege on V$SQL_PLAN_STATISTICS_ALL, V$SQL, and V$SQL_PLAN, otherwise it will show an appropriate error message.
orainventory.txt
===================
What is oraInventory ?
oraInventory is repository (directory) which store/records oracle software products & their oracle_homes location on a machine. This Inventory now a days in XML format and called as XML Inventory where as in past it used to be in binary format & called as binary Inventory.
There are basically two kind of Inventory Global Inventory (also called as Central Inventory) and Local Inventory also called as Oracle Home Inventory.
Global Inventory ?
Global Inventory holds information about Oracle Products on a Machine. These products can be various oracle components like database, oracle application server, collaboration suite, soa suite, forms & reports or discoverer server . This global Inventory location will be determined by file oraInst.loc in /etc (on Linux) or /var/opt/oracle (solaris). If you want to see list of oracle products on machine check for file inventory.xml under ContentsXML in oraInventory (Please note if you have multiple global Inventory on machine check all oraInventory directories)
You will see entry like
HOME NAME="ORA10g_HOME" LOC="/u01/oracle/10.2.0/db" TYPE="O" IDX="1"/
...
...
Local Inventory
Inventory inside each Oracle Home is called as local Inventory or oracle_home Inventory. This Inventory holds information to that oracle_home only.
Can I have multiple Global Inventory on a machine ?
Quite common questions is that can you have multiple global Inventory and answer is YES you can have multiple global Inventory but if your upgrading or applying patch then change Inventory Pointer oraInst.loc to respective location. If you are following single global Inventory and if you wish to uninstall any software then remove it from Global Inventory as well.
What to do if my Global Inventory is corrupted ?
No need to worry if your global Inventory is corrupted, you can recreate global Inventory on machine using Universal Installer and attach already Installed oracle home by option
-attachHome
./runInstaller -silent -attachHome -invPtrLoc $location_to_oraInst.loc
ORACLE_HOME="Oracle_Home_Location" ORACLE_HOME_NAME="Oracle_Home_Name"
CLUSTER_NODES="{}"
Do I need to worry about oraInventory during oracle Apps 11i cloning ?
No, Rapid Clone will update both Global & Local Inventory with required information , you don't have to worry about Inventory during Oracle Apps 11i cloning.
patches applied on non shared appltop.txt
=========================================
select d.name, apps_system_name, f.bug_number, d.SERVER_TYPE_ADMIN_FLAG, d.SERVER_TYPE_FORMS_FLAG, d.SERVER_TYPE_NODE_FLAG,
d.SERVER_TYPE_WEB_FLAG from ad_patch_runs a, ad_patch_drivers b, ad_appl_tops d, AD_PATCH_RUN_BUGS e, ad_bugs f
where a.PATCH_DRIVER_ID = b.PATCH_DRIVER_ID
and f.bug_number in ('5479643','5483388','5486407','5500118','5518587','5521476','5571208','3748835')
and a.appl_top_id=d.appl_top_id
and a.PATCH_RUN_ID = e.PATCH_RUN_ID
and e.bug_id = f.bug_id
/
select a.name as "NODE NAME", b.driver_file_name as "FILE NAME",b.orig_patch_name as "PATCH NAME",b.platform as "PLATFORM", done.language as "LANGUAGE", c.success_flag as "SUCCESS",to_char(c.start_date,'dd-MON-yyyy hh24:mi:ss') as "START DATE",to_char(c.end_date,'dd-MON-yyyy hh24:mi:ss') as "END DATE" from ad_appl_tops a,ad_patch_drivers b,ad_patch_runs c,ad_patch_driver_langs done where b.patch_driver_id=c.patch_driver_id and c.appl_top_id=a.appl_top_id and done.patch_driver_id=c.patch_driver_id and b.orig_patch_name like '%4444880%' order by 1;
recovery using Transportable tablespaces.txt
============================================
here the target instance on which we are gong to do recovery is DFOMEI
and the instance from which are going to bring the data is DFOMEI
here the issue is '/dfomei/oradata/data01/a_nolog01.dbf' datafile has an issue with it nad we do not have any copy of it from theDFOMEI instance to recoverer.
so we shall be dropping the tablespace on the DEV instance and we shall be exporting the corr tablespace from the Test instance(using transportable tablespace) and we shall be then importing to the Dev instance again
Check on the Test instance for Integrity and constarints voilation
=============================================
SQL>EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('APPS_TS_NOLOGGING', TRUE);
PL/SQL procedure successfully completed.
SQL> SELECT * FROM transport_set_violations;
VIOLATIONS
--------------------------------------------------------------------------------
Constraint PAY_TEMP_BALANCE_ADJUST_FK1 between table HR.PAY_BALANCE_BATCH_LINES in tablespace APPS_TS_INTERFACE and table HR.PAY_TEMP_BALANCE_ADJUSTMENTS in tab lespace APPS_TS_NOLOGGING
Constraint SYS_C0030620 between table HR.PAY_BALANCE_BATCH_LINES in tablespace A PPS_TS_INTERFACE and table HR.PAY_TEMP_BALANCE_ADJUSTMENTS in tablespace APPS_TS _NOLOGGING
even when 2 violations are shown, there will be not problem since there is not data.
SQL> select count(*) from HR.PAY_BALANCE_BATCH_LINES;
COUNT(*)
----------
0
SQL> select count(*) from HR.PAY_BALANCE_BATCH_LINES;
COUNT(*)
----------
0
SQL> select owner, CONSTRAINT_TYPE, TABLE_NAME, R_CONSTRAINT_NAME, STATUS
2 from dba_constraints
3 where CONSTRAINT_NAME = '&2';
Enter value for 2: PAY_TEMP_BALANCE_ADJUST_FK1
old 3: where CONSTRAINT_NAME = '&2'
new 3:
where CONSTRAINT_NAME = 'PAY_TEMP_BALANCE_ADJUST_FK1'
OWNER C TABLE_NAME R_CONSTRAINT_NAME
---------- - ------------------------------ ------------------------------
STATUS
--------
HR R PAY_TEMP_BALANCE_ADJUSTMENTS PAY_BALANCE_BATCH_LINES_PK ENABLED
the above constraints needs to be disable to avoid the violations mentioned.
SQL> / Enter value for 2: SYS_C0030620 old 3: where CONSTRAINT_NAME = '&2' new 3: where CONSTRAINT_NAME = 'SYS_C0030620'
OWNER C TABLE_NAME R_CONSTRAINT_NAME
---------- - ------------------------------ ------------------------------
STATUS
--------
HR C PAY_TEMP_BALANCE_ADJUSTMENTS ENABLED
On DFOMEI:
1-. Take a cold backup of DFOMEI.
2. Offline drop the datafile. SQL> ALTER DATABASE DATAFILE '/dfomei/oradata/data01/a_nolog01.dbf' OFFLINE DROP;
3. If the database is at mount point, open it. SQL> ALTER DATABASE OPEN;
4. Drop the user tablespace. SQL> DROP TABLESPACE APPS_TS_NOLOGGING INCLUDING CONTENTS;
ON TFOMEI
------------------
5-. Disable Following constraints:
SQL> alter table HR.PAY_TEMP_BALANCE_ADJUSTMENTS disable constraints PAY_TEMP_BALANCE_ADJUST_FK1;
Table altered.
SQL> alter table HR.PAY_TEMP_BALANCE_ADJUSTMENTS disable constraints SYS_C0030620;
Table altered.
and run SQL> EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('APPS_TS_NOLOGGING', TRUE);
SQL> PL/SQL procedure successfully completed.
SQL> SELECT * FROM transport_set_violations;
SQL>
SQL> no rows selected make sure no rows selected.
6. Tablespaces. ------------
a. The tablespaces need to be in READ ONLY mode in order to successfully run a transport tablespace export.
SQL> ALTER TABLESPACE APPS_TS_NOLOGGING READ ONLY;
Export APPS_TS_NOLOGGING TS using the exp command. exp "'/ as sysdba'" file=exp_tts.dmp log=exp_tts.log transport_tablespace=y \ tablespaces=APPS_TS_NOLOGGING
On DFOMEI:
Copy the datafiles with the desired name in the desired directory.
from TFOMEI Server: auohsfome01 to DFOMEI Server: auohsfome01
cp /tfomei/oradata/data01/a_nolog01.dbf /dfomei/oradata/data01/a_nolog01.dbf -- Transfer the export dumpfile and all datafiles of the tranportable -- tablespace set in binary mode to the target $ORACLE_HOME (TFOMEI)
-- Copy the datafiles with the desired name in the desired directory. imp "'/ as sysdba'" file=exp_tts.dmp log=imp_tts.log \ transport_tablespace=y datafiles=/dfomei/oradata/data01/a_nolog01.dbf
TFOMEI
-----------
7. After the transport tablespace export and the copy of the datafiles, and after the plug-in of the tablespaces during the import),
the tablespaces can be changed back to READ WRITE mode.
SQL> ALTER TABLESPACE APPS_TS_NOLOGGING READ WRITE;
8. Enable constraints.
SQL> alter table HR.PAY_TEMP_BALANCE_ADJUSTMENTS enable constraints PAY_TEMP_BALANCE_ADJUST_FK1;
SQL> alter table HR.PAY_TEMP_BALANCE_ADJUSTMENTS enable constraints SYS_C0030620;
DFOMEI
-----------
9. After the transport tablespace export and the copy of the datafiles, and after the plug-in of the tablespaces during the import), the tablespaces can be changed back to READ WRITE mode.
SQL> ALTER TABLESPACE APPS_TS_NOLOGGING READ WRITE;
recreating con manager views.txt
====================================
goal: Re-create Concurrent Manager Views
fact: Oracle Application Object Library
fix:
For UNIX & Windows NT servers enter from the command prompt:
FNDLIBR FND FNDCPBWV apps/
SYSADMIN
For VMS servers enter from the command prompt:
FNDLIBR "FND" "FNDCPBWV" apps/
SYSADMIN" "System Administrator" "SYSADMIN"
relink full db and apps.txt
===========================
Technology Stack Binaries inclusive Database :
1. Source the 9i ORACLE_HOME Environment
2. Execute the script $ORACLE_HOME/appsutil/install/adlnkoh.sh
3. Source the iAS ORACLE_HOME Envrionment
4. Execute the script $ORACLE_HOME/bin/adlnkiAS.sh
5. Source the APPS Environment
6. Execute the script $ORACLE_HOME/bin/adlnk806.sh
Oracle E-Business-Suite Binaries :
1. Source the APPS Environment
2. Execute following command : adrelink.sh force=y "ad adadmin"
3. Execute adadmin
select --> '2. Maintain Applications Files menu'
select --> '1. Relink Applications programs'
--> select all modules to relink
responsibility User Management not visible.txt
============================================
After assigning the responsibility User Management or Approval Management to a user, the user
cannot use the same because there is an application error preventing so.
The issue is caused by the following setup: no grants were activated.
This is a requirement for use of User Management.
.
Solution
To implement the solution, please execute the following steps:
1. Change the setup for the associated user adding the Security Administrator Role to
them using the system administrator responsibility.
Using the system administrator responsibility, add the Security Administrator Role to the
intended user. The Security Administrator Role is a role available within User Management.
2. Also add the Functional Administrator administrator responsibility as you must assign
the functional and security administrator and then you should have menu choices.
Using the Functional Administrator responsibility:
a. Chose Core Services tab then Menus
b. Under Navigation Menus
c. Select Menu
d. Click Update
e. -= Menu Manager =-
f. Check "Grants" to activate
3. Please retest the issue.
4. If the issue is resolved, please migrate the solution as appropriate to other environments.
restart con mnager in unix.txt
=================================
TIP: Click help for a detailed explanation of this page.
Bookmark Go to End
Subject: How to Restart The Concurrent Manager in Unix.
Doc ID: Note:147449.1 Type: HOWTO
Last Revision Date: 21-NOV-2007 Status: PUBLISHED
Checked for relevance on 21-Nov-2007
Applications Install 11.0.3 to 11.5.10
goal: How to restart the concurrent manager in Unix
goal: How to bounce the concurrent manager in Unix
fact: Oracle Application Object Library
fix:
1. At the command line issue the following shutdown command:
CONCSUB apps/[APPS password] sysadmin 'System Administrator' SYSADMIN
CONCURRENT FND SHUTDOWN
Note: There are 3 options which can be used for controlling the Internal
Manager from the OS as follows:
SHUTDOWN = Standard, non-invasive shutdown.
DEACTIVATE = Will not allow further Requests to Process once Issued.
ABORT = Terminate Requests and Deactivate the Internal Manager.
2. At the command line, issue the following Start Up command:
startmgr sysmgr="[fnd_usernamd/fnd_password]" mgrname="[mgrname]" printer="[printername]"
mailto="[userid userid2...]" restart="[N|minutes]" logfile="[log_file_name]" sleep="
[new_check]" pmon="[manager_check]" quesiz="[number_check]" diag="[Y|N]"
Ex: startmgr sysmgr="applsys/apps" mgrname="std" printer="localprint"
mailto="jdoe jsmith" restart="N" logfile="mgrlog" sleep="90"
pmon="5" quesiz="10" diag="N"
Note: a space is required between arguments and the "diag" parameter
may be omitted if desired.
running Autoconfig manually.txt
================================
run adchkcfg.sh and the outputs will be generated at location " /ptagpi/applmgr/1158/admin/PTAGPI_auohstagp03/out/11260738/"
This location will have files in the form which reflects in case the autoconfig was run
So now manually copy the future files to the expected lcoations
cd /ptagpi/applmgr/1158/admin/PTAGPI_auohstagp03/out/11260738/
cp aplogon.html /ptagpi/applmgr/common/portal/PTAGPI_auohstagp03/
cp afadmprf.sql /ptagpi/applmgr/common/admin/install/PTAGPI_auohstagp03/
cp wdbsvr.app /ptagpi/product/iAS/Apache/modplsql/cfg/
cp zone.properties /ptagpi/product/iAS/Apache/Jserv/etc/
session timeout.txt
=====================
In order for session timeout to function properly, the session.timeout setting
in the zone.properties file must match the application profile option ICX: Session
Timeout. The session timeout value should not exceed 30 minutes. Values greater than
30 could result in JVM heap memory problems.
Submitting conc request from unix.txt
==========================================CONCSUB orauser/pwd RESP_APPL_SHRTNM responsibility USERNAME
[WAIT=check request status] CONCURRENT PROG_APPL_SHRTNM PROGRAM
[PROGRAM_NAME="program description"]
[REPEAT_DAYS=repeat interval]
[REPEAT_END="request re-submission end date"]
[START="date"]
[parameter 1] [parameter 2] . . .
Note: The tokens delimited by [ ] are optional.
Example
---------------
CONCSUB APPLSYS/FND SYSADMIN 'System Administrator' SYSADMIN WAIT=Y
CONCURRENT FND FNDMNRMT
START='"01-JAN-1999 23:00:00"' REPEAT_DAYS=1
REPEAT_END='"01-JAN-2001 23:59:00"' Y 0 0
supress apps password prompt.txt
=================================
Set profile option Utilities:Diagnostics to Yes in order to supress Apps password prompt.
surpass rapid install and directly reach login page.txt
=========================================================
1. Edit index.html and add at the top of the file :
content="0;url=http://
...
or
2. Add the following line in the url_fw.conf file
(should be under $IAS_CONFIG_HOME/Apache/Apache/conf directory):
RewriteRule ^/$ /OA_HTML/AppsLocalLogin.jsp [R,L]
then check that the following line exists in the httpd.conf file:
include "%s_iASconfig_home%/Apache/Apache/conf/url_fw.conf"
3. Bounce apache and clear browser caches
to delete wrongly named file.txt
================================
for i in `ls -q|grep F1`
do
rm $i
done
to use edit context.txt
=========================
To use the editcontext utility, execute the following commands:
$ export DISPLAY=myclient:0.0
$ cd $COMMON_TOP/util/editcontext
$ ./editcontext
when request in RUNNING + TERMINATING.txt
==========================================
If the request remains in a phase of RUNNING and a status of TERMINATING after allocating more processes to the manager, then shutdown the concurrent managers, kill any processes from the operating system that won't terminate, and execute the following sqlplus statement as the APPLSYS user to reset the managers in the FND_CONCURRENT_REQUESTS table:
update fnd_concurrent_requests
set status_code='X', phase_code='C'
where status_code='T';
No comments:
Post a Comment