Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 240 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187.1K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 443 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
APP USER though Remote

Hi All,
I am having a challenge in getting the APP_USER name of the Remote DB.
Solution Built is: I have a Apex installed on DB "X" (X SID) and the base tables are on "Y", DB link is created on X for accessing "Y" (Y SID), we created triggers to log the User which has modified the data on Y tables into an Audit table, though Apex.
Issue: As data changes are happing over DB Link, always the username populated is DB link user instead of Apex user.
Alternatives: Pass the APP_USER (username) as a Value along with data (which needs structure changes )
Need help to provide any alternative which will capture this actual user name from Apex Login.
Best Answer
-
NS150883 wrote: Thanks for the post, pardon for my ignorance. however I am not able to pick the actual logic need to be implemented . The Audit Log Triggers are on Tables which are on the Target DB (which is accessed by Apex using DB Link), can you please help me with the details...!
This is the relevant post: Re: v('APP_USER') over database link
Set the APEX user information in the remote DB by executing the first block in the Initialization PL/SQL Code on the Security Attributes page of your application.
begin [email protected](v('APP_USER')); end;
Use the second expression to get this information in the audit triggers:
...nvl(v('APP_USER'), sys_context('userenv', 'client_info'))...
Reset the remote user information and close the DB link in the Cleanup PL/SQL Code:
begin [email protected](null); apex_util.close_open_db_links(); end;
Answers
-
NS150883 wrote: I am having a challenge in getting the APP_USER name of the Remote DB. Solution Built is: I have a Apex installed on DB "X" (X SID) and the base tables are on "Y", DB link is created on X for accessing "Y" (Y SID), we created triggers to log the User which has modified the data on Y tables into an Audit table, though Apex. Issue: As data changes are happing over DB Link, always the username populated is DB link user instead of Apex user. Alternatives: Pass the APP_USER (username) as a Value along with data (which needs structure changes ) Need help to provide any alternative which will capture this actual user name from Apex Login.
If all or most of the pages in the app(s) are modifying data in the remote database then you should probably set the context in the Initialization PL/SQL Code on the Security Attributes page, and reset it and close the DB link in the Cleanup PL/SQL Code.
-
Hi Fac586,
Thanks for the post, pardon for my ignorance. however I am not able to pick the actual logic need to be implemented .
The Audit Log Triggers are on Tables which are on the Target DB (which is accessed by Apex using DB Link), can you please help me with the details...!
-
NS150883 wrote: Thanks for the post, pardon for my ignorance. however I am not able to pick the actual logic need to be implemented . The Audit Log Triggers are on Tables which are on the Target DB (which is accessed by Apex using DB Link), can you please help me with the details...!
This is the relevant post: Re: v('APP_USER') over database link
Set the APEX user information in the remote DB by executing the first block in the Initialization PL/SQL Code on the Security Attributes page of your application.
begin [email protected](v('APP_USER')); end;
Use the second expression to get this information in the audit triggers:
...nvl(v('APP_USER'), sys_context('userenv', 'client_info'))...
Reset the remote user information and close the DB link in the Cleanup PL/SQL Code:
begin [email protected](null); apex_util.close_open_db_links(); end;
-
Exactly worked :-) thanks for the steps and details....!
-
I can't fully test that at the moment, since I do not have a remote DB available.
But Apex does set the context already automatically using CLIENT_IDENTIFER.
And as far as I remember this is also valid in the remote database session.
The structure of the client_identifier did change depending on apex version, so this might need to be adapted.
In Apex 5 it has the structure APP_USER:SESSION_ID. So to get only the app_user from it, we need to split the string.
select regexp_substr(sys_context('userenv','CLIENT_IDENTIFIER'),'^[^:]*') from dual;