R12.2

[Sri]

Hi erman,

Hope you are doing good, need ur favour once again.

Can we run autoconfig on patch file system without disabling logon trigger?

Thanks,
Raam

[ErmanArslansOracleBlog]

No. You probably will get an error if you do this.

[Sri]

Thanks for the update erman,what is the use of this logon trigger in 12.2

[ErmanArslansOracleBlog]

it is an  after logon trigger. It is an online patching related thing.
You can always view its code using;

SQL> show long;
long 80
SQL> set long 20000
SQL> select dbms_metadata.get_ddl('TRIGGER','EBS_LOGON','SYSTEM') from dual;

Anyways;

It gets the service name that you are connecting to using sys_context userenv.
If you connect to the patch env. I mean if you are connecting to the database using patch service name, then the trigger checks if there is a E-Business Suite Patch Edition exist in the database. If not it gives error.
it reads the service name that you are connection to and the db_domain from your session env.
IF the service name is ebs_patch;
then;
it gets the patch edition name
it sets the current edtition to patch edition.
it alters your session so that pathing actions will wait for locks if needed
It gives error if E-Business Suite Patch Edition does not exist

[Sri]

Thank you. Will run edition uses this trigger?

[ErmanArslansOracleBlog]

What do you mean?
I already explained the use of this trigger. Read above.