This content has been marked as final. Show 2 replies
Have you considered adding the exec apps.mo_global.set_policy_context call to your connection's start-up script?
Tools -> Preferences -> Database -> Filename for connection startup scriptNot the most flexible approach, so I'm not sure if it is appropriate for your application, but just a thought. You might create distinct connection names with different start-up scripts for each org_id.
SQL Developer Team
Thanks Gary for the suggestion. I'll think about that..maybe setup connections for a couple of the DBs and org_ids I use most often and see how that works out. Might just be easier to run the context initialization quickly from one report, then the other reports as separate reports.