Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 75 Insurance
- 537.7K On-Premises Infrastructure
- 138.7K Analytics Software
- 38.6K Application Development Software
- 6.1K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.3K Infrastructure Software
- 105.4K Integration
- 41.6K Security Software
Invalid EUL objects

Hello,
We used Discoverer 10 years ago, and not longer using it after oracle de-supported. We are still seeing some EUL4 objects in Invalid list after dropping the EUL schemas..
Any Ideas..
Thanks
Lalitha
Best Answer
-
Especially if they are invalid, there is zero impact. Also, if you are not using Discoverer there is zero impact. Yes, just drop them.
Regards,
Sharon
Answers
-
Hi Lalitha,
The most likely reason is these objects are from Scheduled Workbooks. When a workbook is scheduled the following database objects are created:
A view (e.g. EUL5_B011206161506Q1V1)
A table (e.g. EUL5_B011206161506Q1R1)
A package (e.g. EUL5_BATCH_PACKAGE011206161506 )
A job (e.g. EUL5_BATCH_PACKAGE011206161506.RUN)If you are no longer using Discoverer, these objects can be removed/dropped.
Regards,
Sharon -
Thanks Sharon,
Yes, Looks like there is a scheduled job that runs every month.. We also dropped the job, You mean we just need to drop these objects and will not see anymore of EUL objects?
EUL4_B050118165224Q1V1
EUL4_B050118165302Q1V1
EUL4_B050118165340Q1V1
EUL4_B050627135621Q1V1
EUL4_GET_ITEM_NAME
EUL4_GET_OBJECT_NAME
EUL4_NAMED_ELEMS
EUL4_B050415174205Q1V1
EUL4_B070724144604Q1V1
EUL4_B070801152018Q1V1
Will try that. Thanks for your response..
Lalitha
-
Especially if they are invalid, there is zero impact. Also, if you are not using Discoverer there is zero impact. Yes, just drop them.
Regards,
Sharon