The status of the SDO JSR - known as JSR 235 - is unclear. It was promoted by BEA and IBM in the JCP and approved very quickly. However, the second version of the SDO specification was not submitted to JCP. In fact, the scope and context of the SDO specification has changed completely:
SDO is now a multi-language specification, with the second version including a C++ SDO API and unofficial PHP implementations already available.
SDO is now supported by several of the major industry vendors, including Oracle, Rogue Wave Software, SAP, and Siebel.
SDO is now positioned as the SOA data services API. The lack of a standard API for data access in SOA was an unusual situation. The Java-only SDO JSR was not really in a position to become the standard API.
SDO is now directly associated with Service Component Architecture, which is considered by industry analysts to be a very important strategic move by several vendors outside the JCP
This all means that the SDO JSR is probably finished. Version 2.0 and onwards of the specification will not be submitted to the JCP.