ORDS_METADATA & multiple listener versions

Question

Is anyone able to explain the ORDS_METADATA requirement (beyond that in the doco that is)?
The doco indicates that the ORDS_METADATA user is required. Which is does seem to be, as evidenced by ORDS standalone not working if the ORDS_METADATA schema does not exist.
I have 4 distinct installations of ords.3.0.0.65.09.31 on a server pointing to a particular database, and yet another server with another ords.3.0.0.65.09.31 install pointing to the same database. All work fine as standalones (without REST).
On this database, select * from ords_metadata.ords_version; returns one row, 3.0.0.343.08.03.
How do I update the ords version? Do I drop the ords_metadata schema and then allow the install process to recreate it? Assuming the new version of the install actually creates it as 3.0.0.65.09.31 (which it does not seem to do).
I would think that it possible to have multiple versions of ords all connecting to the same database. Thence I would expect that the ords_schemas table to have multiple rows, one for each ords instance running against this database. Or doesn't it matter? Am I not having problems because I am avoiding the REST side of things?
If we have more than one configured ords listener pointing at the same database, should each have its own "ords_metadata" schema?
Should we have more than one configured ords listener pointing at the same database? (With the same ORDS_METADATA?)
cheers
teedub

Answer 1

The normal oracle listener process will happily connect users to a number of databases from a number of versions - it is just told the database service name as part of the connection information.
I don't know much about the JDBC thin driver, but if its connection information includes the database service name, then I expect the listener to do what you want without trouble.