How to find a responsibility that can run a particular Conurrent Program

If you would like to know the responsibility that can submit a particular concurrent then use the query mentioned below . It's working for 90% of programs and I'm working on the same to make it 100 % effective ( will update the same when succeed )


Step 1 :

select user_concurrent_program_name from fnd_concurrent_programs_vl where user_concurrent_program_name like '%DIRECT BILLING%'

DIRECT BILLING BO REPORT


Now user the query to find the required responsibilities ...

Query :

select responsibility_name , responsibility_key ,request_group_id , application_id from fnd_responsibility_vl
where request_group_id in (
select request_group_id from FND_REQUEST_GROUP_UNITS where request_unit_id in
( select concurrent_program_id from fnd_concurrent_programs_vl where
user_concurrent_program_name='DIRECT BILLING BO REPORT'))

How to create a database with minimum configuration and parameters

Step 1 : Export the required PATH

export ORACLE_SID=TEST5
export ORACLE_HOME=/u11m/app/ilproddb/9.2.0/
export PATH=$PATH:$ORACLE_HOME/lib:$ORACLE_HOME/bin

Step 2 : Create pfile with the minimum configuration

[ilerpap03:ilmis] /u11m/app/ilproddb/9.2.0/dbs> vi initTEST5.ora
"initTEST5.ora" [New file]
instance_name=TEST5
db_name=TEST5



Step 3 : Now , create the database

[ilerpap03:ilmis] /u11m/app/ilproddb/9.2.0/dbs> sysdba

SQL*Plus: Release 9.2.0.5.0 - Production on Mon Nov 9 12:26:31 2009

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to an idle instance.

12:26:38 TEST5 > startup nomount
ORACLE instance started.

Total System Global Area 178227232 bytes
Fixed Size 743456 bytes
Variable Size 121634816 bytes
Database Buffers 50331648 bytes
Redo Buffers 5517312 bytes
12:26:46 TEST5 > create database ;

Database created

12:30:46 TEST5 >


That's it . Database is created now .

Error :

Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Fri Nov 6 08:45:53 2009
Error 1031 received logging on to the standby
Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Fri Nov 6 08:50:53 2009
Error 1031 received logging on to the standby
Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Fri Nov 6 08:55:53 2009
Error 1031 received logging on to the standby
Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Fri Nov 6 09:00:04 2009
Thread 1 advanced to log sequence 15599
Current log# 1 seq# 15599 mem# 0: /DDMESP_home2/oradata/ORAPMES/redo1a.log
Current log# 1 seq# 15599 mem# 1: /DDMESP_home4/oradata/ORAPMES/redo1b.log
Fri Nov 6 09:00:53 2009
Error 1031 received logging on to the standby
Suppressing further error logging of LOG_ARCHIVE_DEST_2.
Fri Nov 6 09:01:24 2009
WARNING: inbound connection timed out (ORA-3136)
Fri Nov 6 09:01:32 2009
WARNING: inbound connection timed out (ORA-3136)

OR


Errors in file c:\oracle\product\10.2.0\admin\lims\bdump\lims_arc1_2756.trc:
ORA-01017: invalid username/password; logon denied

Sun Jul 20 05:08:19 2008
Error 1017 received logging on to the standby

Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191


OR

*** 2008-07-20 21:47:24.812
*** SERVICE NAME:() 2008-07-20 21:47:24.781
*** SESSION ID:(156.1) 2008-07-20 21:47:24.781
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
'
*** 2008-07-20 21:47:25.046 62692 kcrr.c
Error 1031 received logging on to the standby
Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'to_prod'
Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'to_prod'
ORA-01031: insufficient privileges
*** 2008-07-20 21:47:25.062 62692 kcrr.c
PINGARC1: Heartbeat failed to connect to standby 'to_prod'. Error is 1031.
*** 2008-07-20 21:47:25.062 60970 kcrr.c
kcrrfail: dest:2 err:1031 force:0 blast:1



Solution :

1. REMOTE_LOGIN_PASSWORDFILE configured to SHARED or EXCLUSIVE
2. Recreate the password file on the standby database to have the same sys password as the primary database.
OR
Copy the password from Primary server to the stnadby server