Startup command in JDBC

Question

How can i execute the startup and recover commands for oracle usingJDBC OCI driver

Answer 1

One way to control a database when the are a 'lot' of attributes is to create a named attribute table. So instead of this
  table X - fields: name, color, width, height, finish, texture, cost
  data X
         bear, brown,       14, 14, shiny, fuzzy, $14
         top,  red and blue, 3,  3, shiny, hard,  $1
.one uses this
  table X - fields: name, id, cost
  table Attr - fields: X_id, name, value
  Data X
         bear, 1, $14
         top,  2, $1
  Data Y
         1,  color, brown
         1,  width, 14
         1,  height, 14
         1,  finish, shiny
         1,  texture, fuzzy
         2,  color, red and blue
         2,  width, 3
         2,  height, 3
         2,  finish, shiny
         2,  texture, hard
     The trade off is ease of use in programming vs more complex logic and possibly more storage space (noting that name in Y could be a number saves on space.)
This might actually result in saving space if the attribute values are sparse - not all of them have values.
This can slow down searches and make queries slower. But that greatly depends on the query. There are cases where this can make it substantially faster. That depends on the nature of the data and the needed queries.
An alternative to this is to make a table for each attribute. Once again there are trade offs there. And it probably isn't applicable for 'attributes for a house'.
Notice in the above that cost is not part of the attribute table. This is a design decision that once again is driven by the needed queries. Presumably cost is an important query item, it will always exist and will always be returned for any query. So it can remain in the main table.
An additional table can be used - an attribute name table. Doing this, and writing code which supports the use of that makes it extremely easy to add new attributes.