Hello,
It is normal that brconnect -c -f check fails with an ora-1017 error,
as you are not providing a user for connection, Brconnect tries then to connect using Oracle system account and the default password.
You should always specify either a specific account "-u sapsr3/password" or "-u / " that means you are connecting using external authentication (OPS$).
In fact you should always connect using OPS$ as it avoid submitting a command line with an visible password in it.
[-u|-user [<user>[/<password>]]|/|//|//<os_group>]
user name/password for database connect
default: system/<default_password>
There is a way to activate traces on BR*Tools by setting en envt variable (BR_TRACE = <level>) or adding a parameter (-TRC <level>) to the BR*Tools command line as stated in the here under note.
Regards
29321 - Creating traces for BR Tools
The following trace levels are available:
1 => Tracing the calls of external prog
2 => Tracing SQL statements
4 => Tracing the call of internal funct°