Wednesday 20 August 2014

Arabic forms are not opening in R12.1.3

Soution:



Refered Note: 292942.1

1.A) Create the "9i behavior" file set:
you have 2 way's to do this:
1* OR Automatically (If you have perl installed)

run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.
$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/nls/data/old/cr9idata.pl
sample output:
Creating directory /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata ...
Copying files to /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata...
Copy finished.
Please reset environment variable ORA_NLS10 to /grdbms/64bit/patchdb/app/oracle/product/p12101a/nls/data/9idata!
After creating the fileset check that $ORACLE_HOME/nls/data/9idata contains more than 500 files
ls -l $ORACLE_HOME/nls/data/9idata | wc -l
note: if $ORACLE_HOME/nls/data/9idata already exist and you want to redo the file generation "to make sure" then it might be a good idea to shutdown all oracle processes using this ORACLE_HOME
2* OR Manually
note: if $ORACLE_HOME/nls/data/9idata already exist and you want to redo the file generation "to make sure" then it might be a good idea to shutdown all oracle processes using this ORACLE_HOME

a) make a new subdirectory under $ORACLE_HOME/nls/data called "9idata"

b) COPY all files in $ORACLE_HOME/nls/data/ to $ORACLE_HOME/nls/data/9idata

c) COPY all files from $ORACLE_HOME/nls/data/old to $ORACLE_HOME/nls/data/9idata
you will need to overwrite some files - this is normal.

on Unix this means:
* make sure the $ORACLE_HOME is set correctly
rm -r $ORACLE_HOME/nls/data/9idata
mkdir $ORACLE_HOME/nls/data/9idata
cp $ORACLE_HOME/nls/data/*.* $ORACLE_HOME/nls/data/9idata
cp $ORACLE_HOME/nls/data/old/*.* $ORACLE_HOME/nls/data/9idata
The ORDER is important, FIRST do point B) then do point C), do NOT inverse this.
d)After creating the 9i fileset check that $ORACLE_HOME/nls/data/9idata contains more than 500 files
* The $ORACLE_HOME/nls/data/old directory only contains the changed files, so you need to overwrite copy the more than 500 files of $ORACLE_HOME/nls/data/ to $ORACLE_HOME/nls/data/9idata and then overwrite some files in $ORACLE_HOME/nls/data/9idata with the ones found in $ORACLE_HOME/nls/data/old .
* You cannot use Oracle9i (or earlier) NLB files in Oracle10g and up.
* You cannot use the new Oracle10g definitions in Oracle9i and lower.
4.B) Enable the Oracle9i behavior:
After creating the "9i behavior" file set you need to point ORA_NLS10 to $ORACLE_HOME/nls/data/9idata instead of the default $ORACLE_HOME/nls/data/ directory and start the database *and* listener on the server using the new setting.

NOTE:  The creation of the "Oracle9i behavior" files and setting ORA_NLS10 to $ORACLE_HOME/nls/data/9idata should be done on the database server AND on all 10g/11g clients which connect to this system (!).
On Unix you need to set the ORA_NLS10 variable for the Oracle user or any other Unix user that stops and starts the listener/database. Make sure to not forget any startup scripts when the server starts up.
When using RAC you need ALSO set the ORA_NLS10 variable using srvctl
$ srvctl setenv database -d <dbname> -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata
-- set it for all RAC managed listeners
$ srvctl setenv listener -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata
-- set it for one specific listener
$ srvctl setenv listener -l <listener_name> -t ORA_NLS10=$ORACLE_HOME/nls/data/9idata


$ srvctl stop database -d <dbname>
$ srvctl stop listener
$ srvctl start listener
$ srvctl start database -d <dbname>

After the restart of the database and listener check the result using sqlplus from the database $ORACLE_HOME 
export ORA_NLS10=$ORACLE_HOME/nls/data/9idata
sqlplus / as sysdba
select to_char(to_date( '18/04/2009', 'DD/MM/YYYY'),'DD-MON-YYYY', 'NLS_DATE_LANGUAGE=FRENCH') from dual;
-- this should give 18-AVR-2009
if this is correct then the *database* side is fine.


    

Tuesday 5 August 2014

Patch is hanging while applying HRMS RUP6 patch

Issue Details:

 Patch is running XDOLoader.class file

 By seeing worker log file getting below error I found below error

SQLState: null
Message: Io exception: There is no process to read data written to a pipe.
Vendor: 17002
java.sql.SQLException: Io exception: There is no process to read data written to a pipe.
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Proto .handleIOException(TTC7Protocol.java:3664)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:353)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:371)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:551)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:351)
at java.sql.DriverManager.getConnection(DriverManager.java:559)
at java.sql.DriverManager.getConnection(DriverManager.java:211)
at oraConn.main(oraConn.java:9)

Soution:

 Kill the current patch session and restart the patch session with low workers.

See Metalink note :1459733.1

Sunday 3 August 2014

Concurrent request is failed with REP-0124,REP-0002 Errors in R12

Symptoms:

Enter Password:
REP-0081: Error during file I/O operation.
REP-0124: Unable to write to the temporary file.
scafa 3
REP-0002: Unable to retrieve a string from the Report Builder message file.
REP--1870639101:
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP--1870639101: Error during file I/O operation.
REP-0124: Unable to write to the temporary file.
scafa 3
REP-0002: Unable to retrieve a string from the Report Builder message file.
REP--1870639101:

Solution:
1. Check the utl_file_dir path wich is creating temp files
2. Delete some temp files from /tmp (utl_file_dir) location
3.If you still facing the issue, check the size of report which is user trying to generate using concurrent request and ask the user to reduce the report size using parameters.
4. Still you are facing issue log SR.

Monday 28 July 2014

POST CLONE STEPS in 11i/R12:
++++++++++++++++++++++++++++++++++++++++++
1.select distinct OUTFILE_NODE_NAME from FND_CONCURRENT_REQUESTS ;

2.select distinct LOGFILE_NODE_NAME from FND_CONCURRENT_REQUESTS ;
3.select node_name , status from fnd_nodes


   CHECK ALL THE NODE NAMES IF YOU FOUND ANY SOURCE NODE NAMES THEN FOLLOW THE STEPS BELOW.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==
1. Make a backup copy of the FND_RUN_REQUESTS, FND_CONCURRENT_REQUESTS, and
FND_CONCURRENT_PROCESSES tables

2. Run the following statements to remove the rows that refer to the node that
is no longer available.. (ERP is an example value)

delete FND_RUN_REQUESTS WHERE parent_request_id
in (select request_id from FND_CONCURRENT_REQUESTS where
upper(LOGFILE_NODE_NAME) = 'ERP'
or upper(OUTFILE_NODE_NAME) = 'ERP');

delete FND_CONCURRENT_REQUESTS where upper(LOGFILE_NODE_NAME) = 'ERP' or
upper(OUTFILE_NODE_NAME) = 'ERP';

delete FND_CONCURRENT_PROCESSES where upper(NODE_NAME) = 'ERP';


commit;




PATCH IS HANGING BY ALLOCATING MORE NUMBER OF USERS

1459733.1
ORA-00020 Error in Alert log file:

How to increase PROCESSES initialization parameter:

1.    Login as sysdba
    sqlplus / as sysdba
   
2. Check Current Setting of Parameters
    sql> show parameter sessions
    sql> show parameter processes
    sql> show parameter transactions

3.    If you are planning to increase "PROCESSES" parameter you should also plan to increase "sessions and "transactions" parameters
    A basic formula for determining  these parameter values is as follows:
   
        processes=x
        sessions=x*1.1+5
        transactions=sessions*1.1
       
4.    These paramters can't be modified in memory. You have to modify the spfile only (scope=spfile) and bounce the instance.
    sql> alter system set processes=500 scope=spfile;
    sql> alter system set sessions=555 scope=spfile;
    sql> alter system set transactions=610 scope=spfile;
    sql> shutdown abort
    sql> startup
oracle.apps.fnd.framework.OAException: Illegal method call because there is no database connection.

Please review the document Login Fails Intermittently With: Application: Fnd, Message Name: FND_NO_DATABASE_CONNECTION (Doc ID 1298103.1)

12.1.2 and 12.1.1 Customers
Apply and test patch 9908921
Be sure to stop and start application tier services after the patch is applied

12.1.3 Customers
Apply and test patch 11832737