SSO to SSB Failing unexpectedly - ORA-20001 Error
Hi everyone!
in our test environment the SSO to SSB stop working and started giving this error:
A SQL exception has occurred.ORA-20001: ORA-20001: Error in f_usermap ORA-20001: Error f_get_uprefORA-29283: invalid file operation ORA-06512: at "SYS.UTL_FILE", line 449 ORA-29283: invalid file operation ORA-06512: at "BANSSO.GOKKSSO", line 18 ORA-06512: at "BANSECR.GSPPRXY", line 293 ORA-20001: Error in f_usermap ORA-20001: Error f_get_uprefORA-29283: invalid file operation ORA-06512: at "SYS.UTL_FILE", line 449 ORA-29283: invalid file operation ORA-06512: at "BANSSO.GOKKSSO", line 18 ORA-06512: at line 1
Even the channels for banner stopped working, we already refresh the part from the ENC_KEY on the middle tier configuration "survival guide" that sungard sends, and nothing, our DBA started debugguing functions on the Application server in particular the GOKKSSO and isolated somo function that unencrypts the password I believe has something to do with this value AUTHENTICATIONBIND_PASSWORD.
we also tried to refresh the password in GUAUPRF logged as BASELINE (thinking that the password might be wrong) but is not allowing us to change this password....
Any ideas on what to look??
Thanks!
- ma_isaura's blog
- Login or register to post comments
Hack Your Knowledge
Recent blog posts
- Luminis IV GCF Single Sign On with OSX=Failure PC=Working
- Cisco 4710 - Load Balancer
- First CPIP - ERROR
- Luminis Developer Job Available w/ Stable Organization
- Luminus Developer Job
- SSO to SSB mixed content error in IE
- Avoid email sending when add or delete user from group
- Luminis components
- Luminis 4 & Groupwise 7
- Luminis Developer Needed for Position w/ Stable Organization
Developer Links
Poll
- Login or register to post comments
- Older polls
Syndicate
Comments
I can't believe what was the problem!
Hi People!
We finally made the SSO to SSB work!!...
I am sorry to say this... we are fairly new even to Linux (which is our OS for the portal and ORACLE servers)... what was happening was that the ENC_KEY directory didn't have read permitions.
our DBA says that he isolated the functions until the portion that reads the ENC_KEY from the directory, and then went and found out that the directory did not have read permitions.
something so simple can complicate things a bunch!... the only problem is tha portal was working perfeclty before, what or who removed this permitions??... something to ask the pillow...
Best,
Isaura