Logging into Shark using Oracle DB- solution

This must have been it - although I don't remember connecting using
admin in any other way since getting 1.1 installed..  
 
I solved the problem by setting the DEFAULT_ADMINISTRATOR_USERNAME  and
DEFAULT_ADMINISTRATOR_PASSWORD to some new values.  I logged in with
those new values, and then reset the admin user's password using the
User Management tab.  Once I had reset the admin password to enhydra, I
was able to connect and also to reset the values in the shark.conf file.
 
Thanks for the help.
Greg
 

-----Original Message-----
From: Sasa Bojanic [mailto:[email protected]] 
Sent: Wednesday, June 22, 2005 9:48 AM
To: [email protected]
Subject: Re: [shark] Logging into Shark using Oracle DB


Hi,
 
everything works fine with Oracle on my machine.
Check if you've previously connected to Oracle through POJO (non-CORBA)
admin application using different password for "admin" user. When you
are connecting to POJO admin, it creates new user with credentials
you've entered, and if afterwards you try to connect with CORBA admin,
your credentials won't be correct (the same should happen if you
afterwards try to connect with POJO admin - if user already exists, POJO
admin checks if password is correct).
 
Regarding problems with creating Oracle DB - I had no problems. Just
provided right configuration in configuration.properties file, started
configure.bat scripts, and all .bat scripts as well as Shark.conf file
were correctly modified, and I was able to start shark admin
application(s), connect and ...
 
Regards,
Sasa.
 
 
----- Original Message ----- 

From: Dahl, Greg (BLM) - contr <mailto:[email protected]>  
To: [email protected] 
Sent: Wednesday, June 22, 2005 3:46 PM
Subject: [shark] Logging into Shark using Oracle DB

I was successful at running Shark 1.1 using HSQL.
 
I was successfully able to configure Shark 1.1 yesterday to create
tables in an Oracle database.  Using the run.bat script, I can get the
SharkCORBAServer up and running (locally on WinXP).  I see from the
command window, that the DODSPersistentManager is using the
OracleDriver.
 
However, when I start the SharkCorbaClient (locally on WinXP), I can not
log in - I am getting a message "2005-06-22 08:28:09,989:
SharkConnectionImpl -> Login failed: Invalid username or password admin"
 
I'm getting the following stack trace:
 
2005-06-22 08:28:09,989: Rollback of Shark transaction happened.
org.enhydra.shark.api.client.wfservice.ConnectFailed: Connection failed,
invalid username or password
 at
org.enhydra.shark.SharkConnectionImpl.connect(SharkConnectionImpl.java:7
1)
 at
org.enhydra.shark.SharkConnectionImpl.connect(SharkConnectionImpl.java:4
3)
 at
org.enhydra.shark.corba.SharkConnectionCORBA.connect(SharkConnectionCORB
A.java:34)
 at
org.enhydra.shark.corba.WorkflowService._SharkConnectionImplBase._invoke
(_SharkConnectionImplBase.java:49)
 at
com.sun.corba.se.internal.corba.ServerDelegate.dispatch(ServerDelegate.j
ava:353)
 at com.sun.corba.se.internal.iiop.ORB.process(ORB.java:280)
 at
com.sun.corba.se.internal.iiop.RequestProcessor.process(RequestProcessor
.java:81)
 at
com.sun.corba.se.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool
.java:106)
 
But I have no idea what parameters to look at.  I've tried several
different ids.  I've looked at the Shark.conf and configure.properties
files to see if something was accidentally changed, but as far as I can
see, the only values that were changed were the
DatabaseManager.DB.sharkdb.Connection.User  and password (which are the
correct values for connecting to the Oracle database).  
 
I should be able to login using the default "admin" and "enhydra" but it
now currently rejects.
 
Any thoughts where I can look for something that may not be configured
correctly?
 
Thanks for your time,
Greg
 
 




  _____  

******* Confidentiality Notice *******
This email, its electronic document attachments, and the contents of its
website linkages may contain confidential health information. This
information is intended solely for use by the individual or entity to
whom it is addressed. If you have received this information in error,
please notify the sender immediately and arrange for the prompt
destruction of the material and any accompanying attachments.