Script – Check RMAN Backup Status

Script – Check RMAN Backup Status
===============================
Scripts to check backup status and timings of database backups –

This script will be run in the database, not the catalog database.

Login as sysdba –

This script will report on all backups – full, incremental and archivelog backups –
=============================================================

col STATUS format a9
col hrs format 999.99
select
SESSION_KEY, INPUT_TYPE, STATUS,
to_char(START_TIME,'mm/dd/yy hh24:mi') start_time,
to_char(END_TIME,'mm/dd/yy hh24:mi')   end_time,
elapsed_seconds/3600                   hrs
from V$RMAN_BACKUP_JOB_DETAILS
order by session_key;


This script will report all on full and incremental backups, not archivelog backups –
==============================================================
col STATUS format a9
col hrs format 999.99
select
SESSION_KEY, INPUT_TYPE, STATUS,
to_char(START_TIME,'mm/dd/yy hh24:mi') start_time,
to_char(END_TIME,'mm/dd/yy hh24:mi')   end_time,
elapsed_seconds/3600                   hrs
from V$RMAN_BACKUP_JOB_DETAILS
where input_type='DB INCR'
order by session_key;

Compile Jsp’s in R12 & 11i

Compile Jsp’s in R12 & 11i

=====================

$cd $ADMIN_SCRIPTS_HOME

$adopmnctl.sh stopall — to shutdown opmn managed services viz., opmn, forms, oacore & oc4j

 $ cd $COMMON_TOP/_pages

$ mv _pages _pages_old

$mkdir _pages

 $ cd $FND_TOP/patch/115/bin or export PATH=$FND_TOP/patch/115/bin:$PATH

Compile all jsps.

$perl ojspCompile.pl –compile –flush -p 2 (or) ojspCompile.pl --compile --fast --quiet

(-p represents parallel threads, if you have enough horse power on your server, you can increase it to 8 or 10)

$cd $ADMIN_SCRIPTS_HOME

Another Option

==============

STEP1.

Login as applmgr user and source the environment by running the script:

/oracle/apps/apps_st/appl/APPS[SID]_[host].env

STEP2:  Run the commands

In Linux/Unix

cd $FND_TOP/patch/115/bin

perl ojspCompile.pl --compile --flush -p 2

In Windows

cd %FND_TOP%\patch\115\bin

perl -x ojspCompile.pl –compile –flush

STEP3:

Restart the Apache services or Middleware services.

How to compile individual JSP manually in R12:

STEP1:

cd $COMMON_TOP/_pages

STEP2:

Delete the class files (abcdef.class) for the JSP that you want to compile manually.

Eg. JSP File abcdef_12.jsp

Class File: abcdef_12.class ------------- Delete this file.

STEP3:

Navigate to the OA_HTML (Location for all the Jsp pages). if the JSP pages do not exist, copy the JSP to the location & run the below command.

$FND_TOP/patch/115/bin/ojspCompile.pl --compile -s 'abcdef_12.jsp' --flush

STEP4:

Restart the Apache services or Middle-ware services.

STEP5:

Check whether the respective class files have been created under

cd $COMMON_TOP/_pages

To Compile JSP’s at runtime in Oracle Apps R12

===============================================

To compile the jsp as soon as you access jsp page :

1. Change s_jsp_main_mode in R12 context file (XML file)

  <jsp_debug_parameters oa_var=”s_jsp_main_mode”>justrun</jsp_debug_parameters>

change it to

  <jsp_debug_parameters oa_var=”s_jsp_main_mode”>recompile</jsp_debug_parameters>

2.Run Autoconfig (adautocfg.sh)

Autoconfig will update file

$INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml

        <param-name>main_mode</param-name>

         <param-value>justrun</param-value>

.

How to compile JSP manually

perl ojspCompile.pl –compile –flush  (Unix)

or

perl ojspCompile.pl –compile –flush -p 2 (Unix where -p means parallel execution)

perl -x ojspCompile.pl –compile –flush (Windows)

ojspCompile.pl is under $FND_TOP/patch/115/bin/

Note* JSP’s are compiled automatically after patching (whenever patch updates one or more jsp it calls ojspCompile.pl to compile JSP)

.

JSP Compilation logs

In 11i, all jsp compilation errors are logged in $IAS_ORACLE_HOME/ Apache/ Jserv/ logs/ mod_jserv.log

In R12, all jsp compilation errors are logged in $LOG_HOME/ ora/ 10.1.3/ j2ee/ oacore/ oacore_default_group_1/ application.log

458338.1  How to Enable Automatic Compilation of JSP pages in R12 Environment

433386.1  JSP Pages Hanging in R12 After Removing Cached Class Files in _pages

783094.1  Compile jsp files at Application R12 at Windows

Node ID does Not Exist for the Current Application Server ID Errors

Node ID  does not exist for the current application server id.
 The URL on which the above error occurs is as follows:

http://myhost.domain:port/dev60cgi/f60cgi

This error also occurs at the time of starting / stopping Apache.

adapcctl.sh start

adapcctl.sh stop

$INST_TOP/admin/install/adgendbc.sh

SOLUTION

1. Do a select on the server_id in the fnd_nodes table.  Here is an example of what it could look like:

server_id=EA99227ED75CFE4EE030149077C4515496138833635529486962342698410274

2. Do a search on APPL_SERVER_ID in the .dbc file.  It could show something like:

APPL_SERVER_ID=EA99220924EF823FE030149077C450C096138833635529486962342698410274

Please manually comment out the APPL_SERVER_ID in the .dbc file.

3. Then re-run adgendbc.sh and it will  seed the node and get a good  application id.

NOTE: If the server_id is missing from the FND_NODES table, ie. if the above SQL does not return anything
To get the FND_NODES table populated with the correct server ID, one may have to use:
Note 260887.1 ->Steps to Clean Nonexistent Nodes or IP Addresses from   FND_NODES

Please refer the Note 274476.1 and Note 363609.1 to have a detailed view to change the IP Address of the Database Server.
5) As the change is made at the OS (Operating System) level.Please ensure that the IP address gets reflected in the DNS server and also in the local host file.

REFERENCES

Correct Method of Changing the IP Address in 11i & R12 (Doc ID 751328.1)
pool fnd_nodes 
set pagesize 50 
col node_name format a15 
col server_id format a8 
col server_address format a15 
col platform_code format a4 
col webhost format a12 
col domain format a20 
col virtual_ip format a12 
set linesize 132 
select node_id, platform_code, support_db D, support_cp C, support_admin A, support_forms F, 
support_web W, node_name, server_id, server_address, domain, webhost, virtual_ip 
from fnd_nodes 
order by node_id;