Skip to Main Content
Forums

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Oracle Forms

Purushotham_MukthaAug 19 2019 — edited Aug 20 2019

Hello,

        

Our current setup system H/W and S/W specifications used for setting up Oracle Forms/Reports Applications:

  • Oracle Virtual Machine 4v
  • Oracle Linux OS 7.4v                     
  • Oracle Forms/Reports 12cR1
  • FMW Infrastructure + WebLogic Server 12cR1
  • ORDS 3.0v for Web Listener

Can somebody tell me the pros and cons of migrating Oracle Forms/Reports 12cR1 into Oracle APEX?

Also, Can you please share your views/comments on below questions.

               1.  How to Convert Existing Oracle 12c Forms and Report into Oracle APEX?

               2.  How to convert existing Oracle Reports into BI Publisher/Apex ?

               3.  Externally we have used Oraclebarcode.jar custom files for Barcode printing? How Can i use the same if migrate to APEX? what about existing Installed Printer on Oracle Linux Server?

               4.  Extended license support Oct 2020 is near and thinking about leveraging of existing oracle forms/reports applications ?

Many thanks in advance!

Regards,

Purushotham

Comments

Dude!
Answer

Yes. Each database will require its own SGA segment and additional databases will add too the total size required. POSIX or /dev/shm shared memory is similar to a RAM disk, which maps memory to virtual files to be shared among processes. By default, the maximum size of /dev/shm is 50 % of the physical or installed RAM. It does however not reserve or allocate RAM other than what is actually being used.

Keep in mind that Oracle database AMM and /dev/shm are not recommended for large memory configurations. As I recall, if your SGA is greater than 2 GB, you should use kernel hugepages instead. Kernel hugepages are more efficient due to larger memory pages, which requires far less resources for memory management and results in much better performance.

An Oracle database instance can use SYS V shared memory, which is either kernel hugepages or conventional 4k memory pages, but cannot use POSIX /dev/shm for SGA and SYS V at the same time. You can however use different shared memory concepts for different Oracle database instances on the same server. For example, running an +ASM instance using AMM and another Oracle database using kernel hugepages and ASMM.

Speaking of shared memory, the SHMMAX kernel parameter applies to SYS V shared memory only. It's a safeguard parameter to limit how much shared memory a process can possibly use and needs to be large enough to fit the largest SGA of any of your Oracle databases. SHMMAX for a server that runs Oracle database is typically set to 4 TB or whatever the platform being x86 or x64 theoretically supports. SHMMAX does not apply to POSIX /dev/shm and Oracle AMM.

For more info, see the following:

https://docs.oracle.com/cd/E11882_01/server.112/e10839/appi_vlm.htm#UNXAR385

Btw, if you have to use OS release 5, use 5.11 at least. There is no reason to run 5.6, which is obsolete.

Marked as Answer by Jhil · Sep 27 2020
1 - 1

Post Details

Added on Aug 19 2019
#forms, #moved-from-devops
10 comments
785 views