This schema-level trigger can help you alter a session automatically so you do not have to modify and recompile
applications that use dblink.
When GLOBAL_NAMES is set to TRUE, applications have to 'alter session ...'1 to continue using database links having names different from remote database's SID. (When GLOBAL_NAMES is set to TRUE, the database link must have the same name as the remote database's SID, otherwise you will see an ORA-02085 error whenever you try to use dblink). For applicationa that have many modules and/or forms and each one uses its own connection, programmers have to review every module and add 'alter session'. Because schema logon triggers do alter sessions automatically whenever the specified user logs on and the work moves from the client to server, programmers do not have to modify and recompile applications.
This trigger was tested on Oracle 9i. Be careful when creating or modifying this type of trigger -- any mistyping will prevent you from logging on.
CREATE OR REPLACE TRIGGER SET_GLOBAL_NAME AFTER LOGON ON APP_USER1.SCHEMA BEGIN EXEC('ALTER SESSION SET GLOBAL_NAMES=FALSE'); END;
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free Oracle tips and scripts.
- Tip contest: Have an Oracle tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical Oracle questions--or help out your peers by answering them--in our active forums.
- Best Web Links: Oracle tips, tutorials, and scripts from around the Web.