Symmetry lets me assume you should edit the Oracle registry (or its equivalent) to allow visibility of system tables to an external ODBC program. It's unlikely indeed that the 'destination' could define what the 'source' makes available. But I must admit I never read the ODBC standard documents as defined by the SAG, so it's a guess indeed.
It may be necessary to define a view over the system tables in the source database, and use ODBC to access that view (if that's allowed).
Or, if all else fails, to copy them regularly to a 'normal' table, which you can surely access. But that's a rather nasty workaround.
Anyway, this is not an Access-problem. Access is only using a ODBC-datasource, which any Windows-program that knows how to connect to an ODBC-driver can do.
Hope this helps.