The application itself may be causing the startup to become slow. Troubleshoot Your Application and the JVM
For optimal startup performance you should set the initial heap size to the same as the maximum heap size. SELECT INSTANCENAME,TOCHAR (STARTUPTIME, 'HH24:MI DD-MON-YY') FROM DBAHISTDATABASEINSTANCE ORDER BY STARTUPTIME DESC Find the uptime of Oracle Database. During the nomount stage, Oracle first opens and reads the initialization parameter file (init.ora) to see how the database is configured. Check the startup history timing of Oracle Instance. On the other hand, if the initial heap is too small, the Java application startup becomes slow as the JVM is forced to perform garbage collection frequently until the heap has grown to a more reasonable size. THE STARTUP (NOMOUNT) STAGE: When you issue the startup command, the first thing the database will do is enter the nomount stage. If your application is small and runs only for a short time you may have to set a small heap size to avoid the overhead of reserving and committing more memory than the application will ever need. For large applications this is inevitable, but you should be aware that using an oversized heap may lead to longer JVM startup times than necessary. The JVM reserves memory for the maximum heap size ( -Xmx) and commits memory for the initial heap size ( -Xms) at startup, which takes time. The heap size has an impact on both the JVM startup time and the Java application startup time. Answer: Startup information is stored in vinstance.startuptime, and uptime can be easily computed as sysdate - startuptime, but shutdown data is problematic.
Oracle startup time how to#
The startup time includes both the JVM startup and the Java application startup.įor information on how to measure the startup time of your application, see Timing with nanoTime() and currentTimeMillis(). The startup time of an application is the time it takes for the application to get up and running and ready to start doing what it is supposed to do. Troubleshoot Your Application and the JVM.
0 kommentar(er)
