Oracle Forms

You are right in that this is not really a "Forms" question.  However, the information you need is here:

https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/asadm/changing-network-configurations.html#GUID-2D7EA55…

Note also that although it should be technically possible to use a 19.x DB with Forms 12.2.1.2, I strongly recommend you move to 12.2.1.4.  This version includes a newer database client layer, as well as an updated pl/sql version (and other db related updates).  Also important to understand is that 12.2.1.2 is no longer entitled to error correction.  So if you hit an issue that is new and there are no existing patches for it in 12.2.1.2, your only option at that point would be to upgrade.  Having to upgrade under those circumstances is rarely fun.  Better to upgrade to a supported version before moving to a new db in my opinion.

Ral_MK wrote:
I hope this is the right area, if not I apologize and can move it to wherever you need it to go.
I currently have an Oracle forms installation (12.2.1.2) running on 12.2.0.1 Oracle database and we are upgrading the database to 19c. 
My question has to do with the repository that is connected to our current database. If I do a seperate db install of 19c, is there a way to move that repository that was created to the new db? If I upgrade the 12c db to 19c will it affect the repo?
Or is there a way to recreate the repo after the db has been moved and not kill the full application install? If so what will need to change on the application side? 
If you need more information I can try to provide it, I hope I explained it well enough. I am just trying to not alter the application server install if I do not have to. 
We want to have 12.2.1.2 forms running on a new 19c db.

I think the easiest thing to do would probably be to run the RCU and create a new repository in the new database once it's up and running.

Full blown caveat, middleware isn't my strong suit so if you get more advice please weight my response appropriately

Cheers,

@"Tubby",

The repository is tied to the WLS Domain.  Therefore, you can't "create" a new one unless you are also prepared to create an entirely new Domain.  In most cases, creating a new domain is not at all desirable since it has all your custom configurations and deployments.

Michael Ferrante-Oracle wrote:
Tubby,
The repository is tied to the WLS Domain. Therefore, you can't "create" a new one unless you are also prepared to create an entirely new Domain. In most cases, creating a new domain is not at all desirable since it has all your custom configurations and deployments.

Good to know, thanks!

Cheers,

I appreciate this! I am afraid I am not in charge of making the call to move  to 12.2.1.4 but I made a note of your advice and will keep that in mind. I appreciate the help and will research more from the link you provided. Thanks again

Hello

I migrated from db11g to 19c : 19.7 last patch (April 2020) last for NOT- CDB , remeber that, from 20c is not possible to have NOT-CDB,

and I created new VM machine with  installed a new  oracle db , it serve only to store repository, therefore at end,  I have 4-tier schema:

DB 19c

weblogic 12

DB for RCU

and client