Strange behavior with connect id
I thought I had seen everything. Not true. In ten years I have never seen anything like this.
Installed a db on Linux server and was runnning great for 2 weeks. Installed second database on same host (and same connect id), They changed host names on the server and my original DB no longer allows any p/soft client connectivity (unix or windows). Second db running great still.
Get this.......When launching app designer or data mover, the error is
Invalid User ID and password for signon. But when it takes me back to login screen, it will in fact allow access the second attempt. Has anyone every seen anything so strange? Logins allowd only after 2 attempts -regardless of the client machine. It acts as though it does not recognize my connect id the first time, but then allows me in after second attempt.
I could really use some expertise on this if anyone has heard of this.
Thanks much,
Terry
Installed a db on Linux server and was runnning great for 2 weeks. Installed second database on same host (and same connect id), They changed host names on the server and my original DB no longer allows any p/soft client connectivity (unix or windows). Second db running great still.
Get this.......When launching app designer or data mover, the error is
Invalid User ID and password for signon. But when it takes me back to login screen, it will in fact allow access the second attempt. Has anyone every seen anything so strange? Logins allowd only after 2 attempts -regardless of the client machine. It acts as though it does not recognize my connect id the first time, but then allows me in after second attempt.
I could really use some expertise on this if anyone has heard of this.
Thanks much,
Terry
Replies to This Discussion
-
Permalink Reply by Derek Tomei on -
Hi Terry,
A couple of questions.
Are you logging in to the database or the application server? Since they changed the server name, did you recreate the application server?
Derek
-
Permalink Reply by Terry Hartson on -
Hi Derek
Yes, the database from any windows (or unix) client. But yes, it is the database server.
The database itself sits alone on the Linux box, the app/batch are separate unix machines, and of course the client machines
are all windows. On the windows clients, I get a second attempt to login (the successul one), but on unix machines
there are no gui's and no second attempts so app/batch fails immediately.
The server name change was on the database server only.
It almost appears like the connect cannot authenticate the first attempt, but second attempt it does. And once in, everything looks normal, so I don't believe there is corruption of any kind. (that was my first though).
Thank you for your reply.
Terry
-
Permalink Reply by Terry Hartson on
-
Derek
One more observations....
Boot strap mode util such as data mover have no issue. As you know, they do not use connect id but rather access id. Access id appears fine.
Also, no issue connecting to database from a command prompt either client or server. But as soon as p/soft is invoked, that is where the problem begins.
Thanks
Derek Tomei said:Hi Terry,
A couple of questions.
Are you logging in to the database or the application server? Since they changed the server name, did you recreate the application server?
Derek
Custom Search
Latest PeopleSoft Jobs
Senior HRIS Business Analyst
Salt Lake City , UtahPayroll Specialist
Natick , MassachusettsController
Indianapolis , IndianaPeopleSoft Developer (2 spots)
Saint Paul , MinnesotaPart-time Accountant - College Degree Preferred
Schaumburg , Illinois© 2010 Created by Derek Tomei
