%META:TOPICPARENT{name="ErrorMessagesP"}%
==Error Messages (P)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

    
===Proxy not authorized to connect as client===

The "proxy" error is associated with Oracle authentication failure. If you experience the "proxy" error, insure that you pass the correct Oracle username and password in your Data Sources. If the error persists, Multi-Tier users may hardcode the Oracle username and password in the <nop>OpenLink Session Rules Book. The following instructions assist Multi-Tier users with this task:

1. Use a text editor to open the oplrqb.ini file, which you find in the /bin sub-directory of your <nop>OpenLink server components installation.

2. Locate the [generic_oraxx] section, which corresponds to your <nop>OpenLink database agent. For example:

{{{
[generic_ora81]
Description = Default settings for Oracle 8.1.x agent
Program = ora81_mv
Environment = ORACLE81
ReUse = always
;CommandLine =
;ConnectOptions =
;Directory = /tmp
;Database =
;Userid =
;Password =
;ReadOnly = Yes
}}}

3. Remove the semicolons in front of Userid and Password.

4. Hardcode the Oracle username and password. For example:

{{{
Userid = scott
Password = tiger
}}}

5. Save your changes and exit the file.

6. Restart or reinitialize your Request Broker.

7. Test.
    

===Evidence===

Data Source Attributes
DBMS Version
Request Broker Log