-
1. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 20, 2013 12:31 PM (in response to Azadare M)1 person found this helpfulHi,
In runtime connection setting, you need to enter application user name and password along with his valid responsibility key and responsibility application.
Regards,
Sandeep M.
-
2. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 20, 2013 2:12 PM (in response to Sandeep M.)1 person found this helpfulHi..Thanks Sandeep...
which application user name and password?
and which responsibility key and name resp..
-
3. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 21, 2013 6:22 AM (in response to Azadare M)Hi Abbas,
You need to provide oracle application user name and password and any responsibility which is assigned to this user.
Whenever we login to oracle application we provide user name and password and then we see the responsibility list and then once you select any responsibility then list of functions.
To run your page with same functional security JDeveloper needs user name and password with his valid responsibility key and responsibility application short name.
Hope it is clear now.
Regards,
Sandeep M.
-
4. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 21, 2013 6:45 AM (in response to Sandeep M.)Thanks a lot Sandeep...Its very help full to me..
Now I got this time.
I have user name , password , responsibility key bur how can I get short name of that particular responsibility
Thanks...
-
5. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 21, 2013 6:52 AM (in response to Azadare M)you can get responsibility_key and application_short_name for a responsibility using fnd_responsibility_vl and fnd_application views.
-
6. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 21, 2013 6:53 AM (in response to Sandeep M.)Thanks...I got it....
Thanks a lot Sandeep......
-
7. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 21, 2013 7:24 AM (in response to Azadare M)Hi Sandeep...
I am still getting same error while I run the HelloWorldPG.xml even I have given valid user name,password, respnsibility key and application short name...
I ran following query to get respnsibility key and application short name....
SELECT r.responsibility_key,fa.APPLICATION_SHORT_NAME FROM fnd_user u,
fnd_user_resp_groups ur,fnd_responsibility r,fnd_application_tl a,fnd_application fa WHERE r.version = 'W'
AND ur.responsibility_id = r.responsibility_id AND u.user_id = ur.user_id AND
fa.APPLICATION_ID = a.APPLICATION_ID AND r.application_id = a.application_id AND u.user_name = upper(:user_name) ORDER by 1
-
8. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 21, 2013 8:20 AM (in response to Azadare M)Hi Abbas,
Try one by one below solutions:
1. Make sure you are using correct version of Jdeveloper patch, you can find many threads in this forum that help you to find that.
OR
2. "Go to Jdeveloper Menu Tools | Preferences | Embedded OC4J Server Preferences | Under Global | Startup: choose 'Default Local IP Address'".
OR
3. Make sure DBC file is placed in correct directory and in project properties same has been selected.
OR
4. Check the DB connection again and test it.
Regards,
Sandeep M.
-
9. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 21, 2013 8:45 AM (in response to Sandeep M.)HI Sandeep...Thanks for reply
I am using oracle 9i JDeveloper.
I have choose 'Default Local IP Address'".
I put .dbc file in to "C:\setups\JDeveloper\jdevhome\jdev\dbc_files\secure" path
And checked DB connection and tested again but still giving same error....
-
10. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 21, 2013 9:10 AM (in response to Azadare M)Hi Abbas,
I am sure the problem is with DBC file only, can you ask DBA to again provide the same from instance.
OR
if you have other teammate working on same instance you can take it from them.
Please ensure you are using correct JDev version using metalink.
Regards,
Sandeep M.
-
11. Re: java.sql.SQLException: No suitable driver;
Azadare M Jun 21, 2013 9:49 AM (in response to Sandeep M.)Hi Sandeep..
I have searched in Metalink and i checked for version but I havent got suitable answer..But I read one paragraph here that..
"
- Make sure it is middle tier dbc file not database tier, the file is under $FND_TOP/secure
- Turn AUTHENTICATION to OFF using following command:
%<mount point>/util/java/1.4/j2sdk1.4.2_04/jre/bin/java \
> oracle.apps.fnd.security.AdminAppServer apps/apps AUTHENTICATION OFF \
> DBC=$FND_TOP/secure/<dbc file> - Comment out entry APPS_JDBC_URL from dbc file under JDeveloper directory.
"
I am sharing my .dbc file kindly check it out...
#DB Settings
#Wed Jun 05 00:11:02 PDT 2013
GUEST_USER_PWD=GUEST/WELCOME
APPL_SERVER_ID=DE60F44655CF0014E0439DEA3084001438881921312575574384100395557631
FND_JDBC_BUFFER_DECAY_INTERVAL=300
APPS_JDBC_DRIVER_TYPE=THIN
FND_JDBC_BUFFER_MIN=1
GWYUID=APPLSYSPUB/PUB
FND_JDBC_BUFFER_MAX=5
APPS_JDBC_URL=jdbc\:oracle\:thin\:@(DESCRIPTION\=(LOAD_BALANCE\=YES)(FAILOVER\=YES)(ADDRESS_LIST\=(ADDRESS\=(PROTOCOL\=tcp)(HOST\=dendbebsdev01.ds.vyom.net)(PORT\=7112)))(CONNECT_DATA\=(SID\=EBSD)))
FND_JDBC_STMT_CACHE_FREE_MEM=TRUE
FND_JDBC_STMT_CACHE_SIZE=200
TWO_TASK=EBSD
FND_MAX_JDBC_CONNECTIONS=500
FND_JDBC_USABLE_CHECK=false
FNDNAM=apps
FND_JDBC_PLSQL_RESET=false
DB_PORT=7112
FND_JDBC_CONTEXT_CHECK=true
FND_JDBC_BUFFER_DECAY_SIZE=5
DB_HOST=dendbebsdev01.ds.vyom.net
At the 3rd line of dbc file I even tried with changing of GUEST to my oracle EBS login USER name welcome to password...but still not working....
Thanks
-
12. Re: java.sql.SQLException: No suitable driver;
Sandeep M. Jun 21, 2013 10:06 AM (in response to Azadare M)Hi Abbas,
You need not to change DBC file.
Refer metalink Note 416708.1 for JDeveloper version for your application version.
Also ask your DBA to get the DBC file from correct location on middle tier (it varies in 11i and r12).
Regards,
Sandeep M.