How to use FNDCPASS


To change an Oracle Applications schema password (other than APPS/APPLSYS):-
[oracle@sujeet scripts]$ FNDCPASS apps/WELCOME 0 Y system/manager ORACLE GL GL1

Log filename : L390641.log
Report filename : O390641.out
To change the APPS and APPLSYS schema password:-

1.) Stop all application services.
2.) Start only database and database listener.
 [oracle@sujeet scripts]$ FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME

Log filename : L390640.log
Report filename : O390640.out
 You have new mail in /var/spool/mail/oracle
 SQL> conn applsys/WELCOME

 Connected.
 SQL> conn apps/WELCOME

Connected.

Note:- Check the FNDCPASS logfile for any error. If the password has changed successfully then run 
autconfig in application tier. Otherwise do not run autconfig. 



To change an Oracle Applications user's password:-
USER:-vision,operations,sysadmin..

[oracle@sujeet scripts]$ FNDCPASS apps/WELCOME 0 Y system/manager USER VISION WELCOME

Log filename : L390642.log
Report filename : O390642.out

 [oracle@sujeet scripts]$ FNDCPASS apps/WELCOME 0 Y system/manager USER operations WELCOME

Log filename : L390643.log
Report filename : O390643.out
[oracle@sujeet scripts]$ FNDCPASS apps/WELCOME 0 Y system/manager USER sysadmin WELCOME

Log filename : L390644.log
Report filename : O390644.out
To change all ORACLE schema passwords:-
 [oracle@sujeet ~]$ cd /oracle/PROD/apps/apps_st/appl/

[oracle@sujeet appl]$ . APPSPROD_sujeet.env

 [oracle@sujeet appl]$ FNDCPASS apps/apps 0 Y system/manager ALLORACLE sujeet

Log filename : L390638.log
 Report filename : O390638.out
To change an Oracle Applications schema password (other than APPS/APPLSYS):-
[oracle@sujeet scripts]$ FNDCPASS apps/WELCOME 0 Y system/manager ORACLE GL GL1

Log filename : L390641.log
Report filename : O390641.out

FRM-92101:There was a failure in the Forms Server during startup"

R12: "FRM-92101:There was a failure in the Forms Server during start up" Error When Attempting to Launch Forms [ID 454427.1]



                   

Solution:-

In several customer instances, $ORACLE_HOME/lib/ldflags was a symbolic link that pointed to a location that did not exist.  This was resolved by performing the following UNIX commands to point the $ORACLE_HOME/lib/ldflags to the $ORACLE_HOME/lib/ldflags :
$ cd $ORACLE_HOME/lib (DB_tier)
$ rm ldflags
$ ln -s $ORACLE_HOME/lib/ldflags ldflags

Then,  stop the web tier services (adopmnctl.sh stop) and relink the forms executable(s):


$ cd $ORACLE_HOME/forms/lib/(Appl_tier)
$ make -f ins_forms.mk install

Start  the web tier services (adopmnctl.sh start)....

Error resolve...........
                                     

compile invalid objects or Apps Schema-(Oracle ebsR12)


You can compile invalid objects (or Apps Schema) using the following methods:

I. Using Database Tier
-Login as database tier user
11i

* Set environment variable (under $ORACLE_HOME/[SID]_[Hostname].env)
* cd $ORACLE_HOME/rdbms/admin
* sqlplus /nolog
* SQL>conn /as sysdba
* SQL> @utlrp.sql

Release 12

* Set environment variable (under $INSTALL_DIR/db/tech_st/RDMBS_Home/[SID]_[Hostname].env)
* cd $ORACLE_HOME/rdbms/admin
* sqlplus /nolog
* SQL>conn /as sysdba
* SQL> @utlrp.sql

II. Using application tier (adadmin)
-Login as application tier user
11i

* Set environment variable from $APPL_TOP/APPSORA.env)
* adadmin
* option 3 compile/reload Applications Database Entities menu
* option 1 Compile Apps Schema

III. From SQL plus, this is individual objects only
-Figure out invalid Object in the database using

* SQL> select object_name, owner, object_type from all_objects where status ='INVALID';
* SQL> alter [object] [object_name] compile;

IV. ADCOMPSC.pls

The order in which to compile Invalid Objects in schemas is SYS, SYSTEM, APPS and then all others. APPS_DDL and APPS_ARRAY_DDL should exist in all schema's.
In case of an ORA-1555 error while running adcompsc.pls, restart the script.

The script can be run as followed :

cd $AD_TOP/sql
sqlplus @adcompsc.pls SCHEMA_NAME SCHEMA_PASSWORD %

SQL> @adcompsc.pls apps apps %

After the script completes, check for invalid objects again. If the number has decreased, but invalid objects still exist, run adcompsc.pls again.
Keep running adcompsc.pls until number of invalid objects stops decreasing.

If there are any objects still left INVALID, verify them by using the script 'aderrchk.sql' to record the remaining INVALID objects.
'Aderrchk.sql' uses the same syntax as 'adcompsc.pls'. This script is also supplied with the Applications.
Send the aderrchk.sql to a file using the spool command in sqlplus.

e.g. sqlplus apps/password @aderrchk.sql SCHEMA_NAME SCHEMA_PASSWORD %
For objects which will not compile, try the following :

select text from user_source
where name = 'OBJECTNAME'
and text like '%Header%';
This script will provide the script that creates the packages/recreates the packages.

SQL>@packageheader
SQL>@packagebody

If recreating the package does not make the package valid, analyze the user_errors table to determine the cause of the invalid package :

select text from user_errors
where name = '< PACKAGENAME >'
Related Posts by Categories

Inactive session

How to Kill INACTIVE SESSIONS in R12

 Step-1.Connect to SQL:-
Base_dir>Oracle
database>VIS
 
 
[oracle@dev1211]$cd /oracle/VIS/apps/apps_st/appl
[oracle@dev1211 appl]$ . APPSVIS_dev1211.env 
[oracle@dev1211 appl]$ sqlplus
 
SQL*Plus: Release 10.1.0.5.0 - Production on Wed Apr 4 05:21:44 2012
 
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
 
Enter user-name: apps
Enter password: apps
 
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 
SQL>
 
Step-2.Make script to session kill:- 
 
SQL>spool on
SQL> spool /home/oracle/session.sql
SQL>select 'alter system kill session '''||sid||','||serial#||''' immediate;' from v$session where status='INACTIVE';
SQL>spool off
SQL> @/home/oracle/session.sql
 
 
SQL>select 'alter system kill session '''||sid||','||serial#||''' immediate;' from v$session where status='INACTIVE';
  
 
SQL> select 'alter system kill session '||''''||sid||','||serial#||''' 
immediate;',(sysdate-logon_time)/5 from V$session;

Unexpected Signal : 11 occurred at PC=0xB7D3B7CE Function=(null)



Unexpected Signal : 11 occurred at PC=0xB7D3B7CE Function=(null)
Library=/tmp/OraInstall2012-05-28_02-37-07PM/jre/1.4.2/lib/i386/client/libjvm.so

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.

#. install 10g database open first window next after get this error:-

Solution:-

Edit both file:-Oratab and OraInst.loc...

[root@gayatri1 oracle]# vi /etc/oratab
[root@gayatri1 oracle]# vi /etc/oraInst.loc

APP-WSH-231210:An Unexpected Error Occured for Line 388354.


 APP-WSH-231210:An Unexpected Error Occured for Line 388354.
The Error is:ORA-04062 :Signature of package "APP.WSH_DELIVERY_DETAILS_INV"
has been changed..

  Solution:-

  [oracle@APPSR12]$ cd
/oracle/VIS/apps/apps_st/appl/wsh/12.0.0/patch/115/sql

[oracle@APPSR12 sql]$ cp WSHDDICB.pls  /home/oracle/Desktop/

[oracle@APPSR12 sql]$ cp WSHDDICS.pls  /home/oracle/Desktop/

 [oracle@APPSR12 sql]$ rm WSHDDICB.pls

[oracle@APPSR12 sql]$ rm WSHDDICS.pls

generate form through ADADMIN..
STEP:-2 run adadmin

[oracle@APPSR12 scripts]$ adadmin
Is this the correct APPL_TOP [Yes] ?
Filename [adadmin.log] :sonu.log
Do you wish to activate this feature [No] ?
Please enter the batchsize [1000] :
Is this the correct database [Yes] ?
Enter the password for your 'SYSTEM' ORACLE schema: manager
Enter the ORACLE password of Application Object Library [APPS] :  apps


Saving product information.

AD code level : [B.3]

            AD Administration Main Menu
   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration



Enter your choice [6] : 1

         Generate Applications Files
   ----------------------------------------

   1.    Generate message files

   2.    Generate form files

   3.    Generate report files

   4.    Generate product JAR files

   5.    Return to Main Menu





Enter your choice [5] : 2


AD utilities can support a maximum of 999 workers. Your
current database configuration supports a maximum of 84 workers.
Oracle recommends that you use between 4 and 8 workers.


Enter the number of workers [4] :

Your current character set is "AL32UTF8".

Do you want to generate Oracle Forms objects
using this character set [Yes] ?


Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ?

Do you want to regenerate Oracle Forms menu files [Yes] ?
Do you want to regenerate Oracle Forms executable files [Yes] ?

Enter list of products ('all' for all products) [all] : inv

 Generate specific forms objects for each selected product [No] ?


The current set of installed languages is: US

Please select languages for generating Oracle Forms files.
You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] :


Review the messages above, then press [Return] to continue.
Resolved  error >>>>>>>>

FRM-40735:CLOSE_WINDOW trigger raised unhandled exception ORA-06508.

 ERROR>ORA-01403:no data found
FRM-40735:CLOSE_WINDOW trigger raised unhandled exception ORA-06508.


 Navigation:-
Customer support,vision operations>Service Requests>Create Service Requests>open new form>>
enter data>save>error data not found>and form not close...



Solution:-

RUN ADADMIN:-

Compile APPS schema:-

Generate form files:-

1.run adadmin:-steps

[oracle@APPSR12 scripts]$ adadmin
Is this the correct APPL_TOP [Yes] ?
Filename [adadmin.log] : 
Do you wish to activate this feature [No] ?
Please enter the batchsize [1000] :
Is this the correct database [Yes] ?
Enter the password for your 'SYSTEM' ORACLE schema: manager
Enter the ORACLE password of Application Object Library [APPS] :  

 Saving product information.

AD code level : [B.3]

            AD Administration Main Menu
   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration

 Enter your choice [6] : 3 <Enter>

 1.    Compile APPS schema:-

Enter your choice [3] : 1 <Enter>

Review the messages above, then press [Return] to continue.<Enter>
 
AD code level : [B.3]

            AD Administration Main Menu
   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration



 Enter your choice [6] : 1

         Generate Applications Files
   ----------------------------------------

   1.    Generate message files

   2.    Generate form files

   3.    Generate report files

   4.    Generate product JAR files

   5.    Return to Main Menu

 Enter your choice [5] : 2

 AD utilities can support a maximum of 999 workers. Your
current database configuration supports a maximum of 84 workers.
Oracle recommends that you use between 4 and 8 workers.
 Enter the number of workers [4] :
 Your current character set is "AL32UTF8".
 Do you want to generate Oracle Forms objects
using this character set [Yes] ?
  Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ?
 Do you want to regenerate Oracle Forms menu files [Yes] ?
Do you want to regenerate Oracle Forms executable files [Yes] ?
 Enter list of products ('all' for all products) [all] :
  Generate specific forms objects for each selected product [No] ?
 The current set of installed languages is: US
 Please select languages for generating Oracle Forms files.
You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] :


Review the messages above, then press [Return] to continue.

Error resolve.............

Oracle SES install on Linux OS...



                                                                                         

Oracle R12.1.1 Create Secure Enterprise Search (SES)



INSTALL_SES_ON_LINUX_S.4....
Installing Oracle E-Business Suite Secure Enterprise Search, Release 12 [ID 462377.1]
·      Oracle Secure Enterprise Search Release 11g (11.1.2 and 11.1.2.2)

Step:-1
[root@sujeet ~]# cat /proc/version

Linux version 2.6.18-164.el5 (mockbuild@x86-002.build.bos.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Aug 18 15:51:54 EDT 2009

Step:-2
Memory Requirements The memory requirements are determined by the physical
memory consumed by the database and by services such as the WebLogic server. The
memory requirements for installing Oracle SES 11g Release 1 (11.1.2.2) are as follows:
? At least 2 GB of physical RAM. To determine the physical RAM size, enter the
following command:

[root@sujeet ~]# grep MemTotal /proc/meminfo

MemTotal:      2036792 kB


If the size of the physical RAM is less than the required size, then you must install
more memory before continuing.

Step:-3
Available RAM Swap Space Required
Between 2 GB and 8 GB   >>>Equal to the size of RAM
Between 8 GB and 14 GB >>>0.75 times the size of RAM
More than 14 GB              >>>10 GB

Step:-4
To determine whether the system architecture can run the software, enter the
following command:


[root@sujeet ~]# grep "model name" /proc/cpuinfo

model name      : Pentium(R) Dual-Core  CPU      E5300  @ 2.60GHz

model name      : Pentium(R) Dual-Core  CPU      E5300  @ 2.60GHz


Step:-5

To determine the size of the configured swap space, enter the following command:

[root@sujeet ~]# grep SwapTotal /proc/meminfo

SwapTotal:     4192956 kB

Step:-6
 [root@sujeet ~]# free


                    total       used             free     shared    buffers     cached

Mem:        2036792    1970536      66256          0      19344    1687636


-/+ buffers/cache:     263556       1773236


Swap:      4192956        112         4192844


Step:-7
Hardware Requirements The system must meet the following minimum hardware
requirements:
On Linux x86:
Oracle SES requires a minimum of 6.6 GB of disk space to install. This includes 4.9 GB
for the software and approximately 1.7 GB for the initial Oracle SES index. Additional
Oracle SES requirements are based on the amount of data that you need to search.
For example, to index 100,000 documents:
? 4 GB disk space
? 2 GB RAM
To index 1,000,000 documents:
? 20 GB disk space
 6 GB RAM
On Linux x86-64:
 Oracle SES requires a minimum of 7.6 GB of disk space to install. This includes 6.0 GB
for the software and approximately 1.6 GB to create the initial Oracle SES index.
Additional Oracle SES requirements are based on the amount of data that you need to
search.
For example, to index 100,000 documents:
?  4 GB disk space
?  2 GB RAM
To index 1,000,000 documents:
?  20 GB disk space
?  6 GB RAM


Step:-8
 It shows a kernel version and errata level on the system:-

[root@sujeet ~]# uname -r

2.6.18-164.el5



Step:-9

 Create user,Group and assign group
[root@sujeet ~]# /usr/sbin/useradd -g dba oracle

 This command creates the oracle  user and specifies oinstall  as the
primary group. You can also include the -G  option to specify secondary
groups as follows:

[root@sujeet ~]#  more /etc/oraInst.loc

inventory_loc=/10g/app/oracle/oraInventory

inst_group=dba

[root@sujeet ~]# id -a oracle

uid=500(oracle) gid=501(dba) groups=501(dba)


[root@sujeet ~]# /usr/sbin/groupadd oinstall

 If the oracle  user exists, but its primary group is not oinstall , then enter
the following command:-

[root@sujeet ~]# /usr/sbin/usermod -g oinstall oracle

If you wish, you can include the -G  option to specify secondary groups:

[root@sujeet ~]# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle



[root@sujeet ~]# /usr/sbin/useradd -g oinstall -G dba[,oper] oracle

Configure the password of the oracle  user as follows:

[root@sujeet ~]#  passwd oracle

Step:-10

The following or later version of packages for Oracle Enterprise Linux 5.0 and Red
Hat Enterprise Linux 5.0 should be installed:
binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32 bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12
glibc-2.5-12 (32 bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5-12 (32 bit)
libaio-0.3.106
libaio-0.3.106 (32 bit)
libaio-devel-0.3.106
libgcc-4.1.1
libgcc-4.1.1 (32 bit)
libstdc++-4.1.1
libstdc++-4.1.1 (32 bit)
libstdc++-devel 4.1.1
make-3.81
numactl-devel-0.9.8.x86_64
sysstat-7.0.0


[root@sujeet ~]#  rpm -q package_name

Step:-11
[root@sujeet ~]# vi /etc/sysctl.conf


fs.aio-max-nr = 1048576
fs.file-max = 65536
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576

[root@sujeet ~]# /sbin/sysctl -p
  

***************************************************

[root@sujeet ~]# vi /proc/sys/kernel/sem

semmsl >250
semmns >32000
semopm >100
semmni >128

[root@sujeet ~]# vi /proc/sys/kernel/shmall

shmall 2097152
[root@sujeet ~]# vi /proc/sys/kernel/shmmni
4096
[root@sujeet ~]# vi /proc/sys/fs/file-max
131072
[root@sujeet ~]# vi /proc/sys/net/ipv4/ip_local_port_range
1024    65000
[root@sujeet ~]# vi /proc/sys/net/core/rmem_default
262144
[root@sujeet ~]# /proc/sys/net/core/rmem_max
4194304
Parameter Command
semmsl, semmns,
semopm, and semmni              /sbin/sysctl -a | grep sem

This command displays the value of the semaphore parameters in
the order listed.
shmall, shmmax, and
shmmni                         /sbin/sysctl -a | grep shm
file-max                       /sbin/sysctl -a | grep file-max
ip_local_port_range     /sbin/sysctl -a | grep ip_local_port_range
rmem_default             /sbin/sysctl -a | grep rmem_default
rmem_max                  /sbin/sysctl -a | grep rmem_max
wmem_default            /sbin/sysctl -a | grep wmem_default
wmem_max             /sbin/sysctl -a | grep wmem_max
aio-max-nr                 /sbin/sysctl -a | grep aio-max-nr


Step:-12
Setting Shell Limits for the oracle User:-

 To increase the shell limits:-
1.Add the following lines in the /etc/security/limits.conf file:
2. 

[root@sujeet ~]# vi /etc/security/limits.conf

oracle     soft      nproc       2047
oracle     hard     nproc      16384
oracle     soft        nofile      1024
oracle     hard      nofile        65536

Step:-13
2. Add the following line to the /etc/pam.d/login file, if it does not already exist:
[root@sujeet ~]# vi /etc/pam.d/login

session     required     pam_limits.so

Step:-14
Depending on the oracle  user's default shell, make the following changes to the
default shell startup file:
For the Bourne, Bash, or Korn shell, add the following lines in the
/etc/profile  file (or the /etc/profile.local  file on SUSE systems):
[root@sujeet ~]# vi /etc/profile

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi


For the C shell, add the following lines in the /etc/csh.login  file (or the
/etc/csh.login.local  file on SUSE systems):

Step:-15
[root@sujeet ~]# vi /etc/csh.login


if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif



Step:-16   Create dir:-

[root@sujeet ~]# mkdir ses

Step:-17 Assign user and permission:-

[root@sujeet ~]# chown -R oracle:dba ses
[root@sujeet ~]# chmod -R 777 ses

Step:-18

[root@sujeet ~]# init 6

Step:-19    Go to SES_setup_location:-

[oracle@sujeet setup]$ cd SES/

[oracle@sujeet SES]$ ll

-rwxrwxrwx 1 oracle dba 1472974438 Feb  1 18:01 ses_11_1_2_2_0_linux32_1of2.zip

-rwxrwxrwx 1 oracle dba  820405088 Feb  1 16:54 ses_11_1_2_2_0_linux32_2of2.zip

Step:-20 Unzip file

[oracle@sujeet SES]$ ses_11_1_2_2_0_linux32_1of2.zip
[oracle@sujeet SES]$ ses_11_1_2_2_0_linux32_2of2.zip

create a new dir. Same location (ses_11_1_2_2_0_linux32)

Step:-21
[oracle@sujeet SES]$ cd ses_11_1_2_2_0_linux32

[oracle@sujeet ses_11_1_2_2_0_linux32]$ pwd

/setup/SES/ses_11_1_2_2_0_linux32

[oracle@sujeet ses_11_1_2_2_0_linux32]$ ll
total 36
drwxrwxrwx  9 oracle dba 4096 Apr 20  2011 doc

drwxrwxrwx  5 oracle dba 4096 Apr 29  2011 install

drwxrwxrwx  2 oracle dba 4096 Apr 29  2011 Patches

drwxrwxrwx  2 oracle dba 4096 Apr 29  2011 response

-rwxrwxrwx  1 oracle dba 6091 Apr 29  2011 runInstaller

drwxrwxrwx 13 oracle dba 4096 Apr 29  2011 stage

-rwxrwxrwx  1 oracle dba 4534 Apr 19  2011 welcome.html


[oracle@sujeet ses_11_1_2_2_0_linux32]$ ./runInstaller

open window>>>>>>>>>



***********************END Install SES*************************************

Starting and Stopping Oracle Secure Enterprise Search
The command for starting and stopping the search engine in Oracle SES is
searchctl. The executable is located in the $ORACLE_HOME/bin directory:

$ORACLE_HOME/bin/searchctl
The command syntax is as follows:-
Command                           Description
searchctl start                       Start the Oracle SES middle tier

searchctl startall                   Start the Oracle SES middle tier and the database

searchctl stop                        Shut down the Oracle SES middle tier

searchctl stopall                     Shut down the Oracle SES middle tier and the database

searchctl restart                    Restart the Oracle SES middle tier

searchctl restartall                 Restart the Oracle SES middle tier and the database

On Linux and UNIX platforms, you must supply the Oracle SES administrative:-
password when running searchctl  commands. If you have shut down both the
database and the middle tier with the searchctl stopall  command, then to
successfully start them both, run searchctl startall . If the Middle Tier Port is
less than 1024, then the following commands must be run by the root user:

[oracle@sujeet bin]$ ./searchctl stop

Enter admin_passwd (administrative password):    
oracle123

[oracle@sujeet ]$ cd /ses/oracle/seshome/bin
[oracle@sujeet bin]$ ./searchctl startall
password :- oracle123
[oracle@sujeet bin]$ searchctl start/stop
[oracle@sujeet bin]$ searchctl startall
[oracle@sujeet bin]$ searchctl stopall
[oracle@sujeet bin]$ searchctl restartall

http://sujeet.oracle.com:7777/search/admin/

user:-eqsys
pass:-ses12oracle

http://sujeet.oracle.com:7777/search/query/


http://sujeet.oracle.com:7777/console/login/LoginForm.jsp

user:- weblogic
pass:-oracle123



Performing Setup Tasks:-

1.Create a Search Administrator.

2.Enabling Searches on Oracle E-Business Suite
#.Setting language preferences
#.Setting profile options
#.Assigning FND search Crawler responsibility to an FND user.
#.Performing personalization setup.

3.Performing Setup tasks for Oracle SES Integration.
#.Installing Oracle E-Business Suite Secure Enterprise Search.
#.Configuring search parameters for Oracle SES.
#.Performing setup tasks in Oracle SES.

*************************************
Step:-22
1.Create a Search Administrator:-
#.Creating a User (such as sesadmin/welcome).
         System Administrator>security:User>Define>open users fom..
 User name:-sesadmin
 password:-sesadmin

#.Assigning the following responsibilities to the user:-
a> Application search Administrator responsibility.(FND_SEARCH_ADMIN)
Application Search Administrator
Create responsibility:- System Administrator>security:Responsibility>Define
b> FND Search Crawler responsibility.(FND_SEARCH_CRAWLER)

Step:23
2.Enabling Searches on Oracle E-Business Suite
#.Setting language preferences:-
Home page>Preferences>Display preferences>American English..

Step:-24
#.Setting profile options:-
Profile option name                           default value  Set_value  

a> FND : Search Enabling Flag                       N          YES

b> FND : Search Engine URL                          N/A http://sujeet.oracle.com:7777/ http://<hostname>:<portnumber>

c> FND : Search Session Timeout Value for Quary     1200       1800

d> FND : Search Session Timeout value for Quary     1200       1800

e> FND : Search Crawl Batch Size                    1000       3000

Step:-25
Application Search Administrator > Configuration Tab:Query Proxy region>
user:-eqsys
pass:-oracle123
************************
User name:-SERVICE
password:-SERVICE
Time out:-1800
          Update

Step:-26
#.Performing personalization setup:-
Note:-Performing personalization setup to display the Enterprise Search region on top of the Oracle E-Business Suite Home Page.

a> login as sysadmin/sysadmin
b> Select the Functional Administrator responsibility from the Navigator menu.

c> Slect the personalization tab and the application Catalog subtab to open the Appliaction Catalog page.

d> In the search region enter>
   /oracle/apps/fnd/search/webuiin the document path field as the search criteria and Click GO.All document names that match the search criteria should be display in the search result table..

e> Click the personalize page icon for the /oracle/apps/fnd/search/webui/AppsSearchRG document name listed in the result table to open the choose Personalization Context page.

f> Enter 'Application Home Page' (OAHOMEPAGE) in the Set function field and click Apply
   to open the personalization Region page for your document.

g> In the personalization structure region,Select the personalization icon for the Row      Layout field to open the personalize Row layout Page.

h> Set the rendered property to 'true' at the 'function' Applications Home Page' level.

i> Navigate back to the Home Page after applying the personalization change.

j> Review if the Enterprise Search region is getting rendered on the Oracle E-Business Suite Home Page.

k> Perform a search by entering search criteria and click GO to verify if the search result is displayed in the search result page...

Step:-7
#.Configuring search Proxy parameters: Accessing Search Admin Page:-

a> login on to oracle E-Business Suit as search Administrator username
(such as sesadmin/sesadmin)

b> Select the Application Search Administrator responsibility > Application Search Administrator link from the navigator.

Schedules Tab:-use this tab to view crawling status and manage crawling schedules.

Configuration Tab:-Use this tab to configure search proxy parameters to enable the integration between Oracle EBS and SES.

note:-You can also access Oracle SES Administrative page directly through this tab.In the additional tasks section on the lower right corner of this tab.click the SES Admin login link to get to Oracle SES login page.

c> Searchable Objects:-Use this tab to deploy searchable objects from Oracle EBS to the SES instance that you defined in the SES End point URL field in the Configuration tab...

 step:-8
#.Performing setup tasks in Oracle SES:-
Accessing Oracle Secure Enterprise Search Administrative page:-
Use either of the following two ways to access Oracle SES administrative page:-
#. Log on to the Oracle SES administrative user interface through:-

  http://sujeet.oracle.com:7777/search/admin
u:-eqsys
p:-oracle123

#. Log on to the Oracle SES administrative page from the Oracle E-Business Suit Secure Enterprise Search Administrative page.
    Configuration tab > ses Admin login > get Oracle SES login page.

Step:-9
#.Configure the following Global setup task in Oracle SES:-
Identity Management Setup:-
Global Settings tab > identity management Setup link (click in this link)
And enter the following information to activate an available plug-in in order to enable secure search.

#.Select 'oracle.search.plugin.security.ebs.EBSidentityPluginMgr' from the available identity plug-in region and click ACTIVate.

#.In the activate identity plug-in page.enter the following parameter values to define the selected identity plug-in settings for all authentication and validation activities in ORACLE ses:
a> HTTP endpoint for authentication:Enter an end point URL for Oracle E-Businees Release 12 authentication,such as
   http://sujeet.oracle.com/7777/webservices/AppSearch/SecurityService.
b> User ID :- Enter the search administrator's user name that you created earlier.

c> Password : Enter the search Administrator's login password.
d> Click FInish to return to the Global Settings page.

step:-10
Federation trusted Entity Setup:-
    #.Global Settings tab >Federation trusted Entity link.(click on this link)
     Open >Federation trusted Entity page
    #.user name:-sesadmin/welcome
    #.Select the Use Entity plug-in for authentication check box to authentication through the active identity plug-in.
    #.Click ADD.

Step:-11
Quary Configuration Setup:-
     #.Global Settings tab >Quary Configuration link.
     In the query-time Uthorization configuration region,enetr the following parameter values to specify the query configuration for the query-time authorization engine: Time out threshold (milliseconds):500000

#.In the secure search Configuration region,enter the following information in the Security Filter Configuration section to specify security filetr related parameter values:
Authorization Timeout (milliseconds):200000
Authorization Timeout (milliseconds):500000

Step:-12
[oracle@sujeet config]$ cd  /ses/oracle/seshome/search/webapp/config
[oracle@sujeet config]$ vi search.properties
# configure time in milliseconds to wait for security filter refresh task to finish during query processing
sec_filter_refresh_wait_time=2000

Step:-13

Restart instance:-
A> Oracle SES
B> Oracle E-Business Suite instances.

 Accessing Oracle Search Modeler:-
The Search modeler login page should have followinh URL:-
http://sujeet.oracle.com:7777/modeler/faces/ModelerHome.jsp
Only user with'UMX|APPSEARCH_DEVELOPER' user role will have the search modeler login privilege.


Step:-14
Creating Searchable Objects:-


 Note: Make sure that the following configuration should also be performed in Oracle SES server:
1    Locate the search.properties file in $ORACLE_HOME/search/webapp/config directory.
2    Set the security filter refresh task wait time value: sec_filter_refresh_wait_time=20000.
3     This is the time in milliseconds to wait for security filter refresh task to finish during
4    query processing.
5    Use the following steps to set the parameters in Oracle SES to avoid issues related to security
6    plug-in timeout:
7    Logon to the Oracle SES administrative user interface using
8    http://sujeet.oracle.com:777/search/admin
9    Select the Global Settings tab from the Secure Enterprise Search page.
10Select the Query Configuration link from the Search section.
11In the Query-time Authorization Configuration region, enter the following parameter
12values to specify the query configuration for the query-time authorization engine:
·     Timeout Threshold (milliseconds): 500000
13 In the Secure Search Configuration region, enter the following information in the Security Filter
14 Configuration section to specify security filter related parameter values:
·      Authentication Timeout (milliseconds): 200000
15 Authorization Timeout (milliseconds): 500000 Create a search administrator with the following responsibilities:
·      Application Search Administrator responsibility (FND_SEARCH_ADMIN)
·      FND Search Crawler responsibility (FND_SEARCH_CRAWLER)
16Log on to Oracle E-Business Suite with the search administrator user name and password. sesadmin/sesadmin
17 Select the Application Search Administrator responsibility and choose Application Search Administration from the navigation menu.
18 In the Application Search Administrator page, select the Configuration tab.
19 Specify the following information in the SES End Point region:
·      SES End Point URL: Enter an URL address with the format, http://sujeet.oracle.com:777/ in this field. This value can be defined in the 'FND: Search Engine URL' profile option.
·      SES Version: Enter an appropriate Oracle SES version that your system will be integrated with. It should have minimum two characters, and the first two characters should be digits, such as 10.1.8.4, 11.1.2, or 11g. Values entered here will be stored in the 'FND: Search SES Version' profile option.
20 In the Admin Proxy region, enter the following fields:
·      User Name: eqsys /oracle123
·      Password: use the same password for eqsys username when you installed the SES
·      Time Out: 1200 secs
21 In the Query Proxy region, enter the following fields:
·      User Name: an application username with the FND Search Crawler responsibility
·      Password: use the password for the above username
·      Time Out: 1200 secs
22 Once you change the information in the Query Proxy region, the Oracle SES instance needs to be restarted.
23 Set the FND: Search Enabling Flag (FND_SEARCH_ENABLED) profile option to "Y" at the site level.
24 Logon to the Oracle SES administrative user interface using>>sesadmin/ses12oracle http://sujeet.oracle.com:7777/search/admin/
25 Select the Global Settings tab from the Secure Enterprise Search page to configure the following settings.
·      Select the 'Identity Management Setup' link from the System section to set up connections between Oracle SES and an identity management system to validate and authenticate users for secured searches.
·      Select oracle.search.plugin.security.identity.ebs.EBSIdentityPluginMgr from the Available Identity Plug-in region and click Activate.
·      In the Activate Identity Plug-in page, enter the following parameter values to define the selected Identity Plug-in settings for all authentication and validation activity in Oracle SES:
·      HTTP endpoint for authentication: Enter an end point URL for Oracle E-Business Release 12 authentication, such as http://dev1211.iwarelogic.com:8020/webservices/AppSearch/SecurityService
·      User ID: Enter the search administrator's user name that you created earlier in Step 1. sesadmin
·      Password: Enter the search administrator's login password.
·      ses12oracle
·      Click Finish to return to the Global Settings page.
·      Select the 'Federation Trusted Entities' link from the Search section to add federation entities.
·      In the Federation Trusted Entities page, enter the following information:
·      Entity Name: Enter the search administrator's user name that you created earlier in Step 1. sesadmin
·      Entity Password: Enter the search administrator's login password. ses12oracle
·      Select the Use Identity Plug-in for authentication check box to authenticate through the active identity plug-in.
·      Click Add to return to the Global Settings page.
·      Select the 'Crawler Configuration' link from the Sources section to ensure the crawler logging setting is appropriate.
·      In the Crawler Logging region, ensure the crawler log file directory path including log file name defined in the Crawler Log File Directory field is less than the supported length of 100 characters for Oracle SES 11.1.2 or SES 11.1.2.2 integration.
·      Click Apply.
26 
27Restart both Oracle SES and Oracle E-Business Suite instances.
To ensure that the Enterprise Search region appears on top of the Oracle E-Business Suite Home page, perform the following personalization steps:
1     Log in to Oracle E-Business Suite with the system administrator's user name and password. (sysadmin/sysadmin)
2     Select the Functional Administrator responsibility from the Navigator menu.
3     Select the Personalization tab and the Application Catalog subtab to open the Application Catalog page.
4     In the Search region, enter '/oracle/apps/fnd/search/webui' in the Document Path field as the search criteria and click Go. All document names that match the search criteria should be displayed in the search result table.
5     Click the Personalize Page icon for the '/oracle/apps/fnd/search/webui/AppsSearchRG' document name listed in the result table to open the Choose Personalization Context page.
[oracle@dev1211 12.0.0]$ pwd

/data/R12/oracle/VIS/apps/apps_st/appl/fnd/12.0.0/

1     Enter 'Applications Home Page' (OAHOMEPAGE) in the Set Function field and click Apply to open the Personalization Region page for your document.
2     In the Personalization Structure region, select the Personalize icon for the Row Layout field to open the Personalize Row Layout page.
3     Set the rendered property to 'true' at the 'Function: Applications Home Page' level.
4     Navigate back to the Home page after applying the personalization change.
5     Review if the Enterprise Search region is getting rendered on the Oracle E-Business Suite Home page.
6     Perform a search by entering search criteria and click Go to verify if the search result is displayed in the search result page.

Oracle Secure Enterprise Search with Oracle E-Business Suite 11i & R12 releases

What are we announcing?

We are pleased to announce the availability of Oracle E-Business Suite Secure Enterprise Search Solutions for Oracle E-Business Suite R11.5.10 customers. Following products are now available for customers to download via My Oracle Support (formerly known as OracleMetaLink).
Oracle Secure Enterprise Search (SES) is integrated with Oracle E-Business Suite applications Releases R11.5.10, R12.0.4 onwards and R12.1.1. Please see the following matrix for patch numbers.
E-Business Suite ReleasePatch number11.5.10.CU2822563112.0.4738964312.1.18441410
 Abstract APPSEARCH CUMMULATIVE
PATCH   Update 8441410 Product Application Object Library
Release R12 Platform Generic Platform Built
Instructions
 Instructions For Applying This Patch Preparation Tasks
The tasks in this section can be completed without taking any Applications services or users offline.There are no tasks to be performed in this section.Pre-install Tasks
You must shut down all Application tier services before performing the tasks in this section.There are no tasks to be performed in this section.Apply The PatchApply patch
This patch contains the following unified driver file to be applied with
AutoPatch:
    u8441410.drv (This is the unified driver)Post-install Tasks
You must complete the tasks in this section before starting up Application tier services.There are no tasks to be performed in this section.Finishing Tasks
You may complete the tasks in this section at any time after the update, without taking any services or users offline.There are no tasks to be performed in this section.Additional InformationThere are no tasks to be performed in this section.  Description
This patch provides E-Business Suite Release 12.1.1 (onwards) interoperability
with Oracle Secure Enterprise Search minimum version of 10.1.8.4 and Search
Modeler minimum version of 1.2.

After applying this patch, E-Business Suite customers will be able to
integrate with Oracle Secure Enterprise Search and Oracle Search Modeler.


Available Documentation
http://blogs.oracle.com/stevenChan/entry/secure_enterprise_search_11_1

Installing Oracle E-Business Suite Secure Enterprise Search, Release 12 [ID 462377.1]
Oracle E-Business Suite Secure Enterprise Search documentation is available as part of the Online Documentation Library on the Oracle Technology Network:
·      Oracle E-Business Suite User's Guide
·      Oracle E-Business Suite System Administrator's Guide - Maintenance (or Oracle Applications System Administrator's Guide - Maintenance depending on your Oracle E-Business Suite release)
For more information on setup steps and administrative tasks, see Administering Oracle E-Business Suite Secure Enterprise Search, Oracle E-Business Suite System Administrator's Guide - Maintenance.
Additionally, see the following Knowledge Documents on My Oracle Support (formerly OracleMetaLink) about Oracle E-Business Suite Secure Enterprise Search:
·      726239.1: Oracle E-Business Suite Secure Enterprise Search Troubleshooting Guidelines, Release 12
·      744820.1: Oracle E-Business Suite Secure Enterprise Search Best Practices, Release 12
·      781366.1: Search Modeler 1.1 for Oracle E-Business Suite Readme
·      1077540.1: Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.1.3
·      953483.1: Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.1.2
·      566097.1: Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.1.1
·      740499.1: Oracle E-Business Suite Secure Enterprise Search, Release Notes for Release 12.0.6 



ORA-08004: sequence IEX_DEL_BUFFERS_S.NEXTVAL exceeds MAXVALUE

 Error:- IEX: Scoring Engine Harness Error - ORA-08004: sequence IEX_DEL_BUFFERS_S.NEXTVAL exceeds MAXVALUE (Doc ID 2056754.1) SYMPTOMS:- Yo...