I think you are saying you are not able to store your insert as a textual plsql block.
While there is not a production use case for writing a geometry insert for a geometry with 60,000 vertices as plsql or sql text, sometimes it is helpful to be able to pass about a problem or example as a text statement. The issue is that for Oracle when you type out the raw SDO_GEOMETRY constructor each individual ordinate is seen by the parser as a distinct DIANA node. So you just quickly run out of nodes and get the error message that the program is too large.
"One simple trick" for writing modest-sized geometries would be to store the insert statement as dynamic SQL text. In this case the text sql string is seen by the parser as a single node and thus you can cram in 32,767 characters worth of geometry constructor text. But that won't work for your 60,000 ordinate geometry.
For big stuff I have written the following utility which will crunch your geometry into a compressed hex string for placement inside a plsql statement (and decompress it afterwards)
This should allow you to store your 60,000 vertice geometry as a plsql insert statement for sharing with others. There are still limits using this technique but they are much, much higher.
Here is an example of the code in action whereby folks were arguing about an Oracle Spatial problem caused by a geometry which happened to be too large to provide as straight-forward text in a plsql block within a forum entry. So I just packed it down so we could all see and test what was happening.
Hope that is helpful. Note again this should be only used to share geometries between humans and not as part of your production ETL processes.