Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-5801: Error using ANSCLP script when connecting to Oracle DB with Centrify DB2 Plug-in

Centrify DirectControl ,   Centrify DirectControl Plugins ,  

12 April,16 at 11:46 AM

Applies to:

Centrify DirectControl with Centrify DB2-Plugin 4.5.0 on RedHat 6.x & Other Linux Platforms
 

Problem:

Running ASNCLP commands to connect to remote Oracle DB using Centrify DB2 module produce an error.  The asnclp run on the DB2 remote server while trying to authenticate <dbinstance> against <capitalizeddbname> at the target server.
It tries to connect to a remote Database using user/password then fails.  If the username and password tried locally on the Database server, it works.
 
Example:
remote server target server
asnclp --- DB connect à DB: CUT02CUR, User: cut02dbi
 
The connection failed with the error as shown below:
CMD: SET SERVER TARGET TO DB CUT02GWD ID cut02uga PASSWORD "Passw0rd";
====
ASN2022E The action ended in error. An SQL error was encountered. SQL message is "[jcc][4038][12241][3.65.110]
T2LUW exception: SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
ERRORCODE=-30082, SQLSTATE=08001".
ASN1954E ASNCLP : Command failed.

 
Note: ASNCLP program is a command-line interface for administration of SQL Replication, Q Replication (Q-rep), Classic replication and relational Event Publishing.
 

Cause:

The issue is ANSCLP script will connect to both source Domain Controller and target Database to generate SQL for later run.  When ANSCLP connect to remote server, it tries to connect as instance owner (local) with password.  In this instance, it sends over username in upper case. 
 

Workaround:

See Resolution.
 

Resolution:
  • Set the following parameter in /etc/centrifydc/centrifydc.conf :
db2.userpass.username.lower: true
 
  • Run ‘adreload
  • Restart DB2
  • Test ANSCLP script

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.