Dear PaulHolmes. The password we use it --not-- encoded as {SAS002}B6535B5C02BB1BC110FD31944FC989D3. It is something else. But we just compared our encoding with proc pwencode and the one that we find in the libname from the management console is indeed something different every day we try to fix the problem 🙂 When we look at the error trying to register tables the password is shown as XXXXXXXXXXXXXXXXXXXX ; without quotes, showing a space at the end. Timmy, the Oracle account we used to register tables is specified using the managment console user manager (Usermanager-> users-> accounts) We are absolutely sure that this user/password specified there is correct. The connection (server manager) uses the Oracle_ADB, our custom AuthDomain and path leads to the service name in the tnsnames.ora. We cant use DefaultAuth because that is all the SAS users and has nothing to do with users on the Oracle-DB-side. I wonder, do we need a SAS technical user set up on the Oracle DB side? When we use EG to register the library and use our custom AuthDomain "Oracle_ADB" it works fine. Even DefaultAuth works strangely..the users in DefaultAuth are not known to the OracleDB. However to register tables using Management Console it does not. We are going nuts here 🙂
... View more
