Experienced an issue and would like to try and replay some trace files from when the error occurred.
When trying to use a trace file from the udump directory on the database server, BMF always gives an error of File does not contain any SQL to import that was not a dependent statement.
While Oracle is doing tracing, if it gets a SQL that was generated from another SQL statement, such as a SQL statement inside a called package function, then Oracle indicates that the SQL was generated/dependent on another SQL by setting a value of dep=1 (or higher depending on the depth).
BMF will not import these dependent SQL since they are generated from other SQL statements and it would not be realistic to include these dependent SQL since when BMF makes the original function call, the dependent SQL will automatically be executed.
So the trace files you are importing do not include any SQL that are dependent SQL.
So BMF only imports SQL with dep=0. One way this can happen if the trace was started after the original SQL (dep=0) was executed.