Showing results for 
Search instead for 
Did you mean: 

JDBC connection

0 Kudos

Hi there,

we refreshed the quality system and DB that using as source system to XI after that i checked the DB connection and login and pwds used in CC and reset everything but cc giving following error

SQLException: ORA-01017: invalid username/password; logon denied

i thoughof pwd is incorrect and i changhed again and reset everything in CC..but that error is still there..

the connection between the DB and XI is ok ..

could anyone give me possible cause for this..

thanks in advance.



Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Check if your user in not locked.

Former Member
0 Kudos

seems like ur user id is blocked.

check with ur basis team.



0 Kudos

same user id is used for the another interface and that interfaces is working fine..

Edited by: PT Rao on Jan 7, 2008 12:39 PM

Former Member
0 Kudos

Hi Rao,

The exception: java.sql.SQLException: ORA-01017: invalid username/password;

logon denied

Indication that the database user connection information has

changed. Please use the configtool to check if the database connection

is working. The configtool can be used to change the database user

logon info if necessary.

To launch the configtool, please run the configtool.bat from the

following path:


When prompted with 'Do you want to use the default DB settings?' select

'yes'. If an error message is returned, this means that either the

database is not running, or the stored logon information is no longer

valid (someone changed the DB logon info). In this case verify that

the database is up. Next, if the configtool is still unable to connect

to the DB, then select the 'ok' option which will take you to the

'secure store' link. Select 'secure store' to display the stored logon

data. Select the 'jdbc/pool/<sid>/Password' entry. At the bottom

you'll see the parameter where you can update the password. Please set

the correct DB password for the SAP<sid>DB user. Click 'Add' and then

the SAVE icon in the menu bar of the configtool.

The bootstrap process uses this DB logon info to synchronize the

filesystem with the parameters stored in the DB. In your system this

process fails which causes the J2EE startup to fail.

I hope this will resolve the problem.



0 Kudos

Thanks Sarvesh..i will check everything and give you the outcome..