tag:blogger.com,1999:blog-5215551487816981140.post6080143359760954424..comments2024-03-28T22:27:48.595-07:00Comments on ORA-00001: Unique constraint violated: APEX plugin files and 404 not found in ORDS Morten Bratenhttp://www.blogger.com/profile/12300886042835631690noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5215551487816981140.post-63141830667682863992016-12-05T09:52:26.135-08:002016-12-05T09:52:26.135-08:00@Dietmar: Thanks for the feedback, that's a gr...@Dietmar: Thanks for the feedback, that's a great tip!<br /><br />- MortenMorten Bratenhttps://www.blogger.com/profile/12300886042835631690noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-39484761334614504272016-12-05T08:14:59.701-08:002016-12-05T08:14:59.701-08:00Hi Morten,
nowadays (learning from the multitude...Hi Morten, <br /><br />nowadays (learning from the multitude of issues between ords and apex) I always recommend to keep things separated. <br /><br />Meaning I use two instances of ords (ords.war and rest.war as a copy of ords.war) and configure them completely separately with separate configuration directories. <br /><br />When using <b>java -jar ords.war install advanced</b> I can choose NOT to install the ORDS_METADATA repository for an APEX environment (the ADVANCED part is critical here). Thus I can access apex via /ords and (if and only if required) the new rest support using /rest, makes my life a whole lot easier. <br /><br />Plus, I can easily use a higher version of ORDS for APEX without having to patch the repository in the database backend (because it doesn't use ords_metadata at all). <br />Also I can serve multiple apex instances having different versions of ords_metadata installed in the backend ... <br /><br />This approach is just sooo much better, don't have theses issues any more at all. <br /><br />Cheers, <br />~Dietmar. <br /> Anonymoushttps://www.blogger.com/profile/04283721022948206416noreply@blogger.com