Hello,
it looks like schema validation and any operations that occur between schema validation and start of sysadmin subsystem are already costing you around 14 - 16 minutes alone.
These three log statements are interesting:
05:02:18,359 INFO [domain.schema.SchemaBootstrap] Schema managed by database dialect org.alfresco.repo.domain.hibernate.dialect.AlfrescoOracle9Dialect.
05:11:19,838 INFO [domain.schema.SchemaBootstrap] No changes were made to the schema.
05:18:27,012 INFO [management.subsystems.ChildApplicationContextFactory] Starting 'sysAdmin' subsystem, ID: [sysAdmin, default]
One thing you can try for starters is to disable schema validation. This is typically only required for upgrade scenarios and not that relevant in the day-to-day operation. Also, I know from personal experience that Oracle can be slow when retrieving database metadata from a shared service (did not figure out why precisely) / larger database server.
Depending on how much that drops your startup time, I suggest you go ahead and add some SQL profiling / logging to your Alfresco system to see what Alfresco is talking with the database. Even if the database is fast, there may be an issue where Alfresco is talking "a lot" with the database which can slow things down depending on network overhead.
SQL logging can be added via P6Spy or other JDBC logging facades, if it is not possible to log / monitor on the DB server side.
One customer of ours once encountered a bug in Alfresco which would created thousands of unnecessary transactions due to bad scoping, which only hurt the customer due to a "larger than normal" network roundtrip time.
Regards
Axel